Database Info

[Q] ME301T not accepting fastboot commands

Ok, here's what's up. I have updated my ME301T from 4.1.1 to 4.2.1 on the 10.6.1.15.4 build number, and successfully unlocked my bootloader using the TF300T apk file, but when I try to use fastboot to load TWRP on as my recovery, my computer cannot find the tablet to send the commands to. I have tried two different computers with two different operating systems, used the naked drivers, and even forced a bootloader reboot from adb but still cannot get the tablet to accept fastboot commands. What am I doing wrong and is there another workaround for getting TWRP 2.5.0.0 loaded on my tablet?

Bump. Still not getting commands through to my fastboot.

Me too!
I'm in the same situation. Can't seem to get the fastboot usb drivers to work with fastboot commands. Fastboot devices command doesn't display any devices.
Current setup on my me301t:
- bootloader unlocked
- android version 4.2.1
- build # 0.6.1.25
- rooted
I would like to use the fastboot to install twrp or cwm so I can install a custom rom. GooManager won't install custom recovery, says no recoveries are available for my device. Rom Manager says it flashes the CWM recovery but doesn't work. If I take the OTA update to go to build 0.6.1.31 I lose root and am unable to restore root. I then have to reflash to .25 by placing the ASUS stock firmware on my micro-SD card and rebooting into RCK (recovery) using vol-down while powering up.

fastboot
First of all You should to be shure that tablet connected directly to the usb port without any usb-hub. Sometimes usb on front panel of PC may cause same problem, so use one on the rear side. If You use windows os check device manager. You should see something like asus fasboot inteface or bootloader interface, if is not there - reinstall drivers.
P.S.: I hope my English is not too terrible.

The device shows up as "bootloader interface" when in fastboot bootloader. The command adb devices works fine. fastboot devices shows nothing. this is obviously a driver issue, otherwise fastboot devices would show the device same as adb devices. I've tried both on ubuntu and windows with no results.
---------- Post added at 10:05 PM ---------- Previous post was at 09:46 PM ----------
darktowermage said:
The device shows up as "bootloader interface" when in fastboot bootloader. The command adb devices works fine. fastboot devices shows nothing. this is obviously a driver issue, otherwise fastboot devices would show the device same as adb devices. I've tried both on ubuntu and windows with no results.
Click to expand...
Click to collapse
I finally got fastboot to show the device on Ubuntu 12.04. Here's how:
- install the adb fastboot ppa on ubuntu following the instructions at webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html. Can't post the full link because of my XDA perms.
- run fastboot as root like so:
sudo fastboot devices
Didn't initially run it as root. That was the key for me. Still not sure why Windoze didn't work, but that's typical.

Need help flashing TWRP using fastboot!

I'm trying to flash TWRP as a step to installing KitKat but I'm getting stuck booting into fastboot/bootloader trying to install the TWRP Recovery.
After I've installed the adb and fastboot files (15sec ADB Installer v1.3) I connect my tablet and open command in the directory folder and when I type "fastboot devices" all I get back is:
C:\adb
What am I doing wrong? I already have TWRP.blob inside the folder directory but I can't use fastboot to install it because it is not showing my device
I installed 15 seconds ADB Installer v1.3
I installed it on Win 7 64bit Lenovo G560 laptop
I unlocked the tablet myself using the Asus Unlock utility
I only have USB 2.0
I'm not sure if the tablet is in fastboot because I'm not cold starting it. I'm just connecting it to my PC and then opening a command window inside the adb files folder C:/adb
My tablet is running on Android JB 4.2.1 Build 10.6.1.14.10
I started the bootloader to get into fastboot and when it does I'm getting this message
"key driver not found...booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol"
as well as the three bootloader icons
What can I do now because typing "fastboot devices" is returning nothing and typing "fastboot continue" or "fastboot reboot" just brings up the message "< waiting for device > " but nothing happens beyond this.

