Database Info

Dalvik cache wipe. Now EVERYING FC *resolved

So I did this once before and had to nand restore. I just did it again on a new install of fresh 1.1 with apps2sd and it did the same thing. Instant FC on ALL apps at boot. I'm doing this from RA menu. why is this happening?!

beyondinferno said:
So I did this once before and had to nand restore. I just did it again on a new install of fresh 1.1 with apps2sd and it did the same thing. Instant FC on ALL apps at boot. I'm doing this from RA menu. why is this happening?!
Click to expand...
Click to collapse
Adb into the phone, erase *the contents* of /data/dalvik-cache (not the directory itself), reboot the phone.

I understand that but It just makes me a little nervous that it doesn't work from RA.
And I don't know why but this thread got posted twice. Mods please combine? TY

If you are using the v1.5.2 I had this same problem along with others users (i run fresh 1.1 also) and i reported this problem in the RA-heroc-v1.5.2 thread, but got thumped on about how this ROM had no problems. I didn't have this issue in 1.2.3. Everytime you do a wipe in this new Recovery whether it tells you to ADB or not, it will cause your phone to FC everything on reboot.

Found It:
29th December 2009, 12:04 AM
rvm23
Junior Member Join Date: Nov 2009
Posts: 4
--------------------------------------------------------------------------------
Quote:
Originally Posted by gu1dry
"And it says when it fails to clear the Dalvik Cache, to do a simple adb command, sheesh, people are lazy... "
This made me decide to try something. The typical instructions for clearing the caches are:
Quote:
adb remount
adb shell
rm -r /data/dalvik-cache
rm -r /data/boot-cache
reboot
"I tried only the "rm -r /data/dalvik-cache" command in adb, and had the same problem with endless FCs that the wipe dalvik option in the recovery has been causing. I then used adb to do "rm -r /data/boot-cache and rebooted again. Once it reboots, everything appears to work fine.
So it seems like the boot cache needs to be cleared after the dalvik, and the recovery tool isn't doing that."

FYI the clear cache button inside fresh kitchen does do dalvik-cache and boot-cache.

flipzmode said:
FYI the clear cache button inside fresh kitchen does do dalvik-cache and boot-cache.
Click to expand...
Click to collapse
Thanks Flipz! That will save some time!

Agimax said:
Ii reported this problem in the RA-heroc-v1.5.2 thread, but got thumped on about how this ROM had no problems.
Click to expand...
Click to collapse
No, you got thumped for recommending that people stay on 1.5.1, which has known problems with backups.

posguy99 said:
No, you got thumped for recommending that people stay on 1.5.1, which has known problems with backups.
Click to expand...
Click to collapse
I Recommended using 1.2.3, not 1.5.1 or 1.5.2
25th December 2009, 06:50 PM
Agimax
Junior Member Join Date: Nov 2009
Posts: 20
--------------------------------------------------------------------------------
Quote:
Originally Posted by rvm23
Is there a problem with wiping the dalvik-cache in the most recent version of the recovery? Every time I try, I get an error saying it failed and then then get an endless string of force closes after my phone reboots. I then have to restore a nandroid backup in order for my phone to function properly again.
I've had the force close problem twice tonight, and it dawned on me that I had tried wiping the cache in recovery both times. I then tested it a third time and had the same result.
Edit: It would've helped if I had spelled dalvik correctly when searching this thread. Post #85 is about a similar sounding issue.
I have the exact same problem. Now with this new Recovery when i wipe the Dalvik Cache, the phone has a Zillion FC's. I couldn't even use the Nandroid backup, it still had the force closes after i pulled a backup. I just did a Factory Wipe and put Fresh 1.0 back on. Pain In The A**!!!
My Advice To All: Just Don't Wipe The Dalvik Cache Till It Gets Checked Out By Developers Or Go Back To v1.2.3 ...
EDIT: To Be More Clear, I Could Use Nandroid Backup Just Fine, But It Still Had FC's All The Time After Using A Backup.
--------------------------------------------------------------------------------
Last edited by Agimax; 26th December 2009 at 11:36 AM..
* See people like to defend thumping, cause they didn't see a problem at the time *

Well I'm very happy to hear some kind of explaination. Thanks guys!

