Hi, today a have tried to root my htc desire using revoked 2 method. I was unable to install usb drivers. And now i cant even mount desire as hard drive. Computer still reports that device is unknown. I tried different usb ports, 2 different cabels, windows xp and seven. Before everything worked fine. Do you thing it is possible, that i damaged phone, when i plug it out just disconnecting cable?
Which version of unrEVOked did you try? I seems like a driver issue as you have to install the modified Hboot drivers for unrEVOked in a certain way before unrEVOked will work. If you attempted root with unrEVOked 3.21, did you follow the steps mentioned in thi thread?:
http://forum.xda-developers.com/showthread.php?t=776696
and
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
MasDroid said:
Which version of unrEVOked did you try? I seems like a driver issue as you have to install the modified Hboot drivers for unrEVOked in a certain way before unrEVOked will work. If you attempted root with unrEVOked 3.21, did you follow the steps mentioned in thi thread?:
http://forum.xda-developers.com/showthread.php?t=776696
and
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
I used this tutorial http://forum.xda-developers.com/showthread.php?t=788044
and I stuck at 3. point... On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
and after that i am unable to connect desire to pc... no way...seems like something happend with usb driver in phone or i dont know...just i ve tried 3 computers for now and every reports same when I connect usb, that device is unknown
What Hboot do you have?
What is your PVT version? (also check the Bootloader for this info)
0.93.0001 and I forgot...I stucked at third point because i got there no option HBOOT USB
benefic said:
0.93.0001 and I forgot...I stucked at third point because i got there no option HBOOT USB
Click to expand...
Click to collapse
And your PVT version?
Bravo pvt1 ship s-on
hboot-0.93.0001
benefic said:
Bravo pvt1 ship s-on
hboot-0.93.0001
Click to expand...
Click to collapse
Ok, thank you for that info.
To tell you the truth, with unrEVOked 3.21, you must install the modified HBOOT drivers for it to work, otherwise it will not work at all.
Please try following this guide as it is definately requied. I asked you above if you had tried going through it, you mentioned that you had only tried using the guide in the first link, but you definately need to have the modified HBOOT drivers installed to proceed.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Try what is suggested and let me know if you can proceed past step three after configuring the HBOOT drivers first, as it is a must.
MasDroid said:
Ok, thank you for that info.
To tell you the truth, with unrEVOked 3.21, you must install the modified HBOOT drivers for it to work, otherwise it will not work at all.
Please try following this guide as it is definately requied. I asked you above if you had tried going through it, you mentioned that you had only tried using the guide in the first link, but you definately need to have the modified HBOOT drivers installed to proceed.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Try what is suggested and let me know if you can proceed past step three after configuring the HBOOT drivers first, as it is a must.
Click to expand...
Click to collapse
Well I tried connecting usb cable in bootloader menu but no HBOOT USB PLUG appeared and in device manager i dont have Android 1.0 device. and this is the problem.
benefic said:
Well I tried connecting usb cable in bootloader menu but no HBOOT USB PLUG appeared and in device manager i dont have Android 1.0 device. and this is the problem.
Click to expand...
Click to collapse
Hmm... yes i see what you mean. Unrevoked is fussy regarding drivers. Try the following:
1) Uninstall HTC Sync completely, the HTC Driver Setup, and HTC BMP Driver if present.
2) Reboot and reinstall the HTC Sync software (latest version).
3) Now uninstall HTC Sync Alone. Keep other two (HTC Driver Setup and HTC BMP Driver) installed.
4) Reboot your PC again.
Note: do not connect phone to PC at all and make sure the phone is switched off.
5) Switch your phone to the Bootloader screen. Connect the phone via USB and it should show Fastboot USB.
6) Windows will show the device detection dialog box - at this point, stop Windows from getting the driver from Windows Update, and manually choose the location of the driver as the folder where Unrevoked driver is present.
7) After this is done, diconnect phone again.
8) Go through the unrEVOked guide and connect the phone when advised to.
If this fails, then try unrEVOked 3.22 (in my sig below) and see how that goes and although you have mentioned that you have tried 3 different PC's, you may have to consider trying it on a different OS platform, such as Linux.
MasDroid said:
Hmm... yes i see what you mean. Unrevoked is fussy regarding drivers. Try the following:
1) Uninstall HTC Sync completely, the HTC Driver Setup, and HTC BMP Driver if present.
2) Reboot and reinstall the HTC Sync software (latest version).
3) Now uninstall HTC Sync Alone. Keep other two (HTC Driver Setup and HTC BMP Driver) installed.
4) Reboot your PC again.
Note: do not connect phone to PC at all and make sure the phone is switched off.
5) Switch your phone to the Bootloader screen. Connect the phone via USB and it should show Fastboot USB.
6) Windows will show the device detection dialog box - at this point, stop Windows from getting the driver from Windows Update, and manually choose the location of the driver as the folder where Unrevoked driver is present.
7) After this is done, diconnect phone again.
8) Go through the unrEVOked guide and connect the phone when advised to.
If this fails, then try unrEVOked 3.22 (in my sig below) and see how that goes and although you have mentioned that you have tried 3 different PC's, you may have to consider trying it on a different OS platform, such as Linux.
Click to expand...
Click to collapse
ok, i tried what you suggest, but desire refused any other driver...and keep installing unknown usb device driver
benefic said:
ok, i tried what you suggest, but desire refused any other driver...and keep installing unknown usb device driver
Click to expand...
Click to collapse
Try downloading the Android SDK: installer_r08-windows.exe
Follow the steps in this video to hopefully get the appropriate USB drivers - http://www.youtube.com/watch?v=N66J6UiN5Pg&feature=player_embedded
EDIT:
With the phone connected, try the following afterwards:
Check to make sure that you have USB Debugging enabled on your phone.
In Device Manager, right-click your Unknown Android device and select 'Update Driver Software'. Browse to the folder (extract the zip to the Desktop) i have attached below and see if it installs them.
MasDroid said:
Try downloading the Android SDK: installer_r08-windows.exe
Follow the steps in this video to hopefully get the appropriate USB drivers - http://www.youtube.com/watch?v=N66J6UiN5Pg&feature=player_embedded
Try the following afterwards:
In Device Manager, right-click your Unknown Android device and select 'Update Driver Software' (Make sure you are connected to the Internet to search for available drivers via Windows Update).
Click to expand...
Click to collapse
OK, i will try the thing with sdk..i am downloading files right now, but that makes no sense to download any other windows drivers. I think the problem is inside of the phone, because it represents itself like unknown device to any computer with any drivers...if there is a way to restore flash memory or something...well looks like i will have to wait one month for reclamation...how this could happen my god
benefic said:
OK, i will try the thing with sdk..i am downloading files right now, but that makes no sense to download any other windows drivers. I think the problem is inside of the phone, because it represents itself like unknown device to any computer with any drivers...if there is a way to restore flash memory or something...well looks like i will have to wait one month for reclamation...how this could happen my god
Click to expand...
Click to collapse
I agree... it is clearly an HBOOT driver issue or the phone... Windows (PC host) drivers are seperate. I was just running out of ideas really
The only definate way of knowing if it is the device that is causing this issue is if you were to try it on a non-Windows related OS, like Linux and maybe it would work for you using an Ubuntu Live CD.
MasDroid said:
I agree... it is clearly an HBOOT driver issue or the phone... Windows (PC host) drivers are seperate. I was just running out of ideas really
The only definate way of knowing if it is the device that is causing this issue is if you were to try it on a non-Windows related OS, like Linux and maybe it would work for you using an Ubuntu Live CD.
Click to expand...
Click to collapse
well this is good idea...do you think it could also fix the usb issue for windows when i will root my phone in linux?
benefic said:
well this is good idea...do you think it could also fix the usb issue for windows when i will root my phone in linux?
Click to expand...
Click to collapse
Yes, because it is not as fussy with drivers as Windows is - with Windows, they have to be properly removed from its cache. With Linux, the phone should be detected ok (unless the phone is at fault).
Here is a simple guide that you can follow:
http://rootmydroid.co.uk/guides/desire/howtolinux-root-your-desire-using-unrevoked-in-linux/
Keep those fingers crossed
MasDroid said:
Yes, because it is not as fussy with drivers as Windows is - with Windows, they have to be properly removed from its cache. With Linux, the phone should be detected ok (unless the phone is at fault).
Here is a simple guide that you can follow:
http://rootmydroid.co.uk/guides/desire/howtolinux-root-your-desire-using-unrevoked-in-linux/
Keep those fingers crossed
Click to expand...
Click to collapse
So, linux didnt work either, system didnt even recognize that anything was plug in. Even crossed fingers dident help Well only last thing I have to ask, if there is any possibility to recover hboot, restore it somehow. Forexample through recovery menu in hboot loader and some kind of .zip file, that i will put to SD card. If not, well I will have to step out to that freezing weather and walk to orange store for reclamation, which I hope would be positive for me, but something telling me it surely will.
I found something about usb unbrick here on xda forum, but is only for root phones
well i found this http://forum.xda-developers.com/showpost.php?p=9056719&postcount=15 i think it could work, just i dont know a way how to discover my CID number..to modify mtd0.img file
ok, i did everything step by step using rageagainstthecage tutorial, but nothing happend at all.
If anyone could help...
Are you able to get into Fastboot?
I suppose running your stock RUU in Hboot won't make a difference then... how about trying the PB99IMG method, which involves renaming the extracted rom.zip file to PB99IMG.zip from your stock RUU, placing this to the root of your SD card and then letting it run from Fastboot mode. This would restore your stock Hboot. You could also try AlphaRev's modified 0.93 HBOOT with S-OFF?
[solved using the following RUU: http://goo-inside.me/bravoc/ruu/RUU...Radio_2.15.00.11.16_release_168495_signed.exe + the factory Google SDK driver. I solemnly ask of any CDMA Desire user to please download and save in a safe place this RUU]
Guys,
I completely formatted my CDMA Desire (don't ask) and now I'm on the
BRAVOC DTV2 SHIP S-OFF
HBOOT-1.06.0000
MICROP-051e
TOUCH PANEL-SYNT0101
RADIO-2.15.00.11.16
Dec 22 2010, 16:16:39
FASTBOOT USB
...screen. Formatted everything there was to format in Clockworkmod recovery options: sdcard, boot, sd-ext, system, etc.
None of the 3 RUU's for the CDMA Desire work. All give me the Error 130 - Model ID incorrect, use a correct RUU error (I've previously succesfully used RUU's, but I have gotten this before.)
I used to have Oxygen's Gingerbread ROM in there.
ADB devices shows nothing. I have Windows XP. In Control Panel, I got Android USB Devices - My HTC on there, says working properly.
Tried to push recovery using fastboot commands, says Failed every time.
Changed USB ports, I guess I'll keep changing, as that's been the trick from time to time...
Any ideas? Been at least two hours searching and trying, would love some input...
Hi, I'm stuck in a quandary with my HTC desire
I believe i have the USB BRICK issue, i cannot get the phone recognised in any PC, have used official HTC cable and other and another PC, all work with my other android phone but not this one. I cannot get into ADB or FASTBOOT via cable not even if i boot into the bootloader. I get nothing
I can't use fastboot commands or ADB via windows CMD prompt but i can adb via wireless, sadly that does not help with tools like 'revolutionary' or 'fastboot' commands.
I successfully managed to create a goldcard and flash a stock WWE RUU, which went well, and the phone went back to stock but i only get 'USB DEBUGGING' symbol pop up on the phone side when i plug the cable in, nothing in device manager, no option to install any drivers, i checked it wasn't set to charge only in 'settings' and usb dubugging is checked.
Phone will charge on the official HTC cable.
I still a noob so if i have missed something or have quoted any of the above incorrect then i hope you understand.
I think I'm missing something so simple.
Could i kindly ask if anyone could talk me through any terminal emulator methods i could use from within the phone to help solve this problem.
I do not get any change in device manager when the phone is plugged in and have tried front and back ports, there is no yellow triangle etc in device manager indicating a driver issue and i also did a fresh install of windows 7 and new htc install. (Win XP gave the same results)
I even checked the usb port on the pcb and it is in good condition, nothing jammed in there, no broken / damaged pins and the solder points are all good.
Many thanks
Chris
Bravo PVT4 SHIP S-ON
HBOOT-0.93.001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010,17:52:18
Hi,
So on one casual Sunday afternoon after getting burgers with my friend, I went to use my phone to find that the screen was on the fritz:
(had images uploaded onto IMGUR but I can't like to them because it's a new account )
After taking the battery out and restarting it, it went into the htc load screen and then glitched out again.
(had images uploaded onto IMGUR but I can't like to them because it's a new account )
I'm able to get into the HBOOT menu fine and it says the following:
VISION PUT SHIP S-ON
HBOOT - 0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
I have tried downloading and loading 4 different PC10IMG.zip(s), none of which have worked for reasons such as:
CID INCORRECT! UPDATE FAILED!
One of the PC10IMG.zip that I used seemed to load fine(?), no error message was shown but it went back to HBOOT after checking the zip and there's no change to the state of the phone.
I installed ADB on my computer and the adb drivers for my phone installed fine but adb devices doesn't detect my phone. I'm unable to get into the usb debugging menu to turn debugging on which I'm guessing doesn't help.
I also installed fastboot which detects the phone fine.
Any suggestions?! Really stuck, pretty sure the phone's not under warranty any more (I've had it for over 2 years and took it apart once to try fix a broken headphone jack, to no success might I add).
Bought phone off of ebay, the incredible 2 is stuck on bootloader, i cant recover/factory restore, bootloader is locked and s-on, and computer recognizes it as a unknown device, although HTC sync recognizes it as an unknown htc phone. I've tried multiple times to load a few RUU signed stock roms, but nothing happens when its done loading in hboot. Do i have any options left or is it dead?
LOCKED
Vivo-W XA SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-boot
Try to use revolutionary.io to try n unlock it
Sent from my One using xda app-developers app
chillybean said:
Try to use revolutionary.io to try n unlock it
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
Just tried it, didn't work. My computer doesn't recognize it, says its an unknown device so i don't think i can do anything with it via usb. Although HTC serial interface pops up sometimes and when i click on it, it gives me driver details:
HTC Serial Interface (COM7)
Driver Provider: HTC corporation
Driver Date: 11/1/2013
Driver Version: 2.0.6.24
so idk if that's anything..
twister3982 said:
Just tried it, didn't work. My computer doesn't recognize it, says its an unknown device so i don't think i can do anything with it via usb. Although HTC serial interface pops up sometimes and when i click on it, it gives me driver details:
HTC Serial Interface (COM7)
Driver Provider: HTC corporation
Driver Date: 11/1/2013
Driver Version: 2.0.6.24
so idk if that's anything..
Click to expand...
Click to collapse
Are you on windows 8.? Win 8 has problems with adb. Try in a win7 machine.
Sent from my ADR6350 using Tapatalk
sorry for late reply, no im on windows 7, but Ive tried to plug it into windows 8.1 and windows vista machines and the same thing, none of them recognize it. All i can do is load something onto the sd card for the incredible 2 to read from.