Database Info

[DEV][nvflash] Full backup/restore your Transformer!

Code:
###########################################################################
# WARNING #
###########################################################################
# I am not responsible for bricked devices, loss of data, meltdown of #
# your device or thermonuclear war. #
# YOU are choosing to make these modifications, and if you point the #
# finger at me for messing up your device, I will laugh at you. #
###########################################################################
Backup
First of all I would like to make it clear I am not an nvflash expert: as you can guess from my avatar I am a linux user but I downloaded this tool for the first time just yesterday, upon the arrival of my TF.
Thanks to the work of Rayman I think I managed to do a backup of all tablet partitions.
I created a script to simplify the backup process:
Code:
#!/bin/bash
BACKUP_DIR="tf101-backup-`date +%Y%m%d%H%M%S`"
mkdir $BACKUP_DIR
./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
./nvflash --resume --getpartitiontable $BACKUP_DIR/partitiontable.txt
./nvflash --resume --read 2 $BACKUP_DIR/02_BCT_raw.img
./nvflash --resume --read 3 $BACKUP_DIR/03_PT_raw.img
./nvflash --resume --read 4 $BACKUP_DIR/04_EBT_raw.img #bootloader
./nvflash --resume --read 5 $BACKUP_DIR/05_SOS_raw.img #recovery
./nvflash --resume --read 6 $BACKUP_DIR/06_LNX_raw.img #kernel
./nvflash --resume --read 7 $BACKUP_DIR/07_BAK_raw.img
./nvflash --resume --read 8 $BACKUP_DIR/08_GP1_raw.img
./nvflash --resume --read 9 $BACKUP_DIR/09_APP_raw.img #system
./nvflash --resume --read 10 $BACKUP_DIR/10_CAC_raw.img
./nvflash --resume --read 11 $BACKUP_DIR/11_MSC_raw.img
./nvflash --resume --read 12 $BACKUP_DIR/12_USP_raw.img
./nvflash --resume --read 13 $BACKUP_DIR/13_PER_raw.img
./nvflash --resume --read 14 $BACKUP_DIR/14_YTU_raw.img
#./nvflash --resume --read 15 $BACKUP_DIR/15_UDA_raw.img #media (/!\ ~14/30GB large)
./nvflash --resume --read 16 $BACKUP_DIR/16_GPT_raw.img
If you want to make also a backup of the media partition uncomment this line, but know that this operation will generate a 14/30GB img file and take a long time:
Code:
#./nvflash --resume --read 15 $BACKUP_DIR/15_UDA_raw.img #media (/!\ ~14/30GB)
Restore
rayman84 said:
Just FYI, you *don't* want to restore partition 2 and 4 at the very least. (and probably others!)
Partition 2 and 4 are encrypted. nvflash does not decrypt it when --read'ing, but at least during --create, it does encrypt it. I'm not entirely sure whether it encrypts it during --download, but if it does, the tablet will appear bricked after flashing.
Click to expand...
Click to collapse
At the moment I have not yet tried to restore a full backup, but I managed to push the kernel partition.
If someone else wants to try, the restore command should be this:
Code:
./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
./nvflash --resume --download 5 <path-to-your-backup-dir>/05_SOS_raw.img
[...]
./nvflash --resume --download 16 <path-to-your-backup-dir>/16_GPT_raw.img
./nvflash --resume --sync

JD82 said:
Code:
###########################################################################
# WARNING #
###########################################################################
# I am not responsible for bricked devices, loss of data, meltdown of #
# your device or thermonuclear war. #
# YOU are choosing to make these modifications, and if you point the #
# finger at me for messing up your device, I will laugh at you. #
###########################################################################
[/QUOTE]
Thank you sir I fully intend on at least attempting this or something similiar to try to make a back up will read more carefully.... a little later
[SIZE="6"][COLOR="Red"]Done like dinner[/COLOR][/SIZE]
Did two back ups not including media and both seem identical 8.23.9 preserved at the very least for prosperity. Thanks for the commands now proceeding to root. I will update to 3.1 stock and use the root only thread to see if I can go that root to root ;-). Cant decide whether I need the clockwork mod? guess we'll see.
Click to expand...
Click to collapse

I tried to restore the kernel partition and it worked like charm (06_LNX_raw.img)

Good work! Overall it looks correct
Just FYI, you *don't* want to restore partition 2 and 4 at the very least. (and probably others!)
Partition 2 and 4 are encrypted. nvflash does not decrypt it when --read'ing, but at least during --create, it does encrypt it. I'm not entirely sure whether it encrypts it during --download, but if it does, the tablet will appear bricked after flashing.

Perfect! I intend to be working on installing Gentoo tonight, and this will be an excellent first step in case I botch anything