What's the point of wiping the dalvik-cache?

jonnythan said:
What's the point of wiping the dalvik-cache?
Click to expand...
Click to collapse
That's the cached java bytecode for your applications. If you erase it, the phone will recreate it the first time you run the application again.

posguy99 said:
That's the cached java bytecode for your applications. If you erase it, the phone will recreate it the first time you run the application again.
Click to expand...
Click to collapse
Actually, to be a bit more specific, Dalvik is android's own native language based off of java. It is structured and runs just like java bytecode. Of course we don't code applications in bytecode so we use something familiar which is java source code, then with some help from an interpreter, we take said java source and convert it to dalvik bytecode for running on android.
The reason you may want to clear the dalvik cache is as follows. The Dalvik virtual machine which runs within android caches an optimized version of the bytecode to improve app loading and performance. If you get random force closures it is very possible that the cache for your apps may be incompatible with your current version of the app for any of a number of possible causes.
Clearing the cache forces the Dalvik virtual machine(DVM) to correctly rebuild the cache to what you currently have installed, and in many cases it fixes the force closures. Usually dvm and boot caches are normally the culprit when you install a new rom and experience force closure problems.

Thanks for the help guys! Mods please rename the thread "resolved"

Same problem here.
However, I don't have any boot-cache so I'm stuck with a clean dalvik cache an a ton of FC!
What to do?

Stuck in boot loop every time I flash a rom

I've flashed a few roms now (masters stock rooted voodoo versions of nexus s firmware) and every time I do the boot logo just keeps on going until I do a battery pull and reboot, and then it's ok.
It's not a problem, I just wondered why this happens??

did you wipe dalvik, factory settings, cache?
did you change the kernel?

zephiK said:
did you wipe dalvik, factory settings, cache?
did you change the kernel?
Click to expand...
Click to collapse
No. These roms don't wipe anything and I don't want to lose my stuff. I don't think you are meant to wipe with them either.

buachaille said:
No. These roms don't wipe anything and I don't want to lose my stuff. I don't think you are meant to wipe with them either.
Click to expand...
Click to collapse
I was asking if YOU did wipe them because if you're going from one ROM to the other ROM you are supposed to wipe.
You lose your settings and apps. Back them up using Titanium Backup (Or any other related app).
Or.. better yet, just perform a nandroid backup. After that, wipe those 3 and reboot. See if the problem is resolved, if it is then you already know. If not then nandroid restore.

If you're going from one ROM to a completely different ROM made by someone else, you have to wipe data/factory settings!
If you're flashing an updated version of the current rom you're using, wipe cache/dalvik-cache.
If you're flashing different roms every other day, go buy Titanium Backup to backup your apps/settings.
And uh what ROM are u flashing where "you're not meant to wipe"
-Nexus S

nxt said:
If you're going from one ROM to a completely different ROM made by someone else, you have to wipe data/factory settings!
If you're flashing an updated version of the current rom you're using, wipe cache/dalvik-cache.
If you're flashing different roms every other day, go buy Titanium Backup to backup your apps/settings.
And uh what ROM are u flashing where "you're not meant to wipe"
-Nexus S
Click to expand...
Click to collapse
I am new to this so I'm still getting my head around it.
From stock I went to the rooted voodoo version of this - http://forum.xda-developers.com/showthread.php?t=971690.
From there I went to the stock rooted version of this - http://forum.xda-developers.com/showthread.php?t=979851
In both cases it says:
Rom Information:
Does it wipe: No
Does it flash the radio: Yes
So since they don't wipe, I assumed I shouldn't wipe anything, but it looks like I was wrong. From your post it looks like I should have wiped the cache and dalvik cache. I know how to do this in CW but I've never done it and my roms are working fine.
So next time master releases an update I gather I should wipe cache and dalvik cache yeah?
Also, when I do this will it remove any of my settings or apps?
Hope you can answer these questions, and thanks for advice so far.
<<edit>>
Just did a bit of googling and it looks like you don't lose settings when you wipe dalvik cache and cache, so what does actually get removed.

There is a thread stickied in development called ref roms themes and kernels. It gives step by step directions on how to flash all three including what should be wiped. Check it out
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.

