Database Info

[Q] Problems installing TWRP on unlocked JB, wont go into fastboot

Hello everyone,
I am new to XDA but not new to the Android rooting, flashing industry. I've flashed and rooted several phones, aswell as my own phone with a custom ROM. So I figured, since mine tf700t hasnt any warranty anymore that I will install Cromi due to the lag of the original software.
In order to install Cromi you need an unlocked bootloader and TWRP installed. The unlocking of the bootloader was like stealing candy from a baby. Then i wen't on to install TWRP with this guide: http://forum.xda-developers.com/showthread.php?t=1833212
1) Install Android SDK
2) Download TWRP Recovery blob and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Rename the downloaded file to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
At step 4 I ran into some problems. No matter what I do, i can't seem to boot the device into fastboot where you will see the three icons, among them the USB icon. I watched several youtube videos and read everything i could find but still no solution. What am I doing wrong at this point? What I did noticed was that the volume up and down buttons in some videos where at a different place then mine are. I have a Tf700t, when it is in landscape the volume buttons are at the top right corner on the edge of the device, the power button is on the top left on the edge of the device. At some videos the volume button was on the left side and on the top right side. Does this maybe have anything to do with it?
Thanks for the help in advance. I feel kinda stupid to not get it into fastboot mode, this never was a problem with other devices...

What firmware are you on? That guide is not updated for newer firmwares as newer firmwares have already removed that usb icon in the bootloader screen. In order to enter fastboot mode, all you need to do is power + volume down (holding down both buttons) and you should already be inside fastboot mode, no other button needed. Otherwise, through adb, you can try "adb reboot bootloader", which should take you to fastboot mode as well.

huy_lonewolf said:
What firmware are you on? That guide is not updated for newer firmwares as newer firmwares have already removed that usb icon in the bootloader screen. In order to enter fastboot mode, all you need to do is power + volume down (holding down both buttons) and you should already be inside fastboot mode, no other button needed. Otherwise, through adb, you can try "adb reboot bootloader", which should take you to fastboot mode as well.
Click to expand...
Click to collapse
Ah this explains a lot. Now when I connect it to my PC it is recognized, but when i run a 'fastboot devices' (eveything is set properly with paths etc) my tablet isn't recognized. Should I install a different driver? As for now my PC says it has APX drivers

