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.
Hello all
How often should you clear cache or fix permission using CWM?
Jim
Sent from my VEGAn-TAB using XDA
Personally I do it when ever the ROM that I am on starts acting a bit quirky. Which is not very often if you are running a stable build like VeganTab, CM7 or even the Froyo ROMs that have been out for a while. If you ever see yourself loading up a bunch of apps and running them allot. Over time you might would want to clear the cache and definitely fix permissions to get things back in order.
jweir said:
How often should you clear cache or fix permission using CWM?
Click to expand...
Click to collapse
They're not something you need to do often, or even occasionally, as part of some preventive maintenance regimen.
If you switch ROMs, then you will have to clear cache. Actually, it's best to do a "wipe data/factory reset" in CWM in this case--cache will get formatted in the process.
You would want to clear cache if you upgrade the current ROM; it is better, though, to instead wipe dalvik-cache. Similarly, if you upgrade an app manually--ie. not via the Market or the usual Android update process: eg. by overwriting an app in /system/app or /data/app and rebooting the system--you might want to clear cache.
You might have to clear cache after powering on the tablet after a long (weeks, months) period of inactivity. In this case, the battery will go flat and the system will lose its date and time--going back in time, so to speak. This might, in turn,cause cached data to go out of whack--though Android should take care of this normally.
The "fix permissions" step is needed even less. This link explains why you would want to use it: Again, it might be needed after a ROM update, and not otherwise. This means that doing a fix permissions after a SD card repartition or a wipe data/factory reset step is nonsensical--the fix_permissions script operates on existing data.
I was getting out of space on my internal phone, so I decided to clear wipe cache and dalvik cache through CWM, but I find i save a lot of space BUT some apps stop working, maybe they are lost. So was does this actually do? Why are the apps there, but can't work? :crying:
Ok, after rebooting they are actually working again, i didn't even lost any data (progress on games) but I am really concerned what does this really do??
rolo143 said:
I was getting out of space on my internal phone, so I decided to clear wipe cache and dalvik cache through CWM, but I find i save a lot of space BUT some apps stop working, maybe they are lost. So was does this actually do? Why are the apps there, but can't work? :crying:
Ok, after rebooting they are actually working again, i didn't even lost any data (progress on games) but I am really concerned what does this really do??
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Dalvik_(software)
When you reboot, Dalvik cache and Cache are re-created. So no space saved this way.
Feanor88 said:
http://en.wikipedia.org/wiki/Dalvik_(software)
When you reboot, Dalvik cache and Cache are re-created. So no space saved this way.
Click to expand...
Click to collapse
I was wondering what wiping the Dalvik cache did, too. I installed an inverted app and someone told me I needed to wipe the Dalvik cache in order for it to remain in place after a reboot, so I did that. Now my phone says "Optimizing apps..." It must rbe e-creating the cache.
As far as I know, when a rom boots up for the first time Dalvik goes through each & every apk's & extract the Dex & put it in the cache. So probably it is a location of all apks. If dalvik cache is not wiped after a new rom is installed,dalvik cache will skip because it founds the dexed cache files attach to the directory. The result is "Force close" issues.
So wiping dalvik cache can be done without any problem many times within the same rom & that's why is shows "optiming apps" after a dalvik cache wipe.
saqib nazm said:
As far as I know, when a rom boots up for the first time Dalvik goes through each & every apk's & extract the Dex & put it in the cache. So probably it is a location of all apks. If dalvik cache is not wiped after a new rom is installed,dalvik cache will skip because it founds the dexed cache files attach to the directory. The result is "Force close" issues.
So wiping dalvik cache can be done without any problem many times within the same rom & that's why is shows "optiming apps" after a dalvik cache wipe.
Click to expand...
Click to collapse
Thanks! That's in line with my suspicion, except I didn't know when I posted my question that an apk file was nothing but a zip file that contains a dex (Dalvik executable) and a bunch of other files. Your explanation makes sense. I also noticed that if I install an individual app from a zip file using CWM Recovery, then it clears the relevant part of the Dalvik cache for me. That doesn't happen when I install an apk file directly using Root Explorer.
guys one line question i am performing "Wipe cache and dalvik-cache" will my phone internal memory be deleted ? thanks a ton
deepankarbu said:
guys one line question i am performing "Wipe cache and dalvik-cache" will my phone internal memory be deleted ? thanks a ton
Click to expand...
Click to collapse
Nop, it will not
Sent from my SK17i using xda premium
Phone didn't boot after wiping Dalvik Cache
Hi Geeks
i have an Xperia Arc S modded with Cyanogenmod JellyBean 4.1.2 Cooked ROM
i had alot of memory issues as applications keep closing whenever system runs out of memory, it is always obvious in the DSP application with the walkman in addition to visualizations inside the walkman
i searched for a solution and some told me that wiping the dalvik cache might solve the problem, so i gave it a try and rebooted in CWM recovery mode "built inside ROM" , cleared the Dalvik cache , and the phone keeps displaying the Xperia Logo without any further progress, as if it's in somekinda loop !
any idea what to do next without wiping my Data ? thank you all
BR
AMR
Koptanov said:
Hi Geeks
i have an Xperia Arc S modded with Cyanogenmod JellyBean 4.1.2 Cooked ROM
i had alot of memory issues as applications keep closing whenever system runs out of memory, it is always obvious in the DSP application with the walkman in addition to visualizations inside the walkman
i searched for a solution and some told me that wiping the dalvik cache might solve the problem, so i gave it a try and rebooted in CWM recovery mode "built inside ROM" , cleared the Dalvik cache , and the phone keeps displaying the Xperia Logo without any further progress, as if it's in somekinda loop !
any idea what to do next without wiping my Data ? thank you all
BR
AMR
Click to expand...
Click to collapse
Are you sure you only wiped the dalvik?
Sent from Myushi
clears app cache
rolo143 said:
I was getting out of space on my internal phone, so I decided to clear wipe cache and dalvik cache through CWM, but I find i save a lot of space BUT some apps stop working, maybe they are lost. So was does this actually do? Why are the apps there, but can't work? :crying:
Ok, after rebooting they are actually working again, i didn't even lost any data (progress on games) but I am really concerned what does this really do??
Click to expand...
Click to collapse
it clears the app running cache stored in os.
absolutely ..
XperienceD said:
Are you sure you only wiped the dalvik?
Sent from Myushi
Click to expand...
Click to collapse
Yes sir it's only the dalvik cache, both ways this ROM was pretty heavy and i'm not satisfied with the reboot every 2 or 3 hours of use, i will install xperia ultimate HD ROM, they say it's pretty stable and has no problems, and it has the sound enhancements i needed in the Jellybean cooked ROM
thanks for your reply
alcatel 918n
XperienceD said:
Are you sure you only wiped the dalvik?
Sent from Myushi
Click to expand...
Click to collapse
My phone also has those options built-in. If you did the dalvik only it should get back to where you have the icons. BUT, if you did something else aside from the dalvik, my guess would be goodbye data and hello to phone repairs. Please research first before you do anything on your phone. Your phone and my phone have very powerful built-in tools. It could brick the phone. I hope you did not wipe data and flash.
help! my phone's boot taking too long
i wiped /cache and dalvik cache and format /cache. it's taking took long. been waiting for almost 1 hour.
Lucky Patcher Dalvik-cache
I am getting out of space msg when using Lucky Patcher.....apk will be patched on boot......it says to clear dalvik cache to save space.....is this a good idea(will I loose any data from game etc?) or this a issue with lucky patcher?
Clearing Dalvik
Feanor88 said:
When you reboot, Dalvik cache and Cache are re-created. So no space saved this way.
Click to expand...
Click to collapse
Um, that would involve the re- "optimization" process at each boot. Depending on the number of apps you have installed, this process can take an hour.
Simply put, the Dalvik cache is where a virtual machine program (like VMware Player, Workstation or Fusion or MSVM) called "Dalvik" stores information the applications on your device request it to. This storage is for the purpose of making app load times shorter, but because it's all low-level stuff, it has to be loaded prior to the AndroidOS frontend...Fortunately, this cache only needs to be rebuilt when a flag has been set indicating the need, which is set whenever the cache is cleared. Note the distinction between "loading" and "rebuilding" this cache. "Load" is synonymous with "read" and "rebuild" means "write." So time-wise it is the distinction in effort between reading a book and writing one.
Typically I only clear it for troubleshooting reasons; if something is not working. The latest Cyanogenmod has a major problem where the desktop data is liable to randomly corrupt.
Typically, the only solution is a Dalvik wipe in CM or whatever. If you have recently installed a large number of apps(over twenty)then it might be best to clear the cache via recovery at the next cold boot, especially if your device does weird stuff like getting hot, discharging while plugged in to the OEM charger, widgets crash spontaneously, wallpapers are replaced by defaults, etc....Some of these symptoms can also indicate a virus or malware infection,(especially on custom ROMs or rooted devices) so diagnosis is differential.
But essentially there is no harm in re-building the Dalvik cache, other than the time taken to do so.
Koptanov said:
Yes sir it's only the dalvik cache, both ways this ROM was pretty heavy and i'm not satisfied with the reboot every 2 or 3 hours of use, i will install xperia ultimate HD ROM, they say it's pretty stable and has no problems, and it has the sound enhancements i needed in the Jellybean cooked ROM
thanks for your reply
Click to expand...
Click to collapse
CM has this new MAJOR stability issue, it seems. The random crashes and reboots will soon combine(if they haven't already)with the deletion of your desktop customizations and your widgets will begin vanishing forever. Not even a full wipe and rebuild will bring them back.
Been using AOKP on Nexus 7 2013 for a month now. It is based on CM, but it is way more stable.....haven't needed to re-boot in two weeks! Uptime, baby!
UPDATE 04/05/2014: Been running without rebooting for over a month, now. AOKP is definitely WAY more stable than any other ROM I've used.
Dalvik explained
Saqib Nazm said:
As far as I know, when a rom boots up for the first time Dalvik goes through each & every apk's & extract the Dex & put it in the cache. So probably it is a location of all apks. If dalvik cache is not wiped after a new rom is installed,dalvik cache will skip because it founds the dexed cache files attach to the directory. The result is "Force close" issues.
So wiping dalvik cache can be done without any problem many times within the same rom & that's why is shows "optiming apps" after a dalvik cache wipe.
Click to expand...
Click to collapse
There is a full explanation of the dalvik cache on wikipedia.
The wiki entry fully explains dalvik cache and the integral part it plays in your android system. In very simple terms, it is a cache that allows the system to talk to the exe of a program without the need to load the cache on each and every start. The dalvik is is loaded once, and then never again (unless you wipe the dalvik cache, in which case, it is rebuilt upon reboot). There is no affect on any given program when the dalvik cache is wiped, other than starting slower the first time it is started after the wipe.
Related (I think) - Samsung Galaxy S5 running CM 12.1 latest nightly (6-14). I started on CM 12.0 nightlies in March or April and transitioned to 12.1 within a day or two acter it showed up. That was a relatively noticeable transition requiring new gapps and a factory reset as I recall. I read somewhere that wiping cache and dalvik cache was unnecessary between one 12.0 nightly to another and between one 12.1 nightly to another, so I typically have not performed the cache and dalvik wipe during nightly upgrades, of which I've probably done 30 or 40 since I started on 12.0. After each nightly update flash, when I ask TWRP to reboot the system, without wipes, all my 160 or so apps are optimized, taking some time, before the noot is compete. This morning out of curiosity, after the nee ROM was flashed, I chose the option in TWRP to wipe the cache and dalvik cache before I askefasked TWRP to reboot the system. The wipe process took at least as long to complete as a typical optimization, and when I rebooted, I still got the lengthy optimization. So I'm tbinking either there's no relationship berween app optimization and wiping the caches, or CM and/or TWRP automatically wipes the caches whether I do or not.
---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------
Please forgive typos in my previous post - SwiftKey or something is making proofreading and editing difficult today.
Not the exact answer, but may interests u.
Koptanov said:
Hi Geeks
i have an Xperia Arc S modded with Cyanogenmod JellyBean 4.1.2 Cooked ROM
i had alot of memory issues as applications keep closing whenever system runs out of memory, it is always obvious in the DSP application with the walkman in addition to visualizations inside the walkman
AMR
Click to expand...
Click to collapse
Hi, I do not have the exact answer. But I wanted to share my own observation. When I wipe dalvik caches through CWM recovery, I find my phone taking a long time to finish booting every time. Sometimes I thought it would not boot up, I removed the battery and tried to swith on and my phone boots up. I do not know why it happens, may be I had installed a large no of apps.
I've got Nexus 5 with bootloader unlocked , after few weeks security patch arrived and after the phone switched off and showed error symbol and when I entered recovery mode it showed that error in system/bin.sh files need some help here
hello actually i am intending with xda developers forum and using custom rom for almost 8 years. but the problem is i never know what does that wipe methods do. until now i just fallowed the instructions but i think i need to know .
i have 2 main questions.
1-) what are this wipe processes do (exacly what are they wiping)
a-)Wipe Data/Factory Reset
b-)Wipe Cache Partition
c-)Wipe Dalvik Cache
please give me proper explenation for each .what are they wiping ? and why we using them for ?
2-) A proper cleaning on my android device. as much as i use my device there is junk files, cropses and all other unnecessary files rolling up in times. so this is very disturbing. and i want to have a blank page only with my rom and my karnel + bootloader etc files i don't want anything more.
so question is this. what should i do to clean my device as this clean like having nothing except basic things ?
if any of you explaint this 2 questions for a dumb user i hope it will be very helpfull also other newbie android users. or the people like me ignorant for 8 years shame of myself
anyway thank you for your help and interests.
Quayron said:
hello actually i am intending with xda developers forum and using custom rom for almost 8 years. but the problem is i never know what does that wipe methods do. until now i just fallowed the instructions but i think i need to know .
i have 2 main questions.
1-) what are this wipe processes do (exacly what are they wiping)
a-)Wipe Data/Factory Reset
b-)Wipe Cache Partition
c-)Wipe Dalvik Cache
please give me proper explenation for each .what are they wiping ? and why we using them for ?
2-) A proper cleaning on my android device. as much as i use my device there is junk files, cropses and all other unnecessary files rolling up in times. so this is very disturbing. and i want to have a blank page only with my rom and my karnel + bootloader etc files i don't want anything more.
so question is this. what should i do to clean my device as this clean like having nothing except basic things ?
if any of you explaint this 2 questions for a dumb user i hope it will be very helpfull also other newbie android users. or the people like me ignorant for 8 years shame of myself
anyway thank you for your help and interests.
Click to expand...
Click to collapse
A. Wiping data/factory reset completly erases whats in /data,
Your apps, dalvik cache, app data and many others are wiped, but those i listed are the most relevant
With certain devices internal storage can be wiped such as Xperias because /data/media is where the internal storage is mounted however this is typically avoided with the recoveries we have
2. Wiping cache, the cache is typically used to store information or app data that isnt permanent however that can cause crashes or other kinds of issues after a mod instalation
3. Dalvik/art cache is used to store decompiled readable versions of the android apps installed meaning it can launch the app much quicker however if you dont wipe this, it can cause much more issues after installing a app mod lets say
Envious_Data said:
A. Wiping data/factory reset completly erases whats in /data,
Your apps, dalvik cache, app data and many others are wiped, but those i listed are the most relevant
With certain devices internal storage can be wiped such as Xperias because /data/media is where the internal storage is mounted however this is typically avoided with the recoveries we have
2. Wiping cache, the cache is typically used to store information or app data that isnt permanent however that can cause crashes or other kinds of issues after a mod instalation
3. Dalvik/art cache is used to store decompiled readable versions of the android apps installed meaning it can launch the app much quicker however if you dont wipe this, it can cause much more issues after installing a app mod lets say
Click to expand...
Click to collapse
so is there a way to clean my leftover media/data/etc.. in internal storage withouth touching rom files ?
Quayron said:
so is there a way to clean my leftover media/data/etc.. in internal storage withouth touching rom files ?
Click to expand...
Click to collapse
Your ROM is in /system so wiping data doesn't affect the system its self
You can wipe data but that wipes dalvik cache
Its probably better to wipe caches with a data wipe
Quayron said:
so is there a way to clean my leftover media/data/etc.. in internal storage withouth touching rom files ?
Click to expand...
Click to collapse
thank you so much.