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.
Hi guys. I have problem. So i have my efs folder backuped. It contains following files
Code:
imei
-> bt.txt(23 bytes)
-> mps_code.dat(3 bytes)
nv.log(87,2kb)
nv_data.bin(1 697kb)
nv_data.bin.md5(32 bytes)
nv_datadel.bin(2 048 kb)
So i copied this to efs folder on my phone with root explorer. Rebooted phone and nv_data.bin changed to 2mb and i still have wrong IMEI
So guys. What is the solution?
Could someone help? Or know way how to prepere efs folder that would have my imei? I can provide pictures of my imei printed on my galaxy s box to proof that i'm not lying.
@EDIT
I forgot to mention that i have some clockwork backups. Do they contain imei backup?
if it was a nandroid backup then yes it will contain the imei
when you are using root explorer have you mounted system RW ??
if so and you still cant get it back, flash back to a froyo rom and it will be restored
Flashing Froyo helped. Thank you.
Close this topic
GSII_Repair is this safe to use with my sgs as i have meesed up my imei when flashing ics will this bring back my imei and allow me to make calls in
Sounds like GSII is for galaxy S 2... I think the repair for broken imei is to flash a stock rom
Yes the repair for the IMEI is to either flash a stock rom.
Alternatively use your backup to copy the .nv_data.bin & the .nv_data.bin.md5 files from your backup efs folder and overwrite the current ones in your efs folder. If you do this also delete the nv.log, .nv_data.bak & .nv_data.bak.md5.
can anyone upload .qcn file for D410 plz
i can guide you through all process & dont worry about your imei you can upload file without imei
pm me if you are interested
required software
qpst
https://code.google.com/p/mydownloadsection/downloads/detail?name=QPST.2.7.374.rar&can=2&q=
ultra editor
http://www.ultraedit.com/downloads.html
imei converter
https://drive.google.com/file/d/0B-GozWsZJNF_aXJwTnBZMWRKZEk/view?usp=sharing
Hello friend, you could do uploads correctly? In .qcn file contains the IMEI information?
Guide me steps to fix 2nd Imei for lg d410/ as full partition are deleted and recreated .So lost imei .any how got first Imei .plz help to fix other
this is 'persist" partition for x00td device only after flashing this by twrp/orangefox recovery or use
(Partitions Backup & Restore App) in your rooted device
. you have to flash "persist.emmc.win" by using recovery (or use Partitions Backup & Restore App)
after that "root" your device and use "root explorer" and go to persist folder and edit "sn.bin" file and change the serial number as same as back side of yours phone device. and change sn.bin file permitions rw-r-r-
then install a fastboot firmware and you willl see your real model and serial number...
also i m putting a "sn" and "flag" file for "x00t" device users too( for x00t device users only) and you can't flash it by using recovery just replace folders into your device by inside "persist folder" using "root explore" and repalce them and change permitions rw-r-r-
and after that flash fastboot firware and it will fix your model and serial number.
In "sn.bin" file "HB84RK842267VT04B62" don't change this number its mean "xootd"
In "sn.bin" file "HB86KE92196WWR06RDY" means "x00t" (don't change it)
after these number you will see 16 digit number starting with "J---------------" something like this change it to your real serial number by using root explorer editor which is in back side of your phone
if i don't have back serial number or box ?
sabh123 said:
In "sn.bin" file "HB84RK842267VT04B62" don't change this number its mean "xootd"
In "sn.bin" file "HB86KE92196WWR06RDY" means "x00t" (don't change it)
after these number you will see 16 digit number starting with "J---------------" something like this change it to your real serial number by using root explorer editor which is in back side of your phone
Click to expand...
Click to collapse
Bro I have different codes, HB849J84215Z2X041CPJ4AAB76085156LX
After I installed Corvus os 17 a11(which was unstable(but didn't mentioned) and so they pulled it out from website right now) idk how but at start it was working just fine. Is it different as after this rom it shows device name as ASUS_XOOTDA.
sabh123 said:
this is 'persist" partition for x00td device only after flashing this by twrp/orangefox recovery or use
(Partitions Backup & Restore App) in your rooted device
. you have to flash "persist.emmc.win" by using recovery (or use Partitions Backup & Restore App)
after that "root" your device and use "root explorer" and go to persist folder and edit "sn.bin" file and change the serial number as same as back side of yours phone device. and change sn.bin file permitions rw-r-r-
then install a fastboot firmware and you willl see your real model and serial number...
also i m putting a "sn" and "flag" file for "x00t" device users too( for x00t device users only) and you can't flash it by using recovery just replace folders into your device by inside "persist folder" using "root explore" and repalce them and change permitions rw-r-r-
and after that flash fastboot firware and it will fix your model and serial number.
Click to expand...
Click to collapse
ok so i took the .sn.bin from x00t.zip, changed the device code to the one you provided for X00TD and entered my serialnumber, then moved the file to /persist. didn't fix sn unfortunately.
my questions are:
- do i have to copy "flag", too, and is that safe/do i have to change anything? (since it's for X00T)
- how can i alternatively flash persist.emmc.win? appears to me that it needs to be *.img format
i'm also a bit confused about the state of my persist partition. Cx File Explorer displays it and the contents (but doesn't offer changing permissions), 2 other Explorers didn't display /persist (although in one it was displayed like a file). tried changing permission with one Explorer before moving it with Cx, but gets stuck during changing permissions.
Btw, my only problem is slow mobile internet (edge) and i think that's due to C4ATAS000000 serial. IMEI were gone before, too, but have been able to fix that.
Interkonekt said:
ok so i took the .sn.bin from x00t.zip, changed the device code to the one you provided for X00TD and entered my serialnumber, then moved the file to /persist. didn't fix sn unfortunately.
my questions are:
- do i have to copy "flag", too, and is that safe/do i have to change anything? (since it's for X00T)
- how can i alternatively flash persist.emmc.win? appears to me that it needs to be *.img format
i'm also a bit confused about the state of my persist partition. Cx File Explorer displays it and the contents (but doesn't offer changing permissions), 2 other Explorers didn't display /persist (although in one it was displayed like a file). tried changing permission with one Explorer before moving it with Cx, but gets stuck during changing permissions.
Btw, my only problem is slow mobile internet (edge) and i think that's due to C4ATAS000000 serial. IMEI were gone before, too, but have been able to fix that.
Click to expand...
Click to collapse
did you fix this? i managed to change the serial number and fix imei but still only 3g network. I see the LTE icon but no signal
MairaFA said:
did you fix this? i managed to change the serial number and fix imei but still only 3g network. I see the LTE icon but no signal
Click to expand...
Click to collapse
i haven't been able to fix it. wanted to revert to stock (supposedly in Android 8 serial change is possible), but made a stupid mistake and bricked my device.