I had CM13 and today, I upgraded to CM14.1 (I totally forgot to backup my EFS partition and restore it, and I lost the old EFS backup)
Ever since that, my SIM cards aren't working. Turns out that my IMEI numbers are displaying as 0 only.
I tried certain ways to get it back, but I couldn't.
I'm considering to revert back to MIUI 8, but I don't think that it would work.
Can anyone please suggest me some other way to solve this?
You can try this guide. Good Luck.
Flash miui rom, but first check if your phone is kate or kenzo. Your efs may be fine. Don't restore the efs of a different phone version.
ayush3051 said:
You can try this guide. Good Luck.
Click to expand...
Click to collapse
Thank you VERY MUCH!
It worked like magic!! I scared ****less.
Sam.1211 said:
Flash miui rom, but first check if your phone is kate or kenzo. Your efs may be fine. Don't restore the efs of a different phone version.
Click to expand...
Click to collapse
I did that, it did not work.
The method above worked flawlessly.
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
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
Dear,
I installed 4.4 RC1 PA, per the instructions, however I'm stuck in bootloop. Then I tried to go back to an earlier version, of course with a suitable kernel, but still the same. Then I installed the stock rom 4.1.2, and again repeated bootloop. Finally install the stock ICS, the system is booted, but I do not have a GSM network. Once again I try to install custom, happens to bootloop. Works only stock ICS but without GSM network. Do something was wrong?
Thanks in advance!
I guess your EFS partition got all messed up while flashing.No baseband,no serial,no imei,no signal and so on.Have you made any backup of it?
This EFS thing is tricky.Search around here to get an idea about this.
TheImpossibleEnemy said:
I guess your EFS partition got all messed up while flashing.No baseband,no serial,no imei,no signal and so on.Have you made any backup of it?
This EFS thing is tricky.Search around here to get an idea about this.
Click to expand...
Click to collapse
What you think, is this possible way to fix? I'll try this. http://www.digitalreborn.com/fix-samsung-galaxy-unable-mount-efs/
So I assume you have a backup.There are plenty of tools for restoring it,like the EFS Professional or kTool.If your backup is in either img or tar format,easy way could be restoring it via philz kernel's advanced recovery(if you are using stock jb or ics).
i have the unknown baseband and null imei. is there any fix for this?
i have flashed stock 4.0.4 and nothing
flashed 4.4.4 and worked for a day then all signal bars turned to the circle with bar across
flashed all possible radios when i was on stock 4.0.4 and nothing
flashed back to 2.3.6 and nothing.
replaced sim reader and bottom antenna and still nothing
tried to repair imei with android terminal and said i didnt have permission
tried with mtk tool but no option for my model
tried like 3 softwares to replace imei, with my own, but no luck.
is there any other way i can flash the imei to my phone? thanks
I believe discussion of imei changing, or modifying is prohibited on xda. You might want to double check that.
even if im trying to put phones imei back in since its been null?
440bro said:
I believe discussion of imei changing, or modifying is prohibited on xda. You might want to double check that.
Click to expand...
Click to collapse
they're trying to repair imei\baseband in order to get data working again so its cool, i think you're thinking of swapping esn\imei perhaps... now thats a different story around here.
Edit: @ op do you have a backup of your EFS laying around?
no i cant seem to find it, i know i had a backup on my pc but no where to be found. i have another note and tried to back that one up and put in my bad note but there was no nv_data.bin
do note efs backups have this file?
ufuknut said:
no i cant seem to find it, i know i had a backup on my pc but no where to be found. i have another note and tried to back that one up and put in my bad note but there was no nv_data.bin
do note efs backups have this file?
Click to expand...
Click to collapse
oops sorry about that, I automatically assumed it did have NV_data.bin. I'm so use to my galaxy I thought the note would have it also since its a Sammy. perhaps a member with more knowledge regarding this device will chime in and assist you with this problem but it might be one of the files in the root of "efs" folder...
sent from my Liquid Smooth SGH-I717
both my notes dont have this file and one is working without issue, just the one i sue for custom roms is messed up.
ufuknut said:
both my notes dont have this file and one is working without issue, just the one i sue for custom roms is messed up.
Click to expand...
Click to collapse
Have you restored the phone via keys? or maybe try the apps that back up EFS from the good phone and then restore to the bad phone. I have no idea about this area.
Also have you read here
tried both with no luck. i backed up the efs with hc-k tools and restored with same program on back phone and still no bars. :crying:
yes i tried the link above and the guy said he lost the link to the rom he used to restore his.
hi i was wondering if you guys can help me, i have an efs backup,but i cant seem to be able to restore my imei,i tried Ktool,efs professional,nothing seems to work,i should mention that the efs backup was from a Samsung 4.1.2 stock now my phone is on CM11
thanks
I dont know if cm base and sam base modems are same but if they are:
Firs option: many custom roms come without modems to prevent the country issues so assume that your old modem is still installed you can try to install a new cm modem or like i said if they are same a new version sammy modem.
Second option: go back to stock 4.1.2 and see if your imei is still intact. If not restore your 4.1.2 imei see if it is back. If It is back first try to upgrade official 4.3 via odin then install cm 11 with wipe...
thewalekk said:
I dont know if cm base and sam base modems are same but if they are:
Firs option: many custom roms come without modems to prevent the country issues so assume that your old modem is still installed you can try to install a new cm modem or like i said if they are same a new version sammy modem.
Second option: go back to stock 4.1.2 and see if your imei is still intact. If not restore your 4.1.2 imei see if it is back. If It is back first try to upgrade official 4.3 via odin then install cm 11 with wipe...
Click to expand...
Click to collapse
thanks for replying, I flashed a patched modem and kernal from a different post, but I got boot loop,so I restored a backup that I made before flashing from recovery,and for some reason every thing is OK now maybe restoring is the silotion.
BTW the backup was made after I restored my efs.hop that helps someone.
In a way you helped me, thank you.
roguesa said:
thanks for replying, I flashed a patched modem and kernal from a different post, but I got boot loop,so I restored a backup that I made before flashing from recovery,and for some reason every thing is OK now maybe restoring is the silotion.
BTY the backup was made after I restored my efs.hop that helps someone.
In a way you helped me, thank you.
Click to expand...
Click to collapse
You got bootloop because that modem and kernel are for sammy 4.3 and yours is CM. The backup you restored, is it nandroid backup and is it 4.1.2 ?
thewalekk said:
You got bootloop because that modem and kernel are for sammy 4.3 and yours is CM. The backup you restored, is it nandroid backup and is it 4.1.2 ?
Click to expand...
Click to collapse
no, the backup i restored was from CM 11,thats what surprised me i made the backup in philz touch right before i flashed the patched modem and the kernel to try and solve the imei issue, it was a normal backup (the one where you back every thing),meaning the imei problem was still there,but it was after i tried to restore my original EFS.
so here is what i did in steps
-got corrupted imei on CM 11
-tried to restore with my EFS backup that i made while i was on sammy 4.1.2 using different apps and methods didn't work
-made a full backup using philz before flashing a new modem as suggested
-got boot loop after flashing a new modem
-restored the backup i made before flashing the modem and for some reason my imei was back
roguesa said:
no, the backup i restored was from CM 11,thats what surprised me i made the backup in philz touch right before i flashed the patched modem and the kernel to try and solve the imei issue, it was a normal backup (the one where you back every thing),meaning the imei problem was still there,but it was after i tried to restore my original EFS.
so here is what i did in steps
-got corrupted imei on CM 11
-tried to restore with my EFS backup that i made while i was on sammy 4.1.2 using different apps and methods didn't work
-made a full backup using philz before flashing a new modem as suggested
-got boot loop after flashing a new modem
-restored the backup i made before flashing the modem and for some reason my imei was back
Click to expand...
Click to collapse
I think the reason you got your imei back is the modem you installed with the kernel. So here is what i think happened. You had bootloop so restore got your old kernel back and modem stayed intact. Shortly if you had just installed a new modem from the begenning you would have sold your problem i always say best way to learn is try and fail. i am happy that you have your phone back [emoji106]
I also suggest you to replace the modem with an unpatched clean one. You can have network problem in the future...