Database Develop

error: run 'wipe dalvik' via adb- RESOLVED

I've done an exhaustive search of all forums (plus asked a very experienced developer) and found this problem I'm having posted only once, and it was on a hero. Therefore, I saw no other choice than to post this.
I have a rooted MT3G, running recovery image 1.3.2g.
I am just trying to upgrade to the next cyan, but when I wipe, I get the error message in the subject line while i try to run dalvik cache, and also same error when I try to wipe extensions.
I removed the battery, pulled the sd, reinstalled it, then the battery, rebooted in recovery and tried again. no dice.
I've never had this happen before and I've done quite a few wipes.
Help?
Sorry if this is in the wrong place, etc. I just need some help from someone more experienced than I. It would be much appreciated.
Thank you,
HK

Yes, it is in the wrong place -- You asked a question so it should belong in the Q&A section.
On my G1/Dream dalvic cache is on the ext partition /system/sd/dalvic-cache.
What is the recovery image 1.6? Flash the recovery image in my sig, not the one for the Dream, but for your phone and run the option if you can't find the commands to do it.
Are you having any problems with the rom install, why do you want to wipe it -- most of the time it doesn't cause problems.
Alternitively you can backup your fat32 partition and remake the partitions and you will be set.

Truly sorry about the post in the wrong place. I'm sure mods will rectify that soon.
I'm sorry, i had a typo in my original message. Running 1.3 recovery image.
I did not try to install anything further after experiencing this problem- i stopped, restored nandroid, rebooted, asked my friend (who is also stumped) and came here.
Thanks again,
HK

Hellykitto said:
Truly sorry about the post in the wrong place. I'm sure mods will rectify that soon.
I'm sorry, i had a typo in my original message. Running 1.3 recovery image.
I did not try to install anything further after experiencing this problem- i stopped, restored nandroid, rebooted, asked my friend (who is also stumped) and came here.
Thanks again,
HK
Click to expand...
Click to collapse
You should go here instead, this isnt really Dream related at all. (Sapphire=MT3G)
http://forum.xda-developers.com/forumdisplay.php?f=480
Oh and Amon_RA has a newer version out now that better.Your sd could be a prob if your getting a error when trying to wipe in rec mode.

When you get this just take out ur battery, sd card, and then put the sd in, battery in, reboot or boot to recovery. No more prob.

I did try pulling the battery, then sd, then putting all back and rebooting in recovery. tried it again, but still had the same problem.
Tomorrow I will try an updated recovery image and see what happens.
Is it likely that somehow my sd has corrupted?

Hellykitto said:
I did try pulling the battery, then sd, then putting all back and rebooting in recovery. tried it again, but still had the same problem.
Tomorrow I will try an updated recovery image and see what happens.
Is it likely that somehow my sd has corrupted?
Click to expand...
Click to collapse
Have you tried just clearing out the dalvik-cache with terminal or adb? You can just remove everything in the folder. Since you have a MT I would recommend that you use adb. Go into recovery and do this.
Code:
adb remount
adb shell
# cd /system/sd/dalvik-cache
# rm *
That should clear it

i'm having the same problem! and the sd folder don't have the dalvik-cache! so that cd \system... don't work for me!
ps- htc magic!

As I noted in the title thread, this has been resolved. I figured I would come back and post what I did for others who are having this problem as well, and who might need the same fix.
As it turns out, a theme was causing my problem. I had loaded Alien Aqua a while back, right after I upgraded to 4.2.8. However, for some reason, my phone was reading the original Cyan that I installed- 4.2.4. While this was not causing a problem, apparently it was causing conflicts and corruption.
I re-flashed my root base, then flashed the most recent Cyanogen. No problems whatsoever. All traces of the theme are gone, no force closes, blazing fast phone.
Thanks for the help!

[Q] Nandroid Restore = "Error mounting DATA:!"

