Database Users

[Q] Nexus 7 Update Problem

Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.

GAKB said:
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
Click to expand...
Click to collapse
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?

Solution
ceefercat said:
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Click to expand...
Click to collapse
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!

GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.

It's worth a try!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
That's fair enough, I tried a factory reset first myself to no avail. If you do get your nexus replaced, please let me know if the update works!

ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
I'm considering taking it back because it is not updating as it is supposed to, as it is designed to. A message comes up on the screen that a system update is available. I go through the procedure to download and install said update. The update doesn't install, though the system now says that it is up-to-date.
Bootloader? I don't even know what that is. I don't know that the problem is caused by the bootloader and neither do you. It may be a joke to you but to me its just a pain in the neck.

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
Bootloader issues are a pain in the neck. My bootloader is locked and i cannot erase, flash, format ANYTHING on my Nexus 7... :S

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
obviously the guy doesn't have working knowledge of ADB, rooting/unlocking or any other development terms we use to describe what we are doing to our devices.
The only jokable premise here is some nerd in his mother's basement thumbing his nose at random people because the world he lives in is so narrow it couldn't possibly comprehend the existence of someone honestly asking for advice and then doing the only logical thing he can think of to do as a consumer unfamiliar with a product at a developmental standpoint.
Not everyone wants to root. And not everyone who owns a Nexus has background experience in tinkering with electronics. I've been rooting since my Dinc and I actually want to keep mine as stock as possible. I find more problems come to me when I start messing with the device instead of just leaving it alone.
---------- Post added at 12:58 AM ---------- Previous post was at 12:46 AM ----------
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I appreciate the fix. trying it out now to see if I can get stock 4.2 to update properly
Edit: Worked like a charm thanks bro for the advice

4.1.2 > 4.2.x

Ok. So here's the deal. I'm trying to update to 4.2.2 from 4.1.2, but in recovery I get assert failed, emmc this that and the other.
I'm currently on JZ054K trying to update to JOP40C. I am also fully stock. It's hurting my head using everything I learned from other devices.
*I don't want to do anything with the Nexus into the rooting process. I want to stay fully stock for once.
Please and thank you.

Curiousn00b said:
Ok. So here's the deal. I'm trying to update to 4.2.2 from 4.1.2, but in recovery I get assert failed, emmc this that and the other.
I'm currently on JZ054K trying to update to JOP40C. I am also fully stock. It's hurting my head using everything I learned from other devices.
*I don't want to do anything with the Nexus into the rooting process. I want to stay fully stock for once.
Please and thank you.
Click to expand...
Click to collapse
The "this that and the other" is the only thing which is relevant.
Post the exact error message. If you don't remember what it was, re-attempt the OTA and post a screen shot.

I'll take a photo today. I've been slacking. Away from the forums a bit.

Re: 4.1.2 > 4.2.x
That's the assert failed error. Fully stock neXus.
Sent from my HTC One V using Tapatalk 2

Curiousn00b said:
That's the assert failed error. Fully stock neXus.
Click to expand...
Click to collapse
OK, thanks for that.
Time to come clean though - when you say "fully stock", do you mean
(a) The device has never been rooted ever, or
(b) The device was rooted at one time and then (believed to be) returned to stock.
The assert error that is occurring is a complaint that the boot partition ("LNX") fails a checksum.
This would really only happen under two or three circumstances:
(1) Somehow the boot partition got modded by a root user - eg replacement of the entire boot image such as a "new kernel" or even something tiny like a change to /default.prop, OR
(2) You developed a media (eMMC flash chip) error in your boot partition after the device left the factory, OR
(3) Google/Asus somehow screwed up either the checksum calculation or your N7 slipped out of Asus's factory with a non-standard flash of the boot partition.
Now (3) seems a little bit unlikely. There was a previous user in these forums that reported exactly this same thing happening with a stock (never rooted) device; iirc though, he had a different factory ROM than what you are reporting. So, both his case and yours could be condition (2).
The things which is strange about this possibility (2) is that if a media error occurred randomly in the boot partition, it would be in most cases be fatal to the booting of the device, and neither you nor that other user reported booting troubles. The media error would have to be in a non-critical location such as in the slack space after the end of the boot image but before the end of the partition.
The reason I mention this is because of the way that apply_patch_check() assert seems to work: note that there are 5 parameters total:
filename,length1,sha1val1,length2,sha1val2
This suggests that a successful apply_patch_check() checks the SHA1 signature of the starting file - over an exact byte count, and if that succeeds it actually performs a trial patching operation so that it can compute the SHA1 signature of the output (patched) file and verify that the patch-trial-file has the correct length. This means that partition slack space is probably not included in the first checksum.
This is an extremely conservative and excellent approach to patching things in the field. Note also that the OTA does not touch/modify a single file on your tablet unless everyone of these checks goes to completion.
Also, the stock recovery performs a signature check on the entire zip file that is downloaded by the OTA before any of these other checks begin - which means, that when a stock recovery is used it is impossible to have a bad download being responsible for the errors that you observe.
If your device was never rooted then it seems to me that the odds point towards a hardware error that occurs during the patching-test operation.
If your device is still in Warranty and truly was never rooted, I would encourage you to try and get a new replacement or RMA repair (not a refurb). You are going to have to haggle with Google and show them that assert failure image.
good luck

