yashsingh1/xdaforums huggingface dataset:
[HTC One S] Sneakyghost:
Yeah it is kinda sad to see how things develop over at VF. If it hadn't been for your stubborn but calm insisting, they probably would've gotten away with it.

I was very impressed at first with their efforts and kind replies but after four month of always the same talk and no progress whatsoever i think they are actually not worth half the respect i had.

That said, we can now go on and discuss other matters as we now know we won't gain anything from VF.uk.

One other matter i began to discuss with a fellow XDA Member (Tecaro), whose phone has the same issue as ours. He is basically having some ideas. The first idea was to actually make the Issue reproducible. The first try worked right out of the box.

He suggested to insert a sheet of paper inbetween the SIM Cover (Top) and the 3 Antenna connectors there (BT, WiFi and GPS). His reasoning: if the theory of electronic flutter on the mainboard, stemming from the Radio, and interfering with the buttons is true, then cutting off the antenna of the top cover will make the phone increase output wattage on all modules (including GSM) and thus provoke the issue to come forward. The top cover can be taken off without damaging the phone. That's the reason for going this way.

I was not very much inclined to believe this would work, to be quite honest. But then it did. At first, nothing happened apart from Wifi having really bad signal and GPS not working at all. Didn't test BT.

But then i went downstairs and sat in my car, which is metal and a faraday-cage. Signal got worse and the Issue came up. As bad as on Base 1.78 but not as long and only once. So, to summarize: reducing Antenna-Capabilities and thus increasing output wattage will make the Issue come back even on Base 2.31 and Radio 1.06es. This despite the fact that the new RUU is said to include a fix for the issue.

I am now putting a lot of hope in Tecaro, as he said he works in the electronic engineering field. Maybe he has some decent ideas and maybe its only the drivers and maybe, if the kernel sources are available (they are) those drivers can be disassembled and tweaked by normal people.

Many maybes. I know. But a little hope at least.

maybe there are more engineering people out there with ideas. Maybe we can have our own fix after all.

[EDIT]

Someone also mentioned there was a fix for this on CM9. Still have to investigate this though. No idea where that came from and why we didn't hear about it here yet. Maybe the CM9 users here could research this. I am very limited with my time and would be grateful if anyone could shed some light on this rumored fix...
[HTC One S] ExDr:
If 2.21 resolves issue for your 1S, I do not think it will appear after upgrade to 2.31. At least for me it have not happend.

But radio 1.06s seemed to be slightly better than 1.06es now, so there is no sufficient reason to update in my opinion. If we had s-off I would return radio 1.06s
[HTC One S] Tecardo:
To the CM9 fix: CM9 fixed the touchscreen in one of their updates, after that updated i didn't had the home button issue, but it is not working on cm10. If some one of you can also comfirm this http://ville.giev.de/?p=382
[HTC One S] Sneakyghost:
Unfortunately, I seem to be getting more reports from 2.31 then from 2.21, so for now I'd disagree.

I'd return too if there was a way.

Gesendet von meinem HTC One S mit Tapatalk 2

---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------

Hi Tecaro!

Thanks for checking in here :D

That article you refer to speaks of a touch screen fix, not a touch button fix? Is that correct? Is it the same thing though?

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] Tecardo:
For me it helped, i haven'T researched anymore, cause the problem is not happening to often on my side.
[HTC One S] Burn-pl:
Hi Sneakyghost

I am on RUU 2.21 and CM9. I can confirm that issue occurs on my phone despite CM9 so I believe it does not contain any fix for our problem.
[HTC One S] Dublinguy:
Hi guys, Ive been away and I've been busy with work luckily :laugh: My phone went in for repair and it worked fine for about a month but its gone back to the home screen jumping again. My provider is hopefully changing the phone for me next week but for some reason I looked on their forums and they are "Out of stock" ?? Has HTC pulled the ONE S from the market?
[HTC One S] jbolts:
Similar issue when this problem surfaced for the samsung nexus S here

Fix never came... just empty promises of a magical ota fix that never happened.

