Related
Hello guys, I recently received my refurb phone back from Bestbuy. I flashed MIUI on to it and about 2 days later I'm caught in this boot loop. After reading several threads, I called and got the battery replaced. That did not resolve my issue. I used GTG's unbrick method with KEIS downloaded. ODIN "passed" it and I got rebooted into 3e recovery (not sure where my clockworkmod recovery went, unless that went with the reset). I selected reboot now, and I'm still stuck in the boot loop with samsung popping up. Any ideas?
Thanks in advance
Try this... all credit and thanks to qkster, one of the most helpful people on the infuse forums. http://forum.xda-developers.com/showthread.php?t=1524081
I would run Odin again
Sent from my SGH-I997 using XDA
I've now tried Heimdall, it allowed the phone to turn on. When I turned the phone off it got caught back in the boot loop again. So I retried while checking "flash bootloaders". All seemed to be well, it turned off and the battery charge indicator came on. I turned it back on and checked a few things out, I didn't download or change anything. Shut it back down and it's caught back in the boot loop again.
I've retried Odin 3 times too.
What the heck do I do now?!
j_e said:
I've now tried Heimdall, it allowed the phone to turn on. When I turned the phone off it got caught back in the boot loop again. So I retried while checking "flash bootloaders". All seemed to be well, it turned off and the battery charge indicator came on. I turned it back on and checked a few things out, I didn't download or change anything. Shut it back down and it's caught back in the boot loop again.
I've retried Odin 3 times too.
What the heck do I do now?!
Click to expand...
Click to collapse
after using the one click did you do a factory reset/wipe with in 3e recovery...or if you using one click, and put cwm on just do a data/factory wipe to clean all...
what i would do...because something is not cleaning...
do the one click reboot
and do the one click to get cwm....
then go into CWM
When in CWM:
1. Wipe data/factory reset.
2. Wipe Cache.
3. Go to Advance: wipe dalvik cache.
4 Go back and into Mount and Storage: format system, format data, format cache.
5. Go back and one click again to put gb back on with nothing left over...if you want to stay stock...of if you want to add custom rom
put cwm again to go to a custom rom...
may seem time consuming but sometimes it take a few strokes to clean up...
believe me i have had to do this before...
and let us know...kk
Ok guys, thanks for all of the replies.
I've tried and tried this Heimdall now 4 times, twice clicking flash bootloaders. I've gone into 3e recovery and wiped everything.
It will start and get to the setup wizard (for first time use). I click through it and I get to the main screen. I locked the screen and went to unlock it and after I "swiped" it shut down and went back into the boot loop. I retried the Heimdall again, samething happened with the setup wizard, got to the main screen, unplugged the USB cable and it shut down and back into the boot loop.
Any other ideas? I'd love to use this thing...I just got it back and haven''t been able to use it because of this.
Something similar happened to me like a week ago ..i did not know what to do so i odin back to stock about 7 times before i could reach de home screen,the first 3 times i had bootloops,3 other time i went to initial setup but as soon as i was finishing it ..bootloops,the last time i tried i was able to go into the homescreen but it had some apk left over from previous flash..so i use sgs kernel flasher to flash infusion and get back my red recovery ,then i flashed qster total wipe and flashed emencipation.....im so scared now ..i dont think i will flash anything for a while...anyway hopefully you will find the perfect combination to save your infuse good luck
Sent from my SGH-I997 using Tapatalk 2
iTchill said:
Something similar happened to me like a week ago ..i did not know what to do so i odin back to stock about 7 times before i could reach de home screen,the first 3 times i had bootloops,3 other time i went to initial setup but as soon as i was finishing it ..bootloops,the last time i tried i was able to go into the homescreen but it had some apk left over from previous flash..so i use sgs kernel flasher to flash infusion and get back my red recovery ,then i flashed qster total wipe and flashed emencipation.....im so scared now ..i dont think i will flash anything for a while...anyway hopefully you will find the perfect combination to save your infuse good luck
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
How do I use SGS kernal flasher if I can't get it to turn on? From what I read it requires root and superuser?
So I retired Odin again with no luck. Retried Heimdall by selecting Flash Bootloaders, loaded to main screen, it went back into the boot loop after I locked the phone.
update #3, got into 3e recovery and it rebooted itself from there too.
If you flashed miui you must be rooted ...and yes to use shs kernel flasher you must be in the homescreen ..can you acces cwm? If so flash qster total wipe
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
iTchill said:
If you flashed miui you must be rooted ...and yes to use shs kernel flasher you must be in the homescreen ..can you acces cwm? If so flash qster total wipe
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I may be confused now, when I reflashed to stock didn't that unroot my phone? 3e recovery is all I can get to.
j_e said:
I may be confused now, when I reflashed to stock didn't that unroot my phone? 3e recovery is all I can get to.
Click to expand...
Click to collapse
When you reflash to stock, it does not take out the root unless you erase the proper files yourself. The only thing you lose is the modded 3e recovery and CWM recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium
So, today I trade my HTC One for a RAZR XT925, $350, and a water proof 32GB Sandisk ultra sd card on Kijiji. I thought it was kinda weird to get all of this stuff, but it seemed fine at the time. Afterwards however, I found out that every time you turn off or reboot the phone, it tried to go into recovery mode or something with the android guy and a bar at the bottom in a loop and always factory reset the phone, so no matter what, every time you turned it off, it'd reset it. After hours and hours of work, I have the bootloader unlocked, rooted, CWM installed, and Cynogenmod also installed. It no longer factory resets it (I think, but i sent a text to a random number and when I rebooted it was still there), however, everytime i power off and power on, it goes into recovery mode. This is very annoying and will make it very hard to sell again, but if I can fix this last thing, I'll have a solid phone until the waterproof S4 comes out as well as having made like $100.
So basically, I need to know what to do to make it boot into the rom by default and not the recovery. Also, I searched it up and someone else had a problem where they kept booting into AP fastboot mode I think, I tried that line, it said successful, but it didnt work. For me, it's booting into the recovery by default.
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
recovery
jmcdonald58 said:
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
roguezz said:
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
Click to expand...
Click to collapse
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
recovery
jmcdonald58 said:
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
Click to expand...
Click to collapse
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
roguezz said:
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
Click to expand...
Click to collapse
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
coldtech said:
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
Click to expand...
Click to collapse
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
coldtech said:
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
Click to expand...
Click to collapse
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
mentose457 said:
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
Click to expand...
Click to collapse
is there an alternative to flash the stock ROM on a locked device?
coldtech said:
is there an alternative to flash the stock ROM on a locked device?
Click to expand...
Click to collapse
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
Thanks for the hint, will give it a try. RSDLite just completed flashing, but the odd behaviour of the phone is still the same. Guess I might just have a broken phone... :/
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
coldtech said:
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
Click to expand...
Click to collapse
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
mentose457 said:
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
Click to expand...
Click to collapse
the fb_mode_clear was the culprit, thanks a lot!
and the error says: "downgraded security version. update gpt_main version failed. preflash validation failed for GPT" - which is still keeping me from flashing stuff via fastboot.
since I can't fastboot flash at the moment: do you happen to know where I can get the german modem image so that I can flash it using CWM? I think through all the flashing and trying I have a corrupt or wrong modem file (probably the US version). I can not log into the carrier network right now. it asks me for my SIM PIN and unlocks the SIM, but that's it. so I can't make phone calls or anything right now.
I have been running liquid smooth 2.9 for about a year now with no issues. Last night my battery died and I plugged it in and tried to boot up immediately as I needed it. We'll it shut off again and I let it sit for a few minutes then tried to reboot. Now it just stays stuck in the boot splash screen. I can boot into TWRP but get a failure when restoring. It's telling me E: no packages found to fix. Is this a corrupt backup file or something worse? I can get into Odin or TWRP. I have an older backup saved on my PC, is it worth trying to move that to ext sd card. Thanks in advance for any thoughts
Drew
Update - I tried to ODIN back to a stock image. I get a sucessful load with VRUCML1, but it gets hung up on the verizon load screen now. I tried to ODIN VRALG1 and I get a fail after the aboot step every time. I have tried different cables ans usb ports as well. What are my next steps, if any?
Thanks
Drew
Flash tools, boot it in flash mode, click unlock bootloader, then remove USB and try booting.
Sent from my C5302 using XDA Premium 4 mobile app
justdrew424 said:
Update - I tried to ODIN back to a stock image. I get a sucessful load with VRUCML1, but it gets hung up on the verizon load screen now. I tried to ODIN VRALG1 and I get a fail after the aboot step every time. I have tried different cables ans usb ports as well. What are my next steps, if any?
Thanks
Drew
Click to expand...
Click to collapse
You shouldn't of used the 4.3 stock rom. Now you're probably stuck on it. Post what it says in download mode and I'll direct you to a proper fix.
Sent from my SCH-I535 using Tapatalk 2
justdrew424 said:
Update - I tried to ODIN back to a stock image. I get a sucessful load with VRUCML1, but it gets hung up on the verizon load screen now. I tried to ODIN VRALG1 and I get a fail after the aboot step every time. I have tried different cables ans usb ports as well. What are my next steps, if any?
Thanks
Drew
Click to expand...
Click to collapse
You cannot uee any odin file but the vrucml1 one because you are forever locked. try to flash it again but after you get stuck on the samsung logo pull your battery and do a factory reset in stock recovery.
seanawake said:
Flash tools, boot it in flash mode, click unlock bootloader, then remove USB and try booting.
Sent from my C5302 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Horrible advice! He is on the 4.3 bootloader after the ml1 flash. If he did that he would hard brick!!
Sorry didn't update sooner. Wish I would have seen about the locked bootloader before flashing. Anyways after a few attempts and battery pulls it finally turned on and allowed me to setup as a new phone. I was able to root the phone with saferoot. Kingo would not work for root access. Hopefully an exploit comes along in the future to unlock the bootloader..
Thanks for the help
Phone: Samsung Sprint S5 GM-900P
System: Windows 7
Build: KTU84P.G900PVPU1ANK4 (4.4.4)
Recovery Screen shows:
Android system recovery <3e>
KTU84P.G900PVPU1ANK4
Additional files available/used:
Odin v3.07
CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
philz_touch_6.57.8-klte.tar
ERROR shown after reboot into recovery:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
I tried following the directions from this thread:
ODIN Installation (detailed)
http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Everything worked as I thought it should, but the phone hangs at the recovery screen with above error.
I flash phil's recovery, and the phone will then boot up as normal, but SuperSU reports unable to inject SU binary
I dont care about tripping knox, just looking for a stock build with root (recovery and system) added.
I have rooted my Epic, S2, S3 & S4 with no issues, and as far as I can tell, everything runs as it should, the phone just hangs after the reboot at the recovery screen and never starts the rooting process in the recovery.
I figure I am either missing something simple, or got an update that root wont take with.
Anyone have any tips as to what I am missing and/or doing wrong?
Did you try flashing them from a powered off state, ie battery pull or power off then booting to download mode? That's an essential step in each odin flash
Sent from my SM-G900P using Tapatalk
Yes I did, but I guess I can always try again to be 100%, thanks. :good:
I actually have been flashing for years, that is why I am so puzzled, as everything went how it is supposed to, it is just the rooting process does not start once the phone reboots into recovery.
I watched the vid to see if I just dropped a step, it all matched, but where the phone boots into recovery and asks to root, just never seems to kick off.
You can also try download supersu zip 2.36 then odin custom recovery and flash supersu then boot up. That's what I did on nk4
Sent from my SM-G900P using Tapatalk
banccalif said:
Did you try flashing them from a powered off state
Click to expand...
Click to collapse
This helped... I got it fixed!!
The version of ODIN I had, had auto-reboot checked, and grayed out so you could not uncheck.
I ODIN'ed philz_touch_6.57.8-klte.tarphilz
when ODIN showed the block with finished, and before the phone restarted, I pulled the battery (had back open) & the cable and didnt let boot
I ODIN'ed CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
Pulled battery/cable (no booting!!), then booted directly into Recovery
Waited, it came up into custom recovery, I selected reroot, and BAM!!
Glad to have helped!
Sent from my SM-G900P using Tapatalk
DCRocks said:
This helped... I got it fixed!!
The version of ODIN I had, had auto-reboot checked, and grayed out so you could not uncheck.
I ODIN'ed philz_touch_6.57.8-klte.tarphilz
when ODIN showed the block with finished, and before the phone restarted, I pulled the battery (had back open) & the cable and didnt let boot
I ODIN'ed CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
Pulled battery/cable (no booting!!), then booted directly into Recovery
Waited, it came up into custom recovery, I selected reroot, and BAM!!
Click to expand...
Click to collapse
^This did it for me, holy crap!
I followed the root procedure to a 'T' like you and it would get stuck exactly where yours got stuck.
Seems to me that the stock recovery after rooting is what may be the culprit if this happens???
Either way now I can get everything going hopefully and remove the bloat, some of the nag notifications, etc.
Thanks
I tried these exact steps and I am still getting errors.
y0c0nsci3nc3 said:
I tried these exact steps and I am still getting errors.
Click to expand...
Click to collapse
If autoroot doesn't work for you go and download supersu 2.37 zip (Google it) Odin custom recovery pull battery, boot to recovery and flash supersu them you should be good to go.
banccalif said:
If autoroot doesn't work for you go and download supersu 2.37 zip (Google it) Odin custom recovery pull battery, boot to recovery and flash supersu them you should be good to go.
Click to expand...
Click to collapse
I ended up flashing the NK5 4.4.2 ROM in ODIN then used towelroot.
So I followed the same steps and nothing happened it just froze at the screen on boot.
I was using 4.4.4 stock rom. I fixed mine by installing philz or some other recovery software.
I went into the setting under advance in philz recovery and ran reroot.
It rebooted and I installed supersu and it worked perfect after that.
Hope someone else can get theres to work but I think the problem is with 4.4.4 that people and me didnt read that it doesnt work properly and you have to take extra steps.
DCRocks said:
Phone: Samsung Sprint S5 GM-900P
System: Windows 7
Build: KTU84P.G900PVPU1ANK4 (4.4.4)
Recovery Screen shows:
Android system recovery <3e>
KTU84P.G900PVPU1ANK4
Additional files available/used:
Odin v3.07
CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
philz_touch_6.57.8-klte.tar
ERROR shown after reboot into recovery:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
I tried following the directions from this thread:
ODIN Installation (detailed)
http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Everything worked as I thought it should, but the phone hangs at the recovery screen with above error.
I flash phil's recovery, and the phone will then boot up as normal, but SuperSU reports unable to inject SU binary
I dont care about tripping knox, just looking for a stock build with root (recovery and system) added.
I have rooted my Epic, S2, S3 & S4 with no issues, and as far as I can tell, everything runs as it should, the phone just hangs after the reboot at the recovery screen and never starts the rooting process in the recovery.
I figure I am either missing something simple, or got an update that root wont take with.
Anyone have any tips as to what I am missing and/or doing wrong?
Click to expand...
Click to collapse
I have an unlocked bootloader, and I installed CWM recovery for the Photon q/asanti in the ROM Manager app. I want to install CM11, but when I try to go into recovery, the Motorola dual core screen comes up, and it never goes away unless I turn the phone off. What am I doing wrong? This is really frustrating because I'm so close lol
Get a recovery designed for the HD and flash that.
Sent from my HTC6525LVW using Tapatalk
It is, and I can verify that it's installed too.
If you can't get into it, it's not installed.
Sent from my HTC6525LVW using Tapatalk
Well then I guess the app I "installed" it with is wrong.
But I have a hard time believing that. I think something is preventing it from coming up, because I get stuck on the boot screen immediately after trying to open it. The boot screen shoudn't appear at all. I've also tried giving up and resetting my phone to factory, but it just reboots. I'm bummed because it is running slow and apps are stopping, and I need this phone.
That isn't my phone by the way, it's just a picture to show the screen it gets stuck on when I try to open the recovery.
Can you get into ap fastboot?
MatreyuC said:
Well then I guess the app I "installed" it with is wrong.
Click to expand...
Click to collapse
Neither CWM or TWRP are official for this phone, so you can't install them through their apps. The recovery you attempted to install is for a close relative of the HD, but it's not correct. Get a correct recovery out of the Dev section and flash with fastboot.
Sent from my HTC6525LVW using Tapatalk
Would that be why it gets stuck on the boot screen when I try to open the recovery? The only reason I used it was because it's supposed to work with my phone and some others witht the same codename. Do you know any good tutorials on how to flash a recovery with fastboot? Because I can get into fastboot.
http://forum.xda-developers.com/showthread.php?t=2232476
Sent from my HTC6525LVW using Tapatalk
Thank you