Database Info

[Q] Bricked TF101, tried brk tool, easyflasher, peri

Good day, I am new here as a member. I think I bricked my TF101. The other day I installed 2 apps from play store if i remember it it was yousendit. I am running on stock ICS. then it just automatically turned off. i tried to turn it on again but when it goes into the asus screen with circling dots it just turns off again. tried cold booting it, still the same. then i used wipe data. but an hour has past still my tablet is still showng the android with a rotating orb in its belly. so last night i downloaded every tool i could research. first i tried PERI but it says it does not recognize my device, then i use brks tool v8, i tried installing stock rom as instructed, no success. then i tried easy flasher today and now i cant even see the first boot screen.
I hope you can help me, i use this tablet at work and presentation to my clients. I am new with this OS and seems that i wrecked my tab by solving it myslef, I hope this was not the case. BTW i have a B60 tf101. i bought it second hand with my savings so i have no warranty.
can you please give me a step by step solution, i am very desperate here, thank you.

blitz_krieg916 said:
Good day, I am new here as a member. I think I bricked my TF101. The other day I installed 2 apps from play store if i remember it it was yousendit. I am running on stock ICS. then it just automatically turned off. i tried to turn it on again but when it goes into the asus screen with circling dots it just turns off again. tried cold booting it, still the same. then i used wipe data. but an hour has past still my tablet is still showng the android with a rotating orb in its belly. so last night i downloaded every tool i could research. first i tried PERI but it says it does not recognize my device, then i use brks tool v8, i tried installing stock rom as instructed, no success. then i tried easy flasher today and now i cant even see the first boot screen.
I hope you can help me, i use this tablet at work and presentation to my clients. I am new with this OS and seems that i wrecked my tab by solving it myslef, I hope this was not the case. BTW i have a B60 tf101. i bought it second hand with my savings so i have no warranty.
can you please give me a step by step solution, i am very desperate here, thank you.
Click to expand...
Click to collapse
Easy flaher is the way out,
1) Download universal naked driver and unzip into a folder
2) Download latest Asus transformer firmware and put it in firmware folder.
3) Uninstall all Asus drivers from your laptop.
4) Disconnect your laptop from WiFi/internet and make it offline
4) Now plug your tablet and let windows install required driver.
5) If windows cannot install driver( mostly it won't as laptop is not connected to the net) then use "manually install driver" option and select the folder where you downloaded and unzipped "universal naked driver" and that should install the naked driver.
6) If that doesn't then goto device manager, there you should see unknown device, select it and update the driver manually.
7) Once the driver is installed, then unplug the tablet
8) now connect the tablet back and press volume up and power button together till laptop starts installing APX driver.
9) If it doesn't then try repeating step 5 or step 6 and that will install APX driver.
10) Launch EASY FLASHER and unroot and install stock ROM...
Good luck
Sent from my Transformer using xda app-developers app

udupa82 said:
Easy flaher is the way out,
1) Download universal naked driver and unzip into a folder
2) Download latest Asus transformer firmware and put it in firmware folder.
3) Uninstall all Asus drivers from your laptop.
4) Disconnect your laptop from WiFi/internet and make it offline
4) Now plug your tablet and let windows install required driver.
5) If windows cannot install driver( mostly it won't as laptop is not connected to the net) then use "manually install driver" option and select the folder where you downloaded and unzipped "universal naked driver" and that should install the naked driver.
6) If that doesn't then goto device manager, there you should see unknown device, select it and update the driver manually.
7) Once the driver is installed, then unplug the tablet
8) now connect the tablet back and press volume up and power button together till laptop starts installing APX driver.
9) If it doesn't then try repeating step 5 or step 6 and that will install APX driver.
10) Launch EASY FLASHER and unroot and install stock ROM...
Good luck
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
thanks i will try this immidiately. my laptop is ancient. hopefully i will do it right this time.ill let you know the development

Sir i still cant get it to work i followed your instruction.
BTW here are my details. I guess I downloaded the correct update.
TF101
B60KAS1245548
16gb
I am using an old HP laptop with XP as OS. And I adownloaded this from the asus website and placed it in the folder inside the easy flasher folder WW_epaduser9_2_1_27UpdateLauncher.zip.
Thanks in advance.

