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.
Related
I just flashed the 8/15 version of PA and was wondering if i have to completely wipe everything just to update to 8/18?
It is always recommended to do so to avoid any problems. But you can flash without the wipes and if you run into many issues, wipe and reflash
Sent from my sweet & buttery Infuse
I just flashed the pa jb update without wiping anything and it caused a world of problems for me I had to wipe and and start fresh to have a smoothly running phone again !!! Hope that helps
Sent from my SGH-I997 using xda premium
Flashing Paranoid
stevenk007 said:
I just flashed the 8/15 version of PA and was wondering if i have to completely wipe everything just to update to 8/18?
Click to expand...
Click to collapse
You should not have to wipe data, just wipe cache and dalvik cache. However it is a better chance of no force closes or other problems if you do wipe everything between upgrades.
following the question above about upgrading, do I also need to reflash the kernel too?
Yes you would have to flash the OC kernel again.
Sent from my sweet & buttery Infuse
digitalsunshine said:
following the question above about upgrading, do I also need to reflash the kernel too?
Click to expand...
Click to collapse
Or, you can just replace the boot.img from the PA zip with the one from OC kenel zip file (i.e. extract all the files on your PC, replace the file, re-zip, and flash as per-norm).
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.
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
StayingSober said:
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
Click to expand...
Click to collapse
What kernels did you flashed? And with what ROM?
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
jmxc23 said:
What kernels did you flashed? And with what ROM?
Click to expand...
Click to collapse
Basically tried flashing any compatible kernel with the ROM I was running at the time. For example yesterday I tried flashing the KT747 kernel for Jellybean with the current ROM I'm running, which is the most recent Liquidsmooth 4.2.2 ROM. Still no success
Here is the latest liquid...
Nightly Builds 04/29/13 for d2att, d2spr, d2tmo, and d2vzw available on GooInsideMe
http://goo.im/devs/liquidsmooth/nightly/042913 These Builds Are Very STABLE!
View changes & bug fixes made to our source code here http://github.com/LiquidSmooth
This is quoted from liquid0624 in the liquid smooth thread.
Sent from my SCH-I535 using xda app-developers app
redKrome said:
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry for taking forever to reply, I originally posted this on my lunch break and am finally out of work to reply freely. Anyways, I tried what you said, and downloaded the BMS 3.4 kernel that states is compatible with the version of Liquidsmooth 4.2.2 I am running. Let's just say I yet again had to restore twice once because it did exactly what I stated above, where it gives me the splash screen saying it's running the custom kernel and doesn't boot any further after the Galaxy S3 screen. The first time, I flashed it and then wiped cache/dalvik and fixed permissions before booting up like everyone says you need to do after flashing a kernel, no success.
Then, I read in the kernel's thread that there is no need to do that for this most up to date release, it says you just have to flash the kernel and reboot like with any other zip file. Well that didn't work either, and was forced to restore a backup a second time! What could the problem be?! I'm using the most updated version of TWRP, I'm on the most updated nightly of the Liquidsmooth ROM, I'm using a highly confirmed working and compatible kernel, and following the directions to the T! When it comes to flashing a different ROM, modem, rpm, backup, etc. I have no problem whatsoever. But trying to flash a kernel has never been successful for me so far
Any help from anyone else? It's frustrating that I've never been able to flash any kernels to any ROM I've ever run
Sent from my Samsung SCH-I535 running Liquidsmooth 4.2.2
Im no expert on any of this but this is what i would do. Odin back to stock ROM and reroot and unlock bootloader. Id do this cause i would want a clean slate so i know there is no previous kernel/rom files that may be effecting something. Make a new nandroid backup then reflash the rom ya want to use. Once booted up and everything is running, restart the phone and boot into recovery. Wipe the dalvik and cache like normal then flash the kernel. Hopefully that would take care of the problem.
Only other thing i can think of is to maybe wipe data/factory reset like 2 or 3 times and wipe the caches again and reinstall your current rom. Then flash the kernel. Other than that im out of ideas. Hopefully someone can get your problem solved!
Sent from my SCH-I535 using xda premium
Hey there everyone,
I decided to make a new topic since my other thread had a way other issue. I want to have a custom rom of AOKP on my HTC one x. I've downloaded the file, installed CWM etc. Now my question is what Gapps do I need? Is it rom specific? I know that AOKP runs on android 4.2.2.
Do I need CyanogenMod 10.1.x 4.2.2 Gapps?
Pmage0wns said:
Hey there everyone,
I decided to make a new topic since my other thread had a way other issue. I want to have a custom rom of AOKP on my HTC one x. I've downloaded the file, installed CWM etc. Now my question is what Gapps do I need? Is it rom specific? I know that AOKP runs on android 4.2.2.
Do I need CyanogenMod 10.1.x 4.2.2 Gapps?
Click to expand...
Click to collapse
Most roms will have a link to the proper Gapps package within OP but yes, if it's a 4.2.2 rom, the cm 4.2.2 gapps should work fine.
Pmage0wns said:
Hey there everyone,
I decided to make a new topic since my other thread had a way other issue. I want to have a custom rom of AOKP on my HTC one x. I've downloaded the file, installed CWM etc. Now my question is what Gapps do I need? Is it rom specific? I know that AOKP runs on android 4.2.2.
Do I need CyanogenMod 10.1.x4.2.2 Gapps?
Click to expand...
Click to collapse
I believe you do if you flash the wrong version of GAPPS it can boot loop you.
Nexus 4 CyanogenMod 10.1.0RC2
exad said:
Most roms will have a link to the proper Gapps package within OP but yes, if it's a 4.2.2 rom, the cm 4.2.2 gapps should work fine.
Click to expand...
Click to collapse
Ah yes, http://forum.xda-developers.com/showthread.php?t=2052610 This first linked me to an enormous site with alot of Gapps which confused me. But once I scrolled down to check I could still find the Gapps that were reccomended for that build.
Excuse me for my impatience Carry on!
How do I perform a FULL wipe though?
Pmage0wns said:
How do I perform a FULL wipe though?
Click to expand...
Click to collapse
Reboot into recovery, do a factory reset, wipe /system/, and (optional) wipe the sdcard. Just remember that if you wipe the sdcard you will be wiping the zip files you were going to flash. So, you might want to do that part AFTER installing the Rom and gapps.
Sent from my HTC One X using xda app-developers app
A Full wipe consists of wiping: Cache, dalvik cache, system and factory reset in recovery.
TWRP 2.4+ seems to have issues wiping so if you get error messages or bootloops after doing a full wipe and flashing a new ROM, this could be why. TWRP version of choice is 2.3.3.1
Installing the wrong GAPPS will typically create Force closes when you boot up or try to launch and apps within GAPPS. I've never seen flashing the wrong gapps cause bootloops.
Shiizzzzzz, I flash every gapp package under the sun for every aosp Rom there is for the XL lol... My favorites are midnight gapps... Worked perfect on all roms.
Sent from my HTC One XL using Tapatalk 2
exad said:
A Full wipe consists of wiping: Cache, dalvik cache, system and factory reset in recovery.
Click to expand...
Click to collapse
I keep seeing advice like this on the boards, but doesn't the factory reset wipe both /data and /cache? I honestly want to know so I don't give people bad advice.
Regardless, good call on the twrp version.
Sent from my HTC One X using xda app-developers app
Duckman5 said:
I keep seeing advice like this on the boards, but doesn't the factory reset wipe both /data and /cache? I honestly want to know so I don't give people bad advice.
Regardless, good call on the twrp version.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes but redundancy never hurt anyone. Also, when you take into account the issues with both cwm and twrp across multiple devices, it's best to be overly cautious than not cautious enough. Sometimes I wipe it all twice just to ease my mind. If you read on Tweamwin's site, they also say that most ROM installs wipe the system partition so you should never have to wipe it, but I think we all know that's BS.
TWRP, CWM, ROMS, MODS, these are all developed by random people I don't know, who also have no part in the original manufacture/design of my device. Better to be safe than sorry, I always say.
Fair enough. I guess when you are dealing with stuff that could seriously mess up an expensive device a little caution can't hurt.
Sent from my HTC One X using xda app-developers app
exad said:
Yes but redundancy never hurt anyone. Also, when you take into account the issues with both cwm and twrp across multiple devices, it's best to be overly cautious than not cautious enough. Sometimes I wipe it all twice just to ease my mind. If you read on Tweamwin's site, they also say that most ROM installs wipe the system partition so you should never have to wipe it, but I think we all know that's BS.
TWRP, CWM, ROMS, MODS, these are all developed by random people I don't know, who also have no part in the original manufacture/design of my device. Better to be safe than sorry, I always say.
Click to expand...
Click to collapse
I agree 100%
I always do double wipes of everything before flashing something. And I wipe cache/dalvik after the flash too. I expect that's the reason I never have issues after booting my phone up.
Sent from my One XL using XDA Premium