Database Info

HTC Desire S, Restoring, Flashing, Hboot

Hi everyone! I'm new here so apologies for any mistakes, wrongs etc.
I needed some help with my HTC desire S, I'm new to all this rooting, flashing stuff, but i'm not too thick so understand some things. So heres the story/problem.
About a month ago I S-OFF my phone to try out some awesome custom ROMS, Granted i had some fun with them, I installed an unofficial 2.3.5 gingerbread with sense 3.0, just to see what the new sense was like, As I didn't receive the OTA update on my phone. But now i'd like to restore my phone back to the original ROM that came on the phone. I'm not to fused weather its S-OFF, all I really wanted was my original ROM as Sense 3.0 is running so slow on my phone, and its made a big difference in performance. I'm one of these guys who says please search the forum and google for help. And I did just this and found some great information yet of which i have had no luck with.
I've tried running an RUU whilst my phone is switch on and connected via HTC Sync, No luck. Model ID error 130....Please use the correct ROM (or something along those lines) So i found that u could flash the RUU after extracting the rom.zip and renaming it to PG88IMG.zip. So i did just this, still no luck, Updating was being processed and at the end of the update I got the message Wrong model ID and again Please use correct ROM (something like that anyway!)
Now your probably laughing at me by now thinking rialcniS you thick so and so, your using the wrong RUU. Which to anyone else sounds correct. But surely if i'm trying to convert back to the original stock ROM then 2.3.3 Gingerbread is the one to go for? as this was what my phone was running from the box!
So I did a little bit more research and found out that maybe its to do with my Hboot version. Below are my phones detail.
SAGA PVT ENG S-OFF
HBOOT-6.98.2000 (PG8810000)
RADIO-3822.09.08.20_M
eMMC-BOOT
FEB 24 2011,21:19:05
Software Information:
Android version - 2.3.5
HTC Sense Version - 3.0
Software Number - Desire S 2.10.401.4 [PROXUSER]
Kernel version - 2.6.35.10-g9ac6c7a
Baseband version - 20.48.30.0922U_3822.09.08.20_M
Build Number 2.10.401.4 CL156318 release-keys
Browser version - WebKit/533.1
From my research I found (or at least this is how it translates in my brain) is that I cant install an original stock ROM on Hboot 6.98.2000. Is this correct?
Anyway, for some more information to you guys when I load my phone up in fastboot, it starts searching for the PG88IMG.zip and also something along the lines of PG88DIAG, yet all it says underneath is Wrong or no image?
Am I being a complete idiot, or does this seem strange to some of you more advanced android rooters
If anyone can point me in the right direction to where i might be going wrong, id much appreciate it!
Thanks in advanced
Rialcnis!

