Database Develop

Galaxy S I-9000 IMIE & Phone : unknown

My Mobile is I-9000, I installed an Arabic version JPJPM 2.2.1 on Uk version and mobile restart normally with IMIE & Phone version readable after I closed and restarted the mobile not recognized the phone version and IMIE and give unknown.
I make a recover using the three bottoms and restart the mobile reads Phone Version and IMIE No. and when close and start the mobile back to give phone version and IMIE unknown.
In some forums give the solution to check clear EFS and boot loader update like you see or Download EZbase and flash
I am afraid to do that, please tell me the solution

Read the post .
http://forum.xda-developers.com/showthread.php?t=881162
jje

Reading
I hope to find the solution there

Not working
Please help

Where are the experienced people to tell the right solution to follow
check clear EFS & boot loader and upgrade or Only check EFS
Please help

You can find imei under the battery.

ayman_salah said:
Where are the experienced people to tell the right solution to follow
check clear EFS & boot loader and upgrade or Only check EFS
Please help
Click to expand...
Click to collapse
I am not 100 percent sure, but I see no reason to mess with the bootloaders. Flash the new ROM with Clear EFS checked, and I THINK it will restore your IMEI. It has done so with others.
At this point, you have nothing to lose by trying.

do not clear your efs without making a backup of your efs first.

Just flash the rom from your carrier (www.samfirmware.com) that the phone came with, and you should have proper iemi.

fooman123 said:
do not clear your efs without making a backup of your efs first.
Click to expand...
Click to collapse
His efs is already fragged...so silly to back it up. He is trying to restore it.

Don't clear your EFS. You might still have the backup files in there. If you open your efs in root explorer or an adb shell and have .bak files you need to delete the nv_data.bin and nv_data.bin.md5 files, reboot the phone and it should recreate the files from the backups.

Flash CM7. It's been reported to regenerate IMEI, but ONLY if you keep on using CM7 or MIUI. Any attempt to go back to stock will remove the IMEI.

It does not sound like is efs is totally fragged from his original post. Backing up /efs is easy -- after clearing efs there is no way to regenerate the nv_data.bin (that I know of) without a backup.

rschenck said:
I am not 100 percent sure, but I see no reason to mess with the bootloaders. Flash the new ROM with Clear EFS checked, and I THINK it will restore your IMEI. It has done so with others.
At this point, you have nothing to lose by trying.
Click to expand...
Click to collapse
I will try to do that as you said above "It has done so with others"
Wish me luck

ayman_salah said:
I will try to do that as you said above "It has done so with others"
Wish me luck
Click to expand...
Click to collapse
Good luck, though the consensus of I am sure smarter types than I seems to be that you should take a copy of your efs folder before doing anything...and that seems wise to me, just in case.

How to get lost imei back?

Guys, I called the service centre guy and this is the reply I got. I have not tested this. Any one can test it and tell me. If you think the service guy was posting a bad joke with me, I well delete this thread.
First, you need
A phone with the imei number.
You can also use this method to backup your files if you want to restore your imei number in the future.
Now connect the good phone via usb debug mid and open adb
Then, type the following.
Code:
Adb shell
dd if=/dev/block/mmcblk0p1 of=/sdcard/ilostit.dd
this will backup mmcblk0p1file
Follow until this step, if you want to backup.
Now go back to your phone without the imei number
Then move the back up to the sdcard
Then follow these command
Code:
umount /efs "unmount /efs
dd if=/sdcard/ilostit.dd of=/dev/block/mmcblk0p1
reboot
That's it!
Sent from my GT-I9003 using xda premium
Sent from my GT-I9003 using xda premium

Really a very...very useful post. Bro but is this method useful when we lost imei or before loosing our imei number? Bcoz if this method is for before loosing imei then we have nitrality app. But if we lost imei & in that case if it is helpful then its an awsome trick bro.

vishal24387 said:
Really a very...very useful post. Bro but is this method useful when we lost imei or before loosing our imei number? Bcoz if this method is for before loosing imei then we have nitrality app. But if we lost imei & in that case if it is helpful then its an awsome trick bro.
Click to expand...
Click to collapse
You first need to backup the files as I said in the post. You can later restore three backup and get back you imei.
Sent from my GT-I9003 using xda premium

