Database Develop

[Q] Forgot to back up /efs before my first flash. Productcode korean etc.

I just browsed with root explorer searching for smth and then I noticed that my phones productcode says korean.
On my first ever flash of the phone I forgot to back up the /efs folder as I read about this later. How can I restore to original (german phone, unbranded)? And is this necessary at all? I'm not really planning to use a stock rom ever again, unless I want to send it back for service... Does this actually affect something?
And .. this doesnt/didnt change the phones IMEI or how its called number, did it?
EDIT: I actually did have a .bak of my nv_data.bin and the md5.. I renamed those to the right names etc and rebooted and now the product code is back to german again. But in the IMEI subfolder it still says KOR in that file there.

To get back to the German code.
Hi,
I had the same problem and successfuly changed it back by doing the following - dial *#272*YOUR IMEI# When this opens you get a choice of codes. Change yours to DBT (Germany). A word of warning! This will clear all your settings and apps so backup anything you need before hand.
Good luck and let me know if all is well.

zroice said:
I just browsed with root explorer searching for smth and then I noticed that my phones productcode says korean.
On my first ever flash of the phone I forgot to back up the /efs folder as I read about this later. How can I restore to original (german phone, unbranded)? And is this necessary at all? I'm not really planning to use a stock rom ever again, unless I want to send it back for service... Does this actually affect something?
And .. this doesnt/didnt change the phones IMEI or how its called number, did it?
EDIT: I actually did have a .bak of my nv_data.bin and the md5.. I renamed those to the right names etc and rebooted and now the product code is back to german again. But in the IMEI subfolder it still says KOR in that file there.
Click to expand...
Click to collapse
Inside IMEI folder, you could change content of "mps_code.dat" from KOR to your german one.
Don't forget to also change versions numbers inside "build.prop"...
Sent from my GT-I9000 using XDA App

what exactly do i have to change in the build.prop then?
Also I used the prop browser from sgstools and for ro.product.locale.language it says en and for the region it says GB (guess thats why after a factory reset the language is english.. but thats fine)

CSC and Kies

I have a problem with my phone. I bought the phone through a carrier, so it had the CSC set to UFN, but then i decided to flash through odin the brandless version of the firmware, which has the CSC set to ARO. The thing is that while *#272*<IMEI># shows me that i have the ARO code, kies keeps showing me the UFN cose thus making me unable to update through it. What can i do to make kies update the CSC from UFN to ARO?
Regards

Well i have an update on this, apparently kies is reading the UFN through the PRODUCT CODE and not the CSC. The problem now is that apparently the PRODUCT CODE information, along with other things like IMEI, is stored in a file named .nv_data.bak in the efs folder. The thing is that i don't have that file on that folder, but somehow the phone and kies can still read the PRODUCT CODE and the IMEI so they must be getting the information from somewhere. My questions now are, where is the file from which the phone and kies are reading the product code? Can i change the PRODUCT CODE from there? Can i copy the .nv_data.bak from another I-9070 and work from there or the files are completely different?
Regards

file is called nv_data.bin.md5 - and it must be there - or else *#06# will give you 0000000000 or some kind of error.
IDK if copying this file from other phone will fix it for you but I would rather not give it away to anyone (in this case you) because of IMEI - so it might be hard for you to get one from anyone else.
You can try to flash ARO again - I had PLS ROM (branded by Plus in Poland) and I have flashed XEO (Poland - not branded) and my Kies shows me XEO and OTA update was detected and applied as XEO
I downloaded XEO from here: http://samfirmware.com/
EDIT:
One more thing comes to my mind: is it maybe carrier locked device (as in no other sim card will work on it)?
In such case it is probably that thing - sim locked to UFN and stays there no matter the ROM region code

th3cr0w said:
file is called nv_data.bin.md5 - and it must be there - or else *#06# will give you 0000000000 or some kind of error.
IDK if copying this file from other phone will fix it for you but I would rather not give it away to anyone (in this case you) because of IMEI - so it might be hard for you to get one from anyone else.
Click to expand...
Click to collapse
When i do *#06# i get my phones IMEI perfectly, but in the efs folder the only nv files i have are .nv_state, nv.log and nv_data.bin.md5 (this file with 0 bytes of info). That's why I'm puzzled, if the files are not there i shouldn't be able to retrieve my IMEI or PRODUCT CODE, but i can do that perfectly fine. Maybe the info is stored somewhere else?
Regards
Edit: i believe that flashing the stock ROM doesnt restore the efs folder, am i wrong?

