[Q] JM6 IMEI Change - Galaxy Tab Q&A, Help & Troubleshooting

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.

Related

Help! Restore BML3 / STL3

Hi all mates!
I have a problem with my i9000... I explain my problem fast:
I have extracted the BML3 and STL3 of my phone to 2 files .img... I have duplicated this files to a backup and I modified it. Now, I can´t load the original bml3.img and stl3.img because the /dev/block/stl3 doesn´t exists... not are mounted... also when I restart my phone, the /efs/ directory is empty, and the phone dont ask me for the pin... (obviously, I don´t have call service) but, If I copy the nv_data.bin to /EFS directory, the phone ask me for the pin and I can make and receive calls...
Do you have some idea to load the original stl3 & bml3 files in the phone????
-------------------
well, now I have put the bml3 and I reboot, all is ok, but when I try to put the stl3 and I obtain this message:
dd if=/sdcard/stl3.img of=/dev/block/stl3
/dev/block/stl3: cannot open for write: Invalid argument
but the stl3 partition exist! and I rooted the phone
ls /dev/block/stl*
/dev/block/stl1
/dev/block/stl10
/dev/block/stl11
/dev/block/stl12
/dev/block/stl2
/dev/block/stl3
/dev/block/stl4
/dev/block/stl5
/dev/block/stl6
/dev/block/stl7
/dev/block/stl8
/dev/block/stl9
all is done!!!
I had to reflash the phone after recover the bml3... Now all is OK but my IMEI... it has the famous 004999010640000 number but that is other history
awia said:
all is done!!!
I had to reflash the phone after recover the bml3... Now all is OK but my IMEI... it has the famous 004999010640000 number but that is other history
Click to expand...
Click to collapse
Simply make a Call from your Phone: +49 9901 0640000 xD
Aery said:
Simply make a Call from your Phone: +49 9901 0640000 xD
Click to expand...
Click to collapse
xDDDDDDDDD
Why in the Gods name you messed around EFS in that way?
If your IMEI is messed up, I recon so is your WIFI MAC and BT address too.
Richthofen said:
Why in the Gods name you messed around EFS in that way?
Click to expand...
Click to collapse
because I looking for restore my original IMEI number
the WIFI MAC and BT also are changed?? I don´t have any problem with the wifi... but I don´t tested the BT...
I don´t have the MAC of wifi and BT ............
but wifi works good....... at the moment!
surprise!
when I recovered the product code and I restarted the phone, it shows me the WIFI MAC !!!!
but the KIES reg continues showing me the XXXXXXXXXXXXXX product code...
awia said:
surprise!
when I recovered the product code and I restarted the phone, it shows me the WIFI MAC !!!!
but the KIES reg continues showing me the XXXXXXXXXXXXXX product code...
Click to expand...
Click to collapse
Do you try to copy the files nv_data.bin and nv_data.bin.md5 into /efs and then remove the battery without turning off the phone?
quiron said:
Do you try to copy the files nv_data.bin and nv_data.bin.md5 into /efs and then remove the battery without turning off the phone?
Click to expand...
Click to collapse
no........ I try it now
awia said:
no........ I try it now
Click to expand...
Click to collapse
any news about that?
quiron said:
any news about that?
Click to expand...
Click to collapse
The same result
i had a similar issue with my nv_data files. i backed them up to my computer, then copied a set of nv_data files over from my gf's phone, and it gave the same issue. when i copied my original ones back, it still wouldn't work. seems the signature of the file is changed, and the phone doesn't accept it. your phone has a set of backup nv_data files on the phone in the efs partition. delete your bad nv_data files, shut off your phone, and turn it back on. the phone should recognize the files are gone, and use the backup files......worked for me
edit: just to clarify, only delete the .bin and .md5 files, not the .bak files.
leave: nv_data.bak & nv_data.bak.md5
Hello,
I'm having the same problem but only have the bml3.bak and the nv_data.bak and nv_data.bak.md5.
I updated the firmware to JPH and make the changes to restore the product code to KOR from XEC the original for my country and operator.
The bml3 was corrupted and in the next reboot the phone didn't ask for the pin code of my SIM card.
I try to restore the original files, but the efs is empty or write protected, with root explorer a mount to r/w and only if I connected by usb the phone ask for the pin, and I can access to phone network and can make calls a recive it but the IMEI is the tipical 004999010640000.
The stl3 is imposible to read or write from it. The nv_data.bin can not be reinstalled because pin is not recognise and in a reboot the files are restore to previous state.
I think the nv_data are store somewhere and when the file system is mounted as r/w the efs directory is recovery from there.
Efs directory only has and .android directory, and nv_data.bin, nv_data.bin.md5, .nv_state. No imei directory, etc
awia you has some good news, i'm from spain to, it's possible to speak somewhere in spanish.
Do you recomend to take the phone to SAT?
I bought it in the Telefonica FlagShip Shop in Madrid.
Hello,
An update over my previous comments.
If I used rootexplorer to paste .nv_data.bak and .nv_data.bak.md5 that I backup before and then go to efs directory and mount r/w and immediately copy the previous pasted files, then the process start and ask for my pin, and then the imei is restored. The problem is that this is temporal and only works in the current session, if you reboot the phone then you must to make the same steps. I don't know if I can make a sh to do this step more automatically, because I don't know how and what rootexplorer remount in r/w permissions, may be someone can help me in this tasks.
In my previous comment I said that the pin prompt only has shown if the phone is usb plug in but this is not true, works in all conditions.
About the process, I suppose the bml3 contains all the information and in the bootload process this bml3 set the stl3 and mount over efs directory but for some reason this is not working with my phone because the changes over the bml3, I don't know how can I reestablished it. I use the redbend_ua for that and the bml3 are now like my backed-up one, but still doesn't work.

