I recently tried flashing back to stock (JFD) from a CM 2.3.7 rom using Odin 1.7 and a 512 pit file. However, along the way I encountered many problems. For starters, the phone currently does not load past the vibrant boot screen; ergo, I can't call or text. During the process of flashing the stock rom, my phone had an error saying, "data wipe failed." Then my phone went to the Vibrant boot screen, which proceeded to the battery animation, instead of the usual T-Mobile boot screen/sounds. If I pulled the USB and pressed the power button, the phone would then proceed to continuously loop through the Vibrant boot screen.
The phone is most likely bricked right now, and I don't know how to fix it. I tried looking elsewhere and found people talking about flashing a "Eugene 2.2," but I have no idea what or where to find this; can anyone help?
I went on to use AIO Vibrant Toolbox to try to restore to stock, but that persistent error keeps coming up. Halfway through the ODIN process, I can see my phone's screen show a bunch of words, scrolling up. Among those words say, "Data wipe failed."Afterwards, the phone loads the Vibrant boot screen and battery animation; ODIN says SUCCESS, although I know the flash didn't work. I have reason to believe this is why my phone isn't flashing properly?
Hope this will get you straight.
Berzxrk said:
I went on to use AIO Vibrant Toolbox to try to restore to stock, but that persistent error keeps coming up. Halfway through the ODIN process, I can see my phone's screen show a bunch of words, scrolling up. Among those words say, "Data wipe failed."Afterwards, the phone loads the Vibrant boot screen and battery animation; ODIN says SUCCESS, although I know the flash didn't work. I have reason to believe this is why my phone isn't flashing properly?
Click to expand...
Click to collapse
Try using Heimdall One Click from this thread.
This probably won't help in your case, but try pulling the external sd card if you haven't already. Pulling the external sd card has solved a few boot loops for me in the past, but they were related to a new rom install.
Related
Listen i'm somewhat new so forgive me if i posted in the wrong place.
Just hear me out please.
Ok heres a little s/a. I have a samsung vibrant, last night i flashed my vibrant which was on a rooted vibrant9 rom. To bionix 1.9.1 w/ jacs oc kernal and the voodoo lagfix. Before flashing to the bionix i switched the boot logo and .wav file to one i perfered, i also did the same for the shutdown logo. Now, per the instructions for installing bionix 1.9.1 i took a nandroid backup of my phone on vibrant9 before performing the flash. After i did i flashed using clockwork. Everything went fine, the phone flashed, rebooted and was working great. However i rebooted the phone and relized that the shutdown screen wasnt working as it should because i forgot to include the shutdown.cfg thats required. What i did was took the bionix.zip off my sd card went into it and added the .cfg file i needed. I added it back to the sd card and figured i'd just reflash and all would be fine. Not so lucky however, i tried to reflash using clockwork (which took me to the regular recovery menu you would get to holding down the volume buttons and power) and it failed giving me an error which said "error on line 80". Relizing that the instruction said that if you had the voodoo lagfix you should disable it, i decided to do a factory wipe of all data (thinking that would definitly disable voodoo) after the factory wipe i attempted to flash bionix 1.9.1 again with no luck. After the last attempt i decided to just restore using the nandroid backup of vibrant9 i had taken earlier, the phone went through the restore process with waht appeared to be no problems. After it finished i rebooted from the recovery menu then bammmm. The phone is stuck in a boot loop. Its not a normal boot loop though the initial samsung logo will pop up for a sec then the phone screen will show what looks like tv static for a sec, it just keeps repeating this. To get it to stop i have to pull the battery. Ive tried booting into recovery by holding the volume buttons and the power button, but all that happens is the phone starts into the above mentioned bootloop. As a note whenever i plug the phone up via usb to my computer a grey battery screen pops up but it dosent charge it just sits there, and if i unplug the usb it goes right back into the bootloop. Also my computer will not recognize the phone so using odin seems like a lost cause. I read in a forum for this phone just a bit earlier that its nearly impossible to brick this phone. Have i done the impossible?
Well it sounds like you have hardware locked phone. Also you cannot do a nand restore w/ voodoo enable. That's your problem. There are threads on xda about recovering hardware lock phones. You need to search. If you can get into download mode, you need to flash eugene373's "Froyo that does not brick". Also, once you get phone working, isuggest you keep a disable-lagfix zip on your internal sd.
Sent from my SGH-T959 using Tapatalk
Great Success
Ok, ok after what seems like a million tries i finally got my vibrant working. After finally getting my vibrant into download mode (by removing the battery, putting the battery back into the phone, holding down both volume buttons and plugging in the phone via usb) i used odin to try and flash back to the factory rom. The flash worked except for an error i noticed when the phone was kicked into factory recovery mode to format itself. There i noticed that at the point when all user data was supposed to be wiped it would have a failure to wipe data. After the flash completed with this error i was able to get past the boot loop. At this point my phone would finish the boot sequence but after the samsung s disappeared the screen would just stay black. However, when ever i pushed any of the soft keys on the front they would light up. So what i did was followed the instructions in the above post and used odin to flash eugenes froyo rom that wont brick. Again the flash would complete but when the phone was kciked into factory recovery mode i got an error and it wouldnt complete it would just hang. So what i did next was use odin to again flash the factory rom and to my surprise it worked. So my vibrant is now restored to its full glory. I owe everything to the patrons of this community. Thanks all.
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
itsjuztin said:
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
Click to expand...
Click to collapse
Here's some tips:
1. NEVER restore non-cm7 nandroid backups on a cm7 based rom.
2. Flash stock JFD with repartitioning checked to go back to stock.
3. Reflash vibrant bootloaders. You may have some captivate bootloaders or a mismatched param.lfs that's causing the AT&T bootsplash. It could be one or the other and mismatching captivate and vibrant bootloaders or params could lead to a brick so just flash the vibrant bootloaders since it contains both bootloaders and param.lfs.
4. DL mode depends on the bootloaders you run.
Froyo bootloaders-------------
1. Volume up and down with USB inserted and with battery disconnected
2. Insert battery without letting go of buttons
Gingerbread bootloaders-------
1. hold power and volume up with the battery inserted and with the phone powered off
2. connect USB to pc when booted into DL mode.
P.S. Can you take a picture of the front and the back of the phone so I can identify the kind of phone you are using at this moment?
The name you are using for the device you have is kinda confusing me.
Hello again fellas, I'm hoping someone helps me out of a bind I'm currently in. I just flashed JFD, but the phone is stuck in a boot loop. Here are the symptoms:
After Odin3 shows PASS:
1) Phone turns off, but instead of rebooting, shows transparent battery icon with spinning splash, blank screen, transparent battery icon with spinning splash.
2) If I disconnect from the PC, then turn on, the phone shows a WHITE screen, then the VIBRANT screen with Samsung at the bottom, then white screen, and back to the Vibrant screen.
I have obtained the same results wether "Re-Partition" was clicked or not. I am in the process of d/l AIO Vibrant Toolbox from Bay-Wolf. In the meantime, if anybody has any ideas, I'm all ears (eyes in this case). Thanks.
Did you put the proper pit and tar files in their place? Just try to flash again, you might have just had a bad flash.
Hey, thanks for the reply. After reading your reply, I checked the .pit and .tar files but it checks out.
I have also tried using AIO toolbox and used the files provided by the program but I get the same results. The odd thing is that Odin shows pass. Could it be bootloaders? I know those are sometimes an issue with Captivates, but I don't know about Vibrants.
I have a similar problem, haven't been able to solve it but try this: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Hope it helps.
Just to be sure...can you try with the files available on this post, following the provided steps:
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Look fellas this has been said hundreds of times around here.
When you flash JFD, untick reboot, when using Odin, because then it gives you a chance to do the data wipe and then the cache wipe, this has been the main culprit in almost all boot looping. and do the same with other roms as well, people just immediately reboot after a successful load, and forget to wipe this data factory reset and cache, clearing this out allows no other ghost data from previous install and the present loaders to interfere with the first time boot up, I used to make this mistake, but since doing this it stopped the boot looping.
I want to thank you guys for replying and trying to help. I will look into the links provided above, and see what I can do. I apologize if I have asked a question that has already been covered here. I'm a frequent visitor to the Captivate forums, and I'm aware what's expected of every member before they ask aquestion. However, I am doing this as a favor to friend, and I'm not familiar with the nuances of flashing a Vibrant back to stock. I also didn't have the time to peruse the forums untill I came across a solution. Thanks for all the help, and I'll update you soon on my progress.
Sent from my SAMSUNG-SGH-I897 using XDA App
dseldown said:
Look fellas this has been said hundreds of times around here.
When you flash JFD, untick reboot, when using Odin, because then it gives you a chance to do the data wipe and then the cache wipe, this has been the main culprit in almost all boot looping. and do the same with other roms as well, people just immediately reboot after a successful load, and forget to wipe this data factory reset and cache, clearing this out allows no other ghost data from previous install and the present loaders to interfere with the first time boot up, I used to make this mistake, but since doing this it stopped the boot looping.
Click to expand...
Click to collapse
Can you clarify what you mean be "it gives you a chance to do the data wipe..."?
I tried Odin and unticked reboot and then after Odin says successful, nothing happens. There is no window that pops up on the computer or the phone that gives the option to do a data wipe.
I know there's a data wipe and cache wipe option in CWM, but I can't get into CWM or any sort of recovery mode right now...
you're clarification would be greatly appreciated so that I can get out of this bootloop nightmare
So....
kafepuya said:
Hello again fellas, I'm hoping someone helps me out of a bind I'm currently in. I just flashed JFD, but the phone is stuck in a boot loop. Here are the symptoms:
After Odin3 shows PASS:
1) Phone turns off, but instead of rebooting, shows transparent battery icon with spinning splash, blank screen, transparent battery icon with spinning splash.
2) If I disconnect from the PC, then turn on, the phone shows a WHITE screen, then the VIBRANT screen with Samsung at the bottom, then white screen, and back to the Vibrant screen.
I have obtained the same results wether "Re-Partition" was clicked or not. I am in the process of d/l AIO Vibrant Toolbox from Bay-Wolf. In the meantime, if anybody has any ideas, I'm all ears (eyes in this case). Thanks.
Click to expand...
Click to collapse
Did this get resolved? I am in the same boat working on a friend's phone. Have never had an issue with Odin that I couldn't figure out. But now I'm four days in and about to pull my hair out so the magic fix would be greatly reassuring right now! Help.
You need to enter recovery mode and do data wipe. If it still don't work, try another Odin image.
So I have previously used a rom on my phone and I didn't like it, so I decided to try Gummy for Fassy 0.7.2. I wiped my data, etc before the installation of the .zip. I ran the FassyGum0.7.2.zip as instructed. In recovery I could see that it was installing as it should..then it rebooted to a loading screen that shows Gummy and a scrolling dots as though it is loading/installing something.
Well the next step according to the dev of the ROM mentions that after installing FassyGum0.7.2.zip that I need to install ModifiedGummyGapps.zip. Well due to this loading screen that hasn't gone away in over an hour I can't run the second .zip. I have tried to hold the power button to recycle the phone...nothing happens. I pulled the battery, and turned it back on and held the correct buttons to try and get it back into recovery...nothing it comes back to the Gummy loading screen every time so I can't even recover to an old ROM.
Any Advice??
Cheers
Sounds like you need to use Odin to go back to stock, and then re flash a recovery and try again
Sent from my SCH-I500 using XDA App
brakemynek said:
So I have previously used a rom on my phone and I didn't like it, so I decided to try Gummy for Fassy 0.7.2. I wiped my data, etc before the installation of the .zip. I ran the FassyGum0.7.2.zip as instructed. In recovery I could see that it was installing as it should..then it rebooted to a loading screen that shows Gummy and a scrolling dots as though it is loading/installing something.
Well the next step according to the dev of the ROM mentions that after installing FassyGum0.7.2.zip that I need to install ModifiedGummyGapps.zip. Well due to this loading screen that hasn't gone away in over an hour I can't run the second .zip. I have tried to hold the power button to recycle the phone...nothing happens. I pulled the battery, and turned it back on and held the correct buttons to try and get it back into recovery...nothing it comes back to the Gummy loading screen every time so I can't even recover to an old ROM.
Any Advice??
Cheers
Click to expand...
Click to collapse
The problem was you didnt flash teamhacksung build 1 or 2 first before flashing gummy...if you need proper instructions for flashing ics roms look up section 4 of my guide in general section.
I'm having a similar problem, except after it was stuck in a boot loop, I attempted to odin it, which froze and then led to more problems. Currently all I can do with my fascinate is get it into download mode. But, it isn't recognized in odin or heimdall, or windows. It shows up as unknown device in device manager. Uninstalling/reinstalling samsung drivers hasnt helped. I also installed Android SDK with Google Driver Package to see if it would help but it didnt. As of now I'm not sure what the next step should be as i can not odin, heimdall, recovery, or boot it. I am on Windows 7 64bit.
EDIT: As I've now gotten Odin to flash again, and my device still won't boot, I'm really starting to think Andromeda's recovery has wiped something vital that isn't restored with a "regular" stock ROM image. PIT? EFS? Partitioning? Something like that? Odin successfully flashes the whole image tar (which I've previously used successfully), and the boot splash now correctly changes to the default Samsung one without triangle, but still the phone won't boot (as described in msg #3). So I'm now wondering if there's any way to a more aggressive restore (whence the topic title change)? Or am I barking up the wrong tree here?
----------
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Daniel Smedegaard Buus said:
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Click to expand...
Click to collapse
the reason for Dream and Andromeda not booting ur phone is that, if ur paranoid rom version was latest, then it comes with the new JB mali drivers for which only Dori v7.4 and siyah v5.0 are compatible
since u have already messed up too much with ur phone, u can try the 'KIES' option as the last resort to restore it back, since odin flash is not wrk'ng for u
Okay, so I tried installing Kies and connecting it. A variety of connection attempts, but it just won't connect to the device.
But, I'm making some progress! I've found that when I can get the phone to boot into the "Firmware upgrade encountered an issue." screen, I can get Odin to flash the stock Gingerbread image (still won't in download mode). And I then get a reboot with the regular Samsung boot splash (no yellow triangle) - except it never gets past it. After about a minute, it'll go black and then boot back up to the same splash screen and the same problem.
This is the exact same image I've used previously to revert the device to stock. So I was kinda hoping to see a normal clean. But unfortunately no donut. It reminds me of a computer I once bricked by screwing with its BIOS - it never got beyond POST and so I couldn't reflash it.
Is there something like a BIOS in this thing that could've gotten damaged in some way? And if so, is there any way to use Odin or another tool to fix that?
Cheers,
Daniel
Tried flashing a couple of matching CF kernels. I now get the green battery after the grey one, but still no boot.
All turned out the be the Shun Andromeda kernel re-introducing the hard brick bug. If you have the same issue, see my reply here for links to where you can get the custom PIT trick up and running.