Database Info

Help! TWRP not starting

I tried to install/flash TWRP to my tablet (SM-P900 wifi) using Odin, but it doesn't seem to be working. I've tried Odin v3.09 and v3.07. I have also tried to install TWRP v2.7.0.1 and then v2.7.0.0 for the hell of it. I get a "pass" from Odin and it says the install was a success, but when I enter recovery mode the stock android system recover initiates, not TWRP. I've followed multiple guides to the 'T' with no success. I've even tried to reinstall my USB drivers--though I haven't had any problems connecting my device to my PC. I'm not rooted (yet). I want to root, but I wanted to make a backup before rooting because I was under the impression that I could do that with TWRP. Do I have to root to use TWRP? Any help is appreciated. This is my first time messing around with roots and such. My goal is to root to clear some bloatware and mount an external HDD. Custom ROMS and themes may be in the future, but not now. Should I definitely do a backup before rooting or just root and go from there?
Any help is greatly appreciated!

This may be a silly question, but just to make sure, you are booting into recovery mode and not download mode right? Download mode is volumn down and recovery mode is volumn up.

Graeme H said:
This may be a silly question, but just to make sure, you are booting into recovery mode and not download mode right? Download mode is volumn down and recovery mode is volumn up.
Click to expand...
Click to collapse
Not a silly question for a noob haha. Yes, I installed in download mode.

Not sure if this will help but I noticed that when I installed TWRP with autoreboot turned on and I allowed the OS to boot up I lost TWRP. I reflashed with autoreboot unchecked in Odin and then forced the tablet into recovery manually after Odin was done. TWRP loaded up that time and I immediately did my nandroid backup of stock unrooted.

muzzy996 said:
Not sure if this will help but I noticed that when I installed TWRP with autoreboot turned on and I allowed the OS to boot up I lost TWRP. I reflashed with autoreboot unchecked in Odin and then forced the tablet into recovery manually after Odin was done. TWRP loaded up that time and I immediately did my nandroid backup of stock unrooted.
Click to expand...
Click to collapse
Thank you for your reply. I ended up re-installing the stock firmware/recovery and then flashed TWRP v2.7.0.2 with Odin v3.09. It did the auto reboot, got the pass, then I turned the device off. I tried to boot up in recovery but let go of the buttons too soon, so it booted into OS again (woops). Second time was a charm though, got it to boot into recovery and TWRP booted right up. Yay. I did try to install TWRP v2.7.0.2 before I re-installed the stock firmware, but still wouldn't boot TWRP.

[SOLVED] Unable to root - Recovery is NOT SEANDROID ENFORCING

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

After rooting my nexus 5 is not booting up with non stop booting animation

I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...

nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally

funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:

funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know

I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.

First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.

Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.

fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.

Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.

hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys

@[email protected], possible power button problem?

Give up and go stock?

A burst of fearsome energy overtook me tonight and I just had to root my phone
Kingoroot, Kingroot, Towelroot etc didn't work. Then I read about this thing called TWRP.. sounds great, I said.
Unlocked the bootloader, got TWRP recovery going, tested it out, got ready to add SuperSU and the one that gets rid of bootloader unlocked screen.
Boot loop. Stuck on the Motorola logo. It aint going anywhere.
I've tried all of the suggestions I could find so far here, like using mfastboot to clear cache and user data. It's looking like a dead end. I was following the instructions on a youtube video so of course I didn't back up anything before I tried SuperSU Should I cut my losses and try the stock firmware, or could I do more damage that way?
This is going to ruin my weekend, isn't it?

bootloophell said:
A burst of fearsome energy overtook me tonight and I just had to root my phone
Kingoroot, Kingroot, Towelroot etc didn't work. Then I read about this thing called TWRP.. sounds great, I said.
Unlocked the bootloader, got TWRP recovery going, tested it out, got ready to add SuperSU and the one that gets rid of bootloader unlocked screen.
Boot loop. Stuck on the Motorola logo. It aint going anywhere.
I've tried all of the suggestions I could find so far here, like using mfastboot to clear cache and user data. It's looking like a dead end. I was following the instructions on a youtube video so of course I didn't back up anything before I tried SuperSU Should I cut my losses and try the stock firmware, or could I do more damage that way?
This is going to ruin my weekend, isn't it?
Click to expand...
Click to collapse
If you can still boot to your custom recovery its really not a big deal. Just install the ROM zip of your choosing and appropriate gapps. If you are boot looped when it starts to reboot just hold in the power button for about 10 seconds till it powers off then press and hold volume down while still keeping the power button pressed. After about 5 seconds or so of holding both buttons stop pressing both together. If done correctly you should be at the boofloader screen.

n0ts0smart said:
If you can still boot to your custom recovery its really not a big deal. Just install the ROM zip of your choosing and appropriate gapps. If you are boot looped when it starts to reboot just hold in the power button for about 10 seconds till it powers off then press and hold volume down while still keeping the power button pressed. After about 5 seconds or so of holding both buttons stop pressing both together. If done correctly you should be at the boofloader screen.
Click to expand...
Click to collapse
Yes, I can get to the bootloader. Factory reset there and reset using TWRP doesn't fix the bootloop. That's kinda where I am right now.

Uninstalling SuperSU did it! I used the un-su zip file.

Do you have one of the following 1)Motorola USB drivers for your PC and fastboot or mfastboot/adb setup for your device? 2)ROM zip on your internal storage. 3)A USB OTG drive? Any of these will work. Let me know which you have and we will go from there.

n0ts0smart said:
Do you have one of the following 1)Motorola USB drivers for your PC and fastboot or mfastboot/adb setup for your device? 2)ROM zip on your internal storage. 3)A USB OTG drive? Any of these will work. Let me know which you have and we will go from there.
Click to expand...
Click to collapse
It's ok, I'm back in business - the issue was the installation of the latest version of SuperSU. I used Install from SD Card in TWRP to install the SuperSU remover and it booted fine.
Taking my time now because I need this phone, I'm living in a new country. I backed up and tried an older SuperSU but didn't work - I suppose by doing a factory reset I might have done something that stops a root.
Edit: this http://forum.xda-developers.com/showpost.php?p=63615067

Download the latest stable build of super SU from Chainfires site here. http://download.chainfire.eu/supersu-stable
Then just flash the zip you downloaded in TWRP. You don't need the systemless version of SU if that is what you were trying to do.

n0ts0smart said:
Download the latest stable build of super SU from Chainfires site here. http://download.chainfire.eu/supersu-stable
Then just flash the zip you downloaded in TWRP. You don't need the systemless version of SU if that is what you were trying to do.
Click to expand...
Click to collapse
I think that was the one that bootlooped it. I'll be doing a backup first this time
My main reason for posting my solution in this thread is in case the same thing happens to someone else. Removing SuperSU with that un-su.zip solved it for me.

problem rooting now cant get bootloader

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.