Related
Can not get into APX mode. Tried vol -/pwr, then vol + and wait for the droid with !, then vol+/pwr. Never brings up APX in device manager.
Same problem here. I have used NVflash a few weeks ago, so it did work at that moment, and I saw it in the Device Manager. But now I can't get my Transformer in APX anymore, nothing to see in the Device Manager. Somebody can help me with that?
Update :
- Find the Nvidia USB APX drivers (Google it!)
- Hold Volume+ AND Volume- AND Power at the same time.
This will bring the Transformer in APX mode.
It worked for me!
Pierre118 said:
Same problem here. I have used NVflash a few weeks ago, so it did work at that moment, and I saw it in the Device Manager. But now I can't get my Transformer in APX anymore, nothing to see in the Device Manager. Somebody can help me with that?
Update :
- Find the Nvidia USB APX drivers (Google it!)
- Hold Volume+ AND Volume- AND Power at the same time.
This will bring the Transformer in APX mode.
It worked for me!
Click to expand...
Click to collapse
how exactly did u install the apx drivers? sorry im a noob
NoctMonster said:
how exactly did u install the apx drivers? sorry im a noob
Click to expand...
Click to collapse
1. Plug the device on the computer
2. Put the device in APX
3. Go into device manager, find the NVIDIA thing
4. Manually install drivers with the nvflash.zip package
5. done.
i try to put the device in apx but nothing appears on the computer.
I had the same problem as you and all, but now i try to unbrick it and as soon as i connect the device to the computer, it turns on and stays stuck on the boot screen unless i turn it off. and if i try to turn it on in APX mode, nothing seems to happen, the device doesnt turn on and nothing appears on the computer.
After your TF is plugged into the PC...just keep holding down the power button until you are sure the TF is off....it took a LOOOONNNGGG time when mine was bootlooped and I had to try it several times but finally it happened.
then on your PC; open up device manager and tree-out the USB part to see if the NVidia drivers are showing...if not....no problem.
Hold down the power button and the volume+ button for at least 5 or 6 seconds...you should see your device manager refresh with the information.
When that happens; you are now in APX mode. if you accidentally hit the power/volume+ again...it will toggle you OUT of APX mode. No problem, just hit the buttons again and you are toggled back in.
Have patience...it will work.
i jusr got into apx mode thi morning you just need toue device manager and force install the usb drivers u download.
This post is really jst a testfor Tapa.
Sent from my Transformer TF101 using Tapatalk
detects usb and i can see it in device manager.
but when i go to start a download.bat file i get error
"failed exectuing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition <code:10> message: 0x3 <0x3>flags:0"
anyone else get this?
detects usb and i can see it in device manager.
but when i go to start a download.bat file i get error
"failed exectuing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition <code:10> message: 0x3 <0x3>flags:0"
anyone else get this?
Click to expand...
Click to collapse
Are you in apx mode with the nvidia apx drivers?
AustinMartin said:
Are you in apx mode with the nvidia apx drivers?
Click to expand...
Click to collapse
thats where im unsure. i use to get a little window pop-up saying im in boot mode.
now once i plug in the usb and the TF , i can see the "Nvidia boot.." in the device manager pop up. but when i go to my cmd prompt and start download.bat i get the errors, it looks like its gonna start but then the error pops up.
I've flashed twice before no problems, this time ...problems, the unit won't power on, or reboot.
did i brick it??
C:\tf101\nvflashtf>download
C:\tf101\nvflashtf>cd C:\tf101\nvflashtf\
C:\tf101\nvflashtf>"nvflash.exe" --bct transformer.bct --setbct --configfile fla
sh.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A
43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x027c1000419f6517
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
3 (0x3) flags: 0
Well, putting wthe firmware flash on me sd card and flashing the zip tseemed to work
One of my counterparts in Germany asked me to post it here. All credit goes to opec. This has been covered a few times, but I like the detailed scenario.
**************************
ERROR: Can´t installl hacked ICS Bootloader
I tried installing Hacked ICS Bootloader in Order to get Moscow Desire´s "Alexandra V a501 ICS 4.0.3 ver 1.4 Final" running on my a501.
The following ways of flashing could get the hacked bootloader on my a501:
"Afterota for A600/G100W" (http://forum.xda-developers.com/show....php?t=1675939),
"blackthund3r´s ATX flash tool A500APXFlash.exe" (see "Automated flashing tools" at http://forum.xda-developers.com/showthread.php?t=1622425")
"Manual flashing via nvflash" (see Manual flashing at http://forum.xda-developers.com/show....php?t=1622425)
Trying to flash with this tools always brought me to a Command Promt saying:
Nvflash started
[resume mode]
APX flash tool hang when it tired to Format Partition 4 etc.
and then doing nothing even if i let it stay for hours. No Information or Error so long.
When i tried flashing manualy (see link above)i finaly saw an error:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information
e: 14) message: nverror:0x4 (0x4) flags: 0
So it seemed however that the partition table on my a501 got messed up. Asking google for "failed executing command 25 NvError 0x120002" brought me to an answer "lcd047" posted on tegraowners (http://forum.tegraowners.com/viewtop...p=15285#p15331)
He desicrbes same problem with messed up partition table an restoring it with timmyDean´s root-3.2.1-V4.7z (http://forum.xda-developers.com/show...&postcount=1):
lcd047 wrote:
"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
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk (your sbk number after converting your UID number) 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.
And that worked for me. After flashing, my a501 did a automated reboot, i quickly killed the reboot by holding the Power Button (guessing killing the reboot is not realy necessary because the booting shouldn´t mess up the partition table again) and then brought the devive back to APX Mode (Holding Reset and Power for 3-4 sec. then releasing Power and after 1 second relesaing Reset).
Then i flashed the hacked bootloader via blackthund3rs APX flash tool (see link above).
Then i installed Alexandra V as Moscow Desire descirbes (see "To Install" at http://forum.xda-developers.com/show....php?t=1635577)
It took my 2 days of trial and error, but finaly give me a nice working Alexandra ROM on my a501!
Hope this helps people having the same issues.
Thanks to Moscow Desire, civato, blackthund3r, gersma, zeroNull, lcdß47, timmyDean
***************************************
Note from MD. You guys take note of this. Sometimes, when you get corrupted partition tables, you may have to go back to an HC stock bootloader to get them fixed. Of course there are other methods, but require some indepth knowledge, and this method most people can do easily.
MD
Borked Partition Table
Nice M...thanks for reposting this
will this work on a500
Moscow Desire said:
One of my counterparts in Germany asked me to post it here. All credit goes to opec. This has been covered a few times, but I like the detailed scenario.
Click to expand...
Click to collapse
After hours and hours, this right here was the solution I needed. Many, many thanks.
erndixon said:
After hours and hours, this right here was the solution I needed. Many, many thanks.
Click to expand...
Click to collapse
No problem. Sometimes things get buried back in the threads after awhile.
MD
Help
i'm use a501 3.2.1 stock HC and still unroot.
Now i wanna use alexV ROM, so i have flash ICS BL use blackthunder's flash tools and it's success, with V8a50pub recovery.
but my problem is:
1. still able to boot my stock HC ROM,
2. can't boot into recovery mode, it will display green robot with exclamation in its body
3. can i get guide to flash cwm recovery? i want use CWM-install-A500PubRecovery_v0.2.zip but its extension is .img and i dont know how to use it
sory if i asked noob question
thanks
Go on youtube and just search up how to root acer a500 , its the first video, steps are simple but i'm not too sure you can use pub recovery on honeycomb, after that use one of the flashing tools to install the hacked bootloader ( i prefer the apx flashtool, its fool proof pretty much with the sbk generator built in ) and download the v8 bootloader with your recovery choice and install it, there's even a guide on youtube on how to do it, hope it helps
Sent from my Iconia A501 using xda app-developers app
gigacats said:
i'm use a501 3.2.1 stock HC and still unroot.
Now i wanna use alexV ROM, so i have flash ICS BL use blackthunder's flash tools and it's success, with V8a50pub recovery.
but my problem is:
1. still able to boot my stock HC ROM,
2. can't boot into recovery mode, it will display green robot with exclamation in its body
3. can i get guide to flash cwm recovery? i want use CWM-install-A500PubRecovery_v0.2.zip but its extension is .img and i dont know how to use it
sory if i asked noob question
thanks
Click to expand...
Click to collapse
Please do not post duplicate issues in multiple threads. Please go to your original post.
MD
OK, sorry guys
Sent from my A501 using xda app-developers app
gigacats said:
OK, sorry guys
Sent from my A501 using xda app-developers app
Click to expand...
Click to collapse
No problem
Glad you got things running good. (in the other thread)
MD
Moscow Desire said:
One of my counterparts in Germany asked me to post it here. All credit goes to opec. This has been covered a few times, but I like the detailed scenario.
**************************
ERROR: Can´t installl hacked ICS Bootloader
I tried installing Hacked ICS Bootloader in Order to get Moscow Desire´s "Alexandra V a501 ICS 4.0.3 ver 1.4 Final" running on my a501.
The following ways of flashing could get the hacked bootloader on my a501:
"Afterota for A600/G100W" (http://forum.xda-developers.com/show....php?t=1675939),
"blackthund3r´s ATX flash tool A500APXFlash.exe" (see "Automated flashing tools" at http://forum.xda-developers.com/showthread.php?t=1622425")
"Manual flashing via nvflash" (see Manual flashing at http://forum.xda-developers.com/show....php?t=1622425)
Trying to flash with this tools always brought me to a Command Promt saying:
Nvflash started
[resume mode]
APX flash tool hang when it tired to Format Partition 4 etc.
and then doing nothing even if i let it stay for hours. No Information or Error so long.
When i tried flashing manualy (see link above)i finaly saw an error:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information
e: 14) message: nverror:0x4 (0x4) flags: 0
So it seemed however that the partition table on my a501 got messed up. Asking google for "failed executing command 25 NvError 0x120002" brought me to an answer "lcd047" posted on tegraowners (http://forum.tegraowners.com/viewtop...p=15285#p15331)
He desicrbes same problem with messed up partition table an restoring it with timmyDean´s root-3.2.1-V4.7z (http://forum.xda-developers.com/show...&postcount=1):
lcd047 wrote:
"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
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk (your sbk number after converting your UID number) 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.
And that worked for me. After flashing, my a501 did a automated reboot, i quickly killed the reboot by holding the Power Button (guessing killing the reboot is not realy necessary because the booting shouldn´t mess up the partition table again) and then brought the devive back to APX Mode (Holding Reset and Power for 3-4 sec. then releasing Power and after 1 second relesaing Reset).
Then i flashed the hacked bootloader via blackthund3rs APX flash tool (see link above).
Then i installed Alexandra V as Moscow Desire descirbes (see "To Install" at http://forum.xda-developers.com/show....php?t=1635577)
It took my 2 days of trial and error, but finaly give me a nice working Alexandra ROM on my a501!
Hope this helps people having the same issues.
Thanks to Moscow Desire, civato, blackthund3r, gersma, zeroNull, lcdß47, timmyDean
***************************************
Note from MD. You guys take note of this. Sometimes, when you get corrupted partition tables, you may have to go back to an HC stock bootloader to get them fixed. Of course there are other methods, but require some indepth knowledge, and this method most people can do easily.
MD
Click to expand...
Click to collapse
So, While this did not actually work in my case, it led me to do a search on "TegraOwners" for "Partition Table damaged" where I found "BadSector" which totally fixed my problem. So, A Hearty thanks to you Moscow Desire, as well as to BlackThund3r, for without his direction, I never would found your post either.
That being said, a big thanks to all the Dev's on this site, for without their hard work, there would be no reason for any of the fine information available on this site!
Hey i have a similar problem and i cant figure it out ..heres what i get:
bootloader downloaded successfulyy
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
bootloader status: failed to create the partition <code : 10> message: nverror:0x5
<0x1000005> flags: 0
What is the problem here ?
timmydeans toolkit doesnt work for me,bad sector also doesnt work, But i can see my device in safe and remove hardware...
moizsami said:
Hey i have a similar problem and i cant figure it out ..heres what i get:
bootloader downloaded successfulyy
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
bootloader status: failed to create the partition <code : 10> message: nverror:0x5
<0x1000005> flags: 0
What is the problem here ?
timmydeans toolkit doesnt work for me,bad sector also doesnt work, But i can see my device in safe and remove hardware...
Click to expand...
Click to collapse
If these 2 tools "don't work" there are only 2 possibilities
a) you're not doing things correctly
b) your tab has a faulty memory chip and needs a replacement motherboard
Acer a500 stock on acer logo-dead andriod red triangle
Moscow Desire said:
No problem. Sometimes things get buried back in the threads after awhile.
MD
Click to expand...
Click to collapse
Hello Sir
I have seen lots of post from you regarding Hacer a500 tab, I am not a geek nor a tech, but I do have this tab stock on Hacer logo, and when I tried to hard reset it takes me to dead andriod, please help me out here, with steps to bring back my tab back to life..thanks
Fixed!!! Thanks to Moscow Desire & BlackThund3r, for the leads to the final solution, and obviously bsg19071979 for the actual solution. The partition table was invalid. I ended up using "BadSector" (Had to follow multiple threads on XDA then over to TegraOwners, Then finally back here, to this post "http://forum.xda-developers.com/showthread.php?t=1691729&page=3"
bsg19071979 said:
can be fully corrected sector:
1. Download h??p://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
2. Run a501 A.bat
3. run recovery 1.7.3 -> "Mount and Storage" -> "Format /system"(better than twice).
4. Run a501 B.bat
Click to expand...
Click to collapse
So can someone tell me what i can do to fix this thing?
I was running Stock ICS 4.03, havn't cared much for it, & wanted to go back to Stock HC 3.2, so tried flashing "Acer_A500_7.006.03_COM_GEN1" from A500 Dev forum. (followed directions, but it would just give the android, on his back, with red exclamation point, then re-boot back into 4.03.)
Read somewhere that I should try using the update.zip file from within the archive directly (rather than renaming "SD_Acer_A500_7.006.03_COM_GEN1.zip" to "update.zip"
Tried that, seemed to work fine, then screen went blank when update was nearly finished, and now can only boot tablet in APX mode. (Lost recovery??)
I have tried replacing lost recovery using APX_v0.4A-flashTool-500Manager1.0.2, The manager says it detects the tablet in APX Mode, but when I try logs, it either just stalls at "Waiting for tablet" or says "No device connected"
Tried to install "EUUs_SBK_Acer_A500_1.016.05_COM_GEN1" (HC 3.01) and it will actually put the tablet into download mode, but will go no further. (At least I can see that the tablet's screen is capable of doing something, as opposed to just being black!)
Any Idea's what will get this tablet going again?
EDIT: Using APXFlash tool, for some reason, on 2 different computers, the text on the buttons doesn't show up, so, The only button I could see was "Dump My BCT", when I clicked it, I would get the BCT file not found message.
I found a tutorial (that showed where all the buttons were & wgat they say, & just used the default BCT. Still cannot get past the "Flashing Bootloader (EBT) stage two - uploading image..." message... nothing is happening, just stalled. Still need some direction...
Thanks
In short, being on stock ICS you also had the ICS bootloader and cannot just flash back to any earlier version. Most likely you now have several pieces of different ROMs embedded on your tab. Take a look at TimmyDean's excellent tutorial which will take you back to v3.2.1 and allow OTA updating: http://forum.xda-developers.com/showthread.php?t=1516012
Goodluck!
amphi66 said:
In short, being on stock ICS you also had the ICS bootloader and cannot just flash back to any earlier version. Most likely you now have several pieces of different ROMs embedded on your tab. Take a look at TimmyDean's excellent tutorial which will take you back to v3.2.1 and allow OTA updating: http://forum.xda-developers.com/showthread.php?t=1516012
Goodluck!
Click to expand...
Click to collapse
So, this is pretty much the same thing I was trying with the EUU file from Acer, and produces the same result. It goes as far as saying "Upgrade is under way. It may take more than 10 minutes." Then it appears to start flashing, (The progress bar starts to move) then errors out with the message "We are sorry! The upgrade process failed. Please follow the instructions for recovery" ( So, what exactly are the instructions for recovery?)
A note maybe worth mentioning, this Tab is stuck in APX mode, so when I get the prompt to enable USB Debugging, I am not aware of a way to enable it, also understood we didn't need that as we are using APX mode?
As well, I know I have the right CPUID, as I looked it up before starting the flashing process, and have just now verified it by liiking with USBDeview.
I am using 0380620044400497.
So, after conneccting the tablet, but before running the flash update, I opened a command window, & ran ADB devices. Got the following output:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
Notice there are no attached devices, yet As I mentioned earlier, I do not know of any way to turn on USB de-bugging, and I am in APX mode, so I shouldn't expect to see a device through ADB, Correct?
So, is this going to work at all trying to load a bootloader/recovery if I cannot turn on USB de-bugging?
Sorry, again, Any thoughts?
Danny2 said:
So, this is pretty much the same thing I was trying with the EUU file from Acer, and produces the same result. It goes as far as saying "Upgrade is under way. It may take more than 10 minutes." Then it appears to start flashing, (The progress bar starts to move) then errors out with the message "We are sorry! The upgrade process failed. Please follow the instructions for recovery" ( So, what exactly are the instructions for recovery?)
A note maybe worth mentioning, this Tab is stuck in APX mode, so when I get the prompt to enable USB Debugging, I am not aware of a way to enable it, also understood we didn't need that as we are using APX mode?
As well, I know I have the right CPUID, as I looked it up before starting the flashing process, and have just now verified it by liiking with USBDeview.
I am using 0380620044400497.
So, after conneccting the tablet, but before running the flash update, I opened a command window, & ran ADB devices. Got the following output:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
Notice there are no attached devices, yet As I mentioned earlier, I do not know of any way to turn on USB de-bugging, and I am in APX mode, so I shouldn't expect to see a device through ADB, Correct?
So, is this going to work at all trying to load a bootloader/recovery if I cannot turn on USB de-bugging?
Sorry, again, Any thoughts?
Click to expand...
Click to collapse
Edit: I just ran this again, tried loading an ICS bootloader this time, & noticed there is an error message earlier on in the execution that I previously missed. Please see attached Screen1 (screenshot)
Error is right after bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14)
message: nverror:0x4 (ox4) flags: 0
So, I used BlackThund3r's NVFlash, running in a command window, & captured the screen output in the attached .jpg. NVFlash starts, Attempts to format partition 4, then errors out with the message
"Command Execution failed cmd 13, error 0x12002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
NvFlash started
[resume mode]
Thats it, she hangs here & refuses to go further.
This mean anything to anyone?
Danny2 said:
Edit: I just ran this again, tried loading an ICS bootloader this time, & noticed there is an error message earlier on in the execution that I previously missed. Please see attached Screen1 (screenshot)
Error is right after bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14)
message: nverror:0x4 (ox4) flags: 0
So, I used BlackThund3r's NVFlash, running in a command window, & captured the screen output in the attached .jpg. NVFlash starts, Attempts to format partition 4, then errors out with the message
"Command Execution failed cmd 13, error 0x12002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
NvFlash started
[resume mode]
Thats it, she hangs here & refuses to go further.
This mean anything to anyone?
Click to expand...
Click to collapse
Fixed!!! Thanks to Moscow Desire & BlackThund3r for the leads to the final solution. The partition table was invalid. I ended up using "BadSector" (Had to follow multiple threads on XDA then over to TegraOwners, Then finally back here, to this post "http://forum.xda-developers.com/showthread.php?t=1691729&page=3")
I have an ancient stock HC 3.2 and decided it would be nice to update. Forgetting completely about the fact that I had the ancient honeycomb bootloader as well, I loaded up an ICS update.zip and flashed. Now I'm stuck with a broken tab that displays Boot verification failed on startup. I have access to APX mode, but my computer does not seem to be cooperating with the drivers.
What to do?
Same kind of Problem
I have an A500 with OTA 4.01 o it.
I rooted it successively
Added bootloader ICS - worked fine - could see loader on reboot - used afterOTA
Backuped rom onto SD
Went in to recovery mode and installed JellyBean X rom - I wiped every thing including cache's
Installed fine, went to reboot and nothing.
Power light goes on and that's it.
I have tried several utilties but most need the computer to see A500 as a device or say failed, or do nothing
The "ejectAPX" shows on the eject hardware ion, and ACER USB drivers show up in device manager
I have tried resets, volume buttons etc - no go
The A500 screen did come up with "Acer Download Mode", but that as far as I get.
Any detailed help would be appreciated!
Win7 computer
David
Update
I do have mu cpuid and SBK #
I tried Blackthund3r APX flash tool, using A500_A501_ICS_V7_bootloader
BThdr says APX detected
Tab enters in to download mode with ACER logo on screen,
stage one ok
stage 2 just hangs at 3 quaters the way - I waited over 5 minutes
I have tried the following command with theresults after:
nvflash --bct flash.bct --setbct --odm
data 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0x04FF
1E00 0xABE0D706 0xEBAA3304 0x20502103 --go
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x5 (0x1000005) flags: 0
used babsector and it worked
got back into recovery mode
Been there
Been there (I think I have a messed up reset button actually), but the only thing I can get my tablet back to life on is timmyDean´s root-3.2.1-V4.7z find in the forums extract the files then in the image folder you will find nvflash run the flash.bat but it reformats your flash etc. and brings you back to HC 3.2.1.
I have been through all of the tools and this was the only one that boots to android when its finish, which I need since I think my reset is stuck.
I needed to create ubuntu usb stick and run eppe's code to get my CPUID might help with usb connection issues to use similar too.
Then I was working with nvflash --read and the v8 bootloader stuff (since before my tablet soft bricked I was OTA ICS full stock), and was able to read off my user data with nvflash partition before I did the flashing. That way I saved all of my tablet pictures and video etc. (loop mounted the image read from that partition in ubuntu and was able to pull out any of my user data).
To get my data I used V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip see more at http://forum.xda-developers.com/showthread.php?t=1622425
Then I did:
nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata --sbk %MYSBK% --sync
nvflash --resume --read 2 mybct.bct
nvflash --resume --getbct
nvflash --resume --getpartitiontable mypartitiontable.txt
nvflash --resume --read 13 UDA_raw3.img
I wish I would have backed up all of my partitions that way but I think I will get the replacement part first and then rebuilt the tablet.
Hope that helps
Thanks
What I ended up doing was creating and formatting partitions with Babsector - as opposed to Badsector, which didn't work
The used A500 APXflash
Then installed Jellytime X
The Jellytime was not working properly so I used root-3.2.1 V4 to take it back to 3.21, then OTA to 4.0.1
Root it again and then I stopped.. think I will stay with this rom, until 4.2 is super stable.
I think I did this procedure about 4 times in 2 days, as every rom that I tried either trashed the partition or boot loader, or didn't run properly.
I was lucky as I used afterOTA as part of flash the bootloader, and it saved a txt file with all my cpu info...
David_h99 said:
Thanks
What I ended up doing was creating and formatting partitions with Babsector - as opposed to Badsector, which didn't work
Click to expand...
Click to collapse
What do you means by that? what is this babsector?
HOw do you creating and formatting partitions with Babsector?
I had try badsector and it doesn't work so if you have another way to do it i am very interested!
thanks
you can get babsector here
narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
Make sure your computer sees tablet in APX mode, and the driver in device manager is the ACER USB driver
Then read info on how to run babsector
I have flashed a lot of stuff, but this Iconia is driving me CRAZY.
For starters, the tablet will only boot into APX mode when you turn it on. Blank screen, but the power light is white/blue.
I DO have the SBK, which I grabbed through Ubuntu.
I try using the blackthund3r utility. It detects it in APX mode fine and pops it into the bootloader, but after that it gets stuck. This is at "Flashing Bootloader (EBT) stage two - uploading image..." The command prompt just displays Nvflash started [resume mode].
When I try running v8.bat manually from the command prompt, I usually get a lot of failed command errors which come at different points at times.
The other day I miraculously used the blackthund3r utility and handpicked some bootloader and system files and got it to boot back into Android, but when it tried updating OTA it got stuck on reboot saying the "blob update failed." Now I am back to the start of this post.
I've updated the drivers a few times and also installed the Android SDK. Everything is up to date.
If anyone has any idea what might be holding me up I could use the help. My girlfriend is mad now that I have re-destroyed her tablet after bringing it back to life and I need to get it back to her.
Have you tried using Ubuntu to run the nvflash commands, some have had luck with it where windows won't....
Srbeens guide (its stickied in the general forum) to recovering sbk via Ubuntu also has a few steps in running the nvflash commands directly from Timmy deans v4 EUU which is used to repair partitions, there might be something there u can use...
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
Have you tried using Ubuntu to run the nvflash commands, some have had luck with it where windows won't....
Srbeens guide (its stickied in the general forum) to recovering sbk via Ubuntu also has a few steps in running the nvflash commands directly from Timmy deans v4 EUU which is used to repair partitions, there might be something there u can use...
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
This is working for me up to the same point. I'm getting a "sync failed (bad data)" error and I can't format any partitions.
erndixon said:
This is working for me up to the same point. I'm getting a "sync failed (bad data)" error and I can't format any partitions.
Click to expand...
Click to collapse
k, hopefully its just your partitions messed up and not the dreaded hardware failure... you got couple options left and both of these will work from apx mode
timydeans v4 an EUU based tool which will give you a pre-rooted stock HC3.2 and cwm installed too - it will wipe everything
heres how user lcd047 went about it on his a501 but will work for a500
lcd047 wrote:
"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
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk (your sbk number after converting your UID number) 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.
And that worked for me. After flashing, my a501 did a automated reboot, i quickly killed the reboot by holding the Power Button (guessing killing the reboot is not realy necessary because the booting shouldn´t mess up the partition table again) and then brought the devive back to APX Mode (Holding Reset and Power for 3-4 sec. then releasing Power and after 1 second relesaing Reset).
Then i flashed the hacked bootloader via blackthund3rs APX flash tool (see link above).
Then i installed Alexandra V as Moscow Desire descirbes (see "To Install" at http://forum.xda-developers.com/show....php?t=1635577)
It took my 2 days of trial and error, but finaly give me a nice working Alexandra ROM on my a501!
Click to expand...
Click to collapse
The other way is by using the "babsector.rar" from the russian forums -
you can download it http://forum.xda-developers.com/showthread.php?t=2049778, theres a couple of good links in post 13 of that same thread on how to use it correctly
You don't say which rom was on the tab previously - so once the partitions are repaired and you've run the unlocked bootloader flash you'll need to immediately boot to recovery and flash an ics/jb rom ...do not try booting into android until you have done this....else you'll need to do everything all over again!!!
dibb_nz said:
k, hopefully its just your partitions messed up and not the dreaded hardware failure... you got couple options left and both of these will work from apx mode
Click to expand...
Click to collapse
Very helpful threads. Exactly the problems I was facing. Using the babsector a501a commands, I am getting a "create failed: (bad data)" and "bootloader status: fatal failure to read/write to mass storage" errors right after it creates the partitions. I am guessing that it is probably faulty memory then and it just can't write to it no matter if I am doing it correctly or not. Thanks for all your help.
erndixon said:
I am guessing that it is probably faulty memory then and it just can't write to it no matter if I am doing it correctly or not. Thanks for all your help.
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?p=49951540