Cant post link yet!.... have to reach 10 posts first
[HTC One S] Big4SMK:
I received an OTA update and am on baseband version 1.06es.50.02.31_10.09a.50.04L since a few weeks now. At first the problem seemed solved, but in retrospect I was just lucky a few times. Now that I have been using this version some more, it seems as barely nothing has been fixed. I still have the home button issue with bad reception. One pro though, most of the times I can continue to work with the buttons instead of having to push the power button :)
[HTC One S] Sneakyghost:
I really begin to have it quite bad again with the 1.06es Radio. The issue happened only twice on 2.21 but it's now back daily and very much in the foreground of things. Not as bad as with 1.78 but it's really gotten worse.

I totally regret the update.

Feel the Viper! :D
[HTC One S] zoesdad70:
which network provider are you with? it might be useful this time around to record when international unbranded handsets get the update and then when each network branded phone gets it.

Can't you downgrade the radio again on its own?

Seriously thinking about a custom Rom for my phone as the warranty doesn't seem to be worth jack.
[HTC One S] Sneakyghost:
If you are on an older hboot below 1.13 you might have a chance to downgrade the radio with a recovery externally booted via fastboot, but even then I think it's not really possible. You can flash equal or higher this way though. With hboot 1.13 and up, a radio can't even be flashed equal or higher unless by OTA or RUU.

So, if you happen to be on an older hboot still I would strongly advise to only flash components separately via fastboot and avoid RUU and OTA by all means as those always update your hboot too.

Feel the Viper! :D
[HTC One S] ExDr:
Me too. Today morning I experienced again this damned issue. I've wiped cache and dalvik-cache. Since then I have not experienced it again, but weekend mood was spoiled. Do you know if using of RUU 2.21 downgrades radio to 1.06s as well?
[HTC One S] Sneakyghost:
A little update/correction on the Radio flash matter:

Last night i was able to verify with two people that Radio downgrades are possible with hboot 1.09 and 1.06 or anything below 1.13.

Up until now i assumed that Radio flashes where only possible equal or up (versions) with fastboot or recovery when only flashing a radio.

However, this appears to be incorrect. A downgrade is also possible.

This makes it even more important to avoid RUU or OTA flashes as those always update the hboot.

So, if you are one of the lucky/smart ones that haven't yet updated their hboot, you better stay where you are and flash radios and other system components using recovery or fastboot to avoid the hboot upgrade.

---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------

Yeah thats a real shame. I hoped that others wouldn't update if i did share my experience here. I thought i made it quite clear that this radio is bad for our phones?

You shouldn't have done it. Sorry to hear that you are having trouble now too.

Unfortunately, a RUU downgrade will totally fail if i remember correctly. I remember having tried once and the RUU will just say impossible. It won't even install the other components, let alone the radio. As long as we don't get true S-OFF, we are stuck.

That's why i recommended to be very sure that the Radio is good before upgrading.

I hope that your experience now adds some weight to the statement. Maybe others will be more careful if they read this fail from two persons.
[HTC One S] ExDr:
Good news. RUU 2.21 is downgraded radio to 1.06s and than you can flash only rom with sense 4.1 (viper etc.). Hboot is the same for both 2.21 and 2.31. :good:
[HTC One S] Sneakyghost:
What?

You downgraded your Radio with using RUU 2.21?

Is that true?

Are you sure you don't have an S-OFF device by chance (some do have S-OFF from factory for some really odd reason, probably by accident)?
[HTC One S] usaff22:
I talked to an HTC representative, and he told me no phones are sent out with S-OFF. The only ones that have S-OFF are engineer's only devices.

Sent from pixels to more pixels
[HTC One S] ExDr:
Exactly. RUU flashes previous radio.

But now I have troubles with bootloader unlock. I do not now if it is particular case or not... Unlock token is flashed but not applied when I choose "yes", phone turns off without completion. But I think it may be because of htcdev site mailfunction.:confused:
[HTC One S] sirward:
I just received my One S back from Dynafix. They only did a software upgrade and indeed I can see that some sw has been changed.

The One S was send to Dynafix with:

1.78	0.16.31501S.17_2_10.23.31501S.10L

Now it's running

2.31 1.06es.50.02.31_10.09a.50.04L (nothing special afaik since I see those versions in the first post)

