Unable to flash bootloader + undefined lock/unlock state - Nexus 7 Q&A, Help & Troubleshooting

Hi guys,
i'm from germany and i bought my Nexus 7 yesterday.
I unlocked the bootloader, flashed CWM-Recovery and "AndroidME CM10 N7 1.0.0...-Rom" and configured everything.
The tablet ran just fine. I went to bed and plugged the device for charging.
In the morning, my Nexus 7 didn't woke up.
I pressed the Powerbutton a few seconds to Reset the device. But instead of booting to JellyBean, a weird kind of Bootloader-Menu appears.
There is the Google-logo at the center, and the unlocked padlock at the bottom of the screen. The big 'Start-Arrow' pointing at the powerbutton...and that's it. No Android, no Information-Text, no Arrows beside the Volume keys.
But i can use the volume keys to change the Arrow from 'Start' to 'Restart Bootloader' 'Recovery mode' and 'Power off'.
Only the 'Power off' function work a usual. 'Start' and 'Recovery mode' does nothing (only a 'Booting failed' appeares on the top left corner) and 'Restart Bootloader' forces the device to go 'Dark' (OFF ???).
But...by booting up with volume down and power pressed, the usual Bootloader menu starts. (with arrows near volume keys, Android in the middle of the screen, and the information text on the left side).
The 'LOCK STATE' is UNLOCKED !
Because i also have fastboot-access, i decided to restore the stock image the fastboot-way.
C:\temp>fastboot erase boot
erasing 'boot'...
OKAY [ 2.532s]
finished. total time: 2.533s
C:\temp>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.034s
C:\temp>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\temp>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\temp>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\temp>fastboot flash bootloader bootloader-grouper-3.34.img
sending 'bootloader' (2072 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
FAILED (remote: (BadParameter))
finished. total time: 0.698s
C:\temp>
Click to expand...
Click to collapse
As you can see, i'm not able to flash the bootloader... (tried different PC's, IMG-Files...) !
So my idea was, to check the LOCK/UNLOCK state.
C:\temp>fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.021s]
finished. total time: 0.022s
C:\temp>fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 3.833s]
finished. total time: 3.834s
C:\temp>fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
C:\temp>
Click to expand...
Click to collapse
There seems to be a problem regarding the LOCK-state. The bootloader seems not to be completely UNLOCKED !
I have no idea, what to do next.
Ahhh...i can boot into CWM using the Nexus 7 Toolkit (mskip) but the CWM cannot mount anything.
It looks like there is no working 'SDCARD'...
Can anybody help me....
Thanks in advance...
Marcus

Definitely the same issue.
I am experiencing the same issue. The Flashall.bat script from the original 4.3 distro is failing, I then proceed manually and get these results:
I don't know how to proceed. Maybe the fastboot command has been upgraded in the passage to 4.3 and now it needs another update in order to install 4.3? ...
Well after much thinking... I was trying to force the "yakju" (Galaxy Nexus) bootloaded unto the Nexus 7... My mistake due to owning multiple nexus devices. I'll try again and I am quite sure there will be no problems...

Related

[Q] Can't escape fastboot

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.

[Q] Bricked? No Bootloader and no Sytem

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!

Nexus 7 boot.img flash fails with FileWriteFailed

Device: Nexus 7 (2012) WIFI only
After 4.3 update device started locking up and had to repeatedly long-press power to reboot. Factory defaut fixed first time, Second time (because it started happening again) could not recover from factory default. boot.img will not install and returns a (remote: FileWriteFailed) error.
I've tried multiple cables, PCs, and toolkits with no luck.
I can load bootloaders without issue.
I can format and load system, userdata, recovery (have loaded stock, TWRP, CWM recoveries) all appear to load without issue and work fine but haven't been able to fix this issue.
Once the boot.img flash is attempted, the device locks up hard and a long-press of power is needed to bring it back.
I can boot to Google screen with (Start, Power off, Recovery mode, Restart bootloader options) or directly to bootloader without issue.
First tried restoring 4.3 factory, but have since been trying 4.2.2 factory using Nexus Root Toolkit, Nexus 7 Toolkit, and a lot of SDK command line of fastboot commands. I can run ADB commands if I first get into recovery.
Is there a option I can tickle or something else anyone knows I can try? I'm beginning to think the boot sector of the flash is defective (if this makes sense).
Here's an example of a fastboot update. It hasn't mattered the method, the outcome is always identical. It fails at boot.img flash write failure.
>fastboot devices
015d490651281e0e fastboot
>fastboot erase boot
erasing 'boot'...
OKAY [ 1.186s]
finished. total time: 1.186s
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.998s]
finished. total time: 0.998s
>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.796s]
finished. total time: 0.796s
>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.649s]
finished. total time: 4.649s
>fastboot flash bootloader bootloader-grouper-4.18.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.312s]
writing 'bootloader'...
OKAY [ 9.875s]
finished. total time: 10.202s
>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
>fastboot -w update image-nakasi-jdq39.zip
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........: 015d490651281e0e
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.686s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 5.210s
>
This issue has been resolved. The Nexus 7 was returned to Asus support and the motherboard was replaced under warranty.

