Database Users

[Q] Stuck on fastboot, unlocked bootloader, no adb mode

Dear XDA Geniuses,
I have a 16gb Nexus 7 WI-Fi. I was using Nexus 7 toolkit 2.0.0 to try and flash my nexus 7 back to the the stock google rom (option 9 in the toolkit.) It seems as if it wiped out cyanogen mod 10, which i had been using, as well as clockwork recovery. My nexus 7 now boot up with the google logo and the unlocked padlock on the bootom. using the volume rocker i can select the bootloader option and get an android figure with his chest open.
this is the only option i can select. my attempts have been:
1)connect it to computer. Windows 7 and Windows 8 will not recognize it, nor let me access it from the command line.
2. Use nexus 7 toolkit, which DOES recognize it in fastboot mode, to flash a new recovery on there. it says that a command failed, and won't let it write to it.
3) install adb and android sdk tools. my tablet won't show up under devices, and I am not sure if it is still in usb debugging mode. command line will not recognize it as an adb device and will not control tablet.
when i looked at this thread it was dealing with a locked bootloader, while mine is unlocked. it also wanted command line operations from the computer, which does not seem to work for me.
i was attempting to do something like this (laptop mag blog how to hard reset a bricked nexus 7) but without my nexus 7 showing up under devices I am not sure what my options are.
TLDR: Nexus 7 16gb WIFI only boots into boot recovery. Using nexus 7 toolkit to recognize as fastboot. otherwise will not show up on computer. no recovery, no boot image.
Thank you for reading.

I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "

JerryMc88 said:
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
Click to expand...
Click to collapse
latest progress can be found at imgur slash TAikq
now it is say data transfer failure - too many links. 146.84 seconds.

it was my cable. the cable mounted it in fastboot mode, but would not allow writing. switched out the cable, and we are up and running again. thanks!

Um.... Glad we could help?
Sent from my Nexus 7 using xda app-developers app

Sticky?
Man, I would love to see this sticky posted, or at least a list of errors and fixes stickied. I have been looking for an answer to the same issue for two days. Finding out it was just a lousy cable really really really pissed me off... I'm glad someone figured it out and actually posted their solution, most of these wind up with nothing.

OMG, I've tried to flash my N7 with a new lollipop 5.1 today and got the same issue as described here http://forum.xda-developers.com/showthread.php?t=2724273 then, after 5 or 6 hours of thinking what is going on, I finally found this very old thread and guess what? Changing this sh***ty cable I was using solved the problem.

Use USB ports on the back of your computer, not the front.

[Q] HELP! just bricked my nexus4

I was working on my another android device and use "dd if=boot.img of=/dev/block/mmcblk0p3" command to update its boot partition. However, I wasn't aware that I just plugged in my rooted nexus4 to charge it! Consequently the partition(mmcblk0p3) on nexus4 is overwritten and it could never boot to fastboot mode again. The partition is supposed to be "sbl2" for nexus4. (it means secondary boot loader, I guess).
I notice that there is another partition sbl2b(/dev/block/mmcblk0p13), which seems to be backup for sbl2. Does anyone know how I can restore the backup to sbl2??? Or I should just send it for repair. :crying:

