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
Related
Hi,
My name is Joe aka AndroidSamurai.. I will be releasing more guides and media content in the weeks to come.
I'm currently very busy with "life events(new baby)" and apologize for my absence.
I will be updating this post since it was my original with a new guide updated to new SDK and Android methods.
Thanks again,
AndroidSamurai
Android4D Inc
<golf clap>
Well done.
</golf clap>
What do i do if the new hardware device notification doesnt pop-up ? NM i got it. Thanks for the writeup
@King_tee: Assuming windows, you follow the following steps.
1. Start > Control Panel > System.
2. Hardware > Device Manager
3. Click on the last icon below the File menu. It should correspond to "Scan for Hardware Changes."
If that doesn't work, try unplugging / replugging USB cable, different USB cable, restarting phone, restarting computer, etc.
If you never see the notification, navigate to the Device Manager(inside "System" in the control panel in XP and inside Device Manager on Vista).
You will see ADB Android Device at the top of the list with a Yellow Icon beside it meaning the device is not working. Right-click on the device and select "Update Driver".
Follow the dialogs that pop-up and navigate to where the unzipped drivers are at...
You should be good to go from there...
ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?
devildogg2001 said:
ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?
Click to expand...
Click to collapse
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
I dont know if thats the problem because when i plug it in, it doesnt show up as a notification, and when i go to the device manager it shows the little yellow triangle.. I'll look again. Thanks for the quick reply though. I am no expert in linux, but i have it installed, let me see if i can figure it out there..
tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?
devildogg2001 said:
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?
Click to expand...
Click to collapse
Downloading
http://developer.android.com/sdk/1.1_r1/index.html
Installing
http://developer.android.com/sdk/1.1_r1/installing.html
Found through Google...imagine that.
as well as what xyrcncp said can you you can download it and just mv ~/Desktop/sdk/tools/adb /usr/bin/adb abd you should be able to run the adb commands from any directory. not too hard to cd to the correct directory but i personally don't like to type cd ~/Phone/tools/android-sdk/tools every time cause i tend to make typographical errors. let me know how it worked but you shouldn't have any problems at all
umm no offense but your writing a tutorial for people that are not sure on how to do this, so you must assume that they do not know how to run an executable file...... write yourself a better tutorial without actually bashing the self esteem of some people... tutorials are positive not negative. I already know all of this but still... dont degrade someone due to the fact they dont know how, thats the whole point of writing your tutorial. Nothing should have been left out (including how to run a .exe .com or .bat
" (If you do not know how to install a windows executable file, please kill yourself now! ) "
this isnt honestly written with any hatred towards you, it was a good tutorial. Just might want to think about how you write it next time.
The "bashing" comments in my tutorial are directed towards the people with a true sense of humor. My tutorial was written to tell you how to simply complete a task and not to make you feel better about yourself. I do not get pleasure in abusing people's self esteem nor do I enjoy putting people down.
Just because you got a little sand in your crack does not mean you need to come in a very honest and informative thread and start bashing the people who are bending over backwards to help everyone out.
The reason I created this "tutorial" in the first place was because all the other threads are full of "start searching and stop asking so many damn questions" comments.
So start looking in the mirror when you wake up in the morning and stop saying "My, I think I will run over to good ole' XDA and be an @$$ to everyone today".
I am sincerely sorry that a little sense of humor has caused so much hatred in my thread. Please contact the forum moderators and see if the think my tutorial is so hateful.
lol i dont see any hatred but anyway when i download the adb driver when extracting it says unknown method
@ Nabzilla1990
Are you using Windows or Linux?
Are you using the built-in Zip tool or 7-zip from the links I provided?
Are you using a 32 or 64-bit OS?
using the same operating system as you 64bit vista ultimate sp1 and using winrar to extract
Try using 7-zip man, I have been using it for 3 yrs now.
Basically what I am saying is that everything in my guide is guaranteed to work.
Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt.
it worked with 7-zip thank you and also want to add if it doesnt work for some people plug in ur phone and update the usb mass storage with the usb driver from here and it should work i had that problem earlier
Okay, so I did everything and got up to run cmd, when I type in the cd C:\android-sdk-windows-1.1_r1\tools it says not a specififed folder, but when I type it without the \tools it doesnt work. can anyone help?
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!
haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!
bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.
I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid
I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!
Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!
Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work
matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!
thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!
I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box
I have erased the contents of the phones internal USB storage. Now I notice that I cant mount to my PC.
Anybody know what happening or had same problem
Have you already tried formatting with CWM?
Perhaps this thread contains some useful information for you.
maksymillian said:
I have erased the contents of the phones internal USB storage. Now I notice that I cant mount to my PC.
Anybody know what happening or had same problem
Click to expand...
Click to collapse
I know this is a long shot but go to your dialer and input *#*#8778#*#* and make sure it looks like this pic. I fool with QPST and other things and sometimes forget to change the settings back to PDA and it will not mount. Long shot but what the hey...
alnova1 said:
I know this is a long shot but go to your dialer and input *#*#8778#*#* and make sure it looks like this pic. I fool with QPST and other things and sometimes forget to change the settings back to PDA and it will not mount. Long shot but what the hey...
Click to expand...
Click to collapse
Typed it in and got nothing. Using the android dialler when I pressed the last * the dialer cleared and did nothing.
Just installed the SDK so I could use (hopefully) ADB. When trying to install the Google driver rev4 windows says that rev 4 is no better than the one currently installed.
Also when I connect to the PC it says that the USB device is not recognised either.
I reckon my next thing to try flashing a new Rom via ROM manager.
well that didnt work in fact it has got considerably worse. I used ROM manager to download and install a new rom but didnt install the Gapps how daft do I feel now cos all I got is version of Blandroid running with no Android Market access to download ROM Manager.
I can access my WiFi network so I thought I would simply visit XDA via the mobile browser and download a fresh version of CM7 and then re-flash via ClockworkMod . However all I get is download fail error. I guess it doesn't know where to save the file.
So to recapp I have the following
a Nexus S (running Blandroid ROM)
a Win XP laptop that does not recognise my Nexus S (therefore cant install the Google driver to use ADB)
The Nexus S recovery is ClockworkMod and accessible.
I cannot accept that it is bricked (not just yet anyway)
I have another Laptop with Ubuntu installed. Will this help me in anyway to find a fix. I am not that experienced in Linux unfortunately.
1
i have the same problem. only thing you can try is.
pull out battery. let something metal touch the usb conecter .conecting the metal to a unload source(for static electricity.)
wait couple of hours,and try again.
if that didnt work.
2
open your nexus.
unplug all cables and screws from the main board.
again touch the usb conecter with something metal that has a ground source.
and try again.
the last step worked for me the 1st time pluging it in after i did that.
after that. usb didnt work again.
it probably has to do something with the usb phone charger and static electricity.
but i havent tested it.
will give that a try when I have a bit more time.
In the meantime I have been setting up ADB on my other laptop running Ubuntu 11.04. But unfortunately the Nexus S didnt register on the OS either. I thought you didnt need additional drivers for Linux only windows! I am really puzzled now as I thought the Linux option would have allowed me to flash a different ROM other than Blandroid (which isnt bad its just I dont have the Gapps installed)
maksymillian said:
will give that a try when I have a bit more time.
In the meantime I have been setting up ADB on my other laptop running Ubuntu 11.04. But unfortunately the Nexus S didnt register on the OS either. I thought you didnt need additional drivers for Linux only windows! I am really puzzled now as I thought the Linux option would have allowed me to flash a different ROM other than Blandroid (which isnt bad its just I dont have the Gapps installed)
Click to expand...
Click to collapse
you still have wifi/3G and CWM or bloothoot?
download the Gapps zip. put it on dropbox or any hosting site.download it trough your mobile browser and flash it trug CWM.
or use blutethoot to download it.
might be a short fix.until you get USB to work.
(this is how i do it cuz my usb doesnt work.)
I did try that but for some reason after stating that the download had started - Download Unsuccessful was displayed in the notification area. As useual I open a door only to find a brick wall on the other side.
In the meantime I am back with my HTC Hero.
Thanks for helping anyway!
maksymillian said:
I did try that but for some reason after stating that the download had started - Download Unsuccessful was displayed in the notification area. As useual I open a door only to find a brick wall on the other side.
In the meantime I am back with my HTC Hero.
Thanks for helping anyway!
Click to expand...
Click to collapse
try difrent download solutuins.
seeing you have HTC here.why not tranver your zip trug your hero to your Ns?(with bluethoot)
boy, i hope you haven't started tearing your phone apart yet...
since you still have access to cwm: try to format your sdcard with it. looks like you haven't done that yet.
I would try to uninstall all drivers and associated programs on your PC. Then reinstall the drivers. Windows can be very finicky as you know. Also try PDANET drivers.
ghost010 said:
try difrent download solutuins.
seeing you have HTC here.why not tranver your zip trug your hero to your Ns?(with bluethoot)
Click to expand...
Click to collapse
10 out of 10 - I just got my market back . downloading rom manager will shortly be back on CM7.
USB connection still not working yet but at least I got my account back on the NS and so the phone is usable
wild1z said:
I would try to uninstall all drivers and associated programs on your PC. Then reinstall the drivers. Windows can be very finicky as you know. Also try PDANET drivers.
Click to expand...
Click to collapse
The NS wouldn't connect to laptop with Ubuntu running. I am beginning to think that I have a faulty micro USB port.
Ill try the pdanet drivers later tonight - are they different from the google rev 4 drivers?
maksymillian said:
The NS wouldn't connect to laptop with Ubuntu running. I am beginning to think that I have a faulty micro USB port.
Ill try the pdanet drivers later tonight - are they different from the google rev 4 drivers?
Click to expand...
Click to collapse
Same PC with dual boot? Yeah, try another cord and a another PC. The fact that you plugged it in and it's recognized in some way in the tray says something is fubar. I just don't know if it is the phone though. Best of luck.
Nah, different laptop and different cable. Hope that it charges OK. Gonna have to get a WiFi file transfer app working to move files to and from.
glad to help out :3
there are allot of people that have this USB isue and its HW NS related. nothing we actually can do about it.plus it also happens after changing kernels and roms(i supose) overclocking might be 1 of the reasons thus the voltages not being original.
btw,sorry for my half assed english x3
Double check the modem/pda settings mentioned in post #3. Should be set to pda to see the files on the SD.
Moritzio said:
Double check the modem/pda settings mentioned in post #3. Should be set to pda to see the files on the SD.
Click to expand...
Click to collapse
Having the same issue. I tried that, no such luck.
My computer *did* connect at one point though... couldn't mount USB storage (wasn't prompted) but it did ask for a driver, and currently has a Samsug USB one installed. It won't accept the SDK driver (not 64-bit capable? Or NS4G? Idk...)
Moritzio said:
Double check the modem/pda settings mentioned in post #3. Should be set to pda to see the files on the SD.
Click to expand...
Click to collapse
I got nothing when I entered *#*#8778#*#*. I simply typed it in using the keypad on the dialer. Is there something else I should be doing?
Some of you are like myself are having trouble getting the fastboot drivers to install correctly on Windows 8. The device is always showing with an exclamation mark on it in device manager, and 'fastboot devices' shows nothing. There are other threads out there on XDA which detail methods, such as KidCarter93's method here which show you how to force install the Win7 fastboot drivers on Windows 8.
The problem is this doesn't work for some of us, and I suspected it was something to do with my Ultrabook only having USB 3.0 ports, since my other Win8 x64 box with USB 2.0 ports has no such issue.
I had a poke around and found this site here which shows you how to remove the Microsoft USB 3.0 drivers and instead install the Intel USB 3.0 drivers on Windows 8.
After following the procedure carefully, I can confirm this fixes the problem for me on Windows 8! After successfully installing the drivers, fastboot started working immediately for me.
Step 1: Install the HTC drivers from the standard HTC Sync Manager (Win7/8). If you are on Windows 8.1, please use the HTC Drivers linked later in this thread here (thanks Kardus!)
Follow KidCarter93's method to manually install the Win7 drivers. Read Here. Or you could manually install the latest drivers being maintained in this thread here. I tried them all before arriving at a fix, so my system isnt exactly clean, but I'm sure you could try one or the other as the important part is step 2.
Step 2: Hit up Plugable's site which has a great step by step explanation of how to install the Intel USB 3.0 drivers. Full credit to Jerome for writing the guide, and Ekko who did the original work.
UPDATE: As per Coolookoo's discovery (Thanks Coolookoo!), if you are using a 4th Gen Haswell based Intel CPU, then you need to get the Intel USB 3.0 drivers from this link here instead of the link at Plugable's site. You will however still need his modded .inf files.
Step 3..... Profit
You should now have fastboot working flawlessly on Win8 x64 with USB 3.0, and as a added gift some older 'incompatible' USB devices that you may own should also now work under Windows 8.
Would love to hear some feedback on how this went for you.
If it helped, please hit the Thanks button!
Thanks!!
Hey you are a star. This has been annoying me for weeks now on my usb 3 laptop. can confirm that following your guide worked perfectly and now fastboot recognised perfect.
Thank you
You sir are the man !, I was beginning to think nobody else was having the same issue as me .I've been resorting to using my laptop's usb 2 port to do all my fastboot stuff, sine my desktop has only usb 3's , and this quick fix has made the four usb 3's on the back of my desktop work flawlessly. So yeah thanks for that mate.
Now just to get the two side usb 3 ports working for easier access since they run of a Texas instruments controller.
Sent From My Tricked Out HTC One
---------- Post added at 12:56 AM ---------- Previous post was at 12:16 AM ----------
Never mind, I just downloaded the texas instruments usb 3 driver for windows 7 from the Dell site, extracted the files and left clicked and installed both ini files, and viola, they're working.
Thanks again for posting this, it's much appreciated
Sent From My Tricked Out HTC One
I was able to find this fix as well and I can confirm that it works great. I am using the Surface Pro for most of my flashing and don't have a USB 2.0 port. I was so glad to find this.
That's great guys really glad this is working for you. Thanks for the feedback!
@salada2k - thanks for posting this... i have a Dell XPS 12 i7 ultrabook and this fix worked for me as well....
Great post, thank you!
While I'm not going to mess with the 3.0 drivers (seems there are advantages to using built-in stack for supported devices), this did at least point me in the direction of using my 2.0 ports instead for fastboot, which works great.
Thanks again!
JDAapps said:
Great post, thank you!
While I'm not going to mess with the 3.0 drivers (seems there are advantages to using built-in stack for supported devices), this did at least point me in the direction of using my 2.0 ports instead for fastboot, which works great.
Thanks again!
Click to expand...
Click to collapse
It's my pleasure! p.s. Which advantages are you referring to using the built in stack?
salada2k said:
It's my pleasure! p.s. Which advantages are you referring to using the built in stack?
Click to expand...
Click to collapse
Not sure. The plugable.com page you linked said something about some benefits (like uasp?) but didn't look into it any, just switched over to my 2.0 ports.
Well i gave it a go, still didnt work. adb recognizes my HTC One when it is booted into the regular system, but as soon as it goes into fastboot it is not recognized.... Any other suggestions?
same
salada2k said:
Some of you are like myself are having trouble getting the fastboot drivers to install correctly on Windows 8. The device is always showing with an exclamation mark on it in device manager, and 'fastboot devices' shows nothing. There are other threads out there on XDA which detail methods, such as KidCarter93's method here which show you how to force install the Win7 fastboot drivers on Windows 8.
The problem is this doesn't work for some of us, and I suspected it was something to do with my Ultrabook only having USB 3.0 ports, since my other Win8 x64 box with USB 2.0 ports has no such issue.
I had a poke around and found this site here which shows you how to remove the Microsoft USB 3.0 drivers and instead install the Intel USB 3.0 drivers on Windows 8.
After following the procedure carefully, I can confirm this fixes the problem for me on Windows 8! After successfully installing the drivers, fastboot started working immediately for me.
Step 1: Install the HTC drivers. Follow KidCarter93's method to manually install the Win7 drivers. Read Here. Or you could manually install the latest drivers being maintained in this thread here. I tried them all before arriving at a fix, so my system isnt exactly clean, but I'm sure you could try one or the other as the important part is step 2.
Step 2: Hit up Plugable's site which has a great step by step explanation of how to install the Intel USB 3.0 drivers. Full credit to Jerome for writing the guide, and Ekko who did the original work.
Step 3..... Profit
You should now have fastboot working flawlessly on Win8 x64 with USB 3.0, and as a added gift some older 'incompatible' USB devices that you may own should also now work under Windows 8.
Would love to hear some feedback on how this went for you.
If it helped, please hit the Thanks button!
Thanks!!
Click to expand...
Click to collapse
Working well
thank s a lot
i have done very steps, but still my phone is not recognized in fastboot mode
if i type ADB DEVICES when phone is booted it shows in attached devices, then i do ADB REBOOT BOOTLOADER, but once in fastboot usb, is no more recognized by pc
(installed intel drivers and followed the guide)
but the pc recognize My HTC also when in fastboot.. lol
Helpful topic, thanks a lot
salada2k said:
Some of you are like myself are having trouble getting the fastboot drivers to install correctly on Windows 8. The device is always showing with an exclamation mark on it in device manager, and 'fastboot devices' shows nothing. There are other threads out there on XDA which detail methods, such as KidCarter93's method here which show you how to force install the Win7 fastboot drivers on Windows 8.
The problem is this doesn't work for some of us, and I suspected it was something to do with my Ultrabook only having USB 3.0 ports, since my other Win8 x64 box with USB 2.0 ports has no such issue.
I had a poke around and found this site here which shows you how to remove the Microsoft USB 3.0 drivers and instead install the Intel USB 3.0 drivers on Windows 8.
After following the procedure carefully, I can confirm this fixes the problem for me on Windows 8! After successfully installing the drivers, fastboot started working immediately for me.
Step 1: Install the HTC drivers. Follow KidCarter93's method to manually install the Win7 drivers. Read Here. Or you could manually install the latest drivers being maintained in this thread here. I tried them all before arriving at a fix, so my system isnt exactly clean, but I'm sure you could try one or the other as the important part is step 2.
Step 2: Hit up Plugable's site which has a great step by step explanation of how to install the Intel USB 3.0 drivers. Full credit to Jerome for writing the guide, and Ekko who did the original work.
Step 3..... Profit
You should now have fastboot working flawlessly on Win8 x64 with USB 3.0, and as a added gift some older 'incompatible' USB devices that you may own should also now work under Windows 8.
Would love to hear some feedback on how this went for you.
If it helped, please hit the Thanks button!
Thanks!!
Click to expand...
Click to collapse
You sir, are my hero
Wow, awesome, this worked like a charm on my HTC One! Was going nuts with this, can't believe the problem was with the USB 3.0 ports! Thanks man, really :good:
Thanks for this thread it pointed me in the right direction. I have the Renesas Electronics USB 3.0 eXtensibile Host Controller in my Dell Laptop. I fixed the fastboot issues by installing the Intel drivers from:
http://www.intel.com/support/chipsets/usb3/sb/CS-033082.htm
I just ran the installation wizard which updated the driver and corrected the fastboot issue.
Worked like a charm for my HTC one .. although gotta say this made me appreciate my macbook even more, no need for all this driver nonsense ..
I tried following the linked guide, but when I rebooted after installing the first driver, there was no "unknown device" shown under device manager. Dos anyone know what would cause that, or how I could get that to show up?
Or just use linux and everything to do with android just works, no issues, regardless of hardware or usb port type... I just don't even bother trying to do any of this from my win system anymore
Sent from my HTC One using xda premium
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.