Database Info

[Q] Magic value mistmatch Fix

Hi,
I updated to the latest clockworkmod recovery (clockworkmod_recovery_2.5.1.2_2010112400) and got the message "Magic value mistmatch"
How can I get back into recovery mode? the power + volume up no longer works.

smakcc said:
Hi,
I updated to the latest clockworkmod recovery (clockworkmod_recovery_2.5.1.2_2010112400) and got the message "Magic value mistmatch"
How can I get back into recovery mode? the power + volume up no longer works.
Click to expand...
Click to collapse
Try the Quick Boot app and have it reboot into recovery.

The .12 clockworkmod has this issue - it's the main reason why I don't use it.
I think it's due to using non-padded boot.img files, for example TnT 2.2.0 is affected. I actually need to update my TnT post with this information.

I cant get the tablet to go past the Viewsonic logo. Is quick app a recovery mode? what's the button combination

roebeet said:
The .12 clockworkmod has this issue - it's the main reason why I don't use it.
I think it's due to using non-padded boot.img files, for example TnT 2.2.0 is affected. I actually need to update my TnT post with this information.
Click to expand...
Click to collapse
Roebeet,
Please help. I was trying to flash the 6.1 beta 4 with the latest version of the clockworkmod and now i cannot get past the viewsonic logo screen.
I followed your article from here: wiki.tegratab.com/index.php/ROMs
1. Could not find the "android_Tegra_250_FroyoOV5650v2.msi". Got another "tegra_froyo_20101105" from the site.
2. There is no "nvflash_gtablet.bat" when the file is extracted to the directory "C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105".
These are the .bat files i saw:
nvflash_1gb_crt.bat
nvflash_1gb_crt_256VRAM.bat
nvflash_1gb_hdmi
nvflash_1gb_hdmi_256VRAM
nvflash_1gb_lcd
nvflash_1gb_lcd_256VRAM
Which one should I run?

I've gong through that headache a few times. I've recovered it doing one of two things...
1) Turn the thing off and let it sit for 20 minutes or so.
2) Go into recovery on next boot. For me it would usually let you get back into recovery if I just left it off for 20 minutes. If not then go straight to the link below.
3) Format all partitions and then flash the 2.5.1.1 clockwork recovery
4) Reboot recovery then reflash the ROM
If that didn't get it back then recover via APX
http://forum.xda-developers.com/showthread.php?t=855690

The nvflash I posted is just a update.zip alternative. When you get errors like the mismatch, you need to completely wipe the device using bekit's method.
Here's the best doc I know, about that:
http://forum.tegratab.com/viewtopic.php?f=6&t=8

Thanks. I was able to recover my tablet. Just a question:
Roebeet you .bat file looks like this:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
@set /p batuserinput=Press enter to continue:
I ran the wrong bat file that looks like this:
"nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x3b000011 --create --go
@set /p batuserinput=Press enter to continue:
After this my tablet runs slower than usual. Any idea what "odmdata 0x3b000011" this value did to my tablet?

smakcc said:
Thanks. I was able to recover my tablet. Just a question:
Roebeet you .bat file looks like this:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
@set /p batuserinput=Press enter to continue:
I ran the wrong bat file that looks like this:
"nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x3b000011 --create --go
@set /p batuserinput=Press enter to continue:
After this my tablet runs slower than usual. Any idea what "odmdata 0x3b000011" this value did to my tablet?
Click to expand...
Click to collapse
I actually don't know what it means. My suggestion is to reflash with the right syntax, just to play it safe. nvflash is all low level stuff, so if you mess up the device you can still unbrick it. I've done this a few times.

[solved] Help with NVflash? Reflash failing

