Hello all,
I am trying to restore a ROM's backup that I did and I got this message:
E:format_volume failed to unmount /system
Error while formatting /system
I tried to disable/enable VOODOO lagfix and /system legfix and its do the same. I also tried to do fix permissions.. but without help.
I am using CWM red ver 3.0.2.8x ROM valhala 1.2
Thanks on all the help!!
HQwarp said:
Hello all,
I am trying to restore a ROM's backup that I did and I got this message:
E:format_volume failed to unmount /system
Error while formatting /system
I tried to disable/enable VOODOO lagfix and /system legfix and its do the same. I also tried to do fix permissions.. but without help.
I am using CWM red ver 3.0.2.8x ROM valhala 1.2
Thanks on all the help!!
Click to expand...
Click to collapse
Common problem... You have to first flash a Bali kernel, restore back up, then flash a gb kernel. Do all of the above before rebooting
Sent from my SGH-T959V using xda premium
Related
I think i messed something after flashing the EXT4 mod because when i booted into recovery the text under blue line is orange and yellow and i don't remember it being like that before? i can hit reinstall packages and it loads cwm fine as far as i can tell? this is what it says please let me know whats wrong and how i can fix it please. thanks
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/command
#MANUAL MODE#
--Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/recovery.log
E:Cant open CACHE:recovery/recovery.log
E:Can't mount /dev/block/stl11
(invalid argument)
it is a know issue after flashing ext4, you are still ok, just click on reinstall packages and it will take you to cwm
yeah I'm sure everyone who flashed EXT4 is experiencing the same thing, I am too. CWM still works as far as I'm concerned. I've done like two restores, and flashed trigger rom successfully. I think everyone is getting those mounting errors.
Nevertheless, the phone is ridiculousness fast and smooth !! big ups to dsexton702.
slapshotx2002 said:
it is a know issue after flashing ext4, you are still ok, just click on reinstall packages and it will take you to cwm
Click to expand...
Click to collapse
Crap now that i think about it the OP did mention something about an error botting into CWM i guess this is it right?is it a false alarm?? and how do i fix it? or is there no way to fix it? thanks for the quick reply.
Bryanb82 said:
I think i messed something after flashing the EXT4 mod because when i booted into recovery the text under blue line is orange and yellow and i don't remember it being like that before? i can hit reinstall packages and it loads cwm fine as far as i can tell? this is what it says please let me know whats wrong and how i can fix it please. thanks
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/command
#MANUAL MODE#
--Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/recovery.log
E:Cant open CACHE:recovery/recovery.log
E:Can't mount /dev/block/stl11
(invalid argument)
Click to expand...
Click to collapse
thats because the recovery on the rom is not compatable with ext 4 but clockwork is hence why u can still get into clockwork but not the stock recovery.
yes OP is correct as of now there is no way of fixing it. just ignore it and click install packages and it works just fine
Bryanb82 said:
Crap now that i think about it the OP did mention something about an error botting into CWM i guess this is it right?is it a false alarm?? and how do i fix it? or is there no way to fix it? thanks for the quick reply.
Click to expand...
Click to collapse
will be fixed along with the chargeing animation once we get more ext 4 roms.
thanks everybody i feel allot better now but one more question. Even if i reflash odin and then reflash bionix the ext4 mod will still be there right? or do i have to do the mod again?
Bryanb82 said:
thanks everybody i feel allot better now but one more question. Even if i reflash odin and then reflash bionix the ext4 mod will still be there right? or do i have to do the mod again?
Click to expand...
Click to collapse
if u odin it flashes back the stock file system u would have to reconvert.
RaverX3X said:
if u odin it flashes back the stock file system u would have to reconvert.
Click to expand...
Click to collapse
i fixed the battery issue but i cant fix the recovery AKA cache mount error in recovery
im still working on it, also i found a way to convert back to rfs so you wont have the recovery cache mount issue but you also wont have ext4
dsexton702 said:
i fixed the battery issue but i cant fix the recovery AKA cache mount error in recovery
im still working on it, also i found a way to convert back to rfs so you wont have the recovery cache mount issue but you also wont have ext4
Click to expand...
Click to collapse
Ive been screwing around trying to get my partition for ext4. And I was able to change my cache mount to mount and now I'm not receiving the cache error. Dont know that I did anything to help it along but my phone seems fine other than the OC problems which are minor
Sent from my SGH-T959V using XDA Premium App
GDofWR420 said:
Ive been screwing around trying to get my partition for ext4. And I was able to change my cache mount to mount and now I'm not receiving the cache error. Dont know that I did anything to help it along but my phone seems fine other than the OC problems which are minor
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
WHAT!!! you fixed the error in red writing when you enter recovery before CWM!!!????
and what OC problems?
dsexton702 said:
WHAT!!! you fixed the error in red writing when you enter recovery before CWM!!!????
and what OC problems?
Click to expand...
Click to collapse
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App
GDofWR420 said:
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
try 1400 instead of 1375 for the core and internal maybe to 1200
also might have to warm the rom up to OC'ing because my 1.5 was extremely stable but not till awhile with the rom
dsexton702 said:
try 1400 instead of 1375 for the core and internal maybe to 1200
also might have to warm the rom up to OC'ing because my 1.5 was extremely stable but not till awhile with the rom
Click to expand...
Click to collapse
Kool ill stretch this baby out on 1.2ghz and work my way towards something a little higher. Also I made a note to try those settings next time I try 1.5ghz. Its wild though at 1.2ghz my quadrant scores are in the 1800's all thanks to your easy to follow steps. Thank you sir
Sent from my SGH-T959V using XDA Premium App
I was also screwing around in the sd card yesterday night and noticed I had 3 nandroid back ups I deleted the 2 oldest and kept the newer one now I'm also not getting that mounting error in cwm and as far as OC goes I've notice that my phone is stable at 1.5ghz but depending on which of dr honks kernels I use it requires different voltages:
the 2.1 UV it's stable at core voltage 1400mv and internal 1175mv and the non UV Kernel it's stable at 1400mv and 1150mv. in either one of these settings the scaling need to be set to conservatiove or performance starting at 200mhz instead of 100mhz.
ssmokey727 said:
I was also screwing around in the sd card yesterday night and noticed I had 3 nandroid back ups I deleted the 2 oldest and kept the newer one now I'm also not getting that mounting error in cwm and as far as OC goes I've notice that my phone is stable at 1.5ghz but depending on which of dr honks kernels I use it requires different voltages:
the 2.1 UV it's stable at core voltage 1400mv and internal 1175mv and the non UV Kernel it's stable at 1400mv and 1150mv.
Click to expand...
Click to collapse
yea i noticed they needed to be changed also but i wasnt sure to what
so thank you very much smokey!
also your saying that your ext4 right now, but you dont have the recovery issue?
ive only made one back up and it was on my ext4 sgs4g and im still having the recovery issue even after making some cache adjustments like godofwar did
hmmm need to figure this out
GDofWR420 said:
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
just a fyi, when you SEE "unmount" that means what ever your looking at is "mounted" when you click on it and see "mount" that means its unmounted. I had to pm a dev for that info.
I had to odin my phone to KD1 then formatted the fs to ext4 then flashed Bionix frost from cwm I went to recovery and I had those erros in the page. I went into reinstall packages/ apply update from sdcard/ Yes - Install /sdcard/update.zip then rebooted recovery and I had no more mounting erros in the recovery page. I hope this helps
I've been trying to get the phone back to a normal state so I can start over. I had problems after flashing GB and Valhalla. The first time I flashed Valhalla all was fine except the phone icon in the apps drawer was gone. Then it started to soft reboot constantly and not recognizing the SD card. So I did the ext4 format etc and re did it and all worked except it kept soft booting again.
Now when I load CWM it says
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
and so on..can't partition..restore back up
And Linda complains as is that the system is not available.
However I can still connect it via 'mass storage' and see the contents of the SD card and whatever else.
The phone will boot into now what is...
T959VUVKC1
2.6 Bali
FROYO.VUVKC1
http://forum.xda-developers.com/showthread.php?t=1129933
Flash that if you want a clean Froyo ROM to start off of.
If you want to stick to GB, follow my GB starter pack guide
http://forum.xda-developers.com/showthread.php?t=1223765
Well I some how managed to get GB and Valhalla back on. The only problem I had was it was soft reseting when I was trying to install busybox through the market and other apps. I discovered that the SD was not recognized. I then just disabled lagfix and it seems to be working fine as of now. Will disabling the lagfix affect anything else?
Well it'll lower your read/write performance on the /data, /system and /cache partitions but if you've never used the lagfix before you'll never notice how fast your phone can go. . If you follow the guide I linked you too, you'll have everything set up correctly.
i have the same problem as the op. i wasnt ever in gb but it has the same mount error..
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
so on..
i was told it was because of a "bad motherboard"
misteryibox said:
i have the same problem as the op. i wasnt ever in gb but it has the same mount error..
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
so on..
i was told it was because of a "bad motherboard"
Click to expand...
Click to collapse
Where are you trying to go to?
I cant restore my backup via CMW cuz there is an error "Error unmouting /system!" after i soft-bricked my phone.
I am on Official GB 2.3.6 with Dr honk Stock kernel+CMW+voodoo lagfix with installed of busybox 1.19.3. LAGfix are enabled for system/data/caches.
Unmount /caches
Mount /data
unmount /sdcard
unmount /system
how i do make mount work for /system?
Obies said:
I cant restore my backup via CMW cuz there is an error "Error unmouting /system!" after i soft-bricked my phone.
I am on Official GB 2.3.6 with Dr honk Stock kernel+CMW+voodoo lagfix with installed of busybox 1.19.3. LAGfix are enabled for system/data/caches.
Unmount /caches
Mount /data
unmount /sdcard
unmount /system
how i do make mount work for /system?
Click to expand...
Click to collapse
CWM recovery doesn't work with gb. You'd have to flash back to froyo. I've been able to do an advanced restore with data etc but not /system.
Sent from my SGH-T959V using XDA App
Not necessarily true. Just need to flash Bali kernel, restore nandriod, flash back cwm kernel.
Sent from my SGH-T959V using Tapatalk
Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/ log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
I don't know if this error is related but ok ....
Plz someone could help me?
I had this issue days ago, and it happened to me while I simply only turned off and on my phone.
This is probably caused by bad data and cache(?) partition or by bad (wrong) filesystem used. Try re-flashing STOCK rom eg. XXJPQ and over it custom rom of your choice. If the problem persists, try flashing custom kernel (g3mod) and convert file systems like this:
stl6 - ext4
stl7 - ext4
stl8 - ext2
I never had any issues with g3mod kernel's recovery with theese filesystems.
In gingerbread ROMs I had never issues with data or recovery.
bielmontes said:
Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/ log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
I don't know if this error is related but ok ....
Plz someone could help me?
Click to expand...
Click to collapse
Do you have an ext partition on your phone?
I got into similar problems with the scripts related to ext partition long ago
I too get the recovery error and it is not of any problem to us . This is solved by using g3mod kernel
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If u checked ur available memory when u had the problem, u probably had 0.00kb available. Just saying.
Sent from my GT-I9003 using xda app-developers app
bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If youre going from ROM that uses other filesystems than stock samsung's RFS filesystem such as ext2, ext4, so by flashing the stock ROM causes the bootloop WILL be there. (because the stock kernel doesn't support other filesystems than RFS) You need after flashing stock ROM pull the battery, reinsert it, reboot into recovery by pressing 3-keys combo and then "wipe data - factory reset" in recovery and then "wipe cache partition".
After this, the /data and /cache partition gets either mounted again or reformatted (not sure) with the rfs filesystem and the system will be able to boot.
BTW/little hint: You can see for couple of seconds after flashing the stock rom the phone boots into recovery, shows a couple of lines and there are 2 lines that are RED and say something like
DATA: blablabla... !
CACHE: blablabla... !
This process applies to the ROMs such as Purumod, Kyrillos and maybe others what have other filesystems used than the one used by the stock ROM (RFS).
Thats the description of the "bootloop" problem.
BTW... glad we could help and this has been fixed!
Is there any way i can change the file system to EXT-4 so that i can get the clockwork mod or can i do something else?
Now mine is RFS file system....
Tried installing some custom roms still my fs is RFS only
Can't able to install CYANOGEN MOD It stuck on the boot screen for approx 1 and half hour which is a black screen written "android" on it. bcoz of RFS file system i think
I JUST WANT THE CYANOGEN MOD.
PLEASE HELP ME OUT Is thr any other method for converting RFS to EXT 4 file system
U should flash cwm by tj_style via Odin , then u can flash any custom rom all of them are ext4
Sent from my GT-S5670 using xda premium
I tried all CWM it wont work out Getting dis error ''Can't Mount System'' with CWM 5
pranesh.rkz said:
I tried all CWM it wont work out Getting dis error ''Can't Mount System'' with CWM 5
Click to expand...
Click to collapse
Flash another stock rom
Sent from my GT-S5670 using xda premium
flash cwm boot into it
wipe data and cache
install rom
wipe data and cache
reboot
Hey.
I'm trying to root galaxy fit 2.3.6 stock ROM cwm recovery 5 ext4 and rfs. Anyway, I get this error about the update.zip file: Status 7(installation aborted). I did research, installed cwm recovery 5 WITH SUPPORT FOR RFS, but the error still appears. I CAN mount the system and sdcard in recovery.
Does anybody know a proper solution?Please help
Thanks
did you try ext3 format? in my case work well
Sent from my GT-S5670 using xda app-developers app