Related
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 ...
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
I've already install the the Digitizer before noticing that there are multiple versions for our phone. I have to slide the circle multiple time before I can log in to the home screen. I already S-OFF, ROOTED and SUPER CID and seems still laggy when pressing text keys when texting or when pressing the lower buttons the home menu file or back or search sometime I have to press it twice to work.
I used the PG58DIAG to calibrate the screen and still acts funny is there a fix to this?
Honestly I think I would try to match the screen as close as possible to the appropriate version for the device. You said there are multiple versions of the screen. Which version would be most appropriate for your device ? Perhaps you purchased the wrong version. Is their a way to find out which is the correct version of screen for your device ? If so, I would purchase the correct version. Perhaps this is what is causing the issue ? It could be the wrong version. This is what I would try if I were you. Its likely that with the correct version you won't have these issues. I hope this helps. I wish you the best. Hopefully with the correct version, it won't give any issues.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, kernel version PYD-X stable 3.1, mugen battery 3800mah. Please press thanks if I helped in anyway.
I had this same problem. I purchased before finding there were multiple versions. The digitizer was slow, unresponsive, and inaccurate. I am also rooted and am running CM10. I went into the debugging and enabled the option to view touches and found that it was registering screen touches in certain areas and that caused everything to malfunction. It was a faulty digitizer. I was fortunate my seller sent a new one and it was working perfectly.
Unfortunately I broke the LCD on the second digitizer install and now have to replace that! lol
I would suggest you go into the debugging options and enable the options to see what the screen is registering. It will put a dot everywhere it thinks you are touching and you may notice it is a faulty digitizer. Cheap ones from ebay happen to have a pretty high fail rate. It can also have dead spots where your touching doesn't register. Both are hard to diagnose without those settings.
Good luck.
Com-
Alex13mod said:
I've already install the the Digitizer before noticing that there are multiple versions for our phone. I have to slide the circle multiple time before I can log in to the home screen. I already S-OFF, ROOTED and SUPER CID and seems still laggy when pressing text keys when texting or when pressing the lower buttons the home menu file or back or search sometime I have to press it twice to work.
I used the PG58DIAG to calibrate the screen and still acts funny is there a fix to this?
Click to expand...
Click to collapse
hi, i have the same problem .. did u fix it?
i have HTC Sensation 4g with Android Revolutionary HD 6.8.0 ROM , sebastianFM kernel , fw 3.33 , htc sense 3.6 .. s-off, unlock,
how can i make update to htc sense 4 or 4.1?
it may resolve the problem?
Georgebucataru said:
hi, i have the same problem .. did u fix it?
i have HTC Sensation 4g with Android Revolutionary HD 6.8.0 ROM , sebastianFM kernel , fw 3.33 , htc sense 3.6 .. s-off, unlock,
how can i make update to htc sense 4 or 4.1?
it may resolve the problem?
Click to expand...
Click to collapse
Sense 4.1 Rom stable and super smooth with many tweaks. Here you go
http://forum.xda-developers.com/showthread.php?t=1671547
Sent from my powered HTC Sensation.
Press thanks if it helped
may fix the problem? ..
Georgebucataru said:
may fix the problem? ..
Click to expand...
Click to collapse
Maybe
Sent from my powered HTC Sensation.
Press thanks if it helped
i put it..and it's smoother..it's runnig better..and the touch also start to work better..but stil inacurate?! .. what to do?! i talked with a service man..and he told me that are 2 ways..resorft of replace the touchscreen..i think is resoft..because..sometimesc work good..sometimes no.. ?!
Georgebucataru said:
i put it..and it's smoother..it's runnig better..and the touch also start to work better..but stil inacurate?! .. what to do?! i talked with a service man..and he told me that are 2 ways..resorft of replace the touchscreen..i think is resoft..because..sometimesc work good..sometimes no.. ?!
Click to expand...
Click to collapse
probably it is not a software issue
i tried all the stuff..exceptly super cid? how to do this, what's whis?
Georgebucataru said:
i tried all the stuff..exceptly super cid? how to do this, what's whis?
Click to expand...
Click to collapse
you can change it easily by using a simple command in a command window
when you have supercid you can flash any firmware,radio,rils etc
but i don't think it will help
edit:if you want to do it the command is
fastboot oem writecid 11111111
fastboot reboot-bootloader
but first do fastboot getvar cid just to know your original cid
oh..thank's my friend! ..i want to say ..i have the phone for 3 days..and it's working better and bether!
Never mind my answer
I'm having the same problem with my z710e, it started, I believe, with a Rom update, I'm using viper 1.6.3, my answer is if there any calibration softwware because all the problems seems to be from the center to the bottom of the screen
Enviado desde mi HTC Sensation Z710e usando Tapatalk 2
Hi,
I am new to this forum.
Few days back, I bought a sensation XE on ebay where the seller claims to have run an update and after that, the display backlight wouldn't go on again.
I thought that he screwed up somewhere and I could just flash a lower version and everything would be fine.
But once I got it and entered the bootloader (default one, no root it seems), the light wouldn't go on either. Somewhere I read that this is an indicator that there is a hardware problem which is causing the error since the bootloader is kind of software independant.
Is that right? I just wanted to make sure, before I digg into either way.
Or is it possible that it realy is a software error?
Any advice would be greatly apprechiated
Kindest Regards
Rene
surfer90 said:
Hi,
I am new to this forum.
Few days back, I bought a sensation XE on ebay where the seller claims to have run an update and after that, the display backlight wouldn't go on again.
I thought that he screwed up somewhere and I could just flash a lower version and everything would be fine.
But once I got it and entered the bootloader (default one, no root it seems), the light wouldn't go on either. Somewhere I read that this is an indicator that there is a hardware problem which is causing the error since the bootloader is kind of software independant.
Is that right? I just wanted to make sure, before I digg into either way.
Or is it possible that it realy is a software error?
Any advice would be greatly apprechiated
Kindest Regards
Rene
Click to expand...
Click to collapse
did not get your question try to simplify it and also the details of your phone and wad bootloader shows up is it
shrex said:
did not get your question try to simplify it and also the details of your phone and wad bootloader shows up is it
Click to expand...
Click to collapse
Question is: can this be a software error that could have come from something gone wrong while updating or does this show that it has to be a hardware error?
What I said was that when I enter the bootloader, the backlight isn't on either.
bootloader shows
****LOCKED***
Pyramid PVT SHIP S-ON RL
HBOOT 1.29.0000
RADIO-11.24A.3504.31_M
Open ADSP-v05.6.0.2226.00.0418
eMMC-boot
Noone knows the answer or noone understands the question?
maybe I should rerephrase the question:
If there is no backlight shining in bootloader, can this be caused by a firmware error or does this HAVE to be a hardware error?
surfer90 said:
maybe I should rerephrase the question:
If there is no backlight shining in bootloader, can this be caused by a firmware error or does this HAVE to be a hardware error?
Click to expand...
Click to collapse
do u mean the backlight wch the soft keys have (menu,home,back,search) buttons thos keys?
Not only that, I mean display and button backlight. You can't see anything unless you turn the phone to reflect the sun
Ohh now I got it ... Boot into bootloader n select factory reset but b sure it vll delet all ur data n vll make ur phone as stock
hit thanks if I hve hlped you
sent from HTC sensation using xda premium
Okay i chose factory reset and it didnt give me anything to choose.
Seems like it has finished now.
But still all light is off
surfer90 said:
Okay i chose factory reset and it didnt give me anything to choose.
Seems like it has finished now.
But still all light is off
Click to expand...
Click to collapse
Try flashing a ruu.. Check ruu info guide by kgs1992 in sensation general section.. There instructions to find correct ruu and flashing it were given
Sent from my HTC Sensation using xda premium
okay I did the flash and it was completed without an error. but still the screen has no light.
But (I am not sure whether this happened before) the buttons at the bottom sometimes are iluminated.
So this is a hardware error? or can it still be a software error?
thanks
Alright here's the issue...
Ok so my brother had my rooted HTC SENSATION S-ON with CM9, and he was longboarding and txting (bad combination...). As it results, obviously, he fell and desintegrated the screen, but the phone was fully functional before. Couple of months after the incident, before fixing it, i took it out of the drawer i had it put away and turned it on, and earlier that day i had found a very stable cm10.1 rom for it so i went ahead and installed it because wifi and bluetooth was functional on it. After i do so, i try to turn my wifi on in the innitial Google log on and on the screen it said "Turning WiFi on." and i waited about half an hour and nothing, so i skipped it. When i went into the settings app i tried turning bluetooth on and the switch went back to off instantly. And i went online and did research and saw a guy that just pulled the bluetooth and wifi connectors for the antenna up so they would actually work, and i tried it, but no luck... I also tried flashing the boot.img for the current rom, but also didnt work. So i thought it might have been the rom since it wasnt fully stable yet, so i did a full wipe and re-flashed the currnet rom and re-flashed the boot.img but no luck. So i downloaded a stable release of cm9 and did full wipe and installed the boot.img for that version of cm9, but yet again no luck... So i re-installed the cm10.1 Albinoman build and lived on 4G so far... i need help on re-enabling bluetooth and wifi....plz help im desperate
P.S. I think this might have to do with the incident of the screen, but i dont think its hardware related...anyways im going to have the screen replaced this monday, so wish me luck
Try formatting all the partitions except for SD card and then reflash the ROM.
Look here for general solutions: http://forum.xda-developers.com/showthread.php?t=2085025
Sent from my HTC Sensation
AndroidSupporter318 said:
Try formatting all the partitions except for SD card and then reflash the ROM.
Look here for general solutions: http://forum.xda-developers.com/showthread.php?t=2085025
Sent from my HTC Sensation
Click to expand...
Click to collapse
tried that already
Which recovery do you have? If you don't have 4EXT, you need to get flash it, otherwise, you need to s-off your phone
Sent from my HTC Sensation
AndroidSupporter318 said:
Which recovery do you have? If you don't have 4EXT, you need to get flash it, otherwise, you need to s-off your phone
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea i got 4EXT and i always use smartflash when flashing anything at all
Hmmm... what is your radio version and hboot version number? Try to obtain s-off, and then flash firmware 3.33(i think it has a different radio that might fix your problem)
Also, make sure that you s-off before flashing 3.33 from bootloader.
Here's s-off guide: http://forum.xda-developers.com/showthread.php?p=25202517
Here's firmware 3.33: http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation
AndroidSupporter318 said:
Hmmm... what is your radio version and hboot version number? Try to obtain s-off, and then flash firmware 3.33(i think it has a different radio that might fix your problem)
Also, make sure that you s-off before flashing 3.33 from bootloader.
Here's s-off guide: http://forum.xda-developers.com/showthread.php?p=25202517
Here's firmware 3.33: http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation
Click to expand...
Click to collapse
I cant read the version due to the dead chunks on the screen but i should have it fixed in a couple of days. I preffer not trying to s-off since i find that too complicated, but in case i had to do so, would i have to do a full wipe?
No, a full wipe is not required for s-off.
You can go to "about phone" in the settings to find out about your radio version. It should be the baseband numbers/letters.
Also, which kernel do you have? Flashing another kernel might solve the problem.
Try flashing this kernel: http://forum.xda-developers.com/showthread.php?p=36216263
Or this one: http://forum.xda-developers.com/showthread.php?p=16608447
Sent from my HTC Sensation
i took it to get fixed and they fixed the screen and tried to fix this issue but couldnt and told me
it was a motherboard issue and that it was broken, but i highly doubt it because everything else works
perfectly fine, although i tried the kernel (Sultan) and it didnt work...still got that same issue
Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation
dosnoventa said:
i took it to get fixed and they fixed the screen and tried to fix this issue but couldnt and told me
it was a motherboard issue and that it was broken, but i highly doubt it because everything else works
perfectly fine, although i tried the kernel (Sultan) and it didnt work...still got that same issue
Click to expand...
Click to collapse
hi, didn't see anywhere that you mention your android version, if it is 4.2.X, don't try to turn the WiFi on, rather go to advanced WiFi settings and select a region code in there, whatever you liked. but in case it is 4.1.X then Install WiFix Manager while WiFi is off, and reboot your phone.
good luck. :good:
AndroidSupporter318 said:
Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation
Click to expand...
Click to collapse
as a matter of fact i did try the stock ics and it had the same issue, unafortunately i havent s-off yet, but im not quite sure i want to do that
A friend of mine haf the same problem about a year back. Tried softwarefix but no luck. Restocked it and got the board replaced by htc.
Sent from my GT-N7105 using xda app-developers app
AndroidSupporter318 said:
Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation
Click to expand...
Click to collapse
I did try stock ics, even resetting the phone to stock but no luck. Though i might not want to s-off, finding
that the process is pretty complicated, i yet do not have the knowledge to understand.
help
Hey guys I need help with my galaxy note 2 t0ltetmo, if anyone is interested and is willing to help me with this one I'd appreciate it, cause no one seems to help me. Please help if you can, I'm in desperate need here. Anyways here's the link to the forum: http:// http://forum.xda-developers.com/showthread.php?p=48442689&nocache=1