Database Users

recovery verified failed?

ok so rooted and loaded the 1.031.00_ww_gen1 for my tab.
installed everything cool nice looking no screen or wifi probs at all.
ive since decided i would like to try flexreaper as ive heard it has the ring and faceunlock working,
so i check my recovery is working so i can flash a new update.zip
when i try to enter recovery i get this message:
rasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
if gone to acer recovery installer and tried installing the cwm1.3.4 and 1.7 both by thro2002ro but to no avail still the same error,
i also installed clockworkmod and tried installing the recovery there and rebooting .....to the same error ....can anyone help?

chisme said:
ok so rooted and loaded the 1.031.00_ww_gen1 for my tab.
everything can be
installed everything cool nice looking no screen or wifi probs at all.
ive since decided i would like to try flexreaper as ive heard it has the ring and faceunlock working,
so i check my recovery is working so i can flash a new update.zip
when i try to enter recovery i get this message:
rasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
if gone to acer recovery installer and tried installing the cwm1.3.4 and 1.7 both by thro2002ro but to no avail still the same error,
i also installed clockworkmod and tried installing the recovery there and rebooting .....to the same error ....can anyone help?
Click to expand...
Click to collapse
For those who need the solution :
I presume this should work to downgrade from any ICS builds as well .
just fixed that problem been at it for almost 10 hours to find a correct solution
get your correct UID . In my case there some weird problem UID wasnt diplaying it all (insted i was seeing serial number even with adb devices..) ... use backup_tool to get UID works greats hands down !
get it from this link
Click to download
if that doesntt work look across the forum on how to find your UID
once you have that get EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
get it from this link Click to Download
dont plug in iconia tab let it search for firmware about 5 min eventually it will ask you if you want to restore it say yes and input your CPUID (same as UID) Then put the TAB Into APX MODE
Hold power +reset button for 3 sec then let it power go one sec later let reset go you can use board pin
{
"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"
}
and plug in your usb cable .
This process may take upto 10 mins ... or less
sit back it will be restored back to stock ! HC 3.01
thats it
nvflash utility did not work for me !

chisme said:
ok so rooted and loaded the 1.031.00_ww_gen1 for my tab.
installed everything cool nice looking no screen or wifi probs at all.
ive since decided i would like to try flexreaper as ive heard it has the ring and faceunlock working,
so i check my recovery is working so i can flash a new update.zip
when i try to enter recovery i get this message:
rasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
if gone to acer recovery installer and tried installing the cwm1.3.4 and 1.7 both by thro2002ro but to no avail still the same error,
i also installed clockworkmod and tried installing the recovery there and rebooting .....to the same error ....can anyone help?
Click to expand...
Click to collapse
Read , read, if you installed the leak or received the OTA from Acer to ICS you need to unlock your boot loader and install custom recovery.
There are at least 2 threads in dev section about it.

civato said:
Read , read, if you installed the leak or received the OTA from Acer to ICS you need to unlock your boot loader and install custom recovery.
There are at least 2 threads in dev section about it.
Click to expand...
Click to collapse
The problem is all xda developers are working under M$ Windows programs. Where are the MacOsX dev?
I'm waiting for a good soul to develop a MicroSD or Mac ICS bootloader unlocker...
Sent from my A500 using Tapatalk 2

civato said:
Read , read, if you installed the leak or received the OTA from Acer to ICS you need to unlock your boot loader and install custom recovery.
There are at least 2 threads in dev section about it.
Click to expand...
Click to collapse
I have the same problem but I think Im in the correct path but I cant seem to go to download mode. Im stuck in "entering acer download mode" now I dont know what to do. I.ve read somewhere here in the forums that it has something to do with the windows version. I did it in windows xp. Help pls

ebonikeys said:
I have the same problem but I think Im in the correct path but I cant seem to go to download mode. Im stuck in "entering acer download mode" now I dont know what to do. I.ve read somewhere here in the forums that it has something to do with the windows version. I did it in windows xp. Help pls
Click to expand...
Click to collapse
did u try what i posted above

tawhid111 said:
did u try what i posted above
Click to expand...
Click to collapse
Not yet sir.. I'll try it on monday after reformating my laptop.. thx

ebonikeys said:
I have the same problem but I think Im in the correct path but I cant seem to go to download mode. Im stuck in "entering acer download mode" now I dont know what to do. I.ve read somewhere here in the forums that it has something to do with the windows version. I did it in windows xp. Help pls
Click to expand...
Click to collapse
You are in the download mode = entering download mode. Its the same thing.
Just run the command.

Recovery verified failed ...
Hi all,
I have the same problem
On the splash screen:
Booting recovery kernel image
(IN RED) Recovery verified failed ...
i tried different things like the post before, but nothing change.
Nothing important on my a500, i would like to reinit the system and install FLEXREAPER-R14-1.033.00_1.031.00-ICS.
Thank you for your help
Gill

Yesssssss
Good news!!
Succeed with blackthund3r_A500_APX_Flash_Tool_v0.3-V3BL-CWM
and
first recovery_thor17_403... but black screen...
so with V3-APX-PACKAGES

Hmm nothing has worked for me. Have tried several things. Sometimes the Acer Utility says bad cpu id, then it says its trying to install. Tried ApX Flash but my tab does nothing. I get a power light and that is it. Well maybe another day or two I will figure it out.

blueis300 said:
Hmm nothing has worked for me. Have tried several things. Sometimes the Acer Utility says bad cpu id,
Click to expand...
Click to collapse
Not sure what u mean by Acer utility, but the first thing u need is ya cpuid - the flash wont work without it....
I get a power light and that is it. Well maybe another day or two I will figure it out.
Click to expand...
Click to collapse
the 2nd thing you'll need is the Acer drivers, run the setup.exe. turnntab off and get into apx with button press, then check device manager
that u got acer boot recovery drivers installed under USB controllers, if they not there then check adb interface for apx drivers, as long as
u have one or other u shud be all good

I tried the PBJ upgrade and my CPUID said it was fine but sat at install and never did anything. Tried the APX FLASH and it says complete but still cant do anything.
Says all drivers are installed. It lists apx mode but when I do ADB it doesnt list any devices. Also never lists anything in device manager.

