respected developers
i am a international galaxy s3 user I9300, i have lost my efs folder while flashing ROM, i messed up everything . i have tried flashing with Odin also does not work, it passes but does not boot stucked on the Samsung logo. when i put it on recovery mode it shows efs failed to mount. while reading some thread here i found that it can be recovered by flashing through flash box, so will the handset be recovered by flashing through flash box like z3a... plz helppp..
Read this:
http://forum.xda-developers.com/showthread.php?t=2393289
Unless you have an efs backup, or flashing an EMG modem enables your efs partition to be read again, then you are basically screwed and need a service centre.
Related
HELP!!!
After i tried using App2sd on my rooted S3 I9300 (Intl version), my phne went into a boot loop, and apparently i tried fixing it by installing a new rom..now, here comes the real problem..I installed a wrong ROM, it seems (although the rom is for i9300, it is for a different region)..
So after installing this Rom using odin, i get the message "e: failed to mount efs folder"..
Now im lost, especially because i have no backup of any kind...Is my efs folder corrupted??? and the phone still wont go past the samsung logo..only hope i have is that i can enter into recovery mode
Any suggestions ??? Please..anything...
http://forum.xda-developers.com/showthread.php?t=2393289
sent from the state where marijuana is NOT illegal !
Hei,
I was running 4.3.1 Dirty Unicorns and wanted to flash Smartdroid.
So, flashed Devil recovery and tried to flash the ROM.
It gave me message that there's an error in the zip file.
I was just playing with the options available in the recovery and selected some option, which I don't remember now.
After that, the went into bootloop. "Samsung Galaxy S3 I9300" appears on the screen and the phone reboots again and again.
This loop continued.
The phone could be put in Download mode.
Then, I flashed CWM 6.0.4.4 and flashed 4.1.2, which I downloaded some time back.
It went on well. I could boot the phone and had set it up.
However, I couldn't connect to network.
The IMEI was some default one.
Rooted the phone and tried to restore the backup of efs folder using HC-Ktool.
After restore, when I booted the phone, it didn't boot.
"Samsung Galaxy S3 I9300" appears on the screen and the phone reboots again and again.
I tried flashing the ROM again, CWM again etc etc.
Nothing worked.
In one occasion, after installing CWM 6.0.4.4, I restored from NANDROID backup. Restore was successful.
But, it wouldn't boot.
Same "Samsung Galaxy S3" appears on the screen and the phone reboots again and again.
Once, I flashed Dirty Unicorns ROM from zip via CWM. Still the same.
What is happening and how to solve it?
Any help is greatly appreciated.
Regards,
Babloo
Wipe Data/Factory Reset -> Download mode
Flash latest Android 4.3 from Sammy through Odin, preferably XXUGMK6 or newer.
Hei,
This worked!!!
Thanks.
Why flashing 4.1.2, Dirty Unicorns didn't work and this one worked?
If you can explain, that will be helpful to all.
Now, though the phone is booting, the efs folder is corrupted.
IMEI number is not what it should be.
I have a backup of the efs folder taken using HC-Ktool long back.
So, the ROM on which efs folder was backedup will be different that the ROM I have now. (Does it make any difference?)
Can I just root and restore that efs folder using HC-Ktool?
Thanks for the help!!
Regards,
Babloo
Edit:
If I flash CWM Recovery 6.0.4.4 and restore the NANDROID backup that I took before I started screwing my mobile, will everything be fine?
Sounds like you tried to flash a corrupt file, always check the md5 before you flash.
EFS is totally separate to the rom, format the partition, restore your backup then factory reset should return your imei on the current rom.
Nandroid will not fix the efs, unless you used a custom backup process that included the partition -the default settings would not do this.
Hei,
"format the partition, restore your backup"
For this, can I just root the phone and use Ktool to restore backup?
If you suggest any other procedure, pls give me more info.
-Babloo
Hei,
After the previous post, I could restore my phone from NANDROID backup that I took yesterday, before the whole mess.
After that, I tried to restore the efs folder using HC-Ktool from efs.img.
It gives the message that restore is completed.
But, after reboot, the IMEI remains the same wrong one (the generic 004999...)
The size of efs.img is 20.48 MB.
I tried to restore using the terminal method.
With the command "unmount /efs" I get error message "sh: unmount: not found"
How can I restore the efs and get back my IMEI?
When I tried to "open" the img file in Windows, it couldn't open. It says that the file is corrupted.
Could it have been really corrupted or it is just that Windows is unable to open it?
I restored the efs using the same backup file.
Why is it not working now?
-Babloo
You are trying to skip essential stages and hurry to finish, but your partition is still corrupt -you can't restore anything to a corrupt partition.
Search and read someone who has succeeded doing the same thing, follow their guide exactly.
Hei,
boomboomer said:
You are trying to skip essential stages and hurry to finish, but your partition is still corrupt -you can't restore anything to a corrupt partition.
Search and read someone who has succeeded doing the same thing, follow their guide exactly.
Click to expand...
Click to collapse
I have been searching for a proper procedure to format the efs partition since your post.
Whatever I found didn't work for me.
Can you please point me to any post that you know?
-Babloo
Guys,
Any ideas?
-Babloo
Hello, I'm new member in here. Today I flashed UltimaROM to my SGS3. Before the flashing I installed Philz touch recovery and saved Nandroid, modem and EFS backups in my PC. After the flashing no IMEI number was shown and I got a message saying " Insert SIM card....". So i tried to restore EFS in custom restore option in philz recovery. Even though it showed restore successful , IMEI number is still unavailable and i couldn't connect to mobile network. I also tried ktools to restore efs but no result. Can someone please help me regarding this issue.
What version firmware did you have before you first flashed? If it was really old then that could be the problem.
Flash a 4.3 stock rom, factory reset them boot and see if your efs is read again.
boomboomer said:
What version firmware did you have before you first flashed? If it was really old then that could be the problem.
Flash a 4.3 stock rom, factory reset them boot and see if your efs is read again.
Click to expand...
Click to collapse
Thanks for the reply. I had 4.1.2. If I flash 4.3 stock ROM can i retrieve my IMEI ?
If you flash a 4.3 stock it will update your efs to v2 and should enable it to be read in all newer firmwares.
I have a now bricked Samsung Grand Neo GT-i9060. This happened because after rooting it I tried to unlock the bootloader using EZunlock app. After restart it wont start and was stuck at the Samsung Boot Logo. I didnt happen to take a backup of the EFS folder. On the Android(3E) Recovery Screen it shows "E: Cant Mount EFS(Invalid Argument). I have another GT-i9060. I tried flashing Stock ROM using ODIN and repeatedly and tried Kies also. Every time it will get stuck at the android updating and then say EFS not mounted. I was thinking of using another EFS folder of same modelGT-i9060 and edit it for my IMEI number. Can I do say and if possible at all, how do I flash the edited EFS folder back into my bricked Grand Neo? Please help as i havent made any backup of my EFS folder.
Hello All,
i'm trying to help my friend to unbrick a S3, it just stuck at Samsung Logo forever. I tried to root it, install TWRP, flashed a custom rom (stable as per reviews), reboot it and no go, redo everything again with a stock rom, and still no go. Can anyone help? Thanks in advance.
One thing i found out that when i boot to recovery mode (original android) it does have a error message saying "E: failed to mount /efs (Invalid argument)" will this be the cause ?
rayzx said:
One thing i found out that when i boot to recovery mode (original android) it does have a error message saying "E: failed to mount /efs (Invalid argument)" will this be the cause ?
Click to expand...
Click to collapse
Hi rayzx,
according to what I know, "EFS" is the partition that holds the IMEI (International Mobile Equipment Identity) of your phone. This IMEI number is unique to your phone (Dual-SIM Phones have two IMEI Numbers though). Flashing and reflashing ROMs only will not help here, since flashing (proper) ROMs will/should leave the EFS partition untouched anyways. If that partition gets destroyed / corrupted (commonly referred to as "IMEI-Brick") you will have a hard time restoring it - unless you have a complete backup of the (Stock) ROM INCLUDING its EFS partition. You would have to flash it back up onto the device. Without having that kind of backup, special (expensive) equipment and licensens for doing this are required. Since tampering with the EFS Partition (or tampering with the IMEI) is illegal in most (if not all) contries, the only and easiest way I see is sending the device in for repair to SAMSUNG or a specialized & licensed repair shop - as far as I remember you would need to povide/send the phone itself and the sticker belonging to the phone with its IMEI Number clearly visible.
@rayzx: damaged efs-data don't prevent booting. So take latest firmware & Odin from sammobile.com, flash it. If Odin finshes with 'succeeded', boot into recovery and exec factory reset. Phone should boot then. If you see a factory IMEI 0049..., try KIES-repair function.
If this fails: service center (as said above).
rp158 said:
@rayzx: damaged efs-data don't prevent booting. So take latest firmware & Odin from sammobile.com, flash it. If Odin finshes with 'succeeded', boot into recovery and exec factory reset. Phone should boot then. If you see a factory IMEI 0049..., try KIES-repair function.
If this fails: service center (as said above).
Click to expand...
Click to collapse
Agreed..
Sent from my HTC One M9 using Tapatalk
I think your emmc is dead i had the same probleme but i could get into recovery.. try to glash a pit file if odin stuck u need to change the motherboard