Database Info

[Q] Did i completely brick my tf101?

i tried to unbrick this using
http://forum.xda-developers.com/showthread.php?t=1123429
but now that i followed the instructions all i have is a black screen nothing even pops up. can anyone help me fix this im freaking out right now.

Can you give us more info? Were you rooted? Did you screw up flashing a rom or something? A few weeks ago I had to unroot my TF so I could RMA it and I found that a lot of the posts on here were either outdated or linked to an outside source, which was outdated.
When I got my TF back I decided to re-root it and it was a lot more painful than when I first did it about a month earlier, IDK if I had my images swapped and I was flashing the wrong files or what but it took freaking forever.
I'll upload a stock 3.2 image for you that has to be flashed with nvflash and it will unbrick your tablet. If you want to be rooted use Roach's nvflashable version of Prime instead and that should also fix your TF.

i have a b60 model i was not rooted i tried but failed because i couldnt get superuser to work. i was trying to flash back to stock because i could not get any updates so i figured if i go back to a clean 3.2 i would be ok. then i tried putting it back to stock using one of the post here. then when i tried everything went smooth but then i tried turning my tf101 on and it would not turn on. could you help me fix this? ill be very grateful to you give you a thanks and when i get a job donate to you if we get this working. thank you
edit: i still can get into nvflash but thats about it. idk what to do now

