[Q] bootloader status: Bct Write Failed (code: 22) - Acer Iconia A500

Please help!
I tried to update the bootloader to v9 but after installing the zip file thru cwm, rebooted it said flashing failed and black screen.
I can only get to APX mode.
When I use the blackthund3r_A500_APX_Flash_Tool to flash, it did not detect the APX mode but I can see the APX device from windows. The process hang in EBT stage 2 - uploading image.
So I tried to nvflash. I can enter the nvflash mode ok:
C:\Android\A500\V8-UNL-ICS-HC-bootloader-MULTI-cwm>nvflash --bct bct.bct --setbct --sbk xxxxx xxxxx xxxxx xxxxx--configfile flash.cfg --bl bootloader_apx.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c61c041xxxxxx
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
I can extracted the partition table:
C:\Android\A500\V8-UNL-ICS-HC-bootloader-MULTI-cwm>nvflash -r --getpartitiontable ptable.txt
Nvflash started
[resume mode]
Succesfully updated partition table information to ptable.txt
The partition 4 is:
PartitionId=4
Name=EBT
DeviceId=18
StartSector=896
NumSectors=1024
BytesPerSector=4096
When I try to format partition 4, it failed:
C:\Android\A500\V8-UNL-ICS-HC-bootloader-MULTI-cwm>nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
I reconnected nvflash and try to download the bootloader to partition 4, still failed:
C:\Android\A500\V8-UNL-ICS-HC-bootloader-MULTI-cwm>nvflash -r --download 4 bootloader_v8.bin
Nvflash started
[resume mode]
sending file: bootloader_v8.bin
| 1191932/1191932 bytes sent
bootloader_v8.bin sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0
Can anyone help me please? I can only go to APX mode

MY partition 4 is my Bootloader and I think it is corrupted. I cannot download or format it.
PartitionId=4
Name=EBT
DeviceId=18
StartSector=896
NumSectors=1024
BytesPerSector=4096
But I tried to run nvflash --rawdeviceread and then --rawdevicewrite, it can finished without errors:
C:\Android\A500\V8-UNL-ICS-HC-bootloader-MULTI-cwm>nvflash -r --rawdeviceread 896 1024 p_4.txt
Nvflash started
[resume mode]
failed executing command 30 NvError 0x120002
command failure: readdeviceraw failed (bad data)
C:\Android\A500\V8-UNL-ICS-HC-bootloader-MULTI-cwm>nvflash -r --rawdevicewrite 896 1024 p_4.txt
Nvflash started
[resume mode]
sending file: p_4.txt
/ 4194304/4194304 bytes sent
p_4.txt sent successfully
Can someone extract the partition 4 EBT into a file so that I can try to write it on my A500? Please Help!

Related

[Q] No Access to ROM or Recovery (LNX&SOS error), only apx mode avaible

