Database Info

[Q] HTC Desire Bricked?

I recently tried (foolishly) to do an OTA update from Eclair to Froyo on my rooted Desire and suddenly my device is stuck in a reboot cycle. I do have access to the stock recovery mode and fastboot seems to be working properly. I rooted using unrevoked3 and I don't know if it give me access to any custom recovery tools. I also do not have a goldcard, and as I understand it, I can't make one since I can't get adb up and running.
I have tried pretty much everything I can find that applies to my device, which isn't much since I seem to have some odd bootloader/radio specs which make all the ROMs and RUUs I can find not work. When I boot into fastboot or hboot, my device lists these specs:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-WYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
I can get to the recovery tool and try running update.zip, but I have only found one which gets past signature verification and then errors with a Status 2. I have also tried running the WWE RUUs from: http://forum.xda-developers.com/showthread.php?t=695667 which will run once I give the device the "fastboot oem rebootRUU" command, but they all fail with a code 130 which means the device doesn't match. Also, the RUUs are all for a 1.1x or 1.2x revision and the loader says I have the 2.25.661.2 when it goes though the "are you sure" messages.
Is there anything else I can do to get this back up and running?
edit: An additional note, I have the SLCD screen which I know causes a bunch of issues since it uses a different driver than the AMOLED one and many of the ROMS, RUUs, etc. don't support it.

Hi tahosa,
I am suffering from the same issue but wondring if the Volume -/+ is working in your case or not, another observation that on the "SHIP S-ON" is this mean anything in locking or security issue?
my device gives :
BRAVO PVT3 S-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.00.08
Jan 10 2010, 12:12:05
thanks, and I am also doing some research till find solution.... :s

Volume +/-
My volume buttons are working fine. I can navigate through all of the HBOOT and fastboot menus and get to the stock recovery menus. Any information you have would be awesome. I have been bashing my head against this problem for a couple weeks now and gotten nowhere.

Please try to check this link :
http://forum.xda-developers.com/showthread.php?p=7618995
In my case the volume is not worked :s

No change
Nope, the only image I could find linked from there fails with the same error as the RUU. I think it is mainly to do with the fact that my HBOOT version is higher than what everyone else seems to have.
When the image gets loaded during the HBOOT, it verifies just fine, but when it tries to run the device check, it errors with "Model ID incorrect!"

Fixed: Process
EDIT: I don't know how I overlooked this for so long, but since I did my root using unrevok3d I got clockworkmod recovery and a backup of my old image, which is probably why this method worked for me. These instructions may still hold if you are stock, but no guarantees.
I was able to fix my Desire using the following method:
You first need to identify which version of the software you device has using the HTC reflash tools. To do this, boot your device into FASTBOOT and connect it to USB. Start the fastboot tool and reboot it into the OEM RUU mode using "./fastboot oem rebootRUU". This brings you to the OEM reflash mode and you can run any of the available RUU tools from this page: http://forum.xda-developers.com/showthread.php?t=695667. When you run them, they give you the version of the software on the device as well as what they are trying to overwrite with. Write down your software version if the first two groups don't match since you will most likely need a different version. From here, you can try running the update but it may fail. If it doesn't you should be all set.
If you can, find another one of the RUUs on the xda-developer page which matches your software version. Most of those link back to the shipped-roms page, but if you don't see yours on that list, look at http://www.shipped-roms.com/shipped/Bravo/ for the full list of Desire ROMs and RUUs. Mine happened to be the TELUS_WWE_2.25.661, which is a zip file. If the matching file is an exe, you have the HTC install tool, and can use the instructions above to flash it. If not, rename the .zip to update.zip and put it on your SD card and boot into HBOOT.
From HBOOT, choose recovery, and when you get to the black screen with the red error message press VOL-UP and POWER to get to the options and choose "Apply update.zip from SD Card." If everything matches, it will apply the update, and you should be able to boot up into a stock (or somewhat stock, mine was rooted) ROM for the Desire.
Let me know if this is confusing and I will rewrite it to be easier to follow.

[Q] [HTC LEGEND] (bootloader) [ERR] Command error !!!

