Database Info

cyangomod 10 jelly bean 4.1 rom keeps freezing***

i have just flashes cyangonmod 10 jelly bean for my htc one x at&t and it works good and looks good. the ROM was compatible with my phone and i downloaded it from xda. only problem is that the ROM will keep freezing randomly and i will have to reboot my phone. any suggestions?

Wipe before flashing.

lazarat said:
Wipe before flashing.
Click to expand...
Click to collapse
i completely wiped my entire phone haha. i tried flashing again and it does the same thing. should i delete cache before i reboot?

lazarat said:
Wipe before flashing.
Click to expand...
Click to collapse
it also happens right after i press the switch task button after 9 minuets of use

When in twrp you wipe dalvik cache, cache and factory wipe before flashing a new rom

lazarat said:
When in twrp you wipe dalvik cache, cache and factory wipe before flashing a new rom
Click to expand...
Click to collapse
Yes I did all of that.

Could be a corrupted ROM file from downloading from server. Try downloading it again and reflash it.
Sent from my One X using xda app-developers app

They flashing an old ROM like clean ROM 4.0 for some reason certain Ppl are having issues but flashing that ROM then re flashing cm10 seems to help...are u coming from a 4.0.4 ROM? That for sure causes issues as the jb is built off the 4.0.3 kernel
Sent from my One X using xda app-developers app

Should I reinstall Gapps when upgrading CM10 nightlies?

I usually download both the ROM zip and the gapps zip, reboot into recovery, clear cache and dalvik cache and then install the ROM and Gapps.
My question is should I reinstall Gapps after installing the ROM or will the Gapps that is already there from the previous installation suffice?

My rule of thumb. Always clean wipe. Never have issues of leftover junk. Resetting up a fresh ROM is better then discovering a huge bug due to dirty flashing
Sent from my SCH-I535 using Tapatalk 2

libbrichus said:
I usually download both the ROM zip and the gapps zip, reboot into recovery, clear cache and dalvik cache and then install the ROM and Gapps.
My question is should I reinstall Gapps after installing the ROM or will the Gapps that is already there from the previous installation suffice?
Click to expand...
Click to collapse
As the CM10 nightlies install include a format of /system (which is where the gapps package installs), I'd say it's required. It certainly doesn't hurt to reinstall gapps after installing any AOSP rom (they may or may not format /system) and I don't think any will ever contain the google apps.
edit: flumoxed. Tested this with a format /system, install CM10, boot, no gmail, reboot, install gapps, reboot, gmail there, reboot, re-install CM10, reboot... gmail there. It sticks. Doesn't compute with the format command I see in the CM10 updater-script (along with a backup script of some sort). Will have to do some more testing. Still think it's best to always reinstall gapps.

hopesrequiem said:
My rule of thumb. Always clean wipe. Never have issues of leftover junk. Resetting up a fresh ROM is better then discovering a huge bug due to dirty flashing
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The problem with that is - I upgrade nightlies every couple of days and don't want to reinstall everything and make changes to my settings everytime I do it. Is there a one-click shortcut to restore everything if I clean wipe and install?

Go backup or titanium backup will get most things back for you painlessly.
On the contrary I've been dirty flashing cm10 nightlies for 3 weeks without reflashing gapps and I've experienced no issues so it's perfectly feasible but ymmv
Sent from my SCH-I535 using xda app-developers app

toddley said:
Go backup or titanium backup will get most things back for you painlessly.
On the contrary I've been dirty flashing cm10 nightlies for 3 weeks without reflashing gapps and I've experienced no issues so it's perfectly feasible but ymmv
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You're one of the very few then. The majority of problems in the official thread are people who have dirty flashed and when they finally do a clean wipe - problem solved.

Dirty vs Clean Flash

A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...

Brian Gove said:
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Click to expand...
Click to collapse
If I switch ROM's I factory reset then wipe cache and dalvik cache. If it's a theme for example I only wipe cache and dalvik cache since the theme is suppose to be made for your ROM right?....don't see the reason to reflash the ROM as well.

Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium

Il throw a vote to whichever works.. I usually dirty wipe.. If I have issues then clean it and try again.. With nightlies I tend to be fine dirty a lot, but even still I will do a clean every couple weeks just because..

