Database Develop

[Q] FIX Device ID: How?

Thanks to the good folks here i've just upgraded my Galaxy S to the leaked JPM firmware. So far so good - much faster than JPK I was on.
However - I'm having problems with the Appbrain Fast Web Installer and seem to have found out that it's due to the android device ID being the same because we're all using the same ROM (or something) (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=798644)
So.... How can I find out what my Device ID was/should be and how can I then change it to be "correct".
Any help much appreciated. Seems it might be a common issue....

Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...

nonreviad said:
Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...
Click to expand...
Click to collapse
Thanks for info - checked my IMEI and it seems to be fine - i.e. the one i registered with my insurance with (starts 3547)
I've read the thread you linked to trying to figure out what's what but I can't see anywhere how to find out what my product code is/was/should be or how I can change it. I've seen stuff about backing stuff up (nv_data?) but I'm not aware of having changed these.
All I've done to my phone - flashed JMX and now JPM and applied SuperOneClickv1.4-ShortFuse root. Will that have changed my product code?
I'm a bit lost with this one.

Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App

DamianGto said:
Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
A bit of info that might help(?):
I loaded up SGS toolbox and pressed ""check product code" it says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
I'm guessing that's bad news?!
Under Firmware Info it says:
------------------------------
PDA: I9000XXJPM
PHONE: I9000XXJPM
CSC: I9000OXAJPM
Build Info: 2010. 10
--------------------------------------
When I tap CSC selection it says: "USSD code running" and then "UNKNOWN APPLICATION"
When you say to backup 2 original files - i'm guessing it looks like I don't have those. Is there another way I can check or is it definite from the above. If I don't have the original files am I stuck? Can I get them from anywhere else? Are they default to a phone by region or carrier (my phone is from O2 in the UK and is the 8gb version)
If you say delete the original files (which aren't there it seems) - am I right in thinking this will them make the phone auto-generate new ones? (I really have no idea what these files are for or what they do).
What's the next thing to try? Can I get hold of the missing files from somewhere? Do I even need them? And how do I restore the Product ID (if it's changed!)?
Thanks

Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App

DamianGto said:
Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks

Maybe I am not following this thread correctly, but your last post deals with IMEI and unlock data. Your first post said you needed to change your deviceID. You even link to the Captivate thread that discusses the problem AND in that captivate thread is a link to change Device ID - http://forum.xda-developers.com/showpost.php?p=8604909&postcount=3550
review that post as it tells you where your device ID is located (it is not in the nv_data.bin file). Also, in the captivate thread, one person said he just made one up and that worked for him.
If you mess up with nv_data.bin you will mess up your IMEI and any unlock the phone has - so I caution you be careful.

I made a thread with the solution
http://forum.xda-developers.com/showthread.php?t=815503
This should work.

alsheron said:
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks
Click to expand...
Click to collapse
I had the same problem.
I installed Busybox from the App Market and it solved the problem.

abumuqaatil said:
I had the same problem.
I installed Busybox from the App Market and it solved the problem.
Click to expand...
Click to collapse
thanks...had same problem and that solved it

[Q] I think I deleted the contents of my /efs folder. Help!!!!

Hi all,
I recently upgraded to JPM version of froyo, and wanted to change back the product code to the original. After restoring from the .bak files, I got back the original product codes. However, while copying to another location for backup, I deleted the contents of the /efs folder by mistake (atleast I think I did).
The /efs folder is empty, but the phone still works fine. Haven't rebooted the phone for fear of bricking it. Is there a way to recover deleted files? Or are those files just hidden from view?
Someone please help
Update:
Managed to get of copy of nv_data.bin from a folder used by sgstoolbox. Rebooted the phone and phone works fine. Checked the folder contents, has nv_data.bin, nv_data.bin.md5, .nv_state and a folder named .android. Is there anything else which should be there? How to restore?

Do you have a backup of your /efs folder?

