Database Users

nvflash linux hanging

Hi,
I've got into a mess with my Vega , and have been trying to use nvflash running on ubuntu linux to load the stock software onto the device.
Trouble is, regardless of what I try and flash - nvflash will just stop at various points during the flash procedure.
I've tried another ubuntu machine , just incase it was the USB port or something else. Same results.
Here is a sample output from nvflash :
Code:
[email protected]:/home/adam/soft# ./nvflash --bct H5PS1G83EFR-S6C_V24_0625.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x0b0c0075 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118741df4597
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: H5PS1G83EFR-S6C_V24_0625.bct
- 4080/4080 bytes sent
H5PS1G83EFR-S6C_V24_0625.bct sent successfully
odm data: 0xb0c0075
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 941512/941512 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MSC
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: USP
creating partition: UDA
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MSC 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!
Anyone have any ideas?

From your output everything looks OK to me.
Are you sure the linux command is correct?

I think so, its pretty much the same as the lvds.bat file from the stock installer.
Update - After countless tries I did manage to flash the stock ROM. I then applied modaco custom rom using adb.
Rebooting sometimes brings up android and sometimes black screens. Android seems to have problems all over the place. Wifi sometimes works sometimes doesn't. Will hang at random intervals.
Im thinking the NAND in the device is broken. Does this sound like the right conclusion?

[Q} Stuck in APX Mode

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

[Q] Help to unbrick my Acer a500

Hi i was looking for help on my iconia tab a500 everywhere, i've tried everything and don't get it to work, i try afterota, the blackthund3r, the timmy's help i try flashin bootloader, recovery, with babsector i ran the a502A Bat and give me this:
****************************************************************
* 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:0x7AAB1E00 0xB8CCE601 0x57850203 0x59042103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c6243416121d7
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
Presione una tecla para continuar . . .
then I ran the a501B and get this at the end
Formatting partition 2 BTC please wait.. FAILED¿
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7)
message: nverror:0x42008 (0x6042008) flags: 0
Presiones una tecla para continuar...
If someone can help me I appreciate it very much.
Thank you

I have reached the exact same point...for what I could found the issue is the internal SD damaged... only a MB change would be the solution...
sucks

[Q] A500 stuck in apx mode...cant find partiton 2 BTC

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 .

[Q] nvflash hangs formatting FCK partition

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