Database Info

Sensation Display Problem...

Hi Frends ...
I have gone through many issues ..but seems that ... I'm the lukiest to have this problem for first time ...
Iam using the "[ROM][29 OCT]Pyramid3D v8.2.1 XE | 2.3.4 | SUPER Fast!! | Bricked v1.45 | STABLE" rom...
I changed my firmware to this a week ago today after noon i had a strange problem ... like the bottom part of my screen started flikering ... I restarted my phone couple of times but did not solve my issue ...
So i Used the incremental update of the above mentioned rom ...
after that my phone restarted and same issue was there ....
after some time .. the whole display started to flicker the touch works fine ..
Iam not able to understand any thing on the screen ... but as iknow the locations of button on screen i can attend the call etc ...
iam not able to enter the recovery mode ...
some body please help ...
any other methods from pc to enter the recovery mode ...
Hoping for a solution ...
Thanks Mates ...

oh thats really sad to hear off i hope some of our admins will figure out some way......meantime lemme dig for you

phoenix08 said:
oh thats really sad to hear off i hope some of our admins will figure out some way......meantime lemme dig for you
Click to expand...
Click to collapse
Thanks a lot ... Iam trying Android flasher now ... noting positive yet ...

By the looks of it, it seems like a GPU failure. This also isn't the first display failure we've seen, and the second one in recent memory stating that it happened after they flash the bricked kernel.
I don't want to be paranoid that there's a bug somewhere in the bricked kernel, but it is possible. I'm on that ROM now, I haven't noticed any problems so far, but I likely won't be on it long.

mattbutsko said:
By the looks of it, it seems like a GPU failure. This also isn't the first display failure we've seen, and the second one in recent memory stating that it happened after they flash the bricked kernel.
I don't want to be paranoid that there's a bug somewhere in the bricked kernel, but it is possible. I'm on that ROM now, I haven't noticed any problems so far, but I likely won't be on it long.
Click to expand...
Click to collapse
tHANKS FOR THE INFO...
Can u please tell me ... how to fix ..this ...
Iam really stuck with out the phone ...
Thank Yo ...

http://www.htcsensationforum.com/troubleshooting-htc-sensation-4g/screen-problem-10793/
I found ... a Similar problem in this thread ...

http://www.youtube.com/watch?v=i_H0VhszfRE
This is exactly my problem ..is this software issue or ... hardware issue ...

It's likely a hardware problem, and unfortunately cannot be repaired by any of us. It'll have to be sent in to HTC and will likely cost 150 to 200 USD to be replaced - just estimating off of many similar threads on various forums.
Please keep in mind that I'm not blaming the Bricked Kernel, in my last post I was just suggesting that it could be a culprit, but GPU failure has happened to non-rooted Sensations as well.
There's actually a good chance it's the display too. I believe GPU failure is instant, something happens to it and baboom it's down for the count. You said it flickered increasingly until it's totally unusable, so it may not be GPU failure, but I don't really know for sure.
So, it's either hardware related, or the bricked kernels low-level GPU driver is dicked. You might be able to actually reboot into the bootloader, reboot into the recovery, and actually flash a new ROM/kernel if it's just the kernel. As in, doing so without using the display, because the rest of the phone still works. However, if it's hardware related, you'll need to send it in.

mattbutsko said:
By the looks of it, it seems like a GPU failure. This also isn't the first display failure we've seen, and the second one in recent memory stating that it happened after they flash the bricked kernel.
I don't want to be paranoid that there's a bug somewhere in the bricked kernel, but it is possible. I'm on that ROM now, I haven't noticed any problems so far, but I likely won't be on it long.
Click to expand...
Click to collapse
And the first time I heard of that happening with my kernel.
fizmhd said:
http://www.youtube.com/watch?v=i_H0VhszfRE
This is exactly my problem ..is this software issue or ... hardware issue ...
Click to expand...
Click to collapse
That looks like a hardware problem. But you can easily test that. Flash stock rom. If it still exists you can RMA your phone.

