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.
Related
Well they just recently updated the Amon RA Recovery from 1.8.0 to 2.1.1
so if i could get some help.
they have the new features of wipe data,wipe cache,wipe sd card,wipe sd something,and then they have the wipe dalvik cache,data and factory reset and just wipe cache from last recovery.
So i need to know how to do a full wipe for a Rom
and a how to wipe correctly for a kernel or just flashing anything.
please.
dont flame=]
have a nice day.
anybody kno the new features of the new amon?
what are you looking to do, flash the new Amon?
If so then you need to just push that image to the phone. What I did was after I downloaded the new version i renamed it to something easy, like FILE01 or something. then just push it. Either terminal via your evo or do it using the CMD using adb shell
here is the commande to push it.
1. Copy recovery-RA-supersonic-v2.1.1.img to the root of your sdcard
2. start the terminal app or launch adb
3. su(press enter)
4. flash_image recovery /sdcard/(CHANGE TO WHATEVER YOU NAMES YOUR FILE TO ) .img(press enter)
5. reboot recovery(press enter)
If youre wondering what to do if flashing a new rom, I would do factory data reset twice, then do cache twice and dalvik cache twice. Make sure you have your rom on the root of your SD card. Put it on the first screen as the SD card comes up. Dont put it in a folder. Then do a update from zip and find it and flash it then reboot.
dkdude36 said:
anybody kno the new features of the new amon?
Click to expand...
Click to collapse
Yeah, its the usual except:
under
Wipe:
Return
Wipe ALL data/factory reset
Wipe /data
Wipe /cache
Wipe /sdcard/.android_secure
Wipe /sd-ext
Wipe Dalvik-cache
Wipe Battery settings
Wipe Rotate settings
Partition SD:
Return
Partition SD
Repair SD:ext
SD:ext2 to ext3
SD:ext3 to ext4
Mounts:
Return
Mount /system
Unmount /cache
Mount /data
Mount /sd-ext
Mount /sdcard
I think thats it.
oooh i just flashed it also has folder flashing capabilities and doesnt need signatures. not too shabby. would i give it the big 2.0? nope, but it is pretty nice.
hey guys youve all been great and helful, thanks...was wondering what caulkins format all is, what it does and is it just rom specific. meaning konis elite 3 says to flash it first, if i wanted to flash a different rom say myns or something will the c. format all interfer? thanks again
justintammy said:
hey guys youve all been great and helful, thanks...was wondering what caulkins format all is, what it does and is it just rom specific. meaning konis elite 3 says to flash it first, if i wanted to flash a different rom say myns or something will the c. format all interfer? thanks again
Click to expand...
Click to collapse
It is a flash that write all data and cache it us good to flash when going between roms and if you are having force close issues. When using it erases all your data witch means all your apps aswell
Sent from my unrEVOked using xda app
roscoenr said:
It is a flash that write all data and cache it us good to flash when going between roms and if you are having force close issues. When using it erases all your data witch means all your apps aswell
Sent from my unrEVOked using xda app
Click to expand...
Click to collapse
Well said! Thought I'd add: Use it in conjunction with your usual wipes. It's meant as an extra piece of protection against problems NOT as a replacement to your usual wipes.
blakeboys said:
Well said! Thought I'd add: Use it in conjunction with your usual wipes. It's meant as an extra piece of protection against problems NOT as a replacement to your usual wipes.
Click to expand...
Click to collapse
Yeah meant to out that but spaces thanks
Sent from my unrEVOked using xda app
Couple of things to add to the folks above:
1) It won't work on ClockworkMod Recovery 3.0 since it's an Amend script (update-script). Amon_RA 2.3 and below, and ClockworkMod 2.x both support amend and edify (updater-script and update-binary), so it will work for them.
2) Isn't needed on ClockworkMod Recovery 3.0 or Amon_RA Recovery 2.3 since each have the options to wipe all your partitions (albeit you have to wipe each partition separately. I personally nagged Amon_RA to put in the wipe /boot and wipe /system options).
3) It wipes everything on the phone's internal storage except the WiMAX partition (which would be incredibly stupid since it would wipe out everyone's WiMAX radio and keys!). What it really does is format /system (your ROM and system apps), /cache (the kernel and ROM's cache), /data (your apps, settings, app data, etc.), and dalvik-cache (which is usually on /data or /cache, and is the cache for the Dalvik VM; the thing that runs apps).
4) Your SD card, .android_secure (on the SD card, this is where apps that have been moved to the card via the Applications settings in Froyo or Gingerbread), and sd-ext (old style of moving apps and cache to the SD card WHICH SHOULD NEVER BE USED ANYMORE) partitions are left alone. THEY WILL NOT BE WIPED. So if you have any apps on your SD card (for example, all the Angry Birds games install to SD by default), you will have to wipe them manually.
thank you guys!
If you open up the zip and look at the update-script file, the following commands are listed in it
Code:
show_progress 0.1 0
format BOOT:
format CACHE:
format DATA:
format SYSTEM:
show_progress 0.1 10
To anyone with half a functioning brain cell, it should be obvious what each line does.
Post #5 says it well. The only thing I'd add is there really is little reason to do both wipe and this (esp with ra recovery 2.3). If you do the factory wipe option (first on the wipe menu), that will clear both the cache and data partitions. And since the data partition is already formatted, doing an addition wipe dalvik cache is really not necessary.
To the OP: Please use a more descriptive subject in the future. Almost passed this thread over because of it.
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!
i downloaded CM 10.1 RC 2 and attempted to flash and got the unlimited loader, so i went back into cwmod and whether it's flashing another rom, deleting cache using built in cache deletion, or using dark swipe cache deletion, it only ever performs the first action and freezes at that screen.
for example, 15 minutes ago i tried flashing SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip and all it has the screen has displayed for the past 15 minutes is:
ClockworkMod Recovery v6.0.1.5
-- Installing: /sdcard/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip
using the "wipe cache partition" option shows:
ClockworkMod Recovery v6.0.1.5
-- Wiping cache...
Formatting /cache...
and the screen stays on that until i take out the battery. any thoughts?
Same boat
I think I am in the same boat as you, but with CMR v6.0.3.1. Bonus is I haven't figured out how to get my computer to see my phone on USB in order to reflash stock using Odin.
One thing my previous searches turned up is INFAMOUS super wipe, which I believe is what we need to use with CM10.1 rather than DARKSIDE. Can any more experienced people confirm or deny?
Thanks
ixxalnxxi said:
i downloaded CM 10.1 RC 2 and attempted to flash and got the unlimited loader, so i went back into cwmod and whether it's flashing another rom, deleting cache using built in cache deletion, or using dark swipe cache deletion, it only ever performs the first action and freezes at that screen.
for example, 15 minutes ago i tried flashing SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip and all it has the screen has displayed for the past 15 minutes is:
ClockworkMod Recovery v6.0.1.5
-- Installing: /sdcard/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip
using the "wipe cache partition" option shows:
ClockworkMod Recovery v6.0.1.5
-- Wiping cache...
Formatting /cache...
and the screen stays on that until i take out the battery. any thoughts?
Click to expand...
Click to collapse
rhoegg said:
I think I am in the same boat as you, but with CMR v6.0.3.1. Bonus is I haven't figured out how to get my computer to see my phone on USB in order to reflash stock using Odin.
One thing my previous searches turned up is INFAMOUS super wipe, which I believe is what we need to use with CM10.1 rather than DARKSIDE. Can any more experienced people confirm or deny?
Thanks
Click to expand...
Click to collapse
While you are in download mode hook your phone up to the computer and see if it starts trying to download an odin driver or not. Mine did that one time for me. As soon as you go into download mode plug it in to see. If not redownload the adb drivers and while they are installing keep phone plugged in to usb. As far as darkside wipe you do not need that anymore and yes infamous wipe is better suited for your needs. In recovery can you access mount and storage option? if so, format data, format system. format cache, then flash new rom or recovery if possible. I do not ever dirty flash even though you can do it. I like to make sure every rom I install is clean so I always wipe cache, wipe dalvik, format data, format system, format cache, etc. Might seem like a lot to do but it always works for me.
richardlibeau said:
While you are in download mode hook your phone up to the computer and see if it starts trying to download an odin driver or not. Mine did that one time for me. As soon as you go into download mode plug it in to see. If not redownload the adb drivers and while they are installing keep phone plugged in to usb. As far as darkside wipe you do not need that anymore and yes infamous wipe is better suited for your needs. In recovery can you access mount and storage option? if so, format data, format system. format cache, then flash new rom or recovery if possible. I do not ever dirty flash even though you can do it. I like to make sure every rom I install is clean so I always wipe cache, wipe dalvik, format data, format system, format cache, etc. Might seem like a lot to do but it always works for me.
Click to expand...
Click to collapse
Apologies if I am hijacking the OP, maybe you can try these things too and tell us if you have different results?
Under mounts and storage, I was able to format /data and format /system, but the phone froze up while formatting cache:
ClockworkMod Recovery v6.0.3.1
Formatting /data...
Done.
Formatting /system...
Done.
Formatting /cache...
Click to expand...
Click to collapse
rhoegg said:
Apologies if I am hijacking the OP, maybe you can try these things too and tell us if you have different results?
Under mounts and storage, I was able to format /data and format /system, but the phone froze up while formatting cache:
Click to expand...
Click to collapse
I am not using cwm 6.0.3.1 so I don't know. I use a custom cwm by sk8terwitskilhttps://www.dropbox.com/s/d5zpq8tg5sznegg/cwm6027touch_v14.4.6_hercules.zip
You cannot use Darkside Superwipe on CWM6. It is compatible with CWM5.
Sent from Evils Cradle of Filth T999
alloycowboy said:
You cannot use Darkside Superwipe on CWM6. It is compatible with CWM5.
Sent from Evils Cradle of Filth T999
Click to expand...
Click to collapse
So how does he recover if he already made the mistake?
rhoegg said:
So how does he recover if he already made the mistake?
Click to expand...
Click to collapse
He has to re-flash a recovery with Odin. If that doesn't work, re-flashing a stock ROM with Odin will work.
It sounds like you have a problem with your USB port though, so I am not sure what you can do to fix your phone.
I was setting my overclock with setcpu and it shut down my galaxy gio, and when it rebooted it just kept on the blue circle of cyanogen mod.
I already flashed stock and it would keep on something like the blue circle of cyanogen mod. I flashed cyanogenmod a couple of times too. Already partitioned my sd card again and i already wiped everything a couple of times too...
Someone help, i have readed like hundreds of posts and nothing seems to work
When i flashed stock i used a flashable cwm recovery, because odin dont detect my gio.
Flash stock rom and than go into stock recovery and wipe everything.
Hit thanks if I help
Sent from cooperve.
Raxit k. Tandel said:
Flash stock rom and than go into stock recovery and wipe everything.
Hit thanks if I help
Sent from cooperve.
Click to expand...
Click to collapse
I already flashed, like i said in my thread and nothing happened, the problem seems to have no fix
taximo ben-hur
I have a similar problem or the same problem.
And solve it installing a new CWM only with 4ext.
Try that. Wpe everithing includind Dalvik cache.
And it should work.
__GOLD_ said:
I have a similar problem or the same problem.
And solve it installing a new CWM only with 4ext.
Try that. Wpe everithing includind Dalvik cache.
And it should work.
Click to expand...
Click to collapse
how do I install only with 4ext?
WtvWhoCares said:
I already flashed, like i said in my thread and nothing happened, the problem seems to have no fix
Click to expand...
Click to collapse
Try to flash the stock rom with odin, and when the infinite boot starts, enter in the recovery and wipe everything!
This should solve your problem :victory:
eskorpiao112 said:
Try to flash the stock rom with odin, and when the infinite boot starts, enter in the recovery and wipe everything!
This should solve your problem :victory:
Click to expand...
Click to collapse
Just yesterday i did that, but i cant wipe dalvik cache, when i select '' wipe dalvik cache'' it just pings for less than 1 sec and does nothing i dont know if that is the problem that doesnt let it work.
WtvWhoCares said:
how do I install only with 4ext?
Click to expand...
Click to collapse
your problem is really like I have before.
the only way is install with only ext4. The CWM is in this link http://forum.xda-developers.com/showthread.php?t=1421650
This file: signed_cwm-5.0.2.7-flashablezip-ext4only.zip (Flash from Recovery)
Select the one that have only ext4 reinstall the CWM and clean all again and wipe all including dalvik... will work after that.
Hope have help.
__GOLD_ said:
your problem is really like I have before.
the only way is install with only ext4. The CWM is in this link http://forum.xda-developers.com/showthread.php?t=1421650
This file: signed_cwm-5.0.2.7-flashablezip-ext4only.zip (Flash from Recovery)
Select the one that have only ext4 reinstall the CWM and clean all again and wipe all including dalvik... will work after that.
Hope have help.
Click to expand...
Click to collapse
Already had done that too...
zedbers delivery
WtvWhoCares said:
Already had done that too...
Click to expand...
Click to collapse
Strange, I have really the same problema.
Did you format the system?
With this CWM I can wipe dalvik with the other version 4ext +rfs I have that isue...
Sorry but my experience is only with one device and I have solvet in this way.
Good luck
_GOLD_
__GOLD_ said:
Strange, I have really the same problema.
Did you format the system?
With this CWM I can wipe dalvik with the other version 4ext +rfs I have that isue...
Sorry but my experience is only with one device and I have solvet in this way.
Good luck
_GOLD_
Click to expand...
Click to collapse
Friend, my problem is that i can't format /data or mount or nothing that involves /data like wiping dalvik cache and it makes my phone to dont boot
Descobri noutra thread que tambem es portugues
I'm also having the same issue
(Also im a newbie this was my first attempt at any flashing etc.)
installed signed_cwm-5.0.2.7-flashablezip-ext4only.zip
then installed Jelly Bread v5.0
was ok for a while and working but then i wanted to play with other ROMS (in this case i now wanted to try cm-10.1.4-GT-S5660-gio++.zip)
I enter recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, wipe batt stats
Then install cm-10.1.4-GT-S5660-gio++.zip
Then it hung for 35mins at loading blue circle screen.
I then took battery out and enter recovery, and attempt to wipe data/fatory reset and it says:
--Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/stl13
Formatting /Cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/ .android secure...
Data wipe complete
Also i cant wipe dalvik cache it just does nothing blinks 1 second then back to menu.
Anyone know what i can do to fix this please?
Thanks for any help in advance.
sevrennn said:
I'm also having the same issue
(Also im a newbie this was my first attempt at any flashing etc.)
installed signed_cwm-5.0.2.7-flashablezip-ext4only.zip
then installed Jelly Bread v5.0
was ok for a while and working but then i wanted to play with other ROMS (in this case i now wanted to try cm-10.1.4-GT-S5660-gio++.zip)
I enter recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, wipe batt stats
Then install cm-10.1.4-GT-S5660-gio++.zip
Then it hung for 35mins at loading blue circle screen.
I then took battery out and enter recovery, and attempt to wipe data/fatory reset and it says:
--Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/stl13
Formatting /Cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/ .android secure...
Data wipe complete
Also i cant wipe dalvik cache it just does nothing blinks 1 second then back to menu.
Anyone know what i can do to fix this please?
Thanks for any help in advance.
Click to expand...
Click to collapse
YOu have the right CWM (cwm-5.0.2.7-flashablezip-ext4only.zip)
Make wipe, and format system wipe dalvik cache.
And try again.
__GOLD_ said:
YOu have the right CWM (cwm-5.0.2.7-flashablezip-ext4only.zip)
Make wipe, and format system wipe dalvik cache.
And try again.
Click to expand...
Click to collapse
Cheers for reply, i cannot wipe date/factory reset nor wipe dalvik cache with any recovery.
when i try to wipe dalvik cache it just goes straight back to main menu
And when i try to wipe data it gives me the error:
E:format_volume: make_extf4fs failed on /dev/block/stl13
I have started my own thread as not to highjack this one but im pretty sure we have the same problem.
Thanks again
sevrennn said:
Cheers for reply, i cannot wipe date/factory reset nor wipe dalvik cache with any recovery.
when i try to wipe dalvik cache it just goes straight back to main menu
And when i try to wipe data it gives me the error:
E:format_volume: make_extf4fs failed on /dev/block/stl13
I have started my own thread as not to highjack this one but im pretty sure we have the same problem.
Thanks again
Click to expand...
Click to collapse
Is strange because I have the same problem and solve with CWM only ext4. Try with the rfs r something like that.
Did you make all the steps right?
I really can't help any more I'm new in this too.
And I use a Nexus 4, the Gio is the girfriend phone and I start to change something there becsause is too slow and break all the time.
Now I install there the Light Orange V7 and it's really good...
__GOLD_ said:
Is strange because I have the same problem and solve with CWM only ext4. Try with the rfs r something like that.
Did you make all the steps right?
I really can't help any more I'm new in this too.
And I use a Nexus 4, the Gio is the girfriend phone and I start to change something there becsause is too slow and break all the time.
Now I install there the Light Orange V7 and it's really good...
Click to expand...
Click to collapse
i have tried flashing stock roms+recovery then go to CWM rfs and wipe and still get same errors
did you use cwm-5.0.2.7-flashablezip-ext4only?
Do you think its possible my /dev/block/stl13 could be physically damaged?
sevrennn said:
i have tried flashing stock roms+recovery then go to CWM rfs and wipe and still get same errors
did you use cwm-5.0.2.7-flashablezip-ext4only?
Do you think its possible my /dev/block/stl13 could be physically damaged?
Click to expand...
Click to collapse
Yes I only use that CWM nothing more.
Maybe is damage. Becqau format he system I can do with any CWM onçy wipe the dalvik cache isn't possible.
So if you can do nothing for sure you have a hardware problema.
That happen's when your try put a custom ROM or the phone broken and after you try to solve it.