Database Info

How to install CWM on TF101? I'm not kidding, I didn't find the answer so far here

Ok,
Before people start complaining I should not post this: I have searched the forum and have not found a solution. Therefore please let me specifically describe my situation and please when responding, be accurate, exact, non-ambiguous, complete, and correct.
I have a Chinese TF101 with build HRI66.CN_epad-8.2.3.13-20110511 (I assume that translates to build 8.2.3.13)
I tried running the ROOT guide located in http://forum.xda-developers.com/showthread.php?p=17285912#post17285912
Unfortunately that does not work on my TF101. I get:
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Detected honeycomb! Starting honeybomb mode (scale=10).
[+] Found system: 0xaff181a1 strcmp: 0xaff37b85
[+] Found PT_DYNAMIC of size 240 (30 entries)
[+] Found GOT: 0x00017368
[+] Using device /devices/platform/sdhci-tegra.2/mmc_host/mmc1
[*] vold: 0086 GOT start: 0x00017368 GOT end: 0x000175e8
Followed by never ending silence and no Root.
Someone told me that this guide does not work on my build standard, and gave me links to windows/linux root guides.
These don't work because I have a Mac. I do not have windows and I do not have linux, I only have Mac, and I know no one with a PC that I can borrow for this exercise, so it has to be done from my Mac and not any other platform.
What I want is:
1) Root my TF101
2) get CWM on there
3) get the latest Prime ROM on there.
Can someone please explain to me what I need to do to get prime 1.8 installed on build 8.2.3.13 of a chinese TF101?
Sorry if I sound direct, but I know very little about this stuff and so far I have found nothing that works. Since I know nearly nothing other than how to follow accurate complete correct unambiguous instructions, I would love it if someone can actually provide me with those.

That method only work for 8.2.3.9 or lower.
8.2.3.13 and up use NVFlash method.
Also since you're on 8.2.3.13 you have the option to downgrade to 8.2.3.9.
After which you can root and install an updated root rom

Ok, so can you please explain to me how to use NVFLASH on a Mac? If it is not posisble, can you explain to me how to downgrade to 8.2.3.9?
I'd be very gratefull!
UPDATE: Just saw your response on the other post. I think this will help me a lot! Thanks!

I also had cn firmware, using nvflash is very easy, I use windows and follow the tutorial from YouTube ..

[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] [Dualboot]-[Net-Install] Flash Jhintas Kernel with no Linux Machine available

Hello everybody!
I've just set up a dualboot with ICS/Stock/Rooted as default + Ubuntu as secondary using frankc123's one-click installer with NoDiskNoFun's Net-Install Ubuntu v0.6.
Everything went fine, except it didn't install Jhintas kernel during the Ubuntu install process (net-install) , tried multiple times chosing it being flashed as first, secondary, even building it during install... I've read of others having the same problem on NoDiskNoFun's thread and one user suggested it might be because the Net-Install script can't handle ubuntu being secondary...
So my question is: How do I either flash the Jhinta kernel on top of my Install with no Linux machine available except for the transformer itself
or
how do I change the dualboot order in frank's tool to make ubuntu the default and android the secondary Os (assuming thats really what causes the jhinta kernel not to install during the script)?
I'm really a noob when it comes to stuff like this so help would be greatly appreciated!
Thanks in advance!

I just struggled with the exact same issue today, except I'm using OLiFE instead of frankc123's one-click installer. I finally figured out how to get it working earlier.
There's a file left by net-installer in /Linux_for_Tegra/ named selfbuild.img that has the kernel image that needs to get flashed to your device. I just overwrote the image that contained the 2.6.36 kernel with Jhinta's kernel _after_ finishing all the steps from the net-install scripts. This was a little bit tricky with OLiFE because it builds the image from a few files, so I had to comment out this step to let it flash the provided selfbuild.img as is.
Hope that helps. I can check out what frankc123's one-click installer does if not.
xxaconexx said:
Hello everybody!
I've just set up a dualboot with ICS/Stock/Rooted as default + Ubuntu as secondary using frankc123's one-click installer with NoDiskNoFun's Net-Install Ubuntu v0.6.
Everything went fine, except it didn't install Jhintas kernel during the Ubuntu install process (net-install) , tried multiple times chosing it being flashed as first, secondary, even building it during install... I've read of others having the same problem on NoDiskNoFun's thread and one user suggested it might be because the Net-Install script can't handle ubuntu being secondary...
So my question is: How do I either flash the Jhinta kernel on top of my Install with no Linux machine available except for the transformer itself
or
how do I change the dualboot order in frank's tool to make ubuntu the default and android the secondary Os (assuming thats really what causes the jhinta kernel not to install during the script)?
I'm really a noob when it comes to stuff like this so help would be greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse

