[Eee Pad Transformer General] Franz.Hendrik:
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!