BackgroundWhen I got my OnePlus 8T (after using Samsung devices and a OnePlus 3T for many years) I could access the phone using adb and, when the phone was in Bootloader mode, using fastboot. But I couldn't access the phone in Fastbootd mode.
I tried lots of different things but none of them worked for me and, worst of all, many of the solutions required downloading files from untrusted sources.
I finally decided to see if the Google USB driver would help and, to my surprise, it fixed the fastbootd problem. So I uninstalled the drivers that were being used for Bootloader mode, the Google driver used for Fastbootd mode,
{
"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"
}
and then did a clean install of the Google USB driver so that I could document the process.
InstallationWithout a suitable driver when connected in Bootloader (or Fastbootd mode), my phone shows up under "Other devices" as "Android" with a yellow warning triangle:
I downloaded the Google Windows USB driver from https://developer.android.com/studio/run/win-usb, extracted the contents, and installed the driver by right-clicking on usb_driver/android_winusb.inf and selecting Install:
Next, I booted my phone into Bootloader mode (Note: if Bootloader mode works for you and you didn't want to uninstall the driver, then boot into Fastbootd), found my phone in Device Manager (Other devices), double-clicked it (Android) to pull up the driver details and clicked the Update Driver... button. On the next screen select the second option "Browse my computer for drivers":
And on the next screen I selected "Let me pick from a list of available drivers":
I chose "Androd Device" and clicked on Next:
This brings up the following screen:
(Note: I also have Samsung drivers installed). I clicked on "Google, Inc." under Manufacturer, then "Android Bootloader Interface" from Model and clicked on Next.
I got a warning, to which I replied "Yes":
and the installation completed successfully:
Notice that the phone now shows up as "Android Bootloader Interface" under "Android Device" in Device Manager. Double clicking on it now shows the driver is installed:
And that's it!
I now find that I can also boot into Fastbootd mode, even though I only installed the driver for Bootloader mode.
Note: this driver also works for my OnePlus 3T
Related
So for the first time I've set up my ADB since I will getting a MT3G tomorrow. Environment variables (PATH) set correctly, etc.
When I type adb shell in recovery model, it says *daemon not running. starting it now, daemon started successfully, error: device not found*
"Android Compsite ADB Interface" shows up in my USB devices. So what's the problem.
Then when I load up "emulator -data c:\", it starts up and gives me this error. msvcrt.dll? I've dealt with that .dll file before for other apps and it is in my system32 folder.
So what's going on here.
{
"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"
}
try reinstalling the usb driver.
mine identifies as HTC Dream Composite ADB Interface.
did you install the usb driver that comes in the SDK?
what if you navigate to the location you have the sdk installed? does it work then? maybe the path is not set up as correct as you think? (i had this problem when trying to do fastboot. everything else worked fine except for fastboot. to get that working i had to navigate to the sdk directory.)
I sure did, and it reads exactly that.
Even adb devices doesn't bring a device up. Or adb remount.
Other thing is under Hard Drives Tree, the HTC Android USB Phone Device has a Microsoft driver. I tried to install drivers from the android/usb_driver/ and nothing. Do I have to do this in the Home Screen for the first time so it brings up the permission screen where I click on "Allow Always" for root? Cause I'm not getting that there, so I rebooted into recovery....nothing there as well.
i did have an issue recently where i couldn't get the usb driver to change over.
what i had to do to get it to change was disable and then re-enable usb debugging while the phone was connected to the computer.
it triggers a hardware change in windows and this allowed me to reinstall the correct driver.
uninstalling the current drivers might also help.
I've tried both things.
Same issue.
What Windows Services need to be enabled in order to get ADB to work? I did some tweaking of the services.msc for XP. I think that might be the reason adb shell isn't working.
Same problem I have:
I have TWO rooted G1s, Cyanogen 4.0.4 modified devices with identical Software releases.
The one (rooted by the Golcard Method) is recognized by ADB - the other one (rooted by the One Click Method) is not.
Troubled !
Oh Sorry -this is a Sapphire forum ... I apologize
i tried to flash drivers i get this errer
{
"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"
}
i was on android l v12 , my device is note 3g
i tried to flash new offical miui6 via twrp 2.8 i got error
and wiped data,system etc...
so i am not able to enter recovery and even into rom what to do??
Please Help ME
It seems a problem with Windows rather than with your phone.
First of all don't worry, there are very high chances that you will recover the phone in working state. I worked for over a year with MTK devices, they brick very easily but it's also easy to unbrick.
It's a signature error, not a driver error. I remember Windows has somewhere the option to disable signature checking for drivers. Disable it, then after installing this driver you can re-enable it if you want.
I assume you are able to proceed from this step on, once phone is recognized by PC. If I'm wrong, feel free to ask
To Install Driver without Signature error.
This will Help u to install driver without signature.
What to do:
1. Hold down the Windows key on your keyboard and press the letter C to open the Charm menu, then click the gear icon (Settings).
2.Click More PC Settings.
3. Click General.
4. Under Advanced Startup, click Restart Now.
NOTE: In Windows 8.1, the ‘Restart Now’ button has moved to ‘PC Setting -> Update & Recovery -> Recovery.’
5. After restarting, click Troubleshoot.
6. Click Advanced Options.
7. Click Windows Startup Settings.
8. Click Restart.
9. After restarting your computer a second time, choose Disable driver signature enforcement from the list by typing the number 7 on your keyboard.
10. After restarting, you will be able to install the drivers normally; however, Windows will display a warning message. When the warning appears, click Install this driver software anyway.
You are now complete. I hope this will help you. Good Luck..
Tutorial: How to transfer files to/from our Moto G while in TWRP recovery
This tutorial have been tested in 7, 8, 8.1 and 10 Windows versions. It can work with other devices beside Moto G.
{
"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"
}
Sometimes we need to transfer files to our device while we are in recovery mode. When we forget to copy the zip we were going to flash, when we are installing a
GPE based ROM (we must format /data and erase all files), to transfer a backup... ect. In many cases we need this function.
The purpose of this tutorial is to make our PC succesfully recognize our Moto G as a storage device being in TWRP recovery.
Many users have reported that their devices are not being recognized.
Requirements:
-Have installe the last TWRP recovery version.
-Have installed ADB drivers in PC. You can try this ones Universal ADB Drivers or Motorola Mobile Drivers 64 bits
-USB data cable.
-PC runnig Windows 7, 8, 8.1 or 10 (can work with older versions).Steps: Sorry for spanish images, if you can provide me english captures would be great.
1) Boot into recovery mode and connect to PC with USB data cable.
2) Being completely sure your device is not being recognized, otherwise this tutorial will be totally useless to you.
3) Open Control Panel and click on Hardware and Sound
4) Go to Device Manager.
5) Look for 'Android Device' or 'Android Phone' or any related name, open the list, rigth-click on the device and click on 'Update driver software'.
6) Now click on the second option.
7) Now click on the option below:
8) Make sure 'ADB composite device' is there and click next.
9) Once this is donde, reboot your PC and it will be in capacity to recognize your device as a storage device while you are in TWRP recovery. We can freely transfer files.---------------------------------------------------
Last Update: 17-07-2015
Reserved
Thanks
I had to reinstall Win 10 on my computer and now I'm not able to connect to my 6T in order to root it.
The boot locker is unlocked, I can see it at phone boot. It was unlocked also before last update to OxygenOS 10.3.7.
Debug USB in enabled. When I connect to the phone to the computer it is deceted and I can transfer files.
Whit ADB devices phone is deteted (picture is from all in one tool, using command prompt same result)
{
"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"
}
using fastboot devices the phone is not detected.
installed last official usb drivers (google and oneplus)
Any idea, suggestion or further test that can help?
Thanks
Same problem here. Please help.
Finally I found a working solution.
If you have a laptop you have to disable secure boot.
Then you have to disable signature verification on windows 10 ( How to Enable or Disable Driver Signature Enforcement in Windows 10 | Tutorials (tenforums.com) ).
I used option 3.
Download Oneplus usb drivers ( Download Latest OnePlus USB Drivers for Windows and Mac (getdroidtips.com) ).
Then connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device. If it is found, this means windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Thanks man, it worked for me.
Just to complete, after istalling the drivers you can restore signature verification and secure boot on Win 10.
Everything will work fine.
Hello everybody.
I wanted to unlock an BTV-DL09 [ Android 7 EMUI 5.04 EU ], but I'm stuck like the_wing was.
Modem no found !
Phew, got it unlocked! Moments of terror when entering the commands on the cmd...
A few mentions where I got stuck that may help someone else:
Regarding point 3:
In case your model has LTE (i.e. BTV-DL09), you actually should have a dialer application that you have to use instead of the calculator app, which didn't work for me. This is also mentioned in the DC unlocker app. In case you do it with the dialer, you have to enter following code: *#*#2846579#*#*
Regarding point 4:
Inside the "DC unlocker" app, I also got the "device not found" error, and I was wondering why. Two things I noticed:
- To enable USB debugging, it was not sufficient for me to activate the switch in the developer options, as the default USB mode for me is "charging only". I had to change it to i.e. "Device File Manager (MTP)" by tapping on the notification and then re-activate USB debugging in the developer options (which turned off after switching to MTP mode) to get USB debugging working.
- After enabling "manufacturer mode", the mode was turned off as soon as I quit the menu. So I had to stay in the menu to make sure manufacturer mode is on.
- You can check your device manager in Windows to see if the current mode is active: When doing USB debugging, the device "Android Composite ADB Interface" should show up under "Android Phone" list, whereas when you turn on manufacturer mode, some COM ports should show up under "Ports (COM and LPT)"; the one DC unlocker is searching should be named "Android Adapter PCUI". If you got some devices with not properly installed drivers you should consider installing HiSuite software on Windows first.
Regarding point 8
- When I bought the credits for DC unlocker for PayPal, I had to click on a link arrived to the PayPal e-mail for confirming your account. I then still got the "Server login error", but closing and reopening DC unlocker eventually fixed it.
Hope this helps! Happy unlocking to everybody!
Click to expand...
Click to collapse
I have installed Hisuite and Huawei data card driver.
Impossible to activate Device File Manager (MTP) and manufacturer mode, one deactivates the other, I do not know if this is the problem, but according to the tutorials it is a must.
I have a hard time understanding where the problem comes from, I even tested different USB cable, Win 7 and Win 10, I really did everything, but I'm dried.
{
"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"
}
I finally managed to unlock the bootloader, DC unlocker did not show me information from the tablet, but despite this, I could go to the next step and proceed with the unlocking, it is because of a msie security update according to Valdemaras on cd-unlocker forum, thanks to him.