HELP!, I have been very lucky in the past and have had very few issues rooting and applying different themes, kernels etc. but the fact is I have little idea of what I am doing. For some reason I can't explain I tried to load the ninja rom to get FP5, ( and I did not back up before I tried to install it. because I am that stupid). Not sure what happened but I got stuck in a Samsung logo boot loop. I read where someone else had similar issues and got going again by putting Tweaked 2.2 over top after a clearing data etc so I tried that. Now when I boot I get the Samsung logo and it just sits there. I have rebooted several times, battery pulls, mounted everything and I still get the same frozen logo.
I would like any file I can load from CWM or Odin to get me back up. I will go back to stock if need be but I am not sure what I need to get back to stock FP1 to start again from there. or stock FP5 or whatever.
I have cleared data already so whatever gets me working I will try
I found a video with instructions to to EP4 but I thought that might be a little too far back. I know how to use CWM and Odin, I am just not sure what I need to get to stock, or any good working version, starting from my current state.
(Seached for FP1 stock but mostly found discussions of "upcoming" OTA and the EP4 videos.)
Thanks
fsuinnc said:
HELP!, I have been very lucky in the past and have had very few issues rooting and applying different themes, kernels etc. but the fact is I have little idea of what I am doing. For some reason I can't explain I tried to load the ninja rom to get FP5, ( and I did not back up before I tried to install it. because I am that stupid). Not sure what happened but I got stuck in a Samsung logo boot loop. I read where someone else had similar issues and got going again by putting Tweaked 2.2 over top after a clearing data etc so I tried that. Now when I boot I get the Samsung logo and it just sits there. I have rebooted several times, battery pulls, mounted everything and I still get the same frozen logo.
I would like any file I can load from CWM or Odin to get me back up. I will go back to stock if need be but I am not sure what I need to get back to stock FP1 to start again from there. or stock FP5 or whatever.
I have cleared data already so whatever gets me working I will try
I found a video with instructions to to EP4 but I thought that might be a little too far back. I know how to use CWM and Odin, I am just not sure what I need to get to stock, or any good working version, starting from my current state.
(Seached for FP1 stock but mostly found discussions of "upcoming" OTA and the EP4 videos.)
Thanks
Click to expand...
Click to collapse
Take a look this, you have many FP1 stock roms (debloated/deodex/root etc..) http://forum.xda-developers.com/showthread.php?t=1560117
thanks for the links.
now I can't mount the SD card. Maybe that's why it is stuck in the first place. I know I have run into this before but can't recall what I did to get it mounted.
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
tom0779 said:
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
Click to expand...
Click to collapse
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
mittortz said:
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
Click to expand...
Click to collapse
Cm10 stable works for me. But I installed it in recovery
Sent from my HTC One X-
I figured out the issue. I forgot that with the 2.20 firmware you have to flash the boot.img separately from the ROM. So after the update all I had to do was flash the boot.img and it was all ready to go again
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.
HTC One-S US version. Wow. I will try to keep this short and would really appreciate any input I can get. I should probably resolve myself to it being bricked but who knows.
I updated my device last night to the latest Cyanogen mod (was already running the last release). I factory reset before. While reloading the new version the device froze on the white HTC screen.
I was able to get back to the bootloader and at times the Clockwork Recovery screen. Somehow in the process the SD card became unmounted. I followed the *numerous* threads here on how to resolve it but to no avail. At one point I reformatted the SD card and, for some reason, repartioned the flash ROM allocation to a size much to small to run Cyanogen (I tried to reinstall the stock software from .exe file after relocking the device and this is how I determined the allocated size was to small.
So I am now stuck on the bootloader screen. Is it possible from either ADB commands or ? to correctly partition the drive again? I have Googled and Googled and probably spent more time flying solo on this than I should of (at least past my expertise). I have tried the usuals, factory reset, clear storage, etc. When I tried to use the HTC software to reload the original build, it showed no existing OS on the device. So I am stumped and will provide any information as needed to clarify this confounding problem. Thank you.
michaelsean
It seems like you might have to go back to a stock RUU, What version of HBoot are you on?
Hey all! This is my first post here since i got my htc one S 2 days ago. I have read quite a bit on how to install custom roms and everything.
The very first ROM i installed was the venom viperOneS OTA 2.1.0 and it ran well until i noticed that my camera was not working. Not even through other apps that require camera. All it says is that the camera is unavailable and shuts down the apps. I tried dozens of things to fix the camera, but no luck. Then realised that my microphone didn't work and i couldn't call anybody.
I decided to get my phone back to stock, but it seems to be an extremely difficult process. I downloaded loads of RUU files (including the newest RUU Ville U JB 45) and after re-locking the phone, and running the .exe file i always get an error after its trying to change the signatures saying that this is not the right file for my phone. (When i press 'update' in the installed the current version is blank, not sure if this means anything).
Then i tried an older viperOneS OTA and was left with a bootloop.
Could somebody please help me out on how to get my phone to stock version?
And before you ask if i've wiped my phone before any ROM installation - i have multiple times.
Thank you in advance.