Database Users

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

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

Borked...even with Wheelie

After days of searching the XDA and other forums, I still am having a hell of a time trying to get straightened out. I know it's probably a dumb oversight on my part, but I can't seem to get this tablet up and running again.
I advised my uncle (he's not tech savvy) to purchase one of these from Best Buy after I had bought 2 myself (I've had NO problems with my tabs, nor have the other 4 people I've recommended them to), he updated the stock firmware about a month ago, hasn't worked since; boot loops, spinning wheel, never booted back up into the UI. It was never fooled with and was running stock OS when it went down, but unfortunately I can't see what version it was, nor can I see what firmware was last on it as I can't get into the UI. The serial sticker has fallen off to further aggravate the situation.
I followed the instructions for Wheelie seen here on XDA. All seems to work out, until the end; I can't get booted into recovery and I get this screen:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 037c708641213617
!!!!!phone update success!!!!!
!!!!!phone update success!!!!!
Click to expand...
Click to collapse
I attempt to reboot (as per the instructions) and it gets me nowhere; I have attached the log and hope someone could be kind to help me out. I really appreciate any assistance.
PHP:
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-clockwork-5.8.3.4-tf101.img.SOS
Nvflash started
[resume mode]
sending file: recovery-clockwork-5.8.3.4-tf101.img.SOS
| 4360192/4360192 bytes sent
recovery-clockwork-5.8.3.4-tf101.img.SOS sent successfully
c:\ASUS\wheelie>nvflash -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>blobunpack recovery-clockwork-5.8.3.4-tf101.img
Header size: 60
1 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: SOS
Offset: 76 (0x4C)
Size: 4360192 (0x428800)
Writing file recovery-clockwork-5.8.3.4-tf101.img.SOS (4360192 bytes)
c:\ASUS\wheelie>nvflash -r --download 5 recovery-clockwork-5.8.3.4-tf101.img.SOS
Nvflash started
[resume mode]
sending file: recovery-clockwork-5.8.3.4-tf101.img.SOS
| 4360192/4360192 bytes sent
recovery-clockwork-5.8.3.4-tf101.img.SOS sent successfully
c:\ASUS\wheelie>nvflash -r --go
Nvflash started
[resume mode]
Am I doing something wrong? Should I just raise the white flag and bring the tablet back to B*stB*y and try to have them exchange it? Any help is greatly, greatly appreciated.

It looks like wheelie flashed only your bootloader and recovery partitions (it pushed clockworkmod), so you'd need to reboot into recovery (power+volume down until you see the text in the upper left corner of the screen, then press volume up) and flash a ROM from there.

wingzero2085 said:
It looks like wheelie flashed only your bootloader and recovery partitions (it pushed clockworkmod), so you'd need to reboot into recovery (power+volume down until you see the text in the upper left corner of the screen, then press volume up) and flash a ROM from there.
Click to expand...
Click to collapse
thanks for the response, I tried what you suggested, but the screen stays blank when I try to reboot into recovery. While connected to the PC (a Windows 7, 64 bit b.t.w.) it does show up as an APX device. Is there another way about this? Could it be a hardware issue?

darkstknight1523,
are you flashing the ROM Manager version of CWM recovery? If so that could be your problem. I saw a lot of issues with that on the forum. Try Rogue's CWM or anyhing but the one supplied by ROM manager.
greetz,
Speedstra

Speedstra said:
darkstknight1523,
are you flashing the ROM Manager version of CWM recovery? If so that could be your problem. I saw a lot of issues with that on the forum. Try Rogue's CWM or anyhing but the one supplied by ROM manager.
greetz,
Speedstra
Click to expand...
Click to collapse
I was flashing the recovery found at ROM Manager's site. I will try flashing Rogue's later today and maybe that will get me out of this mess and give you all an update. Thanks

Have you tried just reflashing to stock with-
Code:
./reflash_sbkv2.sh
- and then using Peri? You need to download the firmware from Asus and then blob unpack it.
Sent from my MB865 using xda app-developers app

Getting Closer!!!
darkstknight1523 said:
I was flashing the recovery found at ROM Manager's site. I will try flashing Rogue's later today and maybe that will get me out of this mess and give you all an update. Thanks
Click to expand...
Click to collapse
So taking Speedstra's advice, I put Rogue's recovery.img in the wheelie folder, ran /reflash_sbkv2 and magically I was into Rogue's recovery. I quickly downloaded CM9 to an SD card I had and attempted to install the ROM. Unfortunately, I am still not able to boot. After installing the ROM "successfully" I backed to the main menu and rebooted, however was greeted with nothing.
This tablet wasn't rooted to begin with, and at this point I don't know if I have taken the necessary steps to do so. I assumed since I was in a custom recovery (Rogue's) that I was rooted, but I'm probably wrong.
I am most likely missing a step (or 3) but am hopeful we are one step closer to getting her back up and running. Any ideas?
Here's the log:
PHP:
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]
Could the problem be with the "file not found: boot.img; failed executing command 2147483647 NvError 0x4; command failure: create failed"?

I'm sure the "can't mount" errors can't be good
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

1. Download the firmware from Asus' website.
2. Unzip this.
3. Run blob unpack on the blob file.
4. Rename the *.SOS, *.LNX, and *.APP files to linux.img, boot.img, and system.img respectively and put these with Wheelie.
5. Now run reflash.
6. Go get Peri and root and install recovery with it.
7. Success!...?
Special thanks to kenshin for helping me with the same situation.
Sent from my MB865 using xda app-developers app

ri4naire said:
1. Download the firmware from Asus' website.
2. Unzip this.
3. Run blob unpack on the blob file.
4. Rename the *.SOS, *.LNX, and *.APP files to linux.img, boot.img, and system.img respectively and put these with Wheelie.
5. Now run reflash.
6. Go get Peri and root and install recovery with it.
7. Success!...?
Special thanks to kenshin for helping me with the same situation.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately, not success. I extracted the contents of US_epad-user-9.2.1.24.zip (1 folder, 1 file) to the wheelie directory. I ran blobunpack and it appears it created (4) files called blob.APP, blob.EBT, blob.LNX, and blob.SOS. I renamed blob.SOS to linux.img, renamed blob.LNX to boot.img and renamed blob.APP to system.img. I then ran reflash_sbkv2 and here is that 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>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: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
file not found: blob.SOS
failed executing command 2147483647 NvError 0x4
command failure: create failed
c:\ASUS\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
As you can see, it's saying "file not found: blob.SOS", probably because I renamed it to linux.img. Is there anything I'm missing here?

darkstknight1523 said:
As you can see, it's saying "file not found: blob.SOS", probably because I renamed it to linux.img. Is there anything I'm missing here?
Click to expand...
Click to collapse
Yes, you must not rename the files generated from blobunpack, the flash.cfg file shipped with Wheelie expects blob.EBT, blob.LNX, blob.SOS and blob.APP

sbiriguda said:
Yes, you must not rename the files generated from blobunpack, the flash.cfg file shipped with Wheelie expects blob.EBT, blob.LNX, blob.SOS and blob.APP
Click to expand...
Click to collapse
So what do you suggest I do?

darkstknight1523 said:
So what do you suggest I do?
Click to expand...
Click to collapse
Just run reflash_sbkv2 right after blobunpack without renaming the files generated by the latter.

sbiriguda said:
Just run reflash_sbkv2 right after blobunpack without renaming the files generated by the latter.
Click to expand...
Click to collapse
Sorry for the dumb questions, but what blob should I be unpacking? The blob that comes from ASUS download or the blob from recovery?

darkstknight1523 said:
Sorry for the dumb questions, but what blob should I be unpacking? The blob that comes from ASUS download or the blob from recovery?
Click to expand...
Click to collapse
The one you extracted from the ASUS update zip.

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] bootloader status: Bct Write Failed (code: 22)

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

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