So far so good, we are planning to take the device with us to the death zone, as we name it, where the device was unable to work properly due to the TBP. So I'll try to keep you all posted for the next couple of days/weeks.
[HTC One S] Sneakyghost:
Sorry for your story. It will maybe be good for a while but most definitely come back and since those smart guys updated your hboot too it will be hard for you to go back.

Feel the Viper! :D

---------- Post added at 01:17 PM ---------- Previous post was at 01:16 PM ----------

I think you must have gotten an s-off sample then as usually downgrades do not work.

[EDIT]

Or you somehow damaged the security mechanism because s-off would mean you didn't need to unlock at all I think.

Feel the Viper! :D
[HTC One S] ExDr:
Hmmm, I am not the first who did it. I do not have s-off because I can not flash recovery. Before starting RUU and now (since I can not change it without unlock) there is supercid.

Why don't you start RUU 2.21 and see what happen?
[HTC One S] Sneakyghost:
True. They don't send out S-OFF devices. Why should they. lol. They would be stupid.

Still it happens by accident. I know someone who owns an S-OFF device and he didn't hack it for sure :D

He can flash everything back and forth just as he pleases.

Sometimes they forget to make it S-ON again when they work on it in their repair centers i think.

@ExDr

I will try to flash back to 2.21 tonight, no time right now unfortunately but if i can reproduce your situation that would be the biggest thing since month to find out for me, personally as i was dead sure this is not possible. I would just love this to work for everyone!

This whole S-ON thing seems a bit flakey to me. I am sure if people with skills where looking into these phenomena they would find a loophole there to force S-OFF. Too bad noone is interested.
[HTC One S] ExDr:
I have flashed 2.31 to discard troubles with unlock, but I can not unlock 2.31 as well (((

The worst thing is that RUU 2.21 is not flashed again showing error 140... So strange behavior of bootloader...
[HTC One S] opiswahn:
News from me, after some days with no problem, the problem began again, at first only onece a day and only for a very short period, then, is got worse each new day. Today, the phone is freaking out again like the one before I send it in.

So far so bad....

But this delay the problem comes back makes no sense to me. I mean either the problem is there or not, but this going from nearly nothing to total crap over a week is pretty strange. Couldn't be new software, i didn't install anything since the problem began anew...

This really pisses me off... I don't want so send the phone in again, couse it means again a week without a phone and a good chance to accomplish nothing...
[HTC One S] zoesdad70:
From my experience, the problem does seem to build up over time. HTC replaced my phone the first time I sent it to them and it took three weeks for the problem to raise its head.

If you're still on 1.78, HTC won't want the phone back - That's what they told me. So I have to wait until Vodafone rolls out whichever version they have. I advise you to hold on until you get your phone updated too. Mind you, HTC did let it slip that the update only fixed the issue for 60-70% of people and from browsing around the interwebs, it seems that 2.21 was a better update than 2.31.
[HTC One S] ExDr:
UPD: I have manage to unlock after factory reset from bootloader. But I still can not flash RUU 2.21 - it shows error.

I tried to analyze what happend. The first time I tried to flash RUU 2.21 my 1S had OTA 2.31 over 2.21. May be it was the reason of successful flashin 2.21. Later there was 2.31 installed using RUU and errors occured due to it, I suppose. So if there was vulnerability, it should be in ruu 2.21 or ota 2.21-2.31 :confused:

UPD2: User from 4pda.ru whose instance inspired me to downgrade to 2.21 confirm that he dowgraded from OTA installed 2.31, not from RUU installed.

Hope some geniuses will find the hole there )))
[HTC One S] Sneakyghost:
I just downgraded without any error from 2.31 but i had Venom Viper installed. I had no stock system. Just Radio and hboot where from the OTA.

Now, after reading your post i did this: compared MD5 and SHA-1 from each image in the OTA with the corresponding image in the RUU.

adsp.img; boot.img; hboot.nb0; Radio.img; Recovery.img; rpm.img; sbl1-1.img; sbl1-2.img; sbl1-3.img; sbl2.img; sbl3.img; tz.img; wcnss.img are identical to the last bit. No differences. These are most likely also the relevant files.

Then there are some images more in the RUU that where not in the OTA but i have no idea what they do. I don't know if they really do introduce a lock.

My downgrade really went smooth as butter with no relocking or any other sh1t. The only thing i might have done different is using the HTC adb.exe and fastboot.exe that are in the RUU.

