[Q] complete reformat and start over - Eee Pad Transformer Q&A, Help & Troubleshooting

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.

Related

[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] 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] Bricked my TF101G B90

Hi all,
I've put my transformer into an infinite reboot loop. It starts booting into TWRP, I see the splash and after about 2 seconds it drops to a console with the following message
Code:
Updating partition details...
E:Unable to mount '/staging'
Formatting Cache using make_ext4fs
There are two more lines that come up after that but I can't see because the reboot happens too fast. If hold power up during the reboot, I can get into what ppears to be APX mode, i.e. the tablet stops rebooting, and the screen is completely black. Wheelie detects the device in APX mode but nvflash doesn't work afterwards.
The transformer has a serial number starting with B90, so it's at least SBK2.
Here's how I got into this lousy situation ...
I rooted using the adb commands of the wolf exploit as found in the PERI tool. After that I was trying to install native ubuntu using the net-install rootfs following the instructions in those two links. Everything seemed to work, I got wifi, It downloaded, it installed. But on reboot all I got was an initramfs busybox prompt. I'd chosen the jhinta kernel, so I read though the entire net-install thread again, and found the following three posts:
http://forum.xda-developers.com/showpost.php?p=31458873&postcount=148
http://forum.xda-developers.com/showpost.php?p=31466313&postcount=152
http://forum.xda-developers.com/showpost.php?p=31544961&postcount=162
The short version of which was that the script trying to flash the jhinta kernel didn't work, and I needed to do it manually. So I took the blob from the zip attached to the first post, unpacked it and flashed the unpacked blob to /dev/block/mmcblk0p4, /dev/block/mmcblk0p10 and /dev/block/mmcblk0p9 in turn, testing reboots in between. After flashing to mmcblk0p10 didn't make a difference, I tried flashing on mmcblk0p9 but dd complained about running out of space. The image was 8.8Mb and the partition seemed to be only 8Mb in size. I figured this would be a problem, because that partition is meant to be the recovery kernel I vaguely recalled. So just to be safe, BEFORE rebooting I flashed the recovery image from it's zip file again. I rebooted, and now I'm in the infinite loop.
I don't have access to recovery. I am hoping that I can use nvflash and wheelie maybe to return to stock and go over it again from scratch, but wheelie/nvflash reports the following:
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x37c708340003257
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Nvflash started
[resume mode]
failed executing command 11 NvError 0x8
command failure: create failed
Nvflash started
[resume mode]
connection failed NvError 0x8
I have a nasty feeling that wheelie doesn't work for my TF101G, but I'm not sure. What else can I try, or should I send it back to ASUS and pay for them them return it to stock?
Thanks in advance
NVFlash and Wheelie do not work with the TF101G as it has a different SBK from the two TF101 SBK's.
The SBK is not known because not enough TF101G users tried to crack it.
You can try flashing a different recovery using ADB when in your current TWRP, but beyond that you may be in trouble.
Might want to try either 2.3.2.3 or 2.5.0.0 TWRP.
Hmm, the machine doesn't stay in recovery long enough to do anything via ADB.
Code:
adb wait-for-device
doesn't unblock through three reboot cycles.
So I have two options:
1. try to crack the SBK
2. ship it off to ASUS
Any ideas on how to start on 1? Loop through all the options of wheelie -o? I'm hoping there's a better way to go about it?
Sadly, that is probably true, but you are forgetting option 3: Get a new tablet.

[Q] 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?

Categories

Resources