yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] whynot66:
just bricked mine trying to get s on for dust under screen i got it but couldnt do an ota so thought id go back to try dfferent stock ruu went throught the process but fastboot reboot-bootloader and bricked............ going to htc on friday "doing an ota and never rebooted" under warranty so fingers toes and bollocks are crossed
[HTC Sensation] bobsie41:
Should be OK. I did exactly the same some time ago and gave the same excuse.

Had it back within the week with new motherboard. :D

EDIT On a sidenote. If something like this was possible, why wouldn't HTC repair center do it?
[HTC Sensation] mox123:
is this some sort of hardware fault ?? where the actual hardware is failing and could be a co-incidence,

I don't think that it's just rooted users who are having this issues, the only reason we are hearing of this happening whilst rooting is due to the fact xda is a rooting forum if you get what I mean,

could be freak random failure due to bad batch of hardware or some random flaw in the manufacturing of hardware components,

this just dont go dead for no reason so I'm guessing hardware failure and rooting is nothing to do with it

ive been messing about with fws, ics, etc. running at 1.8ghz oc and blasting the heck out of my phone (2 batteries, hardcore 3d gaming modern combat 3, asphalt 6 hd, etc) where the screen is scortching hot and I can't touch it (need to blow it for 60 secs to cool it down), and no issues

however I am on 3.12 now and not 3.24 as I need to do a full wipe and cant be arsed doing that
[HTC Sensation] EddyOS:
HTC replaced my mainboard on my Sensation after this happened when I tried to flash a stock RUU - no questions asked
[HTC Sensation] Behold_this:
Why should HTC pay for your **** up (bricking the phone not the dust)? Just curious. Some people are so entitled...it's always someone else's fault isn't it? I mean why suffer consequences of your own inexperience or for taking your own KNOWN risk. I think it is truly disgusting how some of you think this kind of FRAUD is cool.
[HTC Sensation] RussianBear:
i seriously doubt a single software command would do a hardware damage. there has to be a pattern to this. if we could find what it is, a solution might be closer than we think. perhaps this adb command erases (obviously, not all the time) some important drivers from the phone's memory? i have no clue, just talking out my ass here lol
[HTC Sensation] dkephart:
Whose fraud is this, anyhow?

At the extreme risk of feeding a troll:

I think the only fraud is "selling" a product that with hidden dangers to the new owner. Imagine if putting a Chevy engine in a Ford was wired to caused the gas tank to stop accepting fuel. That's fraud, and its on the mfrs' hands.

There is a good reason HTC replaces Sensations in QHSUSB state: they made a bundle off of the devices that never get rooted (and some that do).
[HTC Sensation] Behold_this:
Look at my post count and thank you's, champ...I'm not a troll.

And btw HTC doesn't have to fix people's screw ups, like bricks that occur from users cracking their bootloaders and flashing unauthorized software. Just like Ford won't warranty a car that had a Chevy engine put in it. Also they certainly have the right to make it so their cars fail to run with unauthorized parts, to use your ridiculous analogy.
[HTC Sensation] mrg02d:
Guys, there is a rumor that the chips in our regular sensations are from a run that have poor QC. I remember reading back last year that the reason the XE is clocked at 1.5Ghz and our regular sensations at 1.2Ghz was because our run of chips were lower quality and not stable (within their accepted error range) at 1.5Ghz. Perhaps all this flashing triggered a hardware failure. Back when this happened to me, (I AM the OP afterall) I hadnt been doing anything silly. It was sitting idle and when I went to wake it, it was dead. I told Tmobile all this and they said it was a hardware failure. Instant exchange. They were actually more interested in the dust under my screen.

If you were doing something dumb like going back to S-ON, then its likely your fault. If it was sitting by itself, it is likely the chip's fault.

GUYS! Stop trying to achieve S-ON! Obviously, there is something funny about it. There is also no need to do it. There arent any cases of warranty voiding from HTC seeing that you are S-OFF. DO flash YOUR RUU.exe before returning it. DONT bother with S-ON. So you know, I was S-OFF and returned the dead phone. No one found out, nothing came of it. Tmobile made me swear that there were no cracks on the glass. They were more concerened about the glass than anything else.

