A lot of ForeverNOOBS like myself are going to come across this issue every so often. I have succeeded in resurrecting my SGS3 and this may help for you too...
If your phone is stuck at the samsung boot animation flashing pretty much forever your in the same boat I was in.
Chances are you select the NAND Delete option in ODIN 3 before you flashed the L710VPALEN rom.
http://forum.xda-developers.com/showthread.php?t=1737859
After the phone has rebooted every reflashing of a rom will give you the same boot loop. It doesn't matter if its flashed in odin or CWM you will most likely get the boot loop. It took 3 hours to figure that out the hard way. At some point I end up flashing the full odex update of LF9 in CWM then the LF9 baseband, and its still bootlooped.
http://forum.xda-developers.com/showthread.php?t=1743923
I dont know which one gave me stock recovery but in stock recovery you will see these warning.
e:failed to mount /file... I don't remember the exact expression but there is 4 of them e:/failed's.
I only had a few options left in the repertoire of the recovery app so I used factory reset. Immediately rebooted back into recovery and noticed my e:failed warnings had disappeared. I rebooted one more time and no more boot loop!!!! my phone is back on.
I hope this helps.
First of all, this is definitely the wrong section.
Second, for anyone reading this, the TL;DR version is: Flash the stock recovery and do a factory reset.
Sent from my SPH-L710 using xda premium
Related
I flashed CM7 last night, loaded GAPPS, and the market was updating my apps, when I noticed none of the apps were updating. updates were all failing. I went into recovery and restored BAMF 1.5 remix. Now I have a problem. I can not download or update anything from the Market, all attempts fail. I cannot access CW recovery, the HTC white screen is as far as I get. I deleted rom manager, and tried to access CW recovery and still failed. I tried to do a factory reset, and still only get white HTC screen. Tbolt is functioning, I just can't fix my issue. Please help. Thanks.
You can't get in CW recovery or stock recovery?
Sent from my ADR6400L using Tapatalk
Did you try reflashing CW through ROM Manager?
Yep. very strange. I even tried to wipe the phone with factory reset, and just get stuck on white HTC screen. I had deleted rom manager because of something else I read, and can't get it back, But I can't even get to recovery from bootloader.
You can get to recovery through the bootloader by shutting off the phone and turning it back on holding down the volume button and pressing power toggle down to the recovery option and press the power button
Sent from my ADR6400L using XDA App
Orio56 said:
I flashed CM7 last night, loaded GAPPS, and the market was updating my apps, when I noticed none of the apps were updating. updates were all failing. I went into recovery and restored BAMF 1.5 remix. Now I have a problem. I can not download or update anything from the Market, all attempts fail. I cannot access CW recovery, the HTC white screen is as far as I get. I deleted rom manager, and tried to access CW recovery and still failed. I tried to do a factory reset, and still only get white HTC screen. Tbolt is functioning, I just can't fix my issue. Please help. Thanks.
Click to expand...
Click to collapse
Actually I spent a good few hours yesterday trying to help Orio out and we attempted a quite a few things to try and fix the recovery issue, this post should offer a bit more insight to the methods used;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Never once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
Edit: problem solved.
I had already tried reflashing CWM but to no avail. I always saw 'update complete' but when trying to get into recovery it would fail to get to CWM. I retried it again and this time it seemed to take. Then it was just a matter of going into CWM and flashing the untouched quick sense rom.
Thanks.
you dont have recovery reflash recovery and you be good
Hello wonderful people of the S. Vibrant community. I come to you in order to diagnose and hopefully fix a problem with a friends samsung vibrant.
Basically here's the backstory... He wanted to root his Vibrant (2.2 i believe) to ICS so i sent him the AIO Vibrant toolbox and told him explicitly to read the instructions of the tool and any potentials roms he wants to put on his phone. Lo and behold! I proceed to take a 2 hour map and my phone is bombarded with text messages saying that he 'messed up' and the phone is 'looping' upon boot.
I absolutely do not know what the hell he did and he was intentionally vague on what steps he took and what roms he downloaded etc. He mentioned something about reformatting and downloading a new kernal ...
Anyways. As I'm an owner of a Sprint SGS2; i know that sammys are literally the hardest devices to hard brick so i proceeded to search up these forums and odin a stock tar so i can get this thing booted up.
I followed this guide
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/ and proceeded to odin back the pit and tar and it was a success.
Then it rebooted and bam still a boot loop. I tried a KA6 tar and still the same results. So I'm stuck here on how to get this phone out of the boot loop and am wondering if you guys can direct me to where I can hopefully fix this problem.
Side note. AIO Vibrant toolbox says the phone has USB Debugging mode off... (SMFH!!!!).
Thanks guys!
Download the bionix V fish man ROM. Its froyo, its good and it has an Odin flashable file. It comes with Bali kernel.
May help you on your way.
http://forum.xda-developers.com/showthread.php?p=21324042
Even though its boot looping, if you can get into recovery, you may be able to flash about any ROM you want. Wipe data/factory reset, clear cache and dalvik, and flash a good solid ROM. I've gotten out of the situation using both of the options I've listed.
May the force be with you.
I'll try and see if this will work and report back.
Well i odin'd the rom according to instructions and it's on the bali screen now for 5 mins... How long does the first boot take
lilotimz said:
Well i odin'd the rom according to instructions and it's on the bali screen now for 5 mins... How long does the first boot take
Click to expand...
Click to collapse
It does take a while. I'd let it go at least another few minutes. Then update me.
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
If your still stuck, pull battery and boot into CWM recovery. Find Voodoo lagfix in the options. Disable it and reboot the phone. That's most likely why its hanging on the first start.
After you get it booted the first time you can go later and reenable voodoo lagfix.
tried using adb reboot recovery cmd and still no dice...
I assume froyo bootloader, hold both volume buttons and power until you see Samsung text and let go. May take a couple tries.
there is no samsung text. It goes white screen then Bali screen and repeat... (boot loop i guess.. again)
Update : Flashed the second odin tar and it seems to be somewhat working now... got into recovery mode and wiped data / cache... rebooting now
Excellent. If that doesn't boot all the way go back to recovery and disable voodoo lagfix.
Well i got into samsung recovery and deleted user data & cache data.
It does indeed go white screen then Bali screen for some reason... same.
Boot loop. No option to disable voodoo lagfix. Recovery is not CWM but samsung recovery... ?!!
lilotimz said:
Well i got into samsung recovery and deleted user data & cache data.
It does indeed go white screen then Bali screen for some reason... same.
Boot loop. No option to disable voodoo lagfix. Recovery is not CWM but samsung recovery... ?!!
Click to expand...
Click to collapse
Hmm. If you have the update.zip on your phone you can click reinstall packages and it will be CWM recovery.
here's what it says...
Update media:
E: Can't mount /dev/block/mmcklk0p1
(no such file or directory)
E: copy_dbdata_media; Can't mount SD card:
your storage not prepared yet.Please use UI menu for format and reboot actions
E:Copy_dbdata_media:format SDCARD:
formatting Sd card:...
E: Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E: copy_dbdata_media: Can't mount SDCARD:
your storage not prepared yet,please use ui menu to format and reboot actions
copy default media content failed
Your internal sd has been destroyed. Your only option is running the entire os off of an external microsd card. http://forum.xda-developers.com/showthread.php?t=1580902
At least it seems like this is the case. I also had this happen to my phone, but eventually it fixed itself after odining about 20times and installing other roms. Good luck. Heres what I did http://forum.xda-developers.com/showthread.php?t=1665123)
Didn't work for some people, so the fact that mine came back might have just been luck.
le sigh...
I guess i'll try some more tomorrow. Guess he did the unthinkable and 99.9% killed a sammy. Poor galaxy s...
I finally managed to follow your instructiosn and i installed CM9 for the first time and it's now boot looping. Your instructions state to reboot into recovery mod and install it again but I for my life cannot discover how to reboot this thing into recovery mod. What are the steps and buttons again if I may ask?
lilotimz said:
I finally managed to follow your instructiosn and i installed CM9 for the first time and it's now boot looping. Your instructions state to reboot into recovery mod and install it again but I for my life cannot discover how to reboot this thing into recovery mod. What are the steps and buttons again if I may ask?
Click to expand...
Click to collapse
Pull the battery and replace it, hold vol up, vol down and power until you see screen come on then release. That should take you to recovery.
sent from the depths of helly bean
Ok so I searched the forums before this just to let you know.
I wasn't thinking and the wrong kernel got installed as the title says. So, I got into a bootloop (expected). It hits the fan after my next step :'(
I go to bootloader, then to recovery, start up TWRP, then screen goes blank and goes back to the htc bootscreen.
The odd thing is, it now has that disclaimer on the bottom for normal boot sequence.
I have attempted flashing other recoveries, erasing my cache, fastbooting roms, and fastbooting kernels. I assume my choices are limited with S-On since most of the fastboot commands return "remote:not allowed".
Do I have to wait for a RUU?
Thank you for your time in advance
UPDATE:
Finally got Clockworkmod to boot (after reflashing it at least 5 times), sideloaded a ROM, and presto it seems to be alive. Still have that disclaimer on the bootscreen, oh well :/
IF YOU FOUND THIS BY SEARCHING
1. Fast boot flash recovery "recovery file" (I used clockwork non touch)
2. Fast boot erase cache MUST!!!
3. Boot recovery
4. Sideload Rom via adb
seamarshall said:
Finally got Clockworkmod to boot (after reflashing it at least 5 times), sideloaded a ROM, and presto it seems to be alive. Still have that disclaimer on the bootscreen, oh well :/
Click to expand...
Click to collapse
Glad to hear you got it working again. Anytime you install a custom ROM though, you will see the disclaimer on the bootscreen. It isn't a big deal software wise though, it just looks ugly. I'd consider that a minor inconvenience for using a better ROM without the bloat.
So i flashed a GT-S5830i stock firmware on as it was branded to Vodafone and wanted an unbranded one but i came across some issues. So i decided to flash back to the original FW but had trouble flashing through odin. I was able to get into recovery until i stupidly decided to flash a CWM Odin flashable file that wasn't compatible for my device. Now i can't seem to get into recovery.
I am however, able to flash stock FW through Odin but that's about it.
I can't Offline charge, get into recovery or boot the phone up.
When i try offline charge, the battery shows for a split second then tries to boot up.
I need to get into recovery to try and factory wipe it to see if that will help. I doubt it though as it doesn't even get to the samsung logo.
I think something is really messed up
Any ideas?
Thanks