[Q] One X-specific solution for fastboot under Windows 8 - HTC One X

I tried numerous "solutions" floating around this site and web on how to get fastboot working again on my Windows 8 RTM 64bit with HOX on CM10 ROM. ADB and USB memory are working, but fastboot does nothing. Of course have driver signature off in Windows. Currently back to original HTC driver in order to have at least USB memory working reliably.

Lucas0511 said:
I tried numerous "solutions" floating around this site and web on how to get fastboot working again on my Windows 8 RTM 64bit with HOX on CM10 ROM. ADB and USB memory are working, but fastboot does nothing. Of course have driver signature off in Windows. Currently back to original HTC driver in order to have at least USB memory working reliably.
Click to expand...
Click to collapse
Have you tried to kill adb process?
Ctrl+Alt+Del -> Task Manager -> More details
Click on adb process and then hit "End Task" button
Then open cmd and try to run fastboot again.

Thanks for the suggestion, but does not work - waiting for device...

You sure you have the correct USB ADB/Fastboot drivers installed? I had to boot into a special Win* mode to install unsigned drivers.
This thread here should detail it for you. Post 2 covers the unsigned drivers part.
http://forum.xda-developers.com/showthread.php?t=1583801

Yes, had done that previously, too. For me fastboot is working (adb always was) since I use the latest one from the Android SDK.

i just installed these drivers and it worked
Download

Related

[Q] Correct (latest?) drivers/ADB for Vision

Hi guys
I did own a Sapphire/Magic back in the days and came back to Android after some skipping done during the last year. Back then installing usb drivers and adb was easy: plug in the Sapphire, point Windows to the drivers folder, done.
With the Vision/Desire Z it was much more complicated. I did use the old drivers from back then and ran into problems. Device manager had an ADB device listed, ADB couldn't find it though. Once I got it working in Android, it wouldn't interface with the recovery adb though. Once I got that working, it wouldn't show/mount the SD card anymore. Short: a huge mess.
Right now I have everything more or less working (still using the old drivers I used with the Sapphire) but it's not really right, I tried an RUU the other day and it would fail because my ADB/RUU ADB/Driver combination wouldn't match.
Long story short: where did you guys get your drivers from to interface the Vision with ADB/Fastboot?
Update the SDK ...this time its in platform tools. run the sdk update and download the usb drivers. Refresh your SDK.
If you don't want to do that...then install pdanet just to grab the drivers
Or go to cyanogenmod the drivers may be avail in a post from ciwrl in vision.dz download section.
All right, I'm d/ling the Java JDK as prompted by the latest SDK installer
Thanks!
I did this too (SDK + Platform tools) to get ADB/shell. However, I never got fastboot to work (even tried fastboot-mac). Not sure what I was missing, but flashing via SD (including radio) has been working thus far for me. Any recommendations on where to get more info on "fastboot" process, specifically on a Mac?
Hmm... you did notice that the fastboot binary is - at least on Windows - in a different folder than ADB, right?
On Windows its two different paths pointing to either ADB or Fastboot.
[posted on the go]

