Develop Bugs

[Q] Can't install any RUUs

I've just got a Desire on Orange, which I'm trying to debrand. I've made a goldcard, but when I try to install a stock RUU (with the phone connected in HTC sync mode etc.), the installer always quits just after the inital 'setup' progress bar.
I've tried 3 or 4 different RUUs, and they all quit at the same point. Has anyone else had this problem?
btw, I'm on winxp sp3 and have admin rights

xdpm said:
I've just got a Desire on Orange, which I'm trying to debrand. I've made a goldcard, but when I try to install a stock RUU (with the phone connected in HTC sync mode etc.), the installer always quits just after the inital 'setup' progress bar.
I've tried 3 or 4 different RUUs, and they all quit at the same point. Has anyone else had this problem?
btw, I'm on winxp sp3 and have admin rights
Click to expand...
Click to collapse
I would advice you not to press sync mode on phone, just connect usb and then open and run RUU. Also are you using wwe version?
And details of which firmware you are on would be helpfull. And does any message pop up when it quits?
Sent from HELL using XDA App

Thanks for replying
I've tried to install the generic Froyo HTC 2.09 WWE RUU from [FAQ] HBOOT 0.83 / 0.92 / SLCD - rooting and recovery (can't post links yet, sorry)
and a couple of others, including Froyo HTC WWE 2.10 and HTC WWE 1.21/1.15
Every installer has the same problem. Plug in phone, run installer, the progress bar fills up and then it quits. No error message.
I tried updating drivers, as in this thread [Guide] Drivers & RRU Errors Solved in case it was anything like that, but it hasn't made a difference.
Phone details:
Firmware ver. 2.1-update1
Software num. 1.22.61.1
HBOOT 0.83, SLCD screen

Remember you need a gold card in the phone to install a non-Orange RUU

Yep, done that. I haven't taken it out of the phone since I made it. Does the version of HTC sync I'm using make a difference?
I downloaded the version offered on the HTC website, instead of the one that came on the memory card. I've just installed the memory card one now, i'll try everything again using that, including remaking the goldcard.

Having played around with it the other HTC sync installation, it's still not working...

[Q] Can't unroot my Desire - really stuck!

Hi guys. My first post on here I think, but I have been lurking a while and using a couple of the ROMs on the developers forum.
My Desire has a problem where it reboots itself whenever hot. This happened on the standard ROM but has continued when using custom ones also. I've been meaning to send it back to O2 for about a month now but haven't got round to it. I thought I better get it back to standard before I return it, but that's where things started to go wrong.
Both my work PC and laptop wouldn't entertain the phone being connected. HTC Sync could not see it. Downloadd the latest version, tried restarting with only Windows services running etc. but no joy.
So I brought the phone home and connected it to my home laptop, which detects it. I downloaded the SDK and installed the Google USB drivers, all seemed good. I tried to run the HTC ROM Update Utility, but have had various problems.
I am trying to use the O2 RUU from the forums here.
The most common problem is ERROR 140:BOOTLOADER VERSION ERROR
I'm currently running a Froyo ROM.
I have also noticed, that if I reboot the phone to the bootloader and then plug the USB cable in, it goes back to the old Android 1.0 on device manager, which it only does if connected during bootloader. This cannot be changed, no matter how many different drivers I try to update it with.
Any help here would be much appreciated. My warranty expires in May!

Was your phone o2 branded originally?
Sent from my HTC Desire using XDA Premium App

It was, yes.

You might need a goldcard even though your phone was originally o2. Also the failsafe solution is to extract the ruu zip file from the flashing utility, put it on the sd-card and let it flash it automatically.
This way you eliminate a lot of potential errors.
edit: error 140 is bootloader version error. It means your current bootloader is newer than the one in the ruu and the utility does not allow a downgrade. You will either need to find an o2 ruu with the newest bootloader or use a wwe one with a goldcard instead.

Your issue is not related to having a gold card inserted. The message is pretty clear: Your phones hboot is to new (or the RUUs is to old, if you want to put it that way). RUUs will typically not allow you to downgrade hboot. Try to find a newer RUU with a sufficient hboot version or if you are S-Off, find an older hboot and downgrade yourself via fastboot.
Regards.
Edit: sorry... haven't noticed the edit in the post above.
Sent from my HTC Desire using XDA Premium App

OK thanks guys. I don't know what a goldcard is, I'm certain I never had to use one of those when I rooted the phone with the unRevoked method.
I may have found a better O2 ROM this morning, so will give that a try and let you know.

It worked! I'm onto an O2 Froyo ROM now

[Q] HTC Desire India edition RUU Question

I have an HTC Desire which I have flashed with CyanogenMod and rooted with Unrevoked. The phone restarts randomly; more often when connected to a power source. It recently got stuck on the HTC screen and kept rebooting. When I went to recovery, the phone would just reboot again. ClockworkMod Recovery had stopped working.
Then after connecting it to a Windows computer, it somehow booted to CyanogenMod.
When I tried Unrevoked again on a Mac, it said "USB Connection Error" after doing a bunch of things. I could access ClockworkMod recovery though.
The phone continues to restart.
--
To return for warranty claims, I need to restore it back to the Stock HTC ROM, for which I tried using two RUU files from the Development forum.
My baseband is 32U_5.11.05.27. HBOOT 0.93.1
Both the EXEs failed. I got a USB 170 error and 171 error while trying them on different computers with Windows XP.
I extracted the ROMs from the RUU, put them in the SD card and went to HBOOT.
With, the WWE which was marked 32U_5.11.05.27, I got an error that said "Wrong CID Version".
With the India version(the phone was purchased in India), I got an error "Main version is older".
I'm guessing I'm doing something wrong here. I haven't lost hope, but time is running out since I only have until the end of this week before the warranty ends.

Hi,
Did you manage to fix the issue, i too ran into the same issue and want go back to stock Froyo came with my phone.

Did you downgrade the hboot from Alpharev.nl before you run the ruu?
Sent from my GT-P7500 using xda premium

[Q] getting error 170 when trying to ruu

hello, I am new to this forum and I have a problem,
just bought a HTC ONE X it is a Vodafone UK(not locked) rom with Hboot 0.94.000 with software version 1.28.161.9.,the cid is vodap102, and the bootloader says locked, I tried to ruu based on what i saw on this post http://forum.xda-developers.com/showthread.php?t=2106250 with RUU_ENDEAVOR_U_ICS_40_Vodafone_UK_1.28.161.9_Radio_1.1204.103.14_release_256488_signed,
but i keep getting error 170 usb cable not cnnected. I have tried on all the usb ports with the same results.
My goal is to update the phone to 4.1.1.

Do you have the HTC drivers installed ? What do you get if you put the phone in fastboot usb mode and do a fastboot command
Fastboot devices

i have all the drivers installed and latest htc sync.
but somehow i managed to get it to check for updates from the mobile data network and now after 3 updates it runs 4.1.1 with sense+. Thanks for the support given keep on the good work!

Nice :thumbup:

[Q] Bootloader Err

Hello have tried using all the methods HTC dev/Easy Unlock/Revolution/AAHK
HTC Desire HD on Orange UK but has a Telus Rom installed. (Should be irrelevant right?)
None are working my phone is still S-ON
I'm running 2.2.1 Android
HBOOT is 2.0 something
Everytime i go to use "fastboot oem get_identifier_token."
It just errors me out, (Error 7 i think) and doesn't continue.
I get the feeling i need to update/downgrade something, but I keep searching endlessly to find nothing... ><
Any ideas?

Your hboot is too old and doesn't support bootloader unlock. AAHK is now retired and the server hosting the files it needs have been pulled.