Long story short: When restoring via Nandroid it hangs, when using advanced restore the data portion says
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Error mounting DATA:!
Click to expand...
Click to collapse
This afternoon I tried running the Voodoo zip, but the one I downloaded from their site isn't for the Captivate. I ended up with a phone that was constantly displaying 90 degrees off from what it should have been (holding it straight up had the phone thinking I had it on its side).
I decided to uninstall voodoo by creating the "disable lagfix" folder on my card. I rebooted and the phone hung and remained hung at the spinning progress wheel for an hour. I pulled the battery since I couldn't get out of that screen. Rebooting after that had me in what appeared to be the stock version and showed a few of my non-stock apps as "com.etc..." apps.
More reading on here and I found the Captivate-specific version of Voodoo. I figured I'd try to install that before restoring from the Nandroid backup I ran before installing the Voodoo. However, when in recovery mode I couldn't "click" anything with the power button. I tried using adb reboot recovery which didn't fix the problem and instead put me into a non-stop cycle of non-functioning recovery modes after boots.
So I used Odin to get back to stock. Now I'm trying to restore back to where I was before Voodoo. I tried to just run a simple Restore but it hung and after 90 minutes it hadn't completed. So I tried to run an advanced restore and all sections restored except for Data. When I try to restore Data i get the error at the top of this post. I've googled for an answer and everything I've read so far is Cyanogen specific and appears to require Cyanogen to fully fix it. Anyone know how to fix this on a Captivate? Anyone have a link that I'm missing?
Thanks!

If you can boot the phone, then go into android terminal emulator (you may have to download it from the market first) and type mount in the terminal. See what type of partition /data is. If it's ext 4, the disable lagfix was not finished before you pulled the battery. Your best bet then is to download the Captivate voodoo beta 4 kernel version 1.6, which is sticky post in the Captivate development forum here, remove the disable lagfix folder/file from /sdcard/Voodoo/ and let it boot. It will then get you to the point where you should have been at first without having rotation issues and with a kernel that understand ext4. After that, restore your phone to the way it needs to be with Titanium, or by manually downloading and reinstalling any apps that got deleted by your premature battery pull. When ready to do a nandroid backup, do a disable lagfix and let it fully reboot to convert the ext4 to RFS. Then you can do a nandroid backup of restore, as clockwork recovery does not understand ext4 (yet).

Thanks Rajendra! I'll try that and follow up with the results.

I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.

Duplicate post (no way to delete I guess?)

RobertDeBord said:
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Click to expand...
Click to collapse
Try this - once the phone boots - then go to internal sd card and see if there is a Voodoo folder (which there still should be) inside the Voodoo folder make a folder called disable-lagfix - reboot and it should go through the reverse process of creating the lagfix (robot voice). After it finishes reboot go to rom manager and restore.
Hope This Helps....

I can tell you, I've never had a successful restore from rom manager/clockwork recovery. Not once! The only thing that program is good for is as a replacement recovery reboot, it lets you select which zip you want to install from, rather than having to manually name everything to "update.zip". I can't honestly think of anything else its good for. I've tried literally dozens of restores on my captivate and everyone of them has crashed or frozen at some point during the restore. Worthless!!

[Q] Galaxy S won't boot: can't mount sdcard, mmcblk0p2

