It seems that several users including myself had EFS problems - suddenly a corrupted efs dir which means no network and a generic imei
It seems that flashing completely wrong firmware, and especially cm10.1 can corrupt the efs dir in a nearly unrecoverable way - even with a efspro backup its not restore able, because the mount point in backup isent correct anymore like > Efs is located in block 3, not 1 and therefore efspro is unable to restore
So if you get this error
You have this problem - only way to restore efs dir is by writing these commands in terminal it seems >
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
this should remount it back to block3 and after a reboot restore backup with efspro this should bring back network and your original imei again
Until now i haven't seen any other ways to fix this
---------------------------------------------------------------------------------------------------------------
Dont forget to make a backup of EFS with efspro or/and ktool just in case!!
Hi all, i just replaced my sd-card so i can make a swap partition and speed up my phone.
any way.. i played with Swapper 2 options (swap and swappiness size).
after reboot my galaxy doesn't boot into the system i did a nandorid backup,moved back to Samsung official release, did a full system format and still i doesn't boot into the system.
when i'm restore to my cm backup it stuck on it writes that the restore succeed but it stuck on ''Samsung Galaxy SIII'' screen.
when the official release installed (from adb) it does a boot loop over and over (factory reset doesn't work).
another thing i noticed is that in the recovery it writes ''E:failed to mount /efs (invalid argument)''
that can i do? i think i did every thing i can
In recovery can you access the efs partition? If not then it probably is corrupt, you'll need to format it and restore your efs backup.
If you don't have an efs backup then you need a service centre.
I wouldn't mess with any partition software on this phone, too risky.
i don't have /efs partition
Ok so i managed to boot into official firmware and i found that i don't have /efs partition.
i figure this out from EFS Professional, EFS pro and the recovery.
im searching for an hours but with no answer.. - can i create /efs partition?
EFS Recovery
RReeD said:
Ok so i managed to boot into official firmware and i found that i don't have /efs partition.
i figure this out from EFS Professional, EFS pro and the recovery.
im searching for an hours but with no answer.. - can i create /efs partition?
Click to expand...
Click to collapse
Do you have any older backup files.
When you try to restore your backup file CVM or TWRP recovery will ask which partitions you want to restore.
If you see EFS partition on any of your old backups you can restore it.
If no the way to service is seen.
Hi!
I tried to install Android on Samsung Wave GT-S8500. I flashed FOTA and bootloader and got into recovery but since it can't mount /system (same goes for /data and /cache) I can't install any ROM or make any backup.
Is there any way to get those partitions to mount as they should?
wrong kernel. Search Kernel NAND and copy it on SD. You have Kernel SD and u need ro format SD for install any rom
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
edwinn said:
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
Click to expand...
Click to collapse
u need to use pit file for repartition your internal memory.flash your phone with pit file
ifhi said:
u need to use pit file for repartition your internal memory.flash your phone with pit file
Click to expand...
Click to collapse
Total Bull-sh-it!
Don't do this, @edwinn
You will restore your backup either with terminal command or within the custom recovery. Is it tar only or tar.gz?
tetakpatalked from Nexus 7 flo
edwinn said:
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
Click to expand...
Click to collapse
hello u should flash the tar file via recovery this should restores ur efs backup
tetakpatak said:
Total Bull-sh-it!
Don't do this, @edwinn
You will restore your backup either with terminal command or within the custom recovery. Is it tar only or tar.gz?
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
The efs.ext4.tar file is in a folder called "clockworkmod", together with files like boot.img, system.ext4.tar, nandroid.md5 etc.
So I took the next steps:
installed CWM Touch 6.0.3.2 via Odin
copied entire "clockworkmod" folder tot ext sd card
tried to restore from external sd card
After checking MD5 sums the error "MD5 mismatch!" is displated.
Deleting all data in nandroid.md5 was not succesfull.
Further help would be appreciated.
edwinn said:
The efs.ext4.tar file is in a folder called "clockworkmod", together with files like boot.img, system.ext4.tar, nandroid.md5 etc.
So I took the next steps:
installed CWM Touch 6.0.3.2 via Odin
copied entire "clockworkmod" folder tot ext sd card
tried to restore from external sd card
After checking MD5 sums the error "MD5 mismatch!" is displated.
Deleting all data in nandroid.md5 was not succesfull.
Further help would be appreciated.
Click to expand...
Click to collapse
There have been major changes done in CWM since early 6xxx versions. Do you remember which recovery version number did you use to create your backup? I had myself some perfect backups done with 6.0.2.7 that weren't restorable with 6.0.4.5 due to md5 mismatch.
The chances are good you'll be able to restore it, mate.
tetakpatalked from N7100
tetakpatak said:
There have been major changes done in CWM since early 6xxx versions. Do you remember which recovery version number did you use to create your backup? I had myself some perfect backups done with 6.0.2.7 that weren't restorable with 6.0.4.5 due to md5 mismatch.
The chances are good you'll be able to restore it, mate.
tetakpatalked from N7100
Click to expand...
Click to collapse
I found out that the backup was made with Online Nandroid v9.51 (The recovery.log file says so :victory. No info on the CWM version number. It may have been a very old recovery which had a bug that created nested /0 folders in the file systems after every data wipe. I didn't discover that issue until recently . More info on this bug:
http://forum.xda-developers.com/galaxy-s3/help/storage-emulated-0-0-0-flashing-roms-t2214356
The backup may include the nested /0 folders. Perhaps that is causing the checksum mismatch?? (Since the system folder was formatted afterwards)
Anyway. I tried a new non-touch cwm recovery, version 6.0.4.3. No success.
Would you recommend to proceed with the terminal thing? Thx
edwinn said:
I found out that the backup was made with Online Nandroid v9.51 (The recovery.log file says so :victory. No info on the CWM version number. It may have been a very old recovery which had a bug that created nested /0 folders in the file systems after every data wipe. I didn't discover that issue until recently . More info on this bug:
http://forum.xda-developers.com/galaxy-s3/help/storage-emulated-0-0-0-flashing-roms-t2214356
The backup may include the nested /0 folders. Perhaps that is causing the checksum mismatch?? (Since the system folder was formatted afterwards)
Anyway. I tried a new non-touch cwm recovery, version 6.0.4.3. No success.
Would you recommend to proceed with the terminal thing? Thx
Click to expand...
Click to collapse
I am sure it is possible to disable md5 check
tetakpatalked from P5110
i have big problem !!, i own galaxy s3 (i9300) and i use android 4.3 , everytime i try to flash custom rom like cyanogenmod or other rooms im lost network and connection of sim , i do backup to efs file and restore it in the custom rom but this does not work ,I notice that /efs unable to mount in twrp recovery mode i tray to mount it using this command mount -w -t ext4 /dev/block/mmcblk0p3 , but this give message sayes mount: mounting /dev/block/mmcblk0p3 on /efs failed: Operation not supported on transport endpoint
PLEASE I NEED HELP !!!
Fail to mount us 9/10 times a borked recovery (twrp). Flash another recovery or flash a stock rom via odin and start over.
Sent from my HTC One M9 using Tapatalk