Hi,
ok here's my problem:
After a flashing a new kernel + rom (and a crash while flashing the system datas) my a500 shows LNX and SOS checksum Errors.
I can't boot into Recovery or ROM, no ADB access avaible, only APX Mode.
So i've tried to flashing per APX Tool and nvflash a new bootloader+recovery.
But everytime i get this result:
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xXXXXXXX 0xXXXXXXX 0xXXXXXXX 0xXXXXXXX --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0xXXXXXXX
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714981/714981 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
Click to expand...
Click to collapse
tried different bootloaders for A500 (HC and ICS) but everytime with the same errors.
I hope someone can help me.
mfg cas
p.s. sorry for my english
Ok, i think i've made it ...
nvflash seems to unlike the "--sync" and "--odmdata 0x300d8011" command ... after each commandline, the bootloader lost the sync.
now i've used:
/nvflash --bct bct.bct --setbct --sbk ##sbkno## --configfile flash.cfg --bl bootloader_apx.bin --go
Click to expand...
Click to collapse
and the bootloader loads without errors.
then i used these commands (after each command i disconnected the device and reconnected it with the bl command above)
/nvflash -r --format_partiton 4
/nvflash -r --download 4 bootloader_ics_v7.bin
/nvflash -r --format_partiton 6
/nvflash -r --download 6 recovery_thor1.7.3.img
/nvflash -r --format_partiton 2
/nvflash -r --getpartitiontable table1.txt
Click to expand...
Click to collapse
now the bootloader and the recovery should be on the device ... but the tablet still not booting into recovery.
do i need to flash a complete rom to boot into the cwm?
if the answer is yes ... which partition to upload the rom?
EDIT:
Ok, next try.
with the command
nvflash --bct flash.bct --setbct --configfile flash.cfg --create --odmdata 0xb00d8011 --sbk 0xXXXXXXX 0xXXXXXXX 0xXXXXXXX 0xXXXXXXX --bl bootloader.bin --go
Click to expand...
Click to collapse
the console tells me the follow:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0xXXXXXXX
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: EBT
creating partition: SOS
creating partition: LNX
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: ER1
creating partition: USP
creating partition: ER2
creating partition: UDA
creating partition: ER3
creating partition: UDB
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
Click to expand...
Click to collapse
any ideas?
mfg cas
No, you don't need to install a rom to boot into recovery.
Unfortunately I'm not enough NVFlash knowledgable to help you much. But a question.
You said you thought you installed the bootloader/Recovery image on one of your attempts.
Did you try booting into Fastboot? Just curious if the display showed the bootloader version when you booted normally also.
For fastboot on the unlocked BL's, it's vol+ & PWR. If it works, and says "fastboot mode", you can run a fastboot command and install a Recovery that way.
It seems there are 2 or 3 tab's recently that have the same issue as your's. Can't NVFlash a bootloader. Your method gives a lot more info, so maybe one of the bootloader devs knows an answer.
@nisac..... I honestly don't know if this info will assist you to solve your problem but I'll post it in case something helps you.
Your last post shows nvflash reporting 15 Partitions but mine shows only 13 and apart from the fact that it is 2 less than yours there is also a difference in the naming of the partitions.
Mine are as follows.....
Partition 2 Boot Configuration Table (BCT)
Partition 3 Partition Table (PT)
Partition 4 Bootloader (EBT)
Partition 5 GP1 Partition (GP1)
Partition 6 Recovery (SOS)
Partition 7 Kernel (LNX)
Partition 8 System (APP)
Partition 9 Cache (CAC)
Partition 10 Misc (MSC)
Partition 11 Flexrom (FLX)
Partition 12 Checksums (AKB)
Partition 13 User Data (UDA)
Partition 14 GPT Partition (GPT)
..... As I said above don't know if it helps but it might shed some light on your problem.
Moscow Desire said:
Did you try booting into Fastboot? Just curious if the display showed the bootloader version when you booted normally also.
For fastboot on the unlocked BL's, it's vol+ & PWR. If it works, and says "fastboot mode", you can run a fastboot command and install a Recovery that way.
Click to expand...
Click to collapse
i've tried to boot into fastboot (vol+ / pwr), but the only thing i can do with this method is to make a wipe of data and cache (switch rotationlock).
if i only use vol+/pwr the tablet try to boot into the rom (LNX checksum error).
@metpolds
hm ... u are right.
the flash.cfg's have different partitiontables.
if i download a partition-table file from tablet to pc, there are the same partition as in your post.
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=768
BytesPerSector=4096
PartitionId=3
Name=PT
DeviceId=18
StartSector=768
NumSectors=128
BytesPerSector=4096
PartitionId=4
Name=EBT
DeviceId=18
StartSector=896
NumSectors=1024
BytesPerSector=4096
PartitionId=5
Name=GP1
DeviceId=18
StartSector=1920
NumSectors=256
BytesPerSector=4096
PartitionId=6
Name=SOS
DeviceId=18
StartSector=2176
NumSectors=1280
BytesPerSector=4096
PartitionId=7
Name=LNX
DeviceId=18
StartSector=3456
NumSectors=2048
BytesPerSector=4096
PartitionId=8
Name=APP
DeviceId=18
StartSector=5504
NumSectors=153600
BytesPerSector=4096
PartitionId=9
Name=CAC
DeviceId=18
StartSector=159104
NumSectors=313344
BytesPerSector=4096
PartitionId=10
Name=MSC
DeviceId=18
StartSector=472448
NumSectors=1024
BytesPerSector=4096
PartitionId=11
Name=FLX
DeviceId=18
StartSector=473472
NumSectors=25600
BytesPerSector=4096
PartitionId=12
Name=AKB
DeviceId=18
StartSector=499072
NumSectors=2560
BytesPerSector=4096
PartitionId=13
Name=UDA
DeviceId=18
StartSector=501632
NumSectors=7288832
BytesPerSector=4096
PartitionId=14
Name=GPT
DeviceId=18
StartSector=7790464
NumSectors=128
BytesPerSector=4096
Click to expand...
Click to collapse
it seems that the nvflash recreation of partitions don't worked.
and if i could download a partition-table.txt from tablet to pc ... there should be a valid partitiontable on the tablet or not?
hm is there any method to check any of the "successful commands" have an effect?
i have the feeling that none of the commands really worked (formating, downloading the bootloader etc.).
EDIT:
i think the "--odmdata 0x300d8011" is important, to have full access to the partitions, but if i use it, i always get errors (bct write failed).
without it, the tablet connect without any errors, but if i use any command, such as "nvflash -r --format_partition 8" i get this error:
Nvflash started
[resume mode]
Formatting partition 8 please wait.. done!
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
Click to expand...
Click to collapse
EDIT:
i've uploaded the bootloader (714981 bytes) again to partition 4 and read then the content of this partition (--read 4 part4.txt).
this file has a size of 4194304 bytes ...
now i uploaded another bootloader to the same partition without formating, and the file size of part4.txt is the same as before (4194304 bytes).
so none of my previous commands worked ... all for nothing
i can read all partitions and downloading the content to pc, but no write access, all "write" commands (format, download etc.) quits with error "bct write failed".
any idea how to set -rw permissions?
with "--odmdata" and "--sync" i get "bct write failed" error.
I just restored my tablet from an identical situation, by re-creating the partitions with the bootloader from TimmyDean's tool. After that I could flash the ICS bootloader and recovery. Beware however that I also lost the contents of the internal sdcard in the process. See forum.tegraowners.com/viewtopic.php?p=15285#p15331 for details (sorry about the inline URL, I'm not high enough on the totem pole to be able to post links).
Hm, the problem is, the bootloader on my device has no "permissions" to change anything on the partitions.
i can upload the bootloader and the bct file, and download files (partitiontable, partition content etc.) from tablet to my pc, but i can't upload anything into the partitions also change the configuration. (bct write error)
and timmydean's tools use the adb access to the devices, and on my devices the access is unavaiable also the fastboot mode, only apx mode is still "alive".
i've read a lots of threads about similar problems and it seems that my problem with "bct write error" can only be fixed with downgrading to hc downgrade, because my actual bootloader/kernel/whatever still don't the apx methode ... but ... it's still impossible (for me) to downgrad without access to adb or recovery.
i still hope that a recovery, nvflash profi can help me, otherwise i've to send the tablet to acer ...
EDIT:
Ok, i try the timmydean methode (image folder) again, and now i came to the similar point as in my second post here:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0xXXXXXXX
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: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
Click to expand...
Click to collapse
other than in my previous try ... the partitions no. and names are correct, but still the table is invalid / not avaiable.
looks like the same problem before, the bootloader couldn't write anything to the partitions, no readwrite access, only read access ... so it can't write/fix a new partitiontable to part 3.
and all commands i send after the bootloader aborted the process are instantly "crash" with errors:
>nvflash -r --read 4 part4.txt
Nvflash started
[resume mode]
failed executing command 15 NvError 0x120002
command failure: read failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Click to expand...
Click to collapse
nisac said:
i've uploaded the bootloader (714981 bytes) again to partition 4 and read then the content of this partition (--read 4 part4.txt).
this file has a size of 4194304 bytes ...
now i uploaded another bootloader to the same partition without formating, and the file size of part4.txt is the same as before (4194304 bytes).
Click to expand...
Click to collapse
The size read is the entire partition, not just the part you have written to.
nisac said:
Code:
PartitionId=4
Name=EBT
DeviceId=18
StartSector=896
NumSectors=1024
BytesPerSector=4096
Click to expand...
Click to collapse
1024*4096 = 4194304 bytes.
Does the read data start with what you tried to write?
Ah, ok thanks, my fault, i thought the filesize represents only the "written" content of the partition and not the entire partition. ^^
and second answer is yes, i think ... the read command runs without any problems, only the data on partition 13 seems to be corrupt (estimated filesize -209715200 bytes without stopping downloading).
nisac said:
Ah, ok thanks, my fault, i thought the filesize represents only the "written" content of the partition and not the entire partition. ^^
and second answer is yes, i think ... the read command runs without any problems, only the data on partition 13 seems to be corrupt (estimated filesize -209715200 bytes without stopping downloading).
Click to expand...
Click to collapse
I'm wondering it that is not more likely to be a problem in the partition table.
Can you read the PT partition? Could be interesting to have a look at that.
lcd047 said:
I just restored my tablet from an identical situation, by re-creating the partitions with the bootloader from TimmyDean's tool. After that I could flash the ICS bootloader and recovery. Beware however that I also lost the contents of the internal sdcard in the process. See forum.tegraowners.com/viewtopic.php?p=15285#p15331 for details (sorry about the inline URL, I'm not high enough on the totem pole to be able to post links).
Click to expand...
Click to collapse
I'm a little curious about what you mean by "timmydeans tool to recreate the partition tables". Does that mean you just installed the rom&bootloader that TD ships with the tool?
Never actually used the tool, as I came before it was needed. But there are a few other tabs having the NVFlash bootloader issue so would be nice to get some more info if you had to use any of the tools he included in the package.
Yep, here's the result of "--read 3 pt.txt"
https://dl.dropbox.com/u/71965753/pt.txt (512KB)
and here the result of "--getpartitiontable"
https://dl.dropbox.com/u/71965753/partitiontable.txt (2KB)
Moscow Desire said:
I'm a little curious about what you mean by "timmydeans tool to recreate the partition tables". Does that mean you just installed the rom&bootloader that TD ships with the tool?
Never actually used the tool, as I came before it was needed. But there are a few other tabs having the NVFlash bootloader issue so would be nice to get some more info if you had to use any of the tools he included in the package.
Click to expand...
Click to collapse
I just flashed the bootloader from TimmyDean's package, with the option to re-create the partitions:
Code:
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --go
The similar command for the v7 bootloader would fail, because of "not enough room to create partitions", or something like that. Perhaps this had to do with the partitions being labeled differently in the v7 config file, as noted above, or perhaps the BCT was incorrect; somebody who actually knows something about Android booting might be able to tell. The point is, this has restored the partition table to a sane state, and I was able to flash the v7 bootloader and CWM recovery without error immediately after that. From there I just flashed FLEXREAPER from CWM, I didn't need to do any downgrade.
I should note that I did all that from Linux. For what it's worth, TimmyDean's flash tool doesn't seem to work for me (it gets stuck at the "upgrade is under way" message, the flash never starts). But then again, I'm Windows-impaired.
nisac said:
Yep, here's the result of "--read 3 pt.txt"
https://dl.dropbox.com/u/71965753/pt.txt (512KB)
and here the result of "--getpartitiontable"
https://dl.dropbox.com/u/71965753/partitiontable.txt (2KB)
Click to expand...
Click to collapse
The sizes looks ok, comparing to my partition table the only difference is that my UDA is 96KiB larger.
There is however some unknown entries per partition, those differ quite a bit...
The size of UDA in bytes is 7288832*4096 which is 0x6F3800000 in hex, and -209715200 is 0xF3800000. So the value we are seeing is the lower 32 bits of the size of UDA. That could just be a problem with how they are displaying the value, are you getting any "bytes received" messages?
i think the uda partition problem at this point is secondarily because i can't change anything if the partition is corrupt. :/
the problem with the uda partition could be a result of the recreate of the partition with adb because the entire partition became stuck into read-only state (couldn't wipe or formating in recovery or adb).
after this procedure i make a full wipe/factory reset and flashing a new rom+kernel (flexreaper ICS and hc kernel ... the tablet should be still with hc bootloader).
this works fine, only wifi don't work, so i flashing another rom, but this rom don't start ... then i reflashing the flexreaper ics and the tablet stuck in the middle of the flashing process.
this resulting in my actually problem with the SOS and LNX checksum fails.
i've just trying to upload the backup (from cwm) of the recovery to the partition 6, but nothing changed.
i think i send the tablet to acer and hope the best.
EDIT says don't give up!
hm, i've manuelly formating partition 4 (bootloader), 6 (recovery), 7 (kernel), 8 (system), 11 (flexrom), 12 (checksums) and 13 (userdata) and uploaded the image files from timmydeans root 321 to this partitions.
now, sometimes, the tablet hangs after erasing userdata and cache partition (pwr / vol+, rotalock) without any messages. (no errors like LNX checksum fail etc.)
if i boot the device normally (pwr on) i got the beloved LNX checksum error.
and recovery still unavaiable. (SOS checksum error)
don't know what to do.
2 days left till i can send it back to acer ... so use the time luke .. ^^
I have the same problem!!!
the story: A501 with Bootloader Version 3 - A501 Alexandra IV ICS - Thor1.7
so i update to Tegraowners ICS ROM v169, reboot recovery, update to Thor1.73, reboot... lost A501!!!
it boot only in APX mode...
i read more threads, so i test the secure tool root3.2.1, but the tool stop at 10% with the tablet in booloader mode...
so i download EUU version, and i test some command with nvflash!
the result is:
C:\EUUs_SBK_Acer_A501_0.017.01_PA_ATT\Image>nvflash.exe --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk
0xF8A41E00 0xCB4FC501 0x8B052103 0x6D092103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0380620541c14197
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
| 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: partition table is required for this command (code: 8) messag
e: nverror:0x5 (0x1000005) flags: 0
it is the same error you have...
Ur NVerror is different, but dont know what that or what my error number means.
try the nvflash command with the files from the root321 /Image/ folder
i installed NVflash on UBUNTU....
Root3.2.1-v4 - ODMDATA 0xb00d8011
....
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x5 (0x1000005) flags: 0
Root3.2.1-v4 - ODMDATA 0x100c0105
...
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x5 (0x1000005) flags: 0
the same errror....
i try something else...
dito
i found a thread about another device (dell streak), there they use -rawdevicewrite command of nvflash to write the data directly to the SD by defining startsectors of the partition and sector sizes of the file, without using the partition "table".
i've gave it a try and write the image files from root 321 image folder to the partitions, but nothing changed.
i got no error feedback or something like that after successfull executing of the commands, but still getting the SOS and LNX errors.
dont know it will help to restore the partitiontable and recreate the partitions with nvflash to fix this problem ... seems to be a bit more complicated, maybe a hardware issue
tomorrow i will send the tablet back to acer.
OK!
Tomorrow i'll send well the tablet to ACER!

Help with creating partitions!

Recently i got bricked A500 which is stuck in apx mode, no hard reset is available, EUU tool give fails, nvflash commands such as --create --format_all --rawdatawrite and rawdataread also return with errors
Here is log from one of my tries
Code:
D:\root-3.2.1\Image>nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --conf
igfile flash.cfg --create --bl bootloader.bin --sbk 0x9E1ED201 0xEB59F601 0xEB36
1203 0xAE0A2103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0428100041ff3457
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
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Can someone help me with telling what i need to do except swaping motherboard.
I have my own 2 conclusions and actions that i need to take: 1.) Change eMMC flash chip 2.) Give to someone who can flash it through JTAG
Which would solve the problem?
Rastysha said:
Recently i got bricked A500 which is stuck in apx mode, no hard reset is available, EUU tool give fails, nvflash commands such as --create --format_all --rawdatawrite and rawdataread also return with errors
Here is log from one of my tries
Code:
D:\root-3.2.1\Image>nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --conf
igfile flash.cfg --create --bl bootloader.bin --sbk 0x9E1ED201 0xEB59F601 0xEB36
1203 0xAE0A2103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0428100041ff3457
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
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Can someone help me with telling what i need to do except swaping motherboard.
I have my own 2 conclusions and actions that i need to take: 1.) Change eMMC flash chip 2.) Give to someone who can flash it through JTAG
Which would solve the problem?
Click to expand...
Click to collapse
theres a thread in dev to help with being stuck in apx mode
Any possible solutions described there didn't worked for me
Rastysha said:
Recently i got bricked A500 which is stuck in apx mode, no hard reset is available, EUU tool give fails, nvflash commands such as --create --format_all --rawdatawrite and rawdataread also return with errors
Here is log from one of my tries
Code:
D:\root-3.2.1\Image>nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --conf
igfile flash.cfg --create --bl bootloader.bin --sbk 0x9E1ED201 0xEB59F601 0xEB36
1203 0xAE0A2103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0428100041ff3457
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
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Can someone help me with telling what i need to do except swaping motherboard.
I have my own 2 conclusions and actions that i need to take: 1.) Change eMMC flash chip 2.) Give to someone who can flash it through JTAG
Which would solve the problem?
Click to expand...
Click to collapse
If you have access to ubuntu try running the nvflash command from there
dibb_nz said:
If you have access to ubuntu try running the nvflash command from there
Click to expand...
Click to collapse
Thx for advice but that didn't help. I recieve same error in ubuntu
What else i can try?
Theres no easy fix for this unfortunately
But check the apx driver is definitely installed.
Sometimes on a failed flash the drivers get screwed upload
Connect yr mini data cable and check the system trays safely remove h/w
The Acer USB boot-recovery driver should show here.
If it is d/l the latest v0.4a500 manager/ apxFlash tool by blackthund3r
Does thisbrecognise yr tab?????
If so use bundle 17 from the in-app bundle market
Choose the default bct option
There is a thread here that ubshould look at if u haven't already
I'll track it down - if these things don't work i dunno wot will
http://forum.xda-developers.com/showthread.php?t=1691729 [
Q] No Access to ROM or Recovery (LNX&SOS error), only apx mode avaible
Sent from my A500 using xda premium

