[Q] Flashed 4.2.2, IMEI missing, no backup - Samsung Galaxy Nexus

Hi Everyone,
I have a rooted Galaxy Nexus, Verizon version, and just flashed this ROM:
http://forum.xda-developers.com/showthread.php?t=1737849
Unfortunately I did not do a backup of my IMEI folder, which I realize now was a huge mistake. If I do a "*#06#" then the screen comes up with a blank IMEI. Baseband version is unknown, network unknown, phone number unknown.
I've been searching around all afternoon and tried a few things, namely:
Installing the JDQ39 radio, and
Manually adding my APN (Verizon)
The radio didn't seem to make any difference, and I was unable to get my Verizon APN to show up in my list of "Access Point Names." After I save the info and name it still doesn't appear on the list, even after a reboot.
So, I'm not sure if I'm even on the right track, the most promising post I've found is here:
http://forum.xda-developers.com/showthread.php?p=17587351
But in that post, the OP says I must have the "shipped original EFS folder on my phone," and I don't really know where to even look for that. If anyone has any insight I would be greatly appreciative. Thanks in advance for the help.
-Weston

That is for GSM GNex aka Maguro. Maybr trying to flash stock image from google....
Sent from my Galaxy Nexus using xda app-developers app

Wow, there I was thinking I had bricked this thing and really I was just dumb enough to download the wrong version. I flashed a ROM that was actually meant for my phone, reflashed the right radios, and now it works again! Thanks for the help.
-Weston

warnoldscu said:
Hi Everyone,
I have a rooted Galaxy Nexus, Verizon version, and just flashed this ROM:
http://forum.xda-developers.com/showthread.php?t=1737849
Unfortunately I did not do a backup of my IMEI folder, which I realize now was a huge mistake. If I do a "*#06#" then the screen comes up with a blank IMEI. Baseband version is unknown, network unknown, phone number unknown.
I've been searching around all afternoon and tried a few things, namely:
Installing the JDQ39 radio, and
Manually adding my APN (Verizon)
The radio didn't seem to make any difference, and I was unable to get my Verizon APN to show up in my list of "Access Point Names." After I save the info and name it still doesn't appear on the list, even after a reboot.
So, I'm not sure if I'm even on the right track, the most promising post I've found is here:
http://forum.xda-developers.com/showthread.php?p=17587351
But in that post, the OP says I must have the "shipped original EFS folder on my phone," and I don't really know where to even look for that. If anyone has any insight I would be greatly appreciative. Thanks in advance for the help.
-Weston
Click to expand...
Click to collapse
no /efs aka /factory backup, you're pretty much without options.

I have also same problem
IN flash the android 4.2.2 rom on my samsung nexus device (JDQ39)
And I don't have backup of efs folder
Now in my mobile no imei
I flashed radio.img for xda thread but nothing happen
IF want ti recover my imei
Plz help me recover it
Sent from my HTC X920e using xda app-developers app

Related

[Help] Phone won't detect sim. Unknown Baseband and IMEI

So... I seem to be having the efs corruption issue with my co-worker's phone. I've been searching all over and have found how others have solved the problem, but it seems that our nv_data.bin is not located in our efs directory.
Does anyone have any idea where these files are? I need to check the last modified dates of their backup files to see if I can restore them >.<
Any help is greatly appreciated!!
Bump.. If anyone knows where these files are this could help us from running into the corrupt efs problem that many people have had. Usually backing up your efs prevents your phone from becoming unable to function as a phone.
I do remember reading something about our unlock code not being present in our nv_data.bin.. And when I check my efs folder in both my, as well as my co-worker's phone there is no nv_data.bin so maybe it has been relocated??
Anyone with knowledge on this subject.. your input would be greatly appreciated! I'm also gonna read over the unlock threads to see if there is any relevant info there.
I am having this problem now, I know you posted this over a month ago, but please tell me you know the location of the backup files or any other solution for this?'
Thank you,
[Q] T989 - Baseband and IMEI Unknown
I have searched and read many threads already. I understand the i9100 uses a file called nv_data.bin and requires its .bak file for a fix.
But, I dont think the t989 is the same because these files dont seem to exist, or at least not in the locations the threads for i9100 state. I am wondering if anyone has had this problem and/or how they fixed it. I know it was caused because of trying to unlock, but I'm looking for a solution.
Thanks!
just buy one of those $20 online unlock or go to your local phone kiosk to have it unlocked
any one with a machine to unlock Samsung phones can get this phone unlocked easily
there's no software unlock yet, as you have found on your searches
I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"
svahora said:
I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"
Click to expand...
Click to collapse
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!
KillaHurtz said:
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!
Click to expand...
Click to collapse
What does the (d) stand for?
And, how can I make sure this never happens again in the future? I know there are backup options out there (CWM, Nandroid), but are there any that make a complete clone of the phone's image? In case I mess up the efs or IMEI files again I can restore and be ok.
Thanks!
T989D = Canadian release of T989
they are identical, the just use the D for Canadian
AllGamer said:
T989D = Canadian release of T989
they are identical, the just use the D for Canadian
Click to expand...
Click to collapse
Would a Nandroid backup fix this in the future?
is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder
AllGamer said:
is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder
Click to expand...
Click to collapse
I wonder if the new Galaxy Nexus has its IMEI files stored similarly. If so, we can join forces with that forum group.
If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.
-Mr. X- said:
If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.
Click to expand...
Click to collapse
Did it twice, the stock rom, modem, and kernel.
The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).
cyberjam said:
The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).
Click to expand...
Click to collapse
Would the KL1 work any different than the older one? I tried ODINing the original one, and it didn't work and increased the count so I didn't try the KL1.
I just got my replacement phone yesterday for this same problem. Flashed the stock kernal, and also the modem just to be safe and nothing would fix it. From what I know its just a hardware issue, not software. I was chatting with samsung and t-mobile people about this trying all kinds of fixes to nothing left but hardware defect.

