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
Related
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.
Sir, i flashed my nexus with AOSP rom(4.0.3),everything works well for several hours.but yesterday my phone shows error no service,i tries several sim card but facing same issue.so i tried imei no and guess what it shows nothing.... i checked baseband shows unknown. so i flashed stock rom via cwm (restore),but unfortunately facing same problem. so i flashed few baseband images also but not workrd either. plz help me how should i get my imei number back..... i have no backup file of my EFS folder.
First off, don't call me sir
I've been seeing alot of the same issue and no one seems to have a solid lead on the real problem.
And yes, it has happened to me.
My opinion is that flashing *some* roms is causing the bootloader to become corrupted...as this is exactly the issue I had experienced.
A fubar'd bootloader will screw everything up.
The solution for me was to odin back to stock.
Since you did not state if your gnex is gsm or cdma I am not going to attempt to post directions or even file names for you (you can easily search for odin and get them here in this forum). The directions are completely different depending on the gsm/cdma thing.
Be careful and make sure you have the right version of odin and the correct files to flash. It's actually pretty simple, but it's always the simple things that are easiest to get wrong.
g'luck
mangesh hotkar said:
Sir, i flashed my nexus with AOSP rom(4.0.3),everything works well for several hours.but yesterday my phone shows error no service,i tries several sim card but facing same issue.so i tried imei no and guess what it shows nothing.... i checked baseband shows unknown. so i flashed stock rom via cwm (restore),but unfortunately facing same problem. so i flashed few baseband images also but not workrd either. plz help me how should i get my imei number back..... i have no backup file of my EFS folder.
Click to expand...
Click to collapse
For me the solution was to just flash a suitable radio
Sent from my Galaxy Nexus using Tapatalk 2
There is no 4.0.3 for the nexus the last time i remember..
Mach3.2 said:
There is no 4.0.3 for the nexus the last time i remember..
Click to expand...
Click to collapse
? ... 4.0.3 has been out for GN.
zephiK said:
? ... 4.0.3 has been out for GN.
Click to expand...
Click to collapse
There's no 4.0.3 images for the gnex, at least official ones.
http://www.randomphantasmagoria.com/firmware/galaxy-nexus/i9250/
I had this issue as well. I couldn't get the gnex (GSM) to show up in Odin to even start flashing anything so the only thing I could do was send it in to Samsung.
Sent from my Sensation using Tapatalk 2
sorry my mistake its 4.0.4, i have GSM phone.is ODIN solve my problem to get back my baseband.....
buenso80 said:
For me the solution was to just flash a suitable radio
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i tried ur way but its not working and i have the same problem
haziqshaikh97 said:
i tried ur way but its not working and i have the same problem
Click to expand...
Click to collapse
Any update? have anyone make a warranty reclamation? my phone with cyanogen 9 have the same problem, factory image restoration and radio install don´t work for me.
radiazo said:
Any update? have anyone make a warranty reclamation? my phone with cyanogen 9 have the same problem, factory image restoration and radio install don´t work for me.
Click to expand...
Click to collapse
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
PaullieVicious said:
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
Click to expand...
Click to collapse
Hi, I went back to stock by odin but had no success! no gsm signal... baseband unknown :crying::crying::crying:
[email protected]:/data/radio/log # cat nv.log
cat nv.log
Sat Jul 28 12:29:43 2012: /data/radio/nv_data.bin does not exist.
Sat Jul 28 12:29:43 2012: /data/radio/nv_data.bin does not exist.
[email protected]:/data/radio/log # cd /data/radio
cd /data/radio
[email protected]:/data/radio # ls
ls
log
nv_data.bin
nv_data.bin.md5
[email protected]:/data/radio #
is problem hardware pba (modem)
http://forum.xda-developers.com/showthread.php?t=1626593&page=5
any updates? I'm having the same problem, only had my GNEX for a week.
Try copying these files from /factory to /data/radio:
nv_data.bin
nv_data.bin.md5
And set the permissions to 700.
efrant said:
Try copying these files from /factory to /data/radio:
nv_data.bin
nv_data.bin.md5
And set the permissions to 700.
Click to expand...
Click to collapse
Then reboot of course.
Sent from my Galaxy Nexus using Tapatalk 2
PaullieVicious said:
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
Click to expand...
Click to collapse
I use fastboot, and don´t have luck. EFS partition contents exist, but i don´t have imei or baseband detected. I install google jellybean
Same happened to my GNex after flashing miui 2.11.16.
Common sense suggests that the rom, which doesn't include a radio, shouldn't be the reason for the unknown imei and unknown baseband fault.
This has also happened to others of whom most, including me, indicated flashing the updated recovery either twrp 2.3.2.1 or cwm 6.0.1.5/6 which were rolled out for android 4.2 compatibility.
I went back to stock 4.1.2 everything... GNex Tool and ODIN methods, but the problem remained: still UNKNOWN IMEI and UNKNOWN Baseband.
Common symptom to this fault is the phone/os thinks that Flight Mode is ON. Closer inspection in hidden menu phone information (*#*#4636#*#*) clearly shows the radio alternating On/Off continuously... all suggested tricks to set band to gsm manual or auto failed.
I have also tried the OMAP_Flash tool recently leaked from smsng team... it works as described (fix boot partition) but it wouldn't fix this problem.
Those suggesting it's a hardware fault are simply "just saying" but there's no actual prove or method to such a conclusion.
I'm leaning more to believe the cause to be a bug in the updated custom recoveries for android 4.2.
Hope this helps anyone trying to find a fix.... if you find a fix, please PM me
... and for now, i'm using my good old galaxy s i9000 <= will give it to anyone successfully helps us to fix the GNex
Do you have signal? are you in the same rituation described in this post? http://forum.xda-developers.com/showthread.php?t=1797931
I'm in the same situation, only flashing 4.0.4 firmware Imei and baseband are shown, but no signal...
I really don't know if it's just a solvable software problem or it's an hardware one!
Thanks for any news!!!!
xanadux said:
Do you have signal? are you in the same rituation described in this post? http://forum.xda-developers.com/showthread.php?t=1797931
I'm in the same situation, only flashing 4.0.4 firmware Imei and baseband are shown, but no signal...
I really don't know if it's just a solvable software problem or it's an hardware one!
Thanks for any news!!!!
Click to expand...
Click to collapse
similar problem, but unlike dhuberto, not able to get imei back with any version of a stock image using any method.
My radio keeps going FLIGHT MODE on then off then on continuously... I have tried several apps to force gsm off (turn off radio) to no avail.
I personally still think it is not a hardware issue. Maybe it's me just hoping!
I have reasons to slightly believe that it was caused by a bad custom recovery code while doing fix permissions.
I am still researching and I will update once there's some news, good or bad.
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
artorelis said:
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ya, I was asking this question on the Omega forum and I am waiting for the right response.
Sent from my GT-N7100 using xda premium
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
joshphilips said:
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I did downgrade from v17 back to 16 since something went wrong with Poweramp but I forgot that if I selected for the efs backup or not since I (stupidly) didn't think that efs is important...:banghead:
Sent from my GT-N7100 using xda premium
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
Click to expand...
Click to collapse
Thanks for replying, I should have a backup, but it probably be the wrong one. Anyway I will go for a full stock restore since I have the firmware with me now.
Sent from my GT-N7100 using xda premium
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
Good luck.
Click to expand...
Click to collapse
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Dan Law 001 said:
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Click to expand...
Click to collapse
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
muppetmania said:
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
Click to expand...
Click to collapse
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Dan Law 001 said:
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Click to expand...
Click to collapse
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
muppetmania said:
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
Click to expand...
Click to collapse
Thanks for information, but how do I know that if the EFS is "totally" corrupt, "partially" corrupt, or not corrupt at all? In fact, I never touch the EFS in the root. Also, as I am not quite sure that if I have any previous EFS(S) backup or not, so, if possible, where does the backup(s) most likely to be found?
If you haven't taken an EFS backup yourself, then you won't have any.
I don't know the difference between corruption levels either, all I know is I've read a number of forum posts where someone has reflashed stock and their EFS data (i.e. the right IMEI number) is back. So I'd consider that to be a partial corruption. Others have flashed back to stock and it's still a bogus IMEI
Basically, flash back to stock. If it doesn't work, you'll have to take it in for repair.
UPDATE: Please read on - this information is incorrect - it is possible to recover with the correct modem flashed.
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
NOTE: The information from me in this post below is wrong
Dan Law 001 said:
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
Click to expand...
Click to collapse
It's normal your device got unrooted, yes. If your IMEI is still the same after ODIN and stock flash, then you have major issues (sorry!)
Doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What IMEI does *#06# show?
muppetmania said:
it's normal your device got unrooted, yes. If your imei is still the same after odin and stock flash, then you have major issues (sorry!)
doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What imei does *#06# show?
Click to expand...
Click to collapse
004999010640000 / 01
Dan Law 001 said:
004999010640000 / 01
Click to expand...
Click to collapse
Type 004999010640000 into Google...
Sorry man. Good luck getting it fixed.
just flash ME4 modem everything will be alright
bhasg1007 said:
just flash ME4 modem everything will be alright
Click to expand...
Click to collapse
Interesting to know - why does that work? (I don't doubt you, I just like to know why things work)
Just go through this thread http://forum.xda-developers.com/showthread.php?t=2333216
Even i had the same problem no network no imei nothing after downgrading so i just changed the modem and now everything is fine as it should be
Hello to everyone, I was wondering if anyone can help with this. I have a Galaxy Note 2 branded by an Italian company (3hg Italia). It recently received its update to Android 4.3 (update N7100XXUEML2). It was the official update OTA, the phone is not rooted and it had the stock ROM on it. The update somehow messed up my IMEI making it appear as the generic 0049 forcing me on "Emergency calls only" mode. I already tried flashing the same ROM with Odin and repeating the update with KIES, but while the updates always results successful the IMEI remains 0049. I never made a backup of the EFS folder for this phone since I haven't rooted it or flashed any different ROM on it yet. There is any chance that the phone made an automatic backup? I live in the States right now and Samsung tells me I need to ship it back to Italy to have it fixed, but that costs a lot and would take forever, and I would much prefer try to solve the problem locally. Any suggestions would be greatly appreciated, if not for any fix that I can try myself, at least some place on the West Coast that can fix the problem!
Thank you!
Lorenzo
Oh I forgot to add that because of Hardware problems I recently sent my phone to Samsung and they replaced the motherboard, which fixed the problem I was having. I don't know if that could be related!
rext said:
Oh I forgot to add that because of Hardware problems I recently sent my phone to Samsung and they replaced the motherboard, which fixed the problem I was having. I don't know if that could be related!
Click to expand...
Click to collapse
Here's solution : http://forum.xda-developers.com/showthread.php?t=2539731
phluid01 said:
Here's solution : http://forum.xda-developers.com/showthread.php?t=2539731
Click to expand...
Click to collapse
I'm afraid that fix works just if you have your actual IMEI, I instead have the generic IMEI that starts with 0049. But I will check it out! Thanks!
rext said:
I'm afraid that fix works just if you have your actual IMEI, I instead have the generic IMEI that starts with 0049. But I will check it out! Thanks!
Click to expand...
Click to collapse
Then you should simply flash another modem from here : http://forum.xda-developers.com/showthread.php?t=2044937 ... flash a custom recovery first.
phluid01 said:
Then you should simply flash another modem from here : http://forum.xda-developers.com/showthread.php?t=2044937 ... flash a custom recovery first.
Click to expand...
Click to collapse
Thank you so much! I'll take a look into it tomorrow and try it!
rext said:
Thank you so much! I'll take a look into it tomorrow and try it!
Click to expand...
Click to collapse
So I found someone nice enough to give me a hand with this situation, but still no luck yet! Here what they say:
At first glance, the EFS data on the phone was corrupt. I re-generated
that data and restored it to the phone without success.
The GSM radio itself is operational, and the firmware for it is
installed and functional. diagnostic data flows to the towers and back
to the phone but it's not reading the IMEI from the copy of
nv_data.bin contained within EFS. I've re-generated and installed
those files as well, again with no luck.
I rolled the device back to it's original factory firmware and radio
baseband, then ran through the update for the radio baseband, which
also regenerates the contents of EFS, and still no luck.
Given the situation, anyone have other suggestions?
Hi guys, i seriously need help here. Please refer to attached screenshot.
I came here after flashing sokp 4.2.2 rom, and it prompted me an error saying encryption was unsuccessful. After which, i wasnt able to use my phone since then.
I tried to flash stock rom, and I end up with this. Please dont tell me to search the forums because Ive been to them countless times. I suppose this is a efs issue, because baseband and imei are unknown and I do not have a backup for it. Tried with the writing tool for imei, doesnt work as well.
Pls ask me for any info u might need/i missed out to help with this issue.
I think it's in the efs folder, you have to use a root browser and edit factory mode to off instead of on. It's been a long time since I saw factory mode so I'm not 100%
Sent from my GT-N7105 using Tapatalk
sawdoctor said:
I think it's in the efs folder, you have to use a root browser and edit factory mode to off instead of on. It's been a long time since I saw factory mode so I'm not 100%
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. But even if I off factory mode, will the baseband and imei be unknown?
I'm not sure but if it doesn't the 2 things that might be worth trying are, emergency firmware recovery with kies or mskips toolkit has a rescue package but I think you have to go to skipsoft.net now as the thread was closed
Sent from my GT-N7105 using Tapatalk
It's current value is "OFF"...u have to write "ON"...i know it sounds weird but that is the value. Amd if u don't have any previous back up of EFS then there's nothing u can do at home to bring it back. Same thing happened to mine and i got it repaired from a local shop for cheap...they used z3x box...the problem is my IMEI is correct and network works fine...but everytime i flash a ROM i have to take it to the shop and get the modem patched or else it doesn't connect to network. So go to Samsung service centre and get it fixed by them...they'll charge u more but their fix is permanent.
Sent from my GT-N7100 using XDA Free mobile app
Alright, it seems like i have a backup of the efs, bt the nv_data.bin file is not included, and i read on other threads that this file is responsible for the imei and all? This backup is dated in aug2013, but it doesnt help in restoring my phone because the efs pro software doesnt see this as a backup file. Im actually looking for one of the thread that actually taught how to edit the nv_data.bin file, but no luck till date.
This thread might help
http://forum.xda-developers.com/showthread.php?t=1946915
[WARNING! + GUIDE] Backup and Restore IMEI / NV Data Procedure for GT-I9305. There is another post in this thread where they flashed the param.bin file
Check out the last post in this thread
http://forum.xda-developers.com/showthread.php?t=2724169
[Q]Null Imei, Baseband Unknown N7105
Sent from my GT-N7105 using Tapatalk
is it safe to flash the file that is intended for i9300? i dare not do that in case it doesnt work coz is different models.
ok my phone's all fixed up now. If anyone is interested to know, samsung kies original firmware helped.