Database Info

[Q] CMW (internal storage) no ROM (on SD) on TF101 b80

hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "

im on recovery and when i run adb devices it just blank. any walk through is much appreciated!

Do yo have USB debugging on?

I dont know because i was about to flash a new rom so i did a full wipe already

Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.

i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe

i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.

I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!

Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!

If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.

thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...

still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.

yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz

monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.

[SOLVED] Need help: Can't get ADB to recognize device

I have a Windows 7 Professional 64 bit machine. I have tried every combination I can think of to get the TF300T to show up in adb devices, but to no avail. I have installed Asus Sync and then done Update Driver in the Device Manager, uninstalled Asus Sync and downloaded only the drivers from the thread in the development section, modified the android_winusb.inf in the Android SDK and tried using that driver, many restarts, etc. I have needed to modify every android_winusb.inf I have used, btw, since even the Asus ones didn't have my device in there (my hardware ID ends in 4C81, the one supplied only supported 4DAE, which I find odd).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I update the driver, the device does show up in the Device Manager as "ASUS Android ADB Interface" under "Android Phone," which is where my Galaxy Nexus also shows up, but adb devices only returns the nexus. And now, when I go into "My Computer," the Asus doesn't show up as a connected device (the GNex still does). Same in the Device Manager under Portable Devices.
Has anyone been able to get their TF300T to work with ADB on a Win7 64 bit machine? Is it possible that the version of Windows (Professional) could be causing the issue? I have heard that in the past. Any help would be greatly appreciated. Thanks!

I have windows 7 home edition (x64), I had installed Android SDK a long time ago. Before I connected my Pad for the first time, I updated Android SDK through the manager. I don't have ASUS sync nor Suite. The first time I connected the Pad it automatically installed some drivers, and it worked with adb from the get-go.

I'm on Win7 HP 64 and its working fine here
https://docs.google.com/open?id=0B_7VIwxjudWvVEt4N2JaeUJQUVk
Fixed sharing linkage
Here is the drivers I used.

Northern-Loop said:
I'm on Win7 HP 64 and its working fine here
https://docs.google.com/open?id=0B_7VIwxjudWvVEt4N2JaeUJQUVk
Fixed sharing linkage
Here is the drivers I used.
Click to expand...
Click to collapse
Is this the same drivers as here http://forum.xda-developers.com/showthread.php?t=1661653?
The zip has the same name, so I'm just wondering if you made any tweaks to get it to work or not.

Accord281 said:
Is this the same drivers as here http://forum.xda-developers.com/showthread.php?t=1661653?
The zip has the same name, so I'm just wondering if you made any tweaks to get it to work or not.
Click to expand...
Click to collapse
No not changed anything. Have you installed Google SDK with the USB drivers?
http://developer.android.com/sdk/index.html
Enabled USB Debugging on the tablet under Settings/Dev Options?
Here is mine: https://docs.google.com/open?id=0B_7VIwxjudWvUmJKNmtLYVJ4THM

Northern-Loop said:
No not changed anything. Have you installed Google SDK with the USB drivers?
http://developer.android.com/sdk/index.html
Enabled USB Debugging on the tablet under Settings/Dev Options?
Here is mine: https://docs.google.com/open?id=0B_7VIwxjudWvUmJKNmtLYVJ4THM
Click to expand...
Click to collapse
Yes I've done both those things. I even went so far as to try to copy the relevant information from the Asus drivers into the google usb drivers. It lets me install the driver and then shows up under the Android Phone in Device Manager. But still no luck with adb. I even uninstalled the GNex and then reinstalled it using the same drivers as the Asus (again, copying relevant info into the android_winusb.inf file) and that works just fine. Did it again with a Droid Incredible 2 and that also worked. I thought it might perhaps be related to the fact that the .inf file is no longer signed but these 2 cases make that theory go out the window.
I am banging my head against the wall on this one. I had the same problem with an Acer Iconia A500 and I never did get that one to work.

Accord281 said:
Yes I've done both those things. I even went so far as to try to copy the relevant information from the Asus drivers into the google usb drivers. It lets me install the driver and then shows up under the Android Phone in Device Manager. But still no luck with adb. I even uninstalled the GNex and then reinstalled it using the same drivers as the Asus (again, copying relevant info into the android_winusb.inf file) and that works just fine. Did it again with a Droid Incredible 2 and that also worked. I thought it might perhaps be related to the fact that the .inf file is no longer signed but these 2 cases make that theory go out the window.
I am banging my head against the wall on this one. I had the same problem with an Acer Iconia A500 and I never did get that one to work.
Click to expand...
Click to collapse
So when you type adb device it shows nothing?
Try removing all ASUS from device manager reboot then plug device back in and let windows sort it out.
You'll need to Google to remove hidden ASUS stuff from device manager though.