why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form

So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app

What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?

xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Dirty wipe
Sent from a SYNERGIZED GalaxySIII

When I dirty flash, I wipe data cache n dalvik cache. Once I flash what I wanted, I wipe those two once again n select "fix permissions" just in case
Sent from my SCH-I535 using Tapatalk 2

apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Click to expand...
Click to collapse
I disagree. I believe a dirty flash also wipes system. If you are 100% certain that your ROM build effectively wipes system as part of it's install routine, then you could skip this step, however I always wipe system to be safe. This works for me and I rarely need to wipe data or sd card(s).
---------- Post added at 11:01 AM ---------- Previous post was at 10:57 AM ----------
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that?
Click to expand...
Click to collapse
When changing Kernels but not the ROM in a separate recovery session than a ROM flash, you don't need to "dirty wipe." Just wipe cache and dalvik. Dalvik wipe is key so that the dalvik virtual machine can be rebuilt by the new kernel.

Thanks for the info guys.

I usually dirty on nightlies until I have issues. Always clean when switching roms.
Sent from my SGH-I535 using xda app-developers app

It is always good to complete wipe when switching roms.
Sent from my SCH-I535 using xda premium

What if im just switching between stock rom nandroid backups? Can I just restore from one to one? I only have two backups anyways both for stock. Never flashed a rom before
Tap'n

grin0048 said:
This isn't meant to be rude or anything, I'm just honestly wondering if there's any logical reason to think this is substantively different than just not wiping data?
Click to expand...
Click to collapse
I find that this method works better than just wiping cache and dalvik, since im advance restoring data over a clean flash. both ways are considered dirty flashing tho.

I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?

coldhardtruth said:
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
Click to expand...
Click to collapse
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app

droidstyle said:
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
Click to expand...
Click to collapse
Factory reset doesn't touch the davlik(Which I speculate(Guess) has to do more with the kernel than anything)
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is what I meant as a dirty flash when I made the thread yes...
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Usually when I flash a new kernel, or a different kernel, I just wipe the davlik cache and I am fine. There was some reboots after the first boot on the AOSP ROMs but afterwards it ran fine.
SlimSnoopOS said:
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
SlimSnoop is correct. According to one of the developers of a very prominent ROM the IMEI issue was because our phones got confused sometimes(Randomly phone to phone) and tried to reset during a flash. The data it tried to reset was bogus, therefor losing IMEI. He is also correct far as the wiping battery stats. It's only usefull when you have really strange results with battery. Google for the real reason to use them.
Far as backing up your IMEI so you will never run into the problem of losing it.... go into your terminal (almost every ROM has a Terminal emulator)
Type this:
su
then hit enter. Grant permissions
then type:
reboot nvbackup
then hit enter. This will make your phone do some shyt and reboot, but you really shouldn't need to worry about your IMEI after this. Regardless of how many ROMs you flash or what you do or who you date or who you kiss, etc... blah blah....
This really should be the end all for the IMEI...

annoyngduck said:
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
New rom only when their bases are different , like going from ics to jb, or the dev says to do it (Even then Ill try it without a wipe because im lazy).
Themes I never wipe anything
Nightlies never wipe anything.
Edit: If I do have issues I then go back and wipe delvik and cache . That usually straightens out any issues and allows me to keep my setup.

tonu42 said:
Hey but you know I'm right
Click to expand...
Click to collapse
Actually you're not right.
Sent from my SCH-I535 using Tapatalk 2

I seriously can't figure it out.

I've been tinkering with androids for well over a year now and have rooted unlocked and s-off'ed amongst other things many different devices. For some reason I'm having trouble flashing kernels to my s3. Yes I'm unlocked and yes I'm flashing aosp kernels to aosp roms and touchwiz kernels to touchwiz roms. The problem seems most persistent on aosp roms and yes I've also checked that they both had the same cm10 commits. The only kernel I could get to boot was clean kernel on beans custom. Other than that no other kernels will work. The device will boot then the screen will start glitching up and then eventually bootloop. I've also made sure to wipe dalvik and cache plus fix permissions. I've also tried just flashing the kernel after doing a full wipe and starting with a new rom and have root 66ed back to stock and re unlocked. Is there something I'm missing here? I'm getting frustrated as I love custom kernels. Oh and the latest combo I tried was liquid smooth rc3 and lean kernel 1.0. Thanks guys.
Sent from my SCH-I535 using xda app-developers app