all IMEI repairing guides are using nv_data.bin (no .md5) that is 2MB of size so at least this part must be there - thing is my phone gives me my IMEI with 8#06# and i do not have nv_data.bin - just .md5 as in your case - 0b in size.
IDK about product code location but I know that flashing non-branded ROM changed how Kies sees region of my device and I didn't mess with my device anymore - just applied root to XEO and flashed rooted one - I am sure that no root version would work the same way

th3cr0w said:
all IMEI repairing guides are using nv_data.bin (no .md5) that is 2MB of size so at least this part must be there - thing is my phone gives me my IMEI with 8#06# and i do not have nv_data.bin - just .md5 as in your case - 0b in size.
IDK about product code location but I know that flashing non-branded ROM changed how Kies sees region of my device and I didn't mess with my device anymore - just applied root to XEO and flashed rooted one - I am sure that no root version would work the same way
Click to expand...
Click to collapse
If I'm not mistaken the information actually comes from .nv_data.bak not .bin, and kies needs a match from the CSC and the PRODUCT CODE to allow updates. I can change the CSC freely, but lacking the files in the efs folder i cannot change the PRODUCT CODE, but as i already mentioned it is extremely weird because those files also contain the IMEI info and both my phone and kies can read the IMEI and PRODUCT CODE perfectly, which leads me to the conclusion that maybe the files are stored somewhere else?
Regards

Please, can i get some insight on then the matter? At least from the technical part, how can my phone and kies read the IMEI and PRODUCT CODE when the files that have that information (nv_data.bin, nv_data.bak) are missing? Where are they getting the info from, from which files?
Regards

Well, to give a helping hand to people who may encounter the same problem, here is the solution. When i was almost ready to give up i found this thread that explains how to back up the efs data in the Samsung Galaxy S III Mini, and there it said that this particular phone has the NovaThor chipset and that it doesn't posses the normal nv files in the efs folder. So i checked the specs of our phone and i realized that it also has a NovaThor chipset. Then after a little investigation i found that that the file that has the PRODUCT CODE information is in this location /ModemFS/Perm/prot/ and in this file NV.DAT. I changed the PRODUCT CODE there i now i can freely update with kies!
Regards

CSC question
hey guys! i need help.. when i dial *#272*IMEI# my csc/sales provider is O2i(United Kingdom-Ireland). i was wondering how i could change it (if possible, to SMA(philippines)). when i try to do so, i only get o2i and nothing else. no other choices (even when using csc changer from google play). the phone had been locked to o2i but had been unlocked here in the philippines ( phone was given as a gift). any suggestions?

Lost IMEI