Thanx bro...but suppose someone forget to backup those file the any solution we have?

vishal24387 said:
Thanx bro...but suppose someone forget to backup those file the any solution we have?
Click to expand...
Click to collapse
Just pray god for a miracle to happen! It is better you back up now! And no other solution I think..even samsung uses this thing
Sent from my GT-I9003 using xda premium

Code:
Adb shell
dd if=/dev/block/mmcblk0p1 of=/sdcard/[B][U]ilostit.[/U][/B]dd
this will backup mmcblk0p1file
Click to expand...
Click to collapse
I LOST IT ???
The rest of the code looks ok but putting that in to recover IMEI ?
Thats sounds like a joke to me lol

Not sure but i doubt it

ql to know.i was looking for that.

Dude, It is for the backup files.Anybody can try it out if they loose their IMEI. Also, the samsung guy was surely not joking about it, I believe. Plus,ilostit.dd is the backup file..,,and when Samsung restored my IMEI, see gave me the ilostit file..It is in my SD card now and he advised me to follow this method itself...

Just flash modem via odin,help in 95%

Wouldn't there be two identical IMEI's in this case, or am I mistaking?

How on earth is it posible to lose your IMEI?
Just dial *#06#

I keep asking myself that, the IMEI number suddenly got blank/unknown, no idea why.

thakrage said:
How on earth is it posible to lose your IMEI?
Just dial *#06#
Click to expand...
Click to collapse
You can loose your IMEI if flashing went wrong!!!!

Just flash modem with odin and than you have you imei back

Just flash a stock rom via Odin.. that definitely work.. not too sure about just flashing the modem.
Insanity CM

Jason123420 said:
Just flash a stock rom via Odin.. that definitely work.. not too sure about just flashing the modem.
Insanity CM
Click to expand...
Click to collapse
Well, not always! I tried it for i9003 when I lost my IMEI!

