[Q] Unable to re-root in 4.3 - Nexus 7 Q&A, Help & Troubleshooting

I wanted to update my Nexus 7 (2012) to 4.3. I was running stock rom, with the latest Trinity Kernel. I tried to flash the stock kernel so I could update to 4.3, but something went wrong and it bricked. I managed to use Wugfresh's ToolKit to undo root and bootloader unlock, and to install 4.3 . It went just fine.
But now I can't reroot. When I boot the Nexus, I still see the "unlocked" emblem at the bottom, which is weird. I installed the Samsung drivers, and it worked fine and tested fine, but as soon as a I tried to unlock it again, I suddenly lost all Fastboot access and I can't unlock or root.
Can anyone give me any advice?

Related

N7 forgot its rooted!

Hi,
I had rooted my N7 with the Wug's toolkit back when i received it. I did not select CWM at that time (i was crazy).
Since rooted people cannot apply the OTA 4.1.2 update, I have been trying various methods to get into recovery (a common problem with rooted devices).
Nothing seemed to work so I decided to re-run the process of root from the toolkit. during the process, whenever the toolkit rebooted to bootloader, my device would just stay on the fastboot menu. the toolkit showed as if it was pushing the binaries etc and doing its thing, and then rebooted the device back to normal (i had opted the CWM this time to right my wrongs).
After the process, when i checked for Super User, it failed to install updates. Upon checking with 'root checker', it said this device is not properly rooted.
I can boot into CWM recovery now but is doesn't allow me to install the update manually.
Another weird thing is that although i'm still on 4.1.1 JRO03D, the system update prompts have gone and on manually check for updates in settings, it says that my system is up to date!
Please help!
This is the WRONG section.....again....
I had the same problem, you should flash the old bootloader with a toolkit, search for a guide...

Need help with my Nexus 7 please.

Hi guys,
A while back I rooted my sons Nexus 7. For some reason now it is unrooted and I can't get rid of SuperSU. It has the JellyBean 4.3 update on it. Will I be unable to remove SuperSU since the phone is unrooted now?
Thanks,
Rocky
Never mind I took care of the problem. I downloaded the Nexus Root Toolkit and flashed the stock image. Once it completed I locked the tablet. Maybe in the future I will reroot it again.

lost root after 4.4.2 upgrade, cant re-root

hello guys,
I had 4.4.1 rom+kernel stock, rooted and custom recovery, after the OTA to 4.4.2 lost my root and recovery.
tried re-root with wug's but it gets stuck on "pushing root file to you device".
got superSU application but cant remove it because its system application.
Is there a way to root it?
thanks.
Same here except i had cwm touch latest. It seems i have lost my recovery too. If i try and boot into the recovery menu i get the open hood android with a red triangle.
No custom kernel only custom recovery.
Sent from my Nexus 7 (2012)
I lost my custom recovery too. But I just reflashed it (adb reboot bootloader, then flashed a downloaded custom recovery via fastboot), and then reflashed SuperSU as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
santoshgs said:
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
Click to expand...
Click to collapse
I was in the same situation after my OTA of 4.4.2
I had nexus root toolkit, tried to put in twrp with it failed.
Then updated to the latest nrt and then I could flash the latest twrp, havent tried cwm.
and eventually got the root back using nrt
7thAkash said:
I was in the same situation after my OTA of 4.4.2
I had nexus root toolkit, tried to put in twrp with it failed.
Then updated to the latest nrt and then I could flash the latest twrp, havent tried cwm.
and eventually got the root back using nrt
Click to expand...
Click to collapse
Ah, glad that it worked! ^_^
santoshgs said:
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
Click to expand...
Click to collapse
Found the solution to my problem. Used CF Auto Root instead of manually flashing SuperSU again. Cheers guys!
http://download.chainfire.eu/363/CF...merhead-hammerhead-nexus5.zip?retrieve_file=1
Same thing happened to me. just use fastboot to flash CWM, then before you reboot go into the recovery. then next time you reboot it will still be there. For some reason if I flash the recovery then reboot without entering recovery it will loose the recovery.
Once you have the recovery back, just flash the SuperSU binary through CWM.
Also, IMHO, dont use toolkits... you dont really know whats going on when you use those. Learn to use ADB & fastboot. They are really simple to use and you will be better able to help yourself when you have problems in the future.

OTA Nexus 7 2013 4.4.4

[OTA Captured] Android 4.4.4 KTU84P for the Nexus 7 2013
Nexus 7 2013 Wifi (flo) Over Air Update from KTU84L 4.4.3 to KTU84P 4.4.4
This only for Nexus 7 2013 Wifi Version
If you ran Towelroot on 4.4.3 and got root, then took this OTA, you will lose root (no surprise there). I was able to reinstall Towelroot and reroot. (SuperSU reports new binary required, then reports update failed, but after reboot I was rerooted.) Obviously, this only matters if your bootloader is locked.
Yesterday.
I lose root and custom recovery (cwm) after 4.4.4 OTA update on my Nexus 7.
Then I installed TowelRoot, applied the exploit and I gain root again... very very simple! No unlock bootloader needed or fastboot command...
Then with Rom Manager I reflashed custom recovery (cwm), flashed UPDATESuperSu.zip and uninstalled Towelroot apk....
recovery gone
This OTA (actually installed via Android system update) killed my recovery (TWRP) too.
I've reflashed TWRP 2.7.1.1 via fastboot, but I can't seem to get into recovery. Whenever I select Recovery from the bootloader, I get an opened-up android drawing with a red exclamation over him, sort of like the "No command" thing with my Nexus 4, only without "No command". Naturally, I tried holding Power+Vol-UP, but that didn't work like my Nexus 4. I can't seem make any key combination or duration of key hold work...
The happy ending is that I went back to TWRP 2.7.1.0 and I can get into recovery (and reflash SuperSU). Hard to believe there's really a problem with 2.7.1.1. Maybe I'll try the next version...
NRT works perfectly
I just used Nexus Root Toolkit with TWRP and worked perfectly fine for re-rooting.
Just I update the latest version 4.4.4. Its still not rooted from the beginning. Can anyone advice shall I change to run on ART on my tab which is not rooted. Thhhanks
Sent from my Nexus 7 using XDA Free mobile app

No OS Installed Message TWRP but still reboots to system

I just got a new Nexus 7 (2013). I did all the OTA updates until I got on the latest 5.1.1 (LMY48G). I was able to unlock bootloader using Wug's Nexus Root Toolkit. I then tried rooting using the same tool but the process would freeze once it reached the step of temporarily booting TWRP. The window timed out while waiting for device. The tablet did boot to TWRP recovery. However, when I went to reboot to system from TWRP, I got a message saying No OS installed. I was able to reboot back to system despite the message.
At this point, I used Wug's tool to Flash Stock + Unroot. I then tried using CF- Auto Root which worked fine with me. I was now rooted but when flashing to recovery, I got the dead android. I tried downloading TWRP app from Google Store to updated recovery through that method. I did get TWRP flashed but again I still have the No OS Installed message when going to reboot. Finally, I used use Wug's tool to delete TWRP and go back to stock recovery (dead android). Then I tried flashing TWRP through Wug's tool but ended up with same result of getting No OS installed.
Any ideas why I would be getting this message when I am able to reboot back to perfectly working system? Has anyone else experienced a similar problem and been able to get TWRP working correctly?

Categories

Resources