I have a rooted Nexus 7 (2012) with stock Android 4.4.2 (Build KOT49H). I have TWRP installed. Recently, I got a OTA update notification, which I chose to install. After downloading it, the tablet requested to reboot as usual, but it rebooted into TWRP and just stayed there. I had to select reboot in the TWRP menu. The tablet is still in 4.4.2 and now it doesn't notify me of any OTA (it just says "Your system is up to date").
Should I flash stock recovery to install the OTA?
Is the downloaded OTA still somewhere in the tablet?
How do I get the tablet to recognize the OTA again?
Thanks!
Related
I have a rooted nexus 7 device. I kept getting ota updates for my tablet but every time it restarted, twrp showed up and i did not know how to do ota update with the root. So I decided to unroot and I ended up doing a system wipe. Can someone please help me to put the system image back and unroot the device afterwards?
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
So, against my better judgment, I installed the newest OTA update. I was running rooted 4.4 stock. I unrooted via the SuperSU options and installed the OTA to 4.4.2. Then I booted in recovery mode, loaded TWRP from a command prompt, and flashed SuperSU 1.80. Flash successful. BUT, then I rebooted the phone and it gave me the "Upgrading Android" notification again, just like it did when I first installed the OTA update. Then--no root. I'm assuming that it is undoing my root as soon as I reboot the phone. I tried re-flashing SuperSU and clearing the cache/dalvik before rebooting, but same result.
Help? Ideas? Alternatively, is there any decent firewall out there that doesn't require root, since that's all I need it for?
[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
So my son's 2012 Nexus 7 (32 GB Wi-Fi) is struggling to update. I was checking to see if he got the 5.0 update and noticed he's still on 4.4.2. When I tried to update to 4.4.3 it won't reboot and install the update.
I then tried to sideload the update and it failed due to some certificate issue. Maybe because it's unlocked? I then rooted it again (lost it after the last update apparently) and also installed TWRP. I was going to attempt to sideload from within TWRP but adb doesn't see the device in sideload mode for me for some reason.
Bottom line... Can I just flash the OTA zip file like any other file within TWRP? If not, does anyone have any over ideas of what I can do to update this this without wiping it clean?
I think you will have to flash the 5.0 and images using fastboot. Can you get into ap fastboot mode?
before that though, and to answer your questions:
- unlocked bootloader does not cause issues
- I've used twrp to flash all of the KitKat ota updates directly. simply put the update zip in the internal storage of the device (I always put it in sdcard0/) and flash. the only reason that would fail with KitKat is if you have xposed installed, which was fixed by flashing xposed Disabler zip first. I don't think having root mattered.
- for the lollipop update flashing from twrp didn't work for me. I had to first return 4.4.4 to stock system and recovery (by flashing the system.img and recovery.img files from stock 4.4.4) then adb sideload 5.0 ota update. In your case tho you'd have just updated to 4.4.4 so you can just go straight to sideloading.
All the ota update links are in the second sticky in the general section. make sure you follow the correct to:from build numbers.
I'd prefer this longer route of ota updates, but if nothing works then you can probably just flash system, recovery, and boot directly from the lollipop firmware, and leave userdata untouched. I'd also Not flash the bootloader, as it's reported to have issues.
I have ota downloaded waiting to install I'm rooted and unlocked I have twrp installed how do I confirm that phone is stock and then how do I install it using twrp if stock.install failed previously