Database Users

Stuck in APX Mode and Need Help!

Alright, I have been trying to get my A500 out of APX mode for a couple weeks now and have run out of ideas. I am hoping someone here will be able to offer a suggestion I haven't tried. I have read every thread I could find on the subject and it isn't my first time stuck in APX mode and have used the EUU once and Timothy's Root-3.2.1 tool to recover previously. This time something is different though, I have tried 2 different factory EUUs, AfterOTA, APX Flash Tool, Timothy's Root-3.2.1 EUU, nvbat tools, BadSector and possibly more that I am missing, all hangup except the EUUs which error out when the tablet switches to download mode.
I would be greatly appreciative of any ideas anyone may have to save this thing, it is out of warranty and seems to just be an expensive coaster at this point.

The Same Here

The same here too...
Sent from my Galaxy Nexus using xda app-developers app

It sucks, if I can't figure it out within the next couple weeks I think I will take my anger out on it with firearms. I'll pull the battery first but after that rounds will fly.

ponypowerracin said:
It sucks, if I can't figure it out within the next couple weeks I think I will take my anger out on it with firearms. I'll pull the battery first but after that rounds will fly.
Click to expand...
Click to collapse
heck, you can almost get your money back by "parting" it out. Dincdoesme is looking for a front display assembly
Ok, as I sent you the link in PM, for the rest of you folks, here's some things to try.
Note This. I am NOT a brickmaster. I'm just lucky getting things running again for a lot of people. So if these methods don't work, well, don't shoot the cook! I've never been stuck in APX mode, but I've cooked some bootloader's before.
There are a few things that causes this.
1. Your PC is playing tricks. You should disable anti-virus and such. And sometimes, using a different PC can make a difference.
2. Your USB cable. They are not all created equal, as a pin layout may be different. I use my HTC Desire's USB cable and never had an issue. My camera's cables act like they will work, but always produce errors.
3. You have corrupted or damaged memory blocks where the bootloader resides. In this case, the MB will more than likely need replaced.
So with that said, I will give you a link. Now, this zip has one of the very early NVFlash bootloader apps. I couldn't find my original pure NVFlash setup, but I've used this one often in the past. It may be more tolerant.
http://d-h.st/32X
Unzip the contents to a folder.
Have your SBK number ready. You should already have this from your UID number.
Power off your tab. Then manually put it in APX mode, by pressing and holding the pinhole rest, then press and hold PWR. After 4 seconds, release PWR, then 1 second later release pinhole. Your display should be black with a white PWR button. If not try it again or reverse the switches (been a long time)
Start the NVFlash application. DO NOT DOWNLOAD ANY BUNDLES. Plug your tab in when prompted. Always select Auto.
Ignore any windows messages. If it looks like it stops stating no APX devices, just continue.
There are 2 bootloaders and a CWM package. 1 bootloader is for the 500, the other for the 501. They are identicle except for the logo. Just choose one.
Now, note that this is a version 3 unlocked bootloader. It's ok.
At the end, you may or may not get some red ebt message. Ignore it. Just reboot it into CWM.
Hoping this works for you guys.
In the meantime, I'll still look for my original NVFlash which will rule out windows apps and conflicts.
MD

ponypowerracin said:
Alright, I have been trying to get my A500 out of APX mode for a couple weeks now and have run out of ideas. I am hoping someone here will be able to offer a suggestion I haven't tried. I have read every thread I could find on the subject and it isn't my first time stuck in APX mode and have used the EUU once and Timothy's Root-3.2.1 tool to recover previously. This time something is different though, I have tried 2 different factory EUUs, AfterOTA, APX Flash Tool, Timothy's Root-3.2.1 EUU, nvbat tools, BadSector and possibly more that I am missing, all hangup except the EUUs which error out when the tablet switches to download mode.
I would be greatly appreciative of any ideas anyone may have to save this thing, it is out of warranty and seems to just be an expensive coaster at this point.
Click to expand...
Click to collapse
jancarlos1597 said:
The Same Here
Click to expand...
Click to collapse
sebone02 said:
The same here too...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
For you guys stuck in apx - please provide a screenshot of your error messages!!
there are way too many things it COULD be and is difficult to help without physically having the tab in hand!!!! Pictures!!! post some pictures
Running nvFlash,
Go in and edit the .bat file and delete all lines beginning with 'cls' close and save, then run it...and post the error here - not saying you can be fixed but at least all error codes will be in one place.
Depending which error you have will determine whether yr tab needs to be sent to acer for repair...or something far more simple like uninstalling and reinstalling BOTH sets of drivers....
IF apxFlashv4 or timmydeansv4 or MD's suggestion above does not fix you, then yr motherboard is toasted and will need replacement
sebone02 said:
The same here too...
Click to expand...
Click to collapse
@sebone02 -
yr a bit different as u rec'd yr tab stuck in apx, so we dont know what rom was on there b4 this happened....But the bootloader tools definitely wont work from HC3.2 -
first thing to do is make sure you have both sets of drivers installed
the acer ones and the android sdk ones. Then connect to your pc
is the apx device showing and/0r the acer boot/recovery drivers
Try to perform a hard reset to format the cache and userdata
1) Turn off your tablet,
2) Rotation lock to your left;
3) Press Vol+ (which is to a rotation lock) and power on simultaneosly
4) As soon as the tablet vibrates you can release the power on button and you should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.
Then run timmydeansv4.

Thank you to those trying to help.
A couple errors when trying a couple different manual commands with nvflash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nvbat error
EUU error, same thing happens with factory EUUs and root-3.2.1, this error comes up as soon as the tablet switches to apx download mode
Bad Sector error
Sticks in Afterota at flashing recovery
All versions of APX Flash tool hang at the same spot

Yeah, my bag of tricks is empty at the moment. I see in the posts above you, where jazzyjames and a couple others are in the same boat. Everything points to an unrecoverable error in the boot loader partition.
Maybe those guys will stumble onto something, or skirlaz_cz will have some input.
On the 700/701/510 we had the issue right at the start when the first cwm's were couurupting the data partitions when wipes or restores were done. Samsung s3 had the same bug that bricked the partitions. The lead dev in the 700 forum got his own stuck in apx mode for some unknown reason. End result are main board changes for all of them including mine.
On the 70x, they found several hidden partitions, so am hoping that mess is sorted out now.
MD