Figured I should add that my first phone did the same refusal to wake thing on day one with it. Long before rooting and S-OFF had been achieved. It took an hour of messing with it to get it to boot. It was full battery and left idle. I went to wake it, and it was dead as hell. I pulled the battery and all that jazz to no avail. Shortly before I tried getting in touch with Tmobile, it booted. I had held the power button nearly 60 seconds and then it booted. I was scared as heck knowing I had done nothing to it. I returned it the next day for the dust issue and being within the first 14 days.

Also, second phone, the one that died (im on # 3 now) was unstable at 1.5Ghz. It would crash as soon as I tried to clock it over 1.2Ghz. Thats funny since our chip is native at 1.5Ghz!

Dont rule out hardware failure due to crappy QC. I feel HTC covered up something with our regular sensations...

Matt

Matt
[HTC Sensation] undercover:
It's not crappy QC, its actually a result.of.good QC. It's called speed binning, look it up.

Just remember one thing, not all chips are born equal.

Sent throught the wormhole from my CoinInserted Sensation OG.
[HTC Sensation] RussianBear:
can anybody dissect what exactly does the s-on command do?
[HTC Sensation] RussianBear:
some more info on how to put the sensation into the diag mode, then load qpst http://xdaforums.com/showthread.php?t=1366771

edit: qpst setup: http://android-dls.com/wiki/index.p...d_Restore#Using_QPST_to_backup_mobile_setting

http://xdaforums.com/showthread.php?t=1101166
[HTC Sensation] :
-------------
[HTC Sensation] undercover:
S-ON is dangerous if you are not completely back to stock. So far its been the only thing causing bricks, bar few times when people erased certain partitions. Please do not make people believe its not dangerous, it will make.them careless. The scarier it is, the more information they will seek to prevent brick.

Sent throught the wormhole from my CoinInserted Sensation OG.
[HTC Sensation] mrg02d:
One chip being able to run stable at 1.5 GHz, or even 1.8GHz as others claim and another crashing at over 1.2Ghz ain't good QC. There was plenty discussion over possible inferior chips being used in the original sensation. Go look THAT up...

If it were a simple matter of being born unequally, then that sort of range IS POS crappy.

Matt
[HTC Sensation] mrbkkt1:
realistically, once you root, you have no reason to go back to s-on.never really had problems with the n1 getting warranty repair, although if you brick doing it, htc should charge you for the repair imho. there are numerous warnings, they are there for a reason.
[HTC Sensation] sshede:
THIS. The guides have specific information on how to proceed in relocking the device. If you choose to S-On and don't follow directions, it's kind of the hand you've delt yourself. If you want to S-On, it's only logical that literally everything else be back to stock before you bundle the phone back up. You don't wrap up the package before you put the gift inside, do you?
[HTC Sensation] :
------------
[HTC Sensation] undercover:
This is normal in chip world. Why do you think Intel has same chips being supplied with different frequency?

Sent throught the wormhole from my CoinInserted Sensation OG.
[HTC Sensation] :
Is it somehow possible to find out how much your processor is capable of? Without destroying your device ;)
[HTC Sensation] undercover:
Yup. Just use kernel with highest frequency available. Then go up step by step using System Tuner or similar WITHOUT ticking "apply on boot". When it just shuts down, you know you reached its limit. Mine is ok just below 1.7, anything higher, it crashes. Also, you could try increasing voltage a bit before setting frequency, that might allow you to go a step or two higher, but can be dangerous.

Sent throught the wormhole from my CoinInserted Sensation OG.
[HTC Sensation] wmoore:
I used to work in a factory making RAM chips and I can say categorically that there can be huge differences in quality. We pushed chips out the door with 4 different grades with pretty variable QA results across those grades.
[HTC Sensation] RussianBear:
can you not feed the troll, please...

to the leo guy: if you have nothing useful to add (i.e. how to unbrick the device), then don't post here.
[HTC Sensation] :
Happy?
[HTC Sensation] KAwAtA:
hhahahaha 10 char!
[HTC Sensation] mrg02d:
That is still a QC issue, else all the regular sensations would run stable at 1.2Ghz and crash somewhere over. Having mine stable to 1.2Ghz, another's at 1.5Ghz, and then some making it to 1.78Ghz is crappy and unfair. They state 1.2Ghz in the data sheet, yet they have three different classes of phone? Qualcomm states 1.5Ghz. I'll bet Htc got a deal to take a lot of some unequally made chips.

