Database Info

[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] nvflash doubts

I think I already understood the idea with the Secure Key and bootloader, but I still do not completely understand the remaining options:
Is the --configfile the partition table of the device? Can I download it using --getpartitiontable ?
What is --odmdata for? Where did people get the 0x300d8011 value from?
Can I use the --getbct command to download the BCT from my own Transformer or do I need to use the one being distributed in these forums?
If there is an online guide, please direct me to it
Thanks in advance to everyone.

I'm not an expert by any stretch of the imagination, so if you brick your TF, you've been warned...
The --configfile option is used with the --create or --format_all options and species how the memory is partitioned and formatted. It specifies size, attributes, and file system types.
The partition table from --getpartitiontable is mostly sizes, so you wouldn't be able to reverse engineer the config file from just the partition table, although the reading the partitions would probably tell you the rest of the options.
I think the BCT specifies, among other things, hardware configurations such as 16GB vs 32GB. These are specific and you have to get it right.
This is from something I dug up from the Notion Ink
An output BCT file is the header structure stored on the secondary boot device
i.e.nand/emmc/spi-flash, which primarily stores information:
- required to initialise and configure secondary boot device
- required to initialise and configure SDRAM
- required to locate and verify boot loader
ans other non-volatile information that is shared across boot loader and OS
Click to expand...
Click to collapse
I'm not sure if you can write the BCT without erasing everything first. I thought it was encrypted and tied to the bootloader??

gee one said:
I'm not an expert by any stretch of the imagination, so if you brick your TF, you've been warned...
The --configfile option is used with the --create or --format_all options and species how the memory is partitioned and formatted. It specifies size, attributes, and file system types.
The partition table from --getpartitiontable is mostly sizes, so you wouldn't be able to reverse engineer the config file from just the partition table, although the reading the partitions would probably tell you the rest of the options.
I think the BCT specifies, among other things, hardware configurations such as 16GB vs 32GB. These are specific and you have to get it right.
This is from something I dug up from the Notion Ink
I'm not sure if you can write the BCT without erasing everything first. I thought it was encrypted and tied to the bootloader??
Click to expand...
Click to collapse
The thing is: from what I understood, to use --getpartitiontable you need to use the --bct, which receives a .bct file as an argument. And if this file contains device specific information, then I really should use one that is for my own Transformer. And this is exactly why I tried to use --getbct, but the command is failing. Have you seen any example of its usage? Do you know where people have obtained the .bct they are distributing in the scripts?
Thanks

I've seen a buildbct executable for the Notion Ink that takes a specification file and spits out a bct.
I don't think the bct is specific to each device, just each type of device, and it might be pretty generic at that. It's stuff like ram speed and type. If you have a 32GB version, it might not work, but I don't think it would hurt to try. I've used the getpartitiontable command with the bct file that is floating around with nvflash. It seems to work.
I tried to read the bct from the TF and got an error.

I don't seem to be able to find the buildbct executable anywhere :/ And I also get an error while trying to use --getbct, so I guess that is not the way to go.
Since I'm rather curious about this, I'll try to ask the question in the Dev forums. Someone there will know where the file came from, no?
BTW, do you know anything about the --odmdata argument?

vhda said:
I don't seem to be able to find the buildbct executable anywhere :/ And I also get an error while trying to use --getbct, so I guess that is not the way to go.
Since I'm rather curious about this, I'll try to ask the question in the Dev forums. Someone there will know where the file came from, no?
BTW, do you know anything about the --odmdata argument?
Click to expand...
Click to collapse
No, go fish!
Supposedly this worked on a Gtab, so what could it hurt?
./nvflash --bl bootloader.bin --getbct --bct jl-bct.bct --go
http://forum.xda-developers.com/showthread.php?t=934023
The BCT partition is pretty large, but if you poke around with a hex editor (bad hacker!), it's the same 4080 bytes repeated over and over.
EDIT: some insight into the odmdata. last post- http://forum.xda-developers.com/showthread.php?t=1039547

The thread in [1] seems to agree with you. According to it the BCT partition is written from the .bct file, as long as the --create option is used. If this is true, then running the commands below (still did NOT test it) should allow backing up the original BCT:
./nvflash --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --odmdata 0x300d8011 --bl bootloader.bin --bct transformer.bct --setbct --go
./nvflash -r --getbct -bct backup.bct
[1] http://forum.xda-developers.com/showthread.php?t=1010659

