• 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 :(

Adb seems a lot like cmd on windows. I like to fix things so I've used similar tools, experimented with linux boot cd's (saved all my daughters homework that way once from a computer with an unbootable hard drive). I think I can deal with that, I have an older Sony running windows 7 and a Microsoft Surface Pro running Windows 8, not really an apple fan. I also have an old desktop I could probably boot into a version of linux on a thumbdrive or cd - but I'm not so experienced there - yet. Screenshot attached! Since I'm already running 4.3 build number JWR66V I assume this is the incremental update to JWR66Y
 

Attachments

  • resized Screenshot_2013.09.14.19.19.29.png
    resized Screenshot_2013.09.14.19.19.29.png
    154.9 KB · Views: 88
CheyenneDonna said:
Adb seems a lot like cmd on windows. I like to fix things so I've used similar tools, experimented with linux boot cd's (saved all my daughters homework that way once from a computer with an unbootable hard drive). I think I can deal with that, I have an older Sony running windows 7 and a Microsoft Surface Pro running Windows 8, not really an apple fan. I also have an old desktop I could probably boot into a version of linux on a thumbdrive or cd - but I'm not so experienced there - yet. Screenshot attached! Since I'm already running 4.3 build number JWR66V I assume this is the incremental update to JWR66Y
Click to expand...

Excellent! Thanks and sorry for the delay in replying.

Lemme find a download for that OTA and then tweak-up the .zip file for you and then prepare a list of commands that you should be able to use (should be pretty simple unless you encounter USB driver issues (the bane of using Windows with Android unfortunately)).

I'll post something back when I can.

:)

edit: by the way, if the "adb sideload" requires a properly signed file from Google, then I'm guessing this might fail since I'll be modifying the OTA .zip file and it won't (can't) have the proper signature (I'm actually guessing that this will be true since you've still got a locked bootloader :().
 
Hmm, I'm found a download that looks right:

http://android.clients.google.com/packages/ota/google_nakasi/8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip

courtesy of this page

Download: Android 4.3 “JWR66Y” OTA Updates Roll Out (Nexus 4, 7, 10, and Galaxy Nexus) – Droid Life

but the updater-script file inside it does not match what you're showing from the output of my OTA Verifier app :confused: It's size matches the 1.7Mb from the image above, but the line numbers reported by my app do not match the assert expressions and I also cannot find any /system/app/PlusOne.apk entries in there at all...

What are you pointing my OTA Verifier app to on your N7? Is it a file that you've downloaded that you're assuming is the proper OTA's .zip file?

If you're not rooted, then you wouldn't be able to navigate to the /cache folder where the actual OTA's .zip file would be located...:confused:

Lemme know--thanks!
 
CheyenneDonna said:
Back at the beginning of this thread you provided a file for anther poster to use; since he/she was not rooted. I used that file. I reset the device and gave it to my husband, who is fairly happy with it as is. Since mine was out of warranty and ASUS wanted $87 to fix it I figured I'd just replace it. I have the new Nexus(which is nice) and more or less gave up on the old.
Click to expand...

Ah, I can't remember which file that was (I'll have to go back and look :) or if you have its name handy, let me know), but glad you got yourself sorted :thumbup:.

Since you reset it, you could have also unlocked the bootloader (wipes the device, too) and then had the option to flash any of the factory images available for it. Its an interesting and enlightening process (not nearly as daunting after you've done it once, though--there's no real mystery or magic to it other than knowing when it's appropriate and helpful).

Cheers and hope to see you around here more, CheyenneDonna!

:)
 
Drewtildeath said:
I have 2013 Nexus 7, never rooted, exact same problems as above. 1/3 of the way through 4.3 update, and ERROR.
Click to expand...

Hey Drew, welcome to our AndroidForums!

Sounds like another mysterious case of the OTA getting part way through its verification and then finding some kind of mismatch.

Having an unrooted device where this is happening is pretty inexplicable (to me, anyways).

If there are files that can be updated through normal processes and then later these same files are checked by the OTA's verification process and their new contents checksums are not accounted for, well that's just crazy :eek:.

If you've run my app above, go-ahead and post the contents and I'll have a look, but I'm still a bit mystified.
 
scary alien said:
Hey Drew, welcome to our AndroidForums!

Sounds like another mysterious case of the OTA getting part way through its verification and then finding some kind of mismatch.

Having an unrooted device where this is happening is pretty inexplicable (to me, anyways).

If there are files that can be updated through normal processes and then later these same files are checked by the OTA's verification process and their new contents checksums are not accounted for, well that's just crazy :eek:.

If you've run my app above, go-ahead and post the contents and I'll have a look, but I'm still a bit mystified.
Click to expand...

