Database Users

[RESOLVED] yet another Bricked thread, although I'm not sure if I'm really bricked!

In an attempt to flash the new Revolution ROM (I had reverted back to stock ROM last week, which unrooted my TF101), I rooted with ViperMOD, which seemed to work fine, then I installed CWM 5.5.0.4, and flashed the recovery. I can now boot into CWM recovery, but it does not recognize my external MicroSD card, it only seems to see the internal card, so I cannot flash anything. Rebooting sits at the Eee Pad splash screen.
I saw the thread titled “[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush” but I don’t think this is necessarily my issue and I cannot seem to get a connection with my TF101 from my PC when in CWM recovery.
Thanks!
PS - If i could just get CWM to recognize my external microsd card I think I could flash Revolution without an issue

Well 5.5.0.4 is buggy and only reads from the internal sdcard which is the opposite problem of the past. You're not bricked, which is the good news. If you know how to use adb just push a rom to your /media/sdcard and use cwm to flash it; otherwise use nvflash. Make sure you revert back to an earlier cwm after.

haberda said:
Well 5.5.0.4 is buggy and only reads from the internal sdcard which is the opposite problem of the past. You're not bricked, which is the good news. If you know how to use adb just push a rom to your /media/sdcard and use cwm to flash it; otherwise use nvflash. Make sure you revert back to an earlier cwm after.
Click to expand...
Click to collapse
Thanks! Is there a dummy how to for ADB somewhere?

Well, I attempted to use NVFlash from this post http://forum.xda-developers.com/showthread.php?t=1123429
And now I am completely dead, cannot power on or anything

gbatt said:
Thanks! Is there a dummy how to for ADB somewhere?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1071584
gbatt said:
Well, I attempted to use NVFlash from this post http://forum.xda-developers.com/showthread.php?t=1123429
And now I am completely dead, cannot power on or anything
Click to expand...
Click to collapse
Your TF might still be in APX mode. Try pushing and holding power button till it reboot.

That does seem to be the case as I can still connect to it from my PC and run NVFlash on it, which I've done twice now, However, I still am unable to reboot. I tried holding down the power button for several minutes and it does not respond.
EDIT: Adb doesn’t seem to be an option here anymore. I installed and attempted to connect using the tutorial thread posted above, but the device isn’t seen.
I do believe it is permanently stuck in APX mode as I am watching the list of ‘Universal Serial Bus Controllers’ in my Device Manager on my PC and when I hold down the power button the device ‘NVIDIA USB Boot-recovery driver for Mobile devices’ disappears for an instant and then comes right back. It seems like it is constantly booting into APX.
I wonder if there’s something I can do with NVFlash since that seems to be able to still communicate with the device.

Here are the results of NVFlash. I was lucky to get a copy of it as the widows disappears pretty quickly. I don't know if this is useful at all but her it is anyway. Seems like it finishes fine, I just cant boot to anything afterwards.
C:\temp\ROMS\nvflashtf>"nvflash.exe" --bct transformer.bct --setbct --configfile
flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x
8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0380620942e0d657
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: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully

So I'm an idiot, it looks like NVFLash is failing and I didn't even notice it. I am getting this error at the end:
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Am I supposed to have a recovery.img file somewhere for it to load?

I did the same thing. Running nvflash like that is pretty much wiping your Transformer.
What I did was to get the Prime nvflashable ROM and extract it into nvflash root directory. You then get a working machine you can flash any other ROM on.

gbatt said:
So I'm an idiot, it looks like NVFLash is failing and I didn't even notice it. I am getting this error at the end:
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Am I supposed to have a recovery.img file somewhere for it to load?
Click to expand...
Click to collapse
You should have boot.img, recovery.img and system.img in the NVFlash folder.
You might have a tf without an OS if you ran nvflash without a system.img.
Here's ICS in nvflash version
http://forum.xda-developers.com/showthread.php?t=1524302

Thanks guys! That did it! I'm back in action!

Hey guys, I was using ALL in ONE tool I was trying to get new partition (ICS) for my Optimus 2X
and then I got that Error:
lgdrm.img sent successfully
file not found: ics-recovery.img
failed executing command 2147483647
NvError 0x4 command failure: create failed
Then I tried to Bring back old partition (GB)
was same result only was GB-recovery.img not found...
It looks like its bricked, cant power on ... any help pleasE?

Jenkis said:
Hey guys, I was using ALL in ONE tool I was trying to get new partition (ICS) for my Optimus 2X
and then I got that Error:
lgdrm.img sent successfully
file not found: ics-recovery.img
failed executing command 2147483647
NvError 0x4 command failure: create failed
Then I tried to Bring back old partition (GB)
was same result only was GB-recovery.img not found...
It looks like its bricked, cant power on ... any help pleasE?
Click to expand...
Click to collapse
Dude I think your in the wrong Forum.......

Tutorial - Recover B70+ in Windows & NVFlash Info

First of I take no credit for the software used. All goes to AndroidRoot.Mobi!
First of I have:
Windows 7 32BIT
wheelie.zip from - androidroot.mobi/?p=367
WW_epaduser9_2_1_24UpdateLauncher.zip - Original ASUS Firmware from site
Step1:
Extract the wheelie.zip to folder
Extract the WW_epaduser9_2_1_24UpdateLauncher.zip to folder
Step2:
Go into the extracted firmware folder and extract WW_epad-user-9.2.1.24.zip.
You will now see an file called blob in that same folder depending on how you extracted.
Step3:
Copy the blob file into your extracted wheelie.zip folder, into the root directory of it.
Step4:
Open windows command line and cd to the extracted wheelie folder
Example:
cd C:\Users\myName\Desktop\Wheelie
Step5:
If you are now in the root directory of your wheelie folder where all the other files nvflash etc are you can go forward.
Type: "blobunpack blob" in the command line without ""
Now in the wheelie folder you will see 4 new files named:blob.SOS,blob.LNX etc.
Step6:
Connect tablet to pc and put your tablet into APX mode. Volume UP and Power button.
Your computer should make an sound to confirm that it is connected.
Step7:
Check in device manager, under Universal Serial Bus Controller for the Nvidia Recovery something something device. I am not going to explain how to install the APX Drivers or how to put it in APX further. Search the forum.
Step8:
If you can confirm the drivers are correct and connected now in the command line type: "reflash_sbkv2.bat" without the "".
Wait for the process to complete if all the steps was followed correctly it should work out fine.
Again thanks to all the developers whom made the recovery possible:
Bumble-Bee, IEF, kmdm, lilstevie & RaYmAn
As kenshin1388 mentioned, THIS WILL WIPE EVERYTHING!
Some NVFlash information:
Nvflash started
nvflash action [options]
action (one or more) =
--help (or -h)
displays this page
--cmdhelp cmd(or -ch)
displays command help
--resume (or -r)
send the following commands to an already-running bootloader
--quiet (or -q)
surpress excessive console output
--wait (or -w)
waits for a device connection (currently a USB cable)
--create
full initialization of the target device using the config file
--download N filename
download partition filename to N
--setboot N
sets the boot partition to partition N
--format_partition N
formats contents of partition N
--read N filename
reads back partition N into filename
--getpartitiontable filename
reads back the partition table into filename
--getbit filename
reads back BIT into filename
--getbct
reads back the BCT from mass storage
--odm C Data
ODM custom 32bit command 'C' with associated 32bit data
--go
continues normal execution of the downloaded bootloader
options =
--configfile filename
indicates the configuration file used with the following commands:
--create, --format_all
--bct filename
indicates the file containing the BCT
--sbk 0x00000000 00000000 00000000 00000000
indicates the secure boot key for the target device
--bl filename
downloads and runs the bootloader specified by filename
--odmdata N
sets 32bit customer data into a field in the BCT, either hex or
decimal
--diskimgopt N
sets 32bit data required for disk image convertion tool
--format_all
formats all existing partitions on the target device using the config file,
including partitions and the bct
--setbootdevtype S
sets the boot device type fuse value for the device name.
allowed device name string mentioned below:
emmc, nand_x8, nand_x16, nor, spi
--setbootdevconfig N
sets the boot device config fuse value either hex or decimal
--verifypart N
verifies data for partition id = N specified. N=-1
indicates all partitions
Intended to be used with --create command only.
--setbct
updates the chip specific settings of the BCT in mass storage to
the bct supplied,used with --create, should not be with --read,and
--format(delete)_all,format(delete)_partition,--download, and--read
--sync
issues force sync commad
--rawdeviceread S N filename
reads back N sectors starting from sector S into filename
--rawdevicewrite S N filename
writes back N sectors from filename to device starting from sector S
The reference to your partitions all depend on the flash.cfg file located in the folder.
Extraction from wheelie's flash.cfg
[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.EBT
[partition]
name=SOS
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.SOS
In order to create your own script:
Step1:
Create a new text file and rename it to .bat. script.txt -> script.bat.
Step2:
Now edit it, include the first two lines required to prepare for nvflash commands
cd %~dp0
"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
Step3:
Now lets add anything extra we want the script to do.
cd %~dp0
"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
"nvflash.exe" -r --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
"nvflash.exe" -r --bct transformer.bct --download 5 recovery.img --sync
This script will only reflash your recovery with another recovery image. I used this just to explain the relation between the config.cfg file and your partitions, the script should also work but I have not tested it.
Another method that should be useful is just modifying the flash.cfg file to only include the partitions we want flashed. Then running the original script that uses --create. Can somebody confirm this?
THIS IS AT YOUR OWN RISKS!

Great first post, thanks!
So these steps should be the solution if your Transformer doesn't boot anymore for whatever reason (probably after installing some ROM)?
Very detailed description, I think now I can root my TF 101 sbk v2 to install CM9 or something else, if there is this not too difficult way to get it back to life if something goes wrong.

Thanks for this, like a fool I was using the renamed blob files from the original nvflash and not the original blob file names.

Thanks, I can confirm that it does recover your tablet. Recovered mine from an soft brick. Also had a pretty bad moment where not even the phone will start\boot up only APX mode.
To root the tablet just use [GUIDE/TOOL] [EASY] PERI-V0.3: One click root+recovery! (Works with .24!).
I cant post links yet.
I recovered my tablet, root, and then flashed latest HD Revolution Rom. Everything working perfectly!

I would definitely warn everybody that this is not a recommended method to return to stock as it wipes internal storage. I did that a couple days after a soft brick and was disappointed to find all my movies missing. Gotta go find all my DVDs again.
Sent from my Transformer TF101 using xda premium

kenshin1388 said:
I would definitely warn everybody that this is not a recommended method to return to stock as it wipes internal storage. I did that a couple days after a soft brick and was disappointed to find all my movies missing. Gotta go find all my DVDs again.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Thread Updated. Any other method then that will work better and not have data loss?

Franz.Hendrik said:
Thread Updated. Any other method then that will work better and not have data loss?
Click to expand...
Click to collapse
Ill do some looking and see if I can figure out what partition the internal storage is. I believe there is an nvflash command to format a specific partition, so it shouldn't be hard to make an script to format manually and then flash. I'm still new to nvflash though lol.
Sent from my Transformer TF101 using xda premium

NvFlash just the EBT and SOS partitions (Bootloader and Recovery) and you'll save your internal storage. mmcblk0p4 is the partition I believe. I'll make a video guide sometime today to recover from soft-bricks.

looking for this
I looking for this in a few days. Thanks man.

Thing O Doom said:
NvFlash just the EBT and SOS partitions (Bootloader and Recovery) and you'll save your internal storage. mmcblk0p4 is the partition I believe. I'll make a video guide sometime today to recover from soft-bricks.
Click to expand...
Click to collapse
I'm on Revolver 4.0.3 RC3, I would like to flash ubuntu on dual boot, but I don't want to loose any data from Android. If only someona could point out a small how to would be very nice. nvflash rules

Got up to the command to flash SBKV2 and I get "connection failed nv error 0x30011"

Make sure the tablet is in APX mode power + volume up

pkfox said:
Make sure the tablet is in APX mode power + volume up
Click to expand...
Click to collapse
It was definitely in APX mode. heard the PC connect. shows its connected as an APX device.
Am I supposed to flash the sbkv2 no matter what? or is my problem I need to flash sbkv1?
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>reflash_sbkv2.bat
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>cd C:\Users\Spoo\Desktop\Desktop folder\TF101\whe
elie\
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl boot
loader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x252309624468846103
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct -
-configfile flash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
connection failed NvError 0x30011
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
connection failed NvError 0x30011
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>
Click to expand...
Click to collapse
---------- Post added at 02:57 PM ---------- Previous post was at 02:51 PM ----------
Well I feel dumb. I needed to flash SBKV1 it seems. looks like its working.
see what happens when you try to gain root late at night?

Glad you sorted it, I think I read that some B70 models have sbk1 that would explain things

Hi,
I have a TF101G B80. It doesn't matter which version I try to flash. Either SBK1 or SBK2. I always get
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199388248982231
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Unfortunately my device is bricked. So Wheelie was my last hope...
Does anyone have an idea? Thank you very much.
Steve

sscde said:
I have a TF101G
Click to expand...
Click to collapse
Wheelie does not support TF101G units, they have yet another Secure Boot Key.

first time I've had hope in a while...
so a family member, on recommendation of mine, bought a Transformer around Christmas for his wife. They hardly used it, know nothing about tablets or android, and have managed to brick it. Since I'm the family tech guy (only because I am the youngest member of the family) I am stuck figuring out how to fix this. I'm fairly competent working through Windows, but hardly any with Linux.
They upgraded to the latest version of android around mid-May and have been stuck in boot-loop hell since, occasionally turning on and off on its own. After hours and hours of searching, I found this thread and thought I found my solution...but I'm still stuck in boot loop.
The serial sticker is not on the tablet, so I can not confirm what version it is, however I have tried to flash both sbkv1 and 2 and it will ONLY flash sbkv2. Using the tutorial here, everything seemed to work fine, but I am still stuck on the boot screen. I've copied the log here and any assistance would be greatly appreciated.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Anthony>cd c:\asus\wheelie
c:\ASUS\wheelie>blobunpack blob
Header size: 60
4 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: EBT
Offset: 124 (0x7C)
Size: 1454712 (0x163278)
Writing file blob.EBT (1454712 bytes)
Partition 1
Name: SOS
Offset: 1454836 (0x1632F4)
Size: 4284416 (0x416000)
Writing file blob.SOS (4284416 bytes)
Partition 2
Name: LNX
Offset: 5739252 (0x5792F4)
Size: 4151296 (0x3F5800)
Writing file blob.LNX (4151296 bytes)
Partition 3
Name: APP
Offset: 9890548 (0x96EAF4)
Size: 536870912 (0x20000000)
Writing file blob.APP (536870912 bytes)
c:\ASUS\wheelie>reflash_sbkv1.bat
c:\ASUS\wheelie>cd c:\ASUS\wheelie\
c:\ASUS\wheelie>"wheelie.exe" -1 --bct transformer.bct --bl bootloader.bin --od
m 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199401146529303
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
c:\ASUS\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fla
sh.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
c:\ASUS\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
c:\ASUS\wheelie>reflash_sbkv2.bat
c:\ASUS\wheelie>cd c:\ASUS\wheelie\
c:\ASUS\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --od
m 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199401146529303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
c:\ASUS\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fla
sh.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
c:\ASUS\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
c:\ASUS\wheelie>
Click to expand...
Click to collapse

I am sorry for being offline a while now , thank you vodascum for my bad data connections.
Did you check that the files (image files) you are flashing is the correct files?
Can you enter recovery?

Franz.Hendrik said:
I am sorry for being offline a while now , thank you vodascum for my bad data connections.
Did you check that the files (image files) you are flashing is the correct files?
Can you enter recovery?
Click to expand...
Click to collapse
I downloaded the image files directly from the Asus site, so I would hope they're correct, but I don't know how to check.
I can not enter recovery

Any help? I'd really appreciate it

Unrooting the Transformer with the nvflash

Hi everyone!
I´m following this guide here: tabletroms.com/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
At the moment I am trying to bring my Transformer back to it´s original state. My specs are:
TF101, bought in Germany
Serial number B50[...]
Rooted and encrypted
So, when i try to use the method described in the thread i get the folowing output:
Code:
"nvflash.exe" --bct transformer.bct --setbct --co
nfigfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x168
2CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c61c4415f4557
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
- 1361037/1361037 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: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: bootloader.bin
- 1361037/1361037 bytes sent
bootloader.bin sent successfully
sending file: recovery.img
/ 3930112/3930112 bytes sent
recovery.img sent successfully
sending file: boot.img
\ 3518464/3518464 bytes sent
boot.img sent successfully
sending file: system.img
/ 19660800/536870912 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
The device-screen shows this:
Code:
Entering NvFlash recover ymode / Nv3p Server
!!!!! device update failed !!!!!
I am 100% sure that the image i download is not corrupted (md5 checked) and i also get this with all 3 version i already tried (3.2 Build of 8.6.5.13, 3.2 Build 8.6.5.9 and the earliest 3.1 build 8.4.4.5.
What am I doing wrong?
Thanks in advance!
[Edit] I didn´ t connect the device with a root-USB-Port but via a HUB. Did that, now it works.

Rogue Recovery, then blank

so I have managed to use Wheelie to get Rogue recovery on my TF101, but then I get nowhere.
I originally tried installing ClockworkMod via Wheelie, had trouble, then finally got Rogue to load, tried to install CM9 from the SDcard (which says the update is succesful), but when I reboot, I get the blank screen again. Am I missing something in my steps to try to get this back up and running? Here's my log:
PHP:
c:\ASUS>cd c:\asus\wheelie
c:\ASUS\wheelie>reflash_sbkv2
c:\ASUS\wheelie>cd c:\ASUS\wheelie\
c:\ASUS\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --od
m 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199401146529303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
c:\ASUS\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fla
sh.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: bootloader.bin
| 1454712/1454712 bytes sent
bootloader.bin sent successfully
sending file: recovery.img
| 4599808/4599808 bytes sent
recovery.img sent successfully
file not found: boot.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
c:\ASUS\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
c:\ASUS\wheelie>wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199401146529303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
c:\ASUS\wheelie>nvflash -r --download 5 recovery.img
Nvflash started
[resume mode]
sending file: recovery.img
| 4599808/4599808 bytes sent
recovery.img sent successfully
c:\ASUS\wheelie>nvflash -r --go
Nvflash started
[resume mode]
c:\ASUS\wheelie>
I have a feeling it has something to do with (along with my very modest knowledge of development) this part:
PHP:
file not found: boot.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Could this be the issue that's causing all my troubles? If so, could someone please help me out? I really appreciate any assistance, thanks a lot in advance.
PS - it should be noted, this tablet's never been rooted; I was under the impression that if I managed to get into a custom recovery, that I was rooted, but I'm probably wrong.

Check to see if rouge recovery is actually installed. Power and volume down to turn it on, hit volume up when it prompts you. If it comes up, just flash the cm9 zip that way.

darkstknight1523 said:
PS - it should be noted, this tablet's never been rooted; I was under the impression that if I managed to get into a custom recovery, that I was rooted, but I'm probably wrong.
Click to expand...
Click to collapse
Use PERI by Thing O Doom to root and install custom recovery.
http://forum.xda-developers.com/showthread.php?p=26737790

bfmetcalf said:
Check to see if rouge recovery is actually installed. Power and volume down to turn it on, hit volume up when it prompts you. If it comes up, just flash the cm9 zip that way.
Click to expand...
Click to collapse
I guess Rogue isn't actually installed. After powering down, the screen stays blank, never prompted to do anything.

baseballfanz said:
Use PERI by Thing O Doom to root and install custom recovery.
http://forum.xda-developers.com/showthread.php?p=26737790
Click to expand...
Click to collapse
I don't think I'm grasping how to use PERI, if you could be so kind and explain the steps on how to install, I would really appreciate it. Thanks.

Dude. Your error is due to some missing boot.img.
While flashing, wheelie couldn't locate any boot image for flashing (xy_blob.SOS) the SOS partition. If SOS is not flashed, your device cannot boot, cause you have no kernel, because wheelie formatted all your partitions in the previous step.
Easiest way to fix is to do a full reflash of your wheeliedirectory with correct files in it, or, if requested, I can send you the boot image from my kernel to flash with wheelie.
-Rayman

Just download the file
Unzip it to a folder
Connect the TF to the PC
Open the folder that you just unzip PERI to
Click on the EasyRecoveryV0.4.bat file
Follow what the screen ask.

rayman33 said:
Dude. Your error is due to some missing boot.img.
While flashing, wheelie couldn't locate any boot image for flashing (xy_blob.SOS) the SOS partition. If SOS is not flashed, your device cannot boot, cause you have no kernel, because wheelie formatted all your partitions in the previous step.
Easiest way to fix is to do a full reflash of your wheeliedirectory with correct files in it, or, if requested, I can send you the boot image from my kernel to flash with wheelie.
-Rayman
Click to expand...
Click to collapse
Rayman, a name that I've seen on the forums many times, your reputation precedes you. Thanks for the response.
If you could assist in any way possible I'd really appreciate it. Could you send me the boot image from your kernel so I can try to flash it with Wheelie? Do I need to PM you or is it something you can post here?

darkstknight1523 said:
Rayman, a name that I've seen on the forums many times, your reputation precedes you. Thanks for the response.
If you could assist in any way possible I'd really appreciate it. Could you send me the boot image from your kernel so I can try to flash it with Wheelie? Do I need to PM you or is it something you can post here?
Click to expand...
Click to collapse
Okay, assuming you want to flash an ASUS-based rom (or even stock), here is a correct boot image.
The attached file is kernelblob.LNX.zip.
Just extract the zip and you'll get the kernelblob.LNX.
Move the unpacked LNX file to your wheelie directory and do the following ...
Boot up wheelie and start nvflash in resume mode :
Code:
sudo ./nvflash -r --download 6 kernelblob.LNX
Code:
sudo ./nvflash -r --go
Now it should boot atleast.
I am attaching my TWRP recovery here too, might be helpful. To install, do
Code:
sudo ./nvflash -r --download 5 recoveryblob.SOS
Code:
sudo ./nvflash -r --go
Remember, extract files from the zips and push them to your wheelie directory, else files won't be detected by nvflash.

Rayman, thanks for the help, but maybe I'm just not grasping it.
I downloaded the Asus firmware (US_epad-user-9.2.1.24.zip) and extracted the files to the Wheelie directory; (1 folder called META-INF and a file called blob).
I then opened my cmd window and unpacked the blob file with blobunpack
PHP:
blobunpack blob
that created (4) files called blob.APP, blob.EBT, blob.LNX, and blob.SOS.
I downloaded your files and extracted them both into the wheelie directory.
I ran wheelie (at least I think I am running wheelie) by using
PHP:
wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
I then I ran the commands you instructed and it appeared everything went fine, unfortunately, I am still with nothing. Maybe you can dissect what I'm doing wrong through the log:
PHP:
c:\ASUS\wheelie>blobunpack blob
Header size: 60
4 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: EBT
Offset: 124 (0x7C)
Size: 1454712 (0x163278)
Writing file blob.EBT (1454712 bytes)
Partition 1
Name: SOS
Offset: 1454836 (0x1632F4)
Size: 4284416 (0x416000)
Writing file blob.SOS (4284416 bytes)
Partition 2
Name: LNX
Offset: 5739252 (0x5792F4)
Size: 4151296 (0x3F5800)
Writing file blob.LNX (4151296 bytes)
Partition 3
Name: APP
Offset: 9890548 (0x96EAF4)
Size: 536870912 (0x20000000)
Writing file blob.APP (536870912 bytes)
c:\ASUS\wheelie>wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199401146529303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
c:\ASUS\wheelie>nvflash -r --download 6 kernelblob.LNX
Nvflash started
[resume mode]
sending file: kernelblob.LNX
/ 4173824/4173824 bytes sent
kernelblob.LNX sent successfully
c:\ASUS\wheelie>nvflash -r --download 5 recoveryblob.SOS
Nvflash started
[resume mode]
sending file: recoveryblob.SOS
| 4907008/4907008 bytes sent
recoveryblob.SOS sent successfully
c:\ASUS\wheelie>nvflash -r --go
Nvflash started
[resume mode]
I am so very frustrated but hope you can see what I'm doing wrong.

baseballfanz said:
Just download the file
Unzip it to a folder
Connect the TF to the PC
Open the folder that you just unzip PERI to
Click on the EasyRecoveryV0.4.bat file
Follow what the screen ask.
Click to expand...
Click to collapse
thanks baseballfanz, but this isn't working for me either, I connect the TF to the PC and it recognizes it as an APX device. I then try to run the .bat and it doesn't see my device.

I am wondering if it is a hardware problem at this point. I've been noticing that even though I power off the tablet, it automagically reconnects to the PC as an APX device without me trying to turn the tablet back on.
Any thoughts on this being the culprit or am I just a fool who can't get this right?

darkstknight1523 said:
Rayman, thanks for the help, but maybe I'm just not grasping it.
I downloaded the Asus firmware (US_epad-user-9.2.1.24.zip) and extracted the files to the Wheelie directory; (1 folder called META-INF and a file called blob).
I then opened my cmd window and unpacked the blob file with blobunpack
PHP:
blobunpack blob
that created (4) files called blob.APP, blob.EBT, blob.LNX, and blob.SOS.
I downloaded your files and extracted them both into the wheelie directory.
I ran wheelie (at least I think I am running wheelie) by using
PHP:
wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
I then I ran the commands you instructed and it appeared everything went fine, unfortunately, I am still with nothing. Maybe you can dissect what I'm doing wrong through the log:
PHP:
c:\ASUS\wheelie>blobunpack blob
Header size: 60
4 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: EBT
Offset: 124 (0x7C)
Size: 1454712 (0x163278)
Writing file blob.EBT (1454712 bytes)
Partition 1
Name: SOS
Offset: 1454836 (0x1632F4)
Size: 4284416 (0x416000)
Writing file blob.SOS (4284416 bytes)
Partition 2
Name: LNX
Offset: 5739252 (0x5792F4)
Size: 4151296 (0x3F5800)
Writing file blob.LNX (4151296 bytes)
Partition 3
Name: APP
Offset: 9890548 (0x96EAF4)
Size: 536870912 (0x20000000)
Writing file blob.APP (536870912 bytes)
c:\ASUS\wheelie>wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199401146529303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
c:\ASUS\wheelie>nvflash -r --download 6 kernelblob.LNX
Nvflash started
[resume mode]
sending file: kernelblob.LNX
/ 4173824/4173824 bytes sent
kernelblob.LNX sent successfully
c:\ASUS\wheelie>nvflash -r --download 5 recoveryblob.SOS
Nvflash started
[resume mode]
sending file: recoveryblob.SOS
| 4907008/4907008 bytes sent
recoveryblob.SOS sent successfully
c:\ASUS\wheelie>nvflash -r --go
Nvflash started
[resume mode]
I am so very frustrated but hope you can see what I'm doing wrong.
Click to expand...
Click to collapse
It still can't boot, because no rom is installed. But I see my files where flashed succesfully, so please try to get into recovery by holding Power+volume down, then volume up... from there, you can install any flashable zip..

rayman33 said:
It still can't boot, because no rom is installed. But I see my files where flashed succesfully, so please try to get into recovery by holding Power+volume down, then volume up... from there, you can install any flashable zip..
Click to expand...
Click to collapse
I tried to get into recovery by holding Power+volume down, but nothing happens. Should be doing this while it is connected to the PC? When I attempt to power down while connected to the PC, I hear the notification that it has been disconnected, I immediately release the button, but then hear it reconnect as an APX device. I have had experience flashing ROMs to my other tablets and phones, but I've never had the problem of not being able to get into recovery before.
Are there any other files I should have in my wheelie folder other than these:
PHP:
Directory of c:\ASUS\wheelie
07/13/2012 10:14 PM <DIR> .
07/13/2012 10:14 PM <DIR> ..
07/13/2012 10:12 PM 546,761,460 blob
07/13/2012 10:20 PM 536,870,912 blob.APP
07/13/2012 10:20 PM 1,454,712 blob.EBT
07/13/2012 10:20 PM 4,151,296 blob.LNX
07/13/2012 10:20 PM 4,284,416 blob.SOS
05/31/2012 04:58 PM 58,880 blobunpack.exe
06/05/2011 04:43 PM 943,193 bootloader.bin
05/31/2012 05:02 PM 3,172 flash.cfg
07/13/2012 09:04 PM 4,173,824 kernelblob.LNX
05/31/2012 04:48 PM 18,944 libnv3p.dll
05/31/2012 04:48 PM 12,288 libnvaes_ref.dll
05/31/2012 04:48 PM 80,384 libnvapputil.dll
05/31/2012 04:48 PM 9,728 libnvboothost.dll
05/31/2012 04:48 PM 45,056 libnvdioconverter.dll
05/31/2012 04:48 PM 23,040 libnvflash.dll
05/31/2012 04:48 PM 28,160 libnvos.dll
05/31/2012 04:48 PM 10,752 libnvusbhost.dll
07/13/2012 10:10 PM <DIR> META-INF
05/31/2012 04:48 PM 135,168 nvflash.exe
07/13/2012 09:05 PM 4,907,008 recoveryblob.SOS
05/31/2012 04:49 PM 218 reflash_sbkv1.bat
05/31/2012 04:53 PM 218 reflash_sbkv2.bat
06/05/2011 04:43 PM 4,080 transformer.bct
05/31/2012 05:21 PM 196,608 wheelie.exe
23 File(s) 1,104,173,517 bytes
3 Dir(s) 43,178,803,200 bytes free
c:\ASUS\wheelie>
Am I following the steps correctly?

thinking of throwing in the towel
I am considering just bringing the tablet back to Best Buy and hopefully exchange it for a replacement. I can't seem to get things in order and back up and running. Each time I think I'm close, I get the same result and frustrates me. If anyone else has a suggestion, I'd love to hear it.

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