vnomad said:
I'm trying to flash TWRP as a step to installing KitKat but I'm getting stuck booting into fastboot/bootloader trying to install the TWRP Recovery.
After I've installed the adb and fastboot files (15sec ADB Installer v1.3) I connect my tablet and open command in the directory folder and when I type "fastboot devices" all I get back is:
C:\adb
What am I doing wrong? I already have TWRP.blob inside the folder directory but I can't use fastboot to install it because it is not showing my device
I installed 15 seconds ADB Installer v1.3
I installed it on Win 7 64bit Lenovo G560 laptop
I unlocked the tablet myself using the Asus Unlock utility
I only have USB 2.0
I'm not sure if the tablet is in fastboot because I'm not cold starting it. I'm just connecting it to my PC and then opening a command window inside the adb files folder C:/adb
My tablet is running on Android JB 4.2.1 Build 10.6.1.14.10
I started the bootloader to get into fastboot and when it does I'm getting this message
"key driver not found...booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol"
as well as the three bootloader icons
What can I do now because typing "fastboot devices" is returning nothing and typing "fastboot continue" or "fastboot reboot" just brings up the message "< waiting for device > " but nothing happens beyond this.
Click to expand...
Click to collapse
Open Device Manager on your PC. Near the top you should find an entry for a fastboot connected device (your tablet needs to be connected via USB in fastboot mode and yes, you are there when you see the three icons). If there's a yellow triangle next to it, you do not have the correct driver.
Try the ones from this post or try the tool, it's fastboot with training wheels
http://forum.xda-developers.com/showthread.php?t=2646279
If the driver checks out ok (no yellow triangle) you may have an incompatible USB cable. Is it the original charging cable?

berndblb said:
Open Device Manager on your PC. Near the top you should find an entry for a fastboot connected device (your tablet needs to be connected via USB in fastboot mode and yes, you are there when you see the three icons). If there's a yellow triangle next to it, you do not have the correct driver.
Try the ones from this post or try the tool, it's fastboot with training wheels
http://forum.xda-developers.com/showthread.php?t=2646279
If the driver checks out ok (no yellow triangle) you may have an incompatible USB cable. Is it the original charging cable?
Click to expand...
Click to collapse
In Device Manager the ASUS is no longer showing a yellow triangle and it appears to have the right drivers installed. The problem I'm having now is that when I uninstall the drivers for the Asus TF700 in Device Manager I reconnect the device and Windows (7) automatically installs the same drivers. I have even tried "Updating the Drivers" by navigating to the folder where I have (correct) Windows Drivers provided in thread above but I receive a message that device has the most up to date drivers (paraphrasing). I have also tried to do the same thing by navigating to a folder where I have Google Universal Drivers 0.73 installed but again I cannot seem to install them.
How can I override Windows from automatically installing the other drivers or is there a system folder I could send the correct drivers to when installing.

Can't enter fastboot mode, plz help.

im trying to enter fastboot from bootloader but every time i select it, it just reloads the bootloader. everything else works fine.

the bootloader IS fastboot mode.

Well when I run fastboot protocol nothing happens

strker45 said:
Well when I run fastboot protocol nothing happens
Click to expand...
Click to collapse
Get into Bootloader. (I use ADB command: ADB Reboot Bootloader)
Use the volume down button to select "Fastboot Protocol."
It is deceptive as the screen on your Shield won't change.
Use your fastboot commands now. See if that works.

You need to make sure your fastboot and adb drivers are installed and recognized.
Also need fastboot on your pc of course. Good luck.
Once again, the bootloader is fastboot on your tablet, if you are on that screen then you can use fastboot if the above conditions are met.

Same symptom here.
When Android is loaded, Win10 finds it as both MTP and USB debugging device. adb is reporting back. All well.
However, when shield is in fastboot mode, fastboot finds nothing.
In my case reason was driver:
when connected in fastboot mode, win10 wants to install an
Android Device -Android Bootloader Interface
=> you see this in device manager
To satisfy Win10, download NVIDIA USB driver from here
https://developer.nvidia.com/shield-open-source
hence point the driver install in Win10 device manager to the driver download/extract location
Reconnect your shield.
In my case this worked.
Hope this helps

