Database Info

[Q] Galaxy Nexus radio/modem failure, baseband version : unknown

Hi,
I'm new to this forum.
I got a new Samsung Galaxy Nexus (unlocked GSM-i9250) mobile thruoug Google Store and got it to India.
I did an OTA upgrade from ICE Stock 4.0.4 to stock JB 4.1.1. My next upgrade to 4.1.2 failed, though detected by system failed.
So I used the phone for about 2 days and one day after charging, there was no radio service. WIFI works. Tried another SIM
and operator but in vain.
As all my efforts of factory reset, reboot etc failed, I thought of reflashing the latest images.
So I downloaded the latest images from Google site, unlocked the bootloader, followed different threads
and tried updating to 4.1.2. System now boots to 4.1.2 and WIFI works, but no GSM service still.
In the phone settings
Basebad version : unknown
Network : Unknown
IEMI : unknown
Service state : Out of service/Radio off (keeps toggling every 4-5 sec)
So I tried going back to 4.0.4 and system boots back to 4.0.4, but no GSM service
No idea what is happening. Two of us bought at the same time and got the same to India. For my friend, the OTA updates
to 4.1.1 and 4.1.2 went through fine.
I saw similar issues reported but not able to figure out how finally they solved it.
Any suggestions/help is appreciated.
Thanks in advance
Sanu

sanu.mathews said:
Hi,
I'm new to this forum.
I got a new Samsung Galaxy Nexus (unlocked GSM-i9250) mobile thruoug Google Store and got it to India.
I did an OTA upgrade from ICE Stock 4.0.4 to stock JB 4.1.1. My next upgrade to 4.1.2 failed, though detected by system failed.
So I used the phone for about 2 days and one day after charging, there was no radio service. WIFI works. Tried another SIM
and operator but in vain.
As all my efforts of factory reset, reboot etc failed, I thought of reflashing the latest images.
So I downloaded the latest images from Google site, unlocked the bootloader, followed different threads
and tried updating to 4.1.2. System now boots to 4.1.2 and WIFI works, but no GSM service still.
In the phone settings
Basebad version : unknown
Network : Unknown
IEMI : unknown
Service state : Out of service/Radio off (keeps toggling every 4-5 sec)
So I tried going back to 4.0.4 and system boots back to 4.0.4, but no GSM service
No idea what is happening. Two of us bought at the same time and got the same to India. For my friend, the OTA updates
to 4.1.1 and 4.1.2 went through fine.
I saw similar issues reported but not able to figure out how finally they solved it.
Any suggestions/help is appreciated.
Thanks in advance
Sanu
Click to expand...
Click to collapse
I had a similar experience with my previous Nexus S device. The phone would start up perfectly fine but it wouldn't catch reception. I think I flashed the wrong radio.img file (there are a lot of Nexus S variants).
I would try the following steps:
- Flash CWM recovery
- Flash a custom ROM (you can use "Mounts and Storage" in CWM recovery to gain temporary access to your internal storage - you will need to do this to copy your ROM file there)
- If you like it, just stick to the custom ROM.
If you insist on going back to the stock ROM, there are threads here that guide you to go back to stock completely. Even if you go back to a previous ICS ROM (specific to your phone), you should start receiving OTA updates normally.
Best of luck!

Thanks for the reply.
I'm almost sure the radio image is fine. I downloaded the images from
Google Nexus developers site for "takju" for Galaxy Nexus "maguro" matching with my phone.
I flashed matching ROM and radio images from Google site. Tried both ICS 4.0.4 & JB 4.1.2
I'll try custom ROMs if nothing works out. I'm going to try this first time, so need to chk the threads first. This is my first Andriod phone and already ran into trouble after just 2 days of use, that too without any manual flashing. Only OTA happened before the issue.
Could the h/w have gone bad ?
In fastboot mode, the radio version is displayed correctly, but not after phone is up and running.
If the h/w has become faulty, I still expect the "Baseband version" in "About Phone" to be correct.
Is this assumption correct ? If it is s/w issue, I'm relived and I can try some custom image. So I'm hoping its only a s/w glitch.
Thanks a lot

you flashed the wrong rom on your phone and corrupted its efs partition. If you have a backup (why should you if you didn't even know that it was that to fail your phone's radio..) you could proceed and restore it. If you don't it's a big mess and you might have to go to a repair service.
Anyway you could still try and flash the original ROM for your phone and see if it fixes the problem. If not there are tools on the web (search the forums) that could try and restore your partition even if you don't have a backup.
If you succeed in restoring your phone don't EVER forget to backup you /efs partition

