I've been reading threads where recommendations are made to wipe 2-4+ times when switching ROMs.
My question: What's the point in wiping more than once?
Does "wiping" entail either an 'rm -rf' or an 'mkfs.ext3'? If it's an mkfs, then I really don't get it. If it's an 'rm -rf', well.. I still don't get it. Both effectively neutralize a filesystem (with some possible caveats to an 'rm -rf').
I'm not knockin' on the folks who recommend it, but is it really, absolutely necessary? I've never wiped more than once and never have an issue. Is there any non-anecdotal, objective reason why one should do it, other than to possibly satisfy a slight case of OCD?
Thanks for any input.
Some people believe that there is a bug in CWR that causes wipes to not complete. I personally only wipe once and haven't had issues. Wiping multiple times certainly shouldn't hurt anything though.
Sent from my ThunderBolt using Tapatalk
A-ha! Well that could certainly make one paranoid enough to want to wipe it 3 times if CWR isn't completing the wipe. Any idea on how CWR actually wipes? Perhaps I could just write my own pre-install.zip that I could use to wipe it myself. I know BAMF nukes Dalvik on install.
...bump...
Anyone know how CWM accomplishes it wipe? If there is skepticism about whether it works (without having to do it 3 times), I was going to write an update.zip that will make sure it's done right before I flash a ROM.
It basically just formats the partitions. A lot of ROM devs put the wipe script in their installation, so I would just recommend the one wipe before installing a ROM.
Sent from my ThunderBolt using Tapatalk
Related
Hello,
I rooted my eris about a month ago and have flashed about every rom thats been on grdlock's site. But one thing I've never been quite clear on is the whole wipe process. Can someone explain the difference between the factory wipe and the dalvik wipe? For instance why should i do one or the other or both before flashing a new custom rom?
HTC Droid Eris ROOT
Aloysious 2.0 v.7
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Can anybody help??
The factory wipe cleans the phones OS out, the dalvik wipe clears the cache. You don't need to know exactly what they do to know they definitely make ROMs run much cleaner when you do it, because I really dont know the specifics. I don't know how commands are programmed into DOS but I still know that the commands work...if that metaphor makes any sense.
PS - you should definitely do both before flashing a new ROM or restoring a nandroid backup
thanks taco. that helps a ton.
lol
chaneer said:
thanks taco. that helps a ton.
Click to expand...
Click to collapse
Sorry to let you down my friend.
factory wipe is like formating your harddrive on your computer before installing a new OS.
dalvik is a way to run multiple virtual machines where parts of the applications your running on android also run during normal operation to minimize memory and cpu usage, the cache obviously plays a part in memory usage, clearing this is like rebooting the ram on your computer to run faster.
in summary: format both and google your questions before asking them.
thanks guys. and trust me i did search all over for this but couldnt find a definitive answer. i just wanted to know for myself exactly what each "wipe-type" does, but i'll just stick with using both before i flash a new rom unless the dev instructs otherwise.
factory wipe is like formating your harddrive on your computer before installing a new OS.
dalvik is a way to run multiple virtual machines where parts of the applications your running on android also run during normal operation to minimize memory and cpu usage, the cache obviously plays a part in memory usage, clearing this is like rebooting the ram on your computer to run faster.
in summary: format both and google your questions before asking them.
Click to expand...
Click to collapse
Factory wipe is not wiping the os
...factory is like restoring the os, to how it came when you first got your computer, deleting all your programs, personal files, and stuff, that you added over the life of your computer.
You got cache down though.
Hope that makes it a little more clear.
Sent from my Eris using the XDA mobile application powered by Tapatalk
[ROM](7-19-11) SNS Gingerbread v1.4.1, OTA 4.24 Sense, Now W/ Remap Rosies.
Hey guys,
So I'm planning to flash the ROM at this URL: http://forum.xda-developers.com/showthread.php?t=1131217 but it requires that I "wipe" first. My rank says it all--I'm new to this stuff.
So, to the question; What should I wipe, and any tips on flashing this ROM?
Thanks,
Lacedaemon
Well, Its for a different phone, so I would say no.
First of all, Linux has a few different folders. /data is used to install all your apps and stuff, but /system is for the 0S and stuff. The /system section is restricted unless you gain root access. Anyways, /system isn't removed via factory reset, just /data. Installing a new rom, /system has files usually overwritten.... Hope that helps a little. The other folders are for cleaning up what's ever left over.
Yeah, I just flashed from EB01 SC 292 to ED01 MIUIWiz after full Data, Cache, Dalvik, and voltage double wipes, and restored all my old EB01 user Data and apps over MIUIWiz, all in under 17 minutes.
Edit: adding navenedrob's utility method has cut this down to under 10 minutes, plus navigation and reboot time. See post #5
How? Just followed what the Devs have taught us, plus Nandroid Advanced Restore in CWM.
I have been doing this for every ROM I have flashed since I discovered what a Nandroid backup was.
But this is not just a Nandroid Backup. This is a partial restoration called “Restore data” under “Advanced Restore.” All in CWM recovery.
Here is the method I use:
Charge to 100% (At this point, I started the timer)
Boot to Recovery
Wipe Cache and Dalvik (and Voltage for MIUIWiz) x2
Make a Nandroid backup
Wipe Data x2
Flash the new ROM (of your choice) in CWM
Let it boot
Boot to Recovery
Select “backup and restore”
Select “Advanced Restore”
Select the Nandroid Backup file you wish to restore from (probably your latest one)
Here is where it gets cool, and less scary…
There is yet another page, with options:
Restore boot
Restore system
Restore data
Restore cache
Restore sd-ext
+++++Go Back+++++
So no sweat yet
Select “Restore Data”
Reboot completely
Turn off phone (here is where I stopped the timer at 16.5 minutes)
Charge to 100%
Boot and enjoy.
BAM! All the old data is back. On top of the new ROM. Except for stuff that no longer applies, like maybe in-ROM launchers that no longer exist.
My ROM flashing evolution path has been:
Stock
Odin DXC DB/DO tar
EC01 DB/D0 (zip i think, can't remember)
Full ED01 (Adrynalyne method, not OTA)
ComROM 1.0 zip
Evil Fascination, all variants in sequence. Zip
EB01 SC 2.9.2 zip (Why? To see if it would work. Because it means restoring ED01 Nandroid data over an EB01 ROM. Without compromising the ROM. (Thanks for the assistance with this, Lttlwing16.)
ED01 MIUIWiz
Seems to work flawlessly so far. No forced closes, no hiccups, just sweet functionality. Every time so far. And so quick, I sometimes actually have time to use my phone between flashes.
As I said, I have been doing this for just about as long as I have been flashing through CWM. Your backup may overwrite some ROM theme elements, so that is something to think about.
Any other drawbacks? Not that I have found, but…Not completely sure yet, So… You know the drill…
DO NOT TRY THIS UNLESS YOU ACCEPT FULL RESPONSIBILITY AND ARE PREPARED TO DEAL WITH THE CONSEQUENCES!! YOU MAY LOSE DATA OR FUNCTIONALITY!! YOU MAY EVEN MANAGE TO BRICK THIS THING!
But you just made a complete clean-wiped Nandroid Backup, right? So you can always restore the whole thing. Or worst case, do the Odin recovery method. (or even worse case, Heimdall).
I suspect that there is some reason that this method has not been widely promoted already. It seems unlikely that it has not been experimented with, so maybe someone can help show a newbie the error of his ways. Or we may need someone with a thorough knowledge of Fascinate ROMs to add some warnings, caveats, or guidance around potential problems, etc. But it does seem to work just fine for me, and all of the ROMs I have worked with seem smooth and stable. All my apps always work, and update properly. Unless I get stupid and screw something up.
It does seem that Android should be able to pull this off if sufficient attention is given to file structure and dependencies, and if everything data can be kept where a data only restore would look for files. I suspect that I have been having success because of the good work of all the great ROM builders and developers working to fix the Fascinate, and make our experience all that it is. So if this works for you, they are the ones that really deserve the credit and the thanks. They made it work. I just followed instructions, got curious about Nandroid Advanced Restore, and pushed the right buttons. Oh, and wrote it all down.
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Well, I am expecting to learn something from posting this. So thanks. However, it raises more questions for me.
Does it mean that I never have actually needed to wipe data? I could have flashed all those ROMs without wiping data and without issues?
My understanding was that at least the cache would be re-written as needed by the new ROM, rather than trying to work with data created by the old one.
It sounds like it means that if bringing back the old data works, keeping the old data would have worked, too. So even Dalvik could have been left every time?
My thinking was that cleaning the cache and Dalvik before making the backup would mean that when restoring, they would come back blank, and not confuse the new ROM. I was under the impression that something was more likely to go wrong if all that stuff was left in there, and it was safer to bring it in later, after the ROM boots up, and give the new ROM a chance to properly recognize and deal with it.
Is there any logic in that logic? Just asking, because I really don't know. It sounds good.
If not, this thread is for educational purposes only.
But dang, either the Devs are even more awesome than we thought, or I must get lucky a lot. Because I have flashed quite a few ROMs without issues, force closes, etc.
Interested in more feedback on this process.
OK, I did have a couple of FCs of Gmail this last time flashing MIUIWiz, going from EB01 to ED01. It seemed to fix itself after I closed it twice, but I updated Gmail anyway. No repeats.
I have a new preferred method of backing up, cleaning the files, flashing new ROMs and restoring my data. Flashed MIUIWiz 111 over EF 360, the whole process taking about 10 minutes altogether plus navigation and boot time.
(Always create a clean Nandroid Backup (with wiped cache and Dalvik, possibly voltage) 4-5 minute process, not included. This should ensure that the new ROM will create its own compatible cache data after the restore.)
1. Run navenedrob's reformat utility [UTILITY]EXT4/RFS Formatter (CWM3 recovery packages) - xda-developers as a CWM zip from sd card <1 minute process.
2. Flash the new ROM in CWM <1 minute process.
3. Flash new Kernel if needed (before allowing ROM to boot) in CWM <0.5 minute process
4. Allow ROM to boot (3-4 minute process)
5. Nandroid Advanced Restore in CWM (Data only) (3 minute process)(Restores all User Data and apps)
From navenedrob: “Understand that this [format utility] will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device.” But it also puts things back in order if they have gotten screwed up. This could be the solution to issues you are having. Thanks, navenedrob! Very cool.
If there are particularly desirable user setups in the flashed ROM, be advised they may get lost in the restore.
The only issue I seem to have is the need to update/install Gmail. Then all is smooth.
Works for me, but you may totally bork yours. You are responsible for what you decide to do.
times_infinity said:
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I think that means wiping data also wipes Dalvik. So Dalvik wipe is redundant when wiping data. Good to know about the partition info. Seems to support the idea that wiping Dalvik before making the backup would ensure that when the restored data is brought back, it brings no Dalvik data with it, avoiding potential issues with the new ROM.
Hey everyone!
I'm new to the thunderbolt and love flashing roms. I used to use the nexus one and just curious what roms,radios, and kernels everyone uses? I'm a big fan of cm7 but wanted to hear everyone's take on what they like/dislike about their current ROM they are using.
Thanks to all who reply to this thread.
Sent from my VERIZON THUNDERBOLT using XDA App
shockaholick said:
Hey everyone!
I'm new to the thunderbolt and love flashing roms. I used to use the nexus one and just curious what roms,radios, and kernels everyone uses? I'm a big fan of cm7 but wanted to hear everyone's take on what they like/dislike about their current ROM they are using.
Thanks to all who reply to this thread.
Sent from my VERIZON THUNDERBOLT using XDA App
Click to expand...
Click to collapse
It's all in my sig. I've run Chingy's ROMs on my devices for a couple years now because they aren't pimped out, overworked, quirky, experimental ROMs. He strips out heaps of totally useless garbage, optimizes them in all the functional ways every other dev does, provides excellent mods, and bakes in the best kernels. His ROMs aren't FrankenROM projects like Synergy, and they aren't attempting to bend reality like uberBAMF. They're based on the most recent RUUs and they simply work, which is what matters most to me. I'm the kind of guy who'll wipe a ROM if just one thing I use a lot doesn't work right.
That sounds worth a try....can u direct me to that ROM? Also, is it worth to do a2sd with the chingy ROM? Thank you for the input...I like cm7 but I like effiencey. Thanks for your input...look forward to hearing your next reply...
Sent from my ADR6400L using XDA App
shockaholick said:
That sounds worth a try....can u direct me to that ROM? Also, is it worth to do a2sd with the chingy ROM? Thank you for the input...I like cm7 but I like effiencey. Thanks for your input...look forward to hearing your next reply...
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
I've always thought App2SD was kind of pointless unless you had a need too. If anything, it's more risky because your SDcard can become corrupted a number of ways and having apps out there puts them at risk. Chingy's ROMs can be found at themikmik.com. I've NEVER been a fan of AOSP primarily because of CM7. I've run 5 versions on my dInc and all of them have been unstable and quirky. My girlfriend uses it now and likes CM7, but it's a constant battle to keep it stable and running the way it should. The 2 versions I've tried on my Tbolt either had functionality problems or rebooted. I will not tolerate a ROM that reboots if there's any alternative out there that doesn't.
Thanks again for your input...soooo everything that works the way it should?4g..Bluetooth, Skype, navigation, etc. Also...just download the ROM and flash? And its good to go if I'm coming from the stock thunderbolt? You mentioned everything was baked in.
Thanks again!
Sent from my ADR6400L using XDA App
There are a couple of bugs in the leaked RUU on which the roms are based. One, no voice mail notifications (use google voice to work around that). Two, sometimes you cannot answer a phone call, you only get the option to end it. Not sure if there is a fix for that one. Otherwise the ROM (3D) was very stable for me and great battery life.
Sent from my ADR6400L using Tapatalk
Loonatik-
is your entire rom thats in your signature all baked with all the kernals and radios you have listed as well in your signature??
shockaholick said:
Loonatik-
is your entire rom thats in your signature all baked with all the kernals and radios you have listed as well in your signature??
Click to expand...
Click to collapse
Radios don't come in a ROM. You need to flash those separately through a different process. Otherwise, pretty much yes. The kernel doesn't come running at those speeds or the voltages I have set. I undervolt mine even more than stock. You can see my voltages in the pics I have uploaded to XDA, as well as the time-in-state.
I've never had the problem with the phone answering that some people talk about. As for Skype, voice mail... I've never had a use for any of it, so I can't tell you about it. I definitely suggest reading the thread for any ROM... just gloss over it and you'll see what issues people have with it pretty quick. None are perfect, but they WAY better than stock.
loonatik78 said:
Radios don't come in a ROM. You need to flash those separately through a different process. Otherwise, pretty much yes. The kernel doesn't come running at those speeds or the voltages I have set. I undervolt mine even more than stock. You can see my voltages in the pics I have uploaded to XDA, as well as the time-in-state.
I've never had the problem with the phone answering that some people talk about. As for Skype, voice mail... I've never had a use for any of it, so I can't tell you about it. I definitely suggest reading the thread for any ROM... just gloss over it and you'll see what issues people have with it pretty quick. None are perfect, but they WAY better than stock.
Click to expand...
Click to collapse
So...I'm about to start flashing the chingy 3d rom...just a few questions if you dont mind answering...I currently have rom manager installed, and I'm using clockwork recovery.
This is the order I think from what I remember to do things..sorry In advance if I sound like a noob. I only flash roms every so often, so I forget some steps...
1. back up on clockword mod backup
2. wipe factory data
3. wipe cache partition
4.flash rom
5.flash radio (optional...where is the radio you are using loonatik? )
6.reboot
??????
also...when I did a back up just now..I get the following...
ClockwordMod Recovery v4.0.1.5
SD Card space free: 2912MB
Backing up boot image...
Backing up recovery image...
backing up system...
backing up data...
backing up .android_secure...
backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup Complete!
The line that worries me is the "No sd-ext found. Skipping backup of sd-ext."
Should I worry about this?
Again, sorry for the noob questions...
And thank you for continued support and help!
Don't worry about the extension on the SD card. It just means you don't have yours partitioned.
As far as wipe:
Wipe cache
Factory data reset
Advanced...wipe davlik
Mounts and storage...wipe system
Flash the rom
courtesy of my bolt and Tapatalk
shockaholick said:
So...I'm about to start flashing the chingy 3d rom...just a few questions if you dont mind answering...I currently have rom manager installed, and I'm using clockwork recovery.
This is the order I think from what I remember to do things..sorry In advance if I sound like a noob. I only flash roms every so often, so I forget some steps...
1. back up on clockword mod backup
2. wipe factory data
3. wipe cache partition
4.flash rom
5.flash radio (optional...where is the radio you are using loonatik? )
6.reboot
??????
also...when I did a back up just now..I get the following...
ClockwordMod Recovery v4.0.1.5
SD Card space free: 2912MB
Backing up boot image...
Backing up recovery image...
backing up system...
backing up data...
backing up .android_secure...
backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup Complete!
The line that worries me is the "No sd-ext found. Skipping backup of sd-ext."
Should I worry about this?
Again, sorry for the noob questions...
And thank you for continued support and help!
Click to expand...
Click to collapse
The SD-ext is nothing to worry about. No need to manually wipe cache as the factory reset/delete user data function does that. It's good to format /system though. You won't be flashing the radio through clockwork, if that's what you were thinking of doing. That must be done through the bootloader. The radio I'm using can be found in my q AND a thread at the top of the Q&A forum, along with flashing instructions. PM me if you have further questions. I'll respond faster.
ILMF said:
Don't worry about the extension on the SD card. It just means you don't have yours partitioned.
As far as wipe:
Wipe cache
Factory data reset
Advanced...wipe davlik
Mounts and storage...wipe system
Flash the rom
courtesy of my bolt and Tapatalk
Click to expand...
Click to collapse
why would it be good to have your sd card partitioned? just curious..and is needed for the chingy 3dROM
shockaholick said:
why would it be good to have your sd card partitioned? just curious..and is needed for the chingy 3dROM
Click to expand...
Click to collapse
It's used for partitioning the SDcard to use part of it for the system's native file system. Nothing requires it.
I'm sure most of you know what a super wipe zip is if you've owned other smart phones. It's a CWM flashable file that wipes data/cache and formats /cache, /data, and /system (usually twice or three times).
Is there any file like that for the S3 available yet? If not, if someone knows how, could you possible make one? I don't know how to code or develop but it seems like a pretty easy file to make considering all everything you need is already in CWM.
Thank you in advanced.
Hypercore said:
I'm sure most of you know what a super wipe zip is if you've owned other smart phones. It's a CWM flashable file that wipes data/cache and formats /cache, /data, and /system (usually twice or three times).
Is there any file like that for the S3 available yet? If not, if someone knows how, could you possible make one? I don't know how to code or develop but it seems like a pretty easy file to make considering all everything you need is already in CWM.
Thank you in advanced.
Click to expand...
Click to collapse
Wiping any of those 3 times is no different then wiping them once. Just a fun fact.
task650 said:
Wiping any of those 3 times is no different then wiping them once. Just a fun fact.
Click to expand...
Click to collapse
I know, but its a habit. Its just annoying always having to wipe them one by one. Also, is there any way to make it so theres only one "No" to choose from?
Hey folks! Quick stupid question that most of you will say "answered many times before, use the search" to:
What are the exact steps to flash a new radio? I have an MB860 running CM7-MROM connected to the Bell Canada network in Toronto, and every time an app tries to access the GPS, the data connection dies, and I have to reboot to get the data/H+/3G back. I read that someone else had the exact same problem, and fixed it by flashing "N_01.77.33P_can_bell.zip". My phone says it is currently running "N_01.07.05P" (under Baseband version).
I am assuming that I can use this radio because it says "bell canada" in the filename, but how exactly would I go about flashing it? I searched the forums, and some people are saying to use CWM to "install zip from sdcard" just like I would when I update MROM, while others say to first "wipe cache" <- what cache are they talking about? The dalvik cache?
Thanks for your help!
There is the "cache" partition too, you know...
You won't find any detailed instructions on how to flash radio since it is EXACTLY the same as flashing a ROM.
ravilov said:
There is the "cache" partition too, you know...
Click to expand...
Click to collapse
Yes, I know, that's why I'm asking which cache they are telling me to wipe.
ravilov said:
You won't find any detailed instructions on how to flash radio since it is EXACTLY the same as flashing a ROM.
Click to expand...
Click to collapse
Well I've found lots of detailed instructions, but some are saying to install it exactly like you would when flashing a ROM update (don't wipe any cache), and some are saying to "wipe cache" without specifying which cache.
moeburn said:
Yes, I know, that's why I'm asking which cache they are telling me to wipe.
Well I've found lots of detailed instructions, but some are saying to install it exactly like you would when flashing a ROM update (don't wipe any cache), and some are saying to "wipe cache" without specifying which cache.
Click to expand...
Click to collapse
Normally its wipe both. Easier way is extract the radio.img, make sure its called radio.img, fastboot flash radio radio.img
Sent from my MB860 using xda app-developers app
The /cache partition holds a part of dalvik-cache, so when you wipe /cache, you wipe a part of dalvik-cache too. (The other part is on /data.)
I'm not quite sure why so many questions about it though. If unsure, just wipe all the caches you come across. By definition, a "cache" is something that holds temporary information which can be easily rebuilt, so there's no harm in wiping it. You're just making it unnecessarily complicated...
ravilov said:
The /cache partition holds a part of dalvik-cache, so when you wipe /cache, you wipe a part of dalvik-cache too. (The other part is on /data.)
I'm not quite sure why so many questions about it though. If unsure, just wipe all the caches you come across. By definition, a "cache" is something that holds temporary information which can be easily rebuilt, so there's no harm in wiping it. You're just making it unnecessarily complicated...
Click to expand...
Click to collapse
Welp, apparently the people telling you to wipe the cache are making it unnecessarily complicated too, because I flashed the new radio ROM without wiping any cache, and it worked just fine!
And OH MY GOD I had no idea my Atrix could get a GPS lock so fast! It locks in under 5 seconds, EVERY TIME now! It used to take 2-5 minutes, it took so long that if I wanted to GPS track my ride, I'd first turn on the GPS mapping app and put the phone out on the patio table, and let it get a fix while I got ready to leave.
And best of all? I can use data/H+/3G AT THE SAME TIME as GPS! It used to be that as soon as an app started the GPS, the data connection died, and I had to reboot to get it back. Now I can actually use my phone like it was designed!