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] Battery Died - sdcard read-only, system read-only, and data read-only

Well I screwed the pooch on this one...
While browsing on the streak the battery died and after that I had force close issues for just about every user and system app on the phone. Normally that can be something corrupted on the sdcard from the shutdown and you can typically find the folder and remove it. The alternative would be running fix permissions in terminal, adb, or rom manager. That's not the case here (that I've found). It happens or has happened to me on my sgs before but not my nexus or g1 before that so I'm not sure what specifically triggers it. While trying to find the corrupted file I I tried to install Rom Manager but I can't get into the market despite clearing the cache. I can't install any apps at all actually - it will reboot the phone.
It seems to be a permissions problem. When the issue started like 8 hours ago the sdcard, system, and data were all read only. I fixed the sdcard by mounting to my computer and fixing the permissions in windows by changing the folder properties. I eventually fixed the system permissions (I believe) when I fastboot flashed the boot and system.img for the "performance fixes"; however, I can't for the LIFE of me fix the permissions of the /data and whatever else still is read-only. Flashing the system.img did change that to read-write though which was a major step in the right direction. Seriously, I've tried wiping in recovery (it says it works but doesn't wipe when rebooting), fastboot erase /data to name another attempt with no results after rebooting. It just doesn't erase anything like recovery, fastboot, and everything else doesn't have permission to erase, delete, or modify the data partition.
I can't install apps normally or adb.
I can't wipe data - I get errors in adb about it being read-only.
I can't wipe data in Recovery. It wipes, then reboots, with none of the data wiped.
I can't wipe in Fastboot using Fastboot erase /data - same thing as above.
I can't install root explorer only I'm pretty sure that won't work if fastboot doesn't.
I can't fix permissions using any method that I know of...
Is there anything I'm missing on ways to erase/format /data and everything else that might have this permission problem?
Logcat: http://db.tt/0bzhUQi
*edit:
So I also have root when booting amidst all the force closing (tested with titanium backup) I have but ADB doesn't. I can only get su with adb when I run OneClickRoot again and I get the "failed to copy rateagainstthecage to /data/local/tmp/rageagainsthecage. Read-only filesystem. Then says "unbalbe to chmod /data/local/tmp/tageagainsthecage read-only file system which is what I got also when I tried fixing the permissions for that folder. With that - I only have temporary root only in adb - fully rooted otherwise...

Same problem here cant save or delete. Very time I start up I get the welcome screen and I have to input all my info then all of my apps start to crash. I tried flashing the boot and system.img with fastboot but that did nothing so I decided to see what will happens if I erased all of my partitions (system, boot, userdata, recovery and cache) Fastboot reports back that my partitions all got erased but when I boot up (it shouldn't boot up because all partitions are deleted)it start up to the welcome screen and I back to the same problem that I cant permanently wright or delete to the internal drive

Ya - I'm at a total loss. Keep me posted on what you try and I'll do the same. I won't be able to mess with it until later today and not really sure of what I'll try next. As of now it's essentially worthless to use...

Sorry what will happen if you factory reset now and erase tablet storage? (option 4 with volume up +power button)?
At least you have almost nothing more to lose here right.
Otherwise the only solution I think is to wait for CWM recovery image to come out then...
Sorry that this happened to your DS7. I struggled with quite some issue with mine too, it is pretty annoying.

I tried that factory reset over 10 time. All of the same files that I had on the streak7 before this problem stay intact. Factor rest from the recover mode dont seem write to the streak7

killahbeatz said:
I tried that factory reset over 10 time. All of the same files that I had on the streak7 before this problem stay intact. Factor rest from the recover mode dont seem write to the streak7
Click to expand...
Click to collapse
+1. I even fastboot erased /data or attempted to. Seems like the command works but when you reboot everything is still there.
Found the other post which I didn't find http://goo.gl/xlO6y earlier.
I'm wondering if we tried setting permissions with adb with the mounts they're finding in this thread http://goo.gl/wOynl
I'll post back if I can find the chmod commands. That info might help though.

I tried fastboot -w to erase the data from the device. It boots with no force close issues now but I still can't wipe anything (still read only). I think I can install apps now though so hopefully I can install Rom Manager and Root Explorer to fix permissions and see what I can find out. Doubt it will work but hey, if I started out with read only sdcard, data, and system, and now have read-only data, that's progress I suppose.
I only have it for another few days before returning. I received the replacement yesterday and have to mail it back soon.

[Q] Phone state won't change no matter what I do

Quick SUMMARY (see details below if you've got some minutes to read!)
-> I need HELP!!!
-> Phone is rooted stock GB with jb hboot unlocked bootloader and TWRP v2.2.0, also superCID.
-> Problem is phone apps keep force closing and won't retain any change I make after reboot
-> Last installed program was ROM Toolbox
-> Steps already taken include: Reboots, Fix permission, Wipe (ALL), ROM Update using Windows, RUU using SD card.
Details
I have a Vivid with Stock Gingerbread (Rooted, Bootloader Unlocked, Juopunutbear hboot, SuperCID S-OFF, TWRP Recovery v2.2.0)
I recently removed the SD card on my vivid to use on another phone (SGS III) and when I returned the SD card and started my vivid, I tried using the file manager (ES Explorer) and it force closed, following series of other apps force closing.
I restarted the phone and the force closing didn't stop. I tried uninstalling the most recently installed app (ROM Toolbox) thinking it might be the culprit and nothing changed. I rebooted the phone and noticed every time I rebooted, the phone goes back to the state (installed apps, settings and every other thing) it was before I removed the SD card.
I installed Titanium Backup to make a Backup and flash the phone, but it kept force closing and after several reboots and attempts, it installed but couldn't acquire root.
I restarted to recovery to fix permissions and cleared cache and dalvik cache then rebooted the phone. No luck!!!
I eventually decided to wipe the ROM and do a fresh RUU install. I wiped system and data using recovery but when I restarted the phone, it booted to the (pre-SD card removal) state and was still force closing.
I tried installing ICS using the RUU from att and I got an "Error 155" on the way. I also tried installing the RUU using PH39IMG method with the SD card, it goes through the normal install process and when the phone booted, it's still the same state it was that it takes me to changing nothing.
I've tried all I know and it seems the phone is "write-locked" as it won't retain any change after reboot, suggestions to what I can do to fix this weird problem please.

I am not so sure...
Did the sgs3 reformat your sdcard to a different file system?
Sent from my HTC Holiday using Tapatalk 2

rignfool said:
I am not so sure...
Did the sgs3 reformat your sdcard to a different file system?
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
No it didn't. I only used the sdcard to copy some files to the sgs3 and I still could access the sdcard on my vivid through Root Browser in ROM Toolbox.

hardware maybe

Interesting... One thing you could do is enable USB debugging, and save a logcat showing your phone hitting some of these FCs so we can see what is causing them.
Once USB debugging is enabled, simply boot your phone, plug into your computer via USB, open a command prompt to where you have ADB tools installed, and type "adb logcat > log.txt
That will stream the log from your phone into a text file. After you get one or two FCs, on the command window hit CTRL + C to close the console, and save the log. Then post it as an attachment here.

ess.boyer said:
Interesting... One thing you could do is enable USB debugging, and save a logcat showing your phone hitting some of these FCs so we can see what is causing them.
Once USB debugging is enabled, simply boot your phone, plug into your computer via USB, open a command prompt to where you have ADB tools installed, and type "adb logcat > log.txt
That will stream the log from your phone into a text file. After you get one or two FCs, on the command window hit CTRL + C to close the console, and save the log. Then post it as an attachment here.
Click to expand...
Click to collapse
Thanks ess.boyer. I've been busy over the past few weeks so just saw your reply now.
The phone is in a pretty bad shape right now, I managed to drop it and the screen is shattered so I can't touch the screen to use it.
But I put it on and did the log. Please find attached.
Thanks for wanting to help!!!

So I think the install is probably botched. I'd recommend wiping EVERYTHING and reinstalling from RUU (maybe try a different RUU even).
However, first, please try wiping your cache and dalvik cache. Most of the errors are from not being able to find symbols in dalvik.
Also, are you restoring apps using Titanium backup or some other such program? If so, that could also be an issue. If you have, and wiping cache & dalvik cache don't work, you may want to try wiping /data entirely, and NOT restoring apps before you can confirm that the FC issues you were seeing are still there.
Give the cache & delvik clean a try, and if that doesn't work, please attach a similar log so I can confirm you're seeing the same issues, then we can go from there.

ess.boyer said:
So I think the install is probably botched. I'd recommend wiping EVERYTHING and reinstalling from RUU (maybe try a different RUU even).
However, first, please try wiping your cache and dalvik cache. Most of the errors are from not being able to find symbols in dalvik.
Also, are you restoring apps using Titanium backup or some other such program? If so, that could also be an issue. If you have, and wiping cache & dalvik cache don't work, you may want to try wiping /data entirely, and NOT restoring apps before you can confirm that the FC issues you were seeing are still there.
Give the cache & delvik clean a try, and if that doesn't work, please attach a similar log so I can confirm you're seeing the same issues, then we can go from there.
Click to expand...
Click to collapse
Please see my steps already taken.
I've wiped cache and dalvik, I've installed RUU thru windows, I've installed RUU from SD card. But whenever the Phone boots up, the phone state does not change at all (all apps are as they are, all settings are as they are).
I even tried to lock bootloader, remove superCID. Just a reboot and it all goes back to what it was.
Thanks

What happens if you reboot the phone without the SD card in it?

ess.boyer said:
What happens if you reboot the phone without the SD card in it?
Click to expand...
Click to collapse
The phone boots up to homescreen normally and the apps installed on SD don't work, with reduced FC

XT1095 Marshmallow Won't Boot, Full Disk

Stock Android 6.0 with stock recovery, no root, locked bootloader. Ran the device out of internal storage by writing too many files to the application's data directory. The device crashed and now it goes black after the boot animation. Able to get to the bootloader and recover menus. Lots of data stuck on the device. Any advice on pulling the files or getting Android to start again?

Try wiping the cache in the recovery menu.

Red_81 said:
Try wiping the cache in the recovery menu.
Click to expand...
Click to collapse
Tried this already. Thanks for the suggestion!

Sorry, I didn't see that I your original post so I had to start at the beginning with the most simple suggestion.
Go to recovery and try to use the adb shell to copy off the data you want to keep. Maybe also try a backup from adb (I forget the command).
If you know of a program that is taking up alot of data in the data partition that you don't care about losing then you could try using the shell to delete that data file.
Otherwise, you may just have to factory reset and start over.