[Q] Need Help, how to get back .nv_data.bak.md5 & .nv_data.bak file in efs folder

help pls,
i have been wrongly delete the .nv_data.bak.md5 & .nv_data.bak file in efs folder without any backup done.
but i still have the file nv_data.bin.md5 & nv_data.bin in efs folder,
and i been Flash from DXJPA , to JPY , to JPU, to JVB , to JVE , to JV5.
what can i do to get back the .nv_data.bak.md5 & .nv_data.bak file in efs folder??
or can i just get the file from another phone and do some editing ??
y not 1 answer to me ?
can i just get the file from another phone??
just copy and paste it on my phone ??
what will happen if i do by this way ?
Ofc you can try.Here are the files. http://hotfile.com/dl/120562433/d70ac90/files.zip.html
thanks ,
This file is either removed due to copyright claim or is deleted by the uploader.
i have few friend use SGS phone, i can simple get the file from them ,
the problem is i don't know when will happen if i just copy the file from other SGS phone and paste it on my phone .
the imel number will changes to my friend imel number ?
I dont think your imei changes, but your product code might change. Imei is in "imei" folder.
Ps: Hotfile sucks I uploaded files by myself....
They're the backup files and it won't cause a problem that they're deleted. They should be recreated by rebooting your phone if not, just copy the original files and rename them.
You should definitely disregard previous advice in this thread.

[MIUI] IMEI restore from backup after the MIUI 6.1x update

