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!
Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
can you install a stock rom back onto it? There is a baseband selection mode that you may have to do.
http://forum.xda-developers.com/showthread.php?t=1116884
1. Go to Dialer. Dial *#*#4636#*#*
2. Go to Phone information. Choose the preferred network to
"GSM Auto PRL" or "CDMA Auto PRL" or whatever you have.
3. Scroll down, deactivate and activate Phone Radio.
4. Press Menu button.
5. Select Phone frequency, then choose your country.
6. In the previous menu push the Home button to go back to Homescreen.
7. Reboot.
(By Brainmaster)
Ive had to run this a few times depending on radio and rom.
after many trials I am sticking with rooted stock.
Wow that is defiantly a menu I have never seen before.
It doesn't let me select any of the preferred carrier option. When I tap on GSM auto (PRL) it just closes and defaults back Unknown.
It's ded?
Sent from my HTC Phone
thepyro6 said:
It's ded?
Sent from my HTC Phone
Click to expand...
Click to collapse
Ya, I think it is. RIP Nexus S. HTC Sensation here I come.
after you select gsm auto you hit the menu button on your phone then select the carrier. I know its not labeled what it is on the walkthrough but its similar. not phone frequency but like signal or something. then yuo jsut select usa.
reboot and it should find whatever your service is on its own.
have you tried going back to stock rom? I used this version to go back when i thought i bricked out my phone and its been great. I think my friend used it too but he wont admit he used somethign i gave him.
http://forum.xda-developers.com/showthread.php?t=1060192
http://forum.xda-developers.com/showthread.php?t=1038007
Same issue also involved the trinity kernel. Dev may need to be notified.
kmmxracer said:
Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
Click to expand...
Click to collapse
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
No im absolutely sure i flashed the right ROM. Peter Alfanzo was a ROM i flashed after this issue happened. It was the CM7 nightly + Trinity kernel that did me in...
Sent from my Nexus S using XDA Premium App
simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Canehdianman said:
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Click to expand...
Click to collapse
have you tried reformatting all your phones partitions?
simms22 said:
have you tried reformatting all your phones partitions?
Click to expand...
Click to collapse
I've wiped user data/factory reset a few times now. Is there a higher-level format option that I should be using?
I thought for sure that going back to stock (based on these instructions - theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/) would work, but no such luck.
I find it perplexing that the baseband shows in fastboot, but nowhere else. *#*#4636#*#* shows radio off and network type unknown, settings/about phone/ shows baseband version unknown.
I tried different methods that I've found online over the weekend, but nothing has brought my radio back.
I am certainly open to suggestions!
I'm going to provide as much additional information as possible.
I have a Nexus S I9020A, running on Fido (Canada).
My initial problem stems from when I updated to cyanogenmod 7.1 from 7.0. My first (and likely biggest) mistake was not making a backup. Oops.
I think I accidentally chose "Nexus S 4G" instead of "Nexus S". As soon as I did that, I stopped getting any cellular voice or data connection (wifi continues to work fine). Under Phone Information, it said it was a Nexus S 4G.
The phone locks itself into airplane mode now. When I try to turn airplane mode off through the settings menu, it hangs. When I hold down power and choose "turn airplane mode off" it seems to work, but then I still get no signal.
I have pushed it back down to stock. It now remembers that it is a Nexus S (not 4G), but it didn't help the baseband problem.
I have tried to reflash the baseband. no effect.
I called Fido and got them to "repush" the SIM card. No effect.
I am humbly appreciative of any and all help that anyone can provide!
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Thanks! This is similar to some other threads I saw on the android forum (and elsewhere on XDA).
I'll try this when I get home (and get to a reliable wifi signal).
Wow! I haven't looked at my post in a wile. Hopefully you all are getting some resolution to these issues. I ended up calling Samsung and they agreed to fix my Nexus under warranty. They replaced some parts that I can't remember off the top of my head, but it should arive at my door tomorrow!!!
Sent from my HTC Sensation 4G using xda premium
YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Hmmm bad news... my efs folder appears to be empty. Now what?
A very frustrating day... Thought i would have it fixed pretty quick, alas....
My efs folder is empty. I guess that explains the lack of radio, but it appears that i might need to send the phone to Samsung to get the efs reflashed. Is there a way to write it back myself? Ill look tomorrow i guess.
Here is some more info:
I just tried to update to 2.3.6
Clockwork mod is giving me an error message:
Assert failed: getprop("ro.product.device") == "crespo" || get prop("rp.build.product") == "crespo"
E:error in [filename]
(Status 7)
Installation aborted
Not sure if that helps but it's another piece of thepuzzle hopefully.
*sigh*
So it appears that I need a backup of my /efs folder in order to fix this myself (which I do not have).
I know what my IMEI should be, however I have no idea if it is even possible to take someone else's backup and alter it the proper IMEI.
I fear my next option will be to submit it for repair at a Samsung repair shop (and be without a phone even longer )
Hi everyone,
I'm a brand new Nexus S convert on the AT&T network. I've been using a Nexus One for about a year, but I finally got the dreaded power button failure, so I thought it was time to "upgrade".
Anyways, I just got the phone tonight, so I wiped everything, flashed the newest AT&T radio (KF1), then flashed NexusBeam 4.1.0 (custom 4.0.3 ICS), then flashed GLaDos v2.2. This was all done via CWM 5.0.x
After putting in the SIM and turning on the phone, I noticed that I did not get ANY signal for a while. The network status in the settings did not find anything. After about 3 minutes, I finally got EDGE. However, still no 3G.
I looked up the default APN settings for AT&T but it did not help. I also tried flashing another custom kernel (Matrix), but my phone wasn't happy with it (stuck on Google logo).
What could be the culprit here?
P.S. Yes, I made sure the Nexus S is indeed the AT&T model (I-9020a).
Edit:
Even though I have flashed the proper radio, the ROM reverts it to the incorrect version. For example, I've flashed KF1 radio, but the ROM somehow "overwrites" it to the KI1 radio, which is not recommended for AT&T/I-9020a. The baseband also says NO DGSXXKI1.
after flashing the rom flash your correct radio.
You probably clicked KI1 by accident rather then KF1... I'm using KB3 and its really good. Soooo flash the UCKD1 radio first for AT&T... then download Root explorer if u don't already have it
Using root explorer go into EFS file and move the following into root of SD:
Nv.log
Nv_data.bin
Nv_data.bin.md5
Once those files are moved just reboot and u should have your 3G back... then u can flash the radio u want
-Google
iGoogleNexus said:
You probably clicked KI1 by accident rather then KF1... I'm using KB3 and its really good. Soooo flash the UCKD1 radio first for AT&T... then download Root explorer if u don't already have it
Using root explorer go into EFS file and move the following into root of SD:
Nv.log
Nv_data.bin
Nv_data.bin.md5
Once those files are moved just reboot and u should have your 3G back... then u can flash the radio u want
-Google
Click to expand...
Click to collapse
Thank you! That worked!
Hi!
I had repair microUSB on my Captivate and then got Encryption Unsuccessful.
After EU I made repartition on sd card and flashed to Android 2.3 , and got that 3G and GPS doesn't work.
after I flashes Paranoid ROM, 3G GPS the same.
EDGE and WIFI working well.
What I can do to restore 3G , GPS ?
aVirginGirl said:
Hi!
I had repair microUSB on my Captivate and then got Encryption Unsuccessful.
After EU I made repartition on sd card and flashed to Android 2.3 , and got that 3G and GPS doesn't work.
after I flashes Paranoid ROM, 3G GPS the same.
EDGE and WIFI working well.
What I can do to restore 3G , GPS ?
Click to expand...
Click to collapse
You most likely don't have the right APNs. Go look under Settings -> Mobile networks -> Access Point Names. And make sure they matches your carrier's APNs (which you can find with a quick google search).
Also consider looking at different modems. GPS is directly effected by the modem you are using and depending on your carrier that you're using the phone on it could potentially effect that too.
Regardless if you are using this phone on T-Mobile then you likely won't get 3G regardless of what you change on the phone unless you are lucky enough to be in an area where they have updated their service.
I'm using right APN.
Modem is "radio-cm7-ics-captivate-ugkg3-signed" 850 Mhz
I used it before and it worked well untill I have issue with EU.
Anybody can make a backup efs and send me, please?
aVirginGirl said:
Anybody can make a backup efs and send me, please?
Click to expand...
Click to collapse
Actually doesn't work that way. Your efs folder is specific to your phone as it contains your IMEI. If you get from IMEI error, going back to stock KK4 is the solution. Once in there, you use a file explorer with root rights (like ES File Explorer or Root Explorer) to copy it somewhere safe. Then you can flash Corn kernel and get back on the ROM you wanna use.
Before I rooted I was running the Android 6.0.1 OSA update. Now I'm running CyanogenMod 13 Nightly and everything's working awesome except LTE/4G and MMS.
I feel like I've tried everything. With previous devices I was able to use the "Universal VMU APN Fix" to fix any issues but not now. I've also tried the "MVNO Slayer" with no success.
I've even tried pulling the stock build.prop from the stock image file from sammobile.com and making my own "customized" version of the VMU APN fix but I've noticed that the CM13 build.prop file doesn't have any cdma options in it so I'm not sure where those are stored.
And I've tried setting my APN settings manually through the settings menu but that doesn't work either.
Also, trying to revert my device back to stock using image files from sammobile.com results in my device getting stuck at the Virgin Mobile splash screen upon boot.
So I can't get 4G/LTE and MMS working and I can't revert back to stock. I'm worried I've screwed my phone permanently. :/
If anybody can provide some advice that'd be awesome. Thanks!
the weirdness in the first part of your post doesnt make sense as to why your phone is doing that unless the modem got screwed up when you flashed CM13 or if youre on a MM baseband. If i was in your position, i djust go back to square 1 and try again. Reflash the tarball, chainfires root tar, TWRP and let it boot. Make sure its all working fine, then flash a g900p ROM in TWRP and go from there. If you are seeing a virgin mobile bootanimation, they you likely flashes a ROM that wasnt built for your phone. Youre going to want to stick with ROMs made for the g900p specifically
if you want to revert, heres a faster dl of the OK4
---------- Post added at 01:13 PM ---------- Previous post was at 12:40 PM ----------
also, check this thread
http://forum.xda-developers.com/sprint-galaxy-s5/help/cm13-0-nightly-lte-t3422838
youdoofus said:
the weirdness in the first part of your post doesnt make sense as to why your phone is doing that unless the modem got screwed up when you flashed CM13 or if youre on a MM baseband. If i was in your position, i djust go back to square 1 and try again. Reflash the tarball, chainfires root tar, TWRP and let it boot. Make sure its all working fine, then flash a g900p ROM in TWRP and go from there. If you are seeing a virgin mobile bootanimation, they you likely flashes a ROM that wasnt built for your phone. Youre going to want to stick with ROMs made for the g900p specifically
if you want to revert, heres a faster dl of the OK4
---------- Post added at 01:13 PM ---------- Previous post was at 12:40 PM ----------
also, check this thread
http://forum.xda-developers.com/sprint-galaxy-s5/help/cm13-0-nightly-lte-t3422838
Click to expand...
Click to collapse
Thank you for your help youdoofus.
I was able to get back to stock using the OK4 image you linked to.
I also tried flashing CyanogenMod 12.1 and applying APN settings to that without success.
So I guess I'm sticking to stock un-rooted for now unless anyone can help me get APN settings working for Virgin Mobile. :/
KodieG said:
Thank you for your help youdoofus.
I was able to get back to stock using the OK4 image you linked to.
I also tried flashing CyanogenMod 12.1 and applying APN settings to that without success.
So I guess I'm sticking to stock un-rooted for now unless anyone can help me get APN settings working for Virgin Mobile. :/
Click to expand...
Click to collapse
Ok. Gimme a min. I'll be at my computer shortly. You can also hmu on hangouts, I'm youdoofus there too
If you come up with any ideas youdoofus, that'd be awesome. Otherwise after working on this thing for like 8 hours, I was able to get a stock deodexed rooted rom running with Xposed so I'm content for now, lol.
KodieG said:
If you come up with any ideas youdoofus, that'd be awesome. Otherwise after working on this thing for like 8 hours, I was able to get a stock deodexed rooted rom running with Xposed so I'm content for now, lol.
Click to expand...
Click to collapse
does virgin mobile use sprint as their backbone for it as a MVNO? If not, the reason you might not be getting data is the network lock.
youdoofus said:
does virgin mobile use sprint as their backbone for it as a MVNO? If not, the reason you might not be getting data is the network lock.
Click to expand...
Click to collapse
I'm not exactly sure what a MVNO is. I know that Virgin Mobile uses Spring for it's mobile network. I was able to get my old device (Galaxy S3) running with CyanogenMod 11 on Virgin Mobile no problem. (After of course running the Universal APN fix)
an MVNO is a "cell provider" that exists only on paper just like straight talk. they buy their air time off other carriers and sell it as their own. I use straight talk but am using AT&Ts physical hardware. I think virgin uses sprint, but im not entirely sure. if thats the case, you should just need to use sprints APN settings. worth a try at least
Universal apn flasher for virgin mobile. Flash your rom then flash this zip. Works on 4.4.2,4.4.4 and lollipop but cant vouch for it on marshmallow as i havent updated my s5 to marshmallow to try it. Although it shoild work ok.
i'm on aokp MM PCA baseband and used the APN backup and restore method.
2nd post on this page:
http://forum.xda-developers.com/showthread.php?t=1794956
---------- Post added at 12:04 AM ---------- Previous post was at 12:04 AM ----------
i'm on aokp MM PCA baseband and used the APN backup and restore method.
2nd post on this page:
http://forum.xda-developers.com/showthread.php?t=1794956
So I figured out what was wrong with my 4G/LTE. After restoring back to the stock rom, I realized that my 4G/LTE still wasn't working. I talked to the Virgin Mobile customer service rep for a little bit a figured out that my SIM card didn't support LTE. I had actually purchased my phone used via Swappa.com and I purchased the SIM card from Amazon. So apparently I got the wrong SIM card. Virgin Mobile sent me a new one and now I have 4G/LTE again! Still have to test it with a non-stock rom but I'm pretty sure it'll work just fine.
Thank you everybody for the help/suggestions!
KodieG said:
So I figured out what was wrong with my 4G/LTE. After restoring back to the stock rom, I realized that my 4G/LTE still wasn't working. I talked to the Virgin Mobile customer service rep for a little bit a figured out that my SIM card didn't support LTE. I had actually purchased my phone used via Swappa.com and I purchased the SIM card from Amazon. So apparently I got the wrong SIM card. Virgin Mobile sent me a new one and now I have 4G/LTE again! Still have to test it with a non-stock rom but I'm pretty sure it'll work just fine.
Thank you everybody for the help/suggestions!
Click to expand...
Click to collapse
Anybody that pays for a lte sim card should get their money back. If you call your provider they will give you one.