Database Info

Sensation keeps freezing at random?

New to flashing roms on the sensation, but not new to flashing roms in general. (Had a Desire before) and i just flashed Virtuous Sensation as it seemed the most stable from what i could see but an hour after i have done so, it has frozen twice. Why is that? do I need to flash a new kernel??

Matty Matt said:
New to flashing roms on the sensation, but not new to flashing roms in general. (Had a Desire before) and i just flashed Virtuous Sensation as it seemed the most stable from what i could see but an hour after i have done so, it has frozen twice. Why is that? do I need to flash a new kernel??
Click to expand...
Click to collapse
Did you do a clean install? Superwipe? Try wipeing cache and dalvik then re-install Rom and reboot immediately after. Meaning don't flash any other mods before rebooting.
Let me know if you are beyond these steps.

i have just played arround whit my rom an it didt the same found out that it was some tweak script there didt the freez
after removing the script it hasnt done it again

CM10 Alpha 3 Problem?

Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!

Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
Click to expand...
Click to collapse
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.

Phizban said:
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Click to expand...
Click to collapse
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.

Droid111 said:
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Click to expand...
Click to collapse
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.

mjwhirly said:
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
Click to expand...
Click to collapse
Thanks for the help. I'm going to try it within the next few days. Right now I have SKY-ICS going fine but I'll definitely try that.
What do the different kernels do?

Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Click to expand...
Click to collapse
I used TWRP and flashed over CM9 with no problems. Did it as an upgrade. Wipe system> install CM10> install gapps> Wipe cache
Several people have reported that TWRP worked for them.

[Q] Update Codename android to 3.6.0

guys,
I have a noob question. I'm running codename 3.5.0 on my rooted SNS. Codename 3.6.0 was just released last night. Do I have to wipe data and partition in CWM recovery in order to update to the latest Codename release 3.6.0 ? Also any feedback on the stability of this build ?

nexussdroid said:
guys,
I have a noob question. I'm running codename 3.5.0 on my rooted SNS. Codename 3.6.0 was just released last night. Do I have to wipe data and partition in CWM recovery in order to update to the latest Codename release 3.6.0 ? Also any feedback on the stability of this build ?
Click to expand...
Click to collapse
This will be best answered on the codename android thread.
Vs Nexus S4G using tapatalk2

nexussdroid said:
guys,
I have a noob question. I'm running codename 3.5.0 on my rooted SNS. Codename 3.6.0 was just released last night. Do I have to wipe data and partition in CWM recovery in order to update to the latest Codename release 3.6.0 ? Also any feedback on the stability of this build ?
Click to expand...
Click to collapse
No.
Just wipe cache and dalvic (if you wanna update the rom and keep your data) then install 3.6
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Personally, I've tried wiping and not wiping (between 3.3.x to 3.4.1). A full wipe was generally more stable in my case. Phone was having a lot of crashes with the dirty install.
If you can, just backup all your app data and do a full wipe. It should cause less troubles that way. Otherwise, do a dalvik and cache wipe if you don't want to go through the trouble.

Thanks ! The steps mentioned above, generally worked. Installed the ROM followed by wiping cache partition and Dalvik cache
But after update to 3.6.0 my gapps stopped working. Gmail, play store etc would crash on loading. Had to re-install gapps using CWM in order to fix the the problem. Everything seems to be working OK for now.

[Q] no app restore after ICS OpenSense flash

I came from ARHD 1.2.2 and wiped cache, data and delvik and flashed to OpenSensation 200121007 with 4ext. and gapps 20120429.
all is well except Play won't restore any apps. Not looking forward to a one by one.
Any suggestions for an easier fix?
Tried removing my settings/acct and adding in Play. Finds my apps, but that's all.
Should I re-flash CM9, then gapps, then OS, then Bricked?

Yes also before flashing did you wipe data factories reset after wiping cash and dalvik? Make sure you have nandroid backup incase something goes wrong. Steps, wipe cash, wipe dalvik, wipe data factory reset, flash Rom, flash gaaps , see if that solved your issue. Hopefully it will. Best of luck. Before flashing Rom in 4 ext I always wipe data factory reset along with cash and dalvik for a clean install. Hope this helps. Best wishes .
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, mugen battery. please press thanks if I helped in anyway.