blueis300 said:
I tried the PBJ upgrade and my CPUID said it was fine but sat at install and never did anything. Tried the APX FLASH and it says complete but still cant do anything.
Says all drivers are installed. It lists apx mode but when I do ADB it doesnt list any devices. Also never lists anything in device manager.
Click to expand...
Click to collapse
with the euu . did u keep tab disconnected till u got the 'cant detect yr iconia tab screen" then button combo into apex mode?

There seem to be some problem with (64 bit os) try using 32 bit windows....
-Tested over windows 7 32 bit no problem
-Tested over windows 7 64 bit no problem
Double check your cpuid in the folder the file called CPUID.txt inside EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 folder
make sure it match or else youll get invalid cpuid error
make sure your cpuid in in cpuid.txt is written like this 0x0YOUROWNCPUIDGOES HERE example 0x037c624942c11318
and also when entering it in PBJ20upgrade add a 0
example 037c624942c11318
if you need more help pm me

have you tried the new apx flash updater and a500 manager from blackthunder? it lets you go into recovery from your pc and you can flash a new recovery and bootloader ...very easily i think your on the locked bootloader thats why you cant get into recovery like i was,. i installed a PATCHED UNLOCKED bootloader and now everything is cool
its in civato's guide page you can use this guide to flash a unlocked one, (v4+)
http://forum.xda-developers.com/showthread.php?t=1622425
make sure u have a backup and your cpuid!!!!
Optional A500MANAGER
What does it do :
· One-click APX Mode entry
· One-click Recovery Mode entry
· One-click fastboot entry for patched bootloaders
· Instant logcat viewer
· Instant dmesg Viewer
· Function which dumps the dmesg to a text file on the desktop
· Serial number extraction to make SBK calculation exponentially easier
· Links to ICS Root, A500 APX Flash Tool and two download links (Acer and my mirror) for USB Drivers
· Shows what mode the tablet is in at the bottom

Spaces?
Does the SBK extracted from the CPUID need to be entered without spaces?
chismay said:
have you tried the new apx flash updater and a500 manager from blackthunder? it lets you go into recovery from your pc and you can flash a new recovery and bootloader ...very easily i think your on the locked bootloader thats why you cant get into recovery like i was,. i installed a PATCHED UNLOCKED bootloader and now everything is cool
its in civato's guide page you can use this guide to flash a unlocked one, (v4+)
http://forum.xda-developers.com/showthread.php?t=1622425
make sure u have a backup and your cpuid!!!!
Optional A500MANAGER
What does it do :
· One-click APX Mode entry
· One-click Recovery Mode entry
· One-click fastboot entry for patched bootloaders
· Instant logcat viewer
· Instant dmesg Viewer
· Function which dumps the dmesg to a text file on the desktop
· Serial number extraction to make SBK calculation exponentially easier
· Links to ICS Root, A500 APX Flash Tool and two download links (Acer and my mirror) for USB Drivers
· Shows what mode the tablet is in at the bottom
Click to expand...
Click to collapse

4 sets of numbers beginning with 0x a space only between each set....make sense?
Sent from my GT-I9300 using Tapatalk 2

Link
please add new link to Ubuntu image . I can't download it

recovery verified failed FIX explained
ggt91160 said:
Good news!!
Succeed with blackthund3r_A500_APX_Flash_Tool_v0.3-V3BL-CWM
and
first recovery_thor17_403... but black screen...
so with V3-APX-PACKAGES
Click to expand...
Click to collapse
*******************
What he implies is:
1. He used the Manual Modem to Goto APX First Black screen. [ instructions can be got from: blackthund3r_A500_APX_Flash_Tool_v0.3-V3BL-CWM tool under Manual Mode]
2. Then he Used/Resumed with the blackthund3r_A500_APX_Flash_Tool_v0.3-V3BL-CWM, tool under the Automatic Enter APX Mode, till he got APX logo.
3. Went to Bundles and selected recovery_thor There is Option 17. This is First Step when RUNNING blackthund3r_A500_APX_Flash_Tool_v0.3-V3BL-CWM.
4. Then finally Recovery is flashed Perfectly. So u can install any custom ROM.

[Q] Can't get into recovery, can't get into bootloader download, am I bricked?

I am currently stuck without being able to get into bootloader or recovery. I have a rom that is currently working for about 10 minutes at a time (FLEXREAPER-RF1_rv3-CUSTOM-ICS for HC).
I was orignially on the HC bootloader, using CWM v5. I then used the file found here http://skrilax.droid-developers.org/a500/nvflash/images/a500_a501_bootloaders_apx_ics_v7.zip and installed it from CWM. It looked like it installed just fine.
The problem is that now, when I try to get into recovery, I just see this screen
{
"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"
}
Using Afterota, I was able to get my CPUID and the rest
Tablet Serial : 11920475015
Tablet Cpuid : 011920475015
Tablet Sbk : 0x6AA1E101 0x69CCD301 0x991D3003 0x07580203
Bootloader : 0.03.0X-HC
Android Build : FLEXREAPER-RF1_rv3_Acer_AV041_A500_1.031_033_041.00_CUS_WW_GEN1
But when I try to use blackthund3r or Timmydean, my tablet goes into APX just fine (with the screen blank and the power button white), but none of the tools can get my tablet to go into bootloader download mode.
I am totally stuck, and have no idea what to do. I have tried following instructions for http://forum.xda-developers.com/showthread.php?t=1622425 and http://forum.xda-developers.com/showthread.php?t=1516012, but neither of them can get me into bootloader. When I use the TimmyDean tool and put my tablet into APX manually, I get to the screen where I put in the CPUID, but i tells me that the CPUID I am entering is invalid. I've checked using multiple methods, and I always get my CPUID back at 011920475015. Is this a valid CPUID?
I am going crazy here.

I have the same problem,
i cant boot into recovery mode.
and i cant get it to boot into APX mode i just get a black screen.
and can not find any wifi networks wont even search.
Would love some help.