Woah same happened to me just some Hours ago !
If you used SGS Toolbox to check, you are lucky because it automatically creates a backup.
-> I think SUFBS Explorer deleted the efs because i am sure i checked "copy" ... anyway !
If you have any backup file, you are lucky.
One question by the way:
I´ve also lost the "IMEI" Folder, but my IMEI is still correct. Is that because ne nv_bin is just enough for the system checks ?
EDIT: Go and check with SGS Toolbox, if it displays your code, it is still there + it creates a backup file on your sdcard (you should double-check that anyway)

I'd say that the best and easiest way of restoring your product code is by using this: http://forum.xda-developers.com/showthread.php?t=787163
messing around with /efs folder is not a good idea, especially if you don't have a back up.

Just remembered that I have a titanium batch backup of system + apps taken a while ago when I was on stock firmware. Any way to restore the /efs folder from that? The shock of losing the /efs folder was enough to jolt me out of a beer induced haze ;-)
The phone still works, which is good news. But anyway to restore from Titanium backup?

fullerms said:
Just remembered that I have a titanium batch backup of system + apps taken a while ago when I was on stock firmware. Any way to restore the /efs folder from that? The shock of losing the /efs folder was enough to jolt me out of a beer induced haze ;-)
The phone still works, which is good news. But anyway to restore from Titanium backup?
Click to expand...
Click to collapse
Titanium does not backup /efs.. If you don't have a backup, you're basically screwed! Sorry to be the bearer of bad news

Like I said, the phone works fine after I restored the nv_data.bin file. I listed the files which were rebuilt by the system. Is there anything else missing? Can someone post a screen shot of the contents of your efs folder?
Sent from my GT-I9000 using XDA App

fullerms said:
Like I said, the phone works fine after I restored the nv_data.bin file. I listed the files which were rebuilt by the system. Is there anything else missing? Can someone post a screen shot of the contents of your efs folder?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Oh, so you DID have a backup? Nice! Besides what you lited in the first post, there are the following things:
.imei (file)
imei (folder)
- .nvmac.info
- bt.txt
- mps_code.dat

Any idea what those files are for? Possible to check what they contain?
Sent from my GT-I9000 using XDA App

Like i said, my imei folder was deleted aswell...
No problems so far with that !

Use rootexplorer, dont use ASTRO. It's crap and does not show all files, including the whole /efs

My EFS folder is empty too...and I don't know why, I have only flashed a couple of time with odin and JM9....
But SGS Toolbox report my csc correctly as ITV....even if I used the HUI csc from my operator with odin....
Could it be a problem if the efs folder is empty? The phone is working well...the only problem is that it loses very often the wifi connection...but I don't think that it is csc related...

[Q] imei problem in ROM][IMM76I][4.0.4][AOSP] ICS333 RC4

