Database Users

NvFlash USB write failing

Hi
I have a badly bricked A500 I am trying to get up and running again. I have an 11 digit CPUID but not a 16 digit one. I did have it in a text file on my SD card however it seems to have been scrambled
Using the Power/Volume + combo, It will not load any update.zip proceeds and then hangs at "Booting recovery kernel image" the White on Black Acer logo is displayed.
Using Power/Volume - combo has no effect - Just freezes with white on black Acer logo
I can go into ATX mode via the Power/Reset combo and the Acer USB drivers are installed on my Windows 7 machine and when connect windows says an ATX device is connected.
But here's where my troubles start...
I have tried APX flash but it fails without giving a specific reason
I have tried using A500 manager but it fails to change modes or retrieve anything
I have tried HC_RollbackRom_3.2.1_Gen2_tdV4 but it fails
I have tried Nvflash but I recieve the following error msg on any command - "rcm Version OX4", "Command send failed (USB write failed)"
It would seem that even though connected by USB in ATX mode, my computer is unable to talk to the Pad - does anybody have any ideas what steps I can take to get out of this mess.
Any and all help appreciated

subzone said:
Hi
I have a badly bricked A500 I am trying to get up and running again. I have an 11 digit CPUID but not a 16 digit one. I did have it in a text file on my SD card however it seems to have been scrambled
Using the Power/Volume + combo, It will not load any update.zip proceeds and then hangs at "Booting recovery kernel image" the White on Black Acer logo is displayed.
Using Power/Volume - combo has no effect - Just freezes with white on black Acer logo
I can go into ATX mode via the Power/Reset combo and the Acer USB drivers are installed on my Windows 7 machine and when connect windows says an ATX device is connected.
But here's where my troubles start...
I have tried APX flash but it fails without giving a specific reason
I have tried using A500 manager but it fails to change modes or retrieve anything
I have tried HC_RollbackRom_3.2.1_Gen2_tdV4 but it fails
I have tried Nvflash but I recieve the following error msg on any command - "rcm Version OX4", "Command send failed (USB write failed)"
It would seem that even though connected by USB in ATX mode, my computer is unable to talk to the Pad - does anybody have any ideas what steps I can take to get out of this mess.
Any and all help appreciated
Click to expand...
Click to collapse
11 digit CPUIDs aren't truly CPUIDs - they are android device IDs which do not apply here. Take a look at the SKB recovery thread to recover the CPUID from APX Mode. You can then convert CPUID => SBK using http://a500bootloaderflash.tk/sbkcalc/

Hi BlackThund3r
I did a search for an SBK recovery thread as you suggested and found this http://forum.xda-developers.com/showthread.php?t=1751978 (Had been doing a lot of searching for CPUID but never thought to look for SBK
Anyway that thread describes exactly my situation, It would seem it's my bad for being a windows user ha ha but I have used Ubuntu before.
I don't have time to get Ubuntu and try the steps suggested until later tonight but as the thread describes exactly my problem I am confidant it will work so thank you very much in advance.
I will reply back here with the result - Again thank you for your time and quick response.
Subzone

[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] Nexus 7 Cannot boot into recovery and cannot

