Hi buddies,
I created a new thread because I think this issue has not ever treated specifically. When I connect my Hero to my computer, i get USB charging only, and windows shows me the error "usb device not recognized". I tried in two windows 7 PCs, one with Vista, one with XP and one with Ubuntu Maverick, and the same problem. I think that no matter what operating system you try it, because the problem is not drivers, and that is not even recognize the device. Before I was with Floyo and the flykernel 11c. I changed the kernel, I tried several roms (with and without Sense) and nothing ... so I tried it in recovery, and nothing ... and I can not mount as USB Mass Storage from the recovery. I tried with two original HTC cables and a miniUSB cable, with identical results. Someone advised me something?
NOTE: I created this thread in development forum because I need to link development ADB to develop in Eclipse, which used to be able to perfectly
Thanks in advance, and happy new year for you all!!
If you can't mount in Recovery, I would assume there is a problem with your SD card. Have you got another one to test with?
that's i'm just trying, i'm backing up my sdcard to my laptop and low-level format it...
if doesn't work, i'll try with another sd...
thanks for the response, that was quick i'll try and comment here
I shouldn't make a difference to mounting the SD card, but make sure USB debugging is enabled (you may have flashed a ROM which has it disabled by default).
What error do you get if you try and connect to it via ADB?
i'm still backing up the SD stuff to format it...
i tried before usb debugging enabled and disabled, and the same error...
i haven't errors with adb, simply if i try "adb devices" it isn't any device...i'm looking at my logcat and can't see any strange output. In the "devices' administrator" in windows (sorry for my crappy english) it appears "Unknown Device"
not working at all (tried with two microSD, both formatted in fat32)
tried formatting it in windows and in the phone...
here is the recovery.log...
Here is something to try, boot into fastboot and run the following two commands:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
You will need an unlocked SPL for this to work though
same thing
Hi pulimento,
I HAD THE SAME PROBLEM.. curious, i got it after installed the "Flykernel-12c". There is a thread that a i related the problem. Look for my posts.. but just a info, today I was not able to recovery the CELLPHONE, this is happen about 2-3 weeks. You descrived the same situtation that I had.
The SD card is working, I tested in another device. But the HTC hero can not mount. Its weird.
And also, trying to solve, i did something terrible, I format the system..and not way, the same behavior. Now I stucked in the bootscreen .
pulimento said:
Hi buddies,
I created a new thread because I think this issue has not ever treated specifically. When I connect my Hero to my computer, i get USB charging only, and windows shows me the error "usb device not recognized". I tried in two windows 7 PCs, one with Vista, one with XP and one with Ubuntu Maverick, and the same problem. I think that no matter what operating system you try it, because the problem is not drivers, and that is not even recognize the device. Before I was with Floyo and the flykernel 11c. I changed the kernel, I tried several roms (with and without Sense) and nothing ... so I tried it in recovery, and nothing ... and I can not mount as USB Mass Storage from the recovery. I tried with two original HTC cables and a miniUSB cable, with identical results. Someone advised me something?
NOTE: I created this thread in development forum because I need to link development ADB to develop in Eclipse, which used to be able to perfectly
Thanks in advance, and happy new year for you all!!
Click to expand...
Click to collapse
Hi Lost,
I did the command below:
fastboot oem enableqxdm 0
And its waiting for device eternally.
Any clue?
What do you mean UNLOCKED SPL? SPL?
thanks
l0st.prophet said:
Here is something to try, boot into fastboot and run the following two commands:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
You will need an unlocked SPL for this to work though
Click to expand...
Click to collapse
thanks, i'll try after lunch...
l0st.prophet said:
Here is something to try, boot into fastboot and run the following two commands:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
You will need an unlocked SPL for this to work though
Click to expand...
Click to collapse
Tried it with the unlocked SPL, and nothing... tried wiping (fastboot -w) too. i'm running now CM6.1.
What I need to run a RUU? I think that a RUU writes a new hboot, boot.img, radio, ROM...and MAY solve the problem, but i need usb connectivity to run it. any chances?
any commands to try in fastboot (with unlocked spl)?? thanks in advance
The info about flashing an RUU without USB is readily available, in the thread regarding "unbricking" after the original 2.1 update from HTC. You will however need a card reader or oither device that reads MicroSD cards to do it tho. Basically you take the HEROIMG.zip file (called rom.zip) that is extracted from the RUU exe and copy to the root of your SD and then start your device i hboot mode and follow the on screen instructions. For a more detailed explanation have a look at the afore mentioned thread.
tried this (after googled A LOT) :
http://forum.xda-developers.com/showthread.php?t=691639
and not working...
The problems appear to be in MISC partition, there is a parameter with an invalid config (something as UART_ENABLE = 0 or similar...)
do anyone know that "flashing the RUU" (with the HEROIMG.ZIP) will write that partition? i'm pretty sure, but not 100% sure
i'll try a few things tomorrow, now i'll go to celebrate the new year happy new year XDA!!!
PS: users with the same problem, to investigateby yourself, try searching USB Brick Android in google
I had this problem. I bought a micro sd to USB adapter to put another ROM on the card and flashed another ROM that way. That seemed to fix it for me.
now, i'm really disssapointed...hero doesn't recognize sd card at all (even in recovery) and i haven't got fastboot usb connection...and i'm stucked with a 1.5 Sense ROM!!! any ideas? can't download anything from internet (no SD CARD) and can't fastboot... SH*T!!
now, i'm in android 1.5, i do the HEROIMG.zip method...but still USB bricked...going to try another time...i must flash MISC partition with mtd0.img file...(see link in post #13) but be careful if u try this!! You must HEX-edit the mtd0.img to match with your CID (mine is ORANG309) and ROM version!! (mine is 2.74.something)... and you may have installed a SENSE rom...think that our Hero oficially only can use that kind of ROM.
That's the result of my investigation, hope it helps
GREAT NEWS!!!!!!!!!!!!!!!!!!!!!
I only did the procedure below and work.
http://forum.xda-developers.com/showpost.php?p=4467471&postcount=13
I was possible to FLASH ANOTHER ROM.
It was possible to read the SDCARD -> HEROIMG.zip in the FLASHBOOT mode.
GOOOOOOOOOOOD
But the SDCARD AND USB still not work. But now I have a OS at least.
EDIT1: After the install, I upgraded(to ANDROID 2.1) the OS though the HTC OTA(automatically)..
EDIT2: After the OTA to 2.1..THE SD CARD AND USB LINK ARE WORKING!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Related
So I'm trying to get back to HTC to test a few things.
My keyboard is not working well at all with Froyo for some reason and I'd like to make sure it's Froyos problem (anybody else got this problem?)
I've found this thread: http://forum.xda-developers.com/showthread.php?t=559622
I run the wizard and it can't find my phone, though it's connected to the usb and all.
Is that how it should be done?
There is a thread somewhere by btdag called ruu and usb errors solved. That should sort you out.
Sent from my HTC Hero using XDA App
Looks like this thread covers exactly what I'm looking for (including the keyboard issue):
http://forum.xda-developers.com/showthread.php?t=750318
Basically:
For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did:
- Create Goldcard
- Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site
- Rename to HEROIMG.zip
- Boot to flashboot mode (Volume down + Power on)
- Flash.
- Reboot and enjoy your new stock HTC Hero.
Click to expand...
Click to collapse
Haven't tried yet but should do the trick.
Haven't found the "ruu and usb errors solved" thread though.
Thanks!
[Guide] Drivers & RRU Errors Solved
... If you need it...
This is frustrating.
Got stuck in the very first step of both guides.
The one saying to make a gold card, I can't even run adb on windows. It says command not found on cdm.
So I'm going to the more reliable guide with the screenshots.
Right on the first step when you need to uninstall drivers, I select and click "uninstall" and nothing happens.
Gotta love windows.
Anyone who succeded doing this and how?
m4co said:
This is frustrating.
Got stuck in the very first step of both guides.
The one saying to make a gold card, I can't even run adb on windows. It says command not found on cdm.
So I'm going to the more reliable guide with the screenshots.
Right on the first step when you need to uninstall drivers, I select and click "uninstall" and nothing happens.
Gotta love windows.
Anyone who succeded doing this and how?
Click to expand...
Click to collapse
Were you in the correct folder when you tried to use adb? You need to install adb from the sdk, and run it from that folder, else windows can't know what program you are trying to use, unless you add it to $PATH.
I use adb all the time, and have tried millions of driver versions without issue.
pulser_g2 said:
Were you in the correct folder when you tried to use adb? You need to install adb from the sdk, and run it from that folder, else windows can't know what program you are trying to use, unless you add it to $PATH.
I use adb all the time, and have tried millions of driver versions without issue.
Click to expand...
Click to collapse
ยจ
Thanks for the reply.
I didn't use ADB; no idea how to use that.
I managed to get it working after some struggle and what worked was:
- Install HTC Sync. That will install the correct drivers
- Install HTC RUU from the official site
It was many trial and error times but in the end it worked.
Thanks again!
i have same problem. i want back my official soft with now root, but when i tried it with HTC RUU i get error (something about please check the phone has correctly connected on computer) so i don't know where's the problem. And one question more: when i plug my phone with usb cable to computer then which mode should i use? (charge only,disk drive...)
sc0rpp said:
i have same problem. i want back my official soft with now root, but when i tried it with HTC RUU i get error (something about please check the phone has correctly connected on computer) so i don't know where's the problem. And one question more: when i plug my phone with usb cable to computer then which mode should i use? (charge only,disk drive...)
Click to expand...
Click to collapse
Try Installing HTC Sync first.
You using Windows 7 right? I think it's a Windows problem that install wrong drivers. HTC Sync will fix that.
Then you can try again.
The usb you just plug and you're done, no need to set a mode. You should get a (sound) notification that it's plugged.
My major issue with this is the need for a win machine. Everything would be much better if I could just do it in linux.
My phone was sent to repair now You also got trouble with the Hero keyboard?
nope, but the gps is dead. I try to repair it by warranty. But at the moment i have froyo rom with root and as you all knows ROOT=NO WARRANTY :S
im having problem with installing any rom... even stock rom cannot be installed. I have HSPL 2.08 installed. I can enter bootloader. The installation of rom goes through the version check window and then when i hit flash button it shows 0% and after 10 secs pops out window with error code 266 that it cannot get response from the device.
I also tried flashing from the stock sd card (2gb, FAT32 formated) with the stock nbh file renamed to leoimg.nbh but when i enter bootloader mode nothing happens and im stuck on the three coloured screen. I really dont know where's the problem.
I have already had several WM6,5 roms installed... i have tried WP7 and currently i have NAND Android and Magldr 1.12 and nothing happens even if i want to update it to 1.13. Only flashing that works is flashing SPL/HSPL. It works without any issues...
If anyone have an idea i would be very thankfull, because i have tried almost everything.
Please post the spl line from bootloader. Go look, don't just assume it's still what you think it is.
it shows:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
janox1x2x3 said:
im having problem with installing any rom... even stock rom cannot be installed. I have HSPL 2.08 installed. I can enter bootloader. The installation of rom goes through the version check window and then when i hit flash button it shows 0% and after 10 secs pops out window with error code 266 that it cannot get response from the device.
I also tried flashing from the stock sd card (2gb, FAT32 formated) with the stock nbh file renamed to leoimg.nbh but when i enter bootloader mode nothing happens and im stuck on the three coloured screen. I really dont know where's the problem.
I have already had several WM6,5 roms installed... i have tried WP7 and currently i have NAND Android and Magldr 1.12 and nothing happens even if i want to update it to 1.13. Only flashing that works is flashing SPL/HSPL. It works without any issues...
If anyone have an idea i would be very thankfull, because i have tried almost everything.
Click to expand...
Click to collapse
Have you tried a different USB port or a different computer? If this does not work try another USB cable. As far as flashing from SD make a copy of your SD card on your computer and reformat it.I know you said it was already Fat 32 but sometimes it helps to theroughly clean your SD card, this is what reformating it will do. Once you have it reformated just put the ROM on it and try flashimg it again.
so i have finally fixed the problem. The problem was very simple. ROM flash utillity doesn't support USB 3.0 but anyway i don't understand why flashing with sd card doesn't work because i have tried several sd cards with various size.
janox1x2x3 said:
so i have finally fixed the problem. The problem was very simple. ROM flash utillity doesn't support USB 3.0 but anyway i don't understand why flashing with sd card doesn't work because i have tried several sd cards with various size.
Click to expand...
Click to collapse
It is not that it does not support USB 3.0.The problem was that your HD2 drivers cor the USB port you were using were most likely either nolonver correct or corrupted. This is a common probblem for some reason. Maybe samsamuel can post here again and explain it a little better. Glad you got your HD2 up and running again.
T-Macgnolia said:
It is not that it does not support USB 3.0.The problem was that your HD2 drivers cor the USB port you were using were most likely either nolonger correct or corrupted. This is a common probblem for some reason. Maybe samsamuel can post here again and explain it a little better. Glad you got your HD2 up and running again.
Click to expand...
Click to collapse
well im no engineer, but each usb port installs drivers individually for anything you plug in, so port 1, it installs the hd2 drivers, port 2, it installs them again, and sees them as two seperate instances. if you then mess with android, say, and/or wp7, and mtty, you replace those drivers with other drivers, but only for that port, so you can potentially end up with three sets of different drivers on three different ports, so you try something that requires winmo drivers, and the pc is trying to use the ones tweaked for mtty.
Only a theory, thats what usb does, whether thats really the problem, who knows. makes sense to me, so im sticking to it. ALways pays to find the device in hardware list and uninstall it now and again, including 'remove drivers'.
That being said, there could be something in the usb 3 theory in this instance.
well i cannot argue with you guys, because you might be right. But i tried two different USB 3 ports with the exactly same result and failed then i tried USB 2 port and succeded without any problems so maybe there's something about it
All sorts of issues here.
I am no longer able to install new ROMs on my Aria. In the past I have flashed many ROMs on the phone. Recently I flashed an ICS rom but I did not like the way it was working so I went back to Cyanogenmod 7.1 RC1. Now for whatever reason, I am unable to flash any other ROMs. I put the new rom on the SD card like I always had then boot to CWM, go to install from SD card and it says that there are no files there. Which is not true and its not the SD card because I can still see the files with a file manager. When I select the ROM from inside ROM Manager it goes through the process but stops shortly after starting the install. I have heard that using a different version of CWM may work but when I try to download one from ROM manager it says an error occurred when trying to download. Also when I hook the phone up to my PC it doesnt recognize that it is plugged in other than its charging. (yes it is the original USB cord and USB debugging is on).
A few details: This phone has never connected with my current/new PC. It did work at one time with my old one. While trying to fix this I did a complete wipe of the phone, the first time I hooked it up to my current PC I got the whole new hardware detected thing on my PC and USB debug was active on the phone, but I don't know if I accidently hit a wrong option on my PC but it went right away and has never connected again.
I also noticed that the phone is S-ON, I thought/assumed it was S-OFF before. Could it have some how turned back on? I cant get it back off now since I cant use ADB without USB Debug connected.
I no longer use this Aria for daily use (replaced with One X ) so I am open to some possible "extreme" ideas of trying to fix this.
Thanks for any help. This is driving me nuts.
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
drumist said:
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
Thanks. I will give that a try.
drumist said:
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
Install this first: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Then try running the RUU again.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
I have tried installing that before (tried again this time too) and it doesn't help. I still have no connection to the phone. I have Windows 7 if that helps anything.
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
drumist said:
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
Click to expand...
Click to collapse
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
chadd74 said:
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
Click to expand...
Click to collapse
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
drumist said:
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
Click to expand...
Click to collapse
Well,sort of good news here. I had tried different USB ports before but thought I would give it another go, it still was not connecting. So in a bit of a fit of rage I took the micro usb cord at shoved it quite hard into the phone. Well the connection flickered. So it appears over the years the USB slot had gotten a nice amount of pocket lint or whatnot jammed tight in there to where it would connect enough to charge but not enough for a PC connection. I cleaned it all out the best I could and what do you know, it worked.
Foiled by pocket lint.... SMH.
I loaded the 2.2.2 RUU and will give the rest of the problems a go tomorrow and post an update. Thanks again for all the help.
Looks like everything is working like it used to.
Thanks again.
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hello,
I hope that I am not asking a already existing question again, if so, please send me the link and I will follow the instructions there.
I could not find anything, so far, but I am nearly going mad after a day of trying to unbrick my phone.
So, I had CM 11 Snapshot M10 installed, the current clockworkmod, bootloader unlocked through htcdev.
Today I wanted to do a full wipe (including /sdcard, because there were tons of files which I didn't know, lately).
I don't know why, but i ended up wiping /system and /sdcard at the same time.
Now I don't have any system on the phone in order to boot and get adb or mount the phone as a USB drive, and no firmware on the phone which I could flash. I really have no idea how I can get any rom onto the phone, now...
I tried official RUUs ("Please download the RUU which fits your phone), ADB sideload with CWM ("no devices found"), ADB sideload with TWRP (same as with CWM), and now I am running out of ideas...
Does anyone have an idea how to or get ADB sideload working (USB drivers are installed on my PC, but it doesn't seem to work), or how to get a RUU wiorking (I would like to go back to the stock rom anyway, I miss sense by now), or any other way how to revive my phone?
I do have access to the bootloader, fastboot is working, and so is the recovery. Is there any information you would need?
It is an enrc2b international, no branding. CID is HTC__102.
fastboot getvar version-main outputs 2.18.401.3
I really hope that someone can help me out...
Moritz
Adb sideload needs up to 5min to recognise the device.
Or you flash twrp recovery. Which has mtp support (access via windows explorer)
If crusader's suggestion didn't work then:
Try to use a different USB port. If USB 2.0 use USB 3.0 and vice versa.
If that doesn't work too, try running cmd as admin.
Last resort : install Ubuntu or any other Linux distro, and install dev tools on it (check for guides ) .. I have a similar issue to yours when it comes to windows, restarting to Linux always works for me
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
EDIT: looks like my htc drivers were simply retarded. They worked as long as the phone booted into the OS, but failed if I was in the recovery.
Reinstalling worked.
I will now flash CM11 again, does anyone have an idea how to get the RUUs working, or get Sense back in another way?
I lost my old backup with Sense
elektrobastler said:
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
EDIT: looks like my htc drivers were simply retarded. They worked as long as the phone booted into the OS, but failed if I was in the recovery.
Reinstalling worked.
I will now flash CM11 again, does anyone have an idea how to get the RUUs working, or get Sense back in another way?
I lost my old backup with Sense
Click to expand...
Click to collapse
Someone posted his backup files somewhere here on the forums...
First look at your CID (found at the top of the boot loader)
And secondly you can just install sense-based ROMs like viper or revolutionHD (I think that's what it was called) .. RevolutionHD is just stock sense basically with a few performance improvements.
Thank you very much!
You really saved my day
I was able to install CM11 now, it booted.
I instantly shut it down again, though, because I will now try RevolutionHD.
Stock sense (especially the gallery and camera app, never found anything comparable so far) with a few improvements sounds just awesome.
Exactly what I was hoping for, but I never imagined someone had actuall done it!!
Downloading it now, I think this will stay my ROM for the next year(s), depending on how long my X+ will keep on working...