Help...sorry.
Sorry my first post is a cry for help and a 'bump' at that...
Using a Galaxy S I9000, with no IMEI folder in EFS and the 00499... IMEI issue.
The phone was last used to uninstall an app and then 'crashed', resulting in no network.
It is running 2.3.5 XFJVA, CFW (do you need the numbers - if so, which ones?).
I've managed to reconnect to the network but still cannot get the calls and MMS to work.
I've tried your method, bangalorerohan, and have issues.
The first process takes forever, (didn't realise it was a 4gb file) and a message tells me it is writing but 'file too large' and copied 8388609 +0 records in and 8388607 +1 records out.
How do I know if this is working correctly?
After the 'dd if=/sdcard/ilostit.dd of=/dev/block/mmcblk0p1', I just get '>'.
Do I have to wait for something to happen...looks like I just added a line ready for the phone to read, from what I've read?
When I reboot the phone, nothing seems to have changed and the old 0049... IMEI is still there.
There is no IMEI folder in the EFS.
Thanks for taking the time to post a method...
Also, out of interest, why does the working phone give a '#' sign when connected after "adb shell", but the non-working phone give a '$'?

Hi Podgkin,
$ is normal user's prompt in Unix/Linux and so Android console.
# is root (superuser or administrator) prompt.
To make yourself root (superuser) you must have rooted phone.
You may try to issue the following command in the console:
Code:
su
And it will make you root if it is supported on your device (e.g. your device is rooted with patched su executable).
But!!! I would strongly advise to not do this procedure because EFS partition is not 4GB!!! E.g. on my SGS+ GT-I9001 it is around 5 Mb, no more.
First of all you should find exact model of your phone and look up the correct partition for efs e.g. in xda wiki.
Or just issue "mount" command - it should show what is the actual partition behind /efs.
This means that you've tried to copy wrong partition! Not EFS but something else. If you'd succeed in restoring this wrong data into right place you'll irreversibly destroy data that you've had.
Regards,
Andres

Thanks for coming back so quick, andres_a.
But the file created by banagalorerohan's...
dd if=/dev/block/mmcblk0p1 of=/sdcard/ilostit.dd
...is 4gb. (the ilostit.dd file)
Currently, there is only the 'restored by Android' EFS files available...this is the problem.
I need the IMEI folder restored, hence my use of the above.
And the phone is rooted as it is running CFW.
My trouble is getting the 'broken' phone to run/accept/recognise the ilostit.dd file, to see if that can help - I think?

SGN N7000: Help needed with repartitioning efs to ext 4 and error mounting efs??

I have tried to find more about my situation but asking seems to be the only way since all the info is either scattered or not available!
For two weeks I've been trying to fix my note from this ics emmc bug which made me loose efs folder and I have tried several methods with no luck, so I thought that repartitioning sd might kill the bug, so I repartioned just (parts)7,9,10,11 and also went for efs part that was empty anyway thought it might clear bad blocks, although afterwards I flashed efsfix.zip from another thread on here somewhere, because of which network and everything works just no lock screen and power button dialog? And when I flash any rom stock/custom it says (in red) error mounting efs, I found a solution for that by using terminal emulator and commanding "mount", But gotta do it manually afer every reboot?
And my imei is not the same as under my fone, how could I manually edit the imei and insert original fone info?
Could anyone help or guide me to a link so that I can recreate efs partition to ext 4 and the sort out other issues?
Edit: info in-depth!!
Thanks!

Does anyone know how to create/recreate an efs ext 4 partition on galaxy note? Is there a command or certain way to mount efs part as ext 4?

without efs backup you have lost your emei. Unless you resort to illegal methods in most countries (expensive z3x box)
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it.
Anyway, how did you analyze its efs thats corrupted, cause if you can flash gb from pc odin succesfully its not super bricked
Sent from my GT-N7000 using Tapatalk 2

recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
That emei stuff is so overrated by secret agencies.
Sent from my GT-N7000 using Tapatalk 2

Thanks for the reply baz77.
Basically, I wasnt aware of this emmc wipe bug when I bought Note, I got my rom flashing experience and knowledge from SGS2, so after like a week of purchase I tried to flash ICS stunnner on my Note with squeaky clean, but resulted in getting my fone back from samsung after being revived, took 3weeks to return.
At this point I still didnt know about the bug because I had assumed that my own doing caused the super hardbrick, till I flash a criskelo rom with a wipe and my problems started off with not registered on network, after that I have been krazily searching and flashing to have the fone working flawless again without having to send the fone back to samsung becasue of the wait and tiny chips n crack on my fone.
And I figured that efs is corrupted by googling and gathering info about my particular problem and everything pointed towards efs being corrupted!
I am really hoping for them release a fix and I can get my fone back working as a whole again!
Edit: added missing words! Lol
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + no lock screen and power button dialog!?!?

Could I plz ask, where can I get the stock gb with pit file samsung
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + No lockscreen and No Power button dialog!?!?

baz77 said:
recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
Click to expand...
Click to collapse
Apparently, pitfile and efs clear option doesn't work, I tried GB with pitfile got the red 'error mounting efs' and tried stock UK ICS 4.0.3 from (thanks to) Dr.Ketan but Ive still got the error and no lockscreen and faulty power button?!? Plus:- Sim Network is gone :banghead: , i'll just have to flash that efsfix.zip and do the terminal "mount" procedure again!!! manually!
"Probaly Leagality issues there" I'll try the same pitfile procedure with rom from another country if it doesnt work then dont really want to but guess this fone's going back to Samsung for repairs before I sell it off.
Many Thanks for your help!!
<<SUNG>>from my <<SAM>> GT-N7000

baz77 said:
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it. 2
Click to expand...
Click to collapse
I have the custom binary count reset, so they shouldnt have any problems with repairing illegally then?? With stock UK ICS 403 Rom from this forum!?!
<SAMSUNG><ASONG> From GT-N7000!

I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hey baz77,
I tried the same pitfile method with a GB236 Rom built from HongKong and flashed it twice, because I read on this forum somewhere that in the event of errors, missing files and apps after a flash, roms should be flashed atleast once more to get'em fully loaded but unfortunately even that method failed to mount the efs part.
Afterwards, I was just googling for more solutions and I decided to download and flash another GB236 rom Open europe built (wipe version) from Dr. Ketan's stock rom deposites and to my joyous surprise there were 2 extra tar. files, one named efs.md5.tar, so I quickly got my fone in download mode and flashed the rom with pitfile and when that was done, I got the fone back in download mode and Flashed the efs.tar (PDA), CSC, Modem (PHONE) and for the first time in 2 weeks the fone booted up normally as it should with the welcome screen, working lock screen and power button dialog! pheeeewwww!!!
But the imei is still not the same as under the hood, but I guess since the efs part had been corrupted, my fones probabaly using the emergency imei, Im using Alliance v1 with no apprent faults or errors.
i'll flash the GB Rom and try the factory rest code method by you and if it works then dont have to go to samsung and if doesnt then i'll keep using the fone as it is for as long as I have it and keep looking for solutions, if nothing happens then i'll get it sorted from samsung before selling it.
Your help is much appreciated, Thanks baz77!!! :thumbup: :thumbup:
<SAMSUNG><ASONG>from<GT-N7000

back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:

letters_to_cleo said:
back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:
Click to expand...
Click to collapse
Hi Letters_to_cleo,
Thank you for the suggestions mate, at the moment Im on Alliance v.1 403 rom, and I have just tried the fix from your link, did the steps1 & 2 restarted checked imei and it's the same serial (#to#) as you have stated, then i tried the step 3 which indicated that the nv_data.bin file is missing from that folder.
I have already gone to certain extents to return the fone in its generic state, so it won't matter if I tried once more besides trying repairs on GB rom is probably much safer then on ICS builts as long as the fone doesnt die on me,(completely again!), I 'll try your 2nd method in a bit and report back after!
Thanks for the support!!:thumbup:
<SAMSUNG><ASONG>from<GT-N7000

yeah that app wont work if you dont have efs backup. It distills from original. bak file the emei, now with the reflash of efs, even before you had lost it. only generic stuff left.
you need as mentioned before to go to samsung to repair emei, or find a phone place that can do it. You can yourself but in most countries its illegal. You need z3d box or equivalent for that, 150$$$$ lol, I have seen people who bought it offer that service for small fee. But be careful as ot could be illegal in your country, even if its going from generic emei to original emei lol.
Oh and you are welcome, been there done that, with the efs stuff. Samsung fixed mine.
My help is free, now if another has this you know how to help them
After Samsung fixes it,stay on gb, root phone and backup efs on multiple locations(pc, cdrom, floppy disk, bank vault you get it) In future when you buy android do that first. How to is in dr ketans toolbox thread in general section.
edit efs backup is not in nandroid, nor titanium backups. In fact still to date there is not one solution that can back everything up on your phone.
Sent from my GT-N7000 using Tapatalk 2

letters to cleo, corrupt emeis are empty or 0000000000000000000000000,
the 490000 emei is given when resetting efs. That is not corrupt anymore to my knowledge
Sent from my GT-N7000 using Tapatalk 2

oh I ran into missing lockscreen issues after fully fixing it, I have in my profile then statistics started a thread which links to a solution for that
Sent from my GT-N7000 using Tapatalk 2

Hi Enseven reporting,
@Letters_to_cleo, the methods you suggested dont work but thanks for trying to helping, i didnt find the bak file in efs folder but there 2 nv_data files, and they're both dated from Jan2011, renaming them just disable's the network and doent change the imei#, it remains the same!
@baz11, Yes mate, you are right this fone's going back to samung bcuz im not looking to $pend 150 on some box that I wont even use twice.
Im not really that fussed about imei not being as same on fone hardware, just as long the fone works, but like you said it probably is illegal to sell a fone with messed up serial no.
And on top of that fone's price would drop for having software issues, only wanted to fix it so that I could sell it on without loosing much $$ from the original price I paid for it, it'll be disapointing since Ive only had the fone for just over 2 months.
And I did manage to fix the welcome/lockscreen/power button issues by flashing efs.tar I got from that wipe version Open Europe Rom but even after the flash, it restore's the needed files but doesnt really prompt the features so I gotta insert this command through terminal emulator: "echo n- ON> /efs/imei/keystr" "sync"and factory reset, then the fone reboots normally with everything working but the IMEI ofcourse!
Wonder if your lockscreen fix works ive looked for it on your profile's statistic's tab but uable to find it, could you plz provide a link. Thanks
Ive tried all methods with some luck and no further progress apart from having to buy expensive equipment, so I guess i'll keep using the fone and looking for any miraculous solution till I resort to Samsung.
P.S: If they cant find a fix for the emmc bug by working on scripts , they should atleast invent a nano tech powder (gadget bug killer) to sprinkle on the motherboard, LOL!!!
because this problem goes way back, like another user said on here you could make a movie about now, and ithink it started off as a scifi now its a scifi/thriller, "shall I wipe before flashing & risk hardbrick Or shall I wait for samsung to pace up the support!!!
Thanks to xda and memebrs for being online 247 and all the support though!!
<SAMSUNG><ASONG>from<GALAXY-GTN7000>using xda premium!!!

Hi En7,
Sorry to hear my steps didn't work on your phone bud.
I checked some forums here in XDA and I've come across this one: http://forum.xda-developers.com/showthread.php?t=1804117. (I'm not sure though if you have come across that link before or not).
It is for the S3 forum but there's a tool in there that you can try to download and run to somehow restore your corrupted IMEI. It's worth taking the risk I should say but who knows..any given tool/info is highly useful and it could be a clear shot in bringing back your original IMEI back right?
Cheers bud!

