Related
I flashed the new ROM (9100XWKDD_I9100XXKDH_I9100XEUKD1) and now in Recovery I see the error in the attached pic.
Is this normal? If not, how do I fix it? I've tried reflashing the ROM several times through odin with just the ROM loaded in PDA.
Code:
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEU/system/'.
Successfully applied multi-CSC.
Normal. Well, I assume it is because mine does the same!
I managed to get rid of the error by flashing ROM I9100XEKDB which also finally gave me a list of CSCs to choose from. Before there was just the one (XEU) CSC listed.
Only problem is the I9100XEKDB ROM doesn't include a XEU CSC and when I flash back to the KDD ROM I get a similar error and only SEK is listed in the CSC list.
Code:
Can't access to '/system/csc/SEK/system/'.
After flashing the ROM with XEU CSC you need to format and the reflash the phone with the same firmware to get it back to XEU. This is how I did it to get back to XEU from some German csc.
After flashing I9100XWKDD_I9100XXKDH_I9100XEUKD1 I wiped cache and did a factory reset through Recovery. This brought me back to my original error but atleast I now have the XEU CSC, still unable to view or select any other CSCs via the Dailer.
I then performed a factory reset through the Settings menu. Same result as above. Also tried a factory reset using code *2767*3855#
Intratech, do you have the error in post #1?
I might flash the O2 ROM which has a different CSC and the back.
Edit: flashed O2 ROM (I9100XWKDD_I9100XXKDH_I9100O2UKD1) and same error during install and in Recovery. CSC menu only shows XEU, it should show O2 CSC.
Now flashing the XEU ROM for what must be the 20th time today
SOLVED
Fixed it
Found this thread in the SGS forum from where I downloaded the XEU CSC files.
In adb shell noticed the files I downloaded above were already there but in the wrong folder.
Files were in ./system/csc
Files should be in ./system/csc/XEU/system/csc
I don't know why files were copied in the wrong folders and if I flash the ROM will it happend again. If / when I do I'll update here.
The original files are in a RO filesystem. My linux mounting skills being weak I installed Root Explorer and extracted the XEU folder (downloaded from thread linked above) to ./system/csc.
Deleted the original files which were already there (listed below for anyone else with the same problem) and then via Dialer entered code *#272*imei#. Success, CSC XEU was displayed, selected, installed and phone hard reset. Upon reboot bootloader showed XEU installed successfully.
Code:
/system/CSCVersion.txt
/system/CSCFiles.txt
/system/SW_Configuration.xml
/system/csc/feature.xml
/system/csc/sales_code.dat
/system/csc/contents.db
/system/csc/customer.xml
/system/csc/others.xml
Edit:/ The fix wasn't permanent Reflashed the ROM and same error which is strange. If there is some thing wrong with ROM then others should have the same error. It can't be my phone.
Have you looked inside CSCVersion.txt? There's a whole bunch of paths for files. I think it would be wiser to edit it rather than delete it entirely and replace it with the one you suggest.
I checked the paths in CSCVersion.txt to see where the files should be. First time I did delete the originals and copy the downloaded XEU folder.
The second time I moved the original files.
If I can around to it again I'll rename the patch in CSCVersion.txt and see if that helps. Thanks for the tip.
I flashed the FW released today and back to the same error. As far as I can tell it doesn't affect phone in any way. Just no options to choose another CSC. It's stuck on XEU which is OK as I'm in the UK.
Still no correction to this ?
O get this error with the XEU KE7.
SOLUTION
I have found a solution...
I had the problem myself with can not acces to /system/csc/VAU/system/
Download "Root Explorer" and Install
Make sure you go to the main folder (not sd cards)
click "system" then "csc"
The file system in there is Read/Only, so you must make it Read/Write by clicking the Mount R/W, it will become Mount R/O.
Now press the menu button and click "New Folder"
Make the a folder you need, Which in your case's it is "SEK" or "XEU" then in that folder make another one called "system"
All those folders are case sensitive i think... just do it in case.
Now... On all 3 folders (csc, SEK/XEU, & system) touch & hold the folder till "options" appears, then click "permissions"
and tick all boxes.
Abracadabra, hey presto... The problem will be gone now!
.......I'm not entirely sure why this problem is out there or what it does as the folders seem to stay empty, but it WILL fix your problem. I am only new to android but i love problem solving
----Not sure if permanent or not but easy as..
Hope this helps...
PrinceWicked69
PrinceWicked69...Just logged in to thank you for your solution & say that you are the BEST!!!
Wish i would of saw this ealier, has the same ish issue with getting back to H3G.
Error very like your own.
Factory reset didnt fix it for me either, i tryed setting full write access on the csc folder (i didnt create the folders needed)
In the end the thing that fixed it for me was formatting the /system part which isnt normally wiped, error still appeard but i was then back on the correct region code.
When i just changed it using a csc file, it showed on my phone but when plugged into kies still was showing up as kor.
I have no Imei, No baseband, No reception (obviously)
ive been running cognition 1.51
and have downloaded csc selecter or something similer (that never worked) but i think that may be the issue when i opened it..
But i was wondering if there is a fix for this yet? or if someone can help me with resoring my phone to factory including the format of the efs folder?
ive searched for help about this, but noone has seemed to come up with a solution..
any help would be greatly appreciated
FIXED
cantelog said:
1st off i have a macbook running OSX 10.6.8
i take no responsibility for any bricking
make a backup of efs
NOTE: - Buy Root Explorer
- You have to have root!
- You HAVE to Have SUPERUSER installed
- USB debugging ON on your Phone (Settings>Applications>Development)
- Google is your friend and so am i
-- INSTALL SDK
1. Downloaded the android SDK http://developer.android.com/sdk/index.html
2. unzip the SDK and changed the folder name from "android-sdk-mac_x86" to something simple "android"
3. drop the folder into Applications
4. open up terminal and copy "export PATH=$PATH:/Applications/Android/platform-tools/" WITHOUT THE "
(now you have SDK INSTALLED)
-- THE FIX
1. plug in your phone
2. open Terminal, and open Superuser app on your phone
- NOTE: when you write "su" into Terminal, accept on the superuser app.
In Terminal Write -
adb shell
su
cp -r /efs /sdcard
3. Mount your Sdcard
4. copy and save a backup of the folder efs
5. download hexedit for mac
6. open Hexedit and open NV_data.bin, search for i9100
-should be something like "XX 1.500XSAGT-I9100XXXXSAXXXXXXXX"
7. change the RED codes to your CSC country code and save
here are some country codes
8. open /IMEI/mps_code.dat in Hexedit
- change the Code for your country code aswell and save
9. unmount Sdcard
10. MAKE SURE U HAVE A BACKUP OF EFS
11. Goto Root Explorer and copy contents of sdcard/efs to efs/
12. reboot
13. Yippee
Click to expand...
Click to collapse
Did you back up your efs folder?
Sent from my GT-I9100 using xda premium
cantelog said:
I have no Imei, No baseband, No reception (obviously)
ive been running cognition 1.51
and have downloaded csc selecter or something similer (that never worked) but i think that may be the issue when i opened it..
But i was wondering if there is a fix for this yet? or if someone can help me with resoring my phone to factory including the format of the efs folder?
ive searched for help about this, but noone has seemed to come up with a solution..
any help would be greatly appreciated
Click to expand...
Click to collapse
Just reflash modem.
If you didn't back up your efs folder, you might be out of luck. Try flashing the stock firmware for your provider and see if that helps.
Sent from my GT-I9100
all the flashing i have done over the past year with my sgs i9000 and now sgs2 i9100 i have never seen anything todo with efs.
so no i havnt backed up that folder, that cant be the only way to fix this?
i have looked in my efs folder and there is some files with .bak in them so im thinking some of the roms ive flashed in the past may have done a backup or something?
cantelog said:
all the flashing i have done over the past year with my sgs i9000 and now sgs2 i9100 i have never seen anything todo with efs.
so no i havnt backed up that folder, that cant be the only way to fix this?
i have looked in my efs folder and there is some files with .bak in them so im thinking some of the roms ive flashed in the past may have done a backup or something?
Click to expand...
Click to collapse
If you are missing baseband, there can't be imei either so flashing modem should restore it.
Happened to me a couple of times.
Daagen said:
Just reflash modem.
Click to expand...
Click to collapse
ill do that now
cantelog said:
ill do that now
Click to expand...
Click to collapse
ive just reflashed the modem KH3 and still
NO IMEI
Baseband Unknown
WTF
cantelog said:
ive just reflashed the modem KH3 and still
NO IMEI
Baseband Unknown
WTF
Click to expand...
Click to collapse
It means you still dont have modem for some reason.
If you have flashed new kernels recently, go back to kernel which worked and then reflash modem.
Daagen said:
It means you still dont have modem for some reason.
If you have flashed new kernels recently, go back to kernel which worked and then reflash modem.
Click to expand...
Click to collapse
Im going to flash stock KH3 Kernel, Rom and Modem
because that worked for me in the past
do you recommend i re partition from odin? (could it help/hurt?)
No need for repartition.
Daagen said:
No need for repartition.
Click to expand...
Click to collapse
I flashed Stock kernel KH3, Stock Rom KH3, and Stock Modem KH3, Still have NO Baseband still NO IMEI and still NO Reception. aarrgghh
djnoicatse said:
If you didn't back up your efs folder, you might be out of luck. Try flashing the stock firmware for your provider and see if that helps.
Sent from my GT-I9100
Click to expand...
Click to collapse
Telstra Firmware for I9100 isnt available at samfirmware.com yet, so i cant flash that Branded Rom
cantelog said:
Telstra Firmware for I9100 isnt available at samfirmware.com yet, so i cant flash that Branded Rom
Click to expand...
Click to collapse
When you changed CSC, Your IMEI got corrupted. Only way to restore is efs back up or reverting back to original firmware. This should work ...
If not , You may try this one , http://forum.xda-developers.com/showthread.php?t=837239
I was able to solve it using this method. You need to be rooted to do this ...
This will void your warranty ... so be careful.
I would definitely not recommend using a i9000 method of getting the baseband, imei back on a i9100.
The EFS folder contains critical files for the IMEI, Baseband, serial number of the phone etc.
Check in the Q&A threads and in here someone else also had the same issue and they managed to resurrect their phone with some developer support.
Good luck, only other option is a repair job and just say kies crashed through the firmware update and now the phone doesn't boot.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Virtualsk said:
When you changed CSC, Your IMEI got corrupted. Only way to restore is efs back up or reverting back to original firmware. This should work ...
If not , You may try this one , http://forum.xda-developers.com/showthread.php?t=837239
I was able to solve it using this method. You need to be rooted to do this ...
This will void your warranty ... so be careful.
Click to expand...
Click to collapse
FIXED
Thankyou for putting me in the right direction Virtualsk
if you arent using a pit file dont touch the re-partion box or your will screw your phone completely and dont tick the EFS box either although now that doesnt matter as its already to late.
1st off i have a macbook running OSX 10.6.8
i take no responsibility for any bricking
make a backup of efs
NOTE: - Buy Root Explorer
- You have to have root!
- You HAVE to Have SUPERUSER installed
- USB debugging ON on your Phone (Settings>Applications>Development)
- Google is your friend and so am i
-- INSTALL SDK
1. Downloaded the android SDK http://developer.android.com/sdk/index.html
2. unzip the SDK and changed the folder name from "android-sdk-mac_x86" to something simple "android"
3. drop the folder into Applications
4. open up terminal and copy "export PATH=$PATH:/Applications/Android/platform-tools/" WITHOUT THE "
(now you have SDK INSTALLED)
-- THE FIX
1. plug in your phone
2. open Terminal, and open Superuser app on your phone
- NOTE: when you write "su" into Terminal, accept on the superuser app.
In Terminal Write -
adb shell
su
cp -r /efs /sdcard
3. Mount your Sdcard
4. copy and save a backup of the folder efs
5. download hexedit for mac
6. open Hexedit and open NV_data.bin, search for i9100
-should be something like "XX 1.500 XSA GT-I9100XXX XSA XXXXXXXX"
7. change the XSA codes to your CSC country code and save.
here are some country codes
8. open /IMEI/mps_code.dat in Hexedit
- change the Code for your country code aswell and save
9. unmount Sdcard
10. MAKE SURE U HAVE A BACKUP OF EFS
11. Goto Root Explorer and copy contents of sdcard/efs to efs/
12. reboot
13. Yippee
I was trying to make a call, the person on the other side could not hear me. I reboot and...lost my baseband. Checked IMEI, it was also missing. Tried the solution above, but when I get to the below command:
cp -r /efs /sdcard
I get the message: "-r /efs /sdcard: not found"
I'm using Windows 7, BTW.
Please, please help.
Thanks.
After 2 days and a lot of head scratching i've managed to finally get my phone back after a random corruption of my /efs folder... heres what i did:
the important part: you need to be able to access /efs with root explorer etc. and check the 2 files; .nv_data.bak & .nv_data.bak.md5
in order for this to work, these backups must be dated earlier than their .bin counterparts... in my instance, the .bins were modified sep 14th 2011 @ 09:45am (the time i rebooted the phone when i noticed i had no signal and the corruption occured), but my .bak files were both dated dec 31st 2010...
in adb shell, i ran
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
i then downloaded 7-zip, used it to open the .tar file
i deleted the corrupt files;
nv_data.bin
nv_data.bin.md5
i then renamed;
.nv_data.bak > nv_data.bin
.nv_data.bak.md5 > nv_data.bin.md5
after closing and saving the changes, i then went back to adb shell and ran
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/efs-backup.tar.gz -C /
reboot
and voila! i was prompted to select my network provider, check status and all my IMEI, IMEI SV and other info was back to normal!
hope this helps someone out there, as i had a hard 2 days trying all sorts of different methods to get this working and was getting to the point of giving up...
good luck
Dickie.
Original post
right, i've been banging my head against the proverbial brick wall all morning over this... this is the score;
This morning i had no signal - 0 bars with a little x from memory
i switched it into flight mode, thinking when i brought it out it might reconnect
when i entered the power menu again, the flight mode button was greyed out (but it said it was switched on), also 'Call' in settings is greyed out, 'flight mode' is UNticked in 'wireless and networks', and trying to enable bluetooth returns an 'In flight mode' message...
reboots, cache/dalvik/full wipes, reflash of rom, flash of stock from odin inc. modem etc all do nothing...
In settings>about phone>status i am missing a lot of info, including phone number, network type and IMEI/IMEI SV...
i can enable wifi, and i downloaded an airplane mode toggle widget, which re-enables 'call' settings, bluetooth, and replaces the aiplane symbol with a circle with a cross through it...
I'm pretty stuck at this point and all i can think is that perhaps the EFS has become corrupt... anyone got any ideas?? all suggestions appreciated... in the mean time i'm going to look into the EFS stuff which i have no idea about yet lol
cheers,
Dickie.
Click to expand...
Click to collapse
yes you have corrupted /wiped your EFS or IMEI ,
If you backed up your EFS its not a problem just restore .
Plenty of restore EFS posts around broken IMEI etc .
jje
I'm looking in the EFS folder now, all seems to be present, but i am missing my IMEI (*#06#)...
not sure how this has happened, not done anything recently... very strange... but it does seem to be specifically the IMEI as my macs etc all all there and ok...
not backed it up so i'll see if theres a way around it :/
Cheers,
Dickie.
This happened to me 3 days back. Was sure I needed to send it in for service (reflashed and everything without avail) but then someone mentioned the EFS folder corruption issue.
Thankfully, I bumped into Rawat's thread a few weeks prior, and promptly backed up my EFS then.
It only took about 3 minutes in the terminal to fix the problem afterwards, no pc needed.
No EFS backup would usually mean a trip to Samsung service.
I got the same problem sice yesterday... tried all with the help of some guys here but nothing helped!
@eiraku: Do you like to explain me how you fixed the issue in the terminal, because my was /efs folder was also backed up but overwriting doesn't helped
ive just realised, my nv_data.bin & nv_data.bin.md5 have todays date in root explorer, i'm guessing thats a last modified date and that happend during the time in f*cked up, but the nv_data.bak & nv_data.bak.md5 are dated 31 dec 2010...
does this mean all i have to do is rename those backups and all should be sweet???
cheers,
Dickie.
dickie2007 said:
ive just realised, my nv_data.bin & nv_data.bin.md5 have todays date in root explorer, i'm guessing thats a last modified date and that happend during the time in f*cked up, but the nv_data.bak & nv_data.bak.md5 are dated 31 dec 2010...
does this mean all i have to do is rename those backups and all should be sweet???
cheers,
Dickie.
Click to expand...
Click to collapse
Sounds hopeful.
I'd suggest you take a copy of those backups & put them on an external device before renaming anything.
i took 2 backups of the entire /efs folder, then renamed the bak files to bin, but i'm having trouble copying or pushing them to /efs...
anyone know how to mount it as r/w, i cant through root explorer and not sure via adb
any help appreciated...
Dickie.
---------- Post added at 06:24 PM ---------- Previous post was at 05:40 PM ----------
ok, i have tried the following:
busybox umount /efs
busybox mount -o rw -t ext4 /dev/block/mmcblk0p1 /efs
busybox mv /efs/.nv_data.bak /efs/nv_data.bin
busybox mv /efs/.nv_data.bak.md5 /efs/nv_data.bin.md5
then when i check with root explorer all appears correct with the baks gone and the bins dated 31 dec, but upon rebooting its all gone back to the way it was before...
again, anyone got any ideas??
Dickie
Did you found a solution? I'm thinking about going to a service center
i'm trying to work out how to get the damn /efs folder to remain r/w...
everytime i change the files, moments later its reverted to what it was...
just trying a different insecure kernel to see if that helps... even sometimes whilst i'm deleting/renaming the files it suddenly becomes read only again...
really wish someone who knew how to make either an update.zip or an Odin flashable tar could do so with my renamed .bak backup files to overwrite the original bin files...
Dickie
happened to me but the problem solved in a couple of hour without doing nothing
tried making an update.zip but i get a status 6 error... stuck again...
could anyone take a look at this for me?? ive been on this almost 18hours and im tired and need to sleep...
again, any help appreciated!
Dickie
This happened to me whenever my phone restarted after cleaning the battery stats with Battery Calibration app (by NEMA) from App Market. At first, I restored my nv_data.bin file that was backed up (efs backup), but it continued to have same problems for next few reboots...
BUT!
I believe I have a possible simple remedy for this problem:
1. Turn off phone.
2. Remove SIM.
3. Turn on phone.
4. Wait until phone fully boots. (my phone did not detect SIM card and had emergency mode available, showed normal information in About Phone options)
5. Turn off phone.
6. Re-insert SIM.
7. Turn on phone.
nk_blu said:
This happened to me whenever my phone restarted after cleaning the battery stats with Battery Calibration app (by NEMA) from App Market. At first, I restored my nv_data.bin file that was backed up (efs backup), but it continued to have same problems for next few reboots...
BUT!
I believe I have a possible simple remedy for this problem:
1. Turn off phone.
2. Remove SIM.
3. Turn on phone.
4. Wait until phone fully boots. (my phone did not detect SIM card and had emergency mode available, showed normal information in About Phone options)
5. Turn off phone.
6. Re-insert SIM.
7. Turn on phone.
Click to expand...
Click to collapse
thanks for the input but it made no difference...
i now what i need to do, i need to replace those bin files with the bak backup files... i just cant get it to stick after a reboot... its like i never did it...
cheers anyway bud
Dickie
http://forum.xda-developers.com/showthread.php?t=859914
Don't get rid of this ****ing efs corruption !!!
red103 said:
Don't get rid of this ****ing efs corruption !!!
Click to expand...
Click to collapse
using root explorer, look in /efs.
is there a difference in the dates between nv_data.bin and .nv_data.bak??
Dickie
It works !!!!!!!!!!
Thanks a lots dickie2007 !
Yesterday i updated kernel on Revo 2.7.1 via KitchenPro app (for infos from CFROOT_KI3.zip to CFROOT_KI3_v4_2.zip) everything seem fine but this morning no imei, no baseband...
I search a lot before finding your thread (i think this one should be sticky !)
Your procedure is clear & simple (and hoppefully work in my case).
Thanks again dickie2007
PS : It seem since the serie KI* there's a lot of similar problems (i saw many thread during my research this morning about this kind of trouble)
If u flash different carrier branded firmware in CSC & do not set it correctly,
u may find that u can't see ur IMEI via *#06#.
Don't worry. It is still there. This is my way to solve it.
(just several seconds and without efs backup)
1.edit carrier branded code in "/efs/imei/mps_code.dat" to meet what you flash.
Ex. My S2 is CWT in the beginning, so I flash a CWT CSC and edit the code to CWT
2.use *#06# to ensure if IMEI could be shown correctly
3.To double check, u can use *#272*imei#. If u can reset carrier branded code then it is done.
nokia8250 said:
If u flash different carrier branded firmware in CSC & do not set it correctly,
u may find that u can't see ur IMEI via *#06#.
Don't worry. It is still there. This is my way to solve it.
(just several seconds and without efs backup)
1.edit carrier branded code in "/efs/imei/mps_code.dat" to meet what you flash.
Ex. My S2 is CWT in the beginning, so I flash a CWT CSC and edit the code to CWT
2.use *#06# to ensure if IMEI could be shown correctly
3.To double check, u can use *#272*imei#. If u can reset carrier branded code then it is done.
Click to expand...
Click to collapse
Does this also work even if baseband is shown as unknown? I flashed a stock ROM with Odin and lost both baseband and IMEI. dickie2007's method didn't work but maybe yours would have...
Hello
I have a China Mobile galaxy gs3 i9308, and the imei no. was changed to 0000000000000/null because of rom flashing (I think).
Now I am not registered on the network, so I have to change the imei no. back.
I tried several tutorials online, but seems like they're only for the galaxy s.
I tried the 9 step guide but I can't find the .nv_data file in my efs folder.
Can anyone help me or point me in the right direction?
Thank you
http://www.youtube.com/watch?v=JqLK_2I-SBM
check may be it helps
vegeta1 said:
http://www.youtube.com/watch?v=JqLK_2I-SBM
check may be it helps
Click to expand...
Click to collapse
Thanks for the quick reply. But I followed the written version of the guide and it only works for galaxy s? Because in my nv_data.bin file there's no line 00188008 in hex editor.
this is the link to that thread: http://forum.xda-developers.com/showthread.php?t=881162
The video poster also said it only worked for galaxy s.
Any other ideas?
hey, I have the same problem, SGS3 with wrong imei 0049.... i lose my efs file, someone can help us?
You could try flashing stock rom, heard that this sometimes restores imei, not sure if it works on s3
Also, check if the rom or kernel you flashed created a eggs backup, some do
Sent via TCP/IP
Please help
i have the same problem i cant fix my imei, after flashing the phone it changed to 00499.. it made no backups and no nv_data.bin.bak
If the efs folder havent been backed up, what can i do? I tried changing the nv_data file like some tutorials here explain, but no luck(tried couple of times, it defently not compatible with my galaxy s3), i believe these tutorials are for erlier galaxies.
Please help!
Thank you
Sent from my GT-I9300 using xda app-developers app
Flashing a stock rom works then root again it worked for me using a UK 3 official rom
Sent from my GT-I9300 using xda premium
dazzztom said:
Flashing a stock rom works then root again it worked for me using a UK 3 official rom
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
it shouldn't work for restoring IMEI on the S3
tomniu said:
Hello
I have a China Mobile galaxy gs3 i9308, and the imei no. was changed to 0000000000000/null because of rom flashing (I think).
Now I am not registered on the network, so I have to change the imei no. back.
I tried several tutorials online, but seems like they're only for the galaxy s.
I tried the 9 step guide but I can't find the .nv_data file in my efs folder.
Can anyone help me or point me in the right direction?
Thank you
Click to expand...
Click to collapse
Try this : http://forum.xda-developers.com/showthread.php?t=1801997
Did you back up the efs folder before you flash your device?
I understood that imei numbers were hardwired into the phone. And changing them n having the equipment was illegal. This is what the networks use to bar your phone if it gets stolen.
Sent from my GT-I9300 using xda app-developers app
eddydo said:
Did you back up the efs folder before you flash your device?
Click to expand...
Click to collapse
I don't know about international S3 but here in USA IMEI is not located in EFS folder.
chris170569 said:
I understood that imei numbers were hardwired into the phone. And changing them n having the equipment was illegal. This is what the networks use to bar your phone if it gets stolen.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
This program was created not to spoof IMEI just to restore if you have problem with it.
How to restore your IMEI number on SGS3 (GT-i9300)
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
Links:
Restore IMEI on SGS2: http://forum.xda-developers.com/showthread.php?t=1264021
Download EFS PRO: http://forum.xda-developers.com/showthread.php?t=1308546
Download your original firmware using check fus downloader (http://forum.xda-developers.com/showthread.php?t=1032437&page=18)
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Good luck and let me know how it goes
Leahcim
do i have to delete the .nv_core.bak and the .nv_core.bak.md5
---------- Post added at 04:10 PM ---------- Previous post was at 04:04 PM ----------
and which nv_data file do i have to copy i got 7 of them
but if this will not fix my phone, can samsung fix it without replacing the motherboard
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
my imei change sudden when i try to unlock my phone with messing the efs folder but i didn't backup it :crying:so now i dont have network
i have managed to follow all your steps and managed to get my IMEI back.
when i pressed *#06# i was able to see a series of numbers so i guess i got it right.
but i am still not connected to any network. please help!!
leahcim_za said:
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
Links:
Restore IMEI on SGS2: http://forum.xda-developers.com/showthread.php?t=1264021
Download EFS PRO: http://forum.xda-developers.com/showthread.php?t=1308546
Download your original firmware using check fus downloader (http://forum.xda-developers.com/showthread.php?t=1032437&page=18)
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Good luck and let me know how it goes
Leahcim
Click to expand...
Click to collapse
IMEI restore on SGS 3 (GT-i9300)
ronaldshi said:
i have managed to follow all your steps and managed to get my IMEI back.
when i pressed *#06# i was able to see a series of numbers so i guess i got it right.
but i am still not connected to any network. please help!!
Click to expand...
Click to collapse
Hi there
You need YOUR IMEI number back (which is not 00000... or 0049...) it is the one under your battery.
If you followed all the steps, then it should have worked.
One extra thing that you can try is if you did not flash your original phone firmware (and you only flashed the original modem.bin file) then do this step first.
And then work through the 9 step process, ignoring the step where you flash your original firmware (because you will have already done it).
Good luck and let me know when it works
---------- Post added at 12:16 PM ---------- Previous post was at 12:10 PM ----------
lobird said:
but if this will not fix my phone, can samsung fix it without replacing the motherboard
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
my imei change sudden when i try to unlock my phone with messing the efs folder but i didn't backup it :crying:so now i dont have network
Click to expand...
Click to collapse
Hi there
Good news is that it will work - even if you did not back up your efs folder before you messed with it!
Give it a try and let me know when it is fixed.
Good luck
Procedure not work!
leahcim_za said:
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
Links:
Restore IMEI on SGS2: http://forum.xda-developers.com/showthread.php?t=1264021
Download EFS PRO: http://forum.xda-developers.com/showthread.php?t=1308546
Download your original firmware using check fus downloader (http://forum.xda-developers.com/showthread.php?t=1032437&page=18)
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Good luck and let me know how it goes
Leahcim
Click to expand...
Click to collapse
Thanks a lot for the advice regarding SG3 IMEI restoring, but this prosedure doesn't change IMEI !!!
EFS PRO actions was Ok.
Can you help me? Pleeeeeease.
P.S. I know original IMEI numbers
in step 2 you say efs but delete the folder, but when I do that I reboot and I get a message telling me the whole time the camera is null and void wi fi all the options, it is this?
pd. sorry for my English (I'm using google translate)
leahcim_za said:
Hi there
You need YOUR IMEI number back (which is not 00000... or 0049...) it is the one under your battery.
If you followed all the steps, then it should have worked.
One extra thing that you can try is if you did not flash your original phone firmware (and you only flashed the original modem.bin file) then do this step first.
And then work through the 9 step process, ignoring the step where you flash your original firmware (because you will have already done it).
Good luck and let me know when it works
Click to expand...
Click to collapse
I do not remember my previous version, only the update when I asked him to put kies, I can use this firmware?
I9300BVBLG2_I9300TMUBLG1_TMU
I just do not see the ". nv_data"
Bought and activated used phone 2 weeks ago. Phone worked fine thru Friday night. Woke up Saturday to find I could not connect to cell network. Call to carrier revealed my IMEI number does not match the number they have. Somehow my phone IMEI changed to 350000000000006. Internet search revealed many others with same problem. The main difference between their situations and mine is the fact that in almost all of their cases their phone was rooted and they flashed many different ROMS to their phones and something obviously went wrong. My phone is NOT rooted and I have not tried to modify anything. Simple as that. Went to bed working, woke up broken.
I have now researched this the last few days and have no clear answer. Is it possible to set my IMEI back to my correct, legal,clean and not blacklisted value? Any help is greatly appreciated.
My guess is without a backup of the original, you can't do anything about it. Best bet is probably return it to the store you got it from and get a refund/exchange.
Edit:
Fastest and safest bet would be refund/exchange.
Little research has shown other people had a similar issue. Check Nox to make sure the phone hasn't been rooted before, if it has, you know what happened. If it hasn't, chances are the phone was flagged as lost/stolen after being sold (if 2nd hand).
As for a fix, I found this:
http://forum.gsmhosting.com/vbb/f898/g925f-imei-350000000000006-a-2044425/
Recover corrupt IMEI (without prior EFS backup folder)
Items needed
Root Explorer
Efs folder (no need to have a backup of this prior to the disappearance of IMEI folder, but it has to be this folder on the phone)
Obviously having a rooted phone
Instructions
1- With the Root Explorer to back efs folder to the SD Card
2- For safety make a second copy of the folder to the PC
3- Once both copies made to proceed to erase the original EFS folder on your phone
4 Restart the phone
5- When you start the phone, it will automatically create a new folder EFS, Root Explorer to delete the files and nv_data.bin.md5 nv_data.bin found inside the new EFS folder.
6 Copy the folder from the SAI IMEI folder we saved on the SD card and stick it on the new EFS folder created in the root directory of your phone
7- Since the SAI folder we saved on the SD card .nv_data file copy, paste into the new folder EFS generated in the root directory and rename it nv_data.bin phone, then recopy again .nv_data file rename it nv_data.bin.bak
8- With Root Explorer /efs/nv_data.bin change the owner
9. Restart the phone
If all went well you should have recovered the IMEI can check if recovered by entering * # 06 # on the phone dialer.
Thanks for the response ProdigyThirteen.
The Knox is clean 0x0. Everything I have found says the original IMEI is clean and not flagged.
I will definitely look into the procedure you provided. It looks promising. I'll take any sign of hope I can get.
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Shaggydoo said:
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Click to expand...
Click to collapse
Copy the nv_data file from the SD card to the newly generated EFS folder on the phone and name it nv_data.bin. Then make another copy in the same EFS folder and name it nv_data.bin.bak.
Then you need to set the permissions for EFS folder/nv_data.bin file. They need to be set to rw-r-r. However for this procedure you need to be rooted.
Shaggydoo said:
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Click to expand...
Click to collapse
Could you tell me did it work?
No, unfortunately it did not work. After following all the steps again, the IMEI still comes up incorrect. The search continues ..........
Shaggydoo said:
No, unfortunately it did not work. After following all the steps again, the IMEI still comes up incorrect. The search continues ..........
Click to expand...
Click to collapse
Have you tried flashing the stock firmware again? Either by smart switch or odin?
Will try again tonight when I get home.
Callumbr1, No dice on the stock flash. I installed Smart Switch and tried to do the reinitialization. It gets along in the process and then fails in the " Device does not have DRK" error. Also have DM-verity error. I tried to find solution briefly but didn't get far. Ran out of time tonight. Will try again tomorrow. Still appreciate your help.
Shaggydoo said:
Callumbr1, No dice on the stock flash. I installed Smart Switch and tried to do the reinitialization. It gets along in the process and then fails in the " Device does not have DRK" error. Also have DM-verity error. I tried to find solution briefly but didn't get far. Ran out of time tonight. Will try again tomorrow. Still appreciate your help.
Click to expand...
Click to collapse
I remember I did have the exact DRK error on my s6 edge one and dm verity fail. The way I fixed it was by flashing stock firmware through Odin. Quote me when you try again and I'll do my best to help mate.
IMEI
If you want to get back your IMEI try Dashboard .
you will find all your devices there, then try to find a way to write your IMEI in your phone (may need root)
Dashboard (https://myaccount.google.com/dashboard?hl=en)