rialcnis said:
Hi everyone! I'm new here so apologies for any mistakes, wrongs etc.
I needed some help with my HTC desire S, I'm new to all this rooting, flashing stuff, but i'm not too thick so understand some things. So heres the story/problem.
About a month ago I S-OFF my phone to try out some awesome custom ROMS, Granted i had some fun with them, I installed an unofficial 2.3.5 gingerbread with sense 3.0, just to see what the new sense was like, As I didn't receive the OTA update on my phone. But now i'd like to restore my phone back to the original ROM that came on the phone. I'm not to fused weather its S-OFF, all I really wanted was my original ROM as Sense 3.0 is running so slow on my phone, and its made a big difference in performance. I'm one of these guys who says please search the forum and google for help. And I did just this and found some great information yet of which i have had no luck with.
I've tried running an RUU whilst my phone is switch on and connected via HTC Sync, No luck. Model ID error 130....Please use the correct ROM (or something along those lines) So i found that u could flash the RUU after extracting the rom.zip and renaming it to PG88IMG.zip. So i did just this, still no luck, Updating was being processed and at the end of the update I got the message Wrong model ID and again Please use correct ROM (something like that anyway!)
Now your probably laughing at me by now thinking rialcniS you thick so and so, your using the wrong RUU. Which to anyone else sounds correct. But surely if i'm trying to convert back to the original stock ROM then 2.3.3 Gingerbread is the one to go for? as this was what my phone was running from the box!
So I did a little bit more research and found out that maybe its to do with my Hboot version. Below are my phones detail.
SAGA PVT ENG S-OFF
HBOOT-6.98.2000 (PG8810000)
RADIO-3822.09.08.20_M
eMMC-BOOT
FEB 24 2011,21:19:05
Software Information:
Android version - 2.3.5
HTC Sense Version - 3.0
Software Number - Desire S 2.10.401.4 [PROXUSER]
Kernel version - 2.6.35.10-g9ac6c7a
Baseband version - 20.48.30.0922U_3822.09.08.20_M
Build Number 2.10.401.4 CL156318 release-keys
Browser version - WebKit/533.1
From my research I found (or at least this is how it translates in my brain) is that I cant install an original stock ROM on Hboot 6.98.2000. Is this correct?
Anyway, for some more information to you guys when I load my phone up in fastboot, it starts searching for the PG88IMG.zip and also something along the lines of PG88DIAG, yet all it says underneath is Wrong or no image?
Am I being a complete idiot, or does this seem strange to some of you more advanced android rooters
If anyone can point me in the right direction to where i might be going wrong, id much appreciate it!
Thanks in advanced
Rialcnis!
Click to expand...
Click to collapse
Can't say much but I will point you to see this guide if it helps .
www.freeyourandroid.com/guide/flashing-ruu-htc
Sent from a darkly dreaming freak named Ray with a hTC Desire S in his hand which's rom is changed by the owner more than his clothes !

More useful info will be not the current state of your device, but what it was before the S-Off and customizing.
Setup the adb and fastboot commands on your PC /there is guide in my signature.
Then connect the device and type the following commands:
Code:
adb devices ([I]your device serial number should be displayed[/I])
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes[/I])
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img ([I]this will create a misc.img file on your SDcard[/I])
Then copy the misc.img to your PC and open it with HEX editor (XVI32 is free, you can google it)
Open the misc.img with HEX Editor. There will be a number like 1.28.401.1 on line 6. This is the number of your original software.
Search in this thread for the proper RUU and install it.
Important! Before flashing the RUU change your hboot with this one
Maybe sounds complicated but nothing scary about it, just follow the steps carefully.
Good luck

use search there is a whole thread about downgrading the hboot ON THE FIRST PAGE.

Sorry, I had searched and searched everywhere for about 3 hours straight, and every time I found something that seemed promising i would get errors and have no luck.
@amidabuddha, Thankyou so much, this seems very promising. I'll give it ago tonight and keep you posted on the progress!
Thanks again!!

look for a thread called downgrading the new hboot.theres a guide ,it works fine as i have used it myself.

djisgod said:
use search there is a whole thread about downgrading the hboot ON THE FIRST PAGE.
Click to expand...
Click to collapse
djisgod said:
look for a thread called downgrading the new hboot.theres a guide ,it works fine as i have used it myself.
Click to expand...
Click to collapse
Hey, his problem is not the hboot, he needs his Stock configuration for his region (which is wise in order to keep the warranty). The only thing he needs for this is the proper RUU and overwrittable hboot, no downgrades, no other stuff

amidabuddha said:
Hey, his problem is not the hboot, he needs his Stock configuration for his region (which is wise in order to keep the warranty). The only thing he needs for this is the proper RUU and overwrittable hboot, no downgrades, no other stuff
Click to expand...
Click to collapse
So, thanks to you mate i've got it all back to stock! Fantastic! Thankyou very much for your help and keep up the good work!