It's also fishy that the XE came out shortly with 1.5Ghz as its stock speed.

I also wonder if the asynchronous design had any hidden drawbacks? Everyone acts like its such a great idea, yet I see no difference in battery life or performance when running both cores forced on as opposed to asynchronous. How many other phones use asynchronous design?

Matt
[HTC Sensation] undercover:
You just wouldn't accept the truth, would you? You just want people to agree with what you want to hear.

If you cared to look carefully at msm8260 data sheet you would see that its not 1.5 but rather 1.2-1.5. Speed binning came, so they chucked weaker CPUs in OG, stronger in XE. Maybe there was shortage of CPUs so they thrown some stronger ones in the OG as well. That's how its different for each phone.

Anyway. All info us out there, its just a matter of reading up. Oh, and listening to people who WORKED at factories which.made chips and are well aware if the whole process (one of the posters above).

Sorry for OT, really sorry.

Sent throught the wormhole from my CoinInserted Sensation OG.
[HTC Sensation] mrg02d:
Ill bet the issue is really over YOU being butt hurt over ME laughing about Baad getting a slap on the wrist for kanging, isnt it? Your PMs sound like you took it far too personal. Get out of my thread unless you have some trials to prove that a potentially faulty chip cannot be bricked when being overclocked.

The real issue here isnt whether or not HTC and qualcomm were turds for having such a range of operating frequencys, its whether or not rooting/overclocking a less than perfect chip might break it. For some, it just shuts off. For others? Who knows? Anyone? I suspect that HTC used chips that had issues...Some with the issue that rooting/overclocking caused hardware failure.

Could Qualcomm getting cute with their asynchrounous idea also be a possible issue? Maybe a faulty chip, coupled with the asynchrounous gimmick (as of now, I see no trials to prove asynchrounous operation worthwhile) fails when overclocked, or fails due to something in the rooting process? Its too bad we cannot dissect a bricked CPU and see what happened...

I shouldnt pay the same amount for 1.2Ghz if plenty others can run at 1.78Ghz. Thats like paying the same amount to see a movie and getting stuck in the tiny, crappy theatre when others are watching it on the massive screen with plenty of seating.

Keep in mind as well, that people have had their phone crash and burn without any rooting. Something is up with our phones, and I suspect the chip. Unless you do something silly, id assume a brick is from half baked hardware failing. Prove me wrong, id appreicate it. That way we could figure out what the hell is causing the ninja bricks to occur.

EDIT: Seems to me that the message code we are seeing is more along the lines of having the bootloader erased, right? So now, what might cause this to be erased? What gives us access to this? Could rooting accidentally provide some doorway to this part of the phone? If so, then it would be nice if we could develop some way to shut that door. For example (ipad alert, turn away now if you have a silly hate for apple):

The Ipad 2 was jailbroken recently (for 5.0.1). I was told that there was some doorway open that allowed the program to go in and jailbreak. I read that there is another action recommended to CLOSE this doorway to prevent malicious activity. Could rooting our phones have caused some path to be opened that allows us to accidentally erase the bootloader?

Matt
[HTC Sensation] undercover:
Lol, funniest thing I've heard all day. :D

Yes, sir, I'm getting out of YOUR thread. :cool: Bye.
[HTC Sensation] qpqpqp:
So guys is this a software or hardware issue? Is it still safe to root and install custom rom? I bought my phone off of craiglist so i don't think i can do anything if it brick.
[HTC Sensation] RussianBear:
root away, but read all the guides carefully.

probably a lot more than that, since the phone won't even respond to the power button or charger. adb is a powerful tool that can lead to serious consequences.

i've pm'ed several people that were able to access qpst with a gsm phone variant, but haven't heard back yet.

---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------

bumping this over other stuff.

evo 3d download mode rig-up. http://urandroid.com/2011/08/02/work-in-progress-–-access-to-download-mode-on-evo-3d/

it seems like straight shot the more i read about this. all we need are some people that are willing to make a copy of their system. i'm not sure what kind of info will be gathered, so we'll need some volunteers. i confirm that *#*#3424#*#* does work and opens up a diagnostic menu. i'm on a gb build by insertcoin.
[HTC Sensation] :
I could make a copy of my system. You need only system.img ? Which version?
[HTC Sensation] RussianBear:
you'll have to connect your phone with qpst software. check this thread: http://xdaforums.com/showthread.php?t=1468791

