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
Hi guys,
I was running stock 4.4.2 and I rooted with DP Tool, and installed CWM apk recovery from this thread. I backed up using CWM, then unrooted using DP Tool to OTA update to 5.0.1.
I started the installation from kk, the phone rebooted but instead of starting the upgrade it sent me to recovery mode. I rebooted but it keep sending me to the CWM.
I tried to restore my backup, and tried to wipe data/factory rest, but nothing changed. So I tried flashing a new rom using LG flash tool, but when I pressed the Vol-UP button and connect USB to enter download mode, it sent me again to CWM recovery.
I don't really know the rest of CWM options, so is there anyway to get out of recovery mode, or get into download mode?
Thanks in advance
Hi, this is not my first time flashing TWRP on this phone. And I have been successful so far.
Today I use Odin to flash TWRP, and it went through just fine (see screenshot), but when I enter the recovery mode, it says "Android system recovery <3e> LMY47X.G920FXXU2COH2 on top and I am very confused. I tried a few times and apparently I cannot enter TWRP while Odin kept telling me I have flashed it successfully...
Did you have "Auto-Reboot" ticked on Odin? On my Note 4 that used to mean the kernel would reflash the stock recovery upon booting. You need to untick this, turn the S6 off after flashing and then boot directly into recovery using power + home + vol up
Nope. On the S6 auto-reboot menas what it does. The phone gets rebooted after the flash is done.
To the OP: You used the correct file to flash? USed AP mode in ODIN?
I had same problem. I think you need to have rooted kernel through odin first. Idk, that us what i did.
Just so everyone knows how I solved this. I wiped everything and flash TWRP and it worked. I am not sure why, but that's how I got it to work.
I just tried to root my S7 using ODIN and CF-Auto-Root (I've done this before without issue).
It failed for some reason and now I cant get into the bootloader. Vol up Home and power takes me to an 'updating' screen then a yellow exclamation, and finally what looks like the stock recovery?
The only useful option I have is 'apply update from adb'
How can I root and flash TWRP from here?
Thanks!
Ok one step forward two steps back.
I made a mistake - I was pressing vol up not vol down to get into the downloader.
I've now flashed twrp-3.0.2-4-herolte.img.tar but the phone seems to be stick in a loop!
I can boot to TWRP ok, but when booting normally it just loops.
Ok I'm getting there...
re-downloaded and installed TWRP. It seems to have worked this time and boots the system normally afterwards.
But I still dont have root.
I also tried factory reset (from android menu and TWRP) both fail and nothing is reset.
I followed this guide http://www.stechguide.com/root-galaxy-s7-and-install-twrp-recovery/
If you have TWRP, then just flash supersu for root
Download the Superuser Binary .zip from the Internet and flash it through your now working TWRP Recovery..?
You managed to get the Bootloader working because you formatted the data and that deleted everything including the Root binary. So you just have to download it again and flash!
Let me know if I got you wrong in any way because this seems like a quick fix.
Hey. I dont understand I flash the custom recovery with odin but when i go into recovery I have stock recovery. I have tried twrp and Clockwork. Non works, The flash process is passed and complete. I wait for the phone to reboot and let it start up shut it down. Then go into recovery mode. I have taken out the battery before it starts up and go into recovery straight away but still stock... what is going wrong? I have heard about bootloader But all say its no bootloader on for s2 plus. Any help is appreciated! Thank you. If something is unclear please ask. :good:I have tried 6 custom recovery's non works. but will flash
wackyleaks said:
Hey. I dont understand I flash the custom recovery with odin but when i go into recovery I have stock recovery. I have tried twrp and Clockwork. Non works, The flash process is passed and complete. I wait for the phone to reboot and let it start up shut it down. Then go into recovery mode. I have taken out the battery before it starts up and go into recovery straight away but still stock... what is going wrong? I have heard about bootloader But all say its no bootloader on for s2 plus. Any help is appreciated! Thank you. If something is unclear please ask. :good:I have tried 6 custom recovery's non works. but will flash
Click to expand...
Click to collapse
Your mistake is you are letting it boot into system before you boot into recovery. It doesn't work like that, you obviously haven't carefully and completely read the instructions to install custom recovery via Odin.
You have to flash the recovery and then boot immediately into recovery BEFORE allowing the device to boot into any other mode, otherwise, it reverts back to stock recovery.
Here is the simplest way to do this without screwing it up.
When you flash the recovery in Odin, make sure the "autoreboot" option in Odin is UNCHECKED, then flash the recovery. When it is done flashing, disconnect the device from PC, then, you have two options, either remove the battery then immediately reinsert the battery then boot into recovery using the button combination or disconnect device from PC then power the device off then boot into recovery using the button combination.
Sent from my SM-S767VL using Tapatalk