Database Develop

IMeI back

I have my phone unlocked.but my IMEI is corrupted but is working good so far I have network and I havE a backup of my efs folder on my pc. everytime I try to replace it with root explorer I overwrite the efs folder but It doesnt, how can I replace my original efs folder instead of my current efs folder which is corrupted????
Sent from my SAMSUNG-SGH-I897 using XDA App

how did you unlock it?
did you use an app?
does that app have the option to restore original?
probably does...

yes I used helroz app and I have two backups the original one and the helroz app backup but for some reason I paste my efs backup using root explorer but it doesnt overwrite it instead i have two folders with the same name.
Sent from my SAMSUNG-SGH-I897 using XDA App

well if you read the words in the app
the one .bak ISNT a backup. it is a necessary system file.
it says so in the app.
also you cant replace the efs backup like that with root explorer.
it doesnt work like that.
the app from herloz
has an option to restore your original files and re-lock the phone
USE IT!!
how do i know???
i re-wrote the english translation for him~!

so i relock my phone and i get my imei back?? I need it unlock because I use a diferent sim not att. what if I flash stock using odin??? I need my phone unlocked 'cause I dont live in the USA!!!
Sent from my SAMSUNG-SGH-I897 using XDA App

well re-locking the phone will restore your backup!
then re-unlock it using the PROPER code method. not the backdoor file swap method.
use [APP]SuperOneClick v1.9.1
to get the unlock code. (second tab in program says "captivate")
although that app didnt change my imei when i used it months ago, but had no choice the rogers captivates dont have the code stored in the phone, you must get it from rogers. but the att phones have the code hidden inside. it can be found and used.

i restore my backup and nothing still unlocked and corrupted IMeI
Sent from my SAMSUNG-SGH-I897 using XDA App

well every once and a while your network will check imei s and you will just stop working... might want to check out herloz thread.. ask for help,
he knows more about the imeis than most of us here.
we dont mess with em unless we need to. lol

TRusselo said:
well re-locking the phone will restore your backup!
then re-unlock it using the PROPER code method. not the backdoor file swap method.
use [APP]SuperOneClick v1.9.1
to get the unlock code. (second tab in program says "captivate")
although that app didnt change my imei when i used it months ago, but had no choice the rogers captivates dont have the code stored in the phone, you must get it from rogers. but the att phones have the code hidden inside. it can be found and used.
Click to expand...
Click to collapse
I like your description of the 1st method TR, but on the ATT Cappy refurb I got that was upgrade imaged at the factory, OneClick & SGS Unlock only pulled fffff.
Two I earlier upgraded myself both responded to SGS Unlock as did the post upgrade new phone they sent me that probably never saw 2.1. On number 4 of the 4 I've handled, backdoor was the only way.

cool good to know about the refurbs.
i got fffff as well did the switch with the app and its held up through rom flashes att one click rogers stocks gingerbread. still unlocked and correct imei. older version of app though..
though every odd person it happens to. it has happened before in his thread.

Invalid IMEI prompt on bootup

Guys,
I just updated with the CM10 nightly and I am getting a prompt on bootup that my IMEI is not valid. The IMEI is not blank, and isnt something like 0123456789. Is this a big issue? My calling and texting are working fine, as is my mobile data.
Thanks

The same happens to me. I did an efs backup with root manager but is there any risk? Could someone explain please?

I backed up with cwm before loading cm10 0823. And did an imei restore from Nitrality and it says successful. However I still get an invalid imei on bootup
Sent from my GT-I9000 using xda premium

Updated to cm10 0824. Same issue. Should I do a full cwm restore?
Sent from my GT-I9000 using xda premium

Hey guys common issue if you want it back follow my guide http://forum.xda-developers.com/showthread.php?t=1845104 you might want to titanium backup your apps first then backup your sd
Sent from my GT-I9000 using xda premium

Restored cwm backup from before the issue started. No long have invalid imei. Update to latest cm 10 and invalid imei prompt on startup. However the imei screen under About has an imei number in it still.
Sent from my GT-I9000 using xda premium