Installing ADB
1. Under the Choose packages to install dialog in the Android SDK choose Android SDK Platform Tools (you don't need all the other crap) and hit install.
2. Right click on My Computer and then select Properties and then Advanced System Settings, then click Environmental Variables and add the location of the folder that contains ADB to the PATH variable in the second pane entitled System Variables (ex: [path that the main folder is in]\android-sdk_r12-windows\android-sdk-windows\platform-tools)
3. Reboot.
4. You should now be able to access ADB via the command prompt (run --> cmd) simply by typing adb
Flashing Back to Stock 3.2
1. Download it from here and extract the archive with winrar, replace the nvflash linux binary with the windows equivalent, open up download.sh and remove the ./ from the beginning of nvflash and also the first line of the file
2. Change the file extension of download.sh to download.bat
3. Right click it and click run as administrator and then let it do it's work and you should be on a fresh install of Honeycomb 3.2 in no time!

Stock TF101 wont OTA

So my sister just bought a Transformer tonight, It has never been rooted or anything.
It will not detect any updates on the "search for update" OTA thing.
I also downloaded the ICS firmware directly from Asus's website, extracted it on a microSD card, and the trasnformer still doesnt show theres any update.
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
No idea whats going on.
Any help is appreciated.

Did you unzipped the file you download from Asus website? You can't leave it whole, there's another zip inside that zip.

Yep I followed all the instructions

Bawb3 said:
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
Click to expand...
Click to collapse
Reading that gives me the feeling that you probably didn't do it right. There is no reason it won't work.
Can you post the EXACT steps you took?

I'm having the same issue
There is no ASUS directory in the zip.
Inside the second zip there is a file called blob and a directory called Meta-Inf with a bunch if files in.

Okay, I go to asus's tf101 site, download sectiion > firmware.
Download the US SKU 4.0.3 firmware update which is ~300mb
Extract that zip which yields a file with another ZIP inside of it. There is no ASUS folder.
Like the above poster said, the second zip file looks like a recovery update script that you would flash in CWM with a meta-inf with the signatures, and a blob file.
EDIT[SOLVED]:
Okay I figured it out. I downloaded the 3.2.1 update from asus, which does have the ASUS folder. This one worked and launched the update wizard.
It seems that the update wizard looks for the directory /ASUS/Update/US_epad-user-x.x.x.xx.zip file on the root of the microSd card.
So I put the ICS update which is US_epad-user-9.2.1.11.zip into the ASUS/Update/ Directory in the microSD card that I initially extracted from the 3.2 update. Sure it enough it launched the update wizard and allowed me to select that file for the update.
ASUS Didnt properly upload the ICS update it seems.
I still dont know why the OTA didnt acknowledge an update.

OK, this is just getting dumb now.
OK, this is just getting really really stupid now. ASUS I AM SERIOUSLY STARTING TO HATE YOU.
OK I have done the following across MULTIPLE reboots and really getting ticked off now. This would NOT be an issue if the recovery mode didn't give me a damned green droid with yellow triangle with ! in the middle of it.
I have:
Way 1
-------
1 - Extracted WW_epad-user-9.2.1.11.zip from the original WW_epaduser9_2_1_11UpdateLauncher.zip from ASUS site.
2 - Copied extracted WW_epad-user-9.2.1.11.zip to EP101_SDUPDATE.zip
3 - Put both zips on root of microSD. Failed. Tried with copy on /sdcard/ as well, both with and without leaving the original 2 on the microSD.
Way 2
-------
Extracted the WW zip both to the / of the tablet and to the root of the microSD, trying both with and without leaving the originals on the microSD.
Way 3
-------
Same exact as Way 1 and Way 2 but with removing the .zip extension from both files, and with swapping removal of the extension between the 2 files on both the tablet and the microSD.
Way 4
-------
Tried all permutations of Way 1, 2, and 3 with both 8.6.5.21 and 8.6.6.21.
NONE of these ways worked.
I grabbed NVFLASH with 8.6.5.13 and that flashed just fine, except that the recovery mode is still giving me the triangular ! droid image.
I absolutely positively can not root or otherwise do anything to this tablet.
The tablet is a ASUS 32GB Transformer HD Tablet (Serial #: B50KAS#####) with a 2GB microSD formatted with FAT32. (I've tried formatting NTFS and FAT32) This is not a Prime! This is the original Transformer!
I even found an article for how to create your own and tried that as well!.
(Wow really guys? You can't post outside links?? Really? What the heck is that retardation supposed to prevent? I mean really!)
All I get for that mess is the USB connection is dropped even before NVFLASH can do anything. I have Windows 7 Ultimate, Mac OS X Lion, and several distributions of Linux (ArchLinux, Ubuntu, CentOS, Debian, and OpenSUSE). I've tried on them all!! This has been a great many hours trying to figure this out, searching like crazy through these forums. (Incidently, the 10 posts requirement in order to post in the 'experienced' area is just nuts.)
I even tried both the renaming WW portion of the zip name to US as described in other areas in this forum and it still failed! I'm a programmer by trade, and I have never run up against something as stubborn as this! The recovery mode is what is breaking all of this. I absolutely can not get a stable, working recovery mode on this tablet! Heck, I'd be happy with the stock 8.6.5.21 on here or ICS (the 9.2.1.11) without ever again attempting to root the pup! Can anyone assist in getting the recovery mode back to normal? Is there a way to use NVFLASH to write the original recovery mode back such that I stop getting that dang Droid With Yellow ! Triangle image?

Do you have CWM Recovery installed? If so, it will not do the OTA updates, but you can just go into CWM Recovery and then choose the 9.2.1.11 firmware and when it is done flashing, you will have an unrooted stock ICS (with stock recovery).

CWM
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!

deryldoucette said:
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!
Click to expand...
Click to collapse
Razorclaw only works on 8.6.5.19.
Not certain on which version you try to run razorclaw.
use Vipermod on 8.6.5.21 or higher.

was 8.6.5.13 which is what i was able to nvflash back to the tablet. Do you know if there is a more recent nvflash packaged 8.6? Looking to see if I can at least put 8.6.5.21 on here. Currently still running the 8.6.5.13

Mine also wont OTA, i have put the downloads in ASUS/Update and nothing... does not detect updates.

Just bought my tf101 yesterday, same problem. Called support and they told me the update was not pushed to my device yet and a manual update would probably fail.how long ago was ics released?
found it, february 24th... It should be pushed to my device by now, right?
Sent from my SPH-D700 using XDA

G'day guys,
I finally managed to get it to work for me!
TLDR Version - I have the US build version - this may or may not be relevant to these instructions:
* Use "App Backup" to backup all your apps and/or data (optional)
* Factory reset
* Choose "English (US)" from the initial setup wizard and default options for the rest (skip wifi setup)
* Plug the transformer in to your PC via USB
* Create the following folder structure exactly (including case!)
<Internal Storage>\ASUS\Update
* Copy US_epad-user-9.2.1.11.zip that you extracted from US_epaduser9_2_1_11UpdateLauncher.zip to "<Internal Storage>\ASUS\Update"
* Reboot Transformer
* Choose the triangle from the notification area
* TF should update successfully!
Long version:
I followed the instructions in this thread but still wasn't having any luck.
I don't have an external SD card so I was copying the zip from the downloaded file to internal storage\Asus\Update. The triangle was appearing in the bottom right but when I went to do the update it would reboot to the android man with an "!" on his chest. I then tried a factory reset and then recopied the update and tried again. Same "!" dude. I tried another reset but did two things different and it then worked! Instead of choosing "English (UK)" on the initial setup wizard (I'm from Aus) I chose "English (US)" (just a wild guess given its US update required for my TF. The other thing that I did differently was located the update at "ASUS\Update". Note the capitalisation of "ASUS" where previously I was using Asus. I had this idea when I noticed the first time I had both "Asus" and "ASUS" folders there simulataneously. So one or both of those things made it work for me!
If these tips worked for you please post your success (or otherwise even).
Best of luck!

[HowTo] Restore Stock Recovery and Install .26 OTA Manually with Unlocked Bootloader

All credit goes to original posters- this information was compiled from a few different threads to make things easier.
Info came from the following threads:
http://forum.xda-developers.com/showthread.php?t=1803090
http://forum.xda-developers.com/showthread.php?t=1492887
** As always, this has risks. You could brick your device. Do this at your sole discretion. This worked just fine for me, but it might not work for everyone.
** What this does is replace TWRP with the stock recovery, enabling OTA updates to be applied again. It does NOT re-lock your bootloader. It also overwrites your /system image and build.prop with the original .22 image, which should enable the .26 update to be successful.
** This did NOT overwrite any of my settings or apps- that may not always be the case. It's best to expect that this will result in a factory reset, even though in my experience it didn't. Better to be prepared and pleasantly surprised.
** This assumes you installed TWRP or another recovery and need to revert to Stock recovery. Although I'd recommend running the full process anyway, as this ensures you have a fully stock /system partition, build.prop, etc. You can try skipping to step 10 if you're still on stock recovery.
1: Run a TWRP and/or Titanium backup, just in case. Grab everything including recovery if using TWRP.
1a: To be on the safe side, make sure you don't have any other update zips at the root of your external SD or internal storage.
2: Download the appropriate 9.4.5.22 file for your device from here:
3: Extract files from within zip
4: Extract files again from the extracted zip
5: Copy extracted "blob" file to root of folder of the removable Micro SD card or some other folder
6: Through ADB shell or Terminal Emulator, run the following: (May take from 5 to 20 minutes)
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
If copying the "blob" file to the SD card in the keyboard dock, use: dd if=/Removable/SD/blob of=/dev/block/mmcblk0p4
If copying it to the internal memory, use: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
7: Reboot only if the following is displayed (exact numbers may be different):
Code:
1068769+1 records in
1068769+1 records out
547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
Update process will automatically launch
8: Once booted up, root device by using debugfs root here
9: Do not make any other changes to build.prop or the /system directory
10: Download the appropriate dlpkgfile. The US version of the update can be downloaded here. I'll add any others as they are posted.
11: Use root explorer to copy "dlpkgfile" into /cache/ directory. Alternatively you could save the "dlpkgfile" in a microSD then open up a adb shell session.
Code:
su
cat /Removable/MicroSD/dlpkgfile > /cache/dlpkgfile
12: Create the file called "command" under /cache/recovery/ directory.
13: Write this statement in the file /cache/recovery/command
Code:
--update_package=/cache/dlpkgfile
14: Finally reboot into recovery kernel by shutting down first, then press and hold "Volume down" + "Power" once it vibrates release "Power" keep holding "Volume down" until there are some text shown on the boot logo screen. Then press "Volume up" within 5 seconds after releasing "Volume down". The update process should start... wait for it to complete. (This will take a little while, as the dalvik-cache will be rebuilt and your camera firmware will be updated. Once it completes, you should have the updated firmware installed on your tablet
15: Once the update is complete and you're at your home screen, you'll need to re-root. Just follow step 8 again.
16: Once rooted again, you can reinstall TWRP according to the original instructions, or just leave stock recovery on for now to avoid having to do this again once the next OTA comes out.

thanks for taking the risk and trying all this out. i just ran through all the steps and it worked perfectly. (i also had TWRP)

Really stupid question incoming, skip this post if you're in a cranky mood...
How can I tell if I'm running TWRP? I used the unlock tool from Asus then the debugfs root method from another thread in this sub. When I boot into recovery I get a red exclamation point over my surgery table android. It just says something along the lines of Android recovery, so I assume that's stock.

Headcase_Fargone said:
Really stupid question incoming, skip this post if you're in a cranky mood...
How can I tell if I'm running TWRP? I used the unlock tool from Asus then the debugfs root method from another thread in this sub. When I boot into recovery I get a red exclamation point over my surgery table android. It just says something along the lines of Android recovery, so I assume that's stock.
Click to expand...
Click to collapse
Yeah, it sounds like you're on standard recovery, and maybe there's an update file on your SD card or in cache that's failing.
If you follow the OP, it should enable you to update if you haven't yet. It'll pretty much do everything back to default .22 except relocking the bootloader.

Oh, as an afterthought, make sure you don't have any other update zips at the root of your external SD or internal storage, just to be safe.

followed all steps and seems to work. However, in the last step after I created the command file with root explorer, I booted into stock recovery and recovery screen is now just blinking with the Android icon. This does not seem correct! Any suggestions?

rsbuffalo said:
followed all steps and seems to work. However, in the last step after I created the command file with root explorer, I booted into stock recovery and recovery screen is now just blinking with the Android icon. This does not seem correct! Any suggestions?
Click to expand...
Click to collapse
How do you mean blinking? Does the android icon have a red triangle?

i think he may have missed the part where he needs to hit volume up after volume down.

Thanks eoh7678! I did have some update zips at root sdcard that seemed to be causing an issue. I deleted the files and uninstalled busybox. Then I redid the command file. Update was successful!!! About tablet now shows IML74K.US_epad-9.4.5.26-20120720.

Nice work. I was not aware you could go back to stock recovery. I may give this a go. I'm really blown away that somebody hasn't released a flashable zip that is custom stock ready yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

newellj79 said:
Nice work. I was not aware you could go back to stock recovery. I may give this a go. I'm really blown away that somebody hasn't released a flashable zip that is custom stock ready yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I actually have one mostly ready to go, according to what I've read, but to be honest, I've only ever made update zips for samsung or HTC phones. I've never tried this whole blob thing. TBH, I'm scared to death to try flashing my own creation.

Thank you for posting the howto (you saved me from having to write my method) I did everything from my TF700 using terminal and remote explorer to get recovery reverted and .26 OTA installed.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?

newellj79 said:
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
Click to expand...
Click to collapse
I haven't tried the manual update with this one, as I received it OTA before this one was posted, but it erased my su. Happily RootKeeper preserved it.

newellj79 said:
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
Click to expand...
Click to collapse
For me, at least, restoring .22 from the blob removed su. Probably rootkeeper would have solved, but honestly, I figured the safest bet was just to reroot between to make it easier and less prone to problems.

eoh7678 said:
For me, at least, restoring .22 from the blob removed su. Probably rootkeeper would have solved, but honestly, I figured the safest bet was just to reroot between to make it easier and less prone to problems.
Click to expand...
Click to collapse
Kewl. Just curious. Almost done.
Edit... worked great. Thanks!

Having an issue.... Once i move dlpkgfile to cache, make the command file, and reboot to recovery i just get the android with the red triangle. Also once it reboots and i check the cache folder the command file is gone. So at the moment im stuck on 22
Sent from my unlocked and rooted TF700T using the XDA Premium App

cctaylor410 said:
Having an issue.... Once i move dlpkgfile to cache, make the command file, and reboot to recovery i just get the android with the red triangle. Also once it reboots and i check the cache folder the command file is gone. So at the moment im stuck on 22
Sent from my unlocked and rooted TF700T using the XDA Premium App
Click to expand...
Click to collapse
I was having the same problem. My issue was when I downloaded the dlpkgfile a .bin extension was added to the file name. Make sure there is no extension on the filename.

DroidEris1981 said:
I was having the same problem. My issue was when I downloaded the dlpkgfile a .bin extension was added to the file name. Make sure there is no extension on the filename.
Click to expand...
Click to collapse
Im mildly retarded cause the file was 0kb lol. Re-downloading and trying again
EDIT: every copy method i try dlpkgfile ends up as 0kb, not sure what is going on. Using root explorer and terminal fail.
Sent from my unlocked and rooted TF700T using the XDA Premium App

cctaylor410 said:
Im mildly retarded cause the file was 0kb lol. Re-downloading and trying again
EDIT: every copy method i try dlpkgfile ends up as 0kb, not sure what is going on. Using root explorer and terminal fail.
Sent from my unlocked and rooted TF700T using the XDA Premium App
Click to expand...
Click to collapse
I used ES File Explorer (make sure to check the options in settings to tell it you have a rooted phone) to do everything (including creating the file) and it worked great. ES File Explorer is *awesome* - check it out.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

[Q] How make the TF101 Stock and unroot?

Hi
I've been having heavy troubles with the "Android Revolution HD" ROM, my battery lasts forever while in use, but drowns easily and extremely fast when in sleep / shutdown mode.
So I give up, I am going to sell this tablet and I don't want this ROM any more, I don't want my devince Root. I want to get it back to the way it was when I opened the box.
The only think I'd like to get is the Eee Pad Transformer TF101 Firmware: V9.2.1.27 original from Asus to keep using the Android 4.0.X, nothing else.
Since all my attemps of install / reinstall / stock / root / unroot became a mass failure and later on I end coming here and QQ for help I am here to ask what need to be done before doing anything on the tablet.
So here is the summarized question:
How make the TF101 Stock and unroot?
Thank you
And sorry for my silliness

Here is a solution for you, "Instructions for unbricking/flashing ASUS stock firmware" part.
http://forum.xda-developers.com/showthread.php?t=1688012

pstryju said:
Here is a solution for you, "Instructions for unbricking/flashing ASUS stock firmware" part.
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
It just doesn't work (as I was expecting) after doing exactly everything it says, it start installing something and then that is it, nothing happens on my tablet.

Filipebergami said:
Hi
I've been having heavy troubles with the "Android Revolution HD" ROM, my battery lasts forever while in use, but drowns easily and extremely fast when in sleep / shutdown mode.
So I give up, I am going to sell this tablet and I don't want this ROM any more, I don't want my devince Root. I want to get it back to the way it was when I opened the box.
The only think I'd like to get is the Eee Pad Transformer TF101 Firmware: V9.2.1.27 original from Asus to keep using the Android 4.0.X, nothing else.
Since all my attemps of install / reinstall / stock / root / unroot became a mass failure and later on I end coming here and QQ for help I am here to ask what need to be done before doing anything on the tablet.
So here is the summarized question:
How make the TF101 Stock and unroot?
Thank you
And sorry for my silliness
Click to expand...
Click to collapse
Download any firmware on the asus site. Extract the downloaded firmware (eg. WW_epaduser9_2_1_27UpdateLauncher.zip) take the file extracted (eg. WW_epad-user-9.2.1.27.zip) and place on sdcard. Follow the same procedure for installing a custom rom.

gilpederiva said:
Download any firmware on the asus site. Extract the downloaded firmware (eg. WW_epaduser9_2_1_27UpdateLauncher.zip) take the file extracted (eg. WW_epad-user-9.2.1.27.zip) and place on sdcard. Follow the same procedure for installing a custom rom.
Click to expand...
Click to collapse
How do I place things into the SD?
I can only place them into the internal storage, which "Full Wipe" will wipe it out?

Filipebergami said:
How do I place things into the SD?
I can only place them into the internal storage, which "Full Wipe" will wipe it out?
Click to expand...
Click to collapse
Sorry, put the file on the external sdcard. I also used a full wipe script. It takes a little more than installing a custom rom but it works.
I would like to take a question with you. I have already installed several custom ICS rom or JellyBean on my TF101, but the HD videos on youtube are with small crashes. But with Android 3.2.1 works well. This has happened to you?

gilpederiva said:
Sorry, put the file on the external sdcard. I also used a full wipe script. It takes a little more than installing a custom rom but it works.
I would like to take a question with you. I have already installed several custom ICS rom or JellyBean on my TF101, but the HD videos on youtube are with small crashes. But with Android 3.2.1 works well. This has happened to you?
Click to expand...
Click to collapse
I have no MicroSD card into my tablet, only internal storage

Filipebergami said:
It just doesn't work (as I was expecting) after doing exactly everything it says, it start installing something and then that is it, nothing happens on my tablet.
Click to expand...
Click to collapse
Please provide further details. What does easyflasher's window/log say? I've used this hundreds of times of not more to go back to stock or fix issues. Did you install the proper APX drivers?

Lethe6 said:
Please provide further details. What does easyflasher's window/log say? I've used this hundreds of times of not more to go back to stock or fix issues. Did you install the proper APX drivers?
Click to expand...
Click to collapse
It says everything was installed successfully and yes APX drivers are fine I've had others troubles with ROMs so I have it installed properly.
http://img10.imageshack.us/img10/9625/es5b.jpg

Filipebergami said:
It says everything was installed successfully and yes APX drivers are fine I've had others troubles with ROMs so I have it installed properly.
http://img10.imageshack.us/img10/9625/es5b.jpg
Click to expand...
Click to collapse
Did you see any text on the TF display? It should show some text when it is flashing.
Also, when in recovery you can use ADB to push the ww-epad firmware to your tablet's sdcard. Update the driver for the naked driver ADB and then:
adb push ROM.zip /sdcard/
If you need ADB, you can get the adb and dll files required to run here: https://dl.dropboxusercontent.com/u/34321735/adb.zip

frederuco said:
Did you see any text on the TF display? It should show some text when it is flashing.
Also, when in recovery you can use ADB to push the ww-epad firmware to your tablet's sdcard. Update the driver for the naked driver ADB and then:
adb push ROM.zip /sdcard/
If you need ADB, you can get the adb and dll files required to run here: https://dl.dropboxusercontent.com/u/34321735/adb.zip
Click to expand...
Click to collapse
Hi frederuco, you saved me once.
http://forum.xda-developers.com/showthread.php?t=2144143
Do I need to do this all over again?

Filipebergami said:
Hi frederuco, you saved me once.
http://forum.xda-developers.com/showthread.php?t=2144143
Do I need to do this all over again?
Click to expand...
Click to collapse
Yup!
Push the rom to flash to the /sdcard/ and you should be good to flash. Obviously dontjisnafter the full wipe.

frederuco said:
Yup!
Push the rom to flash to the /sdcard/ and you should be good to flash. Obviously dontjisnafter the full wipe.
Click to expand...
Click to collapse
Am I doing this right?
http://img24.imageshack.us/img24/6711/rlof.jpg
http://imageshack.us/f/545/wxne.jpg/

Almost....
You need a space between the .zip and the /sdcard/

frederuco said:
Almost....
You need a space between the .zip and the /sdcard/
Click to expand...
Click to collapse
I am getting error like last time,
http://img850.imageshack.us/img850/2954/lemh.jpg

Try using this version of adb: https://dl.dropboxusercontent.com/u/34321735/adb.zip
It is just the adb.exe and the two dll files required to run it.
I use those in a folder called c:\adb and then put the asus.zip in there and try it.
Also, try executing adb devices to make sure it can connect to your tablet. It should find 1 device.

frederuco said:
Try using this version of adb: https://dl.dropboxusercontent.com/u/34321735/adb.zip
It is just the adb.exe and the two dll files required to run it.
I use those in a folder called c:\adb and then put the asus.zip in there and try it.
Also, try executing adb devices to make sure it can connect to your tablet. It should find 1 device.
Click to expand...
Click to collapse
I still getting error, here is my screen if this helps:
http://imageshack.us/f/534/4vsd.jpg/
and the error log:
http://imageshack.us/f/32/ogc1.jpg/

on your PC try running these, then try to push the file again:
adb kill-server
adb start-server

frederuco said:
on your PC try running these, then try to push the file again:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Here:
http://img850.imageshack.us/img850/2543/h9vj.jpg

Hmm, not sure what to say....
Do you have another PC you can try it on? At least try a PC reboot if nothing else.
Or perhaps a Linux live cd. ADB is native to Linux, just run from a terminal window.

[Q&A] EasyFlasher - Install CWM/Root/unbrick in one click! [ALL TF101][NVFLASH]

Q&A for EasyFlasher - Install CWM/Root/unbrick in one click! [ALL TF101][NVFLASH]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

I though my model was tf101. It was tf201. I brick it! None of the tutorials of this website seems to work. There's a way to unbrik the tf201 bricked with this software?

DavidTG said:
I though my model was tf101. It was tf201. I brick it! None of the tutorials of this website seems to work. There's a way to unbrik the tf201 bricked with this software?
Click to expand...
Click to collapse
http://forum.xda-developers.com/transformer-prime
http://forum.xda-developers.com/showthread.php?t=1514088

*Detection* said:
http://forum.xda-developers.com/transformer-prime
http://forum.xda-developers.com/showthread.php?t=1514088
Click to expand...
Click to collapse
I think my situation is option 2 or 3. There's no guide for that. Also, I can get into recovery mode. If I could do that, I could do option 1!

Where to get TF101 EasyFlasher, or recommended alternative?
Decided to finally root/flash my old TF101. Was following Frederuco's Guide, downloading all the bits and pieces, but the download link in the EasyFlasher thread doesn't work. Search didn't yield anything except posts in that same thread, and none of the most recent posts mention an alternate download location or a new flashing tool to use.
Any help is appreciated.

Help with Easyflasher
I want to flash the Asus stock ROM using Easyflasher.
I downloaded the latest version of Easyflasher on to my Windows 8.1 laptop. I run the app as an Administrator and follow the instructions. Once Easyflasher has completed its operation, I reboot the tablet, but nothing has changed! The tablet is still in the same way. Does anyone have any ideas?

st1974 said:
I want to flash the Asus stock ROM using Easyflasher.
I downloaded the latest version of Easyflasher on to my Windows 8.1 laptop. I run the app as an Administrator and follow the instructions. Once Easyflasher has completed its operation, I reboot the tablet, but nothing has changed! The tablet is still in the same way. Does anyone have any ideas?
Click to expand...
Click to collapse
Did you add the Stock ROM to Easyflasher folder and did you put the TF into APX mode?

*Detection* said:
Did you add the Stock ROM to Easyflasher folder and did you put the TF into APX mode?
Click to expand...
Click to collapse
Yes, run as Administrator, Naked drivers installed, Stock ROM added to the Easyflasher folder and put into APX mode. I have no idea what's going on. Your thoughts?

Which OS are you running? If it's Win 8.x or 64bit, disable driver signing at boot
Did you check you had selected the correct SBK version in Easyflasher?
SBK1 is B6O and previous (Some B7O) serial numbers, anything higher is SBK2

bricked TF101 easy flasher problem
I've done everything in the video on youtube video (youtube . com/watch?v=25i0H43cTqgzz)
but keep getting now where, gets this message every time...any ideas?
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
ERROR! Blob wasn't extracted! Check your .zip file in AsusUpdate folder!
Make sure it is the original .zip that you downloaded from ASUS
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 0kb
>APP size 0kb
>EBT size 0kb
>LNX size 0kb
Done!

upwardseven said:
I've done everything in the video on youtube video (youtube . com/watch?v=25i0H43cTqgzz)
but keep getting now where, gets this message every time...any ideas?
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
ERROR! Blob wasn't extracted! Check your .zip file in AsusUpdate folder!
Make sure it is the original .zip that you downloaded from ASUS
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 0kb
>APP size 0kb
>EBT size 0kb
>LNX size 0kb
Done!
Click to expand...
Click to collapse
The ROM you downloaded from ASUS, the stock one, it comes double zipped, did you extract the first one before putting it into the Easyflasher folder?
I can't remember which way around it's meant to be, but if you didn't extract it first, try extracting it once and putting the extracted zip in the Easyflasher folder
If you did extract it first, try just putting the original direct downloaded zip from ASUS into the folder instead
Been so long since I had stock installed I can't remember, but it looks like that's the problem according to your error messages
Any reason you are returning to the buggy rebooting SOB RR stock ROM when there are 100x more stable custom ROMs like KatKiss 4.4.4 #36 ?

*Detection* said:
The ROM you downloaded from ASUS, the stock one, it comes double zipped, did you extract the first one before putting it into the Easyflasher folder?
I can't remember which way around it's meant to be, but if you didn't extract it first, try extracting it once and putting the extracted zip in the Easyflasher folder
If you did extract it first, try just putting the original direct downloaded zip from ASUS into the folder instead
Been so long since I had stock installed I can't remember, but it looks like that's the problem according to your error messages
Any reason you are returning to the buggy rebooting SOB RR stock ROM when there are 100x more stable custom ROMs like KatKiss 4.4.4 #36 ?
Click to expand...
Click to collapse
Yes I tried both unzipping once and also the direct download also tried the ww tw and us downloads and still nothing. The reason I'm doing this is because somehow during katkiss 4.4.4 I bricked it so I'm at a loss

I'd try an NVFLASH ROM then, that completely deletes and recreates all partitions on the TF, formats everything, and installs a ROM afterwards
Here's the last ICS WW version
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Basically the same routine as Easyflasher, stick the TF into APX mode, make sure the naked drivers are installed and device manager sees the TF when it's in APX mode
Then run download.bat as Admin (Right click > Run as Administrator)
It takes a while to send everything over USB, so be patient
If this doesn't work - there must be another problem somewhere

*Detection* said:
I'd try an NVFLASH ROM then, that completely deletes and recreates all partitions on the TF, formats everything, and installs a ROM afterwards
Here's the last ICS WW version
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Basically the same routine as Easyflasher, stick the TF into APX mode, make sure the naked drivers are installed and device manager sees the TF when it's in APX mode
Then run download.bat as Admin (Right click > Run as Administrator)
It takes a while to send everything over USB, so be patient
If this doesn't work - there must be another problem somewhere
Click to expand...
Click to collapse
ok so I got it back up and running now are there any quick and easy way to root and intsall katkiss 4.4.4 ?

upwardseven said:
ok so I got it back up and running now are there any quick and easy way to root and intsall katkiss 4.4.4 ?
Click to expand...
Click to collapse
Theres a few apps that can root, but you're gonna need TWRP installed again too before flashing KK 4.4.4
Personally I'd try Easyflasher again now you have the TF up and running, if that still fails, try the following:
Try one of these to root
http://forum.xda-developers.com/showthread.php?t=2658335
https://towelroot.com/
AVs might detect this as malware, it's not
http://www.kingoapp.com/android-root.htm
Then download TWRP blob 2.3.2.3
http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Stick it on /sdcard and rename to twrp.blob
Install and Open 'Terminal' on the TF, and type these commands, reboot fully after to complete the install before entering recovery
https://play.google.com/store/apps/details?id=jackpal.androidterm
Code:
# su
<Grant SuperUser permission if it pops up>
# dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
# reboot
All being well you should now be able to enter TWRP and flash KK 4.4.4
Probably a good idea to make a full Nandroid backup in TWRP of this stock ROM before flashing anything else, so if it all goes t1ts up again, you can just restore

*Detection* said:
Theres a few apps that can root, but you're gonna need TWRP installed again too before flashing KK 4.4.4
Personally I'd try Easyflasher again now you have the TF up and running, if that still fails, try the following:
Try one of these to root
http://forum.xda-developers.com/showthread.php?t=2658335
https://towelroot.com/
AVs might detect this as malware, it's not
http://www.kingoapp.com/android-root.htm
Then download TWRP blob 2.3.2.3
http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Stick it on /sdcard and rename to twrp.blob
Install and Open 'Terminal' on the TF, and type these commands, reboot fully after to complete the install before entering recovery
https://play.google.com/store/apps/details?id=jackpal.androidterm
Code:
# su
<Grant SuperUser permission if it pops up>
# dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
# reboot
All being well you should now be able to enter TWRP and flash KK 4.4.4
Probably a good idea to make a full Nandroid backup in TWRP of this stock ROM before flashing anything else, so if it all goes t1ts up again, you can just restore
Click to expand...
Click to collapse
alright I don't know what I'm doing wrong but none of those work. Easyflasher is not doing a thing, towelroot force closes, baidu root the download for en 2.3.7 isn't working and 2.3.6 is in chinese, I followed his direction and got a check once it was done but root checker showed no root. Kingo root fails each time I try

upwardseven said:
alright I don't know what I'm doing wrong but none of those work. Easyflasher is not doing a thing, towelroot force closes, baidu root the download for en 2.3.7 isn't working and 2.3.6 is in chinese, I followed his direction and got a check once it was done but root checker showed no root. Kingo root fails each time I try
Click to expand...
Click to collapse
Give Peri a try
http://forum.xda-developers.com/showthread.php?t=1681155

*Detection* said:
Give Peri a try
http://forum.xda-developers.com/showthread.php?t=1681155
Click to expand...
Click to collapse
gave that one a try and got to flashing and it says /dev/block/mmcblk0p4: cannot open for write: Permission denied so when i continue and it tries to go into recovery I get the android with the caution sign in him.

Are people still supporting this?
Please disregard! don't know how to delete this!

Forgot attachments!
Sorry i forgot the attachments in the previous post, and i cant figure out how to add them there, or delete the post, so i just replied and had everything added here.
AGoonyGooGoo said:
Hello,
I have a received a bricked Transformer Tf101 that is sk1 with model number b40.
I'm trying to use easyflasher 0.8.3.b-STABLE,
I have placed this firmware in the asusupdate folder of easyflasher: WW_epad-user-9.2.1.27 (i did not unzip it)
The naked drives are installed correctly and its in APX mode (See attachment 1)
I then select SBK1 because my S/N begins with b40.
I then click "Flash Asus Stock/Unzip."
Then the prompt comes up and i tried both options "a" or "u" with the same result (see attachment 3)
Then it crashes (see attachment 4)
After selecting close program, it gets to this point and freezes (see attachment 2)
And my asus also freezes (See attachment 5)
From here I have no option but to shut everything down.
I have been working on this for a week now. Can anyone please, PLEASE help me? This will save me a lot of trouble with school by being a vessel for my ebooks so I dont have to spend 500 a quarter on new books. All help is a deeply appreciated.
Click to expand...
Click to collapse