OTA Nexus 7 2013 4.4.4 - Nexus 7 (2013) General

[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

Related

[Q] Unable to re-root in 4.3

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?

[Q] Is my nexus 7 rooted or not, i got CWM and the bootloader is unlocked.

I have a 2012 nexus 7. I had root access before but then i wanted to update my nexus 7 to JB 4.3. So to do that I updated via CWN intallin zip form sd card. Now I want to update it again to Kit Kat 4.4.2. My nexus gives me the message to update it to 4.4.2 OTA but when i do that when it is intalling in recovery, it says an error occured. I still have CWM on my nexus and the bootloader is unlocked, but rootcheckes says I don't have root access. If i wan to update it how can i do that? Via fastboot or installing the zip from sd card via CWM, Im not very clear whether it is rooted or not.
Thank you for your time.

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?

nexus 7 fails to boot

I wanted to downgrade from 5.1.1 to 4.4.4, as the lollipop update wasn't stable for me. I used the Wugfresh Nexus Rootkit. However, when I ran the whole process, the device failed to boot. The bootloader works, but recovery does not. Any help will be welcome

KitKat to Marshmallow update diary, kept apps and settings, rooted

I managed to upgrade my Nexus 7 2013 LTE from KitKat to Marshmallow using factory images yesterday and took some notes. All apps and settings kept (or at least I haven't noticed any issues other than no Xposed) and rooted. I figured someone might find this useful.
So, short version: upgrading directly from 4.4.4 to 6.0 with factory images didn't work without wiping data and where's the fun in that? So I took a longer route and went 4.4.4->5.02->5.1.1->6.0.0. It's possible I could've gone from 5.0.2 to 6.0 or 4.4.4 to 5.1.1 directly but I'm not going to try and see if that's the case. Enjoying Marshmallow now.
Basically, I did the same thing for all three update steps:
Unpacked factory image, rebooted to bootloader, flashed bootloader, radio, system.img, boot.img, cache.img. I rebooted to bootloader after flashing bootloader and again after flashing radio, same thing the flashall.bat does. Don't know if it matters.
Booted to TWRP recovery, flashed supersu zip and renamed /system/recovery-from-boot.p to keep TWRP.
Booted system and grew some gray hairs while the boot animation went on and on until it finally got to the long "optimizing apps" phase.
For 6.0 I flashed a modified kernel and supersu beta 2.52.
So, enjoying Marshmallow now. No issues so far. Root cloak detectors seem to be becoming a plague and I've only used an Xposed module for that.

Categories

Resources