Just as the title says!
I seem to have a error when I try to do it through recovery it keeps telling me to do it through ADB!
I have not wiped it in about 2 weeks and have flashed about 20 or more times, and just a moment ago I was getting some force closes, so I rebooted and the force closes were coming as fast as I could close them.
I just figured I would give it a try and see if it helps!
By the way rooted running 1.5 stock!
Thanks
Roman
Roman G said:
Just as the title says!
I seem to have a error when I try to do it through recovery it keeps telling me to do it through ADB!
I have not wiped it in about 2 weeks and have flashed about 20 or more times, and just a moment ago I was getting some force closes, so I rebooted and the force closes were coming as fast as I could close them.
I just figured I would give it a try and see if it helps!
By the way rooted running 1.5 stock!
Thanks
Roman
Click to expand...
Click to collapse
It still wipes dalvik, even though it shows the error.
Otherwise you can just
Code:
adb remount
adb shell
# cd /system/sd/dalvik-cache
# rm *
That should should clear it
What exactly is the dalvik cache anyway?
Related
So all the sudden i have "android.process.media" force closing it happened like four times so i tried rebooting. Still happened after the reboot and i noticed i lost my ringtones. Finally my phone just rebooted now im stuck on the endless android screen! Any ideas what could have gone wrong.
Oh and by the way this just started today but i've been having android.process.core force closing alot ever since i got the phone.
UPDATE: So i have apps to sd maybe this could be part of the problem. I have booted into recovery and typed
su
cd /system/sd
it returns cant access
Maybe i can move all apps back to phone via recovery terminal I just dont know what the commands to do this would be. Also i am at work so i cant use adb.
OK first off i want to start off with always backup everything before anything
i finally got it working i had to reverse all the scripts to move my apps, data, etc. work but kept rebooting finnally i did a wipe worked... somewhat.... but wouldnt log into google so i created a new password that worked. thanks to everyone for their help (cough)
Solved
Hi,
i solved this problem on my Hero making a complete wipe of my SD card.
Hello All:
Here is a rundown...
Started with JF1.42-RC33 with Apps, Data, Dalvik to SD...
Went to JF1.5 without a wipe and then updated the radio.
All of this went fine. Now when I start up the phone, it
gives me the "System UIDs Inconsistent" message. I press
the button and then everything loads fine. All 125 Apps
are there, Market works correctly, notes are still there,
and I have tested every App and there are no issues.
Loving the new ROM by the way... no stability issues so
far.
The message on the phone says to wipe the data. If there
is not other way to get rid of the nagging error then so
be it... I still have my Nandroid backup from the JF1.42
image.
Just wanted to see if there was possibly a way to fix this
in ADB or the recovery console...
Also, it is in my nature to try and understand these things.
Could this have happened because my /data directory is
on the SD and therefore was not cleared during the Flash
process? Just guessing...
Any ideas?
L8r,
Vermithrax
Vermithrax said:
Hello All:
Here is a rundown...
Started with JF1.42-RC33 with Apps, Data, Dalvik to SD...
Went to JF1.5 without a wipe and then updated the radio.
All of this went fine. Now when I start up the phone, it
gives me the "System UIDs Inconsistent" message. I press
the button and then everything loads fine. All 125 Apps
are there, Market works correctly, notes are still there,
and I have tested every App and there are no issues.
Loving the new ROM by the way... no stability issues so
far.
The message on the phone says to wipe the data. If there
is not other way to get rid of the nagging error then so
be it... I still have my Nandroid backup from the JF1.42
image.
Just wanted to see if there was possibly a way to fix this
in ADB or the recovery console...
Also, it is in my nature to try and understand these things.
Could this have happened because my /data directory is
on the SD and therefore was not cleared during the Flash
process? Just guessing...
Any ideas?
L8r,
Vermithrax
Click to expand...
Click to collapse
wipe and re-set your symbolic links .. all your apps will be back but not their data..
Thanks... I guess I will just take the easy way out and wipe the phone... I have tried various ADB and busybox commands to no avail... What I do not understand is the phone works perfectly after the Nag screen is gone... No force closes... no missing functionality...
I will not do the wipe until this afternoon... Just in case some Linux guru has any ideas...
L8r,
Vermithrax
Unless the nag screen bothers you, or shows up more than once per boot, Id leave it. If you start seeing instability or forcecloses then Id wipe.
Unless there is a good reason to Id avoid a wipe. Of course I dont have OCD so one nag per reboot wouldnt bother me. If you do or it does bother you then yeah wipe.
Solved... For me at least...
I had solved this problem some time ago, but I just thought I would add this to the thread in case others find their way here through a search...
All I did was move the /data/data back to the internal memory...
rm /data/data
busybox cp -a /system/sd/data /data
rm -r /system/sd/data /data
reboot
Had a couple of stale NFS file errors, so I could not really delete the /data directory from the /system/sd. However, there are threads that help with this issue.
Probably the cleanest solution HERE
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?
So I have had issue after issue getting the new version to even INSTALL.. but finally got it after totally deleting the older 1.3.5 version and wiping cache, restart etc.. new install of 1.4.2.. everything works fine....
BUT....
After using titanium backup to restore data there is some kind of bug that makes the birds virtually worthless. I get the data back (levels etc) but when I go try to beat an old level the birds litterally bounce off the pigs without causing ANY damage.
Ive done this 3 different time now, totally removing the game, reinstalling, verified to work "normal" before data restore... and again, not working after the data is refreshed.
PLEASE HELP!
EVO
Myn RLS3
Nets 4.2.1 CFS more
Let me answer my own thread after I finally find the answer minutes after posting this...
Thanks to anuwyn in this thread:
http://forum.xda-developers.com/showthread.php?t=820725
anuwyn said:
Fix for "Application not installed message" and "Installation unsuccessful" on Rooted HTC Hero with FroydVillain 1.5.
I couldn't install Angry Birds and some other applications on the Market after installing
FroydVillain 1.5 and after some debugging I found out why. There seems to be a problem related to
the file "/mnt/secure/asec/smd12tmp1.asec".
Solution: Delete the corrupt file with a terminal app and also delete the market data to be sure.
1. Get "Terminal Emulator" or another terminal app from the Market.
2. Run the "Terminal Emulator".
3. Write:
su (ENTER)
rm /mnt/secure/asec/smd12tmp1.asec (ENTER)
rm /data/data/com.android.vending/cache/* (ENTER)
4. Exit the emulator, reboot and try to install the failing application again.
5. If the above doesn't solve your problem try the following:
- Wiping cache
- Wiping dalvik cache
6. If this doesn't fix your problem just wipe the phone and reinstall everything
Click to expand...
Click to collapse
It SEEMS to have worked!
I know this is kind of an obscure problem that no one else will probably ever have, but figured Id update it just the same.
same thing happened to me, I just restored the older version with the data and then updated the app over the market..worked fine after that
i could never get it to update over the market for some reason... always had to unmount the SD to get it to work.. but couldnt install from the market or save to phone without SD in.
I ended up saving to sd and using root explorer to move it onto the phone, unmount sd, do a cache wipe, install from phone, remount sd. whew!
its updated now and i have successfully done a titanium backup several times. (Thank God)
I have similar issues with fruit ninja attempting to update but just gave up on that one.
I am stuck with a rather odd issue as of late..I did a full wipe and re-install of Bumble Bee 2.4 on my Virgin Mobile Optimus V phone about 4 weeks ago.
In a summery when I download a new app i back it up using Titanium Backup immediately after the installation is finished. Then I move the app to my SD card. Sadly anytime I want to update that app through the Android Market Place or even the Amazon app store, BumbleBee will crash and restart during installation.
I tried a few things on my own. Such as moving the apps to internal storage and updating then but the crashes still happen. I even uninstalled a app and tried to download it from the market place but the phone would still crash and restart upon installation.
I did some looking around and the only thing close to my problem I could find was this.
So the issue was with the full-wipe install, but the problem wasn't what I thought it was last night. The install puts the google apps to /data/app creating that directory if /data was completely gone, however the full-wipe install did not set permissions for the new /data/app directory, which meant the Market couldn't install to it and generally freaked out. One reason this didn't show up for me was because there was a second problem in the full-wipe install -- it didn't format the data partition correctly either (!), so /data/app (sometimes) already existed with the proper permissions. And that's why the bug didn't show for everyone.
You can test (and fix) this yourself by booting into recovery, mounting /data, and then doing "adb shell chown -R 1000.1000 /data/app", "adb shell chmod 771 /data/app", and "adb shell chmod -R 644 /data/app". Reboot and Market installs work.
Click to expand...
Click to collapse
I use the xionia recovery. Can I emulate his steps with it?
I don't mean to double post of have a shameless thread bump but I am willing to try any ideas someone may have. I been googling all around trying to find more on "adb shell chown" ect but I am having some difficulties.
Bump
Bumping this thread. I'm having the exact same problem. Anyone find a resolution?
Thanks!
shameless re-bump
I couldn't find a solution that worked for me to solve this.
The bumblebee rom is great, but I switched to the Inferior Human Organs CM7 rom and all is well. I had some lock screen freezes, but I disabled ADW rotation and that seemed to fix it.