Hello,
I try to unlock my bootloader with htcdev but i get this error :
C:\Users\Administrator>cd C:\Android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
How to fix this ? :$

I'm looking too, but for the [Doubleshot].
Trying the same thing myself on the HTC Doubleshot (MyTouch 4G Slide) and no joy, same exact error.
ericosman, did you by chance follow all the advice on HTC's site -- including specifically installing HTC Sync? I didn't install Sync because it looks like stuff I won't use and don't need, except that Sync has some dependencies (like a USB BMP Driver, whatever that is) that might make the difference. I haven't tried yet but I plan to.
I've tried two different versions of Fastboot, one I downloaded from masterjason.com and another I downloaded from Google's Android SDK manager. Both behave identically, despite one being nearly a megabyte where the other was 70 kilobytes.
I've tried reinstalling USB drivers, no joy.
I can get fastboot devices to work, as well as adb anything when the phone is booted, so I don't think drivers are really the issue.
I think it's HTC making a blanket promise that all the phones in that list can do this and indeed not all can.
[EDIT 2012-01-07: Add more info I found]
Gotta love it. Edited the post, and when saving, was told to refresh and log in. Then I wasn't given a chance to copy-paste what I typed. Annoying.
Anyway, see if I can remember what all I typed...
uhm...
I found through Google, and directed to Yet Another Android Forum somewhere on the 'net, that fastboot oem h will provide you a list of commands that are supported, and get_identifier_token was not among them. I suspect it's the phone's bootloader which contains supported commands, not Fastboot executable itself, so it may require downgrading/upgrading to a different HBOOT that has the necessary command support.
I did find readsecureflag which returns the integer "3" on my S-ON device. I assume then that the command I found called writesecureflag similarly takes an integer value, but what value to feed it, I don't know, and I don't want to risk my phone. Seems benign enough, but I know from computer programming that anything looking benign is not always.
Anyway, if you run fastboot oem h and get_identifier_token isn't there, I'd recommend giving up on this particular method of rooting.
Hope this helps.
[Edit 2012-04-15: Strikeout above no longer applicable info]
Turns out, see Aisho's post below, which sums up what eventually worked for me.
I actually had to wait for an OTA to be available long enough for a dev to package it up to a bootloader-flashable package, which included the get_identifier_token. Once I had that version on my phone, I was able to get the token to HTCDEV and get my bootloader unlocked. Not full access, but not bad: The only downside is if I need to flash a kernel I have to do it separately from the ROM through fastboot, and I don't think I can update my radio (not that I should need to). But hey, I can flash a custom ROM and get rid of this nasty crap T-Mobile thinks everyone should have (I will never play bejeweled, so I don't even want that adware/nagware on my phone).
[/edit]

I actually had this same problem with my HTC Wildfire S, and found this thread in searching for answers -- since I figured it out, I figured I'd put the solution out there.
My HBOOT was precisely the version HTC was advertising on their site as necessary for the unlock, which made it all the more perplexing when I repeatedly got this error. But then it occurred to me that while my version might be the same, HTC had stuck a neat little asterisk* next to the Wildfire S initially, saying that it required a new HBOOT anyway. I'd thought I was smarter than they were, but really what's different in the new download is the incorporation of just the command you're missing here. Since the ability to unlock is fairly new (through HTC officially, I mean) they're providing new HBOOTs with that command line included. I flashed the new HBOOT (even though it was exactly the same version) and lo and behold when I tried it again, it accepted the fastboot oem get_indentifier_token command.
I'd check to make sure that the HTC Legend doesn't have an asterisk as well, and maybe redownload the HBOOT anyway just in case. It can't hurt.

Aisho said:
I flashed the new HBOOT (even though it was exactly the same version)
Click to expand...
Click to collapse
I'm having the same problem on htc salsa, I have the version it says i should have, but have no get_indentifier_token, how is HBOOT updated?
My phone is S-ON and Hboot is 1.07.0000