Northern-Loop said:
So when you type adb device it shows nothing?
Try removing all ASUS from device manager reboot then plug device back in and let windows sort it out.
You'll need to Google to remove hidden ASUS stuff from device manager though.
Click to expand...
Click to collapse
Correct. It will show my GNex or my Dinc 2 (depending on which one is plugged in), but the Asus isn't there. I will try those things and update. Thanks.
Edit: No go. I uninstalled the Asus Composite ADB Interface then turned off USB debugging then uninstalled the TF300T listing that popped up after that. After reboot, I connected it while not in debug mode, allowed it to install the driver itself, then turned on debug mode and had to manually point it to the driver. It still shows up in Dev Manager under Android Phone, but still nothing in ADB. I get the feeling there is nothing that can be done.

My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.

xAshxMoneyx said:
My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.
Click to expand...
Click to collapse
H.O.L.Y. S.H.I.T. that did it. I just switched it to camera (PTP) and it is now listed in adb. THANK YOU THANK YOU THANK YOU THANK YOU!!!!!!

Took me quite a while to figure that out (and I have no idea why it works TBH, just got lucky), glad I could help out.

xAshxMoneyx said:
Took me quite a while to figure that out (and I have no idea why it works TBH, just got lucky), glad I could help out.
Click to expand...
Click to collapse
The odd thing is, my GNex is set to Media device, and it works just fine. Thanks again.

Accord281 said:
The odd thing is, my GNex is set to Media device, and it works just fine. Thanks again.
Click to expand...
Click to collapse
No problem homie. My GS2 didn't have that problem either, went in just fine as ADB.

Accord281 said:
I have a Windows 7 Professional 64 bit machine. I have tried every combination I can think of to get the TF300T to show up in adb devices, but to no avail.5
Click to expand...
Click to collapse
OMG, this is what happened to me last night when I tried to do the downgrade so I could root the phone.
I am on an XP 32bit machine.
I have a feeling that the Samsung software, which I also had installed on this machine is conflicting.
I'm in the process of removing all the drives (Samsung and Asus) and starting from scratch.
I still need to read the rest of this thread to see if someone answered your question, if they did, they they help me as well.
Rob

HI,
I guess a picture is worth a thousand words.
I finally managed to get a screen shot of what I have been asking help on:
I've been trying to do a downgrade so I can root my 300.
Why is the Asus showing up underneath my Samsung and does it matter.
Thanks!
Rob

Looks like it's showing up as ADB so it should be fine. Mine comes under a generic "android phone" listing, but maybe if Samsung was your first ever adb device on the computer, they will all show up that way for you. Just a guess.

thank you so much! I've been trying to solve this for 2 days
:good:
xAshxMoneyx said:
My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.
Click to expand...
Click to collapse

switch storage mode to camera
"I had to switch the storage mode to "camera" on the tablet"
How is that done? I only have usb storage on or off options.. and still stuck

jbosari said:
"I had to switch the storage mode to "camera" on the tablet"
How is that done? I only have usb storage on or off options.. and still stuck
Click to expand...
Click to collapse
Sorry to bump an old thread, but I have the same problem, can't get ADB to recognize my device, and onlu have usb storage on/off in the options.
Anybody shed a light in this?
Thanks in advance

Mefna said:
Sorry to bump an old thread, but I have the same problem, can't get ADB to recognize my device, and onlu have usb storage on/off in the options.
Anybody shed a light in this?
Thanks in advance
Click to expand...
Click to collapse
What is your device and version of Android you're running? It might help to know. There are some tools that can help. I've used USBDeview to delete all drivers and start over to fix problems like this (scroll down to the "Feedback" heading for the download.) After deleting anything ADB related from the list of drivers and starting over with the driver for my device, it worked... Good luck! I'll see what I can find if you write back with your device info.

[solved]Yet another CWM bootloop (b60,5.5.0.4, not recognized device on Win 7 32 bit)