Okay, I have done something wrong.
I had a stock transformer. I am using Linux and am trying to root and install recovery, with the idea being to flash a custom ROM after successful root.
I am using wheelie with NVflash. I was attempting to install a CWM blob. It was saying that it was written, but when I would boot into recovery, it only has the cold boot/wipe data options.
So this is where I screwed up.
I had seen it said that with NVflash it is almost unbrickable so I wasn't being as attentive as I should have been. With all the out-of-date rooting methods and firmware update exploit fixes, I had reading about this for hours.
So anyway, I was stupidly cut/past a command that was originally for windows and just ran it like a dummy. I thought it was extra config info and didn't look carefully. It looked like it was part of the recovery install instructions, but I should have been more careful. The command looks, on further examination, like a wipe/flash firmware, which fails because there was nothing to write in that directory, I believe.
Code:
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
it formated a bunch of partitions and ended with this error
Code:
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
file not found: blob.EBT
failed executing command 2147483647 NvError 0x4
command failure: create failed
I tried to install recovery again, but I get messages like this:
Code:
[email protected]:~/android/transformer/root/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
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bootloader not found (code: 27) message: nverror:0x8 (0x8) flags: 0
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --go
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
I downloaded an update from Asus, US_epad-user-9.2.1.24.zip, which matches my old build, unpacked the blob, and have tried to run the ./reflash script. But it just hangs as you see here.
Code:
[email protected]:~/android/transformer/root/wheelie$ ./wheelie -2 --bct transformer.bct --bl bootloader.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: 0x37c708542bff297
[=] 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
[email protected]:~/android/transformer/root/wheelie$ ./reflash_sbkv2.sh
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
I then have to turn off the tablet to regain the APX connection.
This is might be TMI, but I haven't used any of these Tegra tools before, and would like to fix this thing as I just bought it for my wife this weekend...
Thanks!
Edit: .21 ICS, and C30 tf101.
Update: I was originally using the all-in-one package from wheelie. I downloaded nvflash by itself and made a new wheelie directory with the new nvflash files replacing those that were in the all-in-one. I also reunpacked the blob. Now when I run the ./reflash command, I now get
Code:
$ ./reflash_sbkv2.sh
File recovery.img is missing!
File boot.img is missing!
File system.img is missing!
One or more files are missing. Read documentation and provide the necessary files to continue!
which seems better, I suppose. I am tempted to just try and get those files from a custom rom and see what happens. Although I will try and wait to see if anyone has some advice. My shots in the dark haven't been very helpful so far...still I feel like it looks more promising...
update2 My overconfidence and impatience got the best of me. I tracked down a system, recovery and boot.omg that was in Prime!2.1 (HC) and then added it to the wheelie2 directory. It began to run, but then still hung at the same spot.
I decided to reboot my computer, and I also saw that maybe I did not need (as you can see above) intialize wheelie before reflashing. So I cd to wheelie2 and ran the ./reflash etc.
It wrote and the TRansformer automatically rebooted and showed the gears and now there is at least working Honeycomb (which is 10 times better than the OTA ICS she had.) I am not sure if it was intializing wheelie that gave me the problems or a bad nvflash or did my workstation need a reboot (unlikely, but still...)
Thanks for listening for what is now no goddam reason!

TF101 Settings stopped working

