Database Info

PLEASE HELP! 2.3.4 and suddenly can't connect to my network (Bell Mobility)

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!

[Q] No Network signal after jelly bean

Upgraded to jelly bean OTA and after which no network signal ....... tried hard reset still no network......... do not know what to do...........help

No network signal? or do you mean no internet? and are you rooted? is your sim card readable? please give more details

network signal ..
Billchen0014 said:
No network signal? or do you mean no internet? and are you rooted? is your sim card readable? please give more details
Click to expand...
Click to collapse
sir network signal tower is not picking up .... when you dial says "no network".. sim working fine in other phone

vishal68 said:
sir network signal tower is not picking up .... when you dial says "no network".. sim working fine in other phone
Click to expand...
Click to collapse
Are you rooted? If so flash a different radio or else go to the store they can fix. There is nothing you can do without root.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX

I have the same problem.
It all started when I tried to flash a new JB ROM. I tried Paranoid, XenonHD, JellyBean and none of them were able to connect to my cellular network. Before that I used AOKP and when they released their JB build 1 I tried flashing it as usual with a factory reset and then flash ROM. But I still couldn't connect to my cellular network. I then tried to flash build 1 over my restored nandroid and this time I could connect. It was just like there was some important file that the factory reset removed.
Today I'm running Codename 3.4.0 that I flashed over the JB build from AOKP and I can connect and use the phone but at the same time I feel that the phone is not as responsive and so forth, not because of JB but more because of this flashing over and over again.
I have thought about going back to stock and start over but I'm not sure that would solve it, or at least that is more work then trying to fix this in any other way. (I presume)
Just recently I tried to install the latest Codename (3.5.0) and as usual I did a factory reset and wiped Dalvik, then flashed ROM and GApps but could not connect to cellular. I then tried to flash radio from this thread http://forum.xda-developers.com/showthread.php?t=1116884 both the KF1 and KI1 but still doesn't work.
All this time I can unlock my SIM when the phone starts and I can search for cellular network but trying to connect just gives me an error code stating that I can not connect and that I should try again later.

[Q] Radios / Jelly Bean question

I have been using an ICS ROM (PrimoS v4.1) on my Desire S for some time with no problems, but recently have tried flashing a number of JB ROMs (e.g Andromadus, CM10 and JellyTime). I have found that when using any of these JB ROM's, I am unable to get a data connection and the APN list is blank. Despite many attempts to add APNs manually or by use of APN backup apps, I have failed to add an APN to the list.
Do I need to update the radio to solve this problem? I never did this when going from original HTC Gingerbread to the ICS ROM.
Please excuse the ignorance on this subject. I've read somewhere that there is a danger of bricking the phone when flashing radios, hence my reluctance to try without good reason!
I live in the UK and use Virgin Mobile.
Current radio is: 20.281.30.085AU_3805.06.02.03_M
All help appreciated - I've had a tantalising glimpse of the wonders of Jelly Bean and I'm desperate to get my data connection working!
TIA

I can't say whether changing radios will fix your problem. I use Radio 20.4801.30.0822U_3822.10.08.04 on CM10 and have no problems.
Sent from my Desire S

BillGoss said:
I can't say whether changing radios will fix your problem. I use Radio 20.4801.30.0822U_3822.10.08.04 on CM10 and have no problems.
Sent from my Desire S
Click to expand...
Click to collapse
Thanks for the reply BillGoss.
I took the plunge and updated my Radio to 20.4801.30.0822U_3822.10.08.04 with no problems. My phone continues to work fine with the PrimoS (ICS) ROM, but when I flashed JellyTime, still no APN's and I was unable to create one, hence I can't connect to the 3G network. D'oh!

Correct me if I'm wrong but with ICS you don't have the probelm and with JB you have the problem
that you have no and can not set the APN values, Q, dit you have a clean ROM installed.
I had this problem once when I tested a ICS version with sence 4. Later when I installed a CM10 version
I had no APN so I did a factory reset an de problem was gone. To be sure I wiped al the data on my device
and restored a earlyer nandroid backup. Later I tested a lote of ROMS but so far I don't have the APN issue yet.

