Related
Hi Guys,
I'm having a a big problem with my SGS SGH-i897 a few days ago, and after searching here in threads and other webs i haven't find any solution yet.
The problem starts with a rom update, i had Serendipity VII Build II and i decided to upgrade to the new Cyanogen, i used recovery mode for that. After de upgrade everything was just fine. But i really didnt like the Cyanogen rom so i decided to get back to serendipity (used odin to flash). When i flashed back to serendipity rom (VII build III) i used the files (CSC, PDA, PHONE, Reorient_Kernel_1.1) they have on the serendipity web (http://serendipity7.weebly.com/download.html).
Now here starts my problem, after first boot my phone show "Phone not allowed MM#6" and when i check out my IMEI with *#06# shows me this fake one "004999010640000". That's no my IMEI.
I start seaching here in XDA forums for help and i found out that this happends when the phone has and corrupt IMEI, or corrupt /efs/nv_data.bin file. So i did what forums recommended to do.
Here are the steps i already made.
1. I' reflash de modem.bin from original rom on (www.samfirmware.com) didn't work!
2. I' deleted /efs/nv_data.bin and /efs/nv_data.bin.md5 files (according to this guide http://dp.nonoo.hu/fixing-samsung-galaxy-s-network-problems/ phone was be able to reacred then (didn't work)
3. I flashed back to original 2.1 rom "Master Clear" using Odin3 One Click Downloader and Drivers Captivate Only from here http://forum.xda-developers.com/showthread.php?t=731989 (didn't work)
4. I made a copy of my /efs folder, then delete the nv_data.bin and nv_data.bin.md5. After that i change "bak" for "bin" of backup files files .nv_data.bak and .nv_data.bak.md5 according to this guide (http://forum.xda-developers.com/showthread.php?t=881162) that restores the files and IMEI but it didn't work
5. I edited nv_data.bin file with Hex Editor this lines:
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
and guest what? it didnt work!!
6. I tried to unlock my phone but i realized it was already unlocked.
I dont know what else to do. im' started using Android a month ago so i dont know so much about the system.
Im hopping you can help me out with this guys, what should i do?
And please post the link of guides or tutorial you suggest me to follow, as i say i'm noob with this.
Thanks!
Forever alone! :/
are you able to get into a download or recovery mode?
I would pm connexion2005 as he has alot of useful info and also can rebuild the partition.
Sent from my SAMSUNG-SGH-I897 using XDA App
bulletproof1013 said:
I would pm connexion2005 as he has alot of useful info and also can rebuild the partition.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
agreed. that may be your best bet.
Any luck?
Captivate 2.3.5
bulletproof1013 said:
I would pm connexion2005 as he has alot of useful info and also can rebuild the partition.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Agreed again. This guy brought my cappy back from the dead.
Mate,
I have the same problem. The IMEI on the phone sticker and *#06# dont match. I get same fake IMEI....Need help badly.
Regards,
http://www.mobiletechvideos.com/
There r videos here that can help u
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks everyone for answering.
I already fix my phone with SPTBox
I'm back to my stock IMEI
bulletproof1013 said:
There r videos here that can help u
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yep i followed that video guide but... it didnt work!
The RIFF Box or SPT Box fixes the fake IMEI problem.
Thanks again.
i think unlocking the phone makes it more difficult to restore.
most of the captivate owners that couldn't restore with hex edit following the written or video guide (deleting nv_data etc.) seemed to be people who had unlocked their device as well.
bames said:
i think unlocking the phone makes it more difficult to restore.
most of the captivate owners that couldn't restore with hex edit following the written or video guide (deleting nv_data etc.) seemed to be people who had unlocked their device as well.
Click to expand...
Click to collapse
Well good to know, better later than never.
and yes my phone is unlocked.
My phone's IMEI has been gone for a long time. No ramifications as of yet...
The RIFF BOX won't fix it... . But yes the SPT Box has the capability of doing it.
Sent from my GT-I9100 using xda premium
I faced the similar issue.. see the resolution here - http://forum.xda-developers.com/showthread.php?t=1230997
I tried with SPT box, but it somehow didnt work in my case. Then the repair guy tried some "Z3" and voila it was done. IMEI restored and phone started functioning normal.
How much u spent on it and where in delhi
rkkaranrk said:
How much u spent on it and where in delhi
Click to expand...
Click to collapse
About 13 dollars.
domo.kun said:
About 13 dollars.
Click to expand...
Click to collapse
domo.kun Please help me!! I'm in colombia too! I have the same problem and I did all of those tutorials but I couldn't get back my original imei Could you tell me where can i found people with the correct tools or the box that your mentioned??
Please help me!!!
Gracias!
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
So I got this Captivate to unlock for a friend of my dad's.
I followed all the usual steps, it actually worked, but in the process somehow the IMEI got messed up and throws an IMEI error after boot.
I tried all the known guides for fixing the IMEI but nothing worked.
Unfortunately, the original backup of the /efs/ folder is lost
Is there any way to fix this?
Some have been able to recover from the imei problem by flashin back to Stock Firmware and then u could back up the efs folder after the flash. U could try Stock GB 2.3.5 i897ucKK4. Look in my sig link below if u r on a pc or just go to Stock Roms - One Clicks Master Collection stickied thread in the Dev forum...Post #3
Sent from my SGH-I897 using xda premium
4-2ndtwin said:
Some have been able to recover from the imei problem by flashin back to Stock Firmware and then u could back up the efs folder after the flash. U could try Stock GB 2.3.5 i897ucKK4. Look in my sig link below if u r on a pc or just go to Stock Roms - One Clicks Master Collection stickied thread in the Dev forum...Post #3
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Already tried it twice
I did find a nandroid backup of the EFS, gonna try and work with that somehow.
Edit: Used Nandroid Explorer to extract files, copied over the EFS folder, back to normal!
So lucky I nandroided before I started.
Thanks for the help
HEY GUYS, I am new here and I just wanted to say how much you guys helped me in the past! THANKS
Anyway, recently, I superbricked my Galaxy Note -N700 and i sent it in for a JTAG repair. It did turn on again, but it will NOT read my SIM card. The IMEI is unknown, baseband is unknown. i don't know what to do. I spent 50 bucks on the JTAG service but there was no point. I still cant use it. Can you guys help me out please?!
Have you got an efs backup? Try flashing a new radio / modem or reverting back to gb firmware and see if it comes back.
Sent from my GT-N7000 using xda premium
azzledazzle said:
Have you got an efs backup? Try flashing a new radio / modem or reverting back to gb firmware and see if it comes back.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I do not have an efs backup, because i did not know this will happen after JTAG.
Also, how do you flash new radio? sorry im new to all this stuff :/ and im on gb 2.3 right now.
Thanks!
Explore your sdcard and check if there is a file "efs.img" or "efs.autobackup.img"
Some kernell automaticaly do a backup of efs partition during install, maybe you'll be lucky.
i have efs back up but i dont know how to do can somebody tell me steps ?
My brother owns an AT&T cappy...n after some months of custom rom flashing, he gave me the phone asking me to repair it.
It has stopped reading the sim card, when i checked the imei of the device it gave me a popup of IMEI null/null..also the baseband version is also unknown..
I have many a times flashed the stock rom as every thread about my problem is telling me to do..
also used galaxy s unlock, app for factory unlocking GS devices..but know success
i seriously want to give it a last try before handing it over for a repair outside..
any help would be highly appreciated!!!!!:crying:
Yep, usually using Odin or Heimdall to return to stock firmware should restore the imei. Have u tried to flash to Stock KK4 firmware yet ? The Odin or Heimdall One Clicks for i897ucKK4 can be found here... http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3.
yess!! many a times..but no success
I also wanted to add that :-
during the galaxy s unlock method..i usually get the busybox problem error...though i've installed and verified it many a times
With all the months of flashing that ur brother did...i would think there would be a backup of the efs folder on the sdcard?? Some roms and kernels, when flashed, will create the efs backup for u.
yess!! hopefully dere's an EFS folder.. but i was too bugged up when googling for the method for restoring it..
n also i'm not sure whether the folder is fine or corrupted/messed up..
also i'll be greatful if i'll get to know the easiest step by step process of restoring it.:good:
gautamchawla195 said:
yess!! hopefully dere's an EFS folder.. but i was too bugged up when googling for the method for restoring it..
n also i'm not sure whether the folder is fine or corrupted/messed up..
also i'll be greatful if i'll get to know the easiest step by step process of restoring it.:good:
Click to expand...
Click to collapse
Its as simple as replacing the current one with the backup one.
Sent from my SGH-I747 using xda app-developers app
??
Where to replace...in the root of the system or the SD card,???
busybox error!!!
Can anyone tell me about the BUSYBOX ERROR I'm receiving..??
gautamchawla195 said:
Where to replace...in the root of the system or the SD card,???
Click to expand...
Click to collapse
If you check on the internal sd, you'll see an efs folder. Should probably take a look for yourself before asking those questions
Sent from my SGH-I747 using xda app-developers app