thanks for posting the pix - i see each tool reports different errors - not sure why this would be, all i can tell you is i have had a couple of nvflash errors along with the EUU update failed screen and the display showing "reboot the device", (all at the same time) which never went away no matter how many times i rebooted....somehow though thru multiple tries over many days i got a working tab again...
I'm sure that in the end the apxflash tool finally recognised my tab in apx mode,
once that happened i manually flashed a bootloader.bin and recovery.img -
you can try this if you have tdv4, use the .img files in there to manually flash via apxflash tool
also, if u have access to linux - running nvflash command from it has helped others...
finally lcd047 ran nvflash directly from tdv4 (his was a partition error):
lcd407; said:
* I downloaded timmyDean's root-3.2.1-V4.7z
* I booted the tablet (in APX mode) and I connected the USB cable to it
* in the directory root-3.2.1/Image I run the command
Code:nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --go
* without rebooting, I flashed the v7 bootloader and recovery as per the bootloader thread; since the partition table was restored at the previous step, the operation now succeeded;
* I rebooted the tablet in recovery, and proceeded to wipe the data and flash a ROM the usual way.
As I already noted, I lost all the data from the internal sdcard. I'm not sure if that was the result of the re-creation of partitions, or I inadvertently did that while messing with nvflash, the bottom line is all files are gone. In turn, restoring the CWM backup didn't do much good, because most apps will fail in interesting ways without the sdcard data, so I'll probably just start from scratch and reinstall the apps from a Titanium backup. But I have a working tablet again.
Click to expand...
Click to collapse
another good thread to take a look at, although i got lost after page1!!!!
No access to ROM or Recovery its the only fix i have seen that addresses the problem and provides a solution - its a shame i cannot understand it, lol
from what i've seen on the boards the ebt issue is damn near unrecoverable,
partition errors seem a little easier??
bct errors can sometimes be recovered from using the dump my bct option in apxflash 0.4 IF you can get the tool to recognise yr tab...
If tdv4 fails then its a bit of a lottery in finding something else that works
ensuring that an apx device is recognised by yr pc is fundamental in getting any of the automated tools to work....
I do wish you all the best in finding a solution, and please keep us all posted on how u ALL get on with this....
rgds dibb

ponypowerracin said:
Thank you to those trying to help.
A couple errors when trying a couple different manual commands with nvflash
Sticks in Afterota at flashing recovery
All versions of APX Flash tool hang at the same spot
Click to expand...
Click to collapse
I know its been a while for you facing this problem, but I'm seeing the exact smae problem now.
Did you have any luck getting this fixed?

mandar_h said:
I know its been a while for you facing this problem, but I'm seeing the exact smae problem now.
Did you have any luck getting this fixed?
Click to expand...
Click to collapse
My A500 had a bad memory module and I ended up sending it back to Acer for repair. I was about a month out of warranty but by contacting them through Twitter they went ahead and fixed it for free.

ponypowerracin said:
My A500 had a bad memory module and I ended up sending it back to Acer for repair. I was about a month out of warranty but by contacting them through Twitter they went ahead and fixed it for free.
Click to expand...
Click to collapse
I'm way out of warranty. So I doubt if they will entertain my case at all.
Thanks for the reply.

Try Acer m8 they have been known to repair these faulty out if warranty tabs. That's if you're certain its the chip....See this http://forum.xda-developers.com/showthread.php?t=2738138
Sent from my HTC_PN071 using Tapatalk

Brick?Rom manager

Hi, need help with my tf300t, i was on latest cyanogenmod and twrp, after install rom manager i install cwm recovery for have autupdate and installation with cm10, after reboot to recovery it take me at twrp recovery, i reboot system and reboot again in recovery and now i'm stuck at asus logo, what can i do?
Tablet won't open the selection menu for usb recovery etc.
(If i must send it at asus support, unlock bootloader only invalidate the warranty asus or even that of the store where i buy it?)
(someone knows tell me about how much will it cost me?)

anthraxx90 said:
Hi, need help with my tf300t, i was on latest cyanogenmod and twrp, after install rom manager i install cwm recovery for have autupdate and installation with cm10, after reboot to recovery it take me at twrp recovery, i reboot system and reboot again in recovery and now i'm stuck at asus logo, what can i do?
Tablet won't open the selection menu for usb recovery etc.
(If i must send it at asus support, unlock bootloader only invalidate the warranty asus or even that of the store where i buy it?)
(someone knows tell me about how much will it cost me?)
Click to expand...
Click to collapse
Do I understand you used rom manager to install cwm? If so you just flashed TF201 recovery ( cwm ) onto a TF300 unit.
Use this link as it was made just for this situation.
http://forum.xda-developers.com/showthread.php?t=1680570&highlight=rom+manager

tobdaryl said:
Do I understand you used rom manager to install cwm? If so you just flashed TF201 recovery ( cwm ) onto a TF300 unit.
Use this link as it was made just for this situation.
http://forum.xda-developers.com/showthread.php?t=1680570&highlight=rom+manager
Click to expand...
Click to collapse
can't access to recovery

anthraxx90 said:
can't access to recovery
Click to expand...
Click to collapse
I'll have to think a little about this problem. No recovery, no boot, no bootloader menu, correct?
While stuck on Asus logo try fastboot devices and adb devices, report.

tobdaryl said:
I'll have to think a little about this problem. No recovery, no boot, no bootloader menu, correct?
While stuck on Asus logo try fastboot devices and adb devices, report.
Click to expand...
Click to collapse
can't access to flash menu just asus logo and unlock bootloader on the top left of the screen.

anthraxx90 said:
can't access to flash menu just asus logo and unlock bootloader on the top left of the screen.
Click to expand...
Click to collapse
Humor me!
Example:
I can run "adb logcat" and get logs long before unit completely boots or leaves the screen you are stuck on. Force power off by holding power till screen goes black power on, give one of the commands I gave above,. Do the same and try the other command. Report. You are pretty well trapped and we are looking for any way to process one command by adb or fastboot.
If neither of the above works we have a couple more option. but they will be handled much the same.
In looking at our posts I don't believe we are communicating very well.
Maybe someone else can come in and help you better.
Anyone?