HypnoCondor said:
Correct me if I'm wrong but with ICS you don't have the probelm and with JB you have the problem
that you have no and can not set the APN values, Q, dit you have a clean ROM installed.
I had this problem once when I tested a ICS version with sence 4. Later when I installed a CM10 version
I had no APN so I did a factory reset an de problem was gone. To be sure I wiped al the data on my device
and restored a earlyer nandroid backup. Later I tested a lote of ROMS but so far I don't have the APN issue yet.
Click to expand...
Click to collapse
Yes HypnoCondor, I always do a full wipe before flashing the ROM. I've now done a ot of Googling and trawling XDA threads and have found that the issue seems to be confined to CyanogenMod-based ROMS, not specifically CM10 and covering a lot of different phones. I'm not techie enough to fully understand, but it seems that CM is not registering the SIM card properly and hence the APN list is always blank and can't be edited/saved manually.
What's particualrly confusing is that I recently flashed the CM10-based CyanogenMod 10 Beta Builds [4.1.2][ANDROMADUS 3.x][Frontcam] ROM (http://forum.xda-developers.com/showthread.php?t=1776256) and much to my surprise it worked! My APN list was populated and all was fine. Unfortunately , after rebooting the phone, the APN's were gone and I've been unable to get them back, despite trying every trick in the book gleaned from XDA users with similar problems.
This is very frustrating, because I really love this ROM
Looks like I'll end up going back to the PrimoS (non-CM, ICS) ROM so that I can get my data connection back when I'm away from WiFi. That's a real bummer, but I'm damned if I've been able to find a fix for this issue.

Just for future reference: being unable to set APN has nothing to do with radio and has everything to do with the ROM you're using. But you've already found that out yourself.

Jack_R1 said:
Just for future reference: being unable to set APN has nothing to do with radio and has everything to do with the ROM you're using. But you've already found that out yourself.
Click to expand...
Click to collapse
Thanks Jack_R1. My final plan is to try replacing the SIM card - should receive it in a couple of days.

Phosbrom said:
Thanks Jack_R1. My final plan is to try replacing the SIM card - should receive it in a couple of days.
Click to expand...
Click to collapse
Phosbrom I'm on Virgin and the JellyBean roms you mentioned work great on our service. I'm sure you'll enjoy using them when your new sim arrives :good:

Can't Disable LTE - please, please, please, please help

I live in a fringe LTE area and for the &^$#*Ing life of me can't disable LTE.
I have a 2.20 at&t one x on hboot 1.14, rooted and running latest CM10 nightly .
EVERY option, whether from settings, a widget toggle, even the *#*#4646#*#* special menu IMMEDIATELY AND INSTANTANEOUSLY switches LTE back on when i select any other option.
My phone is completely useless in my apartment without this option. This is why I flashed CM10 in the first place. Please, someone help

Unfortunately my response is light on details, but what about setting up an APN that doesn't access LTE

Might want to try reflashing the rom or if your on an old build factory reset then flash the latest.
My LTE toggle works like it should. im on the latest nightly too

APN workaround drops the connection completely, randomly
I'm on the latest nightly and have tried 3 of them. Can anyone help?

Koizuma said:
Might want to try reflashing the rom or if your on an old build factory reset then flash the latest.
My LTE toggle works like it should. im on the latest nightly too
Click to expand...
Click to collapse
are you also running a 2.20 phone with 1.14 hboot?

theartialmartist said:
APN workaround drops the connection completely, randomly
I'm on the latest nightly and have tried 3 of them. Can anyone help?
Click to expand...
Click to collapse
https://play.google.com/store/apps/...51bGwsMSwyLDEsIm5ldC5hbmRpcmMubHRlb25mb2ZmIl0.
try this, force network mode

someone has to have a solution for this.. please, anyone

I remember on some roms when my lte was being funky it wouldn't let me disabled lte it would just switch back instantly try a sense Rom

The latest CM10 nightlies have this problem. Try flashing a nightly from 12/01 to 12/05. I'm pretty sure this problem appeared with the 12/07 nightly. I have been experiencing this as well. When it does work however, it works great and sticks. So try switching to nightly from a few nights ago.

[Q] Cannot acquire data connections

I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.

TheCing said:
I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.
Click to expand...
Click to collapse
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).

XdrummerXboy said:
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).
Click to expand...
Click to collapse
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.

TheCing said:
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.
Click to expand...
Click to collapse
Hmm... ML1 should be new enough.
That's a bizarre issue.
For me, I mainly get 3G. It seems as if either Verizon pulled some LTE towers near me, or my data antenna doesn't have very good contact. Maybe you're having the same issue.
Do you EVER get 4G? Or literally never?