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] 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!

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.

[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] A500 unable to run ICS??

Hey guys and gals,
I have an Iconia a500 that has been rooted since I got it last December. It has run various 3.2 and 3.2.1 HC roms, then the ICS leaks, and most recently Skrillax's V* bootloader, with Civato's Re-Flexx roms. Just yesterday, I had a random reboot, and then another, but on the second one it wouldn't get past the "loading kernel image" screen. I've tried to EEU back to Vache's 3.0.1 then flash an official rom to get it back on to the official upgrade path, and have been successful, except when going to ICS. Once the official ICS install completes, it hangs on the Acer logo, requiring another EUU. I've also tried Blacktundr's APX tool at that point to go to V8+thor recovery, then flashing an ICS rom. same result.."loading kernel image".
The tablet is fine, as long as I stick with HC roms, and the HC bootloader. It will upgrade-path sucessfully thru 3.2.1, and even run Timmydean's rooted3.2.1, then an old HC rom of my choice. Just NO ICS .
Ideas? Maybe a partition error?

I believe there is a .zip or .rar file called Babsector with 2 .bat files in it that will help me if anyone has them?

ok so i found the babsector files, tried them.. Now i still cannot flash the bootloader with the APX tool.. tab runs fine with timmydean's rooted 3.2.1, but fails to OTA to ICS even. Ideas?

AtariDroid said:
ok so i found the babsector files, tried them.. Now i still cannot flash the bootloader with the APX tool.. tab runs fine with timmydean's rooted 3.2.1, but fails to OTA to ICS even. Ideas?
Click to expand...
Click to collapse
where does it fail on the bl flash, what error do u get?
failing to ota to ics from HC - go to thread how to revert to stock the easy way by jdgM3NT4L - there's a non-US update.zip i posted that worked for me. but until we figure out why u u can't flash the bl, you're stuck with stock.
Sent from my GT-I9300 using Tapatalk 2

Thanks for responding! it is good to hear from a voice of experience on the subject. I will copy/paste my results of various tries asap. I was able to flash the V8 bootloader a couple days ago. But since then i've tried a few methods to get to ics.. Including the Babsector .bats, maunually trying timmydean's and vache's EUUs, all fail at formatting BCT. The APX tools hang at uploading image(bootloader). I'm thinking i may have to do the Rawread technique to map out bad sectors, and place an FCK partition where they reside.... BUT i've not found exact instructions on how to get that to work yet. so for it seems to just hang, but iim sure i'm doing the rawread command wrong. win7x64 by the way.
I have of course uninstalled/ reinstalled and tried both driver versions out there also.
Any tips are greatly appreciated.

Here is a try with babsector's first .bat:
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x19000008) flags: 0

Next try.. same .bat:
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x5 (0x1000005) flags: 0

As i mentioned earlier, I'm guessing I have the failed EEMC memory problem. hoping to remap the partitions. Going to try to put an FCK first and see what happens.

After trying an FCK partition of 1000000 sectors in size..
Enter your SBK:0x94454C00 0x5FECC501 0x17A62103 0x7C302103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924842c045d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: FCK
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 15 FCK please wait.. done!
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 GP1 please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 MSC please wait.. done!
Formatting partition 11 FLX please wait.. done!
Formatting partition 12 AKB please wait.. done!
Formatting partition 13 UDA please wait.. done!
Formatting partition 14 GPT please wait.. done!
done!
sending file: bootloader_v8_green.bin
| 1191932/1191932 bytes sent
bootloader_v8_green.bin sent successfully
sending file: recovery.img
/ 5242880/5242880 bytes sent
recovery.img sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x8 (0x11000008)
flags: 0

Well.. this is definitely uncool.. I made a .bat that loads the bootloader from any upgrade package and runs the flash.cfg from it.. I've tried timmydean's V4, vache's 3.0.1, the babsector cfg's, and even the CES picasso version with it's huge bootloader. ALL are a no-go. My only chance seems to be to map out bad sectors with the Rawread command and try to put a dummy partition on top of them.. IF said partition doesn't fail on format.
Can someone explain the process on how to figure out what sectors are bad with the rawread comand?
I did get an error 12 a couple times before it even tried formatting on a few of my over 50 attempts.
Also.. if i am really screwed here.. anyone know of any broken a500's around that I may be able to buy a motherboard from?
Thanks everyone for your help so far. Without the countless threads I have gone through to learn what I have, I would still be sitting here scratching my head even more lol.

