• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Nexus 7 won't update to 4.3 :(

A

Andromedoid

Newbie
Every time I reboot the device after downloading the update, the installation stops at some time with a dead android error. I've tried installing it multiple times with the same error each time. What is going on?
 
If you don't have stock recovery, use this app Android Root Toolkit, to flash it easily, then try to update again. If that doesn't work then...

OTA Verifier

This app will tell you what went wrong. The update zip that your N7 pulled down is located in /cache/

When you located it, long press it to choose it and run it.

It will give you a detailed log that will be copied to the clipboard.

Post it here so we can further assist.

I'm subscribed to this thread so I can be of further assistance personally. If I can't help you, I'll call the big guns.

jmar
 
Well I tried all the methods you recommended, and I guess due to my tablet not being rooted none of them worked:

2v1knio.png


So at this point I don't know whether I should root the tablet or do a factory reset.
 
If you are rooted, simply flash the stock 4.3 rooted ROM. Its really straightforward. Just wipe cache, dalvik cache, and flash

You don't want to take an OTA while rooted.
 
I'm in the same boat...I have a non-rooted (aka stock) Nexus 7, WI-FI version, 16 GB...and when I try to update with the OTA 4.3 I get the dead android error message. Any assistance is appreciated.
 
Any way to just stop it updating? Mine's rooted and has also failed but keeps downloading the update when I least expect it. I've tried using auto run manager to stop anything with 'update' in framework services but that doesn't have any effect. The machine's running fine so I don't see any need to change it or flash the update in another way 'cos I'd have to go through the hassle of putting all my apps and data back on afterwards
 
If I were you I'd download the 4.3 stock rooted ROM and flash it from recovery. Only wipe dalvik cache and cache. None of your apps or data will be deleted.


4.3 makes the tablet run much smoother/faster. Its a lot of under the hood improvements
 
Andromedoid said:
Well I tried all the methods you recommended, and I guess due to my tablet not being rooted none of them worked:

2v1knio.png

So at this point I don't know whether I should root the tablet or do a factory reset.
Click to expand...

Sorry I'm a little late to this thread, but you've got to navigate down to the particular OTA .zip file that's typically inside the /cache folder and long-press on that to select and analyze.

Let me know if you guys have any questions about OTA Verifier.

Thanks!
 
I was rooted on 4.2.2, and when I saw the OTA for 4.3 was waiting I thought I'd give it a shot, fully expecting a validation error...but it installed without a problem! Unfortunately, it appears I've lost root as the result of it, and several of my root apps are now non-functional. For example, SuperSU tells me I need to re-root in order for it to start working again.

So, will the procedure outlined at the link in Colchiro's post above (http://forum.xda-developers.com/showthread.php?t=2376881) enable me to have a fully rooted 4.3 even if I'm not coming from 4.2.2, or will there be problems if I flash it as indicated from my current state?
 
thecarlsoncrew said:
I was rooted on 4.2.2, and when I saw the OTA for 4.3 was waiting I thought I'd give it a shot, fully expecting a validation error...but it installed without a problem! Unfortunately, it appears I've lost root as the result of it, and several of my root apps are now non-functional. For example, SuperSU tells me I need to re-root in order for it to start working again.

So, will the procedure outlined at the link in Colchiro's post above (http://forum.xda-developers.com/showthread.php?t=2376881) enable me to have a fully rooted 4.3 even if I'm not coming from 4.2.2, or will there be problems if I flash it as indicated from my current state?
Click to expand...
Just flash the newest SuperSU in recovery and you'll be good to go. :)
 
Problem is I can't access the /cache folder at all. Says it's secured against browsing, and that I'll have to copy it to my SD card to select it. Which is obviously impossible to do.
 
Andromedoid said:
Problem is I can't access the /cache folder at all. Says it's secured against browsing, and that I'll have to copy it to my SD card to select it. Which is obviously impossible to do.
Click to expand...

Are you rooted or were you rooted in the past (i.e., you've somehow lost root)?

If the OTA is failing to install and you were rooted, then you must have installed something that changed things on the device that the OTA's updater-script is looking / checking for...

Not being rooted would explain why you can't view the /cache folder...

If you were not/ever rooted and the OTA is failing to install...well, that's a tough nut to crack...:confused:

Also, is your bootloader unlocked?
 
Andromedoid said:
I'm not rooted and never have been. I've never tinkered with my bootloader, either.
Click to expand...
I am willing to bet it is the ASUS keyboard that is tripping the OTA. It seems to be frozen for some users, even if you never froze it. I will dig around and see if there is a way to unfreeze it.

Scary, what do you think?

jmar
 
TIBU can freeze/thaw apps and also change from user <--> system. Might need to buy it to do all that, but it's worth every penny IMHO.
 
jmar said:
I am willing to bet it is the ASUS keyboard that is tripping the OTA. It seems to be frozen for some users, even if you never froze it. I will dig around and see if there is a way to unfreeze it.

Scary, what do you think?

jmar
Click to expand...

I think we figured out that the disabled keyboard was not an issue...

Not sure why an OTA would/could fail on a stock setup :confused:...
 
jmar said:
I am willing to bet it is the ASUS keyboard that is tripping the OTA. It seems to be frozen for some users, even if you never froze it. I will dig around and see if there is a way to unfreeze it.

Scary, what do you think?

jmar
Click to expand...

scary alien said:
I think we figured out that the disabled keyboard was not an issue...

Not sure why an OTA would/could fail on a stock setup :confused:...
Click to expand...

What's funny is that I bought it with Android 4.1 installed, and it updated to 4.2 with absolutely no issue. I've never done anything with this tablet other than perform a factory reset twice, so I don't know why it can't update to 4.3. :confused:
 
Andromedoid said:
What's funny is that I bought it with Android 4.1 installed, and it updated to 4.2 with absolutely no issue. I've never done anything with this tablet other than perform a factory reset twice, so I don't know why it can't update to 4.3. :confused:
Click to expand...

Well, you could try to run my OTA Verifier app against the OTA file, but since you're not rooted, you obviously can't navigate to the /cache directory where it get's downloaded.

I could make you a simple fake-ota.zip file that you could use to have OTA Verifier scan again to see if it will identify something that you might be able to fix (I'm not sure though, because anything that it might find will probably require root to fix--catch-22, etc.).

Lemme know if you want me to post that .zip here--it's pretty simple to create (you're a first gen, wifi, Nexus 7, right?).

Cheers!
 
You must log in or register to reply here.
Back
Top Bottom