hello i have an issue with my IMEI on the samsung galaxy s3 i9300, i restored a rom from another phone with TWRP recovery and the EFS was ticked. and that's when the problem started and after that i flashed 4.3 rom on it but nothing happed, I also tried installing different modems, go back to stock firmware, but when i tried to use QPST or NV reader/writer i was not able to connect the phone in serial mode, only modem would show up. also if i try to put *#7284# i do not get the qualcomm USB settings so i tried doing it with the quickshortcut but when ever i click on the RMNET+ DM + MODEM it automatically goes on MTP. I went trhough older threads. they did not work at all :crying::crying:
Restoring an efs from another phone is illegal as you are attempting to alter the imei, Samsung have obviously prevented this.
If you have the phone's original efs backup, from before you restored the twrp backup, then I'd suggest you use it.
This thread will probably be locked by a moderator.
boomboomer said:
Restoring an efs from another phone is illegal as you are attempting to alter the imei, Samsung have obviously prevented this.
If you have the phone's original efs backup, from before you restored the twrp backup, then I'd suggest you use it.
This thread will probably be locked by a moderator.
Click to expand...
Click to collapse
is there anyway to fix it? i restored it by accident, i backed up the phone with kies, would that help ? i only wanted to restore the data
Pretty sure kies won't backup the efs, but worth a try -there is no other way to fix efs than a service centre.
Sent from my GT-I9300 using Tapatalk
Related
Initial state(stock 4.0.4. ROM):
Device was working properly;
Could call, could use 3G internet;
Everything was good.
After CWM zip installing FoxHound ROM:
Simptoms:
Could not call; for every GSM/3G interogation to telecom operator I get: "Not registered on network";
In my pursuite to fix this, I don't know how, now my device ended in Factory Mode(a yellow box with some debug information appears on my screen and the power button now instantly shutsdown the device and no lock screen available).
The IMEI returned by *#06# is different by the one on the back of the device. It's not a generic one "000...", it almost looks like the original, both seem to be valid after some search, but this is odd. I don't know if it was different before installing FoxHound ... never cared.
What I've tried to do:
I've actually feasted on half of internet for a solution to my problems;
I've tried to flash with Odin tons of stock firmwares, modems, CSCs, including well known ones, my operator ones(Cosmote), my country ones(Romania) -> no luck;
I've tried to restore previous nandroid backups -> no luck;
I've tried to CWM zip install custom ROMs -> no luck;
I've tried everytime to wipe cache, factory reset, delete dalvik, fix permissions, reset battery stats -> no luck;
I've tried all the solutions for the "Factory Mode On" problem, including "echo -n ON > /efs/imei/keystr; chown 1001:1001 /efs/imei/keystr" -> no luck;
I don't have an /efs/ backup before installing FoxHound.
Used GalaxSim, everything was green, no unlock needed.
My device is still in the same condition. No one has an answer. Do you have a solution?
Have you tried flashing with mobile odin?
How did you do a nandroid? With s3 toolkit?
Sometimes when it doesn't work I have to re install the samsung drivers and then try again on full charge.
Something else I noticed with the toolkit was that if I choose a different firmware from the options I done the nandroid with it doesn't work.
Also you may have to flash the insecure image again.
Sorry all could think of.
Sent from my GT-I9300 using xda premium
Samsungnooby said:
1.Have you tried flashing with mobile odin?
2. How did you do a nandroid? With s3 toolkit?
3. Sometimes when it doesn't work I have to re install the samsung drivers and then try again on full charge.
Something else I noticed with the toolkit was that if I choose a different firmware from the options I done the nandroid with it doesn't work.
4. Also you may have to flash the insecure image again.
5. Sorry all could think of.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
1. I haven't tried with mobile odin. This is the first time I've heard about it. I only used desktop odin for flashing.
2. I did a nandroid backup of the stock version of my device, the one which was functional, but without s3 toolkit(also the 1st time I hear about it). My curiosity is why it still wasn't unable to function after I've restored the functional nandroid.
3. I'll try this, thanks.
4. Never heard of insecure image. I'll search for it. Thanks.
5. Thank you very much for your reply. I'll keep you up to date if I'll manage to repair it.
goliathj said:
1. I haven't tried with mobile odin. This is the first time I've heard about it. I only used desktop odin for flashing.
2. I did a nandroid backup of the stock version of my device, the one which was functional, but without s3 toolkit(also the 1st time I hear about it). My curiosity is why it still wasn't unable to function after I've restored the functional nandroid.
3. I'll try this, thanks.
4. Never heard of insecure image. I'll search for it. Thanks.
5. Thank you very much for your reply. I'll keep you up to date if I'll manage to repair it.
Click to expand...
Click to collapse
Get yourself the galaxy s3 toolkit, free from here or you can make a donation.
I like how you numbered my quote
Sent from my GT-I9300 using xda premium
Sad ...
Your EFS data is fu**d and your modem refuses it (and refuses to let you on the network). As far as I know running with an invalid IMEI is illegal in every single country, and in most can land you in actual jail. That being said - search the post about ariza (who had the original modem patch post, but decided to go on a different way) or download this - http://db.tt/PDH8Bc64 !
IMEI broken restore your backed up EFS folder .
jje
Samsungnooby said:
Get yourself the galaxy s3 toolkit, free from here or you can make a donation.
I like how you numbered my quote
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I've download it. Great! Also numbering makes you follow up easier
xclub_101 said:
Your EFS data is fu**d and your modem refuses it (and refuses to let you on the network). As far as I know running with an invalid IMEI is illegal in every single country, and in most can land you in actual jail. That being said - search the post about ariza (who had the original modem patch post, but decided to go on a different way) or download this - !
Click to expand...
Click to collapse
I don't know why my EFS ended ****ed up, and yes, it's illegal. AFAIK, if it's a soft problem, it can be fixed. Isn't the IMEI code embedded into the hardware? Why can't I just wipe everything, from /, and flash a stock ROM? The EFS should be fixed, right?
JJEgan said:
IMEI broken restore your backed up EFS folder .
jje
Click to expand...
Click to collapse
This is important for me, please follow:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
NO
No EFS backup in a nandroid .
Rule one is backup your EFS folder .
If you have a custom rom or kernel that may have auto backed up your EFS to a file efs xxxx.tar .gfz
No EFS then before a service centre try .
http://forum.xda-developers.com/showthread.php?t=1308546
jje
The nandroid ...
goliathj said:
I don't know why my EFS ended ****ed up, and yes, it's illegal. AFAIK, if it's a soft problem, it can be fixed. Isn't the IMEI code embedded into the hardware? Why can't I just wipe everything, from /, and flash a stock ROM? The EFS should be fixed, right?
This is important for me, please follow:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
Click to expand...
Click to collapse
IMEI is no longer so much in "hardware" - it is stored in a protected way in nv_data.bin, which is located in the EFS partition and under normal circumstances is NEVER written by a ROM. Unfortunately the normal nandroid backup does not contain an image of the EFS partition, but some of the better ROMs create a backup (sometimes on the external SD card, sometimes not) - look after something called efsbackup.tar.gz or efsdev-mmcblk0p3.img.gz !
Also the IMEI and serial number from under the battery can (and should) be placed back in a form of edited nv_data.bin - but most likely you will never be able to run that with any of the stock modems and you will still need the patched one that I linked somewhere above.
JJEgan said:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
NO
No EFS backup in a nandroid .
Rule one is backup your EFS folder .
If you have a custom rom or kernel that may have auto backed up your EFS to a file efs xxxx.tar .gfz
No EFS then before a service centre try .
http://forum.xda-developers.com/showthread.php?t=1308546
jje
Click to expand...
Click to collapse
Thank you. Leason learned. Will backup EFS from now on.
xclub_101 said:
IMEI is no longer so much in "hardware" - it is stored in a protected way in nv_data.bin, which is located in the EFS partition and under normal circumstances is NEVER written by a ROM. Unfortunately the normal nandroid backup does not contain an image of the EFS partition, but some of the better ROMs create a backup (sometimes on the external SD card, sometimes not) - look after something called efsbackup.tar.gz or efsdev-mmcblk0p3.img.gz !
Also the IMEI and serial number from under the battery can (and should) be placed back in a form of edited nv_data.bin - but most likely you will never be able to run that with any of the stock modems and you will still need the patched one that I linked somewhere above.
Click to expand...
Click to collapse
Thanks for the info. Good to know.
Finally, my device works. I've contacted a private service.
The Factory Mode problem, which was always on, was fixed by flashing a stock 4.0.4 ROM.
The "Not registered on network" problem had various reasons:
My IMEI had been changed so my modem wasn't accepting any calls. He had rewritten the original IMEI(the one from the back) with "the box".
For unknown reasons for me, 4.1.0+ has some built-in protections and will brick my device everytime I flash it. So, for the moment I'm sticking with 4.0.4.
Some people experienced this problem after updating, so it has something to do with the built-in protections(but the question is "protection against what?"). There's something smelly about our IMEI, we, the ones having this issue. I've bought this device over ebay.co.uk and it arrived unsealed(the merchant told this because he had to check the phone) but with root installed and had 1 count of custom binary flashed, in the download mode screen. This is odd. From now on, I'll ask for IMEI.
I thank everyone for helping me. Best regards!
Stuck on EDGE and in Factory Mode
I have literally over 16hrs trying to get my I747 back working correctly. It all stared when I tried the "Hellfire" rom. I have had my phone rooted running custom roms for over 6 months with no problems. After flashing the "Hellfire" rom I noticed that I was stuck on "EDGE" network, unable to make or receive phone calls or text. After further inspection, I noticed I had "0" for an IMEI#. So I injected my IMEI back on the phone... Still the same problem. I reverted back to stock ROM, Kernel, and Modem... Same problem stuck on "EDGE" network. Several hours later of no stop research, I noticed that my "ERI version Not available". After alot more research I noticed that my "efs" folder was missing the ".nv_data" file. So I backed up the "efs" folder, saved it to my extSD, and then deleted the "efs" folder for the root of the phone. Now I'm in "Factory Mode" even after replacing my backed up "efs" folder with the new one that was created at the root of my Internal sd.
I need help... If anyone has any ideas...:crying:
You might try what they talk about in this thread, don't know if it applies to your situation or not...
I can't post off site URL's, so google "Not registered on network" + stuck in Factory Mode ON - no solution works
It's the thread on androidpit dot com
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
Please, I need help, my motherboard burned and bought a new one with no IMEI, after the technician installed the motherboard, it got generic IMEI "0049 ..." Before the burn motherboard, I had made a backup of the ROM "4.0.4" using CWM, and made a copy of the folder EFS "efs.img/efs.tar.gz" using KTOOL, not sure about KTOOL because was this in 2012^^, but I've tried everything I know, I have tried to restore using the KTOOL, already restored the backup using CWM, already flash ROM "4.1.2/4.3" via ODIN, I have done several reported here in some posts related about IMEI but it still fails, hope some enlightened can help me :/ sorry for my bad english
Model: GT-I9300
Actual ROM: 4.0.4
isisnx said:
Please, I need help, my motherboard burned and bought a new one with no IMEI, after the technician installed the motherboard, it got generic IMEI "0049 ..." Before the burn motherboard, I had made a backup of the ROM "4.0.4" using CWM, and made a copy of the folder EFS "efs.img/efs.tar.gz" using KTOOL, not sure about KTOOL because was this in 2012^^, but I've tried everything I know, I have tried to restore using the KTOOL, already restored the backup using CWM, already flash ROM "4.1.2/4.3" via ODIN, I have done several reported here in some posts related about IMEI but it still fails, hope some enlightened can help me :/ sorry for my bad english
Model: GT-I9300
Actual ROM: 4.0.4
Click to expand...
Click to collapse
error of the technician, the imei is stored in the nand chip(comes with the mobo)and he should had flashed correctly it for you
now since you made a ktool backup(dont know what it is, but looks like a imei backup) and if this ktool is designed for the s3(so it backups all efs partitions, if i remember there are 3, can be wrong tho) you*should* could restore.
but there is a problem,if ktool is correct but its from 2012 that means it did a backup of the old style efs partiton (efsv1) witch dosent work anymore since Samsung upgraded it to efsv2 and downgrading will not help
what you should do is get a s3 with 4.1.2 or earlier and restore your efs to that, upgrade it to 4.3, and get a new efs backup
i could be wrong tho
Edit: i remember a thread about a guy fixing the imei issue without a backup, and i remember Reading a part where he formats the efs partition, so that should help, see if you can find it(i can´t look now). it was in the s3 forums
You cannot restore an efs backup to another handset or motherboard, it's also illegal to change the imei and discussion of this is banned on xda.
Your new motherboard is faulty, return it to the technician.
boomboomer said:
You cannot restore an efs backup to another handset or motherboard, it's also illegal to change the imei and discussion of this is banned on xda.
Your new motherboard is faulty, return it to the technician.
Click to expand...
Click to collapse
really? excuse me is that I see many people talking about it here and have never seen any warning from the moderators, I thought it was legal because everyone says that the IMEI does not change, even changing the motherboard. And I have the invoice from the phone, just did not want to take the support of samsung because they charge too much.
Backing up and restoring efs to same motherboard/handset is legal, trying to move the imei from your old motherboard to new is illegal for you to do.
Hi,
First, I work in a phone repair shop, I'm not trying anything illegal!
I have a Z3x Box at the work, and a S3 i9300 myself.
A friend with another S3 at 600 miles, and has lost his EFS. I already told him to make a backup, but unfortunately he had it on the internal SD. After a bad ROM flash he had to use a PIT file for flashing a stock rom, and that he wiped everything.
His EFS folder was blank, no nv_data or anything.
With the z3x, I tried putting his imei and S/N on my EFS, then doing a backup and sending that copy to him (obviously I restored my phone after that) but it didn't work.
So, I'd like to know if there's any way to repair or regenerate the EFS with a working phone as base, without having to send the phone
dabyd64 said:
Hi,
First, I work in a phone repair shop, I'm not trying anything illegal!
I have a Z3x Box at the work, and a S3 i9300 myself.
A friend with another S3 at 600 miles, and has lost his EFS. I already told him to make a backup, but unfortunately he had it on the internal SD. After a bad ROM flash he had to use a PIT file for flashing a stock rom, and that he wiped everything.
His EFS folder was blank, no nv_data or anything.
With the z3x, I tried putting his imei and S/N on my EFS, then doing a backup and sending that copy to him (obviously I restored my phone after that) but it didn't work.
So, I'd like to know if there's any way to repair or regenerate the EFS with a working phone as base, without having to send the phone
Click to expand...
Click to collapse
Unfortunately i think it's not possible, i think z3x must have the phone connected, i needed to repair my efs via z3x and it could be only done via cable, and also, say your friend he is stuck with patched modem / kernel for the rest of his life, or else he will have Emergency cals only and baseband unknown. Must love z3x as much as you must hate it