Hi guys,
EDIT: Making some progress, the USB port was corrupted, now I can see my device in the adb devices list, yay!
EDIT2: After changing the USB port I was able to install the usb driver and after I connected with ADB I only run this code to get it working: http://forum.xda-developers.com/showpost.php?p=23339963&postcount=249
Sorry to bother you with this in a separate thread, however I am getting nowhere solving this and I've read through a lot of threads already without a clear solution. I am stuck in the CWM bootloop. I am using CWM 5.5.0.4, I am not able to get to the APX mode (if I understand correctly, that the APX mode is entered during boot presing the volume up button (with the two white lines of text appearing with a dead droid as background image)) (the tf101 is always booting to CWM). I've tried to install the naked drivers (http://forum.xda-developers.com/showthread.php?t=1379875) however my system won't accept them (I am getting an error message that the drivers aren't compatible with my device and that I have to make sure the drivers are for a 32bit OS, regrettably I am using a localized copy of windows so I can't paste the english error message). I've tried also other drivers like the one supplied with the android SDK (C:\Program Files\Android\android-sdk\extras\google\usb_driver\) and the ones coming with ViperMOD (http://forum.xda-developers.com/showthread.php?t=1427125), however the outcome is still the same. I've read somewhere to try to use a linux live cd (ubuntu) to flash an another version of CWM (recovery roach), however I couldn't find any guide on this approach.
So to summarize:
0) caused by Boot to recovery option (damn you!)
1) Stuck in CWM loop.
2) No access to SD card to flash another recovery from there
3) tf101 listed under USB in device manager as Unrecognized device with yellow triangle
4) Using win 7 32 bit
5) tried different usb drivers (sdk, naked, viperMOD), they don't install (used the select from list option in device manager, have disk...)
6) no access to external source (sdcard) to flash zip
7) adb not seeing device (adb devices gives empty list, adb remount gives device not found)
8) Tried EasyFlasher (but since the device isn't visible...)
9) installed asus synch and uninstalled afterwards as it didn't seem to help
Hopefuly I included everything I tried. Thanks in advance for any pointers.
I have a CM-10 nighty rom on the internal storage available, but I don't think this will help.
Jokob

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jokob.sk said:
Hi guys,
EDIT: Making some progress, the USB port was corrupted, now I can see my device in the adb devices list, yay!
EDIT2: After changing the USB port I was able to install the usb driver and after I connected with ADB I only run this code to get it working: http://forum.xda-developers.com/showpost.php?p=23339963&postcount=249
Sorry to bother you with this in a separate thread, however I am getting nowhere solving this and I've read through a lot of threads already without a clear solution. I am stuck in the CWM bootloop. I am using CWM 5.5.0.4, I am not able to get to the APX mode (if I understand correctly, that the APX mode is entered during boot presing the volume up button (with the two white lines of text appearing with a dead droid as background image)) (the tf101 is always booting to CWM). I've tried to install the naked drivers (http://forum.xda-developers.com/showthread.php?t=1379875) however my system won't accept them (I am getting an error message that the drivers aren't compatible with my device and that I have to make sure the drivers are for a 32bit OS, regrettably I am using a localized copy of windows so I can't paste the english error message). I've tried also other drivers like the one supplied with the android SDK (C:\Program Files\Android\android-sdk\extras\google\usb_driver\) and the ones coming with ViperMOD (http://forum.xda-developers.com/showthread.php?t=1427125), however the outcome is still the same. I've read somewhere to try to use a linux live cd (ubuntu) to flash an another version of CWM (recovery roach), however I couldn't find any guide on this approach.
So to summarize:
0) caused by Boot to recovery option (damn you!)
1) Stuck in CWM loop.
2) No access to SD card to flash another recovery from there
3) tf101 listed under USB in device manager as Unrecognized device with yellow triangle
4) Using win 7 32 bit
5) tried different usb drivers (sdk, naked, viperMOD), they don't install (used the select from list option in device manager, have disk...)
6) no access to external source (sdcard) to flash zip
7) adb not seeing device (adb devices gives empty list, adb remount gives device not found)
8) Tried EasyFlasher (but since the device isn't visible...)
9) installed asus synch and uninstalled afterwards as it didn't seem to help
Hopefuly I included everything I tried. Thanks in advance for any pointers.
I have a CM-10 nighty rom on the internal storage available, but I don't think this will help.
Jokob
Click to expand...
Click to collapse
Give naked drivers one more shot... remove/uninstall/delete all existing drivers... restart you laptop.. unzip naked drivers into a folder, go to device manager and refresh, windows will try to install Asus driver, if you can stop it then do otherwise once its installed go back, right click and select upgrade/update... once this is done you should see 1st image attached. Now turn off your tablet while cable its to the laptop, press power+ volume up buttons together for say 10 secs and u will be in apx mode, laptop will show either installing apx drivers or unknown device found. If windows installs apx driver, again go back to device manager and delete that driver and manually install naked driver and when completed you should see image 2nd image... as you know while in apx mode tablet screen doesn't show much, now run easy flash and select SBK1 or SBK2 so that you can flash recovery, remember flash either rogue recovery of twrp but not cwm 5.x.x.x as it again blocks the access to external memory..... good luck
PS: windows will say "drivers r not safe/digital signatures are missing" or something like that when you try to install universal naked driver, don't worry just continue and finish it.
Sent from my Transformer TF101 using xda app-developers app

jokob.sk said:
I am not able to get to the APX mode (if I understand correctly, that the APX mode is entered during boot presing the volume up button (with the two white lines of text appearing with a dead droid as background image))
Click to expand...
Click to collapse
No, this is wrong.
Hold down the VOLUP + POWER Button until your tablet turns off and boots into APX mode (APX mode has no display - the screen will stay off)