Hey,
A friend gave me his Galaxy S after another friend of him got it into this following state (I'm not sure what exactly he did or tried to do):
The phone is stuck in a boot loop, sometimes it shows the first frame of the boot animation for a second before booting again. When I start it in recovery mode (Android System Recovery (3e)) I get this error messages:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
The phone does not have an SD card in it.
After reflashing with the same firmware as original, I get these errors:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
meida files copy failed.
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
I've tried flashing different firmwares too, including rooted ones, and the results were the same except for a case where the first error was about not being about to mount mmcblk0p1 instead of sdcard, and another case where another firmware cause the phone to appear to boot, but after a minute or too it got stuck on a black screen and stopped responding.
I followed many different guides on how to fix similar problems, but none of them actually worked.
Please help, thanks a loooot in advance.

http://forum.xda-developers.com/showthread.php?t=1134975
Maybe it will help?

Thanks for the reply. Solutions 1-3 are irrelevant, as I can get into download mode, but even after flashing, any version, the problem is still there. I tried solution 4 (dbdata flash), but it doesn't solve anything. Are there any other partitions I can flash and might be able to solve this?

Ok, next thread
http://forum.xda-developers.com/showthread.php?t=1069867
Maybe here is solution?

Tried flashing the files there and no luck, still the same error. =/
I sent Faria, who said he has tools for solving this problem in that topic a PM, hopefully he'll share his tools with the community.
Meanwhile, I don't mind trying different solutions.
I also noticed something – if I keep the phone in the boot loop for a long time, it will eventually get to either a loop of the carrier boot animation (Which normally doesn't loop), or actually boot for one time. (When it booted I tried to power it off and see if it would boot again normally, and it didn't =/)

i have this kind of error few months ago, what i do was, flash pit file only with repartition, then flash pda, phone & csc.... agn flash this dbdata.rfs file, should fix the issue.

Just tried it, no luck, exactly the same error as before. =/

ops... sorry to heard that, at least it work for me but too bad not for u.....

I have the exact same error message and problem . Really hope someone can find a fix for this because I've spent hours and hours

Yep, EXACTLY same problem as OP and NO fixes for me yet. Tried everything from this thread and other threads. Let's see who's the real king of knowledge who can fix this.

any luck with this issue?

In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.

spamtrash said:
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
Click to expand...
Click to collapse
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.

ambrozic said:
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
Click to expand...
Click to collapse
Any Luck????????

I'd be interested with results as well. As last hope, you can try http://forum.xda-developers.com/showthread.php?t=1330491 this one, but it requires hardware mod...
Sent from tam-tam drum

any update or fix?
Someone found any fix for this?

Yep!
Hi guys!
Yep - probably I found the solution. One month ago I have bought i9000 with this problem (as broken). Finally I managed to start that SGS and even install ICS on it. The problem is (as I suppose) that internal flash memory is broken and You have to move /data partition to external SD card. So some flashes, some changes in files and repartitioning of SD card does the thing.
Currenty I am in the middle of preparing a tutorial to be pushed on YT to show how I managed to solve the problem. Stay tuned
Best regards

this is a hope.. =)=)=) please send me a tutorial. thanks

Ready
So.
Finally I had some time to add voice recording to my movie and volia - is ready.
I hope it will help at least somehow.
I am not sure if this manual will help in Your case(s), but it might be at least a hint
Best regards
Fteller.

^ So, umm, where's the link for your YT video? Thanks.

[Q] Getting Force Close errors after flashing my SGS GT9000... please help.