tf700tTRANSF said:
Ah this explains a lot. Now when I connect it to my PC it is recognized, but when i run a 'fastboot devices' (eveything is set properly with paths etc) my tablet isn't recognized. Should I install a different driver? As for now my PC says it has APX drivers
Click to expand...
Click to collapse
It most likely means that you have the wrong fastboot driver. You should follow the instructions here (http://forum.xda-developers.com/showthread.php?t=2263822) to install the correct fastboot driver from the Universal Naked Driver pack. If you install the driver correctly, the tablet should appear as "ASUS fastboot device" in Windows' Device Manager. Then fastboot commands should work. As a quick reminder, the fastboot driver is a different driver from the adb driver. Windows will only see the fastboot device when you connect your tablet to your PC while the tablet is in fastboot mode, hence a separate driver is needed.
Moreover, when you flash the recovery later, you need to remove the dock and connect your tablet directly to your PC. In my case, even though fastboot recognized my tablet, the flash recovery command failed if the dock was connected.

huy_lonewolf said:
It most likely means that you have the wrong fastboot driver. You should follow the instructions here (http://forum.xda-developers.com/showthread.php?t=2263822) to install the correct fastboot driver from the Universal Naked Driver pack. If you install the driver correctly, the tablet should appear as "ASUS fastboot device" in Windows' Device Manager. Then fastboot commands should work. As a quick reminder, the fastboot driver is a different driver from the adb driver. Windows will only see the fastboot device when you connect your tablet to your PC while the tablet is in fastboot mode, hence a separate driver is needed.
Moreover, when you flash the recovery later, you need to remove the dock and connect your tablet directly to your PC. In my case, even though fastboot recognized my tablet, the flash recovery command failed if the dock was connected.
Click to expand...
Click to collapse
I tried many drivers from the universal naked driver pack. But still, wen i type in 'fastboot devices' nothing happens, and with getvar i only get 'waiting for device'.....I really dont get it, what am I not seeing her....
But then again I cant seem to get "ASUS fastboot device" in windows device manager. Only Asus fastboot interface and some others with ADB etc. Am I looking at the wrong drivers?

tf700tTRANSF said:
I tried many drivers from the universal naked driver pack. But still, wen i type in 'fastboot devices' nothing happens, and with getvar i only get 'waiting for device'.....I really dont get it, what am I not seeing her....
But then again I cant seem to get "ASUS fastboot device" in windows device manager. Only Asus fastboot interface and some others with ADB etc. Am I looking at the wrong drivers?
Click to expand...
Click to collapse
Let me try to recall the exact steps that I did to get the driver installed. I am using Windows 8.1, so the first step for me was to boot into troubleshooting mode of Windows to disable driver verification, but you won't have to do that if you use windows 7 or earlier. After that, open Device Manager, right click on ASUS bootloader interface (or a different name with the yellow question mark, but I remember when I first connected my tablet to my PC, the name was "ASUS bootloader interface"), choose Update Driver Software, then choose "Browse my computer for driver software", and click on "Let me pick from a list of device drivers on my computer". At the next screen choose "Have Disk", browse to the Universal Naked Driver folder and select the file "android_apxusb.inf". From the list you should be able to find "ASUS Fastboot Interface" and install it.

huy_lonewolf said:
Let me try to recall the exact steps that I did to get the driver installed. I am using Windows 8.1, so the first step for me was to boot into troubleshooting mode of Windows to disable driver verification, but you won't have to do that if you use windows 7 or earlier. After that, open Device Manager, right click on ASUS bootloader interface (or a different name with the yellow question mark, but I remember when I first connected my tablet to my PC, the name was "ASUS bootloader interface"), choose Update Driver Software, then choose "Browse my computer for driver software", and click on "Let me pick from a list of device drivers on my computer". At the next screen choose "Have Disk", browse to the Universal Naked Driver folder and select the file "android_apxusb.inf". From the list you should be able to find "ASUS Fastboot Interface" and install it.
Click to expand...
Click to collapse
I really dont get it....It just wont work. Fastboot still wont recognize my tablet.
If i get my hands on another Windows PC I will make a second attempt.
If someone knows a different solution, please tell me. Fastboot on the pc is properly installed for whats it worth....

Try Goo manager Open Recovery Script
I am not sure if this will help you because I am also new to this but I unlocked and rooted my tf201 prime using the steps you did. I rooted my Tf700T a few days ago and my unlocked didnt work until yesterday using unlocker 8 from the Asus site but I still could not make changes to my recovery with Clockwork Mod or TWRP until I used Goo manager and ran the Open recovery script. It worked on my TF700T with build number JOP40D.US_epad-10.6.1.14.8-20130514 which has Android 4.2.1. Give it a try it is easy.
Peace. I hope this helps
tf700tTRANSF said:
Hello everyone,
I am new to XDA but not new to the Android rooting, flashing industry. I've flashed and rooted several phones, aswell as my own phone with a custom ROM. So I figured, since mine tf700t hasnt any warranty anymore that I will install Cromi due to the lag of the original software.
In order to install Cromi you need an unlocked bootloader and TWRP installed. The unlocking of the bootloader was like stealing candy from a baby. Then i wen't on to install TWRP with this guide: http://forum.xda-developers.com/showthread.php?t=1833212
1) Install Android SDK
2) Download TWRP Recovery blob and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Rename the downloaded file to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
At step 4 I ran into some problems. No matter what I do, i can't seem to boot the device into fastboot where you will see the three icons, among them the USB icon. I watched several youtube videos and read everything i could find but still no solution. What am I doing wrong at this point? What I did noticed was that the volume up and down buttons in some videos where at a different place then mine are. I have a Tf700t, when it is in landscape the volume buttons are at the top right corner on the edge of the device, the power button is on the top left on the edge of the device. At some videos the volume button was on the left side and on the top right side. Does this maybe have anything to do with it?
Thanks for the help in advance. I feel kinda stupid to not get it into fastboot mode, this never was a problem with other devices...
Click to expand...
Click to collapse