It's working now. The culprint was the broken usb port. I tried an another one and I was able to proceed to fix my tf101 with help of the naked drivers and the fixed cwm 5.5.0.4 package and transfering it to the internal memory using ADB, so everything is fine now. Thanks for the response!
Sent from my Transformer using Tapatalk 2

Frequently Asked Questions for Asus Transformer TF300T Thread

Welcome to the Frequently Asked Questions for your Asus Transformer TF300T
Click to expand...
Click to collapse
This thread is here to help our community out as best as it can.
Why is this thread here?
There's 2 main reasons really. The first reason is to stop the development threads getting filled with questions which have nothing to do with the thread they're posted in. That then makes the thread go off-topic which is not what a development thread is there for.
The second reason is because there are too many repetitive questions being asked. The main problem with that is the fact that other users will sometimes attack the OP and 'flaming' them.
The main way which this thread will help to stop that happening is by helping you out as much as possible, while being in a friendly environment.
Below you will find the Thread Rules which I expect you all to follow and not to break them.
Thread Rules
1. Remember that while posting in this thread and across the whole site, you must not break the Forum Rules.
2. Even though this thread is for everyone to use, there'll be a lot if new members in here so no flaming or insulting anyone else.
3. As this is a help thread, remember that there is no such thing as a stupid question.
4. Even if you get your question answered by reading the 2nd post, be sure to come back here and read some more. It will help you to learn even more.
​
Click to expand...
Click to collapse
Hall Of Fame
As I'll be keeping an eye on this thread quite a lot, I'll be adding the people to this list who have been the most helpful and are contributing the most, and we need your help for a good FAQs​
Code:
[B][CENTER]
[B]1.[URL="http://forum.xda-developers.com/member.php?u=4518416"][B][COLOR="Blue"] - QuantumFoam[/COLOR][/B][/URL] who is the chief editor of the FAQ
2. - [URL="http://forum.xda-developers.com/member.php?u=2559267"][B][COLOR="Green"]tobdaryl[/COLOR][/B][/URL] - Help provider
3.
4.
5.[/B][/SIZE][/CENTER][/B]
​
Asus TF300 Moderators
Click to expand...
Click to collapse
If you report any posts, the report will go to our SM (Senior Moderator) and FSMs (Forum Specific Moderators). They are our SM - zelendel and our FSMs - babijoee, chrisd1a1, Divine_Madcat, GODZSON, Moscow Desire, zacthespack . If you have any questions about this forum in particular then feel free to drop them a PM or you can use the button report
XDA In General
Click to expand...
Click to collapse
First of all, I'm linking to some general XDA threads which can help you become more familiar with this site and how things run. I feel this is one thing which new users don't realize because they think it's okay to come to this site and post anywhere.
If you don't feel this applies to you, please move onto the Asus TF300T links further down this post.
The first of all is the Forum Rules, which is the first thread that you must read and implement for taking good time here
The XDA Tour and Report Posts
XDA New User Guide - I can't stress enough how important that thread is. If you follow what that guide says, you'll be well on your way to becoming an asset to the XDA forums.
[HOW TO] Make A Substantial Thread, Post, Question & Poll - This is also a must read thread. Why, you ask? Well it's simple. Reading this will show you the best way to post your thread to ensure that people will respond and be able to help you. Rather than just giving no information or a thread title called "Mah phone brikked. Hlp me plzzz!", following that thread will give you the best chance of being helped.
[HOW TO] Make A Good Signature - This really is needed because as you'll see in a lot of signatures, mine included, is that we list our current devices and what ROM/kernel we are using. This helps people to help us. Take a look at the thread to find out what else to include in your signature.
ASUS TF300T Helpful Links
Click to expand...
Click to collapse
- [INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
- [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]
- (TF300T)For All Your Jelly Bean discussions-problems
- (TF300TG)For All Your Jelly Bean discussions-problems
- Small guide for Install recovery and rooting when you are already to JB
- [GUIDE] Help for flash more faster when you use Fastboot Line Command
- How to install Universal Naked Drivers
In post 2 there'll be an FAQ which will help you out aswell
And don't forget to rate for this thread -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance

Reserved for FAQ

Reserved again

Reserved again

Aaaand I'll take #5

USB ADB Drivers (both OS and Recovery modes)
I have a new TF300T factory ICS 4.0.3.
I was able to setup APX mode and its driver is correctly
installed. The tablet is recognized as an MTP device and the
internal (/sdcard) mount point is reachable.
After enabling setup/developer options/USB debugging,
ADB does not 'see' the device though, adb devices
does not return the serial number.
I'm guessing I need more / different drivers.
I have the 'naked driver 0.72' package, but the
.inf is not setup for 'install' and device manager
update driver says I have the latest driver installed?
Do I uninstall the USB driver ASUS sync installed and
and then install the 'naked driver' package from the
new device wizard?
Thanks

fuzzynco said:
I have a new TF300T factory ICS 4.0.3.
I was able to setup APX mode and its driver is correctly
installed. The tablet is recognized as an MTP device and the
internal (/sdcard) mount point is reachable.
After enabling setup/developer options/USB debugging,
ADB does not 'see' the device though, adb devices
does not return the serial number.
I'm guessing I need more / different drivers.
I have the 'naked driver 0.72' package, but the
.inf is not setup for 'install' and device manager
update driver says I have the latest driver installed?
Do I uninstall the USB driver ASUS sync installed and
and then install the 'naked driver' package from the
new device wizard?
Thanks
Click to expand...
Click to collapse
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process. I just received a window computer last week and had the same issue. This will be a long post but was necessary for me.
Here are the choices I had to use to change my drivers
.
windows-start - in search type device manager and return.
right click on the entry you wish to change the driver for.
Update Driver Software.
Browse my computer for driver software.
Let me pick from a list of device drivers on my computer.
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says not signed; install anyway
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!

sigh MTP works but ADB doesn't
tobdaryl said:
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process. I just received a window computer last week and had the same issue. This will be a long post but was necessary for me.
Here are the choices I had to use to change my drivers
.
windows-start - in search type device manager and return.
right click on the entry you wish to change the driver for.
Update Driver Software.
Browse my computer for driver software.
Let me pick from a list of device drivers on my computer.
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says not signed; install anyway
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!
Click to expand...
Click to collapse
can'tn test fastboot yet, but guessing when one work both will.

fuzzynco said:
can'tn test fastboot yet, but guessing when one work both will.
Click to expand...
Click to collapse
I'm sorry your screen capture is not large enough to see.
With your tablet unplugged open device manager; now plug your tablet into the computer and you will either see asus adb interface or maybe a driver failure. Either a larger screen capture or try to explain the changes in device manager is needed.
It would be good if I knew the state of your tablet while you are doing this.
My screenshot for adb (at the top ) and data at the bottom.

followup: tf300 adb drivers?
tobdaryl said:
I'm sorry your screen capture is not large enough to see.
With your tablet unplugged open device manager; now plug your tablet into the computer
and you will either see asus adb interface or maybe a driver failure. Either a larger screen
capture or try to explain the changes in device manager is needed. It would be good if I
knew the state of your tablet while you are doing this.
Click to expand...
Click to collapse
Both tablets work normally with their OSes and the supplied apps work as expected.
For the ICS one all I did was set developer options to enable adb, the tablet does display
the icon in the lower right corner, so the 'server' is working. I wanted to experiment
with custom firmware, so I got a new tablet that still has ICS so it can run nvflash
for tf300t.
Normal boot (the ICS tablet is unrooted & locked as it came from factory,
the JB one is rooted, (using OTA Rootkeeper and OTA JB updates),
locked). I have 2 tablets (Black is JB and Blue is ICS).
MTP and APX modes are recognized, neither recognizes ADB
('adb devices' does not return serial number with normal 'desktop'
displayed).
I see code 10 on the ASUS Transformer ADB interface, (with the usual 'exclamation point' error flag).
MTP and APX drivers did install and work as expected. normal OS (either ICS or JB) boot).
As I said, after looking at the content of the .inf file, there is a section for tf101 and tf201
but not for tf300 and tf700, I wondered if that was the issue ? If so, where does one get the
correct tf300t drivers for adb modes and fastboot mode?
http://support.microsoft.com/kb/943104
As usual ASUS support was less than helpful. They tell me there are no ADB drivers
or Fastboot drivers.
While I'm asking, is ICS supposed to support USB mass storage, (on my HTC devices
I'm prompted for USB connection mode, (charge only (used with adb), disk (UMS) or
HTC sync)? ASUS doesn't prompt for UMS or MTP connection modes?
Thanks

