Fixed- ran the 15 second ADB and fastboot installer
I updated to the latest verion of windows and now ADB and fastboot do not recognize device. I dowloded the phone drivers updated to a current version of ADB and fastboot from google. I have have developer options on and USB debugging. I also tried on another computer and same issue. I'm not getting the pop-up that says allow this computer to use USB debugging which I think might be the problem. Any ideas?
jdh10475 said:
Fixed- ran the 15 second ADB and fastboot installer
I updated to the latest verion of windows and now ADB and fastboot do not recognize device. I dowloded the phone drivers updated to a current version of ADB and fastboot from google. I have have developer options on and USB debugging. I also tried on another computer and same issue. I'm not getting the pop-up that says allow this computer to use USB debugging which I think might be the problem. Any ideas?
Click to expand...
Click to collapse
Might be a little overkill here but unplug your phone from your pc, uninstall moto drivers, reboot, reinstall moto drivers and reboot. Meanwhile in developer settings in your phone, revoke usb debugging authorization and turn usb debugging off.
Once all that is done replug your phone let the drivers install, then toggle usb debugging back on. Hopefully it'll reinstall a fresh adb driver and prompt for authorization.
Related
When I connect my HTC Desire through USB cable to my laptop, my laptop wait a while then pop a windows which says USB Device Not Recognised. My device just got the orange light lit up but there is no response other than that i.e. no menu pops up to choose "charge only, disk drive" whatsoever.
It worked just two days ago before I reflash a new ROM (RCMixHD 3.6.1).
During the flash, the SD card was not recognised too so I tried to get it work by using "fastboot oem enableqxdm 0" as instructed by one post named "USB brick/rickrolled/b0rked -> FIXED!" on MoDaCo.
But I did not flash the update.zip as required cos my problem was fixed before this step.
Can anyone help me fix this problem? Waiting online
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
FASTBOOT shows "FASTBOOT USB", Bootloader also gives me "HBOOT USB PLUG", I think the USB cable is fine.
stringer7 said:
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
Click to expand...
Click to collapse
I tried the two commands in cmd, I copy down what it gives me
E:\SDK\Tools> adb devices
List of devices attached
E:\SDK\Tools> fastboot devices
HT05HPL12963 fastboot
E:\SDK\Tools>
Ok so the fastboot result means you can connect to PC.
What happens if you connect your device whilst it's booted up with USB debugging enabled? Enable this prior to connecting in settings>applications>development.
Hi thanks for the help, I managed to unbrick the USB brick. But now even though I'm able to connect to my laptop, the adb devices still doesn't give me any device. In device manager, I got an "ADB" with yellow exclamation mark under “Other Devices”, just cannot get the right driver for it. Could it be due to the USB brick?
adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.
No ideas?
I can connect adb over WiFi, but ofcourse it says offline.
USB debugging ticked?
A
Adb doesn't work in the bootloader. Only fastboot commands
Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.
Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Metaception said:
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Click to expand...
Click to collapse
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Tigerlight said:
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Click to expand...
Click to collapse
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
Yes the toolkit uses ADB to automate the reboot into fastboot mode.
And my understanding is that enabling USB Debugging changes the drivers required so that you can access the ADB interface.
I rooted and installed my first ROM using the toolkit, idk y it's different now.
I will try to flash via fastboot and then ask in the toolkit thread as well since these driver are the ones that the came with the toolkit.
EDIT: Whhhhooaa, did it! Cheers for fastboot
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
If you want adb usb drivers, i prefer to install moborobo from Moborobo.com.
Start application,
Plug your device with usb debugging on.
and it will do the work.
So I uninstalled all of the previous Samsung/Koush/Intel Android USB drivers for and downloaded SDK Google USB driver. But I can't get adb to work - when I connect the phone, it says Pixel XL under Portable Devices in Device Manager (Win 7.) I can transfer files, but ADB just won't work.
I used some Intel and Koush Android ADB Device drivers previously, and the Google Nexus ADB device did appear in Device Manager, but adb was still a no go.
Does anyone know how to fix this?
Thanks.
Just to make sure, you did enable adb debugging in developer options, right? When you connect the phone to your computer, are you choosing the transfer files option? What is showing up in device manager?
skaforey said:
Just to make sure, you did enable adb debugging in developer options, right? When you connect the phone to your computer, are you choosing the transfer files option? What is showing up in device manager?
Click to expand...
Click to collapse
I enabled debugging in developers options.
I tried most of the settings - charging, file transfer, ptp.
When I connect the phone, only one thing appears - Pixel XL under Portable Devices.
I can transfer files as mtp and ptp.
I can also update the driver for Pixel XL and force Google Nexus ADB driver (I believe it comes from something like 2013-2014 USB driver package by Koush.) When I do that, Pixel XL disappears and Android ADB device replaces it under Android Devices. But ADB still doesn't work, when I do adb devices - nothing shows up.
I can also update this driver with a current Google USB driver from the latest android SDK. I think it's version 11. When I do this, Android ADB device gets replaced with Pixel XL under Portable Devices. Still no adb.
I have updated Java SDK, I have updated Windows 7. I spent literally 4-5 hours on this, and I can't figure it out.
When you see it as adb under device manager, try removing the driver by right clicking and uninstall. Unplug the device and replug it in. Then make sure it's using the newest SDK driver, that's what worked for me.
Tried a different computer. Adb worked as soon as I installed the 15 seconds adb installer.
There's something wrong with my main computer. I already tried uninstalling and reinstalling the driver - it just doesn't work - every time the device is recognized as mtp usb device.
Any tips would be greatly appreciated!
nabbed said:
Any tips would be greatly appreciated!
Click to expand...
Click to collapse
Erase every adb and fastboot folder you have and download android SDK and reinstall platform tools
nabbed said:
Any tips would be greatly appreciated!
Click to expand...
Click to collapse
You could try using the adb minimal with fastboot at the xda link below. It was updated on 10-22-16 this is what I use.
http://forum.xda-developers.com/showthread.php?t=2317790
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?