So I've been messing with android devices for years now and have never ran into this issue. I'm looking to root my new Oneplus 6t, but can't seem to get ADB to recognize the devices. Here are the details....
-Mac OSX Mojave
-USB Debugging on in Dev options
-Tried Clearing the USB authorizations
-Using stock Oneplus cable, but have tried multiple others
-My old Galaxy s8 connects with no issues.
In PTP mode the device will not prompt to authorize the PC, but if I switch to MIDI or USB Tethering it comes up almost instantly. I've updated my android SDK and installed the newest version of Android Studio.
Also, I'm able to access the device via Fastboot and was able to unlock the boot loader, but I'm stuck from here.
Any ideas?
I'm in the same exact boat. Computer recognizes it when it's booted, but once I'm in the bootloader I get nothing but fastboot. I'm using Windows 10
Sent from my ONEPLUS A6013 using Tapatalk
mentalcase said:
So I've been messing with android devices for years now and have never ran into this issue. I'm looking to root my new Oneplus 6t, but can't seem to get ADB to recognize the devices. Here are the details....
-Mac OSX Mojave
-USB Debugging on in Dev options
-Tried Clearing the USB authorizations
-Using stock Oneplus cable, but have tried multiple others
-My old Galaxy s8 connects with no issues.
In PTP mode the device will not prompt to authorize the PC, but if I switch to MIDI or USB Tethering it comes up almost instantly. I've updated my android SDK and installed the newest version of Android Studio.
Also, I'm able to access the device via Fastboot and was able to unlock the boot loader, but I'm stuck from here.
Any ideas?
Click to expand...
Click to collapse
You didn't mention anything about drivers. are the oneplus ADB drivers installed? (I am not sure how things work on mac though)
mentalcase said:
So I've been messing with android devices for years now and have never ran into this issue. I'm looking to root my new Oneplus 6t, but can't seem to get ADB to recognize the devices. Here are the details....
-Mac OSX Mojave
-USB Debugging on in Dev options
-Tried Clearing the USB authorizations
-Using stock Oneplus cable, but have tried multiple others
-My old Galaxy s8 connects with no issues.
In PTP mode the device will not prompt to authorize the PC, but if I switch to MIDI or USB Tethering it comes up almost instantly. I've updated my android SDK and installed the newest version of Android Studio.
Also, I'm able to access the device via Fastboot and was able to unlock the boot loader, but I'm stuck from here.
Any ideas?
Click to expand...
Click to collapse
Did you get.your device from OnePlus or from T-Mobile?
crzycrkr said:
I'm in the same exact boat. Computer recognizes it when it's booted, but once I'm in the bootloader I get nothing but fastboot. I'm using Windows 10
Click to expand...
Click to collapse
When you're on bootloader only fastboot works. That's working as intended.
I was wondering about that. I've been on Samsung phones the last few years so I'm pretty rusty with these things. But all the guides say to check fastboot and adb before flashing the temp twrp. Didn't want to do it if something was wrong
devilrulz4ever said:
When you're on bootloader only fastboot works. That's working as intended.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6013 using Tapatalk
devilrulz4ever said:
When you're on bootloader only fastboot works. That's working as intended.
Click to expand...
Click to collapse
Not quite as I'm attempting to use adb as the phone is in the os not the bootloader.
Also, this was purchased directly from OnePlus.
mentalcase said:
Not quite as I'm attempting to use adb as the phone is in the os not the bootloader.
Also, this was purchased directly from OnePlus.
Click to expand...
Click to collapse
What about the Oneplus ADB drivers? Do you have them installed?
devilrulz4ever said:
What about the Oneplus ADB drivers? Do you have them installed?
Click to expand...
Click to collapse
Drivers aren't required for Mac os.
You probably need a newer adb version. Get the latest mac platform-tools here: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
Related
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
asylumxl said:
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
Click to expand...
Click to collapse
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Gizmoe said:
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Click to expand...
Click to collapse
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
asylumxl said:
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
Click to expand...
Click to collapse
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Gizmoe said:
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Click to expand...
Click to collapse
I'll give that a go, that's the only thing I haven't tried so far. It's just bizarre it shows in every other mode. The device is there in the Device Manager under hidden, but doesn't actually show up as connected. Thanks .
ADB detects my 6P but cannot detect any devices after restarting into the bootloader menu. When this kind of thing used to happen before I just removed and replaced the USB connection to fix. No more.
Mac is seeing "Nexus 6P" in System Report under USB when 6P is booted and "Android" when 6P is in bootloader menu. I am using Google Platform-Tools. I also tried with another super-clean Mac (both are running Sierra) and got same result.
Trying to flash to Oreo OPR 17 from stock 7.1.2. Device is unlocked. USB debugging is enabled. Just says "Connect USB Data Cable" in bootloader screen. I have never had trouble doing this before. Please help. It's driving me nuts.
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
wizardwiz said:
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
Click to expand...
Click to collapse
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Calico007 said:
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Click to expand...
Click to collapse
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you! I knew I was doing something stupid. Much appreciated.
After moving to Lineage 14 from stock 21s, I came to realize Android Pay will not work if the bootloader is unlocked.
So I went to go and lock the bootloader (with TWRP and Lineage still installed) and for some reason when I do a "adb devices" the phone is not seen.
I uninstalled the driver, reinstalled.
Tried unplugging, launching ADB, then plugging in..
Plugging in then launching ADB...
Then i put ADB on my wife's laptop (A PC I have never plugged the leeco pro 3 on to), then plugged in for the first time already in fast boot. Still no dice.
Anyone have any ideas?
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
ekeefe41 said:
That is what I am doing, but I am still concerned about the ADB not seeing the phone in fastboot mode. If I have some type of catastrophic issue where i need to restore from fastboot i will be screwed.
Click to expand...
Click to collapse
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
kaneorotar said:
How about using Magisk to bypass SafetyNet check instead of locking your bootloader?
Click to expand...
Click to collapse
kaneorotar said:
If you boot into fastboot mode (Volume Up + Power), does the phone show up in 'fastboot devices'?
If so, then IMHO you should be fine in catastrophic situation.
Click to expand...
Click to collapse
No, that is the issue, lol
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
sk8223 said:
Do you have adb drivers, and did you try completely deleting your device drivers from Device Manager, then reinstalling them by plugging your phone in via USB Debugging? Are you using the platform-tools package? Did you connect via USB Debugging, and did you authorize the computer (the message should pop up on your phone)? I can't fathom why your phone wouldn't be recognized...
Click to expand...
Click to collapse
Yes to everything, lol
And when I am connected to the phone while in the OS, ADB works fine, shows in when I "ADB devices"
Where'd you get your phone from? Banggood, Geekbuying, Gearbest? Did it come with a vendor ROM? Did it not pass SafetyNet on the original ROM it came with?
Are you following these instructions? Of course, replace the required stock ROM with the one for your version (x720 or x727). So does the issue come up when you reboot the phone via ADB while in the OS?
In any case, try asking on the http://www.leeco.re/ forums as well.
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Delete the drivers you have installed, boot into fastboot and have Windows automatically detect and install for you. Have you tried that? What source did you get your fastboot drivers from?
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Msmdownload drivers are not the same at all, they are Qualcom drivers. Uninstall your fastboot drivers and let windows install them
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Oh man, I had issues getting my 6t to connect to my PC when I first got my 6t. The answer for me was to plug my phone into a USB 2.0 port on the BACK of my PC instead of the front USB ports my PC has. Try using the back USB ports and let me know if that works for you!
Thank you all. I will try these suggestions later today and report back.
I tried the suggestions and still no success in fastboot connecting with my device. Thanks again for the suggestions.
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
jullev said:
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Click to expand...
Click to collapse
Thank you! I can't believe I didn't think to check that.
it is solved for me oneplus 6t not recognized in fastboot
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
hichemkanon said:
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
Click to expand...
Click to collapse
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Thank you.
phaino00 said:
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
Click to expand...
Click to collapse
Did this and still not able to recognize it in fastboot mode
sonice43 said:
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Click to expand...
Click to collapse
Rijul30 said:
Did this and still not able to recognize it in fastboot mode
Click to expand...
Click to collapse
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Really need help. I'm going in circles and wasting a lot of time:
I'm attempting to root a OP6T A6013. Its already been unlocked.
My device is recognized when powered up as an ADB device.
But when i boot into the bootloader it isnt recognized as a fastboot device, and my laptop (Win 8.1) shows ""device malfunctioned. USB not recognized". I've also been trying to install the OP driver but I'm not sure its working correctly. But would that cause the problem with recognizing fastboot?
I've root my OP7Pro (twice, actually) and though I had some driver issues then eventually figured it out. But I never had issues with fastboot.
Any tips or direction?
Hey all , replying to share my solution to this exact problem I was having..
My OP6T (T-Mobile converted to international) was not showing in fastboot devices but showed in ADB.. after hours of searching google and XDA , I ended up just plugging my 6T into another computer and it worked! , instantly recognized my device without hassle.
So just a fyi, it could be something simple as switching USB ports or even another computer.
hopefully this helps if someone get's stuck at this point.
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
sudo fastboot oem unlock worked in linux in first shot while windows was unable to recognize the device.
Thanks a ton.
EDIT : Just to add .. this linux was in VM
OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
I agree. Linux is far better when flashing android phones
anonymoustl said:
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
Click to expand...
Click to collapse
This worked for my OnePlus 9 Pro running Windows 10. Happy modding!
Can anyone help me getting ADB to work for this device. I can get it with every other phone but this one. I have the OnePlus drivers installed but when I type the Command "ADB Devices" The phone isn't listed.
Have you made sure your adb is up to date? Have you tried a different cable or a different port? Also, did you try to see if fastboot detected the device while in the bootloader?
Just trying to get more information so people can help you troubleshoot.
Milly7 said:
Have you made sure your adb is up to date? Have you tried a different cable or a different port? Also, did you try to see if fastboot detected the device while in the bootloader?
Just trying to get more information so people can help you troubleshoot.
Click to expand...
Click to collapse
So I was able to unlock the bootloader while connected. And my ADB is up to date as far as I know. I got it to work with my other devices. I have tried all the ports that I could try and I tried using the stock OnePlus cable as well as a different one but neither worked.
Did you enable adb debugging in developers options?
DaOldMan said:
Did you enable adb debugging in developers options?
Click to expand...
Click to collapse
Yes, ADB Debugging is enabled. Other people have said that switching from File Transfer to PTP solved the issue for them but that didn't work for me.
I solved the issue. I just uninstalled everything then downloaded them again and it fixed the issue.