I had experiencing a problem with my SGS I9000 wherein I could not completely delete anything that had been installed on my phones internal memory... be it applications \ videos \ images \ etc ... I say completely because it did used to tell me that the contents have been deleted when done in KIES and when I had done a factory reset \ formatted my storage... But the contents kept reappearing everytime my phone started up again... Tired of this I decided to flash my phone using Odin3.
My Phone's specs at that time were (had updated to Gingerbread fro Froyo through Kies):
PDA: I9000DDJV6
Phone: I9000DDJV4
CSC: I9000ODDJV6
Now, I've tried flashing using multiple firmware versions... started with the stock DDJV6 version I found here... http://forum.xda-developers.com/showthread.php?t=846913 ... and followed all instructions on how to use Odin while flashing using PIT 512...
This sent my phone first into a continual boot cycle... I was able to get into the Download Mode again after a few attempts and then, I tried flashing again with the Gingerbread firmware 2.3.3 given here
http://androidadvices.com/update-samsung-galaxy-s-gt-i9000-stable-gingerbread-xxjvk/ ...
and when that failed too... I also tried Gingerbread version 2.3.5 .. which was given here...
http://androidadvices.com/update-samsung-galaxy-gt-i9000-xxjvs-gingerbread-235-firmware/3/
Now, I problem I face is... though am able to flash the rom, I keep getting a whole bunch of Force Close error messages when the phones boots up...
(I've attached some images of the error message I am getting...)
I read somewhere that should be getting the standard setup options such as the Google registration page and language options once the flashing is completed... but I don't get that page at all... I just keep getting error messages as the phone reboots!
I've also restarted the phone in Recovery mode (Vol Up + Home + Power) to delete cache files and stuff... but that doesn't help either... I can't seem to understand what step am I missing... I must have tried flashing my phone like a dozen times since yesterday but the problem persists...
I would appreciate if you all could help me out of this problem.
Regards,
Vishal

and if it helps, all data including the Apps and other stuff continute to stay on my phone and haven't been deleted... I had checked 'Re-Partition' in Odin3 hoping it would reformat the storage.

I have the same issue! Stuffed if i can find the solution anywhere... Ill keep an eye and ear out though and if i find a fix elsewhere ill let u know here.

Maybe a silly idea but have you tried another a version above odin 1.3? there is 1.7 and 1.8...
Also another silly thing.. You say you can flash the rom's, does that mean you have custom recovery and tried wipe from there as well...

Go into recovery and do a factory reset.. if u haven't already
Sent from my GT-I9000 using XDA Premium App

Factory reset from recovery menu didn't work for me. Appears to say/do all the right things in the yellow text, but end result is exactly the same as it was. Will try higher Odin versions tonight.

Re:
Thanks for your response everyone.
The Reset option doesn't work for me either... Tried this through the 'Privacy' menu ... as well as getting into the Recovery Mode using the Vol Up + Menu + Start button combination... Please let me know if I've missed any other way to factory reset\wipe the data...
Odin versions... I've used the older version (1.3?) as well as 1.7 ... have also tried using pit 803... but to no avail...
The fact that I can't delete any content on the internal storage drive may mean that it might have got corrupted and may need a replacement?
I am new to this and hence might sound like a noob but I appreciate your patience...

Everyone starts as a noob or beginner, so there are no silly questions.
To totally reset your phone and clear everything off of it you can use the dialer code *2767*3855# : this will delete everything that has been added from your side, including all of your files!
BUT : you should be aware that the formatting starts immediately after you type in the last '#' without getting asked if you really want to wipe everything, so be careful.

Same here; Odin 1.7 didn't alter result. Nor does entering reset code in dialler...

Re:
The other day, I tried to flash the stock rom using the PDA file only... The procedure I followed was... Opened Odin, added PIT 512 and checked Re-Partition, added the DDJV6 PDA file... Hit Start... The process completed and as my phone rebooted again, it went into Recovery and threw up the following error messages:
E: copy_dbdata_media: Can't mount /cache your storage not prepared yet.
E: failed to mount /cache (Invalid Argument)
E: Can't mount /cache/recovery/recovery_kernel_log
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
Upon clicking 'wipe data/factory reset'
E: format_volume: rfs format failed on /dev/block/stl11
Does this indicate something?
And, I do keep getting the force close error messages as well... and some of them are for applications like Titanium Backup and Read It Later... which have already been uninstalled .. but they still seem to exist in the phone's memory...

No idea if this will work but I was recently guided to this thread and it maybe of help to you because it says that it brings you back to a proper base... read the last 5 pages as this is usually recommended in long threads and obviously the whole of the first page. The thread I mean is the one where it says efs recovery below

Re:
Thanks Talon, I will surely try this out!
There's a guy who had a similar problem as mine and he seemed to have solved it by flashing EZBase-4.0.7z ... so perhaps it might help me as well... currently on download... will let you know how it went!

Re:
Flashing with EZBase hasn't got rid of the Force Close error messages... I get tonnes of them... for almost everything from android.phone to even applications which I had uninstalled several times but they just mysteriously come back .... everytime I flash...
Do I need to get root access before I can perform a clean flash... as in, with no force close messages?

vish123 said:
The other day, I tried to flash the stock rom using the PDA file only... The procedure I followed was... Opened Odin, added PIT 512 and checked Re-Partition, added the DDJV6 PDA file... Hit Start... The process completed and as my phone rebooted again, it went into Recovery and threw up the following error messages:
E: copy_dbdata_media: Can't mount /cache your storage not prepared yet.
E: failed to mount /cache (Invalid Argument)
E: Can't mount /cache/recovery/recovery_kernel_log
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
Upon clicking 'wipe data/factory reset'
E: format_volume: rfs format failed on /dev/block/stl11
Does this indicate something?
And, I do keep getting the force close error messages as well... and some of them are for applications like Titanium Backup and Read It Later... which have already been uninstalled .. but they still seem to exist in the phone's memory...
Click to expand...
Click to collapse
THAT (above) could be sorted out with: Click

vish123 said:
Flashing with EZBase hasn't got rid of the Force Close error messages... I get tonnes of them... for almost everything from android.phone to even applications which I had uninstalled several times but they just mysteriously come back .... everytime I flash...
Do I need to get root access before I can perform a clean flash... as in, with no force close messages?
Click to expand...
Click to collapse
Try flashing a froyo rom... might help... then after that if you get no force closes flash gingerbread
Sent from my GT-I9000 using XDA Premium App

Re:
Okay, will download the EzBase froyo version and try flashing that...
As an aside, would you please list the reasons why these force close messages usually pop up? May be I will be able to link my problem to any one of them and then perhaps spot what the root problem could be?
To quote my original problem... To I am unable to fully uninstall the applications which I had installed on my USB storage card... They come back... but most are not functional... I get force close error messages when I try to open them...
And now, am getting force close every time I flash ...

Thanks spamtrash! I will try doing that first... and then perhaps try flashing with EZBase Froyo...

Re:
Okay, so I tried flashing this time using EZBase 2.0 (Froyo version)... and though there were no errors in the Recovery Mode... the force close error messages did come up when the setup wizard is supposed to open... (
Is that some drivers on my phone have not been installed properly which causes these messages to pop up?
I once got an error message saying "Samsung Android" had failed to install ... but when I checked my Device Manager (Win 7)... the ADB Interface was green and installed properly... ??

vish123 said:
The other day, I tried to flash the stock rom using the PDA file only... The procedure I followed was... Opened Odin, added PIT 512 and checked Re-Partition, added the DDJV6 PDA file... Hit Start... The process completed and as my phone rebooted again, it went into Recovery and threw up the following error messages:
E: copy_dbdata_media: Can't mount /cache your storage not prepared yet.
E: failed to mount /cache (Invalid Argument)
E: Can't mount /cache/recovery/recovery_kernel_log
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
Upon clicking 'wipe data/factory reset'
E: format_volume: rfs format failed on /dev/block/stl11
Does this indicate something?
And, I do keep getting the force close error messages as well... and some of them are for applications like Titanium Backup and Read It Later... which have already been uninstalled .. but they still seem to exist in the phone's memory...
Click to expand...
Click to collapse
If u r flashing only the pda file then do one thing first... Open the tar file and see whether it has boot.bin and sbl.bin... If it has then do a full reset by *2767*3855#... And then flash without pit and repartition... Only pda... Do nt tick mart repartition... This wud do ur job...
Sent from my GT-I9000 using xda premium

And if u ve any lagfixes or partition changes then remove that first...
Sent from my GT-I9000 using xda premium

Silm 3.0 bootloop hell [solved]

Hi all
I'm avoiding posting on the Slim thread as this ends up being a bit of a mess.
I've been using Slimbean 3.0 since last Thursday without major issues (nothing big, I was just waiting for the right moment to do a full backup and clean everything).
What happens is that my phone dies while coming back home from work and when I try to reboot it start bootlooping. There's no way I can get it back to life.
At this point I can get to download mode, but nothing else.
Yesterday I've been suggested to start looking into flashing something like CM10 and so I did.
By following these instruction http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd I manage to flash via heimdall CWM speedmod kernel without problems.
I finally have CWM working.
From there I can't get adb detect the device. The only way I can upload the rom is via CWM itself and so I did: I upload both Slimbean 4.2.1 RC1 and Slim_Gapps and cm10.0, just in case.
What I'm trying next is a full wipe to start from clean: full wipe/factory reset works OK, but when I try to format /system I get:
Code:
E:Can't mount /dev/block/st19 to /system with parameters auto llw,check=no
(File exists)
Error mounting /system/!
Skipping format...
Done.
This is the point where I'm at.
If I try to flash Slim I get (error 0), being unable to format system for the same above reason.
If I try to flash cm10.0 it doesn't even pass the device assertion check.
Now I'm particularly clueless. Do I need a different CWM that better supports Slim? Or is the system error something that is inherently wrong with my current status?
Any help is greatly appreciated.
PS: I was trying to find help on #freenode with no luck, I'm available there if anyone wants to help, my nick is ThePeach.
UPDATE: ok it seems that by trying to flash Slimbean it actually replaced the CWM with the one I was used to that comes with Slim and finally managed to format /system and flash Slim correctly without problems.
Yay!
I really hope nobody will ever find himself in this kind of mess...