Correct imei though as in the same as the one under the battery?
Sent from my GT-I9000 using xda premium

Nope. Its a different one.
Sent from my GT-I9000 using xda premium

webchaos said:
Nope. Its a different one.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
OK so its invalid try the link I previously posted if it works or not get back to me
Sent from my GT-I9000 using xda premium

After going back to stock GB, darky resurrection ROM, cm9 and finally cm10. IMEI is back and looking OK. Thanks.
Sent from my GT-I9000 using xda premium

That's good
Sent from my GT-I9000 using xda premium

Felt a bit of nostalgia going back through the last 2 years of ROMs lol. Thanks again.
Sent from my GT-I9000 using xda premium

webchaos said:
Felt a bit of nostalgia going back through the last 2 years of ROMs lol. Thanks again.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Well, in my case, my father's phone lost all efs backups, and nv_data.bin is corrupted (regenerated new one with default generic IMEI).
So, there is nothing to restore from. Reflashing to stock 2.3.6 JW5 firmware didn't help. So you think that I will have to reflash to 2.2.1? How so? I don't understand how older firmware may help restoring correct IMEI...and I don't own JTAG, z3w or SPT boxes...
And for morrons - no, there is no .nv_data.bin, no nv_data.bin.bak, or similiar...only new nv_data.bin(md5) with default, generic IMEI.
Is there any way to restore it? if somebody start to complain that I am thief, I can prove by photos of original phone box, and buying papers I have (my father gave them to me for this purpose).
And no, I don't have to steal anything, I own SGS3, SGS2, SGS, SGT10.1....so stealing another SGS is not an option for me
I just want to restore that phone to it's stock state (and then reflash again with CM10).
Anyone?

Virnik0 said:
I just want to restore that phone to it's stock state (and then reflash again with CM10). Anyone?
Click to expand...
Click to collapse
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
just flash a JVU and a PIT , should get you back your IMEI or look at My android solutions for details

xsenman said:
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
just flash a JVU and a PIT , should get you back your IMEI or look at My android solutions for details
Click to expand...
Click to collapse
Why are you so confident, that JVU will regenerate /efs?
as said before, my father was so genius, that he has wiped /efs partition out. I have restored some data, but without proper IMEI, so now I have generic one. I still do have old JVU package somewhere on my NAS, but I do not understand, how old firmware may help, because I am without any /efs backup anywhere... is that firmware customized so it checks and regenerates /efs if its damaged? If so, why is this feature missing from latest full JW5 firmare? Please understand that I know what I am doing, but right now, I have empty hands...without JTAG, z3w or similiar low-level gadget, it is really hard to restore proper /efs on my own...
But thank you for links, I will take a look on them...

More Clues On Fixing IMEI Issue (solved for me)
In my case I upgraded directly from Froyo to CM10.1 and got then same dreaded 'default' invalid/corrupt IMEI=004999010640000
On inspection of the /efs files present it was clear they had been created by the system in response to not being present.
Following advice in this thread and elsewhere I downgraded back to Froyo (XXJPU) and like magic my correct IMEI re-appeared but as soon as I upgraded up to CM9 it changed back to the invalid default of 004999010640000 again.
To cut a long story short I downgraded back to Froyo (XXJPU) again, flashed a recent CWM recovery and booted into the recovery. I then used ADB to get a (root) shell prompt and discovered that the correct /efs data was being mounted from the device /dev/stl3 and at this point I was able to tar up the contents of /efs and safely make a backup. I then upgraded to CM10.1, restored the correct /efs backup and rebooted.
Happy with correct IMEI now
I am not sure what is going on but I am speculating that the big jump from Froyo to CM10.1 bypasses come critical intermediate ROM build where the correct IMEI data is copied from /dev/stl3. CM10.1 assumes this step has taken place and makes no attempt to get the original IMEI data.
... Robert

