Database Info

[Q] HELP!!: My Phone Bricked Itself!!

Hi all,
As the title says :'( I flashed the new Android Revolution HD 3.6.2 ROM (updated from 3.6.0) and the recommended radio yesterday. Everything went fine and the phone was smooth as ever.
However, while I was playing robo defence today (played for about 5 mins) the phone suddenly shut down, rebooted itself to the startup screen (HTC Logo on a white screen) then when to a black screen and then repeated the process. This happened about 5 times after which I pulled the battery and then tried to restart the phone.
Now the phone won't power on at all!
- Nothing happens when I press the power button.
- Tried vol + power: nothing.
- Took the battery out, waited 20min, tried the above again: nothing
- Plugged it into my pc: nothing i.e. no LED light either
- Plugged it into a wall charger: nothing i.e. no LED light either
What I don't understand is how come my phone has died when I was not in the middle of flashing anything? Has my phone actually bricked itself?
any help would really be appreciated!
Thanks
Is there anything I can do via adb? (I don't know how to use it that well)

Keep trying to boot into vol+down and power
Leave phone on charger and try the button combo that happened with my mytouch when I had one and that worked.
Sent from my HTC Sensation XE with Beats Audio

Remove SD card, boot in recovery, clear cache / dalvik.
If you can boot of cource.

charlieb620 said:
Keep trying to boot into vol+down and power
Leave phone on charger and try the button combo that happened with my mytouch when I had one and that worked.
Sent from my HTC Sensation XE with Beats Audio
Click to expand...
Click to collapse
I've tried that. Still no luck No LED charging light either
septix said:
Remove SD card, boot in recovery, clear cache / dalvik.
If you can boot of cource.
Click to expand...
Click to collapse
No I can't boot at all. Tried booting without the SD card and no luck.
Is it even possible from for a phone to brick itself? Because after I flashed the ROM everything worked fine. It was only when I was playing a game that it died.
Could it be a battery problem? It would explain why no charging light is showing up

charge it via the original charger, hold on for a little while and try booting it up
i've seen it happen to mine once, i panicked just like you.

Before I s-off'ed or rooted I had this happen to my phone. It took a battery pull and then a long hold of the power button to get it to boot. I freaked thinking it was a dud (I had just gotten the phone).
If nothing works, it may be a hardware failure that had nothing to do with rooting. I would go for a warranty exchange. If YOU cannot get it to boot, neither will they without re-flashing the phone the hardcore way. (I believe its called a JTAG?). They will never know you rooted. They will just try a quick boot, see it doesnt, and then open it up to re-flash the thing via factory methods.
Matt

Would have to say its prob an fault with the handset as i am running the same setup as you and also playing robo defence and i play it for about 45 mins at a time with no issues at all .

awesam said:
charge it via the original charger, hold on for a little while and try booting it up
i've seen it happen to mine once, i panicked just like you.
Click to expand...
Click to collapse
Going to try that tonight. Its my last resort because i've exhausted every other option.
Diydude said:
Would have to say its prob an fault with the handset as i am running the same setup as you and also playing robo defence and i play it for about 45 mins at a time with no issues at all .
Click to expand...
Click to collapse
LOL...robo defence love! Thinking about it...it could be a handset issue. When I use the play robo defence on ARHD 3.6.0 ROM the phone would always die or go into a boot loop. But now its just dead.

Any news?
Sent from my Sensation using xda premium

would it be ground problem? check all the contact points
---------- Post added at 08:53 PM ---------- Previous post was at 08:45 PM ----------
would it be ground problem? check all the contact points hope it'll help

Just to update you guys:
I tried everything that has been suggested on this thread and had no luck.
I've sent off my phone to HTC today to hopefully get it fixed. we'll see how it turns out. They said it should be done and on the way back in 7 days. Will post if I get new info or updates

Installing the same Rom I had the same issue. New phone is on the way so I thought what harm could it do now. I tried everything u did. What worked was pulling battery out plug the wall charger in and then hold the power and vol down button then slip in battery and it went into recovery . I tried a reg reboot and nothing. So I pulled sd card out and put into another phone then downloaded another Rom. Put sd card back in shot phone and got back into recovery and flashed a diff Rom and it worked. The phone over heating is bad tho so will leave it be till New phone comes in.

I've had the no boot problem after messing with my partition tables, took it to my carrier, and they fixed it. Hopefully, your phone is so messed up that they can't read that it's been rooted (or hope that they don't care)

Did you install any Kernels with GPU Overclocking for example? Or was it only the normal ROM?

