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

Help Something went wrong flashing stock 5.1 image

S

stampedingTurtles

Newbie
Hello everyone!

This morning I tried to flash the stock 5.1 image on my Nexus 7 (2012) Wifi. I was able to install the android SDK, install the nexus driver from google, and then see my tablet listed with the adb devices command. I ran the fastboot oem unlock command, which worked fine, then proceeded to run the flash-all.bat from the stock image file.

That ran through several steps saying it was formatting things, each of which went fairly quickly, then it said it had an 'unknown error' and now my nexus 7 just says 'Google' with an unlock symbol, and I no longer have any devices showing when I run the adb devices command.

Have I bricked it?

Thanks for any help!
 
sounds like it's soft bricked. I'd suggest you try wugs toolkit - let the toolkit download the 5.1 image and then set it to bricked. Then force flash the 5.1 image.
it's a pretty simple procedure if that doesn't work try force flashing 5.0.2, but I'm pretty sure it will work :)
 
systemofadown said:
sounds like it's soft bricked. I'd suggest you try wugs toolkit - let the toolkit download the 5.1 image and then set it to bricked. Then force flash the 5.1 image.
it's a pretty simple procedure if that doesn't work try force flashing 5.0.2, but I'm pretty sure it will work :)
Click to expand...

I just searched for and downloaded the wugs toolkit, but have no read idea where to start with it. I picked my device and it now has a screen about dependency saying I need to download a modified boot.img and twrp recovery (does the toolkit require installing a different recovery on the device?)

If that doesn't work, how do I force flash? I would try flashing the 5.1 factory image again, but without the device showing up in adb I'm sort of unsure how to go about it.
 
Last edited:
I tried again with the 5.0.2 image and get the same error.

Am I possibly just doing something wrong?

I just noticed that on the last run, when it got to 'writing bootloader' it failed "remote: (invalid state)".
 
Go through the driver setup again. The ADB driver is notoriously a PITA to get installed right. Make sure you fully delete all the drivers on tab 1, and don't skip the reboot of your computer at the end before you go to the second tab.
 
Unforgiven said:
Go through the driver setup again. The ADB driver is notoriously a PITA to get installed right. Make sure you fully delete all the drivers on tab 1, and don't skip the reboot of your computer at the end before you go to the second tab.
Click to expand...
Not sure what drivers to delete or what tabs you are referring to.

My nexus doesn't show up in device manager, but I do have an 'android bootloader interface', is that what I should uninstall?
 
In WUGS, the top button says "Full Driver Installation Guide - Automatic + Manual" Click that button, and a new box pops up with a separate tab for each step. In the first Tab there "step one" is for removing all the conflicting junk windows installs automatically. Follow the steps to a T, reboot your computer, and then go to step two.
 
I went through 'step one' for removing other drivers, of course I can't do any of the steps about rebooting the tablet or turning USB debugging on or off because my tablet won't boot up.

I did try the force flash option in the toolkit, and it still fails at the same step (which seems to be before it gets to the force flashing part of things).
 
ok let me think a little bit, being that you have the ADB and fast downloaded you may be able to try manually flashing the factory image. that's the same procedure you tried at first but instead of running flash all you do each step one by one through the command prompt. when you get to bootloader it's probably going to tell you it failed because 4. 23 is notorious for this just skip it if it fails. I believe you'll manually Flash boot image, bootloader & system image and I'm not sure what else but as long as you have your tablet unlocked you still have a chance :)

I'll try to find a good video on youtube to point you in the right direction ;)
 
ok go onto YouTube and search this title
" how to update and root Android 5.1 manually on Nexus 4,5,6,7,9 & 10 "
Zedomax seems to be the easiest to follow ;)
 
systemofadown said:
ok go onto YouTube and search this title
" how to update and root Android 5.1 manually on Nexus 4,5,6,7,9 & 10 "
Zedomax seems to be the easiest to follow ;)
Click to expand...
Is this the video you meant?