rayman84 said:
Just FYI, you *don't* want to restore partition 2 and 4 at the very least. (and probably others!)
Partition 2 and 4 are encrypted. nvflash does not decrypt it when --read'ing, but at least during --create, it does encrypt it. I'm not entirely sure whether it encrypts it during --download, but if it does, the tablet will appear bricked after flashing.
Click to expand...
Click to collapse
Thanks for reporting. I updated the topic

rayman84 said:
Good work! Overall it looks correct
Just FYI, you *don't* want to restore partition 2 and 4 at the very least. (and probably others!)
Partition 2 and 4 are encrypted. nvflash does not decrypt it when --read'ing, but at least during --create, it does encrypt it. I'm not entirely sure whether it encrypts it during --download, but if it does, the tablet will appear bricked after flashing.
Click to expand...
Click to collapse
Hmm, was there a way back to safety if one was to brick this way. Just curious. Thanks again for the knowledge being passed along.

I am not a developer so I have no idea what those lines are. So how do I basically do this? I am trying to restore the nv files of my Dinc because I bricked it. I have backed up the nv files.
Any help would be appreciated.

If your tablet is bicked you better ask for help in this topic: http://forum.xda-developers.com/showthread.php?t=1123429
Without a backup "those lines" are useless

Thanks! I just unbricked my TF! I flashed all the partitions except 2, 4, and 15 and it seems to have restored everything just fine. There was an error trying to sign into email, but I think that happens when my computer or phone are checking at the same time. I opened the stock app manually and it was working after that.
A little background: I was running stock rooted 8.4.4.11 with CWM-solarnz. I tried to flash Prime 1.5, which I kinda knew would be bad since it's based on 8.4.4.5. My TF was stuck at the splash screen and wouldn't stay off. I held the power button down for 10+ seconds which seemed to do the trick. I put it into APX mode and flashed away. I restored all the partitions except 2, 4, and 15. According to the thread, 2 and 4 are encrypted, and I never bother to back up 15.
Thanks again!

So how does this differ, or what are the advantages to backing up this way versus a nandroid backup?

This method will let you restore even when the recovery is boogered up and you have bootloops when you try to turn on the TF.
This will unbrick your TF when no other method can. It's kinda like the A-team.
. If you have a problem, if no one else can help, and if you can find them, maybe you can hire... The A-Team.
Click to expand...
Click to collapse

Can someone post this type of backup of a completely untouched stock system? I am sure it would be much appreciated by people who muck up their TFs trying to do some ROM or rooting wazardry. Thanks!

I had an interesting encounter tonight with nvflash. I was testing a little theory and flashed the previous 8.2.3.9 bootloader onto a working 8.4.4.11 system.
It confirmed my theory, but bricked my tablet. I was trying to just restore the bootloader using nvflash, but didn't check my script and used the --create command instead. This formatted my TF and wiped out partition 15, which is the only thing not backed up.
While trying to restore my latest backup, one thing that I noticed is that the partition table changed, so I had to update flash.cfg. I also updated the nvflash scripts to use the latest bootloader. With a completely wiped TF, I had to restore using the --create command and put all the filenames in flash.cfg. This might be because I wiped and formatted using the old flash.cfg file.
Eventually, I was able to restore my backup, but for some reason, userspace was gone completely. I had nothing in /data. I was able to restore with CWM.
Still not sure about why partition 12 would not flash. I didn't receive any error messages. So, as a backup to the backup, use CWM to backup!

gee one said:
I had an interesting encounter tonight with nvflash. I was testing a little theory and flashed the previous 8.2.3.9 bootloader onto a working 8.4.4.11 system.
It confirmed my theory, but bricked my tablet. I was trying to just restore the bootloader using nvflash, but didn't check my script and used the --create command instead. This formatted my TF and wiped out partition 15, which is the only thing not backed up.
While trying to restore my latest backup, one thing that I noticed is that the partition table changed, so I had to update flash.cfg. I also updated the nvflash scripts to use the latest bootloader. With a completely wiped TF, I had to restore using the --create command and put all the filenames in flash.cfg. This might be because I wiped and formatted using the old flash.cfg file.
Eventually, I was able to restore my backup, but for some reason, userspace was gone completely. I had nothing in /data. I was able to restore with CWM.
Still not sure about why partition 12 would not flash. I didn't receive any error messages. So, as a backup to the backup, use CWM to backup!
Click to expand...
Click to collapse
Hi - I was just trying to do this backup because I can't get cwm working on US TF 84411 (latest US version). Now I think I realize that nvflash perhaps is also not working on 84411.
It sounds , at least, like you had the correct version of flash if you were even (unfortunately) able to brick yours. I'm using linux, and the nvflash the OP used and keep getting back this:
Code:
[QUOTE]$ /Downloads/transformer/Prime16r2$ ./nvflash --resume --getpartitiontable $BACKUP_DIR/partitiontable.txt
Nvflash started
[resume mode]
connection failed NvError 0x8
$~/Downloads/transformer/Prime16r2$
[/QUOTE]
Also: Have you got CWM working now on US 84411? If so could you point me at the entry that does that?
Thanks and good luck unbricking.
Hashi
edit: I just realized I'd forgotten to get out of normal boot mode and into (vol+/power) mode. Nvflash works fine now as far as doing what the OP says.
I am still wondering about 84411 with CWM. Thanks.

