Hey everyone! I had flashed Lineage 14.1 on my Samsung J210F(https://forum.xda-developers.com/an...ageos-14-1-t3680656/post74433279#post74433279)
And everything was working perfectly until I wanted a file from the stock ROM. I flashed the stock ROM and after my work was done, I flashed Lineage again. Now in the middle of this flashing I lost my network. I tried changing the APN settings and even tried putting it on GSM Only but it's of no use. The network comes and goes abruptly. I even tried going back to the stock ROM but now it's the same over there too. My radio band and everything is as it is. I just can't figure out what's wrong. I have tried reflashing multiple times. There is no problem with the physical hardware or the sim as I have tried it with a different phone too. I haven't touched my efs file either.
Any suggestions would be appreciated!
Somebody please help. I just cant find any solution to this. I've been through each and every forum possible but I still cant find anything. IMEI and everything is normal. I did try to flash the stock rom and the stock rom receives network but as soon as I switch to custom rom, the network goes away. Please help
Bump
DoHave a look at your IMEI status with *#0011#
If it's NG you may have inadvertently corrupted your EFS partition. I dealt with that myself recently. If that's the case, if you've got a backup of the EFS, try to restore it. If not, backup your EFS to your PC or another secure external location, in case of worse emergency later. Then empty your EFS folder except for the FactoryApp and prov_data folders and their contents, then flash a clean firmware with Odin.
This can backfire. Read-up and Backup before proceeding.
I have no further expertise to offer. I just blundered out of messing up my EFS during flashing.
Crike said:
Have a look at your IMEI status with *#0011#
If it's NG you may have inadvertently corrupted your EFS partition. I dealt with that myself recently. If that's the case, if you've got a backup of the EFS, try to restore it. If not, backup your EFS to your PC or another secure external location, in case of worse emergency later. Then empty your EFS folder except for the FactoryApp and prov_data folders and their contents, and reboot.
This can backfire. Read-up and Backup before proceeding.
I have no further expertise to offer. I just blundered out of messing up my EFS during flashing.
Click to expand...
Click to collapse
Yes I have backed it up before but this case isn't about that. I have the proper IMEI number. I'm just not getting signal and it's becoming really frustrating now.
I even tried going back to the stock ROM but I'm not getting any signal there either. Please see the picture attached
darshan1504 said:
Yes I have backed it up before but this case isn't about that. I have the proper IMEI number.
Click to expand...
Click to collapse
I seemed to have the proper IMEI, too, but it's status was NG anyway. Check *#0011# if you haven't yet, to verify.
Crike said:
I seemed to have the proper IMEI, too, but it's status was NG anyway. Check *#0011# if you haven't yet, to verify.
Click to expand...
Click to collapse
*#0011# doesn't work for me but *#06# does and this is what it shows
If you can figure out how to get into servicemode on your device (which is what *#0011# does on my device) then you can check the IMEI status, or if you're confident you can restore the EFS partition try the method I described above.
Beyond that, I'm a virtual noob. My only counsel is to be patient and cautious. Someone with actual expertise may advise you yet in the sub-forum for your device or a thread discussing a similar problem.
Crike said:
If you can figure out how to get into servicemode on your device (which is what *#0011# does on my device) then you can check the IMEI status, or if you're confident you can restore the EFS partition try the method I described above.
Beyond that, I'm a virtual noob. My only counsel is to be patient and cautious. Someone with actual expertise may advise you yet in the sub-forum for your device or a thread discussing a similar problem.
Click to expand...
Click to collapse
The code for me for service mode is *#*#197328640#*#* but I can never get to open it. It just looks blank
There may be other ways to verify the IMEI Status, but that is beyond what I know. Someone more expert may have advice.
Crike said:
If you can figure out how to get into servicemode on your device (which is what *#0011# does on my device) then you can check the IMEI status, or if you're confident you can restore the EFS partition try the method I described above.
Beyond that, I'm a virtual noob. My only counsel is to be patient and cautious. Someone with actual expertise may advise you yet in the sub-forum for your device or a thread discussing a similar problem.
Click to expand...
Click to collapse
Also, I can find FactoryApp but I can't find prov_data folder. This is what my folder looks like. Can you send a picture of yours
If your backup is of your recent, working setup, it might be interesting to compare it to your current EFS. I have no suggestions as to how to inspect the contents of a backup.
Crike said:
There may be other ways to verify the IMEI Status, but that is beyond what I know. Someone more expert may have advice.
Click to expand...
Click to collapse
I'm quite sure there's nothing wrong with the IMEI number. I have confirmed it multiple times. I just feel so helpless. I don't even get to know if someone's calling me. I just hope I can fix this ASAP
Crike said:
If your backup is of your recent, working setup, it might be interesting to compare it to your current EFS. I have no suggestions as to how to inspect the contents of a backup.
Click to expand...
Click to collapse
This is not a backup. This is the actual EFS folder. Anyways thanks for the help. I'll keep bumping till someone else sees it
Also I would like to add that the network sometimes bounces on and off after a reboot so..
My IMEI seemed correct as well. The problem was with something in the EFS partition which resulted in IMEI status NG, and I only discovered this was the issue after seeing the actual IMEI status assessment by the servicemode. I repeat: the IMEI numbers shown by *#06# didn't indicate anything was wrong.
Should you proceed along the path I suggested, make sure to flash a fresh firmware from Odin directly after. It seems to be required to restore the EFS after the procedure mentioned before.
Google "FactoryApp" and "prov_data" before proceeding.
Beyond that, good luck.
Crike said:
My IMEI seemed correct as well. The problem was with something in the EFS partition which resulted in IMEI status NG, and I only discovered this was the issue after seeing the actual IMEI status assessment by the servicemode. I repeat: the IMEI numbers shown by *#06# didn't indicate anything was wrong.
Should you proceed along the path I suggested, make sure to flash a fresh firmware from Odin directly after. It seems to be required to restore the EFS after the procedure mentioned before.
Google "FactoryApp" and "prov_data" before proceeding.
Beyond that, good luck.
Click to expand...
Click to collapse
Btw I did try that code when I had flashed back the stock ROM and it showed IMEI Certificate PASS. I'm sure there's nothing really wrong here because as I said the network sometimes bumps on and off after reboot
I have a question what is the baseband number on the phone? My ROM hasn't been updated for sometime now and I have got official updates for the stock ROM. Does the new update for the stock ROM come with new baseband? Will flashing the update for the stock ROM update the baseband too? Or is that in the kernel? I've read that updating the baseband usually fixes network problems. Please help me fix mine
I just extracted the new update for the stock ROM but I couldn't find any modem.bin file in there. There's just usual system, recovery,etc. If I don't have the modem.bin file how can I flash the radio/baseband? Should I just flash the firmware via Odin through AP or CP option?
Bump
Related
We need to compile a list of ROMs that will alter/not alter the IMEI of our beloved phone. I've updated to so many different types of ROMs which I lost track. Fortunately, I am able to procure a new Captivate under warranty. Now that I've started flashing from stock. First one I flashed was Phoenix 4.5 and so far so good, OEM IMEI unaltered. Anyone care to share should respond positively! Peace out.
Moved to general as not android development
I have flashed
Phoenix
Fire fly
Perception
Cognition
Serendipity
Continuum
Andromeda
Ultimate
Docs
Precision
Paragon
Stripped
And have never had an issue with my imei. Maybe I am lucky
I haven't done as many as you, but I'm in the same boat.
A better list would be one of ROMs that do change your IMEI.
And development have probably stopped doing roger thing that causes IMEIs to change.
Just back up the efs folder and don't worry about it.
Edit: spelling
Sent from my custom ROM'd Captivate
I have flashed pretty much every Rom in the captivate forums, most in the i9000 forum, and quite a few from the vibrant forum with no effect on my imei.
Sent from my ADR6300 using XDA App
The only rom I'm aware of that will have any effect on your IMEI is the gingerbread tech preview rom, which is mostly unusable anyway. Also, if I'm not mistaken, the current CM7 i9000 builds will alter your /efs partition.
The vast majority of the roms you'll come across on xda will not modify your IMEI, as they do not wipe or modify the /efs partition. If you're paranoid about it, just back it up onto your sd card. If you flash a rom and your IMEI changes, just copy the directory contents over the current ones and reboot the phone, and you're sorted.
How about once you flash stock before a rom flash, check to see if you have the right imei. If it does then back up your efs folder and after rom flash replace it.
When i first got my captivate (July) and after JH7 I flashed some ROMs - both i9000 and later the Froyo Beta - somewhere I lost my unlock - I never lost my IMEI, but I suspect it is related to the nv_data.bin being corrupted or changed (product code not matching IMEI maybe). I think the phone reports the wrong IMEI if the product code changes and the IMEI is encrypted - I think flashing from JH7 to i9000 causes the problem.
"bames" has done a lot of testing with this and has a thread in the dev section.
I think the important takeaway is: DON'T assume you IMEI or product code can't be changed - many of us have seen it happen. Backup your EFS folder and files.
Did AT&T disable the charge to account option in android market recently? I flashed from 2.1stock to 2.2.1 paragon5.1 and lost the option to charge apps to my at&t account. Is this imei related?
shen long said:
Did AT&T disable the charge to account option in android market recently? I flashed from 2.1stock to 2.2.1 paragon5.1 and lost the option to charge apps to my at&t account. Is this imei related?
Click to expand...
Click to collapse
i dont think its imei related. one of my captivates is a bone stock JH7, never been rom'd or rooted....and i cant charge to account on most apps i have tried...i gave up
zelendel said:
How about once you flash stock before a rom flash, check to see if you have the right imei. If it does then back up your efs folder and after rom flash replace it.
Click to expand...
Click to collapse
This proved to be challenge to me at some points. Before I got my replacement Captivate, I am sure I have the original EFS file folder backed up. After a flash to one of the many roms which I forgot, I noticed my IMEI has changed to the "test-bed" IMEI which quite a few people have the same IMEI too. I tried to copy the original backed up "EFS" over the faulty ones. Rebooted and the "test" IMEI keep showing up. I tried methods such as CHMOD the folder, rooting, busybox, IMEI recovery guide as posted here in the Android Development section, etc. The annoying "beta" or "test" IMEI still stuck.
That being said, I am a bit scared to flash new ROMs again until there is a surefire way to overwrite unwanted EFS folder with my original backed up EFS folder in the future.
Windycity35 said:
This proved to be challenge to me at some points. Before I got my replacement Captivate, I am sure I have the original EFS file folder backed up. After a flash to one of the many roms which I forgot, I noticed my IMEI has changed to the "test-bed" IMEI which quite a few people have the same IMEI too. I tried to copy the original backed up "EFS" over the faulty ones. Rebooted and the "test" IMEI keep showing up. I tried methods such as CHMOD the folder, rooting, busybox, IMEI recovery guide as posted here in the Android Development section, etc. The annoying "beta" or "test" IMEI still stuck.
That being said, I am a bit scared to flash new ROMs again until there is a surefire way to overwrite unwanted EFS folder with my original backed up EFS folder in the future.
Click to expand...
Click to collapse
Yeah IT gave me a ruff time at one point to. What I had to do to recover my IMEI was to flash stock (still had the test imei) while on stock I had to root and use root explorer to replace just the files that were in the efs folder. Imei folder, IMEI file and nv.bin, and then reboot. Got my right IMEI back and it hasnt changed sense then
Can one of you guys post the test IMEI? Is it just all 0's or something or does it actually look like a legit IMEI?
modest_mandroid said:
Can one of you guys post the test IMEI? Is it just all 0's or something or does it actually look like a legit IMEI?
Click to expand...
Click to collapse
Starts with 004 or something like that. Nothing close to a real imei other than in number of characters.
my friend gave me a phone. when i check it it has no IMEI, no Baseband
so i search in this forum and tried many tricks to recover IMEI but no luck.
i heard that if i can flash a dummy IMEI to this phone i can repair it with z3x box or octopus Box
the problem is i don't know how to flash this to dummy IMEI and also i don't have flash file for it.
I beg everyone to help me. or can give me link where to download those flash files.
or how can i put dummy IMEI to this phone.
i heard nandroid can fix this but i dont have those nandroid.
im new in this forum and sorry for my bad english. help me guys.
e1lahif
up
still no solution
i need help from the experts
you have to take the phone to the samsung service center and get it repaired because your efs folder is missing which has the imei number
With a phone root and busybox
Galaxy unlocker > https://play.google.com/store/apps/details?id=com.helroz.galaxysunlock&hl=fr
Trying to see if you can recover EFS
i tried those you've mention but no luck, i wanna try to restore a nandroid backup but i don't know where can i get or is there will be someone to lend me his nandroid back. sorry for my bad english
arjun08 said:
i tried those you've mention but no luck, i wanna try to restore a nandroid backup but i don't know where can i get or is there will be someone to lend me his nandroid back. sorry for my bad english
Click to expand...
Click to collapse
there is NO IMEI because your efs folder is corrupted or missing/doesnt exist/got deleted,etc..so here are the things you need to follow
* Root your phone first using this link.
http://forum.xda-developers.com/showthread.php?t=1894737
*Flash a custom recovery (ClockworkMod Recovery/CWM)
so now you have a custom recovery so now you can take a backup and you should take a backup(for precautionary measures).
*Install the app "Galaxy_S Unlock" from playstore as LoLaTion said and if you cant download it from playstore then download the apk(installation)file which you will get easily on web.
Also install BusyBox which is available on both playstore and web.
*Now by using the application "Galaxy_S Unlock" try to recover your IMEI.
and if still there is no luck on your phone then you can just go to Samsung Service Centre and hopefully they will solve this problem for you.:angel:
Phone=rooted
flash cwm for backup
installed busy box
tried to repair using galaxy s unlock
but no luck, service centre said they can change board but it cost 70-80% of the brandnew
i can still see my efs folder
.nv_core.bak
.nv_core.bak.md5
.nv_data.bak
.nv_data.bak.md5
was dated 10/12/2012
and my friend said this phone was damage in november
i think there is still a way to fix this rather than go to service centre cause i still don't have budget to buy new board
arjun08 said:
Phone=rooted
flash cwm for backup
installed busy box
tried to repair using galaxy s unlock
but no luck, service centre said they can change board but it cost 70-80% of the brandnew
i can still see my efs folder
.nv_core.bak
.nv_core.bak.md5
.nv_data.bak
.nv_data.bak.md5
was dated 10/12/2012
and my friend said this phone was damage in november
i think there is still a way to fix this rather than go to service centre cause i still don't have budget to buy new board
Click to expand...
Click to collapse
do you get any error message like
Warning! A problem was detected with your device. Your device IMEI number is invalid. And invalid IMEI number could cause network issues including the inability to call emergency numbers.
then this link might help you http://android.stackexchange.com/questions/28963/how-to-restore-my-imei
however,while browsing our forums I came across this http://forum.xda-developers.com/showthread.php?t=1308546
but you cannot use it because its not for our phone... wish we could had something like that.. and just asking out of curosity does your phone have a IMEI number under the battery?
mustafahussain said:
do you get any error message like
Warning! A problem was detected with your device. Your device IMEI number is invalid. And invalid IMEI number could cause network issues including the inability to call emergency numbers.
then this link might help you http://android.stackexchange.com/questions/28963/how-to-restore-my-imei
however,while browsing our forums I came across this http://forum.xda-developers.com/showthread.php?t=1308546
but you cannot use it because its not for our phone... wish we could had something like that.. and just asking out of curosity does your phone have a IMEI number under the battery?
Click to expand...
Click to collapse
the phone has no error like that. just a blank IMEI and baseband unknown
yes the phone has its IMEI under the battery, i hope i can write it back to phone.
i tried already that efs pro but didnt work.
arjun08 said:
the phone has no error like that. just a blank IMEI and baseband unknown
yes the phone has its IMEI under the battery, i hope i can write it back to phone.
i tried already that efs pro but didnt work.
Click to expand...
Click to collapse
you said you can see your efs folder... try this http://android.stackexchange.com/questions/28963/how-to-restore-my-imei
since you can see your efs maybe somehow on CM9 or CM10 there is a possibility that your IMEI can be restored.. give it a try
GoodLuck
Hi,
After installing a custom ROM, the IMEI reported by Android is different from the one on the sticker under the battery.
I believe the IMEI is somewhere in the 'efs' folder, but where exactly? There are all sorts of files and folders in that folder.
There is even a folder called 'imei', but it contains just one file called 'mps-code.dat', and that is only three bytes long, which isn't enough to contain the 15-digit IMEI.
Can anyone help?
Thanks,
Steve
(Phone is Samsung Galaxy Note 2 GT-N7100)
Steve Thackery said:
Hi,
After installing a custom ROM, the IMEI reported by Android is different from the one on the sticker under the battery.
I believe the IMEI is somewhere in the 'efs' folder, but where exactly? There are all sorts of files and folders in that folder.
There is even a folder called 'imei', but it contains just one file called 'mps-code.dat', and that is only three bytes long, which isn't enough to contain the 15-digit IMEI.
Can anyone help?
Thanks,
Steve
(Phone is Samsung Galaxy Note 2 GT-N7100)
Click to expand...
Click to collapse
It's inside the efs folder in the root of your phone.
Backing it up eh?
eatsleep said:
It's inside the efs folder in the root of your phone.
Backing it up eh?
Click to expand...
Click to collapse
No, my phone stopped working and I think it's because the IMEI has got corrupted when I was messing with various custom ROMs - it no longer matches the sticker. I want to figure out a way to fix it - I can't bear the thought that I've just bricked a fine phone that I paid good money for.
Where in the efs folder? There are loads of files and folders in there.
Thanks,
Steve
Wait wait,
You can't text or connect to the network?
Try flashing a official firmware and see if the IMEI matches...
It's not that simple to modify your IMEI n.o, special softwares are required to do this.... It's stored in .nv_data
Don't you have any efs backups?
IMEI getting corrupt is seen many times in s3 and note 2 devices....
And also, modifying your iMEi is illegal, but people out there use a software to do it.... May not be good to discuss this software here...
And one more thing, does your phone shows a generic IMEI number when you dial *#06* ?
eatsleep said:
Wait wait,
You can't text or connect to the network?
Click to expand...
Click to collapse
Thanks for replying, eatsleep. That's right - the whole phone works fine. It will see all the mobile networks in my area, and will register itself on mine (O2-UK). The only thing that doesn't work is voice telephony, SMS, and mobile data.
eatsleep said:
Try flashing a official firmware and see if the IMEI matches...
Click to expand...
Click to collapse
Yeah, I've done that. No good, I'm afraid.
eatsleep said:
It's not that simple to modify your IMEI n.o, special softwares are required to do this.... It's stored in .nv_data
Don't you have any efs backups?
Click to expand...
Click to collapse
Here I must admit to being a bloody fool. I didn't know what I was doing and messed about stupidly in CWM, mounting and unmounting, deleting, reformatting, and so on. Basically I was trying to follow several guides at the same time, and made a total mess of it.
And no, I didn't know about backing up the efs before I started.
eatsleep said:
IMEI getting corrupt is seen many times in s3 and note 2 devices....
And also, modifying your iMEi is illegal, but people out there use a software to do it.... May not be good to discuss this software here...
And one more thing, does your phone shows a generic IMEI number when you dial *#06* ?
Click to expand...
Click to collapse
Not a generic one. It's really weird, because it's almost but not quite the same:
Sticker inside phone:
xxxxxx05861xxx3
*#06#:
xxxxxx05681xxx1
The ...86... has reversed to ...68... and the final 3 has become 1.
I'm an idiot and furious with myself.
Thanks again for any help you can give, though.
Steve
Wow! I've just seen how much it costs to buy that eight-tentacled device who's name shall not be mentioned.
$135 makes poor sense if it's only going to be used once. Perhaps the best idea is to check my local phone repairers until I find one who has the device?
Steve
Bumpety bump just this once:
Any chance of correcting the IMEI myself?
Thanks,
Steve
Steve Thackery said:
Thanks for replying, eatsleep. That's right - the whole phone works fine. It will see all the mobile networks in my area, and will register itself on mine (O2-UK). The only thing that doesn't work is voice telephony, SMS, and mobile data.
Yeah, I've done that. No good, I'm afraid.
Here I must admit to being a bloody fool. I didn't know what I was doing and messed about stupidly in CWM, mounting and unmounting, deleting, reformatting, and so on. Basically I was trying to follow several guides at the same time, and made a total mess of it.
And no, I didn't know about backing up the efs before I started.
Not a generic one. It's really weird, because it's almost but not quite the same:
Sticker inside phone:
The ...86... has reversed to ...68... and the final 3 has become 1.
I'm an idiot and furious with myself.
Thanks again for any help you can give, though.
Steve
Click to expand...
Click to collapse
Hey babe..... please remove both of your IMEIs from here and never post them again in public. I'll post back in some time.... and your IMEI looks quite fine to me but still, lemme look for some time
And, your phone is not bricked, you've just got a bad IMEI
eatsleep said:
Hey babe..... please remove both of your IMEIs from here and never post them again in public. I'll post back in some time.... and your IMEI looks quite fine to me but still, lemme look for some time
And, your phone is not bricked, you've just got a bad IMEI
Click to expand...
Click to collapse
Thank you for replying! I've edited my post to remove the IMEI, as requested. Perhaps you could alter the one where you quote my message?
I realise everyone must say this, but I'm genuinely not trying to do anything questionable or immoral. I just want to restore the IMEI so it's the same as the one on the sticker.
Thanks,
Steve
Steve Thackery said:
Thank you for replying! I've edited my post to remove the IMEI, as requested. Perhaps you could alter the one where you quote my message?
I realise everyone must say this, but I'm genuinely not trying to do anything questionable or immoral. I just want to restore the IMEI so it's the same as the one on the sticker.
Thanks,
Steve
Click to expand...
Click to collapse
Can't find some content for your device but please do one last precaution before following any more tutorials, backup your efs folder and place it in a safe place.......
If you don't find anything, I can provide you with some guides for s3 (my device ) but don't know if they'll work for you....
One advice, reset your phone and send it to any service center.... They may charge you if you are out of warranty.....
here is a random thread i found but I have a bad feeling about the person.... Carry on at your own risk but back up your current efs, it may be recoverable but can move to a unrecoverable state after some repair attempts so, we can have hope....
link:
http://forum.xda-developers.com/showthread.php?t=2141928&page=1
eatsleep said:
Can't find some content for your device but please do one last precaution before following any more tutorials, backup your efs folder and place it in a safe place.......
If you don't find anything, I can provide you with some guides for s3 (my device ) but don't know if they'll work for you....
One advice, reset your phone and send it to any service center.... They may charge you if you are out of warranty.....
here is a random thread i found but I have a bad feeling about the person.... Carry on at your own risk but back up your current efs, it may be recoverable but can move to a unrecoverable state after some repair attempts so, we can have hope....
link:
http://forum.xda-developers.com/showthread.php?t=2141928&page=1
Click to expand...
Click to collapse
Thank you again, eatsleep! I really appreciate your continuing help.
I've gone about as deeply into this as I think I can, without trying even more bits of dodgy software from around the web which might make the situation worse. So, I think my next step should be to take it to a reputable service centre on a no-fix-no-fee basis. If they can't fix it either, then I'll regard it as a write-off and - on the grounds that there is nothing to lose - I'll have one last go with anything/everything I can find on the net.
Whatever the outcome I will report back so that others can benefit from my mistakes!
Thanks everyone who tried so hard to help - have a good weekend.
Steve
Steve Thackery said:
Thank you again, eatsleep! I really appreciate your continuing help.
I've gone about as deeply into this as I think I can, without trying even more bits of dodgy software from around the web which might make the situation worse. So, I think my next step should be to take it to a reputable service centre on a no-fix-no-fee basis. If they can't fix it either, then I'll regard it as a write-off and - on the grounds that there is nothing to lose - I'll have one last go with anything/everything I can find on the net.
Whatever the outcome I will report back so that others can benefit from my mistakes!
Thanks everyone who tried so hard to help - have a good weekend.
Steve
Click to expand...
Click to collapse
Yeah, samsung can definitely help you, but again, be sure to make a backup of current efs to get back if situation gets worse!
And if you fail, then we can try some softwares out there, which might me improper to discuss here, but leave that for only when everything fails....
Wish you all the best
Sooo, my gf and I have same phones. S7 edge. I made back up of mine superstock rom. And made back up of hers rom. We decided to change phones becouse I bought rose gold very cheap and she has gold. So, my back up i transfered to pc, which later got corrupt I dont know why. And her back up tranfered to my phone. Wiped everything. Restored her back up, and by mistake recovered her efs in my phone. Now imei shows 000000. As I said, my back up corrupted, cant open on pc, twrp shows errors of corupted file...how can i recover my imei? Flashing stock clean rom via odin or samsung swich doesnt help...
Wixcee said:
Sooo, my gf and I have same phones. S7 edge. I made back up of mine superstock rom. And made back up of hers rom. We decided to change phones becouse I bought rose gold very cheap and she has gold. So, my back up i transfered to pc, which later got corrupt I dont know why. And her back up tranfered to my phone. Wiped everything. Restored her back up, and by mistake recovered her efs in my phone. Now imei shows 000000. As I said, my back up corrupted, cant open on pc, twrp shows errors of corupted file...how can i recover my imei? Flashing stock clean rom via odin or samsung swich doesnt help...
Click to expand...
Click to collapse
Time to send it back to Samsung for a new board. That's if they have one. Other then that you can try flashing a compete stock rom but normally that doesn't happen.
You learned a lesson. Never restore a backup from a different device.
Wixcee said:
Sooo, my gf and I have same phones. S7 edge. I made back up of mine superstock rom. And made back up of hers rom. We decided to change phones becouse I bought rose gold very cheap and she has gold. So, my back up i transfered to pc, which later got corrupt I dont know why. And her back up tranfered to my phone. Wiped everything. Restored her back up, and by mistake recovered her efs in my phone. Now imei shows 000000. As I said, my back up corrupted, cant open on pc, twrp shows errors of corupted file...how can i recover my imei? Flashing stock clean rom via odin or samsung swich doesnt help...
Click to expand...
Click to collapse
Without an IMEI/EFS backup that was created before doing this, you're not gonna find much of a solution for restoring the device.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
eatsleep said:
Wait wait,
You can't text or connect to the network?
Try flashing a official firmware and see if the IMEI matches...
It's not that simple to modify your IMEI n.o, special softwares are required to do this.... It's stored in .nv_data
Don't you have any efs backups?
IMEI getting corrupt is seen many times in s3 and note 2 devices....
And also, modifying your iMEi is illegal, but people out there use a software to do it.... May not be good to discuss this software here...
And one more thing, does your phone shows a generic IMEI number when you dial *#06* ?
Click to expand...
Click to collapse
Hi
I am using SM-N9500 samsung note 8 model, i frequently change the roms.. but last time i tried to install a custom rom and then i lost IMEI. i am getting error like IMEI-unknown, baseband- unknown, no network and sim cards not working..
i tried installing stock rom, custom roms, it was installing successfully but IMEI is not working. i didnt even back up my EFS folder. So, kindly help me to get back my IMEI.
please find below link to see all the procedures i followed and failed. kindly help me to restore my IMEI.
https://www.google.com/url?q=https:...246000&usg=AFQjCNF056_y5gTI2xpc9jM_I0ZlfkgpkA
Hi,
I've looked elsewhere on XDA threads but solutions don't seem to help.
I was running an older version of ResurrectionRemix on my S7 (SM-G930F). To install the latest version, I had to flash a different kernel. I did this, the ROM worked fine. I didn't need to receive any calls or texts over the day or so, so didn't notice a problem.
Until I tried getting an confirmation PayPal text to my phone. Didn't come through... in the end I managed to get around it, thought it was a problem on there end. However since then I've been told people can't get through to me (just goes straight to Voicemail and I don't receive the SMS messages).
I have reflashed to a different ROM and kernel (stock-based, SuperMan Rom) -- again, the ROM works fine in every way except RECEIVING calls or texts! I tried reflashing with Odin the CL file but no luck.
Short of downloading stock firmware and flashing on Odin, I have no idea what else to try? Any ideas?
Thanks!
OK I've tried stock firmware, and it's still going to Voicemail and no SMS...
Checked the "Call Divert" setting?
And make sure the correct message centre number is set in message settings for SMS
*Detection* said:
Checked the "Call Divert" setting?
And make sure the correct message centre number is set in message settings for SMS
Click to expand...
Click to collapse
No call diverts, Vodafone confirmed message centre number is correct.
Does the phone show the correct IMEI number if you dial *#06# ?
EFS Partition contains the IMEI and radios, missing or corrupt EFS would cause problems for both, although I would expect there to be problems with making calls and sending texts too
*Detection* said:
Does the phone show the correct IMEI number if you dial *#06# ?
EFS Partition contains the IMEI and radios, missing or corrupt EFS would cause problems for both, although I would expect there to be problems with making calls and sending texts too
Click to expand...
Click to collapse
Thanks for helping out -- it just says USSD code running, but then returns unknown command.
So you may be onto something?
*Detection* said:
Does the phone show the correct IMEI number if you dial *#06# ?
EFS Partition contains the IMEI and radios, missing or corrupt EFS would cause problems for both, although I would expect there to be problems with making calls and sending texts too
Click to expand...
Click to collapse
In addition to above post, I do not have an EFS backup.... eek.
I don't know if there's a way to repair this issue without shipping it off to Vodafone?
EDIT: I have a copy of the folder if that helps, all is there. The IMEI file just says BTU however, nothing else?
There is a method iirc to fix EFS, it's here somewhere on XDA in the S7 forum, if I find it I`ll post the link here, in the meantime start reading through some of the Q&A help threads about EFS and see if you come across it first
If you have the backup of the EFS folder you might be able to restore it with the help of threads like this
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Highly suggest reading a lot and asking a lot before attempting anything though or you could make things worse
*Detection* said:
Does the phone show the correct IMEI number if you dial *#06# ?
EFS Partition contains the IMEI and radios, missing or corrupt EFS would cause problems for both, although I would expect there to be problems with making calls and sending texts too
Click to expand...
Click to collapse
*Detection* said:
There is a method iirc to fix EFS, it's here somewhere on XDA in the S7 forum, if I find it I`ll post the link here, in the meantime start reading through some of the Q&A help threads about EFS and see if you come across it first
If you have the backup of the EFS folder you might be able to restore it with the help of threads like this
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Highly suggest reading a lot and asking a lot before attempting anything though or you could make things worse
Click to expand...
Click to collapse
That'd be great if you do find it, thanks. I have the folder now, but only now that it's already broken, so I'm not sure about restoring it.
The Phone INFO app shows my IMEI as the correct one. Does this mean EFS isn't corrupted, or could it still be showing the correct IMEI despite corruption?
Thanks.
Definitely sounds EFS related considering the symptoms and *#06# not working, maybe not 100% missing or corrupted but something not right with it
Either that, or whatever is blocking calls and texts is also affecting that code working / accessing EFS properly
When you flashed stock firmware, did you use CSC instead of HOME_CSC to ensure it factory reset after the flash?
Does your SIM work in another phone for receiving calls and texts?
EDIT - See if this helps
https://www.sammobile.com/forum/showthread.php?t=15196
Looks like the first thread I linked you to, and the one above are about your best bets atm
*Detection* said:
Definitely sounds EFS related considering the symptoms and *#06# not working, maybe not 100% missing or corrupted but something not right with it
Either that, or whatever is blocking calls and texts is also affecting that code working / accessing EFS properly
When you flashed stock firmware, did you use CSC instead of HOME_CSC to ensure it factory reset after the flash?
Does your SIM work in another phone for receiving calls and texts?
EDIT - See if this helps
https://www.sammobile.com/forum/showthread.php?t=15196
Looks like the first thread I linked you to, and the one above are about your best bets atm
Click to expand...
Click to collapse
Am I being dumb? When flashing I just flashed the large AP file. Do I need to separately flash the CSC?
In any case:
Heh, well I started following this guide (https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which was going swimmingly. Got the factory binary working, managed to *#06* and get the correct IMEI. So it's not corrupted to the state of not being unreasonable.
Problem is, when trying to flash firmware back again, I'm stuck at the Samsung screen from the combination binary image... (showing "ASV TBL VER = 8; ASV TBL VER2 = 0" NAD : PASSED; APMB PROVISIONED". Stuck there, won't load.
Tried repeating the process, no luck. Tried flashing TRWP on top to get into recovery and wipe, but now get "RECOVERY IMAGE FAILED!!!" and "REBOOT TO AVOID WARRANTY *****ECK!!!"
Back to the drawing board!
Progress: got past the error by reflashing the BL file from the firmware over the top after the AP. Went to "installing system update" which failed, but then rebooting led to phone boot! Yay.
Now just loading... I'll see if the IMEI is recoverable once booted and if I can receive phone calls.
If not, I'll go to Part B of that above linked guide?
You should always flash all 4 sections of the firmware at the same time
AP, BL, CSC, CP
CP = The modem...
*Detection* said:
You should always flash all 4 sections of the firmware at the same time
AP, BL, CSC, CP
CP = The modem...
Click to expand...
Click to collapse
Interesting, seemed to work without flashing BL/CSC/CP.
In the end that guide A did fix things Reflashing BL allowed phone to boot, and could make and receive calls.
Thanks for your help!
Great, pleased you sorted it :good:
Edited in 2022 to make it look a bit better!
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it OR YOU CAN LEAVE Privo data and factory app, you have a backup anyways. *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma. You may try to skip this step. There have been comments saying that this guide also works without this step.
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while for the signal to appear. If your signal is returned then go to phone app and dial *#06# and look or the IMEI matches the IMEI of the box of your phone (make sure you have the original box if you don't have this then open the back of your phone (if you can), there is a sticker label with your s/n and IMEI. If you cannot open the back of your phone, then you will have to trust that the IMEI is right. If everything is functional then you're done with this guide. The next steps are more ''checking'' if everything is alright.
Step 7) If your s/n is ok skip to step 8 if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and IMEI and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Congratulations on getting past step 8. I hope this guide has helped you and that it worked for you. If not then I'm sorry for not being able to assist you. This guide is just me sharing what I did to solve this issue. Good luck on solving your problem if this guide did not work.
If the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) When you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version. You can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) If it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) If you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Happy flashing and please confirm in the comments below if it worked for your device or not
Guys please comment or it works on your device or not!
It works for me. But I have to manually change CSC on my phone after original rom flash to fix Network. TGP rom have that option.
I followed your guide and my model name changed from G930F to G930FD and my IMEI is just bunch of zeroes wtv
SOLVED AT LAST - MISSING IMEI and EFS DAMAGED SOLUTION
Hi Guys,
First off, please take GOOD note - I am NOT a techy, just an old boring flashaholic who works in an office and likes pyjamas more than partying. This is my account of me fecking up my phone and finally reaching a solution after three days and most of two nights to a missing IMEI, messed up EFS and non-working phone - hoping that it might help anyone as desperate as I was. You do what you do with your phone and that's your business and I'm not responsible if you mess it up, but my hope is that you have have a brain (that's all I have) and you get some helpful piece of info here as I did from a whole ton of posts I read that finally led me to this.
Next - I am not sure what landed me in this mess. I've seen Superman Rom mentioned a couple of times..I didn't use that but I did use Batman Rom which is by the same Dev. It was great to use, too, so I'm not faulting the Dev by any means. What did happen, though, is that when I flashed other ROMS, maybe 3 or 4 of them following, the Batman splash screen was always there before the new ROM's boot sequence, so there were clearly some residual things of it in there ...so perhaps the same coding is in there and could have had something to do with it, I don't know. The breaking point came when I flashed Sac23 Rom hoping to get Pie on my phone. It was cool but I decided to revert to Resurrection Remix - always my favourite overall - and all of a sudden I get errors.
What should have been a routine "Restore" of my backed up RR ROM via TWRP gave "Error mounting EFS". Reboot, wipe, retry. No joy, same again. A couple of tries to restore the EFS from the backup in TWRP didn't work either.
Next go to is flash "original firmware" (more on this wording later). I had that on my PC (not a phone backup, just the firmware so it's clean copy with no data).
Get Odin out, download mode, correct files in correct boxes, all that standard stuff you can find guides on most places - no joy.
Error showing was "Fail at pm.bin" or something like that. Install aborted.
Try again. This time "Fail at cm.bin" Install aborted. Reboot from recovery also fails. Oh sh1t.
Several more attempts made. I have five different Odin vers. I have seven different firmware vers. I have two USB ports and about 8 Samsung cables. Not a single combination I tried worked.
The XDA heroes will know what to do, I thought. I read and read. And read. And CubZ (who is a hero even if he IS from Lancashire ), says MAKE SURE YOUR PHONE IS RUNNING ORIGINAL SOFTWARE. Well...I kinda did that mostly already...but maybe I need to go RIGHT back to the rubbishy 6.0.1 version that came actually ON my phone when I got it....almost 2 years ago? Who remembers that stuff?? I'm about 18 ROMS down the line now. I was desperate. I'm telling you...I even got out my bank statements to trace when my first payment to my current provider was...I read about firmware numbers and country codes, and I chose one from Sammobile with a build date, country code, unbranded code (which my phone always was) and correct phone model (of course!) as I needed. And it WAS .."the ORIGINAL" firmware.
This time I swear Odin failed me a second BEFORE I pressed the start button! No joy.
Have a flask of coffee and a few valium sandwiches and off I go back to XDA again. I read a loooong series of "Missing IMEI" stuff and there's CubZ again with an IMEI/EFS fix guide guide...brilliant! And it WAS brilliant, and clearly he helped tons of people (kudos, man). But I had messed up MY phone in the time-honoured "right royal" way - worse than his guide could help me. My IMEI was Unknown, my EFS was empty, My SIM wasn't being recognised, no network info or signal...nothing. But genius that he is, he CubZ DID post a Combination file that gave me a base to keep trying on when firmware after firmware had failed almost immediately with errors either of pm.bin/abort or cm.bin/abort.
I almost wore the print out on CubZ guide, I read it so much and tried so many times. Then...I see people saying things about U1, U2 and U3 firmwares. Turns out you shouldn't mix the two. I got that snippet from CubZ too. More research and the little coffee-fuelled connections in my brain are like.....ok....
My ORIGINAL firmware has in its name "U1" and there are similar ones with "U2". Might that be it? My phone has been screaming "DEVICE 2 FIRMWARE 1" (or something like that) at every aborted 'original firmware' installation via Odin and download mode that I've tried, including the EXACT firmware that was on my phone the day it was unwrapped and I danced happily round the room with it.
So if DEVICE 2....FIRMWARE should be 2 maybe? Back to Sammobile. There are firmwares with the same model number, country code, branding info as mine..but with a "U2" where mine said "U1". But...they were Oreo and Nougat where mine was "originally" Marshmallow.
It's now day three in the Big Mother House. My valium and coffee and running out and my communication with the outside world has ceased. I've had about five hours sleep, my food is running low and I cannot call for takeaway cos I ficked my phone up good and proper. I even....get this....start looking up PAID services to fix this. I KNOW, right!!??
I pick up a Nougat firmware from Sammobile...careful to match model, country, branding AND U2 - wondering if I can match it up with CubZ's Combi file as a base to appease Odin......and then maybe revert to my 'original' stock from that to start another attempt at the IMEI/EFS thing.
It loaded. Odin was pleased with my sacrifice. And lo and behold, it had restored the whole lot WITHOUT me having to go any further with stock ROM reversions. It frickin' worked. I got my signal back. My SIM card was detected. My phone number was showing. My IMEI was showing. My E-Frickin-S was mended. I feel like Judd Nelson at the end of Breakfast Club.
So here's the semantic bit that I hadn't known and that is unclear in many many posts. My phone is now working 100% on stock firmware....but is is NOT REALLY the ORIGINAL software - it's the MODEL......COUNTRY......BRANDING.....LANGUAGE - specific firmware but it is Nougat where my original was Marshmallow, and it is a U2 firmware where my original FW was U1. THAT was the killer difference, it seems. Thanks to all of you who posted anything - many many of you - who helped me get this. It's a compatibility issue detail I've never seen or had issues with before.
I now have G930FXXS2DRDI_G930FXEU2DRB5_XEU
Where G930F is the model number, XEU is the country code for UK and Ireland (even though UK is a nation and not a country - just sayin' ) and the U2 sits there hiding in the middle of the second section of the name.
Which gives unzipped files as follows: NOTE - THESE ARE NOT LINKS.
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar.md5
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar.md5
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar.md5
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
It's Nougat, but that's okay for now; I got my IMEI, EFS, SIM, BIN, probably ENT, RAC, SUV and BMX too, everything
And now, with my working phone, I am gonna phone the local Chinese Takeaway for food, answer all my emails that popped and binged and tinkled at me when it became resurrected, and leave CubZ with huge thanks and all of you guys with the hope that this helps somebody out there.
And maybe look at backing this sucker up and reverting to my Oreo RR ROM I love so much..... I HATE Touchwiz!!!!
Good luck!
:good::good::good:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
shabbir143 said:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
Click to expand...
Click to collapse
You deleted all files and folders from EFS Mounted partition? how is it possible working?
You are awesome man!
I just deleted the files in EFS, restarted without installing custom rom and my IMEI was fixed.
I'm definitely donating. How to donate to you?
Thanks for your great work!
cisekpro23 said:
You deleted all files and folders from EFS Mounted partition? how is it possible working?
Click to expand...
Click to collapse
I think samsung phones are capable of regnerating their efs. But its not working for me on samsung galaxy s6. Guess I am screwed.
Hey everyone, I'm sorry for not responding to anyone in this thread. I've been inactive for a long time. I want to thank everyone for trusting the guide and I hope it has worked for you if you tried following the steps. If you have any questions feel free to ask me.
Also I have edited my guide to improve the reading experience because I see my English was absolutely horrible at the time when I wrote the guide.
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
vigilante said:
Edited in 2022 to make it look a bit better!
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it, you have a backup anyway *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while if your signal is returned then go to dialer and dial *#06# and look or the imei matches the imei of the box (make sure you have the origional box if you dont have this then open the back of your phone, there is a sticker label with your s/n and imei if imei is not good then skip to step 9
Step 7) now if your s/n is ok skip to step... if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and imei and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Step 9) now for if the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) when you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version you can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) if it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Please donate and like this thread if you found this helpful, I have experienced this problem my self and it costed me €60! I said NO its too expansive so then I found this solution and now I am sharing it to the world, I could have let this guide cost €61 but my guides and solutions are free a support would be great for finding this out
Happy flashing and please confirm in the comments below if it worked for your device or not
Click to expand...
Click to collapse
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
bamcarpio123 said:
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
Click to expand...
Click to collapse
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Click to expand...
Click to collapse
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
vigilante said:
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
Click to expand...
Click to collapse
I'm sorry for being so stupid because I continued without performing a backup in TWRP, I forgot to back up the EFS, and when I panicked because I was already screwed up, I deleted the efs folder—which is incorrect. I deleted the efs partition before I saw this thread. And now it always says, "failed to mount /efs (invalid argument)" and I've done everything, and it seems like everything is done, I have no idea what to do. I haven't slept for four days and there is still no hope. but my phone is still okay with the stock firmware, but it always restarts. I did almost everything but still nothing
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
If I lose my IMEI, it won't matter. But the thing is my phone is always restarting every minute.
(can someone know how to disable auto-reboot so i can still use my phone even the EFS is damaged?)
ALSO THANKYOU FOR YOUR REPLY! I APPRECIATE IT!
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER? HMM. BUT I WON'T GIVE UP
bamcarpio123 said:
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
Click to expand...
Click to collapse
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER?
Click to expand...
Click to collapse
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
.
.
vigilante said:
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
Click to expand...
Click to collapse
My phone is Samsung Galaxy J8. Before i start to flash custom rom, I took a snapshot of the device's hardware information and discovered that the csc is really XTC. I have completed all the necessary steps. I did everything right, but nothing actually changed. I'm so exhausted that I might just give up. I appreciate your assistance.
If I can't retrieve the imei, it's fine, but unfortunately my phone is always restarting
EDIT: MY PHONE IS NOW FIXED. THE SIMS ARE NOW WORKING, THE SIGNAL IS BACK AND I FEEL SO HAPPY. HOW DO I FIX? WELL I USED THIS METHOD, I DELETE ALL THE FILES FROM EFS FOLDER (NOT THE PARTITION JUST THE FILE INSIDE OF IT) THEN I FLASH THE LATEST STOCK ROM WHICH IS ANDROID 10 BUT THE CSC FILE IS FROM ANDROID 9 AND AFTER THAT I USED TFT SAMSUNG MODULE WHICH IS VERY HELPFUL AND LEGIT TOOL AND ITS 100% FREE!. THEN I FIX THE IMEI AND BASEBAND USING THAT TOOL AND YES THAT SOFTWARE IS A BEAST. AND NOW ITS WORKING PROPERLY. IT TOOK ME 2 WEEKS TO SOLVE THE PROBLEM BUT IN REALITY ITS VERY SIMPLE HAHAHA! IT SAVES ME FROM SPENDING MONEY JUST TO SAVE MY PHONE BUT I DO NOT KNOW THAT I AM THE ONE WHO WILL FIX MY PHONE HAHA HOW COOL IS THAT. JUST DON'T GIVE UP NO MATTER WHAT HAPPENS!
#FVCKTHATZ3XBOX
THANKS TO THIS METHOD AND TO SIR VIGILANTE.
EVERYTHING IS POSSIBLE JUST DONT GIVE UP EVEN YOU'RE TIRED.