Related
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
I should be very grateful for any help.
Firstly, the website for the Desire goldcard image creator is down. All (current) Desire goldcard creator guides seem to point at http://psas.revskills.de/?q=goldcard which is giving a 404 error. Can anybody advise on a different method of creating the image, either another utility or manually? Thank you.
Secondly I've had major problems with my Desire and would appreciate any support. I've done plenty of searching and nothing helps. I rooted it via unrevoked, S-Off via alpharev, and provider unlocked it using the ISO tool.
Having had some stability issues I decided to RUU back to the original using the Froyo 02 RUU from shipped roms. However when I run it I got "ERROR [110]: FILE OPEN ERROR" at the point "updating system... 80%"
This has happened once before on my Desire; I sent it back under my insurance / warranty. This has now happened again on the replacement.
I've done lots of searching around and tried all sorts but not much seems to be working.
I've tried redownloading RUUs, various ones from shipped roms and running them (it's not a corrupted RUU download, I'm relatively certain) and I either get the same error 110 at the same point or I get a CID error. I don't have a goldcard and am unable to create one due to the creator webpage being down.
Flashing PB99IMG.zip downloaded from shipped roms, flashing using FASTBOOT, comes up with incomprehensible gibberish on the screen and no apparent effect on my desire.
If I run "fastboot oem boot" the device successfully boots into unrooted O2 branded Froyo ROM, but unrevoked or other rooting procedures don't work due to the lack of ability to get to hboot and the lack of goldcard. On reboot, I get the same HTC "bricked" logo with a warning triangle in each corner and have to "fastboot oem boot" again.
Any assistance offered would be very gratefully received indeed! Thank you.
Current Software Information:
Android version 2.2
Baseband version 32.44.00.32U_5.09.05.30_2
Kernel version 2.6.32.15-gd96f2c0 [email protected] #1
Build number 2.14.207.1 CL2233777 release-keys
Software number 2.14.201.1
Thank you
Ah, the goldcard maker / web server must have been having a temporary glitch (couple of hours), it's back up now. I've made a goldcard and have successfully installed a WWE RUU. Relief!
Anybody else with error 110... good luck, I wish there was a reliable solution.
Thank you
The site seems to be working now, well at least for me its working.
I had rooted my Desire about 1 year ago. Updated to GB 8 months ago (forgot which ROM). Friday my phone stopped Sync'ing all mail/twitter/fb etc. Figured it was time to upgrade to a new ROM. Since I was still S-On, I ran Revolution and got to S-Off. I then wanted to change to 4EXTRecovery, but couldn't get it to take. So tried to run the updated CWM and that didn't upgrade the Recovery version (2.5 something). I figured I would start over from RUU, so ran a RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe. It failed with an Error 130 Wrong Device. So I figured I need a Telstra version (branded phone), so ran RUU_Bravo_Froyo_Telstra_WWE_2.26.841.2_Radio_32.48.00.32U_5.11.05.14_release_150162_signed and I get an Error 140 bootloader. The phone is now at the black htc screen with 4 exclamation points. When I unplug the usb, it shows the following:
BRAVO PVT1 SHIP S-ON
HBOOT-0.00.0000
MICROP-031d
TOUCH PANEL-SYMT0101
RADIO-5.11.05.14
Mar 29 2010,21:34:33
RUU
I think I can still AndroidFlash it, but it gives some FAILS in the log and doesn't change the above info when trying the AlphaRev hboot files.
Any suggestions? I have been searching for 2 days on ways to get this fixed. I can't get to fastboot or recovery, and ADB doesn't list the device.
Cheers
Download the downgrade.img from alpharev
Pull teh battery out of the device, replace.
Hold Back and press power
At the 4 triangles (you are actually in fastboot) Connect USB
Fastboot flash hboot c:\downgrade.img (or whatever the path\name is)
Once complete, pull battery again
Back and power again
Run Correct RUU
Also, if you want to flash a stock ROM, you can flash
RUU_HTC Desire Android 2.3 Upgrade (Gingerbread).exe
and you can download from HTC dev site, but first we wait news from you that you fixed the boot problem
When I run AndroidFlasher with the downgrade.img selected as bootlooder I get the following:
1. When clicking "I'm in fastboot", the window just sits there and nothing happens (waited 10 miutes).
2. Without "I'm in fasboot" ticked, it gives "Error your phone is not plugged in or drivers aren't installed" then "Error, your phone is S-On"
Cheers
As you posted above you are s-on you can not flash downgrade, you need to flash correct ruu
Sent from my HTC Desire using XDA Premium App
St Veronus said:
When I run AndroidFlasher with the downgrade.img selected as bootlooder I get the following:
1. When clicking "I'm in fastboot", the window just sits there and nothing happens (waited 10 miutes).
2. Without "I'm in fasboot" ticked, it gives "Error your phone is not plugged in or drivers aren't installed" then "Error, your phone is S-On"
Cheers
Click to expand...
Click to collapse
Not to worry. You're s-on then. We had to try as it states hboot version 0 which doesn't exist so we don't know what's true and what's not. Continue with my steps
Sent from my HTC Desire using Tapatalk
Okay, thanks for the help! I had to register an account on dev.htc.com and then go to the "Kernal Source Code" page. The top link was the one needed, "HTC Desire Android 2.3 Upgrade" and after downloading the rar file and extracting it, there was the file "RUU_HTC Desire Android 2.3 Upgrade (Gingerbread).exe" inside. Running this fixed the issue! Now to re-read all the steps to do the S-On/Root/4EXTRecovery again from start to finish!
Cheers
St Veronus said:
Okay, thanks for the help! I had to register an account on dev.htc.com and then go to the "Kernal Source Code" page. The top link was the one needed, "HTC Desire Android 2.3 Upgrade" and after downloading the rar file and extracting it, there was the file "RUU_HTC Desire Android 2.3 Upgrade (Gingerbread).exe" inside. Running this fixed the issue! Now to re-read all the steps to do the S-On/Root/4EXTRecovery again from start to finish!
Cheers
Click to expand...
Click to collapse
Great, now u can uae alpharev to S-OFF again and root
Sent from my HTC Desire using XDA App
marius.a said:
Great, now u can uae alpharev to S-OFF again and root
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Actually no. Alpharev only supports already rooted 2.2. Revolutionary is required here
Sent from my HTC Desire using Tapatalk
Hi there,
as I recently bought the HTC One X, I wanted to reinstall a Stock Rom to my old Desire. Unfortunately it won't work for some reason, as I always get an Error [110].
I have tried the following releases from this thread: http://forum.xda-developers.com/showthread.php?t=695667 :
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
(the phone used to be branded by o2 Germany, but I wanted to install a branding-free rom).
When I try to start the boot loader of the Desire now, I just get the HT screen with warning signs in all 4 corners. Please find attached a photo of the screen + a screenshot from the error message (for some reason it's in German, but you'll get the idea).
As I cannot access the actual hboot (CM7rev2 hboot was installed) I can't even install a "normal" rom.
As I don't necessarily need the phone right now it's not that urgent, but I hope you can help me anyway.
Cheers!
did you change hboot back to stock? I haven't done it first time and got the same problem. there is a solution but can't remember where.. try googling..
Sent from my HTC Desire using Tapatalk
No, forgot about that, but now it seems like it's too late to do this, isn't it?
From my understanding, that state your phone is in is fastboot. That means you can probably flash the hboot downgrader from alpharev and run a RUU again.
via xda app
your phone is in fastboot mode at the HTC logo with 4 "!". Download hboot downgrader from alpharev and flash it before rerunning RUU.
Sent from my HTC Original Desire with Android 4.0.4 ICS using Tapatalk
but if you dont have S-Off, cant access to anything instead of fastboot.. from which i can only flash stock ruu's but no one of ruu's are installing successfuly.
so i cant flash hboot, recovery or anything else... that means that the only solution is to reach nearest JTag service...
hm... but if he forgot to downgrade then I assume that he was s-off. so it's doable. I was there... scared the p*ss out of me... ;-)
Sent from my HTC Desire using Tapatalk
me to have some problems in this thread
http://forum.xda-developers.com/showthread.php?p=25349685#post25349685
heraSK said:
hm... but if he forgot to downgrade then I assume that he was s-off. so it's doable. I was there... scared the p*ss out of me... ;-)
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
He should still be S-Off if he's still on CM7r2 hboot.
Sent from my HTC Original Desire with Android 4.0.4 ICS using Tapatalk 2
It won't work with revolutionary / alpharev, it's always stuck at "Waiting for device".
I really don't know what to do now. Any other ideas?
EDIT: I also tried unrevoked just to see if it recognizes my phone, but its the same there: "Waiting for device".
Its late and I'm tired so sorry if you've already tried this...
Install HTC software on your pc and android sdk (to get the drivers and fastboot)
Plug in your phone when its on the 4 !'s screen
fastboot flash alpharevs bravo_downgrade.img
unplug the phone, pull the battery, put it back in, turn it back on then plug it back in (or just reboot the boot loader with fastboot)
then try running this RUU http://www.filefactory.com/file/b4a4027/n/RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
If that doesnt work see what version it says you're when the ruu says what version you're on and what you're updating to and download the ruu with the same number as the one you already have and see if that helps.
I need an Obi-wan here. I'm a noob -- though I've gotten a solid four day education
hacking at this problem.
My wife's Android Desire Z - Stock ROM, S-ON, got stuck looping with a failed
android.process.acore message and after trying a cache clear that didn't help
I set out to factory reset it. Figured the nuclear option would be dead simple. Nope.
Factory Reset from the Hboot menu simply froze the phone
at the HTC menu for an hour. Not good.
From there dozens of resets and reboots and fastboots would sometimes successfully boot
to my wife's setup (so nothing was reset at all), only to get stuck in the acore loop again.
I was once quick enough to put it into
airplane mode and that stopped the error message loops. YAY! I could try a reset
via software! But when I attempted
Settings > SD & phone storage > Factory data reset it rebooted to HTC screen, Vodafone
screen, HTC screen, vodafone screen. ANOTHER loop.
OK, next try was to flash the ROM with an original shipped version.
Couple forums in Dutch said the shipped ROM for the Vodafone Desire z in NL was Bravo/Froyo World Wide English
so I located this file:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_
signed.exe
and attempted reset by running that on a pc.
But the USB connection failed after the unit reset: Error 171, Error 170.
Tried installing HTC Sync AND the Universal boot drivers
and the Android Booloader Driver, as per the helpful advice from Bob Denny at Phandroid. (As a noob, I can't post links here, sorry)
And yep, I disabled anti-virus, had a fully charged phone (I'm hoping you get
the picture here -- I've done my due dilligence and googling before asking for help.) but
nada. RUU rebooted the phone, waited for the bootoader, and either the phone never pings the USB
port to say it's there or the PC doesn't see it.
FINE. I can put a PC10IMG.ZIP on the SD card and dispense with the frustration of messing with windows, right? Well, no.
I extracted ROM.ZIP from the RUU renamed it PC10IMG.ZIP and slapped it in the root
directory of the SD card. I booted to Hboot with the volume down and power buttons, chose
Fastboot and watched the the Zip load (blue verticle progress bar upper right of screen),
check it (brown progress bar upper right), then NOTHING -- back to the Hboot menu.
No error message, and no invitation to
update. Reboot takes me back to screen loop. Normal power-on does the same.
Further searches make me question if this is the right shipped ROM.
The RUU reports that I'm running version 2.42.161.22
(of what? Vision Gingerbread?) and the Bravo/Froyo WWE Rom reported itself to be version 1.59 something.
As this is an S-ON phone, I know I can't roll back to earlier ROMS, and can only install
the exact version as shipped.
So the questions I THINK I need answered:
1. Does anyone know for certain, or know where I can find out, which ROM
shipped with the Vodafone NL Desire-Z in 2010? I can get Kernel source for it at the HTCDev site,
but I see no compiled ROM there -- anything I can do with kernel source?
2. Anyone know where can I get the right PC10IMG.ZIP file to flash the unit from the SD Card? (I tried Shipped-Roms.com and
dozens of google permutations)
3. Is my methodology for flashing the SD Card right or is there anything in the
description above that lends anyone to believe my problem or solution is anything
other than the one I'm obsessing over?
Any help deeply appreciated.
Info from Hboot screen:
VISION PVT SHIP S-ON
HBOOT-0.05.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-BOOT
Apr 11 2011, 23:36:27
Image CRC:
osbl: 0x1B4C7A4C
amss: 0xEF10821B
hboot: 0xCCCC4C36
recovery: 0x9627D8E8
system: 0xB6CE69CE
Please tell me I'm a stupid Noob and I've missed something so obvious I'll leave a
facepalm scar on my forehead, then tell me what it is so I can fix this dang phone and
get my life back. I'd be one appreciative noob.
-b
Try again with the PC10IMG.zip, this time don't extract the rom image, flash the entire zip. If this doesn't work you may need to make a goldcard. This means you will need to boot the phone and get into setting to turn debugging on and will will also need to get the proper window drivers up and running in order to use adb. (Try holding the s key on the key pad while powering on, this may keep the bootloop away)
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
Try again with the PC10IMG.zip, this time don't extract the rom image, flash the entire zip.
Click to expand...
Click to collapse
Yeah, sorry wasn't clear I extracted the zip from the RUU, not the rom itself, so I've tried this one already.
Safe boot doesn't boot -- gets me the HTC screen and freezes there. I'll keep trying, as I think gettting debugging on and going gold card may be my only hope if the problem isn't incorrect ROM (or if there's no finding the correct one).
Here's a simpler question: If in my hboot screen I see
VISION PVT SHIP S-ON
Does that mean the shipped ROM was vision gingerbread and that's the only one to try,
or could my wife's "system updates" upgraded the phone from a Bravo shipped ROM?
And when I get a CID Incorrect error on a Vision Gingerbread ROM, does that mean the WWE Vision Gingerbread ROM I tried to install isn't good because it's not Vodafone, or because it's not the shipped ROM?
Any help will be thankfully appreciated!
Sorry it took so long to get back,
ship s-on is referring to you have a shipped bootloader and your security flags are on, that line is not specific to any version of the desire z
You won't be able to flash any ROM like that unless it is an upgrade from current version. I believe if you go to HTC website the latest ruu was not released as an ota and may work for you as its probably newer. If it doesn't work then you will need to get super cid in order to flash something older, which means you need to get adb working
Sent from my Nexus 7 using xda premium