Efs/etc/modemfs - Galaxy S III Mini Q&A, Help & Troubleshooting

I want a backup of these folders: efs/etc/modemfs PLEASE!!!!!

Someone make a backup of these folders PLEASEEEEE!!!!!!!

alexandru5796 said:
Someone make a backup of these folders PLEASEEEEE!!!!!!!
Click to expand...
Click to collapse
regarding efs, you will not benefit from it, since every phone has his own NV_Data and IMEI.
here are modem and etc

If i'm not mistaken the NV_Data can be restored/rebuild from the servicemenu.

Related

[Q] JM6 IMEI Change

Hi, i've just dialled *#06# to get my IMEI and my imei number has changed from 352*********** to 00004**********.
Does anyone currently know of a way to change the imei number back? Thanks in advance.
Your Friend
Phil
I noticed on JM6 and JMA that it made my IMEI number incorrect as well, so when I entered it, it didn't recognise it to change the CSC.
Not sure if there is a way, hopefully so!
I'm sticking with JJ7 now on my replacement tab until we get a proper recovery mode in place.
I had this on my galaxy S. Solved it by backing up the efs directory to be safe. you need root. then delete everything in the efs dir except nv_data.bak then rename it to nv_data.bin and reboot. It should rebuild the efs dir correctly and put the imei back.
But this only works if the nv_data.bak file has not been modified in anyway otherwise it will rebuild with the 0044 imei.
Lordao
Is a corrupted IMEI, can create you problems
I had it too before, but because I deleted also all the .bak files in the EFS folder...
You can recovery in 2 ways:
1st:
I suggest you to delete the nv_data.bin and the nv_data.md5 in EFS folder using rootexplorer then rename the .nv_data.bak to nv_data.bin and the .nv_data.md5.bak in nv_data.bin.md5 (same suggested by lordao); You can also delete the md5 files because it will rebuild it by itselfs.
2nd:
In the bad case the 1st solution will not work, means that your backup files are corrupted and your IMEI is not recoverable.....BUT if you are lucky like I was I recognize that I had a copy in my sdk folder (the one you used when you rooted the Tab!!!) I think the one click root did a backup copy of the nv_data.bin by itself. Grab that file and copy it in the EFS folder (deleting all the other nv_data.bin and nv_data.md5 and relatives .bak that you have in the folder) restart the tab. It will self rebuild the md5. You can make the new .bak files copying the nv_data.bin and rename the copy ad .nv_data.bak
Hope it will help you
Thanks zerocool76 worked perfect!! I now have my imei back. Your a star. Think I will keep a backup of that file. Just in case of future flashing.
diigibio said:
Thanks zerocool76 worked perfect!! I now have my imei back. Your a star. Think I will keep a backup of that file. Just in case of future flashing.
Click to expand...
Click to collapse
Just to know. Where you found the file? In the sdk? Because it would means that your .bak was corrupted too and I'm wondering why..???!!! Anyway glad it was working.I suggest you to backup all the EFS folder
zerocool76 said:
Just to know. Where you found the file? In the sdk? Because it would means that your .bak was corrupted too and I'm wondering why..???!!! Anyway glad it was working.I suggest you to backup all the EFS folder
Click to expand...
Click to collapse
I noticed and fixed this a few days ago.
When I look at my EFS folder backup, done right after rooting the Tab, I can see that nv_data.bak; size 1732608, is a different size, with an earlier creation date than the original nv_data.bin; size 2097152. According to nv.log, my nv_data.bin was corrupted during the time-frame where I was flashing different modems to the Tab while testing the screen timeout bug on JMA, it reports that when nv_data.bak was restored as nv_data.bin the file size was invalid, then says that it restored nv_data.bin, created from scratch I guess, which resulted in the improper IEMI and a serial# of all 0's.
Bell Tab
Roto-JMA firmware
Bell I9000UGJK4 radio
rgbc said:
I noticed and fixed this a few days ago.
When I look at my EFS folder backup, done right after rooting the Tab, I can see that nv_data.bak; size 1732608, is a different size, with an earlier creation date than the original nv_data.bin; size 2097152. According to nv.log, my nv_data.bin was corrupted during the time-frame where I was flashing different modems to the Tab while testing the screen timeout bug on JMA, it reports that when nv_data.bak was restored as nv_data.bin the file size was invalid, then says that it restored nv_data.bin, created from scratch I guess, which resulted in the improper IEMI and a serial# of all 0's.
Bell Tab
Roto-JMA firmware
Bell I9000UGJK4 radio
Click to expand...
Click to collapse
I destroyed my original nv_data.bin editing with a txt editor instead hex editor, plus I deleted baks files for mistake with root manager (no booze when playing with this **** anymore ), I didn't know that the IMEI is encrypted in that file. When I found a copy in my sdk (that I didn't make!?) I restore everything, and after that time I flashed a lots of Firmwares and Modems, but my imei is still ok.I know that a Galaxy S firmware made this issue because it was changing the nv_data and it didn't match anymore with the phone, so corrupted IMEI.I'm wondering if there is a firmware that is doing the same with the Tab
Mine has done the same but with JK5. First noticed when I did the Samsung UK offer thing. Completely different IMEI to whats on the back of my Tab.
Sent from my GT-P1000 using XDA App
Sorry to dig up and old thread, but is this still an issue, can say flashing back and forward from Overcome for example corrupt IMEI etc?
Interesting - are other Samsung devices able to have their IMEI changed?
What this means is that to a technically capable enough thief (or one who knows someone technical enough that will work on credit), Samsung devices are much more valuable: Normally if your mobile got stolen and you had the IMEI, you would report it to your network and they would have it blocked on all networks. Furthermore the police would use the IMEI to prove that the device is yours if it were recovered. If the IMEI can be changed, the device can't be identified and can't be blocked from networks. It only needs slight tweaking to make it appear valid. Don't know about the implications for post-registration call routing, but the thief wouldn't care about that.
In the US, gsm carriers won't block the number - they seem to view stolen phones as a potential new subscriber.
hello,
i have the same trouble ( imei change)on galaxy tab , but the phone work normally (for now ...).
Can i let it so , or could have trouble in future?
because i don't save nv data folder, and i'm not very good to restore rom.The mod was made from my friend.
excuse for my english ,bye
zerocool76 said:
Is a corrupted IMEI, can create you problems
I had it too before, but because I deleted also all the .bak files in the EFS folder...
You can recovery in 2 ways:
1st:
I suggest you to delete the nv_data.bin and the nv_data.md5 in EFS folder using rootexplorer then rename the .nv_data.bak to nv_data.bin and the .nv_data.md5.bak in nv_data.bin.md5 (same suggested by lordao); You can also delete the md5 files because it will rebuild it by itselfs.
2nd:
In the bad case the 1st solution will not work, means that your backup files are corrupted and your IMEI is not recoverable.....BUT if you are lucky like I was I recognize that I had a copy in my sdk folder (the one you used when you rooted the Tab!!!) I think the one click root did a backup copy of the nv_data.bin by itself. Grab that file and copy it in the EFS folder (deleting all the other nv_data.bin and nv_data.md5 and relatives .bak that you have in the folder) restart the tab. It will self rebuild the md5. You can make the new .bak files copying the nv_data.bin and rename the copy ad .nv_data.bak
Hope it will help you
Click to expand...
Click to collapse
i can recovery ANY imei number on ANY android device im currently making a program to do this automaticly
paul.robo said:
i can recovery ANY imei number on ANY android device im currently making a program to do this automaticly
Click to expand...
Click to collapse
Hows that program coming along? I might be in need of it on account of
losing my IMEI on my Galaxy tab.
ktmman said:
Hows that program coming along? I might be in need of it on account of
losing my IMEI on my Galaxy tab.
Click to expand...
Click to collapse
So i got my IMEI no.back but i still don't have a data connection. The strange thing is if i swap sim cards
with my phone it works so im not sure whats wrong with it.