[Q] Baseband Unkown 4.1.1

I am running CM10 4.1.1 the Phone IMEI is unknown and as well Baseband Unknown. I have flashed a new radio and still nothing. Read a post about working in shell and tried some of that to work through it but it still the same thing. NOTE: it also said for md5 and 4.0.3.
I have looked at this and also tried it but with no luck it seems. I really need help can someone offer me some advice. My Gn also keeps rocking between radio off and radio on. I am willing to buy someone a couple of beverages if I can get some help!
Thanks, Gentry
You can try the 5 steps, no harm trying. Just note that the so called EFS folder is called /factory in the root.
http://forum.xda-developers.com/showthread.php?t=1264021
I had the same problem. I tried everything, different kernels, mods, stock firmware, basebands, etc. Nothing changed. I was able to see baseband version in fastboot screen, but not in Android's about phone view. Eventually I brougth my phone to the service and they changed motherboard.
Sent from my Galaxy Nexus using xda premium

Galaxy S3 rooted - No mobile network

Hi guys,
I am writing this post requesting help with my Samsung Galaxy S3 phone which is rooted and is on T-Mobile UK.
Background/Problem:
After having my phone rooted watching a youtube video I then went onto put a leaked 4.2.2 ROM published by androidgalaxy.cu.cc without doing any cache/dalvik cache/data wipe - I used Odin for flashing. The ROM was working ok except few problems such as the Messaging app wouldn't load at all. After a bit of research much later, I realised it was due to not performing necessary wipes during flashing. I then decided to flash CyanogenMod 10.1 using ROM Manager and again I did not wipe anything. I was completely unaware of the necessity of doing wipes to avoid ROM malfunctioning. As expected after flashing, CyanogenMod wouldn't load and stuck at the boot lopp (on the screen where a glow goes around in circle). I did a wipe and re-flashed and it worked this time but I noticed that there was no mobile network. I read on some forum post that loading a stock rom might help and went ahead and flashed Stock Deodexed T999UVDMD5 ROM hoping it might help, but to no avail. Everything else seems fine but no way can I get the mobile network working. I have since taken my SIM out and tried it on an old HTC Wildfire S to make phone calls and send messages. I have come across IMEI number being missing and EFS (I am not sure what it is) being corrupt and I can identify my situation to be one of them. Upon dialing *#06# I get null/null instead of a proper IMEI number. Following are some of observations from my phone from the Settings:
*Settings>More Settings>Mobile Networks - Insert SIM card to access network services message pops up
*Settings>About Device>Baseband Version - Unknown
*Settings>About Device>Status>Network - Unknown
*Settings>About Device>Status>Mobile Network Type - Unknown
*Settings>About Device>Status>Service state - Out of service
*Settings>About Device>Status>Roaming - Not roaming
*Settings>About Device>Status>Mobile network state - Disconnected
*Settings>About Device>Status>My phone number - Unknown
*Settings>About Device>Status>IMEI - Unknown
*Settings>About Device>Status>IMEI SV - Unknown
*Settings>About Device>Status>Device Status - Custom
I am sorry about bombarding you with so much information, I tried to provide as much info as possible.
I will be very grateful if any of you guys out there could help me out to solve this problem. Thanks a lot!
You're running the SGH-T999 device, right? Make you're you're doing that first.
The best u can tell you is to Odin a stock firmware. Going from 4.2.2 to 4.1.1 ROM's will more than likely give you issues. It's best to Odin so you get a fresh start and avoid any issues.
I highly recommend to use the app Andromizer to make a backup of your IMEI. Sometimes flashing different ROM's can cause you to lose your IMEI. So this will backup it up and restore it when you do lose it easily.
This link may help you.
http://forum.xda-developers.com/showthread.php?t=1808408
Sent from my SGH-T999 using xda app-developers app
Hi. Thanks for your reply.
Yes, since I am using the T Mobile Samsung Galaxy S3 so I assume it is the SGH T999.
If I have understood you correctly.. you suggest I flashed a 4.1.1 ROM using Odin? Will that possibly solve the mobile network issue?
Regarding backing up the IMEI, I will definitely do that once the issue is solved, in case I want to flash another ROM next time.
Thanks.
Sorry, I have been very stupid in assuming that it is SGH T999. I just checked on the settings and the Model Number is GT-I9300.
So could it be that the network problem arose because the ROM I flashed was only meant for SGH T999?
yeamin.arafat said:
Hi. Thanks for your reply.
Yes, since I am using the T Mobile Samsung Galaxy S3 so I assume it is the SGH T999.
If I have understood you correctly.. you suggest I flashed a 4.1.1 ROM using Odin? Will that possibly solve the mobile network issue?
Regarding backing up the IMEI, I will definitely do that once the issue is solved, in case I want to flash another ROM next time.
Thanks.
Click to expand...
Click to collapse
yeamin.arafat said:
Sorry, I have been very stupid in assuming that it is SGH T999. I just checked on the settings and the Model Number is GT-I9300.
So could it be that the network problem arose because the ROM I flashed was only meant for SGH T999?
Click to expand...
Click to collapse
Odin stock GT-I9300 firmware.
Thanks very much sir! My phone is fixed now! Thank you to everyone who commented on this post. Much appreciated. :good:
Aerowinder said:
Odin stock GT-I9300 firmware.
Click to expand...
Click to collapse
I have a registration problem on my I9300 but all the numbers (IMEI Etc.) are fine. what can it be? tried a few stock roms but nothing...
any idea?
vainroma said:
I have a registration problem on my I9300 but all the numbers (IMEI Etc.) are fine. what can it be? tried a few stock roms but nothing...
any idea?
Click to expand...
Click to collapse
Sounds like it was blacklisted
Sent from my SGH-T999 using Tapatalk 4 Beta