tobdaryl said:
Humor me!
Example:
I can run "adb logcat" and get logs long before unit completely boots or leaves the screen you are stuck on. Force power off by holding power till screen goes black power on, give one of the commands I gave above,. Do the same and try the other command. Report. You are pretty well trapped and we are looking for any way to process one command by adb or fastboot.
If neither of the above works we have a couple more option. but they will be handled much the same.
In looking at our posts I don't believe we are communicating very well.
Maybe someone else can come in and help you better.
Anyone?
Click to expand...
Click to collapse
2 days ago i send my tf300 to asus but they called me this morning and ask for 150€ for repair (they told me: the flash memory must be change), i haven't this money, i take tablet to home this afternoon, there is a way to solve the problem by me without asus support? need help :crying:
Edit:I went to the center asus, and I taked my asus tablet, they told me that asus did that price (150€, i not accept that price and i take my tab to home), and that there may be a cable (I doubt it) that has the ability to connect your tablet to your PC even if bricked.
the tablet now is currently charging because battery is too low to poweron.
i hope you might help me. I'm desperate
The pc didn't recognize it in any way, try vol+ and power , vol- and power but nothing, can't access to flash menu and pc didn't recognize. how can i do?
http://forum.xda-developers.com/showthread.php?t=1766227 may help?

anthraxx90 said:
2 days ago i send my tf300 to asus but they called me this morning and ask for 150€ for repair (they told me: the flash memory must be change), i haven't this money, i take tablet to home this afternoon, there is a way to solve the problem by me without asus support? need help :crying:
Edit:I went to the center asus, and I taked my asus tablet, they told me that asus did that price (150€, i not accept that price and i take my tab to home), and that there may be a cable (I doubt it) that has the ability to connect your tablet to your PC even if bricked.
the tablet now is currently charging because battery is too low to poweron.
i hope you might help me. I'm desperate
The pc didn't recognize it in any way, try vol+ and power , vol- and power but nothing, can't access to flash menu and pc didn't recognize. how can i do?
http://forum.xda-developers.com/showthread.php?t=1766227 may help?
Click to expand...
Click to collapse
If you have cord plugged between pc and tablet and both powered on do you get anything if you use command ( adb devices )? I'm not talking about trying to get into any menu or using volume or anything else.
Just connect the cord between pc and tablet and give command.
You may have already done this but I'm not sure and it would be nice to know the message if the command fails!

tobdaryl said:
If you have cord plugged between pc and tablet and both powered on do you get anything if you use command ( adb devices )? I'm not talking about trying to get into any menu or using volume or anything else.
Just connect the cord between pc and tablet and give command.
You may have already done this but I'm not sure and it would be nice to know the message if the command fails!
Click to expand...
Click to collapse
What i must do exactly?

anthraxx90 said:
What i must do exactly?
Click to expand...
Click to collapse
connect powered tablet to pc and in terminal type - adb devices - tell me what response you get from command.
It may not work but is worth a try before you go farther.
If you have not set your path for adb you will need to cd into proper directory with terminal first before sending command. I can't even guess because I don't know your OS but since you had cwm you have used the terninal - Windows = cmd or command.com