I already had a try on this on another forum:
hxxp://www(dot)transformerforums.com/forum/asus-transformer-help/25176-settings-stopped-working-tf101.html
(can't post links yet)
I have a TF101G ( sn:C20KAS035896) from a friend, everytime he went in to the settings it says: "settings stopped working"
I tried a factory reset, (from stock recovery menu), got it to reset, but now i cant get through the "first-time-setup-wizard":
at step 3 it asks to connect to a WiFi network, I select one, it asks for a password, but when I enter it and press ok it says "Unfortunately settings stopped working". After a few seconds it starts again at step one of the wizard..
I figured out it is a WW version.
So, what do I best try next?
After reading some here, i guess I get a alternative recovery and use that to flash a new stock rom onto the tablet.
But could you point me to the right posts and methods, because I'm not sure which is the right one.

http://forum.xda-developers.com/showthread.php?t=1552303
Then this you were looking for ? It is with recovery 3.2.0.1 us or ww stock rooted full rom edition
good luck

It might be. It seems to be a link to a zip file. The contents looks like the contents of a standard firmware file. Only the blob part is much smaller, and there is a system folder which isnt in the standard firmware update.
But I don't know what to do with it..
I was thinking maybe wolfs method 3 could help me out?
hxxp://forum(dot)xda-developers.com/showthread.php?t=1622628
(can't post links yet)
But i'm still strugling with adb though..
When i run "adb devices" I think it should list my TF101 but it doesn't

After some more reading and trying, I've come to the conclusion I can't get adb to connect to the device.
I also have an android phone: a HTC desire, which I can get to connect with adb. But the asus is stuck at the "first-time-setup-wizard" (as I explained above)..
Though I can see the device in windows explorer (win 7 64bit), and the 2 mounted drives "Internal storage" and "SD Card"
I can get it into apx mode, but nvflash doesn't work for my version of the device its a TF101G sn:C20KAS035896
What could i try next?
I want to flash the stock rom, as mine seems to be broken, and I cant use adb
EDIT:
Just found out about wheelie, should that tool be able to do what I want?
androidroot(dot)mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
My device isnt explicitly listed, and EasyFlasher a tool based on wheelie says it doesnt work for my device.. So should it work or not?
Do I need linux for this? I cygwin ok?
EDIT2:
As I understand it, I probably have a Secure Boot Key that isn't version 1 or 2?
There is a sbk detection tool, but afaik it only works on mac, and I don't have a mac available..
I have tried the windows beta version of wheelie, and the output i get is the following:
reflash_sbkv2.bat
Code:
J:\TF101\wheelie>reflash_sbkv2.bat
J:\TF101\wheelie>cd J:\TF101\wheelie\
J:\TF101\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --o
dm 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: 0x305242034059367191
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
J:\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fl
ash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
J:\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
And for the sbkv1 version the same:
Code:
J:\TF101\wheelie>reflash_sbkv1.bat
J:\TF101\wheelie>cd J:\TF101\wheelie\
J:\TF101\wheelie>"wheelie.exe" -1 --bct transformer.bct --bl bootloader.bin --o
dm 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: 0x305242034059367191
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
J:\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fl
ash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
J:\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
Am I overlooking something here?
Should I get adb working with my tablet in its current state?
Or do I have to return the tablet to ASUS?

Same problem here
Hello frydac, I'm having the same problem as you.
Did you find a way to fix it yet?

[Q] nvflash full restore

Greetings everyone. I'm trying to get my head around the nvflash tool to make a full restore on my TF101. Long ago, when I flashed it with a custom rom I made a backup using nvflash, which saved pretty much all partitions inside the device's storage. I also must say that I don't have a clear idea of how nvflash works, so I'm just trying and failing with no luck so far.
I would like to be able to write the raw data I backed up into the device, but I don't know how to do it really. The script I'm working on to perform this task has a create command to write all the partitions and format them as they were when the backup was made. An additional detail is that I had an ubuntu there as well, hence the partition redefinition.
Thing is that the command that creates and format the partitions also writes a bootloader and other data into the device, which doesn't let me to re-write the original bootloader and data I have from the backup.
Here's the script:
Code:
#!/bin/bash
echo 'Restoring ASUS TF101...'
BACKUP_DIR=$1
./nvflash --bct transformer.bct --setbct --configfile $BACKUP_DIR/flash.cfg --bl bootloader.bin --create --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98
./nvflash --rawdevicewrite 0 1536 $BACKUP_DIR/02_BCT_raw.img --bl bootloader.bin
./nvflash --rawdevicewrite 1536 256 $BACKUP_DIR/03_PT_raw.img --bl bootloader.bin
# ./nvflash --rawdevicewrite 1792 2048 $BACKUP_DIR/04_EBT_raw.img --bl bootloader.bin #bootloader
./nvflash --rawdevicewrite 3840 2560 $BACKUP_DIR/05_SOS_raw.img --bl bootloader.bin #recovery
./nvflash --go
./nvflash --resume --sync
./nvflash --resume --download 6 $BACKUP_DIR/06_LNX_raw.img #kernel
./nvflash --resume --download 7 $BACKUP_DIR/07_BAK_raw.img
./nvflash --resume --download 8 $BACKUP_DIR/08_GP1_raw.img
./nvflash --resume --download 9 $BACKUP_DIR/09_APP_raw.img #system
./nvflash --resume --download 10 $BACKUP_DIR/10_CAC_raw.img
./nvflash --resume --download 11 $BACKUP_DIR/11_MSC_raw.img
./nvflash --resume --download 12 $BACKUP_DIR/12_USP_raw.img
./nvflash --resume --download 13 $BACKUP_DIR/13_PER_raw.img
./nvflash --resume --download 14 $BACKUP_DIR/14_YTU_raw.img
# ./nvflash --resume --download 15 $BACKUP_DIR/15_UDA_raw.img #media (/!\ ~14/30GB large)
./nvflash --resume --download 16 $BACKUP_DIR/16_GPT_raw.img
echo "Restore completed!"
As you can see, I'm trying to use the rawdevicewrite option, which in theory is the one I should be using for some of the partitions due to being encrypted (as I read somewhere in here). The main problem of the script is that it can't continue after the first command, because it executes a sync and since there is no bootloader on the device after the formating, it fails.
I read that the config file used by nvflash also contains files to be transfered to the device. When I specify the backed up bootloader to load after the format, the transfer stops for some reason and never finishes. I suspect it has something to do with either the encryption, or because it's replacing something that is running.
So question is: how exaclty the rawdevicewrite can be used? is there a better/easier way to restore this kind of data?
I can't find much documentation about the tool to fix my script. My idea is to automate the restore so I can just throw it a dir, and it restores from there.
Note that I don't really have a problem with the device itself... well, I actually do, but what I mean is that I can successfully flash with stock roms and everything would work properly, but I would like to restore everything I backed up, including the original bootloader, recovery, etc, and I need this, because the recovery img I have (not the backup), doesn't seem to work after installing it, it gets stuck with a warning icon.
Any leads on how I could achive this will be appreciated. Otherwise I guess I will likely lose those partitions and be able to only restore non-encrypted data, which is a pity, because the data is there and theoricaly, raw writing it into the device should restore the state that was backed up.
Thanks in advance, let me know if you need further info.

Question - is the warning icon in stock recovery a dead droid laying down with an exclamation point overhead?
If so, this IS stock recovery working properly. It will only upgrade if a newer firmware zip is found on the internal or external storage, otherwise it will give you a dead droid.

frederuco said:
Question - is the warning icon in stock recovery a dead droid laying down with an exclamation point overhead?
If so, this IS stock recovery working properly. It will only upgrade if a newer firmware zip is found on the internal or external storage, otherwise it will give you a dead droid.
Click to expand...
Click to collapse
No, it's just a normal droid standing with the exclamation mark inside it, see attachment.
Lastnight, while I was playing around with the tablet an update came up, it rebooted the tablet and started the recovery session which seemed to work properly. I actually never used that recovery, so I guess it's safe to assume it's working properly? I thought I would have a few options there to wipe data or something.
I still wonder about the raw write option to fully recover my backups. Does any one think this is not necesary or that should I only worry about data partitions rather than all of them?

Hmm, I am not sure. I have only done full backups using ADB and nandroids in recovery.

[NvFlash] [Recovery] With [Generated Blobs][TF300T]

First off I want to thank @lj50036 for his time and most of all his patients in helping me bring my TF300T back to life I can't thank him enough!! His original post on the TF700T is here. Make sure you go thank him!!
You must have the NVFlash generated files from AndroidRoot.Mobi for ICS or JB.
This is what I did and it might not work for your specific situation. I performed this on a Mint 15 32 bit machine. This is very important (EDIT: This has also been done on Mint 64bit); Ubuntu might not work and would not work for me .
My situation:
I had flashed the wrong recovery (TWRP 2.6.3.0). This left me with only being able to boot into a recovery that would not mount anything but it would boot into APX mode.​
What you will end up needing:
blob.bin
unlock-token.img
factory-config.img
bricksafe.img
Also needed:
Fully charged TF300T (Just plug it in, it will charge no matter what...If not, you don’t need my help!!!!)
Asus data cable
Linux Mint 15 (32 bit) PC
Stock firmware blob (from asus's website. Make sure you get the right one) Download
nvflash and wheelie Download
And fastboot for your PC
You might also need TWRP 2.5.0.0 Download
Mint
1) Lets start with Mint 15 (32 bit) Download and how to make a bootable USB. instructions this has got to be one of the easiest OS’s I have installed and setting up dual boot is cake.
2) Once Mint is booted you want to update it, and it’s a little broken but it’s what I did and you will get some updates. Click where the start menu is in windows find the search field and lookup update manager. Run it and download what you can.
3) Extract wheelie and nvflash to your home folder...
Extract your stock firmware in your downloads folder twice...You will see a blob (this is not a .blob file make sure you put that in the name) file rename it boot.blob and move it to your home folder...
Move the above mentioned device specific files to your home folder..
blob.bin
unlock-token.img
factory-config.img
bricksafe.img
nvflash
wheelie
boot.blob (we renamed it in the last step)
4) Next we need to install fastboot, this is straight up Linux voodoo, open terminal and get comfy cause that’s what you’re going to be using. next type
Code:
fastboot
it will prompt you with the command to install fastboot.
These inputs and outputs are from lj50036 post on the TF700T and may very from your outputs. I used the processes and it worked for me.
Lets get started
Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode....
Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie....
I am going to show you the output of my process
Code:
sudo ./wheelie --blob blob.bin
[email protected]:~ > sudo ./wheelie --blob blob.bin
OUTPUT
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbce2501405
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
It may shutdown after each command, get back into nvflash with the above steps.....
Code:
sudo ./nvflash -r --download 7 unlock-token.img
[email protected]:~ > sudo ./nvflash -r --download 7 unlock-token.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: unlock-token.img
/ 8388608/8388608 bytes sent
unlock-token.img sent successfully
Code:
sudo ./nvflash -r --download 14 factory-config.img
[email protected]:~ > sudo ./nvflash -r --download 14 factory-config.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: factory-config.img
/ 5242880/5242880 bytes sent
factory-config.img sent successfully
Code:
sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
[email protected]:~ > sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: bricksafe.img
/ 12058624/12058624 bytes sent
bricksafe.img sent successfully
Code:
sudo ./nvflash -r --go
[email protected]:~ > sudo ./nvflash -r --go
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
This is where I ran into problems that didn’t work with the TF700T recovery process. I could not boot into Fastboot with the holding the power and the volume down no matter what I did. this is how we got around it.
download the correct .blob from TWRP rename it twrp.blob then run
Code:
sudo ./nvflash -r --download 5 twrp.blob
I don't have output for this.
At this point I could boot into the OS, but still not into fastboot. My OS had the option to reboot to download. If you don’t have this option you could try this or this. But the best way is via the buttons.
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
sudo fastboot devices
INPUT
[email protected]:~ > sudo fastboot devices
OUTPUT
015d2bbce2501405 fastboot
Code:
sudo fastboot erase system
INPUT
[email protected]:~ > sudo fastboot erase system
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
sudo fastboot erase recovery
INPUT
[email protected]:~ > sudo fastboot erase recovery
OUTPUT
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
sudo fastboot -w
INPUT
[email protected]:~ > sudo fastboot -w
OUTPUT
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it just hangs on erasing 'cache'
I just close terminal and open new one, and run the next command
If your tablet hangs just reboot back into fastboot again
Code:
sudo fastboot erase boot
INPUT
[email protected]:~ > sudo fastboot erase boot
OUTPUT
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
sudo fastboot erase misc
INPUT
[email protected]:~ > sudo fastboot erase misc
OUTPUT
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
sudo fastboot erase cache
INPUT
[email protected]:~ > sudo fastboot erase cache
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
sudo fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
INPUT
[email protected]:~ > sudo fastboot -i 0x0B05 flash system boot.blob
OUTPUT
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
sudo fastboot -i 0x0B05 reboot
[email protected]:~ > sudo fastboot -i 0x0B05 reboot
OUTPUT
rebooting...
finished. total time: 0.020s
You will now be back to stock rom stock bootloader but still unlocked!!!!!!!!!!!!!
Boot fully into rom then you can do whatever you would like!!!!!!!!!!!
Make sure you go thank @lj50036

