yashsingh1/xdaforums huggingface dataset:
[HTC Incredible S] corey unknown:
As someone with 16000 S-On :( Im really glad to hear this .. as for the banter on HTC's speed or lack of for updates ... HTC builds are cranked out faster unofficial or official than any other phone models I own ... Normally I don't care much for official rollouts but as there's no s off working for me atm ,knowing that there is confirmed rollouts coming I'm quite happy to wait ... Definate worth waiting for solid n stable than quick n buggy fota...
[HTC Incredible S] -Maverick-:
Can't wait for this to hit, Mike will have a new base for his Android Revolution HD Rom. :D
[HTC Incredible S] Ol' Blue Eyes:
Yes that's fantastic news. Hopefully with the new official Sense 3 ROM, more custom ROMS will be available for us IncS users instead of having devs and cooks port ROMs from other handsets. Perhaps soon we'll have more choice of custom sense ROMs! =)
[HTC Incredible S] RicarduZonta:
Yeaa, can't wait. Hope they don't put the project on hold, because of the resources they need for ICS device updates.

Got bored of sense 2.1. The 3d launcher looks amazing.

Does anyone know if the dialer issue got fixed in 2.3.5?
[HTC Incredible S] sgyh0521:
Id asked HTC and they replied that Incredible S would surely get a Sense 3.5 update but they didnt have exact schedule now:)
[HTC Incredible S] baste07:
That's their robot reply. Yes but no date.
[HTC Incredible S] Splux:
3.5? As far as I know they've only said we'll get the 3.0 update...
[HTC Incredible S] sgyh0521:
In fact sense 3.5 will use less system resources than sense 3.0 and thats why devices using MSN8255 can get this update
[HTC Incredible S] Ol' Blue Eyes:
Does anyone know the exact differences between Sense 3.0 and 3.5? I've tried both ROMs before and there a few UI changes (e.g the tick and the checkbox is different) and you can jump from dialer to contacts, favorites etc directly from the jog dial and the bottom.
[HTC Incredible S] Splux:
But, from what HTC said - we're getting 3.0, not 3.5 :)

At least that's what they said in their official statement.
[HTC Incredible S] EvrStngNevDwn:
Here are the reply i got from HTC when i asked about Sense 3.0 release

Hope it truth.
[HTC Incredible S] RicarduZonta:
Sense 3.0 for Christmas! Thanks for that mate!
[HTC Incredible S] baste07:
Doesn't desire s have sense 3.0 already?
[HTC Incredible S] Splux:
Yes, they have.

http://www.xda-developers.com/android/official-ota-update-for-desire-s-with-sense-3-0/
[HTC Incredible S] baste07:
So the statement of htc rep is crap, because he doesn't even know that desire s already has it
[HTC Desire S] :
I am completely new, I have an s-off ds, I want to turn s-on back on so I can update my phone to 2.3.5 any ideas how to, sorry if I seem dumb
[HTC Desire S] jneapan:
I'm not sure why you would want to get S-ON just to have an official upgrade to 2.3.5 when custom ROMs already have 2.3.7, but I believe what you're looking for is in this guide:

http://xdaforums.com/showthread.php?t=1187231

Any other questions you might have can be answered by searching through the Desire S Android Development Forums

You can always browse through this Index for anything else worth mentioning. Hope this helps.
[HTC Desire S] :
I would agree with previous post. Seen all the problems with official update? Much better off sticking with s-off and one of proxusers sense 3.0 ports. Or bindroid. Or coredroid. Any problems will be patched much faster than HTC.
[HTC Desire S] :
I dont understand a word of what any of you said. I want it back to when I bought it. I dont understand any of this.
[HTC Desire S] jneapan:
The fact is, there isn't a simple "one click and you're done" way to do this. So if you really want to do this, you're going to have to learn how to. The thread i linked is a good start, and the index thread in the development forum is also a great place to find guides on doing just about anything you might need. If all else fails, you could try and find someone in your area who's willing to do this for you, but I wouldn't depend on it.
[HTC Desire S] :
Thanks for all the help. I took it back to store claiming software fault. They replaced my phone.
[HTC Desire S] ice age druid:
Smal problem here. I got a Desire S. I made it S-off can that be the problem. How to restore this?
[HTC Desire S] :
Dude. Read other posts. Im new at this.
[HTC Sensation] mrg02d:
Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.

Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.

Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.