see if you can access the *#*#diag#*#* menu first though.

if you're successful in making a system dump like that, we're almost half way there.

p.s. didn't mean to sound like a **** to you earlier.

---------- Post added at 01:56 PM ---------- Previous post was at 01:53 PM ----------

breakthrough on galaxy s2 forum:

http://xdaforums.com/showpost.php?p=22648011&postcount=47

don't flash that file though lol
[HTC Sensation] :
Okay i can do this tomorrow. Im just too tired this moment
[HTC Sensation] :
So that's everything I get with the DIAG Menu.

Does somebody know how to let your pc recognize your sensation in the QHUSB_DLOAD Mode? Other Methods than bricking :D

Okay I tried Any Cut, but there is no PhoneUtil. So I might need some help with it.
[HTC Sensation] dkephart:
In lieu of PM...

Wonderful. Congratulations.

Except...auto manufacturers construct to specifications, they don't booby-trap the car, although it is up to you to get the authorized parts or the correctly constructed imitations thereof.

In the case of locking down bootloaders, the S-ON switch, and so on, we are talking about deliberately setting things up in a manner that makes it difficult to use your device in a reasonable way. The htcdev unlock site is an admission that this is so. My analogy would have been stronger, I admit, if I had said "replacing a Chevy engine with a slightly modified copy of a Chevy engine" which is more like what we do when we flash ROMS.

You miss my other point: HTC does replace bricked phones, according to the earlier post. The only conceivable explanation is that they make enough off the initial sale to provide for this.

Sorry this is so OT, but I see no reason that we should take the blame when the system is deliberately wired to make relatively slight errors have grievous consequences.

On topic: glad to hear of the progress with QPST.

In the meantime, yes, extreme care is called for in backing down to S-ON; you must flash the original ROM first from RUU or you will have a brick, courtesy the manufacturer. And Behold_this will laugh at you.
[HTC Sensation] Behold_this:
Damn right;)
[HTC Sensation] thetinguy:
No it's not. It's called binning, and every integrated circuit manufacturer does it. "My rude comment here was removed by a Moderator because i'm silly and didn't read XDA's rules"

http://en.wikipedia.org/wiki/Product_binning
[HTC Sensation] masondoctorjt:
Then everyone should pay different prices for cars too, because there are pretty big variances in horsepower between engines that are supposed to be identical.
[HTC Sensation] :
Okay, don't get me wrong, but I think we're heading in the wrong direction. I think it's clear that the manufacturers do Product Binning so not every chip is equaly overclockable. But I really want to help the guys who bricked their device. May you please start a new topic for it.

And please don't be offended.
[HTC Sensation] mrg02d:
You guys need to get out of this thread. It isn't about who is right and who is wrong with respect to binning or QC, it is about causes and fixes of a brick. I still stand by my statement, the sensation has poor quality control. It's evident throughout the phone. We could go back and forth defining quality to be what we want it to be for the sake of winning an argument.

Go start your own thread if you want to argue over the quality, or lack thereof , of the sensations processor.

Oh, and don't ever come quote Wikipedia as your source for something in an argument. That makes you look like an idiot. If you don't understand why quoting Wikipedia is idiotic, then you are of no concern to me anyways.

Matt
[HTC Sensation] hlenforcer:
The most idiotic thing happening in this thread here seems to be a guy who has no clue of what he´s talking about while he thinks his opinion must be the truth ... :rolleyes:

in fact thinking the bricks are a cause of bad QC or cpu "exploding" while running at specific frequencies or aSMP beeing not a feature but a bug (:D) seems to be a bit ridiculous ...

in most situations the brick will be caused by the user itself, not applying stock RUU before going S-ON or by modifying/using things they know nothing about ...

for example you cannot brick your cpu by setting to high frequencies, but by setting to high voltage, all the bigger kernel have voltage limits so that noobs can´t do something wrong, but if they use some **** kernel without that security ofc a cpu can be bricked

i also heard about user modifying/deleting thermal d while not knowing what this thing does and then complain about cpu´s start burning while benching at 1,9ghz :rolleyes:

