New OTA Software update 2.29.110.6 HTC Desire

blackandroidph · March 16th, 2012, 07:57 AM

Hi

I just received an OTA update from HTC. The file reads OTA_Bravo_Froyo_TMO_UK_2.29.110.6-etc etc etc.zip. But every time I try to install it, I get:

E:failed to verify whole-file signature
E:signature verfication failed
installation aborted

My phone is not rooted or messed with in any way. (I'm seriously tempted to root or sell though). I tried renaming it to update.zip but it gives me an error then too. Any ideas as to what this update is and how do I install it?

I searched for update related threads but, I'm only finding a different update.

Thanks!

Tyseyh · March 16th, 2012, 08:18 AM

Bad download?

blackandroidph · March 23rd, 2012, 12:27 AM

Nope. Just tried it again. Got the same thing.

SUroot · March 23rd, 2012, 01:10 AM

Delete it and it should get resent to you

blackandroidph · April 9th, 2012, 12:48 AM

Yeah, I know. I've tried that, it just doesn't work. Gives me the same error...

casarosa · April 9th, 2012, 02:52 PM

Just checked my software update and it reads 2.29.405.14 have had this for ages with no further updates available

SUroot · April 10th, 2012, 01:30 AM

.405 is unbranded direct from HTC. .110 is branded from t-mobile

blackandroidph · April 29th, 2012, 09:34 AM

Ah...thanks. I suppose I'm stuck like this? :P

Hadron · April 29th, 2012, 11:02 AM

If you have an unbranded phone, why are you receiving a T-Mobile update in the first place?

But I'd not worry - recent updates have had very little of note in them.

blackandroidph · April 29th, 2012, 06:14 PM

I don't know. If its unbranded it shouldn't get the update. If its branded, the signature verification should work. Maybe I didn't mess with it, but its possible it was messed with before being repackaged and delivered. It doesn't work, even if I disable that. I suppose I should let it go

But I heard they fixed the issue where the messages went to the wrong person >.>

SUroot · April 30th, 2012, 12:59 AM

What is your current software version?

Thought that bug was addressed ages ago.

blackandroidph · April 30th, 2012, 07:34 AM

2.1.2.110.4 I still have it, though infrequently. If i got my hands on the unbranded one, would that work? Worth a shot...or bad idea?

Hadron · April 30th, 2012, 10:40 AM

OK, so you are branded, so it makes sense that you are receiving this notification. It was casarosa posting their software version that had confused me. Well at least that clears that one up

I'd not worry, or maybe search the web to see if you can find out what was in this update. These days they are very minor.

Tyseyh · May 2nd, 2012, 02:41 AM

Quote:

Originally Posted by Hadron

OK, so you are branded, so it makes sense that you are receiving this notification. It was casarosa posting their software version that had confused me. Well at least that clears that one up

I'd not worry, or maybe search the web to see if you can find out what was in this update. These days they are very minor.

Exactly this. Usually something not even noticeable.
Maybe you're like me in the sense that you know there is an update so you want it?

SUroot · May 2nd, 2012, 11:52 AM

I see no reason to not be on the 2.3 to be honest