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.
Related
Hello,
I've tried time by time and i can't make a backup on any rom
ive tried the squadzone's recovery and anothers as THIS and had no success
Everytime
Backing up system...
Can't mount /system!
Click to expand...
Click to collapse
whyy? its possible to backup any rom on SGM ?? (ive tried with stock and custom too)
Thanks for help,
hreyit said:
Hello,
I've tried time by time and i can't make a backup on any rom
ive tried the squadzone's recovery and anothers as THIS and had no success
Everytime
whyy? its possible to backup any rom on SGM ?? (ive tried with stock and custom too)
Thanks for help,
Click to expand...
Click to collapse
the error is stating that while backing up recovery is not able to mount /system
try to mount /system before backing up rom. it can be mounted from mount and storage option
try to reflash latest cwm which is 5.0.2.8
try to wipe cache and dalvik cache before backing up
I think this problem is with stock ROM Or GB.
I was Flashing Emanom v5
I want to backup GB to restore when in need but, CWM v4 throws this errorBackup error
E: Can't open /cache/recovery/log
I Prepared:
1, Flashed GB through odin without SD mounted and android booted.(with sound in Samsung Logo)
2, Changed some Settings in Android
2a, Rebooted again with Mounted SD(to check if booting ssuccesfully with partitioned SD)
3, Now Rebooted to downloading mode
4, Flashed CMW Recovery v4
4a, Here Android succesfully booted, then I Rebooted in CWM.
5, In CWM, it show the error- E: Can't open /cache/recovery/log
6, when I tried to backup it doesn't
7, Wiped data + Cache
8, Re-tried to backup but it throws that err again.
9, Now I booted Android it does'nt boots(show Samsung Logo but no Sound and boot loops)
So I left off and Flashed Emanom
with whole process skipping steps 5-9
Here With Emanom v5, in CWM Recovery
That Error Again but when I backed up successufully towing error again.
Now what Step I left or any wrong do I did.
If backup-ing GB is possible then we could just restore it to flash any custom ROM without flashing through Odin and requirement of computer.
Sent from xda premium
Stock ROMs can't be backed up right ?
Even if you backed up, its not able to restore.
coolsandie said:
Stock ROMs can't be backed up right ?
Even if you backed up, its not able to restore.
Click to expand...
Click to collapse
if it is backed up i think it can be restored easily.
but to make it compatible with stock rom the person(squad) who ported the recovery needed to make the recovery compatible with rfs partition but its compatible with ext partition
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.
hi
Im having a lot of problems with my phone, I tried to load a new ROM, and I cant!!
Im using CWM 6.0.2.8
when I boot up it says
Cant Mount Cache/recovery/command
Cant Mount Cache/recovery/log
Cant Open Cache/recovery/log
Cant Mount Cache/recovery/last_log
Cant Open Cache/recovery/last_log
when I do a factory wipe, it gets stuck on
Formatting /cache
When I try to wipe/format the cache partition, it is the same story.
When I try to install a new rom, I get
image attached. CAN SOMEONE PLEASE HELP. Also some of my root software is corrupt.
What do I do?
I think I had same problem, wiping the cache part took quite long, but I eventually was able to install my new rom... though all my apps are still there, but at least part of the new rom is there (custom nav bar)
pretty much the same errors I got
ps: you're trying to flash cm 10.1, do you have a kernel for it ? read somewhere you shouldn't use CWM for flashing cm 10.1 with kernel ...
found it: http://forum.xda-developers.com/showthread.php?t=2167381
[ known issues ]
adb doesnt work in recovery (can be fixed)
USB storage doesnt mount in recovery (can be fixed, i think)
formating data partition WILL FORMAT THE INTERNAL STORAGE (FIXED IN v02)
external SDCARD is required to take backups and flashing ROM (FIXED IN v02)
do not use this for flashing CM10.1 (u will need to use the CM kernel for that)
that's what the link says, you need CM kernel for it
I am working on Ubuntu 15.04 and I used the Heimdall suite to do the necessary flashing.
Before I start: I created this post to share my experience with trying to flash a custom ROM on the GT-i9000 and receive some suggestions, though my main concern is the fact that I am unable to mount /system and /data. And yes, I have read posts concerning this issues, but they were too vague, so I decided to write my own.
First I figured I should flash a custom recovery, so I tried flashing the latest CWM for the galaxysmtd in Download Mode and it appeared to have been successful, though when I pressed the 3-button-combo (UP-HOME-POWER), It would boot the default Android System Recovery.
I tried flashing a few CWM and TWRP recoveries (though I didn't try PhilZ Touch, because goo.im is down and I couldn't find a proper PhilZ Touch recovery anywhere else), though I noticed that none of them would work, even though the flash was successful. So I figured I could try flashing a kernel, which would include some recovery - and it worked, to my surprise, though after attempting to wipe a few folders, I got the error: unable to mount /system and /data.
So I came to realise that the only way for me to get a working custom recovery was to flash a kernel, which should include a working recovery. So I ended up flashing Mackay_kernel_0.692_twrp_CMC-signed.zip, which includes TWRP v2.8.0.0. The recovery seems to work fine, though the same error persists: unable to mount /system and /data.
I tried formatting /system and /data, though to no avail: it just forced the recovery to reboot (I have attached the recovery log to this post).
Any help is much appreciated!
I am glad to inform that I managed to resolve the issue by reverting to the stock firmware, ROM and kernel by using Odin v1.83. Though this leaves me with the default recovery, which isn't able to flash a 5.1 ROM.
I tried flashing a kernel with CWM and then flashing a 5.1 ROM with said CWM recovery by installing its .zip, though this method causes the same issue: unable to mount /system and /data.
I tried installing one of the 10 stable versions. I was on stock jw4 with cf+cwm karnel. It started installing and then went into boot in middle for no reason. But it didn't boot. It just kept booting into recovery (not the cwm version i had) with the cm logo.
I tried installing again but it aborted installation every time. (didn't check the log)
I then tried to go back to stock but never boots,in recovery i get a bunch of:
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.
system unable to Format /data...Internal SD card cannot be mounted
rfs format failed on dev block etc etc etc
I tried all the ways i found here but none helped,worked on it for hours. I also flashed a bunch of stock versions with no luck. All just went to recovery with all these erros. Only thing that actually booted was a very old version stock jp something,got same message on recovery but then booted into...cm10 . I just got the boot and then black screen with buttons looking like they are on.
I then gave up and decided i would install cm and hopefully that would be compatible with what ever was changed since it happened because of it.
I now tried installing all the 10 stable versions and then all the 11snapshots. I either get error 7 or 0 and installation aborted or the same thing that happened the first time-it starts installation and then boots, gets stuck in (cm logo) bootloop and ends up in recovery.
ATM my phone is kind of bricked i guess. How do i fix this?