tobdaryl said:
connect powered tablet to pc and in terminal type - adb devices - tell me what response you get from command.
It may not work but is worth a try before you go farther.
If you have not set your path for adb you will need to cd into proper directory with terminal first before sending command. I can't even guess because I don't know your OS but since you had cwm you have used the terninal - Windows = cmd or command.com
Click to expand...
Click to collapse
I use windows 8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://tinypic.com/view.php?pic=2rwn4nd&s=6
(on my pc in programs file i've an asus folder with driver usb)
ok i've done it http://tinypic.com/view.php?pic=1vptd&s=6
but no device are listed under: list of devices attached

anthraxx90 said:
I use windows 8
http://tinypic.com/view.php?pic=2rwn4nd&s=6
Click to expand...
Click to collapse
This shows us you are in your home directory and your os does not know where adb is located. You probably used fastboot to flash cwm to your tablet. Fastboot and adb are normally in the same directory and you need to cd to that directory as you did when you flashed cwm.
If you don't know where that is located you can search for adb or fastboot.
Sorry I don't have windows, I'm using Ubuntu on a mac (I don't even use mac but have it on an external drive if needed). We can figure it out if we are both patient.
So if the above does not give needed results tell me and we'll adjust.

Ok i've tried fastboot and adb but fastboot tell me:wait for device and adb devices can't recognize tablet, there are no device under the list of connected device.
I've tried fastboot reboot and adb reboot to test if the device was connected but nothing happened.

anthraxx90 said:
Ok i've tried fastboot and adb but fastboot tell me:wait for device and adb devices can't recognize tablet, there are no device under the list of connected device.
I've tried fastboot reboot and adb reboot to test if the device was connected but nothing happened.
Click to expand...
Click to collapse
One step down. If you have tf300t on left side about one inch - 25.4 mm below sdcard there is a small hole (reset). With cord still plugged between pc and tablet, power on tablet and use a small paperclip to insert gently into hole. As you insert you will feel it stop, gently push slightly farther and you will feel a little spring.
This will cause your unit to restart and if we are lucky there will be a change in what happens with commands (adb - fastboot) and or what is displayed on the screen.

tobdaryl said:
One step down. If you have tf300t on left side about one inch - 25.4 mm below sdcard there is a small hole (reset). With cord still plugged between pc and tablet, power on tablet and use a small paperclip to insert gently into hole. As you insert you will feel it stop, gently push slightly farther and you will feel a little spring.
This will cause your unit to restart and if we are lucky there will be a change in what happens with commands (adb - fastboot) and or what is displayed on the screen.
Click to expand...
Click to collapse
i've done the reset, but nothing change with adb and fastboot

anthraxx90 said:
i've done the reset, but nothing change with adb and fastboot
Click to expand...
Click to collapse
Only two things left that I know about. You previously listed a link http://forum.xda-developers.com/showthread.php?t=1766227 that might possibly work but at the position we are in currently if it doesn't work we won't know the difference and the drivers already on your pc that are known to work will be replaced so.
1.
I have seen a post somewhere that the case was removed and the battery disconnected and then reconnected and that allowed access to the bootloader menu by holding down volume while reconnecting the battery.
2.
Try the drivers listed above.
Videos for removing case for battery access
1.
http://www.firstpost.com/topic/orga...former-battery-video-KJihe-hpA4M-14773-4.html
2.
http://www.youtube.com/watch?v=9eOu4Y9D33Y
I don't like either choice but with no adb or fastboot access, no recovery, and no bootloader menu we are pretty well trapped.
Just thought of something I have read twice recently. Even though fastboot appears to not work give it the command two or three times. I think I would try this first. Since a stock blob contains rom and recovery I would try to flash stock 10.4.2.13 blob.
fastboot -i 0x0B05 flash system blob
wait here because this is a big file
fastboot -i 0x0B05 reboot
You would unzip stock 10.4.2.13 twice to get the blob. Place the blob into the directory where you found fastboot.

tobdaryl said:
Only two things left that I know about. You previously listed a link http://forum.xda-developers.com/showthread.php?t=1766227 that might possibly work but at the position we are in currently if it doesn't work we won't know the difference and the drivers already on your pc that are known to work will be replaced so.
1.
I have seen a post somewhere that the case was removed and the battery disconnected and then reconnected and that allowed access to the bootloader menu by holding down volume while reconnecting the battery.
2.
Try the drivers listed above.
Videos for removing case for battery access
1.
http://www.firstpost.com/topic/orga...former-battery-video-KJihe-hpA4M-14773-4.html
2.
http://www.youtube.com/watch?v=9eOu4Y9D33Y
I don't like either choice but with no adb or fastboot access, no recovery, and no bootloader menu we are pretty well trapped.
Just thought of something I have read twice recently. Even though fastboot appears to not work give it the command two or three times. I think I would try this first. Since a stock blob contains rom and recovery I would try to flash stock 10.4.2.13 blob.
fastboot -i 0x0B05 flash system blob
wait here because this is a big file
fastboot -i 0x0B05 reboot
You would unzip stock 10.4.2.13 twice to get the blob. Place the blob into the directory where you found fastboot.
Click to expand...
Click to collapse
Ok i'll try to flash blob this afternoon at home, i hope it do something, cause i don't want open my tablet
Edit: i'm at home, the tablet's battery is low and it don't power on now, i to charge now and try

Nothing when i try to flash blob cmd is stop at waiting for devices.

Does windows device manager sees any kind of a transformer device?
If yes try to install the drivers by hand.
right klick on the device
choose update driver software
choose search manually on computer
next window choose from a list on computer (the one at the buttom of the window)
Then you will get a 2sided window
right side you have the company names
left side you have the model type
if you have something like asus ther on the right side choose it
then on the left side choose Asus android ADB device (!!!! not the one with Composite)
then klick on next
if a window pops up saying something like its not recommended just hit yes and install it anyway.
Translatet it from German, so I hope the translation is correct. Just follow the steps and you will know what I mean.

mikaole said:
Does windows device manager sees any kind of a transformer device?
If yes try to install the drivers by hand.
right klick on the device
choose update driver software
choose search manually on computer
next window choose from a list on computer (the one at the buttom of the window)
Then you will get a 2sided window
right side you have the company names
left side you have the model type
if you have something like asus ther on the right side choose it
then on the left side choose Asus android ADB device (!!!! not the one with Composite)
then klick on next
if a window pops up saying something like its not recommended just hit yes and install it anyway.
Translatet it from German, so I hope the translation is correct. Just follow the steps and you will know what I mean.
Click to expand...
Click to collapse
windows don't see the tablet, i've tried but nothing, no usb input sound, it doesn't recognize tf300, i've already driver installed on pc

[Q] Nexus7 fully bricked with APX mode Only

For updating to android 4.3 , I flashed my N7.
I download the package the factory image from Google .
I entered the fastboot and do things following:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15r.zip
when it come to
Code:
fastboot -w update image-razor-jss15r.zip
there is a warning about the bootloader
At this time ,bootloader seems didn't chaged , it's still grouper not flo.
I modified the android-info.txt to cheat the program and the tragedy start.
The windows remind me there is 6 unknown device. And then it fully bricked.
Now, When I turn on the N7, the screen stay blank.
APX device appear while connect to PC.
Can't enter fastboot mode ,can't enter recovery. even the screen can't be lighten.
Anyone else meet the same trouble or someone can help?
Before this, I have had try the follow tools.
The Nexus7 toolkit--won't work
tegra-android-developer-pack from nvidia website tegra developer tools --won't work
nvflash and wheelie from androidroot.mobi --can't work --(It's a rediculous project I think, If the fastboot work,why we need to flash rom via nvflash)

Sorry, but if you really flashed the files above, you have bricked your N7 completely. Probably you should have looked around and informed yourself before starting to flash files which are not compatible with the N7.
Btw. if you had used wheelie before, you would have some recovery files and you would be able to recover yourself from the brick. So it's not a ridiculous project at all.

I thought it's common sense to read, read, read and read a bit more faqs/how-tos/guides before doing anything to a device.
First of all, 'grouper' is the codename of the 1st gen N7 Wi-Fi (the 2012 model) while 'flo' is the 2nd gen N7 (2013 model), so you can't flash ones image to the other device.
Secondly, your device might be saved, but only if you still can access it with fastboot. If so, then flash the proper images for your device using a toolkit or a guide, if not, then you have a nice paperweight.

37nook said:
For updating to android 4.3 , I flashed my N7.
I download the package the factory image from Google .
I entered the fastboot and do things following:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15r.zip
when it come to
Code:
fastboot -w update image-razor-jss15r.zip
there is a warning about the bootloader
At this time ,bootloader seems didn't chaged , it's still grouper not flo.
I modified the android-info.txt to cheat the program and the tragedy start.
The windows remind me there is 6 unknown device. And then it fully bricked.
Now, When I turn on the N7, the screen stay blank.
APX device appear while connect to PC.
Can't enter fastboot mode ,can't enter recovery. even the screen can't be lighten.
Anyone else meet the same trouble or someone can help?
Before this, I have had try the follow tools.
The Nexus7 toolkit--won't work
tegra-android-developer-pack from nvidia website tegra developer tools --won't work
nvflash and wheelie from androidroot.mobi --can't work --(It's a rediculous project I think, If the fastboot work,why we need to flash rom via nvflash)
Click to expand...
Click to collapse
This is a text book example of what happens when people don't read enough, and don't fully understand what they're doing. And it's not as if there aren't enough guides and how-to's here on XDA... and even on other forums!
Hi, 37nook...
You have almost certainly over-written your bootloader with a completely incompatible version designed for a different tablet (2nd gen Nexus 7)... and thus you are hardbricked. This is why you can't access fastboot mode and why your tablet defaults to APX mode when you hook it up to your PC.
And unless you had at some point run the flatline procedure BEFORE being bricked, your tablet is unrecoverable.
Regarding flatline (nvFlash) itself, it's designed, primarily as an emergency recovery measure... and not as a replacement for fastboot, as you seem to suggest in your post. It's preemptive and needs to have been executed before being 'bricked' in order to generate your own unique 'wheelie blobs', which are created on a per-device basis. Without these, nvFlash alone is useless.
It's not much comfort, I know... but I can only suggest you chalk this down to experience, and next time, with whatever tablet/phone you next end up with.... PAY ATTENTION TO WHAT YOUR DOING, AND READ EVERYTHING, and if you're still a little unsure... POST A QUESTION. Better to feel like you're asking a dumb question (which might not be so dumb), than end up with an expensive paperweight.
Rgrds,
Ged.

