• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help HTC Desire S OTA Update

K

kginglis

Lurker
I have a HTC Desire S (branded by Virgin Mobile) and I like to play with (break) the software so I can debrand and run custom ROM's. The only reason I do this is that I hate waiting on the mobile networks to test new builds with all their bloatware before rolling them out to us lowly customers. Next time I'm only buying an unbranded device!!!

I did this successfully with my old HTC Desire which my wife now uses. So bare with me and I'll give you the background to my HTC Desire S woes.

I used the Revolutionary hack to replace the HBOOT (6.98.1002) and make the phone S-OFF. I also replaced the recovery partition with Clockworkmod recovery. So all was good. However, I did this in 2 stages, I replaced the HBOOT a few months back and only got round to finishing by replacing the recovery partition this week.

My next step was to start thinking about flashing some ROM's. Okay so the very day (10 Jan 2012) I finally replaced the recovery partition with Clockworkmod I received an OTA Update. Brilliant I thought, that'll save me installing a custom ROM! So I tried to install the OTA Update, fail!

My first thought was, now that Virgin have released Android 2.3 and Sense 3.0 for the HTC Desire S. I'll just put my phone back to how it was and run the update. My contract is up soon and I'll be getting a new phone so I'll make this as standard as possible before handing it down to my wife.

Great, so I replaced the HBOOT back to a stock image (0.98.0000) and ran the RUU for the branded Virgin Mobile (RUU_Saga_Virgin_Mobile_1.31.351.1_Radio_20.28b.30.0805U_38.03.02.15_M_release_178933_signed.exe). That replaced the Clockworkmod recovery partition with the stock recovery and reset my phone back to how it was.

I now have my phone back to what it was when I bought it (roughly as I think it was 1.47 before I flashed the branded ROM again). The only problem now is that I am no longer being offered the OTA Update (I've tried Settings > About Phone > Software Updates > Check Now).

I did save the OTA update file (OTA_Saga_S_Virgin_Mobile_2.13.351.6-1.47.351.2_release_231143vunyigsoxclccanj.zip) before I wiped my phone again. Can I/Should I run it manually?

Is anyone else running build 1.31 on a HTC Desire S? If not what version are you running? I'm wondering if by flashing the 1.31 version (as it was the only one I could find) I'll no longer get the 2.13 OTA Update.

Android Version: 2.3.3
HTC Sense Version: 2.1
Baseband Version: 20.28b.30.0805U_38.03.02.15_M
Kernel Version: 2.6.35.10-g8ae2b2f htc-kernel@and18-2 #1 Thu Mar 17 20:59:21 CST 2011
Build Number: 1.31.351.1 CL27073 release-keys
Software Number: 1.31.351.1
Browser Version: WebKit/533.1
 
I'm don't think it will work. It looks like the clue you need is in the file name

OTA_Saga_S_Virgin_Mobile_2.13.351.6-1.47.351.2_release_231143vunyigsoxclccanj.zip

These updates are sequential, i.e. you need to install version 1.31* before 1.47*, and have version 1.47* before 2.*, etc. The file name suggests it's to update from 1.47.351.2 to 2.13.351.6, not from your current version.

In which case you need to install the 1.47.351.2 ROM (RUU) or wait to see if you receive the OTA update again.

You can see if you can jog the OTA to your phone with this method:

Dial *#*#2432546#*#* on the keypad. You should then get a notification message (although it may only refer to app updates). Then Menu > Settings > About phone > Software update > Check and see if anything happens!

If you tried the update zip, I think it would detect that you have the wrong update for your phone and wouldn't install. I'm also assuming you're back to S-OFF with an HBoot that's concomitant with your phone's current ROM, otherwise you'll brick your phone.
 
Doh, I should have noticed that version number in the filename! My wife always says I can't see what in front of my face ;)

I'd tried the *#*#2432546#*#* and checked in successfully but there's still no updates. I'm back to S-ON as intended when trying to get back to original settings (see below)

SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011,14:58:38

So how do I get hold of the 1.31 to 1.47 update? Any ideas? Can I RUU to a non-branded 1.47 ROM or will the fact that I'm S-ON and branded stop me from doing that?
 
kginglis said:
So how do I get hold of the 1.31 to 1.47 update? Any ideas? Can I RUU to a non-branded 1.47 ROM or will the fact that I'm S-ON and branded stop me from doing that?
Click to expand...

I've not seen a 1.47* RUU for Virgin. Google only throws up the 1.31 RUU you have.

You won't be able to flash a stock RUU to your phone unless you make a 'Gold card'. But remember you can't install a Virgin (branded) OTA update over a stock ROM. To get back to a Virgin ROM, you'd have to install a Virgin RUU on your phone.

As the Virgin 2.* OTA is fairly new, there might be a chance that a Virgin 2.* RUU will appear soon. If so, you'll be able to flash this straight over your current 1.31* Virgin ROM.
 
I finally went for the Gold Card option and installed:

RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe

I'm now running:


*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011,15:22:13

Android Version: 2.3.5
HTC Sense Version: 3.0
Software Number: 2.10.401.8
Kernel Version: 2.6.35.10-g9ac6c7a | htc-kernel@and18-2 #1 | Wed Sep 21 13:48:03 CST 2011
Baseband Version: 20.4801.30.0822U_3822.10.08.04_m
Build Number: 2.10.401.8 CL156318 release-keys
Browser Version: WebKit/533.1

Everything seems okay, thanks for all your help.
 
You must log in or register to reply here.
Back
Top Bottom