[Q] Problem with TWRP in rooted and unlocked nexus 10 - Nexus 10 Q&A, Help & Troubleshooting

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.

Related

Lost root after 4.1.2

I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Trickee360 said:
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Click to expand...
Click to collapse
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
veeman said:
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
Click to expand...
Click to collapse
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Trickee360 said:
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
got it. thanks much
Will only boot to stock recovery
veeman said:
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
You can just root again and you will have root access.
I lost root too, so I just opened wugtoolkit and hit root. no unlock needed so no loss of programs either.
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
Any news about this. I stay in the same problem.
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
jayyo said:
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
Click to expand...
Click to collapse
So, the bootloader 3.41 is the problem?
Southmad said:
So, the bootloader 3.41 is the problem?
Click to expand...
Click to collapse
For some people, yes. No idea why.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Would that image work ok for Galaxy s3? Or there is no difference at all, just matter the 4.1.2 android version?
Cuz i updated my device throught Kies (cuzz from the device itself it didnt allow, stating that the image has been modifyied :angel: ) and after that even with the persistent mode on Super SU the root is gone

[Q] can't get to recovery mode after unlocking

Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
The robot lying on it's back is the stock recovery. You need to flash CWM/TWRP before you can do a Nandroid
itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
Do yourself a favour and learn how to use ADB instead of toolkits that do more harm than good if used by inexperienced users and you`ll learn to do it the right way.
Look here http://forum.xda-developers.com/showthread.php?t=1474956 for how to.
Youtube tutorial link http://www.youtube.com/watch?v=ZY4KSrgi-rE.
itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
If you have Rom Manager Installed and are rooted you should be able to install CWM thru it.
don't have flash recovery on rom manager
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
itayze said:
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
Click to expand...
Click to collapse
according to ROM Manager you already have CWM installed and its up to date. Have you tried booting into recovery using ROM Manager?
When I press reboot to recovery directly from rom manager it works...
I'm just affraid that in case that I brick or mess up something I won't be able to get to stock recovery mode.
volume down + power button = bootloader (android on his back) also called fastboot mode
use volume buttons to scroll to recovery then press power button to select it
you should then be in CWM recovery if its installed correctly.
If you are using a custom recovery your stock recovery is gone. You would have to use fastboot to flash the stock recovery image back onto the phone. Its rather simple to do as is flashing the stock image file back onto the phone.
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Edit: I posted before you edited your comment.
even though I don't know adb, should I learn and follow this guide?
http://www.androidauthority.com/nexus-4-clockworkmod-recovery-134114
itayze said:
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Click to expand...
Click to collapse
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
kzoodroid said:
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
El Daddy said:
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I call it a bug because its an annoying feature. There are a number of threads no how to remove it but using a toolkit to do it is just as easy.
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
itayze said:
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
Click to expand...
Click to collapse
Glad you got it working. I would still learn adb and fastboot. Though I too use the tool kit every now and then out of convenience.

[Q] [HELP] Missing recovery 4.3

I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
EDIT: when I get the no command "fallen android" when i select recovery from the bootloader on pressing power+vol up does give me acces to the stock recovery. But even on using wug's 1.6.6 root kit I'm unable to root the device and install a custom recovery
Vikas Rao said:
I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
Click to expand...
Click to collapse
Have you tried redownloading twrp seems like a bad download?
yamani.m said:
Have you tried redownloading twrp seems like a bad download?
Click to expand...
Click to collapse
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Vikas Rao said:
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Click to expand...
Click to collapse
I would try to flash the full stock google image with fastboot and see what happens ?
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
I also did it this morning, works fine
EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
Nope did the same thing! gives me the cannot load error, I just copy pasted the filename so can't go wrong there. And a stock rom flash is an option but the thing is i don't have a custom recovery nor root access for titanium backup don't wanna spend time again personalizing. I'm sure there is a simpler way.

[Q] best way to upgrade TWRP ?

currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Use goomanager. It's by far the easiest since it's mostly automated.
mjb152 said:
currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Click to expand...
Click to collapse
I just downloaded the latest version of TWRP, booted into the bootloader and loaded the image by
Code:
fastboot flash recovery {insert name of image file here}
. Easy peasy,,,
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
mjb152 said:
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
Click to expand...
Click to collapse
Just use ADB to Fastboot flash recovery. Either Fastboot flash your root file or copy it to your device. If you copy it to your device, then boot to recovery and flash your Superuser or SuperSU .zip. You don't want to restore your backup though if your on the latest OTA now and your backup is the previous OTA.
SwiftKey'ed from my White Note 2 via XDA Premium HD
Wug works well.. Simple too.
Sent from my Nexus 7 using xda app-developers app
theres TWRP flashable zips in the TWRP thread, this is the easiest if you alrady got TWRP
you can use wug to install it for the first time then use goomanager to update it later or TWRP manager to dl manually.

How to root 4.4.2 nakasig

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...

Categories

Resources