rialcnis said:
So, thanks to you mate i've got it all back to stock! Fantastic! Thankyou very much for your help and keep up the good work!
Click to expand...
Click to collapse
Glad that you solved your issue.
Just out of curiosity - which one was your RUU?
And for your information (there was a complain in your first post about sense 3 performance) - if you receive the 2.10.x.x OTA update notification, the stock sense 3 runs pretty good on my device, no lagging, no bugs so far. So maybe you can give it a try when the time comes.
Enjoy your "new" phone

amidabuddha said:
Glad that you solved your issue.
Just out of curiosity - which one was your RUU?
And for your information (there was a complain in your first post about sense 3 performance) - if you receive the 2.10.x.x OTA update notification, the stock sense 3 runs pretty good on my device, no lagging, no bugs so far. So maybe you can give it a try when the time comes.
Enjoy your "new" phone
Click to expand...
Click to collapse
Yeah I'm not to sure, it was running slow and not nice and fresh like it is now! but i reckon now i know how to solve the problem if it occurs again i might give it a try my original RUU was the one u listed in your post 1.28.401.1. Nice and simple instructions you gave, so thanks very much again!!

[Q] HTC One S S3 CID and others

Hello all,
This is the first time I write on the forum and I'm another frustrated HTC One S (S3) user.
My phone is the Indian version (CID: HTC__038). It's still on the 4.0.3 version (it hasn't got the OTA update yet) and I cannot find any information related to when the 4.0.4 will be released in this region.
So, if I want to get the 4.0.4 I basically have two options:
- Install a custom ROM
- Install a RUU for other country
For the first point, I looked at the TrickDroid 4.0 but I found another thread (http://forum.xda-developers.com/showpost.php?p=33374826&postcount=424) where someone says that you only can install this ROM if you phone has the 4.0.4 version as base. Can anyone confirm this?
As for the second point, I found the problem that it's impossible (so far) to change the CID on the S3 model. So, there is no way to install a RUU from another country. Is this right?
Please, I would appreciate if you can help me on this or tell me a different way to upgrade to 4.0.4.
Thanks!

I know i won't be of any help to you, but i'm in the very same situation
My CID is HTC__662 (Hong Kong), and also for this: no RUU, no OTA, no Custom Rom 4.0.4 based...
And DO NOT try to flash TD v4!! U'll get only into bootloop; i think it's a matter of hboot that's different from 4.0.4 and 4.0.3 (for example, if u take a look at mcOneS3 rom u'll see it's a prerequisite).
I've spent more or less 2 days flashing, rebooting, soft-bricking, crying, recovering, crying again...at the end (after a brief test of TrickDroid 3.0.0, the only Rom i got to work but that did not match my needs) i've been happy to succeed in restoring old stock 4.0.3...
As far as i've understood: as long as we have no OTA/RUU, we are screwed.

I was told that it was only made for the T-Mobile version, but I'm pretty sure that's not right.

Same here, my CID is BSTAR301, still running the stock 4.0.3 and havent even found the RUU for that CID.. I don't really want root or flash any rom yet for warranty purposes (and because I'm satisfied by the way it is, so no need to get my hands dirty on it!) thus I'm relying on official updates, but considering the updates are region/CID/carrier dependant it's highly unlikely that I'll get 4.0.4 let alone Jelly Bean/sense 4+ by the end of the year... what a fricking joke!
Sent from my HTC One S using xda app-developers app

please my htc one s is bricked because i mistakely cleared storage in bootloader with cmw installed now im stock on loop and i cant flash through recovery cos i cant mount .
please can anyone help me with 3uk htc one s ruu h3g__001 pleasse

[Q] hboot 2.14.0000

So I updated my rogers HTC One X with the OTA jellybean update. Then I decided I wanted to root. I did, TWRP (the older revision than the current one) didn't work because the touchscreen wouldn't work. Updated TWRP to the highest version (the one with the on screen keyboard?) and it worked. Flashed Jellybam, stuck on boot screen, flashing white and animation. Then I flashed the boot.img with adb, then flashed jellybam again. Worked, but no touch screen.
Is my solution just to wait for roms that support new hboot?