....

Great Work
Its nice to see that my work on the 700 will be able to, maybe help the 300 community out also.... Keep up the good work.... Thx as always lj :silly:

Thanks for your docs, only a question please, are necessarily forced to use "Linux Mint 15 (32 bit) PC" or can i use Windows as I did to generate the img and blob?
I don't understand this step, "nvflash" work fine to download this file, it doesn't work during the write from Windows command prompt?

OS
Erario said:
Thanks for your docs, only a question please, are necessarily forced to use "Linux Mint 15 (32 bit) PC" or can i use Windows as I did to generate the img and blob?
I don't understand this step, "nvflash" work fine to download this file, it doesn't work during the write from Windows command prompt?
Click to expand...
Click to collapse
I can confirm this working on mint 15 32 bit, mint 15 64 bit, and mint 16 64 bit.. I would stay away from windows if at all possible....Thx lj

When for some reason will no longer start my "unbrickable TF300TG" (hehehe) I'll try with Windows and I will tell you.

I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android

feedback
ebildude123 said:
I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
Did you come from a brick or did you just use nvflash to flash a recovery??

lj50036 said:
Did you come from a brick or did you just use nvflash to flash a recovery??
Click to expand...
Click to collapse
A brick

ebildude123 said:
I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
My device is TF201.
Here is my long story: (search for my post)
http://forum.xda-developers.com/showthread.php?p=50690267
In short, i cannot get fastboot but can get to APX (power + up)
Was thinking of trying your steps but I dun understand how to get twrp.blob.
Also, prior to my brick i flashed some cwm recovery. Does that matter?
I have all the output files from the flatline thingy.
Any ideas?