Thanks.
I tried flashing as the phone radio just stopped working after I charged the phone one day morning.
Let me follow your suggestions. I didn't know about efs partition. may be its messed up
What is puzzling me is, how can the factory images from google be wrong.
clait said:
you flashed the wrong rom on your phone and corrupted its efs partition. If you have a backup (why should you if you didn't even know that it was that to fail your phone's radio..) you could proceed and restore it. If you don't it's a big mess and you might have to go to a repair service.
Anyway you could still try and flash the original ROM for your phone and see if it fixes the problem. If not there are tools on the web (search the forums) that could try and restore your partition even if you don't have a backup.
If you succeed in restoring your phone don't EVER forget to backup you /efs partition
Click to expand...
Click to collapse

sanu.mathews said:
Thanks.
I tried flashing as the phone radio just stopped working after I charged the phone one day morning.
Let me follow your suggestions. I didn't know about efs partition. may be its messed up
What is puzzling me is, how can the factory images from google be wrong.
Click to expand...
Click to collapse
It's not the factory images to be wrong but the fact that if the /efs partition is really corrupted the stock images don't contain the info necessary to flash that partition as well.
In fact it may become corrupted after a wrong flashing but a new, correct, flash won't restore it. The only way back is the /efs backup.
What if you type *#06#? Does it show you an IMEI number or what?

*#06# shows "OK"
clait said:
It's not the factory images to be wrong but the fact that if the /efs partition is really corrupted the stock images don't contain the info necessary to flash that partition as well.
In fact it may become corrupted after a wrong flashing but a new, correct, flash won't restore it. The only way back is the /efs backup.
What if you type *#06#? Does it show you an IMEI number or what?
Click to expand...
Click to collapse

sanu.mathews said:
*#06# shows "OK"
Click to expand...
Click to collapse
Between the blue line and the OK it should show the sixteen digit long IMEI number. the fact that it isn't shown simplifies the diagnosis. I'm 100% sure you've got your /efs partition corrupted.
Please do a forum search on how to restore it.
Sent from my GT-I9300 using Tapatalk 2

Thanks a lot.
This eliminates so much un-wanted time waste/means no need to try various steps.
Can I get efs dump from another Galaxy nexus and flash it on mine after rooting ?
I'm under the impression that IEMI number etc should be in OTP and that can't get corrupted but efs may have some meta data regarding the same
clait said:
Between the blue line and the OK it should show the sixteen digit long IMEI number. the fact that it isn't shown simplifies the diagnosis. I'm 100% sure you've got your /efs partition corrupted.
Please do a forum search on how to restore it.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse

sanu.mathews said:
Can I get efs dump from another Galaxy nexus and flash it on mine after rooting ?
Click to expand...
Click to collapse
No can do, the IMEI is a per device unique number.
Check this thread and do some forum search: http://forum.xda-developers.com/showthread.php?t=1689525
You're not the only one that lost the IMEI so chances are likely to you to resolve your issue!

If I copy the IMEI number from the box or my working phone, will it work ?
What I want to know is, is it only coming from EFS or if IMEI is changed will be there be some signature that will fail etc
I have used fastboot but not sure about rooting, so need to read that before trying Rooting
In India, Samsung won't repair my phone as I got it from US.
Another worry is, let IMEI number be wrong and let there be no network, but atleast "Baseband version : Unknown" shdn't come in the phone, correct ? Coud there be any issue with radio image partition itself ?
clait said:
No can do, the IMEI is a per device unique number.
Check this thread and do some forum search: http://forum.xda-developers.com/showthread.php?t=1689525
You're not the only one that lost the IMEI so chances are likely to you to resolve your issue!
Click to expand...
Click to collapse

sanu.mathews said:
If I copy the IMEI number from the box or my working phone, will it work ?
What I want to know is, is it only coming from EFS or if IMEI is changed will be there be some signature that will fail etc
I have used fastboot but not sure about rooting, so need to read that before trying Rooting
In India, Samsung won't repair my phone as I got it from US.
Another worry is, let IMEI number be wrong and let there be no network, but atleast "Baseband version : Unknown" shdn't come in the phone, correct ? Coud there be any issue with radio image partition itself ?
Click to expand...
Click to collapse
Mate - I too am from India, and I too got the exact same problem, and I too tried all you did - all this about a month back. I have reconciled myself to the fact that its a hardware issue. Since samsung centers in India won't do any repairs, I'm afraid we're both stuck with really expensive music players.
My sympathies.