lol that cracked me up nano powder hahaha good one.
you found the lockscreen fix, its the same fix I found while back from some guru.
I guess you can change emei to original with someone who has such a box. Finding is not to difficult, just need to go to a shop that can repair emei. Preferably Samsung thought, Just go to a samsung service centre, or store where you bought phone. Best unroot and put stock firmware that matches your phones original csc, to avoid anoying questions. Just tell the truth you updated phone and emei was gone/changed and you want original imei back. Samsung can fix it. Note, this time dont use pit or clear csc. Its not needed anymore.
I searched hard and long when I had that issue with emei, wasnt without a backup able to change it back to original, other then Samsung or such a box.
It annoyed the crap out of me. I can relate to what you were going through.
Everybody is nandroid this titaniun backup that, apparently efs is the only thing not standardly backed up with any standard mainstream solution.
Sent from my GT-N7000 using Tapatalk 2

oh, and good idea, maybe you should write a scifi thriller
Sent from my GT-N7000 using Tapatalk 2

Software IMEI doesnt match Hardware IMEI

Hows it going guys. Been using a Captivate now for a month (mostly on CM9, CM 10 as of a yesterday) and now I am being told I ahve an IMEI error. I have ALWAYS had issues with this phone as far as data connection goes (sometimes I can only use Opera as a browser) and maybe this has been the main problem. The software IMEI does not match the number behind the battery door. Is this a problem that AT&T would fix?

