I'm trying to unlock the bootloader of my OnePlus 6 so I can root but my laptop can't recognise my OnePlus in cmd prompt. I tried uninstalling and reinstalling the drivers and even a rooting tool that I got from XDA and nothing is working, can someone help me? (I'm fairly new to rooting)
Did you enable usb debugging?
tdm123 said:
I'm trying to unlock the bootloader of my OnePlus 6 so I can root but my laptop can't recognise my OnePlus in cmd prompt. I tried uninstalling and reinstalling the drivers and even a rooting tool that I got from XDA and nothing is working, can someone help me? (I'm fairly new to rooting)
Click to expand...
Click to collapse
See if you can find your device in Device Manager. If it has an yellow triangle on it you need to install adb drivers for it.
Change USB port - It helped in my case.
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka
Mee too. Im unable to recognise the oneplus thorw the fastboot mode... if i try to type fastboot devices nothing appened...Can someone help us? Thanks
Did you both checked "allow USB debugging" under developer options and actually allowed it after connecting to USB port, it it didn't appear on your phone?
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka
As mentioned, make sure you've enabled Developer Options, then through there, enable OEM unlocking and USB debugging. Is the phone booted into fastboot mode (bootloader) when you're trying to find it via the command line? If you're booted into the system, fastboot won't work. Only adb will.
Another thing that might help is to use a Mac if you have access to one. There's no need for drivers, so that problem is eliminated. Connect via USB and the command line should work. (This is not a PC vs. Mac thing; it's just a practical matter.)
Solution
I had the same issue and the solution for me was to reinstall oneplus drivers the updated ones from the oneplus drive that appears when you connect the device.
As far as I remember, you can check devices with ADB devices not fastboot devices.
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka
TheFaithfulOne said:
As far as I remember, you can check devices with ADB devices not fastboot devices.
Click to expand...
Click to collapse
You can check with both adb and fastboot with the devices argument.
Code:
adb devices
fastboot devices
Same here
But my laptop can reconize my phone on fastboot mode
What OS? If it's Windows 10 N version, then you will need to download the Windows Media Feature Pack.
-Download latest OP6 drivers
-Enable Developer Options
-Enable USB debugging in developer options
When the phone is booted, you can use ADB devices commands, however, when in the bootloader, you'll probably have to use Fastboot devices.
On my phone, ADB devices never works at the bootloader, only outside of the bootloader.
I had an issue where every time I wanted to connect to fastboot, I had to turn off USB debugging, plug into my computer, wait for it to recognize, unplug, enable USB debugging, and reconnect to PC. Might be worth a shot to see if it's the same issue.
cazcryy said:
I had an issue where every time I wanted to connect to fastboot, I had to turn off USB debugging, plug into my computer, wait for it to recognize, unplug, enable USB debugging, and reconnect to PC. Might be worth a shot to see if it's the same issue.
Click to expand...
Click to collapse
Doing this and enabling test mode on W10 LTSB before reinstalling the official OnePlus drivers worked on my OP5T (OOS 9.0.5). I had the same issue the OP described.
What can I do if the phone is locked and is in bootloop? I can't go and do the oem unlock and allow unlocking options in settings as phone is already in bootloop.
Related
I'm wondering if anyone has run into this problem before?
I'm trying to unlock the bootloader on my friend's Photon Q, I downloaded the SDK and installed the Motorola drivers. But when I put his phone into Fastboot mode, the "fastboot oem get_unlock_data" command does not work and CMD just says waiting for devices.
Yes I'm shift+right clicking on the platform-tools folder in the SDK to run the Command Prompt and I did download the correct Fastboot file. The command "adb devices" shows nothing when his phone is plugged in, but it shows my own phone (A Motorola Droid Bionic) when it's plugged into the USB cable. RSD Lite also recognizes both phones when powered on or in Fastboot mode.
I have no idea what to do at this point, we just need to get that unlock data to plug into the Moto site. Would it be possible to use someone else's unlock key or is each one randomized individually for the device? Or would that even work because my computer can't do the command for the unlock data, so maybe it couldn't push the unlock key onto the phone?
quick thought: did you enable usb debugging on the device?
edit: i guess that wouldn't make any difference in fastboot mode...
anyway, yeah, i'm pretty sure each device has it's own unique code. it's odd that fastboot recognizes the device, but the command isn't working. i bet you will get it somehow tho. a similar thing actually does happen to me sometimes, and in my case, it is because my usb ports are going bad and the computer loses connection with the phone.
Man nobody has anything eh? That's a crying shame. I tried using a different computer and went through the same course and still nothing.
I did try USB debugging on and off on both machines, didn't change a thing.
In order for the drivers (and therefore adb) to pick up the phone, I needed usb debugging *and* the phone not to be in charge only mode. Maybe that will help?
If not, when you reboot to fastboot and connect the cable, look at the devices installing list (if win 7) or device manager, and confirm the pc sees the fastboot device. If not you may need to reinstall the driver. Strange I know, but I needed to after getting my unlock data, holding off on unlocking due to the warranty voiding note, then trying again a couple days later where it wouldn't recognize. Seems to be finicky drivers to match a finicky device. But I do love this keyboard lol...
Sent from my XT897 using Tapatalk 2
We've only ever tried it in MTP mode and USB debugging enabled. This is day three of plugging it in and pulling it out and still no go. This is a royal pain, that is for sure.
Download Motorola Device Manager from the website, install, plug in phone. Place the phone into mass storage mode WITHOUT debugging enabled, then other modes, then back into bootloader mode then into fastboot mode. This will install EVERY driver, I didn't see that as one of the things tried.
Once you are in those modes, Android ADB device driver will install.
Hope that helps...
Sent from my XT897 using xda premium
Hi! I'm trying to manually update my phone to Nougat by flashing a 6.0 firmware but I'm not successful. All I get is a blinking green light and that's it. I've tried uninstalling/reinstalling the flash drivers, doing software repair via Xperia Companion, checking that USB debugging is enabled, but still nothing. I was wondering if anybody here has had the same experience as me.
Check the USB driver
Wysłane z mojego F8331 przy użyciu Tapatalka
Use a different USB port. If you're using a front port, try a back one. Even better, use a USB 3 port. I had the same with my front USB 2 ports, worked fine on one of the 3's.
Sent from my F8331 using Tapatalk
try disabling driver signature enforcement on windows startup page, win10 and win7 have different ways to disable this, look over google and try that it might help:fingers-crossed:
okay, i did another software repair via companion and that did it. finally on android nougat. thanks to everyone who responded!
Sent from my F8331 using XDA-Developers mobile app
adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
grimlust said:
adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/oneplus-8t/how-to/guide-fastbootd-to-recognized-computers-t4192449
---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------
You can also try installing the oneplus drivers in the oneplus drive that pops up when you plug in your phone
Edit: Scratch that. I guess the 8T doesn't come with a driver partition. Try this https://oneplususbdrivers.com/oneplus-8t-usb-driver-download/
Install Universal ADB Drivers first and then boot Oneplus 8T to fastboot mode, repair oneplus device driver to "ClockworkMod Android ADB Interface" on Windows, you can use fastboot command for unlock bootloader now.
Universal ADB Drivers https://adb.clockworkmod.com/
I had the worst bloody time getting fastboot drivers installed for my 8T (KB2007, T-Mo).
I ended up having to find the device id for my device and manually patch and resign Google's USB drivers to get it working. If you can handle reading batch files and stuff, clone the repositories at https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows and https://github.com/fawazahmed0/windows-unsigned-driver-installer.
grimlust said:
adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
Click to expand...
Click to collapse
Hi Grimlust i am in this exact scenario is it your device problem solved. If it has done can you walk me through the steps you went through to get that result. Please its my last chance to revive my one plus 8T
savio97 said:
Hi Grimlust i am in this exact scenario is it your device problem solved. If it has done can you walk me through the steps you went through to get that result. Please its my last chance to revive my one plus 8T
Click to expand...
Click to collapse
don't know if you still need it but today i was as desperate as you were and this helped me
How to Install Google's Android Bootloader Interface Drivers
In this comprehensive guide, we will show you how to download and install the Google's Android Bootloader Interface Drivers on your PC.
www.droidwin.com
I am trying to unlock Redmi note 6 pro but facing issue in fastboot. whenever I try 'fastboot devices' command, on 1st query it shows ID but on 2nd time query it shows '????????". when this happen, on phone screen messege appears as " press any key to shutdowd". pls check the attached image and tell me the solution. Have tried uninstall/reinstall driver, updated phone through phone's updater but nothing helps. phone always kicks out from fastboot mode. due to this problem mi unlock tool never detect my phone.
@Narrry84
Change USB port, change USB cable, install Android USB Driver matching your needs if not already done yet
jwoegerbauer said:
@Narrry84
Change USB port, change USB cable, install Android USB Driver matching your needs if not already done yet
Click to expand...
Click to collapse
Have done already these steps. will try changing PC tomorrow..
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Add Samsung A9 2018 SM-A920F to this thread's title thus mainly owners of such device get addressed.
Lucvdkant said:
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Click to expand...
Click to collapse
What does
Code:
adb devices
return?
jwoegerbauer said:
What does
Code:
adb devices
return?
Click to expand...
Click to collapse
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Lucvdkant said:
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Click to expand...
Click to collapse
You have to switch phone's USB mode to ADB.
jwoegerbauer said:
You have to switch phone's USB mode to ADB.
Click to expand...
Click to collapse
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Lucvdkant said:
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Click to expand...
Click to collapse
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
jwoegerbauer said:
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
Click to expand...
Click to collapse
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Lucvdkant said:
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Click to expand...
Click to collapse
Enabling OEM Unlock and/or USB Debugging simply sets an allowance flag, nothing else. It doesn't configure phone's USB mode.
I tried it on the laptop from work and there the phone is recognized in adb. But sadly I don't have administrator rights on that laptop to open Smalipatcher. Is there an alternative or work around available?