blitz_krieg916 said:
Sir i still cant get it to work i followed your instruction.
BTW here are my details. I guess I downloaded the correct update.
TF101
B60KAS1245548
16gb
I am using an old HP laptop with XP as OS. And I adownloaded this from the asus website and placed it in the folder inside the easy flasher folder WW_epaduser9_2_1_27UpdateLauncher.zip.
Thanks in advance.
Click to expand...
Click to collapse
I tihnk a PART of your issues is that you got the wrong file. Instead of the WW version you should be using the US_epaduser file. This is of course thinking that you are in the USA.

I downloaded the WW version thinking that the pad was bought here in the Philippines (second hand). Or maybe I am wrong. Thanks for the idea I'll download the other update and give it a try.

You have a B60 tablet, just use NvFlash via APX mode manually. Much less room for error than anything else IMO, first download image from here http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
Pick WW for ww tablet, or US for us tablet. (I believe yours will be a US tablet, purchased in the Philippines)
Then download wheelie (NvFlash tool) from androidroot.mobi. Copy and paste the files into the other folder you downloaded earlier, overwrite everything with the newer wheelie files.
Put TF into APX mode (Power off, hold volume up while plugged into computer, power back on, screen will remain black and computer should detect device in APX mode.)
Run Reflash_sbkv1.bat (make sure it is sbkv1 not sbkv2 as you have a B60)
If runs successfully you should be unbricked.
You can then reroot with PERI or other if desired.

blitz_krieg916 said:
thanks i will try this immidiately. my laptop is ancient. hopefully i will do it right this time.ill let you know the development
Click to expand...
Click to collapse
It doesn't matter what version of Asus you download ( I'm in US and I downloaded WW version), but can you explain what problems you facing while you try to follow the steps I mentioned... also screen shot of laptop would help I have bricked my tablet at least 10 times and easy flasher (wheelie) always brought it back....
Sent from my Transformer using xda app-developers app

udupa82 said:
It doesn't matter what version of Asus you download ( I'm in US and I downloaded WW version), but can you explain what problems you facing while you try to follow the steps I mentioned... also screen shot of laptop would help I have bricked my tablet at least 10 times and easy flasher (wheelie) always brought it back....
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
Pics and more info would help ^^
Easy flasher *should* work, from what I've heard of it.

I was wondering what's supposed to happen after I launch sbkv1, my tablet just seems to disconnect and the screen stays black.

im trying on whellie tonight
so here are my screenshots. i downloaded from the link you gave me, and downladed wheelie then extracted wheelie on the same folder as the rom. clicked on reflash sbkv1 and on to the next screenshot, how many minutes sholud i wait for it, it says done, but when i switch on my TF nothing happens.

I followed again the whelie using the US and this happened. will it automatically boot my TF or should i manually boot it?

I also used easyflasher and i got stuck with this? what am I doing wrong?

guys i found the box of my TF and shot a pic of the serial number just to be sure.
i researched a bit on other forums and i think im in an permanent apx loop which some say is unsolvable. is this true? i hope not.

blitz_krieg916 said:
I also used easyflasher and i got stuck with this? what am I doing wrong?
Click to expand...
Click to collapse
As far as I can understand, your laptop is recognizing your tablet in APX mode otherwise easy flasher won't work. So plug it back in apex mode and click on "flash Asus stock zip" it will push stock unrooted Asus rom, WAIT for it to finish, it might take some time but WAIT!!! Once its totally finished then you can reboot into a stock ROM.... WAIT for EASY FLASHER to finish.
if you like to root again then use the same to flash recovery and superuser
Sent from my Transformer using xda app-developers app

Thank you for your reply sir. I waited but it seems the while flashing as shown on the screen the TF gets disconnected. I counter check it on the device manager and the "nvidia boot reccovery" was not showing.

It never happened to me, it takes time but it always pushed stock zip through, if that's not happening then I'm out of ideas. I'm sorry to say I'm out of ideas. But sometime back I saw some where, some one suggested a way to unbrick using ADB, I'm not not sure how to ho about it, search the forum, you might find it.. good luck
Following is the last option if nothing else helps and no one can provide you an answer then try following
Instead of flashing Asus stock ROM, Use easy flash to push twrp recovery, i know its not conventional but if you get recovery then you can flash a custom rom... GOOD LUCK
Sent from my Transformer using xda app-developers app