vanquishe said:
My device is TF201.
Here is my long story: (search for my post)
http://forum.xda-developers.com/showthread.php?p=50690267
In short, i cannot get fastboot but can get to APX (power + up)
Was thinking of trying your steps but I dun understand how to get twrp.blob.
Also, prior to my brick i flashed some cwm recovery. Does that matter?
I have all the output files from the flatline thingy.
Any ideas?
Click to expand...
Click to collapse
You have your generated nvflash blobs???

lj50036 said:
You have your generated nvflash blobs???
Click to expand...
Click to collapse
I'm pretty noob so i'm not sure what you mean by generated nvflash blobs.
Here are the files in my nvflash dir:
blob.bin 1,670,651
blob.log 649
bootloader.ebt 1,558,608
bricksafe.img 12,058,624
create.bct 6,128
factory-config.img 5,242,880
libnv3p.dll 54,784
libnvaes_ref.dll 45,056
libnvapputil.dll 81,920
libnvboothost.dll 43,520
libnvdioconverter.dll 45,056
libnvflash.dll 81,920
libnvos.dll 101,376
libnvtestio.dll 96,768
libnvtestresults.dll 46,080
libnvusbhost.dll 44,544
nvflash.exe 272,896
pt_patch.log 298
pt_restore.log 299
recovery.bct 6,128
unlock-token.img 8,388,608
wheelie.exe 105,264

