unknown Baseband( no network,no imei) - Samsung Galaxy Nexus

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.

Related

unknown Baseband issue :( plz help..

Well, from the day one i bought my nexus i had the " unknown baseband " in the About screen of my GSM unlocked NEXUS ! ... I dunno how but i left my phone with sim card inserted for some hours and suddenly i noticed that i have a signal and i checked to see the baseband is identified as xxkk6. Now i downloaded the Factory image from google and i flashed it using the Nexus Toolbox and now i dont have any baseband again.
Tried to flash the baseband only again with no luck, It only shows in the fastboot mode but when the phone is in android mode or ( normal mod ) it shows as unknown!
Tried to flash the UGLA4 baseband and the problem persists!
What should i do now ???
Try to flash back to google stock rom via Galaxy Nexus Toolkit from mskip :
http://forum.xda-developers.com/showthread.php?t=1392310
Download google stock image here :
http://code.google.com/android/nexus/images.html
Then, using GNex Toolkit again to root, unlock bootloader, etc and flash any baseband from this thread below to test :
http://forum.xda-developers.com/showthread.php?t=1405345
i already did that and still not working!
I tried flashing the stock rom over and over , ulnocked , rooted and flashed the baseband file alone and nothing works!
i tried to flash ugla4 and xxkk6 basebands but both didn't work and i only can see them in the fastboot mode info
If you can't seem to get it to work, try returning it to the vendor.
As last resort you can try with ODIN it might work...
code777 said:
If you can't seem to get it to work, try returning it to the vendor.
As last resort you can try with ODIN it might work...
Click to expand...
Click to collapse
I can't return it as i bought it with no warranty from an online store in my country ...
Ok, how can i use odin to restore it ! i mean i need a pit file and the other files right? where can i get them from ?
another thing, do i find the files if i extracted the factory image
thank you!
Install cwm and flash the baseband from there. Should work. Search cwm touch in the forum.
Sent from my Galaxy Nexus using xda premium
M7amad90 said:
I can't return it as i bought it with no warranty from an online store in my country ...
Ok, how can i use odin to restore it ! i mean i need a pit file and the other files right? where can i get them from ?
another thing, do i find the files if i extracted the factory image
thank you!
Click to expand...
Click to collapse
That doesn't mean it has no warranty contact your country Samsung warranty service and explain the situation it must have warranty!
I tried flashing it with CWM and nothing seems to work !
Am i the only one who has this problem ? is it hardware related or what because as i said it was working before and i was able to make and receive calls and data ..
It wasn't workning when i first turned on the phone when i bought it but i was playing around with the setting and apps and i remember having an OTA update from 4.0.1 to 4.0.2 and after 2 or 3 hours it started to work ! just like that !
btw i flashed the old 4.0.1 (ITL41F) factory image and i updated OTA now to 4.0.2 ICL53F but still unknown baseband
are you using a custom rom on the phone?
if you are...you may have installed a rom for the LTE/CDMA phone and not for your GSM phone..
that is why my baseband said UNKNOWN......I had a LTE and I install a GSM rom by mistake...
try installing a custom GSM rom
M7amad90 said:
I tried flashing it with CWM and nothing seems to work !
Am i the only one who has this problem ? is it hardware related or what because as i said it was working before and i was able to make and receive calls and data ..
It wasn't workning when i first turned on the phone when i bought it but i was playing around with the setting and apps and i remember having an OTA update from 4.0.1 to 4.0.2 and after 2 or 3 hours it started to work ! just like that !
btw i flashed the old 4.0.1 (ITL41F) factory image and i updated OTA now to 4.0.2 ICL53F but still unknown baseband
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1398296
here there is a similar thread...somene talk about a corrupted efs partition (try to search something about it), someone just flashed a new radio and solved it
did you also tried to power off the phone and pull the battery for a while? it is a sort of software reset..may work sometimes..
Sounds like your EFS may be corrupted.
There is an app for the I9100 that can repair corrupted EFS's, and it can be done via adb as well, but I'm not sure about the applicability towards the GNex.
Just for reference, I am in no way suggesting you do this, but perhaps someone else can chime in: http://forum.xda-developers.com/showpost.php?p=17587351&postcount=1
hogowner said:
are you using a custom rom on the phone?
if you are...you may have installed a rom for the LTE/CDMA phone and not for your GSM phone..
that is why my baseband said UNKNOWN......I had a LTE and I install a GSM rom by mistake...
try installing a custom GSM rom
Click to expand...
Click to collapse
i am using a gsm factory room and and my nexus is GSM Nexus !
Ok could you please tell me what is the best stable room for GSM Gnex cause there are a lot of them !
M7amad90 said:
i am using a gsm factory room and and my nexus is GSM Nexus !
Ok could you please tell me what is the best stable room for GSM Gnex cause there are a lot of them !
Click to expand...
Click to collapse
I may have jumped the gun a bit, with the i9100 an unknown baseband typically meant a corrupted efs. Do you still have signal and an imei #?
Sent from my Galaxy Nexus using xda premium
Ok i just checked my imei by *#06# and it shows nothing too !!! no numbers at all !! does it mean the it is efs corrupted partition ???
M7amad90 said:
Ok i just checked my imei by *#06# and it shows nothing too !!! no numbers at all !! does it mean the it is efs corrupted partition ???
Click to expand...
Click to collapse
Likely, but again I haven't messed around with the EFS on the GNex yet. Hopefully someone with more knowledge can chime in and get you sorted out.
mudferret said:
I may have jumped the gun a bit, with the i9100 an unknown baseband typically meant a corrupted efs. Do you still have signal and an imei #?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Btw i didn't back up anything and i don't know how to fix the EFS thing but i know how to use odin and adb a little bit
i have this issue suddenly with the radio of 4.0.2 and fixed it by flashing 4.0.1 radio.
never mind .. i got another Gnex and everything is fine now !!! u can't fix it but in samsung service centers

[Q] Baseband Unknown, Signal Drops

Hi, i'm from Brazil and i have a Gnex from UK, and it's unlocked.
When i was at 4.0.2, everythings ok, but after the OTA update to 4.0.4, i'm having some problems if the data is turned on, and the option 'only 2g' is checked the signal is good, but if the data is turned on and i have 3G connection the phone lose signal, and baseband shows Unknown.
My Gnex is Yakju, and i have flashed the 4.1 (JRN84D) from here with baseband I9250XXLF1 and 3.0.31-ge8de0e2 kernel ( on the post shows that's a stock kernel ). And the problems still here.
More info about my Gnex on fastboot mode:
Product Name: Tuna
Variant: Maguro
HW Version: 9
BootLoader: PRIMEKK15
Baseband: I9250XXLF1
Sorry for my bad english, but i can't use 3G connection and i need to recive emails, etc
If anyone can help me, thanks! :laugh:
andieknoxville said:
Hi, i'm from Brazil and i have a Gnex from UK, and it's unlocked.
When i was at 4.0.2, everythings ok, but after the OTA update to 4.0.4, i'm having some problems if the data is turned on, and the option 'only 2g' is checked the signal is good, but if the data is turned on and i have 3G connection the phone lose signal, and baseband shows Unknown.
My Gnex is Yakju, and i have flashed the 4.1 (JRN84D) from here with baseband I9250XXLF1 and 3.0.31-ge8de0e2 kernel ( on the post shows that's a stock kernel ). And the problems still here.
More info about my Gnex on fastboot mode:
Product Name: Tuna
Variant: Maguro
HW Version: 9
BootLoader: PRIMEKK15
Baseband: I9250XXLF1
Sorry for my bad english, but i can't use 3G connection and i need to recive emails, etc
If anyone can help me, thanks! :laugh:
Click to expand...
Click to collapse
I'm not 100% sure but I think your kernel maybe be the Developer preview kernel, the official is 3.0.31-g6fb96c9, you could try flashing that? It's what I'm running with 4.1.1 and it works fine.
andieknoxville said:
Hi, i'm from Brazil and i have a Gnex from UK, and it's unlocked.
When i was at 4.0.2, everythings ok, but after the OTA update to 4.0.4, i'm having some problems if the data is turned on, and the option 'only 2g' is checked the signal is good, but if the data is turned on and i have 3G connection the phone lose signal, and baseband shows Unknown.
My Gnex is Yakju, and i have flashed the 4.1 (JRN84D) from here with baseband I9250XXLF1 and 3.0.31-ge8de0e2 kernel ( on the post shows that's a stock kernel ). And the problems still here.
More info about my Gnex on fastboot mode:
Product Name: Tuna
Variant: Maguro
HW Version: 9
BootLoader: PRIMEKK15
Baseband: I9250XXLF1
Sorry for my bad english, but i can't use 3G connection and i need to recive emails, etc
If anyone can help me, thanks! :laugh:
Click to expand...
Click to collapse
Can you still txt/call while the signal is dropped??
Sgtpanda said:
I'm not 100% sure but I think your kernel maybe be the Developer preview kernel, the official is 3.0.31-g6fb96c9, you could try flashing that? It's what I'm running with 4.1.1 and it works fine.
Click to expand...
Click to collapse
The 4.1.1 is available from OTA, but when i press to install the phone reboot then enter in CWM and shows a message that de update was found, try install but give me a erro message that failed, i'm a new user on android, my phone was an iPhone.
Thanks for help
kyokeun1234 said:
Can you still txt/call while the signal is dropped??
Click to expand...
Click to collapse
No, when de signal is dropped i had to take battery out from phone, wait 5 or more minutes than put it back! If i put it back before i have the baseband unknown message on Config > About Phone. And this happens only if i have 3G signal, i see many people saying about signal issues after OTA to 4.0.4 and if i still with "only 2g" selected i don't have signal drop or disable the data, then i don't have any problem
Thanks for help
andieknoxville said:
The 4.1.1 is available from OTA, but when i press to install the phone reboot then enter in CWM and shows a message that de update was found, try install but give me a erro message that failed, i'm a new user on android, my phone was an iPhone.
Thanks for help
Click to expand...
Click to collapse
If it's the status 7 error it's because OTA's require stock everything I think, including recovery.
Sgtpanda said:
If it's the status 7 error it's because OTA's require stock everything I think, including recovery.
Click to expand...
Click to collapse
How i do that? A update can resolve this problems?
Thanks
andieknoxville said:
How i do that? A update can resolve this problems?
Thanks
Click to expand...
Click to collapse
Not sure if it will fix the problem, I think it's in the kernel you have as that's where WIFI is managed, however you could try and if that doesn't work change the kernel.
Instructions on how to update to official 4.1 are here however if you want to then accept the OTA afterwards when following Method 1 do not delete/rename /system/etc/install-recovery.sh and CWM will be overwritten by stock and you should be able to accept OTA's.
Note: If you don't want to lose your data then you could try skipping the "Wipe data/factory reset" step but do that at your own risk, I skipped it and it works fine though.
Sgtpanda said:
Not sure if it will fix the problem, I think it's in the kernel you have as that's where WIFI is managed, however you could try and if that doesn't work change the kernel.
Instructions on how to update to official 4.1 are here however if you want to then accept the OTA afterwards when following Method 1 do not delete/rename /system/etc/install-recovery.sh and CWM will be overwritten by stock and you should be able to accept OTA's.
Note: If you don't want to lose your data then you could try skipping the "Wipe data/factory reset" step but do that at your own risk, I skipped it and it works fine though.
Click to expand...
Click to collapse
i will try OTA's, if dosen't fix what do you think about FuguMod kernel ?
Thanks for help
someone? a little information, when i have this problem the option to turn off the data disappear, than i have to take out battery wait five or more to get signal again
is problem hardware pba (modem)
http://forum.xda-developers.com/showthread.php?t=1626593&page=5
a "different" kinda phone problem(?)
I looked through most all of these forums and couldnt find anyone with the problem im having. Not sure if it's me or what...
My problem is that when I flash some roms, my phone doesnt work. (yes im on sprint and only using toroplus). Well, yesterday, for most of the day, everything on my phone worked. When I got up this morning, It hadnt charged, and I lost my dialing again. Some ROMs I flash start off. When I go to settings> about phone> status under "Network" it says "unknown" and under "service state" It will say "no service" then checking on "Moblle Network State" It'll say "unknown"", sometimes my phone number shows up, sometimes it doesnt, Most times I cant make outgoing calls and when anyone calls me, it does a half ring and directs my callers straight to my voice mail. Is anyone having this problem too? And if so, how did you fix it? It frustrates the hell outta me and I think I should just go back to ICS although I dont want to. HELLP!!! :-/
Thanks,
Ridge
P.S. I forgot to mention that Im on a Sprint phone and that Im running Houng81's AOKP Aug1 version Baseband: fg01, the kernel that came with the ROM, Ive even replaced them a few times and nothing does any better. Forgot to add this to my prior text LOL sorry, that just gave me away as a n00b huh? HEHE
Ridge
andieknoxville said:
i will try OTA's, if dosen't fix what do you think about FuguMod kernel ?
Thanks for help
Click to expand...
Click to collapse
It's a great kernel.
andieknoxville said:
someone? a little information, when i have this problem the option to turn off the data disappear, than i have to take out battery wait five or more to get signal again
Click to expand...
Click to collapse
Doing the OTA might solve it since it will update (i think) your bootloader to lc03, you still on kk15. If it doesnt, use fastboot and update manually. To run an OTA with cwm installed, you need to download the update.zip from dev section for the OTA you want to run, but do it through cwm (like flashing a custom rom).
Sent from my tf201
bk201doesntexist said:
It's a great kernel.
Doing the OTA might solve it since it will update (i think) your bootloader to lc03, you still on kk15. If it doesnt, use fastboot and update manually. To run an OTA with cwm installed, you need to download the update.zip from dev section for the OTA you want to run, but do it through cwm (like flashing a custom rom).
Sent from my tf201
Click to expand...
Click to collapse
I read in another forum that the "factory" folder is the efs on the Gnex, and maybe my phone was with this folder corrupt, if i get a backup of another Gnex thats everything is working and restore to my Gnex will be resolve the problem?
TheRidge69 said:
I looked through most all of these forums and couldnt find anyone with the problem im having. Not sure if it's me or what...
My problem is that when I flash some roms, my phone doesnt work. (yes im on sprint and only using toroplus). Well, yesterday, for most of the day, everything on my phone worked. When I got up this morning, It hadnt charged, and I lost my dialing again. Some ROMs I flash start off. When I go to settings> about phone> status under "Network" it says "unknown" and under "service state" It will say "no service" then checking on "Moblle Network State" It'll say "unknown"", sometimes my phone number shows up, sometimes it doesnt, Most times I cant make outgoing calls and when anyone calls me, it does a half ring and directs my callers straight to my voice mail. Is anyone having this problem too? And if so, how did you fix it? It frustrates the hell outta me and I think I should just go back to ICS although I dont want to. HELLP!!! :-/
Thanks,
Ridge
Click to expand...
Click to collapse
Well i'm from brazil, and i have a question, sprint is CDMA? If the answer it's YES, do you flash a CDMA rom? if you flash a GSM rom it doesn't work
bk201doesntexist said:
It's a great kernel.
Doing the OTA might solve it since it will update (i think) your bootloader to lc03, you still on kk15. If it doesnt, use fastboot and update manually. To run an OTA with cwm installed, you need to download the update.zip from dev section for the OTA you want to run, but do it through cwm (like flashing a custom rom).
Sent from my tf201
Click to expand...
Click to collapse
Thanks for this post. I bought my mom a sprint gnex for mothers day, and sprint is pushing a 26mb ota. I put TWRP on her phone and rooted. Do I need the stock recovery to do the update, does the update break root?
Sorry, not familiar with Sammy or nexus devices, I've always used HTC. And the nexus forums are kinda hard to navigate because of the way it's split up.
Much thanks to anyone.
Sent from my EVO using xda premium
---------- Post added at 12:26 AM ---------- Previous post was at 12:25 AM ----------
andieknoxville said:
Well i'm from brazil, and i have a question, sprint is CDMA? If the answer it's YES, do you flash a CDMA rom? if you flash a GSM rom it doesn't work
Click to expand...
Click to collapse
Do not flash a GSM ROM on a CDMA device/radio.
Sent from my EVO using xda premium
I had update manually to 4.1.1 factory image, the bootloader has been updated, and the problem still here, maybe this is an efs folder corrupted?
If i get a backup from a gnex that all is working and restore will be fix ?
Thanks
???

[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

[Q] Generic IMEI after OTA 4.3 upgrade

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?

[Q] IMEI says 0 on 4.4.1

Hey guys, I think I screwed up. I think that I lost my IMEI through flashing it and I didn't make a back up. It says 0 and only very few of the *# codes work, the *#7285# and #22745927 codes do absolutely nothing and the only one that I know of that works is *#*#4636#*#* which doesn't help me at all. Most programs that I use don't detect the phone correctly or my phones just downright wrecked. Example is DFS says CPS N/A in every section and Samsung MEID Repair says "Unhandled exception has occurred in your application" when I try to connect it to my phone.
I'm running CM11 4.4.1 and I had the problem when I was running a 4.3 ROM. Also I have data and I can make calls. Its just that I cant send MMS and I drop to edge over time and stay on edge until I restart.
Any help would be greatly appreciated. Everyone I call is saying it'll cost $65 - $75 IF they can even fix it.
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Note that if you reinject IMEI, it might screw up your network
audit13 said:
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
I wish I could, When I try to use it, it says "Failed.. phone does not answer". Keep in mind that *#7284# doesnt do anything at all.
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
pcshano said:
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
chasetacos said:
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
Click to expand...
Click to collapse
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
pcshano said:
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
Click to expand...
Click to collapse
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
chasetacos said:
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
Click to expand...
Click to collapse
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
Click to expand...
Click to collapse
Cool. I Will do this and I will keep you updated. Itll be just a few moments before I complete the process
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
Click to expand...
Click to collapse
So when I try to flash the stock I get an error status 7. Any advice?
chasetacos said:
So when I try to flash the stock I get an error status 7. Any advice?
Click to expand...
Click to collapse
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Cool. It may not be till tonight or tomorrow till I respond, I'm about to have a project m competition. I'll let you know how it goes as soon as I get a chance.
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So now that Ive restored to stock, I have a transparent window with yellow text in it. it reads a bunch of info on the phone. It also said that it was in factory mode?
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So despite being stuck in factory mode I was able to write the NV and luckily I dont have any new network problems as far as I know. However my IMEI now says / 00 and in the phone info it says "unknown"
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
chasetacos said:
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
Click to expand...
Click to collapse
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
pcshano said:
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
Click to expand...
Click to collapse
Still nothing, im getting the same result. This Nv data bin file is not in there. i mean, unless i dont know where to look, but ive checked the whole EFS folder and its not in there...
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
elcocolo50 said:
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately that did nothing . I might just have to cry about it

Categories

Resources