AndDiSa said:
Sorry, but if you really flashed the files above, you have bricked your N7 completely. Probably you should have looked around and informed yourself before starting to flash files which are not compatible with the N7.
Btw. if you had used wheelie before, you would have some recovery files and you would be able to recover yourself from the brick. So it's not a ridiculous project at all.
Click to expand...
Click to collapse
nvflash is not a good choice for one to flash his device because of higher risk.
there is too many tools available with a lower risk.
That's the reason I didn't use wheelie before.
You are right, I am a very impatient person, and now I get a lesson.

Erovia said:
I thought it's common sense to read, read, read and read a bit more faqs/how-tos/guides before doing anything to a device.
First of all, 'grouper' is the codename of the 1st gen N7 Wi-Fi (the 2012 model) while 'flo' is the 2nd gen N7 (2013 model), so you can't flash ones image to the other device.
Secondly, your device might be saved, but only if you still can access it with fastboot. If so, then flash the proper images for your device using a toolkit or a guide, if not, then you have a nice paperweight.
Click to expand...
Click to collapse
It's actually a nice paperweight now.
Thank you for your reply which tells me where I went wrong.
It's a really serious mistake, and it's also a painful story.
I can't access it with fastboot ,so said.

GedBlake said:
This is a text book example of what happens when people don't read enough, and don't fully understand what they're doing. And it's not as if there aren't enough guides and how-to's here on XDA... and even on other forums!
Hi, 37nook...
You have almost certainly over-written your bootloader with a completely incompatible version designed for a different tablet (2nd gen Nexus 7)... and thus you are hardbricked. This is why you can't access fastboot mode and why your tablet defaults to APX mode when you hook it up to your PC.
And unless you had at some point run thev flatline procedure BEFORE being bricked, your tablet is unrecoverable.
Regarding flatline (nvFlash) itself, it's designed, primarily as an emergency recovery measure... and not as a replacement for fastboot, as you seem to suggest in your post. It's preemptive and needs to have been executed before being 'bricked' in order to generate your own unique 'wheelie blobs', which are created on a per-device basis. Without these, nvFlash alone is useless.
It's not much comfort, I know... but I can only suggest you chalk this down to experience, and next time, with whatever tablet/phone you next end up with.... PAY ATTENTION TO WHAT YOUR DOING, AND READ EVERYTHING, and if you're still a little unsure... POST A QUESTION. Better to feel like you're asking a dumb question (which might not be so dumb), than end up with an expensive paperweight.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for your suggestion
There is still a question
I actually run these code twice.
First time a got a warning. because of the file content of android-info.txt in image-razor-jss15r.zip
the code
Code:
fastboot reboot-bootloader
must have been executed, and the bootloader is still grouper.
means the code
Code:
fastboot flash bootloader bootloader-flo-flo-03.14_img
didn't work
And the second time
Code:
fastboot -w update image-razor-jss15r.zip
led to the tragedy because I modified the android-info_txt in image-razor-jss15r_zip
What happened in updating image-razor-jss15r_zip ?

37nook said:
Thank you for your suggestion
There is still a question
I actually run these code twice.
First time a got a warning. because of the file content of android-info.txt in image-razor-jss15r.zip
the code
Code:
fastboot reboot-bootloader
must have been executed, and the bootloader is still grouper.
means the code
Code:
fastboot flash bootloader bootloader-flo-flo-03.14_img
didn't work
And the second time
Code:
fastboot -w update image-razor-jss15r.zip
led to the tragedy because I modified the android-info_txt in image-razor-jss15r_zip
What happened in updating image-razor-jss15r_zip ?
Click to expand...
Click to collapse
That is indeed puzzling... if after flashing the incorrect bootloader, and the bootloader is still showing as 'grouper' AFTER fastboot reboot-bootloader, then I'm puzzled.
I'm also further puzzled, that the rest of the flash went ahead... seemingly successfully. I know on my 'grouper', when fastboot flashing back to factory stock... if the bootloader isn't the correct version (for that version of factory stock), the flash aborts with the message 'Incorrect bootloader version'. I'm not sufficiently knowledgable though, concerning the specific details of the second gen Nexus 7 and it's associated stock factory images, to make further comment.
It's just possible (though unlikely), you might just be stuck in APX mode, instead of having a corrupted bootloader.
I assume you've tried all the usual button press combos... detailed here.
If you can boot into the bootloader, your Nexus 7 is recoverable... though I'm not optimistic.
Rgrds,
Ged.

OP, did you ever have any luck?

zamboniman87 said:
OP, did you ever have any luck?
Click to expand...
Click to collapse
+1

