Hi
I was looking at some of these options on CWM and I was wondering if someone can explain what do these options do when click on them.
- Wipe dalvik cache?
- Fix permissions?
- Mount /efs or /data or /system etc
I especially see dalvik cache and fix permissions on the forums and always wanted to know what do those options do.
Thanks
New_here said:
Hi
I was looking at some of these options on CWM and I was wondering if someone can explain what do these options do when click on them.
- Wipe dalvik cache?
- Fix permissions?
- Mount /efs or /data or /system etc
I especially see dalvik cache and fix permissions on the forums and always wanted to know what do those options do.
Thanks
Click to expand...
Click to collapse
The dalvik cache is where applications are expanded and compiled on the fly, dalvik is google's answer to java, clearing the cache , refreshes your applications in a way that could clear up any wrong information/data in the cache.
Fix permissions does just that , it fixes the file system permissions to what they are supposed to be, this can sometimes get messed up if you mess around in the shell, or manually install files or apps..
Mount , again does just what it says, these partitions are not mounted by default in recovery, they get mounted as needed if you flash a update file, but sometimes if you need to modify the file system while in recovery, via adb, you would need to mount them to have access to them ... Also sometimes, I don't know why, when installing a theme or other zip via CWM, sometimes, they need to be mounted properly to allow the update to modify the files.
Never realized to ask and just followed instructions. This cleared it up! Thanks!
Sent from my SGH-T989 using xda premium
can someone also explain the differences between stock, stable and latest (or custom) recovery? what does each of them do exactly?
specifically when you flash a custom rom and want to wipe data and cache, should you use stable or latest recovery, and why? what's the difference?
edit: oops, i'm in the wrong forum! if my questions don't make sense, please ignore. otherwise much appreciate for any answer.
jh20 said:
can someone also explain the differences between stock, stable and latest (or custom) recovery? what does each of them do exactly?
specifically when you flash a custom rom and want to wipe data and cache, should you use stable or latest recovery, and why? what's the difference?
edit: oops, i'm in the wrong forum! if my questions don't make sense, please ignore. otherwise much appreciate for any answer.
Click to expand...
Click to collapse
Stock = What your phone came with from the manufacture (aka t-mobile)
Stable = Been thoroughly tested and is good for everyday usage
Latest = Updated bug fixes, designed for those who like to help devs oput and test/report back issues. Also for geeks who enjoy flashing such as I.
I'm sure many might have more to input but that is the basic run down.
Related
So i just flashed this rom. and everything worked fine including the ring. So after, i flashed diff mods and colors for the acer ring and also the fix (that was updated 6/2/12 i believe?
then after taking some screen shots. a pop up said,
system ui has stopped unexpecticly. or something like that.
and now the botton in the center is gone. So i cant use it at all.
Checked settings and it is enabled.
What should i do to fix? just reflash any acer ring or just the fix. or just flash the hole rom again?
trevor7428 said:
So i just flashed this rom. and everything worked fine including the ring. So after, i flashed diff mods and colors for the acer ring and also the fix (that was updated 6/2/12 i believe?
then after taking some screen shots. a pop up said,
system ui has stopped unexpecticly. or something like that.
and now the botton in the center is gone. So i cant use it at all.
Checked settings and it is enabled.
What should i do to fix? just reflash any acer ring or just the fix. or just flash the hole rom again?
Click to expand...
Click to collapse
Reboot into recovery then wipe cache, dalvik, fix permissions then reboot check the ring.
Tapatalked from my Galaxy S II.
pio_masaki said:
Reboot into recovery then wipe cache, dalvik, fix permissions then reboot check the ring.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ya. i got it working again.
i get nervous going into recovery to flash something. i already bricked my transformer tf300 last week. but i got it back up and running. i just get scared. I'm gunna do a noob mistake and permently brick one of my devices.
but i didnt wipe anything. i rebooted, but it was still gone, went in settings unchecked, checked acer ring, rebooted again then it was back
btw do you no how to change bookmarks in acer ring. too ur google/ chrome bookmarks instead of the stock ones?
I haven't noticed a way it seems to only show the stock browser, import them into the stock browser should put them on the ring too. Also delete from the stock any you don't want.
Huge edit: forgot to mention, any changes like flashing rings or mods etc. Should be followed by cache and dalvik wipe, and maybe fix permissions. That way old info is wiped so the new info can settle instead of it finding new info where it expects old info...make sense?
Flashing is fine provided you know what you're doing. Don't just do random things and you'll be OK. Only flash for your device, and mods meant for your rom, like the stuff civato posts for his FR rom. Recovery is safe as long as you use common sense and caution. If you don't know what something does, don't use it. Google it or ask, better to wait and know then guess and brick.
Generally always safe to do is wipe cache dalvik fix permissions. No data loss that you see occurs.
Safe if something broke and won't boot BUT you lose apps and settings is wipe data/ factory reset, done with wipe cache and dalvik and maybe fix permissions.
Wiping system wipes out android and you must flash a new rom or restore to boot into the system, and is always done with cache dalvik and data.
I strongly advise against partitioning from recovery if possible. If you must partition your SD card then use a PC tool not recovery. Don't initiate sd-ext wipes directly, if it happens on resets that's fine just don't do it by itself. I only mention this because on my phone we had a string of bricks due to bad recovery mapping and it was nuking our loaders instead. Stick to what I said and you're safe in recovery and flashing. I'm sure others can chime in with more info on this too.
Tapatalked from my Galaxy S II.
pio_masaki said:
I haven't noticed a way it seems to only show the stock browser, import them into the stock browser should put them on the ring too. Also delete from the stock any you don't want.
Huge edit: forgot to mention, any changes like flashing rings or mods etc. Should be followed by cache and dalvik wipe, and maybe fix permissions. That way old info is wiped so the new info can settle instead of it finding new info where it expects old info...make sense?
Flashing is fine provided you know what you're doing. Don't just do random things and you'll be OK. Only flash for your device, and mods meant for your rom, like the stuff civato posts for his FR rom. Recovery is safe as long as you use common sense and caution. If you don't know what something does, don't use it. Google it or ask, better to wait and know then guess and brick.
Generally always safe to do is wipe cache dalvik fix permissions. No data loss that you see occurs.
Safe if something broke and won't boot BUT you lose apps and settings is wipe data/ factory reset, done with wipe cache and dalvik and maybe fix permissions.
Wiping system wipes out android and you must flash a new rom or restore to boot into the system, and is always done with cache dalvik and data.
I strongly advise against partitioning from recovery if possible. If you must partition your SD card then use a PC tool not recovery. Don't initiate sd-ext wipes directly, if it happens on resets that's fine just don't do it by itself. I only mention this because on my phone we had a string of bricks due to bad recovery mapping and it was nuking our loaders instead. Stick to what I said and you're safe in recovery and flashing. I'm sure others can chime in with more info on this too.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
i thanked you for your last post i feel i owe you more thanks than replies you made specifically to me lol. yah i had no idea you had to wipe cache and dalvik and fix permissions. when flashing the acer ring. i thought only do that on roms. thats probably why my acer ring was giving me problems. havn't had one problem with it since i wiped.
but just to clarify, do you wipe cache/ dalvik before or after you flash (Acer ring for example) or both?
trevor7428 said:
i thanked you for your last post i feel i owe you more thanks than replies you made specifically to me lol. yah i had no idea you had to wipe cache and dalvik and fix permissions. when flashing the acer ring. i thought only do that on roms. thats probably why my acer ring was giving me problems. havn't had one problem with it since i wiped.
but just to clarify, do you wipe cache/ dalvik before or after you flash (Acer ring for example) or both?
Click to expand...
Click to collapse
Either or. Some say before flashing some say after. I do before and after but that's just because of my scripts doing it before I flash (full rom). Something like the ring I flash then wipe cache dalvik fix perms after, so any of the mods etc that are not rom installs. Full rom installs I full wipe before then flash everything then clear cache and dalvik. I only fix perms if I get FCs.
Tapatalked from my Galaxy S II.
I am not new to this, I have experience with rooting htc and samsung devices. I have also searched, and searched, and searched with no luck on this.
However, I am stumped on this phone. I am using ODIN to flash the S/U script, I can gain root, install CWM and install it. I can load a ROM but one of 2 things happen: when I boot it up I get stuck in a boot loop, or it won't even install in the recovery.
I have a few questions / statements:
WHY am I getting stuck in this boot loop?
I am wiping cache/dalvik before I install the new ROM.
I am installing the ROM on the SD card vs the internal memory, is that why?
I got stuck 3 times in the boot loop, and I have had to use ODIN to flash my phone back to stock to start over.
Thanks in advance for the help.
If you have searched, and searched, and searched you would have realized that this is not development related.
for someone who's been around then, you should first off know that this belongs in q&a, not development.
that being said, which recovery are you using? i don't think that's your problem but a little more info would be helpful. also, which rom are you trying to use? when you're wiping, try using this, it'll wipe everything necessary. you only mentioned wiping your cache's so maybe that's it? in any case, flash the file i linked, then your rom. check the md5 on it and make sure it's a match. after you reboot, let your phone sit for 10 minutes and hopefully all will be well.
http://www.youtube.com/watch?v=JmvCpR45LKA
Mercuri82 said:
I am not new to this, I have experience with rooting htc and samsung devices. I have also searched, and searched, and searched with no luck on this.
However, I am stumped on this phone. I am using ODIN to flash the S/U script, I can gain root, install CWM and install it. I can load a ROM but one of 2 things happen: when I boot it up I get stuck in a boot loop, or it won't even install in the recovery.
I have a few questions / statements:
WHY am I getting stuck in this boot loop?
I am wiping cache/dalvik before I install the new ROM.
I am installing the ROM on the SD card vs the internal memory, is that why?
I got stuck 3 times in the boot loop, and I have had to use ODIN to flash my phone back to stock to start over.
Thanks in advance for the help.
Click to expand...
Click to collapse
If you look in the darkside rom thread, and some of the other rom threads, you will see three recommended wipes: darkside super, kernel and darkside cache. I would suggest you do all three.
Sent from my SGH-T989 using xda premium
Here is a big problem as well. You wipe cache and dalvik AFTER you flash the rom. I usually do it before as well but always after. That's like wiping before you **** and not cleaning up after
Sent from my SGH-T989 using XDA
odin version
jabberbox said:
http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I used an old version I couldn't get the latest one to work. But it wouldn't even load for me. It been a min sence ive used odin. But my replacement phone is at the house I'll pm you the steps I'll take. Everyone else try to be nice even if you think the question is stupid. Try to show some love
sorry i read wrong. i thought you couldnt gain root. as far as boot loops follow darksides wipe method it work. as far as my replacement phone rooted after first boot. my usb port is broke on my old phone
anyone know how to get back to stock with out it?
sence we are asking crazy ass questions?
dam auto correct
Questions go in the Q&A section
To those of you who helped by answering my question, thank you.
To those of you who told me I posted in the wrong sub section, get over yourself. Especially the guy with 13 posts.
I am wiping cache/dalvik before and after.
I am using CWM from the market, so it should be the newest version.
Ill check out the darkside thread.
You really don't need to wipe dalvik cache after a fresh rom install, unless you didn't delete the data partition (wipe data). And you certainly don't need to do it before and after.
Wiping cache and dalvik cache is really only useful if you make changes to the system but don't want to format the data. This includes flashing themes, and other enhancements, because most of them are replacing system files. On your first boot the dalvik cache gets built. (This is why a lot of devs recommend letting it sit for a bit before using it, it's giving it time to build the cache.)
The reason they tell you to wipe dalvik cache is let's say you're installing a theme, and it replaces systemui.apk and framework-res.apk, located in the system partition. The dalvik cache is already built for these files, so in some cases if you don't wipe the cache you'll boot loop. When you wipe dalvik, you are letting it be rebuilt with the current files.
Also, while we're on the subject, another misconception I see alot of, you don't need to wipe the dalvik cache after you wipe data. Dalvik cache is located on the data partition, it's a folder there. If you wipe the data partition, you've already removed it. (Not to be confused with cache partition, which is used for different purposes. That is it's own partition.)
Hello there,
I was thinking to make a flashable CWM script that eliminates the necessary steps before changing a Rom. He script should have this content:
/format data
/format cache
/format system
/format Dalvik cache
Would it work? If yes has anyone such a similar script and share it please?
Thanks
First of all, wiping dalvik and system is redundant.
Wiping data wipes dalvik (/data/dalvik)
Also, when you flash a tom, it automatically wipes /system unless you're flashing an incremental update.
So why do you want this script when you have to push like 2 buttons anyway (factory reset/wipe data and cache)? The red be more trouble migrating to the flash able to wipe stuff than going to the wipe menu.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Also, when you flash a tom, it automatically wipes /system unless you're flashing an incremental update.
Click to expand...
Click to collapse
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)
Zepius said:
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)
Click to expand...
Click to collapse
If it doesn't wipe system to install the rom, then I don't know what you think it would be installing....I would question that 'dev ' that does that.
Sent from my Nexus 7 using Tapatalk 2
Zepius said:
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)
Click to expand...
Click to collapse
If the ROM doesn't wipe /system, then most likely you're flashing an incremental upgrade, or the dev doesn't know what in the world he's doing and you should probably steer clear of said ROM.
Also, AFAIK, all the gnex ROMs here at xda, rootzwiki, and cyanogenmod wipe /system.
Sent from my Galaxy Nexus using Tapatalk 2
I understand the knowledge shared here but better be safe and follow all four steps then be not sure? Or not?
Can someone help by providing such script please?
Search for the Android Revolution ROM in the dev section. IIRC they have some kind of script in the OP
Anyone can pass Wipe Script Flashable ZIP me to flash (for Baked ROM)?
Thanks!!
There's no need to wipe until after you're done
So i have flashed for awhile and never have encountered this problem. i was on lbj7 i went back to stock. did Ota upgrade to 4.1.2, rerooted flashed another rom and now all it does is forceclose. How do i clean the system completly so i can reflash a fresh clean install. I normally wipe Delvik+cache+ factory what else can i include to insure i have a 100% clean flash?. Any and all help is appreciated thanks!
Wipe internal storage will erase anything on the internal just as it states. What ROM are you trying to flash? Also what recovery do you have and is it up to date. If you want the ultimate clean install I do this, make sure the and if you need gasps or any other file is on the external card
Wipe data, cache, dalvick, system this removes the ROM, internal and maybe even format data. Flash ROM wipe cache and dalvick and if you need to gasps the wipe cache and dalvick the boot. But make sure your recovery is up to date, I use twrp which is on 2.4.4 right now. And you have the correct gasps if needed. Good luck.
Sent from my SPH-L710 using Tapatalk 2
Hey Thanks Giantay.. I am trying to reflash Goodness 9.0.4. Its forceclosing Touchwiz and Apex and all the other.. I seem to have a Wakelock aswell Media is stuck at 40% Battery Useage. I use Cwm. Maybe i should switch to Twrp..
thaset said:
Hey Thanks Giantay.. I am trying to reflash Goodness 9.0.4. Its forceclosing Touchwiz and Apex and all the other.. I seem to have a Wakelock aswell Media is stuck at 40% Battery Useage. I use Cwm. Maybe i should switch to Twrp..
Click to expand...
Click to collapse
To install TWRP the easiest way just download Goomanager from the Play Store here https://play.google.com/store/apps/...anager&feature=nav_result#?t=W251bGwsMSwyLDNd open it go to settings and select Install OpenRecoveryScript, This will download and install TWRP's newest recovery. You could also check the md5sum to see if it's a good download. Sometimes the files that you download are corrupted but I have never had it happen, and I have flashed endless amounts of ROMs on different phones, but it happens people say. I am unfamiliar with that specific ROM but try searching in the thread for it to see if anyone else has had similar experiences and have a way to fix it. Searching is your friend, search and read a lot will ussually solve your problem, and if you don't turn up anything don't be afraid to ask a question instead of doing something that might be unsafe or worries you.
I did as u suggested and just tried re flashing using Twrp. Awaiting Results as first boot aproaches. Thanks again for the helping hand.
Just a heads up. Try and hit the thanks button on these forums if people help you in any way. I don't really care about it but it helps some people especially devs and what not.
What is this?
Recovery flashable cache, Dalvik, and data wiping tools.
Why?
The script that wipes data should help prevent the problems experienced when different recoveries wipe data differently and with different options to choose from.
(Those that have typed in "YES" when wiping data know what I mean)
Why are there two?
One wipes cache & Dalvik.
One wipes cache, Dalvik, and data.
What data is wiped?
The data that is wiped should be all that is required for flashing ROMs (see below).
Media (your pics, music, etc) will not be deleted.
Feedback
Feedback from users that flash a lot of different ROMs (especially both TW and source built) will be useful in case there are any additional files and folders that need to be wiped.
Usage:
As always, flash at your own risk!
Flash in recovery
(these are most useful when using a recovery like TWRP where multiple zips can be queued for flashing)
A typical queue might be something like this:
1) Cache, Dalvik, and Data wiping tool
2) ROM
3) loki-doki
In case any devs want to add this to their ROM updater-script (most likely for an Aroma package), this is the code for the data wipe:
Code:
delete_recursive("/data/app");
delete_recursive("/data/app-asec");
delete_recursive("/data/app-lib");
delete_recursive("/data/app-private");
delete_recursive("/data/backup");
delete_recursive("/data/clipboard");
delete_recursive("/data/data");
delete_recursive("/data/drm");
delete_recursive("/data/log");
delete_recursive("/data/misc");
delete_recursive("/data/property");
delete_recursive("/data/system");
delete_recursive("/data/time");
delete_recursive("/data/user");
Download
Wipe_Cache_Dalvik_SGS4_v1.0
Wipe_Cache_Dalvik_Data_SGS4_v1.0
Wipe_Cache_Dalvik_Data_System_SGS4_v1.0
Thank you for this :good: what about formatting system though? Formatting system before a rom flash has solved many problems for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Planktron said:
Thank you for this :good: what about formatting system though? Formatting system before a rom flash has solved many problems for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
It would be redundant since all devs should format system in their install script.
Finally. :thumbup:
Sent from my SAMSUNG-SGH-I337 using xda premium
I have been meaning to thank you for this - I have used it a number of times already and found it to be very helpful. I am on OUDHS recovery - and while it would be better in some ways if I had TWRP because you can setup multiple files for flashing - it is still a big time saving tool when flashing any rom, update, kernel or theme on OUDHS/CWM. ANd it works beautifully.
I assume that I still need to wipe system when I want to do a totally CLEAN Flash - is that correct? If so - any thought of creating a third file that Wipes Data/Wipes System/Clears Cache and Clears Delvic Cache?
Or do you feel that is not needed?
Lol probably will implement this into my ROM once I put Aroma into it, if that's okay?
lol I love that part about "YES" i've seen too many users wipe their whole partiton and TWRP not be able to create one again (idk why) and then bootloops galore.
mocsab said:
I have been meaning to thank you for this - I have used it a number of times already and found it to be very helpful. I am on OUDHS recovery - and while it would be better in some ways if I had TWRP because you can setup multiple files for flashing - it is still a big time saving tool when flashing any rom, update, kernel or theme on OUDHS/CWM. ANd it works beautifully.
I assume that I still need to wipe system when I want to do a totally CLEAN Flash - is that correct? If so - any thought of creating a third file that Wipes Data/Wipes System/Clears Cache and Clears Delvic Cache?
Or do you feel that is not needed?
Click to expand...
Click to collapse
If devs are coding their install scripts properly, there is no need to wipe system (as I mentioned earlier with formatting system).
But...maybe I should make one just in case.
jetlitheone said:
Lol probably will implement this into my ROM once I put Aroma into it, if that's okay?
lol I love that part about "YES" i've seen too many users wipe their whole partiton and TWRP not be able to create one again (idk why) and then bootloops galore.
Click to expand...
Click to collapse
Absolutely you may use it. That's why I included the code.
Added zip to OP that will also format /system.
I wanted to thank you again for this tool - it has really been very useful and has saved me a ton of time and steps when flashing new roms and updates. Thanks - BIG TIME!