This may help anyone who's IMEI got changed or perhaps even deleted by the MIUI MGC 6 or 6.11 update and perhaps even on further updates.
You need "Root Explorer" (or perhaps something similar) from the market and an backup of your original efs folder!
While the initial installation of MIUI there has been a backup folder created on your sd-card. In this folder there is the backup of your IMEI.
To restore your IMEI just copy "nv_data.bin" and "nv_data.bin.md5" files with root explorer to your original efs folder and replace the old files.
After that you must reboot. The IMEI should be restored now.
This worked for me, perhaps it may help you too!
Nice one
mosen5 said:
This may help anyone who's IMEI got changed or perhaps even deleted by the MIUI MGC 6 or 6.11 update and perhaps even on further updates.
You need "Root Explorer" (or perhaps something similar) from the market and an backup of your original efs folder!
While the initial installation of MIUI there has been a backup folder created on your sd-card. In this folder there is the backup of your IMEI.
To restore your IMEI just copy "nv_data.bin" and "nv_data.bin.md5" files with root explorer to your original efs folder and replace the old files.
After that you must reboot. The IMEI should be restored now.
This worked for me, perhaps it may help you too!
Click to expand...
Click to collapse
This didn't work. I also tried installing EZbase Froyo and the IMEI was still 004999010640000...
Is there a working solution for this yet???
Mosen5, you say to copy to original eds folder. But where is that? Also do I not copy IMEI folder as well (that is within the backup folder)
Its frustrating this as I reflashed this about 5 times now and still stuck with no service.
Updated: Never mind. I found that efs folder (didn't show up with ezexplorer I had used). Pasted those two files and.... it didn't work for me :-(
I even took set it as flight mode, sim out, etc.
I suspect its resetting those files back to what it was because if you try delete them, its back in again straight away. So, pasting those files, would mean it might get reset back to what it had in the first place.
Found a solution. Going along the lines of what mosen5 suggested, but have to use adb command.
Full details here: http://forum.xda-developers.com/showthread.php?t=859914
Important notes the author forget to say:
YOU HAVE TO SET THE PERMISSION ACCODINGLY TO THE OTHER FILES ALREADY PRESENT IN THE EFS FOLDER,otherwise it won't work
Thx

:( EFS folder empty = 12mb of 12 used! How to restore unzipped backup?

Hi all..
So Im pretty new at flashing androids, been using ubuntu for years and am quite familiar with the terminal as well as computers in general. I made the silly mistake of not doing a complete backup of my phone with CWM before flashing with CyanogenMod 9 and now my EFS folder is "empty" but still with Zero free space... giving the "usual" errors":
1) Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)
2) No Network and Signal ( calls, sms and mobile Internet not working)
3) No base Band or Unknown Baseband
4) Sim card lock missing
as described in the [A.I.O. Helpline] My Android Solutions.
CWM seems to have created a copy/paste backup of my EFS folder (not .zip and not .img, just a folder) on sdcard/efs/backup but the EFS folder is read only and root manager cant paste into it. I've read that deleting the EFS folder should recreate it, I tried in terminal with
Code:
rm -r /efs/*
and got the reply:
Code:
rm failed for /efs/lost+found, Directory not empty
How do I go about restoring the EFS folder?
Finally figured out how to copy/paste into the read only EFS folder! I have searched probably about a million threads, all say to "just copy paste" into the efs folder... but never how to do it when its locked because of read only permissions.
I think im one step closer.. but still not quite there yet.
The way to get write permissions is simply to open terminal and get root access and unmount the efs directory using:
Code:
umount /efs
After that, I could open the efs directory in Root explorer and mount it as R/W. Automatically, I get some default files there created by the system which I can delete and then I could copy/paste my backup into the efs directory. Bang, mobile network running, but baseband version is still unknown. Also, my IMEI number is the generic one, not my unique one
The problem now, is that on reboot my EFS directory goes blank again... anyone know how to continue from here?
Snarlster said:
The problem now, is that on reboot my EFS directory goes blank again... anyone know how to continue from here?
Click to expand...
Click to collapse
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
If it gets lost after reboot
Remedies for those who have a efs backup
If you Have a Backup and you want to restore it, this is one method Here or you can use the restore function in the app that you used to back it up
If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.
BUT try this method first
Copy Paste EFS folder with root explorer, after paste , power down phone and reboot into recovery and wipe cache before rebooting....this worked for some
xsenman said:
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
If it gets lost after reboot
Remedies for those who have a efs backup
If you Have a Backup and you want to restore it, this is one method Here or you can use the restore function in the app that you used to back it up
If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.
BUT try this method first
Copy Paste EFS folder with root explorer, after paste , power down phone and reboot into recovery and wipe cache before rebooting....this worked for some
Click to expand...
Click to collapse
Thank you, I had read each thread linking from those threads but it was good for me to do it again!
Flashing the EFS folder with Heimdall gave me the same results as copy/paste, setting the ownership/permissions made no difference in both cases, always empty on reboot.
FINALLY, these are the steps I took to get my phone "working".
1: Odin re-installed the stock I9000JVJV9_OJVJV9_JXJV6.tar file found on sammobile.com as well as the Pit file found on 4shared
2: This gave me an error on bootup... something about "failed to mount dbdata", this was solved with Odin as well by selecting only PDA and using the dbdata.rfs.tar found on hotfile.com.
After this, my phone booted up with the generic imei, a very welcomed change to the previous no imei thats been bothering me! Also, my baseband is showing, the EFS directory is full of files and google play is working... and fortunately, my carrier doesnt seem to care about the generic imei
I'm still going to get my imei back, but first things first! Its time to do some backing up!
Current plan is:
1: Install ClockworkMod
2: BACKUP
3: replace nv_data.bin with the backed up one.
4: reboot / see if my IMEI number is back.
5: BACKUP
6: install CyanogenMod
I hope this helpes someone down the road.. dont be shy on letting me know if my hours of pain helped you!
And... one more thing, my phone is Samsung Galaxy S GT-I9000
Thanks again for pointing me to the right direction
did you only used the PDA included on the I9000JVJV9_OJVJV9_JXJV6.tar file? and how did you use teh dbdata.rfs.tar? thanks.
efs Folder Contents
Hi Guys,
I am hoping you can help me with a problem.
I have a brand new GalaxyS2 i9100, which is on ICS 4.0.4 IMM76XWLPW - XXLQ6 Baseband version, Kernel 3.0.15-1056084 [email protected]#3(SMP PREEMPT Wed Aug 22 2:55:24 KST 2012). The phone is not rooted, but what I did was make a copy of my efs folder to my PC, obviously incorrectly, using My Phone Explorer.
I thought it was just a matter of uploading the folder to my PC and it could be used in an emergency, I thought it would just copy the folder.
What I have discovered, is that all the contents of the efs folder are now on my PC and the efs folder in my phone is empty!!!!
I am now unable to get the files, back into my phones storage.
When I enter *#06# into my phone, the IMEI number shows up and is correct.
I also have a copy of the original efs folder, on my External SD Card.
I have not changed anything else on the phone, other than removing the efs folder contents to my PC. Is there a way, to get all the contents back into my phones efs folder without having to "Root," using say....Emulator or something?
Would a "Hard Reset" on this unrooted stock phone, restore the efs folder to factory settings??
Thank You.
dixielee said:
Hi Guys,
I am hoping you can help me with a problem.
I have a brand new GalaxyS2 i9100, which is on ICS 4.0.4 IMM76XWLPW - XXLQ6 Baseband version, Kernel 3.0.15-1056084 [email protected]#3(SMP PREEMPT Wed Aug 22 2:55:24 KST 2012). The phone is not rooted, but what I did was make a copy of my efs folder to my PC, obviously incorrectly, using My Phone Explorer.
I thought it was just a matter of uploading the folder to my PC and it could be used in an emergency, I thought it would just copy the folder.
What I have discovered, is that all the contents of the efs folder are now on my PC and the efs folder in my phone is empty!!!!
I am now unable to get the files, back into my phones storage.
When I enter *#06# into my phone, the IMEI number shows up and is correct.
I also have a copy of the original efs folder, on my External SD Card.
I have not changed anything else on the phone, other than removing the efs folder contents to my PC. Is there a way, to get all the contents back into my phones efs folder without having to "Root," using say....Emulator or something?
Would a "Hard Reset" on this unrooted stock phone, restore the efs folder to factory settings??
Thank You.
Click to expand...
Click to collapse
I would be careful with that, if you have your efs folder on your sd card, I think it would be better to copy/paste them with root explorer back before reboot... though this is just a guess. In any case, since you have the folder on your PC, then at least you have the backup you need if you get into serious trouble.
If it did reset, please tell us about it in case someone else needs this info later
efs file restore
Thank you so much. After days of not having calling and texting functions available from a corrupted efs folder, who would have thought that a simple copy and paste of the backed up efs to the system would help greatly?
Hey, this worked for me, but I still can't connect to some carriers.

[Q] nv files in the EFS folder/partition

Hello everyone,
N7000, rooted, on stock 4.1.2
In my EFS folder (which is already backed up), I find nv_data.bin, nv_data.bak and nv_core.bak, alongwith their corresponding md5 files.
The only problem with my phone is a dead gps. After much googling and trying out different hardware/software solutions, I am convinced the nv_data file might be the cause.
I compared the nv_data.bin and nv_data.bak files (both 2mb each) on a windows machine and find a lot of differences. Also, the .bak is dated 01/01/2012, while the .bin carries the current date.
So, would it be safe to try out the .bak file by renaming it to nv_data.bin? I can always go back to the original, right?
Also, the 3rd file I mentioned, nv_core.bay (also dated 01/01/2012) is just 1 mb in size. What exactly is its purpose?
Thanks for any advice, I'm very eager to get the gps working and I love my phone!

Categories

Resources