What recovery are you using?

CrazyCharlie said:
What recovery are you using?
Click to expand...
Click to collapse
Clockwork. Can't remember the version
xotox83 said:
Did you install any Kernels with GPU Overclocking for example? Or was it only the normal ROM?
Click to expand...
Click to collapse
No I didn't. Just stock ROM and the standard kernel that came with it. No overclocking either. I mentioned this before - i use to have boot loops every time i played robo defence - even with ARHD 3.5.x. so I reckon it was a hardware issue that eventually kicked the bucket when I moved to 3.6
Matt1408 said:
I've had the no boot problem after messing with my partition tables, took it to my carrier, and they fixed it. Hopefully, your phone is so messed up that they can't read that it's been rooted (or hope that they don't care)
Click to expand...
Click to collapse
Yea...i'm hoping exactly that! its being repaired atm. finger's crossed!

Have u try to connect ur phone to ur pc see if it detected? If you connect ur phone to ur pc and it show up something like can't find the driver that mean is ur phone got hardware issue just call HTC they will fix for you.

Johnsonyc said:
Have u try to connect ur phone to ur pc see if it detected? If you connect ur phone to ur pc and it show up something like can't find the driver that mean is ur phone got hardware issue just call HTC they will fix for you.
Click to expand...
Click to collapse
Yep tried that. My PC didn't detect it - there was no response from either device. Tried to force my PC to detect all connected usb devices and no luck.

My Phone Lives!
Hi guys,
Just to update everyone: I got my phone back yesterday and it's working again!!
Although it has been returned to stock again. According to the letter that came with my phone I think I've got a new main board. This is what it says:
Parts Replaced: PCBA-Main Board with SKU_ID, HTC Global, QSD8260 UMT
Anyone know what it means for sure?
I guess there is hope if a phone bricks itself entirely! and HTC didn't even bother asking any questions i.e. if I rooted my phone or anything. All they asked me was did I try to charge the phone via the main charger, did I take the battery out etc.

Good for you dude. I'm happy it worked out fine for you! And thanks for the update, good to know how they handle things over there.
Sent from my Sensation using xda premium

HTC Sensation Bricked? Suddenly can't turn on anymore..

Hi guys,
I've run into some problems, I installed Android Revolution HD 6.5 two days ago. Everything worked like a charm, now I shutted down my phone to go in recovery, sadly enough my phone won't reboot, does not charge nor does it respond to my desperate pushes on the power button. Anyone experienced anything like this?
Worth mentioning also is that the battery was 80+% charged.. So it would seem strange to me that this would anything to do with eventual dead battery.
Just to be clear: hadn't installed anything, nothing less, nothing more.
If I could just get acces to bootloader through usb or anything like this.
I fear that there is someting seriously wrong here?
What are you guys thinking? Any possible solutions?

Hi,
The same thing more or less happened to me.
My phone went dead one night and wouldnt turn on, charge or connect with the PC. I had already arranged a repair with HTC for another issue and so I sent it off to them and a few days later I now have it back and it is working fine so far.
They replaced the mainboard and a few other bits and pieces all under warranty.
I hope you get your phone fixed and sorted asap.
Mustak

mustakg said:
Hi,
The same thing more or less happened to me.
My phone went dead one night and wouldnt turn on, charge or connect with the PC. I had already arranged a repair with HTC for another issue and so I sent it off to them and a few days later I now have it back and it is working fine so far.
They replaced the mainboard and a few other bits and pieces all under warranty.
I hope you get your phone fixed and sorted asap.
Mustak
Click to expand...
Click to collapse
Did you root it or anything like that? It really seems like an hardware issue.. Thanks for your reply also btw.

TP-Power said:
Hi guys,
I've run into some problems, I installed Android Revolution HD 6.5 two days ago. Everything worked like a charm, now I shutted down my phone to go in recovery, sadly enough my phone won't reboot, does not charge nor does it respond to my desperate pushes on the power button. Anyone experienced anything like this?
Worth mentioning also is that the battery was 80+% charged.. So it would seem strange to me that this would anything to do with eventual dead battery.
Just to be clear: hadn't installed anything, nothing less, nothing more.
If I could just get acces to bootloader through usb or anything like this.
I fear that there is someting seriously wrong here?
What are you guys thinking? Any possible solutions?
Click to expand...
Click to collapse
Hi,
Is there any chance the battery pins could be damaged or bent?
Is there any way for you to get hold of another battery(from a shop or friend) and try that?