udupa82 said:
It never happened to me, it takes time but it always pushed stock zip through, if that's not happening then I'm out of ideas. I'm sorry to say I'm out of ideas. But sometime back I saw some where, some one suggested a way to unbrick using ADB, I'm not not sure how to ho about it, search the forum, you might find it.. good luck
Following is the last option if nothing else helps and no one can provide you an answer then try following
Instead of flashing Asus stock ROM, Use easy flash to push twrp recovery, i know its not conventional but if you get recovery then you can flash a custom rom... GOOD LUCK
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
Thank you very much sir for your time and to all that replied to this problem. It really disconnects after formatting the 10th partition. I researched on how to use the ADB and that requires a lot more knowledge on programming. I will still try the last option, im crossing my fingers it will work or else ill call the asus service center her in the Philippines. Hopefully they can fx it and it wont be an expensive fix. Thanks again!

[Q] Mount USB storage under ClockWorkmod Recovery 6.0.1.0

Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max

Use this guide to recover your device.

Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.

How did you erase everything? Was it through fastboot or CWM?

I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.

maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...

maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2

*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2

The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?

Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2

Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307

I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Issues With Rooting

I used to have a rooted EVO 4G through work, but recently they switched me over to an iSheep, and as you can imagine I absolutely hate it. And since it’s for work they’ve installed AirWatch so I can’t jailbreak it. But I also have a TF101 that's currently not rooted.
I got my TF101 about a year ago and rooted it like every good android user should. But after about 6 months, I found a small hair line crack in the touch screen. I unrooted it and sent it in to ASUS for them to repair. I always keep my tablet closed in the docking station when it wasn’t in use. I then found this thread, http://forum.xda-developers.com/showthread.php?t=1498237 that stated this is why the screen cracked. So ASUS and I went back and forth for about a month before they finally covered it under warranty and repaired my tablet.
When I got my tablet back I found they upgraded it to 9.2.1.27. I connected it to a computer so I could reroot it, but my tablet is no longer detected by a computer. I tried two computers and two data cables. I’ve also tried all the methods for installing the drivers. I didn’t want to send it back to ASUS due to the issues I previously had with them. I’ve been following Thing O Doom’s thread, http://forum.xda-developers.com/showthread.php?t=1681155 because he stated he's working on a rooting apk, but he no longer has his TF101 so progress has been slow.
But in my searching I found this thread,http://www.transformerforums.com/fo...rmed-fix-gain-root-after-8-6-5-21-update.html that stated I can get the zip out of an old ASUS update and put that on my sdcard and let the tablet update itself to an older version. ASUS made an instruction sheet for manually updating with a zip, http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101G/e6754_TF101_Update_SOP.pdf. Once downgraded I could use RazerClaw http://forum.xda-developers.com/showthread.php?t=1345049 to root, and then flash a recovery, rom, etc.
Will this method work? I have to believe no, it just seems too easy. I haven’t tried it yet because I worried about bricking my tablet and not being able to fix it since it won’t connect to a computer.
Any response, opinion, recommendation, experience would be greatly appreciated.

I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY

frederuco said:
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
Click to expand...
Click to collapse
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.

I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.

You may be able to use Wolf's tut for this...

benmatlock said:
You may be able to use Wolf's tut for this...
Click to expand...
Click to collapse
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.

air adb, there's at least 1 good free one in the play store.

Lethe6 said:
air adb, there's at least 1 good free one in the play store.
Click to expand...
Click to collapse
Thanks for the response, I looked into that and I thought you had to be rooted for it to work. I'll look at it again.

akt27x said:
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
Click to expand...
Click to collapse
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.

akt27x said:
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
Click to expand...
Click to collapse
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)

frederuco said:
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
Click to expand...
Click to collapse
I tried this and you're right it didn't install the older firmware. It looked like it was going to because the status bar was moving at the bottom, but after a few minutes it went to an android laying down with his guts open and a exclamation mark above him.

benmatlock said:
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
Click to expand...
Click to collapse
I think I've tried this. I have a terminal emulator installed and I followed some instructions about entering things like this in but I think I got a message stating access denied. But I'll try it again tonight and reply back with the results.

Re: [Q] Possible Downgrade to Root
Using wolf's instructions I tried this with a terminal app on my tablet and got the following.
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
I then tried this and got the following.
[email protected]:/ $ dd if=/sdcard/recoveryblob.bin of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
Sent from my Transformer TF101 using XDA Premium HD app

