Oops, Dalvik moving gone wrong

[Guest mrand]

Sorry to bother you guys, but (once again) i did something wrong.. :)

I wanted to move my Dalvik cache back to the cache partition to compare speed without further thinking.

But after i did this via terminal i got several lines saying: error, not enough space (or similiar); of course i didn´t have enough space left...

Now, after trying to wipe cache in Cwm, i can at least boot up again, but only get FC´s and can´t access any app (for example terminal to move dalvik to sd again..)

So, my question is, is there any other way than restoring a nandroid (which is 2 weeks old... :)) in order to move dalvik to sd and get things working again?? Maybe it is simple, but i don´t get it at the moment!

I also tried a CWM-script i found to move Dalvik to SD, but nothing changed... Any ideas or thoughts are very very appreciated :)

Thank you!

EDIT: In CWM it says: Error in cache: recovery/log

(No space left on device)

Edited April 15, 2011 by mrand

[Guest MountfordD]

Been there too!

I had to do a nandroid restore in the end. It is a pain trying to get it back to the point of screw up but I couldn't find any other way of getting it back either.

[Guest mrand]

Been there too!

I had to do a nandroid restore in the end. It is a pain trying to get it back to the point of screw up but I couldn't find any other way of getting it back either.

Thanks!

Even though i was hoping for better news :)

Is it really impossible to get the damn Dalvik back to SD after trying to press it on system??

There a CWM scripts to move Dalvik to SD, but it seems they only work when Cache is stored completely at the cache partition...

:)

I did another Nandroid now, and if anyone here knows a trick to get out of this selfmade mess, i´d be very thankful :)

Cheers!

[Guest Casterina]

Download a2sd gui... and go to the cache section of the app.. and choose where you want the dalvik cache to be stored on the internal storage or the sd-ext.

[Guest mrand]

Download a2sd gui... and go to the cache section of the app.. and choose where you want the dalvik cache to be stored on the internal storage or the sd-ext.

Thanks for your thought, but at the moment there isn´t anything about installing or similiar :)

I cant even start market or connect it to the pc...

Seems like i´m stuck and have to back to my "old" nandroid :)

[Guest Casterina]

You could always go on terminal emulator and enter a2sd cachesd?

[Guest mrand]

You could always go on terminal emulator and enter a2sd cachesd?

i wish i could do so :)

as i said, i cant open anything, every process is stopped immediately!

looks like my dalvik cache is floating around somewhere between internal and external and i'm stuck!

pretty useless mess i made, especially because i had everything running smoothly, but was too curios :)

thanks for any hints though!

[Guest Casterina]

i wish i could do so :)

as i said, i cant open anything, every process is stopped immediately!

looks like my dalvik cache is floating around somewhere between internal and external and i'm stuck!

pretty useless mess i made, especially because i had everything running smoothly, but was too curios :)

thanks for any hints though!

Ouchhh!!! :) Go to recovery mode, and wipe cache partition?

[Guest Boony123]

Ouchhh!!! :) Go to recovery mode, and wipe cache partition?

^^ this is the only way to keep the rom without a nand backup :)

[Guest AntonioPT]

^^ this is the only way to keep the rom without a nand backup :)

Not really, that won't fix anything.

Reboot into recovery. Under partition options, mount data and sd-ext.

Connect your phone to your PC, and open a shell through adb (run adb shell).

Run the following:

busybox rm -rf /data/dalvik-cache

busybox rm -rf /sd-ext/dalvik-cache

busybox mkdir /data/dalvik-cache

Reboot. Your dalvik cache is now on internal :)

[Guest mrand]

Not really, that won't fix anything.

Reboot into recovery. Under partition options, mount data and sd-ext.

Connect your phone to your PC, and open a shell through adb (run adb shell).

Run the following:

busybox rm -rf /data/dalvik-cache

busybox rm -rf /sd-ext/dalvik-cache

busybox mkdir /data/dalvik-cache

Reboot. Your dalvik cache is now on internal :)

First of all thank you guys for keeping my hopes up :)

Antonio PT, before i start messing around again in adb i have a basic question:

My problem seems to be caused by trying to push a too big cache onto a too small partition.. (I didnt check its size before moving)

Doesn´t this problem still exist when moving via adb? Or can i just move it back to sd instead to avoid these space problems?

I tried a CWM script to do so, but unfortunately it didn´t change anything and i suppose (without according knowledge :P) its because my cache got "broken" because of the space issue and isnt fully on internal at the moment..

Hope i expressed my self clear enough and thank you again for your hints!

Cheers! :)

[Guest de_shepherd]

My problem seems to be caused by trying to push a too big cache onto a too small partition.. (I didnt check its size before moving)

Doesn´t this problem still exist when moving via adb? Or can i just move it back to sd instead to avoid these space problems?

I tried a CWM script to do so, but unfortunately it didn´t change anything and i suppose (without according knowledge :)) its because my cache got "broken" because of the space issue and isnt fully on internal at the moment..

The commands Antonio has suggested don't move the cache - they delete all of the cache dirs and recreate a new empty internal one. When you reboot the cache will be rebuilt (so first reboot may be slow). Also, as your external cache was larger than internal space then I assume that as you run more apps you will run into a "no more space" error at some point when you'll have to decide either to move cache external again or delete some apps!

[Guest mrand]

The commands Antonio has suggested don't move the cache - they delete all of the cache dirs and recreate a new empty internal one. When you reboot the cache will be rebuilt (so first reboot may be slow). Also, as your external cache was larger than internal space then I assume that as you run more apps you will run into a "no more space" error at some point when you'll have to decide either to move cache external again or delete some apps!

Thanks for clearing that up for me :)

Unfortunately i still have the same problem... i booted into recovery, ran the above commands and afterwards did adb reboot.

But when finally booted, the pulse just gave me the same fc´s and stuff :(

Stupid question, but should there be anything visible on pulse´s screen when running these commands?

Or is there any other command i could try to get it working again??

In the meantime i was using an old backup and kind of got used to having "lost" some things, but still there is a little hope and also curiosity :)

So, i would still be very thankful for any hints!

Thank you and Cheers!