[HTC One S] Sneakyghost:
Finally i found some time to read up on my own thread lol. Been a while, always just bumping in with Tapatalk.

Informatiopal/Educational Stuff

Now, i would like to comment on another question that turned up here: How to think about IMEI and Serial changes?

First off, the IMEI is an international Mobile Equipment Identification. So its governed by an organisation bigger than one company. Hence, each and every single mainboard which is mobile (not only mobile phones these days) has a unique IMEI and cannot/shall not be overwritten with another. It is the finger print. Tampering with the IMEI is illegal in some countries. It is used to track people too. So its important for crime investigations too.

This means: if your IMEI changes you get a new board. If it doesn't change, your Board remains the same.

Secondly, the Serial Number: This is solely HTC's property and is mostly used to identify production badges and such. Hence, HTC can do whatever they like to it. So, to keep one phone to one customer and make it stay in the Support-System no matter how many Board-Changes it had, it always gets the same serial burned-in. This means, if you get a completely new phone, the Serial will still remain the same, since it is tied to you, the customer.

Think of it like that: IMEI is tied to the actual hardware, Serial to the customer.

Next subject:

I found that one user reported the issue apparently fixed with JB on a xx26 Phone.

This is quite likely as those phones are changed in hardware-design already and might well be fixed with a software update, whereas the phones prior to june will most likely never be fixed with a software update. That means, if your serial is xx25 or lower, the JB update will not help you in most cases. Keep in mind though, that if you had a repair and got a new board (e.g new IMEI), there is no way to tell its manufacturing date as it gets the old serial number (only way to tell production date so far). So, if you had already a repair and got a new board, there is no way to tell the probability of a reoccurence of the bug after you update to JB. You will have to find out the hard way.

A Report on my current doings:

You might have noticed that i wasn't around as much here. That has several reasons. Mostly, i have given up on this and am currently more into messing with the phone itself. I keep observing the issue though and i will most likely soon press for a replacement/rebuild as i am quite sick of it.

I also realized that there will be no way to make HTC look after this properly. I/we simply don't generate enough pressure.

The only way i see would be the "dirty way" over at Gibarians thread with generating MASSIVE negative publicity. It would need to be so absolutely bad and widespread that HTC would be forced to apologize in public and change their support strategy to direct replacement. This is not gonna happen simply because Gibarians thread generated too much aversion with the users here. Most people commented negative on it and hardly anyone participated. That is no base for decent action.

This is also my point of criticism towards you, my fellow forum readers. If we wanted to change anything, the only way would have been to "fight it dirty" as that is what HTC does. They are not genuine in what they say, they keep deceiving their users. So the only proper reaction would have been to pull this into the light of a big audience and make them blush and apologize.

Since this is not going to happen because too many where afraid to lose something (well there had been evil in the world before this and it could only become strong because fear was reigning the crowd), we pretty much have no option left.

I summarize: we had tried to find a fix ourselves which failed because someone with the right lab equipment didn't have access to an affected device and someone who knew enough about it and had an affected (even s-off'ed) device didn't have access to the right equipment.

We had tried to make public on a big scale what HTC does to us. That failed because people weren't motivated enough out of fear or not enough belief.

I had tried to collect huge amounts of statistical data to serve the publicity- approach and to assist HTC in finding the fault but that lead nowhere.

So we are pretty much left with the standard support strategy from HTC. This, in my eyes is a big WIN for HTC and a fail for us. That in turn makes me not wanting to continue here.

I think i will update the OP once more to the beginning of this brand spanking, shiny new year and then leave it open to your discussion. There is hardly any point in going any further. The only thing this can still serve is inform new victims about their (admittedly little) options.

Thanks for bearing with me and this long thread for so long. You all have contributed a hell of a lot of data and it has outlined the issue very, very clear. I am so sorry that it has helped nothing. So sorry. I wish i could have achieved more for you guys.

Good luck with getting your phones fixed.

I will always be around here but probably post as little as i did the past few weeks.