Related
Hi everyone.. first post here.
I just successfully rooted my Nexus S (GT-I9020T, 2.3.4, GRJ22) using adb, recovery clockwork herring and su 2.3.6.1.
ROM Manager is working fine but I do have a couple of issues.
The recovery doesn't always stick and reverts back to the stock one from time to time (I have to flash again then from inside ROM Manager). Which could be a problem due to the next issue..
I've been trying to install some ROMs (Cynogen for instance) but in one version I get a looping boot screen and in an other it keeps going to the recovery screen. Luckily, it's the right one and I can restore a backup. I'm afraid it might revert to the stock recovery at some point and screw me.
Any thoughts on this?
I should have read some more threads first..
I fixed the recovery issue by renaming install-recover.sh using Root Explorer
So I guess I should just experiment to find good ROMs now.
Can anyone suggest a good ROM? I'm looking for improved battery use, slimmed down system, needs email apps (all google apps probably)
Sorted it all out (mount/unmount, delete caches, etc.)
It's working swimmingly now.
Running Cynogenmod 7 and loving it.
I am using Infinity 1.0.0, stable, fast and great battery life, it is a 2.3.4 rom
A while back I rooted and flashed Revolution HD 3.6.4 on my Sensation without any issues; noticed immediate improvements, and was really pleased with the performance and battery life. Only issue was the occasional boot loop which I remedied by flashing a Bricked kernel.
Fast forward to two nights ago…
My parents also have Sensations and were not very happy with them so I convinced them let me root them which I did.
I did to their phones exactly what I did to mine, including; s-off, perma root, CWM, nandroid backup, flash ARHD 3.6.4 w/ bricked kernel.
The weird part is both of them are now having identical issues with their phones; really slow, 4hr battery life and laggy.
However…
I was sure to wipe the battery stats by draining the battery to complete shutoff, recharging to 100% (basically overnight 8hr+ charge) and erase battery stats from within CWM
I did not do a Titanium backup because a)they really didn’t have much installed, app-wise and b)I thought a fresh install would be cleaner without trying to recover any settings
I made sure to run the Revolution HD Super wipe before flashing the Rom
Installed the HTC Bricked kernel
The only thing different about their phones than my phone is they never applied the official HTC OTA major update. I went into this thinking it would not matter since we’re installing a new rom anyway but perhaps I’m wrong???
Why would two freshly-rooted phones exhibit the same issues?
I’m planning on re-flashing their phones later this week with the newer ARHD 3.6.5 rom (which I just did to mine ) hoping this will clear up any issues they’re having but want to make sure I’m not doing something wrong first…
Let me ask a more direct question.
Can I flash the new Revolution HD 3.6.5 (including the bundled faux kernel) to a phone that has not had the HTC Sense OTA update? Or will issues arise?
I think the problem is radio wise. Install the recommended radio and see if it solve the problem
OKors said:
Let me ask a more direct question.
Can I flash the new Revolution HD 3.6.5 (including the bundled faux kernel) to a phone that has not had the HTC Sense OTA update? Or will issues arise?
Click to expand...
Click to collapse
Hi,
The issue is most probably the kernel.
Try installing the latest.
You have two choices.
1.faux.(in my sig)
2.bricked.(HERE)
Seeing as you have two phones to play with,why not try one on each.
malybru said:
Hi,
The issue is most probably the kernel.
Try installing the latest.
You have two choices.
1.faux.(in my sig)
2.bricked.(HERE)
Seeing as you have two phones to play with,why not try one on each.
Click to expand...
Click to collapse
I flashed both their phones with the bricked kernel when I installed the rom originally.
If the problem isn't due to the older Sense version being installed what I plan on doing is flash both phones with ARHD 3.6.5 and leave the bundled kernel installed (have the 3.6.5 with new faux on my phone and so far so good).
I can try the radio flash also but I never had to flash the radio on my phone and all three phones are identical (bought them at the exact same time; family plan-thing).
OKors said:
I flashed both their phones with the bricked kernel when I installed the rom originally.
If the problem isn't due to the older Sense version being installed what I plan on doing is flash both phones with ARHD 3.6.5 and leave the bundled kernel installed (have the 3.6.5 with new faux on my phone and so far so good).
I can try the radio flash also but I never had to flash the radio on my phone and all three phones are identical (bought them at the exact same time; family plan-thing).
Click to expand...
Click to collapse
Hi,
I have never updated via OTA,and I never will.(Do not trust what it will do to my phone)
There are known issues with the bundled kernels.
Both of the latest kernels have had good reviews.
Just saying.
The OTA could've updated your radio.
Sent from my Sensation using XDA Premium App
Check if you have recommended radio or not. If not, flash recommended radio. Then,
Try to download ARHD 3.6.5 (check MD5), download latest kenels of your choice.
- Super wipe
- Flash Room, and reboot (just set up phone, dont set google account and facebook yet).
- If you want do flash roomcleaner: reboot into recovery and flash roomcleaner.
- If not, just reboot in recovery, wipe cache and wipe davik cache, then flash kenel of your choice.
- Reboot, set up your google account, facebook account, email account, etc...
- If phone experiences a bit lag during turning page to page in homescreen. Just reboot again. After that you can do all battery calibration, flashing mods or themes.
It may be too careful but that just to make sure I dont mess up everything with flashing.
Hope this help!
stevendph said:
Check if you have recommended radio or not. If not, flash recommended radio. Then,
Try to download ARHD 3.6.5 (check MD5), download latest kenels of your choice.
- Super wipe
- Flash Room, and reboot (just set up phone, dont set google account and facebook yet).
- If you want do flash roomcleaner: reboot into recovery and flash roomcleaner.
- If not, just reboot in recovery, wipe cache and wipe davik cache, then flash kenel of your choice.
- Reboot, set up your google account, facebook account, email account, etc...
- If phone experiences a bit lag during turning page to page in homescreen. Just reboot again. After that you can do all battery calibration, flashing mods or themes.
It may be too careful but that just to make sure I dont mess up everything with flashing.
Hope this help!
Click to expand...
Click to collapse
Hi,
ROM cleaner is flashed immediately after flashing the ROM, without any reboot.
Thanks for all the advice. I just got a call from my mom today saying her phone dies real fast and every time she takes a photo the screen goes black resulting in a battery-pull.
I gotta fix their ****z pronto.
I hyped the whole rooting thing up pretty good after flashing my phone, so far their experiences are pretty bad.
@ stevendph, I'll do exactly as you outlined. Thanks for the step by step.
fwiw the radio is whatever was on the phone from the time of purchase. Ill flash it as well with the 'recommend' radio.
So the consensus is to go back to the Bricked kernel and overwrite the new "updated" Faux kernel bundled in the ROM???
malybru said:
Hi,
ROM cleaner is flashed immediately after flashing the ROM, without any reboot.
Click to expand...
Click to collapse
Yep, it's can be flashed immediately or after 1st reboot, the result will be the same as roomcleaner's function is to delete system apps, files, skin and wallpaper (which are useless or you dont use). Those also can do it manually but yes painfull .
As i stated before, it's just i am doing carefully to watch if is there anything wrong with room flashing, then continue flash other things. What i did was flash, check, flash, check... until having what neccessary -->nandroid backup, flash, check, etc . Just me to be careful
@Okors: related to kenels, just make sure you notice this.
- Faux latest kenels 0.24r1 is really good and stable (if you have 0.24 beta 7, you dont need to update, as they are same).
- Bricked kenels: v1.5 final has the problem with camera, playback video (sometimes for some devices) as blackscreen, freezing. Version 1.4r1 is really good and stable (without Zram enable). Version 1.5 beta #490 with zram, working great for me anytime including camera, playback, etc... but there are reports from someone that they have lags (i dont)...
That's all what i know when testing and reading reports about these kenels, you have the right to choose what is suite for you.
I would just flash Pyramid 3D and 0.91 Bricked, check if GPS and camera work, then call it a day. If GPS doesn't work you could always try my fix or crypted's, boh are flashable.
Pyramid 3D has been the most stable and the fastest out of all the ROMs that I've tried without having to extensively customize for myself. Honestly though, I would just flash your parents stock again. Doesn't sound like they are power users.
Sent from my HTC Sensation
nrvnqsrxk said:
...Honestly though, I would just flash your parents stock again. Doesn't sound like they are power users.
Sent from my HTC Sensation
Click to expand...
Click to collapse
To be honest, I'm mostly after the improved battery life for them. You're right, they're not power users; in fact the phones are way to "smart" for them. Their biggest complaint is battery life (as was mine before I rooted).
At this point I just want to get their phones back to a stable state. It's frustrating because I NEVER had any of these issues when I flashed my phone.
Even the kernels, radios, etc didn't make 'much' of a difference. I was blessed with a really, really stable flash right out of the gate
I even updated to the latest ARHD and bundled faux kernel and my phone is rock solid.
Both of my parents are coming over tonight for dinner. I'm planning on reflashing them to ARHD 3.6.5. using the steps outlined earlier. Hopefully all goes well or it's restore-to-stock time.
OKors said:
To be honest, I'm mostly after the improved battery life for them. You're right, they're not power users; in fact the phones are way to "smart" for them. Their biggest complaint is battery life (as was mine before I rooted).
At this point I just want to get their phones back to a stable state. It's frustrating because I NEVER had any of these issues when I flashed my phone.
Even the kernels, radios, etc didn't make 'much' of a difference. I was blessed with a really, really stable flash right out of the gate
I even updated to the latest ARHD and bundled faux kernel and my phone is rock solid.
Both of my parents are coming over tonight for dinner. I'm planning on reflashing them to ARHD 3.6.5. using the steps outlined earlier. Hopefully all goes well or it's restore-to-stock time.
Click to expand...
Click to collapse
Hi,
May I suggest using the 3.6.x series with the 0.9.1 bricked kernel,found HERE
I put it on my son's Sensation,and he loves the stability and battery life.
He's not a power user.
He just wants a smartphone that works.
Just a thought.
You could also try the stock rom xe by eddyos. Everything works fine and battery last for 14 to 24 hrs in medium to light usage.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
Hello!
So there is this annoying thing that's been going on since I firstly rooted my phone and started flashing ROM's, radios etc.
I've been using only ARHD ROM's since they have a great reputation, haven't tried others.
So, I started with ARHD 3.6.x ROM's and now I'm on the latest 6.2.1. XE ( No OC ).
So the problem for me all through my experience with my phone, is getting random reboots at mostly no specific times.
The most common is in this situation:
The phone is just sitting nicely in my pocket, I feel that somebody is calling me. I take the phone out of the pocket, want to answer by unlcoking the phone and ding! it just crashes.
When I turn it on, the random reboots just won't stop until I give the phone a rest and don't use it for a while. Because after a random reboot the reboots just keep on coming, if I use the phone.
This also happens when I just take the phone out of my picket and try to unlock it.
So, mostly it reboots when I try to unlock it.
This just makes the phone unreliable and many times people can't call me because I have no idea that it has crashed in my pocket.
I've been hoping that it would stop with the next version of ARHD but it didn't. The problem keeps comming back.
So I wanted to know: Is there any way to see, what is the soul purpose of those crashes? Is there anyway it's curable? Because I don't know if it's the HW or the SW. When I had stock everything and no root, these problems were not present.
My setup:
* Super CID
* Firmware from 3.24.401.1 & 3.25.401.101 RUU
* Android Revolution HD 6.2.1 XE
* Radio: 11.68.3504.00U_11.21.3504.13_2
* Kernel ( from about info ): 3.0.16-g5e58c5e [email protected] #1
* Any other info you need to help me fully?
the kernel could be the problem...try not to use it and see if it happens again..however i suggest to you to flash the insertcoin rom cause it is the best ics rom out there...trust me try it and you will not be disappointed
I have the same problem with all ROMs, including stock, except for the Virtuous Quattro alphas which I was able to run 20 days straight without a crash (impossible with other ROMs). Also the battery readings after a crash is weird, dropping from eg. 60% before the crash, down to 5% when booting after a crash. I contacted HTC about this and they told me it's probably a faulty mainboard. So I'm planning on sending it back in a few months.
I have the same problem with all sense roms GB and ICS its really frustrating I've had it for some time already
Sent from my HTC Sensation XE with Beats Audio using xda premium
Today I will try virtuous_quattro_alpha3_pyramid. If it's too buggy, will try the Inqusition. And if I still have any problem, give the InsertCoin a try. Will post my findigs as I get them.
Any idea what kernel to use? Which is the most stable?
not sure but crashes may have something to do with your applications being in sdcard. i have moved all my applications to phone memory (though i don't have many) and i have not had a forced reboot after that. also super-smooth/ultra-smooth rosie helped, with this tweak my phone is really fast now.
using leedroid rom.
If the phone didn't reboot on stock then it's a firmware/software issue - go back to fully stock and see if the problem still occurs.
If not then start from scratch and make sure the checksums match the downloaded file before you install then, especially the firmware and radio file.
From my hd2 days you might first try setting your network manually, as I did hear that even native Android phones can reset during auto network selection.
So now I am on Virtuos Inqusition and the reboots still occur. It's frustrating.
And ONLY when I take my phone out of my pocket to see what time is it.
So I met a guy who is on all stock, without root etc. and he's getting the same issues.
Anyone else having this problem?
Could it really be the HW fault?
Or still could just be because an official ICS ROM for the Sensation hasn't come out yet?
Full wiped?
Did you full wiped it before you upgraded to the latest verison? In many cases reason for reboots are kernel and/or cache related. So maybe something which is still in your cache could bring that output. Another possibility is when you restore apps and settings from System Tuner or Titanium backup. As you are using stock kernel I don't think it should be the problem generator.
1. Do a nandroid backup
2. Full wipe with Mike's script
3. Fresh install ICS rom you like (I'm using Insertcoin 4.5.4 + Ultrasmooth Rosie)
4. Check MD5
5. install custom ROM
6. Don't restore settings/apps from Google.
7. Don't restore apps/settings from Titanium etc...
Just try to use your phone without all your apps installed for a short time.
Good Luck, hope it helps...
Yes, I always Super-Wipe before a fresh install.
But I will re do everything, installing only the timetable for buses - addicted to that app.
Can I restore contacts from google or should that wait for a while?
Update
So, it's been a while that I've been using Virtous Inqusition with Google sync and nothing else. The original problem still exists, Could this be a HW issue?
I don't really want to go all stock to loose SuperCID and everything else.
So, I guess I have to stick with this problem and leave my Sensation unreliable.
Tomekks said:
So, it's been a while that I've been using Virtous Inqusition with Google sync and nothing else. The original problem still exists, Could this be a HW issue?
I don't really want to go all stock to loose SuperCID and everything else.
So, I guess I have to stick with this problem and leave my Sensation unreliable.
Click to expand...
Click to collapse
Do a full wipe and reflash the ROM also wipe the battery stats and perhaps try a different kernel maybe one closer to stock frequency
Sent from my HTC sensation 4g using Tapatalk
Hey guys,
I've got a Wind G2X which I've recently installed the new 2012 baseband on using LG's tool and the local webserver trick (I believe this technically rebrands the phone to T-Mobile). I then installed some not-latest Eaglesblood AOSP and had it for a while -- everything was pretty solid.
Then I decided to upgrade to the latest, since I like to stay up to date. During this upgrade, I've also tried to "Fix Permissions" (in CWM, after a data wipe) to make sure the permissions are correct just in case -- this operation makes no sense if it relies on there being data (I suspect it does, because I was able to successfully Fix Permissions after flashing the ROM). While "fixing permissions", I've had the phone freeze up, so I pulled the battery, tried again, same thing. Ever since, I've tried installing the latest EGB AOSP and kept finding my phone either dead due to emptied battery (way too quickly) or dead WITH battery charge, every day.
Just recently, I flashed HellFire Sandwich (tried 1.7 and now 1.9), both of which greeted me with "Process stopped.. something something.media". Now in 1.9, when I went to the Play Store for the first time, it hung. I had to pull the battery. 2nd run worked fine.
So I have the following questions:
1. What could be wrong? I doubt it's just bad luck with the ROMs -- surely they would notice such significant problems.
2. When I flash a new ROM, I do the "wipe data/factory reset" and "Wipe Dalvik cache" (should I do the 2nd step? if not, can it cause problems?) followed by flashing the ROM and then GApps. When I do this, can there be some remains from the previous ROM (or some system components) causing the stability issues, or is it a perfectly clean installation with the exception of the recovery partition?
3. Is there anything I can do to truly restore/wipe the phone to prepare it for flashing some ROM and guarantee that there isn't some residual software that can cause problems?
I'll see how stable HellFire Sandwich 1.9 will be on this phone, but the .media crash and Play Store hang may be indicators of more to come.
Thanks!
:/
All ICS roms for g2x have issues with the stability , you should wait the new SU660 Kernel source for a super stable and fully working ICS ROMS
always make wipe factory reset, wipe dalvik and go to advanced and select format /system , before flash any roms, there is no bug froms previous software if you follow these steps (sorry for the english lol ) e_e/
I recomend you any cyanogen based rom (GB 2.3.7) with camera port for cyanogen in the lg optimus 2x thread
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.