Woody said:
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
Click to expand...
Click to collapse
This weekend I tried to install the drivers again. I first went through the control panel and device manager and deleted anything that said android and asus, then rebooted my computer. I then tried to install PDANet because I read that it'll install the drivers needed and if you're having a problem it's an easy way to install them. During the PDANet install it told me to plug my transformer in to load the drivers. When I did it said it was installing new drivers but then it said they didn't install. My transformer came up as an unknown device in device manager.
I then went through and deleted the unknown device and checked in the control panel again, then rebooted my computer. I then put my tablet in APX mode to try and get it to load the drivers. Again it didn't install them and my transformer came up as an unknown device. I deleted the unknown device agian, rebooted, and went to ASUS website and installed ASUS Sync. When it finished I rebooted and then started ASUS Sync. Again when I connected my transformer to my computer it said it was loading the drivers, then it failed, and the computer showed my transformer as an unknown device. ASUS Sync also stated there was no device connected to it.
All the reading I've been doing, it seems like there are some other people experiencing the same issues I am, and I haven't seen where anybody has posted a solution. If anybody has any input please let me know.

I think I'm getting closer. I downloaded WLanAdb from the play store and followed the directions and downloaded the needed files to my computer. In the command prompt I type "WLanAdbTerminal devices" and my tablet will show in the list of devices. But WLanAdb is only setup to except a few commands, the main purpose of the app is for pushing files. It was the only wireless ADB app that I could find that didn't require root.
I then found SSHDroid in the play market and I downloaded putty to my computer. I connect to my computer using that. When I type "adb devices" I get a mesage that states
daemon not running. starting it now on port 5038
daemon started successfully
List of devices attached
I then left putty and went back to the command prompt and typed "adb connect (with my ip address and port from SSHDroid)" and it said it connected to that ip address and port. I then type "adb devices" and there are no devices listed.
Again I think I'm very close to getting my tablet connected wirelessly to adb. I think there is just one simply thing I'm missing. Any help would be greatly appreciated.
I'll continue to update this thread until my tablet is rooted or I reach a dead end, so this will be a reference for anybody experiencing the same issues as me.
Thanks in advance.

akt27x, did you ever come to a solution?

presbypenguin said:
akt27x, did you ever come to a solution?
Click to expand...
Click to collapse
I haven't. I'm now trying to make a Linux boot flash drive to see if I can get my tablet to connect that way, since I've read that Linux doesn't require drivers. I downloaded LinuxLive USB Creator but haven't had the time to try it yet.

[Q] TF101 not recognized by PC (Windows 7/8 x64)

OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available​
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?

Do you have the stock USB cable? Are you plugging in to a usb3 slot?
Does the rom have fast charge enabled? I think that's what it's called but it allows USB charge rather than seeing your files and such.
Do you have mtp mode or mass storage mode options on the tablet?
Sent from my SGH-T999 using Tapatalk 2

Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?

estugarda said:
Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?
Click to expand...
Click to collapse
Lol I don't know on honeycomb. It's been a long time but these threads are filled with fast charge and the other issue as well. Do some more searches it's bound to give you something.
Sent from my SGH-T999 using Tapatalk 2

TomTcom said:
Lol I don't know on honeycomb. It's been a long time but these threads are filled with fast charge and the other issue as well. Do some more searches it's bound to give you something.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I did look around. I read a ton of posts here and elsewhere. There is nothing to the point. People at transformer forums are actually advising to just forget about the usb and use wireless transfer instead, since there are so many people with this problem who can't solve it. That would be fine with me, but I'm especially stuck because I can't flash anything since my USB connection is not working, and current CWM recovery doesn't seem to support flashing from internal memory/sd card.

Before you do anything else, install TWRP recovery before you brick your TF with CWM
Install Goo Manager here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Tap the menu dots at the top right of the app and choose "Install OpenRecoveryScript"
That should flash the latest TWRP recovery for you

