Help HTC Desire G7 disaster when upgrading

[henrymorgan]

Used HTC Android Phone ROM Update Utility 1.0.3.2011 and ended up with "Error [152]: Image Update Error - The ROM Update Utility cannot update your Android phone."
I can't get it to recover either. Any help to get it back to where it was before would be much appreciated.
Also, HTC Sync (2.0.4) won't see the phone anymore.

 

[Hadron]

Hi Henry, and welcome to AF,

OK, the RUU has failed part way through the update. That's usually recoverable, but we'll need to know a bit more about your phone.

Firstly, what type is it (GSM or CDMA? If you don't know, what network are you on and what country (actually tell us that anyway)? Can you provide a link to the RUU that you were trying to use? And which image was it trying to update when the error occurred.

What happens if you do try to boot the phone: describe what you see on the screen. Can you get into fastboot mode (boot while pressing the "back" button, and you should get a white screen with some little androids at the bottom, a simple menu and the word fastboot). That's the other mode you can run RUUs in. If it's really bad you might have a black screen with little warning symbols and the word "RUU" on it, but that's OK because an RUU (ROM Update Utility) is what we're going to have to use anyway. Most of the questions at the start were just to help with finding a suitable alternative RUU for you.

Don't worry about HTC sync - it won't see the phone until you can boot into android, which means until this is fixed. But it's not necessary for this.

Edit: Final question: why were you running the RUU? Just fancied an update, or were you having problems with the phone?

 

[henrymorgan]

Hi Hadron - I'm in the UK.

1. The phone was originally T-Mobile but I have unlocked it and it was working fine with my Vodafone sim.

2. The RUU filename is "RUU_HTC Desire Android 2.3 Upgrade (Gingerbread)". It's dated 29.07.2011.

When you hover the cursor over the filename it says "Acresso Software Inc" and "file version 15.0.0.498". I downloaded it as a torrent.

3. The current image version is 2.29.110.6 (according to the RUU) and is offering to upgrade to 3.14.405.1.

4. It failed at the radio image.

5. On boot-up I get a black screen with "htc" in the centre and the warning triangles in each corner. It's the same in fastboot, however if I connect to the computer via usb cable, boot up (same black screen) but then disconect the cable, I get a white screen with warning triangles at
the bottom and at the top:

BRAVO PVT4 SHIP S-ON
HBOOT-1.02.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Jul 22 2011,16:19:16

RUU

When I reconnect I go back to the black screen.

6. I was repairing the phone for a colleague and wanted to give him the latest software.

and it was all going so well ....

I hope that's enough information and you can dig me out of this hole!

PS Just run the RUU again and, having failed, I disconnected the USB cable and the following information appeared:

"Parsing...[downloaded ZIP]
[1] RADIO-V2 - Fail-PU
[2] SPLASH - OK
[3] RECOVERY - OK
[4] SPLASH2 -OK
[5] RADIO_CUST - OK
[6] BOOTLOADER - OK
[7] USERDATA - OK
[8] SYSTEM - OK
[9] BOOT - OK
Partition update fail!
Update fail!"

 

[Hadron]

Aaargh, it would be the radio! OK, that's not good, but it's sometimes recoverable with a different RUU.

Problem is, RUUs are ROM Upgrade Utilities, so won't let you downgrade, and it has upgraded your HBOOT. So it may well be that no other RUU will run.

What I can suggest is downloading a new copy of the 2.3 upgrade from shipped-ROMs.com. These provide md5 codes, which you can use to check whether the download is good before running the RUU. The 2.3 upgrade is near the bottom of the list, in a zip (together with some other stuff).

Otherwise the most recent TMP-UK RUU I can see there is Shipped ROMs. Unless you have a "goldcard" you will only be able to run T-Mobile RUUs or the 2.3 upgrade - the phone was originally T-Mobile and the RUU will check.

I'd try a fresh copy of the 2.3 upgrade first, then if that doesn't work we'll just have to see whether the T-Mobile one will run with the phone in this state despite the 1.02 hboot.

Before trying, do remove the battery for a few minutes, make sure everything is discharged and cool.

Good luck.

 

[henrymorgan]

Hi Hadron

The steer was good; must have been a corrupted RUU as the new one worked fine 1st time.

After a bit of stuttering, the phone worked, but it does seem a bit unstable. It occasionally goes into a reboot cycle and eventually gives 7 buzzes, which I think means it's overheating. Possibly the wireless setup; just tried to download a "live" wallpaper twice, and each time it's rebooted.

The welcome sound on initializing is incredibly LOUD; any way of tweaking that?

The reason I had my colleague's phone in the first place was because he had dropped it, shattering the glass and LCD, which I replaced. I suspect the motherboard might not be too happy;I've found on some blogs the originals could be troublesome.

Many, many thanks for your quick and incisive input and help. If you can suggest anything else I could (or should) do with the phone, I would be eternally grateful.

 

[Hadron]

PVT-4 (late hardware revision) devices don't usually suffer from overheating, but 7 vibrates usually means a serious hardware problem. Were there any problems before the fall? If it tends to fall over when the cpu is being exercised that could indicate an overheating problem - 3G downloads do generate heat, though I'd have thought that a wallpaper would have been fairly quick. Trouble is, if it's the motherboard there's not much the end user can do apart from replace it.

Yeah, the startup sound is particularly ironic because it's accompanied by the phrase "quietly brilliant"! . Unforunately it's in the /system area, which is inaccessible unless you root the phone (gain administrator access). That was my fix - I've been running custom ROMs since a month or two after I got the phone (almost 3 years ago now).