Database Info

[Q] Problem Rooting 5.01

I did a factory image install of the latest from nVidia then let it update to 5.01. Made sure it was unlocked, put CWM on it, was able to go from bootloader into CWM, installed SuperSU, rebooted. No root. Went into recovery ... and it's the stock recovery ("No command"). Tried this multiple times in multiple ways and no matter what happens, once it boots into the system, CWM is gone.
Is this something I've done wrong or is this something to do with 5.01? I don't understand how it can be the latter given that I'm not seeing anyone else with this problem. Help!

Solved
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.

kmellis said:
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
Click to expand...
Click to collapse
can you help me out? Im getting the image of the android on its back with a red triangle and "no command" under it.
not sure if im even doing it correctly
EDIT: Never mind I got it working just had to use the cmd prompt to flash once I did "adb reboot bootloader" from there I followed the steps. thank you everyone who made this possible.

Flashed wrong boot file

Hi Well I had this big problem and I was close to solving it until i messed things up, I tried to not ask for help here but it's been a week and I can't find anything ): My g925p is just useless right now. I hope you can help me
Short version
Using Twrp I picked the efs.img to flash it and I didn't see it had two options ( Boot, recovery ) It's on boot by default so I guess the file flashed as boot and now everytime i turn the phone on it goes directly to download screen ( for odin ) ... I think if someone can make a backup of their boot.img file and upload it somewhere i could flash it and then everything would be back to normal ? At least boot into the rom .-. Thanks for your time !
By the way, When I try to transfer files via sideload twrp tells me i need a higher version for that device, And I have the latest version .-. Thank you guys
Long version
It all started when I tried to flash twrp with flashify, I guess i flashed a wrong version and my phone got stuck on a bootloop, I fixed it by installing the latest version of twrp and factory reset, But then it got into a bootloop in the initial setup, So I decided to Flash a light rom and it worked ! but it wouldn't connect to data, Before I had this problem I backed up esf.img and I thought it would restore connection, But then ... ( Continue in short version B) )
Thanks you so much for reading guys !

Download and install the firmware via odin that should fix your problem

dhonzik said:
Download and install the firmware via odin that should fix your problem
Click to expand...
Click to collapse
That was the first thing I tried but Odin would give me the nand write error, And googling People would just say " Try different cable, different usb port, your nand is burned and you need to replace it " I did the two first things but the second, Well I succeded flashing a rom through twrp so i dont thing there's something wrong with it.
Thanks for the answer tho.

