Related
Hello,
Please help if you can! I updated my Nexus S to 2.3.4 the other day, and everything was working fine. Today, the phone at some point lost the ability to connect to my network (Bell Mobility). I was out and about and was turning data off, and might have hit the 2g/3g toggle by accident, and seem to remember reading about that causing problems - though I have no idea if I did for sure (the sun was bright) and am honestly not sure what's wrong EDIT: when I go into wireless & networks\mobile networks\network operators, the phone will only recognize Roger's Wireless (and it was bought at a Telus store!) The UI still works fine, and I can still connect via wifi - just no way to get it to recognize Bell's network
As stated above, everything was working fine this morning - voice, data and sms all good. Here is all the info from my phone:
Android version 2.3.4
Baseband version NO DGSXXKD1
Kernel Version 2.6.35.7-ge383d80 [email protected] #1
Build number GRJ22
The bootloader is unlocked, and I had been running CM7 before flashing the manual 2.3.4. I'm not sure what to do. Tried re-flashing the manual 2.3.4 update.zip, and nothing. I know a very little bit about rooting/flashing (just enough to follow guides), and am wondering whether I need to re-flash a different kernel/radio/rom or something. I did search, and couldn't find anything that outlined my problem exactly (I do apologize if something is out there and I just didn't look hard enough).
Again, the phone was bought new at a Telus store, and found the Bell Mobility network out of the box no problem. Am hoping someone can help!
Thanks so much for reading, and if you are able to help.
Check your APN's to make sure the data info is in there I had to manually enter mine (bought phone from Telus to use on Bell/Sasktel's network) for Sasktel and bob was my uncle
Every upgrade i need to put them back in. No automatic for me, so i would start there
Menu - Settings - Wireless & Network - Mobile Networks - Access Point Names.
If nothing is in there, you need your APN settings. Talk to bell support for the info, and they should be able to help you over the phone (they support android even if they dont sell a Nexus S)
Cheers!
Thanks so much for your response, though I don't think that the APN's are the issue at all; they're still in there and fine. I think that it's the actual radio (or baseband), as the phone will not recognize the bell network, only the Rogers network (and it was bought new at a Telus store!)
I think that I need to re-flash the radio, and maybe the kernel. I searched to try and find the radio image for my phone, but haven't found anything clear enough for me to be comfortable to try - I've read time and again that flashing radios is one of the riskier things to do. I don't think that my phone is bricked (can still boot it up, and all of the ui works and can connect via wifi). Don't want to risk doing more damage.
Thanks again for your response though!
i think i'm having the same problem. i've manually upgraded to 2.3.3 then to 2.3.4. and then i put a sim card in - not used it as a phone before this.
i can get 3-4 white bars lit up but can't connect to any network. the bars turn green when wifi is active, but still can't connect ("can't connect at this time. please try again later" toast appears). not sure if the phone is borked, or if the upgrade wasn't that successful.
I actually have this same issue but using it on at&t in the USA...Really hope it isn't broken cause I have no way to fix it since i'm not in canada
Maybe check if the 2g box is checked in mobile networks. Check your apn settings and if that doesn't help try and flash another radio.
Sent from my Nexus S using Tapatalk
djnoicatse said:
Maybe check if the 2g box is checked in mobile networks. Check your apn settings and if that doesn't help try and flash another radio.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
i'm unrooted, and don't intend to root. apn is fine as suggested above, and regardless of 2g checked or unchecked, still no connect
Rogers is the only 2G gsm provider, your phone may be stuck on 2G. If you have the choice, I would go back to 2.3.3 full stock and see if everything then works.
Sent from my Nexus S
Matridom said:
Rogers is the only 2G gsm provider, your phone may be stuck on 2G. If you have the choice, I would go back to 2.3.3 full stock and see if everything then works.
Sent from my Nexus S
Click to expand...
Click to collapse
but you have to root to flash 2.3.3 right?
MarkusPO said:
but you have to root to flash 2.3.3 right?
Click to expand...
Click to collapse
No. you are best to use cwm and restore a stock image for your phone
Sent from my Nexus S
Your best option is to flash back to 2.3.3. Download rom manager from the market and flash clockwork recovery. Once in recovery flash the 2.3.3 .zip file. I saw it somewhere here but i forgot where I saw it. Hope that helps.
Sent from my Nexus S using Tapatalk
Try this http://devsforandroid.com/index.php?board=18.0
I'm NOT SURE if it'll work, but it's worth the try. Make sure to to wipe everything before you flash. I'm not responsible for any damage this may cause. But I hope this helps you out.
If anyone wants to chime in and correct me please do so.
Sent from my Nexus S using Tapatalk
Or if you're not comfortable flashing the stock 2.3.3 rom maybe just try and flash back the xxkb2 radio which I believe was the stock baseband for Rogers, telus, Fido and bell. I have the .zip file for you to try and flash through CWM if you need it. Otherwise you can find it somewhere here aswell.
Sent from my Nexus S using Tapatalk
i'm not looking to root nor use any 'hacks'. i don't trust them.
under the battery, the phone is just a i9020. no letter afterwards.
Flashing a ROM doesn't require root, it requires unlocking the bootloader, which Google officially allows you to do that. You can unlock the bootloader, flash 2.3.3 ROM, then lock it as if it had never been unlocked. Just keep in mind that unlocking resets to factory default and wipes your SD card clean, backup before you do it.
Ahhh yes, I had same thing except with Telus I fixed it once, but the second time I could not get it to work, do this, flash this radio
http://forum.xda-developers.com/showthread.php?t=1044261
it is the stock radio your phone came with, then call up bell and get them to "repush" your sim card... hopefully you will see your network again.
Si_NZ said:
Flashing a ROM doesn't require root, it requires unlocking the bootloader, which Google officially allows you to do that. You can unlock the bootloader, flash 2.3.3 ROM, then lock it as if it had never been unlocked. Just keep in mind that unlocking resets to factory default and wipes your SD card clean, backup before you do it.
Click to expand...
Click to collapse
if i unlock to then flash, don't i need a radio package? how do i know which one to use?
also, would i be able to do a full compile of android and flash that?
MarkusPO said:
if i unlock to then flash, don't i need a radio package? how do i know which one to use?
also, would i be able to do a full compile of android and flash that?
Click to expand...
Click to collapse
It depends on which ROM you flash. I flashed the official 2.3.3 ROM, it contains the radio image, it'll flash it as you apply the update.
Do you remember which baseband version it came with out of box? That should give us hint as to which radio applies to your phone. I think there are really only two types of radios used except NS 4G, 850/1900/2100 (i9020A radio) and 900/1700/2100 (i9020T radio). You can ask your service provider or check out their website which band you are running on.
Back to flashing ROM, I just realised you don't even need to unlock the bootloader if you are flashing Google signed files. You should most likely be able to flash a 2.3.3 full ROM, then flash the 2.3.4 update file. But if you find the 2.3.4 full ROM, that's even more convenient. I saw a full ROM on the forum, but I that was for i9023 or i9020. Not too sure, maybe others know.
For the Canadian carriers, as stated before, Rogers is the only 2g (edge) carrier all others (Bell, Telus, Sasktel) are 3g (HSPA). go Settings>Wireless & network settings>mobile networks and ensure "Use only 2g networks" is not selected.
If this does not work flash the KB2 modem, the other modems may lose 850mHz spectrum which could be causing your grief.
Solution!!! (At least this worked for me!) - Didn't have to flash anything
Hey all,
I apologize for not posting this sooner, but found a solution that worked for me, hope it might work for others experiencing the same problem.
**PLEASE keep in mind that though this worked for me, I don't know if it will work for you (maybe it might make things worse for some people). Especially keeping in mind that I DON'T KNOW FOR CERTAIN what originally caused the issue for me, nor what specific factors (rom build, phone model, radio image, etc) might have contributed. As well, I am on the Bell Network. USE ANY OF WHAT'S STATED BELOW AT YOUR OWN RISK. Disclaimer stated, read on...**
In the dialer, I punched in *#*#4636#*#* and then from the menu that popped up, selected Phone Information.
From there, in the Set preferred network type: drop down menu (scroll down a little, you'll see it) I selected GSM/CDMA auto (PRL). **Again, remember that I'm on the Bell Network in Canada. Should you be trying this, these settings might not be for you. Again, AT YOUR OWN RISK**
Then, still from the Phone Information screen, I pressed menu button (the hard menu button on the phone), and then chose the Select Radio Band option. From there, I believe I selected Auto, though I may have selected USA (It's been a couple of days, and I can't remember, I apologize).
After that, went back to the Phone Information menu, and pressed Run Ping Test. It seemed to show all of the necessary (and appropriate for my network) settings as ok, and... everything worked!!! Full network connection as before!
Hope this might help someone else! Keep in mind that I'm not sure what caused the original problem; I do believe I remember pressing the 2g/3g toggle, and also remember reading somewhere that this can cause problems. Specifically, that it stopped peoples phones from going back from 2g to 3g - in my case (Bell Mobility) there is no 2g network to drop down to, so if it got stuck on EDGE mode, it probable looked for the only local carrier with a GM EDGE network, (Rogers) and got stuck there. Not sure, but maybe this is what happened. Any wise folks out there that might be able to confirm/offer insight?
Anyhow, thanks so much for all the responses and offers of help!
I just ordered a recertified Verizon 3G Xoom, and I didn't think about the implications of it being a Verizon device. This is NOT upgraded to 4G LTE -- will the "Stingray" builds of the various ROMS still work? Is there any way to apply WIFI-only ROMS (including stock) if I don't care about the 3G working? Given the age of the device I really want to get Jelly Bean on it.
I will need to cancel this order ASAP if the answers to these questions turn out to be "no"...
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
trunzoc said:
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
Click to expand...
Click to collapse
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
magnafides said:
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
Click to expand...
Click to collapse
Thanks. I'm placing my order as soon as Wife says OK. If you don't mind, and if you remember, please send me a PM of how it goes with the flashing once to get yours.
Would love to coordinate what we do since there doesn;t seem like a whole lot of certainty exists about what we are trying to do.
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
magnafides said:
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
Click to expand...
Click to collapse
Any luck? I also have a Xoom 3G MZ600 on the way and could careless about 3G...
hasnt eos got jellybean roms for all versions of the xoom? 3g should work imo
Sent from my Xoom using XDA Premium App
I'm in the same boat and curious to see if anybody has any words of wisdom. I love my refurbed Xoom 3G but am eager to get JB on it. Any help is greatly appreciated.
FWIW everything I have heard/read seems to indicate that it is possible to flash WiFi only ROMs on the 3G Xoom, and apparently everything will work fine except for the 3G (naturally). I haven't taken the plunge yet myself, still running stock ICS.
Is there any word on whether the Verizon 3G Xoom will get Jelly Bean?
It can be done....
I purchased a used 3g Xoom around Apr 2012. After initially unlocking / rooting and installing a ROM (EOS) on my 3g Xoom, the 3G radio wasn't working so I started fresh. I locked the device and SBF'd the original Xoom firmware, then used the official over the air (OTA) upgrades to get back to stock ICS. I thought this might fix the 3g issue; it did nothing.
EOS Roms overclock the GPU by default, which caused problems with my (and my wife's Wifi version) Xoom. My only requirements for a ROM are stability, no clutter from dumb carrier installed applications, compatibility, and of course root access. I found a pre-rooted stock Jellybean rom, but it was for the Wifi Xoom. It worked great on my wife's though; and heard rumors that it could work with mine.
*SO*...I took a leap of faith and installed it. It works great. No 3g radio of course, but I gave up on trying to get that to work anyway...so if you don't care about losing your 3g , this will probably work for you. I don't think my 3g will ever work, but I suspect this won't ruin yours if it is currently working. Don't hold me to that; this is a risk.
Random notes and refresher info:
-you will need an SD card. I'm pretty sure the following instructions will only work if you use one.
-If at any point you get the android guy with an orange exclamation point during boot...it is probably ok, just let it sit there for a couple minutes. it should continue to boot into whatever ROM you are currently on. Make sure you enable usb debugging in settings after boot.
-to access RSD, Recovery, or Fastboot mode, press and hold your power button to start the Xoom booting. When you see the Motorola logo, wait a second then press the volume down button. Then you can use volume down again to cycle through your options, and use volume up to choose one.
-the exact differences between RSD / Fastboot and Recovery modes are beyond the scope of this post (and me) so just know that your Xoom can be modified using software on your PC via USB with RSD and Fastboot modes, and stock recovery can be replaced with modified versions to add more functionality. Recovery is used to do all sorts of things...flash Roms, mount drives, format, cleanup caches, etc.
***
General instructions. Just guidelines; you will probably need some previous experience with computers / rooting etc.
(If you are already unlocked, rooted, and have a replacement recovery, skip to the last step.)
1.) Follow this guide to prep your Xoom: (unlocking, rooting, and install CWM recovery)
http://www.xoomforums.com/forum/motorola-xoom-development/15179-how-rookie-rooting-flashing-unrooting-under-one-roof.html
Note: you may have heard of Lord AOI tool; it is supposedly designed to simply the above process. I found it didn't work well and was more difficult to use than good ol' adb commands. I recommend skipping it.
2.) OPTIONAL: Next, I recommend using the latest Rogue recovery. Just use standard CWM recovery to flash it. It is nice because it allows you to use the touchscreen to manipulate instead of having to use the hardware buttons (volume buttons are kind of a pain). See here: http://forum.xda-developers.com/showthread.php?t=1235170
3.) Finally, flash the pre-rooted stock Jellybean ROM. See here: http://forum.xda-developers.com/showthread.php?t=1796335
(here's the direct ROM link for those not needing instructions or extra info: http://www.mediafire.com/?7w5w65l66hgggo8 )
Good luck and let us know your results...
Q&A for [Radio][Modem][5.X.X] Updated Modem and radio files from oxygen os
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Radio][Modem][5.X.X] Updated Modem and radio files from oxygen os. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
its work on validus rom v8 , and i have more stable signal now , thanks
recover from oxygenOS fw.
Reply for script error while in twrp for flashing blisspop after using oxygen modem.
It was happened to me as well. What I did was;
Reflash cm12 firmware updater 21/03 followed by firmware updater 02/04. Then continue installing ROM, gapps, and etc. It worked for me at least.
Modem
I am currently running Blisspop...
Do I flash only the modem since I have the firmware provided by blisspop or I flash with the Oxygen firmware and modem?
Lost MMS
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
wttp said:
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
Click to expand...
Click to collapse
If you are precisely sure your APN is exactly as before, call your phone company and see if their 'reset' will help. Over these last several years and numerous ROM changes, it has solved my issues now about 3-4 times when nothing else was obvious, and it was always the MMS issue for me, as well. (Consumer Cellular)
JeffDC said:
If you are precisely sure your APN is exactly as before, call your phone company and see if their 'reset' will help. Over these last several years and numerous ROM changes, it has solved my issues now about 3-4 times when nothing else was obvious, and it was always the MMS issue for me, as well. (Consumer Cellular)
Click to expand...
Click to collapse
About 2 hours on the phone with Straight Talk, and no success. They sent several signals, but ... So tried reinstalling piece by piece and nothing helped. Won't be a show stopper for me as I don't send pictures much (everything else works great). Connection with the Full Oxygen Modem is the best I have ever had, and staying connected in spots I had no signal before.
Thanks for the help, but still a little miffed.
Answer to jasonx3 question
jasonx3 said:
I'm having this issue on CM 12s after flashing. i did a clean install from TWRP. i can't connect to LTE signal keep crashing. look at the signal icon you will see what i meant. will flashing this modem fix this?
Click to expand...
Click to collapse
This is an easy fix. Go to settings>mobile network> APN > select the correct carrier.
I had mine set automatically to T-Mobile and had to switch it to Metro PCS.
---------- Post added at 12:43 PM ---------- Previous post was at 12:37 PM ----------
wttp said:
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
Click to expand...
Click to collapse
MMS app> settings> auto enable data and auto enable retrieve.
Should I flash only modem or whole firmware on cm-12-20150415-NIGHTLY? If I flash the firmware, will it be overwritten if I update cm12 rom? Sorry for my ignorance.
A great contribution
thanks
OxygenOS modem on encrypted CM12s
I sideloaded the OPO_OxygenOS_1_0-flashable-modem.zip file to encrypted CM12S with TWRP2.8.6. It didn't give me LTE at home where my wife's Moto E 2015 has it, but it did improve signal strength on LTE Discovery from -100 dBm to about -80 dBm but still EDGE. Will keep it until something better comes up.
Can someone please send a mirror of this modem and firmware? I am having bad luck downloading on main thread it always fails on Google drive and the mirror on main thread is wrong md5.
Thanks
Ty29 said:
Can someone please send a mirror of this modem and firmware? I am having bad luck downloading on main thread it always fails on Google drive and the mirror on main thread is wrong md5.
Thanks
Click to expand...
Click to collapse
Update ~ Never mind I figured out how to use Google drive.
Does it work with CyanogenOS and will it fix the signal dropping issue?
Can we backup current modem before flashing the new one ?
Hey can someone answer the question that has been asked a cpl times already if whether or not people on CM 12- or Blisspop like me- have to flash FULL or just MODEM. Sorry but i thought that's what this q&a was for
Revert back to original Modem
I had initially flashed the oxygen modem given in the first post. But later I figured out that the low reception was due to my location and not due to the cm modem.
Right now I want to revert back to my original modem settings and keep it open for future updates
what should be done here?
Do I need to erase and flash once again so that the future updates from OTA nightly will include any possible updates in modem too.
maxpayne1989 said:
I had initially flashed the oxygen modem given in the first post. But later I figured out that the low reception was due to my location and not due to the cm modem.
Right now I want to revert back to my original modem settings and keep it open for future updates
what should be done here?
Do I need to erase and flash once again so that the future updates from OTA nightly will include any possible updates in modem too.
Click to expand...
Click to collapse
CM has started to use the same modem as Oxygen OS (that you have) some weeks back. And anyways an update will overwrite your current, if it is newer.
Does the new Cm12 come with oxgenos radio & modem?
Does the new Cm12 come with oxgenos radio & modem? suppose if i have wifi or call quality issues in cm12 do i have to flash the modem or the whole firmware and is wiping necessary?
Not working on moto g xt1033
Hi,
i just flash this zip and after system reboot my phone is not turning on, so what is the issue here?
Hello!
I am currently rooted and running the latest COI5 firmware. My signal quality has greatly reduced since upgrading to this firmware. I have attempted to Odin the BOH6 modem/radio file. Once doing so, I get an X on the signal, and baseband version shows "unknown." I then Odin the COI5 modem and I have service back, crappy service, but service never the less. When I have BOH6, I would have LTE, now I have H+. With BOH6 I would have H+ in some areas, now I have EDGE.
Anyone have a suggestion on how I can get back to BOH6 and/or how I can make my service better?
I was trying to play Madden and I keep getting kicked for not having a network connection when it fluctuates from LTE to H+ to UMTS to EDGE.
Thanks!
Tee Jay
Not sure what the cause of your issue is but this is what happened to me. Since I rooted I've been running jovy23's stock modified deodexed ROM. Jovy's ROM does not include the modem so when I updated from BOH6 to COI5 I was using BOH6 baseband for a day. When I got home that night and updated to the COI5 modem I had no network connection at all until I toggled WIFI on & off.
My network connection is working just fine on COI5. I personally can't tell a difference from BOH6. I haven't seen anything other than the LTE & 4G symbols since I got this phone. I know I'm not helping much but just wanted to share.
shouren04 said:
Not sure what the cause of your issue is but this is what happened to me. Since I rooted I've been running jovy23's stock modified deodexed ROM. Jovy's ROM does not include the modem so when I updated from BOH6 to COI5 I was using BOH6 baseband for a day. When I got home that night and updated to the COI5 modem I had no network connection at all until I toggled WIFI on & off.
My network connection is working just fine on COI5. I personally can't tell a difference from BOH6. I haven't seen anything other than the LTE & 4G symbols since I got this phone. I know I'm not helping much but just wanted to share.
Click to expand...
Click to collapse
I appreciate your response.
It just seems that in my area, I'm receiving much weaker signal reception with COI5.
A trick that worked on older models is to flash via odin, however uncheck the option to auto restart. Instead manually power down the phone then reboot straight back into download mode and flash again.
intifadamericana said:
A trick that worked on older models is to flash via odin, however uncheck the option to auto restart. Instead manually power down the phone then reboot straight back into download mode and flash again.
Click to expand...
Click to collapse
I'll have to try that when I get home from work.
Thanks!
intifadamericana said:
A trick that worked on older models is to flash via odin, however uncheck the option to auto restart. Instead manually power down the phone then reboot straight back into download mode and flash again.
Click to expand...
Click to collapse
Tried it. Same thing. Crap.
Thanks for the tip though!
I have no service and no cellular network problem on my N5, running dark rom 7.1.2 aosp, with franco kernel ( never had issues before ), newest radio and bootloader. This started happening when i got my new sim card from my provider and i got 4g signal in my area for the first time. I tried manually selecting radio by going in the hidden menu by entering *#*#4636#*#* and i got lte and full bars signal after selecting band 8 ( 1800 hz ) but only for a minute then it went back to empty triangle. Tried selecting 3g only in preffered network, tried manually selecting provider, tried toggling airplane mode on/off a bunch of times nothing works. Any suggestion would be highly appreciated, i love my N5 very much and i would hate to throw it in a drawer somewhere. Thanks in advance
Flash back to a stock ROM and test it worth your new new.
Does the sim work in another phone?
audit13 said:
Flash back to a stock ROM and test it worth your new new.
Does the sim work in another phone?
Click to expand...
Click to collapse
Yes the sim is working fine on any other phone. I will try gping back to stock thanks
EmilChurle23 said:
Yes the sim is working fine on any other phone. I will try gping back to stock thanks
Click to expand...
Click to collapse
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
iamxaq said:
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
Click to expand...
Click to collapse
Gonna try this fix now and I'll edit the result thanks for some hope
EmilChurle23 said:
Gonna try this fix now and I'll edit the result thanks for some hope
Click to expand...
Click to collapse
This morning it's not sticking with Pure Nexus, so I'll be trying DarkRom. I really don't want to use a CAF if I can avoid it, but it may become a necessity. Do people on T-Mobile have this problem?
iamxaq said:
This morning it's not sticking with Pure Nexus, so I'll be trying DarkRom. I really don't want to use a CAF if I can avoid it, but it may become a necessity. Do people on T-Mobile have this problem?
Click to expand...
Click to collapse
I wil try aosp by santosh m and see if it sticks
EmilChurle23 said:
I wil try aosp by santosh m and see if it sticks
Click to expand...
Click to collapse
So I've hit a point where I have 3G and nothing else. I can't yet get LTE to work. I'm using LineageOS CAF. How about yourself?
iamxaq said:
So I've hit a point where I have 3G and nothing else. I can't yet get LTE to work. I'm using LineageOS CAF. How about yourself?
Click to expand...
Click to collapse
No luck with aosp by santosh m and pure nexus 7.1.2 , can't even get it to connect. I guess my last hope is caf based i will try lineageos caf. All i need is the efs backup from stock? If i can get it to work with 3g i will be satisfied because i did some digging and found out that my network provider which is Vip MK has no lte support for nexus 5 d820 ( my model ) only 3g, but i can't even connect with 3g selected. I guess because this one is for US frequencies it will not work whatever i try but i will give lineageos caf a chance.
EmilChurle23 said:
No luck with aosp by santosh m and pure nexus 7.1.2 , can't even get it to connect. I guess my last hope is caf based i will try lineageos caf. All i need is the efs backup from stock? If i can get it to work with 3g i will be satisfied because i did some digging and found out that my network provider which is Vip MK has no lte support for nexus 5 d820 ( my model ) only 3g, but i can't even connect with 3g selected. I guess because this one is for US frequencies it will not work whatever i try but i will give lineageos caf a chance.
Click to expand...
Click to collapse
I was able to get 3G only to work on my Nexus 5 by reflashing the EFS from 6.0.1; I'm trying right now to see if I can install PureNexus 6.0.1 then dirty flash to PureNexus 7.1.2 with any success. Also, I might just switch to T-Mobile, but I have to wait until later this week for that.
Hi,
LTE band 8 is not in 1800 MHz but first of all you can check your N5 model - US model is D820 and is not supported for LTE on 1800 MHz (band 3). For 1800 Mhz band you need D821 model.
Regards,
iamxaq said:
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
Click to expand...
Click to collapse
To clarify that:
You had the problem with not recognizing the sim or having no service at all. And you solved this by flashing the sstock 6.0.1 backing up the efs, flashing to Pure Nexus 7.1.2 and restoring the efs immediatley after flashing the rom (+kernel+root+etc)?
This solves this mysterious no sim/no service bug, which many (?) N5 owners experience? If this is true, I'd be really happy
Iced-Earth said:
To clarify that:
You had the problem with not recognizing the sim or having no service at all. And you solved this by flashing the sstock 6.0.1 backing up the efs, flashing to Pure Nexus 7.1.2 and restoring the efs immediatley after flashing the rom (+kernel+root+etc)?
This solves this mysterious no sim/no service bug, which many (?) N5 owners experience? If this is true, I'd be really happy
Click to expand...
Click to collapse
It didn't stick. After I lost it I was unable to get it back. I gave up and switched to T-Mobile, where it is no longer a problem. Apologies for not having more testing information. I was able to get solely 3G on multiple instances, but getting the elusive 4G was beyond me.
I've had this problem before in two nexus, one of them running latest stock and the other a customized ROM. I tried to flash a stock ROM image in both of them with no luck. I was pretty sure that the image I was flashing was the latest, so the radio & bootloader should be flashed to the latest versions. But it didn't worked.
Finally I found on a XDA thread where someone was posting only the latest bootloader & radio to flash. I did it with NRT (in Advanced Utilities) and it worked:
View attachment 4196236
I can't remember or find the thread, so I post the images here:
- Bootloader-hammerhead-hhz20h.img
- Radio-hammerhead-m8974a-2.0.50.2.30.img
I think I had to flash them twice because the first time it wasn't right, but there were 4 months since then and still no failure
ochoceros said:
I've had this problem before in two nexus, one of them running latest stock and the other a customized ROM. I tried to flash a stock ROM image in both of them with no luck. I was pretty sure that the image I was flashing was the latest, so the radio & bootloader should be flashed to the latest versions. But it didn't worked.
Finally I found on a XDA thread where someone was posting only the latest bootloader & radio to flash. I did it with NRT (in Advanced Utilities) and it worked:
View attachment 4196236
I can't remember or find the thread, so I post the images here:
- Bootloader-hammerhead-hhz20h.img
- Radio-hammerhead-m8974a-2.0.50.2.30.img
I think I had to flash them twice because the first time it wasn't right, but there were 4 months since then and still no failure
Click to expand...
Click to collapse
Thanks for your input. I'll check that when I have some time. This is really weird as it looks like a hardware problem but if you can fix it with this method it's clearly a software issue...
best regards