I have been finally successful in downgrading the phone to 2.3.3 but when I try to root the phone either using revoked or acs the phone goes offline and they both just sit there saying "waiting for device". I have uninstalled htc sync and the usb drivers and just reinstalled the drivers but the same still happens. I am running win7 x64 and i run the scripts as an administrator.
Second question - I have noticed on the tbh us gsm unlock tutorial that it will only work on 2.4.29. <-What is this number, the radio, build, kernel?????????? I got that info from the posts on droidworld.
Related
I tried to root my Desire GSM (running Android 2.2, stock obviously...) with unrevoked, but every time i try, it gives the following error message (After the phone reboots):
"Communications with phone unexpectedly interrupted. Try again."
I'm running Winodws7 (driver signature mode...) + hboot drivers and i deinstalled everything from HTC Sync
I also tried it on ubuntu, but it wouldn't even connect to my phone.
Can someone please help me?
PS: I attached a photo from my hboot, if it helps.
When your desire is in hboot as on the picture, what device do you have in windows devicemanager under "android"?
There should be something like "android bootloader interface", with that it worked for me today
You are using unrevoked 3.32? Your usb cable is ok? Are you using any usb hubs, try to avoid them for this kind of work
People reported problems with newer versions of unrevoked.
I rooted mine with 3.21 - no hassle and error-free rooting.
Also check the Hboot driver status valo_lindstroem suggested, if not correct, install them using this method.
thanks for the quick help..
now it works. ;-)
I just check the box for "USB-debugging"
Okay, so here's my story. I have an HTC Desire. Bought it two days ago.
I've flashed and rooted with unrEVOked 3.32, then installed this ROM: http://forum.xda-developers.com/showthread.php?t=773997 (The stock ROM with radio)
It was working wonderfully, then I figured hey, why not install HTC's available update. So I did.
It installed, and now does nothing but reboot. I've tried to re-recover from the (now 3e) menu, but keep getting signature verification failures.
I've tried to create a GoldCard, got a spare 1GB MicroSD card that I'm using, but when trying to use ADB, I get a 'device offline' error, and therefore can't create a GoldCard. I have USB drivers installed from HTC Sync, and they worked fine for the flashing process itself. USB development was enabled the last time my phone booted, but I'm not sure whether that counts when I can't boot it.
I'm busy downloading and am going to reinstall HTC Sync for drivers, but have also tried the drivers included as a package in Android's SDK.
I've tried switching MicroUSB cables (although I only have 2 at the moment - HTC and SonyEricsson) with no luck, after reading stuff about some manufacturers' cables not playing well with ADB. Still get a device offline error.
I've got all I need to make a GoldCard, but ADB just won't work. I've also tried disabling firewalls/antivirus, to no avail.
Help?
Checkout this thread it has some good info
http://forum.xda-developers.com/showthread.php?t=831734
To make gold card use the gold card tool. If you can't find it here on XDA then PM me your email.
Sent with HTC Desire
When it said that my device was offline, I installed the Hboot drivers from unrEVoked and updated the SDK as well (might of used the SDK drivers instead) and it got sorted out.
Hi
My Win7 disk crashed some time back and I'm trying to get it back to the way it was which, I believe, had hboot and fastboot drivers for my (now rooted) HTC Desire on it. I can't remember everything about how I did it before but now, when I put the phone into HBOOT then connect it to the PC, it installs as "HTC Serial Interface" and I don't seem to get it to become an "Android Bootloader Interface".
Can anyone suggest anything to help?
As I mentioned, I _think_ I had the hboot drivers installed before, but it's always possible I didn't so if I don't need them any more anyway as the phone's already rooted, please let me know.
What I remember from before was using fastboot to install a custom recovery so perhaps that's the case.
Thanks
John
jgmccabe said:
Hi
My Win7 disk crashed some time back and I'm trying to get it back to the way it was which, I believe, had hboot and fastboot drivers for my (now rooted) HTC Desire on it. I can't remember everything about how I did it before but now, when I put the phone into HBOOT then connect it to the PC, it installs as "HTC Serial Interface" and I don't seem to get it to become an "Android Bootloader Interface".
Can anyone suggest anything to help?
As I mentioned, I _think_ I had the hboot drivers installed before, but it's always possible I didn't so if I don't need them any more anyway as the phone's already rooted, please let me know.
What I remember from before was using fastboot to install a custom recovery so perhaps that's the case.
Thanks
John
Click to expand...
Click to collapse
Install these.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
What are you trying to do?
abaaaabbbb63 said:
Install these.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
What are you trying to do?
Click to expand...
Click to collapse
Those are the instructions I was following but those drivers wouldn't install by the "right click on the .inf file and select 'Install'" method so had to be done by attaching the phone. When I attached the phone Windows went off and installed the "HTC Serial Interface" drivers!
However - I had a bright idea; uninstalled the "HTC Serial Interface" driver from device manager, switched off my wireless (because the "skip checking windows update" option when drivers installing doesn't seem to work very well!) and connected the phone again. This time it said it couldn't install the drivers so I went to device manager and followed the instructions again and now have an Android Bootloader Interface.
Overall what I'm trying to do is just play with different ROMs. I'd s-offed etc and loaded teppick74's (or something like that) Gingerbread ROM some time back to give the phone to my daughter but she had some problems with it and now uses an iPhone so I've got it back. I had to use the AmonRA recovery (I think) for that ROM because it used the older format that EXT4 Touch Recovery didn't support so I'm just trying to get back to the state where I can use that and play about more.
Thanks for taking the time to answer
John
I'm having trouble using this method. I have all the drivers installed... Except for the Hboot driver, It won't download.. I downloaded it from a mirror, but says it can't start? I had to do it fully manually install, It didn't show up on my windows device manager when booted into HBOOT and plugged into USB, so I had to do it manually with have disk, it said drivers weren't digitally signed, blah blah... it finally installed the driver but says it can't start. I have a feeling this is why unrevoked3 hangs... It gets to WAITING FOR BOOTLOADER, And if I click into it... It will say WAITING FOR HBOOT.. and if I click anything else on phone, it says communications interrupted. So I am not sure if it's because of the failed HBOOT Driver installation or what..
I'm on Windows 7 x64, I've got all the Android SDK tools on here. I've already gotten my bootloader unlocked via HTC Dev. I just want to root so I can put a custom ROM on here, because I am using the phone mostly for music.
Can anyone help?
OMG... finally got it working. I installed HTC Sync Manager again and decided to run it and see what happened. While it was scanning for music on my computer windows installed the drivers. More than once it seems.
Now I need to know if I can uninstall Sync Manager but keep the drivers. It keeps opening up and I don't know if it's safe to flash recovery if that's going to happen.
Flashed TWRP successfully and made my back up.
--------------------------
OLD NEWS BELOW:
Here's the deal... I just flashed the 3.x RUU so I'm stock but I'm unlocked and s-off. I'm trying to flash TWRP via fastboot so I can get a custom ROM on here. I turned on USB debugging on the phone.
First of all, that stupid HTC Sync manager keeps trying to install and I don't know how to stop it. Googling has not helped with this.
Second, I can't get the device to be seen in adb, or at least not online. I seem to be going backwards with all the steps I have taken to try to get this to happen.
I'm using dotatt's adb package. When I attach the phone while it is off windows looks for drivers and usually fails. One time it seemed to work and adb saw the device but then when it boots up that Sync Manager wants to install so I decline. Then my phone was seen but listed as offline.
So I tried uninstalling all HTC things on my computer and reattach phone. Didn't help anything. I tried installing the HTC Sync then uninstalling it thinking I would get the drivers, no go.
I grabbed these Universal ADB drivers http://www.koushikdutta.com/post/universal-adb-driver linked to from a twrp page here https://twrp.me/devices/htconem9.html
Nothing lists as a device in ADB at all now.
My windows Device Manager shows "Unkown Device" under "Other Devices" with no driver listed.
Tried this:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
http://forum.xda-developers.com/showthread.php?t=2588979
Still not working.
ACK! Can anyone help me out?
Is there still an issue with using usb 3.0 ports? I feel like I heard something about that way back when.
That's pretty much how it's always been. Best way to get the appropriate drivers is to install HTC sync, let it do its thing, reboot the PC, then uninstall HTC sync without removing the drivers. To the best of my knowledge, been that way since at least the days of the Incredible, if not before. At least it's how I've always gotten the drivers to use adb.
Yeah I remember that from the Rezound, which is why I did that, but it seems that the drivers didn't actually get installed this time until I let HTC Sync Manager start running and scanning my computer. That's when I saw the message that it was looking for drivers and twice it told me it installed them.
I would think it would have them installed during the 'actual' installation process. So I guess I just uninstalled prematurely. Seems weird. But it's working now so all good.