robertrath said:
In my case I upgraded directly from Froyo to CM10.1 and got then same dreaded 'default' invalid/corrupt IMEI=004999010640000
On inspection of the /efs files present it was clear they had been created by the system in response to not being present.
Following advice in this thread and elsewhere I downgraded back to Froyo (XXJPU) and like magic my correct IMEI re-appeared but as soon as I upgraded up to CM9 it changed back to the invalid default of 004999010640000 again.
To cut a long story short I downgraded back to Froyo (XXJPU) again, flashed a recent CWM recovery and booted into the recovery. I then used ADB to get a (root) shell prompt and discovered that the correct /efs data was being mounted from the device /dev/stl3 and at this point I was able to tar up the contents of /efs and safely make a backup. I then upgraded to CM10.1, restored the correct /efs backup and rebooted.
Happy with correct IMEI now
I am not sure what is going on but I am speculating that the big jump from Froyo to CM10.1 bypasses come critical intermediate ROM build where the correct IMEI data is copied from /dev/stl3. CM10.1 assumes this step has taken place and makes no attempt to get the original IMEI data.
... Robert
Click to expand...
Click to collapse
Exactly that. Same goes with going from Gingerbread to Jelly Bean.
That critical intermediate rom... Is CM9
In other words, to safely preserve your IMEI,
Froyo/GB ---> CM9 ----> CM10/10.1/JB
Sent from my GT-P7510 using Tapatalk HD

Help! Accidently deleted OS I think? Possibly "Bricked"

Hey guys. I messed up my phone. amature mistakes. I learned my lesson. I was trying to flash a jellybean rom plus the Devil R3 kernel over to a rooted Captivate using CWM. It flashed the Devil kernel over smoothly then when I went to intall the Jellybean rom zip it started to go smoothly then it rebooted in about 5 seconds into the installation and all that came up after 20 min of sitting was the Devil kernel screen. I can get to download mode. I could flash different kernels with odin but then I thought to myself my phone is basically bricked, so I tried that one click unbrick and it also messed up my drivers so now I can't use odin. It worked kind of but didn't change anything. Now I am stuck at the AT&T boot screen. I think the OS was deleted. I can't acesses the SD card. I was stupid and didnt create a CWM backup first. Now all I wanna do is simply go back to a basic 2.3.5 gingerbread and I am never gonna try anthing this dumb again. Please help guys this is my last hope.
edit:
I also wanted to clear up I used the corn kernel to install CWM it worked for the installation of the devil kernel but not the installation of Jellybean OS

Heh, deleting the os? I do it all the time, it means nothing. Have you used heimdall at all? That will mess up your drivers, so make sure you don't try to Odin using the same usb port you did with heimdall.
Sent from a jelly bean

korockinout13 said:
Heh, deleting the os? I do it all the time, it means nothing. Have you used heimdall at all? That will mess up your drivers, so make sure you don't try to Odin using the same usb port you did with heimdall.
Sent from a jelly bean
Click to expand...
Click to collapse
Yeah that one click unbrick used heimdall. I tryed a different usb port it worked I can use odin again. What should I do now?

AllieB said:
Yeah that one click unbrick used heimdall. I tryed a different usb port it worked I can use odin again. What should I do now?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1300843
Go to that thread and then to the second post. Download an Odin one-click for gingerbread kk4 probably with bootloaders unless you've been on gingerbread previously in which case you can go without boot loaders. Using that will take you back to stock gingerbread. Then you can use Odin to flash your corn kernel or devil kernel, which ever one you want and continue on with your flashing fun.
Just an FYI based on your OP what happened during the rom flash is normal. A lot of the Jelly Bean roms out there use different partition layouts and different kernels. So when you start the flashing of the rom the first thing is does it install those two things. So a lot of times when it changes one or both of those it will cause a reboot about 5 seconds in and will get you stuck in a boot loop. Next time you end up stuck on a kernel screen just pull the battery and replace it. Then use the three button combo to boot back into recovery. From there you should be able to flash your rom again and it should work without problem.

Its okay to have the OS 'deleted'. First thing you need to do is go into recovery (red devil options screen). Then go to mounts and storage, connect your phone to different computer if possible and mount your internal SD. Open up a browser on your computer and download another ROM (cm10 is stable). Drag and drop that ROM.zip unto your internal SD and flash it from recovery. Peace amigos.

Its a great relief to have such a giving crowd out there