It says:
Does it wipe: No
Does it flash the radio: Yes
Click to expand...
Click to collapse
because its saying that the ROM doesn't wipe. Some ROMs are built in a way so that it automatically wipes your phone to ensure best performance. The creator is just saying that it doesn't do that BUT you need to wipe. The keyword does and need are two different things. The basic concept between going from 1 ROM to another (unless its the same ROM series) requires a wipe in all three: dalvik, cache, factory. If you're going from the same ROM to a newer version and encounter bugs, its best if you wipe.
I'm a more advanced user when it comes to Android since the first Android phone. I know what I'm talking about. When you go from stock ROM to another, its going to have bugs if you don't wipe.
If you're using Axura 1.1.1.0 and its fine, and he releases a new version. You can flash without wiping (but you can wipe cache & dalvik to be safe; none of your settings will be wiped). Wiping factory settings is the only one that will wipe your settings / apps.
If you're going to be a flasher, its best if you purchase Titanium Backup Pro (or MyBackup.. but I highly recommend Titanium Backup). Use this program and it will save all of your apps + settings to them. Just don't use it to save SYSTEM apps/files because it will cause FCs.
Dalvik Cache / Cache.. its nothing you need to know in particular. It's just removing cache that your phone set up to increase speeds. It just wipes them and gets the Android system to re-establish them. So no caches from the previous ROM will carry over onto the new one.

EDIT: n/m..............

zephiK said:
It says:
because its saying that the ROM doesn't wipe. Some ROMs are built in a way so that it automatically wipes your phone to ensure best performance. The creator is just saying that it doesn't do that BUT you need to wipe. The keyword does and need are two different things. The basic concept between going from 1 ROM to another (unless its the same ROM series) requires a wipe in all three: dalvik, cache, factory. If you're going from the same ROM to a newer version and encounter bugs, its best if you wipe.
I'm a more advanced user when it comes to Android since the first Android phone. I know what I'm talking about. When you go from stock ROM to another, its going to have bugs if you don't wipe.
If you're using Axura 1.1.1.0 and its fine, and he releases a new version. You can flash without wiping (but you can wipe cache & dalvik to be safe; none of your settings will be wiped). Wiping factory settings is the only one that will wipe your settings / apps.
If you're going to be a flasher, its best if you purchase Titanium Backup Pro (or MyBackup.. but I highly recommend Titanium Backup). Use this program and it will save all of your apps + settings to them. Just don't use it to save SYSTEM apps/files because it will cause FCs.
Dalvik Cache / Cache.. its nothing you need to know in particular. It's just removing cache that your phone set up to increase speeds. It just wipes them and gets the Android system to re-establish them. So no caches from the previous ROM will carry over onto the new one.
Click to expand...
Click to collapse
That is a very helpful post and clears a lot up. Many thanks. Looks like I had better do it again and do it right this time.
I've got titanium backup. Bought it after I rooted, but never restored with it yet. Also, thanks for the info about no saving system files with it, as I currently do have it setup to backup all user apps and system data, so I will have to change that. I gather I should just change it to all user apps??

buachaille said:
That is a very helpful post and clears a lot up. Many thanks. Looks like I had better do it again and do it right this time.
I've got titanium backup. Bought it after I rooted, but never restored with it yet. Also, thanks for the info about no saving system files with it, as I currently do have it setup to backup all user apps and system data, so I will have to change that. I gather I should just change it to all user apps??
Click to expand...
Click to collapse
Backup all user apps is the one you want to do. You can backup bookmarks using Google sync or a app known as BookmarkSB
If you have system apps backed up, delete all backups using batch and reapply user app backup

zephiK said:
Backup all user apps is the one you want to do. You can backup bookmarks using Google sync or a app known as BookmarkSB
If you have system apps backed up, delete all backups using batch and reapply user app backup
Click to expand...
Click to collapse
Thanks for your help. I reflashed the rom and I did it properly this time. Had a bit of a problem with TB restore as I'm a noob but Joel from TB answered an email I sent him very quickly and I got it sorted (thanks joel).
How long does it take to flash a rom once you get good at it? Took me a while tonight because of mistakes.
Sent from my Nexus S using XDA App