[Q] IMEI and Baseband Missing - GT-N7100

Hi,
I'm sure this has been covered many times but I'm finding little information that relates to the GT-N7100 or anything that I can actually get to work...
So, I'm new to flashing Android phones. This is my first Android device. I've messed around with ROMs on old Windows Mobile 6.1 and 6.5 devices before but not Android.
The problem I'm basically having is that my GT-N7100 no longer recognises quite a few system details, mainly the baseband version and the IMEI.
I'm not 100% sure where the problem first occured. What I did last night was:
Installed ODIN for Windows and flashed a root/recovery ROM to the device to root it.
Checked SuperSU was there, check. All good.
Tried to boot into CWM Recovery to flash a MIUI ROM. I got the Samsung Galaxy Note II GT-N7100 screen appear, followed by flickering like an out of tune TV.
After some Googling, found that I'd somehow got the wrong ROM for the GT-N7100, followed by a link to the correct one... so I downloaded that, flashed it, all good. I can now bootinto CWM Recovery.
Did a backup through CWM. Flashed the ROM, set it all up, then noticed I only had "Emergency Calls Only". Checked a few settings and everything looked OK. I did a bit of Googling and it pointed to checking the IMEI number.
Checked my IMEI and it came up as 004999010640000 which didn't look right to me. Tried pressing a few random buttons, nothing. Checked my box and that was definitely not right as my IMEI is 356000053********.
In a bit of confusion, went back into CWM Recovery and did a restore. This seemed to put the stock but rooted ROM back onto the device, clearing MIUI. Now I just have a circle with a line through it where the signal strength would normally be.
About Device says IMEI is "Unknown". Dialling *#06# brings up "null / null".
Now, I'm not sure where the problem occured, but I do remember seeing the circle with a line through it on the stock ROM before I flashed MIUI... so I've got a feeling it was the root/recovery that killed it.
I thought it did, but it turns out that CWM Recovery's backup does not backup the /efs folder, and even if it did, I've got a feeling it was fudged before I even got to that stage...
I have tried taking a copy of the existing /efs folder and pasting it onto my external SD card. I have then deleted the /efs folder, rebooted the device so that it regenerated the folder, deleted the nv_data.bin and nv_data.bin.md5, copied the .nv_data.bak and .nv_data.bak.md5 from the backed up copy and renamed them to nv_data.bin and nv_data.bin.md5 to no avail.
One guide suggested there may be a failed checksum error in the nv.log file, but there isn't a line that says anything about an md5 checkum error.
I tried one this morning that talked about using a hex editor to restore the information. I've done this again to no avail. I could see in the file that model number was correct when editing it, but no sign of an IMEI... but it was a large file...
I've tried a few other random bits and pieces that I can't remember, as to be honest, it was getting late and I was getting tired.
This is the information that my About Device screen shows:
Model Number: GT-N7100
Android Version: 4.1.2
Baseband Version: Unknown
Kernel Version: 3.0.31 -1071214 [email protected] #1 SMP PREEMPT Fri May 31 11:14:19 KST 2013
Build Number: JZO54K.N710XXDME6
Network: Unknown
Signal strength: 0dBm 99 asu
Mobile network type: Unknown
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
My phone number: Unknown
IMEI: Unknown
IMEI SV: Unknown
The only thing I haven't really tried so far is just flashing a stock ROM to it. Not sure where to get this from to be honest either.
Any ideas what I can do? I have noticed while typing this that it doesn't seem to be registered a SIM card being inserted? It was last night... I did try booting with no SIM card and reinstalling the SIM, but it doesn't seem to pick it up now?
Any help would be great.
Cheers,
Mike.
Little bit of an update. I have some progress.
I flashed back to the stock ROM and I now have a baseband version of N7100XXALIH, which is great. We're getting somewhere... but I still have no IMEI. This is the current report from my About Device screen:
Model number: GT-N7100
Android version: 4.1.1
Baseband version: N7100XXALIH
Kernel version: 3.0.31 -259982 [email protected] #1 SMP PREEMPT Tue Oct 2 02:04:58 KST 2012
Build number: JRO03C.N7100XXALJ1
Network: O2 - UK
Signal strength: -95 dBm 9asu
Mobile network type: GPRS
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
My phone number: Unknown
ERI Version: Not available
IMEI: 004999010640000
IMEI SV: 01
Serial Number: 00000000000000
Device status: Normal
Your imei is generic, if you have efs backup restore it
Otherwise flash stock rom +wipe if it doesn't solve then better send to service station.
Sent from my GT-N7100 using xda premium
Shame, I thought that might be the case.
I've just done a stock ROM flash and wipe which resolved the baseband issue... but it hasn't restored the IMEI. Unfortunately the backup I took didn't include the EFS when I thought it did so I have no backup to restore.
I'm just fiddling with a few things but not holding my hopes up. I might try a few things and if it doesn't work by the weekend, then I'll just unroot, try to clear the flash history and take it into CPW and say it's broken and I don't know why... see how it goes...
Not got much further with this to be honest. I've asked a friend who has the same device if he can send me a copy of his EFS folder that I could have a dig around with to see if I can find anything, but waiting on that at the moment... He sent me his nv_data.bin and nv_data.bin.md5, but when I put these in the EFS folder and rebooted (with no SIM for safety), it still pulls out the dummy IMEI number...
Someone has suggested to me to search around on here for the standard PIT file, to flash that and then flash a stock pre-rooted ROM which should sort it all out. I've not heard of this before, but from a quick search I've found that PIT is Partition Information Table... which suggests this is going to completely re-build the partition table and then flash a new device. Is this advisable, and do you think it could resolve my issue?
I've managed to install TriangleAway and reset the custom flash count to 0, so it no longer reports as custom firmware... I may just take it to CPW tomorrow and see what they say before I even think about messing with this PIT stuff anymore.
Unfortunately, EFS is a little more complicated than a folder with a few files, it's a dedicated partition which generally can't be restored without a backup.
Using somebody else's folder won't work, and actually using another imei is probably illegal since every phone is supposed to have one unique imei.
I've read that people some times miraculously get back their imei after flashing stock rom, but since you've tried it, I don't think there's realistically much to do besides sending to service.
Sent from my GT-N7100 using Tapatalk 2
nimraynn said:
I've managed to install TriangleAway and reset the custom flash count to 0, so it no longer reports as custom firmware... I may just take it to CPW tomorrow and see what they say before I even think about messing with this PIT stuff anymore.
Click to expand...
Click to collapse
I had faced the same issue and was able to get the IMEI back. Even I did not have the backup of the EFS folder. Go through the thread.
http://forum.xda-developers.com/showthread.php?t=2331833
Try to find a stock rom which has all three - CSC, Modem and PDA available. Install it with PIT from ODIN. (I installed 4.1.1) Once installation is complete, you should be able to see you IMEI number correctly. Root the device and take the back up of the EFS Folder and install any rom that you need. Hope this helps.
This is illogical
Flashing 3 files have no more role than flashing stock rom +wipe
On The contrary flashing 4.1.1 may brick your device.
Sent from my GT-N7100 using xda premium
what about Kies emergency recovery ? did u tried it ?
adytum said:
Unfortunately, EFS is a little more complicated than a folder with a few files, it's a dedicated partition which generally can't be restored without a backup.
Using somebody else's folder won't work, and actually using another imei is probably illegal since every phone is supposed to have one unique imei.
I've read that people some times miraculously get back their imei after flashing stock rom, but since you've tried it, I don't think there's realistically much to do besides sending to service.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't planning on actually using someone else's folder, but more using it to test if that was firstly 100% definitely my issue, and secondly to see if I could dig around to try and work out what might actually be wrong with the /efs directory. I have absolutely no intention of using someone else's IMEI, which is the reason why I took the SIM card out before booting it up with the new nv_data.bin.
kailashnj said:
I had faced the same issue and was able to get the IMEI back. Even I did not have the backup of the EFS folder. Go through the thread.
http://forum.xda-developers.com/showthread.php?t=2331833
Try to find a stock rom which has all three - CSC, Modem and PDA available. Install it with PIT from ODIN. (I installed 4.1.1) Once installation is complete, you should be able to see you IMEI number correctly. Root the device and take the back up of the EFS Folder and install any rom that you need. Hope this helps.
Click to expand...
Click to collapse
I'll take a look and see, but I've tried a stock ROM already and it's not worked.
dr.ketan said:
This is illogical
Flashing 3 files have no more role than flashing stock rom +wipe
On The contrary flashing 4.1.1 may brick your device.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Why would flashing 4.1.1 brick the device? I used a stock ROM to flash back to and according to About Device, I'm currently running 4.1.1?
yahyoh said:
what about Kies emergency recovery ? did u tried it ?
Click to expand...
Click to collapse
I haven't, I'll take a look and see.
nimraynn said:
Why would flashing 4.1.1 brick the device? I used a stock ROM to flash back to and according to About Device, I'm currently running 4.1.1?
Click to expand...
Click to collapse
Just search xda 'sds' or sudden death, you will find answer.
Sent from my GT-N7100 using xda premium
yahyoh said:
what about Kies emergency recovery ? did u tried it ?
Click to expand...
Click to collapse
Thank you so much for this suggestion! I tried it, but unfortunately Emergency Recovery wouldn't detect that my device needed it. I guess it technically didn't as the OS was working, just didn't have a working IMEI...
However, it did keep popping up telling me there was an update for the device, and everything had a different version number. PDA, PHONE and CSC all had completely different versions to what was flashed... so I thought, what harm can it do? Hit update, let it do it's thing and hey presto! I have a working device again! :good:
I'm doing my happy dance. Saved me a trip to CPW tomorrow! :fingers-crossed:
dr.ketan said:
Just search xda 'sds' or sudden death, you will find answer.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Sounds nasty!
nimraynn said:
Thank you so much for this suggestion! I tried it, but unfortunately Emergency Recovery wouldn't detect that my device needed it. I guess it technically didn't as the OS was working, just didn't have a working IMEI...
However, it did keep popping up telling me there was an update for the device, and everything had a different version number. PDA, PHONE and CSC all had completely different versions to what was flashed... so I thought, what harm can it do? Hit update, let it do it's thing and hey presto! I have a working device again! :good:
I'm doing my happy dance. Saved me a trip to CPW tomorrow! :fingers-crossed:
Sounds nasty!
Click to expand...
Click to collapse
u can try firmware upgrade and initialisation
dr.ketan said:
Your imei is generic, if you have efs backup restore it
Otherwise flash stock rom +wipe if it doesn't solve then better send to service station.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
is it possible if you backup your efs folder and send it over to us to have a correct one to restore?
No.
It's different for each device. To flash others is illegal and all the devices have same imei will gets banned.
So never try to share same imei.
Sent from my GT-N7100 using xda premium
Hey,
I also had same problem with my mobile.. while changing the firmware i lost my IMEI and got no Baseband version.. How can i fix it?
nimraynn said:
Hi,
I'm sure this has been covered many times but I'm finding little information that relates to the GT-N7100 or anything that I can actually get to work...
So, I'm new to flashing Android phones. This is my first Android device. I've messed around with ROMs on old Windows Mobile 6.1 and 6.5 devices before but not Android.
The problem I'm basically having is that my GT-N7100 no longer recognises quite a few system details, mainly the baseband version and the IMEI.
I'm not 100% sure where the problem first occured. What I did last night was:
Installed ODIN for Windows and flashed a root/recovery ROM to the device to root it.
Checked SuperSU was there, check. All good.
Tried to boot into CWM Recovery to flash a MIUI ROM. I got the Samsung Galaxy Note II GT-N7100 screen appear, followed by flickering like an out of tune TV.
After some Googling, found that I'd somehow got the wrong ROM for the GT-N7100, followed by a link to the correct one... so I downloaded that, flashed it, all good. I can now bootinto CWM Recovery.
Did a backup through CWM. Flashed the ROM, set it all up, then noticed I only had "Emergency Calls Only". Checked a few settings and everything looked OK. I did a bit of Googling and it pointed to checking the IMEI number.
Checked my IMEI and it came up as 004999010640000 which didn't look right to me. Tried pressing a few random buttons, nothing. Checked my box and that was definitely not right as my IMEI is 356000053********.
In a bit of confusion, went back into CWM Recovery and did a restore. This seemed to put the stock but rooted ROM back onto the device, clearing MIUI. Now I just have a circle with a line through it where the signal strength would normally be.
About Device says IMEI is "Unknown". Dialling *#06# brings up "null / null".
Now, I'm not sure where the problem occured, but I do remember seeing the circle with a line through it on the stock ROM before I flashed MIUI... so I've got a feeling it was the root/recovery that killed it.
I thought it did, but it turns out that CWM Recovery's backup does not backup the /efs folder, and even if it did, I've got a feeling it was fudged before I even got to that stage...
I have tried taking a copy of the existing /efs folder and pasting it onto my external SD card. I have then deleted the /efs folder, rebooted the device so that it regenerated the folder, deleted the nv_data.bin and nv_data.bin.md5, copied the .nv_data.bak and .nv_data.bak.md5 from the backed up copy and renamed them to nv_data.bin and nv_data.bin.md5 to no avail.
One guide suggested there may be a failed checksum error in the nv.log file, but there isn't a line that says anything about an md5 checkum error.
I tried one this morning that talked about using a hex editor to restore the information. I've done this again to no avail. I could see in the file that model number was correct when editing it, but no sign of an IMEI... but it was a large file...
I've tried a few other random bits and pieces that I can't remember, as to be honest, it was getting late and I was getting tired.
This is the information that my About Device screen shows:
Model Number: GT-N7100
Android Version: 4.1.2
Baseband Version: Unknown
Kernel Version: 3.0.31 -1071214 [email protected] #1 SMP PREEMPT Fri May 31 11:14:19 KST 2013
Build Number: JZO54K.N710XXDME6
Network: Unknown
Signal strength: 0dBm 99 asu
Mobile network type: Unknown
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
My phone number: Unknown
IMEI: Unknown
IMEI SV: Unknown
The only thing I haven't really tried so far is just flashing a stock ROM to it. Not sure where to get this from to be honest either.
Any ideas what I can do? I have noticed while typing this that it doesn't seem to be registered a SIM card being inserted? It was last night... I did try booting with no SIM card and reinstalling the SIM, but it doesn't seem to pick it up now?
Any help would be great.
Cheers,
Mike.
Click to expand...
Click to collapse
anupjoshi said:
Hey,
I also had same problem with my mobile.. while changing the firmware i lost my IMEI and got no Baseband version.. How can i fix it?
Click to expand...
Click to collapse
dr ketan There are solution with Last firmware with new efs2?
with 4.1.2 all work but if upgrade To 4.3 leaked, i have imei ok but Not network registered.. prese help me. thanks
Inviato dal mio GT-N7100 con Tapatalk
vingar said:
dr ketan There are solution with Last firmware with new efs2?
with 4.1.2 all work but if upgrade To 4.3 leaked, i have imei ok but Not network registered.. prese help me. thanks
Inviato dal mio GT-N7100 con Tapatalk
Click to expand...
Click to collapse
mine after upgrade to 4.3 same happened as DMG1 custom rom, imei getting 00499xxxx and cannot connect to network..
i'm really really frustated... does it seems that the modem chip is too old and cannot accept any new released modem ?
downgrade modem in 4.3 impossible, getting imei null.. flash kernel in 4.3 brings me boot loop and vibrate.. and no one cannot give me better solution..
i googling everywhere and found some method on how to repair imei using uart usb cable.. is it possible ?
Mobile network not available
Hi Dr.Ketan and everyone else on here.
I've been following/installing Roms and posts on XDA since the original HTC desire days before moving onto an S2 and then the Note 2, strangely enough is my first post. I have been following the progress of this rom since early October and finally decided to give it a try with the more matured version 3.
The Rom worked well and I can see this pretty much being ready as new daily Rom (ProBam is my current daily). There is one problem though that I have spent half the day trying to figure it out, I thought someone here might be able to give me advice. I did a backup in Philz then and full wipe before installing the Rom.
After the Rom loaded everything that I tried seemed to work quite well, apps in general were fluid and from what I could see things were as they should be. When trying to text or make calls I ran into “Mobile network not available” problems. When installing the rom I did select the MI6 modem. So far I have tried.
1. Checking the sim card (testing it in another phone)
2. Contacting my cellular provider (Cell C in South Africa) to make sure they didn’t block me for any reason (which they didn’t).
3. I went into network settings to manually select my network (it wont register to Cell C).
4. I tried restoring Probam again which works but now get “Mobile network not available" problems on that Rom, the same issue on todays nightly Cyanogen 10.2 which does indicate that this is a problem with other Roms now.
I did some hunting on Google and see that others have had similar problems with Samsing phones where their EFS folder gets corrupted and IMEI number becomes 0000. In my case it looks like my IMEI number is still there and when I checked my Philz backup I learnt today that a standard Philz backup doesn’t by default backup the EFS folder (just my luck). Short of downloading a 1 gig stock rom using crappy South Africa internet and flashing it with Odin might there maybe be a quicker way that I have overlooked?
Beyond this thanks for a really great Rom, I am curious what would cause this problem with the V3 Rom so that no one else is affected with this, I have flashed other Roms over the years and not had this one yet :>
Thanks!!
Emergency Calls Only
dr.ketan said:
Your imei is generic, if you have efs backup restore it
Otherwise flash stock rom +wipe if it doesn't solve then better send to service station.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Model number: GT-N7100
Android version: 4.1.1
Baseband version: N7100XXALIH
Kernel version: 3.0.31 -199846 [email protected] #1 SMP PREEMPT Thu Sep 20 03:30:33 KST 2012
Build number: JRO03C.N7100XXALJ1
Network: O2 - UK
Signal strength: -95 dBm 9asu
Mobile network type: GPRS
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
My phone number: Unknown
ERI Version: Not available
IMEI: 3546.... GOOD
IMEI SV: 01
Serial Number: R31... GOOD
Device status: Normal
After restoring EFS my Imei back but I am still stuck on emergency calls only
Please help me Ketan Sir