Fixed by sending in for warranty
Just an update...I was having all of these symptoms...unknown IMEI, Baseband, etc...basically gave me an expensive media player for a few months while waiting for a fix on XDA. After no update I decided to call up Samsung and after talking to 3 different technicians, I was able to send it in. Just a note for anyone about to do the same, they will try very hard to blame it on the carrier/SIM card, so save yourself some trouble and just say you already went to the physical store of your carrier (calling isn't enough)and they couldn't get it working. Once you get past that, they will email you a printable 2-day UPS shipping label so you can ship it to them for free. It took 2 weeks from the time I called to having a working phone back in my hands.
This was their fix:
Problem found:
NO PCS SERVICE
Solution:
REPLACED PBA
After a quick search I found that the PBA is the motherboard, so it's definitely a hardware issue. Hope you guys are still under warranty because I've heard this is ~$200 to fix otherwise.
Good luck.

Dropping data and no calls/texts. Advice please.

Just in case this post gets moved, I want to identify my device as the Verizon Samsung Galaxy S3 (i535).
To give a little background on my issue, I have an issue with the device. When I first got it back in July, first thing I did was root the device. Naturally, since it was a new device, I was working with experimental methods... a couple weeks ago I thought to download CyanogenMod 10.1 (nightly build) to flash it with 4.2 and rid myself of the persistent OTA update that as we all know could not effectively install because of the measures I took to root. So, I boot into recovery and flash my custom rom. BAM! As it turns out, I did not have an unlocked bootloader and my phone was now teetering on the verge of being a $600 paperweight. I got that dumb yellow triangle saying unofficial firmware detected or some nonsense like that... Anyway, I look around the internet and decided that I was going to revert back to a stock rom using Odin, and then proceed to unlock my bootloader and root the device (I followed method 3 here) I used some touch recovery console that I have never heard of before (backups incompatible with ClockworkMod recovery) and something must have failed because my back up would not flash. I took the hit on losing most everything and reflashed successfully the custom rom mentioned earlier.
After about a week, I noticed the device began to drop data. 4G would just stop at random parts of the day, and I would have to disable and enable the data to get it to reconnect. At this point I was still able to make and receive phone calls and texts. After about 3 days of this, I concluded it was more than likely a bug in the custom rom, and that I could not live with it... so I redid the a fore mentioned tutorial and left the phone as a stock/unlocked/rooted device. The data issue continued, but with a twist. I was now unable to make or receive phone calls or texts. No matter what I did, I could not do anything and the 4G would only stay connected for a matter 5 minutes or so. When I logged into my vzw account, it identified my device as an unknown non-verizon device. Customer service walked me through various soft/hard reset techniques and nothing worked. They also suggested I try a new SIM card, which failed to work.
So, I turn to the bright minds of the android community. I have already decided not to invoke the Verizon warranty offered, where the result is they take my malfunctioning phone in flawless cosmetic condition and replace it with a "like-new" phone in working condition, because I think it's garbage that a warranty would give out used crap (should fix or replace). I have not contacted Samsung customer support yet because I wanted to see what my options were. I've already attempted flashing different radios and nothing seem to make any difference. If I have to, I will revert it back to stock again and invoke Samsung's warranty program, but I would much rather keep the phone. As it sits, I am stuck with my Motorola Droid Razr Maxx, and that just doesn't cut it.
So I ask, is there anything that can be done? Anyone know of a fix for my situation? I saw something about this in my quest for an answer and I don't know if my situation is a fit for this fix. If anyone has any knowledge of my issue and a work around for it, it would be greatly appreciated. I am at my whits end.

It sounds like you've done your homework on your problem.. The only thing in your post I didn't see was your sim card.. Maybe pulling it wait 2min restart. Shut down and insert,, or maybe a reprovision of the sim may be in order..
Ahaaaa....!!!

If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.

HHF2 said:
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
Click to expand...
Click to collapse
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.

mkruluts said:
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
Click to expand...
Click to collapse
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.

HHF2 said:
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
Click to expand...
Click to collapse
Ok. So I tried the reprovsioning mentioned above. When my phone rebooted I was on data and able to make phone calls. Score! However, I checked the IMEI and it said 0. So, thinking that it was just a matter of time before my device began to stop working again... I did the IMEI fix. Now my phone is placing calls and holding data without issue. The OTA updates are flooding in and installing without issues.
I would like to point out, while I feel better having done the combination of both reprovisioning and IMEI fix, ultimately the initial reprovisioning did appear to resolve the issue.
Thanks to everyone for the assistance provided.

[Q] NV_DATA.BIN and BAK Files Missing - Thus no service what-so-ever

ok so here's the deal folks. I've been trying to fix this problem on my ATT Skyrocke since the 21st. I had flashed a copy of the Liquid Smooth ROM with all data working. Bear in mind, this S2 is net unlocked and APN settings are changeable with my sim card in, and everything is set to Straight Talk APN settings. When LS ROM was installed, everything worked fine, til this fateful day of the 21st where everything just stopped... No network, no data, no nothing. Every once in a while my network shows up and allows me to make short phone calls ranging from 45 seconds to 10 minutes, and sms/mms are even more widely spread on being able to receive. After going through my EFS folder, it seems that the phone is missing a critical file named nv_data. I have everything else in the EFS folder that should be there, at least from my experience, but my data still will not come back up. SOMEONE PLEASE TELL ME THIS IS FIXABLE!!!!!!!!!!!!! I'm losing my mind, considering this is my only work phone for my business, and as of yet, i don't have enough income from this business to buy a new phone.
EDIT*****
Before I forget, which I already did once, I have tried the following steps to fix this:
1: Bought a new sim card tray through ebay - no change
2: Flashed back to stock ROM - (multiple times) no change
3: Flashed multiple older roms - no change
4: Ran the EFSFix off of this: http://forum.xda-developers.com/showthread.php?t=1611796
Currently looking at performing a dark side wipe to install a new custom rom, but not sure if this will work yet or not.

420tuprophit13 said:
ok so here's the deal folks. I've been trying to fix this problem on my ATT Skyrocke since the 21st. I had flashed a copy of the Liquid Smooth ROM with all data working. Bear in mind, this S2 is net unlocked and APN settings are changeable with my sim card in, and everything is set to Straight Talk APN settings. When LS ROM was installed, everything worked fine, til this fateful day of the 21st where everything just stopped... No network, no data, no nothing. Every once in a while my network shows up and allows me to make short phone calls ranging from 45 seconds to 10 minutes, and sms/mms are even more widely spread on being able to receive. After going through my EFS folder, it seems that the phone is missing a critical file named nv_data. I have everything else in the EFS folder that should be there, at least from my experience, but my data still will not come back up. SOMEONE PLEASE TELL ME THIS IS FIXABLE!!!!!!!!!!!!! I'm losing my mind, considering this is my only work phone for my business, and as of yet, i don't have enough income from this business to buy a new phone.
EDIT*****
Before I forget, which I already did once, I have tried the following steps to fix this:
1: Bought a new sim card tray through ebay - no change
2: Flashed back to stock ROM - (multiple times) no change
3: Flashed multiple older roms - no change
4: Ran the EFSFix off of this: http://forum.xda-developers.com/showthread.php?t=1611796
Currently looking at performing a dark side wipe to install a new custom rom, but not sure if this will work yet or not.
Click to expand...
Click to collapse
goto READ THIS B4 POSTING | THE MOST Common Questions Answered HERE read/do q)25.d and borrow someones active att sim card, if after that phone still doesnt work right then its some kind of hw failure