show-p1984 said:
And the first time I heard of that happening with my kernel.
Click to expand...
Click to collapse
Hey, man, as I said above (just want to make it clear), I'm not trying to blame the bricked kernel. I said "But I likely won't be on it long" cause I flash a lot , not trying to put down the kernel in any way.

mattbutsko said:
Hey, man, as I said above (just want to make it clear), I'm not trying to blame the bricked kernel. I said "But I likely won't be on it long" cause I flash a lot , not trying to put down the kernel in any way.
Click to expand...
Click to collapse
Never said you did
Just wanted to make clear that I never heard of such thing
Most probably it's the gpu or the framebuffer that pulled up it's hoofs. And that would only be brickable through a kernel if it sets way off voltage/clock settings. And then there would be a lot more ppl experiencing this ^^

This is true, I'm throwing the blame on HTC then. I've probably read 10 cases since owning the phone on various forums and websites (I've had it for two weeks) and some people bought it brand new, others are rooted. I kind of always suspected the heat could be an issue, with the stock battery, using the phone with the screen on for 10+ minutes guaranteed warmth - playing a game for 10+ minutes made the phone hot to the touch, the screen would even be warm where the main board is located on the bottom of the phone.
I have a Chichitec battery now and while it occasionally gets warm, I have no severe heat issues any more. Oh and by the way, the Bricked kernel is the only way I can stand using Sense, it's just so fluid now, and the battery life is pretty good too.

Frends, ...
Iam not able to enter the recovery mode ...
The phone keeps displaying white screen when i remove the batery and switch on holding the volume key down....
Nothing else happens ...
So I hope this is a hardware issue ...
and i shall sent it to htc ... since my phone is rooted will i get the warranty ...

fizmhd said:
Frends, ...
Iam not able to enter the recovery mode ...
The phone keeps displaying white screen when i remove the batery and switch on holding the volume key down....
Nothing else happens ...
So I hope this is a hardware issue ...
and i shall sent it to htc ... since my phone is rooted will i get the warranty ...
Click to expand...
Click to collapse
Just ruu it. Boot it up, fire up the ruu, wait a few minutes, done.

show-p1984 said:
Just ruu it. Boot it up, fire up the ruu, wait a few minutes, done.
Click to expand...
Click to collapse
Im sorry , ... i dint understand what you mean ruu it ...
i used the adb reboot recovery, and when i giv command to reboot in recovery mode the phone restarts and white screen is shown nothing else ...
thnak you

fizmhd said:
Im sorry , ... i dint understand what you mean ruu it ...
i used the adb reboot recovery, and when i giv command to reboot in recovery mode the phone restarts and white screen is shown nothing else ...
thnak you
Click to expand...
Click to collapse
Boot up your Phone. Let it sit @ Homescreen.
Download this: Click Me
connect your phone to your pc.
start it.
follow the instructions on your pc monitor and wait. (it may take 15 minutes+ depending on what is flashed)
If the procedure succeeded and the problem is still there, you can safely RMA it. You are now back to stock. Stock hboot (limited fastboot), stock recovery, stock rom, stock radio. But you are still s-off. Normally that would not bother HTC, because some phones were sent out already with factory s-off, but if you want s-on again (this is the high risk part, it may brick your phone for good, but you are sending it in either way, so normally there would be no harm done. Your decision!) you can do this from your fastboot (adb reboot-bootloader):
Code:
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Now you should be S-ON again.
If there is a pink "*** SECURITY WARNING ***" Readable on your screen, just repeat the above process without the S-ON part ofc.
EDIT:
just remembered that you have no screen Only white ^^
So if your screen is still white after fastboot reboot-bootloader do this: fastboot reboot
Your phone should now boot up (with htc bootup sound, etc...).
If it does not, for whatever reason, just repeat the above process without the S-ON (it's most likely that you have the pink warning, just can't see it ^^).
After this your phone should boot up normally. You can send it in now. (100% stock, there is virtually no way HTC could tell you were S-OFF, ofc only if you haven't s-off'd with HTC's bootloader s-off)

show-p1984 said:
Boot up your Phone. Let it sit @ Homescreen.
Download this: Click Me
connect your phone to your pc.
start it.
follow the instructions on your pc monitor and wait. (it may take 15 minutes+ depending on what is flashed)
If the procedure succeeded and the problem is still there, you can safely RMA it. You are now back to stock. Stock hboot (limited fastboot), stock recovery, stock rom, stock radio. But you are still s-off. Normally that would not bother HTC, because some phones were sent out already with factory s-off, but if you want s-on again (this is the high risk part, it may brick your phone for good, but you are sending it in either way, so normally there would be no harm done. Your decision!) you can do this from your fastboot (adb reboot-bootloader):
Code:
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Now you should be S-ON again.
If there is a pink "*** SECURITY WARNING ***" Readable on your screen, just repeat the above process without the S-ON part ofc.
EDIT:
just remembered that you have no screen Only white ^^
So if your screen is still white after fastboot reboot-bootloader do this: fastboot reboot
Your phone should now boot up (with htc bootup sound, etc...).
If it does not, for whatever reason, just repeat the above process without the S-ON (it's most likely that you have the pink warning, just can't see it ^^).
After this your phone should boot up normally. You can send it in now. (100% stock, there is virtually no way HTC could tell you were S-OFF, ofc only if you haven't s-off'd with HTC's bootloader s-off)
Click to expand...
Click to collapse
Iam really thank ful to u for the information provided ...
I downloaded the rom as u suggested ..but bad luck ... i got the error its worng one ...
and i downloaded this one ...
RUU_Pyramid_HTC_Europe_1.24.401.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190934_signed
but at last i got error ...Error 131 Customer id error Plz find the correct rom ...
How will i find the correct rom for my phone ..
Thanking You...

fizmhd said:
Iam really thank ful to u for the information provided ...
I downloaded the rom as u suggested ..but bad luck ... i got the error its worng one ...
and i downloaded this one ...
RUU_Pyramid_HTC_Europe_1.24.401.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190934_signed
but at last i got error ...Error 131 Customer id error Plz find the correct rom ...
How will i find the correct rom for my phone ..
Thanking You...
Click to expand...
Click to collapse
Is it a branded sensation?

show-p1984 said:
Is it a branded sensation?
Click to expand...
Click to collapse
it was i s-offed it and installed it with pyrmid rom ...[ROM][29 OCT]Pyramid3D v8.2.1 XE | 2.3.4 | SUPER Fast!! | Bricked v1.45 | STABLE
after this all this problem happend ...

Thanks to all for giving me such a great support.
I never had got such great support from any of other forums.
My phone did not get fixed, i sent it for service.
Hope they will fix it for me ...
and Once more thanks to all for having time to spent for me ...

[Q] HTC Aria will not boot if plugged in

EDIT: Wrong category, sorry. I'm new.
Rooted Aria/Liberty won't turn on if it's plugged in (wall charger or USB). The orange charging light is on and the screen is lit but black. The menu buttons do not turn on. I have to remove the battery after unplugging it for it to turn on.
The phone is rooted and the problem is consistent no matter what ROM I use. I believe it is a problem with the bootloader, but I'm not very advanced with these things.
I rooted the phone with Unrevoked and whenever I boot into recovery mode it says "Revolutionary CWM v4.0.1.4."
Any suggestions on how to make this problem go away? I know it's minor, but it is my mother's phone and every time I'm on the phone with her she complains about it.

The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!

juzz86 said:
The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!
Click to expand...
Click to collapse
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.

ellaizee said:
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.
Click to expand...
Click to collapse
Tried this one mate?

juzz86 said:
Tried this one mate?
Click to expand...
Click to collapse
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.

ellaizee said:
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.
Click to expand...
Click to collapse
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704

glevitan said:
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704
Click to expand...
Click to collapse
You are MAGICAL. Thank you so much! And thanks to juzz86 for the suggestions as well.
I used fastboot to flash the recovery and now it does the normal battery image when the phone is off and charging.

No problem. When that happened to me, I panicked but after a couple of google searches I came across that...glad you solved it.
Sent from my Inspire 4G using XDA

All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.

ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
hahaha sorry for that. As u can see, I realised after writing it and erased it, but you probably saw it first.....

ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!

juzz86 said:
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!
Click to expand...
Click to collapse
Even in UK they use mate a lot....but it is no defense for me...I am in Argentina... lol

[Q] HTC Sensation rebooting after root

Hi all, I am sorry if this is already posted or answered but I spent all day yesterday searching and reading and cannot find the answer.
I have 2 Htc sensations that I messed up some how and would be very grateful if you could help me with them.
Phone 1 has been rooted for a long time and in preparation for ICS I flashed T-mobil: Download 3.32 from here
http://forum.xda-developers.com/showthread.php?t=1459767
and now the phone works but it will randomly reboot. I have wiped the cache, delvak cache and battery stats.
I am completely lost please help.
Phone 2 I think I may have messed up real bad here is what I did to it.
I rotted it from here
http://forum.xda-developers.com/showthread.php?t=1192300
I got to step 2 sub step 6 and now it continuously reboots it starts with the white screen with HTC on it then goes to another white screen that says HTC Quietly brilliant for a second and repeats.
Please help me yes I am a noob and grateful for any help.

Wow that was a fun ride (not really) it appears I did not flash the PG58IMG file correctly, after I flashed it correctly I got Insert Coin installed and so far it seems that they both are working. only time will tell.
Thanks anyway guys.
A.J.

If you are trying to install the latest firmware and having the HTC log restart problem. Try to super wipe on the recovery and install first the 3.12 firmware.
HTH

Did you install supercid after root?
Sent from my HTC Sensation 4G using xda premium

Both phones are working fine but I have a new question, I can not get the voice dialer to work ie I long press the button on my plantronics bt and say call tom.
I have tried vlingo from the market and this fix
http://forum.xda-developers.com/showthread.php?t=1133246
but nothing has worked. is it just not working in Insert Coin rom?

Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.

which of the 2 phones you are talking about?
In a previous post you said that problem was solved, now what?
Also, it would be better to know what your bootloader says and what you were attempting to do before black screen.

area1509 said:
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
Click to expand...
Click to collapse
Sounds like a brick to me, but since the problem is unclear, it's possible to fix. I wish I could help but I don't understand your issue to be honest!

I had 3.32 on it with Insert Coin ICS and thought I have 2 so might as well restore one to factory setting that's when I tried to flash the 1.17 and it never started again.
T-Mobile HTC Sensation 4G
The other one is working so I am not messing with it.

I had the same thing happen to me and it was over for the phone. Took it in to tomo and told them it died and after I charged it and went to turn it on, bam, went black and never came back. They never got it to work either and replaced it for me

You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)

kualmente said:
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
Click to expand...
Click to collapse
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.

mugetsu666 said:
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
Click to expand...
Click to collapse
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.

No what's happened to him is what happened to me. It's like it gets fried or something. The screen goes black and u can't turn it on or get into bootloader. Tmobile told me when it happened it was dead and got me a new 1

kualmente said:
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
Click to expand...
Click to collapse
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.

area1509 said:
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
Click to expand...
Click to collapse
Good luck mate. Just let us know if it worked

Bootloop problem. Cannot access recovery. Cannot restart.. One X

Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help

If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.

You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous

Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.

I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?

Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner

Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium

ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?

I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..

The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?

Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help

Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.

Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff

Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.

Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX

THAT is AWESOME

Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.

Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2

Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .

Heh it must have been so
Sent from my HTC One X using Tapatalk 2

[SOLVED] Flashing light, no screen...Help appreciated!

Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again

What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita

timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated

So does it power on at all?
Sent from my Evita

timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!

Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.

It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita

Hi from Canada!... I just wanted to be part of the greetings.. :laugh:

exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)

I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.

My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita

timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:

Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated

Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita

timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated

Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita

timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now