Thank you guys for all your help! I got a rom flashed over "Helly Bean" Now the only issue I am having is the IMEI is messed up. I don't have any clue what to do now. I have tried following other posts even a video and I'm stuck! Please help!
Once again guys thank you so much cause I'm a far stretch from where I was last night where it was a blank Kernel that wouldn't install a rom.
Update:
A few minutes ago I got service w/o changing anything I got a bunch of texts I tried to make a call and lost service. I rebooted and same problem as it has been. No service and it popped up with the IMEI problem.

AllieB said:
Thank you guys for all your help! I got a rom flashed over "Helly Bean" Now the only issue I am having is the IMEI is messed up. I don't have any clue what to do now. I have tried following other posts even a video and I'm stuck! Please help!
Once again guys thank you so much cause I'm a far stretch from where I was last night where it was a blank Kernel that wouldn't install a rom.
Update:
A few minutes ago I got service w/o changing anything I got a bunch of texts I tried to make a call and lost service. I rebooted and same problem as it has been. No service and it popped up with the IMEI problem.
Click to expand...
Click to collapse
Provided the imei issue happened during the helly bean flash you should have a backup on your internal SD card. Look on your internal SD for a folder labeled backup. If you have that look in there and hopefully you'll have a folder within it labeled efs.
If you have that try downloading an app called nitrality from the play store and use it to restore that copy of your efs folder.
Like I said IF it happened because of the helly bean flash that should fix your problem. If not I don't want to tell you what you'll probably have to do....
Sent from my SGH-I897 using XDA

m1batt1 said:
Provided the imei issue happened during the helly bean flash you should have a backup on your internal SD card. Look on your internal SD for a folder labeled backup. If you have that look in there and hopefully you'll have a folder within it labeled efs.
If you have that try downloading an app called nitrality from the play store and use it to restore that copy of your efs folder.
Like I said IF it happened because of the helly bean flash that should fix your problem. If not I don't want to tell you what you'll probably have to do....
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
Ok I went and downloaded that app. I went into tools. Then selected restore efs. It popped up susscessful. Nothing else happened. What should I do next?

AllieB said:
Ok I went and downloaded that app. I went into tools. Then selected restore efs. It popped up susscessful. Nothing else happened. What should I do next?
Click to expand...
Click to collapse
Reboot then check and see if your imei matches and of you get signal again.
Sent from my SGH-I897 using XDA

m1batt1 said:
Reboot then check and see if your imei matches and of you get signal again.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I have rebooted. Nothing has changed. Although this freak thing happens ocasionally. I get service for about 2 minutes then it will go away. It has happened 2 times today once before that efs restore and once after. I blew off the sim card ant that was not it. IK it's not AT&T's tower because before this I would get full signall 24/7.

m1batt1 said:
Reboot then check and see if your imei matches and of you get signal again.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I have rebooted. Nothing has changed. Although this freak thing happens ocasionally. I get service for about 2 minutes then it will go away. It has happened 2 times today once before that efs restore and once after. I blew off the sim card ant that was not it. IK it's not AT&T's tower because before this I would get full signall 24/7.

AllieB said:
I have rebooted. Nothing has changed. Although this freak thing happens ocasionally. I get service for about 2 minutes then it will go away. It has happened 2 times today once before that efs restore and once after. I blew off the sim card ant that was not it. IK it's not AT&T's tower because before this I would get full signall 24/7.
Click to expand...
Click to collapse
And you did check that you have a backup?
Sent from my SGH-I897 using XDA

Thanks all you guys btw!

m1batt1 said:
And you did check that you have a backup?
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
Yes I have the backup. It is on the SD card Backup/efs

AllieB said:
Yes I have the backup. It is on the SD card Backup/efs
Click to expand...
Click to collapse
Ok I did some playing and actually went in and deleted my efs folder. I did this because I've personally never had the issue so I wanted to see what I could do to understand it better.
So like you Nitrality didn't do me any good so I apologize for pointing you in that direction.
What did work for me is I went in with a file explorer and simply copied all the files in the backup /efs folder directly into the root /efs folder where they should be. I then rebooted into recovery and fixed permissions. Then rebooted normal and all was good.
Now keep in mind that helly bean was the rom that made that backup for you. So if by some chance in your flashing process, a rom that you flashed prior to helly bean caused the issue then the efs backup you have could be corrupt as well. But for now we'll assume it is good and go from there.