I first extracted the RUU and took adb and fastboot from there. With those, i did all unlock, relock and flash stock recovery operations. Noticable where that both executables are much much larger than the ones from the Google SDK and that the device access is established noticably faster than with the sdk equivalents. They seem to be different.

I will spend some more trial and error on this to further find out during the coming days. I will run the 2.31 RUU sometime next days and check on the downgrade options.

My theory is though, that since the hboot is the same for 2.21 and 2.31 a downgrade is possible and for your phone, something just went very wrong. I could imagine that something in your phone is just damaged.

Did you lock the phone after upgrade with RUU and before running 2.21 for downgrade? Did you do "fastboot erase cache"? did you clear storage from bootloader? Have you gotten the latest drivers?
[HTC One S] ExDr:
Glad to hear you've manage to do it! :highfive: It seems that "fastboot erase cache" and cleaning storage from bootloader were missed... Would you please share all steps (or give a link) for my correctness :fingers-crossed:
[HTC One S] Sneakyghost:
It's not sure to help though just an idea mate.

Boot to boot loader, hook up device to pc, launch command prompt and navigate to your Android SDK folder. Then type in "fastboot erase cache"

This will clear the system cache. This is always recommended after kernel flashes and I think the RUU should be doing that too actually. Then there is an option in bootloader to clear storage. That will erase and reformat your sd card (backup your stuff first).

If your device doesn't accept fastboot commands you might have to unlock first.

Whenever you launch a RUU, it extracts to TEMP in Windows. If you look at the running parts with a process explorer you can find out where exactly. If you let the RUU wait you can copy out HTC 's adb and fastboot from there together with the adbwinapi.dll to some other folder (make it "c:/android" for easy navigation and a failsafe path). If you use those then you might have better results as this adb and fastboot is a special HTC one and I already noticed faster connections. Try with them.

I think I will upload a package with these files to my drop box tomorrow for people to use.

Feel the Viper! :D
[HTC One S] touch of jobo:
You can not run a RUU with a lower hboot than you have. But 2.21 and 2.31 both have hboot 1.14. So even though it is a radio downgrade, it is not a hboot downgrade.
[HTC One S] Sneakyghost:
Yeah thanks I figured that by now. :D

Feel the Viper! :D
[HTC One S] usaff22:
I so wish we could have S-OFF, then I could root without worrying about warranty purposes, people would be able to downgrade HBOOT, Radio etc.

But I don't think anyone is interested, as you said, which is quite unfortunate. One method could be to send a device to warranty S-ON, and see which partitions have changed if it arrives S-OFF. But as you said, no one is interested and willing to brick a number of their devices. Oh well.

Sent from pixels to more pixels
[HTC One S] Sneakyghost:
Yeah well thats a really hard task and not even unlimitid.io offer S-OFF for this phone so i guess as long as none of the guys with really special skills buys this phone there won't be anything happening.

I am just very glad that ExDr pointed out that i can backflash to the previous radio. The Phone's Wi-Fi is so much better again and the HBI is still occuring but its just mild and not very annoying so this was really cool. Thanks again. I was so sure that a backflash is impossible but i never thought about the identical hboots and that that could possibly be a chance...
[HTC One S] ExDr:
My pleasure. I've manage to downgrade radio and to restore my 2.31 backup as well. Now nobody complains about drop out of my voice during call :good:

Intresting fact that RUU 2.21 does not start with error 140 if there is unmodified stock 2.31. But it starts without any troubles if there is modified stock 2.31 or custom rom.
[HTC One S] Sneakyghost:
The RUU needs two preconditions to start ( i always launch it in fastboot mode - not as many fails from my experience):

Always: locked bootloader

Occasionally: Stock recovery being flashed prior to relocking. However, since the RUU does flash Recovery also, it is not always required, just if the process errors out this can be one of the first things to try.

Then, if there are errors, you can try to overcome them by thoroughly rinsing the Chip, namely by wiping and/or formatting /system, /data, /cache, then proceed to bootloader/fastboot mode and do a wipe there and also (remember to backup your stuff) wipe the SD Card.