[Tutorial] - Flash ICS v9 Bootloader manually under Linux.

Tutorial - Flash ICS v9 Bootloader manually under Linux.
I am writing this tutorial, because I was unable to replace the HC 3.01 bootloader under Windows with the ICS Bootloader.
This is a translation from the German tutorial at Android-Hilfe.de written by me (aka Brickerl).
Preparation: Tablet must be in APX Mode.
Turn your table off!
Use a paper clip and press the Reset Button softly. You can feel a soft resistance.
As you press the Reset button hold also the Power button. Do this 3 seconds long.
Now release the power button and the paper clip.
The light of the powerbutton glows now white (at least it does for me) und the display is black.
Files needed (see attachment):
bct.bct
flash.cfg
nvflash for Linux
bootloader_apx.bin
bootloader_v9.bin
Your SBK number!
We write a script. I call it a500.sh.
Make a new file. e.g. with vi.
Code:
vi a500.sh
Write this into the script file.
Code:
#!/bin/sh
./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x12345678 0x12345678 0x12345678 0x12345678 --sync
Modify your SBK.
Make the file executable.
Code:
chmod +x a500.sh
Execute the scipt as root. Dont worry there is no flashing yet. If there are some status messages all is ok. Otherwise cancel NOW or your tablet is bricked afterwards.
The status messages can look like this.
Code:
# ./a500.sh
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0xxxxxxxxxxxxxx
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Step 5:
Now the actual flashing begins. We add 3 lines to the script.
Code:
#!/bin/sh
./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x12345678 0x12345678 0x12345678 0x12345678 --sync
[B]./nvflash -r --format_partition 4
./nvflash -r --download 4 bootloader_v9.bin
./nvflash -r --go
[/B]
The output can look like this:
Code:
# ./a500.sh
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0xxxxxxxxxxxxx
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
[B]Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
Nvflash started
[resume mode]
sending file: bootloader_v9.bin
| 1191932/1191932 bytes sent
bootloader_v9.bin sent successfully
Nvflash started
[resume mode]
[/B]
Ready. On the device „Pass“ is displayed and it can be rebooted.
Nice little guide mate. Thanks for contributing!
MD
Yeah good stuff, will post a link from the root guide when I get back to my pc...
This is perfect for those running ics/jb roms BUT still on the HC bootloader and custom recovery, you may want to make that clear.
The other thing you may like to do is to add instructions to flash a custom recovery. The .img files can be found in the v8 bootloader.zip (not sure about v9.zip) This would be perfect for those who just cannot get flashed using windows for whateva reason.
Sent from my GT-I9300 using Tapatalk 4
Excellent Tutorial for NVFlash in Linux Great job, Very helpful! I especially like the extra detail in showing the output after you enter the commands.
- Kaiji
Error
What I've done wrong?
[email protected]:~$ sudo '/home/christian/Arbeitsfläche/ICSv9/a500.sh' [sudo] password for christian:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c61854400e097
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: 3
sending file: /home/christian/Arbeitsfläche/ICSv9/bct.bct
- 4080/4080 bytes sent
/home/christian/Arbeitsfläche/ICSv9/bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: /home/christian/Arbeitsfläche/ICSv9/bootloader_apx.bin
| 714981/714981 bytes sent
/home/christian/Arbeitsfläche/ICSv9/bootloader_apx.bin sent successfully
waiting for bootloader to initialize
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 (0x4) flags: 0
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x120002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
Click to expand...
Click to collapse
/home/christian/Arbeitsfläche/ICSv9/bootloader_apx.bin sent successfully
waiting for bootloader to initialize
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 (0x4) flags: 0
Click to expand...
Click to collapse
Reboot
Hello.
Very good job. Thank you.
But i don't know how to reboot.
Someone can help me?
Oberkellner said:
Tutorial - Flash ICS v9 Bootloader manually under Linux.
I am writing this tutorial, because I was unable to replace the HC 3.01 bootloader under Windows with the ICS Bootloader.
This is a translation from the German tutorial at Android-Hilfe.de written by me (aka Brickerl).
Preparation: Tablet must be in APX Mode.
Turn your table off!
Use a paper clip and press the Reset Button softly. You can feel a soft resistance.
As you press the Reset button hold also the Power button. Do this 3 seconds long.
Now release the power button and the paper clip.
The light of the powerbutton glows now white (at least it does for me) und the display is black.
Files needed (see attachment):
bct.bct
flash.cfg
nvflash for Linux
bootloader_apx.bin
bootloader_v9.bin
Your SBK number!
We write a script. I call it a500.sh.
Make a new file. e.g. with vi.
Code:
vi a500.sh
Write this into the script file.
Code:
#!/bin/sh
./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x12345678 0x12345678 0x12345678 0x12345678 --sync
Modify your SBK.
Make the file executable.
Code:
chmod +x a500.sh
Execute the scipt as root. Dont worry there is no flashing yet. If there are some status messages all is ok. Otherwise cancel NOW or your tablet is bricked afterwards.
The status messages can look like this.
Code:
# ./a500.sh
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0xxxxxxxxxxxxxx
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Step 5:
Now the actual flashing begins. We add 3 lines to the script.
Code:
#!/bin/sh
./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x12345678 0x12345678 0x12345678 0x12345678 --sync
[B]./nvflash -r --format_partition 4
./nvflash -r --download 4 bootloader_v9.bin
./nvflash -r --go
[/B]
The output can look like this:
Code:
# ./a500.sh
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0xxxxxxxxxxxxx
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
[B]Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
Nvflash started
[resume mode]
sending file: bootloader_v9.bin
| 1191932/1191932 bytes sent
bootloader_v9.bin sent successfully
Nvflash started
[resume mode]
[/B]
Ready. On the device „Pass“ is displayed and it can be rebooted.
Click to expand...
Click to collapse
Hello.
The flash was easy, thank you. but i can't reboot
Can you help me please?