Efs problems are best fixed by going back to stock.

m1batt1 said:
Ok I did some playing and actually went in and deleted my efs folder. I did this because I've personally never had the issue so I wanted to see what I could do to understand it better.
So like you Nitrality didn't do me any good so I apologize for pointing you in that direction.
What did work for me is I went in with a file explorer and simply copied all the files in the backup /efs folder directly into the root /efs folder where they should be. I then rebooted into recovery and fixed permissions. Then rebooted normal and all was good.
Now keep in mind that helly bean was the rom that made that backup for you. So if by some chance in your flashing process, a rom that you flashed prior to helly bean caused the issue then the efs backup you have could be corrupt as well. But for now we'll assume it is good and go from there.
Click to expand...
Click to collapse
I did the copy and paste with the recovery file manager. I then backed out and fixed permissions. rebooted. nothing has changed.

korockinout13 said:
Efs problems are best fixed by going back to stock.
Click to expand...
Click to collapse
AllieB said:
I did the copy and paste with the recovery file manager. I then backed out and fixed permissions. rebooted. nothing has changed.
Click to expand...
Click to collapse
Then I'm afraid to tell you that the only other way I know to get your efs and imei corrected is to flash back to stock again as stated before...

m1batt1 said:
Then I'm afraid to tell you that the only other way I know to get your efs and imei corrected is to flash back to stock again as stated before...
Click to expand...
Click to collapse
Dang I have too try that.

[Q] lost imei

I have nexus 6 in Canada.
I had android 5.0.1. I know it was 5.0.x stock - not OTA updated.
I decided to install chroma rom using the thread here.
http://forum.xda-developers.com/nexus-6/development/rom-chroma-01-11-2015-t3000003
I installed twrp, and chroma.
I followed the instructions and it worked.
I didn't flash a radio myself. just the chroma rom, gapps, and supersu.
It worked yesterday.
This morning I got a message that android phone app stopped.
I could not make phone calls or sms.
I didn't put much thought into the error message.
I wanted something more stock and I just installed lightrom.
I only installed lightrom, no other flashing.
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
The problem persists -- no phone calls or sms.
now:
I looked at my about phone in the settings and it says unknown IMEI.
Any pointers to how I can fix this?

Did you flash correct radio ?
Can you see your imei ?
If nothing works flash latest stock.
Sent from my Nexus 6 using XDA Free mobile app

What does it say when you type *#06* into the dialer

I see unknown imei in settings about phone status imei info.
I didn't flash a radio individually. I don't know if one of the roms flashed a radio with it.
androiduser2011 said:
Did you flash correct radio ?
Can you see your imei ?
If nothing works flash latest stock.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse

ricey1986 said:
What does it say when you type *#06* into the dialer
Click to expand...
Click to collapse
Update:
I had made a twrp backup of the efs partition. I restored it.
Now the phone calls, sms, and everything works.
Anyone know why it lost the imei?
It was working, I didn't flash anything but the imei disappeared.

david1212 said:
Update:
I had made a twrp backup of the efs partition. I restored it.
Now the phone calls, sms, and everything works.
Anyone know why it lost the imei?
It was working, I didn't flash anything but the imei disappeared.
Click to expand...
Click to collapse
hi david,
i have same problem, lost my imei, and unknown baseband
can you upload "twrp backup of the efs partition" please...
i hope that can help me too

david please share efs backup from twrp, hope it help others

His efs backup will not help others. It is unique to his device and will only work for his. Its basically a I'd number. Loosing an imei is serious stuff and makes your phone useless. I'm glad you had a backup. Now I'm curious how so it don't happen to others. Flashing radios won't wipe efs.
Sent from my Nexus 6 using XDA Free mobile app