Hey guys,
So I recently bought a nexus 7 32gb (first generation) and used it for about 30 minutes, then I applied what I presume was a faulty update and it has soft bricked my tablet.
Heres the scenerio,
-I cannot get my nexus 7 into usb debugging mode because it wont boot up into the actual interface and such
-Everytime I try to install the ADB drivers, the system installs it as "google nexus 7 bootloader interface"
-recovery mode will not load up, it ends up at the google screen with a text on the topright saying "booting failed"
-I'm pretty sure my bootloader is locked which could be another reason why I cant do any of the methods involving cmd, nrt, or that manual android sdk toolkit thing.
As far as I know right now (which is barely anything since I'm new to using this tablet), I can't do anything because I cannot get into usb debugging, nor can I get the tablet to read as the ADB interface / pass the full driver test in NRT.
Hopefully someone can help (Very descriptively please!) , thanks!
Sidenotes : my boot loader menus states the following...
FASTBOOT MODE
Product Name - Grouper
Variant - Grouper
HW version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - idk if I should actually post this but im going to assume it's irrelevant for this subject
Signing - not defined yet
Lock state - Locked
Also, It was fresh out of the box, I think the tablet was updated to 4.1

bump...
anyone?!??!?!

I'm having a problem that is a little similar to yours. I have a nexus 7 2013 wifi. It won't boot up all the way it gets stuck on the X screen. Bootloader is locked and usb debugging is off. I've been trying to figure out if I can do a pull or backup over the adb sideloader.
Does your nexus have that capability?
I did come across a method that would unlock the bootloader. You need to install a nexus 7 toolkit.
I don't know if that will help you but let me dig up the link to the instructions.

If you would take the time to actually read the guides around here you would know that USB debugging is not a requirement in fast boot or recovery mode. USB debugging only applies to a booted os. Why don't you follow the guides and manually install your drivers? Use fast boot commands to flash a stock image. This isn't difficult to do. Stop messing with toolkits and learn something. You're here on XDA, utilize the resources we have.

happyfuntimes7 said:
Hey guys,
So I recently bought a nexus 7 32gb (first generation) and used it for about 30 minutes, then I applied what I presume was a faulty update and it has soft bricked my tablet.
Heres the scenerio,
-I cannot get my nexus 7 into usb debugging mode because it wont boot up into the actual interface and such
-Everytime I try to install the ADB drivers, the system installs it as "google nexus 7 bootloader interface"
-recovery mode will not load up, it ends up at the google screen with a text on the topright saying "booting failed"
-I'm pretty sure my bootloader is locked which could be another reason why I cant do any of the methods involving cmd, nrt, or that manual android sdk toolkit thing.
As far as I know right now (which is barely anything since I'm new to using this tablet), I can't do anything because I cannot get into usb debugging, nor can I get the tablet to read as the ADB interface / pass the full driver test in NRT.
Hopefully someone can help (Very descriptively please!) , thanks!
Sidenotes : my boot loader menus states the following...
FASTBOOT MODE
Product Name - Grouper
Variant - Grouper
HW version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - idk if I should actually post this but im going to assume it's irrelevant for this subject
Signing - not defined yet
Lock state - Locked
Also, It was fresh out of the box, I think the tablet was updated to 4.1
Click to expand...
Click to collapse
Use Nexus root toolkit and folow Full driver instalation guide for correct driver instalation
After this use Flash stock to repair, then you can continue to unlock/root or anithing else.

APX MODE driver and stuck in APX mode issues

Tab is an acer iconia a500 8gb version running CWM, and HC bootloader. Last ROM on honeycomb was flexreaper but I forget version. I hadn't used tab in a while.
I wanted to let you know how I resolved it. I spent 2 days trying to upgrade to ICS bootloader and touch recovery. I almost gave up with a partial brick of a tab. I was no longer able to boot a ROM but could get to APX mode (sort of APX mode) where screen was black and power LED was on by using manual process. Hold in power and Reset for 3 seconds then release power while holding reset for another second. Tab would be recognized as APX mode device by the computer and flash tools but I couldn't get any of the tools to do the flashing. Blackthunder and nvflash failed with various errors. I found out after hours of trying this was not really APX mode. See below.
1. To fix USB driver issue. I had to install the Naked USB driver and Google USB driver from SDK package. All links found here on XDA. Only at this point did the tab show as a valid working APX device in devices and printers. Drivers still showed as unknown but worked. In Device manager was showing under USB host controller as acer usb recovery device or something like that.At this point I had all drivers installed. Acer driver, Google USB, and naked driver. I installed in that order until device was working on win 7 x64.
2. APX mode is described in some places as blank screen with power LED on but this is like stage one of apx mode. You still need the tool (nvflash or blackthunder) to get you to the point where the screen says APX mode in white font in the left upper corner and you are truely in APX mode. Use the auto process in the tool until you get there. My tab also had the word acer in large green font in the middle of the LCD when in true APX mode. I was never able to get to full APX mode using manual APX process on tab. This seems to place the tab in an APX ready state. Then you can use nvflash, a500manager, or blackthunder auto tools to get to full apx mode. Tab does a quick reboot or something and vibrates when going from APX ready to full APX mode with the screen going from blank to where it says apx mode in small white letters and acer in green large font (middle of screen). After I was in APX mode The only thing that worked was BABSECTOR or BADSECTOR tool to flash it. I ran the a501a.bat and then the a501b.bat inside the extracted folder to get ICS V8 bootloader and touch recovery installed. Once I used the BADSECTOR tool the process was quick and flashed in a matter of a few minutes. In 2 minutes I had completed what was going on for almost 2 days. Wow! I almost gave up. You can edit the script or just insert your SBK at the prompt.
I found the BAD or BABSECTOR process listed in a short post comment on another forum using google searches. There wasn't a lot of detail. Just the order of file use and that it it worked for someone who was having similar issues. You obviously need your SBK.
Hope this helps someone. Good luck!
Auto signature below is wrong. I had changed to flexreaper ROM.

smd11873 said:
Tab is an acer iconia a500 8gb version running CWM, and HC bootloader. Last ROM on honeycomb was flexreaper but I forget version. I hadn't used tab in a while.
I wanted to let you know how I resolved it. I spent 2 days trying to upgrade to ICS bootloader and touch recovery. I almost gave up with a partial brick of a tab. I was no longer able to boot a ROM but could get to APX mode (sort of APX mode) where screen was black and power LED was on by using manual process. Hold in power and Reset for 3 seconds then release power while holding reset for another second. Tab would be recognized as APX mode device by the computer and flash tools but I couldn't get any of the tools to do the flashing. Blackthunder and nvflash failed with various errors. I found out after hours of trying this was not really APX mode. See below.
1. To fix USB driver issue. I had to install the Naked USB driver and Google USB driver from SDK package. All links found here on XDA. Only at this point did the tab show as a valid working APX device in devices and printers. Drivers still showed as unknown but worked. In Device manager was showing under USB host controller as acer usb recovery device or something like that.At this point I had all drivers installed. Acer driver, Google USB, and naked driver. I installed in that order until device was working on win 7 x64.
2. APX mode is described in some places as blank screen with power LED on but this is like stage one of apx mode. You still need the tool (nvflash or blackthunder) to get you to the point where the screen says APX mode in white font in the left upper corner and you are truely in APX mode. Use the auto process in the tool until you get there. My tab also had the word acer in large green font in the middle of the LCD when in true APX mode. I was never able to get to full APX mode using manual APX process on tab. This seems to place the tab in an APX ready state. Then you can use nvflash, a500manager, or blackthunder auto tools to get to full apx mode. Tab does a quick reboot or something and vibrates when going from APX ready to full APX mode with the screen going from blank to where it says apx mode in small white letters and acer in green large font (middle of screen). After I was in APX mode The only thing that worked was BABSECTOR or BADSECTOR tool to flash it. I ran the a501a.bat and then the a501b.bat inside the extracted folder to get ICS V8 bootloader and touch recovery installed. Once I used the BADSECTOR tool the process was quick and flashed in a matter of a few minutes. In 2 minutes I had completed what was going on for almost 2 days. Wow! I almost gave up. You can edit the script or just insert your SBK at the prompt.
I found the BAD or BABSECTOR process listed in a short post comment on another forum using google searches. There wasn't a lot of detail. Just the order of file use and that it it worked for someone who was having similar issues. You obviously need your SBK.
Hope this helps someone. Good luck!
Auto signature below is wrong. I had changed to flexreaper ROM.
Click to expand...
Click to collapse
Hi,
Thanks for your informative post - I had no idea there were different "apx modes".
Can you link where you downloaded your drivers in step 1 and the tools in step 2? If your method actually worked, some links would really be helpful.
Thanks!
Rich

[Q] Nexus 7 wont start (anything)

Hello to All,
Yesterday I have tried to mount on my Nexus a partition that was not in use (22gb), used the terminal emulator...
After that command my Nexus wont start... anything not even the LOGO Google appear, when I connect to my PC with the USB cable he recognize only this on the device manager.
Asus transformer Prime APX interface.
Test that I have done:
Try to change baterry and the problem is the same
When I connect to the charger I dont receive any logo
Trie to boot on recovery mode fail
Change the driver in the device manager and start with Nexus root tool kit but it don't work...
Can anyone help me???
Thanks
Tiago Silva

Tsilva80 said:
Hello to All,
Yesterday I have tried to mount on my Nexus a partition that was not in use (22gb), used the terminal emulator...
After that command my Nexus wont start... anything not even the LOGO Google appear, when I connect to my PC with the USB cable he recognize only this on the device manager.
Asus transformer Prime APX interface.
Test that I have done:
Try to change baterry and the problem is the same
When I connect to the charger I dont receive any logo
Trie to boot on recovery mode fail
Change the driver in the device manager and start with Nexus root tool kit but it don't work...
Can anyone help me???
Thanks
Tiago Silva
Click to expand...
Click to collapse
Hi, Tsilva80...
I hate to be the bearer of bad news, but this has all the hallmarks of a corrupted or erased bootloader, in which case your Nexus 7 is probably irretrievably hardbricked.
The lack of the 'white-on-black' Google logo on boot; the lack of the 'white-on-black' battery charging animation when plugged into a wall socket... and the APX entry on Windows device manager, are all symptomatic of a dead, corrupted or erased bootloader.
And without a working bootloader, not only will the device not boot, but you can't even run fastboot commands in order to fastboot flash a Google factory stock image. The bootloader is critical; without it, nothing happens. It's the 'Achilles Heel' of the Nexus 7.
---
APX mode is the default state the Nexus 7 enters into in the absence of a working bootloader, with the expectation that somebody with the necessary technical skills and equipped with an nvFlash tool, will nvFlash a replacement bootloader.
Unfortunately, there is no universal nvFlash tool available for the Nexus 7.
Unless you have, at some point, previously generated unique device dependent 'wheelie blobs' using the flatline procedure (See here and here for more details on this) your only option, is to have the devices motherboard replaced.
Even with the 'wheelie blobs', I haven't read anywhere of anybody successfully using them to revive a hardbricked Nexus 7.
---
Your only glimmer of hope, is that you may have inadvertantly ('deliberately') entered APX mode, by mistake... by pressing VOL-UP (holding) + POWER ON when the device was powered down.
If this is the case, then you **might** be able to break out of APX mode by LONG PRESSING the POWER BUTTON for 15-20 seconds... But this will only work if there is a working bootloader for the device to boot into. If it's erased or somehow corrupted, the Nexus 7 is hardbricked.
See this post, for a list of Nexus 7 button combinations, and more details about entering and exiting APX mode.
---
I really hope you can get your Nexus 7 working again, but based on your post, I can't say I'm optimistic. I suspect you will need a new motherboard.
For what's it's worth... Good Luck.
Rgrds,
Ged.