fuzzynco said:
Both tablets work normally with their OSes and the supplied apps work as expected.
For the ICS one all I did was set developer options to enable adb, the tablet does display
the icon in the lower right corner, so the 'server' is working. I wanted to experiment
with custom firmware, so I got a new tablet that still has ICS so it can run nvflash
for tf300t.
Normal boot (the ICS tablet is unrooted & locked as it came from factory,
the JB one is rooted, (using OTA Rootkeeper and OTA JB updates),
locked). I have 2 tablets (Black is JB and Blue is ICS).
MTP and APX modes are recognized, neither recognizes ADB
('adb devices' does not return serial number with normal 'desktop'
displayed).
I see code 10 on the ASUS Transformer ADB interface, (with the usual 'exclamation point' error flag).
MTP and APX drivers did install and work as expected. normal OS (either ICS or JB) boot).
As I said, after looking at the content of the .inf file, there is a section for tf101 and tf201
but not for tf300 and tf700, I wondered if that was the issue ? If so, where does one get the
correct tf300t drivers for adb modes and fastboot mode?
As usual ASUS support was less than helpful. They tell me there are no ADB drivers
or Fastboot drivers.
While I'm asking, is ICS supposed to support USB mass storage, (on my HTC devices
I'm prompted for USB connection mode, (charge only (used with adb), disk (UMS) or
HTC sync)? ASUS doesn't prompt for UMS or MTP connection modes?
Thanks
Click to expand...
Click to collapse
The universal naked drivers work properly for our unit even though they are not marked as such.
Asus MTP, go to settings/storage and select (in my case) three dots in the upper right(options). This will give you usb computer connection, click that, place a check beside MTP.
Your device manager entry with code 10 is where you use the directions I provided earlier to install universal drivers. While you were away I made a post in general with screen shots that may help.
Uptate:
I forgot fastboot. The tablet will only present the fastboot interface to your pc when you are in fastboot mode. From bootloader menu volume down to the usb symbol and volume up to select. This is only available after you unlock!

