The last few times that i have wiped dalvik cache i get this
Cache wipe complete.
E:unknown volume for path [/sd-ext]
anyone have any ideas what this is/means?
thanks!!
Pretty sure this happens to everyone. It happens to me at least - don't worry about it is the point. dalvik is still wiped.
ok thanks as long as its nothing to worry about.
kimbernator said:
Pretty sure this happens to everyone. It happens to me at least - don't worry about it is the point. dalvik is still wiped.
Click to expand...
Click to collapse
Agreed, always get that error.
Sent from my HTC Glacier using XDA Premium App
ditto happens to me as well
My defy has started to become sluggish at times. Imbusing cm7 stable.
It wasnt like this before. So i have a question. What does wiping cache in recovery do? Does it factory reset my phone? Will wiping cache make the phone fast again?
Sent from my MB525 using xda premium
your phone wil be clean and fast. Wipe data/cache remove everything. after that you must to configure everything (google account, install apps...). Dont forget to backup! (titanium backup...)
Thanks for the reply..but are you sure data and cache are both the same??
I thought cache was just the cache used by apps..
Sent from my MB525 using xda premium
I flashed Quarx's CM10 ROM and it runs completely fine at first, but then when I reboot my phone it gets stuck at the splash screen and won't load the operating system. The only way I've found to fix it is to reset to factory defaults, which isn't really an ideal solution as I don't want to have to reinstall everything every time I reboot my phone.
Does anyone have any idea what I can do?
Bump
Just clear dalvik cache in custom recovery. You can find it in "Advance" menu. Dalvik cache has to be clean before first boot. You can wipe all caches just in case. After this try to reboot a couple of times to see if this issue persists.
Vicsa said:
Just clear dalvik cache in custom recovery. You can find it in "Advance" menu. Dalvik cache has to be clean before first boot. You can wipe all caches just in case. After this try to reboot a couple of times to see if this issue persists.
Click to expand...
Click to collapse
I have cleared all caches and nothing has worked. I've left it to try and boot for at least an hour several times, but it just doesn't want to boot.
I'm only having this problem on CM10, by the way.. 7.2 still works.
Strange issue
Check after reboot in BootMenu (in 'boot' section) if it still boots in 2nd_boot and not in 2nd_init or normal. Normally if it boots in 2nd_boot at first, it should stay in 2nd_boot.
Vicsa said:
Strange issue
Check after reboot in BootMenu (in 'boot' section) if it still boots in 2nd_boot and not in 2nd_init or normal. Normally if it boots in 2nd_boot at first, it should stay in 2nd_boot.
Click to expand...
Click to collapse
2nd-boot is selected.
Try a format to ext4 from bootmenu.
After doing this reboot and wipe data once, then it should work fine
Sent from my MB526 using xda premium
I had that problem too
thekguy said:
Try a format to ext4 from bootmenu.
After doing this reboot and wipe data once, then it should work fine
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I had this problem few months ago...
I have tried everything (in my opinion) and only flashin with sbf file helped, then installing Quark's rom again...
Well, sbf is the surest way, but the method posted above I've used successfully to downgrade from cm10 to miui gb
Sent from my MB526 using xda premium
thekguy said:
Try a format to ext4 from bootmenu.
After doing this reboot and wipe data once, then it should work fine
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
It boots into CM10 then I when I restart the phone it gets stuck on the splash screen again.
And what happens when only format to ext4+ cache wipe(no wipe data).
Also cm10 for me sometimes hangs or boot loops on first run, removing battery and powering up manually fixes the issue
Sent from my MB526 using xda premium
thekguy said:
And what happens when only format to ext4+ cache wipe(no wipe data).
Also cm10 for me sometimes hangs or boot loops on first run, removing battery and powering up manually fixes the issue
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Same thing happens, it just hangs.
It runs perfectly fine on the first run, but then when I reboot it it just hangs at the boot splash screen every time I restart it.
Motorola or cyanogenmod screen
Sent from my MB526 using xda premium
thekguy said:
Motorola or cyanogenmod screen
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
CyanogenMod screen.
Then you can't boot(after the first boot) even after formatting to ext4, data wipe+ cache wipe again?
Sent from my MB526 using xda premium
thekguy said:
Then you can't boot(after the first boot) even after formatting to ext4, data wipe+ cache wipe again?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Yeah, that's right. It's really weird, though.. because CM7.2 works flawlessly.
Really very weird. Does the booting problem occur even if you make no changes to the filesystem and simply reboot after first flash?
You can also try a sbf flash, though it probably won't help much
Sent from my MB526 using xda premium
thekguy said:
Really very weird. Does the booting problem occur even if you make no changes to the filesystem and simply reboot after first flash?
You can also try a sbf flash, though it probably won't help much
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Okay, I tried that and I think I figured out the problem. My phone is carrier unlocked and I'm with a different provider, so I have to flash a soft sim unlock on my phone which is causing boot problems on CM10.. any ideas on what I should do?
If your phone is carrier unlocked, then you don't need to flash any unlock
Sent from my MB526 using xda premium
thekguy said:
If your phone is carrier unlocked, then you don't need to flash any unlock
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
My phone is locked to a carrier, "unlocked" was a typo.
Hi guys, I have a problem that is huge for me. When someone calls me and I answer it, the timer stops at 00:01 and freezes, after which I get a force close, and after that I can't call anyone and noone can reach me because the same thing happens. What should I do?
For me it happens only some cases when I use data on EXT ROMs and I solved it always by wiping dalvik cache.
Which type of ROM you are using?
Sent from my NexusHD2 using xda premium
im using Cyanogenmod 10, i think it Jellybean, the kernel says jellybean r1.
If data on EXT it happens to me. Try wipe dalvik cache and fix permissions.
Sent from my NexusHD2 using xda premium
I have a quick question. When switching ROMs should I also in addition to factory reset, also perform a system/wipe to wipe the already installed custom ROM? Thanks.
It is generally unnecessary, but not a bad idea to do so. Most devs have their updater script format /system, but you'll find the occasional one that omits that one line.
Sent from my Nexus 7 using Tapatalk HD
Alright. So I shouldn't worry about performing system wipe?
Sent from my Nexus 7 using xda app-developers app
tsmith9191 said:
Alright. So I shouldn't worry about performing system wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think it's better to wipe the system. As I've faced many kind of froblem because of a dirty flash. And I've seen many bug reports on several ROM thread and it just came out that it's not the ROM but the dirty flash is causing the problem. It will probably take 1-2hr to get back to the previous position so what's the big didfference??
____________________________________________
Please press the thanks button if you find this helpful.
ashik992 said:
I think it's better to wipe the system. As I've faced many kind of froblem because of a dirty flash. And I've seen many bug reports on several ROM thread and it just came out that it's not the ROM but the dirty flash is causing the problem. It will probably take 1-2hr to get back to the previous position so what's the big didfference??
____________________________________________
Please press the thanks button if you find this helpful.
Click to expand...
Click to collapse
OK. So when switching ROMs I should perform factory restore, wipe all caches, as well as system/wipe to erase the ROM currently installed. I have done it that way before but I always get nervous when I wipe system, cause now it has no ROM installed at all and I don't want anything to happen in that case. But thanks for the quick reply
Sent from my Nexus 7 using xda app-developers app
tsmith9191 said:
OK. So when switching ROMs I should perform factory restore, wipe all caches, as well as system/wipe to erase the ROM currently installed. I have done it that way before but I always get nervous when I wipe system, cause now it has no ROM installed at all and I don't want anything to happen in that case. But thanks for the quick reply
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What could happen?? Hardbrick?? A little chance..... Here's what I think when I do something risky. Just Think like I don't have any device if I can get this device back it's bonus for me.
You can always flash a rom whatever it has one or not untill your device can be booted into fastboot. So don't be afraid if something bad(!?) happens and you can boot into fastboot mode. Once I even had no boot just the fastboot it took less than 5 min to get a system on it.
And dirty flash is always an option. I myself had and seen many people having problems with it.
_________________________________________
Don't just say thank, there is a button for thnking.
Clean is always the best! But always make a backup before the wipe process!
Wipe:
/system
/userdata
/.android-secure
/dalvik-cache
/cache