Hello, I lost IMEI data from my i9305 :\
Trying to fix it whole day, but I give up now, im done.
I tried several guides (sammobile.com/forum/showthread.php?t=15196) but nothing helps.
Basicly biggest problem I face is that when I dial to *#7284# it shows "Network is not avilable" so nothing happens, or with another method with removing EFS folder, after backuping it at SDcard1 I have no .nv_data file to modify it and fix everything.
I use SentinelROM v6.0, I tried installing some modified modems, but it was retarded from me. I installed one from orginal firmware today meanwhile I was trying to fix IMEI :\
Can anyone help me?
@edit
I dont have backup. Imei and baseband - unknown ;(
I also would like to add that I know my imei (have it written down :3), but can I somehow rebuild efs based on it :3?

I feel so lucky, I flashed orginal firmware through odin and everything is fine now I just need to upload 4.4 again, and make backup for future!
That was my lesson :3 Thread can be closed.

[HELP] No IMEI, CSC Unknown, no SIM Card not recognized

After I flashed my I8190 with a custom ROM it has the following problems No IMEI (null/null), CSC Unknown, no SIM Card not recognized, but my baseband is recognized (i8190xxamg4)
I read that it might a problem with the EFS folder and that it can be fixed over the nv_data file, but i don´t have the nv_data.bin file in the efs folder.
i have tried every single fix available on the Q&A Forum, flashing stock rom + pit, flashing new baseband even modemfs files and the EFS backup from the thread above but it still doesn´t work.
Does anyone have a nv_data.bin, so i can use it to get my imei back and edit it to my original one, or is there any other fix.
please help me, i really need to get my phone working again asap
thanks in advance

anyone?

Please I need your HELP...!

I'm still with my broken SGS3 mini (GT-i8190) using it only for computer. I cannot make any call or something like that, so the internal signal doesn't work.
My phone broke about a year ago (IMEI null, not generic; Serial Number modificated; unknown baseband). This happended when I tried to flash the thirth time the ENOX ROM, and a couple of days after the phone begun to run slower, and 4 hours after (during the same day) the phone have frozen and didn't boot anymore.
Then I tried to flash (stocks ROM, stocks ROM with root, CM, Carbon ROM, etc...) and I cannot regenerate or recover the IMEI/SN/Baseband.
I have not any box to try to fix my phone, and I cannot buy one (a lot of money for me just now).
I thought that if it possible a thing, I would like to test but I don't know if it's possible.
I was thinking in take a entire EFS folder from other device SGS3 mini (same model, no L/N) and try to edit the files that contains the IMEI information and this thinks with hexadecimal editor. It would be possible? Or it's stupid try to do this? I don't know... **** (sorry).

CrashOverride93 said:
I'm still with my broken SGS3 mini (GT-i8190) using it only for computer. I cannot make any call or something like that, so the internal signal doesn't work.
My phone broke about a year ago (IMEI null, not generic; Serial Number modificated; unknown baseband). This happended when I tried to flash the thirth time the ENOX ROM, and a couple of days after the phone begun to run slower, and 4 hours after (during the same day) the phone have frozen and didn't boot anymore.
Then I tried to flash (stocks ROM, stocks ROM with root, CM, Carbon ROM, etc...) and I cannot regenerate or recover the IMEI/SN/Baseband.
I have not any box to try to fix my phone, and I cannot buy one (a lot of money for me just now).
I thought that if it possible a thing, I would like to test but I don't know if it's possible.
I was thinking in take a entire EFS folder from other device SGS3 mini (same model, no L/N) and try to edit the files that contains the IMEI information and this thinks with hexadecimal editor. It would be possible? Or it's stupid try to do this? I don't know... **** (sorry).
Click to expand...
Click to collapse
Yes your EFS is broken. EFS is a partition and not just a folder You can backup a EFS from a another s3 mini and restore it to your one but you will get signal problems example WiFi because same MAC address) and the other s3 mini too. You should know the IMEI number is NOT saved in EFS partition, the real IMEI is saved in a hidden partition so it means you didn't lose your IMEI. But your IMEI security key code (it's saved in /efs>imei) is gone and it means you will never get access to your IMEI number again.

xXPR0T0TYPEXx said:
Yes your EFS is broken. EFS is a partition and not just a folder You can backup a EFS from a another s3 mini and restore it to your one but you will get signal problems example WiFi because same MAC address) and the other s3 mini too. You should know the IMEI number is NOT saved in EFS partition, the real IMEI is saved in a hidden partition so it means you didn't lose your IMEI. But your IMEI security key code (it's saved in /efs>imei) is gone and it means you will never get access to your IMEI number again.
Click to expand...
Click to collapse
Thanks for all...

Imei is probably stored in CSPSA partition which is mmcblk0p9. I can see my serialnr in there and referees to modemfs, but the rest is encrypted.
I started to look at this a bit closer today to see if I can find out how this all is put together.(efs/modemfs/CSPSA).

tys0n said:
Imei is probably stored in CSPSA partition which is mmcblk0p9. I can see my serialnr in there and referees to modemfs, but the rest is encrypted.
I started to look at this a bit closer today to see if I can find out how this all is put together.(efs/modemfs/CSPSA).
Click to expand...
Click to collapse
Please I need help!!!! I say what happended here... Could yo help me?

Mod Edit
May I remind you of the XDA RULES # 5
Thread closed
malybru
Forum Moderator