progress ADB for JB works, ICS doesn't.
tobdaryl said:
The universal naked drivers work properly for our unit even though they are not marked as such.
Asus MTP, go to settings/storage and select (in my case) three dots in the upper right(options). This will give you usb computer connection, click that, place a check beside MTP.
Your device manager entry with code 10 is where you use the directions I provided earlier to install universal drivers. While you were away I made a post in general with screen shots that may help.
Uptate:
I forgot fastboot. The tablet will only present the fastboot interface to your pc when you are in fastboot mode. From bootloader menu volume down to the usb symbol and volume up to select. This is only available after you unlock!
Click to expand...
Click to collapse
Since neither tablet is currently unlocked I'm just trying
to get 'adb devices' to return the serial number in normal
OS boot mode. With the tablets in APX mode, Windows
Device Manager does see the APX driver correctly.
After updating the driver per your instructions, Windows 7
+ JB works, Windows 7 + ICS does not.
Windows 7 Pro '"see's" the Jellybean TF300T ('adb devices' responds with device serial number)
That tablet is running 4.1.1 (OTA JB) started life as 4.0.3 and was rooted without unlock while
on ICS, OTA Rootkeeper saved, JB OTA updated, OTA Rootkeeper restored root successfully.
The new ICS tablet that has nothing other than USB debugging turned on, is not seen on the same
Windows 7 Pro that see's Jellybean fine. I'm puzzled, if JB is seen properly, the driver is installed
correctly, right?? Unless there is factory defect in the new tablet, what else might cause different
behavior for ICS vs JB firmware, with the same driver?
Thanks

fuzzynco said:
Since neither tablet is currently unlocked I'm just trying
to get 'adb devices' to return the serial number in normal
OS boot mode. With the tablets in APX mode, Windows
Device Manager does see the APX driver correctly.
After updating the driver per your instructions, Windows 7
+ JB works, Windows 7 + ICS does not.
Windows 7 Pro '"see's" the Jellybean TF300T ('adb devices' responds with device serial number)
That tablet is running 4.1.1 (OTA JB) started life as 4.0.3 and was rooted without unlock while
on ICS, OTA Rootkeeper saved, JB OTA updated, OTA Rootkeeper restored root successfully.
The new ICS tablet that has nothing other than USB debugging turned on, is not seen on the same
Windows 7 Pro that see's Jellybean fine. I'm puzzled, if JB is seen properly, the driver is installed
correctly, right?? Unless there is factory defect in the new tablet, what else might cause different
behavior for ICS vs JB firmware, with the same driver?
Thanks
Click to expand...
Click to collapse
It is very possible that adb will not work properly on ICS unless it is unlocked. I can't remember but would say it is very likely since JB does work and both use the same drivers. In two days I was unlocked, on the latest JB, twrp installed and waiting for a non stock based rom.
There are some differences between JB and ICS. I received ICS input from wha2do concerning methods of entry into apx and bootloader while I was gathering info to update my thread. Here are the ones we identified.
or - no need to hold volume with these
8. adb reboot bootloader
or
9. fastboot -i 0x0B05 reboot-bootloader
or
10. from terminal - you must be rooted for this to work
su
reboot bootloader
Note 1: If you have nvflash installed some of the commands presented in this post may not work; possibly 8, 9, and 10 - THANKS TO wha2do for this info!
I need to update my info to: If you have ICS or Nvflash.
I think you are ok but give adb another try on ICS when you unlock and if you have problems let me know.

