I was able to connect to the n5x via fastboot successfully upon unboxing. However, I decided to update to take the OTA first and then unlock / flash unencrypt boot.img / twrp / supersu beta. Once the update was complete I of course enabled developer options, enabled usb debugging, and allowed for OEM unlocking.
Now I can still connect via adb just fine, but the pc cannot connect over fastboot (not even the toolkits can). I did notice under device manager that the pc does not recognize the n5x while in fastboot now (like it does in adb normally). I cannot install pc drivers to remedy this while the device is in fastboot mode.
I am using google usb drivers (current), java/sdk/etc. all installed. Super perplexing...no idea what the difference is between the original build and the MDB08I version (b/c this is where things went sideways for me).
Owned a nexus 7, 5, 6, and 9 ...I am so surprised at this outcome lol (always been a breeze).
Mtp on server 2012 was the issue.
I had this issue after i unlocked the bootloader easily, then when I tried flashing modded boot image I couldn't connect and wasn't finding my device from adb devices. I had to reinstall the Google drivers and finally worked after 3 hours of restarting my phone and computer ? hope this helps
Related
I finally got around to trying to install a custom recovery and root my HTC M8 (Verizon, KitKat 4.4.4).
I had previously unlocked my phone with SunShine - and have S-Off.
I tried installing adb/fastboot/drivers downloading from this thread:
http://forum.xda-developers.com/showpost.php?p=48915118
On my phone I turned off fastboot, enabled developer mode, and enabled USB debugging.
I connect my phone, it says USB debugging connected - and my PC (Windows 7) recognized the device.
However, when I try fastboot devices it does not recognize my phone - it returns nothing.
I realized that I had previous versions of adb/fastboot installed on my PC (From HTC Syanc & the WugFresh Nexus toolkit). I uninstalled them and reinstalled the drivers from that link, but still no adb/fastboot.
One thing I noticed is that (unlike the tutorial video on the link) in Device Manager my phone is not recognized under Other devices/ADB interface, but rather appears under Android USB devices / My HTC. I tried following the tutorial and tried to update the driver software, but it was not possible to use the downloaded Google drivers.
I tried unistalling the My HTC driver. The phone then appears for time under Other Devices / Android phone and then it re-installs the My HTC driver.
The PC recognizes it as an MTP/Media Player device, but not as an ASB one.
Any suggestions?
edit: Never mind. Arg, stupid me - I forgot to put the phone into fastboot usb mode.
Yeah....
ADB commands only work in a booted O.S or recovery
FASTBOOT commands only work in the bootloader
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Put in fastboot mode, connect to computer and manually select fastboot interface from the device manager "install device/update driver manually" box. That worked for me.
JusTeN_ said:
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Click to expand...
Click to collapse
Its fine just search for fastboot devices and see if your device comes up. Mine was showing the same thing and i continued and it worked
I updated my OP3 to OxygenOS 4.1.3 two days ago and obviously lost my root and custom recovery.
After the update, I used the OnePlus 3/3T unified Toolkit because it worked just fine for the past year.
However, upon checking the status of the device, it detected 0 devices connected.
Using the command prompt also gave me the same answer; no devices.
I already have USB debugging allowed/OEM unlocked and developer options enabled, and bootloader is already unlocked, so I don't know what's the problem with this.
Try to reinstall the drivers trough the toolkit. If that ain't worked try to install manually the driver in device controll in windows and select the driver that you can install when download sdk.
For a weird reason my windows, sometimes, lost the driver for adb devices and then i can, just like you, not see my adb or fastboot devices.
Just a quick question.
Im unable to access fastboot or bootloader mode through adb command line.
I turned on usb debugging, connected phone to usb cable with my pc, run command line in platform-tools - adb devices and nothing happens.
I think i know the answer, but i want to be sure. Is it because i dont have unlocked bootloaded (OEM Unlock, still 6 days to wait)
Do you have the proper drivers? Try downloading the universal ADB drivers.
Sent from my Lenovo P2a42 using Tapatalk
Switch USB mode to PTP instead of MTP. I don't know why, but it works like that after Android KitKat/Lollipop release. Used this trick on LG G2 mini and now on my P2
I dont know if i have correct drivers, but i think so
https://dl.google.com/android/installer_r24.4.1-windows.exe
http://download.oracle.com/otn-pub/...m=1498221676_80503fd7b283f64cfa8ae7825b0021e2
My Xiaomi Redmi phopne is detected correctly, but its rooted and OEM unlocked
edit:
It's fine now. Its unbelivable what a mess is with adb files/usb drivers and similar. There is so much that can go wrong.
I wiped everything and installed minimal adb and fastboot + lenovo usb/mtp drivers
Now pc detects my phone.
"""""""""""""""""""""""""''Help Help Help Help"""""""""""""""""'''''''''’'''''
I am having Moto M XT1663 phone I bought was already boot unlocked so i decided to Install recovery and Root so that I can enjoy rooted things.
The problem is that the phone not detectable in Fastboot mode phone can only be detected in ADB mode. When I write command "ADB devices" it shows my device.
If I want to reboot into boat loader and use fastboot devices after hitting enter it shows nothing and no error appears.
I google about my phone's drivers that should be installed in order to use fastboot mode. So I installed them but no success.
One thing I notice that In fast boot mode my laptop giveys USB detection error and also tells me ADB interface failed.
Tried below mentioned things in order to get my phone detected in fastboot mode:
1) tried 3 different laptops(my Nexus 6p is detectable on all three laptops).
2) changed USB cable.
3) FDR using recovery.
EDIT: Problem solve by install Mediatek driver from windows update