So what was the benefit to doing the ota again? You seem like you knew the risks I'm just wondering what the reward was?
Sent from my HTC One XL

Are you sure you are on the latest version (2.3.3.1)? Its supposed to fix the the touch screen issue.
http://forum.xda-developers.com/showthread.php?t=1677447

My reward was the chance to have a digital interaction with someone who offers no answer to a simple question, and instead thinks snark is worth their posting time. Obviously.

Twrp works fine as I said. It's the roms, once flashed, that don't respond to touchscreen swipes.

veemodz823 said:
Twrp works fine as I said. It's the roms, once flashed, that don't respond to touchscreen swipes.
Click to expand...
Click to collapse
The hboot screwed up both touchscreen response within TWRP and within the OS. I would have assumed that the new version of TWRP fixed both. I'm not personally on hboot 2.14, so hopefully some folks that are can chime in with some insight.

redpoint73 said:
The hboot screwed up both touchscreen response within TWRP and within the OS. I would have assumed that the new version of TWRP fixed both. I'm not personally on hboot 2.14, so hopefully some folks that are can chime in with some insight.
Click to expand...
Click to collapse
I didn't think that a recovery would actually fix something within an os when the two are two completely different things in my mind. I think that TWRP working on 2.14 means that something in TWRP has been changed from previous versions to accomodate 2.14. I guess the same just has to be done for the roms, but that's just my uneducated guessing and logic.

I too am having the same issues. Installed 5 different rom's, all of them had no touch screen capabilities. Still working on it, if I come across anything I will let you know. Were you able to backup your old rom with TWRP? If you did I would love if you could send me your recovery file since CWM happened to delete mine. I have Rogers evita if that's the same as yours.

Hey, no I didn't back up.
did you try this rom?
http://forum.xda-developers.com/showthread.php?t=2076361

veemodz823 said:
I didn't think that a recovery would actually fix something within an os when the two are two completely different things in my mind.
Click to expand...
Click to collapse
Yes, they are separate. But it's recovery that is installing the OS. So it seems logical to me it can cause a problem with the OS.
Sent from my HTC One X using xda app-developers app

veemodz823 said:
My reward was the chance to have a digital interaction with someone who offers no answer to a simple question, and instead thinks snark is worth their posting time. Obviously.
Click to expand...
Click to collapse
Sorry I didn't know you didn't have a backup. Now I feel terrible for joking with you before.
Sent from my HTC One XL

veemodz823 said:
Hey, no I didn't back up.
did you try this rom?
http://forum.xda-developers.com/showthread.php?t=2076361
Click to expand...
Click to collapse
I haven't tried that rom, it's an Australia one....don't know if that would work for us rogers guys. Might perm brick it

http://forum.xda-developers.com/showthread.php?t=2083314
It seems to have worked for this dude and I *believe* the Telstra is the same phone as ours and not an international version. But make sure. I would've flashed it but I'm at my volunteer.

Telstra is the same phone as Rogers (dual core S4 version of the One X/XL).
If it works, you'll need to manually enter the Rogers APN.
Sent from my HTC_Flyer_P512_NA using xda app-developers app

Does anybody think its possible that the new OTA firmware (flashing the entire OTA and not just the ROM) has some sort of difference compared to older ones.. surely a broken touch screen after the OTA can't be a coincidence. 2nd case.
Or its possible that the ROMs/recovery aren't compatible with some sort of change in firmware.. I wonder..

absolutelygrim said:
Does anybody think its possible that the new OTA firmware (flashing the entire OTA and not just the ROM) has some sort of difference compared to older ones.. surely a broken touch screen after the OTA can't be a coincidence. 2nd case.
Or its possible that the ROMs/recovery aren't compatible with some sort of change in firmware.. I wonder..
Click to expand...
Click to collapse
The weird thing is this: with older TWRP you can't get the touch screen to respond, but with newer TWRP it will respond to touch.
In the thread I posted above someone says this:
"Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source."

