When you have flashed a rom and there are Nightly'ish Builds that you would like to flash, do you still have to wipe data/factorty reset,wipe cache partiton and wipe dalvik cache?
alabran86 said:
When you have flashed a rom and there are Nightly'ish Builds that you would like to flash, do you still have to wipe data/factorty reset,wipe cache partiton and wipe dalvik cache?
Click to expand...
Click to collapse
Usually if you're staying within the same area (like CM10 nightly to another) you don't need to wipe data. Just cache and dalvik (also known as a dirty flash). However, this seems increase the chance of having problems so some people always do a full wipe just in case. You definitely need to do a full wipe going from JB to ICS, ICS to JB, etc.
With small changes yes, do devs always tell u when there are big changes, no. Also it seems like when you get around 3-4 dirty flashes things get wonky no matter what. Best most reliable experience is always clean. And remember if u flash dirty dont post bugs until u confirm on a clean flash.
Sent from my SGH-I535 using Tapatalk 2
battery cache
Is it a good idea to clear battery cache every once in awhile? What is the main purpose for this option?
alabran86 said:
Is it a good idea to clear battery cache every once in awhile? What is the main purpose for this option?
Click to expand...
Click to collapse
Wiping battery stats is useless as stated by google developers. http://www.xda-developers.com/android/google-engineer-debunks-myth-wiping-battery-stats-does-not-improve-battery-life/
Thanks
Thank you very much for the helpful information Tonu42 and Zalithian!!
Related
Sorry, this might be kind of a noob question, but i see build 23 is out for CM7. If i flash the new build, do i need to totally set up my phone all over again?
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Genocaust said:
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Click to expand...
Click to collapse
Thanks. Ugh, i didn't even think about that when i flashed CM7. Seems like it is a real PITA to wipe every time and have to configure all the settings again.
I had good success on my move from stock -> Ice Glacier (un-crapwared stock) by making a full TitaniumBackup of -everything- and then restoring it app by app (along with settings). They are similarly built ROMs, and it worked well for me with minimal downtime. You may want to consider trying that if you are just changing between CM flavors, as I would presume they are mostly backward compatible with a few fixes/features here and there. At worst it may leave you with just system settings to redo.
When i flash a new CMNightly all i do is wipe the cache and the Dalv/Cache and i've yet to have any problems. If you are worried about wiping and restoring everything. you might want to look into Titanium Backup.
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
shortskoolbus said:
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Wiping the Cache and wiping the Dalv Cache will not reset the phone. Only a full wipe will do that.
To my understanding, a "full wipe/factory reset" in Clockwork Recovery will only clear /cache, /data, and Davlik cache. /boot and /system will not be touched. Some users moving from Froyo to Gingerbread have had problems with /system, and a wipe of /system (from within Clockwork Recovery or from adb) has solved some problems for people, beyond what a full wipe can do. Discussions are in the CM7 thread in the Application Development subforum.
I know, most people refuse to search for anything.
i usually wipe the Cache and the Dalv Cache when updating nightlies, but several times i've wiped nothing and just flashed the new one on top and its always worked just fine for me
I always do a full wipe when installing roms. Setting it up each time makes me think its a whole new phone which is cool.
You do NOT need to wipe when upgrading to a new version of the same ROM. I've probably flashed 10 no-wipe updates of cm7 on my phone and it's still perfectly stable, no force closes or anything.
Boot into recovery and wipe cache and dalvik cache before flashing. Give it a few mins to "settle" on the first boot, reboot again and you're good to go.
Worst-case scenario you'll just wipe and reflash anyway, and nothing lost.
Hi all. I recently got my Inspire and have flashed a few ROMS, finally settled on CM7.1 RC. I want to try out the nightly route, but not entirely sure what order to do it all in. This is what I think I need to do:
Go into recovery, format /cache, wipe dalvik cache. Flash nightly 144 over my current 7.1, flash the bbmod165bBFS.zip, then juwe11 script (does this get flashed each nightly?), then reboot. Is this correct, or am I forgetting anything? Do I need to flash gapps again? I already made a NANDroid. Thanks.
RampageRR said:
Hi all. I recently got my Inspire and have flashed a few ROMS, finally settled on CM7.1 RC. I want to try out the nightly route, but not entirely sure what order to do it all in. This is what I think I need to do:
Go into recovery, format /cache, wipe dalvik cache. Flash nightly 144 over my current 7.1, flash the bbmod165bBFS.zip, then juwe11 script (does this get flashed each nightly?), then reboot. Is this correct, or am I forgetting anything? Do I need to flash gapps again? I already made a NANDroid. Thanks.
Click to expand...
Click to collapse
you got it. i dont think you have to flash the script everytime and you will not have to flash gapps everytime. btw you dont have to wipe between nightlys just simply flash over
Thanks, I appreciate the quick reply. So I shouldn't bother to wipe cache and dalvik cache? I thought that was pretty much recommended before flashing the majority of stuff. Ok, so I'm off to flash this nightly.
I never wipe between nightlys. But if you ever do encounter problems, then wipe cache, dalvik cache then reflash
Sent from my Desire HD using XDA Premium App
I've always wiped cache and dalvic between nightlies. I don't know if it's needed but I've never had any problems with installs. It only takes a few seconds and it's never hurts to be safe.
Sent through the power of Cthulhu!
I flashed 144, no issues so far. Thanks to all of you for the replies. I ended up wiping cache and dalvik cache just to be safe. I know there's a change log, but has there been any changes of consequence over 7.1 RC that are noticeable?
I know the most easily noticeable is if you put a lock screen on you can disable the lockscreen. Plus from 143 on is now on 2.3.5 if I'm not mistaken which does have some slight tweaks.
Sent through the power of Cthulhu!
how much wiping is necessary on the nexus s when flashing roms and kernels? i've had a habit of wiping data/cache/dalvik 3 times each from my epic days when it only had a broken clockwork recovery to work with. is that a recommended procedure?
i also see that when you select wipe data/factory data reset in clockwork, it wipes cache. does this make the wiping cache step unnecessary when installing a new rom?
one last thing. . . every time i wipe dalvik cache the prompt delivers an error. is this normal? is anything actually being wiped?
thanks in advance for your help
v3rk said:
how much wiping is necessary on the nexus s when flashing roms and kernels? i've had a habit of wiping data/cache/dalvik 3 times each from my epic days when it only had a broken clockwork recovery to work with. is that a recommended procedure?
i also see that when you select wipe data/factory data reset in clockwork, it wipes cache. does this make the wiping cache step unnecessary when installing a new rom?
one last thing. . . every time i wipe dalvik cache the prompt delivers an error. is this normal? is anything actually being wiped?
thanks in advance for your help
Click to expand...
Click to collapse
Use dalvik-wiper.zip from morfic to wipe the dalvik on your Nexus S.
Steps to flash a rom, kernel:
wipe cache
wipe dalvik using dalvik-wiper.zip
flash rom/kernel
fix permissions
If you're having any issue, boot loops, wipe data.
wow i can't believe i went this whole time without ever actually wiping the dalvik. . . heh
thank you! armed with this info i couldn't resist the itch to do a clean install of my favorite rom/kernel
What exactly does this do? Every time I'm flashing a new ROM and I wipe/fix permissons I seem to hang at the boot screen. Am I hurting myself not doing this?
Sent from my SCH-I535 using xda app-developers app
You shouldn't have to fix permissions on a new ROM flash. In fact, running the fix permissions command is rarely needed. I would never make it a routine thing to do.
hallstevenson said:
You shouldn't have to fix permissions on a new ROM flash. In fact, running the fix permissions command is rarely needed. I would never make it a routine thing to do.
Click to expand...
Click to collapse
Agreed
Some more info would be much appreciated here; I realize there is info out there but I'm still not 100% sure *what* I'm actually doing besides following instructions when doing wipes to flash anything. Not hijacking the thread but I'll rephrase the Q and hopefully someone can help clear things up:
When I read thru various guides for flashing various updates including ROMs, Gapps, kernels, system MODs etc, it seems that the order of the wipe and the extent of the wipe differ even between the same ROM (different model phone, ports, etc).
Is there a "standard" wipe procedure/ order of steps for;
(a) flashing a ROM update (assuming same kernel, and gapps flash needed ontop)
(b) flashing a new ROM (from a different build and/or kernel)
(c) flashing a system MOD (ex: crossbreeder)
(d) flashing a kernel (update or new)
I know there are those who feel that OCD urge to wipe wipe rinse repeat for every little thing but I'm hoping someone can clear us n00bs up on *why* we are doing what we are doing. The *essential* wipes and the order of each, and what files/partitions is that wipe effecting.
One more to expand on OP's question;
When then *should* we fix permissions?
Thanks a ton
MichPRich said:
Some more info would be much appreciated here; I realize there is info out there but I'm still not 100% sure *what* I'm actually doing besides following instructions when doing wipes to flash anything. Not hijacking the thread but I'll rephrase the Q and hopefully someone can help clear things up:
When I read thru various guides for flashing various updates including ROMs, Gapps, kernels, system MODs etc, it seems that the order of the wipe and the extent of the wipe differ even between the same ROM (different model phone, ports, etc).
Is there a "standard" wipe procedure/ order of steps for;
(a) flashing a ROM update (assuming same kernel, and gapps flash needed ontop)
(b) flashing a new ROM (from a different build and/or kernel)
(c) flashing a system MOD (ex: crossbreeder)
(d) flashing a kernel (update or new)
I know there are those who feel that OCD urge to wipe wipe rinse repeat for every little thing but I'm hoping someone can clear us n00bs up on *why* we are doing what we are doing. The *essential* wipes and the order of each, and what files/partitions is that wipe effecting.
One more to expand on OP's question;
When then *should* we fix permissions?
Thanks a ton
Click to expand...
Click to collapse
There is no standard wiping procedure. At the bare minimum you should factory reset, wipe cache, and wipe dalvik cache for a ROM. In some instances a dirty flash may be recommended for an update, but not always. Others like to add steps to the reset, such as formatting system. I always clean flash for any rom by factory reset, wipe cache, wipe dalvik cache, format system, then flash rom. I usually flash a kernel without wiping anything.
Different developers have different opinions on what you should do and how efficiently it works. In my opinion, I think a lot of the multiple wiping procedures some developers recommend is unnecessary. However, if I'm running their ROM I will follow the instructions exactly so I can accurately report bugs to them if something comes up.
Fixing permissions is usually unnecessary, it has to do with rewriting app permissions to the kernel and will often fix issues involved with force closing. I really don't think it helps too much, but some devs like to recommend it. The reason it takes a long time to boot is because after you fix permissions, every app has to ask the kernel to run again. Which can take a while depending on how many you have installed.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
There is no standard wiping procedure. At the bare minimum you should factory reset, wipe cache, and wipe dalvik cache for a ROM. In some instances a dirty flash may be recommended for an update, but not always. Others like to add steps to the reset, such as formatting system. I always clean flash for any rom by factory reset, wipe cache, wipe dalvik cache, format system, then flash rom. I usually flash a kernel without wiping anything.
Different developers have different opinions on what you should do and how efficiently it works. In my opinion, I think a lot of the multiple wiping procedures some developers recommend is unnecessary. However, if I'm running their ROM I will follow the instructions exactly so I can accurately report bugs to them if something comes up.
Fixing permissions is usually unnecessary, it has to do with rewriting app permissions to the kernel and will often fix issues involved with force closing. I really don't think it helps too much, but some devs like to recommend it. The reason it takes a long time to boot is because after you fix permissions, every app has to ask the kernel to run again. Which can take a while depending on how many you have installed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Very good info, thanks.
I was unsure why my ROM (Dark Rootbox Nightly builds on usc) have us wipe/reset, wipe cache, and the final step in wiping dalvik comes *after* flashng ROM/gapps. But your response helps a lot ty again.
MichPRich said:
Very good info, thanks.
I was unsure why my ROM (Dark Rootbox Nightly builds on usc) have us wipe/reset, wipe cache, and the final step in wiping dalvik comes *after* flashng ROM/gapps. But your response helps a lot ty again.
Click to expand...
Click to collapse
It's simply personal preference on what the developer thinks is most efficient.
Sent from my SCH-I535 using Tapatalk 2
A lot of good info, thanks. What is stored in dalvik cache
Sent from my SCH-I535 using xda app-developers app
camf3xu said:
A lot of good info, thanks. What is stored in dalvik cache
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Dalvik cache is what actually runs an app. It stores a specific file after an app is installed to allow the app to run.
Sent from my SCH-I535 using Tapatalk 2
Does anyone have a zip that will wipe my phone clean so that I can install a new ROM? I have one for my GS3, but I was unable to find one for my One X. Even with a Google search.
Kelton Rivas said:
Does anyone have a zip that will wipe my phone clean so that I can install a new ROM? I have one for my GS3, but I was unable to find one for my One X. Even with a Google search.
Click to expand...
Click to collapse
You'll need to find the RUU for the firmware that your phone is currently on. Download the ruu to your computer. Plug in phone and boot into fastboot. Run the ruu on the computer and it will bring your phone back to 100% factory status.
It won't wipe your sdcard though. To get it squeeky clean, you'll need to format the sdcard.
Sent from my HTC One XL using Tapatalk 2
I think he's talking more along the lines of caulkins format all zip.
Try searching for that. It formats system, data and cache.
Sent from my HTC One X using xda premium
To be clear, you don't "need" any such zip in order to install a custom ROM. Some people believe such "Superwipe" zips are a cleaner way of doing it (and may also be useful if you are experiencing bugs after a ROM flash). But I've never used anything of the sort, and never had any issues.
Just wipe cache and Dalvik, then factory reset in recovery (do not factory reset in bootloader, as this corrupts the SD). Then flash the ROM. No need to format system, as this is done automatically when you flash the ROM.
By that logic, no need to wipe cache or dalvik either since factory reset does that. I find wiping system provides peace of mind and one thing to cross off when troubleshooting buggyness within a Rom.
Sent from my HTC One X using xda app-developers app
Yeah plus I'm sure I've seen ROMs that don't wipe system during the install script. I always wipe system, for peace of mind, seeing as it only takes a second.
Sent from my HTC One XL using xda premium
exad said:
By that logic, no need to wipe cache or dalvik either since factory reset does that.
Click to expand...
Click to collapse
Not sure, but I don't think that is true. I thought all factory reset did was format the /data partition (delete user data).
Also, wiping cache and Dalvik is completely harmless. They will just rebuild themselves when you reboot. There is literally no reason not to wipe them, in any number of circumstances. Wiping system . . . not so much.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
timmaaa said:
Yeah plus I'm sure I've seen ROMs that don't wipe system during the install script.
Click to expand...
Click to collapse
I've seen this on another device, but haven't seen or heard of it on this device. Although, of course I haven't flashed every ROM available.
Sure, it typically doesn't hurt to do wipe system. Although I've seen the all-too-common instance of the n00b randomly wiping things (including system) and then asking "why won't the phone boot" (umm. . .because you wiped the OS). Thus, I normally refrain for recommending to wipe system (at least without making it clear what that actually does).
In any case, my main point is that all the required wipes are available in recovery, and no special wipe "zip" is explicitly needed (although might help in certain instances, as I've already mentioned).
Isn't dalvik kept in /cache or /data?
redpoint73 said:
Not sure, but I don't think that is true. I thought all factory reset did was format the /data partition (delete user data).
Also, wiping cache and Dalvik is completely harmless. They will just rebuild themselves when you reboot. There is literally no reason not to wipe them, in any number of circumstances. Wiping system . . . not so much.
Click to expand...
Click to collapse
I'll be honest, I did use one for a while back when I used twrp. While it is kinda pointless, it is a lot faster adding it to the zip install list than going through every wipe/format option.
OT: I feel like I'm the only one using philz touch recovery. Anyone else using it? It's got a lot of nifty features.
jacobas92 said:
Isn't dalvik kept in /cache or /data?
Click to expand...
Click to collapse
I had to look it up, but apparently it is on /data. So Factory Reset should in fact wipe it.
I've probably always though of Dalvik as something that should be wiped separately, since you should (at a minimum) wipe cache and Dalvik when doing a "dirty flash". Than I just do it by habit when doing a "clean" flash.
As I already mentioned, most of us will likely agree that there is no harm in wiping things that are going to be wiped anyways "just in case".
As long as you aren't one of these folks that wipes /system, then asks why his OS is gone.