Database Info

[Q] NVFlash

So I never used it before, since I thought it would be fairly straightforward. But nope, it turns out more complicated. First I wanted to backup the device, yet when I downloaded the zip file, I only see scripts. How the hell do you run them. Do I replace the files in the original folder and run the download.bat? Videos online show it formatting and installing prime when you run download.bat. After backing up I wanted to dual boot Ubuntu, yet those instructions aren't much more clear. Again do I replace those files in the zip with the original nvflash folder? How do I run the script once I put them in there? The Nvflash.exe doesnt help. And he says to put recovery.img, boot.img, and system.img in the /image folder (for prime), yet I have no idea where those are. NVFlash hasnt been explained well. I see videos online showing how to use it for basic root, but when it comes to anything else, everyone is silent.

Here:
www.androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
There is a link to the prime rom 1.4 needed too.
1- download nvflash
2-download the primerom 1.4
3-extract both zips
4- in the extracted primerom folder, copy system.img, boot.img, recovery.img
5-paste them in your nvfash folder
6-connect your tablet to ur pc n enter APX mode
7-double click on download.bat(yes it looks like a script)
8-sit and relax and your tablet will boot with thw prime rom.
9-now, boot into recovery (POWER+ DWN) THEN UP. wipe everything and install the rom of your choice.
Sent from my Transformer TF101 using Tapatalk

dude2k5 said:
So I never used it before, since I thought it would be fairly straightforward. But nope, it turns out more complicated. First I wanted to backup the device, yet when I downloaded the zip file, I only see scripts. How the hell do you run them. Do I replace the files in the original folder and run the download.bat? Videos online show it formatting and installing prime when you run download.bat. After backing up I wanted to dual boot Ubuntu, yet those instructions aren't much more clear. Again do I replace those files in the zip with the original nvflash folder? How do I run the script once I put them in there? The Nvflash.exe doesnt help. And he says to put recovery.img, boot.img, and system.img in the /image folder (for prime), yet I have no idea where those are. NVFlash hasnt been explained well. I see videos online showing how to use it for basic root, but when it comes to anything else, everyone is silent.
Click to expand...
Click to collapse
It's not easy to explain something that has so many uses and so little documentation. Try to find anything over at nvidia where this thing comes from and let us know how that goes:
Here is all I've gotten and it is just by typing in (either in linux or Win) this:
Code:
nvflash --help
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
--updatebct <bctsection>
bctsection should refer to the section of the bct we are updating.
Curently we suport updates for following sections
<SDRAM> updates SdramParams and NumSdramSets fields
<DEVPARAM> updates DevParams, DevType and NumParamSets
<BOOTDEVINFO> updates BlockSizeLog2, PageSizeLog2 and PartitionSize
And this crazy nvflash utility has been the most useful small program I've had for the transformer and I think will remain that way. Some of the commands (e.g. when you insert the SBK or Secure Boot Key) seem like magic, and I've no idea where people have come up with these things. Other pieces of it are pretty clear like using --read {filename} to put a partition .img file on the PC as a backup of that numbered partition.
Sorry: I'm still learning this as well, and will be well . forever.