Hard Bricked Nexus 7 2012 Wifi NVFlash tool reports "uknown device found"
I just need to know and maybe need help modifying the adb/fb/apx android_apxusb.inf file more specifically targeted toward the nexus 7 for windows xp, my tablet does not boot into fastboot mode so fastboot.exe and adb.exe commands for reviving my tablet is out of the question.The nvflash tool in apx mode would be my only hope as the tablet stays with black screen and does not even show battery icon of it charging.I have been searching day and night for a solution and nothing.I have tried all the button combinations for the weird amount of seconds blah blah and nothing, i have tried everything, believe me...nvflash would be my only hope.I do not have any backed up blob.bin files so I can not use wheelie.exe I even tried someone elses blob.bin but no It is because the uid is unique I understand, I even opened the blob.bin file with notepad and supplied my CSSN code and the first part worked but the next part stumped me.... the rcm version part.I have the Secure Boot Key generated by supplying the CSSN of device in blackthunders tool so I want to run NVFlash.exe --bl bootloader-grouper-4.18.img --sbk 0x10117000 0x761CD506 0x7EE73604 0xBE055203 --sync.I have tried the universal naked drivers 0.73 but "ASUS Transformer Prime APX Interface" shows up in device manager after modifying the android_apxusb.inf file and supplying it the "Hardware device id" from device mamager by right clicking selecting properties etc;.Could there be an entry I could put in the android_apxusb.inf file for nexus 7 that nvflash.exe would not report "Uknown Device Found" and would recognize my nexus 7?.I did get the "ASUS Transformer Prime APX Interface" succesfully installed but nvflash is whining about the device being unknown.Furthermore I would like to make clear that the were no exclamation yellow triangles or anything and the device reported as working properly in device manager.I dearly would appreciate some insight into this.This all happpened on a personal quest to flash another kernel.Sequentially I use "TWRP" to wipe everything that they suggest you wipe" Davlik cache", "data", and two others, but after I wiped them I noticed that those were recommended to be wiped for flashing another ROM.I read just a little more down in the webpage that for flashing a kernel I only needed to wipe Davlik Cache and Data.I restarted the tablet and bam! bootloop.The android colorful spheres and no further.To recover from this I used Skip's Nexus v1.8.0 used the Soft-Bricked Bootloop option on the middle right of the tool's GUI hit the Flash Stock+Unroot buttton and let it run.I would let it run then it would take to long and appear to not progress so I stopped it and re ran it.This happened a few times but I finallly got it to complete, and after the toolkit rebooted my device i saw the "GOOGLE" Text when device booted.I waited for about 2 minutes and I saw it was not getting anywhere so I powered the Nexus 7 device off.
Next thing I did was press power button and nothing.I have tried everyhing, I assume that the solution would be nvflash and a cutomized .INF file pin point targted specifically for the nexus 7 2012 WiFi only tablet.Please help me, if there is no special APXInterface entrie i can edit the android_apxusb.inf file to help nvflash detect my device then it is game over for me.LOL I have seen many people post with a similar and identical poblem that have given up but I'm determned.LOL

Begining to think that it has to do with the nvflash.exe version is why.
After downloading another nvflash.exe with it's acompanying .dll's I found a nvflash program that executed and did not display the familiar "unknown device found" error message.I did it with the "NVidia USB Recovery mode for mobile" driver, nothing fancy.I was surprised that that nvflash version at least ran.The nvflash version i used is the nvflashtf201which is the Tegra3 ICS nvflash.I run that version of nvflash and I at least get this message in the command prompt on Windows XP sp3 after issuing a "harmless" nvflash --sync command.
Nvflash v1.13.87205 started
chip uid from BR is: 0x0000000000000000015d483bd137ec12
rcm version 0X4
Command send failed (usb write failed)
I googled around and some people say that it is because the bootloader is locked, and other say it is because the SBK version is 2 or higher or somthing if im not mistaken.As far as I know is that before I got the gadget hard bricked the boot loader was unlocked.I have even gone as far as to reformating my other computer and installing Unity Linux just to get my device accepting the nvflash commands I have configured the "rules.d" files to what "lsusb" shows I have tried different versions of nvflash like from upload sites and even from nvidias site even tried a newer cable (the newer cable works better but the old one still works)., I downloaded the "Cardhu" "Jelly Bean" stuff from the Tegra Android Development Pack 2.0r6 ( not 2.0r7 because the Tegra Android Development Pack 2.0r7 gives me an md5 hash blah blah error and would not install). The Tegra Android Development Pack 2.0r6 comes with nvflash.The reason I downloaded it was just to get nvflash.I do not have any blob files backed up, I only have the SBK from the chip uid of my device thus would like to try and get a hold of an nvflash in which the "--sbk" command parameter has not been deprecated.I understand that maybe i might not get lucky as the the newer nvflash programs might all have the "--sbk" parameter neutered as well as a few more command parameters.So does anyone know if there is a nvflash version that has the -"--sbk" command paramete support so that I can test and verify if the failed error message above if because I did not supply the program a Secure Boot Key or am I wrong about thinking I need to supply nvflash with a Secure Boot Key in this newer version given the program has a recent algorithm given the program found my devices chip uid as shown in the comman line output above? If thers nothing I can do then can some one comfirm.If there is another nvflash binary that is Tegra3 ICS and has the "--sbk" parameter then point me to where I can find it, or pm me. Thanks

I am almost giving up.
I have been trying to run the tools to check the SBK version.I have read and understand that the reason that I get that usb write error is because of 1.) a locked bootloader. 2.) the SBK version. and the other reasons I am not familiar with.I do not know how to unock the bootloader from APX mode(If that's possible at all.)I did have the bootloader unlocked before running the Nexus 7 toolkit v1.8.0.The option that I ran before my tablet got hosed was the option in the toolkit "Back to Stock" "Current status:" which I had the Soft-Bricked/Bootloop" option selected under the "Flash Stock + Unroot" button which I pressed. After the latter process was finished it rebooted my tablet did it's magic(as I could not see a better way to recover my tablet from the anterior soft brick event which happened before I was led to this process by trying to flash Faux123 kernel) my tablet got stuck at the "Google" with white text and all black screen.The tablet took to long to boot (more then a minute )so I shut it down with the power button.I went to power it on by pressing power button and WALA! hard bricked i'm hosed.The tablet does not boot into fastboot or anything. I cannot use ADB or fastboot either, just the complicated APX mode.I wish tablets were reformatable like computers.But back to the reason for the post;I ran the sbkchek tool and I get a "Segmentation Fault" error.I see many indiviuals in this forum had success running the tool.I am on a 32bit pc with Unity Linux OS.I tried a live cd with Puppy Linux and same error.I tried running the SBKDetect tool that downloaded these forums and the Live CD gives me the "cannot execute binary file" even though it is flagged executable or whatever(I'm not familiar with linux pardon the pun)".I am gonna try to run the tool on Unity Linux and see if I have success but I doubt it will work.Does anyone know if the 2012's Nexus 7 SBK version is SBKv1 or SBKv2?If there are different versions im not sure.I am guessing that the newer than 2012 versions of Nexus 7 have a different SBK version then the earlier ones.I have a question.Could the process of finishing the Nexus 7 Toolkit's "Flash Stock + Unroot" process have changed my bootloader to a locked bootloader and that's why i am getting the RCM Version 0x4 Cannot (Write to USB) error? If it is then what good is it to me if Icannot unlock the bootloader from APX mode? It's a dawg gone shame becuase I have the SBK.Can some one give me some insight or confused dog the right way.lol?