I cant install TWRP on SM-P900 ;(

Hi
This is really frustrating. I own many Samsung devices and never had any issue installing twrp, so I am not a noob when it comes to firing up Odin and flashing the image however I am stuck with this device.
I used couple guides with no success. ;( I cant get rid of the Samsung recovery and replace with TWRP. Odin says success but that is just a lie.
I tried both the lollilop bootloader and the older one then TWP with various versions (3.1x , 2.8.x) No luck.
Can anyone please provide me "working files" with "simple steps" in case I am missing out on some minor details. This is SM-P900 Kitkat 4.4.2 version.
- I flash the bootloader using the BL slot in dl mode
- I reboot to downloader again and and install TWRP
- I type adb revoot recovery
Boom, I am back to frigging Samsung recovery

Hi ,
This is a follow up
The only guide that worked for me is this one. It might be helpful to others.
https://forum.xda-developers.com/ga...guide-install-official-lollipop-p900-t3154362

I had trouble getting TWRP to take at first too. It seems Samsung overwrites the recovery upon rebooting so even though TWRP flashed successfully it just gets overwritten when the system restarts. The simple solution for me was to disable the Reboot option in Odin, install TWRP, manually shut down and then enter Recovery mode. Hope that helps. I came across this suggestion either in the thread linked to above or while googling.

Im installing into properly rooted and I have twrp 2.8.7. I want 3+ TWRP.
I flash with PDA/AP and with "autoreboot" unchecked. I power off and power+home+volUP for recovery.
Tablet enters a "enttering recovery" bootloop which can be only disrupted by going into power+home+volDWN to enter Download, and than I can flash with ODIN 2.8.7.
2.8.7 is the latest I can boot into. WHAT IS WRONG?!!!!!!!!! I lost hope, with flashing 100x

Did you try updating TWRP from inside TWRP?
Sent from my Samsung SM-P900 using XDA Labs

try do a full wipe from stock recovery . after that flash twrp selecting the ap and bl in ODIN twrp3.1....tar booth of them (AP & BL)

no no no i tried everything. but than I found out this post : https://s4.postimg.org/s3pel2ekd/this_guy.png and that solved the day!!

With p900 work perfect, but install hard. With this twrp 3.1 i install lineage 14.1, all works good.

Rooting mistake! Can't reinstall stock firmware, no root, no recovery.

I desperately need help! let me start off by saying that I'm usually decent at figuring problems out myself I've lurked on XDA for awhile and have had many a phone that I was able to root or fix myself.
However this issue is impossible. I've made a mistake and tried to root my phone without upgrading to the version the root was originally intended for. I was using the CF auto root that I've found here at XDA. Now I am stuck on the "Recovery is not seandroid enforcing" error whenever my phone reboots. Everywhere I've searched says to boot into recovery but this is the message I get when I try to go into recovery?
Also how can I flash the stock firmware when my phone was not successfully rooted? CWRM or TWRP won't work without root access. So that leaves me as follows, I can't flash firmware without root access, I can't get root access or stock firmware without booting into recovery, and I can't boot into recovery without un-corrupted firmware? Do you see this giant loop of impossible I've roped myself into? I've tried using Odin to flash the firmware and I always get the "FAIL! (Auth) message right away. And as far as rooting goes I know of no other way other than with my original firmware.
Sometimes I am able to boot into my phone if I am lucky but I can never get into recovery or factory reset. This is all so frustrating as I had an old phone exactly like this one that I was able to root correctly not before finding out it wasn't unlocked and had to send it back! Is my phone screwed?
My phone is a Galaxy s5 SM-900w8 4.4.2

DJBTB said:
I desperately need help! let me start off by saying that I'm usually decent at figuring problems out myself I've lurked on XDA for awhile and have had many a phone that I was able to root or fix myself.
However this issue is impossible. I've made a mistake and tried to root my phone without upgrading to the version the root was originally intended for. I was using the CF auto root that I've found here at XDA. Now I am stuck on the "Recovery is not seandroid enforcing" error whenever my phone reboots. Everywhere I've searched says to boot into recovery but this is the message I get when I try to go into recovery?
Also how can I flash the stock firmware when my phone was not successfully rooted? CWRM or TWRP won't work without root access. So that leaves me as follows, I can't flash firmware without root access, I can't get root access or stock firmware without booting into recovery, and I can't boot into recovery without un-corrupted firmware? Do you see this giant loop of impossible I've roped myself into? I've tried using Odin to flash the firmware and I always get the "FAIL! (Auth) message right away. And as far as rooting goes I know of no other way other than with my original firmware.
Sometimes I am able to boot into my phone if I am lucky but I can never get into recovery or factory reset. This is all so frustrating as I had an old phone exactly like this one that I was able to root correctly not before finding out it wasn't unlocked and had to send it back! Is my phone screwed?
My phone is a Galaxy s5 SM-900w8 4.4.2
Click to expand...
Click to collapse
TWRP doesn't actually require root, it can do what it wants without it. It needs root to use adb while booted into TWRP but that isn't because TWRP requires root to do it, it is because adb requires root.
Root is sometimes used to flash TWRP via an app.
Have you tried flashing TWRP via Odin then seeing if you can boot to recovery?
Also, if you get lucky and the device boots into system, try going to system settings>backup and reset then find the factory reset setting, try factory reseting it that way and then see if you can flash TWRP or your stock firmware via Odin.
Are you booted into download mode when you are flashing stock firmware in Odin?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
TWRP doesn't actually require root, it can do what it wants without it. It needs root to use adb while booted into TWRP but that isn't because TWRP requires root to do it, it is because adb requires root.
Root is sometimes used to flash TWRP via an app.
Have you tried flashing TWRP via Odin then seeing if you can boot to recovery?
Also, if you get lucky and the device boots into system, try going to system settings>backup and reset then find the factory reset setting, try factory reseting it that way and then see if you can flash TWRP or your stock firmware via Odin.
Are you booted into download mode when you are flashing stock firmware in Odin?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I've tried doing a factory reset if I get lucky and it takes me into the main screen but immediately it gives me the "seandroid" error message the same as if I press volume up, menu, and power. I am able to boot onto download mode ive tried this to flash firmware but Odin gives me a Fail (Auth) message each time. I'm not even sure if TWRP has a version for my phone yet I'm not sure much about TWRP. If there's a way I can break this chain I'll try anything.

TWRP working so far
I found a custom version of TWRP and thankfully was able to flash it on my phone using odin. I was also able to get the Root working with TWRP as well. I'm going to play around with the phone awhile longer to see if everything is fine. I no longer get the "seandroid" error message while booting up the phone however it does briefly appear upon loading into the recovery but so far TWRP takes its place after a few seconds. It worried me at first but as long as TWRP kicks in each time it's a good sign. I'll leave the thread as unresolved for a while longer in case anyone has any further suggestions or in case something goes wrong but all my thanks goes out to Droidriven!

DJBTB said:
I found a custom version of TWRP and thankfully was able to flash it on my phone using odin. I was also able to get the Root working with TWRP as well. I'm going to play around with the phone awhile longer to see if everything is fine. I no longer get the "seandroid" error message while booting up the phone however it does briefly appear upon loading into the recovery but so far TWRP takes its place after a few seconds. It worried me at first but as long as TWRP kicks in each time it's a good sign. I'll leave the thread as unresolved for a while longer in case anyone has any further suggestions or in case something goes wrong but all my thanks goes out to Droidriven!
Click to expand...
Click to collapse
Good to good, glad you made progress, hopefully that's all you'll need to do.
I don't see how I was much help though. All I did was explain TWRP not needing root.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Good to good, glad you made progress, hopefully that's all you'll need to do.
I don't see how I was much help though. All I did was explain TWRP not needing root.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Understandable, however I never would of thought to try TWRP without your suggestion. It seems when you are stumped the answer is right there all it needs is someone else to chime in and point it out. Like trying to beat a hard level over and over sometimes just give the controller to someone else and they will get it their first try lol.

DJBTB said:
Understandable, however I never would of thought to try TWRP without your suggestion. It seems when you are stumped the answer is right there all it needs is someone else to chime in and point it out. Like trying to beat a hard level over and over sometimes just give the controller to someone else and they will get it their first try lol.
Click to expand...
Click to collapse
By the way, when flashing stock firmware via Odin, root is not required. The only time root is required to flash stock ROM is when flashing a stock firmware that has been converted into a custom recovery stock flashable.zip. It is not uncommon for someone in this community to convert stock firmware into a recovery flashable .zip. This is used so that the device doesn't lose root or custom recovery. When flashing stock the normal way via PC, it removes root and reverts the device back to stock recovery. Then the device has to be rooted and flash recovery again. The stock flashable .zip avoids all of that because it gets flashed in custom recovery, this way, recovery is not lost and root is not lost.
This only applies "IF" someone converts the firmware to flashable .zip. Not all devices have a stock flashable .zip available though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

HELP!! Mate 9 Stuck in ERROR MODE After Reset.

Hello all, this is my first post so I apologize if anything isn't right.
I recently flashed my Mate 9 to stock Nougat B19x through a method I found on this site and then decided I wanted root. Bootloader was already unlocked so I flashed TWRP and then tried to flash a couple different root methods that all failed... So I factory reset through TWRP and tried again but they still failed so on the initial boot everything worked except the screen was blank except for the soft keys. I rebooted and the same again so I put it in fastboot and tried to re-install Nougat through the same method that worked before. It went through the whole process seemingly fine and finished with 'Update should start automatically' but then the phone boot into error mode. I've looked through everything I can find here and done everything I can think of myself but nothing has worked. I can boot into to fasboot but nothing else, not even after flashing any recoveries or stock images extracted from UPDATE.app.
Func no is 14 and error no is 1.
It's a MHA-L09 and I really need to fix it as I can't really afford anything else right now. Any help would be really appreciated and I'm happy to add more info if I've missed anything.
Thanks guys!!!

BUMP
Sorry if it's not very concise, just really need help!

What commands are you using to flash the stock files?

CandyFoxJ said:
What commands are you using to flash the stock files?
Click to expand...
Click to collapse
Standard fastboot flash recovery/system/boot
Not sure if I'm flashing all the right files or if huawei needs different commands.

Follow this guide.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

Thanks for your help. That's the one that I used in the first place but everytime I try again, TWRP either doesn't flash even though it says success or I can't get into recovery.
Everytime I try to access recovery using the hardware keys it boots to error mode so is there another way??

I've been looking into this some more and have found it could be a motherboard issue. Is this correct? And if so how much would that kind of repair cost and would it even be possible considering I've unlocked the bootloader?
Thanks again.