HBOOT is updated via bootloader mode (on my phone, assumably the same for most HTC phones). You will need the correct HBOOT for your phone, and it will probably have to be contained within a full update package (for my phone, it's PG59IMG.ZIP, for the Dream it was DREAIMG.ZIP, your phone model will have its own filename). That file goes on the SD card, you boot into bootloader (usually, remove battery to ensure phone is full off, replace battery, and power up while holding the "VOLUME DOWN" button in). It then checks the file and asks you if you want to update.
However, if your phone is the same or newer version as the file you are trying to use, there's a good chance it will not work (the phone will not downgrade (usually (I think (I could be wrong) ) ) ).
You might also be amongst the lucky few who have a phone with what's called an RUU available. That's an .EXE file you run in Windows, connect your phone, and it writes what's in the file directly to the phone regardless of version.
HIH.

I have the upgraded HBOOT version as Im following a thread for how to do it, which incidentally isnt working, when I go to the bootloader menu it finds the file but does not up date it. It has been updated to the current version stated on htcdev with a FOTA update which may be why the HBOOT upgrade doesnt work.
I have the HTC salsa and it does reference RUU a few times. I dont use windows but HTC sync doesnt seem to find the phone, I have tried many things to get it working
Am I meant to run the EXE provided by htcdev and dont run HTC SYNC? Should I be in the bootloader menu/recovery first before running it?

@ericosman
did you follow every single steps ?
I just did it on my Legend (24 hours ago), in the end I followed the post of BlaY0 (http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62) and it worked great.
And yes, the RUU file is the one of a few MiB that you find at the very beginning at HTCdev.
The only trick is that I had to restore my data backup but also my boot backup, otherwise I was stuck in the hboot.
I did it by flashing the recovery image, as I deleted my old update.zip of ClockWorkMod, following the steps of http://forum.xda-developers.com/showthread.php?t=1290841 (see the end of the post: 'New recovery'). Then I went to 'Advanced restore' and restored both my boot image and my data back.
Always backup your system before playing around !

i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below

chris... said:
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
Click to expand...
Click to collapse
Alright, let's try again.
Before the step 1 of HTCdev, it asks you to upgrade your phone to the latest RUU. You don't have to. (see BlaY0's post [1])
Just download the RUU file, thus you will be able to retrieve the very hboot's zip (just run the EXE, don't go through the installer but instead locate its temporary extraction folder with the task manager and get that rom.zip).
They only want you to install HTC Sync so that your phone is recognized by Windows and the RUU can located it.
[1] BlaY0 explains that you don't have to upgrade to the latest HTC ROM or even RUU.

got it, and dump that zip file with the correct file name onto the root of the sdcard and start the bootloader
YAY it works, time to proceed to unlock
The version I got from a different post must not have been the correct one

im sure im bumping an old thread, but im trying to unlock an old espresso, but its having the same issue as the OP, i cant find the RUU with the new hboot, it currently has the 1.02 hboot, any clues?

Have you tried following the steps I referred to ?
Look at my two posts.
In fastboot, What is displayed besides the hboot version ? Something like "unlocked" ?
If note you have to re-flash your hboot with HTC dev method, once again read the post I linked to.
Sent from my Legend using XDA

just to add that on my MyTouch 4G slide I had hboot-1.44.0007 and gave me the same error as the first post when trying to unlock through htcdev.com. I did an OTA update to HBOOT-1.45.0013 (Software version 1.63.531.2 710RD) then went back to htcdev.com and it worked without problems

Getting this while trying to re-unlock evo 3d ics. hboot 1.58.