But blaming HTC for bad QC because they are putting cpus in a phone sold with 1,2ghz that sometimes can reach 1,3ghz and sometimes can reach 1,8ghz is really ridiculous, OC-capabilities are a result of a superior manufacturing technic compared to the goals of the product which is nice to have but really no bought feature ...on pc hardware some times ago this kind of cpus got most fame because you had the chance to get a cpu that reaches 50% more performance than sold with, but you really cant complain about getting a cpu that is less OCable than the average ones ...
[HTC Sensation] dkephart:
+1

...and in fact this is obvious: the fact that the phone goes into QHS_USB state proves...the CPU is still alive! The problem is then that something that you did violated the tight restraints on what is permitted with using fastboot (not adb, as I understand it, BTW) causing the bootloader to curl up like a poked anemone...

Some call this noobness on your part (which, of course, it is!), I think it is just as much proprietary wierdness on the part of HTC. One thing is clear, though: if you don't want to read the requirements of going from S-OFF to S-ON and think you might want to do so, you are rooting the wrong device.

One more time: the ounce of prevention is reading and realizing that you must use an RUU to ROM and recovery in their original state before turning the secureflag "ON". And if you don't know what this means, don't try it.

That said, is there any answer yet to whether a restore is possible from the QPST image? I am not volunteering to test this, you notice... ;)

dkephart
[HTC Sensation] mrg02d:
Not all bricks are from s-on. Mine happened while it sat idle, weeks after rooting and OCing. Do explain that one mr. "I have all the answers "

Who is to say that the chip was ever intended for 1.2Ghz max, yet the manufacturer wound up main many capable of much more? I see it as them having 1.5Ghz as the target and wound up with a run that wasnt stable over 1.2Ghz.

Enough of this crap. You can't explain all bricks by user error. Something is wrong with a chip that sits idle and then fails. End of story. Either present a refereed paper disputing me, or sit the hell down. Your trolling comments have nothing to do with fixing this. I presented the idea as just that, an idea.

Go start your own thread about how butthurt you are over something I said. You too tinky, I see your sad little butt in here thanking people for stirring up trouble. You damn well know my comments about Baad were justified. It ain't my fault he effed up and got into trouble, it's his. So stfu already about it.
[HTC Sensation] hlenforcer:
Qualcomm :rolleyes: the target clocks can be between 1,2ghz-1,5ghz depending on what HTC ordered for the OG Sensation ... just look at their specs sheet ...

Some of this bricks are user errors, i never said that all should be, believe it or not, also a HTC phone can break, like a toaster can break, and this should not have something to do with failing QA ... there are millions of sold sensations and an amount below 1% bricks their sensation through noobness or through bad luck, phones including all of their internals can break on its own, surprise surprise ...

And if you believe it or not, i talked already to ppl that looked into this download mode and related things for self education and interest in ARM SoC´s and would be able to recover those broken sensations, but they won´t do it because it is just to unimportant and to risky to break them completely ... so i see no real sense in this thread, nobody will say: "come set me up an unix box + ssh + sensation connected through usb to fix that thing ..."

but i´m not "mr. "I have all the answers "", so maybe i´m wrong ;)
[HTC Sensation] mrg02d:
" so i see no real sense in this thread"

And with that, you are free to leave. Anything else is simply to stir up trouble. There's the door, get out. Just because you feel differently doesn't give you the right to come in here and state that YOUR understanding is defacto. It's ridiculous that you would claim to have spoken with "people" and that you guys decided, with your infinite wisdom, that it's worthless to try fixing this kind of error and just expect us all to accept it.

Tinky, you are just making yourself out to be an ass with your giving thanks to anyone that comes in here to stir up trouble. Thought you were leaving?

Matt
[HTC Sensation] masondoctorjt:
Fact is, most the bricks happened from poor direction following. Ie. Writing secureflag before flashing stock RUU. You can't EXPECT a CPU rated at 1.2ghz to overclock, but it is nice that it does. It seems way more CPUs clock to 1.7 or even higher than have been bricked. That is what, a 40% overclock? That's pretty good if you ask me. And many go further to 1.9ghz, sooooo. Not sure what the problem is, especially since HTC replaces them even when it is user error, why don't we get back to discussing how to fix, rather than blame a CPU that, for the majority, performs 40% better than it is supposed to.
[HTC Sensation] scummymoney:
So tmobile instantly exchanged your phone due to the faulty chip? My phone is most likely soft-bricked, i would like to ameliorate the phone by myself. However, going to t-mobile and exploring the weaker chips predicament would not be a bad last resort..