Death of a Transformer on Christmas Eve

Hi people. The story is this one:
the night before Christmas Eve, I left my transformer in charge, and, before I went to sleep, battery was full, so I unplugged it, leaving it switched on, on the desk.
The morning later, when I tried to unlock it, it wasn't responding at any combinations of events, starting by pressing Power button, and trying to dock/undock it ecc.
At first, I thought to a SOD, but there was no way to wake it up.
So, I tried to plug it to a pc, and it was only recognized as an APX device, there was no way to use ADB, and if I tried to restore to stock (i.e.) using NVFLASH, I only got an error about the impossibility of read/write (I'll post the log later).
What happened in your opinions? I was thinking to RMA it, but I cannot get back to stock, so, I would have my warranty voided.
Any ideas and/or advices?
EDIT: I add the log of NVFLASH:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x**************
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: 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
- 65536/943193 bytes sent
\ 131072/943193 bytes sent
| 196608/943193 bytes sent
/ 262144/943193 bytes sent
- 327680/943193 bytes sent
\ 393216/943193 bytes sent
| 458752/943193 bytes sent
/ 524288/943193 bytes sent
- 589824/943193 bytes sent
\ 655360/943193 bytes sent
| 720896/943193 bytes sent
/ 786432/943193 bytes sent
- 851968/943193 bytes sent
\ 917504/943193 bytes sent
| 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

aldur999 said:
Hi people. The story is this one:
the night before Christmas Eve, I left my transformer in charge, and, before I went to sleep, battery was full, so I unplugged it, leaving it switched on, on the desk.
The morning later, when I tried to unlock it, it wasn't responding at any combinations of events, starting by pressing Power button, and trying to dock/undock it ecc.
At first, I thought to a SOD, but there was no way to wake it up.
So, I tried to plug it to a pc, and it was only recognized as an APX device, there was no way to use ADB, and if I tried to restore to stock (i.e.) using NVFLASH, I only got an error about the impossibility of read/write (I'll post the log later).
What happened in your opinions? I was thinking to RMA it, but I cannot get back to stock, so, I would have my warranty voided.
Any ideas and/or advices?
Click to expand...
Click to collapse
if read/write is truly impossible, having a custom rom shouldnt be detectable without great effort (the flash memory has died). Likely just RMA it, i suspect that theyll replace it.
We need your log though

joshman99 said:
if read/write is truly impossible, having a custom rom shouldnt be detectable without great effort (the flash memory has died). Likely just RMA it, i suspect that theyll replace it.
We need your log though
Click to expand...
Click to collapse
Ok I attached log at first post. In case of replace, they would just give me another transformer?

sorry for your lost dude

Hearmeman said:
sorry for your lost dude
Click to expand...
Click to collapse
Thanks, it's been very hard!

you must've been rather naughty this year.
Sent from my Transformer TF101 using xda premium

So, what is the cause of all these horror stories I keep reading about the Transformer? Make me nervous every time I press the power button!
Is there something internal that is defective and basically our Transformers are a ticking time bomb? Or is it something else?

SiNJiN76 said:
So, what is the cause of all these horror stories I keep reading about the Transformer? Make me nervous every time I press the power button!
Is there something internal that is defective and basically our Transformers are a ticking time bomb? Or is it something else?
Click to expand...
Click to collapse
i think it's like any other device - sometimes some are bad .... :\

Yeah, sounds like the sdcard is dead. They shouldn't be able to detect you got a custom rom going there. And trust me, it will take them a heck of a lot more effort to replace the sdcard than to just give you a new TF. So, yeah, chances are if you RMA it you will get another TF.
Just RMA it, man.
PS - Been naughty this year?

goodintentions said:
Just RMA it, man.
PS - Been naughty this year?
Click to expand...
Click to collapse
I already RMA it, I'm just waiting for UPS
And, I'm italian, I know the word naughty only in a way, so, I'll limit myself saying I I've been very unlucky

Got the same problem. Well not entirely tho. I bricked my transformer when returning to stock. So it's a stock rom on the moment, but it won't boot and i can't go to recovery it gives a little android figure with a error sign. So i'll probably just go back to the store and or RMA it.

Hmm, how long is the warranty again? My box is at school but I'm home for the holidays..

In Europe there is a legal right for 2 year warrenty, (but stores mostly say it's 1 year)

It ended very well. I RMA it 28th December, and today they have sent back my repaired transformer

[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] New info (in OP bold txt), can you answer? - Power on/Reboot goes into APX mode

Sorry, other post is a bit hard to read, was trying to see if upgrading my TF300t (unlocked, rooted, nvflash run) to v9.4.3.30 would fix it - which unfortunately didn't.
I'm having issues resolving powering up and reboots automatically going into APX mode. Plus lost my icons (fastboot, wipe, ? ) when powering up w/vol down
button. Only have choice of Recovery or let it cold-boot into ICS. The original help post for added details is at:
Original post with more details
I'm thinking the AndroidRoot booloader I've been running from when I originally created my nvflash backups got corrupted. The update (via Install Zip in TWRP) does
not seem to have updated the bootloader. In reading even more posts, another user shows:
The Device is UnLocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.3.30-20120604" A03
Checking for android ota recovery
I see the exact same except my version is "WW_epad-9.4.3.30-20120604", which makes me think the bootloader isn't getting updated correctly & is still the original AndroidRoot
version which became corrupted? I also double checked the new EBT blob I'm flashing via a hex editor and it shows it has a US SKU! So does that mean nvflash isn't truly
flashing it? If not, how can I get it to take either with nvflash, ADB, or TWRP?
Also can see (lack of) progress below *sigh*

wha2do said:
Sorry, other post is a bit hard to read, was trying to see if upgrading to v9.4.3.30 would fix it - which unfortunately it didn't.
I'm having issues resolving powering up and reboots automatically going into APX mode. Plus lost my icons (fastboot, wipe, ? ) when powering up w/vol down
button. Only have choice of Recovery or let it cold-boot into ICS. The original help post is at:
Original post with more details
See (lack of) progress below.
Click to expand...
Click to collapse
Well, still need some suggestions/help. I've run:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 twrp2.5.0.0.img
Didn't do anything to fix the APX issue nor get my fastboot icon back. I'm wondering if I should try using
the bricksafe.img file I'd created before - not sure what exactly it contains and if it would be any different.
At this point I'm days away from seeing if I can return the tablet (under a 2 year warranty plan - thought it
was said if they can't fix, get my money back rather than a replacement) and look at something else.
I've read and read and not found anything useful yet and not much on the nvflash backup file use for restoring...
Help!

You could try erasing the misc partition.
I think this this is the right command, but you might have to check the exact command syntax (don't have nvflash handy right now):
nvflash -r --format_partition 3
Sent from my TF300T using Tapatalk

f69m said:
You could try erasing the misc partition.
I think this this is the right command, but you might have to check the exact command syntax (don't have nvflash handy right now):
nvflash -r --format_partition 3
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Thx & that's the correct syntax, but what is nvflash's partition 3 (misc)? And is this nvflash PartitionId 3 or adb's mount point /dev/block/mmcblk0p3? In
nvflash's partition table list, MSC (assuming this is the same "misc" partition) is listed as PartitionId 12...
When I do a list of partition tables from nvflash, it shows this as type Partition_table and named PT. I did install the Partition Table app
and see where 3 may be coming from, as in the mount point /mmcblk0p3, labelled as MSC?
Looking at other known nvflash/Partition table comparisons, one nvflashes blob.APP (system) to partition 10 yet the Partition Table app
shows /system, labelled as APP mounted on /mmcblk0p1. And with blob.SOS, nvflash sends it to 5 yet the adb command uses /mmcblk0p4...
I maybe interpreting these all wrong and it's ok - just being very cautious about formatting a partition and what effect it will have... Thanks in advance for clarification!

wha2do said:
Thx & that's the correct syntax, but what is nvflash's partition 3 (misc)? And is this nvflash partition 3 or adb's mount point /dev/block/mmcblk0p3?
When I do a list of partition tables from nvflash, it shows this as type Partition_table and named PT. I did install the Partition Table app
and see where 3 may be coming from, as in the mount point /mmcblk0p3, labelled as MSC?
Looking at other known nvflash/Partition table comparisons, one nvflashes blob.APP (system) to partition 10 yet the Partition Table app
shows /system, labelled as APP mounted on /mmcblk0p1. And with blob.SOS, nvflash sends it to 5 yet the adb command uses /mmcblk0p4...
I maybe interpreting these all wrong and it's ok - just being very cautious about formatting a partition and what effect it will have... Thanks in advance for clarification!
Click to expand...
Click to collapse
Sorry, my bad, haven't really used nvflash much. Just assumed it would be the same numbers. :/
Yes, I mean the MSC or misc partition /dev/block/mmcblk0p3.
It holds commands for the bootloader, for eaxample "recovery", etc. Cleaning it might make your bootloader behave. Might.
Sent from my TF300T using Tapatalk

f69m said:
Sorry, my bad, haven't really used nvflash much. Just assumed it would be the same numbers. :/
Yes, I mean the MSC or misc partition /dev/block/mmcblk0p3.
It holds commands for the bootloader, for eaxample "recovery", etc. Cleaning it might make your bootloader behave. Might.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
No problem at all, I appreciate the help and I just always try to be cautious! Just to be doubly sure, here's the excerpt from
getting the partition table info from nvflash earlier today:
PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096
So doing the nvflash -r --format_partition 12 command should be safe. Wondering, does it make sense to do this first:
nvflash --resume --rawdeviceread 317568 512 msc.img
Should back up what's there if need it afterwards...again being safe, lol!

wha2do said:
No problem at all, I appreciate the help and I just always try to be cautious! Just to be doubly sure, here's the excerpt from
getting the partition table info from nvflash earlier today:
PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096
So doing the nvflash -r --format_partition 12 command should be safe. Wondering, does it make sense to do this first:
nvflash --resume --rawdeviceread 317568 512 msc.img
Should back up what's there if need it afterwards...again being safe, lol!
Click to expand...
Click to collapse
Yes, this looks like the right one. Unfortunately /proc/partitions does not give a start sector, but the name MSC matches. /proc/partitions gives the size at 2048, but that should be 1K blocks, so maching the 512 4K-blocks shown by nvflash.
Yeah, should be save to erase, but being careful and having a backup never hurts. Might even be interesting to have a glance at the contents.
Sent from my TF300T using Tapatalk

Well, I think if indeed the bootloader is corrupted I've found my flashes of a new one aren't taking. I tried nvflashing blob.EBT, blob.SOS, blob.LNX, and then blob.APP from the stock v9.4.3.30
update (all in same nvflash session) and all listed as successful. The rest did take...but wasn't sure about blob.EBT. I expected to see the US_epad version (and I've checked the blobs
with a hex editor and they indeed have the US SKU).
I ended up sideloading v9.4.3.17 in TWRP and saw the bootloader version stayed the same (WW_epad-v9.4.3.30). With a stock recovery back in place, I tried to see if I could take an OTA
back to v9.4.3.30, but said no updates were available. Ended up sideloading v9.4.3.30 and am back to where I was...
I also let the tablet battery run down completely, charged fully over night hoping something might "reset", but no go...
Last thing I'll be trying later is a factory reset via TWRP (read try doing it three times to be sure) and reload v9.4.3.30. If not, looks like I have two options: 1) try the reformat of the MSC partition
and/or do an nvflash rawdevicewrite of the bricksafe.img file. Just worried with both that it'll create more issues (being very careful since at least I can still get into APX, ADB, and ultimately boot up).
Any recommendations/suggestions on how to get blob.EBT to flash successfully or which step to try next? Please, please, please...lol!

I tried doing a factory reset. Probably overkill, but also wiped cache, Dalvik, and data while in TWRP. Then booted up, skipped set up, and did this two more times. Didn't have any effect,
so I tried sideloading v9.4.3.30 and same old story...
I finally quit and restored my nandroid made prior to the factory resets and now have to decide:
Try the format of the MSC partition or nvflash bricksafe.img. Again just being very cautious since while tedious, I can still use my tablet by restarting via nvflash.
Wish I could get advice from one of the AndroidRoot members!!
Any ideas/recommendations at this point?