I have no efs folder yet I am able to get an efs_backup?

Using the thread below, I am able to get an efs_backup, but there is no original efs folder on my phone. it has all the nv_data.bin and files like that, but no "efs" folder on my phone. What is the proper file structure? Thanks
http://forum.xda-developers.com/showthread.php?t=881162
You have no /EFS partition? and still get a backup with the files in it? Use a root enable file explorer and check the very root of the phone for /efs not /system/efs but /efs...
I am running the stock Xperia Play ROM and I don't have an /efs partition either. I haven't tried making backups yet, but I do have an IMEI and I can make and receive calls.
I understand this is the forum for a Samsung phone and perhaps only Samsung phones store their IMEI like this. Is it even possible to lose your IMEI on an Xperia Play?

Empy Modemfs Folder

Hi, im running JB VSLP9 (Movistar Argentina firmware) and recently i decided i should backup efs and modemfs just in case. I followed the steps in this guide http://forum.xda-developers.com/showthread.php?t=2342100
I don't know if this is related but recently i've been having some problems with 3G connectivity. Sometimes the phone shows good signal but no data connection. You have to restart the phone to correct this. Also, some people have told me that calling me directs them straight to voice mail.
I was looking at my modemfs folder and then discovered that it is empty! 0 files, 0 bytes. So i tried to restore the backup that I made (16mb). But nothing changed, the folder is still empty ....
Is this normal ??? Can my problems be related to the "backup" of efs and modemfs ????
Thanks
Can anyone at least check your modemfs folder and tell me its contents ?
Piachnp said:
Can anyone at least check your modemfs folder and tell me its contents ?
Click to expand...
Click to collapse
Here you go.
But I do not know how to fix yours...
Thanks Shutdown, i tried wiping everything and flash the firmware again, but the modemfs folder is still empty... That crappy backup guide ****ed up everything
Does anyone know if i can ask for someone using the same firmware for the contents of this folder and copy them to my phone ????
Piachnp said:
Thanks Shutdown, i tried wiping everything and flash the firmware again, but the modemfs folder is still empty... That crappy backup guide ****ed up everything
Does anyone know if i can ask for someone using the same firmware for the contents of this folder and copy them to my phone ????
Click to expand...
Click to collapse
Maybe you need to mount modemfs partition before restoring? Look how to do that (trough terminal emulator, or ADB shell).

