Hi there,
I'm trying to follow the guide at roothtchero.co.uk, but I can't even downgrade from 2.73.61.66.
When I try and run the official 2.73.61.5 ROM installed from the HTC website I get a 171 error when once the phone fastboots(?) my phone screen goes white with green text showing the phone name and date, and then orange highlighted white text saying RRU USB. Then there's nothing, and the waiting for bootloader message on the ROM software just times out.
Can anyone give me some advice how to fix this?
I've also created a GoldCard, (I used the 2GB micro SD that came with the phone), and have rebooted the phone, but I've noticed no change.
Any help would be really appreciated.
Cheers,
Blaise.
go into device manager and make sure your Hero phone, shows up as MY HTC. if not, make sure you've got the right drivers installed for your phone. Once you've done that, you can downgrade to .65 Orange ROM without needing the Goldcard Method
install the latest htc sync too
Thanks chaps,
So I've been checking out the device manager in the background when I try and perform the update, here's what I noticed.
I have Developer mode turned on, with my phone.
When I plug my USB into my computer under ADB Interface I have My HTC and HTC Sync is green.
When I run the RUU software HTC Sync disconnects, and I have to wait a good while for it to show green before I can run the update successfully.
When the phone reboots into bootloader mode I have a warning symbol under ADB Interface with a driver named Bootloader
Also when I start from scratch, uninstall, reboot, then reinstall everything, my Hero installs the HTC Dream composite ADB Interface in device manager as default. :S I have to manually choose My HTC as my driver.
It seems to be when the bootloader runs I get the following warning over the bootloader driver in device manager.
"Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
You need to restart your computer before the changes you made to this device will take effect."
I have already uninstalled everything, so how does this happen?
Another thing I've noticed is that I have USB Debugging enabled, should this be on or off when I perform a RUU updated?
Start > type Change device installation settings
Select No, then never.
try this http://forum.xda-developers.com/showthread.php?t=647353
This did the trick! Thanks for posting the guide.
To recap, the problem I was havin gis that all sorts of weird drivers were being associated with my Hero, for starters when I had installed the latest HTC Sync, my device was being picked up as a HTC Dream, so I changed this to My HTC.
Secondly when I ran the RUU and my phone rebooted into bootloader mode, a bootloader driver was being installed but having a conflict with another driver, it also asked me to restart my PC, I fixed this by updating the driver to My HTC again, and voila, easy update.
Thanks for all the help!
Cheers,
Blaise.
Related
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
msiviter said:
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
Click to expand...
Click to collapse
You are probably running the wrong driver. Follow my driver guide part iv. (You should be on My HTC not ADB driver)
If not then probably your gold card hasn't stuck (check it) or you'll need to use windows xp instead (can use a virtual machine).
I had this issue when using windows 7 64 bit.
Download the drivers in the attachment in the noob guide. Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
oliwan said:
Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
Click to expand...
Click to collapse
Depending on whether this works for this guy, might be a simpler method than the alternative.
@msiviter - please try the above quoted method first
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Try This
While trying to flash the RUU the phone reboots.
When it is rebooted you see RUU.usb on your phone screen. But no flash process.
While phone is still connected to pc and is still in RUU.usb mode.
Go to device manager on your pc. Right klik android devices and renew the USB driver to HTC driver.
Reboot computer and reboot phone.
then try to flash again.
This was the solution for me.
Tried all the above, spent 6 hours on it, I've got the closest by going to a (win7 64bit) pc that has never had the sdk on it then the RUU goes further but terminates with error [140] Incorrect Bootloader. I've made my goldcard again to no avail (Sandisk 512mb) and checked the goldcard data which was OK, I'll try it tomorrow on a different (Kingston 8gb) card.
Any other ideas?
Thanks for your help so far.
Matt
Update: New SD card and goldcard now gives 'Error [131] Incorrect Customer ID' on my Win7 x64, I'll try on my dads old XP laptop later!!!
I suspect it is a windows 7 issue. On the first attempt I managed to downgrade when I moved to my Vista machine.
I must have tried for about 6 hours with Win7 then moved back to my old Vista PC and it worked first time.
From observing the process on Win7, when the phone boots to the bootloader, the RUU program then gives it 180 seconds to confirm Bootloader is loaded "waiting for bootloader...1-180sec". Looking at the system tray the USB driver that is used for HTCsync disconnects and the device now says it is Android 1.0 and Win7 needs to find a driver for this. Win7 fails to find a driver for "Android 1.0" so it never allows propper communication between the phone and the computer.
(There are separate Win7 64-bit drivers - check you are using these?)
P.P.S. The stock card that came with the phone worked fine as a Goldcard for me and I think most people.
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] whether trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
You installed the latest version of HTC Sync while your phone was unplugged/ Then you plugged the phone in to detect new drivers. Waited for the drivers to successfully install and then ran the RUU?
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
What drivers are reading in device manager when in the normal os? And same question when in fastboot mode?
I did exactly that on my win7 x64 and xp mce sp3 x86 pc's both had 'My HTC' in Device manager and had a sync relationship established with the latest 'Legend' HTC sync software.
Both gave the almost random error messages although now the bootloader almost finishes now so I'm past the [171] usb (driver) errors and I'm on [131] and [140] errors which pertain to bootloader and incorrect customer errors which I think are goldcard related. Although like most people I do rush through things and not read instructions! I've now made 4 goldcards via the various guides and I'm sure they are OK.
My Bro is getting his desire this week and I was determined to beat him to eclair but it looks like I'm in the lap of the T-mobile gods waiting until June (or july....September.... December etc).
Matt
I have same issue with msiviter, CUSTOMER ID ERROR.
I was able to run RUU regarding to guid from btdag (section IV).
What can I do now?
try deleting the drivers and then starting again perhaps?
I have the same issue here, can't downgrade to the previous Orange RUU, also using Win7 x64.
Have tried reinstalling drivers, and using other ROMS, nothing seems to work. I also find that when I run the RUU it loses connection to my phone before it even tried rebooting the phone into the bootloader.
shotgunfool said:
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Click to expand...
Click to collapse
this is how i've done 2 of mine, 2 dev laptops on 2 differnt hero's ... didnt work, with adb, sdk everything loaded for android dev ...
desktop worked fine for both hero's.
Same Issue
The trick to get the RUU to actually update the phone, for me, was to make sure that in Device Manager the ADB Interface driver was showing "My HTC" and not "HTC Bootloader". I was able to switch between drivers using the update driver button, and didn't need to download any new files or specify a folder or anything.
use windows xp and try my method of downgrade from 2.1 in my sig.
Hey guys, as you can see im new to this forum, i have a G2 touch that isn't rooted or anything like that and decided to update to the new ROM on HTC site so i could get OTA upates for 2.1
So i've got all the right drivers for HTC sync (comes up as "ADB Interface - My HTC" in device manager) so that it stays connected when i launch the RUU on my laptop (running Win 7 64-bit), but then when it goes into the first part of the update where my phone is in the bootloader?? part HTC Sync decides to disconnect and the update says its not plugged in an cancels the RUU and im stuck with my phone in what i think is bootloader (it says RUU USB on the screen when plugged in then changes to RUU when i take the cable out)
Anyway, can somebody please shed some light onto what is happening and give me a hand on how to successfully install the ROM update or point me in the direction of a good how to guide
Cheers!
it's a driver issue, update your drivers AND make sure you have the latest version of the htc sync software.
If possible use a machine that isn't using Windows 7 as it's known to cause issues...
Windows 7 has no real issues, just does it differently. Just reinstall the drivers when in the fastboot bootloader mode. Fixed.
i wanna get s-off and root on my wife's phone using the revolutionary method so she doesn't lose any data, problem is that I can't get the HTCDriver3.0.0.007 on my windows 7 machine to open up, i get a windows popup that asks is it ok to run this file, i hit 'ok', then that's it, setup never starts. so when i try to run revolutionary, i get stuck at the 'zerging root' step. apparently it won't get past that step until after i get that htcdriver to install.
i've made sure the phone was in usb debugging, updated windows, tried to download that same exe from other sites, and still nothin.
anybody have an idea of what to do
There's no point bothering to run Revolutionary until you get the driver installed....
Are you logged in with admin privileges on Windows ? Is a User Access Control window popping up that you don't see and aren't responding to ?
You could use HTC sync to get the drivers that's what u did...
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
the only window i get is the one asking if i'm sure i wanna run the file, i hit yes and nothin else happens. i'm the admin, i even ran hit 'run as admin' and it still nothing happened. i've tried other exe files that i have on my computer to see if they would run and they ran. it's just this one
i thought htc sync had to be disabled in order to use revo though
Sync does have to be disabled, but I think what Revos means is install the sync and connect your phone. It should at that point automatically install the htc driver for your specific device. Then remove the HTC Sync and leave the driver.
Stratejaket said:
...but I think what Revos means is install the sync and connect your phone. It should at that point automatically install the htc driver for your specific device. Then remove the HTC Sync and leave the driver.
Click to expand...
Click to collapse
Don't the instructions at revolutionary.io say exactly that ?
how could i uninstall sync and not uninstall the driver with it
The installer from HTC includes multiple pieces that show up individually in Add/Remove Programs. Easiest thing is to try it...
Sent from my ADR6400L using XDA App
i FINALLY got it! i reinstalled htc sync, it was over 100 mb. then deleted it. after that, i plugged the phone in and mounted it as a disk drive, so it installed whatever drivers it needed. then mounted it as htc sync; windows installed more drivers. then i set it to charge only, enabled usb debugging and ran revolution again, and it finally worked. she's rooted!! thanks!!!
Same thing was happening to me when I was tryin to root my mom's Thunderbolt. Couldn't get past the "Zerging Root..."
So contrary to what all the guides say, I installed HTC Sync, it installed all it's pre-requisites during the install, UPDATED HTC Sync to latest version, it updated all the pre-reqs again, mounted phone to computer as a disk drive, waited for drivers to install, mounted phone to HTC Sync, waited for all drivers to install, confirmed that HTC Sync was communicating the phone, set phone as Charge Only, waited for drivers to install, unistalled HTC Sync, ran Revolutionary, waited a minute, it FINALLY got past Zerging Root!
Hope this helps anyone else who has been tearing their hair out over this issue...
Alternate solution for rooting with latest ota...if you have locked bootloader
For those of you that have endured the frustration of updating to the latest software version (2.11.605.9) There is hope! Apparently with this software version, the bootloader is locked. And for some reason this version would not allow the "Revolutionary" rooting method to work. (I would imagine everyone with this problem had issues with not being able to get past Zerg Root. At least that was the problem I had)
Anyways, I got my phone rooted....heres how.
Per the instructions for using Revolutionary, install the driver as stated on their website. (Make sure HTC Sync is not installed on your computer)
Download Mecha_2.11.605.3.zip (I'm a newbie here so I cant post links, but I found it through Android Police but if u google it its easy to find, its hosted on multi upload) rename the zip file as PG05IMG and put on the root of your SD card (as you would in other rooting methods) and run the bootloader.
Once its booted and all that fun waiting is over and your TB powers back up, make sure to turn off all wireless connections to make sure OTA doesnt try to upgrade you. (I turned on airplane mode as soon as I could)
From there run Revolutionary as instructed from their website. Worked like a charm for me, and hope it does for all of you with this same problem.
I TAKE ABSOLUTELY NO CREDIT FOR THIS SOLUTION. Thank you for all you developers out there that make our phones able to be so much cooler and more enjoyable. I'm just glad I could help in this marginal way, and hope that someone will find it usefull. SPREAD THE WORD IF YOU KNOW OF ANYONE HAVING THIS PROBLEM
Thunderbolt Tool
I was able to S-OFF and ROOT my Thunderbolt by using the Thunderbolt Tool located at this link... rootzwiki.com/topic/27310-all-in-one-the-htc-thunderbolt-tool
This app does it all for you, just follow the instructions.
I have a problem with using HTC dev.
After pressing Fast boot and plugging it into my computer and my computer (windows 7) makes an error sound. I thought nothing of it and continued, when it came to the time when i had to get the identifier token, it didn't show.
Instead it said "Waiting for Device".
I googled it and i found a page, I uninstalled HTC sync and it still came with the same result.
Might there be something wrong with my drivers? If so how can i fix it?
Please help me , i wanna get back into rooting after leaving the iP4.
Thanks
Did you have HTC Sync enabled while you had the phone connected to your computer? If so, it should have been disabled.
Have you made sure you have the necessary drivers installed?, I had the same problem I think and this was my problem (I think), also did you restart your computer after uninstalling HTC Sync? Cause (I think ) it has to be disabled for the DEV unlock to work.
I had the exact same problem when trying to unlock the bootloader on my Rezound, I tried everything that was mentioned above and had no luck. But the second I used my friend's computer to do it all, it worked perfectly fine. I don't know why but for some reason my computer just would not recognize the device in fastboot no matter what I did. Hope this helps.
While the drive is connected, get to the devices screen.
You should see an Android section.
Right click on the device listed under Android. Click uninstall.
Unplug the device and wait for the device list to update. The Android section should disappear.
Now plug in the device again, and it should load the device driver again.
Give it a sit.shot after that.
Hello,
I am new to these forums, therefore I cannot post into a Development thread.
I rooted and flashed a ROM on my phone (Genome 2.0 to be specific.)
It was a fine ROM, but I actually prefer Sense 4.1+ for right now and wish to go back to stock due to support reasons for my company as well. I saw a thread where you can use RUU. However, I cannot get the program to detect my phone (the dreaded error 170.) I also am in the process of using the ZIP file method where you grab it from the temp while RUU is open (getting it on my SD card has been another story.)
However, in the event I cannot get this to work, can someone who has got their DNA back to stock from root/ROM please give me some troubleshooting for the drivers? HTC Sync isn't detecting my DNA when there are no drivers. I wish to know how to remove ALL drivers for this phone from the device manager so it is as if I never had this device connected to my PC. I believe if I had these removed, it may help a lot of the issues I am having.
After hours (about 5 hours total) of checking into this, I figured out that it was trying to install the windows USB drivers for whatever reason. I just manually uninstalled whatever drivers it was trying to install (in this case, it showed up as Android 1.0 in the device manager.) I reinstalled it and manually browsed to the HTC folder in x86 Program Files after downloading and installing HTC Sync. It installed these drivers, showed up as MyHTC Phone, and I profited from my bloated factory Sense 4.1+ phone
In case anyone else was wondering, here are the steps:
http://forum.xda-developers.com/showthread.php?t=2017525
Let me amend his steps:
1. When you boot back into your bootloader, go into Fastboot.
2. Make sure you uninstall any PDANet drivers or all drivers you had on your phone while rooted/ROM'd up.
3. Download HTC Sync Manager and install.
4. Disconnect your phone from USB and reconnect.
5. Install drivers manually from HTC folder in Program files x86.
6. Run RUU.
Going to attempt to unlock the bootloader again, shouldn't have any issues since I took care of that initially before I rooted this phone. I hope that I have solved a few people's issues who might have been like me scourging the internet hopelessly for help.