Related
I've had my Sensation for a week or so now... rebooted it earlier on, and now it's totally dead. Won't power up, won't charge, or anything.
Any recommendations of anything to try that I might not have tried? I've got a good background in this kind of technology, so I've tried the usual stuff - battery removal, leaving plugged in, holding buttons for longer etc...
Is there a trick that anyone's found?
If not, should I go back to '3' to replace it... or should I go to HTC and see if they'll replace with a nice S-OFF unit??
Thoughts please?
volume down and power button together and see if you can get recovery screen up and do a factory reset
Hi Gavin
Sadly it needs something more than that - that was the first thing I tried, thinking it might be software related.
Even tried leaving the battery out overnight before trying again, that didn't work.
What I have found, now, is that if I plug in the charger FIRST, and THEN connect the battery, I get an orange LED. I thought this might mean it is charging, but no, because when I unplug the charger again, the orange LED stays lit, and remains so until the battery is removed again.
I don't recommend trying this yourself, because it does say somewhere in the literature, NOT to apply power, without the battery being in place. I just figured, it's already dead, so it might do something different!
What I'd like to know / find out, is if there's a real "hardware" reset switch/button... my Toshiba TG01 had some hidden PCB pads which would allow different booting modes, etc... somethign like that I think it needs. I'm going to have to get a new one ANYWAY, but it'd be good to know what happened to this one, first!!
Sounds like a hardware issue to me (maybe motherboard failed, that was an issue with all previous HTC devices)
Put it on charge without the battery. Now with a paperclip hit the +- pins for a second. After that unplug it and put battery in and normally charge it. Friend of mine did this with his Sonyericsson and it worked. Otherwise send it back to htc.
Sent from my HTC Sensation Z710e
Ok, I've spoken to HTC, and as it's within the first 28 days, the onus is on 3UK (Hutchinson3G) to replace the handset.
Spent over an hour in store with them this morning, trying various things, and they decided that they would replace the handset. Except they then realised that they won't replace handsets which were from 3 'direct'.
So, I figured, can't hurt to try the 'shorting' method - I would again, out of a background in electronics, say DO NOT TRY THIS METHOD, UNLESS IT'S A LAST RESORT! IT COULD SERIOUSLY DAMAGE THINGS.
Now, instead of a constant orange light, I've got a flashing orange light.
Still no actual operational power though.
Thinking about it
This reminds me of a laptop I used to have - it had a "Quick Boot" feature which relied on stuff in the boot-area of the hard drive. Back then, I had a 'less-than-legitimate' copy of Windows 7, which used a boot-modifier to work as "genuine".
That laptop would, on occasion, refuse to power up for hours, and sometimes days at a time - and I traced that down to it being an issue relating to the loader software in the boot area of the HDD.
I wonder if this is a similar issue on the Sensation - an exception in the "quick boot" that makes it think there's still quick-boot data, even though there isn't, because the battery's been out. It's all hypothetical, but interesting to know how these things tick.
And who knows, maybe 3UK will send me an S-OFF unit in replacement.
i honestly dont know why you would try shorting your phone thats still under warranty. Are you trying not only to fix your phone, but also void your still current warranty?
take it back. get it replaced, and stop trying mcgyver tricks. Its just not needed.
Leigh,
Thanks for your concern for my handset. Personally I'd say having a brand-new, week-old handset to fail completely and spectacularly is 'not needed', either (!) But, really, any of the above actions, which were given to me in good faith, were up to me to use, or not use. I made a calculated decision based on i) the current level of operability of the handset ii) the likelihood of any action taken voiding the warranty iii) the likelihood of my receiving a new handset under said warranty. I hoped I made it clear enough that anyone who would even THINK to consider performing the above procedure would also make such a calculated decision.
I don't know who McGyver is, but you'll notice that I did put a warning in my post stating that others shouldn't try it... chances are it would cause damage to the phone's power management, at the very least, it's cause wear on the voltage regulation side.
That said, there are times when simply shorting devices *can* work as said devices can hold small amounts of charge which can be dissipated with a short, a reverse polarity or otherwise. The cavaets being - a) it's already totally and completely dead, short of it going in flames, it cannot be made worse; b) the shorting (or other action) is momentary - the smallest fraction of a second.
Yes, it's under warranty. Yes, they're going to replace it. If we wanted to go into the whole matter of ethics, *if* I were the manufacturer, and I had proof that someone had done the above steps to their handset, NO, I would not honour the warranty. But I'm not, they don't, the handset already more-than-likely has a mainboard failure, so I was prepared to take the risk.
Eventually, the Service Manual for the device will be released, and this will help with matters of apparent hardware failure. In the meantime, it's a learning curve for everyone, and if I could help that curve at all with my dead handset, in the knowledge that a new one is coming, that's what I hoped to do.
Again, for all clarity, safety, etc. I am not advocating, or recommending the actions detailed above, or ANY other action other than in accordance with the user manual which was provided to you with your device. Do ANY of the above STRICTLY at your own risk, and on your head be it.
If anyone else has any ideas - "McGyver" or otherwise (who is he?!) - that won't obviously cause warranty-replacement issues, I would be happy to try them in the hope of furthering the knowledge of this new device. I'm grateful for any help, and for any chance to increase the small amount of knowledge we already have on this device.
McGyver is a character in an old American TV show from the 80's.He always got into impossible situations and always had some tricks up his sleeve like making a laser out of a package of gum,a paperclip,and a match.
Sent from my HTC Sensation 4G using XDA Premium App
maybe it's the battery
I hat the same problem on my TG01, at the end it came out the Li-ion was all draind and my TG01 would not Charge it anymore.
not eaven in an external Charger
New battery was the only solution.
Maybe it's the same problem you have.
Hi GhostRider
I remember the days of the TG01 - turned out a decent handset, in the end.
I'd hope it's not a faulty battery on a week-old handset - although I don't have another battery to test it with, so I suppose it's possible that it was manufactured as faulty.
My new handset replacement arrives on Tuesday though... but I'll keep checking here to see if anyone wants me to do anything with this one in the mean time.
Had my first Sensation for a week and then it beeped and died just like yours. All I did was swap the battery and plug in the charger. Still nothing. Called TMO and got a replacement.
I think even if you managed to do CPR and get it back up the fact it died in the first place indicates a serious problem. Personally I'd rather have one that's reliable.
I would be excited if my sensation bricked, I've been trying to brick it for a few days. sadly no luck. If it is bricked tmobile atleast will replace it with another, that's atleast another chance at getting s-off.
Mine did what yours did the other day. I thought it was ****ed. I took battery out for 5 and after that put it in and charged for ten minutes. Sadly, it worked fine after that.
samnada said:
Still nothing. Called TMO and got a replacement.
Click to expand...
Click to collapse
s-off i hope?
My replacement is due around 1330h (UK time) today.
I'll let you know the status of the new phone when it comes.
I'd bet a beer it's *STILL* S-ON though...
Here's hoping!!
Ok, my new Sensation has arrived.
PYRAMID PVT SHIP S-ON RL
HBOOT-1.17-0011
eMMC-boot
Jun 2 2011,22:31.39
Oh well. At least there's perma-temp-root for now
I've followed this course to its natural end, however, I appear not to be the only one with the 'dying sensation' problem... so might be good to keep this thread alive?
Cheers all
Hi, a little story about my Sensation....
First if I make some mistakes please excuse me I am an Austrian
So, where i should start....
First I want a S-OFF and it works ok than I installed a the rom manager from the market and the app says i have no root acess ok so I thought it is too stubid for me and I thought it isn required for me to have a Custom Rom or root and so i want to set it to S-OF
ok I set a SuperCID no problem it has worked
after that i have used an Tutorial from a German forum...
yes and in the end of the tut were i should reboot the bootloader the Sensation bricked! Now I know my mistake i didn't haven't flashed the stock rom bevor!
so now the situation is like that:
the phone is dead no reaction and no backlight but only at one time it turned on the backlight as i put in the battery and than i pluged in the usb than the backlight turned off and i can't make the backlight on.... yet
when i plug in the usb the device is shown in the device-manager in windows..
I don't have any plan...I think it's that an it shut go to HTC-Support!
greets Blacki
no one has an idea now the same happend to another user in the german forum
What is shown in device manager of Windows? Please state the exact text shown. Thanks!
there stands "qhsusb_dload"
I've read some sites in the thread with the S-OFF/ON Tutorial and there is also a guy who has the same problems!
greetz Blacki
edit: I think it's totaly bricked I think I will bring it back to my dealer and say that it cames dead out of the box because it's only 3 Days old -.-
Blacki888 said:
there stands "qhsusb_dload"
I've read some sites in the thread with the S-OFF/ON Tutorial and there is also a guy who has the same problems!
greetz Blacki
edit: I think it's totaly bricked I think I will bring it back to my dealer and say that it cames dead out of the box because it's only 3 Days old -.-
Click to expand...
Click to collapse
Briked device...
Mine is bricked too. Sending HTC with the hope that they can reflash everything and it will come back to life.
Return it you will probably get away with it htc will just ref lash and return to you,
So you can't boot into bootloader or recovery? I.e., pull battery, put it back in, and turn on while holding power and volume down?
Rumball said:
So you can't boot into bootloader or recovery? I.e., pull battery, put it back in, and turn on while holding power and volume down?
Click to expand...
Click to collapse
I've tried a hard reset and also to come into the bootloader and the battery stays out over night! No chance
So you guys think I have a good chance to get it fixed for free?
I don't know but it's possible that I get a new device because here in Austria HTC has an service partner so they don't fix the devices by themself so I think HTC will change the device before they must pay the company to fix them! I really don't know I hope it will get fixed for free because it's 4 days old
greetz Blacki
Try, If you can, To Run the RUU. Because what you did semi-bricked your device. Not totally bricked. Just try to turn on IF you can and Run the RUU! This same thing happened to me when i tried to install a custom font!
I've tried it when i run the RUU.exe than it says Error 170 I think it's an connection error and i've tried it to reboot etc. etc. with "adb" but it always say "waiting for device"
Blacki888 said:
there stands "qhsusb_dload"
I've read some sites in the thread with the S-OFF/ON Tutorial and there is also a guy who has the same problems!
greetz Blacki
edit: I think it's totaly bricked I think I will bring it back to my dealer and say that it cames dead out of the box because it's only 3 Days old -.-
Click to expand...
Click to collapse
With all due respect, people like you are the exact reason why we had an encrypted bootloader to begin with....to protect HTC from having to foot the bill for people who want to tinker with their phone, brick it, and then swap it for a new one as if the product was defective (leaving them to eat the cost). Quite frankly, this is ridiculous. It doesn't matter that your phone is 3 or 4 days old. If I buy a car and crash it within the first 3 or 4 days, should the dealership have to swap my car out? You knew the risks of what you were doing when you started the process (if you didn't then that's your fault for not reading), if you weren't willing to accept those risks then you shouldn't have done it. I hope you get your phone working, but if you aren't successful in fixing it, don't try to pass the buck off back to your dealer by lying about the phone coming out of the box dead. Take some responsibility for your actions. Remember it's dishonest actions like these that led to the locked bootloaders to begin with. Next time flash with care and make sure you read and understand what you're going to be doing BEFORE you start.
mysterioustko said:
With all due respect, people like you are the exact reason why we had an encrypted bootloader to begin with....to protect HTC from having to foot the bill for people who want to tinker with their phone, brick it, and then swap it for a new one as if the product was defective (leaving them to eat the cost). Quite frankly, this is ridiculous. It doesn't matter that your phone is 3 or 4 days old. If I buy a car and crash it within the first 3 or 4 days, should the dealership have to swap my car out? You knew the risks of what you were doing when you started the process (if you didn't then that's your fault for not reading), if you weren't willing to accept those risks then you shouldn't have done it. I hope you get your phone working, but if you aren't successful in fixing it, don't try to pass the buck off back to your dealer by lying about the phone coming out of the box dead. Take some responsibility for your actions. Remember it's dishonest actions like these that led to the locked bootloaders to begin with. Next time flash with care and make sure you read and understand what you're going to be doing BEFORE you start.
Click to expand...
Click to collapse
I agree completely. And, this also supports my thread that was removed. People dont need to be doing all this S-OFF and S-ON business for a measly bloatware removal project. If you dont intend to flash some ROMs and KNOW what you are doing in the process, you need to go the temp root method and spend time reading and understanding. That said, Id bet money that someone here can figure out how to fix this phone, so dont go talking about ripping off HTC when you should be waiting for someone here to help you fix the problem.
Matt
is there any way to fix it
There is some sense in the comments about HTC/dealer footing the bill, it's not their fault.
However we all hate insurance companies, don't we? Like the ones who declined to pay for the houses of those poor people in the states who got hit by a hurricane or the ones who insure your car and then should something happen, they want some crazy excess and raise the insurance, never mind it was hit on a parking lot when you weren't even there.
This is very dishonest and you should not do it, however it came to my mind and I decided to share it.
You can fix your phone by getting a phone insurance, then wait for say a while until you can claim from it and then dump the phone in a) the sink, b) bucket with household bleach + hot water or c) a river, wait for an hour and it's ready
freakzone said:
There is some sense in the comments about HTC/dealer footing the bill, it's not their fault.
However we all hate insurance companies, don't we? Like the ones who declined to pay for the houses of those poor people in the states who got hit by a hurricane or the ones who insure your car and then should something happen, they want some crazy excess and raise the insurance, never mind it was hit on a parking lot when you weren't even there.
This is very dishonest and you should not do it, however it came to my mind and I decided to share it.
You can fix your phone by getting a phone insurance, then wait for say a while until you can claim from it and then dump the phone in a) the sink, b) bucket with household bleach + hot water or c) a river, wait for an hour and it's ready
Click to expand...
Click to collapse
What does a device insurance company such as Asurion or SquareTrade have to do with the actions of some home/car insurance company? NONE. This is like saying, since someone in your family did something dishonest, I get to rob your house, because you're all relatives.
It's insurance fraud that causes all of us to pay those higher rates and have to endure so many hassles.
If it's wrong to send it to HTC claiming it came out the box broken, then it's wrong to commit insurance fraud too. This is not a case where the device had a hardware defect that had nothing to do with the bootloader being unlocked. So there's no gray area on this one.
I can't say I've been honest every day of my life, but let's not act like one form of fraud is more noble than another form of fraud.
Let's find a legit way to resolve this issue. And the legit way is, for the device owner to take it to a repair shop and be honest about what happend and pay for help, or send it to HTC and be honest about what happened and pay for service. Whatever fee will be less than the price paid for the Sensation by far I'm sure.
Im willing to bet that the fee to repair it from HTC will be less than the insurance + deductible from an insurance company.
Matt
It was intended to be a joke, thus the smiley, sorry guys
I am generally against crime, including insurance fraud
mrg02d said:
Im willing to bet that the fee to repair it from HTC will be less than the insurance + deductible from an insurance company.
Matt
Click to expand...
Click to collapse
I agree, it probably will be cheaper to just be straight up with HTC and pay their fee.
Darnell_Chat_TN said:
I agree, it probably will be cheaper to just be straight up with HTC and pay their fee.
Click to expand...
Click to collapse
i am sure they will find out so yeah
Turning on my phone today and it was stuck on the HTC logo. After 20 mins, I pulled the battery (all I could do) now when I try and start it, it just vibrates 5-8 times and refuses to start.
Is there anyway to sort this, or should I return? The phone is only 6 weeks old, so I can get my money back on it.
If you haven't modified the phone (S-Off, root etc) then I would just take it back to the shop and ask for a replacement. After only 6 weeks they should still take responsibility for it and not make you go via the network provider for a replacement.
Yep, as long as you haven't voided the warranty (root etc)
They'll be more than happy to replace it.
Good luck with that.
The quality of these phones is really quite bad. Mine was also one with a gap at the top of the screen..
That, as well as the emmc problem means I wont be buying another Desire S, or HTC phone.
even if u voided the warranty,the emmc cip is broken and they canot know anything you done on it...
think in a positive way..when you bricked your phone accidentally,with working recovery,but you cannot do anything,you can jsut try your best to fry the emmc chips by keep on pulling battery,so that it'll be covered under warranty
tcchuin said:
even if u voided the warranty,the emmc cip is broken and they canot know anything you done on it...
think in a positive way..when you bricked your phone accidentally,with working recovery,but you cannot do anything,you can jsut try your best to fry the emmc chips by keep on pulling battery,so that it'll be covered under warranty
Click to expand...
Click to collapse
Great, never knew that
Thought it would be the end if that happened
Sent from my HTC Desire S using xda premium
Phone info: rooted, stock, s-off, CWM 5.0.2.7, BusyBox 1.17.1, ES File Explorer
In a nutshell, my phone's display died after a bit of condensation appeared under the glass. I have no idea how the moisture happened, as I've been babying this phone since my 1/7 purchase, and I haven't dunked the phone in water or exposed it to steam. Had it tucked in an inside coat pocket while going for a walk, discovered condensation spots later that evening (and no, I don't sweat like a horse, either). Screen began flickering over next four days, requiring brightness to be turned up to max, but otherwise operated normally--until day five, when the display went out completely. Liquid indicator under the battery is pure white, btw.
So, after discussion with HTC Warranty and Repair, my phone will be shipped off to be fixed, hopefully, under warranty, and I won't get dinged for out-of-warranty repair since this is a moisture issue (albeit one I'm baffled as to the cause).
What I'd like to know is what to expect upon return of my repaired phone. I know the HTC tech's will likely be wiping all data, and this means I'll have to reroot, correct? I have my most recent Nandroid backup on both my PC and my SD card, so I can restore to that, but I wasn't clear about the rerooting end of things.
Any experiences from others who have gone through the warranty repair process would be appreciated.
Many Thanks --
--
King Cheetah
Well I sent my 3G Slide in to get the camera lens cover and keyboard fixed. I had the old hboot and flashed back to stock with s=on. They fixed the 2 issues and updated my phone to the Froyo OTA with the new hboot.
It isn't unrealistic to think the same would happen. So the Fabulous work the guys in the dev forum will be more appreciated once the hboot issue is solved.
Sent from my myTouch_4G_Slide using xda premium
Actually, I just got back my phone from repair. hboot was 1.44.007 the one that is hackable.
It's essentially a roll of dice right now, because the OTA isn't in full effect yet. Maybe you can make a special request that they don't restore your phone (although that's usually the first thing they do) or tell them that you don't want the latest OTA
That pretty much answers my question--I'll have to go through the process once more for root once I get it back.
As far as I've been able to glean from the HTC and T-Mobile forums, the OTA is still on hold due to error troubleshooting, so I doubt that will be applied until all the bugs have been squashed. In fact, there's no word that the update will be ready this month, so I'm fairly confident the hboot will still be 1.44.007.
Thanks for the replies --
--
King Cheetah
Yea - I sent one in to be serviced and got it back as it went out (fixed though) and still had s-off 1.44.0007 hboot.
I restored everything else to stock retail launch before sending it in.
They told me on the phone before I shipped it that if they chose not to repair i'd get charged. If there was evidence of tampering it was their option to not do anything to it.
I was also told that it would be flashed to their current software as the last thing before it left the factory.
I imagine it's up to the tech to decide if they want to work on it if it comes in with s-off - but now we have a guide for how to get s-on so this should no longer be a concern - it's in dev here.
Also, my theory was that the update being on hold was why I got it back with the software I sent it out on - and seems to be what everyone else thinks too.
Hello,
I recently got an insurance replacement of my phone, and this one seems to have an odd issue and I'm not sure if its software or hardware. Basically, sometimes, (frequently) when I go to unlock the phone, I will swipe my finger to unlock and feel the haptic feedback and such, and if its bright I can see the LCD on, but the back light will take an extra 2 or 3 seconds to actually turn on. There's also a bright area in the screen, not too major, but noticeable when reading text on a white screen. Should I contact T-Mobile for a replacement? My phone is still in the 1 year warranty. Could this be a software thing? I'm running virtuous Inquisition 4.0.2. I don't remember this happening on my phone prior to the insurance replacement. My old display was the acer, and this one is the sharp, if that makes any difference.
Sent from my HTC Sensation Z710e using XDA
Bump? Should I warranty this?
Sent from my HTC Sensation Z710e using XDA
I think you should try to warranty it.
I'm also running Virtuous 4.0.2 and never had similar issue.
But before that try to test other ROMs - do they have similar issues?
I tthink the bright spot may have actually been caused by my phone overheating overnight a few weeks ago. Was at like 170f before I woke up and turned it off. The bright spot is right near the sim card slot which is what was hottest, where the processor must be. I think I'll just warranty it, T-Mobile tends to be pretty easy going with warranty returns.
I called tmobile, told them my phone overheated for no reason overnight (even though it was probably my fault) and that now there's a screen defect, they didn't even put up a fight, took like 5 minutes to get a replacement out of them. So easy. Should I unroot the phone and go back to s-on and all of that stuff? Do they check for that? Or do they just check for water damage and cracked screens, etc.? I'd hate for them to claim it was out of the warranty terms. I just don't want to brick my phone returning to s-on, which I know is a bigger risk than when going s-off.