sjorge3442 said:
Hows it going guys. Been using a Captivate now for a month (mostly on CM9, CM 10 as of a yesterday) and now I am being told I ahve an IMEI error. I have ALWAYS had issues with this phone as far as data connection goes (sometimes I can only use Opera as a browser) and maybe this has been the main problem. The software IMEI does not match the number behind the battery door. Is this a problem that AT&T would fix?
Click to expand...
Click to collapse
You can restore your IMEI by going back to stock KK4 with Odin (or Heimdall). Or if you have a backup of your efs folder (highly suggested).
You can go back to CM10 after without any problem. KK4 -> flash Corn kernel -> Flash CM10 and Gapps.
Hopefully your IMEI will stay fine but if not, you have your efs backup so just swap it by either mounting system or with a root explorer.

And usually to prevent additional mismatches in IMEI, it's advised to remove the SIM card before flashing. I haven't had a problem doing that.

So i apparently made a big mistake. I simply flashed back to stock kernal while still running CM10, so that obviously messed things up. I then use oneclick un brick and went back to 100% stock. While running Keis to update back to gingerbread, the update failed and now I have the phone ! computer screen showing. Neither my laptop nor my desktop are recognizing the device. What should I do now?

sjorge3442 said:
So i apparently made a big mistake. I simply flashed back to stock kernal while still running CM10, so that obviously messed things up. I then use oneclick un brick and went back to 100% stock. While running Keis to update back to gingerbread, the update failed and now I have the phone ! computer screen showing. Neither my laptop nor my desktop are recognizing the device. What should I do now?
Click to expand...
Click to collapse
Search before posting? lol
Here it is: http://forum.xda-developers.com/showthread.php?t=1953930
There's abolutely no reason to go back to 2.1 eclair. You should flash Odin KK4 without bootloaders when things like this happen. Now you'll have to flash Odin KK4 with bootloaders