mustafa_droid said:
I am not sure if this will help you because I am also new to this but I unlocked and rooted my tf201 prime using the steps you did. I rooted my Tf700T a few days ago and my unlocked didnt work until yesterday using unlocker 8 from the Asus site but I still could not make changes to my recovery with Clockwork Mod or TWRP until I used Goo manager and ran the Open recovery script. It worked on my TF700T with build number JOP40D.US_epad-10.6.1.14.8-20130514 which has Android 4.2.1. Give it a try it is easy.
Peace. I hope this helps
Click to expand...
Click to collapse
Oh! GooManager works again? Which TWRP version did it flash when you ran the Open Recovery script?

TWRP
berndblb said:
Oh! GooManager works again? Which TWRP version did it flash when you ran the Open Recovery script?
Click to expand...
Click to collapse
I had to flash it with openrecovery-twrp-2.6.3.2-tf700t.blob. using the platform-tools because I could not use the one with Open Recovery script by that time I wiped the entire device! It could have been my fat fingers but I just installed CM 11-20131221 (Kit Kat 4.4.2) on my tablet today without any issues. I have not done much with it yet but I will let you know later.

[Q] Unable to access fastbbot <Device Not Found>

Hi,
I am trying to restore my TF300T to stock ROM and when accessing fastboot I get the <device not found message>
I have ADB/FASTBOOT installed on my laptop (running Win7 64bit)
My tablet details are below:
Device = Unlocked
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "TW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
I have the RCK / Android and Wipe Data icons but no USB icon (I believe this is correct as I am automatically in fastboot mode, based upon the information above)
I have read a lot of posts but an unable to resolve this matter. Any help is greatly appreciated.
Thanks in advance.

Hi!
That is correct. The "starting fastboot USB download protocol" tells you that you are in fastboot mode. Now comes the tricky part: Finding a fastboot package that works with your computer and your Transformer. F.e. I have three different ADB/Fastboot installations and only one works. I've installed this one here: http://forum.xda-developers.com/showthread.php?t=2588979
Note: The programm installs itself into C:\adb\ so you have to copy your recovery there...
You have to check first if your Transformer is connected. If "fastboot devices" is retuning a serial number than it's all fine... :good:

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.

Phone Wont Start

Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!

J0hncramer said:
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
Click to expand...
Click to collapse
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).

LokifiedMee said:
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
Click to expand...
Click to collapse
I just tried fastboot devices in powershell while the phone is connected via USB in fastboot mode and nothing was listed
Edit: i was able to get fastboot to work, I had to do the following steps i found on stack exchange to get my device to show up properly in device manager:
https://stackoverflow.com/questions/8588595/android-fastboot-devices-not-returning-device
Open device manager
Find Unknown "Android" device (likely listed under Other devices with an exclamation mark)
Update driver
Browse my computer for driver software
Let me pick from a list of devices, select List All Devices
Under "Android device" or "Google Inc", you will find "Android Bootloader Interface"
Choose "Android Bootloader Interface"
Click "yes" when it says that driver might not be compatible
Click to expand...
Click to collapse
With fastboot working and issues in device manager solved I was able to get TWRP loaded to my phone via fastboot and change my boot slot to get back into the phone

Installing GrapheneOS onto Google Pixel 3 - Fastboot Unlock <waiting for device>

