Related
Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..
All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app
same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.
Hello! Can somebody help me with the question how can I root this device?
Please?
Try this man, i always use this guide for root and unlock with cwm.
https://m.youtube.com/watch?v=9C_QEYHzoEk
As far as I know there isn't a Exploit for 4.4.2, so you have to unlock the Bootloader at any rate.
If you just want to root, the easyiest way is just to boot the CF-Auto-Root boot image for your device: http://autoroot.chainfire.eu/
If you just want to flash custom roms, theres no need to root your actual ROM. Just flash the TWRP recovery Image via fastboot.
antila said:
Hello! Can somebody help me with the question how can I root this device?
Please?
Click to expand...
Click to collapse
Hi, antila...
Straightforward enough, if you know how to use fastboot...
------------------------------------------------
* Unlock the bootloader with fastboot oem unlock
-- BEWARE... THIS WILL FACTORY RESET THE NEXUS 7... and you will loose everything on it. All user installed apps and any files (music, video, pics etc.) will also be lost.
* Fastboot flash a Custom Recovery, such as CWM or TWRP, with fastboot flash recovery recovery.img
-- (where recovery.img is the name of the recovery image file to be fastboot flashed).
* Using that Custom Recovery, flash Chainfire's SuperSU root updater .zip.
* Reboot and you're rooted.
------------------------------------------------
I've written about this procedure in slightly more detail here.
The only thing that's changed since, is Chainfire's SuperSU root package has been updated to v1.86, and which you will find here...
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
If you prefer CWM to TWRP, then the latest CWM recovery can be found here...
http://www.clockworkmod.com/rommanager
(It's important you get the correct recovery for the particular type of Nexus 7 you have.)
For a fuller understanding of fastboot, checkout the 'stickies', particularly this one, which pertains directly to your question. It's a little out of date now... but the basic principles still hold.
This thread is also worth a look.
Good luck rooting your N7... (it's really not that difficult).
Rgrds,
Ged.
Root does't work
GedBlake said:
Hi, antila...
Straightforward enough, if you know how to use fastboot...
------------------------------------------------
* Unlock the bootloader with fastboot oem unlock
-- BEWARE... THIS WILL FACTORY RESET THE NEXUS 7... and you will loose everything on it. All user installed apps and any files (music, video, pics etc.) will also be lost.
* Fastboot flash a Custom Recovery, such as CWM or TWRP, with fastboot flash recovery recovery.img
-- (where recovery.img is the name of the recovery image file to be fastboot flashed).
* Using that Custom Recovery, flash Chainfire's SuperSU root updater .zip.
* Reboot and you're rooted.
------------------------------------------------
I've written about this procedure in slightly more detail here.
The only thing that's changed since, is Chainfire's SuperSU root package has been updated to v1.86, and which you will find here...
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
If you prefer CWM to TWRP, then the latest CWM recovery can be found here...
http://www.clockworkmod.com/rommanager
(It's important you get the correct recovery for the particular type of Nexus 7 you have.)
For a fuller understanding of fastboot, checkout the 'stickies', particularly this one, which pertains directly to your question. It's a little out of date now... but the basic principles still hold.
This thread is also worth a look.
Good luck rooting your N7... (it's really not that difficult).
Rgrds,
Ged.
Click to expand...
Click to collapse
Hello! Thank you for your help. I did everything as you wrote. Unlocked bootloader, installed TWRP but for some reason root still don't work. Can you give me a link on SuperSu where I can flash it trough TWRP? Please?
Thank you very much for your help.
Once you've got TWRP installed, just download the latest SuperSU (http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip), and flash it through TWRP.
antila said:
Hello! Thank you for your help. I did everything as you wrote. Unlocked bootloader, installed TWRP but for some reason root still don't work. Can you give me a link on SuperSu where I can flash it trough TWRP? Please?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi, antila...
If you've unlocked the bootloader, and flashed TWRP... then you've pretty much done the 'hard' part..
As @jfmcbrayer says, download SuperSU v1.86 directly to your Nexus 7, and flash it in TWRP.
However, sometimes the SuperSU app icon doesn't always appear in the app drawer after the TWRP flash... although it's very likely you are actually (probably) rooted.
To fix this, see my post here.
If this **still** doesn't work... try flashing an older version of the SuperSU root .zip, available here...
http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
This will flash SuperSU v1.75... and then go to Google Playstore to update it to SuperSU v1.86. You will probably be prompted to do this anway, as soon as it is detected you're running a slightly out of date version...
Good luck.
Rgrds,
Ged.
Why didn't you just boot the CF-Autoboot bootimage as I suggested? It's the easyest way and you could have kept your stock recovery (less trouble with OTA Updates)
Just fastboot boot boot.img and a few seconds later your device is rooted...
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
sfobrien said:
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
Click to expand...
Click to collapse
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Lenster45 said:
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Click to expand...
Click to collapse
Since you took the OTA your bootloader may be locked. After you get it unlocked I gave you where to get the recovery you need, the one you have is not KitKat friendly.
Lenster45 said:
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
Click to expand...
Click to collapse
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
charesa39;53763629
EDIT: Oh said:
Strange, had a friend who took the OTA awhile back and it locked the bootloader. It was a JB version maybe they changed it with KitKat ? ( he could have locked it prior to my getting it going who knows) Thanks for the info, have never used an OTA since I got my N10 when it first came out.
Click to expand...
Click to collapse
charesa39 said:
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
Click to expand...
Click to collapse
That did it. Thanks
Hi,
Could you add a [SOLVED] tag to the title, as it is now solved ?
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.
Hello guys, I tried to flash Dirty Unicorns ROM
I have a brand new nexus 6p
At first I went through this tutorial:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
First stuck was when I tried fastboot devices in cmd, those USB drivers from sdk manager didn't seem to work, so I downloaded some other driver, which seemed to work
Now I am stuck here:
How To Install A Custom Recovery On Your Device
fastboot flash recovery <filename>.img
So in my CMD I did this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16932 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.827s
and after fastboot reboot, the device is still the same, still the same bootloader, when I hit "recovery mode", there is just the green android robot lying on his back with red ! and after a while the device just starts like normal
also when I start I see "your device software cant be checked for corruption. Please lock the bootloader......" etc and Google logo with unlocked lock in the bottom, but I guess it's normal
any advice please?
solved, /thread
bejek said:
solved, /thread
Click to expand...
Click to collapse
Please post how you solved your issue so it's here for someone searching for an answer in future.
well I found some other guide how to unlock, flash twrp, root etc...
in this guide there is completely missing one step, where you must download some modified boot image and flash it before flashing twrp
so after I performed this:
fastboot flash boot boot.img
I was able to flash twrp recovery...
bejek said:
well I found some other guide how to unlock, flash twrp, root etc...
in this guide there is completely missing one step, where you must download some modified boot image and flash it before flashing twrp
so after I performed this:
fastboot flash boot boot.img
I was able to flash twrp recovery...
Click to expand...
Click to collapse
You don't need a modified boot.img for TWRP unless:
A) You're running extremely old firmware
B) You've flashed an extremely old version of TWRP
C) You're running Android N
What version of TWRP did you flash? Were you previously using Android N?
Heisenberg said:
You don't need a modified boot.img for TWRP unless:
A) You're running extremely old firmware
B) You've flashed an extremely old version of TWRP
C) You're running Android N
What version of TWRP did you flash? Were you previously using Android N?
Click to expand...
Click to collapse
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
bejek said:
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
Click to expand...
Click to collapse
You did enable OEM Unlock under developer options right? That's very odd you found a guide that said to flash a modified boot.img. Can you post a link to the guide?
Jammol said:
You did enable OEM Unlock under developer options right? That's very odd you found a guide that said to flash a modified boot.img. Can you post a link to the guide?
Click to expand...
Click to collapse
Ofc I did.
I am not sure where did I see it for the first time, but this step was definitely in more guides than just this one.
for example here:
https://devs-lab.com/root-install-twrp-in-nexus-6p.html
and this is the step I am talking about:
Prerequisites:
Unlocked Nexus 6P bootloader.
ADB USB Drivers
Minimal ADB Package
TWRP Recovery: Nexus 6P.
SuperSU (For Root): Download.
Modified Boot.img: Download.
Installing TWRP Recovery in Nexus 6P:
1. Launch command.bat file & type:
fastboot flash boot boot.img
bejek said:
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
Click to expand...
Click to collapse
A modified boot.img hasn't been required for quite some time, and still isn't required. I can see from the link you gave that the modified boot.img is for MDB08K, which is a very old build. This means that guide, and any guide that instructs you to flash a modified boot.img, is outdated unless you're on quite an old build. What build are you actually on?
Heisenberg said:
A modified boot.img hasn't been required for quite some time, and still isn't required. I can see from the link you gave that the modified boot.img is for MDB08K, which is a very old build. This means that guide, and any guide that instructs you to flash a modified boot.img, is outdated unless you're on quite an old build. What build are you actually on?
Click to expand...
Click to collapse
Well I know it's outdated, but without it I wasn't able to flash TWRP - and trust me, I tried every guide here at XDA and went through a big bunch of threads, I was really desperate.
I have no idea what build was originally in my 6p, some 6.0.0.
Now I am on newest stock, MTC20F
bejek said:
Well I know it's outdated, but without it I wasn't able to flash TWRP - and trust me, I tried every guide here at XDA and went through a big bunch of threads, I was really desperate.
I have no idea what build was originally in my 6p, some 6.0.0.
Now I am on newest stock, MTC20F
Click to expand...
Click to collapse
You really just needed to update to the latest build before unlocking/rooting (standard procedure), then any current guide would have been fine. Either way you got it done though, so happy days.
The fact that you have no idea what build you were on previously is a little worrisome though, it's one of those basic things you should know before you start messing with your phone. But you're new to this so it's a learning curve I guess.
Instead try out,
fastboot boot twrp_src_name.img
(Where twrp_src_name is your TWRP file name)
That should directly boot you to the TWRP. Else try custom TWRP builds like the one with MultiROM.
Heisenberg said:
You really just needed to update to the latest build before unlocking/rooting (standard procedure), then any current guide would have been fine. Either way you got it done though, so happy days.
The fact that you have no idea what build you were on previously is a little worrisome though, it's one of those basic things you should know before you start messing with your phone. But you're new to this so it's a learning curve I guess.
Click to expand...
Click to collapse
Yeah, you are obviously right. I didn't even let it update to the latest stock build and went straight to flashing new rom, so I guess there was the problem with TWRP.
bejek said:
Yeah, you are obviously right. I didn't even let it update to the latest stock build and went straight to flashing new rom, so I guess there was the problem with TWRP.
Click to expand...
Click to collapse
If you don't boot into recovery right after flashing it, the standard recovery will overwrite it. If you want to prevent this, after flashing TWRP, boot directly into TWRP. Flash latest SU to root it (This will prevent the system from overwriting twrp on reboot.)