estugarda said:
OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available​
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?
Click to expand...
Click to collapse
Are those drivers signed? I know 7 will reject an unsigned driver for security reasons.
Nexus 4 CyanogenMod 10.1.0RC2
---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------
estugarda said:
Yes, I have stock USB cable. At least I think so. I'm not the first owner. How can I be sure? It seems to be charging fine on the wall charger. It doesn't charge thru PC though.
If you are asking me if I tried it on USB 3.0; yes I did. Both 2.0 and 3.0. Not recognized.
I don't know if the ROM has "fast charge". I'm new to the TF101, and Honeycomb in general, and I didn't notice such an option. Where can I look?
I also didn't see any MTP/Mass storage modes in settings. Where would they be?
Click to expand...
Click to collapse
It should be somewhere in "storage" in settings.
Nexus 4 CyanogenMod 10.1.0RC2

Here you go hope it helps
Nexus 4 CyanogenMod 10.1.0RC2

*Detection* said:
Before you do anything else, install TWRP recovery before you brick your TF with CWM
Install Goo Manager here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Tap the menu dots at the top right of the app and choose "Install OpenRecoveryScript"
That should flash the latest TWRP recovery for you
Click to expand...
Click to collapse
Unfortunately, GO Manager wouldn't install OpenRecoveryScript. It says something along the lines of "No Recoveries were found for your device..."
ryaniskira said:
Are those drivers signed? I know 7 will reject an unsigned driver for security reasons.
Those from Asus websites are signed 100%.
Nexus 4 CyanogenMod 10.1.0RC2
Click to expand...
Click to collapse

estugarda said:
Unfortunately, GO Manager wouldn't install OpenRecoveryScript. It says something along the lines of "No Recoveries were found for your device..."
Click to expand...
Click to collapse
You might need to update to ICS first then, maybe Honeycomb is too old
CWM has a habit of boot looping devices, I would try updating to an ICS ROM and then trying Goo again before going for a Jellybean ROM
EDIT - You might have more luck getting TWRP installed using Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012

In the same boat
estugarda said:
OK. First of all, although I'm using the TF101 for the first time, I'd like to say that I've done a fair bit of rooting, troubleshooting and customizing various Android devices (HD2, Desire, SE x10, SGS2, SGSN, SGSN2...). So I ensure you, any lack of knowledge regarding the TF101 is not caused by ignorance. I'm trying to find out the cause for my problem for few days now, but can't find something to catch on. There are many similar problems with TF101 not being recognized by PC, but they all offer solutions which don't work, I don't understand them, or which make no sense.
Let's start at the beginning.
I have gotten my hands on Asus EEE Pad Transformer TF101. It was really cheap. I was told it came form USA.
It's obviously rooted, has a custom rom and recovery (ClockworkMod Recovery v3.2.0.1. roach2010-tf101-r1)
This is waht it says in Settings>About:
Model Number:
Transformer TF101G (although I think it is actually just a Wi-Fi model - TF101, it has no SIM slot)
Android version:
3.2.1
Baseband version:
Unknown
GPS version:
V5.5.8
Wi-Fi version:
V5.2.65
Bluetooth version
v6.24
Kernel version:
2.6.36.4-g6aa10ba
[email protected] #20111023
Build number
HTK75.prime_epad-2.1.0-20111105
Mobile Dock version:
Not available​
It seems to be working fine, except for being totally filled up with apps, bloatware and data. Natural instinct was to install a clean ROM. I wanted to go with CM, and a newer Recovery, but I got stuck on the first step. I can't get it recognized on any of my computers. Both Windows 7 and 8.
However I plug it in, I get; USB device not recognized. One of the USB devices attached to you computer has malfunctioned... This happens when I connect the USB cable when Android is booted up, when in recovery and also in APX mode, providing I have entered it (I'm not really sure because the display is always black).
In Device Manager, I can see only one exclamation icon (I did enable show hidden devices) in Universal Serious Bus Controllers called Unknown Device, which seems to be from the TF101. I tried uninstalling it. Restarting both the tablet and the computers. I tried to manually override those Unknown Device drivers with ASUS Android USB drivers for Windows and Universal_Naked_Driver_0.72 and ventana apx driver, but it wouldn't take any of them. I also tried installing them manually by right clicking on the INF files, and still nothing.
Then I thought I could mount the sdcard or USB mode in recovery, but that wouldn't work either.
Any solutions?
Click to expand...
Click to collapse
Have exhausted all resources all so if you find out anything please pm me. In the mean time I am still looking and I will keep you posted if I find out anything.

philseven said:
Have exhausted all resources all so if you find out anything please pm me. In the mean time I am still looking and I will keep you posted if I find out anything.
Click to expand...
Click to collapse
My guess is a bad USB cable. I had my USB cable stop working for ADB/APX/MTP/PTP but it still works with the Asus wall wart for charging. New USB cable fixed it straight away.

Solution
hi. if you cannot enter apx mode. try flashing a new rom of the tf101 or reflashing your current recovery

Soft brick Asus transformer tf101,None boot stuck\no USB
Hello I'm having the same problem with my tf101 but I can't get windows 7 64bit too load a driver for it, tried them all? Mine is soft bricked and there's no recovery file to restore. getting file not found.
Only shows CMW Based recovery v 5.5.0.4 roach-tf101-r2, also won't see SD card to re flash a rom or recovery.img, seems everywhere I turn I hit a wall on getting it back to working again, just hangs on Asus Logo?
please help? do I need to use a terminal program? is there a way to force a driver to load and see it long enough to reimage?
Thanks tons for any help.:crying:

rmontgo3Denver said:
Hello I'm having the same problem with my tf101 but I can't get windows 7 64bit too load a driver for it, tried them all? Mine is soft bricked and there's no recovery file to restore. getting file not found.
Only shows CMW Based recovery v 5.5.0.4 roach-tf101-r2, also won't see SD card to re flash a rom or recovery.img, seems everywhere I turn I hit a wall on getting it back to working again, just hangs on Asus Logo?
please help? do I need to use a terminal program? is there a way to force a driver to load and see it long enough to reimage?
Thanks tons for any help.:crying:
Click to expand...
Click to collapse
Same problem here... Tried Naked Driver and still got nothing. The Tablet just won't get recognized by the computer (Windows 8.1).
Did you have any luck unbricking it?
I've been through soft bricks before but this time, it seems to me that I've hit the bottom... I just can't think of anything else... any help??

had this problem for 2 years now. started off off like that, now it doesnt recognize at all. if it's rooted, flash a recovery using a terminal emulator. (there are instructions on team win's website on how to flash it to the appropriate block). then, just install a ROM with twrp. mine is in a permaloop. wiping data, rebooting, doing it again. if you get it to work, don't tinker with it any more. that's from my experience.
Sent from my LG-LG870 using Xparent Blue Tapatalk 2

