Related
Afternoon all,
I debranded my desire using an RUU flashing it to 1.15.405.4 but now HTC Sync isn't recognizing the phone, it is just coming up as 'Disconnected' yet it is still being recognized as a removable disk when in disk drive mode so it can't be a USB brick.
I can't get ADB working either since the phone isn't being recognized so it isn't installing the required ADB drivers for the phone. I can't go back to my stock firmware either because USB Debugging has to be installed correctly for the RUU to run. I had no problems initially, but after upgrading to this ROM I have seemed to have this problems.
I want to root, but if I can't have access to the ADB a root would not be possible? Please correct me if I'm wrong.
If anyone has any advice I would be glad to hear it. Thanks
I have the same problem with HTC Sync - just can't get it to see the phone. Hopwever to get ADB working make sure you have USB Debugging turned on in the settings under Applications / Development / USB Debugging.
sbdags said:
I have the same problem with HTC Sync - just can't get it to see the phone. Hopwever to get ADB working make sure you have USB Debugging turned on in the settings under Applications / Development / USB Debugging.
Click to expand...
Click to collapse
Thanks for the reply.
I have USB Debugging turned on in the menu, but it seems to not be recognized. I have done all the command prompts in cmd, but it doesn't list the device under ADB devices. Hmm.. :/
I had the same problem after all my updates, that worked for me, restart your pc and restart the phone, leave it plugged in by usb, it worked every time for me, hope that will help.
I restarted my computer then phone - leaving the USB plugged in, but it's still not being recognized. Am I doing the steps the wrong way round?
It's annoying because this is stopping me from rooting at the moment and I really want to get my hands on froyo!
Thanks
I'm not to sure I'm a newbie to all this, what I did was tun the phone and pc off, turn the phone back on first then turn the pc on as soon as the pc detects the phone put the phone on sync, and so far it always worked for me after a update, maybe you have a different problem maybe a proper dev can help you out.
fredhd said:
I'm not to sure I'm a newbie to all this, what I did was tun the phone and pc off, turn the phone back on first then turn the pc on as soon as the pc detects the phone put the phone on sync, and so far it always worked for me after a update, maybe you have a different problem maybe a proper dev can help you out.
Click to expand...
Click to collapse
Tried the above a couple of times, no luck. Thanks for the help though.
Hope someone knows a fix cause I'm eager to root my phone and get onto some froyo goodness! haha
Cheers
The HTC drivers are pretty damn bad with regards to Sync. I always do adb-related work in recovery for that very reason - I can almost never get Sync working.
Can you get adb working in recovery?
Ok here is what worked for me
1- Uninstall the HTC sync and the HTC drivers
2- open MSConfig and disable all non microsoft services
3- restart windows
4- install HTC sync
5- Connect the phone and it will connect
6- re enable the disabled services and restart Windows
Does it work normally every time after that, or do you have to go through that jazz every time?
Hopefully it works every time - I'll give that a shot if so.
Hi,
The ADB isn't being found in Command prompt it outputs 'list of devices' but there is no device listed. All drivers are installed as well.
I will try the above and see if that helps.
Cheers
Hi Matey, I had this exact same problem after rooting my desire last night - basically check task manager for any adb processes and kill em, if that still doesn't work re-run the htc sync install and select repair and it'll be ok again.
I had to do this on my home laptop which I used for the root, but also on my works laptop even though this was turned off and not used for rooting at all so think it's an issue with htc sync not seeing the same phone, but at the same time seeing the same phone and getting confused.....
so - reinstall using repair and reboot and all should be well matey...
Thanks for the help guys.
I had to reinstall Windows for other reasons, and after I reinstalled HTC Sync it still wouldn't recognize the phone but ADB is working so I can do all the shell commands.
Cheers for all the help.
I take my above post back. The phone is now not being recognized by ADB, it seems to have occurred after I have turned my computer back on. Windows installed some updates and I'm wondering whether they might have had an affect.
Anyone had any experiences in the same sense?
Ok Guys heres what I,e got
Firmware ver 2.1-updat 1
Baseband ver 32.36.00.28U_4.06.00.02_2
Kernal ver 2.6.29-b7e82785
Build Num 1.19.707.7 CL171460 release keys
Software num 1.19.707.7
Browser ver Webkit3.1
Ok. now I,ve spent probably about 24 hours during the past three days trying to root the thing. made a gold card after about 10 attempts, have tried and tried to root the thing, have tried 3 or 4 different methods, most fail becase either I loose USB connection to the fone when navigating to Bootloader. From there on in she all over rover. Actually I,m not sure I have the right ROM to add to the fone, but I,d really like to get to the point where it asks for the rom. I,ve aged about 10 years since embarking on this venture, and still the thing is as bought. The phone isnt branded, bought it thru ebay from Hong Knog I think, has asian english which aint no fun. Have loaded Morelocal2 on but it still aint nice.
Can someone who has rooted one of these with similar ver software email me whith there secrets please before I go totally insane or really root the thing against a brick wall.
Cheers Guys.
Try the tutorial in my sig (second link). You should have no problems rooting with that.
It provides you with the required downloads for rooting. Just download and flash your ROM of choice in place if the 'rootedupdate.zip' file.
Please state any errors you recieve while attempting root.
-------------------------------------
Sent via the XDA Tapatalk App
Rooting Desire
I,ve tried your link, now my wife has been helping me, she cant get it to install either, I,ve even got to the stage of watching in Device manager what happens when it goes into Bootloader/recovery mode. the link between the HTC and the computer breaks,SOOOOOOO as I,ve stated before I have a very good understanding on HOW to root the thing, its just that for some reason I cant keep the phone connected thru the USB . I think this is the only prob I have. Something else that also happens is I get a Customer ID failed message half way thru step 1
What ever system I try to use to root this thig thats where I end up.
Wifie is going to try one more time, this time we are going to try the fone with a default startup to look at the disc not the HTC Syn.
Please keep trying to help guys
Rooting Desire
OK Heres the wifie update,
Screen says,
Pushing update file to device
error: device not found
error: device not found
Now wipe and apply rootupdate.zip from the recovery image menu.
Error: device not found
[email protected]:/mnt/cdrom/root$
So there we go guys, thats it in a nut shell
Try using the TinyCore method, I had all sorts of issues in Windows but this worked first time...see this post...
http://forum.xda-developers.com/showpost.php?p=6710081&postcount=2
obviously download the right Live CD for your bootloader
Also if you are trying to root in windows, make sure you have HTC Sync installed.
Desire root
Yep, I,m using the tiny core app followed the instructions in the link as advised. Still loses connection at bootlader/recovery
When you get back to Bootloader, how long do you wait before trying to run? As I normally leave it 5 or so seconds and then it's fine...if you do it too quick it'll say no device found
Which TinyCore CD did you download? I'm assuming you have HBOOT 0.80 on your device before you started?
Rooting a desire
An answer to your question, I,m using the tcl_r4_desire_hb80 file. when you ask how long are you waiting , I reckon it taks me more than 5 seconds to type in sudo ./step2.sh
I could try it again and wait longer.
Desire a rooted phone
Nope sorry guys, I,ve tried god dam everything, still wont connect afetr step 1 with tcl_r4_desire_hb80.
Somehow I need to be able to force a usb connection.
hey I tried this on Vista and XP, thought XP might be better. is there a stand alone app to force USB drivers when tcl_r4_desire_hb80 boots into termial screen
If you have done step 1, is it possible after failed attempts at getting into the recovery, you have usb bricked it?
Try switching it on normally and see if you have normal usb connectivity, and the sd card mounts and works fine?
socktug said:
If you have done step 1, is it possible after failed attempts at getting into the recovery, you have usb bricked it?
Try switching it on normally and see if you have normal usb connectivity, and the sd card mounts and works fine?
Click to expand...
Click to collapse
I too was thinking that there is a possibility of his device being bricked, especially when receiving errors indicating that the device cannot be found in recovery.
Rooting desire
OK, wondered that myself,
connected phone to PC, sync straight away with fone
reconnected it to pc in disk drive mode and connected, checked in My Computer and the disc drive was there with all my files.
Suppose that means everything there is ok to
OK if it isn't usb bricked then it's got to be a driver issue. My suggestion would be to follow the tutorial in the dev section and use tiny core linux.
Rooting desire
OK guys,,, so heres where I,m at, so far all info gained from you lovely people has been to no avail.
What I,m getting is this
In device manager I am watching what happens when the Desire goes from fastboot to bootloader. In bootloader I get "Android 1.0 with the yellow tiangle indicating it aint set up with drivers. In fastboot I get "My HTC" under Android USB Devices. now in either Bootloader or fastboot I,m only getting one or the other, and as I said, the triangle under "Android 1.0"
Now Ive gone to Android 1.0 and tried to add a driver, seemingly thers not a driver in the world that will work with Android 1.0. All driver in my Sdk dont work. The driver installer asks for a driver but wont except anything trown at it.
First, via your phone, go to Menu > Settings > Applications > Development and ensure the USB Debugging option is selected.
Try a different USB port.
I actually think you need to create a Gold Card even though you have stock rom 1.19.707.7
Try the Gold Card.
-------------------------------------
Sent via the XDA Tapatalk App
I have the exact same issue on win.7 64bit.
Try ignoring the no android 1.0 issue, continue to put your phone into recovery with the volume down and power buttons. Wait about 10 seconds after you see the black screen with red triangle, and then click on recovery windows.bat. Works for me everytime.
Windows takes it's time to see and install devices so it may be that you are trying things too quickly after connecting the usb lead.
Hello
Posted this over in Pauls MoDaCo forum as well but not had any replies yet so thought it best to try here as well.
I've bricked my Desire, phone loads up but the sim and sd card aren't recognised (though I can still use wi fi).
When connecting the phone to my PC (tried windows 7 and XP) the drivers fail to install and I get various faults like the device being recognised as android 1.0 usb to a Qualcomm device.
The phone is still rooted (I can install rooted apps from the market) however after following various unbricking guides I always get stuck at stage 2 (i.e. enable sd card), if the PC won't recognise the device how can i run the 'fastboot oem enableqxdm 0' command?
I've also tried running fastboot using a terminal app on the phone but it doesn't recognise fastboot, should i be in a specific directory on the phone when running this command?
Any help greatly appreciated.
Cheers
Have you tried using a different jab port? I had to use one at the back of my pc front ports wouldn't install drivers properly.
Sent from my HTC Desire using XDA App
You need to follow the guide on modaco for unbricking your device. You have the usb brick, and it can easilly be fixed.
Follow the steps religiously and you will be up n running in no time again.
I've followed the guide lots of time, it's not that long winded so it shouldn't be to hard to follow.
I get stuck on step two, using the fastboot command.
My PC and also tried laptop (Win XP and 7), different USB ports (front and back) but each time it attempts to load drivers and I end up with it either being recognised as an Android 1.0, Android Bootloader Interface or a Qualcomm device. I then run fastboot, and get the device not recognised error.
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
celticone said:
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
Click to expand...
Click to collapse
You don't need to get into recovery for this.
You have sdk installed, so boot your phone by pressing power while holding down the volume down button.
Use a command prompt on your pc and cd to the tools directory in the sdk. If the sdk is saved to the root of your C: drive on the pc you would type
Code:
cd C:\android-sdk-windows\tools
When in there type
Code:
fastboot oem enableqxdm 0
This will re-enable your sd card and allow you to continue.
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
celticone said:
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
Click to expand...
Click to collapse
It definitely sounds like the old usb brick problem, so that's a good thing! When you tried the commands were you booted into fastboot? When you connect the phone to the computer does the phone display change from saying fastboot to fastboot usb? I think thats what it should say, can't remember to be honest!
Have you tried another usb port, and a different cable too?
Edit: I'd also try rebooting the computer to ensure any running process etc are closed.
Got it fixed, final throw of the dice this morning I connected the phone to a Vista laptop and it was recognised straight away, so downloaded HTCSync then ADB tools on to the laptop and finally got the re enable command to work.
Jeez that took for ever, strange that Xp, Win7 and Linux PCs couldn't recognise the phone but Vista did.
Still got it sorted, thanks for the help.
No worries. Glad you got it sorted.
I have almost the same problem.
but with the legend.
SD is not recognized.
Can´t Call,
Can´t connect via USB.
Is there something I can do in the built in terminal in the ROM?
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App
EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...
perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes
Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.
Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.
Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...
What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.
try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.
Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever
It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.
buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip
No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.
**BUMP**
Anyone care to take a shot??
OK everybody I think I already know what is going to come from this but I'm putting it out there anyway to see if anybody else in this world has experienced anything like this and managed to resolve it. I'm assuming it's the boot-loader that is at fault here but maybe, hopefully I am wrong.
So a friend of mine has rooted and installed Cyanogenmod 7.1 stable on his HTC Desire (bravo - gsm) using the revolutionary method. It has been working fine except he had many issues getting any ADB drivers to install and work. I've resolved this issue using Koush's drivers. Good old Koush. File transfers work fine too so the USB itself is obviously fine.
The problem I am facing is that he couldn't and now I cannot for the life of me get HBOOT/Fastboot drivers to install. I've tried using Windows and Linux for this task. I'm assuming that all was well before considering the fact he rooted his device!
Now, please don't shout at me but maybe there is a fancy HTC mode like the Samsung download mode that can be used? It's been a while since using HTC and couldn't recall if there was or even if it would be on these early devices.
So....
In Linux I've done all of the 51android.rules stuff and it works with my Galaxy Nexus and Nexus One. I can also see the device in 'sudo lsusb'.
In Windows.... well.... it's Windows, what more can I say!
The device shows up in device manager as Unknown USB Device (Device failed Enumeration). Now I know that basically means that my device is technically buggered, over current, generally failed to connect etc. I've tried different cables, ports and computers!
So here is the boot-loader information:
Revolutionary (In the pink bar at the top)
S-OFF
HBOOT-6.93.1002
RADIO-5.11.05.27
Whether in Fastboot or HBOOT, when I plug the device in it flashes between Fastboot and Fastboot USB/HBOOT and HBOOT USB PLUG
after a few seconds it goes back to the USB unplugged state on the phone and Windows pops up USB devices not recognized and I get the device show up in device manager as mentioned above.
If I try to install any HTC or custom/universal Fastboot drivers thy all fail as does HTC sync.
I've tried suggestions in this post too - http://forum.xda-developers.com/showthread.php?t=2124360
I think that is everything I can provide. Let me know if you need anything else! Like I say, I think it's the boot-loader itself but would loved to be proved wrong!
Thanks in advanced everyone!
DeeToTheVee
Does connecting your phone as a storage device work?
Yes both storage mode and ADB work fine. ADB was a pain to get working though. Only the universal drivers from Koush worked on windows.
Sent from my GT-P1000 using xda app-developers app
[Q] Help
I have some problem ,
Still no work :/ My os Windows 8.1 x64 ,
Mobile ... , usb device not recognized. So sad i cant downgrade my hboot and still no work Fastboot…
I try disconnect all devices and try all usb port on my computer no work . . .device failed enumeration.
Htc sync cant find my phone. But storage is work fine. Any idea ? Solution ? please
Kasp3rsky said:
I have some problem ,
Still no work :/ My os Windows 8.1 x64 ,
Mobile ... , usb device not recognized. So sad i cant downgrade my hboot and still no work Fastboot…
I try disconnect all devices and try all usb port on my computer no work . . .device failed enumeration.
Htc sync cant find my phone. But storage is work fine. Any idea ? Solution ? please
Click to expand...
Click to collapse
Windows 8 has some problems with installing drivers. I used friends Windows 8 to root her phone and got the same message. With my Windows 7 it worked fine
thanks Yes , windows 8 is su*k but i have Windows 8 and8.1 --11 months but some things is worst (drivers now) i actually finished Bricked and Downgrade my phone (hboot) on Windows 7x64 everything is OK adb and fastboot working on
But i want do this thing on my deskop PC with Win8 Do you think it will ever be possible haha Mic*osoft =D
:good:
Theres a thread in desire general somewhere by @k3lcior and he had same problems with windows 8 but he found the solution (drivers etc) have a search for it or look at his profile then threads started by him. The solution is here somewhere
Try this: http://forum.xda-developers.com/dro...er-fix-windows-8-1-update-2-fastboot-t2831385