Tmobile chalked it up to hardware failure and has a new (likely refurbished :rolleyes:) on its way.

I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?

Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.

Matt
[HTC Sensation] badnewswrx:
Just swayed my decision on wether to root or not.
[HTC Sensation] TheStigx:
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
[HTC Sensation] Behold_this:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
[HTC Sensation] mrg02d:
Hey guys, it is dead as a door knob.

http://xdaforums.com/showthread.php?t=1321110

That ought to sum things up...

Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
[HTC Sensation] mrg02d:
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.

My computer told me that it failed to install whatever it felt it needed.

So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?

Although I have a new one coming, Id like to get to the bottom of this for everyone else.

Matt
[HTC Sensation] Behold_this:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
[HTC Sensation] mrg02d:
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens. :)

Im guessing that is what a JTAG does? Would be great once warranty time is over!

I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?

Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
[HTC Sensation] Behold_this:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
[HTC Sensation] mrg02d:
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?

I guess its safer to start over, huh?

EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.

Matt
[HTC Sensation] Behold_this:
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
[HTC Sensation] vitusdoom:
nice. maybe there are aliens inside your phone! :) Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much :D
[HTC Sensation] mrg02d:
:D

Im the alien!

Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.

Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.

Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.

I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).

Ugg..

Matt
[HTC Sensation] vitusdoom:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. :P (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. :( )

where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
[HTC Sensation] mrg02d:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone. :(

Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.

Matt
[HTC Sensation] vitusdoom:
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.

most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this :P ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this? :D
[HTC Sensation] k2worldwweapon:
this is the EXACT problem im having! on my tmobile SGS2
[HTC Sensation] k2worldwweapon:
not sure if this has already been mentioned but what do you guys think of this?

http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
[HTC Sensation] galsalah:
Hey guys,

I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
[HTC Sensation] stressak:
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(
[HTC Sensation] drpink:
InsertCoin

I just installed this. It seemed to install OK but the phone just keeps rebooting to the HTC screen.

The problem is, my backup didn't get saved to the SD Card

Anyone help?

Appreciated.
[HTC Sensation] mrg02d:
So you can boot into recovery, right? And you are saying that while in recovery you see that you have no backup to boot to, right? Take out the SD card and put it into something that will let you connect to your PC. Load a ROM onto the SD card and then put it back into the phone, boot into recovery, and flash the ROM.

This ought to work, unless someone sees something bad about it.

Matt
[HTC Sensation] mrg02d:
A factory fix will be the fastest...Someone would have to develop a JTAG and have the software to re-flash the device. Right?

Not something I would do or let anyone without extensive knowledge and experience do.

Matt
[HTC Sensation] stressak:
Well, thats not really good news :-/ I really dont understand why nobody can ubrick that, even when its so common problem nowdays
[HTC Sensation] moto211:
Its not that no one can fix it. I'm sure there are plenty of qualified devs who can figure out how to utilize this mode and/or come up with a jtag solution. The issue is that every sensation in existence is less than a year old and therefore under warranty so why spend time fixing something that the factory will fix? And if you unlocked using the HTC method and have a truly voided warranty, wtf were you thinking? Jk. But it does suck if you're in that boat.
[HTC Sensation] Matt1408:
Yeah, it's "technicially" possible to fix this in the QHSUSB mode, but none of us have the tools to do this. Which is sad, really...

I got this problem after accidentally overwriting the wrong partition on my phone and then it just wouldn't boot... But anyways, I got the driver for the QHSUSB, and I was able to talk to the phone using Putty, but that came to a dead end because I really had no idea what to do.

Anyways, I took the phone to my carrier and they shipped it out to get it fixed. I received the same phone back, meaning that the tools to fix this DO exist, they're just safely in the hands of the HTC Authorized Repair Centres...
[HTC Sensation] k2worldwweapon:
and you didnt have any issues with your warranty being voided? i just shipped my SGS2 and im a little nervous that they will try to charge me money to fix it because of the fact that i bricked it
[HTC Sensation] NielDK:
This would be great to have as a seperate section really.

Seems this is some sort of "backdoor" recovery.

More info and mentions of some tools here. http://rootzwiki.com/topic/4602-qdloader-driver/

and here http://xdaforums.com/showthread.php?t=1188510
[HTC Sensation] gtrplr71:
My phone met the QSHUSB driver brick when trying to relock the bootloader for dust under the screen when using the adb command "fastboot oem writesecureflag 3" I am just curios will charge me for this? did HTC charge you guys? Tmobile is sending me a new device
[HTC Sensation] vinas1:
fastboot oem writesecureflag 3 just bricked my Sensation too. Luckily, I have another here because I too was turning S-ON and them BAM! BRICKED! :mad:

but like I said it's going back to them and I have the replacement up and running... just be aware people! ;)
[HTC Sensation] Catnap:
Hmm, awful lot of people getting bricked when trying to go back to S-ON. Doesn't look good for returning it if I get screen dust.
[HTC Sensation] ajay83:
In what order did you try & restore s-on? I've returned mine to s-on in the pass no problem.

Order I did it was:

Flash ruu.exe from pc

Already had super-cid, so just used "fastboot oem writesecureflag 3 " command & bootloader locked & went to s-on no problem.

Problems can occur if trying to s-on on rooted backups, etc...

If restoring the original backup made of rom that came with phone, then I think you restore backup, restore stock recovery for your backup then s-on & it should work.
[HTC Sensation] EddyOS:
Just happened to me, was trying to flash a new RUU (using the PG58IMG method) and it now just sits on a black screen and the QHSUSB_DLOAD was picked up by Windows. Got the drivers for it but have no idea what to do now.

Just as well I don't use my Sensation now I have a Galaxy Nexus but was curious as to these new ICS RUUs. That'll learn me!!

Off to CPW I go
[HTC Sensation] aNYthing24:
Hey Eddy, I remember you saying stock ICS looked ugly. What changed your mind? :p
[HTC Sensation] EddyOS:
The Nexus was a free upgrade and is bloody awesome!! LOL!!
[HTC Sensation] xuvert:
OMG!!!!

I was using my phone and suddenly BANG!!! it shuts down and now doesn't starts.

When i plug in to my computer "QHSUSB_DLOAD" driver don't found.... i am really disappointed of HTC

And for my bad luck, a friend purchased the phone in Canada and i have no invoice and also no HTC service in México...

What a bad day.

Greetings!
[HTC Sensation] aNYthing24:
It just happened randomly? Were you rooted? Trying to flash something custom?
[HTC Sensation] xuvert:
Hello aNTthing24.

yes it was randomly... I was writting a whats app message when it reboots two times and then black screen...

and yes it was rooted, i wasn't trying to install nothing.

i'm very sad :(

Greetings
[HTC Sensation] undercover:
Do we have a potential time bomb here?
[HTC Sensation] masondoctorjt:
I hope not. Seems there would be more happening like that if it was a timebomb. I mean look at how many posts there are about dust.
[HTC Sensation] xuvert:
I have been reading a lot and the thing is that the phone appears to be completly empty and waiting to be reprogrammed...

Someone that wants to share their phone and boot image in hex to try to unbrick the phone??? It would be really great!! :cool:

Greetings
[HTC Sensation] jeibosquez:
it's so WEIRD! i needed to get S-ON to send back for warranty and i had rooted via revolutionary flashed almost every ROM for the sensation( at least what was available at end of october) and when my clumsy self droped my fone at work it cracked the screen! i did my reseach and flashed the t-mo 1.29 RUU then the secure flag3 command in fastboot! THING IS after i S-OFF'ed the same fone just cause i wanted to practice using adb! and both times it worked flawlessly! IDK whats going on!
[HTC Sensation] Jedi2011:
It's because you did the S-ON after flashing with a factory RUU.

The bricks seem to be happening when people flash a stock ROM via CWM and then try to set S-ON while the device is still rooted.
[HTC Sensation] EddyOS:
Mine did it just from flashing the RUU, wasn't even trying to S-ON. I was just wanting to see what the new leaked ICS RUU was like
[HTC Sensation] Mash23:
I think this might ne because of the test RUU because I have returned S-ON 3 times with 1.45 RUU and it hää always booted with no errors what so ever. The new ICS 4.0.3 won't boot without the firmware from the RUU.
[HTC Sensation] EddyOS:
I know it's a test RUU but flashing the RUU in its entirety includes the FW so it's nothing to do with that. It's just my phone falling over! Gonna send it back to HTC when I can be bothered
[HTC Sensation] dexter93:
Did anyone try the QPST tool? There's a chance you could reflash the bootloader
[HTC Sensation] Sdobron:
You need the files though.

The ICS firmware caused this hard brick for me. It probably has been causing other bricks too. I don't think cwm is the problem. It's been around for a long time and on plenty of devices.
[HTC Sensation] ajay83:
I wonder if everyone with this problem should write up exactly what software they were running or had before they had a brick?

Ive also tried the ICS roms and used firmware before hand, but went back to my XE 1.73.401.4 rooted back up and flashed hboot 1.17.0011 now.

Wondering whether any traces of that firmware is left behind and could cause a problem should I try and S-ON again?

This seems to be an interesting problem indeed.
[HTC Sensation] xuvert:
Yes, i looked at it yesterday, but with QPST i need an MBN factory image...
[HTC Sensation] hlenforcer:
Yep, would be a good idea if the thread starter could start a vote for ppl with bricked devices, to see which of them tried the ics firmware, would be interesting in my opinion.
[HTC Sensation] undercover:
You *****, just flash it LOL.

On a serious note, it would be interesting to see more work in regards to that. If someone knows exactly what we need to unbrick (if its sw) we could ask HTC for it with a hint that this would save them from reviving devices on warranty.... Surely needed files would suddenly accidentally appear somewhere.....
[HTC Sensation] ajay83:
Damn, just went back to S-ON no problem.... PHEW!!!
[HTC Sensation] louis47:
I have a Sensation with Custom Rom. I backup the original Rom that came with it.

I have the new Firmware 1.23..... and supercid. When i will go back to Stock and S-on, with the magic words "fastboot oem writesecureflag 3 " do I need to go back first to HBoot 1.17....?

I live in the Netherlands my Sensation is (was) not branded. HTC_E11. I will be prepared if I must goback to s-on and stock.
[HTC Sensation] baric88:
I will never root my phone again it made my blaze unable to be upgraded, new phone I can jack it without root
[HTC Sensation] yozpalang:
First of all I have to say I feel for you guys but if you are willing to sell your bricked sensation pm me with your asking price, I don't know how to fix them I just have a sensation with a broken digitizer, digitizers are around $35 on ebay. I'm in us and looking for T-Mobile version
[HTC Sensation] yozpalang:
so nobody interested?
[HTC Sensation] pirlano:
any news about Sensation boot repair with QPST?
[HTC Sensation] dexter93:
If you can sneek up to a htc repair center and take the files needed, sure
[HTC Sensation] tigger69:
I need a new digitizer for mine, anyone fancy sending me a gift from a dead Sensation? :p
[HTC Sensation] dmcb123:
Im assuming then that nothing in the RUU's can be flashed with QPST?