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'm running Carbon CO2 1.1. My question is will i lose my flash to the Cricket network if i install a new rom? I afraid to wipe data/factory reset. I looked around and found no solution. Thanks in advance!
I just flashed the phone yesterday so don't know much about flashed phones.
No.
Roms and unlocks are different beasts.
Thanks, everything went well.
What ROM did you use to get to Cricket? My parents are leaving Sprint and don't want to buy new phones..
Generally, flashing over to another carrier isn't handled by a rom, but by "flashing" (different than flashing a rom.) It requires editing network information to get the phone to connect to another network. I haven't had that much experience with Cricket, but I know that they are willing to flash your phone at the stores when you sign up for service. Granted, some of their flashes are "Voice and text only" but you can search on here, there are many ways and tools to enable data. Once I leave the office I'll look for a few links and post if I find any.
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?
This is consistent across every CM14 ROM I've flashed. I am upgrading from CM13.
The signal bar at the top is blank as in "no service", it attempts to reconnect and show a signal for a split second but then goes back to "no service" again. When I remove my SIM card and reboot the problem simply vanishes, but of course I can't get LTE
Firmware: PCA
Recovery: TWRP 3.0.1.0
I have tried running the ROM stock with no data restore and I have tried flashing APN settings from this post.
I at first thought it was a CM14 bug but then I read that others had no problems with CM14 ROMs.
Assuming you actually have a SM-G900P (since a lot of people ignore that little detail) it's probably a matter of Cm14/14.1 doesn't appear to be wholly happy with anything other than the latest baseband, which is now PK1. To get it, just reflash to stock with Odin and then poke at the thing until it gets the two OTA updates that will bring you up to PK1. At that point if you like you can poke at the controls to update the PRL and Profile (just to be sure everything's good) and then let me suggest you make a call or two and/or send some SMSes to be sure you didn't mess something up when you tried to change the APN settings one almost never needs to touch, and then flash TWRP (or whatever recovery you use) right back in and sideload the Cm14.1 nightly and open-gapps for 7.1. Also, you will need to do a factory reset after upgrading to 14.1 or you'll get a wholly different set of misbehaviours out of the phone (trust me... I deliberately cut corners through multiple rounds of reflashing to find out what symptoms to look for). One of the more endearing failures can be no soft keyboard, nobody wants that.
I had a bunch of weirdness happening (including completely non-functional GPS) with CM14 a few days ago, and since the changelog doesn't seem to show anything addressing the screwy problems I had, it hints very strongly that people will need to update to PK1 before they can expect the device be reliable.
OH... and don't try and enable Adoptive Storage if it asks. The performance is abysmal for some reason (around 2Mb/s on a Class-10 card that otherwise hums along at 14Mb/s) and it will make any apps that are trying to use storage run like crap.
So people have it working on PK1? Has anyone had it working on PCA?
Edit: Odin restored PK1, it didnt want to boot after the reflash. I installed TWRP and restored a PCA Backup, updated PRL and profile. I flashed a cm14.1 ROM and still had the same issues.
It also didn't wipe my internal storage when I ran odin, which I remember it doing in the past.
Worked great on my S5 900P
Gracefully I got it to work on Resurrection Remix. Idk if it was the APNs or just more stable ROMs.
I booted RR stock w/o gapps, I went to enter in the APN settings using this site and it just magically worked after I entered in only the first line. It's hard to tell if it was because the ROM found out how to connect or if the first line of the APN settings triggered something.
I have the international Note 5, with a t-mobile sim card. When I am on the 4g network and I try to call somebody it takes 20-30 seconds to call. When people call me, they can't reach me. Though the 4g internet works like a charm.
The only way for calling to work is to switch it to 2g, but I am loosing the 4g internet speeds.
I contacted t-mobile, they tried to reset the network, but the problem persists.
Any suggestions?
Would flashing with a custom rom help?
Should I flash the original t-mobile rom?
unce unce unce
I found the problem
The problem has to do with the volte... This option is not available with the n905c model that I have, and there seems not to be a fix with t-mobile. Fricken Samsung didn't put available this feature in the upgrades of some international phones eg the Dubai model that I have...
I have the same problem
I just bought two t-mobile branded Note 5's and I'm using them on Family Mobile (previously owned by tmobile). If I limit my networks to 2G & 3G all of my calling works fine but the moment I enable LTE all of my incoming calls go strait to vm. The problem persists on both phones so I don't think it's a hardware issue. I've tried rooted and unrooted, magisk and supersu. VoLTE is turned off on both phones (since it's not supported by family mobile) but I've tried every combination of settings I can think of and nothing helps. I hate having to choose between having LTE or getting incoming calls and would love to fix the problem. Or is there a good way to totally disable or remove the VoLTE services? If I remember correctly there were similar problems with some of the S4s that required an app like advanced signal status (??? been a while) to overcome. Can anyone help? Please and thank you.
I have the same problem
Hi all,
I have the same problem, even I have install & root with custom rom the problem still exist.
someone told me that the problem is in 3G signal.
so I decide to choose LTE & GSM only, & it works for me. however it could not give 3G signal on my phone.
Did you find the other olution of this?
Evening all, I've been having this same issue, hoping there would be a fix. Not ready to purchase a new phone when there is nothing wrong with the one I have still good for at least another yr(maybe). but not rite now.
i fix the problem
Hi all,
maybe this method could solve the issue. please try it & follow below step.
1. reset to factory setting then after finish please clear Dalvik Cache.
2. Flash with the latest Odin & latest firmware, but you don't need to change everything in options tab. then click start.
3. After finish, then insert APN as mention in this link (please read how to set APN on Galaxy note5)
4. After select your desired APN, please change APN name become ****4g.com (or you can find this apn setting in your carrier SIM (check in google)
5. Finish, please check your phone.
hope above method could solve the issue, however it works for me now.
please try at your own risk & don't forget to always save your data before.
This is the FIX for the Note 5 SM-N920 C, i know this works because i have been dealing with this for MONTHS, so i tried EVERY Custom Roms Untill i figuard WHY NOT flash a Stockish T-Mobile Rom with a Custom Kernel for the 920C. And Just like that i got My Awesome Note 5 BIZACKKK, Here we go, Follow these steps, Upgrade to the FIRST 7.0 that came out for the SM-N920C, of course you should already know to turn on debuging + OEM, Flash TWRP through Odin, then go to the TMOBILE Development Section and THANK "@Marinella" First and foremost for cooking up this Rom, Download his Stockish Unrooted Rom ++7.0 ROM Stock Unrooted N920TUVU4EQE1++you will also need (MAKE SURE TO THANK--->>> ""@AndroidSword"" ) this 7.0 Kernel, go to the seack bar and type it in, FUEL-KERNEL-V2 .... now before anything, Of course do FULL WIPES Of Everything like you usually wipe when downloading other Roms, flash the stockish Rom first, then the Kernel, Just so you know, the Kernel has 2 choices of root. ITS AS SIMPLE AS THAT>>!!!!, Boot your Device and wait, this took me months to figure out after flashing so many diffrent Rom, Now I Have My Favorite International Note 5 Back, trust me , this WILL WORK ON THE 920C. ENJOY...
hi,
above method is for SM-N920C, do you have solution for SM-N920T ?
No Idea, sorry, try different Custom Rom, i have not heard of this issue with the 920T. Good Luck.