Re: 4.1.2 > 4.2.x
It bears mentioning that, since the OTA is a patch, it's going to error out if the system is as the OP describes it. I'm unaware of any update zip that patches 4.1.2 to 4.2.2 directly. Since he's skipped a couple updates, he's going to have to do some sideloading to catch up and get to an upgradable state.
Sent from my Nexus 7 using Tapatalk HD

najaboy said:
It bears mentioning that, since the OTA is a patch, it's going to error out if the system is as the OP describes it. I'm unaware of any update zip that patches 4.1.2 to 4.2.2 directly. Since he's skipped a couple updates, he's going to have to do some sideloading to catch up and get to an upgradable state.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Good catch najaboy
I didn't catch that (JZO54K -> JOP40C) reference, but oldblue910's OTA thread does list such an OTA as having been available in the past.
Plus, iirc the boot image check occurs late in the OTA installer script, possibly even the very last assert() before patching actually starts - so it is hard to imagine that all other checks would have succeeded had a mis-matched OTA been applied.
However, it is indeed odd for "back dated" OTAs to get downloaded automatically esp when more recent upgrades are available, i.e. JZO54K->JDQ39. And nowhere did the OP mention side-loading.
Looks like the OP's got some 'splainin to do...

Ok. So yes.
A. The Device is FULLY STOCK. Never touched anything on it. Brand new on Christmas day.
I've been watching QBking's videos about upgrading it, and yes. I thought the same thing. Going from 4.1.2 to 4.2.2 directly, I noticed that seemed a bit off. I've seen more than just me with this issue. A few on XDA, and few on other websites.
I have tried downloading the 4.2.1 update. I tried sideloading it once. It failed. Atleast I believe it did. I don't know if I had the right download though.
All help is appreciated. I thank you guys as well. This 4.2.2 update is just what the OTA checker keeps throwing at me. I've tried clearing the data/cache of Google Services Framework(I believe this made me redownload the update).

Curiousn00b,
I'm 99.99% positive that you were applying a valid OTA file.
For instance if you have JZO54K on your tablet, and you were going to apply a sideloaded OTA you could choose any of 3 OTAs
JDQ39 (4.2.2) from JZO54K
JOP40D (4.2.1) from JZO54K
JOP40C (4.2) from JZO54K
My comment in the prior post was only that the automatic download always seem to download the OTA update to the most recent (in this case JDQ39) release, so your mention of JOP40C ota seemed slightly off; but if there was some reason to pick an older update, sideloading should still allow that to work correctly.
Bottom line is that a fully stock, never unlocked, never rooted tablet should be capable of accepting a factory OTA, and I would thus consider your tablet to have some unknown defect.
Just to be clear (I recall that the previous person reporting your symptoms was on JRO03S), you are currently on JZO54K, correct?

I found multiple people with it via Google. Couldn't really find a fix for it.
And yes. I'm on JZ054K.
Tomorrow I'll try going to 4.2 from 4.1.2. I'm pretty sure I've tried it already. I remember seeing the C/D parts at the end of these 2 files.

Curiousn00b said:
Tomorrow I'll try going to 4.2 from 4.1.2. I'm pretty sure I've tried it already. I remember seeing the C/D parts at the end of these 2 files.
Click to expand...
Click to collapse
If the problem occurs during the initial checksum of the (currently installed) boot image, then none of the three OTAs (starting from the same JZO54K base) will succeed. If there is something very strange - say a read/write error during the trial patching operation, I suppose it is feasible that one could succeed and another not. But they all should start out looking for the identical bootloader SHA1 checksum as they should be expecting the same (jzo54k) starting condition.
Anyway, post your results.