I will test the battery in the laboratory tomorrow.. I've read you should get a minimum of 3.6V or something like that? Curious to see what has caused this problem. Do you think htc would see I flashed a custom rom on it if I send it to repair?

TP-Power said:
I will test the battery in the laboratory tomorrow.. I've read you should get a minimum of 3.6V or something like that? Curious to see what has caused this problem. Do you think htc would see I flashed a custom rom on it if I send it to repair?
Click to expand...
Click to collapse
Hi,
That is why i suggest a different battery.
If they can switch it on,they will see the s-off.
If they cannot,it does not matter.

malybru said:
Hi,
That is why i suggest a different battery.
If they can switch it on,they will see the s-off.
If they cannot,it does not matter.
Click to expand...
Click to collapse
They don't use a JTAG unit or anything like that to see what has went wrong than I presume? Well, first thing I'll do is test it right away at the laboratory. I will post the result in the evening.

TP-Power said:
Did you root it or anything like that? It really seems like an hardware issue.. Thanks for your reply also btw.
Click to expand...
Click to collapse
My sensation was rooted and had a custom ROM on, but I was preparing to send the phone back in when it got bricked. I had managed to install stock rom and do S-on but the phone had an unlocked bootloader using HTC dev website, so I was worried they wouldnt do the repair.
As it happens they did all the work under warranty and didnt say/ mention having unlocked bootloader. It has come back locked though.

Was anybody able to find a fix for this?
My sensation 4g has basically the same problem. After rooting and installing ICS it worked fine for a few days then it ceased booting or responding to a charger (no LED response). I was able to turn on the phone again by letting it sit for a while but no luck lately. I'm wondering if my phone is bricked?
When I press the power button the screen stays black with lights on (no LED).
I can't get into bootloader and the phone is not detected by ADB, I tried the unbricking project thread by Dexter, however my phone is not detected by linux. On windows, i did get it to detect as qhsusb_dload.
Any thoughts would be helpful!
Thanks

asuen06 said:
Was anybody able to find a fix for this?
My sensation 4g has basically the same problem. After rooting and installing ICS it worked fine for a few days then it ceased booting or responding to a charger (no LED response). I was able to turn on the phone again by letting it sit for a while but no luck lately. I'm wondering if my phone is bricked?
When I press the power button the screen stays black with lights on (no LED).
I can't get into bootloader and the phone is not detected by ADB, I tried the unbricking project thread by Dexter, however my phone is not detected by linux. On windows, i did get it to detect as qhsusb_dload.
Any thoughts would be helpful!
Thanks
Click to expand...
Click to collapse
If your getting QHSUSB DLOAD I'm so sorry to tell you as I believe your device is HARD BRICKED. You can try jtag. If you search there are several companies who will jtag. I'm wishing you the best and I'm sorry about your device.
Sent from my HTC Sensation 4G using xda premium

I had to return my HTC Sensation to the repair center. Apparently the motherboard just fried. I got a new motherboard and just S-OFFed the phone again. Very weird problem though. As has been said in this post earlier, if they can't turn on the device they won't see it is S-OFFed and your warranty will apply.

[Q] Unpleasantness... Bricked phone?

So, while I'm no expert I'm not new to rooting and flashing. Did it quite a bit on my older Droid Inc 1, and have performed a few on my new SG3.
I have 3 backed up ROMs on my SD, Synergy, Beans and CM10. I was running Synergy and decided to give CM10 another shot to see if I could figure out what was killing NFC. So, flashed it up with ROM Manager (Used Odin previously) and everything went swimmingly. ROM was running, NFC was working, all my apps were reinstalled, no problems.....
Decided to see if I could get Wallet working on this install, so flashed it in, made the changes to build.prop and rebooted.
Heeerreeee's where the trouble started. Part way through the reboot the phone just shut down. Completely. 100%. Dead.
I had 87% battery when I started so it 'shouldn't be a battery problem. No power, no LED when I plug in the charger, no vol-up, home, power to get into recovery.
One interesting thing did happen while I was trying to get the phone up, I removed the battery for a bit, and plugged the USB cable in and got a red charging light. Put the battery back in, light still there. 1 minute later, light goes off and still nothing happening with the phone at all.
Anyone have any ideas beyond all the stuff I've given a shot to?

Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app

nexus995743 said:
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Unfortunately not. Only thing that seems to show up is in the device manager, a QHSUSB_DLOAD device that's banged.

Hmmmm
Sent from my Nexus S 4G using xda app-developers app