vanquishe said:
I'm pretty noob so i'm not sure what you mean by generated nvflash blobs.
Here are the files in my nvflash dir:
blob.bin 1,670,651
blob.log 649
bootloader.ebt 1,558,608
bricksafe.img 12,058,624
create.bct 6,128
factory-config.img 5,242,880
libnv3p.dll 54,784
libnvaes_ref.dll 45,056
libnvapputil.dll 81,920
libnvboothost.dll 43,520
libnvdioconverter.dll 45,056
libnvflash.dll 81,920
libnvos.dll 101,376
libnvtestio.dll 96,768
libnvtestresults.dll 46,080
libnvusbhost.dll 44,544
nvflash.exe 272,896
pt_patch.log 298
pt_restore.log 299
recovery.bct 6,128
unlock-token.img 8,388,608
wheelie.exe 105,264
Click to expand...
Click to collapse
Ok yes you should be able to do what you need to do.. You tell me what you need and we will get your tf201t up and running again.....

lj50036 said:
Ok yes you should be able to do what you need to do.. You tell me what you need and we will get your tf201t up and running again.....
Click to expand...
Click to collapse
First, let me thank you for responding. Really appreciate this.
You mean I actually have hope even that now I only have a black screen + APX device detected in windows 7?
Should we continue this on this thread? Since its tf201 and not tf300
Or should we continue on IRC?
http://forum.xda-developers.com/showthread.php?p=50690267
(please read my story (10th reply down))
I have no idea how to proceed at all and dun wish to do anything silly.
Should i follow what you did or this:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?p=50691902
-----------------------
1. Download an un-blob'd ROM (links below). [Advanced users can use BlobTools (blobunpack) and unblob a ROM. Make sure you have compatible unblob'd images of the bootloader, recovery, kernel & system]
2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)
3. Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode.
4. Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie
wheelie.exe --blob blob.bin
5. After wheelie does it's job, your device will be ready in nvFlash mode. You can now begin the process.
6. We start with the bootloader. In the case of the un-blob'd ROMs below, this is the blob.EBT file. To flash the bootloader, use this command:
nvflash.exe -r --download 4 blob.EBT
7. Next we move to the recovery image. In the case of the un-blob'd ROMs below, this is the blob.SOS file. To flash the recovery image, use this command:
nvflash.exe -r --download 5 blob.SOS
8. Next we move to the boot image. In the case of the un-blob'd ROMs below, this is the blob.LNX file. To flash the boot image, use this command:
nvflash.exe -r --download 6 blob.LNX
9. Next we move to the system image. In the case of the un-blob'd ROMs below, this is the blob.APP file. To flash the system image, use this command:
nvflash.exe -r --download 10 blob.APP
10. Finally, we reboot the device. After you run the following command, you will see the text "AndroidRoot 9.4.2.28" and your device should reboot in a few seconds. If you device does not reboot after you see the text, force a reboot (long press the Power button)
nvflash.exe -r --go
-----------------------

