Just want to say I have encountered exactly this issue today.
Running Virtuous Inquisition 4.0.2 and the phone was running fine till I took battery out to change SIM. Now even the Orange LED light doesn't come up when its connected to the power source.
Help!
I've been running the Virtuous Inquisition ROM for some time now and never had a problem with it.
Steps that I followed were:
1. Upgrade to 3.32 firmware
2. Clear cache and performed a complete wipe
3. Flashed the 4.0.2 ROM
4. Restored my apps from TI Backup. (No, I did not restore any system data)
Everything just worked fine for a few minutes until I needed to change the SIM Card, for which I opened the phone up and left it like that for 20 minutes. Phone did not power up after that.
Running Virtuous Inquisition 4.0.2 and the phone was running fine till I took battery out to change SIM. Now even the Orange LED light doesn't come up when its connected to the power source.
Help!
I've been running the Virtuous Inquisition ROM for some time now and never had a problem with it.
Steps that I followed were:
1. Upgrade to 3.32 firmware
2. Clear cache and performed a complete wipe
3. Flashed the 4.0.2 ROM
4. Restored my apps from TI Backup. (No, I did not restore any system data)
Everything just worked fine for a few minutes until I needed to change the SIM Card, for which I opened the phone up and left it like that for 20 minutes. Phone did not power up after that.
Last edited:
I think there is a mod of sticking some foil or paper in between the battery and the back. Its in the Dev thread. Some have responded saying they have had success with the phone not dying or battery not draining. Not sure why it works. Hope that might help.
Sent from my HTC Sensation Z710e using Tapatalk
Sent from my HTC Sensation Z710e using Tapatalk
its not working for me because its needed to show QHSUSB DOWNLOAD mode when i plugged it in to pc . but the problem is its not showing any thing
check whther its dead or not, theres a irc chat #unbrick ask help from them or contact dexter93
the unbrick thread will only support the s-on bricks (at least at first).
have you guys tried contacting the rom chiefs to see if they can pin-point the issue(s)? it's very strange that so many people are having the qhsusb issues from the same rom.
have you guys tried contacting the rom chiefs to see if they can pin-point the issue(s)? it's very strange that so many people are having the qhsusb issues from the same rom.
I think those with qhsusb issues are different than those of us when the phone is completely dead....nothing is recognized on the computer....doesn't matter how long you charge....and it happened when the phone was 100% charged.
Anyway...just an update...my phone was sent back to HTC..looks like they've fixed it and is on the way back to me. They never contacted me saying it's not repaired under warranty....so not sure if they fixed it or just gave me a replacement
Now the question is...should I try to root it again or jsut stick with Stock and wait for the official update from T-mobile next month!
Anyway...just an update...my phone was sent back to HTC..looks like they've fixed it and is on the way back to me. They never contacted me saying it's not repaired under warranty....so not sure if they fixed it or just gave me a replacement
Now the question is...should I try to root it again or jsut stick with Stock and wait for the official update from T-mobile next month!
Wait surely if this happened on such a largely used rom, we need to find out what is causing this problem?
Sent from my HTC Sensation Z710e using XDA
Sent from my HTC Sensation Z710e using XDA
guys,
Another post this morning
Looks like he was running some form of ARHD, and his phone died......
Starting to get a little strange and uncomfortable.
Take a look:
http://forum.xda-developers.com/showthread.php?t=1642317
Another post this morning
Looks like he was running some form of ARHD, and his phone died......
Starting to get a little strange and uncomfortable.
Take a look:
http://forum.xda-developers.com/showthread.php?t=1642317
Yes...something is happening..and no one seem to be pointing that out to the ROM devs...Mine was running Revolutin HD 6.2.2 when it happened. Was ok until then..not sure if it's related.
Maybe you could try this
http://www.youtube.com/watch?v=_Pcxt6nKI10
and then continue with the unbricking process if possible.
http://www.youtube.com/watch?v=_Pcxt6nKI10
and then continue with the unbricking process if possible.
But I think this only works if you get the qusb load error. If your phone is completely dead I am not sure....mine just got a new motherboard when it got back to HTC.
The question is....what's causing this? Just a random hardware issue or is it related to what we're putting onto the phone?
The question is....what's causing this? Just a random hardware issue or is it related to what we're putting onto the phone?
Hey guys, I'm new to xda but coming from android-hilfe.de board i have little experience with Android.
I got a sensation XE with updated first to Elegancia ICS with Sense 4 with bricked kernel, then changed to coindroid with bricked kernel. Now using the faux kernel.
My phone data:
Android 4.0.4
Sense 4.0
Coindroid 1.5.1
Faux v005
I got a heavy issue:
Loving the feature sweep2wake I chose the bricked kernel. shortly after using this one my phone frozes quite often after regular use. I dont know what kind of problem i had. i sticked to s2w and flashed faux v006b6 kernel - but there i had the same issue. on the other board i was instructed to disable s2w - so i just flashed the v005 version. some time after i realized using it normally my phone looked like it frozes, but still respond. it looks like my display stopped kinda working but the other hardware works.
Anyone knows about this issue and can provide help?
I'd highly appreciate if you guys could help me
THX
I got a sensation XE with updated first to Elegancia ICS with Sense 4 with bricked kernel, then changed to coindroid with bricked kernel. Now using the faux kernel.
My phone data:
Android 4.0.4
Sense 4.0
Coindroid 1.5.1
Faux v005
I got a heavy issue:
Loving the feature sweep2wake I chose the bricked kernel. shortly after using this one my phone frozes quite often after regular use. I dont know what kind of problem i had. i sticked to s2w and flashed faux v006b6 kernel - but there i had the same issue. on the other board i was instructed to disable s2w - so i just flashed the v005 version. some time after i realized using it normally my phone looked like it frozes, but still respond. it looks like my display stopped kinda working but the other hardware works.
Anyone knows about this issue and can provide help?
I'd highly appreciate if you guys could help me
THX