Forgive the ignorance, but isn't the test OTA file posted previously for 2012 nexus. Or should that work for 2013 as well?
 
Drewtildeath said:
Forgive the ignorance, but isn't the test OTA file posted previously for 2012 nexus. Or should that work for 2013 as well?
Click to expand...

They'll be different files. They have different device/product names:

2012: grouper / nakasi (wifi) and tilapia / nakasig (mobile)

2013: razor (wifi) and razorg (mobile) [not sure what the board names are]​

Are you trying to manually install an OTA?
 
So, colchiro, I just follow the guide in the link to flash, but only wipe /cache & dalvik?

I am rooted running 4.2.2 build JDQ39 getting the update error.
 
If you're upgrading from stock to the next version (same rom), wiping both caches should be all you need. If it starts acting goofy, you can always factory reset after.
 
colchiro said:
If you're upgrading from stock to the next version (same rom), wiping both caches should be all you need. If it starts acting goofy, you can always factory reset after.
Click to expand...

Alright, so is rooted still considered stock? I've not put any custom ROMs on there. Would it keep my root? I do have VooDoo's OTA rootkeeper
 
John Bean said:
Rootkeeper won't work in the case of updating to 4.3. You can easily re-root afterwards so it's not a big deal.
Click to expand...

Found this interesting tidbit last week but haven't had time to test it yet:

https://plus.google.com/100930259139694354037/posts/JTBDYZf4r8R

https://github.com/poliva/random-scripts/blob/master/android/keeproot.sh

nightfox7 said:
Alright, so is rooted still considered stock? I've not put any custom ROMs on there. Would it keep my root? I do have VooDoo's OTA rootkeeper
Click to expand...

Yes, you can certainly be rooted but stock as long as you didn't change / remove any of the stock O/S components. But, as John Bean says, root for 4.3 JB cannot be preserved with OTA RootKeeper, but the above script might do the trick.
 
colchiro said:
Flash this. Worked great for me and kept all my apps. [4.3][grouper & tilapia] STOCK ROOTED 4.3 (JWR66V) [Flashable Zip] - xda-developers
Click to expand...

nightfox7 said:
Alright, so is rooted still considered stock? I've not put any custom ROMs on there. Would it keep my root? I do have VooDoo's OTA rootkeeper
Click to expand...

The link I have above is to a rooted version of stock, so you should be good.

Make a backup in recovery (always good insurance). :D
Clear both caches.
Flash the update.
 
Ok, So I know this post is a bit old, so I don't know if the original people will be able to help me at all, but here goes:

So I got a 2012 Nexus 7 a little while ago, it is unmodified in any way, and when it came it had 4.2.1 on it. It immediately had the update for 4.3 ready to install on it. As soon as I told the device to restart and install the update, it would get a little bit into the installation and would crash (little android with the red triangle with the ! in it).

I would have to force the device to turn off and back on, and it would come back with 4.2.1 on it, and when I try to update it again, it would say that it is up to date. A couple days later, it would pop up again in the notifications that the update was ready to install, and the same thing would happen.

I looked through this forum and tried out the OTA verifier that scary alien posted with the test OTA he put in his post. When it finished, the results look a LOT different from what other people posted here. In the fail count in that statistics part, it had 447 fails. The result log is pretty long, and I am very unsure as to what the crap I am doing, so any help is insanely appreciated.

I tried to paste the result into here, but it is too long. I put it onto pastebin so you guys can see it. If there is a better way to get the result log to you guys, let me know and i'll put it up there.

the pastebin is i2Wyjbcb
(Turns out I can't post links either because of the new-ness of the account.)

Again, I have no idea what I am doing, so any help getting this thing to update will be great, Thanks!!
 
Welcome to our AndroidForums, Benez1ze :).

There's an issue with OTA Verifier with the new updater-script files that Google's been publishing--they included/formatted things a bit differently that what my app can apparently handle. I've been working on a new version to handle this, but it's still in the works.

Probably the best thing to do would be to examine the /cache/recovery/*log* files (last_install.log and install.log I think are the names) that get produced when you've attempted an OTA installation (actually, after every reboot, but the important versions of the files are the ones that are still present after the failed OTA).

The files that have failed the OTA will be listed in there.

If you could grab those and post them up, we might be able to help you out (i.e., use a rooted file explorer to copy them to your external storage and then transfer them off your device (attach them here, pastebin, etc.).

Let us know if you have more questions :).
 
Hey, thanks for the responses, the update notification for "System update downloaded, touch to install" just came up again, so I am holding off on that until I am able to access those install logs.

I am a little apprehensive about rooting the device (fear of making a very expensive paperweight). Is there a good site to use as a guide for rooting it?
 
You must log in or register to reply here.
Back
Top Bottom