vrmuhr said:
To satisfy Win10, download NVIDIA USB driver from here
https://developer.nvidia.com/shield-open-source
hence point the driver install in Win10 device manager to the driver download/extract location
Click to expand...
Click to collapse
Thank you, worked very well for me.

Issue with upgrading TF300T from original version to KatKiss version

Hi all,
I am new in this forum, and also a newbe when it's about rooting and flashing android devices. My TF300T tablet is 3 years old and I wanted to give it a second live by upgrading from 4.2.1 to 5.1.1.
I understand form several threads that you have to make sure you follow a few steps before upgrading to 5.1.1:
1: Enable developer mode, activate USB debug and accept not verified apps. (Done!)
2: Unlock bootloader. (Done! unlock message appears when tab starts up)
3: Flash TWRP via fastboot. This fails over and over...message: "waiting for device"
I can perform the command ADB reboot bootloader via CMD, so it looks like the drivers work and the connection is there. What could I be doing wrong? Before I unlocked the bootloader, I used the "wipe data" option in the bootloader and suspect because of that I can't run recovery via the RCK in bootloader anymore. Are both issues linked to each other?
Beside the fact that I am stuck on this, I also don't know if I run a JB bootloader or not. Can somebody confirm if this is a JB version? This is my bootloader message in bootloader mode:
key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" a03
Starting Fastboot USB download protocol
*Update*
While I was still trying options and reading threads after placing this thread, I decided to also install adb/fastboot on my mac, and there I get a more specific error message when I try to flash TWRP. It's not saying "waiting for devices" but "error: cannot load 'twrp.img'"
Also when I run fastboot devices, I get the device serial back so the link is there.
Is it possible that there is a problem with the destination folder or partition?
Thanks for your help!

No need for further support, I was able to solve the issue. When I point to the specific directory where the twrp file is stored during fastboot flash recovery, it works just fine.
Strange this is not discribed in any instruction.

Cannot install USB drivers on Windows 10, device not displayed with fastboot devices

When I try to install the USB Drivers It fails with an error message.
ADB devices works, but fastboot devices doesnt.
I'm on Windows 10.

Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).

redpoint73 said:
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
Click to expand...
Click to collapse
Yes, I'm trying fastboot from the bootloader screen.
On windows 8.1 it works, I can install the needed drivers, on windows 10 I cannot. Doesn't work. I wonder why adb works but fastboot doesn't.

I had this exact issue up until today, and this what I did to get fastboot on my shield tablet:
1. Uninstall all adb usb drivers just to make sure you start from a clean slate.
2. Then go to Nvidia (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) and download their Nvidia shield tablet drivers.
3. While plugged into the computer (have the tablet set to transfer files or mtp) go to the Bootloader menu on your shield tablet and then on your computer go to device manager and update the drivers. For me the device showed up as Fastboot, right click and select update drivers from the folder that you unzipped your nvidia shield tablet drivers to. When I did this I actually got an 'This device cannot start. (Code 10)' error message but I think this is okay because when I looked at the device manager again a new listing had appeared near the top called Android Composite Device.
4. Now go through the exact same process to install the drivers that you did for the 'fastboot' device but now for the 'Android Composite Device', you should also still get the 'This device cannot start. (Code 10)'. After you've done all that reboot the Shield Tablet.
5. Once the tablet has rebooted go to command prompt with Administrator Privledges and type ADB devices and your device should show up, then type adb reboot bootloader and the tablet will reboot into the bootloader menu. I this point I did not select fastboot protocol and I'm not sure if this made a difference, but in any case in the command prompt type Fastboot devices and at least for me this finally worked.
I hope this helps.

Thank you Captain_FSU! :good:
I had the same problem. My Shield K1 was showing up on adb devices but not at fastboot devices. I was unable to update the driver. In Win 10 Device Manager my Shield was showing up at Portable Devices and it was impossible to install the driver there. So finally I am able to unlock bootloader and install TWRP.