Hi guys,
I am having a strange problem. I was runing stable CM9 on HTC Sensastion, and yesterday screen just stoped to response to touches. I can wake the phone on button but can not unlock it. After a whole day wiping, doing factory reset, etc, i flashed RUU for it, and screen was working with stock ROM. Looking at HTC Sense I reminded myself why I flashed CM9 in the first place, so Iflashed it again this time CM9.1 stable. Screen issue came back. Then I flashed Bruces CM10 and the issue is still there. ta ****?! Phone is fully functional, exceptit doesn't respond to touches. I can't it 100% doesn't response, because there are some situations (1 of 10) whenunlock animation starts but then freeze. Also, screen is fully functional in 4EXT Recovery.
I did JPBear S-Off
4ext recovery
1.27111 HBoot
flashed cm9.1 and cm10(bruce) over 3.33 ruu
Any sugestions? Thank you for any kind of help!
Ask in the questions and answers section
I am sorry for not putting the thread in right place. I'm preety new/noob.
It's not working with Venom also..
I'm gona flash RUU again...
Instalation through Recovery was smooth, without any problems. When instaling Venom screen is used for selecting options. It worked well there. But when phone boots up, and I touch to unlock, ring moves a bit and freezes. Capacitive buttons are not working also
I'm gona flash RUU again...
I can't believe..screen is working in Stok ROM. Ugliest **** on planet...ghrrrrrrrrrrrrrrrr
Guys..any ideas?
After whole bunch of flashes, I managed it to work somehow with ViperS. After that I flashed CM10, it worked whole day, but same thing in the morning. No response.
One thing that I noticed is that when I format partitions using 4EXT, and looked into info, amount of Size and Free are mismatching, like there is some data on partitions!? Maybe problematic files are in there..Like the partitions are not formated.
Related
Appologies for not replying to the original MIUI thread. I am not a new user and i am very experienced in flashing roms etc, especially on samsung devices. I have been around for a while now but this is my first post so i cannot post in the dev section yet.
Last night i flashed MIUI to my infuse. I followed the instructions in the op here exactly.
http://forum.xda-developers.com/showthread.php?t=1278053
I had no problems flashing and everything was successfull, however there were 2 major issues. First being the soft keys. The four buttons menu, home, back, and search buttons did not function at all. They werent even backlit. The volume rocker and power buttons functioned fine. I reflashed from blue cwm twice and still nothing.
This is where i ran into my second issue. There were no posts about anyone having the soft key issue however i did notice alot of people losing their recover and being stuck on the samsung boot screen. This eventually happened to me.
I went to samfirmware and downloaded 2.1 and odin'd it, then odin'd the community kernel to get ext4 and red cwm then restored my nandroid so i am back to normal. I wanted to post about my soft key issue but as i said i had to post in q&a due to my lack of posts.
Any suggestions? if not, i at least wanted to inform the dev of the issue.
Thanks
have you tired CM7, just asking cuz they have almost the same bugs....so i would curious to see if your softkey issue transfers to that rom as well. and if not........
i would try loading up CM7, wiping from the orange CWM and flashing MiUi from there. it Should have worked the way you did itk if you were coming from stock. but who knows maybe seeing if it happens on Cm7 will lead to your answer.
just an idea though
no i havent been able to try cm7 yet as i dont have a build environment set up anymore and havent seen a release yet, would love to give it a shot if someone wants to send me a zip.
i really hope it doesnt have the same issue or ill have to donate this thing to my fiance and get a gs2 or something lol.
Check your mail, you seem to know what your doing so test it out see what happens.
Happy Flashing
Happy flashing indeed, thanks for this im going to give it a go right now, bbl with results.
Hell the only reason i was flashing miui to begin with is b/c i am currently unable to build cm7 so hope this works..
Thanks a ton!!
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
powdered_donuts said:
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
Click to expand...
Click to collapse
Glad it all worked out.....
Hey guys, I been away from the sensation for a few months now and I think I bricked it on my first flash back! I was flashing ARHD & I followed the noob guide, I downloaded firmware & updated, deleted the firmware file, performed super wipe, flashed the rom, and I checked my md5 sums. Now I'm bootlooping the white HTC splash screen, and sometimes I see the beats audio symbol but right back to the slash screen! Ahhh.... I use this line for work. I used the 3.30 firmware as it said to & I'm on boot 1.27? I know one of you guys can help, so please ANYONE,I've got a get this fixed tonight.....
well if its booting then fortunately you're not bricked lol
have you tried re flashing the new firmware?
I flashed the 3.30 that the installation guide I was following told me to. I have ext 2.2, so is that an issue or is it the correct recovery.
Anyone who can walk me through this I'd really appreciate it guys. Just like most, I rely on my phone for work. I'm a little worried here, I've flashed quite a few times and I've never had an issue like this that I couldn't restore out of.....
Try this??
what I did was everything you did.. except I used this firmware update...
Firmware from 3.30.401.1 & 3.30.401.101 RUU
--- MD5 checksum: 824295C6ACDC8D55BED9E0B913192DBE *PG58IMG.zip ---
--- Only for 3.30.401.1 & 3.30.401.101 based ROMs
Then I installed the ICS Energy rom, and everything works great.. I've also flashed a few other roms without issues.. I haven't tried the arhd yet.. I'm currently running the virtuous AOSP rom.. and still, everything works great.. I hope this helps
Just a side note.. have you tried formatting the sdcard then trying that setup? I did have issues with my sdcard in the beginning, but after formatting, I've had no issues..Also make sure the ROM you're using is made for the correct firmware, otherwise you'll have bootloops! hope this helped!
That's the same firmware I used, and I've ran the firmware upgrade twice now. Now right after I updated the firmware the first time I did it, I rebooted on accident & it wouldn't boot even before I flashed arhd.... is this normal?
It wouldn't boot into hboot? What I did was put all the needed files on my sdcard, flashed the firmware, removed the sdcard(while the phone is powered on).. booted into the rom, then put the scdard back in and removed the firmware update..then rebooted the phone, then wiped and loaded an ICS rom..that was really about all I did.. and so far all works well.. I'm really at a loss as to what the problem on your end is.. it sounds like you've done everything you're suppose to do..
You could try to run the relevant ruu (assume you have s-off?) and start again?
http://forum.xda-developers.com/showthread.php?t=1074559
Update::II flashed Virtuous and had no issues and everything is running perfect. Looks just like my transformer prime now. I doing know why at this point that my system would not play nice with ARHD, I followed the guide to the letter and I flashed the firmware 3.30 several timed just as directed. None the less, I am satisfied with this from, and my device is much smoother and more productive than the ****ty GS2 by T-Mobile that I had been using the last few months! I just can't retire my Sensation. Thank you to all who chimed in, you're a great community!
Bricked
That happened to me too when I tried to install ICS without updating the firmware
first.
I just re-booted to recovery and did a restore. I'm assuming you backed up your
ROM right?
Then at least your phone will go back to normal and you can start over...and use it for work haha
I'm good now on virtuous, but I just couldn't get ARHD to work for me. Yes I had upgraded to the proper firmware first, and I always compare md5 sums. I'm by no means an expert, but I always research, read and ask all the nessecary questions before I flash anything I'm not familiar with. I think there may just be rare occasions when some of the devices just won't play nice with certain software. Virtuous took on the first flash & I'm actually very pleased with it, so all's well that ends well. ICS is just so much more intuitive & functional for me
.
So I got the desire S for more then a year now and decided to flash it with 4.0.4.
Build date 24 june. From here.
Now the first week I didn't seem the have any problems but now it randomly reboots. Mostly it keeps rebooting till I plug it in the powersupply then it keeps working and I can take it out again. But after a while... during a call or just when it's in my pocket it reboots again. What can be the problem here? Anyone who got a anser for that?
More information please
ROM name? How did you root / unlock your DS? What other apps have you recently added that may have helped to cause this?
We aren't mind-readers - our balls are made of flesh and blood, not crystal :angel:
Yeah sorry.
http://forum.xda-developers.com/showthread.php?t=1429215
CyanogenMod 9 Alpha for HTC Desire S
That mod I installed. I only installed whatsapp and google maps.
Other then that didnt do anything else.
To unlock the phone I used the following software.
SuperOneClick 2.2
adb-fastboot-win
ClockworkMod Recovery
There were problems like this a while back with CM9, but they haven't happened for a while.
There were, also, some issues with using CMW but none with using 4EXT Touch.
So, my suggestion would be:
Install 4EXT Recovery Control and Touch Recovery (https://play.google.com/store/apps/details?id=ext.recovery.control)
Install the ROM again using a clean install - superwipe all partitions as 4ext (format, not to be confused with the name of the recovery tool)
I assume that if you are on hboot 2.00.0002 you know about http://forum.xda-developers.com/showthread.php?t=1525100
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
wildcardspv said:
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
Click to expand...
Click to collapse
well, regarding the screen issue, use the battery all the way, til it shuts down. then rwmove the battery n press the powere button as if u were turning on ur phone. then let the phone be still over a night. then re-insert the battery n plug the phone into charge but BEWARE THAT U WILL NOT TOUCH THE SCREEN AT ALL, TIL IT'S FULLY CHARGED. i tried this solution, n it worked. maybe so did it for u :-??
n about the lags, i recommend u to install Seeder 2.00 which is recently released n can decrease the lags as much as possible. and also u could try out making 256/128MB swap with 100% swappiness using Kernel Tuner v4. alsi set these settings IN THE ORDER I'VE TYPED in venom tweaks --> misc --> minfree settings
4
8
16
32
48
64
got no more idea
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
wildcardspv said:
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
Click to expand...
Click to collapse
Install TWRP (TeamWin Recovery Project) and use that to flash ViperS once more (after doing a full wipe of course). Since the only recovery that allows the installation of kernels on an S-ON device is 4ext, you will need to extract the boot.img file from the ViperS installer .zip and flash that using fastboot. Detailed instructions on how to flash a boot.img file through fastboot can be found here: http://forum.xda-developers.com/showthread.php?t=1752270
I don't really trust 4ext because 4ext gave me a lot of weird and nasty bugs. Using TWRP is worth a shot.
hello.
I had a HTC One S, T-Online Germany branded, with s-on and the Viper rom(-> unlocked and rooted).
Then it ran out of batterie, (not the first time that happend after a long day) and when i plugged it in and turned it on again, the x-axis of the touchscreen was mirrored: The Display is normal but when I touch anywhere on the left side it acts like I touched at this spot on the right side.
I was hoping that it was some bug in the rom, and flashed it again.. while flashing I discovered that the same bug is in the recovery (twrp).
I reflashed the recovery and rom a cupple of times untill I lost hope.
Then I s-off'ed it and changed the cid (I wanted to do this since a while) and flashed some custom kernels to see if this would bring any change..
I have no idea what else I could try to solve this.. has anyone a good idea or do you believe it is an hardware bug?
sincerly, menessim
well I guess, no one can help here..