veemodz823 said:
The weird thing is this: with older TWRP you can't get the touch screen to respond, but with newer TWRP it will respond to touch.
In the thread I posted above someone says this:
"Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source."
Click to expand...
Click to collapse
typical HTC.. If you are still having issues, I may be able to help you RUU downgrade

Some already quoted me but to be clear.
Htc ship firmware updates with their official updates that customs rarely ever ship. Firmware relating to the touchscreen were updated and kernel changes are required to use it.
Twrp uses official sense kernel so just updated to latest. All kernels based on the kernel that shipped with 3.17 willbe fine.
Eg custom 3.17 jb roms and kernels will be fine.
But all things not based on 3.17 do not have the required kernel updates for the touchscreen.
It is unknown what changed so likely this won't get resolved until Htc release source for 3.17 kernel.
Downgrading from 3.17 has been reported to perma brick phones. Do so at your own risk, you have been warned..
---------- Post added at 05:07 AM ---------- Previous post was at 04:27 AM ----------
Also twrp does not install os/roms. Roms install themself. Roms include an update binary that has all the file operation apps like del, copy, move, read operation etc. And they include an update script that makes use of all the apps it ships with.
Twrp is a skeleton, it just starts the Rom and lets the rom do its own thing.
Twrp does not alter how a Rom installs, eg it can neither break nor fix things like this touchscreen problem.

All right, so to he clear, its just a matter of waiting for 3.17 compatible roms. Would that be far off considering Twrp is already updated to support 3.17 kernal roms? Or does HTC need to release source for custom 3.17 roms to be made? And what about that Telstra Rom that was mentioned? Why would that work, how was that made?

Twrp 2.3.3.1 works because it uses Htc sense 3.17 kernel (based on linux kernel 3.4.10). Twrp does not "support 3.17 kernel roms", twrp does not care what kernel a Rom has. Twrp simply has updated so it can function. If a Rom can function or not has nothing to do with twrp.
Telstra 3.17 Rom works because it is based on 3.17 Telstra Rom and uses the 3.17 kernel.
There is several 3.17 based roms. Based on the singtel 3.17.707.1 and Telstra 3.17.841.1 and I'm sure now there is loads of evita regions with 3.17 available more variations will show up.
Cm is not a sense rom. Same goes for aokp and such. Anything in "original development" is not based on sense. All those can not use sense kernels as they would need to add all the extra Htc stuff for it to work and you just end up with sense and not cm etc.
I can say again; only roms that can use the 3.17 kernel work and basically that just means only sense 3.17 roms. Anything else will not work. That is unlikely to change until 3.17 kernel source is released. There is several 3.17 based roms.
Kernel source could take up to 3 months. It has been 1 already. So could be another 2 months before this can be fixed in non sense roms.

[Q]No Sevice after 2.15 hboot update, can't go back to stock

So I recently updated my hboot to 2.15 for the new 3.4 kernel. I have a Telus branded One S, so I used this firmware to update: http://www.androidfiles.org/ruu/getdownload.php?file=Ville/OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip
However, when I update to this hboot, I lose service. I will have it for a couple seconds or so, then I will lose it. This has happened on every ROM I have tried, including the new ones with 3.4 (CM, PAC, Carbon). I have tried going back and using the previous RUU's (I've tried this, and this) But those two aren't on the same hboot correct? Those two don't work, and I am unaware of any others as none are listed on that site.
So my problem is that I have no service, and I can't go back to previous hboots and I don't know why. Is it a problem with the new radio? If so I haven't found any great tutorials on where and how to get different radios.
If anyone could help me at all I would be so grateful if they could point me in the right direction. If someone helps me I could definitely make it worth their while over paypal
I can post screen shots or whatever if someone could tell me if they need any information in order to help.
Hboot-2.15.000
Radio-1.13.50...
Can't SuperCID as it's JB... CID is Telus_001 atm