nexus995743 said:
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Well, I called Verizon and they've shipped me a replacement. I guess throwing all my bit and pieces into a new main body should work fine...

Oh no. Another one sending a phone back because of rooting. That's why they lock bootloaders.
Sent from my Galaxy Nexus using xda app-developers app

+1

Have you tried borrowing someone's battery to see if you can also least boot? I have four samsung batteries for the S3 and would consider sending it to you before getting a replacement. I think the cost of a battery is $3 on Amazon.
Sent from my SCH-I535 using xda premium

The reasons were different but i had the same thing happen to me, my phone wouldn't boot, wouldn't show up in the computer. Nothing, i tried my wife's battery, no change there either. I left it on the charger overnight and tried turning it on in the morning and after messing with it it came back on. Haven't had an issue since. Don't know what caused it, the phone just freaked out, turned off and wouldn't turn back on.
You can also try the resistor trick to see if that will bring your phone back. Here is a cheap way to do it.
http://hackaday.com/2012/09/03/saving-a-bricked-phone-with-a-pencil-lead/ Otherwise you can go to radio shack and pick up a resistor.
If Verizon sends you your phone back cause you messed with it, there is a brick repair service for like $60 bucks PM for the link if it comes to that.

Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app

nexus995743 said:
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
hehe.. I can't say I was pleased with having to go that route, (can't stand being defeated by electronics) but all in all I can't imagine a simple software change causing the entire unit to just go dead. Not booting properly, or locking up and such, sure... but not just dead.
By this morning I had tried another battery (a friend has an SG3 also) to no effect, but I didn't try leaving it plugged in overnight. I did check the battery with an external charger I have and it was showing fully charged....
So, I'll get a replacement and stay away from CM10 at the very least.
**ihavenewnike - Not sure why you're on an android developers forum really...

Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it.
Ahhhh... It's just like it never left. :victory:

keno1964 said:
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it. . .
Click to expand...
Click to collapse
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest

ooofest said:
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
Click to expand...
Click to collapse
Don't like you.......

Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.

