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.

HELP recovery problem

nvflash --bl bootloader.bin --download 9 cwm254recovery.img
bootloader.bin sent succesfully
sending file: cwm254recovery.img
-851968/4026368 bytes sentdata send failed NvError 0x30012
command failure: partition dowload failed
Click to expand...
Click to collapse
HELP!!!!!!!!!!!!!!!!!!!!!!!!

haltol said:
nvflash --bl bootloader.bin --download 9 cwm254recovery.img
HELP!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Two topics?
Seems to be a partition error, there was another person with this error...
Have you tried this?: http://forum.xda-developers.com/showthread.php?t=861950

Found the link of the other person, he fixed using above link i believe:
Post:
http://forum.xda-developers.com/showpost.php?p=10464361&postcount=44
Thread:
http://forum.xda-developers.com/showthread.php?p=10464361#post10464361

Moved to general

[Q] nvflash

Last nigh I left my transformer at 25% battery power in flight mode.
This morning was not able to switch my Transformer on.
After trying all possibilities to enter recover mode without success, I decided to use NVflash and reflash prime_v1.4.
However NVflash exits with the following error. What can go wrong?
Any idea how to fix this?
Regards,
Nikola
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA xA532EEB 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c208340403317
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x42008 (0x19042008) flags:
0

same error :s

Have you copy/paste your NVFlash command in this thread or do you write it yourself?
Because it seems to be an error in your command:
the right command is:
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Click to expand...
Click to collapse
The difference between this one and yours is the "0" before "xA532EEB6". You muste have "0xA532EEB6"
if it dosen't work try with another version of Prime... (1.5 or 1.8)

Kasimodo said:
Have you copy/paste your NVFlash command in this thread or do you write it yourself?
Because it seems to be an error in your command:
the right command is:
The difference between this one and yours is the "0" before "xA532EEB6". You muste have "0xA532EEB6"
if it dosen't work try with another version of Prime... (1.5 or 1.8)
Click to expand...
Click to collapse
This is the content of download.bat
cd %~dp0
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
I tried with different versions of Prime but the same error happens.
Is there any other way to get some more logging/debug info from the bootloader or to check if the emmc memory is not broken or locked.
Regards,
Nikola

I think there is a problem with your internal SD. Because the next command after creating partitions is to format partitions.
But have you tried to download another nvflash.exe?
Otherwise I don't see anything else

battery is too low

Command is correct (it's in dowload.bat file) and battery is 100% (all night charging) but always the same error...
When I execute batch file, after a few seconds, screen turn on and display :
Code:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxxxxxxxxxxxxxxxxxxx
And batch file close...

tnp0511 said:
Command is correct (it's in dowload.bat file) and battery is 100% (all night charging) but always the same error...
When I execute batch file, after a few seconds, screen turn on and display :
Code:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxxxxxxxxxxxxxxxxxxx
And batch file close...
Click to expand...
Click to collapse
Exactly the same behavior here.
I will try to charge it tomorrow with another charger.

Make sure to run in a cmd window so that you can see why it's exiting

Run from cmd window
AustinMartin said:
Make sure to run in a cmd window so that you can see why it's exiting
Click to expand...
Click to collapse
The run has also been done from a cmd window:
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB 0xECFE1D98 --go
It is always exiting with:
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x42008 (0x19042008) flags: 0
Also interesting to notice that when I run without --create and without --go but with --sync
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB 0xECFE1D98 --sync
The output is
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c208340403317
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
but I never get the prompt back.

Is your TF101 rooted?

Kasimodo said:
Is your TF101 rooted?
Click to expand...
Click to collapse
Yes, it was rooted. 1 mount ago i flushed prime1.4 using the same procedure (nvflash + prime1.4). everything worked OK until sunday morning when the TF101 would not switch on.
Regards,
Nikola

Argh. I'm afraid that there is a physical problem.
If it was mine I will try to unroot it to see. Anf after the best is to contact Asus for return.

any other idea ?
otherwise return to Asus on Saturday

im sorry for bumping old thread, just curious about the result, since now i have exatly the same problem, i can go into apx mode, but when i started the download.bat, the problem is the same, nvflash just exit after that, tf screen turned on, and when i tried to start the download.bat again, the cmd only show "nvflash is starting"

uman01 said:
im sorry for bumping old thread, just curious about the result, since now i have exatly the same problem, i can go into apx mode, but when i started the download.bat, the problem is the same, nvflash just exit after that, tf screen turned on, and when i tried to start the download.bat again, the cmd only show "nvflash is starting"
Click to expand...
Click to collapse
+1
what can we do?

DTrainMusicVein said:
+1
what can we do?
Click to expand...
Click to collapse
You probably have an SBKv2 tablet which you can't use NVFlash right now

baseballfanz said:
You probably have an SBKv2 tablet which you can't use NVFlash right now
Click to expand...
Click to collapse
I checked the original package and it says B50, where exactly would I find if its SBKv1 or 2? Correct me if I'm wrong, but I thought B50s were SBKv1?
Thanks in advance

DTrainMusicVein said:
I checked the original package and it says B50, where exactly would I find if its SBKv1 or 2? Correct me if I'm wrong, but I thought B50s were SBKv1?
Thanks in advance
Click to expand...
Click to collapse
Yes you're B50 should be SBKv1.
You do have all the needed files in the nv flash folder?

I believe so, I have downloaded the rooted and unrooted US versions of the ICS NVFlash and I am going to try the WW next? Any other tips? Its still failing on me...

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

[Q] TF101 constant loop

I have a TF101 b70 but is in loop
It's happened other times and managed to fix, but it's not working anymore.
I used nvflash and wheelie
I extracted blob inside WW_epad-user-9.2.1.27.zip and use blobunpack to extract blob.APP, EBT, LNX and SOS files
after I run
./wheelie -1 --bl bootloader.bin --bct transformer.bct --odm 0x300d8011
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
./nvflash -r --go
after reboot tf101
The rom is writed normally, but continues in loop.
I tried everything to get into adb mode
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
but continues loop
what do I do?