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.
Related
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 have bootloop fire hd 8 and usb debugging off, how i can fix it?
Try:
1/ Factory reset in recovery => dont work.
2/I go recovery mode -> " apply update from ADB" ->
{
"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"
}
it not found my device because USB Debugging is off (?), so i cant sideload Firmware in https://forum.xda-developers.com/showpost.php?p=73033483&postcount=2, plz help
blackerghost said:
i have bootloop fire hd 8 and usb debugging off, how i can fix it?
Try:
1/ Factory reset in recovery => dont work.
2/I go recovery mode -> " apply update from ADB" ->
it not found my device because USB Debugging is off (?), so i cant sideload Firmware in https://forum.xda-developers.com/showpost.php?p=73033483&postcount=2, plz help
Click to expand...
Click to collapse
Enabled USB debugging is not required for sideloading in recovery mode. That would render the whole recovery functionality useless. I just checked it.
Make sure your USB port and cable are okay, maybe use another. Some hubs don't work with ADB.
Also check your drivers. Uninstall and reinstall the official or universal ADB driver. You should notice when the device is detected.
Attention: Only sideload the system version you're on or higher. Downgrading could brick your tablet.
lassemacchiato said:
Enabled USB debugging is not required for sideloading in recovery mode. That would render the whole recovery functionality useless. I just checked it.
Make sure your USB port and cable are okay, maybe use another. Some hubs don't work with ADB.
Also check your drivers. Uninstall and reinstall the official or universal ADB driver. You should notice when the device is detected.
Attention: Only sideload the system version you're on or higher. Downgrading could brick your tablet.
Click to expand...
Click to collapse
Tks u, my sideload is in process.
I change cable but it still not recognize my devices, so i update driver software and pick it from list driver.
Hello all,
after hours of searching and tries, i need some help.
I have Android 8.1 on my Asus Zenfone Max pro M1 and i have a win 10 PC
I have followed this guide --> https://forum.xda-developers.com/as...obs-to-unlock-relock-bootloader-twrp-t3894847
I have unlocked my bootloader with the apk without any problem
My phone is not recognized by adb. I have install drivers (with the phone, try to install also from the guide), when i plug my phone on USB (with USB debugging active) is recognized by Windows in the device manager (without yellow flag)
{
"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"
}
but the command "adb devices" return nothing and like "fastboot devices" when i am on fastboot mode too
I have also tried another usb cable and another PC (on win 7)
I am stuck now, don't know what to do more.. Any clue?
Did you turn on USB debugging & OEM Unlock from developer settings?
debdeep98 said:
Did you turn on USB debugging & OEM Unlock from developer settings?
Click to expand...
Click to collapse
USB debugging is enable but OEM Unlock is not present from developer settings.
Yeah my bad no OEM unlock on asus.. Did you accept that allow pc thing with security key when first connecting to adb? If yes then revoke auth and try connecting. Also reinstall the drivers both asus and adb and try different cables and keep the device in mtp mode.
debdeep98 said:
Yeah my bad no OEM unlock on asus.. Did you accept that allow pc thing with security key when first connecting to adb? If yes then revoke auth and try connecting. Also reinstall the drivers both asus and adb and try different cables and keep the device in mtp mode.
Click to expand...
Click to collapse
I have tried MTP and other mode, different cable including the original one..... Still the same.
Can't revoke auth because adb never recognized my device
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