[Q]PB Liberty Tab Recovery Help Needed Stuck

HI, I have been working on the PB Liberty Tab G100 for over a week.. I just want it back to stock.. no custom boot loaders or roms etc.. just so they can use it..
the story so far... I was asked to repair a PB liberty tab that was supposedly just freezing.. I think it had a custom boot V8..
Recovery was not working just getting the android dube with red triangle.. so installed thor recovery via fastboot..
tried the update method.. did not work.. tried everything.. but was having an issue with the wiping and formating...
I managed to finally get the cpuid by using a 64 bit version of ubuntu and have managed to get the SBK.. tried the recommended flashs A500 apx etc
but now i'm stuck in apx mode.. when i try to use V8-UNL-ICS-HC-bootloader-MULTI-cwm method I get the failed to format..
info found from this thread http://forum.xda-developers.com/showthread.php?t=1751978
**********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Press any key to continue . . .
Flashing HC-Bootloader...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
I think I have an internal storage issue, or bad sectors.. or I am just not using the right apx.. and help would be awesome..
i have read so many forum sections and pieced together which has finally got me into the device.. but now I seem to have hit a brick wall..
so help i have tried to track down the bad sectors software to run in apx mode but cant seem to find it al all the link i have found are dead..
quick update
**********************************************************
* Make your choise: *
*(1) ICS bootloader V8 with TWRP-2.1.3-ICS cwm(touch cwm)*
*(2) ICS bootloader V8 with PubRecovery-v0.2 (BareBones) *
*(3) ICS bootloader V8 with Thor-1.7cwm (touch cwm) *
*(4) ICS bootloader V8 with Thor-1.7.3 NEW cwm(touch cwm)*
* with its compatible recoveries. *
**********************************************************
(1 2 3 4):4
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c62484260****
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x60420
08) flags: 0
*****************************************************************
* Press any key when your A500/501/G100W is in bootloader mode *
*****************************************************************
Press any key to continue . . .
UPDATE
I have tried running Badsector but all i get it this.. I have checked the correct drivers are installed.. but just seem to be stuck..
I am thinking my internal storage is fried..
****************************************************************
* 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 :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0x****1E00 0x0**51700 0xEB*****2 0x682*****
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c624842601397
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 . . .