GdmImpulse said:
I just struggled with the exact same issue today, except I'm using OLiFE instead of frankc123's one-click installer. I finally figured out how to get it working earlier.
There's a file left by net-installer in /Linux_for_Tegra/ named selfbuild.img that has the kernel image that needs to get flashed to your device. I just overwrote the image that contained the 2.6.36 kernel with Jhinta's kernel _after_ finishing all the steps from the net-install scripts. This was a little bit tricky with OLiFE because it builds the image from a few files, so I had to comment out this step to let it flash the provided selfbuild.img as is.
Hope that helps. I can check out what frankc123's one-click installer does if not.
Click to expand...
Click to collapse
Hey!
Thanks for the reply! But if I am not mistaken OLiFE is Linux only, or isn't it? Like i said I unfortunately have no access to a Linux machine other than the transformer itself, so I'm stuck with Franks tools, plus while I get the theory behind what you are saying, I have no Idea how to do it myself... I'm really a newbie when it comes to Linux, which is why I'd like to try it out on the TF
Any ideas on how to flash the kernel either during install, or afterwards without OLiFE? Maybe via NVFlash? (Just wildly guessing here)
Thanks!

xxaconexx said:
Hey!
Thanks for the reply! But if I am not mistaken OLiFE is Linux only, or isn't it? Like i said I unfortunately have no access to a Linux machine other than the transformer itself, so I'm stuck with Franks tools, plus while I get the theory behind what you are saying, I have no Idea how to do it myself... I'm really a newbie when it comes to Linux, which is why I'd like to try it out on the TF
Any ideas on how to flash the kernel either during install, or afterwards without OLiFE? Maybe via NVFlash? (Just wildly guessing here)
Thanks!
Click to expand...
Click to collapse
It should definitely work with nvflash since that's what OLiFE is using. From what I can see in the scripts, you can run:
nvflash -r --download <PARTITION> selfbuild.img
Where <PARTITION> is 5 for secondary and 6 for primary (AFAICT, booting net-install from primary doesn't work anyways, so likely this should be 5 for you).

could you by any chance walk me through this? from what you said I'd be guessing to do the following:
put the selfbuild.img into the nvflash folder
open a cmd and navigate inside the folder
plug transformer in apx mode + install drivers
type nvflash -r --download 5 selfbuild.img into the cmd
is that all I have to do? if its really that easy, than wow!
where is the /Linux_for_Tegra/ folder that contains the selfbuild.img located tho? couldn't find it on my TF, and once I found it, how do I pull it? mount the ubuntu partition in android and pull it via root explorer?
thanks a lot! :victory:
acone
GdmImpulse said:
It should definitely work with nvflash since that's what OLiFE is using. From what I can see in the scripts, you can run:
nvflash -r --download <PARTITION> selfbuild.img
Where <PARTITION> is 5 for secondary and 6 for primary (AFAICT, booting net-install from primary doesn't work anyways, so likely this should be 5 for you).
Click to expand...
Click to collapse

xxaconexx said:
could you by any chance walk me through this? from what you said I'd be guessing to do the following:
put the selfbuild.img into the nvflash folder
open a cmd and navigate inside the folder
plug transformer in apx mode + install drivers
type nvflash -r --download 5 selfbuild.img into the cmd
is that all I have to do? if its really that easy, than wow!
where is the /Linux_for_Tegra/ folder that contains the selfbuild.img located tho? couldn't find it on my TF, and once I found it, how do I pull it? mount the ubuntu partition in android and pull it via root explorer?
thanks a lot! :victory:
acone
Click to expand...
Click to collapse
That sounds right. That's what I did to get it working. This is assuming that the Windows version of nvflash takes the same parameters of the Linux version, but it sounds like it does.
You can probably pull the file from Android. If you have an sdcard, you can copy it from Linux. I've uploaded the image from mine that you can try if you are having trouble pulling the file. This is from Net-Installer 0.6: 2shared.com/file/9wAIoPat/selfbuild.html

okay, so I've tried this, here's what happened:
-put the selfbuild.img into the nvflash folder
-open a cmd and navigate inside the folder
-plug transformer in apx mode + install drivers
-type nvflash -r --download 5 selfbuild.img into the cmd
-cmd shows something along the lines of nvflash starting [resume mode] than it would get stuck forever with nothing happening afterwards
-tried to see if nvflash was working properly via nvflash --sync and it would give me the 'nvflash started rcm version 0x4 command send failed' error SBK2 users get without using wheelie, then the device lost connection (odd, was that supposed to happen?)
-downloaded wheelie (eventho I have an sbk1 device [B50])
-navigated to the wheelie folder and replaced the bootloader.bin with the one from franks tools (not sure if that was necessary)
-opened up a cmd, navigated to the wheelie folder and typed in wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct (wheelie SBK1DEVICE SET_ODM_DATA_TO 0x300d8011 SET_THE_BOOTLOADER_FILENAME_TO bootloader.bin SET_THE_BCT_FILENAME_TO transformer.bct)
-nvflashed the selfbuild.img again using nvflash -r --download 5 selfbuild.img
IT WORKED!
not entirely sure what i did there as I just randomly pulled bits of information from a ton of threads and google, but it worked :victory:
touchpad is now working, but I still can't get it to connect to my wifi using wpa_gui, it shows my router when scanning (wpa2-personal psk aes [so i'm assuming the encryption has to be set to CCMP?]) but when I enter the password and try to connect it just gives me the "associating" for a second than says "disconnected, last message bssid=00:00:00:00:00:00 reason=0
any clues why?
thanks again for the help! :good::good:
GdmImpulse said:
That sounds right. That's what I did to get it working. This is assuming that the Windows version of nvflash takes the same parameters of the Linux version, but it sounds like it does.
You can probably pull the file from Android. If you have an sdcard, you can copy it from Linux. I've uploaded the image from mine that you can try if you are having trouble pulling the file. This is from Net-Installer 0.6: 2shared.com/file/9wAIoPat/selfbuild.html
Click to expand...
Click to collapse

