adb can't seem to find my device while fastboot does..
I installed the HTCDriver_4.0.1.001 for usb drivers
I can see my device in devicemanagement under Android usb devices > My HTC
this are the cmd results:
C:\Android\fastboot>fastboot devices
FA2AVW103684 fastboot
C:\Android\fastboot>adb devices
List of devices attached
C:\Android\fastboot>
can anyone help me out?
Do you have usb debugging enabled?
Sent from my HTC One X+ using Tapatalk 4 Beta
Roodenburgertje said:
adb can't seem to find my device while fastboot does..
I installed the HTCDriver_4.0.1.001 for usb drivers
I can see my device in devicemanagement under Android usb devices > My HTC
this are the cmd results:
C:\Android\fastboot>fastboot devices
FA2AVW103684 fastboot
C:\Android\fastboot>adb devices
List of devices attached
C:\Android\fastboot>
can anyone help me out?
Click to expand...
Click to collapse
Are you trying to get adb acces to your phone when booted up or in recovery? As already said, in the first case you need to enable USB Debugging in developer options. If your phone is in recovery it may take some minutes for your computer to detect it after starting ADB server.
reaper90 said:
Are you trying to get adb acces to your phone when booted up or in recovery? As already said, in the first case you need to enable USB Debugging in developer options. If your phone is in recovery it may take some minutes for your computer to detect it after starting ADB server.
Click to expand...
Click to collapse
Yes im trying to adb acces from recovery without succes
is it win 8 or 8.1 ?
Win 8.
And i have a international hox+
You can only access adb sideload from your recovery. Every other function of adb is only accessible after your device boots into Android.
wrong wrong wrong, shut up, NasaGeek
Roodenburgertje said:
Yes im trying to adb acces from recovery without succes
Click to expand...
Click to collapse
Works for me without problems on Windows 8. I don't know what driver version i have, i think i installed the driver with htc sync from my phone and uninstalled htc sync later.
Try the following:
1. Connect your phone to your computer and reboot in recovery.
2. Open command line and navigate to the folder where your adb/fastboot files are.
3. Type "adb start-server" and wait some minutes (as i said it may take some minutes to recognize the phone in recovery)
4. Type "adb devices" and now your device should be listed there as in recovery. If not, wait some more time and try again. Shouldn't take longer than 10 minutes. Otherwise there's probably something wrong with your driver and/or adb/fastboot files.
NasaGeek said:
You can only access adb sideload from your recovery. Every other function of adb is only accessible after your device boots into Android.
Click to expand...
Click to collapse
You should have full adb access in recovery .....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
You should have full adb access in recovery .....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
You are quite correct. I don't know what I was thinking. I'll edit my post.
The driver that comes with htc sync works just fine...
Alternate is Koush's universal ADB driver...
Related
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Thermaltake868 said:
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Click to expand...
Click to collapse
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
[email protected] said:
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
Click to expand...
Click to collapse
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Thermaltake868 said:
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Click to expand...
Click to collapse
I always had the device shown as BLANK on "adb" when using windows
whereas on fastboot I never had that issue.....
can u try this
In windows install this MInimal ADB and Fastboot give a try on"fastboot devices" using this
if not working re install the drivers and try the MInimal ADB and Fastboot again
I am suggesting this because it had worked flawlessly for me with proper drivers and MInimal ADB and Fastboot.......
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Thermaltake868 said:
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Click to expand...
Click to collapse
Dude try this USB drivers if nothing works
[email protected] said:
Dude try this USB drivers if nothing works
Click to expand...
Click to collapse
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
EDIT:
I manage to get device ID on adb devices in windows, but when I enter bootloader in fastboot he can't recognized him on command "fastboot devices" he said "device not found", and I can't flash kernel becouse he needs to be in fastboot.
Thermaltake868 said:
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
Click to expand...
Click to collapse
Weird I just installed this and Minimal ADB on my PC and checked....
all good here can see the Device on the adb and fastboot..
try again as administrator or something...might help not sure
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Thermaltake868 said:
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Click to expand...
Click to collapse
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
[email protected] said:
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
Click to expand...
Click to collapse
I am using minimal adb that you gave me, and yes both files are in the folder.
Thermaltake868 said:
I am using minimal adb that you gave me, and yes both files are in the folder.
Click to expand...
Click to collapse
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
[email protected] said:
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
Click to expand...
Click to collapse
I did that too now, and in windows I get adb devices he show me number of my device, my friend told me now that I can flash kernel when I am in OS that I don't have to be in fastboot he will enter fastboot on his own, and I try that too, and as I told he manage to find device via adb, but when he enter bootloader in fastboot he is waiting for device in kernel cmd windows he can't find him.
Make sure your using a USB port that connects directly to your mobo. adb/fastboot is dodgy with USB hubs. Try a port at the back of your PC.
Sent from my HTC One X+ using Tapatalk
I fixed it I had old drivers for USB I installed new from intel chipset did the setup.exe -overall in cmd after that I uninstall htc drivers that I installed before remove them completly restart PC after that install latest HTC Sync connect the phone run the .bat from kernel, and it went successfully.
Thanks for all the help guys
Adb is showing list of devices attached..what is the solution for this..if any one knows how to solve this problem can u help me??
@Vinay23
On the device I'm using, this was under "Default USB Configuration" - advice from others appears to be that selecting PTP is the way to go.
For me, it works =).
Hope that might help out.
I found it here:
“adb devices” returns empty “List of devices attached” on Ubuntu
Based on react native documentation (https://facebook.github.io/react-native/docs/running-on-device) I wanted to connect to ADB in my ubuntu vm (Ubuntu 18.04.2 LTS) but my problem is that i keep ge...
stackoverflow.com
Hello all, been scouring the web with no avail, so I must come here for your help.
I used some of the guides on this forum in order to root, install CWR, and Cyanogenmod a few months back, but I'm back again today after an OTA update got me stuck in CWR/bootloader.
I can use both of these, and both of these only. I cannot boot into the ROM.
When looking, I've realized the only way to fix this would be to do a full reset and install the ROM again. I've wiped the device with CWR, but I'm not able to flash another ROM onto the device. (I'm looking to flash the GPE ROM this time).
My computer is detecting that something is connected, but even with the ADB drivers and everything, ADB still isn't detecting the device. Any pointers?
Also when looking around, I also noticed that many guides tell me I need to turn S-ON off, and I've tried doing that with rumrunner, but that didn't work since ADB wasn't either.
TLDR; I'm stuck in bootloader/recovery, am not able to flash/sideload due to my PC not detecting the device.
Anyway, THANKS LOADS IN ADVANCE. I've spent all afternoon searching today, and this is my last resort.
-GoldenTatertot
TWRP 2.6.3.3+ and adb sideload will be your friend. Try that and post back results
sent from my mobile device
SaHiLzZ said:
TWRP 2.6.3.3+ and adb sideload will be your friend. Try that and post back results
sent from my mobile device
Click to expand...
Click to collapse
I'm not able to sideload though. My PC isn't detecting the device.
GoldenTatertot said:
I'm not able to sideload though. My PC isn't detecting the device.
Click to expand...
Click to collapse
You need to install HTC sync to ensure the proper drivers are installed.
Download HTC sync manager
Install it,
Remove HTC sync manager but leave drivers
place HTC one on boot loader then fastboot option, connect device to computer wait until android 1.0 installs
Disconnect device and boot to recovery, reconnect device and let drivers install.
Run from computer CMD and get to the place where adb and fastboot exes are located.
Type command adb devices
the if successful prompt to do a adb sideload
Sent from my HTC One using xda app-developers app
TopoX84 said:
Download HTC sync manager
Install it,
Remove HTC sync manager but leave drivers
place HTC one on boot loader then fastboot option, connect device to computer wait until android 1.0 installs
Disconnect device and boot to recovery, reconnect device and let drivers install.
Run from computer CMD and get to the place where adb and fastboot exes are located.
Type command adb devices
the if successful prompt to do a adb sideload
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Alright, I installed and uninstalled HTC sync manager, only uninstalled from PC's native uninstallation process, and not sure if the drivers got uninstalled- didn't ask me about it.
After that, I recall a popup telling me it's installing Android 1.0, which only was active for a moment. I disconnected and booted to recovery, reconnected to computer, and 'adb devices' returned no devices.
Thanks again. Today was the first day at school without my phone this year, and it was dreadful. I'm a total addict.
Do you have a linux distro available which you can try? Preferably Ubuntu. Everytime Windows screwed up, I was able to do adb/fastboot perfectly with Linux.
Install:
sudo apt-get install android-tools-adb android-tools-fastboot
Define rules:
sudo gedit /etc/udev/rules.d/51.android.rules
Write this in that file: SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="Ubuntu"
Save and exit, then do sudo adb / fastboot devices.
svemprala said:
Do you have a linux distro available which you can try? Preferably Ubuntu. Everytime Windows screwed up, I was able to do adb/fastboot perfectly with Linux.
Install:
sudo apt-get install android-tools-adb android-tools-fastboot
Define rules:
sudo gedit /etc/udev/rules.d/51.android.rules
Write this in that file: SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="Ubuntu"
Save and exit, then do sudo adb / fastboot devices.
Click to expand...
Click to collapse
Do you think you could write or link me to a more detailed guide about that? Don't have much knowledge about that kind of stuff. Especially since I don't know what I need to look for.
Ahh, was finally able to get ADB to work on my computer. All good now.
GoldenTatertot said:
Ahh, was finally able to get ADB to work on my computer. All good now.
Click to expand...
Click to collapse
Do you mind telling us the steps? For other people looking for a solution?
Sent from my HTC One using xda app-developers app
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
eriknors said:
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
Click to expand...
Click to collapse
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
dottat said:
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
Click to expand...
Click to collapse
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
eriknors said:
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
Click to expand...
Click to collapse
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
dottat said:
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
Click to expand...
Click to collapse
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
eriknors said:
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
Click to expand...
Click to collapse
Not an install. Unzip and run cmd prompt from there. Note that your fastboot commands will start HTC_fastboot
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
eriknors said:
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
Click to expand...
Click to collapse
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Got it
dottat said:
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Click to expand...
Click to collapse
No dice. ADB worked just fine but still no fastboot
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Uzephi said:
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Acoustichayes said:
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Click to expand...
Click to collapse
Well tbh I've been trying on both just to see if anything works.
eriknors said:
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Click to expand...
Click to collapse
He asked that because if you use mine you need to use htc_fastboot devices
Otherwise you will be using the fastboot from sdk install.
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Had the same issue tried every thing, but eventually end up installing uBuntu that solved every thing.
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
Its due to the missing device descriptor.
Royal PITA, I have yet to get it working. I just keep a win7 laptop around.
The only way this could be "fixed", would be if we had a newer eng-hboot that had the descriptors set.