I'm not much help sorry, i guess you've read what there is regarding this.
there is a few posts from user 'yaworski' who managed to fix this in one of the old bootloader threads, thats all i can offer at this point. you might wanna pm him? or maybe blackthund3r or eppeP. wish u all the luck in getting fixed.
rgds dibb
Sent from my GT-I9300 using Tapatalk 2

Actually you have been a great help, as you have been a large part of many of the threads I have read on the subject
I see this post: http://forum.xda-developers.com/showpost.php?p=27456113&postcount=22... but I did not succeed in finding where they actually went through the process.
I've tried running the rawdeviceread command to find the bad sector/s, but I think i am loading the RAM bootloader(Timmydean's) wrong. I have been using the a501 A.bat to load the bootloader, then killing it where it waits for the bootloader to initilize. From there I open another command prompt window, but nvflash hangs at every command. I'm not very well versed in Nvflash, as I only know what I have seen here and at Tegraowners.
Can someone tell me how to load the bootloader without having it execute any commands? That way I can run the rawdeviceread command and maybe figure out how to go from there. I also need to know if there is a way to create a partition without formatting it(I think that is automatic?). That way I can create the dummy FCK partition over the bad sector/s and skip it so the others can create/format successfully.

Re: [INFO/DEV] A500 ICS Bootloader (plus unlocked patched version)
oops just annihilated my post...and links to couple early bootloader threads, useful info really bct error....
apxflash tool allows you to dump your bct so you can nvflash - as long as your tab enters download mode and the apx usb device is showing up, go ahead and flash it -
Theres lots of info in some of the older bootloader threads http://forum.xda-developers.com/showthread.php?t=1514951)??? well worth a read
sp3dev said:
I have uploaded the archive with nvflash and some instructions on using it with A500. This is only intended for hardcore geeks who know how ARM boots. Be careful - while you can't really brick tegra2 (since it has a minimal usb-capable bootloader in the OTP area), you can screw up things and it will be quite hard to force the tablet to boot in some cases due to stupid security checks.
You can use this to download any bootloader/recovery/linux you want. That will help us with porting uboot. Someone may even write an automated tool for reflashing bootloaders and unbricking tablets..
http://www.mediafire.com/?pp97x9aahs58hzp
Let me just copy-paste the README from the archive here.
1. First, generate your sbk with http://vache-android.com/v1/index.php?site=sbk
2. Then, get a hold of mmcblk0 start sectors (at least 4KB) and copy it to mmcblk0_start
3. run the ./rip_bct.sh script and supply it with your SBK to rip BCT (boot config table. contains ram timings among other things)
4. run ./download.sh to connect nvflash to iconia (do it in APX mode). Note that you also need to supply your SBK here, but not as a long single number, but as it is displayed on the website
5. You can now play with nvflash - for example, read partitions, partition table and write your own flash_ic.cfg with partition layout
6. If you flash linux/recovery, make sure to update the magic values (like itsmagic does).
To do it, first download the 12th partition (AKB)
then, in the akb.bin, at address 0x84, replace 4 16-byte entries with the same pattern
"00 FB 30 94 99 01 4F 97 2E 4C 2B A5 18 6B DD 06"
ok, you need to patch the file once and can use it in further flashing. Just upload it to the device (like sign.sh does)
POTENTIAL PITFALLS. Listen up, I ain't gonna help you if you eff up here.
1. You must use BCT from your device Otherwise, the bootloader will not boot.
You will still be able to use NVFLASH, but until you dump your own BCT and use it
with NVFLASH, the device will not be booting again
2. If you use the ./iconia_boot.bin that differs from the bootloader on your
device, the device will get stuck in the APX mode after a reboot. If you do it,
flash the new ./iconia_boot.bin to the device (to the partition 4).
.
Click to expand...
Click to collapse
Sent from my GT-I9300 using Tapatalk 2

Ok hoping to try again tonight. thanks for your help!