buachaille said:
Thanks for your help. I reflashed the rom and I did it properly this time. Had a bit of a problem with TB restore as I'm a noob but Joel from TB answered an email I sent him very quickly and I got it sorted (thanks joel).
How long does it take to flash a rom once you get good at it? Took me a while tonight because of mistakes.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I can usually get from booting into recovery to having a usable device with most everything set up in about...10 minutes? Assuming I already downloaded the ROM lol sometimes those mirrors are slooooooow.

Wipe it

I was one who hated doing a factory reset and reinstalling everything. I dirty flashed Codename Android 3.32 over my old ICS and everything seemed fine. If I tried to update to 3.3.4 I had problems and the only way everything was cleaned up was by a wipe and reset. I follow the following rules and had everything going again in 15minutes after following a link on android forums "Full wipe. What's the big deal? Steps to take (15 mins)" since I can't post the link just follow the search.

Without the link this thread is pretty pointless.
Sent from my Nobody Cares.

search the term to get the link
I am restricted and can't put up the link but if you just do a search for the term.
( Full wipe. What's the big deal? Steps to take (15 mins)" )
you will find the site and it's worth it if you constantly change roms..

bmuseed said:
I am restricted and can't put up the link but if you just do a search for the term.
( Full wipe. What's the big deal? Steps to take (15 mins)" )
you will find the site and it's worth it if you constantly change roms..
Click to expand...
Click to collapse
Ok well flashing codename over stock ics is pretty silly in itself first of all.
I don't know why we get so many threads on wiping. It's pretty simple:
If you are flashing nightlies, USUALLY you can just wipe cache and dalvik and be ok. If you DO get problems then you should do a full wipe (system,data,boot and cache). This way you dont post about bugs you think the rom has, where it is actually bugs from dirty flashing.
When flashing different ROM's, you need to full wipe. Always.
With titanium you can backup your apps, so restoring apps take literally a few minutes.

if you get a cluster f*#@ of problems then clean install. It isn't that hard. Use Titanium Backup and good to go.
In Recovery:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with only bootloader, recovery and radio...dalvik-cache resides on /data, so it's gone already.
3. flash rom
4. gapps & custom-kernel (if needed). No need to let the phone boot & settle before flashing them (most custom-kernels have a script that automatically wipes /cache & dalvik during kernel-install)
5. reboot
6. Run TB -- restore missing apps with data --1st option under restore
just updating rom:
1. flash rom-zip
2. wipe /cache and dalvik-cache
3. reboot
Do this before reporting any issues on the thread since the problems are often related to this and not the ROM or kernel.
Sent from my Nexus S using xda premium

[Q] From CM10 20130330 to CM10 20130416 ??

Hi and thanks for all the help and pre-thanks for any help on this. I am just a TAD paranoid from a previous flash.
I have been running CM10.1 20130330 and gapps 20130301 for 2 plus weeks now. It was pretty stable until I restored Talkback from my Titanium backup from the GB backup and then said, I am not blind and tried to remove it with TBU and it wouldn't install. Everything works ok with some warnings that::gmail, gaaps, email, TBU, etc have guit working, I press on and things work.
I want to flash the CM.1 20130416 and gapps 20121212.
Following http://forum.xda-developers.com/showthread.php?t=1776129 Scott's directions for coming from JB 4.1 I would need to do a Factory reset?
CWM: Wipe Cache / Factory Reset Note: You should be fine without this step, but it is HIGHLY recommended as it makes certain all bugs are wiped clean. (Should be fine???)
Install ROM: Scroll down for downloads
Install OC kernel [Optional]: Scroll down for downloads (not using)
Install Gapps: Here (the latest for JB 4.2.1 - 12/12/12) - Working swipe! ---- Here (the latest for JB 4.1.2) - New GAPPs 10/11/2012
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
TWO questions:
1. Factry reset removes all my programs doesn't it (?) and I would need to re-install again, right? or restore from Titanium BU? or CWM Blue Restore?
2. I am reading about the nightlies and do you guys wipe everything every time or what?
I am getting the hang of it and enjoying basically a new phone and really don't want to go back to stock with this if I can avoid it.
Thanks for an awesome Forum
OD

Oldbutnew said:
Hi and thanks for all the help and pre-thanks for any help on this. I am just a TAD paranoid from a previous flash.
I have been running CM10.1 20130330 and gapps 20130301 for 2 plus weeks now. It was pretty stable until I restored Talkback from my Titanium backup from the GB backup and then said, I am not blind and tried to remove it with TBU and it wouldn't install. Everything works ok with some warnings that::gmail, gaaps, email, TBU, etc have guit working, I press on and things work.
I want to flash the CM.1 20130416 and gapps 20121212.
Following http://forum.xda-developers.com/showthread.php?t=1776129 Scott's directions for coming from JB 4.1 I would need to do a Factory reset?
CWM: Wipe Cache / Factory Reset Note: You should be fine without this step, but it is HIGHLY recommended as it makes certain all bugs are wiped clean. (Should be fine???)
Install ROM: Scroll down for downloads
Install OC kernel [Optional]: Scroll down for downloads (not using)
Install Gapps: Here (the latest for JB 4.2.1 - 12/12/12) - Working swipe! ---- Here (the latest for JB 4.1.2) - New GAPPs 10/11/2012
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
TWO questions:
1. Factry reset removes all my programs doesn't it (?) and I would need to re-install again, right? or restore from Titanium BU? or CWM Blue Restore?
2. I am reading about the nightlies and do you guys wipe everything every time or what?
I am getting the hang of it and enjoying basically a new phone and really don't want to go back to stock with this if I can avoid it.
Thanks for an awesome Forum
OD
Click to expand...
Click to collapse
Since you are already having some fc issues from restoring I would recommend
1) Factory reset
2) Go to Mounts and storage
3) Format system
4) Format data
5) Format cache
6) Flash ROM, flash G-apps(either for 4.2.2 is fine)
7) Wipe dalvic
8) Reboot
Once you have done this either let playstore re-install apps, or install manually. Do NOT restore data