hey vin. actually i had tried that thread and instructions for such already. although i went ahead and did it again in hopes that maybe i just did it wrong, but no change.
Here's a little update:
The baseband is known, running on I727UCMC1 baseband, but the IMEI number shows up as 0/00. I spent the entire night searching the forums here and over at androidforums.com and ran through google. There's no listing of the baseband being known, but the imei number being corrupt. Maybe I'm just using the wrong keywords... IDK but I do know this is really strange. I've never ran into this issue before.
So anyone know why the Baseband would be known, but the IMEI corrupt?

420tuprophit13 said:
hey vin. actually i had tried that thread and instructions for such already. although i went ahead and did it again in hopes that maybe i just did it wrong, but no change.
Here's a little update:
The baseband is known, running on I727UCMC1 baseband, but the IMEI number shows up as 0/00. I spent the entire night searching the forums here and over at androidforums.com and ran through google. There's no listing of the baseband being known, but the imei number being corrupt. Maybe I'm just using the wrong keywords... IDK but I do know this is really strange. I've never ran into this issue before.
So anyone know why the Baseband would be known, but the IMEI corrupt?
Click to expand...
Click to collapse
baseband aka radio has nothing todo w/the imei.
as to why imei got corrupted, idk why it happened and i dont know if theres a fix for that
edit: a bad radio might corrupt the efs folder though not sure if thats what happened to u
it seems you might have a corrupted efs folder
search for corrupted imei
try this http://forum.xda-developers.com/showthread.php?t=1611796