vanquishe said:
First, let me thank you for responding. Really appreciate this.
You mean I actually have hope even that now I only have a black screen + APX device detected in windows 7?
Should we continue this on this thread? Since its tf201 and not tf300
Or should we continue on IRC?
http://forum.xda-developers.com/showthread.php?p=50690267
(please read my story (10th reply down))
I have no idea how to proceed at all and dun wish to do anything silly.
Should i follow what you did or this:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?p=50691902
-----------------------
1. Download an un-blob'd ROM (links below). [Advanced users can use BlobTools (blobunpack) and unblob a ROM. Make sure you have compatible unblob'd images of the bootloader, recovery, kernel & system]
2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)
3. Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode.
4. Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie
wheelie.exe --blob blob.bin
5. After wheelie does it's job, your device will be ready in nvFlash mode. You can now begin the process.
6. We start with the bootloader. In the case of the un-blob'd ROMs below, this is the blob.EBT file. To flash the bootloader, use this command:
nvflash.exe -r --download 4 blob.EBT
7. Next we move to the recovery image. In the case of the un-blob'd ROMs below, this is the blob.SOS file. To flash the recovery image, use this command:
nvflash.exe -r --download 5 blob.SOS
8. Next we move to the boot image. In the case of the un-blob'd ROMs below, this is the blob.LNX file. To flash the boot image, use this command:
nvflash.exe -r --download 6 blob.LNX
9. Next we move to the system image. In the case of the un-blob'd ROMs below, this is the blob.APP file. To flash the system image, use this command:
nvflash.exe -r --download 10 blob.APP
10. Finally, we reboot the device. After you run the following command, you will see the text "AndroidRoot 9.4.2.28" and your device should reboot in a few seconds. If you device does not reboot after you see the text, force a reboot (long press the Power button)
nvflash.exe -r --go
-----------------------
Click to expand...
Click to collapse
freenote
#crombix
kk

Thanks for your great tutorials. I did this process on my TF201 and it worked great. Trying to do the same on my teenagers TF300T and I'm running into an error.
When I do fastboot -i 0x0b05 flash system boot.blob I get error: cannot open "boot.blob"
Tried renaming the file, as well at using another copy of the file from my cloud. I noticed the file is listed as a txt file not a blob file
Never mind. Used the stock blob and it worked.

JoanneDisFan said:
Thanks for your great tutorials. I did this process on my TF201 and it worked great. Trying to do the same on my teenagers TF300T and I'm running into an error.
When I do fastboot -i 0x0b05 flash system boot.blob I get error: cannot open "boot.blob"
Tried renaming the file, as well at using another copy of the file from my cloud. I noticed the file is listed as a txt file not a blob file
Never mind. Used the stock blob and it worked.
Click to expand...
Click to collapse
Great to see you up and running ....
Let us know if there is anything you need help with in the future ...
Thx Josh

tf300t
Hello, i am new here, for this: My Name is Lorenzo.
My question is: is possible to rewrite The system of My TF300T from windows 7 with nvflash?
My Win7 detect tf300t only in APX Mode. Today from apx mode with The wheelie command i think That i have entered in NVFLASH mode, It is possible?
which are The command to rewrite system That i Must do to have a tablet functional At 100%? (Someone Can write here The exactly command That i Must type in Command Prompt? Thanks)
(Sorry for My bad English and if i have repeated answer or question in this forum)
I Hope That Someone Can help me, i am desperate! :'(
(Today evening, when i finished to work, i post The exatly files That i have to use nvflash and i Hope That Someone Can help me to exit from this situation.
Very thanks

Hello,
I Know my tf300t is an old one but I brick it yesterday. I try to resolve this problem with your tutorial.
I've got two problems with it:
- the link to download nvflash dans wheelie are down (if someone have them it would be aprreciate)
Thanks a lot