OK - 1st try will be unlock and attempt adb again
I think you are ok but give adb another try on ICS when you unlock and if you have problems let me know.
Click to expand...
Click to collapse
on ICS tablet
Do the locked root process
OTA Rootkeeper save
Unlock ICS bootloader
test fastboot devices
test adb devices
(if ok)
adb backup
fastboot flash recovery
boot to recovery
test adb devices (in recovery mode)
nandroid backup
Hopefully everything will work as it should
if everything else worked I can try nvflash backup process
*sigh* I hope it works

fuzzynco said:
on ICS tablet
Do the locked root process
OTA Rootkeeper save
Unlock ICS bootloader
test fastboot devices
test adb devices
(if ok)
adb backup
fastboot flash recovery
boot to recovery
test adb devices (in recovery mode)
nandroid backup
Hopefully everything will work as it should
if everything else worked I can try nvflash backup process
*sigh* I hope it works
Click to expand...
Click to collapse
Good list and order. I'm always in favor of getting adb and fastboot working properly before going forward. If you experience problems you have done everything possible to give yourself a path to recovery.
Let me know If I can help further.
Good Luck!
Be positive! It's going to work!
Just take your time and try to stick to your list.
Note: do not use WIPE DATA on the bootloader menu!!!

Note: do not use WIPE DATA on the bootloader menu!!!
Note: do not useWIPE DATA on the bootloader menu!!!
Click to expand...
Click to collapse
You know, I've often wondered why that is even there,
The right place to do 'wipes' is in a custom Recovery,
where there is an OS controlling the device mounts
and unmounts. The boot loader is more or less like
a PC's BIOS, while it can do it, its too early in the
boot process for it to have the right understanding
about whats happening in the devices setup, to
do it safely and properly.

fuzzynco said:
You know, I've often wondered why that is even there,
The right place to do 'wipes' is in a custom Recovery,
where there is an OS controlling the device mounts
and unmounts. The boot loader is more or less like
a PC's BIOS, while it can do it, its too early in the
boot process for it to have the right understanding
about whats happening in the devices setup, to
do it safely and properly.
Click to expand...
Click to collapse
+1
Thanks for the explanation.

how to unlock bootloader please?
I just received my asus t300 and updated all the software OTA so it is now on stock Jelly Bean. I have read in a few places saying use the ASUS bootloader unlocker but it was for ICS i believe. I have read posts of the asus unlocker bricking devices that have JB installed and I don't want to be one of those people. Please point me in the right direction on how to safely unlock the bootloader so I can root and try out a faster ROM. I have rooted my cell phones (note2, gsIII) all day long but for some reason I can't find the start of the "bread crumb" trial for this device.
Thanks!!!
Q

quantum3 said:
I just received my asus t300 and updated all the software OTA so it is now on stock Jelly Bean. I have read in a few places saying use the ASUS bootloader unlocker but it was for ICS i believe. I have read posts of the asus unlocker bricking devices that have JB installed and I don't want to be one of those people. Please point me in the right direction on how to safely unlock the bootloader so I can root and try out a faster ROM. I have rooted my cell phones (note2, gsIII) all day long but for some reason I can't find the start of the "bread crumb" trial for this device.
Thanks!!!
Q
Click to expand...
Click to collapse
Quot from Asus: ※This tool now only works with TF300T ICS & JB of TW,US,WW CN SKU. It won’t work on other devices.
Register your unit with Asus, log into play store, run the unlocker. The bricks I have seen unlocking have been caused by WIPE DATA on the bootloader/recovery menu. Never use that!
Note: I failed to add this link earlier. This is good simple directions for unlock.

I'm not sure how to search for my problem, but I can try to describe it
all of my root directory has been moved into a folder called 0, and now there are just some random folders in the new root directory
I recently unlocked my bootloader and flashed twrp, and I made a recovery image at that point.
Then I flashed CM10.1
Then I decided not to use CM10.1 , so i tried to restore from the recovery image
So now thats where I am, and I am trying to root it now.
The default root directory that i had previously placed the CM10.1 zip is in the folder 0, and it wouldnt read any zips i placed in the regular root directory.
So if i place the root-signed zip into the regular root directory, it doesn't read it.
It does read it if it is in the same directory as the CM10.1 zip, or the folder called 0
I flashed the zip, and it didnt seem to do anything.
I may have not done a certain step during the recovery or restoration process, but I was pretty sure to wipe cache before flashing stuff, and I reset to factory before flashing CM10.1
So the main problem I am having now is that I am unable to be rooted.
Im sorry this is horribly worded >.<
any help would be greatly appreciated!

[Q] Bricked Asus Transformer TF 101 B60