If you can't get to fastboot, you're boned (I presume it's not booting up at all?). Out of interest, do you get QCOM_USB_DLOAD show up in device manager when you plug it in to your PC?
Don't suppose your other device is an Optimus 2X by any chance?

Rusty! said:
If you can't get to fastboot, you're boned (I presume it's not booting up at all?). Out of interest, do you get QCOM_USB_DLOAD show up in device manager when you plug it in to your PC?
Don't suppose your other device is an Optimus 2X by any chance?
Click to expand...
Click to collapse
Yes it's not booting up at all. all I can see while holding the power key is red LED light.
I saw QHSUSB_DLOAD in device manager.
Bad luck, the other device is not Optimus 2X.

It might not be fully dead then, it is possible to use the Qualcomm download mode on other phones.
Have a look at this for the One S, I guess it could apply, if so you just need a dump of mmcblk0p3.

Rusty! said:
It might not be fully dead then, it is possible to use the Qualcomm download mode on other phones.
Have a look at this for the One S, I guess it could apply, if so you just need a dump of mmcblk0p3.
Click to expand...
Click to collapse
I stuck on step 3 of the second part in that thread. I held the power key for 10 seconds until the (QDL mode) disappear. However, I did not see any new /dev/sd* nodes. And it came back to (QDL mode) after 2 or 3 seconds. Do you have any idea how I can get the device nodes to appear?
Greatly thanks for your help.

I have no idea, I'm afraid. As far as I know, you're the first person to get into QCOM download mode on the N4.

[Q] nexus 7 deep brick + nvflash for nexus 7

I up rom fail, can't go to recovery mode or start so i choose power off now it won't boot with black screen
when nexus 7 connect to pc, it show "APX mode" with ASUS Tranformer prime apx driver
i used all button but it still not working, can't use fastboot or adb
my nexus has rooted, i have brooken screen but it still run randomly. (my device sure can't give back to ASUS of Google)
Questions:
Have nvflash version for nexus 7?
I used nvflash gtablet and have an error : "Unknow device found". How to fix it ?
what about if i use usb jig ?
If you have another solution just reply me, please.
Sorry about bad english

You already did start another thread - if you do a search, you'll see many have a similar problem, for example:
http://forum.xda-developers.com/showthread.php?t=2340237&highlight=apx
Unfortunately, at this point there is no solution to recover the N7 from APX mode - sorry.

Nexus 7 stuck in APX mode, Won´t turn ON, No Backlight.

Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)

Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.

GedBlake said:
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.
Click to expand...
Click to collapse
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.

Gabu1405 said:
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.
Click to expand...
Click to collapse
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.

GedBlake said:
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.
Click to expand...
Click to collapse
Well, charged my device for a whole day, and now I tried to do the button combinations which you sent the link, nothing happened.
I thought that my battery could be unplugged or the cable was loose or something, so I opened the tablet and it was fine.
So, I just decided to do the button combinations while plugged into my PC, and I noticed that doesn´t matter which combination I try, the tablet disconnects from the PC and instantly reconnects, but still in APX mode.
I guess it is Game Over for me, gonna recharge it again, and try again tomorrow.
Thanks again.

Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Hi!
I had a Nexus 7 stuck in APX mode as well. Without the blobs saved you can't do anything. I tried a lot of thigs but nothing really helped. I ended up searching for an another N7 with a broken screen but with a working motherboard online. I was lucky and find one around $15. I swapped the boards and it was good to go.
Zsolti

Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Check out my guide.

Help needed to restore my Nexus 7 to a working state

I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?

bluescreened803 said:
I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?
Click to expand...
Click to collapse
Hi, bluescreened803...
APX mode is usually indicative of a corrupted bootloader partition. This could occur as a result of a bad bootloader flash (for example, with a loose/dodgy USB cable connection, during a bootloader flash), or as a result of overwriting/flashing the bootloader partition with something that is not a valid bootloader.
Whatever the cause, the Nexus 7 cannot boot without a bootloader, nor can it be placed in fastboot mode to receive fastboot flash commands. Similarly, it cannot boot into recovery mode, whether that be stock recovery or a custom recovery such as TWRP.
It's hard-bricked, and will display in Windows device manager as an APX device.
But... check out these button press combos...
https://forum.xda-developers.com/showthread.php?t=2133986
If these button press combos fail to revive your Nexus 7, then it's almost certain that it's hard-bricked, and will require a motherboard replacement to get it up and running again.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs

GedBlake said:
Hi, bluescreened803...
APX mode is usually indicative of a corrupted bootloader partition. This could occur as a result of a bad bootloader flash (for example, with a loose/dodgy USB cable connection, during a bootloader flash), or as a result of overwriting/flashing the bootloader partition with something that is not a valid bootloader.
Whatever the cause, the Nexus 7 cannot boot without a bootloader, nor can it be placed in fastboot mode to receive fastboot flash commands. Similarly, it cannot boot into recovery mode, whether that be stock recovery or a custom recovery such as TWRP.
It's hard-bricked, and will display in Windows device manager as an APX device.
But... check out these button press combos...
https://forum.xda-developers.com/showthread.php?t=2133986
If these button press combos fail to revive your Nexus 7, then it's almost certain that it's hard-bricked, and will require a motherboard replacement to get it up and running again.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
Thanks for your help!
I tried your button combinations but non of them worked. Is there anything I can do with the device in APX mode???? Can I not reflash a new bootloader???????
I also did find that in APX mode you can use nvflash to restore your device, but that requires device specific blob files that I cant get.

bluescreened803 said:
Thanks for your help!
I tried your button combinations but non of them worked. Is there anything I can do with the device in APX mode???? Can I not reflash a new bootloader???????
I also did find that in APX mode you can use nvflash to restore your device, but that requires device specific blob files that I cant get.
Click to expand...
Click to collapse
Hi again, bluescreened803...
Apologies with my delay in responding - been busy with family.
------
Regarding reflashing the bootloader...
You're in a catch-22 situation. You need a bootloader in order to flash a bootloader. Without a working bootloader, you cannot 'send' fastboot flash commands to the Nexus 7, and thus cannot flash a bootloader
------
Regarding nvFlash...
I suspect you're alluding to the 'flatline' procedure from 2013...
https://forum.xda-developers.com/showthread.php?t=2455927
This is a procedure which generates device specific 'wheelie blobs' - these 'blobs' are then stored away (eg., on your PC) in preparation for a rainy day, in the event that the Nexus 7's bootloader ever becomes corrupted or overwritten.
Theoretically, these 'blobs' can then be latterly used to rebuild/reconstitute the bootloader, and make the Nexus 7 bootable again, via nvFlash in APX mode.
Unfortunately however, these 'blobs' need to be created BEFORE the bootloader is damaged. And for the sake of emphasis...
Wheelie blobs are device specific.
Wheelie blobs are NOT cross-transferable.
In other words, 'blobs' generated on a specific Nexus 7 will ONLY work for that specific Nexus 7, and not for any other Nexus 7.
-------------------------------------------------
Some thoughts...
I always thought that 'flatline' was somewhat experimental, with a fairly low chance of success, but nonetheless, back in 2013, I generated my own Nexus 7 wheelie blobs - it was a nerve wracking experience, 'cos it involved (if I remember correctly) fastboot flashing a special custom modified version of Clockwork Mod Recovery, which in turn, flashed a special modified version of the bootloader, with special API 'hooks' in it, which allowed the creation of the 'blobs'. It seemed to have gone quite well, with the 'blobs' and associated files successfully created.
However, I never had the opportunity to actually test my 'blobs' out, because it would have entailed deliberately 'bricking' my Nexus 7 in order to actually test them and see if I could resurrect it from hardbrick...
...which wasn't something I was wildly enthusiastic about doing, for tolerably obvious reasons
Anyhow, my Nexus 7 is no longer in use, and last year, to free up space on my laptop, I deleted a lot of stuff, including all my Nexus 7 related files, including my wheelie 'blobs'.
-------------------------------------------------
If your Nexus 7 is bootloader hard bricked, and it certainly sounds like it probably is, then your only realistic recourse is to replace the motherboard.
Rgrds,
Ged.

bluescreened803 said:
I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?
Click to expand...
Click to collapse
There is a guide on how to unbrick your Nexus. I have post it on XDA, go check it out.