Ok. So i have FINALLY got my phone back up and running after all sorts of issues. I found myself in a position were I had to build a jig to make this damn phone work again.
Ok so, I once again have thie IMEI conflict. I am sitting on 4.2.1 AOSP Jelly Bean. I installed everything without having the sim card in this time, so now I am unsure why this error occurred. I can use my phone to make calls, send texts, and use the internet, so im not really sure what it's deal is. All i know is that I don't want to be stuck using my old blackberry again, so I am going to make sure I know the correct steps to follow to fix this.

sjorge3442 said:
Ok. So i have FINALLY got my phone back up and running after all sorts of issues. I found myself in a position were I had to build a jig to make this damn phone work again.
Ok so, I once again have thie IMEI conflict. I am sitting on 4.2.1 AOSP Jelly Bean. I installed everything without having the sim card in this time, so now I am unsure why this error occurred. I can use my phone to make calls, send texts, and use the internet, so im not really sure what it's deal is. All i know is that I don't want to be stuck using my old blackberry again, so I am going to make sure I know the correct steps to follow to fix this.
Click to expand...
Click to collapse
I believe I mentioned this before but when flashing to stock KK4, you should make a backup of your efs folder. It contains your IMEI and restoring your backup would fix your problem.

so, just to be clear. I just need to flash the stock KK4 kernal to my phone to fix the IMEI number? I would use odin to do this right?
Sorry for all teh noob questions. I just dont wanna end up in the same terrible situation i got myself into last time.

sjorge3442 said:
so, just to be clear. I just need to flash the stock KK4 kernal to my phone to fix the IMEI number? I would use odin to do this right?
Sorry for all teh noob questions. I just dont wanna end up in the same terrible situation i got myself into last time.
Click to expand...
Click to collapse
You'd need to use Odin KK4 to get back to stock, make a backup of your efs folder, flash Corn kernel and then flash the ROM you wanna use.

BWolf56 said:
You'd need to use Odin KK4 to get back to stock, make a backup of your efs folder, flash Corn kernel and then flash the ROM you wanna use.
Click to expand...
Click to collapse
Thanks! I for some reason thought this is what I tried to do before, when it ended up crashing my phone. The stock kernel will run with what ever custom rom I still have installed?

sjorge3442 said:
Thanks! I for some reason thought this is what I tried to do before, when it ended up crashing my phone. The stock kernel will run with what ever custom rom I still have installed?
Click to expand...
Click to collapse
Odin KK4 is a ROM, it will bring you back to stock GB. From there, you'll have to follow the steps I posted above.

so ive been having issues with my phone as I've been too busy to reset to the stock rom. Is this what I should be using? With or without bootloaders? forum.xda-developers.com/showthread.php?t=1386924

sjorge3442 said:
so ive been having issues with my phone as I've been too busy to reset to the stock rom. Is this what I should be using? With or without bootloaders? forum.xda-developers.com/showthread.php?t=1386924
Click to expand...
Click to collapse
Without bootloaders if you're already on GB or higher.

ok. So i have sucessfully created backups of my EFS folder using both EFSPro and Super Manager. Problem now is that I cannot get EFSPro to recognize that my captivate with HellyBean installed is connected to me PC. Also, Super Manager will not allow me to paste my copied EFS folder into the directory. What should I do now?
EDIT: Alright, So I flashed to stock, flashed a semaphore kernel and then installed CM9.1. From here after connecting and disconnecting the phone a few times I was able to get EFSPro to push the recovery tar to my phone. It reboot, but when I check the IMEI, it still is the generic one.

sjorge3442 said:
ok. So i have sucessfully created backups of my EFS folder using both EFSPro and Super Manager. Problem now is that I cannot get EFSPro to recognize that my captivate with HellyBean installed is connected to me PC. Also, Super Manager will not allow me to paste my copied EFS folder into the directory. What should I do now?
EDIT: Alright, So I flashed to stock, flashed a semaphore kernel and then installed CM9.1. From here after connecting and disconnecting the phone a few times I was able to get EFSPro to push the recovery tar to my phone. It reboot, but when I check the IMEI, it still is the generic one.
Click to expand...
Click to collapse
You could simply make a copy of your efs folder and use a root explorer to switch it if your IMEI doesn't match.

so the efs folder i backed up with Super Manager cannot be restored by Super Manager? If I have to buy root explorer, thats not a big deal, but if i dont, well then its silly to purchase it it. Root explorer will however allow me to restore the efs folder that I have backed up onto my pc?