MrR0ng said:
I am currently stuck without being able to get into bootloader or recovery. I have a rom that is currently working for about 10 minutes at a time (FLEXREAPER-RF1_rv3-CUSTOM-ICS for HC).
I was orignially on the HC bootloader, using CWM v5. I then used the file found here http://skrilax.droid-developers.org/a500/nvflash/images/a500_a501_bootloaders_apx_ics_v7.zip and installed it from CWM. It looked like it installed just fine.
The problem is that now, when I try to get into recovery, I just see this screen
Using Afterota, I was able to get my CPUID and the rest
Tablet Serial : 11920475015
Tablet Cpuid : 011920475015
Tablet Sbk : 0x6AA1E101 0x69CCD301 0x991D3003 0x07580203
Bootloader : 0.03.0X-HC
Android Build : FLEXREAPER-RF1_rv3_Acer_AV041_A500_1.031_033_041.00_CUS_WW_GEN1
But when I try to use blackthund3r or Timmydean, my tablet goes into APX just fine (with the screen blank and the power button white), but none of the tools can get my tablet to go into bootloader download mode.
I am totally stuck, and have no idea what to do. I have tried following instructions for http://forum.xda-developers.com/showthread.php?t=1622425 and http://forum.xda-developers.com/showthread.php?t=1516012, but neither of them can get me into bootloader. When I use the TimmyDean tool and put my tablet into APX manually, I get to the screen where I put in the CPUID, but i tells me that the CPUID I am entering is invalid. I've checked using multiple methods, and I always get my CPUID back at 011920475015. Is this a valid CPUID?
I am going crazy here.
Click to expand...
Click to collapse
Well, first off, your UID is fine. For ICS that is. TimmyDeans tool requires an HC UID. So you can't use it in TimmyDeans. Theoretically the SBK is the same for both in a lot of cases, just the UID number changes. But you have your UID so all is not lost.
Probably just the recovery image got toasted. Also, there are reports that a small percentage of tablets don't get along well with certain version recoveries. No know reason for this.
Can you boot into fastboot mode? (vol+ amd PWR) if so, you can try to fastboot a new recovery image through the android SDK. You can access fastboot through the Android SDK/Platform-tools folder on your PC (open a command window there. Put the tab in fastboot mode, plug in to PC, make sure windows recognizes it as fastboot device.
fastboot flash recovery recovery.img
(recovery.img being the name of the recovery you wish to use)
or
You can try the manual method of NVFlash. Personally I use one of the older tools from BlackThund3r to do this. It's not listed anymore, so if you need it, I'll have to package it in a zip file and post it.
Anyhow, those are a couple of methods to use.
MD

Hi
i need more info on how to fastboot through the Android SDK/Platform-tools.
i have downloaded the android sdk but look like just a package DOWNLOADER developer.android.com/sdk/index.html
cant use the other methods ( NVFlash BlackThund3r) it just hang on the black screen

First off, you have to download and install the Android SDK. When finished, it should install (under Win7) C:\program files (x86)\android\android-sdk
When you install it. make sure you right mouse click and "install as administrator". A good practice to get into when installing things.
Everything you need to know about installing the SDK (including platform tools) can be found here;
http://developer.android.com/sdk/index.html
In there is a folder \Platform-tools. This is where you find Adb And Fastboot. If you hold SHIFT + Right mouse click, you can open a command window there. (win7)
But this is all dependent on whether you installed the correct drivers. Some say Acer Drivers will work. Personally I prefer to use the Google USB Drivers for Android. (google USB Drivers Android).
How do you know your drivers work? Easy, put your tab in APX mode, display will be black but you see the PWR button lit.
Check Windows Device manager with the tablet plugged in. Should list an APX device or Recovery Device. If it doesn't, you need to install the drivers manually by selecting the folder where you extracted the google drivers to. Ignore any incompatibility message.
Whether APX Mode, or Fastboot, Windows should load the specific drivers. If Device Manager doesn't reflect this, then you need to sort it out.
If you want to reflash something using Fastboot, like a boot.img or recovery.img, place the .img file in the same directory as the fastboot command. In most cases with the newer version SDK, it will be in Platform-tools.
The more common fastboot commands can be found in this thread, which I posted the command for recovery.img earlier.
http://forum.xda-developers.com/showthread.php?t=1619913

When i open fastboot.exe the window opens for 1 second and then closes again. am i missing something else.
i am starting to think i may have bricked my tab.

xgutterratx said:
When i open fastboot.exe the window opens for 1 second and then closes again. am i missing something else.
i am starting to think i may have bricked my tab.
Click to expand...
Click to collapse
Dude, you can't "double click" fastboot.exe. Don't work that way.
As I posted earlier, open a CMD window in the platform-tools folder on your PC.
Then put your tab in fastboot mode (vol+ and PWR) till your tab says "fastboot mode". Then plug it in, and check Windows loads the fastboot drivers. (you should see it loading drivers in the windows taskbar).
After that, then you can run the fastboot command to install a recovery image. "IN THE CMD WINDOW"
If you don't feel comfortable doing this, then don't. We can find some other method that may be more comfortable for you.
I can zip up the app that I use, and maybe you should try that first. It uses NVFlash. As I really don't want you to bork things up anymore than they are now. Especially if you're not comfortable with fastboot (you can really bork things up with this).
Give me a little bit, and I'll post something for you guys to try.

Now, this is the tool I generally use. It requires the tab be in APX mode.
http://www.4shared.com/zip/ycbdG0qY/Ver4_BL_and_CWM.html
Extract the zip to your PC. It contains ver4 unlocked bootloader and CWM. I know this combo works.
Put your tab in APX mode. Connect to PC and verify windows loads the correct APX drivers. Then unplug the tab.
Start the app by "right mouse clicking A500APXFLASH.exe, and select "run as administrator".
Plug your APX Mode Tab into the USB when the app tells you. ( i think you have to do this first, or the app will do it for you. Can't remember, an don't feel like flashing another bootloader to find out)
Get your SBK number (usually I have this in notepad so I can copy and paste it).
Usually I select Manual as I only want to select the Ver4 unlocked.bin and the Thor Recovery and none of the other stuff.
Then I select Automatic when prompted. And follow the prompts when asked.
NOTE: After plugging in your APX mode tab, you may still see a message at the bottom of the app stating "No APX Devices Detected" Ignore this and click Next.
This was a small bug.
Also, sometimes on Win7 you may get a windows error box. Ignore this also and close it.
DO NOT UNPLUG the tab until the apps says complete. The whole process takes about 5 minutes or so to complete.
Then it's safe to unplug the tab. Shut it down, and reboot to recovery to make sure it works.
Also something I want to mention. If you guys installed OTA's, make sure you delete the "boot to recovery.p" in your tabs System file as states in Civato's thread. Otherwise, when you boot normally, it will delete your Custom Recovery, and you'll be doing this again.
MD

Hi MD,
thx for trying to help out here, much appreciated.
I've just tried your steps, the apx flash utility stays put at "stage two - uploading image..." and the nvflash cmd prompt stays at "[resume mode]". Waited for 10 minutes...nothing.
Is there anything else to try ?
ta,
T

Tommmii said:
Hi MD,
thx for trying to help out here, much appreciated.
I've just tried your steps, the apx flash utility stays put at "stage two - uploading image..." and the nvflash cmd prompt stays at "[resume mode]". Waited for 10 minutes...nothing.
Is there anything else to try ?
ta,
T
Click to expand...
Click to collapse
Well, there's always some tricks to try.
Did you use the Google drivers and verify you tab is registered in Windows Device Manage as APX device or Recovery Device?
To manually go to APX, shut down tab. Put a paper clip in the reset button, and hold. With your other hand, press and hold PWR for 3 seconds, release PWR, then about 1 second later remove paper clip. You should have black display with pwr lite on. Plug in tab and check device manager.

apx flashutil claims "Acer APX Mode device detected"
device mgr shows "Acer USB Boot-recovery driver" under "Universal Serial Bus controllers"

Tommmii said:
apx flashutil claims "Acer APX Mode device detected"
device mgr shows "Acer USB Boot-recovery driver" under "Universal Serial Bus controllers"
Click to expand...
Click to collapse
OK, that's good (I had to double check with mine)
Now, did you run the package I posted earlier? Reason is, it uses a .bin file instead of an apx package.
Also, as I am dealing with several other folks, do you have a bootloader when you boot? Like Skirlax_CZ blah blah blah version xxxx?

I tried the bootloader_ics_v4.bin and the recovery you supplied.
There's no mention of a bootloader on the A501
Supposition : if my cpuid were wrong, would apxflash throw an error?

Tommmii said:
I tried the bootloader_ics_v4.bin and the recovery you supplied.
There's no mention of a bootloader on the A501
Supposition : if my cpuid were wrong, would apxflash throw an error?
Click to expand...
Click to collapse
@Tommmii, Which tablet do you have? a 500 0r 501?
Generally, if the UID/Sbk were wrong, the apps would throw an error.

A501
I'm beginning to suspect my UID (037c700140c0941) could be wrong.
If so, i'll be stuck up a creek without a paddle

Tommmii said:
A501
I'm beginning to suspect my UID (037c700140c0941) could be wrong.
If so, i'll be stuck up a creek without a paddle
Click to expand...
Click to collapse
Looks like an HC UID. But it doesn't matter. If this was the UID you pulled under HC. Basically, ICS will change the UID. As a matter of fact, it may change it several times when you install ISC Roms. What shouldn't change, in most cases, is the SBK. Usually the SBK is the same under HC and ICS. At least with my tab it was.
Naw,,,, you still got a paddle.
I got a 501 also.
So tell me, do you have any bootloader at all when you try to boot normally?
Also, you didn't tell me what happened when you tried running the app I posted with the Ver4 unlocked bootloader. Did it work? (don't worry if it said 500 or 501, can fix that later)
Attached is my 501 ver4.bin Throw it in the same directory as the tool I posted.