disregard my last post and this one, I got it working, simply needed a reboot when it was stuck on 'associating...' was able to apt-get the ubuntu software center now, just to run into the next problem: upon running it it says starting then crashes with a crash report, when I try to open up the details it says "icon 'package-install' not present in theme", downloaded synaptics, tried to start it from applications/system tools/administration/synaptic package manager but the system will just show the loading icon for a second then nothing happens... guess I'm off for a great start into the world of linux
just tried to set the encryption of the router to wep and connect, wpa_gui says its connected but I cant ping anything via terminal or sudo apt-get stuff, plus oddly enough while the tf is connected none of my other devices can access the wifi
tried WPS as well both with the push button (gives a waiting or registrar status forever) and a generated pin (router just tells me to start wps on the tf, tf tells me registrar does not yet know pin) - so thats not working either...
disabling encryption entirely and just leaving the network open (this is what worked for me during net-install) won't do anything either, status will just show "associating" forever...
any clues?

xxaconexx said:
disregard my last post and this one, I got it working, simply needed a reboot when it was stuck on 'associating...' was able to apt-get the ubuntu software center now, just to run into the next problem: upon running it it says starting then crashes with a crash report, when I try to open up the details it says "icon 'package-install' not present in theme", downloaded synaptics, tried to start it from applications/system tools/administration/synaptic package manager but the system will just show the loading icon for a second then nothing happens... guess I'm off for a great start into the world of linux
just tried to set the encryption of the router to wep and connect, wpa_gui says its connected but I cant ping anything via terminal or sudo apt-get stuff, plus oddly enough while the tf is connected none of my other devices can access the wifi
tried WPS as well both with the push button (gives a waiting or registrar status forever) and a generated pin (router just tells me to start wps on the tf, tf tells me registrar does not yet know pin) - so thats not working either...
disabling encryption entirely and just leaving the network open (this is what worked for me during net-install) won't do anything either, status will just show "associating" forever...
any clues?
Click to expand...
Click to collapse
Glad to hear you got the kernel working :highfive:
FWIW, I was having problem with WPA2 as well. For now, I've manually modified /etc/wpa_supplicant/wpa_supplicant.conf to get it working. http://forum.xda-developers.com/showthread.php?p=33856819&highlight=wpa2#post33856819 is what I followed to modify the config for my network.