[Q] No IMEI means radio is broken?

Phone: Samsung Galaxy Nexus GT-i9250TSGGen
I had a stock android version, that I never rooted or flashed. Suddenly the SIM stopped working, I figured out that there is no IMEI number and the baseband is unknown.
I flashed to a custom ROM, and tried to do few things using the Galaxy Nexus Toolkit:
1) custom ROM android 4.1
2) Flashed a custom radio
3) made a copy of the /efs folder, deleted the original and replaced it after restart.
The Samsung service center said the entire board has to be changed, with an estimated cost of $140 USD.
Can someone help me with my options? Is it definitely a hardware problem? is there anyway to know for sure?
samdev09 said:
Phone: Samsung Galaxy Nexus GT-i9250TSGGen
I had a stock android version, that I never rooted or flashed. Suddenly the SIM stopped working, I figured out that there is no IMEI number and the baseband is unknown.
I flashed to a custom ROM, and tried to do few things using the Galaxy Nexus Toolkit:
1) custom ROM android 4.1
2) Flashed a custom radio
3) made a copy of the /efs folder, deleted the original and replaced it after restart.
The Samsung service center said the entire board has to be changed, with an estimated cost of $140 USD.
Can someone help me with my options? Is it definitely a hardware problem? is there anyway to know for sure?
Click to expand...
Click to collapse
If you have a nandroid back up, try and restore with it. This could solve ur problem.
saishyamk said:
If you have a nandroid back up, try and restore with it. This could solve ur problem.
Click to expand...
Click to collapse
Thanks, but I hadn't created a back up before. Is there a way to use a back up from a different phone? where would l find more information?
samdev09 said:
Thanks, but I hadn't created a back up before. Is there a way to use a back up from a different phone? where would l find more information?
Click to expand...
Click to collapse
I had an old nandroid back up and I used the method in this post to fix my IMEI problem: forum.xda-developers.com/showpost.php?p=47048361&postcount=9
And when you said you took a back up of the /EFS folder, you meant pulled the .bin and .md5 files from the /factory or the /radio folders OR did you use something like kTool? Because, as people have pointed out in other threads there is no /EFS folder for the Galaxy Nexus. The IMEI information is stored in the Radio and Factory Folders. For more information on how IMEI works on the GNEx, refer to this post: http://forum.xda-developers.com/showpost.php?p=47045295&postcount=6
But you are saying the baseband is also unknown. A radio flash should have fixed it. Try restoring Stock ICS using Odin. i hear this fixes some problems like this. U can use thus guide forum.xda-developers.com/showthread.php?t=2065470
If Odin is a little complicated, try the Nexus Root Tool kit. U gotta experiment to find the right problem and them fix it. No other go. I doubt that replacing the board will solve it as it looks like a software issue, unless you fried your radios.
saishyamk said:
I had an old nandroid back up and I used the method in this post to fix my IMEI problem: forum.xda-developers.com/showpost.php?p=47048361&postcount=9
And when you said you took a back up of the /EFS folder, you meant pulled the .bin and .md5 files from the /factory or the /radio folders OR did you use something like kTool? Because, as people have pointed out in other threads there is no /EFS folder for the Galaxy Nexus. The IMEI information is stored in the Radio and Factory Folders. For more information on how IMEI works on the GNEx, refer to this post: http://forum.xda-developers.com/showpost.php?p=47045295&postcount=6
But you are saying the baseband is also unknown. A radio flash should have fixed it. Try restoring Stock ICS using Odin. i hear this fixes some problems like this. U can use thus guide forum.xda-developers.com/showthread.php?t=2065470
If Odin is a little complicated, try the Nexus Root Tool kit. U gotta experiment to find the right problem and them fix it. No other go. I doubt that replacing the board will solve it as it looks like a software issue, unless you fried your radios.
Click to expand...
Click to collapse
Thanks again. Yes, the /efs folder is not where it was supposed to be. I did find the correct location and moved it. I will try using your ideas. Just one more question:
Since I had not done anything that would wipe out my IMEI number (neither software hacking nor physical damage). I wonder why this problem suddenly occurred. Just to eliminate a possibility, how can I know for sure that I have not "fried the radios"?
Appreciate your help. If I know that it is a software problem, I can continue to play with the Nexus toolkit and try different solutions.
samdev09 said:
Thanks again. Yes, the /efs folder is not where it was supposed to be. I did find the correct location and moved it. I will try using your ideas. Just one more question:
Since I had not done anything that would wipe out my IMEI number (neither software hacking nor physical damage). I wonder why this problem suddenly occurred. Just to eliminate a possibility, how can I know for sure that I have not "fried the radios"?
Appreciate your help. If I know that it is a software problem, I can continue to play with the Nexus toolkit and try different solutions.
Click to expand...
Click to collapse
I'm not sure how to check if your radio is fried. Basically, it means something's wrong with your hardware, where you experience occasional or complete signal loss. But in your case, you lost your IMEI. So, back up your nv_data files, flash using NRT or ODIN and see what happens.
NRT will push the stock radio while doing the "Flash Stock + Unroot" Option. So, you'll get the stock baseband as well. This should fix it. If your IMEI still doesn't work, try restoring the nv_data.bin and md5 files you backed up as mentioned in the link I posted.
Let me know how it works out. :good:
Always make a backup of /EFS (Support in both PhilZ_CWM & TWRP )for safety, though the IMEI would be only wiped by CWM wipe /factory option......happened to me a few days back, luckily i got my /efs restored & flashing stock doesn't bring any IMEI back since it's actually phone specific plus comes with a proper MD5 !!
the above method should work and here more info on the EFS

Categories

Resources