elbscorp said:
Since you are already having some fc issues from restoring I would recommend
1) Factory reset
2) Go to advanced then
3) Format system
4) Format data
5) Format cache
6) Flash ROM, flash G-apps(either for 4.2.2 is fine)
7) Wipe dalvic
8) Reboot
Once you have done this either let playstore re-install apps, or install manually. Do NOT restore data
Click to expand...
Click to collapse
Thanks
I will do this now, but when I go into the Advanced Menu, I am assuming CWM Blue, I only see repartition and not format. I also do not see system as an option. Am I missing something? I am searching threads for answers now. Thanks.

Oldbutnew said:
Thanks
I will do this now, but when I go into the Advanced Menu, I am assuming CWM Blue, I only see repartition and not format. I also do not see system as an option. Am I missing something? I am searching threads for answers now. Thanks.
Click to expand...
Click to collapse
I apologize,it is in mounts and storage

elbscorp said:
I apologize,it is in mounts and storage
Click to expand...
Click to collapse
Got it thanks, Formatting now.

elbscorp said:
I apologize,it is in mounts and storage
Click to expand...
Click to collapse
Thanks a million.
Up and running and Google Play is automatically reinstalling all my apps at present. Very nice as this has never happened in prior rom flashes.

Oldbutnew said:
Thanks a million.
Up and running and Google Play is automatically reinstalling all my apps at present. Very nice as this has never happened in prior rom flashes.
Click to expand...
Click to collapse
Glad to hear it's working for you

[Q] Flashing SlimKat & some general questions

Hi everyone!
I have three questions.
1. a) The installation instruction on slimroms.net says you should do system partition wipe as well in addition to normal TWRP wipe. I used to do normal TWRP wipe only when I flashed SlimBean, and it worked (maybe not since it got bricked). Wiping system is actually necessary?
b) When you update the ROM, do you have to do full wipe again? Or can I just flash the ROM zip file after erasing cache/dalvik? I have long been curious about this since the first instruction always has this phrase: 'if you are coming from a different ROM'.
2. Is there a simpler way than using TitaniumBackup after flashing?
3. Do I need to flash updateSU zip file every time I flash the ROM?
Thank you in advance!