The SD Card is often underrated. It is quite a common cause for trouble and is worth a decent wipe every now and again too. Here you have to be careful though as some formatting programs (if mounted as usb mass storage and connected to pc) also cause more trouble by setting wrong parameters. I prefer the build-in clear storage option and use windows programs only to recover the card in case it gets damaged/corrupted ("bricked" as some would probably say). The build-in process should ensure correct filesystem parameters and addressing.

If you observe these basics, it is not a problem to get a RUU to run.

Last but not least: i have frequently had issues with my firewall not recognizing changed adb pathes and not asking for new permissions, getting stuck in old rules and settings. Thus, adb would not work even though it appeared like its not blocked.

In my experience, its quite a good idea to fully switch of Firewalls and also antiviral protections to ensure ports are open and files not locked by some protective process. Then it should work.

So guys, now its on you to try 1.06s versus 1.06es radio.

If you are afraid of losing warranty: if you don't unlock and just run the two RUU's you'll be fine. Above instructions are mainly for those having unlocked and running custom stuff.

If any of youse is still on an old hboot you should by any means avoid flashing a RUU/OTA though as that will update your hboot and make going back below 2.21 impossible in case you are experiencing difficulties on the newer versions. Bear that in mind.

There is flash zips with full, untouched RUU's on XDA so you can unlock, flash a stock recovery and then flash components seperately like ROM, Radio, Recovery and such, then hboot doesnt get updated.
[HTC One S] geostar1:
Just talked to HTC's customer care manager on the phone. Apparently there is a new update coming out to fix the issue.
[HTC One S] opiswahn:
Thats what they always say... For at least 12 Weeks now...
[HTC One S] sirward:
As expected, two days after receiving the device back from Dynafix, it started flickering & vibrating again (touch buttons stopped working too) when we entered a cellar in the city where there was only EDGE service available.

I immediately contacted Dynafix again since there is a special rule about problems reported within two days that are not fixed after repair. Let's see what will happen now... Not sure if I should contact HTC again about this (double bookings for repair etc).
[HTC One S] corbie:
After 2,5 weeks waiting, I got my phone back from repair center. After unboxing, I didn't notice any changes in cover, no notes what was changed. I switch on the phone, turn GSM mode, run browser, and got sensitive button problem straight away. :(. This phone is a piece of crap. I lost rest of hope. I don't want to wait another few weeks for sending it back to repair center. I stuck with useless phone. Insurance company may only send it back again to repair center and give me nokia c1 as temoprary replacement.

I noticed now that they changed baseband from 0.15.31501S19_2_10.13.31501S to 0.16.31501S.17_2_10.23.31501S.10L

build number 1.78.206.4

I noticed also, that problem is even more frequent than last time.

I'm really disappointed.

Choosing HTC one S was my worst mistake i ever made. :(
[HTC One S] ExDr:
Why do not you try at least RUU 2.31?
[HTC One S] corbie:
Because In my opinion that is more hardware problem, than software. Anyway I noticed on my phone that problem show up even when I hold my phone touching volume button, or sometimes in moment when I'm sending or receiving text messages without data connection on.
[HTC One S] sirward:
True, RUU 2.31 is what our One S is running on after the trip to Dynafix. Had the same problem again on it so I'm afraid it's not a great fix, it might help a bit but we only have the device back for two days and that's a bit too short too call the update totally worthless I guess.
[HTC One S] Sneakyghost:
So they actually put you on the worst software available. A big LOL to your repair center. Send it back and tell them to get things done right or rather do it yourself.

Software 2.21 has the best results for most ( fix success rate 60 -70 percent according to HTC).

Upgrade to 1.06s radio and see if it helps you before you give up.

[NOTICE]

Because i get asked that often: i have all Radios and RUU's i could get hold of in my DropBox and my MediaFire down below in my signature. Just in case you need it.

[NOTICE 2]

Seems like only flashing a radio.zip with the radio.img is not enough. Configs are missing. Tecardo is working out a way to fully flash a radio including the right configs. Then the Up/Down process for testing different Radios in regards of the Home Button Issue can be considered complete. So the zips in my sig are good to flash but they do miss the right configs and if you flash them the phone will run with the configs you had previously in there. Not a problem at all but if you swap between US and WWE/EU it can be a problem (giving you bad signal, low speeds, drops and the like).