Hi guys,
Looking for a genuis here...I've spent the last few days trying to work this puzzle out:
Installing GrapheneOS onto Pixel 3 phone using Windows 10, using command line tools only. Android Studio is not installed on the PC.
Here's what I've done so far...downloaded:
The Pixel image - GrapheneOS stable channel for Pixel 3
ADB & fastboot
First we downloaded fastboot (ADB, Android SDK platform-tools for Windows): https://developer.android.com/studio/releases/platform-tools - had an issue with the fastboot flashing unlock command...it doesnt unlock the device, instead says <waiting for any device>
Then we deleted the SDK platform tool and installed Minimal ADB & Fastboot and the same darn issue happened - the fastboot flashing unlock command doesnt unlock the device... command prompt says <waiting for any device>
The device is carrier unlocked, OEM unlocking enabled, USB debugging enabled, File transfer (MTP) mode on.
The following commands work with the SDK platform-tools & minimal ADB & Fastboot: adb devices, adb reboot bootloader
The block is the command: fastboot flashing unlock as we keep getting <waiting for device>.
Tried to fix this myself, here's what has been tried so far (not necessarily in this order):
Checked Fastboot version... fastboot --version works for both downloads so it's recognising it! Wahoo.
Used command prompt & powershell - when it gets to the fastboot flashing unlock command the response is always <waiting for device>
Checked the PATH (in control panel / advanced setting) and made sure environmental variable goes to the right folder
Downloaded Google USB Driver - nothing changed, we already had up-to-date drivers
Tried to change the fastboot script, click to open the fastboot file, when I click "open" the command prompt pops up, red error message flashes then the command prompt window closes in the blink of an eye. I then turned off Windows secuirty setting for app, same thing still happens.
Tried all USB ports with USB-C cable - same error <waiting for device>
Tried all USB ports with anotehr USB-C cable - same error <waiting for device>
Please help!

The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.

jwoegerbauer said:
The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.
Click to expand...
Click to collapse
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!

Redsquirrel77 said:
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!
Click to expand...
Click to collapse
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com

jwoegerbauer said:
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com
Click to expand...
Click to collapse
Thanks so much, I think we are getting closer to success!
Qualcomm USB driver downloaded and successfully installed.
Update since the Qualcomm USB driver download:
adb reboot bootloader command works - phone goes into fastboot mode
fastboot devices - no response (new command line)
fastboot - -version shows version and installation
fastboot flashing unlock response is still <waiting for any device>
Used command adb shell getprop ro.boot.cid and response is 00000000
Response should be 11111111 if it's a Google phone...is this my issue? Or does it help explain why fastboot isn't working?

Fastboot operates on device's bootloader only if unlocking bootloader isn't denied. Makes sense,, doesn't it?
Me and all my friends always test this by running
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported" <- on some devices: adb shell "getprop sys.oem_unlock_allowed"
If returned value is 1 - or true, then it's supported otherwise it's not.

Hi,
I don't know if it will help but try this.
PROBLEM
I tried all manner of ADB drivers and fastboot drivers for the last 4 hours just so that I am able to oem unlock this OnePlus device.
I have all OnePlus drivers installed. I have the ADB drivers installed from here. With all these I was able to run adb commands on the phone when it was on including commanding the phone to enter into EDL mode, commanding the phone to reboot into bootloader (fastboot mode). However in once in Fastboot mode, I could not communicate with phone and all I got was "waiting for device".
SOLUTION THAT WORKED FOR ME
It could be a computer brand model. Turns out the problem was not Windows. The problem was not Oneplus. The problem was my Lenovo Thinkpad which apparently requires its own Lenovo USB drivers.
If at all you're on Lenovo machine and you're stuck on "waiting for device" in Fastboot mode despite trying everything, then try installing Lenovo USB Drivers. I would recommend installing the generic ADB drivers first from here. Then installing the Lenovo drivers that are specific to you machine from here. Mine is Thinkpad.
I really hope this helps if not you, then someone else just about to pull their hair out.