brick?

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

Nakasi - dead for good ?

Hello people,
I think, I've killed my nexus7 nakasi - 16GB model for ever today. Could you please help me try to resurrect it, or did I really kill him ?
Before, I was using unlocked, SuperSU rooted, KK 4.4.4 with TWRP bootloader and disabled some services (to stop stupid ota notifications coming up).
Today I wanted to try 5.1.1 (LMY47V), so I downloaded the ota, unzipped it, loaded adb, reboot into bootloader and ran flash-all.bat, as usually (I have already done it coulpe times before and never had any problems), until now.
Everything was running fine, until rebooting into bootloader ... ok.. waiting for device. The command line has stuck, so I removed table, terminated job, and tried booting bootloader by volume- & power. Nothing.
Please find my log output below.
Code:
D:\temp\adb>adb reboot bootloader
D:\temp\adb>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.022s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 0.033s]
finished. total time: 0.036s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.270s
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.039s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.319s]
finished. total time: 0.322s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.775s]
finished. total time: 8.778s
sending 'bootloader' (2100 KB)...
OKAY [ 0.268s]
writing 'bootloader'...
OKAY [ 1.249s]
finished. total time: 1.524s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
^CTerminate batch job (Y/N)? y
Is there anything I can do to revive him ? Or is he dead now ?
I have tried:
VOL+ VOL- POWER
VOL- POWER
Disconnecting battery + combination of previous before & after battery removal
Connecting power + combination of previous before & after battery removal
When i connect it to my pc now, I can hear sound of new device connected - in APX mode.
Holding POWR VOL+ VOL- for 15 sec, causes tablet to disconnect and connect again in APX, but bootloader won't start.
Plugging it on charger does nothing, battery indicator doesn't show up.
Please help !
remusator said:
Hello people,
I think, I've killed my nexus7 nakasi - 16GB model for ever today. Could you please help me try to resurrect it, or did I really kill him ?
Before, I was using unlocked, SuperSU rooted, KK 4.4.4 with TWRP bootloader and disabled some services (to stop stupid ota notifications coming up).
Today I wanted to try 5.1.1 (LMY47V), so I downloaded the ota, unzipped it, loaded adb, reboot into bootloader and ran flash-all.bat, as usually (I have already done it coulpe times before and never had any problems), until now.
Everything was running fine, until rebooting into bootloader ... ok.. waiting for device. The command line has stuck, so I removed table, terminated job, and tried booting bootloader by volume- & power. Nothing.
Please find my log output below.
Code:
D:\temp\adb>adb reboot bootloader
D:\temp\adb>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.022s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 0.033s]
finished. total time: 0.036s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.270s
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.039s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.319s]
finished. total time: 0.322s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.775s]
finished. total time: 8.778s
sending 'bootloader' (2100 KB)...
OKAY [ 0.268s]
writing 'bootloader'...
OKAY [ 1.249s]
finished. total time: 1.524s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
^CTerminate batch job (Y/N)? y
Is there anything I can do to revive him ? Or is he dead now ?
I have tried:
VOL+ VOL- POWER
VOL- POWER
Disconnecting battery + combination of previous before & after battery removal
Connecting power + combination of previous before & after battery removal
When i connect it to my pc now, I can hear sound of new device connected - in APX mode.
Holding POWR VOL+ VOL- for 15 sec, causes tablet to disconnect and connect again in APX, but bootloader won't start.
Plugging it on charger does nothing, battery indicator doesn't show up.
Please help !
Click to expand...
Click to collapse
Hi, remusator...
Sorry to be the bearer of bad news, but it sounds like your Nexus 7 is hardbricked. Both APX mode and the lack of the battery charging animation are classic hallmarks of a bootloader that may have have become corrupted, erased or accidentally overwritten.
APX mode is the state the N7 defaults to in the absence of a working bootloader, and with the expectation that somebody with the necessary software tools and knowledge will be able to nvFlash a replacement bootloader.
Unfortunately, there is no universal nvFlash tool available for the Nexus 7. The only way of accessing nvFlash on the Nexus 7 is, if you had, at some previous point, created your own unique Nexus 7 device dependant 'wheelie' blobs via the Flatline procedure.
So, without a working bootloader, the Nexus 7 cannot boot, nor can it be reflashed via fastboot commands (since it's the bootloader that 'accepts' those commands).
The only option (other than via nvFlash with previously generated Flatline 'wheelie' blobs, and which I suspect you don't have) is to have the motherboard replaced.
I have read accounts here on XDA of people sourcing Nexus 7 replacement motherboards from various online sources, and performing the replacement themselves. I don't know how easy or difficult it is, or how much it might cost (probably not much), but with a dead bootloader, it's likely the only way of resurrecting your Nexus 7.
Good luck...
Rgrds,
Ged.
Addendum: I assume you've tried all of these (that might be applicable)...
[REF] Nexus 7 Button Combinations
http://forum.xda-developers.com/showthread.php?t=2133986
----

Categories

Resources