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

restore nv-data.bin

So. my IMEI is jacked up. I made a copy of /efs when I got the phone but instead of making an archive I did a straight copy, Seems like the fat filesystem owned the permissions.
I am trying to restore from that backup but I am not having luck. People say you can just drop those files into place but it seems that they are replaced after every reboot. What do the permissions need to be? I see that ownership needs to be 1001:1001. Also, can I do this on JH7 with any success?

If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo

I used the CWM flashable zip to get back to JH7, didn't use odin (im not at home yet, and this was eating away at me at work, heh).
Ill flash back with odin and then see where that gets me. For my own sanitys sake, could you tell me what the permissions are on your files in /efs?

i have a fix that worked for me posted in the dev section

bames said:
i have a fix that worked for me posted in the dev section
Click to expand...
Click to collapse
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply

z28james said:
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply
Click to expand...
Click to collapse
once in jf6 if your imei isn't corrected then delete everything but the nv_data.bin and .nv_data.bak.md5.
use android terminal emulator to execute following (must have busybox installed)
su
busybox chown 1001:1001 /efs/nv_data.bin
reboot

avgjoegeek said:
If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo
Click to expand...
Click to collapse
fyi android id is different than the device id. Device ID = IMEI.

I see my problem, the efs directory I have is from my OLD captivate. Arrrg....I have no backup of my current /efs. The random nv_data.bin it creates has the correct product code already.
There must be something in the phone that knows the imei as this is why it was not accepting my dropped in files (the files from my old phone).
Ah well...ill use it till ATT blocks the test IMEI "lose" mine and go get a refurb as I have insurance.
FYI, the stock original firmware does not create those .bak files from what I could see. I bet your files had jacked product IDs but perhaps the part that went with your IMEI was still intact. This would be why my phone wont accept my old phones nv_data.bin?

once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.

bames said:
once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.
Click to expand...
Click to collapse
None of those files get generated for me or exist. If I remove everything, a generic nv_data.bin and .imei get created. Thats it. If I copy over the files from my old captivate, I believe they do get created but since the IMEI in that file does not match whatever is being checked in the phone, new files are created anyways.
I suppose nobody as of now knows how to generate the string that is in the nv_data.bin based on an IMEI so it seems that I am out of luck.
Perhaps some shady place in town can help me repair the IMEI or something

