Hi!
I have (had maybe) officail Android 2.1 with sense. Yesterday an OTA update showed up, so I updated the system and the phone is now down.
System doesn't start at all... Only HTC logo shows up, I can't flash any official HTC rom.
Errors:
140: wrong bootloader version, 131: wrong client ID
the only error information from HTC phone is... as I show on picture... very informative and descriptive
I've tried 6 offficial update rom's from HTC.
The phone error statement is red error sign...
Graphic, no text :/
I attached a photo with this
All the thing is quite recent, any ideas?
Cheers!
Paweł Lipko
What you need to do is download the android recovery system, see my sig (RA-hero-v1.7.0.1 Recovery). Install that and then let us no when you have. This will enable you do do other things and then we can go from there.
Hi again!
At the beginning I would like to say thanx for help
Ok following "RA-hero-v1.7.0.1 Recovery" thread I've downloaded SDK with ADB.
To be correct with the timeline, I'll tell that this PC already has got HTC drivers coming with HTCSync software. Probably I write too much, but it's better to have too much of information than too less
Before the problemm which we are trying to solve here - phone worked fine with windows. Now XP says, that "device hasn't been recognized succesfully and the gear could not work correct. (I don't know english version for that, Polish Windows I have )
Next - ADB doesn't see the phone:
\Android SDK\tools>adb shell reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Restarting windows - doesn't help
Trying to list devices in ADB - none
restarting AB daemon - doesn't help
Removing HTC Drivers and HTC sync (it was old version for android v.1.5 and 1.6. Still it worked before disaster with 2.1 )
Rebooting XP
Installing HTC Sync for Android 2.x. This include: HTC BMP USB Driver 1.0.5375 (32Bit), HTC Driver Installer 2.0.7.018
After installation new HTC Sync, XP says that it recognized the phone correctly, but still I have no access to SD Card storage. Only drive letter shows up. Lets take it as progress
still yet ADB gives output:
\Android SDK\tools>adb shell reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've tried to puty the same command with FastBoot and HBoot - but - nothing new comes with that...
At this level I think I'm stuck.
knock knock - any ideas?
What operating system are you running? Definatly a driver issue.
Windows XP SP3 Polish ver.
HTC Drivers as I wrote earlier - latest from htc.com
As for now I'm downloading HTC Sync also for older Androids - 1.5 and 1.6.
I'll try to remove this HTC Sync for And 2.1 with drivers and install that for 1.5 & 1.6.
If You say, it's a drivers issue - maybe there is a mess on my PC, I'll try using another one or two with both HTC Sync versions and give You a reply.
But when the disaster happened I tried to flash Hero with official ROM and I've had only info's like error 131 or 140 - as I mentioned at the beginning.
And it was other PC, with brand new HTC Sync, so the driver problem could be... no the clue...
I'll post when I'll try to install HTC Sync on other PCs.
Cheers!
Paweł
Shadow_82 said:
Windows XP SP3 Polish ver.
HTC Drivers as I wrote earlier - latest from htc.com
As for now I'm downloading HTC Sync also for older Androids - 1.5 and 1.6.
I'll try to remove this HTC Sync for And 2.1 with drivers and install that for 1.5 & 1.6.
If You say, it's a drivers issue - maybe there is a mess on my PC, I'll try using another one or two with both HTC Sync versions and give You a reply.
But when the disaster happened I tried to flash Hero with official ROM and I've had only info's like error 131 or 140 - as I mentioned at the beginning.
And it was other PC, with brand new HTC Sync, so the driver problem could be... no the clue...
I'll post when I'll try to install HTC Sync on other PCs.
Cheers!
Paweł
Click to expand...
Click to collapse
ah in that case error 131 or 140 is nothing to do with drivers, for error 140 as far as I know the ROM is not compatible. You will need to try find a version that is suitable. try the HTC website for updates.
Hmm.. You say that it's not drivers problem?
Well...
I already tried to flash these ROM's listed from XDA Developers:
[ROM] Official HTC Hero RUU ROM + Radio Links
WWE: (World Wide English)
RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_ NoDriver.exe
RUU_Hero_HTC_WWE_1.76.405.6_WWE_release_signed_NoD river.exe
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river.exe
RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_No Driver.exe
RUU_Hero_HTC_WWE_2.73.405.61_WWE_test_signed_NoDri ver.exe
RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDri ver.exe
I've tried also ROMs from official htc.com website.Europe website and Polish website - still its the same, but when something doesn't want to work...
ROM version 2.73.405.5
All of them gave me errors:
140: wrong bootloader version,
131: wrong client ID.
All of these ROM's weren't able to say which version currently is installed on my HTC Hero...
Total HTC Hero Eclipse
I'll try to flash them once again, right now I take my pendrive, I'll go to my friend and let's roll
God damn it - another Q - by the way
How I'll be checked to be able to post external links?
Should I ask some moderators?
Or it'll happen just like that in a month or year?
ok.
another PC, completetly not known to this HTC Hero.
first windows told me that it doesn't recognize the phone. It's ok. it doesn't have any drivers.
I've installed latest HTC Sync with drivers - the one for Android 1.5 and 1.6, filename:
_HTC Legend_HTC_Sync 2.0.40.exe
Rebooting windows and...
Windows still doesn't recognize the phone
Trying to flash it with one of official ROMs
Yup - error 170 - no connection with phone
adb devices - no devices...
next: uninstalling this HTC Sync
rebooting windows
installing new one for android 2.1
filename: _HTC Wildfire_setup_3.0.5422.exe
rebooting windows
once again windows doesn't recognize the phone
Trying to flash it with official ROM
filename: RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
Connection error... damn...
ADB:
\HTC SDK\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
After some fight with USB I managed to make Windows recognize the phone, a drive letter shows up, but I can't acces data on SDCard.
ADB after restarting it's daemon doesn't see the phone
Another try to flash it with official ROM
ok. there's any progress - RUU App sees the version on the phone
trying to flash the phone
and... error 140 - wrong bootloader ver.
ADB: error: device not found
I'm starting to be confused...
Any ideas?
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.
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.
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.
Hey
I've got a problem updating my HTC Mozart.
It's a device from T Mobile Germany, which has the standard firmware.
In the Development-subforum there is a new firmware, 1.28.xxxx
My problem is that I can't update my HTC Mozart.
If I start the updater on the PC with the mobile connected, it quits after a timeout stating ERROR 260 - CONNECTION ERROR.
Is there anything I have to do or - better yet - a step-by-step instruction?
Do you have any idea, why it might fail?
//EDIT: I'm trying to flash from a Windows XP PC (32 bit) via USB.
And yes, I tried to use the bootloader, but it only displays SERIAL.
Could you please help me?
FrozenLord said:
Hey
I've got a problem updating my HTC Mozart.
It's a device from T Mobile Germany, which has the standard firmware.
In the Development-subforum there is a new firmware, 1.28.xxxx
My problem is that I can't update my HTC Mozart.
If I start the updater on the PC with the mobile connected, it quits after a timeout stating ERROR 260 - CONNECTION ERROR.
Is there anything I have to do or - better yet - a step-by-step instruction?
Do you have any idea, why it might fail?
//EDIT: I'm trying to flash from a Windows XP PC (32 bit) via USB.
And yes, I tried to use the bootloader, but it only displays SERIAL.
Could you please help me?
Click to expand...
Click to collapse
I didn't think that there were any actual updates available yet :S
Well there is a new version in the development subforum
It's an inofficial update, but that hasn't stopped me before...
In the meantime, I even managed to solve the problem:
Windows XP needs USB drivers in order to be able to use the RUU.
HTC's RUU doesn't provide any driver as it seems - and neither does Zune.
I had to install Active Sync (version 4.5 seems to be the latest) in order to get the driver - although the HTC Mozart can't be synced using Active Sync.
After that it was just going to the boot loader and starting RUU.
Hello,
I'm really desperate on.
I fail already get 8.1 32bit running for weeks because HTC Fast Boot in Windows.
I found googled without end and thousands of tips. All to no avail.
Off the driver signature. Installation of the latest HTC Driver.msi. Install ClockWordMod Universal ADB Driver. Installing HTC Sync ..
But the fastboot driver is always available with the following error:
Error on a request of the USB BOS descriptor.
According to the description on the internet I will KB2917929 import. Have I done, nothing changed.
What am I doing wrong?
LG
Robert