[Q] Copying EFS folder to other identical phone?

I have two identical Note 3 from AT&T. (Mine and my wife's) I screwed my phone and do not have backup of the EFS folder. Can I copy my wife's EFS folder to my phone?
If my copy my wife's EFS folder to my phone, will it cause IMEI duplication on our phones?
AlwaysNoob said:
I have two identical Note 3 from AT&T. (Mine and my wife's) I screwed my phone and do not have backup of the EFS folder. Can I copy my wife's EFS folder to my phone?
If my copy my wife's EFS folder to my phone, will it cause IMEI duplication on our phones?
Click to expand...
Click to collapse
If you did not make any backup of your EFS folder, and your IMEI is messed up, this could be your solution to recover your lost IMEI. NOTE THAT AT LEAST YOU MUST HAVE THE SHIPPED ORIGINAL EFS FOLDER ON YOUR PHONE ( even if you didn't make a backup of it yet and even it's messed up ) FOR THIS METHOD TO WORK
Paulita1 said:
If you did not make any backup of your EFS folder, and your IMEI is messed up, this could be your solution to recover your lost IMEI. NOTE THAT AT LEAST YOU MUST HAVE THE SHIPPED ORIGINAL EFS FOLDER ON YOUR PHONE ( even if you didn't make a backup of it yet and even it's messed up ) FOR THIS METHOD TO WORK
Click to expand...
Click to collapse
So I can use the EFS folder from another identical phone? Will both phones have same IMEI if I copy it?

Please: were i found EFS folder in system, Oreo Roms?

TWRP ok, i create backup and i can restore too, but i need manage this EFS folder with root Explorer, whats the directory?
system/?
Thanks for attention.
joaonds said:
TWRP ok, i create backup and i can restore too, but i need manage this EFS folder with root Explorer, whats the directory?
system/?
Thanks for attention.
Click to expand...
Click to collapse
Hi, this directory Is not available for the user from 6.0 onwards
EmiAndroid said:
Hi, this directory Is not available for the user from 6.0 onwards
Click to expand...
Click to collapse
How TWRP get this folder to backup?
Is there in some local, with root i not found.
I need this directory, because twrp dont restore my IMEI when i update my rom, i lose imei and backup not save me, i dont know why.
joaonds said:
How TWRP get this folder to backup?
Is there in some local, with root i not found.
I need this directory, because twrp dont restore my IMEI when i update my rom, i lose imei and backup not save me, i dont know why.
Click to expand...
Click to collapse
Mmmm look, check this theard https://forum.xda-developers.com/moto-g5s-plus/how-to/how-to-fix-imei-g4-pesist-flashed-t3780837 and tell me, good look!

Categories

Resources