Hello people
My friend his phone (Samsung Galaxy Ace S5830) was really slow, so I suggested to root the phone and install a new custom rom. But something went wrong, first I rooted the phone, that went well, but than I wiped the data/factory reset and the cache partition and tried to install a new custom rom. But it ran into an error.
-- Appling Muti-CSC --
E:failed to mount /system (Invalid argument)
Click to expand...
Click to collapse
:crying: Now the phone only boots up to the samsung logo and than it stops :crying:
:fingers-crossed: Does someone has an solution :fingers-crossed:
Greetings Gio
*Sorry for the bad English..*
install the custom recovery and put it on your sd card then from the stock recovery choose(apply update from sd card) and choose the custom recovery file and flash it then install any rom and flash it by choosing (install zip from sd card) from the custom recovery menu
i hope that i hepled
Sent from my legend ACE using tabatalk
It happened the same with mine once, just try what nizar.nasani said, it should work! :good:
Flash srock rom and than go recovery and wipe every thing it will work.
Hit Thanks if i Help,
Via ace s5830i.
please
Galaxy_Guy said:
install the custom recovery and put it on your sd card then from the stock recovery choose(apply update from sd card) and choose the custom recovery file and flash it then install any rom and flash it by choosing (install zip from sd card) from the custom recovery menu
i hope that i hepled
Sent from my legend ACE using tabatalk
Click to expand...
Click to collapse
dear sir, if you have the custom rom please upload for me please ( samsung galaxy ace duos sch-i589)
i tried to install jellybean to samsung galaxy ace s5830.but i didnt backup my data before installing firmware.the mobile stucks showing 'ANDROID'.recovery mode and downloading mode doesnt works.what should i do?
hai this is ramesh
I have rooted my samsung ace gt s5830i......but it is can't rebooted till now always showing boot screen.....
if i entered into recovery mode it is showing - Appling Muti-CSC --
E:failed to mount /system (Invalid argument)
can u people help me out in this problem
Related
Hello,
I flashed MIUI and it was very buggy for me, all apps were crashing and so on. Then i decided to flash Darky 10.1.
Followed the tutorial without any issues, but after this i got no signal. Snooped around the OS and found out it did not see my sdcard. After booting in recovery mode I saw that it could not mount the efs partition.
If i try to mount it via shell i get:
Code:
# mount /dev/block/stl4 /efs
mount: mounting /dev/block/stl4 on /efs failed: Invalid argument
I unfortunetly have no backup of the efs partition.
Did anyone else experience this problem or has a fix for this?
Push. I have that problem too... I was on Darkys ROM for some months without any flashing problems. Now i wanted to change from Darkys ROM 10.1 (Gingerbread 2.3.4) to Galnet MIUI. I had to downgrade to Froyo and then install the CWM zip in CWM. This was NOT succesful. It always says "Installation aborted (Status 7)". Then i tried to install CyanogenMod 7.1. Upgraded to Gingerbread Stock with CWM 3 and when i first flashed it via ODIN the phone first booted in the standart Android CWM display (dont know the name sry). The phone automatically formated cache etc. but then it showed me 2 times "/efs is not mounted". I was able to boot and to open CWM but ALWAYS when i want to install ANY CWM ROM it shows me the message with Status 7 ...
How can i mount /efs again and make CWM ROM Flashing able again?
Thank you.
someone help me plz
i had problem with my galaxy n7000
when i try to install the offical rom it's stop and can't complete.
it give me this massage:
failed to mount /sd card
your storage not prepared yet, please use UI menu for format and reboot actions
when i use odin to flash offical rom it's give me fail
sorry about my bad languge
Guys need your attention & a consoling solution for my bricked phone, that can go in recovery & download mode. But the stock recovery mode says
--Applying multi CSC--
E:failed to mount/system(Invalid arguement)
E:failed to mount/cache(Invalid arguement)
E:cant open /cache/recovery/log
The troubled began when i added internet tweaks to build.prop.
When i reboot, phone got stuck at samsung logo.
Then when i opened cwm their i found error mounting system, & was unable to restore backups but when i used Rafael's "FORMAT ALL EXT4.ZIP" i was able to mount /system in cmw but these errors got shifted to stock recovery
now i'm able to flash zips & restore backups but of no use. still phone stuck at logo
Do i need to take my phone to Service center or any other advices?
nayser said:
Guys need your attention & a consoling solution for my bricked phone, that can go in recovery & download mode. But the stock recovery mode says
--Applying multi CSC--
E:failed to mount/system(Invalid arguement)
E:failed to mount/cache(Invalid arguement)
E:cant open /cache/recovery/log
The troubled began when i added internet tweaks to build.prop.
When i reboot, phone got stuck at samsung logo.
Then when i opened cwm their i found error mounting system, & was unable to restore backups but when i used Rafael's "FORMAT ALL EXT4.ZIP" i was able to mount /system in cmw but these errors got shifted to stock recovery
now i'm able to flash zips & restore backups but of no use. still phone stuck at logo
Do i need to take my phone to Service center or any other advices?
Click to expand...
Click to collapse
The reason you are getting those errors is that stock recovery cannot handle ext4, that's normal.
Probably the simplest thing to do would be to follow the unbrick tutorial:
http://forum.xda-developers.com/showthread.php?t=1840645
thanks for specifying the Ext4 problem...
can i get back to Ext3 by flashing any zip through cmw recovery?
Well rfs is the default file system format, not ext3. If you use this version of CWM then you can go to mounts and storage > format /cache, /system and /data back to rfs. However you will obviously now have no ROM on your phone so will still need to either restore a backup or flash a zip of a ROM that includes the entire /system folder, which is most, if not all. I've never tried this technique by the way, so no guarantees here.
Also try to restore only Nandroid backups made with the same version of CWM that you are using to avoid problems.
Hy there,
I installed a costume rom the other day and realyzed that after doing that the phone didn't recognized the sim anymore. I tryed installing the rom again but still the same result. Afther that i tyed installing a firmware using odin and now the phone won't start at all(it only oppens in download mode ). When i tryed to install the firmware it appeard an error:
E:failed to mount /dbdata (Invalid argument)
--Copying media files...
E:failed to mount /dbdata (File exists)
E:coppy_dbdata_media:Can't mount /dbdata youre storage not prepared yet. Please use UI menu to format and reboot action.
.....
the thing is that when i try to format it requests a key/password and i don;t know what it is and when i try to install again the rom it says that there is no space left. What can i do?
Please help!
I just had the same error on my I9000 (after trying to flash back to the stock Samsung ROM). I fixed it by following the instructions here, which worked perfectly for me:
http://blog.kalpetros.com/2012/04/how-to-fix-cant-mount-dbdata-error-sgs.html
u can also get it here
http://forum.xda-developers.com/showthread.php?t=2149455
its common error so juz chill n read carefully.
Sent from my GT-I9000 using xda premium
:good:
Thanks a lot for this post.
My i9000 was stuck in reboot loop after downgrading from CM10.
this resolution fix the issue
I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?
Amphibian59 said:
I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=1640906
Amphibian59 said:
I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?
Click to expand...
Click to collapse
You should factory reset and wipe cache and dalvik cache partitions. If else fails, try flashing a different stock ROM.
gsstudios said:
You should factory reset and wipe cache and dalvik cache partitions. If else fails, try flashing a different stock ROM.
Click to expand...
Click to collapse
Thanks guys. Meanwhile I managed to track down the XXJVU ROM and now have the phone up and running again on Cyanogenmod 10.2.1. But despite wiping cache and Dalvik cache, and factory resetting, it is still rooted! There is no Superuser app but #Superuser is still in the settings menu, and my bank's app reports that it won't work because the phone is rooted. Very odd. I suppose I'll have to try a different stock ROM, but why doesn't root disappear when flashing a stock ROM?