Hi all first off I'm sorry if this has been posted before but I'm having a problem unbricking an Asus transformer tf101 B60, I'll start with what's going on or not for that matter. lol
1. Boot to recovery is CWM-Based Recovery v5.5.0.4 roach-tf101-r2
2. will not see sd card / backup-restore= -2014-04-05.02.52.56 / no files found
3. Choose a zip = e: can't open /sdcard/update.zip
4.PC windows 7 pro 64 bit will not see the tablet when plugged into usb getting unrecognized device,force driver still getting yellow ding=device cannot start
if I plug in the usb and turn on the tablet windows does not even see that and unit sits on logo screen. and other screen the cold lynx boot that hangs there.
So in short I'm hitting a brick wall, windows won't see it, it won't see the SD card in recovery mode.
I've read in these posts how to fix this problem and have all the software / firmware you name it, but they all say almost the same thing, windows needs to see the device in order for any of these fixes to work, and thus is my wall I'm hitting.
Any help to find a solution to this problem would be oh so thankful to you all and call you Tablet Gods, this was a tablet given to me as a paper weight and I thought if it boots it can be fixed?
Thanks for your time and God like tablet knowledge.
Cheers.

Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable

Driver Not Working
*Detection* said:
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Click to expand...
Click to collapse
I booted the unit into recover mode and windows sees unknown device..Ok
Tried to install new naked driver and getting a splash saying not compatible with windows 64 bit, I tried this on a brand new windows 7 pro 32 bit laptop and got the same results. I do have a brand new usb cable for it thinking that the old one was faulty, tried adb again same thing no device found, are there any commands in terminal emulator that can force the driver on the usb port? I'm thinking that if windows sees an unknown device then at least it sees something there just not whats there? Am i wrong in that somehow it's lost the usb firmware connection? so the driver will not install and if forced does not make the connection to the device? So this is my results.
So I'm ready to put gun in mouth over this, my laptops going to divorce me over driver abuse and the tablet mocks me with the frozen Asus logo.
Again Thanks for all the advice and i'll keep slugging it out.As this unit is in perfect condition outside of the Bricked part

You don't need to boot it into recovery mode to start with, just install the drivers normally first with the TF101 connected and booted normally
It's always going to say it can't find the device if the driver isn't installed
Focus on getting that APX driver installed and working, once you have that installed, Im pretty sure it will see the device fine

Asus TF101 B60 Softbrick? What Now?
Hello all.
I've been searching in vain for an answer to my Bricked Asus tf101? I'm just going to get right to the problem.
I can't get the tablet to be seen by windows 7 pro 64bit, Unknown device and yes I've tried everything, except asking if there's a way to force connection through a terminal like I've seen done with a router and a network switch to force a flash file so as to get at least a response after a reboot instead of just the Asus splash screen, here's a summary.
The Good.
1. I can boot to recovery CWM-based recovery v5.5.0.4 roach-tf101-r2 with menu's
Bad: Does not see sd card only see's internal and there's no file or folder error for backup/restore
2.Boots to screen with 2 icons data wipe and linix cold boot and goes nowhere from there just hangs.
So I'm stuck here, I have all to tools to do the job only if windows would see it, Adb does not see device which means the same thing no driver no fix,
Everywhere I read it says do this and that and it will restore to factory, that would be great if windows saw the thing, so I'm looking for a way to get the tablet to boot to something other than a loop. also tried the put the E101_SDUPDATE.zip in the root of the SD card and restart, does not see the card or file or both so it's not loading the file?
1. windows 7 not seeing device, will not take force drivers, Universal-Nvidia-Asus- MTP
2. recovery does not see sd card, so can't flash new anything?
3. So no communication from SD/USB
4. Is there a terminal command I can use to force a Blob or flash a recovery to the tablet when drivers and USB don't respond?
And to top that off my laptop filed for divorce for driver abuse..lol I'm not giving up.
Thanks to you all,
I want to thank you all for your time and advice it is very much appreciated, and I'll keep slugging away because I know there's a fix out there.
Cheers.

Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install

Thanks
*Detection* said:
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Click to expand...
Click to collapse
Thanks for the Advice, Is there a thread outlining this so I can give it a try? I do have a new laptop I'm building out with windows 7 Pro 32bit as I've had so much trouble with the 64bit version.

If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done

*Detection* said:
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
Click to expand...
Click to collapse
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work

Sicknote said:
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Click to expand...
Click to collapse
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc

*Detection* said:
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
Click to expand...
Click to collapse
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.

Sicknote said:
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Click to expand...
Click to collapse
You're not going to be able to put the tablet into APX mode till you get the drivers installed correctly.
With the tablet connected to the computer and the tablet on, download the naked driver package. open up device manager and right click on Other Devices - APX and chose update driver. Chose browse and then go to where you downloaded the naked driver package. If it complains that they aren't signed, click install anyway. If successful, you should now be able to put your tablet in APX mode.