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
Related
I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790
Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition
jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.
For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed
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
I'm using a windows 7 laptop with the normal drivers installed, and i have recently worked on an htc m9 and an m8. adb works fine on all my other devices. i reboot to bootloader and the computer instantly detects the connection and fastboot works. as soon as i boot into twrp, the usb disconnected sound goes off, and there is no mtp or adb. same thing with the os (newest stock system image). what the hell is going on?
Sieger179 said:
I'm using a windows 7 laptop with the normal drivers installed, and i have recently worked on an htc m9 and an m8. adb works fine on all my other devices. i reboot to bootloader and the computer instantly detects the connection and fastboot works. as soon as i boot into twrp, the usb disconnected sound goes off, and there is no mtp or adb. same thing with the os (newest stock system image). what the hell is going on?
Click to expand...
Click to collapse
can you confirm that "fastboot devices" returns your unit's serial number?
while "an htc m9 and an m8" work you still need Nexus-specific driver
please quote the USB's VID/PID from W7 device manager while in TWRP and/or OS
alternatively, post UsbTreeView_report
yes, fastboot works fine. i had to reflash the newest system image several times while trying to figure out why the tablet kept bootlooping after deleting bloatware off of the system partition (the google app doesn't like to be frozen or deleted anymore). the problem is that the n7 isn't even detected via USB outside of the bootloader. I'm assuming that the proper nexus driver is installed, but i cant just "update driver" with the official google drivers, because the tablet isn't detected by windows.
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
Pixel XL (Verizon) Not Being Recognized via "ADB Devices" command on Windows 7.
So I got my 128gb pixel xl from Verizon today. It's still 7.1.0 (Build NDE63P) so I want to unlock the bootloader asap. I was able to get the phone booted up and mostly set up without taking the OTA update (I pulled sim card before booting the phone for the first time, and I skipped the wifi setup).
I intended to follow the instructions here to use dePixel8 to unlock the bootloader. I got USB debugging enabled on my phone, and ABD/Fastboot installed on my computer (Windows 7 laptop). The problem is the phone doesn't come up in the list when I use the "adb devices" command from the command prompt within the SDK folder. Looking at the device manager, it appears my laptop is automatically installing the "Google Nexus ADB Interface" driver for the phone, is this not the correct driver? I downloaded the USB drivers from here and tried pointing the Device Manager at them to force a driver update, but the device manager tells me the drivers are already up to date.
Can someone please explain to me how to get my computer (Windows 7) to recognize my phone via ADB so I can push dePixel8 and unlock the bootloader? I feel like I'm so close to being able to unlock the bootloader, but my phone not being recognized via ADB is driving me freaking crazy.
Thanks!
EDITED TO ADD: If I turn off USB debugging, and just put the phone in File Transfer mode when connecting via USB, it never shows up in Windows Explorer as any kind of storage device, which would make me think its a problem with the driver, right?
That link has the wrong Fastboot ADB version. Use this one
https://developer.android.com/studio/releases/platform-tools.html
TonikJDK said:
That link has the wrong Fastboot ADB version. Use this one
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Thanks for the prompt reply. I'm currently uninstalling Android Studio and SDK I downloaded, and will install the one you linked.
I think this is still a problem related to the driver Windows 7 is automatically installing for my phone. If I turn off USB debugging, and just put the phone in File Transfer mode when connecting via USB, it never shows up in Windows Explorer as any kind of storage device, which would make me think its a problem with the driver, right?