Did you look at the s=off post?. Go to http://www.moonshine.io and see if your phone is on the list. I had OTA 2.15 and with moonshine script I got the s=off. With s=off you can go back to stock.

cuiltheory said:
Did you look at the s=off post?. Go to http://www.moonshine.io and see if your phone is on the list. I had OTA 2.15 and with moonshine script I got the s=off. With s=off you can go back to stock.
Click to expand...
Click to collapse
Doesn't work since I am on the TELUS WWE 3.16.6614, and that says it is only for 3.14

Ster76 said:
So I recently updated my hboot to 2.15 for the new 3.4 kernel. I have a Telus branded One S, so I used this firmware to update: http://www.androidfiles.org/ruu/getdownload.php?file=Ville/OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip
However, when I update to this hboot, I lose service. I will have it for a couple seconds or so, then I will lose it. This has happened on every ROM I have tried, including the new ones with 3.4 (CM, PAC, Carbon). I have tried going back and using the previous RUU's (I've tried this, and this) But those two aren't on the same hboot correct? Those two don't work, and I am unaware of any others as none are listed on that site.
So my problem is that I have no service, and I can't go back to previous hboots and I don't know why. Is it a problem with the new radio? If so I haven't found any great tutorials on where and how to get different radios.
If anyone could help me at all I would be so grateful if they could point me in the right direction. If someone helps me I could definitely make it worth their while over paypal
I can post screen shots or whatever if someone could tell me if they need any information in order to help.
Hboot-2.15.000
Radio-1.13.50...
Can't SuperCID as it's JB... CID is Telus_001 atm
Click to expand...
Click to collapse
I'm on the same boat with you. CID is Telus_001 too. If you find a way to solve the problem, please let me know, I'll do the same too. Thanks a lot.

Moonshine is updating the script, so check his web site from time to time.

the problem is not the new hboot. is new cm10.1 based roms. (NOW SEEMS FIXED)
it happened to me too. I did not update hboot and stayed with 1.14.0004 and flashed early versions of Carbon_HALO roms with 3.0.80 kernel by $droyd$ and lost signal until toggle airplane mode on-off.. then wiped and flashed carbon with 3.4 kernel.. same thing. data issue again. Then flashed carbon 6-21 build and data has worked well so far for 20+ hours.

[Q] Where to get firmware (not radio)?

Here is a thread with radio and firmware from the ICS RUU: [RADIO] [FIRMWARE] ICS firmware and radio from WWE RUU. Also there are a threads with radios here and there. But where can i get older firmwares than the one from ICS RUU thread?
Offtopic: I flashed this firmware with radio (because i wanted the newest, and i had the oldest after downgrading to get S-OFF... i expect i'll get some hatred from the forum for flashing radio without strong reason). It was said in thread that it contains touchscreen drivers. I also flashed cyanogen 10.1 rom. The thing is I feel scrolling and especialy it's "kinetics" are weird, compared to stock rom i had before (i have problems controlling scrolling speed, it's either too slow or too fast). Sadly, i can't remember had it changed after i flashed cyanogen or this new firmware, therefore can't tell the reason. I was wondering what if i had to downgrade firmware - i don't know where to get it. Or maybe i should start a thread about scrolling issue?

and i had the oldest after downgrading to get S-OFF
Click to expand...
Click to collapse
confused with that line.
what is your phone bootloader status right now? s-on s-off
idk if this one is older or, refer to juggies post here http://forum.xda-developers.com/showpost.php?p=43692733&postcount=1814

You can try extracting it from ruus, that's what someone did (from the Ics ruu) in that thread you got it from. But I doubt the extra firmware being upgraded is your problem anyway, haven't heard of anyone else with such issues.
CyanogenMod does feel different scrolling etc. than sense roms, maybe you just have to get used to it