[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

[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] NVFlash Working Yes or No?

Are folks having luck with NVFlash? I have read that it has been working for some and not others. If it is then I will go ahead and follow the guide and harvest my snapshots. I would really like to have the insurance that come with access to the low level flashing that NVFlash offers. If folks are having a lot of drama with it I will probably just wait until the kinks are worked out.
FYI:
I have a 32GB TF300T on ICS (.30). I'm unlocked and have CWM installed.
Best,
Feend

Yes, NVFlash works if you properly generate the files from the bootloader and backup once you have NVFlash access. If done properly, you can go back to ICS bootloader from JB.
Follow the guide, and don't update to Jellybean until you are certain you can access NVFlash via Wheelie on your device.

jimpmc said:
Yes, NVFlash works if you properly generate the files from the bootloader and backup once you have NVFlash access. If done properly, you can go back to ICS bootloader from JB.
Follow the guide, and don't update to Jellybean until you are certain you can access NVFlash via Wheelie on your device.
Click to expand...
Click to collapse
Could you provide the proper information about using Nvflash to restore when you have an issue?

tobdaryl said:
Could provide the proper information about using Nvflash to restore when you have an issue?
Click to expand...
Click to collapse
Seems like someone on the tf700t forum may have figured it out.
http://forum.xda-developers.com/showpost.php?p=32796329&postcount=189

daws said:
Seems like someone on the tf700t forum may have figured it out.
http://forum.xda-developers.com/showpost.php?p=32796329&postcount=189
Click to expand...
Click to collapse
Thanks for the information.
I had thought that was proper until I saw a post by rayman (nvflash OP and Dev).
"Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything.."
It appears we are still missing information needed for proper restore.
I had hoped the poster suggesting nvflash had found a goldmine and could help us out.
Thanks again!

tobdaryl said:
Thanks for the information.
I had thought that was proper until I saw a post by rayman (nvflash OP and Dev).
"Your issue is the that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything.."
It appears we are still missing information needed for proper restore.
I had hoped the poster suggesting nvflash had found a goldmine and could help us out.
Thanks again!
Click to expand...
Click to collapse
Well if it's not a good idea to flash bricksafe.img to restore a bricked tablet, it makes you wonder what the point of the file is. For myself, in the absence of any better instructions, I have saved a copy of the tf700t post. I hope I never have to restore a bricked tablet but knowing me, it's a possibility.

daws said:
Well if it's not a good idea to flash bricksafe.img to restore a bricked tablet, it makes you wonder what the point of the file is. For myself, in the absence of any better instructions, I have saved a copy of the tf700t post. I hope I never have to restore a bricked tablet but knowing me, it's a possibility.
Click to expand...
Click to collapse
Thank you for the help with nvflash.
I have saved your information also.

One can go back to ICS from JB, by doing the following:
Obtain an official ASUS ICS firmware.
Unzip the file to get to the blob.
Use blobunpack to save the blob.ebt, blob.lnx, and blob.app files. The blob.ebt is an ICS bootloader.
Obtain CWM or TWRP for ICS.
Unzip the recovery file to the blob.
Use blobunpack on the recovery blob to save the recovery.sos (it will be called whatever your blob file was)
put the blob.ebt, blob.lnx, blob.app and recovery.sos files all in the nvflash directory.
Then run:
wheelie --blob blob.bin
nvflash.exe -r --download 4 blob.EBT
nvflash.exe -r --download 5 recovery.sos
nvflash.exe -r --download 6 blob.LNX
nvflash.exe -r --download 10 blob.APP
nvflash.exe -r --go
Boot into recovery, wipe data & cache, then reboot. You will end up in stock ICS. If you wanted to just install a custom ROM, you can skip downloading partitions 6 and 10, and just install the bootloader and recovery, and then just go into the recovery and install a custom ROM from there. Make sure to wipe the data and cache/dalvik cache.

jimpmc said:
One can go back to ICS from JB, by doing the following:
Obtain an official ASUS ICS firmware.
Unzip the file to get to the blob.
Use blobunpack to save the blob.ebt, blob.lnx, and blob.app files. The blob.ebt is an ICS bootloader.
Obtain CWM or TWRP for ICS.
Unzip the recovery file to the blob.
Use blobunpack on the recovery blob to save the recovery.sos (it will be called whatever your blob file was)
put the blob.ebt, blob.lnx, blob.app and recovery.sos files all in the nvflash directory.
Then run:
wheelie --blob blob.bin
nvflash.exe -r --download 4 blob.EBT
nvflash.exe -r --download 5 recovery.sos
nvflash.exe -r --download 6 blob.LNX
nvflash.exe -r --download 10 blob.APP
nvflash.exe -r --go
Boot into recovery, wipe data & cache, then reboot. You will end up in stock ICS. If you wanted to just install a custom ROM, you can skip downloading partitions 6 and 10, and just install the bootloader and recovery, and then just go into the recovery and install a custom ROM from there. Make sure to wipe the data and cache/dalvik cache.
Click to expand...
Click to collapse
Great! Thanks for the information.
This should help many others who are lost.

jimpmc said:
One can go back to ICS from JB, by doing the following:
Obtain an official ASUS ICS firmware.
Unzip the file to get to the blob.
Use blobunpack to save the blob.ebt, blob.lnx, and blob.app files. The blob.ebt is an ICS bootloader.
Obtain CWM or TWRP for ICS.
Unzip the recovery file to the blob.
Use blobunpack on the recovery blob to save the recovery.sos (it will be called whatever your blob file was)
put the blob.ebt, blob.lnx, blob.app and recovery.sos files all in the nvflash directory.
Then run:
wheelie --blob blob.bin
nvflash.exe -r --download 4 blob.EBT
nvflash.exe -r --download 5 recovery.sos
nvflash.exe -r --download 6 blob.LNX
nvflash.exe -r --download 10 blob.APP
nvflash.exe -r --go
Boot into recovery, wipe data & cache, then reboot. You will end up in stock ICS. If you wanted to just install a custom ROM, you can skip downloading partitions 6 and 10, and just install the bootloader and recovery, and then just go into the recovery and install a custom ROM from there. Make sure to wipe the data and cache/dalvik cache.
Click to expand...
Click to collapse
Thanks for posting that information.
Do you know if the above commands would also serve to unbrick a tablet? I have a suspicion that they might but only in some cases.

daws said:
Thanks for posting that information.
Do you know if the above commands would also serve to unbrick a tablet? I have a suspicion that they might but only in some cases.
Click to expand...
Click to collapse
This should work in some instances, but if the partition tables have been corrupted or overwritten, then more might be needed. For the TF101, the NVFlash .bat file completely rewrote the partitions and something similar could be attempted, although I'm not sure of the full set of commands to do so on the TF300. Best bet is to try and get into a working recovery and take it from there.

jimpmc said:
One can go back to ICS from JB, by doing the following:
Obtain an official ASUS ICS firmware.
Unzip the file to get to the blob.
Use blobunpack to save the blob.ebt, blob.lnx, and blob.app files. The blob.ebt is an ICS bootloader.
Obtain CWM or TWRP for ICS.
Unzip the recovery file to the blob.
Use blobunpack on the recovery blob to save the recovery.sos (it will be called whatever your blob file was)
put the blob.ebt, blob.lnx, blob.app and recovery.sos files all in the nvflash directory.
Then run:
wheelie --blob blob.bin
nvflash.exe -r --download 4 blob.EBT
nvflash.exe -r --download 5 recovery.sos
nvflash.exe -r --download 6 blob.LNX
nvflash.exe -r --download 10 blob.APP
nvflash.exe -r --go
Click to expand...
Click to collapse
How Could I do :
Unzip the recovery file to the blob
and
Use blobunpack on the recovery blob to save the recovery.sos (it will be called whatever your blob file was)

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