Hi,
I want to note that I've tried several methods of fixing my efs, but without luck.
I run TE and what I've seen is that instead of:
/dev/block/mmcblk0p1 on /efs type ext4(rw,nosuid,nodev,noatime,commit=20,barrier=1,nodelalloc,data=ordered)
I have a line which looks like:
/dev/block/mmcblk0p1 on /efs type ext4(rw,nosuid,nodev,noatime,barrier=1,data=writeback)
My question is, as a Terminal and linux total newbie/n00b, how can I make it just like in the first instance? What do I write? I'd love to repair my EFS to get my IMEI back Big thank you in advance!
Duobix said:
Hi,
I want to note that I've tried several methods of fixing my efs, but without luck.
I run TE and what I've seen is that instead of:
/dev/block/mmcblk0p1 on /efs type ext4(rw,nosuid,nodev,noatime,commit=20,barrier=1,nodelalloc,data=ordered)
I have a line which looks like:
/dev/block/mmcblk0p1 on /efs type ext4(rw,nosuid,nodev,noatime,barrier=1,data=writeback)
My question is, as a Terminal and linux total newbie/n00b, how can I make it just like in the first instance? What do I write? I'd love to repair my EFS to get my IMEI back Big thank you in advance!
Click to expand...
Click to collapse
https://market.android.com/details?...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
Oh yes, I forgot to mention: I ALREADY tried GS2_repair, HC-kTool, and NONE seemed to help solve my efs problem :/
In that case, your last chance before you send it back to Samsung will probably be to PM a member on here called Odia. He apparently fixes/recovers people's IMEI's/EFS for a small donation/'case of beer'.
Related
Hi all.
I have got my SGS II for 4 months and i was running it with stock rom and CF kernel. Yesterday, I was comming home from chrismas and was asked - as usual - to turn off my phone on the plane. Put it in plane mode and shut down.
Turned on for some series watching, turned off for arrival.
After that, my phone quit working: no SIM could be detected. After some research, I realized that my IMEI was set to 0 and Phone: unknown. I went back right away to stock, but it did not help.
By the time I flashed, i had no idea that efs folder did not came with cwm backup, so i have no backup of working efs folder.
I have some files on EFS folder, but i have no idea of what is "good" folder.
Can somebody point me to some direction?
I heard about some miracles perfomed by ODIA user, hehehe.
Thanks in advance.
Try this thread.
I did...
But I still cannot have access to change the efs files/dir. And still didn't figured how to have write access for these. Could you enlighten me?
Thanks!
To get write access you need to use a file explorer like Root Explorer (or similar) from the Market.
PauloSherring said:
But I still cannot have access to change the efs files/dir. And still didn't figured how to have write access for these. Could you enlighten me?
Thanks!
Click to expand...
Click to collapse
Are you getting "permission denied" and/or "read only filesystem" errors?
I take it you ARE running all commands with root priviledges?
It is working!
Thanks people! I've been struggling with this problem for only two days, but it feels like months! I needed to umount the /efs unit and mount again with other accesses priorities (r/w, i.e.).
In fact, this thread: http://forum.xda-developers.com/showthread.php?t=1261948&page=5 was the reason for me achieving this.
i had the same issue with my galaxy,
https://market.android.com/details?...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
this utility helped me to fix it.
Thanks to Helroz
Glad you got it working Paulo I can imagine it would be pretty stressy to have a working phone one minute and a reboot later no IMEI.
PauloSherring said:
Thanks people! I've been struggling with this problem for only two days, but it feels like months! I needed to umount the /efs unit and mount again with other accesses priorities (r/w, i.e.).
In fact, this thread: http://forum.xda-developers.com/showthread.php?t=1261948&page=5 was the reason for me achieving this.
Click to expand...
Click to collapse
Please could somebody tell me if there is any known method for backing up efs/IMEI data that works for the S5830i and if anybody has ever actually successfully restored their IMEI number for this model of phone?
I've read alot of information about differrent methods, although most of them are in the Galaxy S forums and I've seen one post in the Galaxy Ace S5830 forum stating there is currently no known working restore method for the S5830 (but not the S5830i).
Also, apparently (see http://forum.xda-developers.com/showpost.php?p=25718433&postcount=8) you can actually corrupt the /efs partition when backing it up if you are not carefull as it is a hidden partition that is not mounted by default when the phone boots. Apparently, if you don't unmount it after you've backed it up, goodbye /efs partition.
Even if there is no current working restore technique, I would rather backup now to be on the safe side and hope a restore method becomes apparrent in the future as I've already lost my IMEI information once (and managed to get a phone replacement under warranty luckily). I would however prefer to know how I can safely do so first.
Ok, so I've been looking into how to do this for a couple of weeks now and still nothing. Surely somebody must know some information regarding /efs or IMEI data on the s5830i?
I'm in an ADB shell at the moment and I've got an /efs folder in my root directory, but I've looked in this directory and it's currently completely empty (including hidden files). The only thing I can presume is that on my phone /efs is merely a directory that has been created for the specific purpose of acting as a mount point for the actual 'efs partition', which is not actually mounted at the moment for whatever reason.
Issuing the mount command confirms nothing along the lines of an efs partition is mounted. I've had a look in /dev and from searching this forum a bit more, I understand, efs is likely to be /dev/stl# (where # is a digit). So does anybody know which one it is?
I'm not going to do anything silly and start dd'ing it straight off but there must be some way of backing it up safely seeing as it has been done on many other phones. Also any information on when and how it is mounted (by Android OS) and how to mount it safely would be much appreciated even if this is more Android general than my specific model of phone.
I may be speaking to myself in this thread but in case anybody else needs an answer, it looks like Galaxy Toolbox can do an /efs backup and is compatible with the S5830i. See:
http://forum.xda-developers.com/showthread.php?p=25949902
https://play.google.com/store/apps/details?id=com.doky.sgtoolbox
Incidentally, that information seems to imply that the /efs device file is at /dev/bml15, which does exist on my phone, not that I plan on manually interacting with it!
I know this is an old topic and no one showed up here.
But I wanted to come to say to you THANKS! because you really helped me
kitsune0 said:
I know this is an old topic and no one showed up here.
But I wanted to come to say to you THANKS! because you really helped me
Click to expand...
Click to collapse
galaxy toolbox is the solution :good: i already try it ... work fine in restore and backup
terminal emulator
su press enter
busybox dd if=/dev/bml15 of=/sdcard/bml15.img press enter
angel.sea said:
terminal emulator
su press enter
busybox dd if=/dev/bml15 of=/sdcard/bml15.img press enter
Click to expand...
Click to collapse
1. Use SGY Toolbox
2. Use this .
http://forum.xda-developers.com/showthread.php?p=38823212
3. Then at last resort
Use the command given by above person
AW: Is efs/IMEI Backup Possible for S5830i
Yeah thats work for me too :thumbup:
Gesendet von meinem GT-S5830i
TLDR: Phone was bricked revived it now stuck with generic IMEI
Ok so basically my GS3 got bricked dont know exactly why but in recovery it said e: failed to mount /efs (Invalid argument) i was able however to revive it with this thread post #4 ( http://forum.xda-developers.com/showthread.php?t=2204960 ) but now my IMEI is "generic" 004999010640000 and now i cant connect to the network. Im on a mac and the only tutorials ive seen are for windows. my question is is there anyway to change it from the phone itself or on a mac? Sorry if this has been asked before but if anyone can point me in the right direction that would be great.
PS i know changing your IMEI is HIGHLY illegal but i just want to change it back to the original one on the back of the phone.
You're #2 today and #1073453 in total, asking for help with 00499... issue! Not nice...
Use the flipping search bar! :/
Im on a mac...
oh im sorry but if you read the whole thing IM ON A MAC so anyway to fix this would be great...
djembey said:
You're #2 today and #1073453 in total, asking for help with 00499... issue! Not nice...
Use the flipping search bar! :/
Click to expand...
Click to collapse
Restore your backed up EFS folder through whatever method you used .
No backup then a Samsung service centre .
jje
Ok so i have a backup but its the coorrupted one... anyway to open up the .img and copy the files manually on a mac? sidenote when i restore the corrupted one im in a boot loop
JJEgan said:
Restore your backed up EFS folder through whatever method you used .
No backup then a Samsung service centre .
jje
Click to expand...
Click to collapse
Sorry not a clue don't even know how to switch a Mac on .
jje
If your EFS dump is a full partition dump (it being .img suggests that), you can simply write it back in recovery with:
Code:
umount /efs
dd if=/sdcard/yourefs.iso of=/dev/block/mmcblk0p3
reboot
If that fails or throws errors, repeat the steps in the tutorial you linked to re-create an empty EFS partition.
By the way /efs is an EXT4 partition so neither Windows nor Mac (or any other BSD-derivate) are natively capable of reading it, only Linux computers (read: Ubuntu, ...) or specialized tools that simulate filesystem drivers are able to do so.
so i tried that and wasnt able to boot past the i9300 screen. any other suggestions?
d4fseeker said:
If your EFS dump is a full partition dump (it being .img suggests that), you can simply write it back in recovery with:
Code:
umount /efs
dd if=/sdcard/yourefs.iso of=/dev/block/mmcblk0p3
reboot
If that fails or throws errors, repeat the steps in the tutorial you linked to re-create an empty EFS partition.
By the way /efs is an EXT4 partition so neither Windows nor Mac (or any other BSD-derivate) are natively capable of reading it, only Linux computers (read: Ubuntu, ...) or specialized tools that simulate filesystem drivers are able to do so.
Click to expand...
Click to collapse
ugh
Ok so i havent updated this in awhile but here it goes...
First i installed ubuntu on my mac and converted my corrupted EFS partition to .iso and opened it in linux. Anyway no files in there.
Second the samsung service center here in alaska is only for TVs...
Third ill call samsung on monday but dunno what i can do besides save up for another phone or a octopus box or what you call it.
Hello.
I had problems with my EFS folder and IMEI.
Now i got it all back and running the Official Android 4.3 Firmware I9300XXUGMK6-DBT
But now i want to go back to custom roms ( Paranoidandroid ).
With the update to EMG4 Android changed the EFS folder.
That was the problem why i lost my IMEI.
What can i do, to get custom roms back !?
Everytime i flash ParanoidAndroid i dont get MobileNetworks.
Ask your question in Q&A section... this section is just for developers...
Hi mate ! Wrong section but i'll try to help you.
I read again your post, so, i guess you can simply flash an EMG4 modem !
^Try this before this :
I'll make it quick, and if you don't understand, i'll develop. Also, i apologize for my bad english.
1 ; Delete your EFS folder
2 ; Reboot in recovery, connect your mobile to the computer.
3 ; On your computer, start an ADB session and type, in the exact order the following commands :
adb remount
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
Once it's done, reboot your phone and check if your IMEI is back. If not, reflash an EMG4 modem and restart your smartphone.
Let me know how it's going, PM me if you want, or, you can add me on Skype ; Orath. (Don't forget the dot )
Okay so here it goes. I had missing IMEI problem in a custom ROM when not on a samsung base. I had a neatefs (app on android) backup which I tried to restore using HC ktool (Bad idea, I know). It gives me a successfully done message and tells me to reboot. Now my phone is stuck in bootloop no matter what (Stock firmware, wipe data, factory reset nothing works) and the recovery gives the error mentioned in the title.
/efs is unmountable for me. I tried various methods mentioned for S3 and Note such as connecting the phone in ADB mode and following the steps but none of that works.
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
AKAndrew41 said:
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
Click to expand...
Click to collapse
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
ruleh said:
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
I've tried all that, none helps. I've even installed a busybox as mentioned somewhere else which said that the syntax mke2fs is not available without a busybox. Nothing worked. Still unable to mount efs afterwards.
pHraiL^ said:
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
Click to expand...
Click to collapse
I'm pretty sure it won't damage anything, or at least to me didn't. Because whenever I want to reinstall a new ROM I always format everything I've mentioned earlier so I don't find it harmful for the device, as long as you don't have data worth backing up.
Also, wipe dalvik.
If you installed busybox, make sure you uninstall the previous version prin pressing uninstall, and them installing 1.23.1 because for me sometimes it says it's intalled, but after reboot I still have the old one.
After you do that, connect phone to PC and try running
adb shell
Once you do that, give a try to the command
umount -f /efs
even if it says it's umounted, then type
mount /dev/block/mmcblk0p3 /efs
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
Click to expand...
Click to collapse
These two are the commands everyone is talking about the S3 phone having same issue. I tried everything. The first command works and it shows something like:
"The filesystem will be automatically checked every 35 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override."
For the second line of code when I try, this is what I get:
"It says "mount: can´t find /dev/block/mmcblk0p3 in /etc/fstab"
Now I have also tried adding space and /efs to the second command. It gives me nothing, not even any error. So I presume it works but then when I reboot efs is still messed up. I have no idea what these commands does actually. I think it has something related to re partitioning. Shouldn't the second command line give the same output as the first one? Its been a whole day searching for this thing. I got my phone messed up real bad.
EDIT: One more thing, when I hit the # df command on ADB, it shows 3 drives (/dev, /cache, /emmc) when not in su and 4 when in su (/dev, /cache, /emmc, /system). No where it shows any efs partition. Is there suppose to be any?
EDIT2: After the second line command. Using mount -t following someone's guide I get the efs partition but I think it is way too small. See the attachment. This partition is gone again after reboot.
OH GOD I got it working. After more searching, I found out the the block used for efs storage in S2 is mmcblk0p1 not mmcblk0p3. Phew!
Follow the same commands to make it work. Just rename the block.
Here is a guide which helped me figure out the block: http://www.usoftsmartphone.com/t306464.html
Thanks everyone
im having same trouble now with the S7. the page you share not there anymore. please share me how to figure out the block