funkyo0o said:
I have been trying to run the tools to check the SBK version.I have read and understand that the reason that I get that usb write error is because of 1.) a locked bootloader. 2.) the SBK version. and the other reasons I am not familiar with.I do not know how to unock the bootloader from APX mode(If that's possible at all.)I did have the bootloader unlocked before running the Nexus 7 toolkit v1.8.0.The option that I ran before my tablet got hosed was the option in the toolkit "Back to Stock" "Current status:" which I had the Soft-Bricked/Bootloop" option selected under the "Flash Stock + Unroot" button which I pressed. After the latter process was finished it rebooted my tablet did it's magic(as I could not see a better way to recover my tablet from the anterior soft brick event which happened before I was led to this process by trying to flash Faux123 kernel) my tablet got stuck at the "Google" with white text and all black screen.The tablet took to long to boot (more then a minute )so I shut it down with the power button.I went to power it on by pressing power button and WALA! hard bricked i'm hosed.The tablet does not boot into fastboot or anything. I cannot use ADB or fastboot either, just the complicated APX mode.I wish tablets were reformatable like computers.But back to the reason for the post;I ran the sbkchek tool and I get a "Segmentation Fault" error.I see many indiviuals in this forum had success running the tool.I am on a 32bit pc with Unity Linux OS.I tried a live cd with Puppy Linux and same error.I tried running the SBKDetect tool that downloaded these forums and the Live CD gives me the "cannot execute binary file" even though it is flagged executable or whatever(I'm not familiar with linux pardon the pun)".I am gonna try to run the tool on Unity Linux and see if I have success but I doubt it will work.Does anyone know if the 2012's Nexus 7 SBK version is SBKv1 or SBKv2?If there are different versions im not sure.I am guessing that the newer than 2012 versions of Nexus 7 have a different SBK version then the earlier ones.I have a question.Could the process of finishing the Nexus 7 Toolkit's "Flash Stock + Unroot" process have changed my bootloader to a locked bootloader and that's why i am getting the RCM Version 0x4 Cannot (Write to USB) error? If it is then what good is it to me if Icannot unlock the bootloader from APX mode? It's a dawg gone shame becuase I have the SBK.Can some one give me some insight or confused dog the right way.lol?
Click to expand...
Click to collapse
I'm in the exact same situation. Nexus 7 2012 hard bricked, shows up in windows with APX driver. Nothing on the screen (stays dark). I have another blob.bin file from my Nexus 7 (bricked one is a friends), but I don't know how to go about modifying blob.bin, if it's even possible, or even finding out this device's SBK. Wish there was a way.

Blob.bin files are encrypted I think.
mzanette said:
I'm in the exact same situation. Nexus 7 2012 hard bricked, shows up in windows with APX driver. Nothing on the screen (stays dark). I have another blob.bin file from my Nexus 7 (bricked one is a friends), but I don't know how to go about modifying blob.bin, if it's even possible, or even finding out this device's SBK. Wish there was a way.
Click to expand...
Click to collapse
Right.I have tried modifying the blob file but I think it would not work.I have not studied nor am I ever gonna reverse engineer a closed source program, nor am I a cryptographer, but nvflash uses some bit strength of encryption to genrate that blob.Since it is encrypted and it would be defeating the purpose of an encryption algorithm existing at all(unless it is a "Proof Of Concept" cracked cypher like WEP) to always generate the same "blob" of "pseudo random data"; and aside from defeating the purpose dumb if it did;Then my guess would be that the probabilty is low to none.But you sure can use the "CSSN" number or "UID" on the box your device came in or a sticker inside your device, then get the "SBCalcv1.1.zip" tool (you should be able to easily find if you google it.There is a link in these forums) and follow the intuitive graphical user interface and it will calculate and display your SBK in a 0x00000000 0x00000000 0x00000000 0x00000000 "format".But getting the SBK was easy what is not goin for me is getting the tools "sbkcheck" and "sbkDetect" (These 2 tools are for Linux only I think) to run without the errors and show me what version.I am not sure if I am wasting my time with the probability my device is SBKv2.If i am not mistaken SBKv2 is the brain child of the manufacturers genius idea of locking the devices down more.So what I understand if I am not mistaken (someone correct me if i am wrong) is that SBKv1 can be used with nvflash but not SBKv1.And having a locked boot loader would make the nvflash tool cough up the dreaded "RCM Version 0x4 Command send failed (USB write failed)" error or whatever the error was lol. Locking the devices down more would increase there sales with the surefire fact someone is bound to brick their device.Instead of investing efforts to facilitate the device's recovery (which probably would be trivial) in case of a human mistake they just seem to want to DRM hardware.If you paid for the darn thing you should have the right to fix or repair the dawg gone thing,it would not hurt anyone but all the patents and intellectual property, registered trademark crap would not allow it.

Someone else blob.bin file might not work but..
I am pretty sure for the reasons i have explained above a blob.bin file will not work which is not unique to the indiviual device it was generated or created on but if you feel that lucky and with all due respect did not understand why then here it is.Good Luck don't say I didn't warn you it would not work.

current solution
mzanette said:
I'm in the exact same situation. Nexus 7 2012 hard bricked, shows up in windows with APX driver. Nothing on the screen (stays dark). I have another blob.bin file from my Nexus 7 (bricked one is a friends), but I don't know how to go about modifying blob.bin, if it's even possible, or even finding out this device's SBK. Wish there was a way.
Click to expand...
Click to collapse
Guys i think there isn't any solution right now, need to wait for Google or some developer to make a proper toolkit to solve that.
till that the only solution i think is to change the Motherboard; that's available on ebay,
but for me i did nothing with my tab, it was updated it self through OTA to 4.4.2.
just working fine but then after a day it got stuck i restarted it,(it took more time then normal to restart) and dead
but what i am confuse of is, if i buy a motherboard and this problem appear again
i am waiting to know what is the mess that take it to APX mode; only after that i will order a motherboard.

Is it still under warranty? You could send it in and have them possibly fix it under warranty. I tried to update to KitKat via the normal method and something went amiss and I went into APX mode as well.
I informed Asus about it and they had me RMA it and it was fixed, free of charge since it was still under warranty (less than year old).
Never hurts to try.