It's an old thread but maybe it's helping someone...
If you receive the error described in the topic title/first post you need to simply register to htcdev dot com and follow each step(including the 1st step because that's actually what you need to do )

i got same problem w my Z3 plus hbot will work on my z3 plus????????

[Q] I regularly loose 2G reception.

I regularly loose 2G reception on my HTC Desire S while still having Wifi access. I can fix this by rebooting the phone but after a while the 2G connection is. I did not have the same problem with the SIM-card in other mobiles at the same location so I reckon that it must be a HTC Desire S specific problem.
What can I do to fix that problem (except of restarting my phone a couple of times per day)?

it might help to know details about your phone. Is it S-OFF'd or unlocked through htc-dev? Is it running a custom ROM? Have you changed the radio?

It is S-OFF'd and rooted. I am running the HTC ROM. I have not triggered with the radio. I am not sure whether it is unlocked.
It currently picked up signal again without rebooting. Signal strength is -107dBm 3 asu.
Is there anything else that you need to know?

zurpher said:
It is S-OFF'd and rooted. I am running the HTC ROM. I have not triggered with the radio. I am not sure whether it is unlocked.
It currently picked up signal again without rebooting. Signal strength is -107dBm 3 asu.
Is there anything else that you need to know?
Click to expand...
Click to collapse
so you're on stock rom. Have you seen if any other ROMs give you this problem?

No and I would prefer other options before I start switching between ROMs as I am quite happy with the stock option.
Recently, I couldn't run the HTC System Upgrade. I guess it is because the phone is S-OFF'd etc. I thought originally that the modifications would just be overwritten during an upgrade process so that I would have to S-OFF and root again.

Well then it's quite a tricky situation here. If you don't want to change ROMs i presume you don't want to change the radio because the risks involved are much higher. Don't forget you can always make a backup so that if the custom ROM isn't helping you can return your phone to how it was.
However, I believe these problems are usually associated with the radio, rather than the ROM so changing it may solve your problem. But as i said before, the risks involved are higher.
If you want to change the radio:
http://forum.xda-developers.com/showthread.php?t=1178001 <-- here is a list of radios
To flash it just place the file in the root of your sd card and rename it to PG88IMG.zip
Then boot into the bootloader (pressing volume down + power) and it will automatically search for the file.
Then it will ask for confirmation. Select Yes
It will flash the radio and then reboot your device.
Be sure to delete the file after and also be sure to check the md5sum!!!!
I will warn you though, last (and only) time i flashed the radio the phone was stuck on the HTC screen. I panicked for a little while but then clearing the cache in recovery fixed it. This usually doesn't happen and a radio flash should be fine as long as you check the md5sum.

I have downloaded radio 20.4801.30.0822U_3822.10.08.04 and followed the instructions by gu1dry (see below).
As a response to
Code:
adb shell md5sum /sdcard/PG88IMG.zip
I get md5sum: permission denied. What is going wrong?
I deactivated fastboot on my device. Does that have any implications for flashing a new radio?
gu1dry said:
Code:
adb shell md5sum /sdcard/PG88IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
[*]The HTC Desire S will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
[*]The bootloader will scan for the radio update. Once it finds the update, select Yes.
[*]Allow the bootloader to finish flashing the updated radio, and reboot the HTC Desire S normally.
[/list]
Downloads:
From Gingerbread-based RUUs:
From the 2.10.401.5 RUU:
20.4801.30.0822U_3822.10.08.04
md5: 2fddef29eb1f8001d9cad14f48061f54
Click to expand...
Click to collapse

Help needed please.... got into a dead end with my One X

Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster

sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout

jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good:

[Q] How to i change my CID and allow OTA updates

Hi,
i recently got an HTC One S phone (used, no warranty). The phone seems to have been "played with" as it had Super User installed. However it was acting wierd so i did a factory recovery using the boot menu. This meant Super User was gone.
I am totally new to the updating an HTC phone, i found doing firmware changes to Sony and Samsung phones to be pretty much more easier!
My needs are pretty basic ! which is i want to achieve the following
I want to change my phone to have a normal CID without depending on carrier delays for updates (my CID is ORANG1)
I do not want to install a custom ROM, i want OTA updates to happen
I want to have my phone get the OTA update for Jelly Bean
When i boot into the phone (volume - + restart), i see the following,
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.3150S.19_2
OpenDSP-v21.1.0.32.0314
eMMC-boot
Mar 15 2012, 23:37:23
Other facts
My CID - ORANG1 (using CID getter app)
Phone model - S4 Z520e
I hear the Jelly Bean update sorts the helicopter issue with the HOME button, though i am not sure if the restart issue when browsing with the stock browser has been resolved. The helicopter HOME issue is driving me nuts.
Appreciate if someone can provide me the steps about how i can go about getting my phone CID changed and the OTA udpates working for the new CID, as searching the forums have not really helped me nail the way i can go about doing this.

Before we get started I'd like to know your home country (sorry I don't know your flag) and whether you're on stock or custom recovery.
As I'm on this device from the very beginning and know almost any corner in this forum I'll point you out where to find the things and information you'll need and some advantages as well as some disadvantages of what you want. Also I'll point out an alternative.