sjorge3442 said:
so the efs folder i backed up with Super Manager cannot be restored by Super Manager? If I have to buy root explorer, thats not a big deal, but if i dont, well then its silly to purchase it it. Root explorer will however allow me to restore the efs folder that I have backed up onto my pc?
Click to expand...
Click to collapse
I suggest root browser lite. It is the best root explorer I've personally used and its free.
Sent from my SGH-I897 using xda app-developers app

sjorge3442 said:
so the efs folder i backed up with Super Manager cannot be restored by Super Manager? If I have to buy root explorer, thats not a big deal, but if i dont, well then its silly to purchase it it. Root explorer will however allow me to restore the efs folder that I have backed up onto my pc?
Click to expand...
Click to collapse
m1batt1 said:
I suggest root browser lite. It is the best root explorer I've personally used and its free.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
There are a few free root explorers out there, I personally use Root Explorer but you can use a free one. It only needs root right.

ok so I am still having issues over here. I have efs folder that I backed up with Super Manger while I was still on Gingerbread right after rooting with a working IMEI. It has three files and one folder in it. an empty IMEI folder, a Cryptprop_onetimeboot, cyrptprop_securewipe data, and nv text document. When I used root explorer light to copy the backup folder to the current efs folder, I found about 7 files there. I deleated them, pasted the backup folder contents and restarted my phone and I still have the generic IMEI. There was also a folder in current efs folder called lost and found which I cannot deleat.

sjorge3442 said:
ok so I am still having issues over here. I have efs folder that I backed up with Super Manger while I was still on Gingerbread right after rooting with a working IMEI. It has three files and one folder in it. an empty IMEI folder, a Cryptprop_onetimeboot, cyrptprop_securewipe data, and nv text document. When I used root explorer light to copy the backup folder to the current efs folder, I found about 7 files there. I deleated them, pasted the backup folder contents and restarted my phone and I still have the generic IMEI. There was also a folder in current efs folder called lost and found which I cannot deleat.
Click to expand...
Click to collapse
Did you verify the backup you made before flashing? The IMEI shouldn't be empty so I'm thinking you got a bad backup.
Are you getting any error with your generic IMEI?

[Q] Disable IMEI check on Jelly Bean ROMs

Hello guys
Is there a way to disable "Wrong IMEI Notification" on system startup?
I know how to restore IMEI, but my network works fine with generic IMEI, so I don't care about it much.
The only thread I was able to find is here:
http://forum.xda-developers.com/showthread.php?t=1862416
It's about 4 months old and no answer is given.
Currently I'm running Helly Bean 4.2.1 (Release - 05.01.13)
Thanks in advance

archildroid said:
Hello guys
Is there a way to disable "Wrong IMEI Notification" on system startup?
I know how to restore IMEI, but my network works fine with generic IMEI, so I don't care about it much.
The only thread I was able to find is here:
http://forum.xda-developers.com/showthread.php?t=1862416
It's about 4 months old and no answer is given.
Currently I'm running Helly Bean 4.2.1 (Release - 05.01.13)
Thanks in advance
Click to expand...
Click to collapse
It's cooked into the system apps, so unless someone has the knowledge to change it, the answer is no.
Fixing the problem is quite easy though and takes 15min at most after a good TiBu backup, if it gets too annoying, take that extra 15min

BWolf56 said:
It's cooked into the system apps, so unless someone has the knowledge to change it, the answer is no.
Fixing the problem is quite easy though and takes 15min at most after a good TiBu backup, if it gets too annoying, take that extra 15min
Click to expand...
Click to collapse
I flashed "i897uckk4 Odin One Click NO Bootloaders, Re-partition, Full Wipe" - IMEI is still some generic 0049...
What should I do now?

archildroid said:
I flashed "i897uckk4 Odin One Click NO Bootloaders, Re-partition, Full Wipe" - IMEI is still some generic 0049...
What should I do now?
Click to expand...
Click to collapse
Is it still giving you the error msg?
Is your phone a refurb?

