How do I clear dalvik cache on 2.3 Droid x ?
Thanks in advance
Sent from my ADR6400L using XDA App
If you're rooted, it's in recovery. Not sure about stock.
I read around and saw that you can get into the recovery menu with Droid X Recovery Bootstrap. Just turn off USB Debugging in the Development section of the Applications Settings.
Also, if that doesn't work I read that the D2 Recovery Bootstrap should work.
Sorry if these lead you on a wild goose chase, but it's was the only thing I could find.
It's in recovery under Advanced. You should see Wipe Dalvik Cache.
You can also use "Titanium Backup" to clear Dalvik cache.
Related
Alright this is killing me. First I tried to upgrade from the rooted gb leak to deodexed and it killed my phone, I had to spf it. I assumed it was because I wiped the phone a few times after installing it. ell, this time I decided to do it again but not wipe after the install. And what happened? Same thing as before, boot loop central.
Assuming I'm coming from the spf without a ROM installed, how the hell do I get the deodexed gb working?!
you need to sbf back to 2.3.340 then root it and use droid x bootstrapper to flash clockwork. then once you have clockwork mod then wipe data and install zip of gingerbread and should be set...let me know if you have more problems
Yeah, that's what I'm doing now. Do I go straight from 340 to GB deodexed?
Well thats f***ing great, I did what you said (flashed GB deodexed after clearing my data straight from rooting and bootstrapping the spf) and now my phone won't get passed the moto boot logo.
What now? I can't get into the bootstrap or the stock recovery
Be sure to wipe the dalvik in the advanced settings. I installed and didn't have any issues. Of course, whenever I install a new ROM I always, wipe the cache/user data, cache partition and dalvik. I switch ROMs at least weekly and have never had an issue with bootloops or stuck logos.
Bobby
I have the same problem. I have tried 5 times with the same results. SBF with 340 then root, dxbootstrap, reboot clear data, clear cache, clear dalvik cache, install GB from zip, clear data, clear cache, clear dalvik cache, reboot. Stuck at moto logo.
nnylyart said:
I have the same problem. I have tried 5 times with the same results. SBF with 340 then root, dxbootstrap, reboot clear data, clear cache, clear dalvik cache, install GB from zip, clear data, clear cache, clear dalvik cache, reboot. Stuck at moto logo.
Click to expand...
Click to collapse
Here's what you need to do:
SBF with 340.
z4root, install dx bootstrap and root it. go to the bootstrap bootloader, clear data and flash rooted GB.
Start up rooted GB, download Droid 2 bootstrapper and bootstrap it. Go to the D2 bootloader.
Flash GB Deodexed without clearing data. Then reboot.
thewanton said:
Here's what you need to do:
SBF with 340.
z4root, install dx bootstrap and root it. go to the bootstrap bootloader, clear data and flash rooted GB.
Click to expand...
Click to collapse
I get this far and it hangs on Moto boot screen every time. I give up.
You don't wipe between rooted gb and flashing deodex gb
Rooted Droid X loving Gingerbread...
Twitter: Sierra8561
nnylyart said:
I get this far and it hangs on Moto boot screen every time. I give up.
Click to expand...
Click to collapse
If you make it to this point, go to recovery wipe, then reboot DONT FLASH. that worked for me, then booted installed bootstrap and flashed deodexedgb
Rooted Droid X loving Gingerbread...
Twitter: Sierra8561
The Key that I think some are missing is that you need to install the RootedGB *before* the deodexedGB.
It looks like DeodexedGB only fixes /system. You need the first install to take care of all the other stuff.
Also note that thewanton mentioned Droid 2 Bootstrapper. It's been reported that DX bootstrap doesn't work with GB.
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Thanks! That worked! This was "undocumented" step I was missing.
Hey guys
I had started to use nightly builds. My question is should I have to wipe factory n Cache?
Sent from my Nexus S using XDA Premium App
Nope, if you continue to use the nightlies, just wipe dalvik cache,
If you come from different rom, just wipe data and cache and dalvik cache.
Once you are on the nightlies you never wipe anything. Don't listen to any nonsense about caches and dalviks just go to recovery, flash nightly, reboot!
Sent from my Nexus S using XDA App
Thank you.. do I have to wipe if I'm switching to different rom of same version?
Sent from my Nexus S using XDA Premium App
You're losing no data wiping cache and dalvik, why not do it then, it saves you from trouble.
rentaric said:
You're losing no data wiping cache and dalvik, why not do it then, it saves you from trouble.
Click to expand...
Click to collapse
Because it doesn't "save you from trouble." But I'm not going to argue about it. The OP asked if he had to wipe when upgrading nightlies and the answer is No.
Sent from my Nexus S using XDA App
Plz tel about this... Toll then do I have to wipe if I'm flashing different rom of same android version!?
Sent from my Nexus S using XDA Premium App
ancilary said:
Plz tel about this... Toll then do I have to wipe if I'm flashing different rom of same android version!?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes for different roms you must factory reset.
Sent from my Nexus S using XDA App
rentaric said:
You're losing no data wiping cache and dalvik, why not do it then, it saves you from trouble.
Click to expand...
Click to collapse
Correct.
matt2053 said:
Because it doesn't "save you from trouble." But I'm not going to argue about it. The OP asked if he had to wipe when upgrading nightlies and the answer is No.
Click to expand...
Click to collapse
You are so wrong. Of course he needs to wipe Dalvik and Cache even if he installs another nightly. Its because the new nighlties bring new apps versions, or new kernel changes. Deleting Dalvik and cache forces the Android to reload the Dalvik cache for all the apps. Also, it saves you from trouble of incompatibility or FC's.
ancilary said:
Plz tel about this... Toll then do I have to wipe if I'm flashing different rom of same android version!?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Different ROM same Android - wipe Data, Dalvik, Cache.
Same ROM same Android - wipe Dalvik, Cache.
brainmaster said:
Correct.
You are so wrong. Of course he needs to wipe Dalvik and Cache even if he installs another nightly. Its because the new nighlties bring new apps versions, or new kernel changes. Deleting Dalvik and cache forces the Android to reload the Dalvik cache for all the apps. Also, it saves you from trouble of incompatibility or FC's.
Different ROM same Android - wipe Data, Dalvik, Cache.
Same ROM same Android - wipe Dalvik, Cache.
Click to expand...
Click to collapse
Well you can have your superstitions but there is no rational reason to manually wipe your cache or your dalvik cache when upgrading CM nightlies, and that comes straight from the developers of the ROM who are more knowledgeable than I am. None of the CM devs have EVER suggested it, and when asked, have said that it is not something that should be done. I will take their word over yours.
EDIT: This is the closest I think we will find to a definitive answer: http://review.cyanogenmod.com/#change,4933
So, CM development team does not suggest a wipe of dalvik or cache when upgrading. The nightly installation instructions do not mention wiping dalvik or cache. I personally have flashed several hundred nightlies over the last year and have never wiped cache or dalvik when upgrading. Many many other users have flashed hundreds of nightlies each and have not wiped cache or dalvik and have not had problems. There is no reason to do this action, it is completely pointless. It is like saying "you must have your phone pointing to the east when you boot." Sure maybe it does not hurt anything but we don't really need to keep spreading this superstition.
EDIT: In re-reading this I feel like my posts come across as disrespectful and/or antagonistic. I simply disagree with what was said and I feel I have good reason to. But the OP can read about both points of view and then try for himself and choose what works best for him.
CWM recovery was developed from CM7 devs. So why do you think that they've integrated or made a option to wipe dalvik if that is not needed?
Especially if installing another kernel, wiping Dalvik is a must.
But you are right, the OP can choose himself either he will do that or not.
I don't think that your post is disrespectful and/or antagonistic, you have just expressed your opinion. If we don't discus issues with each other we are not gonna make any progress on learning.
brainmaster said:
CWM recovery was developed from CM7 devs. So why do you think that they've integrated or made a option to wipe dalvik if that is not needed?
Click to expand...
Click to collapse
There are lots of options in CWM recovery that are not needed when flashing
Like I said, in the link it is expressed very clearly that the developers of the ROM feel it is "completely pointless" (exact words) to wipe cache and dalvik when updating to newer CM build.
There are times when a user or developer might want to wipe cache or dalvik and so those options do exist. There are other partitions that a user or developer might want to format from time to time for various reasons as well. And the option to do those things is there in CWM recovery. But that does not mean they should be done every time, just because they are there.
In the link I posted, a submission was made to CM code to make it easier for users to wipe dalvik and cache and install a zip all in one command. The submission was rejected because the reviewers agreed that it was "completely pointless."
Why after so much time do you think "Wipe Dalvik Cache" is still obscurely placed in the "Advanced" menu of CWM Recovery? It would be very easy and simple to wipe cache and dalvik automatically when installing a ROM through CWM Recovery or at least put the option on the main page. Do you think that Koush just likes to give users a hard time? Do you think he wants it to be difficult for them to update their ROMs? I don't think so. I think he understand that it is an advanced function that can be useful in some circumstances but is not typically needed in 99% of cases.
The developers also note that the cache is invalidated via hashes automatically. So its basically auto wiped.
The only reason that I wipe is when the nightly contains a new kernel, dalvik should be wiped to eliminate possible problems.
Sent from my Nexus S 4G using Tapatalk
I want to clean and delete all data on my a500, just like when it comes from the store.
My tablet is rooted, do you advice me to wipe it by going to the menu settings, or should i do it in CWM?
In CWM what option do i use?
Thanks!
Learn how to flash a new rom on it. Google xda , find your device and look in android development for your device
sent on the flytouch 3 / superpad 2
Hello there. I usually follow the instructions in the install page for Virtuous Picasso. Just google "How to Install Virtuous Picasso ROM on Acer Iconia A500." It goes over how to install the custom ROM, but the pre-work is very detailed. The only thing missing in there is that you could/should also wipe the battery stats. It's in the Advanced menu under the "Wipe Dalvik Cache" option. I hope this helps.
use CWM, boot into recovery mode, then wipe data/factory reset, wipe cache partition, go to advanced: wipe Dalvik cache, wipe battery status, & don't forget to wipe your behind
Hey guys just a quick question about installing nightly builds on the nook. When Rom Manager asks whether to wipe data/cache and what not, if I select it, will it wipe the internal memory completely? leaving no user files behind? or will it only wipe the system files?
It will wipe everything and it will be a fresh install.
Sent from my LG Optimus V using Tapatalk
If you update, just wipe cache
It wipes the /data partition but doesn't wipe /sdcard /sd-ext or /met/emmc.
Sent from my MB860 using xda premium
EGM92 said:
Hey guys just a quick question about installing nightly builds on the nook. When Rom Manager asks whether to wipe data/cache and what not, if I select it, will it wipe the internal memory completely? leaving no user files behind? or will it only wipe the system files?
Click to expand...
Click to collapse
Just wipe Davlik.
if boot is longer than normal after wipe, it's normal!
votinh said:
If you update, just wipe cache
Click to expand...
Click to collapse
patruns said:
Just wipe Davlik.
Click to expand...
Click to collapse
So... just wipe Davlik Cache is what you guys are saying?
Good question helped out a newb here
Jiv_au said:
So... just wipe Davlik Cache is what you guys are saying?
Click to expand...
Click to collapse
Correct
Sent from my LG Optimus V using Tapatalk
Jiv_au said:
So... just wipe Davlik Cache is what you guys are saying?
Click to expand...
Click to collapse
Note: wipe cache and wipe Dalvik cache are 2 different things.
+ wipe cache is a quick way to clean the current running ROM
+ wipe Dalvik is a completely clean.
After wipe Dalvik, next time it boots, it will take a lot longer time due to the device has to re-compile the whole thing before ROM start running and booting.
I think I need to drop a few lines about wipe cache/Dalvik.
As I posted above, I said it wiped clean.
Apparently, I am NOT 100% correct.
I just updated to nb198, wiped cache (formatting /cache) then wipe Dalvik cache.
After done updating ROM, booting up, I expected everything clean, completely fresh.
It's not the case, I went to Market and all old search history were still shown. Not only with Market but other apps too.
So
a. either wipe cache/Dalvik is NOT completely clean wipe or
b. it was completely clean but somehow, those old cache info, which stored somewhere I don't know, get automatically restored back.
Okay, I did a quick read of the FAQ for CWR, and came across these:
Wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
So, I'm taking this guide on board and will wiping Cache AND Davlik. So that's two steps prior to installing a new CM7 nightly build.
votinh said:
I think I need to drop a few lines about wipe cache/Dalvik. *snip*
a. either wipe cache/Dalvik is NOT completely clean wipe or
b. it was completely clean but somehow, those old cache info, which stored somewhere I don't know, get automatically restored back.
Click to expand...
Click to collapse
You didn't happen to store them in uSD card? Or perhaps app data/cache are separate from system data/cache...
Will look into it further...
I had no problems with my Defy (CM7.1) until now.
Whenever I open "Gallery" Defy takes too long to load the pictures. I get to see a blurry/pixel-ated version of all my pictures. It takes way too long to load the actual preview of the pictures. Once I close the Gallery & kill it via Task-Manager my phone hangs. I have to reboot the phone by removing-reinserting the battery. This is getting annyoing!
Are/Have any one of you face similar issues? How do I resolve this?
Please help!
Try increasing vsel or formatting cache and dalvik cache
Sent from my MB525
How do I format cache & dalvik cache?
Bumping it up...
Boot into recovery mode, select custom/latest recovery. There is an option to wipe cache partition (not the wipe user data/factory reset) and then go to advanced, you will see wipe dalvik cache option there.
Sent from my MB526 using XDA App
Thanks a lot premaca! I wiped cache/dalvik cache & it solved the problem!
Thanks a ton for the help!