yeah I had tried that first but it wouldn't work, then read a post about how wpa_gui is not always showing the correct status of the wifi, so I connected to my wifi, left it at "associating" and rebooted, after a reboot it showed "connected" :laugh:
got the software center to work as well, installing synaptics did the trick, eventho I can't run synaptics itself, the error I had before with the software center was gone after i installed it.
is usb hotplugging working for you? I know jhintas kernel is not supposed to have it, but NoDiskNoFun stated is was working with his net-install script in the post so I'm curious. rn I have to have the usb device plugged in during boot for it to work.
GdmImpulse said:
Glad to hear you got the kernel working :highfive:
FWIW, I was having problem with WPA2 as well. For now, I've manually modified /etc/wpa_supplicant/wpa_supplicant.conf to get it working. http://forum.xda-developers.com/showthread.php?p=33856819&highlight=wpa2#post33856819 is what I followed to modify the config for my network.
Click to expand...
Click to collapse

[Q] Please help me to recover my totally bricked TF101

I've tried many solutions (read from various forums) but yet to find a way to recover my bricked TF101.
I totally don't know how to use linux so please help me by using Windows's way.
Thank you.
I will try to describe as clear as possible regarding my issues.
The serial number began with B50K so should be SBKv1.
This tablet belong to my brother, he can't turn on the unit last week and he asked help from his friend.
I have no idea what his friend did but now this tablet only able to be detected in APX mode once plug into Windows PC.
The battery still able to charge via USB cable (I have opened up the casing and measured the battery pack voltage (above 8.0V).
ADB can't find this tablet but NvFlash can upload bootloader.bin successfully when run "download.bat"(the rest of the steps failed).
USB cable and PC, drivers all should be OK as I am able to flash my other TF101 unit.
Please read the below error messages when I tried to run Nvflash and wheelie:
Run NvFlash "download.bat" from DoS Promt, TF101 LCD screen shows:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 037c61542axxxxx
(Nvidia recovery driver still shown in Windows Device Manager)
Run reflash_sbkv1 from DoS Promt, TF101 LCD screen shows:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 037c61542axxxxx
!!!!phone update success!!!!
!!!!phone update faileded!!!!
!!!!phone update faileded!!!!
(Nvidia recovery driver still shown in Windows Device Manager)
I've tried on different PC and notebooks, XP, Windows 7 (both 32-bit and 64-bit), all returned same results, no luck.
I've tried Peri Tool 0.4 and EasyFlasher-0.8.3b all can't fix as well.
The TF101 only can detected as APX, tablet screen only turn on during "flashing".
Can't enter recovery mode (Power+Volume Down), can't turn ON (no display nor sound).
This problem possible caused by hardware issues like faulty NAND chip etc?
Please help me to solve this tablet.
Thank you in advance.

The logs show "bad data". Can you re-download everything and start over?

Lethe6 said:
The logs show "bad data". Can you re-download everything and start over?
Click to expand...
Click to collapse
Thanks for your reply..
Tried many times with different nv flash version, same failed results.

Go to this post: http://forum.xda-developers.com/showthread.php?t=1995157
Download the application per the instructions. You are NOT going to install Linux and you will NOT dual boot your tablet.
Once you have the Windows application open you will click on the Flash tab. From the dropdown called Dualboot A/U, select the option that says "Android Only". Make sure you have the system.img file in your images folder which is Roach rooted ROM called "Prime".
The purpose of this is it works directly with your APX mode. I looked at your screenshots and the commands looked odd to me but I could be wrong.

TomTcom said:
Go to this post: http://forum.xda-developers.com/showthread.php?t=1995157
Download the application per the instructions. You are NOT going to install Linux and you will NOT dual boot your tablet.
Once you have the Windows application open you will click on the Flash tab. From the dropdown called Dualboot A/U, select the option that says "Android Only". Make sure you have the system.img file in your images folder which is Roach rooted ROM called "Prime".
The purpose of this is it works directly with your APX mode. I looked at your screenshots and the commands looked odd to me but I could be wrong.
Click to expand...
Click to collapse
Hi,
Thank you for the link, will give it a try.
BTW, why you say "the commands" look odd? I am running the commands in Dos Prompt so that I can see all the logs.
Tried tfubuntu, still got error. Please see the attachment.

ongbs said:
Hi,
Thank you for the link, will give it a try.
BTW, why you say "the commands" look odd? I am running the commands in Dos Prompt so that I can see all the logs.
Click to expand...
Click to collapse
It looks like your nvflash command duplicates what the wheelie command already did. I could be wrong though, there are a couple of ways to input the commands from both wheelie and nvflash.

TomTcom said:
It looks like your nvflash command duplicates what the wheelie command already did. I could be wrong though, there are a couple of ways to input the commands from both wheelie and nvflash.
Click to expand...
Click to collapse
Tfubuntu installer failed with almost same error as NvFlash "download.bat", any clues?
Seems like every time the error shown when trying to create partition.
Anyone know how to use NvFlash to create partition in TF101 manually?

ongbs said:
Tfubuntu installer failed with almost same error as NvFlash "download.bat", any clues?
Seems like every time the error shown when trying to create partition.
Anyone know how to use NvFlash to create partition in TF101 manually?
Click to expand...
Click to collapse
It might be an issue with B50 series...
Here is a manual idea you can try:
From windows dos prompt, go to the directory where the wheelie.exe and nvflash.exe files are located. Don't run your batch file.
Copy this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Once that is done, copy this and hit enter: nvflash -r --getpartitiontable ptable.txt
In that directory, the file will create called "ptable.txt". This is your partition table and identifies what's already set up. I believe BCT should already be set up.
To get out of nvflash mode, type this: nvflash -r --go
Mine looks like this:
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=1536
BytesPerSector=2048
Tell me what you get.

TomTcom said:
It might be an issue with B50 series...
Here is a manual idea you can try:
From windows dos prompt, go to the directory where the wheelie.exe and nvflash.exe files are located. Don't run your batch file.
Copy this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Once that is done, copy this and hit enter: nvflash -r --getpartitiontable ptable.txt
In that directory, the file will create called "ptable.txt". This is your partition table and identifies what's already set up. I believe BCT should already be set up.
To get out of nvflash mode, type this: nvflash -r --go
Mine looks like this:
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=1536
BytesPerSector=2048
Tell me what you get.
Click to expand...
Click to collapse
Thank you for your quick response.
Tried that DOS command, still failed.
Whenever trying to read/write to partition, command will return with errors.
Please refer to attachment.
Possible a hardware failure?

Your partitions probably need formatting. I'll pull the default android only config file from tubuntu application and post some instructions later tonight.
I had to format my partitions before so give me some time.
Sent from my SGH-T999 using Tapatalk 2

Ok we'll do a similar process. I'm not sure on the config file so I don't want to give something that I'm not sure how it worked. I formatted one of my partitions to ensure this command works.
Go back to the DOS prompt where wheelie and nvflash are located.
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
The last command will reboot you. With your current setup you may now need to power off again, go back into APX mode and run your batch file or the Tubuntu application I had you download before.
Let me know what happens.

TomTcom said:
Ok we'll do a similar process. I'm not sure on the config file so I don't want to give something that I'm not sure how it worked. I formatted one of my partitions to ensure this command works.
Go back to the DOS prompt where wheelie and nvflash are located.
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
The last command will reboot you. With your current setup you may now need to power off again, go back into APX mode and run your batch file or the Tubuntu application I had you download before.
Let me know what happens.
Click to expand...
Click to collapse
Thank you my friend.
Will try it when I back home today.

TomTcom said:
Ok we'll do a similar process. I'm not sure on the config file so I don't want to give something that I'm not sure how it worked. I formatted one of my partitions to ensure this command works.
Go back to the DOS prompt where wheelie and nvflash are located.
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
The last command will reboot you. With your current setup you may now need to power off again, go back into APX mode and run your batch file or the Tubuntu application I had you download before.
Let me know what happens.
Click to expand...
Click to collapse
Tried those commands and returned with error, look like my TF101 doesn't has partition on it.

ongbs said:
Tried those commands and returned with error, look like my TF101 doesn't has partition on it.
Click to expand...
Click to collapse
This idea is at your own risk. I can't test it because that would require me to format my tablet and redo all my stuff. If you don't feel comfortable then I understand.
Download this file, this is my dropbox link: https://www.dropbox.com/s/qnk61hrx5w8s2qp/androidpartition.cfg
This file is a .cfg text file. You can open it in an editor and view it. Put this file in the directory where wheelie and nvflash are located.
We are going to attempt to format all partitions and use this config file to model all your partitions after.
Steps:
1. wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
2. nvflash -r --format_all --create --configfile androidpartition.cfg (if this doesn't work see step 2b.)
2b. nvflash -r --format_all --configfile androidpartition.cfg
3. nvflash -r --go
Let me know what you get.

TomTcom said:
This idea is at your own risk. I can't test it because that would require me to format my tablet and redo all my stuff. If you don't feel comfortable then I understand.
Download this file, this is my dropbox link: https://www.dropbox.com/s/qnk61hrx5w8s2qp/androidpartition.cfg
This file is a .cfg text file. You can open it in an editor and view it. Put this file in the directory where wheelie and nvflash are located.
We are going to attempt to format all partitions and use this config file to model all your partitions after.
Steps:
1. wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
2. nvflash -r --format_all --create --configfile androidpartition.cfg (if this doesn't work see step 2b.)
2b. nvflash -r --format_all --configfile androidpartition.cfg
3. nvflash -r --go
Let me know what you get.
Click to expand...
Click to collapse
I definately will try it later my friend.
Thank you for your help.

TomTcom said:
This idea is at your own risk. I can't test it because that would require me to format my tablet and redo all my stuff. If you don't feel comfortable then I understand.
Download this file, this is my dropbox link: https://www.dropbox.com/s/qnk61hrx5w8s2qp/androidpartition.cfg
This file is a .cfg text file. You can open it in an editor and view it. Put this file in the directory where wheelie and nvflash are located.
We are going to attempt to format all partitions and use this config file to model all your partitions after.
Steps:
1. wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
2. nvflash -r --format_all --create --configfile androidpartition.cfg (if this doesn't work see step 2b.)
2b. nvflash -r --format_all --configfile androidpartition.cfg
3. nvflash -r --go
Let me know what you get.
Click to expand...
Click to collapse
Still got error my friend. Do you think possible all these error caused by faulty hardware?

ongbs said:
Still got error my friend. Do you think possible all these error caused by faulty hardware?
Click to expand...
Click to collapse
It's probable my commands aren't correct. Hopefully you can see from the idea of how I started the commands and try to figure it out with some google searches. I don't know for sure if that config file is in the correct format for nvflash either. I used it from the Tubuntu application but the Tubuntu application doesn't have a "format all" and recreate everything option.
I believe your partitions are either not set correctly or the partition table is corrupt or non-existent.
I don't think you have faulty hardware at this point because you can execute wheelie and nvflash without problems so as long as you can do that you still have a fighting chance to recover the tablet.
I searched a lot on these commands but you'll need to do some more. I don't know yet what else I can provide. Good luck!

TomTcom said:
It's probable my commands aren't correct. Hopefully you can see from the idea of how I started the commands and try to figure it out with some google searches. I don't know for sure if that config file is in the correct format for nvflash either. I used it from the Tubuntu application but the Tubuntu application doesn't have a "format all" and recreate everything option.
I believe your partitions are either not set correctly or the partition table is corrupt or non-existent.
I don't think you have faulty hardware at this point because you can execute wheelie and nvflash without problems so as long as you can do that you still have a fighting chance to recover the tablet.
I searched a lot on these commands but you'll need to do some more. I don't know yet what else I can provide. Good luck!
Click to expand...
Click to collapse
Alright. thank you my friend.
I am noob in NvFlash, hope other experienced members can give me some advices.

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