Related
Hi everyone. I have a samsung galaxy s vibrant on android 2.2. I am a total noob with any modifications but am going overseas next month and wanted to unlock my phone. After looking into rooting etc. I downloaded odin and darky's ROM resurrection edition. I followed the prompts to go into recovery and wipe etc. and remove battery and turn back on. After using odin and restarting my phone now just flashes the start screen showing galaxy s GT-I9000. I can't enter recovery mode just download mode. I'm unsure what to do and even tried mounting another recovery file on odin which lead me to the same point. Any help would be greatly appreciated.
Try re-flashing it and see if that works, sometimes that's all it takes. It's possible you just had a bad flash.
I've tried about 5 times now and it seems to keep failing to boot after flash and sticking on the initial boot screen and flashing on and off. Is there a way to download and flash an original ROM and mount on odin to start over?
Try getting into download mode. Hold and continue to hold up & down volume controls while holding in the power button. When the Vibrant logo comes up release only the power button. If you do get into recovery that way scroll down to install zip from sd card and install whatever rom you've got on there that you want to use. Let me know if that works or not.
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Spike84 said:
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Click to expand...
Click to collapse
Look for a hard surface... concrete for example.. now take your phone and throw it as hard as you can... Just kidding don't do that, that's a permanent reboot. I know the frustration, I've been there many times. You may want to go back and read through the noob guide, I'm not sure what else to suggest. Hopefully someone else will read this and have a better suggestion. Good luck.
haha yeah the thought crossed my mind. I appreciate your help. I'm still reading through the forum. Most instructions seem to require me to reach recovery mode or usb debugging. My phone is no longer being recognized on the computer but odin is obviously still recognizing so I'm going to try a fresh 2.2 on odin and see if that works.
Good luck, I'm rooting for ya. If that does not work and your close to a T-mobile store I'd just run it in and have them check it out, they may have to replace it.
Thanks again. I'm actually in Canada and using a sub provider from bell "virgin mobile".
I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
deathbenotproud said:
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
Click to expand...
Click to collapse
Howdy, DBNP,
The Exhibit II is pretty much unbrickable...you won't need to resort to esoterica like jtag
The guide in the Exhibit II Wiki usually works out well. I'd try booting into stock recovery, doing a data wipe, then install stock with Odin. The Wiki has the links to the files you need. BTW, I didn't write the Odin portion @ the wiki; I just hosted required files when the links went stale.
Easy way to start recovery
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Once you're back up and running first thing you should do is install Clockworkmod. HTH, & good luck.
I cannot get my phone to get into recovery mode, though. if I press volume+up, the phone simply displays the firmware error message. thus, I cannot do a data wipe.
deathbenotproud said:
I cannot get my phone to get into recovery mode, though. if I press volume+up, the phone simply displays the firmware error message. thus, I cannot do a data wipe.
Click to expand...
Click to collapse
Sorry if this is redundant, but this was with:
Easy way to start recovery
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
This has never failed for me. IDK, Perhaps your earlier Odin try wiped the recover partition. Can you get into Download mode? (hold Power-on Vol-Down)
I can enter download mode, but I cannot enter recovery mode. volume down gets me into download, while up gets me the error message. I cannot get to that menu anymore.
deathbenotproud said:
I can enter download mode, but I cannot enter recovery mode. volume down gets me into download, while up gets me the error message. I cannot get to that menu anymore.
Click to expand...
Click to collapse
Are you saying that you get an error when you press Vol-Up at the initial "Warning!" "A custom OS can cause..." screen, the initial download mode screen?
when I press and hold the vol-up sequence, it takes me to the initial error of "firmware upgrade has encountered an issue..."
when I press and hold the vol-up sequence, it takes me to the menu where it says custom OS etc., press up to continue, down to cancel (restart phone).
deathbenotproud said:
when I press and hold the vol-up sequence, it takes me to the menu where it says custom OS etc., press up to continue, down to cancel (restart phone).
Click to expand...
Click to collapse
And when you press Vol-Up at this screen what happens?
it takes me to odin mode/download mode.
deathbenotproud said:
it takes me to odin mode/download mode.
Click to expand...
Click to collapse
OK, that's good. That tells us that your exhibit2's /dev/block/mmcblk0p5 partition is undamaged. AFAIK Odin when properly used, can flash a new rom to your phone. Please try again, following the instructions in the wiki, reading carefully, downloading any files that you need, if you don't have them. Please walk through the wiki procedure to reflash stock from Odin, this procedure has worked for many,many people. Keep careful notes, you may be an edge case for some reason.
I'm posting links to this thread in the discussion threads that we use, since we're not allowed a forum. These threads get the most attention.
Exhibit II 4g discussion HERE
Exhibit II 4g dev thread HERE
yeah, I have tried doing that myself, as well as my friend who is rather skilled with android devices. he tried that all himself today, as well as attempting add. nothing worked.
deathbenotproud said:
yeah, I have tried doing that myself, as well as my friend who is rather skilled with android devices. he tried that all himself today, as well as attempting add. nothing worked.
Click to expand...
Click to collapse
I think you and your friend did it wrong. You should try again, following the wiki carefully.
we re-did it this morning step-by-step with no new results. we tried three times.
odin does its thing successfully, then when it goes to reboot, instead of going into recovery mod, it just goes to the firmware upgrade issue message.
deathbenotproud said:
we re-did it this morning step-by-step with no new results. we tried three times.
odin does its thing successfully, then when it goes to reboot, instead of going into recovery mod, it just goes to the firmware upgrade issue message.
Click to expand...
Click to collapse
Sorry to hear it. If Odin won't fix your phone and you've only had it a few weeks, I'd return it. I've linked your thread to our discussion threads, perhaps someone else has an idea.
that's the issue. because I have tried to flash it via odin, they're saying they won't take it because of the firmware upgrade error that keeps coming up. :/
because they won't take it, and the normal flashing to stock method isn't working, what do you think I should do next?
deathbenotproud said:
because they won't take it, and the normal flashing to stock method isn't working, what do you think I should do next?
Click to expand...
Click to collapse
I don't know who "they" are, but the chances of anyone at a T-Mob store or a Walmart knowing you touched your phone with Odin or even what Odin is are practically nil. "It's three weeks old, I turned it on and it doesn't work. Gimmie my replacement."
Or seek out a repair service to reflash your phone.
all right, i'll take it back and get a different rep. thanks for your help, though
deathbenotproud said:
all right, i'll take it back and get a different rep. thanks for your help, though
Click to expand...
Click to collapse
I'm sorry we didn't resolve the problem. Better luck next time!
deathbenotproud said:
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
Click to expand...
Click to collapse
go into recovery and do a factory reset then reboot from recovery.
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10
Recently I obtained a Galaxy Player 5.0, I've been trying to put CM9 on it. I downloaded Odin 1.85, and the correct kernel. Now, whenever I boot it into download mode, it doesn't see it. Recovery or just straight turning on will let it see it, but not in download. I uninstalled and re installed the drivers, and even tried using Kies to install them. Nothing. I've tried the newer Odin, Nothing. I'm trying to put Clockwork Mod Recovery on it.... If there's a way to fix this, or put it on it a different way, I'd appreciate it. Also, I previously had it rooted, then unrooted it with SuperOneClick, if that helps any. I'm just tired of spending 4-5 hours a day on trying to figure this out, and so far I've found no threads that are exactly like mine. Any help would be VERY much appreciated
KannibalKorp said:
Recently I obtained a Galaxy Player 5.0, I've been trying to put CM9 on it. I downloaded Odin 1.85, and the correct kernel. Now, whenever I boot it into download mode, it doesn't see it. Recovery or just straight turning on will let it see it, but not in download. I uninstalled and re installed the drivers, and even tried using Kies to install them. Nothing. I've tried the newer Odin, Nothing. I'm trying to put Clockwork Mod Recovery on it.... If there's a way to fix this, or put it on it a different way, I'd appreciate it. Also, I previously had it rooted, then unrooted it with SuperOneClick, if that helps any. I'm just tired of spending 4-5 hours a day on trying to figure this out, and so far I've found no threads that are exactly like mine. Any help would be VERY much appreciated
Click to expand...
Click to collapse
Which brand of the Galaxy Player do you have? (International, or USA)
Also, were you able to boot into the Clockword Mod?
It's the USA version, and I'm trying to put it on there for the first time. (I'm new to this) I have to US .Tar, but Odin doesn't see it to begin with so I cant put CWM recovery on there.
Apologizes for not reading your problems for thoroughly.
Remove the drivers you have now, and kies, reboot, and install this:
(Click Here!)
Reboot again, and before you plug in your device to the computer shut it off.
Afterwards, when the device is turned off hold the bottom volume button and the power button at the same time.
Shortly after you will see the triangle, and if you get this far please let me know. I'll guide you with the rest.
Omg. Thank you SO much, man, it finally recognizes it. You're amazing! Now what?
Glad you made some progress.
Since you're using the Galaxy Player 5.0 (USA), make sure you're downloading (This!)
Next step is to open up Odin with your device, make sure your device is turned off before you connect it.
Turn on the player while holding down on the bottom volume button, don't let go till it does boot on. If it works, you'll see the download mode triangle/android.
Connect it then, to the system. If Odin refers it as a COMP (#) then it should be ready to flash.
Use the downloaded file, by placing it in the PDA section of the program. Simply put, you must browse for where you downloaded the file.
Once ready, just flash.
Now you should have Clockword Mod!
I was able to do the rest on my own, but I wouldn't have gotten that far without you, thank you SO much man, I honestly can't thank you enough!!!