faizleaves said:
Guys i think there isn't any solution right now, need to wait for Google or some developer to make a proper toolkit to solve that.
till that the only solution i think is to change the Motherboard; that's available on ebay,
but for me i did nothing with my tab, it was updated it self through OTA to 4.4.2.
just working fine but then after a day it got stuck i restarted it,(it took more time then normal to restart) and dead
but what i am confuse of is, if i buy a motherboard and this problem appear again
i am waiting to know what is the mess that take it to APX mode; only after that i will order a motherboard.
Click to expand...
Click to collapse
I think I'm the newest member of the hard-bricked Nexus 7 club. Not a happy place to be.
Same thing happened to me last night. Watching YouTube, screen froze, audio kept playing. Went to hard restart, and the Nexus 7 was stuck in a boot loop. Went to boot into fastboot (vol - and power) and it would come up in fastboot, but would not boot to recovery. Restarted a couple times, and now, it's stone dead - won't boot to fastboot, or white Google screen. Nothing. It will connect as an APX device, and I've installed generic drivers. I'm trying to communicate through adb or fastboot, but nothing.
I can't imagine what happened. It was accidentally dropped from about 4 feet earlier in the week - maybe something came loose?
This sucks.

My Nexus 7 (V1) is on APX Mode i have installed the Universal Naked Driver 0.73. Gives it every Chance to bring it back to Android???

[Q]Stuck on Google splash

OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.

a.child said:
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
Click to expand...
Click to collapse
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck

joegestes said:
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
Click to expand...
Click to collapse
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.

a.child said:
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
Click to expand...
Click to collapse
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?

I'm at work now, but I'll try new cables and ports when I get home as well as the adb commands.
I was trying to flash 5.0.1 , and was running some CM12 nightly when it failed. To be clear, the ROM was working fine until it wasn't.
I was using NRT and I had force flash selected (recommended settings I think), but I'm not 100% sure post flash factory reset was checked but in the CMD log I did see it wipe and attempt to write userdata.
I have not tried a different version of stock.
I believe ADB is installed outside of NRT abd i have to manually set my path variable to C:/ADB (which screws up normal command prompt, but idk how to fix that) for NRT to work. I have a 2013 nexus 7 and used the same setup to flash PA a while back without any issues.
NRT doesn't detect my phone when displaying the splash screen, but idk about TWRP.

joegestes said:
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
Click to expand...
Click to collapse
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck

a.child said:
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
Click to expand...
Click to collapse
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.

joegestes said:
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
Click to expand...
Click to collapse
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
I sort of suspected it was a hardware issue when I was getting nowhere with NRT, but I wanted confirmation from someone more knowledgeable than me. Any idea on the likelyhood it is something other than the port? The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue.
oh well...

a.child said:
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
Click to expand...
Click to collapse
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
a.child said:
Any idea on the likelyhood it is something other than the port?.
Click to expand...
Click to collapse
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
a.child said:
The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue
Click to expand...
Click to collapse
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.

joegestes said:
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
Click to expand...
Click to collapse
Well i replaced the port and the battery and i'm having the same problem. And I did check to make sure I didn't reinstall the old port.
Guess she's dead :'(

Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)

ddaggebi said:
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
Click to expand...
Click to collapse
Thanks for the suggestion, but it didn't work. I was able to lock and unlock the bootloaded again, but it didn't have any effect.

Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...

ddaggebi said:
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
Click to expand...
Click to collapse
Looking at other forums, pretty sure the emmc is dead, but I'll try flashing an older version.

[HOWTO] Unbrick Hardbricked (stuck onUSB Logo) MeMo Pad ME170CX (and others)

This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool

Hey @korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated

Premie said:
Hey korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Click to expand...
Click to collapse
I literally faught that error for a whole day. I tried 5 different computers, all had that issue. Usually my tablet would connect and disconnect once before the logo came up. Within that brief window, I was able to start the flash and it worked. I'm pretty sure that's what did it. If you aren't seeing this, turn up your PC's volume and listen for the USB sounds.
This whole thing is pretty annoying, but when it works, it works.

Thanks
I shall keep going at it until it works or I find another solution.

PLEASE help me!
korockinout13 said:
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Click to expand...
Click to collapse
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?

Nandr0idC0nsumer said:
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Click to expand...
Click to collapse
If you have a working boot loader, you don't need to do this.

korockinout13 said:
If you have a working boot loader, you don't need to do this.
Click to expand...
Click to collapse
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore

Nandr0idC0nsumer said:
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Click to expand...
Click to collapse
What happens instead of fastboot mode?

korockinout13 said:
What happens instead of fastboot mode?
Click to expand...
Click to collapse
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."

Nandr0idC0nsumer said:
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Click to expand...
Click to collapse
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.

korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well

Nandr0idC0nsumer said:
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Click to expand...
Click to collapse
You have adb? That's not possible unless you are getting past the boot loader.

korockinout13 said:
You have adb? That's not possible unless you are getting past the boot loader.
Click to expand...
Click to collapse
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload

Nandr0idC0nsumer said:
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Click to expand...
Click to collapse
Hm... seems like you should be able to work with that if you have something flashable.

korockinout13 said:
Hm... seems like you should be able to work with that if you have something flashable.
Click to expand...
Click to collapse
Returned the tablet at Best Buy to get "fixed" (come on bestbuy, I know you mean replaced.) Thanks for your help

Repair
Hi,
I think i can help you out because i worked with the intel tool for weeks now to find a solution to root the me581cl.
Go to my thread and download a newer version of intelPhone tool.
http://forum.xda-developers.com/general/help/root-downgrade-asus-me581cl-t3075678
If you crashed your tab totaly, you must put the 4 OS IFWI,dnx files like in the first post and then also boot.img, fastboot.img, recovery.img.
Uncheck only the ifwi folder, but select it before. So its possible to check blank phone and on demand flash.
Then click start flash and the files get loadet up. Now push vol+ and vol- togehter and plug in the device.
(device must be off before you plug it in. If not, press 10 sec the power button.)
The reest you can read in my thread. A downgrade from Android 5 to 4.4 is also possible.
Good luck

Guys, my ME176CX is shafted after completing the L update, it boots to the android with the red exclamation box...i can get past this by using the volume + & power and arrive in the recovery. from there I have tried the wipe cache/wipe userdata (doesn't help) also i tried to adb sideload one of the roms in the collection of roms thread. no good. ideas??

Any solution?
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Man I'm living in Venezuela a bad country to get damaged any gadget everything is 5 times expensive who your country and without any help in our soil by ASUS.

is this solution applicable to non-intel memopad? (e.g. me172V)

playinghier said:
is this solution applicable to non-intel memopad? (e.g. me172V)
Click to expand...
Click to collapse
No, this is very specific to the Intel chipset.