hello,
i flashed ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 from GB 2.3.5 AND my imei disapeard.
i flashed back to stock rom and the celular service worked .
then i flashed back to ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 and now i have a imie and everything works fine execpt of the face that the imei is not the one listed on the phone (behind the battery. is that o.k ?

shmhazan said:
hello,
i flashed ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 from GB 2.3.5 AND my imei disapeard.
i flashed back to stock rom and the celular service worked .
then i flashed back to ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 and now i have a imie and everything works fine execpt of the face that the imei is not the one listed on the phone (behind the battery. is that o.k ?
Click to expand...
Click to collapse
Flash back to stock and backup your EFS folder this includes the nv_data.bin file that contains your IMEI
Google search will be you friend or alterntively search the forum as this question has been asked before and answered by myself for other users

just reflash your stock rom....

I found there was an autobackup in /sdcard/efs/IMEI so backed up /efs and then copied /sdcard/efs/IMEI to /efs ...bit scary though for a simple ROM flash

jago25_98 said:
I found there was an autobackup in /sdcard/efs/IMEI so backed up /efs and then copied /sdcard/efs/IMEI to /efs ...bit scary though for a simple ROM flash
Click to expand...
Click to collapse
read the disclaimer that all DEVs post on the OP They all say the same thing
"Flash at your own risk"
Remember these are not the Factory ROMs and things may go wrong.
Read the whole thread for a ROM makes for a very informed decision before flashing

I guess what I'm dying to know is why some rooms blank the efs folder and why some don't. I read about losing the efs folder but after doing gummy and black from without needing to restore I figured the backup had to be just a precaution. hope the restore instructions get added to instructions.
is is that some rooms have the efs folder in their tar all and others don't? if so might it be better to not have it in the tar all so restore isn't needed. if you do a cp and get the order wrong you might blank your only backup (should have another backup of course but its nice to be nice to people of course

jago25_98 said:
is is that some rooms have the efs folder in their tar all and others don't?
Click to expand...
Click to collapse
EFS folder is a STATIC folder ie it will NEVER be included in a ROM stock or custom.
The nv_data.bin file located in the EFS folder contains data unique to each handset therefore it will not be included in any ROM.
Some ICS ROMs will cause issues with the permissions on the EFS folder and the files within causing the IMEI to display incorrectly or to have none at all

Lexrsk said:
EFS folder is a STATIC folder ie it will NEVER be included in a ROM stock or custom.
The nv_data.bin file located in the EFS folder contains data unique to each handset therefore it will not be included in any ROM.
Some ICS ROMs will cause issues with the permissions on the EFS folder and the files within causing the IMEI to display incorrectly or to have none at all
Click to expand...
Click to collapse
Well that's the thing you see. As far as I can tell ICS333 doesn't have the /efs folder so whatever is on there before the ROM is loaded should be there after unpacking. But unlike the Black ROM it isn't and I don't understand why.

jago25_98 said:
Well that's the thing you see. As far as I can tell ICS333 doesn't have the /efs folder so whatever is on there before the ROM is loaded should be there after unpacking. But unlike the Black ROM it isn't and I don't understand why.
Click to expand...
Click to collapse
If it it is not there then post in the ICS333 thread.
Include the output of "df" from either terminal emulator or ADB
ie
cd /
df >>/sdcard/phonedir.txt

thanks,
i copied the backuped nv data from stock rom and got my imie back.
maybe it's somthing in the permissions ilke said here.
thanks a lot .

HELP - CM10 upgrade and lost IMEI

Need some help here, hopefully without having to go back to JF6 (that is a little scary at this point). Was pretty happy with CM9 and updated through most nightlies. Just today I upgraded to CM10. All seemed to be working well except that I received a warning of invalid IMEI. I pushed through it and had the phone working on CM10 (with low memory /data isses - that could later be rectfied) then realized that the IMEI issue would mean AT&T would likely shut my phone down. The invalid IMEI is generic and has been flagged as invalid. I also ran into a few issues where I could not download from the Play Market App and think this was the reason.
I nandroid backed up CM10 and restored CM9 but still no dice. As I learned later it doesn't touch the efs folder which somehow the CM10 upgrade modified or had the effect to change it. Uuughh. many others were having the issue.
Anyway, I have verified that there are no /efs backups anywhere on my phone or SC or emmc cards. There are no backups within the efs folder. So, I am hosed. Any way to edit the nv_data.bin file a la this process for either CM9 or CM10?
http://forum.xda-developers.com/showthread.php?t=881162&highlight=restore+imei
This seems to be the only way I can see that would get me back with no IMEI EFS backup. But, going back to Android 2.1 Eclair or 2.3.5 Gingerbread would be a time killer and have to go through rerouting (?), upgrading, etc.
Any thoughts or direction?

tonyo123 said:
Need some help here, hopefully without having to go back to JF6 (that is a little scary at this point). Was pretty happy with CM9 and updated through most nightlies. Just tpday I upgraded to CM10. All seemed to be working well except that I received a warming of invalid IMEI. I pushed through it and had the phone working well then realized that this is an issue where AT&T will likely shut my phone down. The invalid IMEI is generic and has been flagged as invalid. I've also run into a few issues where I cannot download from the Play Market App although not sure if this is the reason.
I backed up jCM10 and restored (CEM NANDROID) CM9 but still no dice. As I learned it doesn;t tough the efs folder which somehow the CM10 upgrade modified or had the effect to change it - although I understadn the ROM is not supposed to do this but I see many having the issue.
Anyway, I have verified that there are no efs backups anywhere on my phone or SC or emmc cards. There are no backups within the efs folder. So, I am hosed. Any way to edit the nv_data.bin file a la this process for either CM9 or CM10:
http://forum.xda-developers.com/showthread.php?t=881162&highlight=restore+imei
This seems to be the only way I can see that would get me back with no IMEI EFS backup. But, going back to Android 2.1 Eclair would be a killer and have to go through rerouting (?), upgrading, etc.
Any thoughts or direction?
Click to expand...
Click to collapse
Go Stock with rooted KK4 and flash what ever rom you want after.
http://forum.xda-developers.com/showthread.php?t=1358180

Okay
silvertag said:
Go Stock with rooted KK4 and flash what ever rom you want after.
http://forum.xda-developers.com/showthread.php?t=1358180
Click to expand...
Click to collapse
All right it was a long painful night and day. Found and downloaded Heimdall One Click .jar with UCKK4 GB. Ran it and it restored the correct IMEI. It was unrooted and stock.
Then what was previously easy became an adventure to root and and load a kernel with CWM. I must have bricked the phone 10 times havimg to redo the Heimdall to Gingerbread 2.3.5 numerous times including reloading samsung pc drivers. Eventually with Odin, I found the right sequence using Corn Kernel for UCKK4 703 injected with CWM (not 705 or 706 versions which kept failing) which allowed me to get CWM loaded onto the phone.
I still could not restore my CM9 nandroid backups as the /data restore kept failing having to redo things from scratch. So, then I copied the latest CM9 nightly .zip onto the internal SD then loaded it from the Corn-CWM restore. CM9 booted and things were better but phone nad none of the settings and things still not right. Then rebooted into CWM recovery and restored the last CM9 nandroid backup. Now things worked and everything was back to normal with the correct IMEI.
Man that was a long stressing and scary day...
Made multiple copied of EFS for the future.
Will hold off on CM10 until the /efs issue is resolved as well as the memory management is better understood (while on CM10 I immediately ran into /data out of memory problems (I know I needed to move things to SD but never got around to it once the IMEI issue came up).
So, all is back to CM9 and finally working fine

odin to stock, then you will get imei back, backup efs folder, and flash back to cm10.

I have the same problem, but i'm om Rogers and 5 days now and no problems yet. I have a backup of my efs folder can I just copy paste?

master2828 said:
I have the same problem, but i'm om Rogers and 5 days now and no problems yet. I have a backup of my efs folder can I just copy paste?
Click to expand...
Click to collapse
Yes just make sure you set the correct permissions on the files. BTW You won't have a problem on Rogers. Canadian providers have all their black listed (lost/stolen) imei separated. They don't share it so a black listed imei on Rogers will work on Bell or Telus and vice versa. Only thing is that your phone can no longer be tracked by imei in case of emergency since its not the correct information but E911 will still locate you via GPS if you ever place a call.

silvertag said:
Yes just make sure you set the correct permissions on the files. BTW You won't have a problem on Rogers. Canadian providers have all their black listed (lost/stolen) imei separated. They don't share it so a black listed imei on Rogers will work on Bell or Telus and vice versa. Only thing is that your phone can no longer be tracked by imei in case of emergency since its not the correct information but E911 will still locate you via GPS if you ever place a call.
Click to expand...
Click to collapse
Cool, thanks, what are the correct permissions? if i run fix permissions from kernel will that do the trick?

master2828 said:
Cool, thanks, what are the correct permissions? if i run fix permissions from kernel will that do the trick?
Click to expand...
Click to collapse
That should do
EDIT: Checked my settings on nv_data.bin and its 777 (everything checked in RootExplorer)

silvertag said:
That should do
EDIT: Checked my settings on nv_data.bin and its 777 (everything checked in RootExplorer)
Click to expand...
Click to collapse
So where exactly do i put the efs folder? I looked on the root of my phone and i dont see a efs folder currently, i tried to put the backup i have there but it didnt work still go the error. i dont even know how i got the backup i have actually lol, i just copied my whole phone contents to my pc before i wiped just in case and there is an folder /backup/efs...lucky i guess

master2828 said:
So where exactly do i put the efs folder? I looked on the root of my phone and i dont see a efs folder currently, i tried to put the backup i have there but it didnt work still go the error. i dont even know how i got the backup i have actually lol, i just copied my whole phone contents to my pc before i wiped just in case and there is an folder /backup/efs...lucky i guess
Click to expand...
Click to collapse
It sounds like you have the backup that is sometimes made in the /sdcard (or /mnt/sdcard) folder, which is the internal storage you see when it's connected to your machine.
To see the /efs folder (assuming it exists), you would need to use either shell commands from inside ADB, or a root file explorer. If it's not there, you should just be able to dump the contents of that backup folder to a directory called /efs and go from there.

S3 MINI i8190 IMEI NULL after cyanogenmod update

Hi guys,
Yesterday I updated my cyanogenmod 11 with newest version doing a wipe cache first. After rebooting my phone seems to have an issue: the IMEI is null and I can't call or receive calls.
So I decided to flash the stock rom with odin, I thought that this could help, but nothing to do, the IMEI is still null and I can't use the phone
The first time I installed cyanogen I made a backup (using TWRP function), looking for that backup files, I discovered a file called efs.ext4.win, but if I try to open it with an unrar program, I see these files inside:
\.files
\bluetooth
\FactoryApp
\imei
\RFHAL
\RFHAL.DEF
\wifi
GUARDFIL
gyro_cal_data
pre_recovery.log
I don't see any "nv_data.bin" file or something like that. Is that normal?
Anyway, I think that EFS folder is corrupt or missing, i don't know. Is there a way to solve this issue? Thank you.

MaterialX said:
Hi guys,
Yesterday I updated my cyanogenmod 11 with newest version doing a wipe cache first. After rebooting my phone seems to have an issue: the IMEI is null and I can't call or receive calls.
So I decided to flash the stock rom with odin, I thought that this could help, but nothing to do, the IMEI is still null and I can't use the phone
The first time I installed cyanogen I made a backup (using TWRP function), looking for that backup files, I discovered a file called efs.ext4.win, but if I try to open it with an unrar program, I see these files inside:
\.files
\bluetooth
\FactoryApp
\imei
\RFHAL
\RFHAL.DEF
\wifi
GUARDFIL
gyro_cal_data
pre_recovery.log
I don't see any "nv_data.bin" file or something like that. Is that normal?
Anyway, I think that EFS folder is corrupt or missing, i don't know. Is there a way to solve this issue? Thank you.
Click to expand...
Click to collapse
S3 mini has no nv_data.bin file in EFS folder. You made already a backup of your efs, try to restore it with TWRP to get your IMEI back
Sent from my GT-I9301I using XDA Free mobile app

xXPR0T0TYPEXx said:
S3 mini has no nv_data.bin file in EFS folder. You made already a backup of your efs, try to restore it with TWRP to get your IMEI back
Sent from my GT-I9301I using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for replying.
I tried to restore EFS folder using TWRP and my backup, but nothing changed, I still don't have Imei and baseband.
Do you think that flashing a PIT file could help me?
Thank you so much.