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

i9000m insanity (semi-brick issue)

Hi guys,
Ok, so I've been Googling like a mofo for the past 3-4 days, trying this and that, investigating my issues, and I still need some help.
I've got a Bell I9000M that I would describe as the following:
1) Boots into any rom I flash via Odin (so far just GB and Froyo)
2) Internal SD works (I can see my files via USB), but "Internal Storage" shows unavailable.
3)I also flashed this phone before backing up my EFS folder so my unlock number is scrambled. I have a backup of the post unlocking-attempt EFS folder, but am unable to copy this back to where it needs to be. I've tried with ADB and no dice and I've tried copying it in with the phone on using Root Explorer - Root Explorer will copy the files back (and I'll even get the no SIM icon after a few minutes), but everything's gone and the EFS folder is empty when I reboot.
I'm kinda stuck. I just got this phone off CL last week thinking I'd flash it and go on my merry way like I normally do. I wasn't aware of the I9000M's horrid reliability. Anyway, any help would be appreciated!

ch0g0nda said:
Hi guys,
Ok, so I've been Googling like a mofo for the past 3-4 days, trying this and that, investigating my issues, and I still need some help.
I've got a Bell I9000M that I would describe as the following:
1) Boots into any rom I flash via Odin (so far just GB and Froyo)
2) Internal SD works (I can see my files via USB), but "Internal Storage" shows unavailable.
3)I also flashed this phone before backing up my EFS folder so my unlock number is scrambled. I have a backup of the post unlocking-attempt EFS folder, but am unable to copy this back to where it needs to be. I've tried with ADB and no dice and I've tried copying it in with the phone on using Root Explorer - Root Explorer will copy the files back (and I'll even get the no SIM icon after a few minutes), but everything's gone and the EFS folder is empty when I reboot.
I'm kinda stuck. I just got this phone off CL last week thinking I'd flash it and go on my merry way like I normally do. I wasn't aware of the I9000M's horrid reliability. Anyway, any help would be appreciated!
Click to expand...
Click to collapse
use the solutions on Quick fixes and solutions link below, especially the guide on how to make efs stick after reboots

Ok, so I did the making the IMEI/efs stick and it seems to have rectified everything for me! IMEI is back to what it should be, baseband is back, storage reads properly. Wow! I'm ecstatic right now! I've been dicking with this thing since last Friday and you've got me sorted in under 10 minutes, brilliant!
If you ever pass through British Columbia, let me know! I'll buy you a beer or something
Thanks again!

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.

[Q] Lost IMEI, etc the /efs folder and how to reuse and oldcopy

I am puzzled and confused about the /efs folder.
I have a P1000 which was running a January nightly build of CM10; this worked, including the telephone function, sort of...
I then upgraded to Android 4.2.2, CM10.1 from 21030728 - which works much better BUT it lost all the telephone capabilities (it shows Baseband version unknown). After much digging I think understood correctly that I must have ruined my /efs folder.
I do have previous /efs folder copies (not made with any particular tool) on my external SD card but even using something like Root Browser or Root File Manager to copy an old version (in which the telephone worked) to write over the existing /efs folder I do not regain access to the phone function.
My questions are these, if anyone can explain to me what is happening for I would like to understand:
1. I tried to delete the existing /efs folder (using Root Browser and Root File Manager) but it does not delete: why?
2. I am clearly doing something wrong when trying to copy an old version in order to write over the existing one (which does not work): what and why and how do I get around this to make it work?
3. How does Android protect the /efs folder and is there a way to get round this?
i have read far and wide but so much seems to be contradictory or inconsistent. Or is there a place where all is explained (and if so where?).
Thank you in advance.

Hello,
I had the same problem. I have restocked my Galaxy Tab but it did not work. I have tried to flash the modem with odin and it works! After reboot my Galaxy Tab i have Signal and the imei is restored. I have root my Galaxy Tab again and flash CM10.1 and it works prefect. I have now CM10.1 on my tab and i can use phone functions and the imei is restored. Have you tried to restock it and flash the modem with odin?
Good Luck!

Besides restocking or flashing a modem, you can try and restore your EFS backup with EFS Professional... Try to give it a shot.

[Q] Problems Backing Up EFS info

Hi. I'm new to rooting and flashing ROM's. I have had a Samsung Captivate (Gingerbread) that I haven't been using for quite some time and I thought I might try to update it to KitKat. I have read that it would be important to back up the EFS file so that I can keep my IMEI info. I rooted my phone using the tutorial on these forums and tried to use EFS Pro, but was not able to get past "the device is not perm rooted". Various threads suggested changing adb status, but I could not find that information (though I was able to find the USB debugging selection). I know that the phone is rooted so I looked for an older copy of EFS Pro in case the newer versions had dropped support for the Captivate. I couldn't find one so I looked at other ways to back up the files, but most information was for other (newer) Samsung phones. I could not install Samsung Tools. I really don't want to proceed with installing KitKat before backing up the EFS information. How do I go about doing this? I have tried the search function on the forum for this device and couldn't find what I was looking for (or maybe I didn't understand the information). Any thoughts?
I hope flashing KitKat will be easier than this issue...
Thanks.

Curious D said:
Hi. I'm new to rooting and flashing ROM's. I have had a Samsung Captivate (Gingerbread) that I haven't been using for quite some time and I thought I might try to update it to KitKat. I have read that it would be important to back up the EFS file so that I can keep my IMEI info. I rooted my phone using the tutorial on these forums and tried to use EFS Pro, but was not able to get past "the device is not perm rooted". Various threads suggested changing adb status, but I could not find that information (though I was able to find the USB debugging selection). I know that the phone is rooted so I looked for an older copy of EFS Pro in case the newer versions had dropped support for the Captivate. I couldn't find one so I looked at other ways to back up the files, but most information was for other (newer) Samsung phones. I could not install Samsung Tools. I really don't want to proceed with installing KitKat before backing up the EFS information. How do I go about doing this? I have tried the search function on the forum for this device and couldn't find what I was looking for (or maybe I didn't understand the information). Any thoughts?
I hope flashing KitKat will be easier than this issue...
Thanks.
Click to expand...
Click to collapse
You could just manually backup your efs folder using a root explorer or through adb. Have that backup on your pc in case you lose your IMEI.
That being said, when it happens (which is fairly rare), a flash back to stock (KK4) usually fixes it and then you're fine to update/flash again.

Other EFS backup options would include:
1) EFS☆IMEI☆Backup by wanam >> his xda thread, his playstore listing.
2) [HOWTO]Comprehensive IMEI/EFS Backup lists two simple ways to permanently backup up IMEI on your phone. One is with adb, the other is with Terminal Emulator for those with rooted devices. The commands used are said to be based on "Samsung's built in backup." The thread is in the SGS3 forum, if nothing else is an excellent source of background information for backing up and restoring nvdata.

I tried to copy the efs folder using Root Browser because the adb method looked very involved. When I started Root Browser, it was able to see a Titanium backup that I had placed into the SD card even though I had formatted the SD card. I figured that the format didn't wipe the information so I proceeded to copy the efs folder over. However, after copying the folder, I stuck the card into my computer and did not see the folder and could not copy the folder over to my computer. Is it because the card is formatted differently than my computer or is it that the file is not compatible with Windows given that it is an Android folder?
Will copying the folder be enough for backing up? If it is this easy to restore the efs, why use EFS Pro? Is there something else with the folder that needs to be present in order to restore a phone that loses IMEI information?

Curious D said:
I tried to copy the efs folder using Root Browser because the adb method looked very involved. When I started Root Browser, it was able to see a Titanium backup that I had placed into the SD card even though I had formatted the SD card. I figured that the format didn't wipe the information so I proceeded to copy the efs folder over. However, after copying the folder, I stuck the card into my computer and did not see the folder and could not copy the folder over to my computer. Is it because the card is formatted differently than my computer or is it that the file is not compatible with Windows given that it is an Android folder?
Will copying the folder be enough for backing up? If it is this easy to restore the efs, why use EFS Pro? Is there something else with the folder that needs to be present in order to restore a phone that loses IMEI information?
Click to expand...
Click to collapse
If you have it on your SD card, it should be fine. The idea is to have it on something else than your device's internal memory in case something goes wrong and can't get it there.
As for efs pro, some devices can't manually backup like the Cappy or is not enough. But once again, it doesn't happen very often that you lose your IMEI.

Okay. That's great. I guess I can try my first ROM flashing to KitKat. Thanks.