Should I make backup of EFS partition from time to time? Is it change? Is it depend on ROM? I made a backup after I unboxed Nexus. I have EFS backup on my phone, notebook and external hard drive... I hope it is safe

I had the same issue with a Galaxy S5 a while ago, I had to search and find a IMEI repair tool, which I don't think you will find on XDA as it can be used for bad purposes. But they are out there.

You only need 1 backup but the question is how this is happening. I see a lot of threads about it. So its an issue that we all need to figure out how and get preventative measures figured out
Sent from my Nexus 6

From what I've heard, if you flash all of the stock components through ADB (ROM, bootloader, modem, etc), it will trigger a rebuild of the EFS. I'm not 100% sure of this, but I remember reading something along those lines. I believe the phone has a backup partition for the EFS (which contains the IMEI, MAC Addresses, etc).

Product F(RED) said:
From what I've heard, if you flash all of the stock components through ADB (ROM, bootloader, modem, etc), it will trigger a rebuild of the EFS. I'm not 100% sure of this, but I remember reading something along those lines. I believe the phone has a backup partition for the EFS (which contains the IMEI, MAC Addresses, etc).
Click to expand...
Click to collapse
That sounds fantastic. It should be that way.
Sent from my Nexus 6 using XDA Free mobile app

david1212 said:
Update:
I had made a twrp backup of the efs partition. I restored it.
Now the phone calls, sms, and everything works.
Anyone know why it lost the imei?
It was working, I didn't flash anything but the imei disappeared.
Click to expand...
Click to collapse
upload please...please...please...

henhida said:
upload please...please...please...
Click to expand...
Click to collapse
As others have said. The EFS backup is unique to my device. It won't help you with yours.

If you absolutely cannot regenerate it with the method I said, warranty service is your best bet.
Sent from my SM-N900T using Tapatalk

Never tried this myself, but here is a guide for imei recreation on a Samsung device. At the very least it will give you an idea of some additional things you might try.... http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
Sent from my Nexus 6 using Tapatalk

Emei Null... EFS folder deleted

Hi,
I am in India and just purchased an unlocked t mobile note 4 yesterday.
I rooted it and installed Maximum Overdrive ROM. Now EMEI is gone and shows null. I did do a backup of efs using Dr. Ketan EFS backup app but somehow the folder got deleted.
Please suggest if there is any way to recover the emei? Please suggest. THANKS

Isn't the IMEI number located under the battery?

it is there... but since its shows null when I check by *#06# phone is not reading the SIM card... says SIM card is not registered
Its an unlocked T mobile phone
AlkaliV2 said:
Isn't the IMEI number located under the battery?
Click to expand...
Click to collapse

kanu1and said:
it is there... but since its shows null when I check by *#06# phone is not reading the SIM card... says SIM card is not registered
Its an unlocked T mobile phone
Click to expand...
Click to collapse
I'm not comfortable giving you any advice at this point because you're clearly using this phone in an international unlocked way and any advice I could provide could lead to further damage. You can Google Search "Restore IMEI without EFS Backup" and find guides that will help, but if you decide to follow them that will be on you. Sorry I can't be of more assistance.

Thanx for reverting mate... got it fixed... flashed stock kitkat old version and everything is working fine now... :good:
AlkaliV2 said:
I'm not comfortable giving you any advice at this point because you're clearly using this phone in an international unlocked way and any advice I could provide could lead to further damage. You can Google Search "Restore IMEI without EFS Backup" and find guides that will help, but if you decide to follow them that will be on you. Sorry I can't be of more assistance.
Click to expand...
Click to collapse

Glad to hear everything is working fine now, if possible make a brand new EFS backup and store it off the phone. I have tried different apps and by default most store the folder in the phone (which doesn't make any sense) so i had to manually export it. I am currently using EFS Manager(IMEI)-Note4 which lets you backup to the SD and cannot recommend it enough.

did that already mate... this time I have copied complete folder as well using root explorer...
cant take chances
Sent from my SM-N910T using Tapatalk

Note 4 imei null
I have same problem, how did you fix it? Please share, thnx

Flash stock ROM reroot and flash custom... that should fix the issue
Sent from my SM-N920G using Tapatalk