Related
Universal Naked Driver 0.72
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
Since ICS is on the way you will get you bootloader upgraded most likely. Then the unlock APK should follow if Asus holds up there end.
This will allows for comminucation with your tablet and phones (execpt moto for now)
Hope Asus hits you up soon with the unlock.
Cheers!
DDMS ok on my evo 3D with your driver, will test my transformer later
Nice work, was waiting for this
Although, could you tell me how did you get into fastboot mode on device? Did you use ICS, or any special bootloader, maybe a modified one?
keyra74 said:
DDMS ok on my evo 3D with your driver, will test my transformer later
Click to expand...
Click to collapse
Thanks for the feedback
fonix232 said:
Nice work, was waiting for this
Although, could you tell me how did you get into fastboot mode on device? Did you use ICS, or any special bootloader, maybe a modified one?
Click to expand...
Click to collapse
On my transformer prime I think the fastboot option only was available after the bootloader came unlocked but I could be wrong. I just do not remember seeing it before.
But after the unlock it I rebooted to the bootloader and then there was three options 1) BootToOS 2) Fastboot 3) Wipedata.
Once you select fastboot it says enabling fastboot protocols. Hope this helps but I do have a prime so it may be different.
1wayjonny said:
On my transformer prime I think the fastboot option only was available after the bootloader came unlocked but I could be wrong. I just do not remember seeing it before.
But after the unlock it I rebooted to the bootloader and then there was three options 1) BootToOS 2) Fastboot 3) Wipedata.
Once you select fastboot it says enabling fastboot protocols. Hope this helps but I do have a prime so it may be different.
Click to expand...
Click to collapse
Hmm, then please remove the Fastboot options from the original Transformer's log, as we have no access to it yet ;D Maybe with a modified u-boot, but that needs some time.
Any fix for Linux? DDMS doesn't find my TF anyomore since I upgraded to ICS
DDMS confirmed working on my ics transformer and windows here (with these drivers)
http://imgur.com/Wnmhd
gnufabio said:
Any fix for Linux? DDMS doesn't find my TF anyomore since I upgraded to ICS
Click to expand...
Click to collapse
Hey try adding these device ID's to your USB config, this should allow ADB, APX and also Fastboot if and when TF101 gets a unlocked bootloader.
USB\VID_0B05&PID_4E1F
USB\VID_0B05&PID_4E1F&MI_01
USB\VID_0B05&PID_4E3F
USB\VID_0B05&PID_4E3F&MI_02
USB\VID_0B05&PID_4DAF
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0955&PID_7820
keyra74 said:
DDMS confirmed working on my ics transformer and windows here (with these drivers)
http://imgur.com/Wnmhd
Click to expand...
Click to collapse
Thanks for the feedback!
complete noob question. adb still confuses me and im tryin to unbrick my prime. its in the recovery bootloop, the thread im following says to do some adb commands. but "adb shell" gives me the message "adb" is not a recongnized as a command or blah blah.. so i figured its cause i don't have the drivers? well anyways.. this thread looks like it has what i need... but where\how do i install the drivers? tia.
shady503403 said:
complete noob question. adb still confuses me and im tryin to unbrick my prime. its in the recovery bootloop, the thread im following says to do some adb commands. but "adb shell" gives me the message "adb" is not a recongnized as a command or blah blah.. so i figured its cause i don't have the drivers? well anyways.. this thread looks like it has what i need... but where\how do i install the drivers? tia.
Click to expand...
Click to collapse
ya... adb not recognised means you don't have the android sdk installed. Also this is the tf101 not the prime. To install drivers hit start and type in drivers. find the one that says unknown or android 1.0 or apx or something right click and hit manually install driver
mrevankyle said:
ya... adb not recognised means you don't have the android sdk installed. Also this is the tf101 not the prime. To install drivers hit start and type in drivers. find the one that says unknown or android 1.0 or apx or something right click and hit manually install driver
Click to expand...
Click to collapse
You also get that message if you have the SDK installed but not in your path and you are trying to run the command outside of the Android\android-sdk\platform-tools\ directory where the adb command resides. I have posted a guide for installing the SDK and then installing these drivers in the Roach's Clockwork Mod Recovery thread. I was trying to help solitude65 who installed a Recovery that only reads internal apparently after he wiped the internal sdcard or didn't realize he needed a ROM on the internal sdcard. Not sure how much of it will apply to the Prime as I have a TF101 and used it to confirm the steps I posted over there.
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
1wayjonny said:
Hey try adding these device ID's to your USB config, this should allow ADB, APX and also Fastboot if and when TF101 gets a unlocked bootloader.
USB\VID_0B05&PID_4E1F
USB\VID_0B05&PID_4E1F&MI_01
USB\VID_0B05&PID_4E3F
USB\VID_0B05&PID_4E3F&MI_02
USB\VID_0B05&PID_4DAF
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0955&PID_7820
Thanks for the feedback!
Click to expand...
Click to collapse
Can you tell me specifically what USB config you are referring to and where to find it?
Thank you SO much! I was pulling my hair out, trying to find drivers for my TF101 in recovery mode, and I couldn't.. But these helped me immediately, and did the job!
Thank you!
I am on Windows 8 and couldn't get this installed with an error about missing the hash for the file. It of course is missing, since this isn't a signed driver.
I followed the instructions at http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/ and was able to install the driver. If you're using Windows 8, you can do the same to install these unsigned drivers (or any other unsigned drivers for that matter).
Updated version, feedback helpful
1wayjonny said:
Updated version, feedback helpful
Click to expand...
Click to collapse
In order to provide feedback, I would have to have an issue...
the sarcastic joke and hidden props aside, I have a few now phones ill give it a go with sometime in the next week, amazing timing however, just reformatted my "utility" laptop... (CDMA Workshop is such a PITA to resetup after every reformat... so effing annoying! ****ty DRM and updates however are the requirements for a legit copy... sometimes I regret spending that $100)
Hammerfest said:
In order to provide feedback, I would have to have an issue...
the sarcastic joke and hidden props aside, I have a few now phones ill give it a go with sometime in the next week, amazing timing however, just reformatted my "utility" laptop... (CDMA Workshop is such a PITA to resetup after every reformat... so effing annoying! ****ty DRM and updates however are the requirements for a legit copy... sometimes I regret spending that $100)
Click to expand...
Click to collapse
No worries thanks for any help.
I having an issue trying to remove the previous version to the latest one I just sold my tf201 and today i got the nexus7 can someone help on a step by step on what to do in device manager. Now my galaxy nexus isn't recognized when i write adb devices in cmd after trying to push the latest one
perfecto
i tried rooting and playing with my TF101 when i first got it ages ago, but it was all such a pain in the ass. thank you for making this part a bit simpler.
Tried pointing Device Manager to the folder I unzipped Universal drivers to and got this.
Anyone else?
Please help is it possible to root my tf700t tablet? Its updated to latest available update as of 05/29/2013!! Jellybean 4.2.1 i dont need anything too fancy just tired of a laggy tablet that i have no control over yet payed $500+ for... looking forward to be able to remove any app on my device without it not letting me even get a chance to select an option to remove. Posting a picture of my screenshot in settings> about. Thanks gladly appreciate if i can get help on this :fingers-crossed:
This thread: http://forum.xda-developers.com/showthread.php?p=40754957
It's right below yours, for goodness sake.
Send From My Samsung Galaxy S3 Using Tapatalk 2
ShadowLea said:
This thread: http://forum.xda-developers.com/showthread.php?p=40754957
It's right below yours, for goodness sake.
Send From My Samsung Galaxy S3 Using Tapatalk 2
Click to expand...
Click to collapse
Now now, let's be nice...we all know that people hate to read/search on Wednesdays
MRCANNADY said:
Now now, let's be nice...we all know that people hate to read/search on Wednesdays
Click to expand...
Click to collapse
Some seem to hate to read/search on days ending with "y".
ShadowLea said:
This thread: http://forum.xda-developers.com/showthread.php?p=40754957
It's right below yours, for goodness sake.
Send From My Samsung Galaxy S3 Using Tapatalk 2
Click to expand...
Click to collapse
thanks:laugh::good:
cant get past daemon start process
beahrr77 said:
thanks:laugh::good:
Click to expand...
Click to collapse
i feel useless... after i run the batch file from the extracted motochopper folder, it starts in terminal and says not found followed by daemon started and nothing happens.. i checked usb debug and the unknown source security boxes on the tablet and since im running windows 7, i ran the batch file as administrator. please anything will help kind of afraid to pull usb cable out of laptop
beahrr77 said:
i feel useless... after i run the batch file from the extracted motochopper folder, it starts in terminal and says not found followed by daemon started and nothing happens.. i checked usb debug and the unknown source security boxes on the tablet and since im running windows 7, i ran the batch file as administrator. please anything will help kind of afraid to pull usb cable out of laptop
Click to expand...
Click to collapse
Have you installed the android SDK so you have the correct USB drivers? As long as command is not doing anything you can pull the cable. In your case it is waiting for a known device to bbe plugged in which isn't there as you don't have the right drivers.
i was trying to root my phone by following the guide from the FAQ
http://forum.xda-developers.com/showthread.php?t=895545
and i got to the step:
point it to where you downloaded the Android SDK (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
Click to expand...
Click to collapse
to install the usb driver and it didnt work as there is no google usb section of the SDK download.
I went and downloaded google-usb-drivers from google but my computer (win 7) still cant find anythign compatible.
what do i do?
EDIT: oops i didnt realize i had no title. Sorry. Feel free to add one if you want.
Also i did search for this. and was suprised to find no results... however there are lots of different search boxes to choose from on this site. I was pretty sure i chose the one for nexus s
Did you select the correct library path for Windows to find the driver on the computer??
Sent via Tapatalk 4 now Free
Did you select the correct library path for Windows to find the driver on the computer??
yes i did point to the folder. both the parent folder and the various inner folders.
it works fine in usb mode when the phone is on.
they are the official google usb drivers is there another source for my Nexus S.
also for reference it is under other devices - android 1.0
do i even need that step?
chico1st said:
Did you select the correct library path for Windows to find the driver on the computer??
yes i did point to the folder. both the parent folder and the various inner folders.
it works fine in usb mode when the phone is on.
they are the official google usb drivers is there another source for my Nexus S.
also for reference it is under other devices - android 1.0
do i even need that step?
Click to expand...
Click to collapse
is there another good guide i can follow? maybe there is a step i need to do before usb install? This guide assumes the usb drivers will come with the SDK but the only data the SDK tries to update is itself to SDK15 which the guide specifically mentioned not to do.
chico1st said:
is there another good guide i can follow? maybe there is a step i need to do before usb install? This guide assumes the usb drivers will come with the SDK but the only data the SDK tries to update is itself to SDK15 which the guide specifically mentioned not to do.
Click to expand...
Click to collapse
Try this...
Setting.Out said:
Try this...
Click to expand...
Click to collapse
that has the same issue
i cannot get usb connectivity in for the fast boot mode
from the rootkit the when i plug in my device even after installing the universal usb drivers i think windows is installing something else. Thus stopping me from accessing it while in fastboot mode
Not really sure what to do here. USB debugging enabled and everything all the guides are pretty easy to follow and have the same steps.
Google PdaNet, download and install it after attaching your phone to pc via usb. It will also install device driver... I think it is 'android 1.0' driver issue...
Sent from my Nexus S using XDA Premium 4 mobile app
Faizi Ch said:
Google PdaNet, download and install it after attaching your phone to pc via usb. It will also install device driver... I think it is 'android 1.0' driver issue...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
do i have the usb debugging mode on or off when i do this?
Faizi Ch said:
Google PdaNet, download and install it after attaching your phone to pc via usb. It will also install device driver... I think it is 'android 1.0' driver issue...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, usb debugging should be on...
chico1st said:
do i have the usb debugging mode on or off when i do this?
Click to expand...
Click to collapse
Sent from my Nexus S using XDA Premium 4 mobile app
nope didnt work
just so you know when i plug in the phone with debugging on i have 'android composite adb interface' installed
i have removed all the drivers from this computer previously. i can do it again though.
after installing pdanet i have 'android 1.0' pop up under other devices with an exclamation on it in device manager...i don't know if that is normal or not?
how do i know when this is working? i always try to run "oem fastboot unlock" which goes to "waiting for device" but will i no longer see the
USB control Init
USB control init end
??
It is the same issue of android 1.0 driver which i also faced in win8... You have to install android 1.0 driver manually from device manager
Sent from my Nexus S using XDA Premium 4 mobile app
Faizi Ch said:
It is the same issue of android 1.0 driver which i also faced in win8... You have to install android 1.0 driver manually from device manager
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so if i go to install the drivers from the pdanet folder if i tell device manager to search the winusb folder it says "cannot find drivers for your hardware" and if i dont search and say have disk - i chose 'android device' then the file in android_'winusb' file but it says "specified location does not have information about your hardware"
so i cannot get it to work.
This is on XP and win7 (2 different computers). I prefer the XP one for this though
Install nexus s root toolkit, then try to install driver from there.
http://forum.xda-developers.com/showthread.php?t=1766475
Or try this
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Faizi Ch said:
Install nexus s root toolkit, then try to install driver from there.
http://forum.xda-developers.com/showthread.php?t=1766475
Or try this
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
YAY somehow that last one worked thank you so much!!!
now a question. I have been following this guide which is from 2011 and the superuser code it recommends has a version for donught and froyo. My SNS is at 4.1.2 right now so can i use those super user scripts or should I use something else? or do i need that at all. I just want to put a new rom on my SNS.
thank you all i love you!
chico1st said:
YAY somehow that last one worked thank you so much!!!
now a question. I have been following this guide which is from 2011 and the superuser code it recommends has a version for donught and froyo. My SNS is at 4.1.2 right now so can i use those super user scripts or should I use something else? or do i need that at all. I just want to put a new rom on my SNS.
thank you all i love you!
Click to expand...
Click to collapse
Welcome!
First unlock your bootloader and install custom recovery. Then download latest supersu zip and install it via recovery
Sent from my Nexus S using XDA Premium 4 mobile app
Do not use these instructions anymore, Microsoft FINALLY fixed it, look here
....
HTC Driver Install Instructions
Go to Desktop, press Windows key + R, type in "shutdown.exe /r /o /f /t 00" and click OK.
Now click on Troubleshoot, then click Advanced Options then Start Up Settings.
Now click Restart. Let the PC restart and press either the number 7 or F7.
Download this and install it.
Wait for it to finish and then reboot and enjoy
Make sure you plug your phone into a USB 3.0 port EVERY Time when using Fastboot
....
If you have any problems with your USB 3.0 port afterwards and want to return it to original driver, follow these steps to return to your original driver
Press Windows key + R, type in "devmgmt.msc" and click OK.
Expand Universal Serial Bus Controllers.
The USB 3.0 port is listed as "AMD USB 3.0 Host Controller", double-click on it and select the Driver tab, click "Roll back driver" and select Yes.
Restart your computer
Thanks for sharing
Sent from my HTC One S using xda app-developers app
dd98 said:
Today I present to you a fix for fastboot on Windows 8.1 x64 on Intel and AMD machines with USB 3.0. This will NOT work on USB 2.0. This should work if you follow instructions exactly. I am not responsible if anything goes wrong and/or breaks. The Intel fix is NOT mine I'm just posting it here for convenience (Original Intel tutorial here)
All credits for the Intel solution go to the people here
Please hit the thanks button if it helped
Click to expand...
Click to collapse
im getting an error when extracting the amd fix zip
try 7zip or winrar to extract
dd98 said:
try 7zip or winrar to extract
Click to expand...
Click to collapse
Went nuclear and am installing Ubuntu as we speak... But as soon as it's done I'm going back to try this... I simply used whatever decompressor is in win explorer, even though I have both 7zip and winrar..... (Forehead smack) :silly:
i uploaded folder to mega so here you go: https://mega.co.nz/#F!C0gQSQCC!VixiF0rMM71qXVzXeWS5KA
dd98 said:
i uploaded folder to mega so here you go: https://mega.co.nz/#F!C0gQSQCC!VixiF0rMM71qXVzXeWS5KA
Click to expand...
Click to collapse
i truly appreciate you taking the time to do that for me.. truly!
however, since going to dualboot linux ive solved all those problems... have new ones now though
No radio, no firmware it seems... have a rom that boots but no way to connect..
Achieved S-OFF trying to fix it but no... nothing works... should i be using a sense rom?
thanks again!
you shouldnt need a sense rom, why dont you download amd fix.zip in ubuntu, extract it and move the files to your windows partition and then try to fix your usb then try running an ruu
try to fix adb on linux try this
1. Open terminal
2. type this: sudo gedit /etc/udev/rules.d/51-android.rules and hit enter
3. considering your phone is htc type in the following on the text editor window: SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
4. save the file and restart your computer
or if this didnt work try this: http://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
Morning gents,
Got my ONE yesterday and obviously trying to unlock when I hit this roadblock. I tried the intel fix above earlier this morning and last night. I was able to get the intel drivers to take, but lost all of my usb ports in the process and had to roll back. As soon as I accept the first intel driver for the eXtensible controller, all peripherals are dead. Am I missing the obvious here??
I've spent more time trying to get my old pc (with Win 7) up and going than trying to fight 8.1 into submission. Naturally the HDD on that unit is dead now. CURSES!
What is the forecast for a solution on this? Is it a windows update or just waiting for an HTC driver update?
Thanks for any guidance.
thanks a ton worked wonders :laugh:
Microsoft knows about this, but doesn't seem willing to provide a general fix. Ultimately the problem is that Microsoft added an extra validation to device registration that HTC devices don't seem to honor. They're releasing an update to fix particular devices, but we don't yet know if end users will be able to edit the white list.
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
Sent from my One S using xda app-developers app
I have windows 8 32 bit. I would like to know if i will have problem when i will update windows to 8.1 32 bit. My computer have only usb2.0 ports
The problem exist only with usb3.0 port or i wil have it also with 2.0?
thanks
The problem exists with USB 2.0 ports as well. The reason that the "fix" posted works for USB 3.0 ports is because it uses Intel's USB 3.0 drivers for Windows 8 to work around the problem. There's also "fixes" floating around that involve rolling back to Microsoft's Windows 8 USB drivers to make it work.
If you don't have another PC that you can use to do things in fastboot, stick with Windows 8 until a proper fix is available.
Thanks... Finally I can Fastboot on Win 8.1... :good:
I can't install the driver update...getting an error that states "The system cannot find the file specified".
are you sure you read the note at the start and followed the instructions EXACTLY
dd98 said:
are you sure you read the note at the start and followed the instructions EXACTLY
Click to expand...
Click to collapse
The only thing I did any differently was to download the files before the reboot. I can't imagine that makes a difference but please correct me if I'm wrong. I validated all aspects of the initial note, still no luck. Again, I'm trying the AMD fix.
Likeachampion3 said:
I can't install the driver update...getting an error that states "The system cannot find the file specified".
Click to expand...
Click to collapse
Same problem here
I know there are multiple fixes out there for getting Windows 8.1 to detect HTC phones while in fastboot mode, but some are dependent on whether you have an Intel or AMD processor and USB 2.0 or 3.0. This is the latest fix, and should work on all types of PCs and HTC phones. It worked for me on my computer with Windows 8.1 x64, Intel processor, and USB 2.0.
This is a repost of a thread by @izi501 in the Wildfire S forums; I just wanted to help spread the word. Credit goes to Auth from 4PDA and @niks255.
The issue has something to do with the BOS descriptor in Windows 8.1. It has been fixed in update rollup 2967917.
Instructions:
1. Install update rollup 2967917 for Windows 8.1.
- To check if you have the update installed already, go to Control Panel > Programs and Features > View Installed Updates > type "KB2967917" in the search box.
- If you don't have the update installed, open Windows Update to install it.2. Download the attached file Fastboot.reg.txt and change the extension to Fastboot.reg.
3. Right click on the Start button and choose Command Prompt (admin). Then type "regedit" and press enter.
4. Go to File > Import > choose Fastboot.reg.
That should be it; Windows 8.1 should now be able to detect your phone when in fastboot mode!
Yes it will fix this issue for all PC's. Read about it here http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'm wondering why my reg file works for One S. Your device must have a different code, so it means a different registry key. Did you check it for yourself?
niks255 said:
Yes it will fix this issue for all PC's. Read about it here http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'm wondering why my reg file works for One S. Your device must have a different code, so it means a different registry key. Did you check it for yourself?
Click to expand...
Click to collapse
I wasn't aware that the reg file was supposed to be device-specific. I didn't check for codes specific to the One S, but I used your reg file and it worked fine for me. I don't have the phone anymore, so I can't check. Maybe someone else can verify the registry keys.
Anyway, thanks for the fix!
Sent from my OnePlus One using Tapatalk
It works.
Thanks you
You saved my day
THANK YOU VERY MUCH, SIR !!!
Is this for all htc devices?
EDIT: nvm it worked!!!
KkdGab said:
Is this for all htc devices?
EDIT: nvm it worked!!!
Click to expand...
Click to collapse
it should work for every single android device having problems with fastboot
Works on Windows Technical Preview as well!!
dr3amsindigital said:
i know there are multiple fixes out there for getting windows 8.1 to detect htc phones while in fastboot mode, but some are dependent on whether you have an intel or amd processor and usb 2.0 or 3.0. This is the latest fix, and should work on all types of pcs. It worked for me on my computer with windows 8.1 x64, intel processor, and usb 2.0. I have a s4 one s; i'm not sure if this works with s3.
This is a repost of a thread by @izi501 in the wildfire s forums; i just wanted to help spread the word. Credit goes to auth from 4pda and @niks255.
The issue has something to do with the bos descriptor in windows 8.1. It has been fixed in update rollup 2967917.
instructions:
install update rollup 2967917 for windows 8.1
to check if you have the update installed already, go to control panel > programs and features > view installed updates > type "kb2967917" in the search box.
if you don't have the update installed, open windows update to install it.
download the attached file fastboot.reg.txt and change the extension to fastboot.reg.
right click on the start button and choose command prompt (admin). Then type "regedit" and press enter.
go to file > import > choose fastboot.reg.
that should be it; windows 8.1 should now be able to detect your phone when in fastboot mode! This will probably be one of my last posts here. I needed this fix to restore to stock, since i just sold my phone (i've moved on to the oneplus one). Thanks to all the devs out there that have made the htc one s so great!
Click to expand...
Click to collapse
perfect
thanks its running:laugh:
thanks so much, it works great!!
Thankyou
I read lots on this forum, but I signed up just so I could say thank you so very, very much for this post! I spent about 12 hours straight trying to get the fastboot driver to work for my HTC Sensation which I wanted to unlock and upgrade. I read lots and lots and lots of posts and tried out lots of suggested fixes but this was the only thing that worked and it was delightfully simple, even though I'd never made any changes to the registry before. I am forever in your debt!
thanks so much for this. it worked for my at&t htc one x
Been wanting to update my HTC One Mini and couldn't cause of this one fastboot fix, thanks so much!!!
dr3amsINdigital said:
I know there are multiple fixes out there for getting Windows 8.1 to detect HTC phones while in fastboot mode, but some are dependent on whether you have an Intel or AMD processor and USB 2.0 or 3.0. This is the latest fix, and should work on all types of PCs. It worked for me on my computer with Windows 8.1 x64, Intel processor, and USB 2.0. I have a S4 One S; I'm not sure if this works with S3.
This is a repost of a thread by @izi501 in the Wildfire S forums; I just wanted to help spread the word. Credit goes to Auth from 4PDA and @niks255.
The issue has something to do with the BOS descriptor in Windows 8.1. It has been fixed in update rollup 2967917.
Instructions:
Install update rollup 2967917 for Windows 8.1
To check if you have the update installed already, go to Control Panel > Programs and Features > View Installed Updates > type "KB2967917" in the search box.
If you don't have the update installed, open Windows Update to install it.
Download the attached file Fastboot.reg.txt and change the extension to Fastboot.reg.
Right click on the Start button and choose Command Prompt (admin). Then type "regedit" and press enter.
Go to File > Import > choose Fastboot.reg.
That should be it; Windows 8.1 should now be able to detect your phone when in fastboot mode! This will probably be one of my last posts here. I needed this fix to restore to stock, since I just sold my phone (I've moved on to the OnePlus One). Thanks to all the devs out there that have made the HTC One S so great!
Click to expand...
Click to collapse
After hours of researching on how the f*ck I can make fastboot work for my old Desire S, this did the trick. A million and more thanks for you.
OMG, finally I can connect my htc one to win8.1.
Million thanks!
Man, I wish I have found your post 3h ago ) Thanks to your reg file now I have fastboot working on Win 8.1
Respect, dr3amsINdigital !
vertycall said:
Man, I wish I have found your post 3h ago ) Thanks to your reg file now I have fastboot working on Win 8.1
Respect, dr3amsINdigital !
Click to expand...
Click to collapse
link not working brother
sivahariprasad said:
link not working brother
Click to expand...
Click to collapse
What link? Everything works for me.
dr3amsINdigital said:
What link? Everything works for me.
Click to expand...
Click to collapse
I am not able to download it. The text file just opens inside the browser.