My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s
Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.
Just read this guide and download the latest factory image from here.
Good luck.
Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s
The Nexus was frozen at this point and had to be manually forced to restart bootloader.
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.
Then send is as it is. You can't do any more about it.
Good luck.
Related
I am trying to flash my Nexus 7 entirely back to stock 4.3. I was following the guide that is sticky'd in this thread to flash the Google image. This is these are the errors I get:
Code:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 2.532s]
finished. total time: 2.535s
C:\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.266s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.415s
Also the bootloader keeps freezing on me after I attempt this. I also am unable to restart bootloader by command or the selection, it just goes to a black screen and "fastboot devices" gives me ????????????? instead of my device ID. I can fix this by turning it off and booting back into the bootloader and it will properly display my device ID.
It is unlocked and on 4.23 that's listed there. What else can I do?
engagedtosmile - You should post this question in comminus' stickied thread. I read all 54 pages of it and he's very good at diagnosing the problem and helping to get it resolved.
engagedtosmile said:
I am trying to flash my Nexus 7 entirely back to stock 4.3. I was following the guide that is sticky'd in this thread to flash the Google image. This is these are the errors I get:
Code:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 2.532s]
finished. total time: 2.535s
C:\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.266s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.415s
Also the bootloader keeps freezing on me after I attempt this. I also am unable to restart bootloader by command or the selection, it just goes to a black screen and "fastboot devices" gives me ????????????? instead of my device ID. I can fix this by turning it off and booting back into the bootloader and it will properly display my device ID.
It is unlocked and on 4.23 that's listed there. What else can I do?
Click to expand...
Click to collapse
Hi, engagedtosmile...
Yeah.. there is a known issue with the v4.23 bootloader.
Your problem could be the bootloader v4.23 from build JWR66Y.... try flashing the bootloader v4.23 from build JWR66V.
See this thread for details (a couple of people have uploaded the bootloader v4.23 from build JWR66V, for both 'grouper' and 'tilapia' Nexus 7's on this thread - when I find the time, I'm going to upload them myself... so I don't have to keep hunting out the link).
Hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, engagedtosmile...
Yeah.. there is a known issue with the v4.23 bootloader.
Your problem could be the bootloader v4.23 from build JWR66Y.... try flashing the bootloader v4.23 from build JWR66V.
See this thread for details (a couple of people have uploaded the bootloader v4.23 from build JWR66V, for both 'grouper' and 'tilapia' Nexus 7's on this thread - when I find the time, I'm going to upload them myself... so I don't have to keep hunting out the link).
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks but I have done that as instructed in the sticky post (I ran into the error before but was able to flash it fine). I thought I would try to Lock the bootloader and unlock it again, it locked fine but now errors out when unlocking.
I am back to step 1 it seems.:crying:
engagedtosmile said:
Thanks but I have done that as instructed in the sticky post (I ran into the error before but was able to flash it fine). I thought I would try to Lock the bootloader and unlock it again, it locked fine but now errors out when unlocking.
I am back to step 1 it seems.:crying:
Click to expand...
Click to collapse
Have you tried changing to a different USB port on your PC... or a different USB cable, or even a different PC.
I know I've had difficulties, when trying to send/write to 'system', and changing to a different USB port usually resolves the problem... so it might be worth a shot.
Gotta be really careful when flashing bootloaders, as one false move can cause hardbrick, which is pretty grim.
Rgrds,
Ged.
GedBlake said:
Have you tried changing to a different USB port on your PC... or a different USB cable, or even a different PC.
I know I've had difficulties, when trying to send/write to 'system', and changing to a different USB port usually resolves the problem... so it might be worth a shot.
Gotta be really careful when flashing bootloaders, as one false move can cause hardbrick, which is pretty grim.
Rgrds,
Ged.
Click to expand...
Click to collapse
I will have to try it on my home PC later. I have tried different cables and ports on my work PC to no avail. It just won't unlock at all now.
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
- Wiped everything
- Forgot to copy the .zip files - so thats the point where everything went wrong
- Tried to upload it via adb push - failed when I wanted to install the zip
- Startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
GedBlake said:
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
Click to expand...
Click to collapse
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
I see the charging animation and holding the power button for 30 second didnt help.
wtherrell said:
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Click to expand...
Click to collapse
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Downloads/nakasi-jwr66y » sudo ./flash-all.sh
Password:
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.577s]
finished. total time: 0.577s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.026s]
finished. total time: 1.026s
erasing 'recovery'...
OKAY [ 0.852s]
finished. total time: 0.852s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.488s]
finished. total time: 0.488s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.493s]
finished. total time: 6.493s
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: XXXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
FAILED
Device version-bootloader is '4.18'.
Update requires '4.23'.
finished. total time: 0.139s
Click to expand...
Click to collapse
hd21337 said:
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Click to expand...
Click to collapse
Maybe not... the v4.23 bootloader from Jellybean 4.3 build JWR66Y is known to cause issues when fastboot flashing back to factory stock. For this reason, it is recommended you replace that version of the bootloader with the one from build JWR66V. It's still, ostensibly, the same bootloader, but seems to fastboot flash OK.
As build JWR66V is now no longer available on the Google Developers website, somebody has extracted and uploaded the old bootloader from build JWR66V here. (You might have to scroll down a little for the link).
Oh.... and ADB devices doesn't work when you're in the bootloader... it requires a fully booted Android OS to work.
The command I think you're looking for is fastboot devices
Rgrds,
Ged.
hd21337 said:
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
Click to expand...
Click to collapse
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
jkkk88 said:
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
Click to expand...
Click to collapse
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...that suggested to me, the known issue with the bootloader from build JWR66Y as detailed here (in red letters, at the very top of the first post in the thread), and discussed here... as being the likely cause of the problem.
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Good luck.
Rgrds,
Ged.
GedBlake said:
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Click to expand...
Click to collapse
My concern was that OP could not start (deleted ) recovery from bootloader menu. He should look into stickies. Nexus is still alive and should get new bootloader as you recommended from another build.
Hi guys (@GedBlake and @jkkk88),
sorry for the late answer.
I just tried to run the flash-all.sh with the other bootloader image... but its worse than before.
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.580s]
finished. total time: 0.580s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.769s]
finished. total time: 0.769s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.854s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.489s]
finished. total time: 0.489s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.494s]
finished. total time: 6.495s
sending 'bootloader' (2100 KB)...
OKAY [ 0.267s]
writing 'bootloader'...
OKAY [ 9.376s]
finished. total time: 9.643s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
Click to expand...
Click to collapse
So and at this point, he stuck for about 20 minutes - I aborted it because he didnt move on. And now the N7 is dead. No power charging icon and animation and I cant turn it on (30 seconds holding power button etc.).
So I think I just killed it
Any ideas if there is an another reset trick etc.?
Thanks!
I've been having issues with my Nexus 7. The first time it was stuck in a boot loop not making it past the Google logo. I booted into the bootloader, flashed a new factory image, and I was off.
Then a few weeks later the same thing happened. Only this time, I can't get a factory image to flash. Any ideas?
I think my flash memory is gone bad.
carlowahlstedt said:
I've been having issues with my Nexus 7. The first time it was stuck in a boot loop not making it past the Google logo. I booted into the bootloader, flashed a new factory image, and I was off.
Then a few weeks later the same thing happened. Only this time, I can't get a factory image to flash. Any ideas?
I think my flash memory is gone bad.
Click to expand...
Click to collapse
Possibly... or possibly not.
Hi, carlowahlstedt...
carlowahlstedt said:
...Only this time, I can't get a factory image to flash...
Click to expand...
Click to collapse
It might be helpful if you could be more specific... like, what errors did you encounter?... how did you go about flashing a factory image?... did you use a toolkit, like Wugs?... or just regular fastboot?
For somebody to assist you in diagnosing a given problem, in the hope of fixing it... they need all the facts available... no matter how seemingly innocuous or irrelevant.
The 'devil', as it is said, resides very much in the 'detail'.
Rgrds,
Ged.
Thanks Ged. I guess I was kinda hoping for a tool that could some how test the memory.
Here's the output from the toolkit:
********************************************************************************
* Universal Nexus Linux Toolkit v2.4.2 by tatelucas *
********************************************************************************
Flash Google Factory Image
Before starting the process your device must be in Bootloader Mode.
In the following instructions you will learn how to do it:
1. Power off the device.
2. Press and hold Volume Down, then press and hold Power.
3. Your device screen should show an image of an opened android.
You're now in the Bootloader Mode! If you don't see the image,
you must follow the instructions again.
4. Please connect the device to your PC via USB.
5. Do you want to start the process? [Y/N]: Y
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.015s
erasing 'recovery'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.019s]
finished. total time: 0.019s
sending 'bootloader' (2100 KB)...
OKAY [ 0.276s]
writing 'bootloader'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.247s
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting into bootloader...
You'll notice that it doesn't have anything past the "rebooting into bootloader". The screen is locked up on the device and nothing is happening. After sometime I manually reboot into bootloader and get:
ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
finished. total time: 174.893s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 0## (removed this)
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4990 KB)...
OKAY [ 0.682s]
writing 'boot'...
FAILED (remote: (AccessDenied))
finished. total time: 2.378s
I also seems to have lost recovery mode? If I click on Recovery Mode in the bootloader it just flashes the text and that's it.
Not sure what else would be helpful to see/know. Thanks for the help.
Google search
android factory images
Grab the latest for your device
Extract all
fastboot flash bootloader nameofbootloader.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now either click the flashall.bat or, as I would recommend, do it manually
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash data userdata.img
fastboot flash recovery recovery.img
(Feel free to use twrp or cwm if you don't want stock)
Now reboot
Side note, stay away from toolkits whenever possible
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Google search
android factory images
Grab the latest for your device
Extract all
fastboot flash bootloader nameofbootloader.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now either click the flashall.bat or, as I would recommend, do it manually
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash data userdata.img
fastboot flash recovery recovery.img
(Feel free to use twrp or cwm if you don't want stock)
Now reboot
Side note, stay away from toolkits whenever possible
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help. I downloaded the latest image for the Nexus 7 Wifi (NOT 2013) and attempted to flash the bootloader but I get this:
sending 'bootloader' (2100 KB)...
OKAY [ 0.333s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.466s
I found this thread, which I took to mean to download the bootloader from the 4.3 image. I did that but get the same result.
Also, it shows that I already have 4.23 so it seems like I wouldn't need to flash this in the first place?
Thanks again for the help.
Then skip the bootloader but do the rest of the steps
And you are just using fastboot right? No toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Then skip the bootloader but do the rest of the steps
And you are just using fastboot right? No toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, no toolkits.
Looks like the erase system command is having issues writing as well. Included the reference to the command so you could see that as well:
platform-tools carlo.wahlstedt$ ./fastboot erase system -w
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
erasing 'userdata'...
OKAY [ 0.024s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6453985280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 24620
Label:
Blocks: 1575680
Block groups: 49
Reserved block group size: 391
Created filesystem with 11/394352 inodes and 52512/1575680 blocks
sending 'userdata' (102525 KB)...
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 81.408s
Looks like data partition is corrupt, hopefully fixable but you will need adb shell. So continue on with the steps above and hopefully you can get into either recovery or os, then you can use dd or fsck or something to format, well hopefully so long as it is not too corrupt
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Looks like data partition is corrupt, hopefully fixable but you will need adb shell. So continue on with the steps above and hopefully you can get into either recovery or os, then you can use dd or fsck or something to format, well hopefully so long as it is not too corrupt
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't think it's looking good:
platform-tools carlo.wahlstedt$ ./fastboot erase boot
erasing 'boot'...
OKAY [ 0.015s]
finished. total time: 0.015s
platform-tools carlo.wahlstedt$ ./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.015s]
finished. total time: 0.015s
platform-tools carlo.wahlstedt$ ./fastboot flash system nakasi-kot49h/image-nakasi-kot49h/system.img
erasing 'system'...
OKAY [ 0.011s]
sending 'system' (625382 KB)...
OKAY [ 86.819s]
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 152.721s
platform-tools carlo.wahlstedt$ ./fastboot flash boot nakasi-kot49h/image-nakasi-kot49h/boot.img
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
^C (I forced a reboot here after waiting a long time)
platform-tools carlo.wahlstedt$ ./fastboot flash boot nakasi-kot49h/image-nakasi-kot49h/boot.img
sending 'boot' (4992 KB)...
OKAY [ 0.818s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.374s
platform-tools carlo.wahlstedt$ ./fastboot flash data nakasi-kot49h/image-nakasi-kot49h/userdata.img
sending 'data' (104289 KB)...
OKAY [ 14.212s]
writing 'data'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 14.227s
platform-tools carlo.wahlstedt$ ./fastboot flash recovery nakasi-kot49h/image-nakasi-kot49h/recovery.img
sending 'recovery' (5532 KB)...
OKAY [ 0.893s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.448s
platform-tools carlo.wahlstedt$ ./fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting... (I forced a reboot here)
ERROR: usb_write failed with status e00002ed
finished. total time: 106.130s
It's also "locking up" on most every command that I send. By that I mean, you can't move through the bootloader menu.
Any other thoughts?
Sorry to say but I feel your nand is fried... If you still have warranty you should claim it but as of now I would give it 50/50 that even JTAG would work to resurrect you tab
Sorry for the bad news, best of luck
Sent from my Nexus 7 using XDA Premium 4 mobile app
Well that sucks. Thanks for the help.
Gave my 2012 N7 to my nephew, a month later it's frozen 'Google' in the center and a green arrow / start up top. Using the vol. keys I can cycle between start/reboot bootloader/recovery mode/power off, selecting anything but power off loops.
Also, I had to reinstall the sdk but 'adb devices' shows nothing. Any hope of bringing this back to life?
joe2262 said:
Gave my 2012 N7 to my nephew, a month later it's frozen 'Google' in the center and a green arrow / start up top. Using the vol. keys I can cycle between start/reboot bootloader/recovery mode/power off, selecting anything but power off loops.
Also, I had to reinstall the sdk but 'adb devices' shows nothing. Any hope of bringing this back to life?
Click to expand...
Click to collapse
If you are in fastboot, adb commands will not work, you need to use "fastboot devices" to see if you are connected. If you are flash a recovery from fastboot and you can work fairly easily from there. Is the bootloader locked or unlocked?
EpJoker said:
If you are in fastboot, adb commands will not work, you need to use "fastboot devices" to see if you are connected. If you are flash a recovery from fastboot and you can work fairly easily from there. Is the bootloader locked or unlocked?
Click to expand...
Click to collapse
Yep, agreed...
joe2262 said:
Gave my 2012 N7 to my nephew, a month later it's frozen 'Google' in the center and a green arrow / start up top. Using the vol. keys I can cycle between start/reboot bootloader/recovery mode/power off, selecting anything but power off loops.
Also, I had to reinstall the sdk but 'adb devices' shows nothing. Any hope of bringing this back to life?
Click to expand...
Click to collapse
Hi, joe2262...
'adb devices' will not show anything if the device is booted into fastboot mode.
The command you need is 'fastboot devices'...
This will confirm you have a working FASTBOOT connection... and from which you can run fastboot commands... such as fastboot flashing a Custom Recovery (CWM or TWRP).
Or alternatively, fastboot flashing back to factory stock.
Either way... I suspect your Nexus 7 is likely recoverable.
At worst, it's just 'softbricked'.
Rgrds,
Ged.
Yes, it's unlocked but I want to go to a stock install.
C:\Users\joe\Desktop\android\android-sdk-windows\nakasi-jdq39>flash-all
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.016s]
finished. total time: 0.016s
sending 'bootloader' (2096 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.262s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.640s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
Press any key to exit...
??????????????????????
It worked fine months ago when I went back to stock. Damn kids!
Do I need to format boot, recovery and system, is that the proble,m?
Sent from my SM-T310 using xda premium
After an update to my 2012 Nexus 7 a ways back, it became unbearably slow and I gave up on it. I'm assuming it was the 5-dot-something update because after doing a bit of digging just for kicks, it seems the same thing has happened to everyone else. So, I wasn't paying close enough attention and I flashed the 4.2.2 2013 nexus 7 version (from here https://developers.google.com/android/images) onto my 2012 Nexus 7. Feel free to point and laugh now.
My tablet is now stuck with showing the Google logo, and won't go past that. Plugged into my pc, it now longer shows up under devices in adb. However, if I go into recovery mode and then into sideload mode (and I've tried all the other options, clearing cache and factory reset I think), it will show up under adb, and will let me sideload. I've tried just about every file on this page https://forum.xda-developers.com/showthread.php?t=1745781 and still no luck. I've gone into the update script and removed the assert line as many suggest. Always ends up at "Aborted Installation" with no errors.
Are there any other options at this point, or do I have a new paperweight?
Thanks!
Ghoast said:
After an update to my 2012 Nexus 7 a ways back, it became unbearably slow and I gave up on it. I'm assuming it was the 5-dot-something update because after doing a bit of digging just for kicks, it seems the same thing has happened to everyone else. So, I wasn't paying close enough attention and I flashed the 4.2.2 2013 nexus 7 version (from here https://developers.google.com/android/images) onto my 2012 Nexus 7. Feel free to point and laugh now.
My tablet is now stuck with showing the Google logo, and won't go past that. Plugged into my pc, it now longer shows up under devices in adb. However, if I go into recovery mode and then into sideload mode (and I've tried all the other options, clearing cache and factory reset I think), it will show up under adb, and will let me sideload. I've tried just about every file on this page https://forum.xda-developers.com/showthread.php?t=1745781 and still no luck. I've gone into the update script and removed the assert line as many suggest. Always ends up at "Aborted Installation" with no errors.
Are there any other options at this point, or do I have a new paperweight?
Thanks!
Click to expand...
Click to collapse
Hi, Ghoast...
I think you need to reflash it.
It's been quite a while since I flashed my Nexus 7 2012, but if I remember correctly...
Long press and hold the power button and volume-down button together; this will reboot the Nexus 7 2012 into the bootloader.
Using fastboot, flash a Nakasi/Nakasig (depending on your device) Google factory image available from the first link in your post.
Sorry I don't have the time to provide more details, but I have to go out soon.
Rgrds,
Ged.
GedBlake said:
Hi, Ghoast...
I think you need to reflash it.
It's been quite a while since I flashed my Nexus 7 2012, but if I remember correctly...
Long press and hold the power button and volume-down button together; this will reboot the Nexus 7 2012 into the bootloader.
Using fastboot, flash a Nakasi/Nakasig (depending on your device) Google factory image available from the first link in your post.
Sorry I don't have the time to provide more details, but I have to go out soon.
Rgrds,
Ged.
Click to expand...
Click to collapse
I wish I could! In flashboot mode my device doesn't show up under the device list in adb. I can enter the commands but it just says <waiting on device>. Adb only seems to acknowledge it when I go into... I think it's called Recovery Mode. From there I can sideload updates, but as far as I can tell that is all I am able to do. Thanks though!
Ghoast said:
I wish I could! In flashboot mode my device doesn't show up under the device list in adb. I can enter the commands but it just says <waiting on device>. Adb only seems to acknowledge it when I go into... I think it's called Recovery Mode. From there I can sideload updates, but as far as I can tell that is all I am able to do. Thanks though!
Click to expand...
Click to collapse
Hi, Ghoast...
You're using ADB when you should be using Fastboot!
ADB doesn't work whilst the tablet is in fastboot mode.
ADB only works in fully booted Android and Recovery.
Only fastboot.exe will flash a device whilst it's in fastboot mode.
So, with the Nexus 7 booted into fastboot mode, type...
Code:
fastboot devices
If you have a successful fastboot connection (ie., assuming no driver problems), this should return your Nexus 7's serial number.
Your should then be able to flash the device using fastboot flash commands...
e.g.
Code:
fastboot flash bootloader [I]<<name-of-bootloader.img>>[/I] file
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc,
etc.
Or alternatively by running the flash-all.bat batch script file which accompanies factory stock images, although if I remember correctly there may be some problems with this method with the Nexus 7.
Be very careful when flashing the bootloader. Flashing the bootloader is the riskiest part of flashing a Nexus 7 and can potentially hardback the device if you flash the wrong one, or if, whilst flashing it, the USB is disconnected mid-flash. This would then require a motherboard replacement .
If your Nexus 7 is already running bootloader v4.23 (visible in the bottom left hand corner of the bootloader screen), there's no need to reflash it, as this is the latest version of the bootloader.
-----------------------------------------
I haven't reflashed or bothered with my Nexus 7 for about three years now, so my recollection of the precise details on reflashing it are somewhat hazy.
You can find some useful and important info on returning a Nexus 7 back to factory stock, here...
https://forum.xda-developers.com/showthread.php?t=1907796
-----------------------------------------
There are several different approaches that can be taken when flashing a Nexus device, including a Nexus 7 2012.
My own preferred method is to fully unzip the Google stock factory image to be flashed and then to fastboot flash the device partition by partition.
Apologies for the vagueness of my response - my memory isn't what it used to be, but one thing I am absolutely certain of...
ADB.exe won't flash your device.
fastboot.exe is required for flashing.
Rgrds,
Ged.
GedBlake said:
Hi, Ghoast...
You're using ADB when you should be using Fastboot!
ADB doesn't work whilst the tablet is in fastboot mode.
ADB only works in fully booted Android and Recovery.
Only fastboot.exe will flash a device whilst it's in fastboot mode.
So, with the Nexus 7 booted into fastboot mode, type...
Code:
fastboot devices
If you have a successful fastboot connection (ie., assuming no driver problems), this should return your Nexus 7's serial number.
Your should then be able to flash the device using fastboot flash commands...
e.g.
Code:
fastboot flash bootloader [I]<<name-of-bootloader.img>>[/I] file
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc,
etc.
Or alternatively by running the flash-all.bat batch script file which accompanies factory stock images, although if I remember correctly there may be some problems with this method with the Nexus 7.
Be very careful when flashing the bootloader. Flashing the bootloader is the riskiest part of flashing a Nexus 7 and can potentially hardback the device if you flash the wrong one, or if, whilst flashing it, the USB is disconnected mid-flash. This would then require a motherboard replacement .
If your Nexus 7 is already running bootloader v4.23 (visible in the bottom left hand corner of the bootloader screen), there's no need to reflash it, as this is the latest version of the bootloader.
-----------------------------------------
I haven't reflashed or bothered with my Nexus 7 for about three years now, so my recollection of the precise details on reflashing it are somewhat hazy.
You can find some useful and important info on returning a Nexus 7 back to factory stock, here...
https://forum.xda-developers.com/showthread.php?t=1907796
-----------------------------------------
There are several different approaches that can be taken when flashing a Nexus device, including a Nexus 7 2012.
My own preferred method is to fully unzip the Google stock factory image to be flashed and then to fastboot flash the device partition by partition.
Apologies for the vagueness of my response - my memory isn't what it used to be, but one thing I am absolutely certain of...
ADB.exe won't flash your device.
fastboot.exe is required for flashing.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ged,
You were right! I was looking at the wrong thing, so thank you for that. I was able to flash the correct bootloader as the one I had on there was not the right version - I tried to update before updating the bootloader and it said it required 4.23. After updating and restarting the bootloader, I tried the flash-all bat file and got these results:
C:\nakasi-kot49h>flash-all.bat
...
FAILED (command write failed (No error))
finished. total time: 0.002s
erasing 'boot'...
FAILED (command write failed (No error))
finished. total time: 0.004s
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.006s
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.007s
erasing 'system'...
FAILED (command write failed (No error))
finished. total time: 0.006s
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.004s
target didn't report max-download-size
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No error))
finished. total time: 0.005s
Press any key to exit...
Lots of failing with no errors so... I dunno!
Thanks!
Ghoast said:
Ged,
You were right! I was looking at the wrong thing, so thank you for that. I was able to flash the correct bootloader as the one I had on there was not the right version - I tried to update before updating the bootloader and it said it required 4.23. After updating and restarting the bootloader, I tried the flash-all bat file and got these results:
C:\nakasi-kot49h>flash-all.bat
...
FAILED (command write failed (No error))
finished. total time: 0.002s
erasing 'boot'...
FAILED (command write failed (No error))
finished. total time: 0.004s
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.006s
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.007s
erasing 'system'...
FAILED (command write failed (No error))
finished. total time: 0.006s
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.004s
target didn't report max-download-size
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No error))
finished. total time: 0.005s
Press any key to exit...
Lots of failing with no errors so... I dunno!
Thanks!
Click to expand...
Click to collapse
Just to confirm, is the bootloader unlocked? If not, you can unlock it with...
Code:
fastboot oem unlock
You can't flash anything with a locked bootloader. If the bootloader is unlocked, you should see a white unlocked padlock symbol underneath the white Google logo when booting the Nexus 7. It should also say 'unlocked' in the bootloader screen in tiny letters in the bottom left hand corner.
It's also possible your fastboot executable may need updating. You can get the most up-to-date version of fastboot (and ADB) from here...
https://developer.android.com/studio/releases/platform-tools.html
Other points worth considering... Ensure you have a good USB connection between your PC and the Nexus 7. Sometimes it's also worth trying different USB cables and/or different USB ports on your PC when encountering problems when flashing a device.
Hope this helps and good luck.
Rgrds,
Ged.