greetings, ive read several threads about the IMEI and efs thing but unfortunately i havent found a solution for my problem yet.
I´ve lost my IMEI because i deleted my efs folder from the root folder of my phone (galaxy s3) and i had no backup. Someone restored the IMEI with Zbox or Octopusbox (not sure which one it was) and everything worked fine. So i made an efs backup and flashed Cyanogenmod, but after flashing the Rom my IMEI was lost again (0049...) and the phone couldnt find a network. Restoring the efs backup did not work and so i had to go back to stock and let the guy restore the IMEI again.
And here comes my question: I am currently on stock rom with rooted kernel (havent flashed any rom since the second restore because i dont want to risk losing the IMEI again) and i really like to change the Rom because you know stock rom is kinda bad. Does anyone have a clue what i need to look out for or why my IMEI gets corrupted on flashing another Rom?
What version of firmware did it come back from the repair with?
Usually a poor repair will install an older firmware, with efs v1, as boxes won't work on v2. Trying to update to a newer firmware, v2, will corrupt the imei.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
What version of firmware did it come back from the repair with?
Usually a poor repair will install an older firmware, with efs v1, as boxes won't work on v2. Trying to update to a newer firmware, v2, will corrupt the imei.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
the firmware wasnt changed at all, it was UGMK6 stock with CF-rooted Kernel. the IMEI got restored via samsung tool on my pc and it got connected to the box via UsbOverEthernet client. The console only showed like:
-checking root access
-writing IMEI to phone
-patching modem
-ok
is there a way to check if i have efs v1 or v2?
Related
my imei is null/null ive tried flashing to stock rom http://forum.xda-developers.com/showthread.php?t=1506330 but it didnt recover the imei. is there anyway to fix this?
Stock modem.
rangercaptain said:
Stock modem.
Click to expand...
Click to collapse
Does not work, ive tried the modems from http://forum.xda-developers.com/showthread.php?t=1769255
You have to return to stock completely.
rangercaptain said:
You have to return to stock completely.
Click to expand...
Click to collapse
Sorry to ask but, how do i do that? Is it this? http://forum.xda-developers.com/showthread.php?t=1506330
Ive flashed the AT&T stock rom already and it doesnt fix it
I had to do this the other day, for the same reason. Returning to stock Gingerbread from the link you posted did not restore the IMEI for me. However, I found a stock ICS .tar online that DID restore my IMEI: http://www.hotfile.com/dl/162779447/3bb6230/I717UCLF6_I717ATTLF6_ATT.zip.html
I did a full nandroid backup, flashed stock ICS and verified the IMEI had returned, re-flashed TWRP and made a backup of only the EFS partition, restored my full nandroid backup and then restored the new EFS backup over that. Worked great and I had almost no downtime.
Only issue I have now is flashing the GB modem sets my IMEI as 0. I normally wouldn't care, because I can still connect to everything, but Cerberus won't run without a valid IMEI. Restoring my EFS backup does nothing. Returning to the ICS modem restores the IMEI again. Blah.
still availible?
Do you by any chance still got the file, I have been looking for such a file like that, my imei shows null as well as the baseband does and i have tried every single modem or ROM i've found , had no luck, most of the roms will just reboot every 2 min on my galaxy note, but 1 stock ICS at&t rom, works perfectly but got no luck getting back my imei, would be so great if you could help.
johnus said:
I had to do this the other day, for the same reason. Returning to stock Gingerbread from the link you posted did not restore the IMEI for me. However, I found a stock ICS .tar online that DID restore my IMEI:
I did a full nandroid backup, flashed stock ICS and verified the IMEI had returned, re-flashed TWRP and made a backup of only the EFS partition, restored my full nandroid backup and then restored the new EFS backup over that. Worked great and I had almost no downtime.
Only issue I have now is flashing the GB modem sets my IMEI as 0. I normally wouldn't care, because I can still connect to everything, but Cerberus won't run without a valid IMEI. Restoring my EFS backup does nothing. Returning to the ICS modem restores the IMEI again. Blah.
Click to expand...
Click to collapse
Hi
I know there is plenty of threads but i still dont know what to do (my english not so good)
So my history begins with stock I9300XXELLA i think - i rooted it and flashed some other roms later, few days ago i decided to try this 4.2.2 leak and i flashed fantasy rom. It asked me if i want to do backup of my efs so i did. Later it asked me about new modem i think, i agreed too. After installing this rom i found i cant connect to my network and my imei is generic (000499). I tried to restore my efs backup with ktool but it only got me to factory mode opening (ktool saw efs backup but couldnt find nv_data.bin there - its there i checked). Next thing i did was flashing stock rom
I9300XXELLA by ODIN and trying to restore efs again this time with Samsung I9300 EFS Backup. It said its complete but i still have no network and my imei is still generic. What should i do? I heard about 3 file rom but i dont know which to flash. Sorry for another thread about this but its my last hope.
PS. My efs backup looks like this EFS.tar.gz--->EFS(folder)-->files
Looks like efs restore didn't go right. Flash stock 4.1.2 , stock basebsnd again and try restoring it.
sent from the state where marijuanated muffins are NOT illegal !
I think my backup is wrong bcoz when i entered efs folder i had files in it and another /efs folder which had same files inside
Start at the beginning or simply take the phone to a service centre .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts
Ok i managed it, i flashed 4.2.2 with older modem than my 4.1.2 so i "downgraded" modem. This older one had different efs partition so i had to do was flashing XXEMG4 modem back : ) Thank you for replies
Hello All.
I have a Samsung Galaxy S3 international (GT-I9300 - OS 4.0.4 - I9300DXLE8 baseband) I applied a ROM update (4.2.1) and lost signal. I then flashed again using various ROMS but nothing. I did some research about the EFS folder and using the XXEMG4 modem binary to get the IMEI number back from the generic one but now I cannot connect to any of the mobile carriers that are found. I have to admit, before I discovered the XXEMG4 issue (from a thread here) I did (mistakenly) look in to the EFS folder and I confess I most likely have messed that up and that may be the reason I cannot get a signal any further even though I can get the correct IMEI?
Is there anything I can do which would not involve sending the phone to Samsung? Flashing the stock ROM did not fix it and now, I have found, regardless of what ROM I flash, I must also flash the XXEMG4 modem as well otherwise I just get a generic IMEI number. I blame myself and my own stupidity for not reading more about the EFS system first (and not making a backup either) so I just wanted clarification that there is nothing more I can do.
To summarise:
Updated ROM and lost IMEI (generic)
Did not back up EFS folder
Flashed various ROMS - no service & generic IMEI
Flashed ROM with XXEMG4 modem
Phone IMEI is correct but still no service - emergency calls only
Ariza patch did nothing, factory reset does nothing, stock ROM does nothing.
Many thanks for your time.
Install the patched mg4 modem and all should be fixed
Sent from my iPhone using Tapatalk
Start from beginning flash leaked firmware via odin from sammobile
Then root by cfroot
Install recovery and then flash custom recovery..
Also if u do have a backup of stock with working imei then u cn restore that if u dnt want to do the odin procedure..
Thanks for the replies but I seem to have fixed it.
I restored back to stock ROM, restored EFS Backup using KTools and restarted the phone and all is well.
I am now backing the phone up completely using EFS Pro.
Many thanks.
If you've corrupted files in the efs folder then no, there is nothing you can do yourself. The repair should not be too expensive as no hardware needed replacing.
Edit. You wrote 'didn't backup efs', but now say you've solved it by restoring your backup -which is the whole point of taking a backup before you flash anything.
ianwuk said:
Thanks for the replies but I seem to have fixed it.
I restored back to stock ROM, restored EFS Backup using KTools and restarted the phone and all is well.
I am now backing the phone up completely using EFS Pro.
Many thanks.
Click to expand...
Click to collapse
Where can I download Ktools?
Tidus32x said:
Where can I download Ktools?
Click to expand...
Click to collapse
Via search XDA
Hi guys, my phone (Galaxy S3 i9300 international) was repaired at service centre with z3x box after dirty downgrade from 4.3 t 4.1.2, i lost my IMEI, than when it was fixed, my phone was on 4.1.2, now i cant update my phone to 4.3 because i will get the emergency calls only again, after i tried repairing it and flashing with stock 4.3 rom via Odin but again emergency calls, then it was repaired again and put on 4.1.2 android, but i don't know why can't i upgrade it normaly without getting emergency calls, i tried also backing up .img of my efs partition when it was working, and restoring it on 4.3 but emergency calls was showed again, my imei was not broken, i just got emergency calls, tried flashing the patched MG4 modem but then my imei was null/null and i got it serviced againn. Yyes i have backed up my efs it is working now and i am on 4.1.2
Guys is there any chance for my phone to go on 4.3 after servicing with z3x box, i heard somewhere that i am now stuck on 4.1.2 forever, is that a sad truth?
Update: I can switch on whatever 4.1.2 ROM if it's MG3 or lower (EFS v1), after flashinng i get no network, i run ariza patch and it works, but ariza patch won't work on 4.3 or MG4 newer ROMs.
I also tried zuluman patched kernel and modem, and nope, no results, still no network.
Bump. Help please?
Your issue is the repair made your efs folder incompatible with all newer firmwares, a patched modern AND kernel may enable you to update -from what I've read the two are linked.
Failing that you could wipe the efs folder, flash a blank (someone posted a link the other day) then get a reputable repair to program the imei and serial numbers back on. A lot of repairs seem to fix by downgrading and Ariza, which is no use for efs v2.
There is a thread in general on restoring your imei, but hardware is required.
boomboomer said:
Your issue is the repair made your efs folder incompatible with all newer firmwares, a patched modern AND kernel may enable you to update -from what I've read the two are linked.
Failing that you could wipe the efs folder, flash a blank (someone posted a link the other day) then get a reputable repair to program the imei and serial numbers back on. A lot of repairs seem to fix by downgrading and Ariza, which is no use for efs v2.
There is a thread in general on restoring your imei, but hardware is required.
Click to expand...
Click to collapse
Thanks for the reply, i'll try to mix something up.
Oh, and one more question, does that all mean that i can never be on full stock anymore? I mean having 4.1.2 and normally upgrade to 4.3 with a normal efs update through installation?
With the first option no, you cannot use unpatched firmwares and your efs remains v1.
The second option might work, but depends if a repair can write to v2 efs.
Sent from my GT-I9300 using Tapatalk
Hello xda I am at my wits end over this.
Basically I got sick of stock roms and wanted my phone to be faster so I decided to install cyanogenmod, that was grand. Phone could still send texts and call people. Then I wanted to change to miui, I backed up my efs files with efspro like the step by step guide said and done everything correctly. Once I finished, my efs folder got corrupted because I had the 0049 imei.
Nothing is showing up in efsprofessional for restore. I downloaded a stock 4.3 rom for my phone, it restored my imei code but I didnt have it unlocked. I backed up efs again, flashed to 4.1.1 but I still couldn't restore efs. I downloaded ktool and other programs, it says I restored efs but when I reboot the phone, it doesn't seem to work.
I don't know what to do. I have the backups but it seems like nothing is working. Are older versions of efsprofessional less temperamental? Is there any stock roms that would work better? Any help?
If there is any questions, please ask away. Thank you
suckylemon said:
Hello xda I am at my wits end over this.
Basically I got sick of stock roms and wanted my phone to be faster so I decided to install cyanogenmod, that was grand. Phone could still send texts and call people. Then I wanted to change to miui, I backed up my efs files with efspro like the step by step guide said and done everything correctly. Once I finished, my efs folder got corrupted because I had the 0049 imei.
Nothing is showing up in efsprofessional for restore. I downloaded a stock 4.3 rom for my phone, it restored my imei code but I didnt have it unlocked. I backed up efs again, flashed to 4.1.1 but I still couldn't restore efs. I downloaded ktool and other programs, it says I restored efs but when I reboot the phone, it doesn't seem to work.
I don't know what to do. I have the backups but it seems like nothing is working. Are older versions of efsprofessional less temperamental? Is there any stock roms that would work better? Any help?
If there is any questions, please ask away. Thank you
Click to expand...
Click to collapse
Try this patched modem and kernel
Use PhilZ recovery choose wipe to install a new rom in settings then
1.Flash this ROM v5.2; http://echoerom.com/galaxy-s3-gt-i9300/
2.Flash patched kernel mk6; from here https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list
3.Flash patched modem mk6; from here https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list
4.Reboot.
5 Factory reset if bootloop