No cellular connectivity whatsoever

So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?

gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?
Click to expand...
Click to collapse
Try restoring via fastboot for a clean slate. I understand from your post that you're flashing via custom recovery.

gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day
Click to expand...
Click to collapse
CM12.1 may flash the new radio that OxygenOS flashes, from which there is not necessarily an immediate return.
Possible you have that new radio. See here:
https://forums.oneplus.net/threads/oxygenos-back-to-cm11s.296219/#post-10851703

gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?
Click to expand...
Click to collapse
Can you still see your baseband and IMEI? Go into Settings/About Phone for the baseband version and Settings/About Phone/Status for the IMEI.
Transmitted via Bacon

Baseband is unknown and there's no mention of IMEI anymore... does that mean I lost my IMEI/it got corrupted? Am I screwed? I planned on trying the fastboot restore but only as one of the last resorts. If CM12.1 use the same radio then my 12.1 should work but that doesn't either. Nothing works. I've tried CM11s, CM12, CM12S, CM12.1... sigh...
I think I had a modem/efs backup in one of my nandroids and I tried restoring that too with no luck
Restored one of my CM12 nandroids and now I have a baseband of "DI.3.0.c6-00230-M8974AAAAANAZM-1". For some reason or another, that doesn't look right to me even though I've never really paid attention to what the baseband ever listed. Still can't seem to locate my IMEI #. I did the #*#*4636*#*# and the cell radio is on and turning it off and one still only shows emergency calls only. Obviously I'm not going to try to call 911 just to test if the radio gets service. However, I can see my IMEI # so I guess that's good. I must have some bad firmware update. Guess I'll copy out all my stuff to my otg usb and fastboot restore and see if that helps unless there's something else I can try.... please let me know...

gqukyo said:
Baseband is unknown and there's no mention of IMEI anymore... does that mean I lost my IMEI/it got corrupted? Am I screwed? I planned on trying the fastboot restore but only as one of the last resorts. If CM12.1 use the same radio then my 12.1 should work but that doesn't either. Nothing works. I've tried CM11s, CM12, CM12S, CM12.1... sigh...
I think I had a modem/efs backup in one of my nandroids and I tried restoring that too with no luck
Restored one of my CM12 nandroids and now I have a baseband of "DI.3.0.c6-00230-M8974AAAAANAZM-1". For some reason or another, that doesn't look right to me even though I've never really paid attention to what the baseband ever listed. Still can't seem to locate my IMEI #. I did the #*#*4636*#*# and the cell radio is on and turning it off and one still only shows emergency calls only. Obviously I'm not going to try to call 911 just to test if the radio gets service. It really does look like it's my IMEI # that got jacked... what can I do now?.... :T
Click to expand...
Click to collapse
You've got a corrupt EFS partition. There's a thread detailing how to fix your situation in our general section.
Transmitted via Bacon

tried to flash the persist.img from http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 but that just prevents my phone from booting up properly. I only see the OnePlus logo with not Powered by Android on the bottom...
I take it back, it does show the powered by android but only for a split second then it stays on the OnePlus logo and doesn't do anything... :T
Restored back most recent cm12.1 nandroid and now I do see IMEI number in the about settings but still only emergency calls only... Guess its a good start, no sure what else I can do at this point.

Now you see your imei but you dont have the signal,it means your modem file does not work.So the first thing to do is backing up the efs then you can flash 44s modem and proximity patch.Probably it will work.It worked for me.

Ok there may be hope then. Just flashed the 44s modem then nandroided back to my CM11s then flashed modem again just in case lol. Don't recall seeing a proximity fix but it's ok as long as my cellular connectivity works, I'll deal w/ other issues later. Otherwise all I have is an expensive media player... lol it's booting up now so we'll see... *fingers crossed*
Nope didnt work...going to try a fresh CM12 install...
Trying to flash roms and in the wizards it always states I don't have a sim installed so I'm not sure it's my modem that's messed up or if it's something else related to hardware related to the sim. The sim itself works in my other phone... tried a different sim and it's still emergency calls only. don't know what to do now. doing all this and it's still not working so I doubt even the fastboot restore would work... might just have to rma... which would probably take 4eva...