If so, you can just copy the video URL and click the film icon in the toolbar and paste the link in there. It will embed the video and make it easier for the OP.;):):thumbsupdroid:
 
Thank you Unforgiven, thats it exactly Sir.
I don't know why but when I use Chrome on my N9 it never lets me copy the URL anymore :(. Edit to add, if I go to the YouTube page on Chrome I probably can copy the URL I'll try it next time I need one. I always go to the YouTube app maybe that's why I can't do it..
I always have to pull out my laptop, boot it up and do it that way through IE...
anyways I'll get back on topic ;)
 
If I recall correctly, some of the bootloader files for the Nexus 7 2012 edition are bad files and luckily the device detects this and reports it as being bad rather than flashing it and hard bricking the device. OP, have you tried unzipping the factory image and flashing each piece manually and intentionally not flashing the bootloader img file and see if that works?
 
Well, I've got a few minutes here to try some things, otherwise this will have to wait for tomorrow.

I tried manually flashing the bootloader, it sends the bootloader but when it starts writing, I get 'FAILED (remote: (InvalidState))

Also, I notice that the bootloader I've got is 'bootloader-grouper-4.23.img', is that the most current one and/or right one for my device?
 
as far as I know that's the most current and the corrupted one. I manually flashed my Nexus 7 & just skipped the bootloader after it failed.
 
Man I wish I were there :(
OK being that you can get into bootloader mode, when you do that and plug your device in and open wugs toolkit does it recognize your device with the serial number over on the little sidebar. If so Try force flashing 5.0.2.with wugs -
make sure you select 5.0.2 as what your device is running, select soft bricked, force flash
 
systemofadown said:
Man I wish I were there :(
OK being that you can get into bootloader mode, when you do that and plug your device in and open wugs toolkit does it recognize your device with the serial number over on the little sidebar. If so Try force flashing 5.0.2.with wugs -
make sure you select 5.0.2 as what your device is running, select soft bricked, force flash
Click to expand...

I don't know where it would show the serial number, but the wugs toolkit can do things like reboot the device, so it appears to be able to connect to it.

I wonder if the partition that the system images goes into is corrupt? Is there a way to reformat those?
 
try forced flashing 5.0.2 first
click that your status is soft bricked in the little window and then select force flash at the prompt. if you can get back to 5.0.2 up and running then you can try manually flashing 5.1

Edit
okay I'm just going to try to get you back running 5.0.2 first then you can worry about 5.1 once you're up and running in 5.0.2 ;)
In the tool kit select your model type I guess its a Nexus 7 wifi and then select Android 5.0.2 as what you're running.

next look at flashstock/unroot &select soft bricked boot looping

now click on flash stock/unroot and select force flash mode. if it gives the bootloader failed writing thing just let it keep rolling if everything else is ok then you'll be ok
See if that works - it might take a little while for all files to be flashed over so don't unplug too early it'll tell you when it's done
 
Last edited:
systemofadown said:
try forced flashing 5.0.2 first
click that your status is soft bricked in the little window and then select force flash at the prompt. if you can get back to 5.0.2 up and running then you can try manually flashing 5.1
Click to expand...

I've tried 5.1 and 5.0.2 and manually flashing 5.0.2. I'm going to have to come back to it tomorrow.
 
Well, I'm going to take another look at it today. So far, I used the wugs toolkit to attempt to flash 5.1 and 5.0.2, the status selected was soft bricked, and I tried both with and without force flash selected.

I tried to use wugs toolkit to individually flash files, and I tried manually flashing files with the fastboot commands. No matter what I've done, flashing the system image always fails with the message "FAILED (data transfer failure (unknown failure))" on 'sending system'.

I'm really starting to think maybe there's a hardware issue that is preventing it from writing to that portion of the storage? If I can't get this thing going again soon, I'm probably just going call this thing junk and tear it apart to salvage the screen for another nexus 7...

At this point, I'm not really sure what else to try before declaring the thing dead, so if anyone has any ideas, let me know!
 
You must log in or register to reply here.
Back
Top Bottom