did you try wiping cach, davik cach, and fix permissions AFTER flashing then reboot?
Ofc wipe cach and dalvik cache before also.

My usual process goes something like this
*Wipe Cache
*Wipe Dalvik
*Flash Kernel
*Wipe Cache & Dalvik again
*Fix Permissions
Works like a charm every time.
Samsung Galaxy S3

i have had the same trouble once...fixed it by flashing back to a stock kernel first.
try this:
wipe cache & dalvik
flash stock kernel.zip- http://db.tt/ceeDTAfz
flash custom kernel
reboot

Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app

sumredhed567 said:
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
Click to expand...
Click to collapse
stock kernel = stock TW kernel
Sent from my SCH-I535 using xda app-developers app

Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app

sumredhed567 said:
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
another thing you might try is formatting system in cwm.

droidstyle said:
another thing you might try is formatting system in cwm.
Click to expand...
Click to collapse
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!

sumredhed567 said:
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
Click to expand...
Click to collapse
now when you odin back to stock, your booting into stock recovery after flashing the rom(root66) and doing a data wipe/factory reset correct? you said full wipe, but just want to be clear. it may be corrupted internal memory and might need to be reformatted.

I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app

sumredhed567 said:
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
follow section 6 of my guide...link in sig!

Always perform a full/mega wipe as:
1) Wipe data/factory reset
2) Wipe cache partition
3) Wipe dalvik cache
4) In mounts/storage section wipe /system
5) wipe /data
6) wipe /cache
7) wipe /preload
Then flash new ROM.
For flashing a kernel, please perform steps 2 and 3.

General ROM installation questions

When going from one ROM to another (ie. AOKP to CM10), is it only necessary to do a "clean" wipe, or are other steps recommended, such as reverting to stock first? I used to have a Droid 2 and people used to recommend that, but I don't know if it's necessary with this phone.
Also, what exactly does a "clean" wipe entail? I've seen multiple explanations. This guide suggests that you need only wipe data/factory reset and format system. Other people mention things like wiping cache and dalvik cache from recovery. Is there any sort of consensus on this?
Lastly, is it necessary to do these "clean" wipes when flashing a new nightly or new build, or does this simply vary depending on the ROM in question?
Thanks.

If you change ROMs most people recommend doing a data wipe.
Clean wipe is wiping data. If you wipe data, /cache is wiped too, so any subsequent cache wiping is unnecessary.
It is not necessary to wipe data when flashing a nightly or updated build.

When going from one Rom to another or one base to another (4.1 to 4.1.2) a full wipe is recommended that's system, data, cache. Nightly builds are usually safe to flash on top of each other unless otherwise noted. Biggest advice I can give is if you don't do a full wipe and encounter bugs you should go back and do a full wipe to ensure its the dirty wipe that caused it.

Neverendingxsin said:
When going from one Rom to another or one base to another (4.1 to 4.1.2) a full wipe is recommended that's system, data, cache. Nightly builds are usually safe to flash on top of each other unless otherwise noted. Biggest advice I can give is if you don't do a full wipe and encounter bugs you should go back and do a full wipe to ensure its the dirty wipe that caused it.
Click to expand...
Click to collapse
+1 its just not worth it.. Full wipe

Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app

x714x said:
Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ha, I have made this mistake before.

x714x said:
Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How can I verify this? It looks like AOKP has a custom kernel; what are the extra steps I need to take if I want to go to CM10 or back to stock?

Quacker said:
How can I verify this? It looks like AOKP has a custom kernel; what are the extra steps I need to take if I want to go to CM10 or back to stock?
Click to expand...
Click to collapse
If you're on AOSP (which includes CM10 and AOKP) then you'll need to reflash an ICS Touchwiz Kernel to go back to stock. You can go from CM10 to AOKP on the same kernel, depending on the merges. Sometimes new merges make it so an older kernel won't boot, etc.