Pls flash your nandroid backup which gave you the imei first,after gain your imei ,back up it,then you can flash what rom you like,if you dont have your imei,just flash your imei backup.The most important thing is to back up your efs.
Sent from my A0001 using XDA Free mobile app

Think my efs is fine as I can see the IMEI now but no matter what nandroid and fresh install I try, I can't get the cellular connectivity to work. I backed up all partitions just in case.

gqukyo said:
Think my efs is fine as I can see the IMEI now but no matter what nandroid and fresh install I try, I can't get the cellular connectivity to work. I backed up all partitions just in case.
Click to expand...
Click to collapse
Being able to see your IMEI doesn't necessarily mean your EFS is ok.
Transmitted via Bacon

Well tried the persist.img but that didn't work so what else can I do?

The one thing that would definitely fix your issues would be if you had an EFS backup. I don't know why people don't do this. Without that I have no idea what you can do.
Transmitted via Bacon

Never had that issue before and I've own android phones from the HTC Hero. Lesson learned though, thankfully it's still under warranty and it's not that expensive a phone...

gqukyo said:
Never had that issue before and I've own android phones from the HTC Hero. Lesson learned though, thankfully it's still under warranty and it's not that expensive a phone...
Click to expand...
Click to collapse
Not all Android phones employ an EFS partition. I'd never heard of it before this phone but a bit of research on my part revealed the importance of an EFS backup.
Transmitted via Bacon

That would make sense then. As I was reading about EFS, seems like it was mostly Samsung phones. I guess I can try a fastboot restore... nothing else to lose. lol
Doh! apparently there is something to lose when fastboot restoring... phone stopped booting back up correctly after a few fastboot restores and now it won't even turn back on... lovely... at least I had a expensive android media player before, now I have a brick... lol

Edited - Sorry

I have the same issue with all verisons of CM12. I get No service. Although the XNPH44S radio was the best. Meaning I could atleast see 3-4 bars for about 1 second and then off for a couple of minutes and then back on again for 1 second and so on. I believe it is a problem with not having a proper radio. One plus should release a better working radio in my opinion. I am on PTEL Mobile network (uses T-Mobile). So until we get a good working version of the radio I think some people like us are stuck on cm11.

OnePlus One... I'm pretty sure I messed up my EFS partition.

UPDATE:
I have baseband wifi and bluetooth back but my IMEI is still showing up as 0 and no signal. I know the phone is reading the sim because I can see the phone number saved on the sim info.
Also getting "OEM_NV_Backup The NV Partition is invalid!" when I boot OxygenOS
Does anyone know where I can get 16GB installs for ColorOS and OxygenOS? I have a 16GB phone but when I use the msm download tool to install ColorOS I end up with a 64GB install.

Do you have any backup for the EFS partition?

I had same problem about EFS partition and No IMEI too. So I am almost sure that flashing completely untouched official Oxygen OS downloaded straight from official site will solve your problem as it did mine. Just download "Build" from here (oneplus forum) and flash it with latest TWRP. After that you'll get your fully working network connectivity back. Then just flash any other ROM you like, but look for perfect modem first (c6 works best in Asia and c7 rest of the world, but try both if you want). All the best :fingers-crossed::good:

SaurabhMumbaiOneS said:
I had same problem about EFS partition and No IMEI too. So I am almost sure that flashing completely untouched official Oxygen OS downloaded straight from official site will solve your problem as it did mine. Just download "Build" from here (oneplus forum) and flash it with latest TWRP. After that you'll get your fully working network connectivity back. Then just flash any other ROM you like, but look for perfect modem first (c6 works best in Asia and c7 rest of the world, but try both if you want). All the best :fingers-crossed::good:
Click to expand...
Click to collapse
gonna try that now, should I take any other steps before flashing in twrp like wiping anything?

so I tried installing oxygen through twrp but I was getting error 7 (phone is marked as A0001 and install is marked for OnePlus). I tried using the files and instructions from the oxygen 2.14 thread and somehow my phone hard bricked lol, I've learned so much about this phone in the last 2 months.
Gonna throw ColorOS on there and try going straight to OxygenOS from there.