rootrider said:
Before we get started I'd like to know your home country (sorry I don't know your flag) and whether you're on stock or custom recovery.
As I'm on this device from the very beginning and know almost any corner in this forum I'll point you out where to find the things and information you'll need and some advantages as well as some disadvantages of what you want. Also I'll point out an alternative.
Click to expand...
Click to collapse
Wonderful to hear a quick response.
I live in Sri Lanka (small Island nation located at the bottom part of India, last colonized by the British!). The situation is that i think i am in stock, as i got this phone used and though everything is functional the helicopter home button issue, phone freezing when i use the stock browser for over a few minutes, connection looses (all reported errors with 4.0.3 and even 0.4) means i need to get this to Jelly Bean to make the phone more usable as i love the size and speed of the phone.
To start of is there any way i can see if my phone is in stock or custom recovery? I just searched and found http://forum.xda-developers.com/showthread.php?t=2124349, does the instructions "Fastboot getvar version-main" work?
Another twist is that i have the much loved Windows 8 running on my PC, i am not sure if that will have any effect on any command executions.

Wait you got 1.06 Hboot I would not flash RUU or OTA if you got that because you can update what is needed or if needed for roms plus you don't have to piss about when flashing roms so if I was you don't do it.

Thank you and welcome to this forum!
Your bootloader is still at version 1.06. Which is very good, as yours and version 1.09 allow you to flash nearly everything (kernels, radios, etc.) from within your device. Bootloader versions higher than 1.09 don't allow this anymore. For flashing kernels and radios you then will need to get into the phones fastboot mode and use the Android SDK on your pc, typing things like 'fastboot flash boot boot.img'.
Let's get started with recovery. To root your phone you usually need to flash a custom recovery. TWRP is the only one working bugfree atm. You can download it here.
To flash it and doing other usefull things try to get comfortable with the HTC One S All-in-one-toolkit.
So why do I mention this, also you wrote that the only thing you want to do is udating straightly to JB?
After the OTA update you'll be on bootloader version 2.15. It's just one more thing from htc to lock their devices even more, as at this time they don't behave very friendly to the dev community. Downgrading the bootloader is kind of pain and not easy so, unless you're familiar with linux (I did it succesfully several times).
Also stock JB from htc has one more surprise: Your system folder will be kind of write protected, which means, also you seem to have full root, after a reboot your formerly deleted (you thought so) files wil be back. Also added files in that folder won't be present any more. That crap is hardcoded into htc's JB kernel and sources are not available atm. But this problem was solved by flar2, who wrote a kernel module to bypass this.
So your hardware issues are left. As I'm not concerned by this I can only summarize what I read about these in the forum. They are obviously hardware related and therefore independant from software. Somebody wrote, a new radio had helped, others write different. In summary you'll have to check this out for your device.
Let's resume at this point:
Your device is unlocked and at 1.06. It needs to be relocked for the JB update and it will have a less comfortable bootloader version afterwards and it will be hard to get rid of the crapware in your system folder, as you'll have to unlock and root again for doing so. And it's questionable the JB OTA update will fix your hardware issues.
So I'd recommend the following procedure (you could still do the OTA update at any time, I'll help you then):
- use the all-in-one-toolkit, flash latest TWRP
- Flash latest EU radio 1.11 from here with twrp
- restore JB from my nandroid backup (download 3.16)
- if you experience troubles with your wifi connection, flash these wifi partitions
- check if your hardware troubles have been resolved
- to get root use all-in-one-toolkit again and flash elemental kernel (by flar2)
It seems a lot of work, but it's worth it. PM me, if you need additional help or decide to do the OTA update.

wow, thanks so much for all the info. I will give this a try tonight as i have the phone @ home, using my One X as the regular phone until i get the One S sorted. Then i will hope push out the One X and keep the One S as my regular phone. I prefer the One S size which is more ideal for one handed operation, shame that HTC opted for a pentile display that took out the sharpness.
Also based on your suggestions would it be better for me to opt for a custom ROM than HTC standard to resolve my issues?