I ended up calling Samsung today. I described the problem (damaged IMEI) and they sent me a pre-paid shipping label to send it off to Plano TX to have them take a look (i'm in Austin).
I will let you guys know how this turns out.

My phone is on its way back to me. They ended up swapping the mainboard under warranty.
I suppose if you have a damaged IMEI and can deal with using an old phone for a week, consider sending it over to samsung.

did you have to pay for new mainboard? cause i got the same problem but i am not the orginal owner for the phone.

Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.

Phateless said:
Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.
Click to expand...
Click to collapse
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text

z28james said:
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text
Click to expand...
Click to collapse
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...

Phateless said:
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...
Click to expand...
Click to collapse
Well, the warranty period is a year and so since its been less than a year since the captivates release, you should be good. It would seem the only way it would be out of warranty would be if samsung for some reason deemed it to be at some point. Im sure you could call samsung with the IMEI and verify.
In my case, my product ID had become damaged. My problem is although I had a backup of /efs, it was for my first captivate, not my current. I deleted /efs and moved the backup into place. Seeing that it was the nv_data.bin for some other phone with another IMEI (the IMEI is encrypted inside that file) it instead replaced the files with a generic set of files and the dreaded test IMEI.
Since nobody had a good way to write the IMEI to that file as it expects, I was SOL.
If I could do it again, I would make a .99 cent jig (I did this using a wonderful thread here labeled something like "make a jig without cutting up USB cable) which gets you into download mode if odin or something soft bricks your phone, root, make a backup of /efs and then take a nandroid backup. I THINK I remember reading that sgstools can backup /efs for you but in the sticky there is a method on how to make a .tar of /efs (good as this will retain permissions/ownership as if you straight copy them to the sd card with fat32, the filesystem does not understand linux permissions and blows them away).

Master-Clear did the trick 4 me
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!

TommyZee said:
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!
Click to expand...
Click to collapse
Do you know where I can find this ODIN3 one-click and how to do a master clear?

[Q] No SIM-card found

Hey all!
So my problem is that my SGS can't find any SIM cards...
First of all i got 2.1 android and then i updated to 2.2 version:I9000NEJP2
After that it seemed that my SGS was really slow, so i decided to use CFW.
I installed Darky's v.8.0
Everything worked fine, was really fast.
The next step was to unlock the simlock. First i tried SGS Unlock freeware.
I watched some vids and read some threads and the most of em said or wrote that this app worked fine. I tried it but the app couldn't find any codes on the phone.
After that i decided to try the PC version. I downloaded "Generate Unlock Windows" but this doesn't work for me too. No keys were shown in the box -.- .
So i tried it sometimes, and the result was, that i couldn't use my SGS any more.
Can't find the sim. I tried several times, nothing worked.
Then i downgraded my fw to I900XXJP2 once more, but useless...
does anybode have an unfreeze code, or does anybody know how i could solve that prob?
maybe unlock-code?
and if yes, where could i get this the best way?
Simlock is [3; Austria]
IMEI (still the original one): 354795/04/228598/8
thanks for any kind of help
maybe i'll sound a little bit nooby, but i'm new in that forum and also a new android user
thx

This may or may not solve your problem but some people have found that their SIM card seems to stop working after they have changed their product code. The fix for this is to run the following commands from ADB (you need to be rooted with SU installed):
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
Or if you have a Terminal Emulator on your phone you can do the following:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
AFAIK it can't do any harm running this file ownership command on nv_data.bin even is it isn't the cause of thr problem so give it a try, I hope it helps!

so first of all i got to tell u, that i've never used ADB before, and i do not know what that is and how i can start that
i started to google it but after reading several pages i'm do not know more...
could you pls tell me how i can start and type that?
and also where i can find it?
thx

didnt work
I tried the one with the terminal emulator..
did everything like u wrote, reboot...
nothing happened
seems that i ruined something -.-
maybe an other idea how i could solve that prob?
additional information: i got a little simcard symbol at the top of the screen and next to it there is a callsign

try nav_data.bin copy to your pc and run sgux from cmd or post it here

can't find the efs folder on my phone, where should i look for the file?...

Alex Varga said:
can't find the efs folder on my phone, where should i look for the file?...
Click to expand...
Click to collapse
in market download super manager also install busybox if you don't have
run super manager>settings>select busybox file
then select /system/xbin/busybox
and select enable ROOT function
after that run file explorer in super manager and go back till first folder isn't acct and 2nd cache folder; now scroll to efs and copy nv_data.bin to sdcard
after that you can unclick enable root function in settings of user manager

00.ante said:
in market download super manager
Click to expand...
Click to collapse
Ok i searched with astro for it and i looked for it manually.
Astro couldn't find it and i also saw that there isn't anything in the efs folder.
So now i got a problem, right?^^

Alex Varga said:
Ok i searched with astro for it and i looked for it manually.
Astro couldn't find it and i also saw that there isn't anything in the efs folder.
So now i got a problem, right?^^
Click to expand...
Click to collapse
I wrote before with astro but then remembered that astro doesn't have root rights so I've edited text if you want copy complete efs folder and post it here.
One more question did you ty another sim card?

00.ante said:
in market download super manager also install busybox if you don't have
run super manager>settings>select busybox file
then select /system/xbin/busybox
and select enable ROOT function
after that run file explorer in super manager and go back till first folder isn't acct and 2nd cache folder; now scroll to efs and copy nv_data.bin to sdcard
after that you can unclick enable root function in settings of user manager
Click to expand...
Click to collapse
ok i copied it to my card, and now i have the file...
i don't know what u mean with that cmd action, but here is my file...
http://www.megaupload.com/?d=TLWMXQ23

when you enter this code *#7465625# is it only first option (I think it's Network lock; nos sure) ON and rest is OFF? also keep your orginal nv_data.bin on pc

00.ante said:
when you enter this code *#7465625# is it on first ON and rest is OFF? also keep your orginal nv_data.bin on pc
Click to expand...
Click to collapse
So the first is ON, the rest is OFF...
What does this mean?
And i think the file isnt the same as it was when the phone got out of the factory...
I dumba** didn't make a backup befor i started workin' on it...

Alex Varga said:
So the first is ON, the rest is OFF...
What does this mean?
And i think the file isnt the same as it was when the phone got out of the factory...
I dumba** didn't make a backup befor i started workin' on it...
Click to expand...
Click to collapse
So for ON is network lock which is good.
Ok you keep your orginal nv_data file on pc and copy these files to your efs folder with super manager. Then reboot phone and post back does sim work now.

00.ante said:
So for ON is network lock which is good.
Ok you keep your orginal nv_data file on pc and copy these files to your efs folder with super manager. Then reboot phone and post back does sim work now.
Click to expand...
Click to collapse
no, it doesn't...
the same problem
so what could i do now?
I found that thread, but i don't know what i have to put in there.
Do you know a side where i could find the codes for other countries?
Or what things i shall do too.
This guy wrote that he tried it at 2.1 and i have 2.2.
Could that be a prob?
thx for ur help

when you enter code from post before what does it say on first option? is it on or off now

00.ante said:
when you enter code from post before what does it say on first option? is it on or off now
Click to expand...
Click to collapse
I tried it, used the code and somehow there didn't appear OFF or ON.
Nothing is standing there.
What does this mean?

Alex Varga said:
I tried it, used the code and somehow there didn't appear OFF or ON.
Nothing is standing there.
What does this mean?
Click to expand...
Click to collapse
Not sure but try this. delete files I send you in elf folder and copy these 2 files from zip and then reboot phone and see with code is network lock on or off and if it doesn't work then delete files from elf folder (ones I send you) and copy orginal nv_data.bin back; then reboot phone and with code see network unlock
and please post back for all situations. Also try booting phone without any sim in it and then with sim
when enter code if no locks are there then it should be everything like in picture

Alex Varga said:
I tried it, used the code and somehow there didn't appear OFF or ON.
Nothing is standing there.
What does this mean?
Click to expand...
Click to collapse
OK this is last shot. If nothing worked before try these 2 files from zip on phone and post back; and before coping them delete old ones and also can you post your nv.log from efs folder?

Tried everyone of your solutions and in every case i could NOT see the [ON] or [OFF].
It seems like it disappeard. Only space left, no symbols, nothing.
And the card can't be found too.

ups sorry forgot to attach 2 files. If this doesn't work I don't know what will. then put back orginal file in efs folder.
Also if you know someone who has also sgs still locked to your network copy his files here (complete efs folder)
all files I posted are modified and worked without problem on my sgs. Also please post nv.log from you efs folder here

correct IMEI, but NO EFS folder --> no service

Hello guys, a friend of mine just gave me his phone because "it has got a problem" he said. He just flashed a ROM from CMW, but he noticed that there was no service. the problem is that, if I dial *#06# there is the CORRECT IMEI, but if I search for the EFS folder, there is no trace of it. how is this possible? the IMEI shown in the phone also corresponds to the IMEI wrote on the back of the phone... so it's clearly correct. how this could be possible? I tried adding manually the EFS folder using root explorer (and mounting it as R/W), but after the reboot the phone automatically delete the folder I created.. any idea? thank you!

blak24 said:
Hello guys, a friend of mine just gave me his phone because "it has got a problem" he said. He just flashed a ROM from CMW, but he noticed that there was no service. the problem is that, if I dial *#06# there is the CORRECT IMEI, but if I search for the EFS folder, there is no trace of it. how is this possible? the IMEI shown in the phone also corresponds to the IMEI wrote on the back of the phone... so it's clearly correct. how this could be possible? I tried adding manually the EFS folder using root explorer (and mounting it as R/W), but after the reboot the phone automatically delete the folder I created.. any idea? thank you!
Click to expand...
Click to collapse
Look in My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

nothing worked for me.. I tried to flash an earlier version of android, gingerbread, and the EFS folder was recreated but was incomplete. there were no "imei" folder into efs folder, and also there were no nv_core.back files, ecc... despite this, the IMEI number was shown correctly in the phone, but no signal/data... :S

blak24 said:
nothing worked for me.. I tried to flash an earlier version of android, gingerbread, and the EFS folder was recreated but was incomplete. there were no "imei" folder into efs folder, and also there were no nv_core.back files, ecc... despite this, the IMEI number was shown correctly in the phone, but no signal/data... :S
Click to expand...
Click to collapse
Have you tried restoring the original firmware and checked? If not you should do that.
http://forum.xda-developers.com/showthread.php?t=1102881
:fingers-crossed:

no network service issue with jelly bean
I have a similar issue here.
First of all I flashed usin this guide:
thehelptimes.com/install-jelly-bean-on-galaxy-s-i9000-how-to-official-rom-android-4-1
provider is congstar (T-Mobile reseller)
*#06# gives me the correct IMEI
/efs folder exist
/efs/imei too
I tried killing the nv_data.bin in order to have the phone recreate it. That happened, now the phone asked for a pin at reboot but the pin doesn´t get
accepted. It also doesn´t get locked after 3 attempts. It just doesn´t get accepted.
Then I noticed that the rights of the nv_data.bin are different than the other files. I changed that but it got changed back after reboot and the pin still isn´t accepted.
I have no idea whats wrong. Next attempt back to gingerbread :-/

EMnEL said:
Have you tried restoring the original firmware and checked? If not you should do that.
http://forum.xda-developers.com/showthread.php?t=1102881
:fingers-crossed:
Click to expand...
Click to collapse
yep I tried restoring gingerbread, and, as I said, the phone created the efs folder, but it was incomplete... there were no IMEI folder, other folders were missing, and there were NO nv_data.bin files. I tried reflashing jelly bean and the efs folder was, again, completely missing...

Alright, I am gone back to XJVP but this wasn´t much help.
No signal either.
IMEI still shown by dialing *#06#
as of forum.xda-developers.com/showpost.php?p=26827676&postcount=4512
I need to get into root to kill the efs folder.
So I am back to XXJVU (gingerbread) now to get it rooted.
Before root there is still no network yet but I still can display the IMEI 3547.... (which is listed in the settings too).
Alright now I am going to root it. Hope this helps somehow.
I have the strong feeling that this phone ends up as a mp3/mp4 player
UPDATE....
- Alright, according to this I better not kill the efs by ODIN ? I didn´t yet. forum.xda-developers.com/showthread.php?t=1114958
- I checked the efs folder and noticed it is pretty much holding the same content as
in an efs offered for download "i9000 358001043596739 efs.rar" at 199.91.153.60/pa6q9c9bboog/eyyse638dh3kncn/i9000++358001043596739+efs.rar
So it looks pretty much like it should, I can see my perfect IMEI but it still doesn´t work. I am lost. No clue.
Back in my I9003 the SIM just works perfect so it is obviously not an issue of the SIM
UPDATE 2...
- flashed back to XXJP1 Froyo which was a bad idea now the IMEI is empty - F**K!
- going back to XXJVU now
UPDATE 3...
- Back to XXJVU still no signal however it detected at least T-Mobile at boot and gave me a radio box to select T-Mobile.
Sometimes the signal strength shows one bar (two bars when I am going to the window that points in direction of the sender)
though it should be fairly more here as other phones proof. No matter what that means anyway it says there is no service.
UPDATE 4...
- Compared the mobile settings with the i9003 and noticed that the i9003 shows EDGE, the i9000 GPRS

Alright, I got it back to GT_I9000_XXJQ3_XXJPY_DBTJS2 and made an official upgrade to the latest stock via KIES then. Nothing better.
I assume thise phone got a hardware defect then. Even though it doesn´t seem too logical

[Q] i8190 IMEI NULL/NULL

Hello,
got the same Problem like alot others. Wrong flashing and the complete EFS was destroyed.
Now i go back to Stock, rebuild the Baseband and the Counter is 0. But still have IMEI NULL/NULL
I read now alot of posts in the Net and tryed a lot but nothing helped.
So my Question is, is there really a solution to build the IMEI back to the Original one if you completly lose the original
EFS Folder? Or do i need to get it to technican to get it back with a Box?
I tryed IMEI Changer App but this one doesnt work on my i8190.
If there is another way to fix this, would be grate to get a but of Help.
Thank you in advance.

So i try to change the IMEI with ALP. But ALP directly gets an Read Error while try to get the IMEI.
Is there a File i can put in and change it with ALP to get back my IMEI?

I had the same problem when i was on my SGY. Just reflash the rom through odin and fix permissions. ??
There is no bad choises, only bad results.
SGS III Mini
tenshi_xp's PAC Rom RC-3
KitKat 4.4.4.

Hi,
thank you for your Answer. But i already reflashed Stock Rom all things are back, i just miss the IMEI File or Area. Saw on the net there are IMEI Folder to flash with ODIN
so i can change it with ALP. But most of the Sites or Files or deleted, maybe false and Viruses, i dont know.
My Problem is that my complete EFS Folder was lost, no Backup nothing. With different Flashes and Stuff i got it back with Baseband, CSC and so on. Just my IMEI tells
me NULL/NULL and ALP cant get it, because this Part isnt available anymore
Can you tell me Stockrom or something i can try? Need something for an open German i8190.
Best Regards

guzzzi0 said:
Hi,
thank you for your Answer. But i already reflashed Stock Rom all things are back, i just miss the IMEI File or Area. Saw on the net there are IMEI Folder to flash with ODIN
so i can change it with ALP. But most of the Sites or Files or deleted, maybe false and Viruses, i dont know.
My Problem is that my complete EFS Folder was lost, no Backup nothing. With different Flashes and Stuff i got it back with Baseband, CSC and so on. Just my IMEI tells
me NULL/NULL and ALP cant get it, because this Part isnt available anymore
Can you tell me Stockrom or something i can try? Need something for an open German i8190.
Best Regards
Click to expand...
Click to collapse
Our IMEI number isn't saved in /efs partition/folder. It's saved in mmcblk0p9 partition which take up to 1MB. The efs partition (/efs>imei folder) only contains the IMEI key code to access the IMEI number in mmcblk0p9 path. If your IMEI key code got wiped and you didn't make a backup of your efs partition, then you will (unfortunately) never see your IMEI again
BTW : Does WiFi, Bluetooth etc. works or not?
EDIT : I found a interesting therad for you http://forum.xda-developers.com/showthread.php?t=2755787. Maybe you can use this efs backup from this user and change the IMEI to your original one.

xXPR0T0TYPEXx said:
Our IMEI number isn't saved in /efs partition/folder. It's saved in mmcblk0p9 partition which take up to 1MB. The efs partition (/efs>imei folder) only contains the IMEI key code to access the IMEI number in mmcblk0p9 path. If your IMEI key code got wiped and you didn't make a backup of your efs partition, then you will (unfortunately) never see your IMEI again
BTW : Does WiFi, Bluetooth etc. works or not?
Click to expand...
Click to collapse
Yes all other Services are working WiFi and BT. Just the IMEI Numbers are gone.
But if its possible to recreate the Folder and File i think its possible to change the IMEI Number with APS to the old one from the Mobilphone.
But i can get them back if i recover with a OctupsBox or how this boxes are calling?!

guzzzi0 said:
Yes all other Services are working WiFi and BT. Just the IMEI Numbers are gone.
But if its possible to recreate the Folder and File i think its possible to change the IMEI Number with APS to the old one from the Mobilphone.
But i can get them back if i recover with a OctupsBox or how this boxes are calling?!
Click to expand...
Click to collapse
Check my edited post mate

xXPR0T0TYPEXx said:
Check my edited post mate
Click to expand...
Click to collapse
Thank you. Will try this when im back at Home. I will give Feedback if it was possible.

When try to install this with CWM i get an Installation aborted
Isnt there a complete Stock Rom with Partition file and everything needed?

guzzzi0 said:
When try to install this with CWM i get an Installation aborted
Isnt there a complete Stock Rom with Partition file and everything needed?
Click to expand...
Click to collapse
There is an alternative method. You can flash this efs.img (which you find in the zip file) with terminal emulator which needs ROOT access.
1. root your device and download terminal emulator from Google play store.
2. Copy the efs.img to your internal storage and open terminal emulator.
3. After open terminal emulator type su to give root access, (your supperuser app asks for root access, confirm with yes)
4. Type/Copy this code : dd if=/storage/sdcard0/efs.img of=/dev/block/mmcblk0p11 in terminal emulator and press "enter"
5. Now your efs partition got overwritten with the efs.img
BEFORE!! you start this method, backup your "current" efs folder by type in terminal emulator : dd if=/dev/block/mmcblk0p11 of=/extSdCard/EFS.img
Please do this at your own risk!

xXPR0T0TYPEXx said:
There is an alternative method. You can flash this efs.img (which you find in the zip file) with terminal emulator which needs ROOT access.
1. root your device and download terminal emulator from Google play store.
2. Copy the efs.img to your internal storage and open terminal emulator.
3. After open terminal emulator type su to give root access, (your supperuser app asks for root access, confirm with yes)
4. Type/Copy this code : dd if=/storage/sdcard0/efs.img of=/dev/block/mmcblk0p11 in terminal emulator and press "enter"
5. Now your efs partition got overwritten with the efs.img
BEFORE!! you start this method, backup your "current" efs folder by type in terminal emulator : dd if=/dev/block/mmcblk0p11 of=/extSdCard/EFS.img
Please do this at your own risk!
Click to expand...
Click to collapse
Hello,
the Problem is this .ZIP File isnt available anymore on MEGA Hoster

guzzzi0 said:
Hello,
the Problem is this .ZIP File isnt available anymore on MEGA Hoster
Click to expand...
Click to collapse
Wait mate. I will upload this efs.img...

guzzzi0 said:
Hello,
the Problem is this .ZIP File isnt available anymore on MEGA Hoster
Click to expand...
Click to collapse
Here the ZIP file. It's not flashable, just unzip it and flash it with terminal emulator

Im sorry but this didnt helped. I think i really need all Parts back to re-partition + Bootloader and all other stuff to get it back.
But i think to send it to a shop to get it back into life.
Many thanks for your Help and merry Christmas and happy new Year
Best Regards

guzzzi0 said:
Im sorry but this didnt helped. I think i really need all Parts back to re-partition + Bootloader and all other stuff to get it back.
But i think to send it to a shop to get it back into life.
Many thanks for your Help and merry Christmas and happy new Year
Best Regards
Click to expand...
Click to collapse
Yes it's better to send it back to Samsung center
Merry Christmas and happy new year too