[Q] Help with fastboot driver?

Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
MetroGnome711 said:
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
Click to expand...
Click to collapse
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Sadly...
eL_777 said:
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Click to expand...
Click to collapse
Sadly, i don't have such a machine lying around. The wife's comp has the sdk installed as well (she's a nexus user). Although, on her windows 7 machine, in fastboot i do see MyHTC driver as ok, but when i run the "fastboot oem get_token_modifier" command, i get "(bootloader) [ERR] Command error!!! OKAY finished"
so something still quite wrong!
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
.... This probably explains my problem as well. Will try on a Windows 7 computer in the morning and report back to see if that was the problem.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
ADB and Fastboot both work fine on Windows 8. I had to install the newest 4.3.0.001 drivers to get ADB to recognize my One on my Windows 7 partition, despite having had the most recent behind that. My Windows 8 partition worked like a charm because I had more recently installed the updated drivers on it. It's also possible you were connecting your phone to a USB 3.0 port. ADB/Fastboot is "wonky" over USB 3.0, and if you don't have the correct USB 3.0 drivers, you have no chance at all. Also, you need USB Debugging turned on, which can be done in this version of Android by going to Settings -> About -> Software Information -> More, then tapping on the build number 7 times, unlocking developer options, then going to Settings -> Developer options, and checking USB Debugging.
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
IceDragon59 said:
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
Click to expand...
Click to collapse
I can confirm. I successfully got fastboot to run on OS X, but when I try to send my token via HTCDev, I'm met with error 160: MID not Allowed..

[Q] Cannot Unlock Bootloader on Windows 8.1

Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
killfire72 said:
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
Click to expand...
Click to collapse
Use another computer if you can.
I had similar problems until I used this version of adb
http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
ashyx said:
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
Click to expand...
Click to collapse
That version of ADB didn't work for me either. Anyway I was able to get fastboot to work but not ADB so I was able to unlock and root and everything through a strange method using only fastboot.
Second question, if I am switching between AOSP roms, say for example CM to PA, can I dirty flash or do I have to reset?
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
xeron72548 said:
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
Click to expand...
Click to collapse
Not so, I and others have ADB working fine on USB 3.0 ports.
The problem is Windows 8 driver signing enforcement blocking the install of drivers. You need to go to advanced startup options to disable it.
Download these drivers first and extract: http://www.mediafire.com/download/i3lcm7dwl581518/ADB_Fastboot_Drivers_Win81.zip
Follow these instructions to disable driver signing enforcement: http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
Once fully booted go into device manager and you should see a device called 'Android 1.0' with an exclamation mark.
Right click 'Android 1.0' then 'update driver software' then 'Browse my computer for driver software'
Click the 'Browse' button and then browse to the driver folder 'ADB_Fastboot_Drivers_Win81' extracted earlier then click next to install the driver.
You will get a warning about unsigned drivers, just ignore and continue.
The drivers should install and you should see a new entry in device manager called 'Android phone' which means the ADB driver is installed.
ADB should now be working.
Thank you so much for this. Have been wondering for a very long time
Sent from my HTC One_M8 using XDA Free mobile app
It sounds like you've got plenty of technical help already, but I will say that I use ADB perfectly fine on my desktop with Win 8.1 so it's possible. I also use hassoon's toolkit occasionally with no issue.
Before I could get the desktop to recognize the M8 I had to completely uninstall all drivers related to my previous galaxy nexus as well as remove any mention of the device in Window's USBdeview. After a reboot, I just plugged in the M8 and windows automatically installed the necessary M8 drivers. I can then run fastboot and adb from the toolkit.
I ended up uninstalling the MSFT USB 3.0 drivers and use the Intel USB 3.0 drivers instead on my Win8.1 laptop that has only USB 3.0 ports. Works great.

[Q] ADB not recognizing device

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

Going mad just can't get fastboot to work?

I have tried windows and editing the inf file for it to recognise the Swift but adb works but fastboot doesn't. That is after toggling USB debug several times to get the authorization prompt to appear. I have tried Ubuntu 15.10 live CD, updated udev rules but adb/fastboot does not detect any device.
Is anyone able to help? I am at a complete loss of what I am doing wrong?
I just want to unlock and flash twrp 3 recovery.
Thanks
xda163fm said:
I have tried windows and editing the inf file for it to recognise the Swift but adb works but fastboot doesn't. That is after toggling USB debug several times to get the authorization prompt to appear. I have tried Ubuntu 15.10 live CD, updated udev rules but adb/fastboot does not detect any device.
Is anyone able to help? I am at a complete loss of what I am doing wrong?
I just want to unlock and flash twrp 3 recovery.
Thanks
Click to expand...
Click to collapse
Think fast boot only works in bootloader mode see here for unlock instructions
http://https://wiki.cyanogenmod.org/w/Install_CM_for_crackling
If I am using windows what drivers should I install? Adb works but does fastboot need drivers also? I have tried fastboot both with phone in and out of the fastboot screen - I have to pull battery to get out of fastboot mode! Thanks
Quite close to begging here never had problems like this with previous phones. Adb works (it reboots into fastboot) but fastboot doesnt it just says waiting for devices.
Any pointers appreciated - thinking it is driver related whatever I choose it seems to say compatible driver not found.
Any pointer to drivers that should work would be great?
Have tried again in Ubuntu (not got adb or fastboot working Ubuntu 15.10 live cd) and in Windows (adb working but fastboot now).
Help!
xda163fm said:
Quite close to begging here never had problems like this with previous phones. Adb works (it reboots into fastboot) but fastboot doesnt it just says waiting for devices.
Any pointers appreciated - thinking it is driver related whatever I choose it seems to say compatible driver not found.
Any pointer to drivers that should work would be great?
Have tried again in Ubuntu (not got adb or fastboot working Ubuntu 15.10 live cd) and in Windows (adb working but fastboot now).
Help!
Click to expand...
Click to collapse
I can't get fastboot working either. Really annoying me.
I have got this sorted. I will post details in the morning. I used a live USB of Ubuntu 15.10.

Categories

Resources