Here's the short version:
I think the flash.cfg file is different for the 84411 files. Compare flash.cfg with partitiontable.txt in the backup directory. Look at the file sizes- I recall that a few of them are larger.
Also, bootloader.bin is from the 8239 update or something like that. I used the blob.EBT that can be extracted from the ota update. This is the 84411 boatloader.
For CWM-solarnz that works with 84411, look in the pure root thread by mashi in the dev forum. I posted a recovery.img that will work in post 385 or so.
sent from my cyanogen(mod) vision

Also, I found that you can reboot out of APX mode after flashing with this command
./nvflash -r --go
It only works after you sent the original nvflash command. You can use it from the command line after backing up all your partitions and want to reboot the TF.
sent from my cyanogen(mod) vision

gee one said:
Here's the short version:
I think the flash.cfg file is different for the 84411 files. Compare flash.cfg with partitiontable.txt in the backup directory. Look at the file sizes- I recall that a few of them are larger.
Also, bootloader.bin is from the 8239 update or something like that. I used the blob.EBT that can be extracted from the ota update. This is the 84411 boatloader.
For CWM-solarnz that works with 84411, look in the pure root thread by mashi in the dev forum. I posted a recovery.img that will work in post 385 or so.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thanks gee - I think you're right about flash.cfg. It's not easy to tell because of the format differences. I did the math (sectors * bytes) for the first few partitions and didn't see a size difference, but there are other things that are too odd about each format.
I'll go back and give that cwm a try that you mentioned. I have the recovery.img mentioned, but had heard so much negative stuff that I wasn't sure about it anymore.
Hashi.

I think it's only 2 partitions 12_USP and some other ones. An easier way might be to compare the actual file size that was downloaded with flash.cfg.
sent from my cyanogen(mod) vision

gee one said:
I think it's only 2 partitions 12_USP and some other ones. An easier way might be to compare the actual file size that was downloaded with flash.cfg.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Point taken: I suppose the good news is that before the recovery partition, there isn't any changes I can see, but which flash.cfg were you recommending you use in post 385 in the pure root thread? I'm not too sure of what I'm doing with flash.cfg yet, but I'm making some assumption that it has to be created or fetched for that first ./nvflash command, or else you are not working in sync with the partition table on the tf. Is there an automated way to recreate it where you're running nvflash from ?
Forgive me if those are pretty dumb questions. I just hate starting from scratch, and now that I've got an nvflash backup, I no longer trust it since your post about 5 up.

[Q] G2x, Bricked ? Help please (tried NVflash)

So, I bought a g2x ,Rooted with a flashed rom (not sure which) .
Would have random reboots one day battery died and it never woke up after.
I used to be able to get into cwm (v. 3.0.5 flashed) Now it just hangs at the LG logo and does nothing. I tried calling the guy who sold it to me to get some info of Recoverys and roms he doesn't answer.
1. A custom Recovery was flashed, but don't know which and how it was flashed.
2. A Custom rom was flashed but don't know which.
3. It will connect to my win7 pc and shows up in Device manager. (Battery out, vol up + vol dwn)
4. NVflash finds it, but never succeeds.
5. One-click finds it, but never succeeds.
Ive tried using NVflash, followed the instructions : Battery out, hold down vol up + dwn, plug in usb, run command. It loads Fastboot, then thedownload of the bootloader is sucessfull but just hangs there never send the img file. Then it just gives NV error. One-click does the same no matter what recovery I try to flash, ext or int.
When I was able to get into Recovery I would give error about not eing able to mount cache and such, even when I tried to go back to a stock rom. Now I'm not bale to get into any Recovery, Vol dwn + Pwr. Only LG logo.
What I think I need is to Repair the internal Memory and partitions. From ADB, only problem is I can't turn the phone one to get my pc to recognize and install the adb drivers.
Any help would be great!

NO HELP ?

Hi, I'm pretty new myself to the g2x device. However, I'm able to install recovery and flashed to a different custom ROM before. so I have some experience in this area. When reading your post, I'm not fully understanding what you're saying. Are you able to turn the phone on at all? Or you stuck at the LG logo?
Are the battery able to charge with the phone off? Just to be sure we have to isolate the battery to determine whether it is the problem. Is there anyone around you that have the g2x. The problem I think is that your phone is unable to install the driver into your computer. You need to use someone device to install the NV driver. Once you install the NV driver.
Attempt to turn it on first. If it still won't boot. Then we can try to reflash the Recovery to the 4.02. If you able to do all this and get to the recovery screen, then I think we are set... The goal is to get to the recovery screen.
I hope this help...But anything more technical, we have to wait for others to help..Best of luck