Power On gives the white Acer logo, followed by a bootlogo ("android" metallic type letters) From memmory that could be the stock HC bootlogo. Stuck in a loop though...
VolDown & PWR gives the HC Andy with an exclamation triangle dangling above his head.
edit : just tried renaming SD_Acer_A501_1.309.02_COM_GEN1 to update.zip , it updated the rom but no boot same as above
edit2 : didn't see your attachement...just tried it, stuck at [resume mode] in the nvflash debug window

You rock so hard!
The super ridiculous fastboot method worked PERFECT for me. Took me all of 2 minutes. I was pulling my hair out. Thanks so much for the AMAZING support. Love the android community.
Moscow Desire said:
Well, first off, your UID is fine. For ICS that is. TimmyDeans tool requires an HC UID. So you can't use it in TimmyDeans. Theoretically the SBK is the same for both in a lot of cases, just the UID number changes. But you have your UID so all is not lost.
Probably just the recovery image got toasted. Also, there are reports that a small percentage of tablets don't get along well with certain version recoveries. No know reason for this.
Can you boot into fastboot mode? (vol+ amd PWR) if so, you can try to fastboot a new recovery image through the android SDK. You can access fastboot through the Android SDK/Platform-tools folder on your PC (open a command window there. Put the tab in fastboot mode, plug in to PC, make sure windows recognizes it as fastboot device.
fastboot flash recovery recovery.img
(recovery.img being the name of the recovery you wish to use)
or
You can try the manual method of NVFlash. Personally I use one of the older tools from BlackThund3r to do this. It's not listed anymore, so if you need it, I'll have to package it in a zip file and post it.
Anyhow, those are a couple of methods to use.
MD
Click to expand...
Click to collapse

Tommmii said:
Power On gives the white Acer logo, followed by a bootlogo ("android" metallic type letters) From memmory that could be the stock HC bootlogo. Stuck in a loop though...
VolDown & PWR gives the HC Andy with an exclamation triangle dangling above his head.
edit : just tried renaming SD_Acer_A501_1.309.02_COM_GEN1 to update.zip , it updated the rom but no boot same as above
edit2 : didn't see your attachement...just tried it, stuck at [resume mode] in the nvflash debug window
Click to expand...
Click to collapse
Ewwww.... right now, I am at a loss for a plan of attack.
After running the rom, and it updating ok, the Acer with the metallic logo's tells me it's a modified bootloader (I saw this in the earlier unlocked bootloader logos. Ver3 I believe. However, this ver3 I don't believe had flashboot capability.
Ver3 is ok. You can run it. Why we can't get it updated to ver4 right now, is beyond me.
Hmmm.... will have to come up with a different plan.
One thing puzzles me, why when you ran that .... "update", it didn;t put a stock bootloader on it.
Ewwww... too bad you are not near Moscow. I would love to get my hands on it.

could i run nvflash manually when connected in APX mode ?
Perhaps it would show more debug info then...?

[Q] My tablet is completely f***ed

I already had a problem where I was stuck in a bootloop and was told to flash the stock image (see here for previous issue : http://forum.xda-developers.com/showthread.php?t=2783631 ). I did this and tried it with the Nexus root toolkit with no wipe mode enabled and when I tried turning on the nexus I get this very annoying looping screen which shows the word google in the middle and the green start button at the top pointing towards the power button. every time I press the power button the green sign reapears and nothing happens. when I do this from the fastboot screen (using cmd on PC) I see a little message in the upper left corner saying "booting failed". I cannot seem to get the adb working at all which is a real problem and I am not sure if this tablet is reparable but I need someones help urgently http://forum.xda-developers.com/images/smilies/mad.gif
{
"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"
}

Gloftking said:
I already had a problem where I was stuck in a bootloop and was told to flash the stock image (see here for previous issue : http://forum.xda-developers.com/showthread.php?t=2783631 ). I did this and tried it with the Nexus root toolkit with no wipe mode enabled and when I tried turning on the nexus I get this very annoying looping screen which shows the word google in the middle and the green start button at the top pointing towards the power button. every time I press the power button the green sign reapears and nothing happens. when I do this from the fastboot screen (using cmd on PC) I see a little message in the upper left corner saying "booting failed". I cannot seem to get the adb working at all which is a real problem and I am not sure if this tablet is reparable but I need someones help urgently http://forum.xda-developers.com/images/smilies/mad.gif
Click to expand...
Click to collapse
Have you tried to flash the stock Android images using fastboot?
Note: Following command WILL WIPE your device.
Code:
fastboot -w update image-nakasi-ktu84p.zip
For Nexus 7 (2012 WiFi): https://developers.google.com/android/nexus/images#nakasiktu84p
For Nexus 7 (2012 3G): https://developers.google.com/android/nexus/images#nakasigktu84p
deltatux

I just tried that
deltatux said:
Have you tried to flash the stock Android images using fastboot?
Note: Following command WILL WIPE your device.
Code:
fastboot -w update image-nakasi-ktu84p.zip
For Nexus 7 (2012 WiFi): https://developers.google.com/android/nexus/images#nakasiktu84p
For Nexus 7 (2012 3G): https://developers.google.com/android/nexus/images#nakasigktu84p
deltatux
Click to expand...
Click to collapse
I tried what you said and when I entered the code in the cmd I got the following
"archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >" (without quotes)
and it just hangs here. Any idea what the problem is?

deltatux said:
Have you tried to flash the stock Android images using fastboot?
Note: Following command WILL WIPE your device.
Code:
fastboot -w update image-nakasi-ktu84p.zip
For Nexus 7 (2012 WiFi): https://developers.google.com/android/nexus/images#nakasiktu84p
For Nexus 7 (2012 3G): https://developers.google.com/android/nexus/images#nakasigktu84p
deltatux
Click to expand...
Click to collapse
for some reason whenever I try to execute your code I get
"archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >" (without quotes)
and it just hangs there
I appear to have bricked my nexus 7 as the tablet is not starting at all and I can recall that at some stage I accidentally used the fastboot command "fastboot erase bootloader" (not sure if it actually did that)
any ideas how to reverse this?
BTW in device manager the tablet shows up as UNKNOWN Device

Gloftking said:
for some reason whenever I try to execute your code I get
"archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >" (without quotes)
and it just hangs there
I appear to have bricked my nexus 7 as the tablet is not starting at all and I can recall that at some stage I accidentally used the fastboot command "fastboot erase bootloader" (not sure if it actually did that)
any ideas how to reverse this?
BTW in device manager the tablet shows up as UNKNOWN Device
Click to expand...
Click to collapse
If you erased the bootloader without flashing another one back in, you just bricked your device. The only course of action to save it is to do an nvflash but that would have required you to back up the nvflash blob before this incident. If all else fails, your tablet's a dud.
I would recommend either replacing your entire tablet or buy a replacement board on eBay and replace the motherboard yourself and then it will run like new.
deltatux

If you entered that command, your device is hardbricked and the only thing you can do about is to send it to Asus/Google for RMA.

Erovia said:
If you entered that command, your device is hardbricked and the only thing you can do about is to send it to Asus/Google for RMA.
Click to expand...
Click to collapse
I doubt Google/ASUS will repair it and if they do, it'll likely cost you as much as a new tablet. I still stick to what I said and either get a new tablet or replace the motherboard yourself.
deltatux

That is so annoying
I was trying to flash another bootloader called ("bootloader-grouper-4.23.img") but I think some error occurred in the command prompt and I am very surprised it actually let me do that unknowingly.
Is there another boot loader inside the nexus 7 that allows this procedure of swapping bootloaders to take place or is there any kind of hard reset button inside the nexus (I don't care what happens to my data on it)

deltatux said:
If you erased the bootloader without flashing another one back in, you just bricked your device. The only course of action to save it is to do an nvflash but that would have required you to back up the nvflash blob before this incident. If all else fails, your tablet's a dud.
I would recommend either replacing your entire tablet or buy a replacement board on eBay and replace the motherboard yourself and then it will run like new.
deltatux
Click to expand...
Click to collapse
how on earth are you meant to use the nvflash software and does it definitely require a blob file.
BTW I do seem to recall that I saw a "writing to bootloader message" in cmd before it became inoprable. does that mean there is any better chance of this thing being revived?

Gloftking said:
how on earth are you meant to use the nvflash software and does it definitely require a blob file.
BTW I do seem to recall that I saw a "writing to bootloader message" in cmd before it became inoprable. does that mean there is any better chance of this thing being revived?
Click to expand...
Click to collapse
nvflash is meant to be a debugging software as an absolute last resort to restore a Tegra based device. More on nvflash here:
http://forum.xda-developers.com/wiki/Nvflash
The blobs are tied to your device because nvflash works pretty much at hardware level, so without your own blobs, it's nearly impossible to recover. Here's the procedure to extract the blob before brick: http://www.xda-developers.com/andro...nexus-7-and-other-asus-tablets-with-flatline/
As for "writing to bootloader", if you can't access the bootloader now, it may be because you flashed the wrong bootloader (likely from the 3G variant of the Nexus 7 instead of WiFi-only or vice versa). Unless you can somehow gain access to fastboot, you'll need to recover via nvflash.
Without the blobs backed up, you'll probably be better off replacing the Nexus 7 motherboard with a working OS and all.
deltatux

cant believe this
deltatux said:
nvflash is meant to be a debugging software as an absolute last resort to restore a Tegra based device. More on nvflash here:
http://forum.xda-developers.com/wiki/Nvflash
The blobs are tied to your device because nvflash works pretty much at hardware level, so without your own blobs, it's nearly impossible to recover. Here's the procedure to extract the blob before brick: http://www.xda-developers.com/andro...nexus-7-and-other-asus-tablets-with-flatline/
As for "writing to bootloader", if you can't access the bootloader now, it may be because you flashed the wrong bootloader (likely from the 3G variant of the Nexus 7 instead of WiFi-only or vice versa). Unless you can somehow gain access to fastboot, you'll need to recover via nvflash.
Without the blobs backed up, you'll probably be better off replacing the Nexus 7 motherboard with a working OS and all.
deltatux
Click to expand...
Click to collapse
are you people seriously saying that one command sent electronically through a wire can physically break a device to the extent that it is 100% impossible to repair electronically (if there are no blob files made in advance to preform a recovery). It just makes me wonder how could such a command exist (who on earth would use it). as fer as replacing the motherboard is concerned my n7 is a 32 gb meaning it will be hard to find an affordable replacement.
BTW I am pretty sure the bootloader was for the wifi version (my n7 is wifi) and I am also suspicious that the nexus toolkit had bricked my tablet because I tried the temporary boot feature and I saw in the corner something like "downloading bootloader img". At some other point in time I used the dreaded command (either before or after). I cant remember which one of these these operations had caused the brick because it was only later I noticed the tablet was in a Sleep of Death http://forum.xda-developers.com/images/smilies/mad.gif
thanks for the advice anyway

deltatux said:
The blobs are tied to your device because nvflash works pretty much at hardware level, so without your own blobs, it's nearly impossible to recover. Here's the procedure to extract the blob before brick: http://www.xda-developers.com/andro...nexus-7-and-other-asus-tablets-with-flatline/
Click to expand...
Click to collapse
Deltatux can you tell me pls if I can use this guide with KK 4.4.4?
Sorry for asking here but I can't post yet in the developers threads.

Just a potential fix proposition
deltatux said:
Have you tried to flash the stock Android images using fastboot?
Note: Following command WILL WIPE your device.
Code:
fastboot -w update image-nakasi-ktu84p.zip
For Nexus 7 (2012 WiFi): https://developers.google.com/android/nexus/images#nakasiktu84p
For Nexus 7 (2012 3G): https://developers.google.com/android/nexus/images#nakasigktu84p
deltatux
Click to expand...
Click to collapse
deltatux said:
If you erased the bootloader without flashing another one back in, you just bricked your device. The only course of action to save it is to do an nvflash but that would have required you to back up the nvflash blob before this incident. If all else fails, your tablet's a dud.
I would recommend either replacing your entire tablet or buy a replacement board on eBay and replace the motherboard yourself and then it will run like new.
deltatux
Click to expand...
Click to collapse
Erovia said:
If you entered that command, your device is hardbricked and the only thing you can do about is to send it to Asus/Google for RMA.
Click to expand...
Click to collapse
guys I have managed to get my nexus 7 into APX mode by pressing the buttons on the side however I am not sure where to go from here. Every time I try to update driver in device manager I get the error "There is no driver selected for the device information set or element" and as a result cannot update it to the asus apx mode interface thing that nvflash provided. if there is any other possible course of action I can take from here that does not involve physical repair then please do let me know after all I Only plan to replace the motherboard as a last resort option

To be able to recover from APX mode, you'd have to have a backup of your tablet. Without a proper backup, you can't do much. Also, there is no way of using someone else's backup, since every motherboard has a different signature key.

Could someone confirm if my assumptions are correct?
Mine is stuck in APX mode therefore if I send it to ASUS to repair my data will lost? If the motherboard is replaced my data is lost? In its current state my data on it is unrecoverable?
Just wondering if it's safe to sell for spares, seeing that I've got no way to wipe it.

hold on a minute
I thought NVFlash could somehow be used to flash a completely new bootloader with a 'new' crypto-signature as that is the sort of thing that can be achieved with the nexus 5 and various other non Tegra 3 devices. What is the big deal with the n7 and besides how can you expect anyone to use a system like that (blobing in advance) when perhaps 90% (or more) of people who run into this problem have never herd of such a system and would then be completely SOL.
Also is there any way in which one could get hold of the internal SD card practically so it can be taken out and surgically re-implanted into the new motherboard or vice-versa with the bootloader to prevent me from having to purchase another 32GB logicboard (such a waste).

nihil sleighride said:
Could someone confirm if my assumptions are correct?
Mine is stuck in APX mode therefore if I send it to ASUS to repair my data will lost? If the motherboard is replaced my data is lost? In its current state my data on it is unrecoverable?
Just wondering if it's safe to sell for spares, seeing that I've got no way to wipe it.
Click to expand...
Click to collapse
Oh and yes all data will be lost if they replace the motherboard as they will throw away the old one or re-use it and re-solder etc. However if you're lucky they will use special tools to flash the software back into the main board although this is almost guaranteed to format everything on the internal SD unless you can detach it somehow beforehand (still waiting on an answer for that one) or ask the data recovery people to rescue the data when you get it back (that's only if they did not throw it away) or even tell the asus repair service not to delete the data if possible. The main issue is when you flash a tablet or phone you will be re-installing the operating system and the internal SD is part of that operating system so there is almost no way to save the data on it in just a soft-bricked state never mind a hard-bricked one.
And yes most of your assumptions would match that of my own right now. having said the above there is probably no way an end user could get data off it if you sold it as a spare because there would be no way to access it unless they managed to escape the apx mode and used some kind of file recovery program via the adb which is why I do then again say don't give up hope just yet (I am not an expert)
BTW how did you get into APX mode because if you did what I did (erased the bootloader via fastboot) then you are as of now SOL (awaiting further confirmation of that) whilst on the other hand if it was a charging issue or anything else then I would not recommend any of the above suggestions. There are numerous stories of people being stuck in apx mode and got out again after some time and if you did not modify your tablet before this happened then all your data will still be their
there seems to be too many APX 'ed devices right now and I just wonder what Google must be thinking about this and if they will do something or not

Mine was rooted and had been pretty much updated when a new Paranoid Android was released. I flashed a new release, which took way longer then normal to update. All seemed OK but a few hours later, it completely locked, so I attempted to reboot and that's when it got stuck in APX.

RMAed $165 HELP!
@deltatux, et al. - so the cable came out when I was trying to flash bootloader (which was taking FOREVER... very unusual) in my daughter's tablet and I had to send it in for RMA. They want $165 for the motherboard ALONE. I've asked them to ship it back to me.
If I get a new motherboard off like eBay is it just a simple swap? I'm just checking I have built many PCs over the year and think I can handle the swap...

Guys have any of you seen this
This is a known story of a guy who actually managed to escape the SOL situation we are all in (bricked by entering "fastboot erase bootloader" in cmd) and I am not sure why it happened
http://androidforums.com/nexus-7-ge...icked-bootloader-erased-help.html#post5289634
post number 15 by rootbrain
does this mean the n7 2012 has a backup mechanism of some sort or did he just install his own on the bootloader? http://forum.xda-developers.com/images/smilies/fingers-crossed.gif

[Q] - Help with seemingly perma-bricked LG G2 (VS980)

Hi all -
Thanks for checking in on my tale of woe. The summary is that I have seemingly nuked my partitions on my LG G2 (Verizon Edition VS980) so that nothing happens when I try to power the device on (literally nothing, no logo, no screen backlight turning on, etc.). In Windows, with some coaxing, the device will appear as a QHSUSB_BULK device (with a yellow exclamation point in Device Manager, and even when I boot into Linux to look at the partitions, they aren't visible.
How I got here:
I was happily running XDABBEB VS980 2.3.0 from http://forum.xda-developers.com/showthread.php?t=2715408 with a few Xposed framework tweaks. Great ROM.
I dirty-flashed XDABBEB's VS982.5 v1.0.0 from http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551 to have a look at the G3 interface. I did a Nandroid backup first, like any good crack flasher
I neglected to read the step in the VS982.5 thread about the fact that this ROM was bumped. I still am not sure what that means.
I played with VS982.5 for a bit, and it didn't really seem like I'd want to use it long term. Also, some of the LG apps didn't seem to work on first try, not sure if that was an additional flash required. (QRemote was what I ran into). Anyway, I thought I'd go back to VS980 2.3.0 for then by just restoring my Nandroid.
Booted into TWRP to restore the Nandroid. It did it's thing.
Upon reboot, the device showed the LG Logo and showed a Security Error in the upper left-hand corner, and sat there briefly, then shut off the screen. (Sorry, I don't remember the precise text, it was in small white letters, several lines' worth of text).
I tried rebooting a couple of different ways, and eventually gave up and followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142
From a Linux Live CD (Specifically an old Hiren's 15.2), I thought I'd followed the instructions correctly. The partitions did show up correctly under /dev/sdk1.../dev/sdk36 or whatever. I did the dd as prescribed with the files.
Then I tried to reboot, and here we are. Apparent hard-brick.
What I've tried since the Linux fiasco.
Rebooting many different ways. (Recovery mode, etc.)
Going back to stock with kdz and tot methods, following this: http://forum.xda-developers.com/showthread.php?t=2432476 . The device is not recognized, probably because the normal USB driver won't load.
Checking to see if it'd show up in adb and fastboot commandline interfaces. No, of course.
Booting back into Linux to try the dd again. No luck. The 30+ partitions don't show up under /dev
Letting it charge, thinking the battery may have died. It has been plugged in long enough that it should be 100%. (I can't tell when the device is on or off any more, because there are literally no indications.). This doesn't seem to have made any difference
Holding the Down button and plugging in the USB port gives the QHSUSB_BULK (Code 28) error in Windows, so at least it's doing something... but not much.
Ideally, of course, I'd like to restore the partitions, get my nandroid written back to the device, and carry on with life. Failing that, I'd like to get the nandroid off so I don't have to spend hours setting up another G2. My mistake for keeping the nandroid on the device - I've never bricked a device this badly, and it's always been recoverable with some googling!
Help!

Mark-7 said:
Hi all -
Thanks for checking in on my tale of woe. The summary is that I have seemingly nuked my partitions on my LG G2 (Verizon Edition VS980) so that nothing happens when I try to power the device on (literally nothing, no logo, no screen backlight turning on, etc.). In Windows, with some coaxing, the device will appear as a QHSUSB_BULK device (with a yellow exclamation point in Device Manager, and even when I boot into Linux to look at the partitions, they aren't visible.
How I got here:
I was happily running XDABBEB VS980 2.3.0 from http://forum.xda-developers.com/showthread.php?t=2715408 with a few Xposed framework tweaks. Great ROM.
I dirty-flashed XDABBEB's VS982.5 v1.0.0 from http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551 to have a look at the G3 interface. I did a Nandroid backup first, like any good crack flasher
I neglected to read the bottom of the VS982.5 thread about the fact that this ROM was bumped. I still am not sure what that means.
I played with VS982.5 for a bit, and it didn't really seem like I'd want to use it long term. Also, some of the LG apps didn't seem to work on first try, not sure if that was an additional flash required. (QRemote was what I ran into). Anyway, I thought I'd go back to VS980 2.3.0 for then by just restoring my Nandroid.
Booted into TWRP to restore the Nandroid. It did it's thing.
Upon reboot, the device showed the LG Logo and showed a Security Error in the upper left-hand corner, and sat there briefly, then shut off the screen. (Sorry, I don't remember the precise text, it was in small white letters, several lines' worth of text).
I tried rebooting a couple of different ways, and eventually gave up and followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142
From a Linux Live CD (Specifically an old Hiren's 15.2), I thought I'd followed the instructions correctly. The partitions did show up correctly under /dev/sdk1.../dev/sdk36 or whatever. I did the dd as prescribed with the files.
Then I tried to reboot, and here we are. Apparent hard-brick.
What I've tried since the Linux fiasco.
Rebooting many different ways. (Recovery mode, etc.)
Going back to stock with kdz and tot methods, following this: http://forum.xda-developers.com/showthread.php?t=2432476 . The device is not recognized, probably because the normal USB driver won't load.
Checking to see if it'd show up in adb and fastboot commandline interfaces. No, of course.
Booting back into Linux to try the dd again. No luck. The 30+ partitions don't show up under /dev
Letting it charge, thinking the battery may have died. It has been plugged in long enough that it should be 100%. (I can't tell when the device is on or off any more, because there are literally no indications.). This doesn't seem to have made any difference
Holding the Down button and plugging in the USB port gives the QHSUSB_BULK (Code 28) error in Windows, so at least it's doing something... but not much.
Ideally, of course, I'd like to restore the partitions, get my nandroid written back to the device, and carry on with life. Failing that, I'd like to get the nandroid off so I don't have to spend hours setting up another G2. My mistake for keeping the nandroid on the device - I've never bricked a device this badly, and it's always been recoverable with some googling!
Help!
Click to expand...
Click to collapse
sorry have you fixed your phone yet?? if not install vmware and slax. using this linux environment helped me. then you can follow the instructions on
http://forum.xda-developers.com/showthread.php?t=2582142

v.konvict said:
sorry have you fixed your phone yet?? if not install vmware and slax. using this linux environment helped me. then you can follow the instructions on
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Thanks for your note - I tried that in step 7 above. (VMware + Ubuntu).

Mark-7 said:
Thanks for your note - I tried that in step 7 above. (VMware + Ubuntu).
Click to expand...
Click to collapse
so you tried with slax?? not ubuntu??

v.konvict said:
sorry have you fixed your phone yet?? if not install vmware and slax. using this linux environment helped me. then you can follow the instructions on
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
v.konvict said:
so you tried with slax?? not ubuntu??
Click to expand...
Click to collapse
Hmm, no, I didn't. I'll try with Slax. It didn't occur to me that the linux distro would make a difference.

Mark-7 said:
Hmm, no, I didn't. I'll try with Slax. It didn't occur to me that the linux distro would make a difference.
Click to expand...
Click to collapse
okay give it a try and tell me how it goes

Okay, I did that (this is a really cool distro, I didn't know about it).
But, sadly, still no partitions showing up.
{
"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"
}

Mark-7 said:
Okay, I did that (this is a really cool distro, I didn't know about it).
But, sadly, still no partitions showing up.
Click to expand...
Click to collapse
on your bottom right look for qhulb usb device and connect it to slax. am sure you can see many partitions on your windows. if you connect it to slax they will disappear from windows and then you continuw with ls /dev/sd*

Yes, I did that (that's what I was trying to show with the little thing down in the lower right - the QHUSB_BULK thing is actually showing up as a USB device rather than flash storage).
I had the SDK1-36 partitions showing up in Linux before - and then I must've done something wrong in the thread that we refer to up above...I did all the DD steps and I think I wiped all the partitions somehow, as even though the QHUSB_BULK device is connect to the VM, it's not giving me the partitions (or asking me about all the auto-mount failures).

Mark-7 said:
Yes, I did that (that's what I was trying to show with the little thing down in the lower right - the QHUSB_BULK thing is actually showing up as a USB device rather than flash storage).
I had the SDK1-36 partitions showing up in Linux before - and then I must've done something wrong in the thread that we refer to up above...I did all the DD steps and I think I wiped all the partitions somehow, as even though the QHUSB_BULK device is connect to the VM, it's not giving me the partitions (or asking me about all the auto-mount failures).
Click to expand...
Click to collapse
in slax it doesnt give the automount failures. okay can you tell me what was happen when you connect your phone to windows no the vmware. if it shows many partitions in windows then you are still okay

Nope, the partitions do not show up in Windows any more either.
(I know what it looked like when it did. Now, it is not recognized as a disk device at all).

Mark-7 said:
Nope, the partitions do not show up in Windows any more either.
(I know what it looked like when it did. Now, it is not recognized as a disk device at all).
Click to expand...
Click to collapse
okay have you tried the tot method. i know your phone isnt showing anything but its worth a try i guess.

v.konvict said:
okay have you tried the tot method. i know your phone isnt showing anything but its worth a try i guess.
Click to expand...
Click to collapse
Thanks so much for trying. Yes, I've tried recovering with both the KDZ and TOT attempts.
TOT method appears to fire up correctly (after the megalock weirdness), but because the device won't mount or load drivers, nothing happens after I hit Normal Flash.

Mark-7 said:
Thanks so much for trying. Yes, I've tried recovering with both the KDZ and TOT attempts.
TOT method appears to fire up correctly (after the megalock weirdness), but because the device won't mount or load drivers, nothing happens after I hit Normal Flash.
Click to expand...
Click to collapse
Sorry bro am out of ideas

I thought I'd update this story to let people know how it ended.
I ended up ordering another LG G2, but saw this thread late one night:
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
I had to make a Windows XP VM to get it running with the HS-USB 9008 mode, but after I did that, I kept getting the "device was not found in dload trying flash programmer" error.
I ended up contacting one of the guys in that thread who did a teamviewer session with some custom build of the b2b support tool, and he was able to unbrick it. He does charge for the service though.
It wiped the phone, but it is back in service now under XDABBEB's 2.3.0.
So now I have a spare LG G2 on its way.
Thanks, v.konvict for all the ideas.

another brick in the wall...
Mark-7 said:
Nope, the partitions do not show up in Windows any more either.
(I know what it looked like when it did. Now, it is not recognized as a disk device at all).
Click to expand...
Click to collapse
I dont think you nuked your partitions in Linux.
I HAVE THE EXACT SAME SCENARIO. Going from xdabbebs vs985 ROM back to the vs980 2.3.0 ROM, clean fash, except I didn't Nandroid it I simply flashed the rom back in under TWRP .
The security error thing came up RIGHT AFTER THAT. And I couldn't get it gone. And finally ended up same as you, computer could see the phone but no partifions. I think that just happen because the battery was dying. You just got yours to what's his name before the battery totally failed :victory:
There something in the hardware didn't like it when we reverted to the former ROM.

I don't think it was a hardware issue - my guess is that it had something to do with the fact that the G3 ROM is a bumped ROM, and I didn't know the difference.
Perhaps if I'd reverted back to 24a bootstack before flashing, all would be good.
But I don't know, and am a bit gunshy to play more.

Mark-7 said:
But I don't know, and am a bit gunshy to play more.
Click to expand...
Click to collapse
I can totally relate. I'm thinking I'll have to replace either the main board or the battery on this unit.

I think mine recharged OK, even in the mostly-bricked state. When plugged into the USB port, something seemed to still be happening (recognized as a driverless USB device)

[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.