Hey guys and gals,
I have an Iconia a500 that has been rooted since I got it last December. It has run various 3.2 and 3.2.1 HC roms, then the ICS leaks, and most recently Skrillax's V* bootloader, with Civato's Re-Flexx roms. Just yesterday, I had a random reboot, and then another, but on the second one it wouldn't get past the "loading kernel image" screen. I've tried to EEU back to Vache's 3.0.1 then flash an official rom to get it back on to the official upgrade path, and have been successful, except when going to ICS. Once the official ICS install completes, it hangs on the Acer logo, requiring another EUU. I've also tried Blacktundr's APX tool at that point to go to V8+thor recovery, then flashing an ICS rom. same result.."loading kernel image".
The tablet is fine, as long as I stick with HC roms, and the HC bootloader. It will upgrade-path sucessfully thru 3.2.1, and even run Timmydean's rooted3.2.1, then an old HC rom of my choice. Just NO ICS .
Ideas? Maybe a partition error?
I believe there is a .zip or .rar file called Babsector with 2 .bat files in it that will help me if anyone has them?
ok so i found the babsector files, tried them.. Now i still cannot flash the bootloader with the APX tool.. tab runs fine with timmydean's rooted 3.2.1, but fails to OTA to ICS even. Ideas?
AtariDroid said:
ok so i found the babsector files, tried them.. Now i still cannot flash the bootloader with the APX tool.. tab runs fine with timmydean's rooted 3.2.1, but fails to OTA to ICS even. Ideas?
Click to expand...
Click to collapse
where does it fail on the bl flash, what error do u get?
failing to ota to ics from HC - go to thread how to revert to stock the easy way by jdgM3NT4L - there's a non-US update.zip i posted that worked for me. but until we figure out why u u can't flash the bl, you're stuck with stock.
Sent from my GT-I9300 using Tapatalk 2
Thanks for responding! it is good to hear from a voice of experience on the subject. I will copy/paste my results of various tries asap. I was able to flash the V8 bootloader a couple days ago. But since then i've tried a few methods to get to ics.. Including the Babsector .bats, maunually trying timmydean's and vache's EUUs, all fail at formatting BCT. The APX tools hang at uploading image(bootloader). I'm thinking i may have to do the Rawread technique to map out bad sectors, and place an FCK partition where they reside.... BUT i've not found exact instructions on how to get that to work yet. so for it seems to just hang, but iim sure i'm doing the rawread command wrong. win7x64 by the way.
I have of course uninstalled/ reinstalled and tried both driver versions out there also.
Any tips are greatly appreciated.
Here is a try with babsector's first .bat:
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Next try.. same .bat:
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
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
As i mentioned earlier, I'm guessing I have the failed EEMC memory problem. hoping to remap the partitions. Going to try to put an FCK first and see what happens.
After trying an FCK partition of 1000000 sectors in size..
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: FCK
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 15 FCK please wait.. done!
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 GP1 please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 MSC please wait.. done!
Formatting partition 11 FLX please wait.. done!
Formatting partition 12 AKB please wait.. done!
Formatting partition 13 UDA please wait.. done!
Formatting partition 14 GPT please wait.. done!
done!
sending file: bootloader_v8_green.bin
| 1191932/1191932 bytes sent
bootloader_v8_green.bin sent successfully
sending file: recovery.img
/ 5242880/5242880 bytes sent
recovery.img sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x8 (0x11000008)
flags: 0
Well.. this is definitely uncool.. I made a .bat that loads the bootloader from any upgrade package and runs the flash.cfg from it.. I've tried timmydean's V4, vache's 3.0.1, the babsector cfg's, and even the CES picasso version with it's huge bootloader. ALL are a no-go. My only chance seems to be to map out bad sectors with the Rawread command and try to put a dummy partition on top of them.. IF said partition doesn't fail on format.
Can someone explain the process on how to figure out what sectors are bad with the rawread comand?
I did get an error 12 a couple times before it even tried formatting on a few of my over 50 attempts.
Also.. if i am really screwed here.. anyone know of any broken a500's around that I may be able to buy a motherboard from?
Thanks everyone for your help so far. Without the countless threads I have gone through to learn what I have, I would still be sitting here scratching my head even more lol.
I'm not much help sorry, i guess you've read what there is regarding this.
there is a few posts from user 'yaworski' who managed to fix this in one of the old bootloader threads, thats all i can offer at this point. you might wanna pm him? or maybe blackthund3r or eppeP. wish u all the luck in getting fixed.
rgds dibb
Sent from my GT-I9300 using Tapatalk 2
Actually you have been a great help, as you have been a large part of many of the threads I have read on the subject
I see this post: http://forum.xda-developers.com/showpost.php?p=27456113&postcount=22... but I did not succeed in finding where they actually went through the process.
I've tried running the rawdeviceread command to find the bad sector/s, but I think i am loading the RAM bootloader(Timmydean's) wrong. I have been using the a501 A.bat to load the bootloader, then killing it where it waits for the bootloader to initilize. From there I open another command prompt window, but nvflash hangs at every command. I'm not very well versed in Nvflash, as I only know what I have seen here and at Tegraowners.
Can someone tell me how to load the bootloader without having it execute any commands? That way I can run the rawdeviceread command and maybe figure out how to go from there. I also need to know if there is a way to create a partition without formatting it(I think that is automatic?). That way I can create the dummy FCK partition over the bad sector/s and skip it so the others can create/format successfully.
Re: [INFO/DEV] A500 ICS Bootloader (plus unlocked patched version)
oops just annihilated my post...and links to couple early bootloader threads, useful info really bct error....
apxflash tool allows you to dump your bct so you can nvflash - as long as your tab enters download mode and the apx usb device is showing up, go ahead and flash it -
Theres lots of info in some of the older bootloader threads http://forum.xda-developers.com/showthread.php?t=1514951)??? well worth a read
sp3dev said:
I have uploaded the archive with nvflash and some instructions on using it with A500. This is only intended for hardcore geeks who know how ARM boots. Be careful - while you can't really brick tegra2 (since it has a minimal usb-capable bootloader in the OTP area), you can screw up things and it will be quite hard to force the tablet to boot in some cases due to stupid security checks.
You can use this to download any bootloader/recovery/linux you want. That will help us with porting uboot. Someone may even write an automated tool for reflashing bootloaders and unbricking tablets..
http://www.mediafire.com/?pp97x9aahs58hzp
Let me just copy-paste the README from the archive here.
1. First, generate your sbk with http://vache-android.com/v1/index.php?site=sbk
2. Then, get a hold of mmcblk0 start sectors (at least 4KB) and copy it to mmcblk0_start
3. run the ./rip_bct.sh script and supply it with your SBK to rip BCT (boot config table. contains ram timings among other things)
4. run ./download.sh to connect nvflash to iconia (do it in APX mode). Note that you also need to supply your SBK here, but not as a long single number, but as it is displayed on the website
5. You can now play with nvflash - for example, read partitions, partition table and write your own flash_ic.cfg with partition layout
6. If you flash linux/recovery, make sure to update the magic values (like itsmagic does).
To do it, first download the 12th partition (AKB)
then, in the akb.bin, at address 0x84, replace 4 16-byte entries with the same pattern
"00 FB 30 94 99 01 4F 97 2E 4C 2B A5 18 6B DD 06"
ok, you need to patch the file once and can use it in further flashing. Just upload it to the device (like sign.sh does)
POTENTIAL PITFALLS. Listen up, I ain't gonna help you if you eff up here.
1. You must use BCT from your device Otherwise, the bootloader will not boot.
You will still be able to use NVFLASH, but until you dump your own BCT and use it
with NVFLASH, the device will not be booting again
2. If you use the ./iconia_boot.bin that differs from the bootloader on your
device, the device will get stuck in the APX mode after a reboot. If you do it,
flash the new ./iconia_boot.bin to the device (to the partition 4).
.
Click to expand...
Click to collapse
Sent from my GT-I9300 using Tapatalk 2
Ok hoping to try again tonight. thanks for your help!
Related
So yesterday I was playing Angry Birds space on my tablet running AOKP Milestone 6 with TWRP. The game started lagging like no other so I exited the game, Got to my home screen and it was locked up. Hit the reset button and it wasn't booting, stating that was loading the kernel, I loaded into TWRP, and it wasn't seeing anything on my SD Card so I decied to just do a rollback using Timmydeans root 3.2.1 downgrade, and whenever I run the EUU i just stops during it the restore
http://forum.xda-developers.com/showthread.php?t=1307539
I tried running this in the Image folder in the timmydean download
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0xD19C1E00 0x68B3E601 0x87FA0203 0x45312103 --go
I get the following message
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c620442e124d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) me
ssage: nverror:0x42008 (0x6042008) flags: 0
I also tried running the V8-UNL-ICS-HC-bootloader-MULTI-cwm with v8.bat and v8.bat
I need help on getting me back working.
Theres something bad with the partitions on your internal sd.
Download Bad Sector from my Dropbox: http://db.tt/won7nZlr
In apx mode run a501a.bat. when finished, reboot and go in recovery. Format system partition 3 times. Go back in apx mode. Run a501b.bat. when finished, you are on unlocked ics bootloader v8 and cwm 1.7.3. Boot in recovery and flash the ics rom you like.
Gesendet von meinem Iconia A501 mit Tapatalk 2
VelosCohagen said:
Theres something bad with the partitions on your internal sd.
Download Bad Sector from my Dropbox: http://db.tt/won7nZlr
In apx mode run a501a.bat. when finished, reboot and go in recovery. Format system partition 3 times. Go back in apx mode. Run a501b.bat. when finished, you are on unlocked ics bootloader v8 and cwm 1.7.3. Boot in recovery and flash the ics rom you like.
Gesendet von meinem Iconia A501 mit Tapatalk 2
Click to expand...
Click to collapse
Just ran the A501 A.bat and got the following
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c620442e124d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Still unable to get into recovery.
Sounds like a hardware issue with your internal sd. I think you'll have to send it to Acer for repair. But maybe, one of the many other guys here in the forum may be of help for you.
jazzyjames said:
Just ran the A501 A.bat and got the following
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c620442e124d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Still unable to get into recovery.
Click to expand...
Click to collapse
Try this one package(h?? p change to httр):
h??p://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.htm
Hello,
I have the same problem.
When I run A501A.bat, it creates some partitions and format 4 partitions. The blank screen of the tablet shows acer logo with Acer Apx Mode in white and after that nothing happens!
If I reboot the tablet, I can't go to recovery.
I don't know the tablet's story because I bought it broken. The tablet stucks in Apx mode.
(I am sorry for my bad english)
Sent from my Galaxy Nexus using xda app-developers app
EDIT: post deleted = sorry guys this was sposed to be a pm
Hello,
When I try A501A.bat that's what happens:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c618743e02497
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 4 EBT please wait.. done!
failed executing command 14 NvError 0x30012
command failure: create failed (bad data)
Appuyez sur une touche pour continuer...
Can anybody help me please.... :crying:
Thanks.
(I am sorry for my bad english)
Same problem here!!!
Could someone please help?
Thanks a lot!
Code:
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) me
ssage: nverror:0x42008 (0x6042008) flags: 0
sebone02 said:
Hello,
When I try A501A.bat that's what happens:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c618743e02497
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 4 EBT please wait.. done!
failed executing command 14 NvError 0x30012
command failure: create failed (bad data)
Appuyez sur une touche pour continuer...
Can anybody help me please.... :crying:
Thanks.
(I am sorry for my bad english)
Click to expand...
Click to collapse
stragnagn said:
Same problem here!!!
Could someone please help?
Thanks a lot!
Code:
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) me
ssage: nverror:0x42008 (0x6042008) flags: 0
Click to expand...
Click to collapse
this appears to be the same error code as the OP's...I pm'ed jazzy earlier this
week to ask him if he had fixed his tab...
his reply was No...he had to send it in for repair and get the motherboard replaced....
If timmydeansv4 does not work in this instance then you will need to contact acer!!!
also could u pls post yr error code in this post as well trying to get a thread with all the error codes posted, thanks and good luck
dibb
VelosCohagen said:
Theres something bad with the partitions on your internal sd.
Download Bad Sector from my Dropbox:
In apx mode run a501a.bat. when finished, reboot and go in recovery. Format system partition 3 times. Go back in apx mode. Run a501b.bat. when finished, you are on unlocked ics bootloader v8 and cwm 1.7.3. Boot in recovery and flash the ics rom you like.
Gesendet von meinem Iconia A501 mit Tapatalk 2
Click to expand...
Click to collapse
Files on the link removed. Can someone upload these files?
Iganja said:
Files on the link removed. Can someone upload these files?
Click to expand...
Click to collapse
https://mega.co.nz/#!q5U1nRYZ!IS4FMz0Mb7ewo-Vd-2u5KU_cRE7zreTR4KgU_q8HcC8
Sent from my SM-N910U using Tapatalk
dibb_nz said:
mega.co.nz/#!q5U1nRYZ!IS4FMz0Mb7ewo-Vd-2u5KU_cRE7zreTR4KgU_q8HcC8
Sent from my SM-N910U using Tapatalk
Click to expand...
Click to collapse
Thank U!
It is a pity that it did not help .
Still gives the following error :
Code:
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
bad memory chip, new motherboard is only fix
Sent from my SM-N910U using Tapatalk
Okay so this thing is driving me nuts! I have the A500 and it is stuck in APX mode. A buddy gave me this saying it was bricked. I would love to get it up and going! I have been from forum to forum and going nuts here. I really though I was going to be able to get it with the timmydean tool. But when I enter my cpuID its one number too long. CPU ID: 0x37C6205446015D7. I got this number from doing some trick on ubutnu. I have my SKB as well. Can anyone help me out. I don't know much at all about tablets and flashing roms on them. I used to have a Windows Mobile phone back in the day and did a great deal of making kitchens for it but this seems like a lot more steps. Is there a trick with the cupid on timmydeans tool? Thank you in advance!
beamerguy0 said:
Okay so this thing is driving me nuts! I have the A500 and it is stuck in APX mode. A buddy gave me this saying it was bricked. I would love to get it up and going! I have been from forum to forum and going nuts here. I really though I was going to be able to get it with the timmydean tool. But when I enter my cpuID its one number too long. CPU ID: 0x37C6205446015D7. I got this number from doing some trick on ubutnu. I have my SKB as well. Can anyone help me out. I don't know much at all about tablets and flashing roms on them. I used to have a Windows Mobile phone back in the day and did a great deal of making kitchens for it but this seems like a lot more steps. Is there a trick with the cupid on timmydeans tool? Thank you in advance!
Click to expand...
Click to collapse
You dont need the 0x just use 37C6205446015D7
what do u mean is there a trick on timmydeans tool - thats HC 3.2??
dibb_nz said:
You dont need the 0x just use 37C6205446015D7
what do u mean is there a trick on timmydeans tool - thats HC 3.2??
Click to expand...
Click to collapse
okay, took the 0x out and it took it... However now it start to run but after about 10 to 20 seconds it fails and tells me to try again. The tablet is showing up on my computer as being in apx mode when I connect it.
beamerguy0 said:
okay, took the 0x out and it took it... However now it start to run but after about 10 to 20 seconds it fails and tells me to try again. The tablet is showing up on my computer as being in apx mode when I connect it.
Click to expand...
Click to collapse
ok lets back up the bus a bit!!!
What tool are u using?
Do you know if the tab was on HC or ICS?
dibb_nz said:
ok lets back up the bus a bit!!!
What tool are u using?
Do you know if the tab was on HC or ICS?
Click to expand...
Click to collapse
alright I believe what happened is my friend had ICS, but while updating something happened and that's when he said it was bricked. So when I was reading some of the many millions of forums I saw some talked about using Timmy deans tool to go back to stock HC and start over. So that's what I was trying to do.
beamerguy0 said:
alright I believe what happened is my friend had ICS, but while updating something happened and that's when he said it was bricked. So when I was reading some of the many millions of forums I saw some talked about using Timmy deans tool to go back to stock HC and start over. So that's what I was trying to do.
Click to expand...
Click to collapse
okidoki! got it
For timmys tool to work you need USB debuggign enabled on your tab, so if you cannot boot to ensure that this is enabled, you need to try another tool!!!
the babsector.rar works when tdv4 won't...it will reset the partitions on your tab, flash the unlocked bootloader and cwm. If there is an error please post the output....You will also need to flash an ICS or JB rom
dibb_nz said:
babsector.rar download here
How to use babsector -
Turn your tab off and put it in apx mode manually. Press and hold reset button, hold power for 3 secs after the light comes on and release it, after another second release the reset button. Your screen is black and the power light is on.
On your PC:
Download and extract the .rar to a folder on your PC
Connect your tab to your PC
Navigate to the babsector folder and click on 501 A.bat
On your tab:
Reboot into recovery power/volume DOWN - (closest end to the power button)
Go to Mounts and Storage Menu and
Format - System, Data, Flexrom, Cache
Then flash your ICS/JB rom, power off.
Go back into apx mode and run 501 B.bat
Reboot into recovery and do the wipes
Reboot!!!
Click to expand...
Click to collapse
dibb_nz said:
okidoki! got it
For timmys tool to work you need USB debuggign enabled on your tab, so if you cannot boot to ensure that this is enabled, you need to try another tool!!!
the babsector.rar works when tdv4 won't...it will reset the partitions on your tab, flash the unlocked bootloader and cwm. If there is an error please post the output....You will also need to flash an ICS or JB rom
Click to expand...
Click to collapse
okay, thanks so much, I will try this tomorrow morning and post the results. Is there a full working jelly bean rom for the a500 now? I know I saw some things were not working like WiFi or cameras... Those were older post though. Can you point me to where I can get a good ICs or jelly bean rom?
beamerguy0 said:
okay, thanks so much, I will try this tomorrow morning and post the results. Is there a full working jelly bean rom for the a500 now? I know I saw some things were not working like WiFi or cameras... Those were older post though. Can you point me to where I can get a good ICs or jelly bean rom?
Click to expand...
Click to collapse
It failed Here is what it said when I ran the a501 A.bat
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
Enter your SBK:0x1dd41e00 0xb8961700 0x57dff302 0x88792103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c6205446015d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .
beamerguy0 said:
It failed Here is what it said when I ran the a501 A.bat
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
Enter your SBK:0x1dd41e00 0xb8961700 0x57dff302 0x88792103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c6205446015d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .
Click to expand...
Click to collapse
oh dear, not good news I'm afraid...this is the error for the fault memory chip and unfortuanately there is no fix for that....sorry dude
dibb_nz said:
oh dear, not good news I'm afraid...this is the error for the fault memory chip and unfortuanately there is no fix for that....sorry dude
Click to expand...
Click to collapse
NOOOOooooooooo lol Well, glad I asked before continuing to go crazy with it... I have seen motherboards that are pretty cheap for it... LIke 50-60.00. If I change it out would that work? Well assuming that the board I buy is good and everything. I would like a tablet with GPS but really don't want to spend a couple hundred bucks on a new one at that time. Thank you for all the help you gave me
Apologies for yet another thread. I've been through every "unbrick" thread and still not able to boot the tab. I'm starting to think it's time to recycle the thing.
So, I picked up my tab one day and it had powered off (bone stock on the latest OTA). Tried to boot up and never got past the Acer splash screen (multiple attempts). Tried to reflash via the sd card, and it failed. Now it only boots to the dead Android. Try to flash another rom (these are stock releases) and it hangs for over a day without completing. Now it won't get past apx mos, black screen with a power light. Tried to flash via nvflash using several automated methods, they all fail complaining of various errors that seem to be related to bad partitions. I run badblocks and get errors. Now, having gone through everything short, I go to euu. That also hangs on copying the image. I'm out of ideas. is there something I haven't tried, or am I likely dealing with s dead tab at this point?
Pretty much the same thing happened to me last night I stayed up all morning trying to fix it but I'm beginning to realize it's probably something in the hardware.. Odd there so many all about the same kind of time.. Mine was rooted and the only thing I can boot to is the first skrillax boot loader screen, or Acer screen..depending on what I did..guess its Tims for a new tab..any suggestions? Lol
Sent from my A100 using Tapatalk
droidxxxxx said:
Pretty much the same thing happened to me last night I stayed up all morning trying to fix it but I'm beginning to realize it's probably something in the hardware.. Odd there so many all about the same kind of time.. Mine was rooted and the only thing I can boot to is the first skrillax boot loader screen, or Acer screen..depending on what I did..guess its Tims for a new tab..any suggestions? Lol
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
I guess we can take the guts out and make them into picture frames?
I did the fix my Acer thing from the Acer website found out mine is out of warranty for sure but they got back to me with an email and a phone number and I called and talked to a girl who told me it would be 200 and $49 just to get it in the door for a repair. Needless to say I *****ed and moaned told her I was going to throw it in the garbage and she is now sending me a label for FedEx to ship it and they will look at it hopefully they will fix it possibly for free now lol so I'm going to be sending it off when I get the label. I've tried just about everything and it seems mine just isn't recognized very well by the PC. I wonder if I have the correct drivers
Sent from my SCH-I535 using Tapatalk
wsmithjr said:
Apologies for yet another thread. I've been through every "unbrick" thread and still not able to boot the tab. I'm starting to think it's time to recycle the thing.
So, I picked up my tab one day and it had powered off (bone stock on the latest OTA). Tried to boot up and never got past the Acer splash screen (multiple attempts). Tried to reflash via the sd card, and it failed. Now it only boots to the dead Android. Try to flash another rom (these are stock releases) and it hangs for over a day without completing. Now it won't get past apx mos, black screen with a power light. Tried to flash via nvflash using several automated methods, they all fail complaining of various errors that seem to be related to bad partitions. I run badblocks and get errors. Now, having gone through everything short, I go to euu. That also hangs on copying the image. I'm out of ideas. is there something I haven't tried, or am I likely dealing with s dead tab at this point?
Click to expand...
Click to collapse
This is what I'd do, and this goes for anyone stuck on the acer logo or otherwise soft-bricked.
Run babsector.rar file.
This is the ONLY file that will give you an error that can be troubleshooted. NONE of the auto tools or the manual nvflash method will do this.
Once babsector has run, post the output and we can tell if its the dreaded hardware fault or not.
Download and instructions here http://forum.xda-developers.com/showthread.php?t=2049778
A great guide by kaijikun here http://forum.xda-developers.com/showthread.php?t=2450119
If you get stuck with the black screen with the power led light ON.
Hold the power button for 5 secs until it goes off.
Re-enter apx mode manually (i.e. this means using the buttons, don't use the auto tools, it won't work)
It also goes without saying, you need the acer drivers http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=3851 and the drivers from the android sdk, you can download a mini zip here https://www.dropbox.com/s/x98233x397wrzr1/Step_1_Drivers_mini_sdk_adb.zip
If you don't have your CPUID, there's no way of unbricking.
If you don't know what a CPUID is AND can still boot, read this guide here http://forum.xda-developers.com/showthread.php?p=25429111#post25429111.
If you cannot boot and don't have your CPUID you need to recover it using Linux, see srbeens guide here http://forum.xda-developers.com/showthread.php?t=1751978
Just to say, the whole unbricking process takes some time....mostly downloading everything you need. You will also need a fully charged tab, you can sometimes use 40-50% of your battery doing this. To be safe connect your charger and leave it there till you are done.
The other thing is your PC OS...there has been mixed success with win8 and 64bit. FOr best results win7, vista and xp work best. If you are linux savvy, you're in luck, no driver issues at all with this OS!!!
The only way you can not restore your tab to fully working order is if your tab has the faulty memory chip. And the only way to know if this is the case is to run the babsector.rar file.
dibb
wsmithjr said:
Apologies for yet another thread. I've been through every "unbrick" thread and still not able to boot the tab. I'm starting to think it's time to recycle the thing.
So, I picked up my tab one day and it had powered off (bone stock on the latest OTA). Tried to boot up and never got past the Acer splash screen (multiple attempts). Tried to reflash via the sd card, and it failed. Now it only boots to the dead Android. Try to flash another rom (these are stock releases) and it hangs for over a day without completing. Now it won't get past apx mos, black screen with a power light. Tried to flash via nvflash using several automated methods, they all fail complaining of various errors that seem to be related to bad partitions. I run badblocks and get errors. Now, having gone through everything short, I go to euu. That also hangs on copying the image. I'm out of ideas. is there something I haven't tried, or am I likely dealing with s dead tab at this point?
Click to expand...
Click to collapse
Yeah same thing happened to my A500. But downloaded 4 files Because there was 4 to choose from.
I renamed the file, eg filename.zip, to "update" with no extension. Copied to a clean micro SD. Inserted the SD card. Held the volume down and power switch until tablet vibrated and toggled the screen lock switch on then off. Then sat and watched. The whole process can take 30 minutes and for a long time it seemed stuck at about 25%. I decided to wait and see. And it all came good.
My A500 was stock no root. Still is and seems to work better now.
:good:
Here's the output from a501 a.bat, as requested.
Nvflash started
rcm version 0X20001
System Information:
* *chip name: t20
* *chip id: 0x20 major: 1 minor: 3
* *chip sku: 0x8
* *chip uid: 0x037c61c742a14597
* *macrovision: disabled
* *hdcp: enabled
* *sbk burned: true
* *dk burned: true
* *boot device: emmc
* *operating mode: 4
* *device config strap: 0
* *device config fuse: 0
* *sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .
Thanks in advance. ..
dibb_nz said:
This is what I'd do, and this goes for anyone stuck on the acer logo or otherwise soft-bricked.
Run babsector.rar file.
This is the ONLY file that will give you an error that can be troubleshooted. NONE of the auto tools or the manual nvflash method will do this.
Once babsector has run, post the output and we can tell if its the dreaded hardware fault or not.
Download and instructions here http://forum.xda-developers.com/showthread.php?t=2049778
A great guide by kaijikun here http://forum.xda-developers.com/showthread.php?t=2450119
If you get stuck with the black screen with the power led light ON.
Hold the power button for 5 secs until it goes off.
Re-enter apx mode manually (i.e. this means using the buttons, don't use the auto tools, it won't work)
It also goes without saying, you need the acer drivers http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=3851 and the drivers from the android sdk, you can download a mini zip here https://www.dropbox.com/s/x98233x397wrzr1/Step_1_Drivers_mini_sdk_adb.zip
If you don't have your CPUID, there's no way of unbricking.
If you don't know what a CPUID is AND can still boot, read this guide here http://forum.xda-developers.com/showthread.php?p=25429111#post25429111.
If you cannot boot and don't have your CPUID you need to recover it using Linux, see srbeens guide here http://forum.xda-developers.com/showthread.php?t=1751978
Just to say, the whole unbricking process takes some time....mostly downloading everything you need. You will also need a fully charged tab, you can sometimes use 40-50% of your battery doing this. To be safe connect your charger and leave it there till you are done.
The other thing is your PC OS...there has been mixed success with win8 and 64bit. FOr best results win7, vista and xp work best. If you are linux savvy, you're in luck, no driver issues at all with this OS!!!
The only way you can not restore your tab to fully working order is if your tab has the faulty memory chip. And the only way to know if this is the case is to run the babsector.rar file.
dibb
Click to expand...
Click to collapse
wsmithjr said:
Here's the output from a501 a.bat, as requested.
Nvflash started
rcm version 0X20001
System Information:
* *chip name: t20
* *chip id: 0x20 major: 1 minor: 3
* *chip sku: 0x8
* *chip uid: 0x037c61c742a14597
* *macrovision: disabled
* *hdcp: enabled
* *sbk burned: true
* *dk burned: true
* *boot device: emmc
* *operating mode: 4
* *device config strap: 0
* *device config fuse: 0
* *sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .
Thanks in advance. ..
Click to expand...
Click to collapse
Its a hardware fault, bad memory chip
Sent from my GT-I9300 using Tapatalk
Thank you for the confirmation.
dibb_nz said:
Its a hardware fault, bad memory chip
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Same thing happened to mine
Exact same thing happened to mine. No recourse since mine was out of warranty but I complained about it on an Acer Forum and on their facebook page and within a couple of hours I was contacted and instructed to mail it in. I had to pay for the shipping charges there (like 12 bucks) but they shipped it back on their dime and it was fixed. From shipping to them to getting it back was about 2 weeks. I was ready to swear off Acer forever but they manned up and fixed something that was obviously a widely known defect since it's happening to many others.
Dear dibb_nz,
What if A500 A.bat is working flawlessly for me, but A500 B.bat is failing during BCT formatting stage:
Code:
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 0) message: nverror:0x2 (0x2) flags:0
Should you need any additional info, just ask me
Thank you in advance for reply!
Hardware failure?
a501A failed. Here is the script.. Is my a500 suffering from the same bad memory chip problem?
Nvflash started
rcm version 0x20001
System Information:
- chip name: t20
- chip id: 0x20 major: 1 minor: 3
- chip sku: 0x8
- chip uid: 0x037c6185435f2617
- macrovision: disabled
- hdcp: enabled
- sbk burned: true
- dk burned: true
- boot device: emmc
- operating mode: 4
- device config strap: 0
- device config fuse: 0
- sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
: 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x42008 (0x2042008) flags:0
Thanks in Advance.
SyavsoN said:
Dear dibb_nz,
What if A500 A.bat is working flawlessly for me, but A500 B.bat is failing during BCT formatting stage:
Code:
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 0) message: nverror:0x2 (0x2) flags:0
Should you need any additional info, just ask me
Thank you in advance for reply!
Click to expand...
Click to collapse
mhiester said:
a501A failed. Here is the script.. Is my a500 suffering from the same bad memory chip problem?
Nvflash started
rcm version 0x20001
System Information:
- chip name: t20
- chip id: 0x20 major: 1 minor: 3
- chip sku: 0x8
- chip uid: 0x037c6185435f2617
- macrovision: disabled
- hdcp: enabled
- sbk burned: true
- dk burned: true
- boot device: emmc
- operating mode: 4
- device config strap: 0
- device config fuse: 0
- sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
: 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x42008 (0x2042008) flags:0
Thanks in Advance.
Click to expand...
Click to collapse
Sorry u both having probs an I not sure I can help but.....
@SyavsoN so do u get an error with the first bat file? If not,
run the first one again
Enter recovery and do the wipes
Reboot recovery and flash yr rom
What happens???
@mheister and everyone else with bct error.
Apxflash tool is the only tool that can fix these errors.
Normally u can use the default bct when u get to that option. But if u have probs with the default then u must use the bct from yr tab. So choose the dump yr bct option.
Thats about all I can suggest for u guys atm,
If @blackthund3r is still lurking around here he may be able to help out with this!!
dibb
Socrates11 said:
Exact same thing happened to mine. No recourse since mine was out of warranty but I complained about it on an Acer Forum and on their facebook page and within a couple of hours I was contacted and instructed to mail it in. I had to pay for the shipping charges there (like 12 bucks) but they shipped it back on their dime and it was fixed. From shipping to them to getting it back was about 2 weeks. I was ready to swear off Acer forever but they manned up and fixed something that was obviously a widely known defect since it's happening to many others.
Click to expand...
Click to collapse
I just got the same issue. a501 A.bat gives me the same error: "bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x8 (0x19000008) flags: 0"
Code:
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
I just posted on the Acer Americas Facebook page, let's see what they say...
HyeProfile said:
I just got the same issue. a501 A.bat gives me the same error: "bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x8 (0x19000008) flags: 0"
Code:
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
I just posted on the Acer Americas Facebook page, let's see what they say...
Click to expand...
Click to collapse
Try Acer dude, 3 users have had there's repaired by acer for free, even if they were no longer under warranty!!! It's worth a shot
Sent from my HTC_PN071 using Tapatalk
Anyone know how to get in contact with Acer. I've looked around in their support website, but I can't chat with a support assistant because my tablet is out of warranty.
Sent from my DROID RAZR using Tapatalk
Check my fix out!
wsmithjr said:
Here's the output from a501 a.bat, as requested.
Nvflash started
rcm version 0X20001
System Information:
* *chip name: t20
* *chip id: 0x20 major: 1 minor: 3
* *chip sku: 0x8
* *chip uid: 0x037c61c742a14597
* *macrovision: disabled
* *hdcp: enabled
* *sbk burned: true
* *dk burned: true
* *boot device: emmc
* *operating mode: 4
* *device config strap: 0
* *device config fuse: 0
* *sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0
Press any key to continue . . .
Thanks in advance. ..
Click to expand...
Click to collapse
I had the same error check out my tut (http://forum.xda-developers.com/showthread.php?p=49585687)
hello i have an A500 stock rom and recovery,never flash it anything and one day it just died after puting it on stand by, i can put in in apx mode but i never turn the debugg on, so when i try to flash it ..nothing happens, the sd method dont work i hace the cpuid and the sbk witht the linux method, but thats as far as i can get.
im on ics, my bootloader is v0.03.12-ics and when i press vol +, power and rotation lock i got this
Bootloader v0.03.12-ics: starting fastobbot USB download protocol.
its was bricked so i run the a501 A.bat and after it i just came with an APX mode only
This is the result of the a501.bat
Nvflash started
rcm version 0X200001
System Information:
chip name: t20
chio id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0380624440e10417
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
opertating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
--4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x1080000 entry point: 0x1080000
ending file: bootloader.bin
: 714409/714409 bytes sent
bootloader.bin sent successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
formating partition 2 BCT please wait ... FAILED
command failure: create failed (bad data)
bootloader status: specified partiton is invalid or does not exist (code: 7) message: nverror: 0x42008 (0x6040008) flags: 0
press any key . . .
Any ideas . I think i have lost my partitions, is there a way to create them?
by the way im very noob here so a step by step procedure is what i need....
Thank for the help you can provide me .
(I already tried a lot of searching, no success)
I am trying to recover an Acer Iconia A500, which seemed to have a bad sector in the first 4MB of flash. So after Babsector and manual rawwrite/rawread tests, I created a modified flash.cfg which inserted an FCK partition for the bad sectors between the BCT and PT partitions. However when I run nvflash --create, it hangs trying to format that FCK partition (which is just there to prevent use of the bad sectors).
Is there a workaround, e.g. some way of telling nvflash not to format the FCK partition while still creating the proper contents of the BCT and PT partitions (so I can move on to flashing the desired bootloader, kernel and recovery)?
Update: By simply trying again and again, it randomly succeeded (once) in getting past the FCK formatting. No change in config or command, just repeated tries (which cannot be good for the flash chip).
I am using the old nvflash.exe (dated 2011-11-23, size 152064, no --version option) with the following command line:
Code:
nvflash --bct flash.bct --setbct --configfile flash.cfg --create --odmdata 0x100c0105 --bl dlmodebl.bin --sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX
dlmodebl.bin (like nvflash.exe and flash.bct) is from timmydean's root-3.2.1-V4.7z
The output (from failed attampts) is this:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0xXXXXXXXXXXXXXXXX
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: dlmodebl.bin
| 714385/714385 bytes sent
dlmodebl.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: FCK
creating partition: PT
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 15 FCK please wait.. done!
(and it just hangs after that). The one time I was successful, it swiftly did all the partitions then flashed the various .bin and .img files as specified in flash.cfg. Output was this:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0xXXXXXXXXXXXXXXXX
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: dlmodebl.bin
| 714385/714385 bytes sent
dlmodebl.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: FCK
creating partition: PT
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 15 FCK please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 GP1 please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 MSC please wait.. done!
Formatting partition 11 FLX please wait.. done!
Formatting partition 12 AKB please wait.. done!
Formatting partition 13 UDA please wait.. done!
Formatting partition 14 GPT please wait.. done!
done!
sending file: bootloader.bin
| 1191932/1191932 bytes sent
bootloader.bin sent successfully
sending file: recoveryThor.img
\ 4810752/4810752 bytes sent
recoveryThor.img sent successfully
sending file: boot.img
- 3450880/3450880 bytes sent
boot.img sent successfully
sending file: system.img
/ 629145600/629145600 bytes sent
system.img sent successfully
sending file: flexrom.img
/ 104857600/104857600 bytes sent
flexrom.img sent successfully
sending file: checksum.img
/ 10485760/10485760 bytes sent
checksum.img sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x8 (0x11000008)
flags: 0
However, the result is still not bootable (to recovery, system.img doesn't match the other parts).
The modified flash.cfg differs from timmydean's only in a smaller BCT and the extra FCK partition at the beginning, here is the new beginning:
Code:
[device]
type=hsmmc
instance=3
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=FCK
id=15
type=data
allocation_policy=sequential
filesystem_type=basic
size=3141632
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
Wow that's some nice investigative work there...
These things are way above my skill level, but I can offer some thoughts from being around the Acer forums here for a while now.
You are correct regarding the chip. It is faulty (or the solder is.) Which is why formatting 'worked' after multiple attempts.
It's still failing on the bct write error. What I can tell you is, each tabs bct is 'different'. For nvflash to operate correctly, you must use your tabs own bct. Once flashed successfully with skrilax_cz bootloader, it doesn't appear to matter which bct you use...
Blackthund3r's apxFlash tool has an option to dump (and save) your tabs bct, which can then be used to successfully nvflash.
If you could somehow retrieve the original bct you may be able to resolve the problem....in saying that though, you will still be left with a faulty emmc, so any success you have with the flash, at some point it will fail completely....attempts at Reflowing the solder has worked in some but not all cases, so that's at least worth a try.
I wish you all the best with your endeavours, the bct error has never been resolved and thei conclusion has always been "it's a faulty chip" not much comfort for those with the issue, especially being through no fault of their own....
One other thing, through many, many flashing attempts of my own, I did get this error once...thankfully between the auto tools and babsector/tdv4 etc, I managed to get it up and running again. I've never had any trouble with it over the 2-3 years since...there maybe a small sliver of hope for you there...
Good luck with it !!
dibb
Sent from my HTC_PN071 using Tapatalk
Unfortunately, Blackthunder's utility just kept getting in the way, as it kept assuming I was starting from a working tablet in ADB mode, not a broken tablet that could only be put in APX mode with the reset button. I managed to find an XDA thread with a tool to extract the CPUID from APX mode and another thread with a tool for creating the Iconia specific SBKv1 from the CPUID.
Blackthunder's tool seems to be mostly a wrapper around the base tools (adb.exe, fastboot.exe and nvflash.exe), and at least the nvflash from the timmyDean ROM bundle fails when asked to read back the old BCT, while the nvflash from the wheelie bundle simply doesn't accept an SBK argument. Anyway since I have by now repeated reformatted the flash, I doubt the old BCT is still there.
From what I have read however, the (unencrypted) BCT depends only on the following:
1. How the RAM and FLASH is wired to the Tegra chip in a specific tablet model (and which RAM and FLASH chip models they are, for instance do they run on 1.8V or 3V).
2. Parts of the partitioning.
3. Parts of the bootloader configuration (the --odmdata argument).
So using the BCT from timmyDean's bundle should be fine for the A500 it was written for.
Another thing is that during flashing, the BCT and other early boot parts need to be encrypted with the device specific SBK. For the A500 and A501 we know the SBK and can do so directly (via the --sbk option to the old nvflash.exe or the BlackThunder GUI), while for some later tablets we don't know the SBK but can use the the wheelie trick to make the tablet encrypt it for us (this is what the wheelie preparation procedure essentially does).
I still haven't found a detailed nvflash manual, the documentation for the RCM preboot protocol or the documentation for Tegra's AES engine.