So I had to wipe everything (system, cache, etc) before twrp let me install oxygen. I got oxygen installed but now it loops in oneplus screen and I got this issue come up after installation finished

Some more progress... was able to install oxygen os finally and it look like I'm almost done coming back from this nightmare. Baseband is back, WiFi and Bluetooth work, now just need to see about restoring my iemi, I've found some info on how to restore imei so I'll try that tomorrow sometime after waking up. I've learned so much about this damn phone! !

My bottom screen has also stopped working. The replacement screen you brought from, it is original or clone?? How does it feel to the screen when you buyed the phone from your friend. And i hope you'll get back your imei too

Rex2688 said:
My bottom screen has also stopped working. The replacement screen you brought from, it is original or clone?? How does it feel to the screen when you buyed the phone from your friend. And i hope you'll get back your imei too
Click to expand...
Click to collapse
It's not original. Screen is fine the only downside to non oem front assembly is that that capacitive buttons will not be as bright, some have reported that they don't light up at all, seems to be luck of the draw.

intehweeds said:
Some more progress... was able to install oxygen os finally and it look like I'm almost done coming back from this nightmare. Baseband is back, WiFi and Bluetooth work, now just need to see about restoring my iemi, I've found some info on how to restore imei so I'll try that tomorrow sometime after waking up. I've learned so much about this damn phone! !
Click to expand...
Click to collapse
As I can see from your screenshot from previous reply, you are not using official ROM. Completely official ROM is named as "OnePlus_Bacon_OxygenOS_201601190107". There was no need to wipe internal storage. Use this guide to modify the updater script. It worked for me perfectly. Then flash it and just boot into ROM. I was able to recover everything including IMEI number by this method.
And yeah, I feel the same way. I've learned so much from our beloved Bacon :laugh:

intehweeds said:
Some more progress... was able to install oxygen os finally and it look like I'm almost done coming back from this nightmare. Baseband is back, WiFi and Bluetooth work, now just need to see about restoring my iemi, I've found some info on how to restore imei so I'll try that tomorrow sometime after waking up. I've learned so much about this damn phone! !
Click to expand...
Click to collapse
You have baseband so your imei is back

yet another update
installed oxygenos with twrp, I have baseband wifi and everything but no data signal and my IMEI is 0
I've hit yet another wall :crying:
Why isn't there a 16GB version of ColorOS and OxygenOS? When I install ColorOS via msm download tool I end up with a 64GB install, I think this might be causing my "OEM_NV_Backup The NV partition is invalid!" issues as well.
Just need to resolve those two issues, bad nv partition and my IMEI being 0
Anybody know where I can get a 16GB version of colorOS, I have a feeling I overlooked something I was supposed to tweak

giaur said:
You have baseband so your imei is back
Click to expand...
Click to collapse
That's what I thought but my IMEI still shows up as 0

I don't understand why you are not flashing official Oxygen OS even after saying it solved each and everything for me?? And since it is official, it is bound to support 16 GB variant as well.

http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Ok, so the link I posted should be a last resort. You will find a recovery tool that I used when my IMEI would not return correctly. Follow all instructions, but do note that this will completely wipe everything, and if I remember correctly, that includes all personal files. The tool should land you back on the original software (like CM11S). I say try EVERYTHING else people tell you first before doing this. You're essentially starting over your phone. Good luck!
EDIT: Your recovery will be stock as well.

SaurabhMumbaiOneS said:
I don't understand why you are not flashing official Oxygen OS even after saying it solved each and everything for me?? And since it is official, it is bound to support 16 GB variant as well.
Click to expand...
Click to collapse
I did flash the official one. I used the link from the oneplus page that takes me to a forum post. At first I wasn't able to do it with twrp but afterwards I was able to
I did it once with the tool they provided and a second time through twrp, imei still 0

Inflection said:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Ok, so the link I posted should be a last resort. You will find a recovery tool that I used when my IMEI would not return correctly. Follow all instructions, but do note that this will completely wipe everything, and if I remember correctly, that includes all personal files. The tool should land you back on the original software (like CM11S). I say try EVERYTHING else people tell you first before doing this. You're essentially starting over your phone. Good luck!
EDIT: Your recovery will be stock as well.
Click to expand...
Click to collapse
done this already and still IMEI is 0

intehweeds said:
done this already and still IMEI is 0
Click to expand...
Click to collapse
Aww, I'm sorry man. Best of luck finding a solution.