BWolf56 said:
Is it still giving you the error msg?
Is your phone a refurb?
Click to expand...
Click to collapse
I was on Helly Bean 4.2.1 and it was giving me an error message because of wrong IMEI.
I didn't have efs backup, so I backed up everything and flashed stock kk4 assuming that it would restore my IMEI, but it's still 00499...
So how do I restore my IMEI?
No it's not refurbished.

archildroid said:
I was on Helly Bean 4.2.1 and it was giving me an error message because of wrong IMEI.
I didn't have efs backup, so I backed up everything and flashed stock kk4 assuming that it would restore my IMEI, but it's still 00499...
So how do I restore my IMEI?
No it's not refurbished.
Click to expand...
Click to collapse
That's actually how you restore your IMEI.. By flashing Odin KK4. Did you restore anything after flashing?
I went ahead and did a little google search (which can go a long way ). Here's what I got: http://forum.xda-developers.com/showpost.php?p=24175451&postcount=2

BWolf56 said:
That's actually how you restore your IMEI.. By flashing Odin KK4. Did you restore anything after flashing?
I went ahead and did a little google search (which can go a long way ). Here's what I got: http://forum.xda-developers.com/showpost.php?p=24175451&postcount=2
Click to expand...
Click to collapse
First I flashed Odin kk4 - wrong IMEI, reflashed few times, no luck. Than Eclair, Froyo - same result
Guide mentioned above didn't help, there were no files in /data/radio, and there is no folder /factory, or /data/factory. I copied nv_data.bin from /efs to /data/radio set chmod 700 but it didn't change anything.
Any more ideas?
Seems like I'm just unlucky (
Now flashed back to HellyBean 4.2.1, restoring backups...

archildroid said:
First I flashed Odin kk4 - wrong IMEI, reflashed few times, no luck. Than Eclair, Froyo - same result
Guide mentioned above didn't help, there were no files in /data/radio, and there is no folder /factory, or /data/factory. I copied nv_data.bin from /efs to /data/radio set chmod 700 but it didn't change anything.
Any more ideas?
Seems like I'm just unlucky (
Now flashed back to HellyBean 4.2.1, restoring backups...
Click to expand...
Click to collapse
Umm Your file explorer probably doesn't have root rights if you can't see those or you have to show hidden folders in settings.

BWolf56 said:
Umm Your file explorer probably doesn't have root rights if you can't see those or you have to show hidden folders in settings.
Click to expand...
Click to collapse
I'm using ES File Explorer (root settings were checked, permissions granted) and Yes, I rooted device (first flashed corn kernel).
Already flashed HellyBean 4.2.1 (10JAN13). Will take a chance after restoring backups.

Just tried to do like described in the link - folder /data/radio is empty for me, unable to find /factory folder
I wonder why flashing stock kk4 didn't restore IMEI ((
I backed up efs folder after installing Odinkk4, but I don't think it can help.
Good thing is that my carrier works just fine no matter IMEI
Anyway, thanks for trying to help me out. :good:

@archildroid, Josh at Mobiletechvideos.com I believe can restore your imei without having a back up. There will be a charge for it, but next to Adam Outler, you won't find a better set of tech fix it hands.
Sent From The Land Of Frag

I have tried lots of methods to restore my IMEI, but no luck.
One thing I encountered: This wrong IMEI popup has "Galaxy S Settings" icon in the corner, so I froze it with Titanium and the popup disappeared.
Of course you lose all the abilities, that Galaxy S settings have - TV Out, Color tuning etc.
I hope someone with sufficient knowledge will modify Galaxy S Settings, to disable this popup.
P.S. Before changing anything in system apps, MAKE NAND BACKUP, I'm not responsible for anything you do to your phone!

archildroid said:
I have tried lots of methods to restore my IMEI, but no luck.
One thing I encountered: This wrong IMEI popup has "Galaxy S Settings" icon in the corner, so I froze it with Titanium and the popup disappeared.
Of course you lose all the abilities, that Galaxy S settings have - TV Out, Color tuning etc.
I hope someone with sufficient knowledge will modify Galaxy S Settings, to disable this popup.
P.S. Before changing anything in system apps, MAKE NAND BACKUP, I'm not responsible for anything you do to your phone!
Click to expand...
Click to collapse
Usually, going back to stock KK4 with Odin fixes your IMEI problem. Once there, you make a backup of your efs folder and you're set for your android's life. It's a one time backup (as long as you don't delete it..) and can be restored whenever.