tekrhino said:
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
Click to expand...
Click to collapse
I have looked into those and will most likely make one very soon. (I think I have everything I'd need, just may need to cobble some resistors together).
Couple of things I noticed throughout this 'process', regarding the CM10 (9-15 nightly) ROM, NFC and google wallet....
At first install of CM10 I noticed that NFC was active and working normally. It could read my tags without issue. After Wallet was installed though, NFC disappeared. It wasn't just disabled, it simply wasn't there any more. It was after noticing this that I decided to reboot, at which point my original problem started.
The reboot never came close to completing though, it shut down before it actually made it to the 'boot' phase, as in, while it was shutting down.
The actual cause of the power off is still a mystery to me, as I can't see a simple app change causing hardware failure.

So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?

AB_ said:
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
Click to expand...
Click to collapse
I told them what happened, just left out a few bits of info.
"I rebooted it, and it never came back on." and that was that.

Nice.
I should have gone that method, but ended up paying for the repair service from MobileTechVideos

A friend has the qhsusb-dload showing up as well.. phone won't turn on.. flashed a bad kernel or rom I forget which.. red light comes on.. that's it.. its a Verizon i535 .. tried the resistor jig and nothing happens.. any ideas to fix?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Guess he had aokp rom then flashed neak kernel and that's when it died..

[Q] Sidekick 4g Bootloop Please Help!!!

I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help

Use heimdall n hold the volume buttons n enable flash bootlaoders
Sent from my SGH-T959V using xda app-developers app

@karose465 How old is the phone? If less than a year (doubtful), it should still be under warranty. Or you may be eligible for upgrade pricing: Fore example, "Customers with a Classic plan (two-year contract) are eligible for our lowest upgrade price on a new phone when at least 22 months have passed since their last phone upgrade. A new two-year contract is required to take advantage of best upgrade pricing. Of course, you can always upgrade a phone at any time, regardless of how many months have passed since your contract began."
For more info on Heimdall, just Google Heimdall Android.

Anyone with a sidekick contract ends earliest next march..

karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.

RicAndroid said:
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
Click to expand...
Click to collapse
I think for him and myself, the biggest problem is being unable to get the phone to stay in download mode. For some reason, the battery won't charge and the phone itself continously turns off and on when plugged in. So the charge isn't holding, therefore nothing will stay on/open.

Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium

gamingwiz said:
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
I did some forum searching and found this. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=1477838

Thanks ill check into that
Sent from my HTC Glacier using xda premium

karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
---------- Post added at 04:33 PM ---------- Previous post was at 03:41 PM ----------
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576

Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium

EpicLordPhone said:
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.

Power Button Repair relating to Boot Loop
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
my Sidekick 4G is very old and just now went into bootloop... i googled the word and came across this forum.
As quoted above by previous poster that a power button repair was needed... I figured that I had nothing to lose, it being so old, I smashed the crap out of the Sidekick 4G on its power button. Lo and Behold, it booted into the system successfully.
SO... if no one has any qualms about smashing the crap out of their power button... give it a shot. It worked for me.

MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app

EpicLordPhone said:
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app

immorality said:
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Hmmm thanks, I might just try that!
Sent from my Amazon Kindle Fire2 using xda app-developers app

Mines stuck in a boot loop too.
I don't know if my Sidekicks problem is related to this or not. I rooted it and flashed it over to Glorious Overdose v5 on May 22nd this year and it's been running great. At least it was until last Friday, Sep 13. I was having trouble connecting to the WiFi at my house so I rebooted the phone. When it started to come back up a female voice started saying, "VooDoo lagfix has been disabled." "Converting /data and /system partitions." "Conversion time estimated 10 minutes."
I let it do it's thing and that's all it's been doing all weekend. I can get into recovery mode, I've tried restoring the phone from my backup with no success. I've even tried running through the process of setting up GOv5 again and it says it's successful, but the phone never boots up. It just stays in the same blasted bootloop and saying the same things over and over again about VooDoo. I've checked the VooDoo logs and there is an error file for the 13th and the logs following say "conversion." Can someone point me in the right direction as to what I can do to get my phone working again? Everything I've tried to research so far hasn't worked.

v5 hold both volume button, the track button and power button. Should put you into recovery mode. If not, you will have to put phone into download mode. You do this by taking out battery, then pluging into computer. When you reinsert battery hold volume down and power, if I remember correctly, and your download screen should come up. From your cp manually unroot it. Then it should be fixed, and just reroot it. I hope this was helpful
Sent from my SGH-T839 using xda app-developers app

No idea what I'm doing, precisely, but...
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.

LathyrusRoots said:
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
Click to expand...
Click to collapse
And almost a year later I log in and see this. Your most welcome. I haven't been working on phones for awhile but if I remember right, some models can be powered on by plugging the phone into a power source and when the phone vibrates or has a sign of life unplugging the unit. Some cables don't work and sometimes doing this via a computer can power up a device. Other than that, the other more dangerous way is to short out the pins on the bottom of the unit. I don't remember the pins but you can google a charge port diagram to help. I don't recommend doing this unless you have absolutely no other choice. Incidentally, this is why a phone will power itself on when a battery is put in and no other button is touched. The port is wet and corrosion has caused a link on the power pin and believe its pin 3. A simple cleaning with 90%+ rubbing alcohol solution will fix if cleaned quick enough.

[Q] HTC ONE S Bricked

Hey Guys,
a friend of mine just bricked his HTC-OneS and I'm here to help him get it back to life
He installed the latest PacMan Rom and everything was awesome.
All over sudden the Phone didn't boot up anymore.
It can be charged via USB, so maybe one can do something over USB
Windows-PC doesn't recognize the Phone he says...
As far as I remember its an HTC One s ville c2 (is there anything like this)
Due to the Fact that I'm a Motorola User, I have no idea where to start trying to recover his Phone...
Please Help me do it

do you know how to use some adb/fastboot commands? run fastboot oem getcid in the bootloader.
hold down volume down and power to go into the bootloader.

I would try to get into the bootloader first. That would provide a gateway to possibly fixing his (or her) phone.

Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app

I don't think I've ever seen a tool like that. I think the best bet would be to get into recovery, mount and try to flash a new rom (C2 roms in this case).

esok44 said:
Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Yes, go to androidruu.com, look for villec2 and click on it. The latest RUU should work unless he is carrier branded. Then you will need to use a carrier RUU.

Got hands on his phone and it doesnt do anything...
No bootloader nothing.
Only thing that happens is that it recognizes its on a wallplug...
Sent from my XT925 using xda app-developers app

Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?

esok44 said:
Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?
Click to expand...
Click to collapse
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.

tivofool said:
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.
Click to expand...
Click to collapse
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?

esok44 said:
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?
Click to expand...
Click to collapse
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.

tivofool said:
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.
Click to expand...
Click to collapse
Thank you dude, will give it back to him and tell him, that he should send the phone back, cause it seems like this is a common problem
Greetz Esok