I'm not exactly new either, I've used NVflash at least once before to flash a recovery onto a Streak. I've rooted and Flashed recovery to a few MYtouch4g's.
But this G2X is just proving to be a problem.
To answer some of your questions.
When The phone does power on, it just hangs at the LG screen.
I tested the voltage of the battery with a meter and shows 3.8-3.7 volts of power, and is able to light a tiny light bulb. I also checked the charging port and power is running to the prongs which would touch the battery to charge. I did put the battery into another G2X and it worked. I no longer have access to the other G2X so do further testing.
I was and can still get the PC to recognize the phone via battery out, Vol up + Vol dwn & connect usb wire. PC recognizes beeps and phone shows up in device manager as "Android usb recovery mode" or something simular. So the APX driver is installed
When I try to NVflash (while keeping vol up + vol dwn) CWM 4 or Stock recovery its the same result, Loads bootloader and just hangs until it spits out an NV error (i'll post the result). (S/W Upgrade screen does show up on phone)
I cannot boot into any recovery via holding Vol dwn + Pwr.
Ieven tried the One-click recovery, no go, errors out.
I did find a Zip file with a recovery which is supposed to load the phone the factory supposed to format partitions and load original files. Uses NVflash, its just a bat file which runs the NVflash commands. found here. But this loads some files then when it gets to the formating partition it errors out. i'll post what it does. link > android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335474/25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15-03-2011/
Code:
C:\Users\Alan\Desktop\recover>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR
-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --configfile android_fa
stboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02804081423f7117
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.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: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. |
I think what needs to be done is to fix the internal partition I think they got damaged somehow?

Wow, you doing really good. Unfortunately, I think this problem is out of my league. The worst you can do is call T-mobile. Tell them your device is defective and they can send you a new one. But since your phone is rooted, if they found out then we can run into some problem. Most likely they will charge you 99 dollars for damaging the phone. I hope you'll find a way to fix your device because the G2x rock...
PS: I think the previous might have flash a lg optimus 2x Rom, which could explain why the phone is damage...If your phone is in fact a Optimus 2x and we flash the wrong recovery, that could also explain why we can't install the recovery...
android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335474/25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15-03-2011/

WARNING: This can destory your internalSD card partitions. If it's not broke don't fix it!
ALL COMMANDS ARE IN RED
I am not responsible for any damage you do to your phone.
I did this same thing to my phone... I was still able to get into recovery though. You can repair the internal partitions through ADB if you can still get into recovery.
Steps to recreate partitions.
Boot into recovery
from your PC open cmd prompt
change to your ADB directory
run adb shell
fdisk -H 1 /dev/block/mmcblk0
once in the fdisk of ../mmcblk0 you might as well delete all the partitions if you believe that they are corrupted
d
1
repeat for partition 2-8
one all of your partitions are gone you now have a blank internal SD and will need to execute the following to restore all the proper partition sizes
Partition 1
n
p
1
First Cylinder start 129
First Cylinder stop 55168
We will repeat this for partitions 2 and 3
Partition 2
n
p
2
Start 55169
Stop 63360
Partition 3
n
p
3
Start 63361
Stop 63616
On to partition 4 which will be extended (this is the last partion you will choose primary or extended)
Partition 4
n
e
4
Start 63617
Stop 975424
Now onto partition 4-8 which are automatically selected as logicall partions (no option is given)
Partition 5
n
Start 63681
Stop 64704
Partition 6
n
Start 64769
Stop 65088
Partition 7
n
Start 65153
Stop 261760
Partition 8
n
Start 261825
Stop 975424
Once you have done this the partitions are ready to be written to the internalSD
I would recommend choosing the command p to verify that all of your start and stop blocks are correct.
From this point you have the option to either quit without saving changes or to write the partition table itself. Once you are sure that you have entered all of your partitions correctly you can choose the command w
At this point you have recreated all the partitions on your InternalSD card. If you have a nandroid backup at this point you should be able to restore it without a problem once you copy it over to the internal or external (depending on which CWR you are running).
If I've forgotten any steps please feel free to comment and include them.
Thanks to TeamWhiskey for helping me resolve this issue when I had it...

casper200519 said:
WARNING: This can destory your internalSD card partitions. If it's not broke don't fix it!
ALL COMMANDS ARE IN RED
I am not responsible for any damage you do to your phone.
I did this same thing to my phone... I was still able to get into recovery though. You can repair the internal partitions through ADB if you can still get into recovery.
Steps to recreate partitions.
Boot into recovery
from your PC open cmd prompt
change to your ADB directory
run adb shell
fdisk -h 1 /dev/block/mmcblk0
once in the fdisk of ../mmcblk0 you might as well delete all the partitions if you believe that they are corrupted
d
1
repeat for partition 2-8
one all of your partitions are gone you now have a blank internal SD and will need to execute the following to restore all the proper partition sizes
Partition 1
n
p
1
First Cylinder start 129
First Cylinder stop 55168
We will repeat this for partitions 2 and 3
Partition 2
n
p
2
Start 55169
Stop 63360
Partition 3
n
p
3
Start 63361
Stop 63616
On to partition 4 which will be extended (this is the last partion you will choose primary or extended)
Partition 4
n
e
4
Start 63617
Stop 975424
Now onto partition 4-8 which are automatically selected as logicall partions (no option is given)
Partition 5
n
Start 63681
Stop 64704
Partition 6
n
Start 64769
Stop 65088
Partition 7
n
Start 65153
Stop 261760
Partition 8
n
Start 261825
Stop 975424
Once you have done this the partitions are ready to be written to the internalSD
I would recommend choosing the command p to verify that all of your start and stop blocks are correct.
From this point you have the option to either quit without saving changes or to write the partition table itself. Once you are sure that you have entered all of your partitions correctly you can choose the command w
At this point you have recreated all the partitions on your InternalSD card. If you have a nandroid backup at this point you should be able to restore it without a problem once you copy it over to the internal or external (depending on which CWR you are running).
If I've forgotten any steps please feel free to comment and include them.
Thanks to TeamWhiskey for helping me resolve this issue when I had it...
Click to expand...
Click to collapse
Can you help me with a video easier to work !!!!!!!! hopefully my phone will return to stock

I love you. Thanks for putting up the instructions.

chulun9999 said:
Can you help me with a video easier to work !!!!!!!! hopefully my phone will return to stock
Click to expand...
Click to collapse
I will try to get some video on it when I get time... If you get stuck on any of the instructions just ask and I'll check back often to try to help

casper200519 said:
I will try to get some video on it when I get time... If you get stuck on any of the instructions just ask and I'll check back often to try to help
Click to expand...
Click to collapse
you can guide me. I really do not understand to be able to work with it. I do not know where to start
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed

chulun9999 said:
you can guide me. I really do not understand to be able to work with it. I do not know where to start
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed
Click to expand...
Click to collapse
The how-to that I wrote is on recreating the partitions... I understand your error is with allowing nvflash to create them. Are you still trying to put an O2x image on a G2x?

casper200519 said:
The how-to that I wrote is on recreating the partitions... I understand your error is with allowing nvflash to create them. Are you still trying to put an O2x image on a G2x?
Click to expand...
Click to collapse
yes . i try to put an O2x image on a G2x . and now it happen this status . how do i repair my mistake .please help me

I am experiencing the same issue. Any luck resolving this????
I have CWM as my recovery system... So I cannot use ADB -- it won't connect.
Any ideas???

crosses fingers and prays
hope someone figures this out soon, i have been in many weird spots but none more than this g2x, it always worked fine and one day after reinstalling the cm7 nightly it never booted, just the LG boot screen and no more! windows even recognizes the phone but as fastboot only, NV flash says it worked but i never get further than LG screen, CLK Recovery wont pop up! hope someone solves this cus i love this phone!!

tylermauthe said:
I am experiencing the same issue. Any luck resolving this????
I have CWM as my recovery system... So I cannot use ADB -- it won't connect.
Any ideas???
Click to expand...
Click to collapse
ADB works in cwr recovery.if you find my other post labeled [REF]Repair internal SD in the dev area it has some q&a from others
Sent from my LG-P999 using XDA Premium App

Sorry for reviving this post!
This has been so helpful!
My phone was not able to boot in normal mode, but only in CWM! Thanks KAsp3rd!

need help with lg p999
hey am new here but am having the same problem and i need som help because i accedentaly used usde an nvflash tool for a lg p990 on my lg p999 and now am having problems with my baseband, sim,audio and my ime # is gone but the phone works but those are the problems that am having. so if any 1 help please assist

[Q] looking for nvflash zipfile with stock recovery

I've been unsuccesfully searching the forum for a zipfile containing the stock recovery for the TF101/nvflash/install script. Can someone help me find or get it ?

You can download the stock firmware from the ASUS website- unzip it, unzip it again, then use the blobunpack tools on the juicy blob it contains. The blob.SOS will be the stock recovery which can be flashed directly with nvflash. And by directly, I mean after a little editing of the flash.cfg file to point the SOS partition to your recently unblob'ed SOS file.
So after you flash all that, be advised that the stock recovery has the stock kernel that matches the ROM. This might be incompatible with your bootloader and have side effects such as bootloops, memory loss, nausea, constipation, and bootloops.

Thanks ! about your warning: say I've got an installed 8.6.5.21 and rooted it and installed CWM and then I do what you said and unblob the 8.6.5.21 firmware zip, won't I then have the correct bootloader ?

I would most likely say yes, but it all depends on how you got your 8.6.5.21 rom. If you rooted it using a pure root method like brk's or moshi's method, from a stock 8.6.5.21, then it's the stock bootloader for 8.6.5.21. If you used nvflash to erase and flash, then the bootloader will probably be whatever nvflash used- usually bootloader.bin that is in the zip with it. If you flashed a rooted 8.6.5.21 zip, it might have flashed the EBT as well, but this isn't always the case.
To make it more complex, there are two kernels on your TF- one in the LNX partition (boot.img) and one in the SOS (recovery).
The bootloops aren't well understood, so matching them might not make a difference. If you have access to nvflash, it's not that big a deal since you can simply reflash. If you have a later model, be careful since there aren't any second chances.
So, how did you get to the 8.6.5.21 rom?

Ohh, you can check you bootloader version by turning off your tf and then booting into recovery (power and volume down). The bootloader version will be in the white text at the top of the screen.
sent from my cyanogen(mod) vision

Fortunately I can use nvflash since my serial starts with B50.
I used the 8.6.5.13 zip that contains nvflash and download.bat first and used APX and ran the download.bat. Then I upgraded to 8.6.6.19 and rooted with Razorclaw. Then I updated to 8.6.5.21
Does that make sense to you to determine what bootloader I got ? Another problem that I got is that I have windows PCs here only and I don't know how I can compile the blobtools on a windows pc.

gee one said:
Ohh, you can check you bootloader version by turning off your tf and then booting into recovery (power and volume down). The bootloader version will be in the white text at the top of the screen.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
8.6.6.19-20111101
is that helpful ?

That's great. I suppose you could try the stock recovery with the 8.6.5.21 kernel. The worse that will happen is that you will have to reflash another recovery. Plus, your 8.6.5.21 rom seems to be doing fine.
I have no idea how to compile with windows, but lucky for you there are pre-compiled versions of the tools. I haven't used them for windows, but I suppose they would have some instructions. You'll probably have to use them from the command line or maybe powershell?
https://github.com/AndroidRoot/BlobTools/downloads
the nvflash ccommands will be something like this:
You probably don't have to change the flash.cfg file since you aren't using the --create command. Also, bootloader.bin is probably fine as is since it won't write this either. In the second nvflash command, the 5 indicates that you want to write the SOS partition. This corresponds to the id # in the flash.cfg file.
Code:
nvflash.exe --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
nvflash.exe --resume --download 5 /path/to/your/blob.SOS
nvflash.exe --resume --go
good luck!

Thanks for your help. In about half an hour its bedtime for me an coming days I have no time for my own things so it will be a few days before I will try out what you said. I had already searched for the windows binaries but couldnt find them so thanks !

Hello gee one !
i have nearly the same problem and I hope you can help me...but my englisch is poor, so please be patient.
I had to go back from revolverrom to StockWWE-rom (because of warranty). I ( hope) had unroot my devive with brk´s files .
I am not shure the way i rooted it in the pas,t but i think it was with the brk also.
i have Clockwork Recovery 3.2.0.1-roach2010-tf101-r11 and bootloader8.6.5.13 2011.09.25- hope this information is helpfull.
Witch steps had i to do to have all stock?
can i take brktool rootkit7.1 and the option restore backup / restore preverious backup-boot recovery+system ?
then i use /select the downloaded stockrom wwe from asus webside .?
Or am i wrong?
Kind regards
gandalf
(My model is a B60)

I have an opinion about unrooting for warranty purposes- either live with it or know how to unroot before you root. If your rooting method had said that it was not possible to unroot so your warranty would be irrevocably void, would you still have rooted your tf?

yes , i prove it- it is still rooted.
But i have another (maybe for the same reason) problem: ican´t wipe data -factory reset with clockwork mod.
the message: error removing data/system /packages.
-And i think thats also the reason for the freeze+ bootloops if i flash a custom-rom.
Kind regards
gandalf
by the way- i trie to find out the rootng method-

nvflash usage
Hi,
gee one said:
You probably don't have to change the flash.cfg file since you aren't using the --create command. Also, bootloader.bin is probably fine as is since it won't write this either. In the second nvflash command, the 5 indicates that you want to write the SOS partition. This corresponds to the id # in the flash.cfg file.
Code:
nvflash.exe --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
nvflash.exe --resume --download 5 /path/to/your/blob.SOS
nvflash.exe --resume --go
Click to expand...
Click to collapse
Thanks gee one for the nice tip (not tried yet).
I'm in a similar situation. Is there some documentation on nvflash (command line arguments and configuration file)?
Mikael

McKael said:
Hi,
Thanks gee one for the nice tip (not tried yet).
I'm in a similar situation. Is there some documentation on nvflash (command line arguments and configuration file)?
Mikael
Click to expand...
Click to collapse
There isn't a lot of documentation. I think you basically have to take a few things apart to see what is going on. Other devices use it too, so broaden your search to include the xoom, the galaxy tab, notion ink?, or anything else that uses the tegra 2. Once you see a few commands, you see what it does.
There is a paragraph at the end of this:
http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
I think nvidia has or had some flash tools on their developer website and you can check out some of the other forums for gamers and overclockers that might use nvflash to flash their gpus.
Also, there is a secret document hidden in the tool itself that I extracted by typing "nvflash --help"
Code:
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

Thanks for your answer, much appreciated.
I did some research but finding specific stuff isn't easy at all
gee one said:
There isn't a lot of documentation. I think you basically have to take a few things apart to see what is going on. Other devices use it too, so broaden your search to include the xoom, the galaxy tab, notion ink?, or anything else that uses the tegra 2. Once you see a few commands, you see what it does.
There is a paragraph at the end of this:
...
Click to expand...
Click to collapse
Thanks, I had seen the page but I missed this paragraph.
gee one said:
Also, there is a secret document hidden in the tool itself that I extracted by typing "nvflash --help"
Code:
...
--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
Click to expand...
Click to collapse
The help says the --setbct command shouldn't be used along with --download, is that the reason why you used 3 steps (3 commands)?
Mikael

No, that's more of a suggestion, as far as I can tell. It's more like read shouldn't be used with create. Setbct won't do much without create.
Info is pretty spare, I suggest backing up your data and then get flash happy. Get your hands dirty and after a few bootloops, you'll figure it out.
sent from my cyanogen(mod) vision

gee one said:
No, that's more of a suggestion, as far as I can tell. It's more like read shouldn't be used with create. Setbct won't do much without create.
Info is pretty spare, I suggest backing up your data and then get flash happy. Get your hands dirty and after a few bootloops, you'll figure it out.
Click to expand...
Click to collapse
Ok, I'll give it a try!
BTW, on a B60 TF101 Transformer is it relatively safe to play with nvflash? (In other words, should I still be able to reflash everything with nvflash even if I break everything up?)
Mikael

Based on info from the internet, you should have access to nvflash with your b60. There is an unbricking thread in development.
sent from my cyanogen(mod) vision

McKael said:
Ok, I'll give it a try!
Mikael
Click to expand...
Click to collapse
Well... FYI it worked perfectly. Everything looks right now and I was able to apply the latest OTA ICS update.
(What I'm wondering is why my attempts from Android itself, using dd, were not successful.)
And, for the record, there are useful information there:
http://www.cyber.com.au/~twb/doc/tf101.html
Thanks again gee one!
Mikael

[Q] Bricked my TF101G B90

Hi all,
I've put my transformer into an infinite reboot loop. It starts booting into TWRP, I see the splash and after about 2 seconds it drops to a console with the following message
Code:
Updating partition details...
E:Unable to mount '/staging'
Formatting Cache using make_ext4fs
There are two more lines that come up after that but I can't see because the reboot happens too fast. If hold power up during the reboot, I can get into what ppears to be APX mode, i.e. the tablet stops rebooting, and the screen is completely black. Wheelie detects the device in APX mode but nvflash doesn't work afterwards.
The transformer has a serial number starting with B90, so it's at least SBK2.
Here's how I got into this lousy situation ...
I rooted using the adb commands of the wolf exploit as found in the PERI tool. After that I was trying to install native ubuntu using the net-install rootfs following the instructions in those two links. Everything seemed to work, I got wifi, It downloaded, it installed. But on reboot all I got was an initramfs busybox prompt. I'd chosen the jhinta kernel, so I read though the entire net-install thread again, and found the following three posts:
http://forum.xda-developers.com/showpost.php?p=31458873&postcount=148
http://forum.xda-developers.com/showpost.php?p=31466313&postcount=152
http://forum.xda-developers.com/showpost.php?p=31544961&postcount=162
The short version of which was that the script trying to flash the jhinta kernel didn't work, and I needed to do it manually. So I took the blob from the zip attached to the first post, unpacked it and flashed the unpacked blob to /dev/block/mmcblk0p4, /dev/block/mmcblk0p10 and /dev/block/mmcblk0p9 in turn, testing reboots in between. After flashing to mmcblk0p10 didn't make a difference, I tried flashing on mmcblk0p9 but dd complained about running out of space. The image was 8.8Mb and the partition seemed to be only 8Mb in size. I figured this would be a problem, because that partition is meant to be the recovery kernel I vaguely recalled. So just to be safe, BEFORE rebooting I flashed the recovery image from it's zip file again. I rebooted, and now I'm in the infinite loop.
I don't have access to recovery. I am hoping that I can use nvflash and wheelie maybe to return to stock and go over it again from scratch, but wheelie/nvflash reports the following:
Code:
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: 0x37c708340003257
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Nvflash started
[resume mode]
failed executing command 11 NvError 0x8
command failure: create failed
Nvflash started
[resume mode]
connection failed NvError 0x8
I have a nasty feeling that wheelie doesn't work for my TF101G, but I'm not sure. What else can I try, or should I send it back to ASUS and pay for them them return it to stock?
Thanks in advance

NVFlash and Wheelie do not work with the TF101G as it has a different SBK from the two TF101 SBK's.
The SBK is not known because not enough TF101G users tried to crack it.
You can try flashing a different recovery using ADB when in your current TWRP, but beyond that you may be in trouble.
Might want to try either 2.3.2.3 or 2.5.0.0 TWRP.

Hmm, the machine doesn't stay in recovery long enough to do anything via ADB.
Code:
adb wait-for-device
doesn't unblock through three reboot cycles.
So I have two options:
1. try to crack the SBK
2. ship it off to ASUS
Any ideas on how to start on 1? Loop through all the options of wheelie -o? I'm hoping there's a better way to go about it?

Sadly, that is probably true, but you are forgetting option 3: Get a new tablet.

[Q] complete reformat and start over

After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.

aknisley said:
After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.
Click to expand...
Click to collapse
0 is for internal storage
Obb is app data folder
we can format 0
but I will only delete data of apps
install different ROM.
press thanks if I helped you.

aknisley said:
After several ROM installs and getting to bricking, I ended up with folders with names like "0" and "obb". Is there a way to reformat the internal storage and get back the beginning? Currently using KATKISS.
I wanted to put Ubuntu on but "failed" in TRWP when installing the zip.
Click to expand...
Click to collapse
why not just return to stock and begin again.
follow this: http://www.transformerforums.com/forum/asus-transformer-tf101-development/31919-frederuco-s-guide-flash-tf101-back-stock.html

barkeater said:
why not just return to stock and begin again.
follow this: http://www.transformerforums.com/forum/asus-transformer-tf101-development/31919-frederuco-s-guide-flash-tf101-back-stock.html
Click to expand...
Click to collapse
Well, I cannot, because I cannot flash TWRP. TO follow the recipe, It calls for TWRP and all I have is CWM. Try as I might, I cannot install TWRP. I tried via ZIP and also from blob. Nothing. As I write this, I am trying to go back to stock via CWM. It is taking a while, so it may work. As of now, I have been able to re-flash CM10_Nightly, but when I try ano other ROM, it boot loops. I may have really hosed it, now, though. We shall see. I am not averse to NVFlashing it , but have not yet found instructions to do that under Linux. I do not have a Windows computer and most of them call for it.

In case it saves someone else's bacon, I thought I'd post my findings.
I rebooted into windows and tried the 'one click transformer root' tool. It runs and then tells me that it cannot deal with my tablet as it is not running ICS. I tried another one called which is supposed to return to stock called EasyFlasher 0.83. It acted like it installed the stock image, but did not do anything. It would always reboot to CWM.
In CWM., I could wipe and flash an image, but it would never boot. Just bootloop. I had CM10 on the tablet and am guessing that the install was not quite kosher. I could not install any other recovery image, either.
To solve it, I downloaded the blob tools
Blob Tools
I already had wheelie since I used the CM page to install it
CM10 install
I unpacked the image by first unzipping the zip from asus. IN it was a file called 'blob'. I then unpacked it:
Code:
./blobunpack latest/blob
it created 4 files called blob.APP, blob.EBT, blob.LNX and blob.SOS
We want the blob.SOS file. I put it in the wheelie directory and modified the commands I used to initially install the CWM recovery:
Code:
# ./wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
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: 0x370018042607097
[=] 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
# ./nvflash -r --download 5 blob.SOS
Nvflash started
[resume mode]
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
# ./nvflash -r --go
Nvflash started
[resume mode]
My zip file was in the root of the SD card, so it immediately reflashed itself after it rebooted. Finally!

congrats!
Yeah, I have no experience with cwm or any other os other than Windows. Glad you got it sorted. Happy Holidays!

barkeater said:
congrats!
Yeah, I have no experience with cwm or any other os other than Windows. Glad you got it sorted. Happy Holidays!
Click to expand...
Click to collapse
Like I said, though, I could not get it to do anything in Windows or Linux. I think it was a permissions problem or a directory structure which was incorrect. Regardless, this worked and i was able to root it using one click root. I was unable to flash the twrp recovery by the preferred method and had to first 'fix sdcard write permissions' from the twrp app. Then the app would not flash it. So i used dd via adb and got it. I have flashed katkiss and am trying it out. I feel as though i have been released from cwm/cm10 hell, finally.