ericjslee said:
Hi everyone!
I have three questions.
1. a) The installation instruction on slimroms.net says you should do system partition wipe as well in addition to normal TWRP wipe. I used to do normal TWRP wipe only when I flashed SlimBean, and it worked (maybe not since it got bricked). Wiping system is actually necessary?
b) When you update the ROM, do you have to do full wipe again? Or can I just flash the ROM zip file after erasing cache/dalvik? I have long been curious about this since the first instruction always has this phrase: 'if you are coming from a different ROM'.
2. Is there a simpler way than using TitaniumBackup after flashing?
3. Do I need to flash updateSU zip file every time I flash the ROM?
Thank you in advance!
Click to expand...
Click to collapse
1.a. In TWRP > Wipe menu > You have an option to wipe the system partition so you just have to check it. Before doing this make sure that the option -rm is checked in TWRP settings.
1.b. Only wipe cache and dalvik cache for an update.
2. TB is one of the best apps to restore apps & data. You can also create a flashable zip to restore your backup.
3. Yes as long as SuperSU isn't fully implemented in the rom.

Primokorn said:
1.a. In TWRP > Wipe menu > You have an option to wipe the system partition so you just have to check it. Before doing this make sure that the option -rm is checked in TWRP settings.
1.b. Only wipe cache and dalvik cache for an update.
2. TB is the on of the best apps to restore apps & data. You can also create a flashable zip to restore your backup.
3. Yes as long as SuperSU isn't fully implemented in the rom.
Click to expand...
Click to collapse
Thanks!!

Primokorn said:
1.a. In TWRP > Wipe menu > You have an option to wipe the system partition so you just have to check it. Before doing this make sure that the option -rm is checked in TWRP settings.
1.b. Only wipe cache and dalvik cache for an update.
2. TB is one of the best apps to restore apps & data. You can also create a flashable zip to restore your backup.
3. Yes as long as SuperSU isn't fully implemented in the rom.
Click to expand...
Click to collapse
Another question:
I flashed franco on SlimKat ROM. So, do I need to do full wipe when I update the ROM?
Or can I erase cache/dalvik > flash ROM > gapps > franco > SuperSU?

ericjslee said:
Another question:
I flashed franco on SlimKat ROM. So, do I need to do full wipe when I update the ROM?
Or can I erase cache/dalvik > flash ROM > gapps > franco > SuperSU?
Click to expand...
Click to collapse
No. Wipe cache and dalvik is enough for an update so "cache/dalvik > flash ROM > gapps > franco > SuperSU" is correct.
I'm not sure for SlimKat but with some ROMs you don't need to flash GApps at each update.

Primokorn said:
No. Wipe cache and dalvik is enough for an update so "cache/dalvik > flash ROM > gapps > franco > SuperSU" is correct.
I'm not sure for SlimKat but with some ROMs you don't need to flash GApps at each update.
Click to expand...
Click to collapse
That's good. I don't know why formatting cache takes so long with Nexus 5. I'm always stuck at "Formatting Cache using make_ext4fs function" for a minute or two. This didn't happen with my Galaxy Nexus.

ericjslee said:
That's good. I don't know why formatting cache takes so long with Nexus 5. I'm always stuck at "Formatting Cache using make_ext4fs function" for amount a minute or two. This didn't happen with my Galaxy Nexus.
Click to expand...
Click to collapse
TWRP has been updated to v2.6.3.4.
Wiping cache, system... doesn't take a long time now

Primokorn said:
TWRP has been updated to v2.6.3.4.
Wiping cache, system... doesn't take a long time now
Click to expand...
Click to collapse
Sorry for bothering you with similar questions, but I just wanted to make sure! When I change the kernel from franco to Trinity, I erase cache/dalvik and just flash Trinity, right? Only when I want to try out another ROM, I need to full wipe? Thanks.

ericjslee said:
Sorry for bothering you with similar questions, but I just wanted to make sure! When I change the kernel from franco to Trinity, I erase cache/dalvik and just flash Trinity, right? Only when I want to try out another ROM, I need to full wipe? Thanks.
Click to expand...
Click to collapse
If you didn't modify the rom=> you can flash a custom kernel WITHOUT any wipe
If you already change the kernel => you have to dirty flash your current rom (no wipe) then flash another custom kernel
If you want to try another rom => you have to full wipe: data+cache+dalvik+system