Related
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
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'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.
hello. i installed android 4.2.2 via odin and i didn't wipe data/cache partition before upgrade. after a while i did a factory reset from settings and after that i wiped data partition from recovery. after that i tried to wipe cache partition also from recovery but an error appeared and the phone restarted.
So my question is: why when i try to wipe cache partition from recovery i have that error? if i use any aplication to wipe cache when the phone is booted to android there is no problem. also the cache can be cleared with no problem from settings/storage. The error came up only from recovery.
Thanks.
You are using stock recovery?
I tried wiping cache. But I didn't notice error. And yes it also rebooted itself, which I didn't ask it to. But my cache was cleared
Sent from my GT-I9105P using XDA Premium 4 mobile app
Brian_SGW_CM9 said:
You are using stock recovery?
I tried wiping cache. But I didn't notice error. And yes it also rebooted itself, which I didn't ask it to. But my cache was cleared
Sent from my GT-I9105P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes,i am using stock recovery. Well i did not try to wipe cache on 4.1.2, just on 4.2.2, so i do not know if on 4.1.2 is doing the same. Do you have 4.1.2 or 4.2.2? I also read that s4 users have the same error while wiping cache partition after updating their android. Could another flash solve the problem?
gabi_tz said:
Yes,i am using stock recovery. Well i did not try to wipe cache on 4.1.2, just on 4.2.2, so i do not know if on 4.1.2 is doing the same. Do you have 4.1.2 or 4.2.2? I also read that s4 users have the same error while wiping cache partition after updating their android. Could another flash solve the problem?
Click to expand...
Click to collapse
actually if it does the work, it doesn't really matter if it reboots itself after wiping cache, after all you only need it to wipe your cache, so if it does the job, then why let the problem bother you
Brian_SGW_CM9 said:
actually if it does the work, it doesn't really matter if it reboots itself after wiping cache, after all you only need it to wipe your cache, so if it does the job, then why let the problem bother you
Click to expand...
Click to collapse
agree with you, but how do i know if the cache is cleared if i have that error?
Go to settings. Storage.
There should be a column saying:
Cached data.
If it's a lot, then it's not cleaned
Sent from my GT-I9105P using XDA Premium 4 mobile app
Brian_SGW_CM9 said:
Go to settings. Storage.
There should be a column saying:
Cached data.
If it's a lot, then it's not cleaned
Sent from my GT-I9105P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
now its 60mb, but several days passed from the time i tried to wipe cache partition. yesterday i received a notification for a software update. it was 4.2.2 I9105PXXUBMI1, which replaced the one that i flashed with odin I9105PXXUBMG8. when i will have time i will try again to wipe cahe from recovery, maybe the problem is fixed with this new firmware.anyway, the phone is working oustanding the way it is. thanks for the answers.:good:
Hello,
I have a quick question. For some reason after I installed any lollipop ROM on my g3 on the 1st boot it sais android is upgrading like it would if you wiped the dalvik / art cache. Also for some reason some apps from the previous rom are still installed. My g3 has twrp 2.8.5.1 install. I figured to post this under the general questions and answer section to see if anyone has ever has had this happen. Does any one know why this happens or how to make it not.
Thanks
Sent from my LG-VS985 using XDA Free mobile app
clapper66 said:
Hello,
I have a quick question. For some reason after I installed any lollipop ROM on my g3 on the 1st boot it sais android is upgrading like it would if you wiped the dalvik / art cache. Also for some reason some apps from the previous rom are still installed. My g3 has twrp 2.8.5.1 install. I figured to post this under the general questions and answer section to see if anyone has ever has had this happen. Does any one know why this happens or how to make it not.
Thanks
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
wipe /system /data /cache /dalvik before flashing your new rom. "Android is upgrading" means dalvik cache is created on first boot.
its perfectly normal to happen like this!!
Its perfectly normal the OS is pre-compiling to make the most out of ART, this would happen allot when you have ART enabled and clear Dalvik Cache.
That makes since. Guess I still have to trying re installing cm 12 with out wiping the cache to dalvik and see what happens
Sent from my LG-VS985 using XDA Free mobile app
clapper66 said:
That makes since. Guess I still have to trying re installing cm 12 with out wiping the cache to dalvik and see what happens
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
No just do the normal wipe. Don't select the areas to wipe. Just factory reset it and it should clear just the cache.
On start up it will still do the "updating android" thing. Make sure your phones battery life is high and its not plugged in the charger. It will get really hot.