Re: 4.1.2 > 4.2.x
This is after trying 2 of the updates.
One to 4.2 and other to 4.2.2.
The first on is 4.2.2
Sent from my HTC One V using Tapatalk 2

Curiousn00b said:
This is after trying 2 of the updates.
One to 4.2 and other to 4.2.2.
The first on is 4.2.2
Click to expand...
Click to collapse
As I said, I didn't really expect any of them to succeed.
Where to proceed from here? You really only have 3 choices:
- Use your tablet on 4.1.2 and never upgrade
- RMA for repair/refurb replacement
- Root it, fix the problem, and relock it (so that it is 100% stock again). No guarantess that some trouble won't develop down the road.
As I said before, neither you nor I have any explantion for why a never-rooted tablet would not be able to accept a valid factory OTA. Your tablet either:
(a) slipped out of the factory with an unknown bootloader variant, OR
(b) the boot partition managed to develop bit-rot that does not affect the tablet's ability to boot, OR
(c) there is some other unidentified hardware fault that occurs during the apply_patch_check() process
I would call Asus and see what they will do for you before you make a final decision. (Their warranty has a lot of weasel-words in it; they might tell you that it's not their problem.) If you want an RMA and they push back, I think you should keep repeating that the tablet is less than 3 months old.
good luck

I also noticed that I can't boot into recovery normally. I use ADB or the OTA way to reboot into recovery.
If I get into Bootloader and plug the USB in, the Nexus 7 will freeze at whatever selection I am currently on. Bootloader, Restart, Recovery, etc and nothing will happen.
When I click Recovery, I get a black screen with Google, nothing happens, plug the USB in, and still. Nothing happens. I don't know what's wrong with it.
Thanks for the help.

bftb0 said:
As I said, I didn't really expect any of them to succeed.
Where to proceed from here? You really only have 3 choices:
- Use your tablet on 4.1.2 and never upgrade
- RMA for repair/refurb replacement
- Root it, fix the problem, and relock it (so that it is 100% stock again). No guarantess that some trouble won't develop down the road.
Click to expand...
Click to collapse
My N7 has the same error about the boot partition. It's rooted, unlocked, and has CWM installed. I'm running 4.1.2 (JZO54K). I downloaded the JZO54K to JDQ39 zip file, and got the failure
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")
when I tried to install it via CWM.
How would I fix this - I assume I need to get a copy of the 4.1.2 boot.img and flash it, but I'm not sure how to flash it. I can do it in Windows if I have to, but I'd rather use Linux if I can. I have the adb tools installed on Linux.

mvi57 said:
How would I fix this - I assume I need to get a copy of the 4.1.2 boot.img and flash it, but I'm not sure how to flash it.
Click to expand...
Click to collapse
Yes, that's right. It is easiest is to flash it with fastboot
Code:
fastboot flash boot boot.img
It can also be flashed to the block device
/dev/block/platform/sdhci-tegra.3/by-name/LNX
from a root shell (say in a terminal emulator) using the "dd" utility if you are familiar with that.
A custom kernel or even a trivial re-packing of the boot image (say for a small /default.prop file change) probably is what caused the boot image to be changed from stock.

bftb0 said:
A custom kernel or even a trivial re-packing of the boot image (say for a small /default.prop file change) probably is what caused the boot image to be changed from stock.
Click to expand...
Click to collapse
I didn't install a custom kernel, and as far as I know I didn't change default.prop either.
I reflashed the boot image, it went ok, but I still get the error trying to do the update. I guess I'll have to wipe and flash the whole 4.2.2 image to get it installed.

mvi57 said:
I didn't install a custom kernel, and as far as I know I didn't change default.prop either.
I reflashed the boot image, it went ok, but I still get the error trying to do the update. I guess I'll have to wipe and flash the whole 4.2.2 image to get it installed.
Click to expand...
Click to collapse
Never mind, I flashed the bootloader-grouper-3.41.img instead of pulling boot.img from the .zip. It's working now.

mvi57 said:
Never mind, I flashed the bootloader-grouper-3.41.img instead of pulling boot.img from the .zip. It's working now.
Click to expand...
Click to collapse
That observation is extremely counter-intuitive.
While the bootloader is responsible for booting the recovery, it is certainly not "running" after the recovery starts booting, so it's hard to understand why or how it could have any effect at all on the OTA processing.
Is it possible that the error which occurred after you re-flashed the boot image (LNX) was something different than the original error concerning the checksum on the boot partition?
You might want to consider flashing the v4.18 bootloader to the tablet if you plan on using any dev kernels.

bftb0 said:
That observation is extremely counter-intuitive.
Click to expand...
Click to collapse
Poorly worded, sorry. After I flashed the boot.img I extracted from the zip file, the update ran fine. I looked at the error message again and noticed that one of the numbers matched the size of boot.img, and then realized I flashed the wrong file. I shouldn't do this stuff when I'm tired.
Thank you for all your help!

Do not flash stock with Nexus 7 Toolkit!

Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.

Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
Well.. I've never had any problems fastboot flashing 4.2.2 myself.
------
I would suggest you don't use toolkits...at all... period!
Learn FASTBOOT...
...and be extremely cautious when it comes to FLASHING the BOOTLOADER...
A corrupted BOOTLOADER flash will 'hardbrick' the device in a heartbeat - make sure you have a secure USB connection...
Test along these lines..
Code:
fastboot flash boot <a boot.img>
or
fastboot flash recovery <a recovery.img>
If these go across, the new BOOTLOADER probably will.
The worst that's going to happen (with these two) is a 'softbrick' - a headache at worst.
A headache you can get over...
Hardbrick is death - and nobody get's over that.
Rgrds,
Ged.

I know this. Thanks.
I flash 4.2.2 with fastboot. Because nexus 7 toolkit is buggy, when i upgrade android from 4.2.1 to 4.2.2 with toolkit i got brick. Just read my 1 post
I give link to this thread creator of toolkit, maybe he fix this bug. Maybe no, anyway, start from this day i will flash firmwares ONLY with fastboot.

Good decision, i never used this kind of tool for flashing something.

Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.

mskip said:
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
Click to expand...
Click to collapse
I can't give you list of "errors" etc, just because i don't wanna again "brick" my nexus :/
What i did:
1. I enter in toolkit
2. Choose version (4.2.1 or 4.2.2, don't matter, i got "brick" on both versions)
3. Choose "download and flash stock"
4. Download stock from toolkit, or from google developers site
5. Flash downloaded firmware
After this i got "Booting failed".
Then i flash stock 4.2.2 with FastBoot - and all is ok. But when i again try to flash stock 4.2.2 with toolkit - im again got Booting failed.
That's all.
Ofcourse i have last ver. of toolkit.
Current ToolKit [V4.3.7], Latest Available [V4.3.7]
Current Mods Section [V2.5.0], Latest Available [V2.5.0]
Click to expand...
Click to collapse

I'm getting this samething to happen to me except I can't even get manual fast boot to work either. Both are giving errors about no such device found or timeouts.

I used the toolkit to flash stock and all was fine for me... Weird.
Sent from my Nexus 7 using xda app-developers app

nexus 7 toolkit, works 100% on me and my sis tablet no errors at all..

walliester said:
nexus 7 toolkit, works 100% on me and my sis tablet no errors at all..
Click to expand...
Click to collapse
Hicksy994 said:
I used the toolkit to flash stock and all was fine for me... Weird.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you use toolkit for flashing stock 4.2.2?

Never, ever had a problem with Wug's toolkit, that thing is written brilliantly and it has saved my ass more times than I can care to count.

I was totally new to android development before I tried the nexus toolkit. Now I have a rooted n7 and prime, though I gotta say, rooting the prime took from me more time. I would suggest that you run the test-like driver check before attempting the one click magic.
Sent from my Nexus 7 using xda premium

The sequel of flashes you made is confusing for me but you should flash stock no matter the version 4.1 or 4.2 cuz you can get to latest by OTA updater.
Sent from my Nexus 7 using Tapatalk 2

In last update:
+Added MD5 hash checks before flashing for ALL stock images to avoid bad flashes
+Added selection to flash Radio images in the Flash Image section (gsm models)
Good, any1 can test?

No problem for me, I used last tookit to return stock rom 4.2.2 from cyanogenmod 10.0.1 with franco r65kernel.
I desired to return factory rom, because of low charging issue and fast battery drain.
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse

Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
I HAVE flashed stock using the toolkit multiple but no problem for me.....

More, I wanna tell you guys that battery so slow in charging issue is solved after flashed stockrom 4.2.2 from google server. B4 with Cm 10.1 and franco r65, I have to charge it more than 10 hours to full, but now only 5 and half hour with Stockrom 4.2.2 . Problem is relevant to custom rom and modded kernel as I think
hassam_tariq2003 said:
I HAVE flashed stock using the toolkit multiple but no problem for me.....
Click to expand...
Click to collapse

Nexus 7 Turn On Problem
mskip said:
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
Click to expand...
Click to collapse
Dear I am facing the same problem I tried to update it with Adnroid 4.3 official. First time it showed boot img failure. I again tried to flash it through Tool Kit and it gave me some error. I tried to restart bootloader and shut it down by pressing power button. After that nothing happens. Now when I connect it to my Computer it shows me unrecognized USB. Does this mean its not dead and there is any option to get it turn on?
It will be highly obliged if you could reply me with the solution. I am in Pakistan and we don't have any service center.

saqibyk said:
Dear I am facing the same problem I tried to update it with Adnroid 4.3 official. First time it showed boot img failure. I again tried to flash it through Tool Kit and it gave me some error. I tried to restart bootloader and shut it down by pressing power button. After that nothing happens. Now when I connect it to my Computer it shows me unrecognized USB. Does this mean its not dead and there is any option to get it turn on?
It will be highly obliged if you could reply me with the solution. I am in Pakistan and we don't have any service center.
Click to expand...
Click to collapse
I'm in the same boat exactly the same thing. i hope there is a fix for this.

ChrisHRocks said:
I'm in the same boat exactly the same thing. i hope there is a fix for this.
Click to expand...
Click to collapse
You should flash the stock bootloader, when connected, find this amongst the advanced utilities, and if the drivers are not working then use the driver diagnostic tool. You will not lose your apps doing this.
One other thing is that once your bootloader is returned to stock, you can use the Google Framework cache and data clearance mthod, described in other posts, to force the 4.3 Update. This really does work, and means that your apps and data remain intact.

can someone please help?

I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!

You can use fastboot to erase your current partitions then manually flash the 4.3 stock images.

I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.

chrisbo4 said:
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
Click to expand...
Click to collapse
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.

Rirere said:
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Click to expand...
Click to collapse
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.

chrisbo4 said:
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
Click to expand...
Click to collapse
Install this through device manager.
http://d-h.st/kDu

Username invalid said:
Install this through device manager.
http://d-h.st/kDu
Click to expand...
Click to collapse
Okay, it's installed. I'm not sure what I should unzip though?

chrisbo4 said:
Okay, it's installed. I'm not sure what I should unzip though?
Click to expand...
Click to collapse
You can either flash stock images with fastboot or install TWRP then flash stock zip file.

chrisbo4 said:
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
Click to expand...
Click to collapse
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!

gunner1937 said:
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
Click to expand...
Click to collapse
Thank you for the information, and I'm not offended at all. I spent most of last night reading, and attempting to get adb running on my computer. I experienced issues getting drivers installed, and the computer recognizing the device. Also, trying to find the directories... I'll keep searching to see if I can get this figured out. Thank you again!

Thanks to everyone for helping me through this problem. After a lot of searching, research, reading, and video tutorials, I flashed stock images to the N7 via fastboot. I always thought that adb and fastboot was way too advanced for me (and it probably still is), but at least I got the basics down. Thank you all again.

Nexus 7 Wi-Fi (2012) OTA update trouble

Hey guys. I'm not sure if this is the right section for me to post this so sorry in advance if it's not.
So I have Android 5.1 version with TWRP and I keep getting the notification that the 5.1.1 update has been downloaded, but whenever I try to install it, it just goes to TWRP recovery and nothing happens. I've tried installing it from "install" and tapping on the update.zip file, but I get errors. Basically what I figured I should do is just update to 5.1.1 and use Nexus Root Toolkit to root the device again (I think I've done it like this with past updates, but I might have been using CWM). So what I want to do is to have a rooted device with the latest official Android version released for it (or a custom one if it'll make it faster) but as you probably already guessed, I'm a bit lost here and I'm not sure what to do in order to achieve that.
Btw The bootloader has been unlocked a long time ago if this helps in any way with this particular issue.
Any help would be greatly appreciated.