After clicking advanced and the clear davlik cache option a message shows up that something could not be (either) found or mounted.
But I am still able to scroll down and clear the davlik cache and have it say "Davlik Cache Wiped"
Basically my question is do you have to mount a certain part of the phone so that clockwork can fully gain access and wipe the davlik?
Hand76 said:
After clicking advanced and the clear davlik cache option a message shows up that something could not be (either) found or mounted.
But I am still able to scroll down and clear the davlik cache and have it say "Davlik Cache Wiped"
Basically my question is do you have to mount a certain part of the phone so that clockwork can fully gain access and wipe the davlik?
Click to expand...
Click to collapse
The message you're seeing is a complaint that it can't mount sd-ext. If you have no sd-ext, then you have nothing to worry about.
Cool thanks man.
Related
It gives you the option to do so under advanced, but when you wipe it it doesn't give you confirmation that it wiped.
Same problem for battery stats
Doesn't for me
This is why many roms suggest using AR instead of clockwork, and why most times when you have an issue with a ROM, and say you already wiped, the first question you'll generally get is "did you wipe with clockwork or AR?"
fachadick said:
This is why many roms suggest using AR instead of clockwork, and why most times when you have an issue with a ROM, and say you already wiped, the first question you'll generally get is "did you wipe with clockwork or AR?"
Click to expand...
Click to collapse
So, don't use clockwork? Switch to AR in ROM Manager?
Or use CW through Recovery instead of through ROM Manager, at least until you have problems. I never have, and I've flashed plenty of ROMs, kernels, radios, etc. Even tested to see if dalvik was wiping correctly, and it was. But nobody cares about my anecdotal evidence, and there may be some issues that I've just dodged.
Regardless, there are several threads about this already.
SilverZero said:
Or use CW through Recovery instead of through ROM Manager, at least until you have problems. I never have, and I've flashed plenty of ROMs, kernels, radios, etc. Even tested to see if dalvik was wiping correctly, and it was. But nobody cares about my anecdotal evidence, and there may be some issues that I've just dodged.
Regardless, there are several threads about this already.
Click to expand...
Click to collapse
I've been using CW threw recovery.
But it never confirms the dalvik or batt wipe.
JG-1 said:
I've been using CW threw recovery.
But it never confirms the dalvik or batt wipe.
Click to expand...
Click to collapse
Doesn't mean it's not happening. But it also doesn't mean it's not not happening, either. All it means is that it's not confirming whether it is or isn't wiping, but it may or may not be wiping and just not telling you that it did. Or didn't.
ClockworkMod DOES indeed wipe the dalvik cache. I think the reason why many people are confused is that it only takes a second or two for the dalvik cache to wipe on CWM, whereas it takes longer on RA. However, the reasoning behind this is simple- most people wipe the cache partition before wiping the dalvik cache. When you wipe the cache partition, you are wiping everything on that partition, including the dalvik cache. So in essence, when people go to the Advanced menu in CWM to directly wipe the dalvik cache, they are essentially wiping a blank folder.
If you don't believe me, try this:
1. Reboot into recovery
2. Go to the CWM partitions menu and mount the cache partition
3. adb shell
4. cd /cache/dalvik-cache
5. Type "ls-a" and note all the files.
6. Exit adb shell
7. Wipe the cache partition in CWM
8. adb shell
9. cd /cache
10. Type "ls-a". This time there should be no dalvik-cache directory.
antiphon said:
ClockworkMod DOES indeed wipe the dalvik cache. I think the reason why many people are confused is that it only takes a second or two for the dalvik cache to wipe on CWM, whereas it takes longer on RA. However, the reasoning behind this is simple- most people wipe the cache partition before wiping the dalvik cache. When you wipe the cache partition, you are wiping everything on that partition, including the dalvik cache. So in essence, when people go to the Advanced menu in CWM to directly wipe the dalvik cache, they are essentially wiping a blank folder.
If you don't believe me, try this:
1. Reboot into recovery
2. Go to the CWM partitions menu and mount the cache partition
3. adb shell
4. cd /cache/dalvik-cache
5. Type "ls-a" and note all the files.
6. Exit adb shell
7. Wipe the cache partition in CWM
8. adb shell
9. cd /cache
10. Type "ls-a". This time there should be no dalvik-cache directory.
Click to expand...
Click to collapse
I posted this exact test and result a couple of weeks ago, with the same reasoning. People don't care, they believe what they want to believe.
It would be at least compelling if somebody from the other camp would post proof that CWM does NOT wipe their dalvik cache.
SilverZero said:
I posted this exact test and result a couple of weeks ago, with the same reasoning. People don't care, they believe what they want to believe.
It would be at least compelling if somebody from the other camp would post proof that CWM does NOT wipe their dalvik cache.
Click to expand...
Click to collapse
Other camp is always anecdotal. "I couldn't flash xxx Rom after wiping with clockwork, but I switched to AR, wiped, and was able to flash perfectly". Hell, I'm one of them, was only able to flash BS once I switched over to AR.
Sent from my blah blah blah blah
I always get the error saying: E: Can´t mount /dev/block/mmcblk1p2 (Invalid argument) whenever i try wiping dalvik cache...
I m on desire HD...is there AR already for DHD?
sphuyal said:
I always get the error saying: E: Can´t mount /dev/block/mmcblk1p2 (Invalid argument) whenever i try wiping dalvik cache...
I m on desire HD...is there AR already for DHD?
Click to expand...
Click to collapse
This is a 5month old thread, for the EVO, try taking your question to its own thread on the desire hd forums. http://forum.xda-developers.com/forumdisplay.php?f=754
sphuyal said:
I always get the error saying: E: Can´t mount /dev/block/mmcblk1p2 (Invalid argument) whenever i try wiping dalvik cache...
I m on desire HD...is there AR already for DHD?
Click to expand...
Click to collapse
Wrong thread, wrong section, wrong forum. DHD uses MMC instead of MTD, and Amon_RA has said he (so far) is only making Amon_RA Recovery for MTD devices.
I tried to manually flash ROMs by booting into recovery. But in order to do that I need to do a full wipe. But I am not sure for this particular "Wipe Dalvik Cache" option. I select it and it says E:Can't mount /dev/block/mmcblk1p2 (Invalid arguments)
But after I press Yes - Wipe Dalvik Cache is says Dalvik Cache wiped. Have I actually wipe that dalvik cache? =/
That's an error normally caused if you wiped data and cache then went onto wipe the Dalvik-Cache manually in the advanced menu.
What you are doing is trying to wipe it twice and it gets confused so throws up this error.
As a general rule you shouldn't need to use this advanced method if you have already wiped data and cache.
Not the best answer but I believe to be accurate.
Just use full wipe 1.3, saves loads of hassle for wiping between ROMs.
Depends on how often you update and change ROMs as has been discussed many times. This question was just asking about dalvik cache.
Sent from my Desire HD using XDA Premium App
Oh looks like I am wiping too much. haha. thanks guys!
Something to help newbies and the well versed alike. A list of linux/smartphone terminology to help you understand some of the acronyms, etc, used on the forums.
d33ps1x said:
Something to help newbies and the well versed alike. A list of linux/smartphone terminology to help you understand some of the acronyms, etc, used on the forums.
Click to expand...
Click to collapse
Full wipe means:
data/factory reset
cache wipe
dalvik cache wipe
wipe system in mounts and storage
wipe cache in mounts and storage
Wiping system is very important as a flash is usually an update to a different and improved system version! ( for instance from KKA to LA4).
When getting into a bootloop pull the battery, reinsert battery and go in recovery mode and wipe data/factory reset and cache and reboot, done
gee2012 said:
Full wipe means:
data/factory reset *CACHE WIPE
cache wipe *CACHE WIPE
dalvik cache wipe
wipe system in mounts and storage
wipe cache in mounts and storage *CACHE WIPE
Wiping system is very important as a flash is usually an update to a different and improved system version! ( for instance from KKA to LA4).
When getting into a bootloop pull the battery, reinsert battery and go in recovery mode and wipe data/factory reset and cache and reboot, done
Click to expand...
Click to collapse
Why would you format or "Wipe" the Cache partition 3 times? Just curious...
i got a bootloop after installing google apps. I've already installed cyanogen but after installing the Google Apps, cynaogenmod does startup and its a black screen.
Can you please help?
striker280 said:
i got a bootloop after installing google apps. I've already installed cyanogen but after installing the Google Apps, cynaogenmod does startup and its a black screen.
Can you please help?
Click to expand...
Click to collapse
this is no support thread. please use forum search. bootloop problem is known and easy to solve.
So I'm just curious here. I never messed with rooting and ROMS with my original Moto Droid, it started with my Droid Charge. I've always adhered to the rule of wiping the 'big 3' when doing a major change. Data Wipe/Factory Reset. Wipe Cache and Wipe Dalvik Cache.
My question is this; when doing a data wipe/factory reset, one of the steps listed during the process is formatting cache. Then when wiping the cache, it does and displays what appears to be a duplicate function it says "formatting cache".
So .... when doing a main 3 wipe, are we actually accomplishing the same thing by just doing a data wipe/factory reset and wiping the Dalvik Cache?
Hmm, if got it correctly then all you need to do is "wipe/factory reset" and "wipe dalvik cache". After doing so there's no need to format cache once again.
/system should be formated automatically when flashinging new ROM, though i do that manually. Justc in case.
Sent from my super Galaxy Nexus plus®
So, been running the nightlies and have noticed something since the latest M1.
I haven't narrowed down exactly WHEN it occurs, but it does occur often, I believe it's mostly when the screen is off though....
I'll receive a notification (gmail mainly, sometimes an sms) and my system goes nuts in that the haptic feedback is full force and gives double responses usually, followed by extreme lag to the point where I can't even answer calls if someone calls me. I am forced to restart, is this a current known issue? is anyone else having this problem?
BoredInIraq said:
So, been running the nightlies and have noticed something since the latest M1.
I haven't narrowed down exactly WHEN it occurs, but it does occur often, I believe it's mostly when the screen is off though....
I'll receive a notification (gmail mainly, sometimes an sms) and my system goes nuts in that the haptic feedback is full force and gives double responses usually, followed by extreme lag to the point where I can't even answer calls if someone calls me. I am forced to restart, is this a current known issue? is anyone else having this problem?
Click to expand...
Click to collapse
Fully wipe your phone...
Quasimodem said:
Fully wipe your phone...
Click to expand...
Click to collapse
What do you mean by "fully wipe"?
This procedure?
Wipe Data \ Factory Reset
Wipe Cache
Advanced => Wipe Dalvik Cache
Mounts and Storage => format /system & format /data & format /cache
Advanced => Reboot Recovery
Wipe Data \ Factory Reset
Wipe Cache
Advanced => Wipe Dalvik Cache
Mounts and Storage => Mount /system
Mounts and Storage => Mount /data
Flash ROM
Flash Gapps
Advanced => Fix Permissions
Reboot system now.
All steps must be followed
BoredInIraq said:
What do you mean by "fully wipe"?
This procedure?
Wipe Data \ Factory Reset
Wipe Cache
Advanced => Wipe Dalvik Cache
Mounts and Storage => format /system & format /data & format /cache
Advanced => Reboot Recovery
Wipe Data \ Factory Reset
Wipe Cache
Advanced => Wipe Dalvik Cache
Mounts and Storage => Mount /system
Mounts and Storage => Mount /data
Flash ROM
Flash Gapps
Advanced => Fix Permissions
Reboot system now.
All steps must be followed
Click to expand...
Click to collapse
Those look familar
You really don't have to do all that... Factory Reset, Wipe Cache, Wipe Dalvik, Format system, flash rom and gapps...
Quasimodem said:
Those look familar
You really don't have to do all that... Factory Reset, Wipe Cache, Wipe Dalvik, Format system, flash rom and gapps...
Click to expand...
Click to collapse
Did it anyway, that notification issue has stopped (thanks!), BT seems to be working OK....modem didn't change and now cell signal seems to be slightly worse than it was (LTE), but still acceptable. Trying out the newest modem to see if it helps any...