realsis said:
Steps, wipe cash, wipe dalvik, wipe data factory reset, flash Rom, flash gaaps, see if that solved your issue. Hopefully it will. Best of luck. Before flashing Rom in 4 ext I always wipe data factory reset along with cash and dalvik for a clean install.
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, mugen battery. please press thanks if I helped in anyway.
Click to expand...
Click to collapse
Darn the Luck ! ! ! No change. I did from scratch.
Guess it's a one by one.

If you have nandroid, restore nandroid, use titanium backup to backup all apps, install new ROM, Gapps and restore from titanium backup.
While you are at it, I'll suggest try CM10.

webharsh said:
If you have nandroid, restore nandroid, use titanium backup to backup all apps, install new ROM, Gapps and restore from titanium backup.
While you are at it, I'll suggest try CM10.
Click to expand...
Click to collapse
I do have nandroid, bur I figured the last time I tried OS it was unstable so I didn't use the nandroid.
Is CM10 stable with OpenSense 1007, WiFi calling and tether?
Perhaps you can answer this.
Some suggested that TWRP was a better recovery. I tired it with the todays re-flash and still have these (gapps) issues. But it seems to have overwritten 4ext though it does use some element of 4ext based on the progress log.
Is there a way to delete TWRP and just go back to 4ext?

metropical said:
I do have nandroid, bur I figured the last time I tried OS it was unstable so I didn't use the nandroid.
Is CM10 stable with OpenSense 1007, WiFi calling and tether?
Perhaps you can answer this.
Some suggested that TWRP was a better recovery. I tired it with the todays re-flash and still have these (gapps) issues. But it seems to have overwritten 4ext though it does use some element of 4ext based on the progress log.
Is there a way to delete TWRP and just go back to 4ext?
Click to expand...
Click to collapse
CM10 is quite stable not sure how it compares with Opensensation. Bruce CM10 is getting updates almost every other day. I asked you to try because since you are between ROM's you can get a feel of what CM10 is and how it works out for you.
Wifi calling , I don't think works on any AOSP/CM based ROM. Tether I've never used so dunno again. Check CM10 forum.
I think you can install 4ext on top of TWRP to replace it.

webharsh said:
CM10 is quite stable not sure how it compares with Opensensation. Bruce CM10 is getting updates almost every other day. I asked you to try because since you are between ROM's you can get a feel of what CM10 is and how it works out for you.
Wifi calling , I don't think works on any AOSP/CM based ROM. Tether I've never used so dunno again. Check CM10 forum.
I think you can install 4ext on top of TWRP to replace it.
Click to expand...
Click to collapse
WTH, I'll try another. So far (knock silicon) OS is pretty stable. I think I didn't properly wipe the first time I tried and/or this kernel is better.
WiFi and Tether do work with AOSP (pretty sure OS is AOSP derived).
4ext simple wouldn't reinstall over TWRP2, although it doesn't appear that TWRP is making some use of 4ext "routines" somehow.
Since OS is stable, I'm good.

metropical said:
I came from ARHD 1.2.2 and wiped cache, data and delvik and flashed to OpenSensation 200121007 with 4ext. and gapps 20120429.
all is well except Play won't restore any apps. Not looking forward to a one by one.
Any suggestions for an easier fix?
Tried removing my settings/acct and adding in Play. Finds my apps, but that's all.
Should I re-flash CM9, then gapps, then OS, then Bricked?
Click to expand...
Click to collapse
That happened to me when I changed my hboot by way of upgrading the firmware and my phone got a different android ID. I think titanium Backup gives you the option to restore the latter id number if you run it just when you are starting to setting up your phone. I didn't know that so I ended up installing one by one but gave me the chance to discard the ones I wasn't using
Sent from my Sensation using AOSP 4.1.2

[Q] Having slight problems with CROMI 3.0.4

First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?

furou said:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
Click to expand...
Click to collapse
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.

I think I read somewhere about a CROMI forum? If there is one, can someone point me to it?

sbdags said:
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
Click to expand...
Click to collapse
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?

furou said:
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
Click to expand...
Click to collapse
Either is ok but kernel Installer is faster to do