Acer a500 stuck in APX mode

Hi, I'm new to this forum and pretty much new to rooting/flashing tablets of any kind. I have a Acer a500 with stock rom which just broke down a couple of days ago for no reason. After much googling and searching this forum I have figured out that it is stuck in apx mode and I've tried everything I can to fix it but so far nothing has worked. Suffice it to say when I use nvflash I get this error.
C:\Users\user\Downloads\nvflash-A500>nvflash --bct bct.bct --setbct --bl bootl
oader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x6b721f00 0x6447ba0
1 0x8b0e5e03 0x48dd2003 --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c624340608197
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
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
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x5 (0x1000005) flags: 0
C:\Users\user\Downloads\nvflash-A500>nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
C:\Users\user\Downloads\nvflash-A500>nvflash -r --download 4 bootloader.bin
Nvflash started
[resume mode]
I assumed my partitions were corrupted so I've tried running babsector but am unable to start up in recovery mode after running a501 A.bat. I've also tried many other things but nothing has worked. Does anyone have any suggestions? I'd really appreciate any advice. Thanks!
procedure
for babsector to work you need to run A then reboot to APX mode - then run B if it shows an error than it will be a hardware failure
truthtrans said:
Hi, I'm new to this forum and pretty much new to rooting/flashing tablets of any kind. I have a Acer a500 with stock rom which just broke down a couple of days ago for no reason. After much googling and searching this forum I have figured out that it is stuck in apx mode and I've tried everything I can to fix it but so far nothing has worked. Suffice it to say when I use nvflash I get this error.
C:\Users\user\Downloads\nvflash-A500>nvflash --bct bct.bct --setbct --bl bootl
oader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x6b721f00 0x6447ba0
1 0x8b0e5e03 0x48dd2003 --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c624340608197
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
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
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x5 (0x1000005) flags: 0
C:\Users\user\Downloads\nvflash-A500>nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
C:\Users\user\Downloads\nvflash-A500>nvflash -r --download 4 bootloader.bin
Nvflash started
[resume mode]
I assumed my partitions were corrupted so I've tried running babsector but am unable to start up in recovery mode after running a501 A.bat. I've also tried many other things but nothing has worked. Does anyone have any suggestions? I'd really appreciate any advice. Thanks!
Click to expand...
Click to collapse
freightyard said:
for babsector to work you need to run A then reboot to APX mode - then run B if it shows an error than it will be a hardware failure
Click to expand...
Click to collapse
Thanks for replying. I ran A first and these were the results....
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c624340608197
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:0x
5 (0x1000005) flags: 0
Press any key to continue . . .
Then I shut down and restarted again....still in apx mode...and ran B...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c624340608197
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:0x
5 (0x1000005) flags: 0
Press any key to continue . . .
Just wanted to note that when I tried to flash using blackthund3rs apx flash tool my tablet shows a green acer logo in the middle of the screen and in the top left it says something like entering apx mode, but when I run the babsecter it has the normal white acer logo in the middle of the screen and in the top left it says entering acer download mode. Don't know if that is pertinent or not but just thought I'd mention it.
So from the results above does it sound like my tablet is just not going to be revived? Is it a hardware failure for sure?
hardware
looks like it
you could reflow the board just do a search in forum on reflowing for procedure

Resources