tf101
hi, my asus tf101 has a same issue,my laptop don't recognized my asus,i dont know if the problem is in the cable or what,.i tried already what i saw in youtube but nothing happen.,the sdcard slot is not working,i used cwm v5.8.1.8 touch ,.but i want to change it into original stock version..now ,im working on how my device will recognize...is there a solution to bringback the original recovery base without using computer?..thank you..
---------- Post added at 03:08 PM ---------- Previous post was at 03:04 PM ----------
fabioporto said:
Same problem here... Tried Naked Driver and still got nothing. The Tablet just won't get recognized by the computer (Windows 8.1).
Did you have any luck unbricking it?
I've been through soft bricks before but this time, it seems to me that I've hit the bottom... I just can't think of anything else... any help??
Click to expand...
Click to collapse
got a same issue here,with my asus tf101,i regret to changed my recovery base into cwm touch v5.8.1.8.. it didn't show my ext sdcard file to change it again..i want to bring back the old one..but i don't know how..please please please..need help..
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
James130201 said:
hi. if you cannot enter apx mode. try flashing a new rom of the tf101 or reflashing your current recovery
Click to expand...
Click to collapse
hi sir,..i have the same problem above,.my data cable doesn't work ..the cwm i used now doesn't show my ext sd card,.only clockworkmod file,.is it possible to flash the old rom without computer?..how..please reply ,..thanks,

Don't wanna be the bearer of bad news but, I gave up trying to recover that thing a long time ago buddy. My advise to you would be: let go of it. The way I see it, the only way you could do it would be if you could replace the connection port and regain access to you tablet through you computer - considering the problem is being caused by that port.
Another way of doing that would be if you could actually have access to the tablet's internal storage and then place a ROM there so you could flash that using CWM.
Those are the only two options I didn't try, and now I can't, since I gave mine away to someone I thought could try one of those things, but not even an eager 17 year old boy could do it.
So, good luck with that.

Firmware Upgrade Encountered an Issue. Tab 2 7 (P3110)

Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.

How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.

Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.

I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!

Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.