Database Info

3g activation problem EURO 3g Xoom

I have very strange problem with my euro 3g xoom. When I bought it it recognized my sim card and network (T-Mobile Hungary). Now I flashed Tiamat 2.2.2 Moray. Of course I had a lot of problems with that one so I went for Hammerhead and flashed 3.2.2 stock rooted too. In every case I did a complete wipe / factory reset and a dalvik cache wipe too.
Now the actual nature of the problem is that I LOST PARTS OF MY 3G SETTINGS. This means I cannot define APN any more nor can I select service provider. Menus are missing. 3g device activation fails with infinite attempt to activate device.
As it appears to me Xoom seems not to recognize my 3g modem at all..
Any suggestion / comment is welcome. Right now I am on 3.2.2 stock rooted with of rogue ran a kernel. Oc 1.5 ghz rock solid, excellent performance no FCs at all, ONLY 3g is not working at all.
Thanks for any support in advance.
My hardware is European Xoom 3g, model nr. MZ-601 - Tegra 250.
-p0rt3r-

UPDATE_1
Tried Rogue Recovery 1.3.0 to see if the Solarnz one based on CWM 3.2.0.0-rc1 is responsible not wiping some faulty settings - no success, still missing menus in Mobile Network settings.u
For ppl who might responde to this rthred: I don't really nee a GUI for setip its okay when u guys tell me which file to edit in order to put in my APN which is very genuine: "internet"
Right now my baseband is "unknown" in the about tablet section....
-p0rt3r-

UPDATE_2
Here is what I have in the Mobile network settings:
Data enabled
Data Roaming
System select
Activate device
And no, I cannot scroll down any further etc.
p0rt3r-

UPDATE_3
Went back to Hammerhead where:
Version 2.1
Fixed all the application signatures - Google applications should update fine now.
All of the language packs are now incorporated into this rom
European 3g support should be 100% working now.
Native screenshot is back
now what I see is:
Data enabled
Data roaming
System select (change CDMA roaming mode) - I am on GSM!
Activate device.
Thats it for Mobile network settings menu.

You need to extract the telephoney files after installation. Bear with me and I will try to find the link. Be back soon.
Ok, here is the thread I think you need: http://forum.xda-developers.com/showthread.php?t=1089695
You should have backed up your original Euro 3G with CWM (Clockworkmod Recovery)
These are the files you need:
settings.db settings.db-shm settings.db-wal telephony.db telephony.db-journal from the data.img (From your original backup) You will need unyaffs.exe (use google search to get it)
1) Copy (not move) your original data.img to the same folder as unyaffs.exe.
2) Open cmd prompt and change directory to point to the folder now containing the unyaffs.exe and the data.img
3) type "unyaffs data.img" without quotes and press enter.
4)Copy all databases from /data/data/com.android.providers.settings/databases/ (above mentioned files)
5) Flash the rom you want i.e. Hammerhead etc. (Best clean install)
6) Then reboot
7) Once booted and signed in etc. open a cmd prompt pointing to adb's location
8) adb remount
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb push settings.db-wal /data/data/com.android.providers.settings/databases/settings.db-wal
adb push settings.db-shm /data/data/com.android.providers.settings/databases/settings.db-shm
adb push telephony.db /data/data/com.android.providers.telephony/databases/telephony.db
adb push telephony.db-journal /data/data/com.android.providers.telephony/databases/telephony.db-journal
adb reboot
If you have followed the instructions properly then on reboot you should have Euro menu for choosing GSM etc.
Hope this helps. Thanks and credit goes to lowtraxx
Phil

diigibio, thank you
diigibio,
thank you. Would be more than happy if you could provide me with som information how to get Hamerhead or any other native Tiamat rom to work on Euro 3g Xoom.
So far I can confirm that
http://forum.xda-developers.com/showthread.php?t=1183416
lowtraxx's solution is fine, all working now except Google aps updates but I do not really care for that 3g and wifi functionality is the most important, any other thing is addiional gift
waiting for your info.
-p0rt3r-

Problem solved completely?
Phil,
excellent. I cannot say how much this gonna help for me in the future. As for lowtraxx's 3.2, now I hv Hungarian market on Hammerhead I had US market... not sure if I do Hamerhead or any other Tiamat I will have my native market so I will leave this thread open for a while to see if anybody has experience with the solution you just sent me.
I also hv to say great community here, in 2 hrs u solved my problem. Thank you for this.
-Zoltan

Glad I could help. Enjoy. All the best for the New Year from the UK.

Same to u too mate from Hungary

Flashable Virgin Mobile LTE fix

I made an updated flashable VM fix from V.R2 of Mopedryder's version of the fix http://androidforums.com/threads/vi...rgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/. I wrote a new updater-script to accommodate our new apns-conf. This also deletes telephony databases and updates the build.prop somewhat accordingly,carrier brand is also correctly set as VM also. I recommended using this on a clean flash of your ROM or after a factory reset, let me know if you get LTE,text and calls working and which ROM and kernel you are using and we can add or change stuff. This should work with CM 12 & 13
Take a backup first via twrp before using this. I am not responsible for any damage you cause on your end!
How to install:
Download to Ext SD Card
Reboot into recovery
Either Clean Flash with ROM &Gapps
Or
Flash and then
Factory Reset (Dalvik,Cache,Data)
Reboot
LTE should immediately turn on
texts and MMS should now work, textra helps if you get problems sending pics.
https://drive.google.com/file/d/0Bz99NuhE3XwmRnRTWW9SejY2MlE/view?usp=docslist_api
Sent from my Virgin Mobile Moto E via CM 13

Thanks man, I was actually working on this, used the other thread to manually get everything working, once I saw it worked I was working on a script to do it via flash like this, I just got the device to have a decent phone while my Nexus 6 is getting rma'd, must say I'm super surprised at this little $40 phone
Sent from my XT1526 using Tapatalk

soupysoup said:
Thanks man, I was actually working on this, used the other thread to manually get everything working, once I saw it worked I was working on a script to do it via flash like this, I just got the device to have a decent phone while my Nexus 6 is getting rma'd, must say I'm super surprised at this little $40 phone
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
This is my favorite phone I've had so far, I broke the screen on my old one and bought another one because I wanted to see LTE work on the custom ROMs so badly. @Starklyraving and @hydroman202 have been so awesome working all along to get this fixed. Cheers guys!
Sent from my Virgin Mobile Moto E via CM 13

Thanks

I spent some time this afternoon throwing together an Aroma flashable zip to activate LTE on Boost, FreedomPop, Sprint, Ting, and Virgin Mobile. It's a really simple setup, but I've hit a hangup getting build.prop to edit in recovery mode.
Is your zip actually patching build.prop or is it just acting like it does?
Mind you, I've had LTE running fine with no changes whatsoever to build.prop so I may just cut those patches out.

I double checked the prop.sh file and I made a few edits to fix mms but I'm not finished yet,I'll upload that tomorrow but to answer you the zip also clears the correct databases and replaces the eri and apns_conf file and changes the numeric in build.prop and carrier branding
Sent from my Virgin Mobile Moto E via CM 13

Sands207 said:
I double checked the prop.sh file and I made a few edits to fix mms but I'm not finished yet,I'll upload that tomorrow but to answer you the zip also clears the correct databases and replaces the eri and apns_conf file and changes the numeric in build.prop and carrier branding
Sent from my Virgin Mobile Moto E via CM 13
Click to expand...
Click to collapse
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d
unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)
Update the getprop values, copy apns and eri to the right place.
I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.
CM13 will most probably won't get the fix.

Sands207 said:
This is my favorite phone I've had so far, I broke the screen on my old one and bought another one because I wanted to see LTE work on the custom ROMs so badly. @Starklyraving and @hydroman202 have been so awesome working all along to get this fixed. Cheers guys!
Sent from my Virgin Mobile Moto E via CM 13
Click to expand...
Click to collapse
I will say I'm super impressed with moto for this device, I mean come on, I paid $40 for this thing, it performs almost as well as my Nexus 5, I just wish it had a little bit bigger screen and some more storage, but I mean for $40 really, I had very low expectations for this phone, it was just something to get me by until me N6 comes back from RMA, but after using it for a week I'm impressed, I'm actually working on 6.0 for it too, bcuz I know it can run it and I think it will improve on an already amazing device, good stuff moto, after my Nexus 6 I wasn't a fan of moto, but this restored my trust in them a great deal....
Sent from my XT1526 using Tapatalk

scritch007 said:
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d
unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)
Update the getprop values, copy apns and eri to the right place.
I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.
CM13 will most probably won't get the fix.
Click to expand...
Click to collapse
The main difference is in apns-conf.xml. eri.xml is purely cosmetic and LTE works perfectly without patching build.prop. I'm currently pulling the build.prop patching from my zip and updating the various apns-conf.xml files with the most current information. I'll upload in a bit.

scritch007 said:
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d
unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)
Update the getprop values, copy apns and eri to the right place.
I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.
CM13 will most probably won't get the fix.
Click to expand...
Click to collapse
@scritch007 Thanks, if you could include it that would great. The difference is on lines 23 + 24 of prebuilt/system/etc/cdma/virgin/apns-conf.xml the value for LTE for Virgin Mobile at least in the US I believe is n.ij.ispsn instead of v.vmu.ispsn which is used for 3g data that is there now. I am guessing with the introduction of spark network the value was changed. The prop fix just sets our carrier branding correctly as Virgin Mobile in settings>sim info and in quick settings because by default without the fix we are listed as using Boost Mobile as our carrier and in quick settings it will just read "roaming indicator off" and can only use 3g. I am using the fix in CM 13 right now. The only difference between flashing the fix with CM 12.1 and 13 and probably CAF too is that APN's can be viewed,added,edited etc in CM 12.1 and in CM 13 APN's are not visable but the fix still works by replacing the correct files and prop edits.

The carrier information in SIM status is taken from eri.xml. I get no difference in functionality between patched and unpatched build.prop files. It may have once been necessary, but I think whatever problems those build.prop patches solved have been resolved.

deega said:
The carrier information in SIM status is taken from eri.xml. I get no difference in functionality between patched and unpatched build.prop files. It may have once been necessary, but I think whatever problems those build.prop patches solved have been resolved.
Click to expand...
Click to collapse
OK great
Sent from my Virgin Mobile Moto E via CM 13

scritch007 said:
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d
unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)
Update the getprop values, copy apns and eri to the right place.
I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.
CM13 will most probably won't get the fix.
Click to expand...
Click to collapse
I just looked a bit deeper into the code you linked. (specifically init_surnia.c) It's setting the CDMA values based on the value of ro.boot.fsg-id, expecting virgin or sprint else it's boost. A getprop ro.boot.fsg-id returns nothing on my CAF 0.10 surnia. getprop ro.cdma.home.operator.numeric returns 311870 (boost). Expected behavior would return the following in my case:
ro.boot.fsg-id=virgin
ro.cdma.home.operator.numeric=311490
If I understand the structure of APN entries correctly, getting this resolved would make it possible to include the APNs in the default apns-conf.xml.
I'm not sure how ro.boot.fsg-id is derived, but adding ro.boot.fsg-id=virgin to build.prop doesn't alter the above behavior.

deega said:
I just looked a bit deeper into the code you linked. (specifically init_surnia.c) It's setting the CDMA values based on the value of ro.boot.fsg-id, expecting virgin or sprint else it's boost. A getprop ro.boot.fsg-id returns nothing on my CAF 0.10 surnia. getprop ro.cdma.home.operator.numeric returns 311870 (boost). Expected behavior would return the following in my case:
ro.boot.fsg-id=virgin
ro.cdma.home.operator.numeric=311490
If I understand the structure of APN entries correctly, getting this resolved would make it possible to include the APNs in the default apns-conf.xml.
I'm not sure how ro.boot.fsg-id is derived, but adding ro.boot.fsg-id=virgin to build.prop doesn't alter the above behavior.
Click to expand...
Click to collapse
Yes this is taken from the CDMA test build I made. I had asked people to set the fsg-id to the correct value. This can be done thanks to fastboot:
Code:
fastboot oem config fsg-id virgin
This wasn't added into CM.

Something like that would certainly help! If the CDMA properties were set based on a user-selectable carrier then it would solve a lot of headache with the apns-conf.xml files. We know the appropriate APNs for Boost, Sprint, and Virgin. It would be nice to have them folded into the default apns-conf.xml.

deega said:
Something like that would certainly help! If the CDMA properties were set based on a user-selectable carrier then it would solve a lot of headache with the apns-conf.xml files. We know the appropriate APNs for Boost, Sprint, and Virgin. It would be nice to have them folded into the default apns-conf.xml.
Click to expand...
Click to collapse
It definitely would. I don't understand why this isn't already fixed in CM 12.1, it also should be listed as an issue in the wiki but it isn't.

I just tried placing the values from the code @scritch007 linked into build.prop like so:
Code:
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
gsm.sim.operator.numeric=311490
gsm.sim.operator.alpha=Virgin Mobile US
gsm.operator.numeric=311490
gsm.operator.alpha=Virgin Mobile US
Then I tried appropriately tagging the VM APNs with numeric="311490" mcc="311" mnc="490" while including them in a default, huge apns-conf.xml file.
Even with the proper numeric codes set in build.prop, the phone populates its APN database with Sprint (310120) APNs. Getprop yields the following results:
ro.cdma.home.operator.numeric=311490
gsm.sim.operator.numeric=31000
gsm.operator.numeric=310120
I sure hope hardcoding these values into init works better than defining them in build.prop. It's clear that the value of gsm.operator.numeric is pretty important. It's also clear that patching build.prop doesn't help us.
Pardon me if this is all old news, but I'm pretty new here.

RingPlus provisioning on Cyanogenmod

hey guys,
I'm currently running CM13 nightlies and want to do a clean install without flashing over my current setup. is there any way i can retain my provisioning while flashing a new cm build? i tried wiping and installing a new nightly build. everything booted fine, but the phone was not provisioned. even after flashing mvno slayer, the phone wouldn't register to the network.
I have to flash back to stock and then flash cm if I want a fresh install?

Provisioning *should* persist through flashes... unless you're changing providers.
I was able to get my device provisioned for Sprint on stock when I used it, and then was able to flash any ROM I wanted. Never needed to go back to stock, but I always stayed on Sprint.

arrrghhh said:
Provisioning *should* persist through flashes... unless you're changing providers.
I was able to get my device provisioned for Sprint on stock when I used it, and then was able to flash any ROM I wanted. Never needed to go back to stock, but I always stayed on Sprint.
Click to expand...
Click to collapse
technically it's ringplus (updated title), but I don't think being an MVNO makes the process any different. So if I wiped and flashed a new CM build but couldn't get the phone to register, what can I do? Trying to avoid going through the whole process of RSDlite back to stock and starting from complete scratch...

gtmaster303 said:
technically it's ringplus (updated title), but I don't think being an MVNO makes the process any different. So if I wiped and flashed a new CM build but couldn't get the phone to register, what can I do? Trying to avoid going through the whole process of RSDlite back to stock and starting from complete scratch...
Click to expand...
Click to collapse
I'm not following - was it working before, and the act of updating the ROM to a newer build of CM broke the provisioning?
Never heard of that before, but have you considered it's the update? Have you tried restoring a backup? You do have a backup...?

arrrghhh said:
I'm not following - was it working before, and the act of updating the ROM to a newer build of CM broke the provisioning?
Never heard of that before, but have you considered it's the update? Have you tried restoring a backup? You do have a backup...?
Click to expand...
Click to collapse
Yes, everything was working fine. I wipe, then flash a new build of CM, but it doesn't register with the network. Restoring my backup has everything working again. It's just that the rom has been quite sluggish and I wanted a fresh start. I don't know if it was always like this or because of an app. That's why I'm starting over

gtmaster303 said:
Yes, everything was working fine. I wipe, then flash a new build of CM, but it doesn't register with the network. Restoring my backup has everything working again. It's just that the rom has been quite sluggish and I wanted a fresh start. I don't know if it was always like this or because of an app. That's why I'm starting over
Click to expand...
Click to collapse
Just try to clean wipe the working ROM, see if that works.
If it does, I'd say that update of CM is the issue.

Did you ever find a solution? I am having the same problem. If I install the latest CM 13 the phone no longer connects to the cell network. Stupidly, I did not do any backup, so the only option I have to go back to the stock ROM. With the stock ROM the phone connects to to the network with no problem.

nemo3 said:
Did you ever find a solution? I am having the same problem. If I install the latest CM 13 the phone no longer connects to the cell network. Stupidly, I did not do any backup, so the only option I have to go back to the stock ROM. With the stock ROM the phone connects to to the network with no problem.
Click to expand...
Click to collapse
What about flashing an older build of CM13?
What were you running before you flashed the latest CM13?

arrrghhh said:
What about flashing an older build of CM13?
What were you running before you flashed the latest CM13?
Click to expand...
Click to collapse
To answer your questions, I was running CM13 I can't find older builds of CM13 that work. The only ones I find are relatively new.
I managed to get voice to work. I still don't have data. These are the steps I took. I am not sure all of them are necessary. But at least now voice is working.
Dial *#*#4636#*#*
Click on the 3 vertical dot menu on top right
Select Radio Band -> PCS (1900 MHZ)
Back button <|
Set Preferred Network Type to LTE/CDMA (auto PRL)
Back button <|
Back Button <|
Settings -> Cellular Network Settings ->Preferred Network Type -> CDMA+LTE/EVDO
Settings -> Cellular Network Settings->CDMA subscription -> NV
Reboot
---------- Post added at 05:23 AM ---------- Previous post was at 04:44 AM ----------
OK, now I got 3G data.
I changed
Settings -> Cellular Network Settings ->Preferred Network Type -> CDMA/EVDO/GSM/WCDMA
Reboot
Now if I could only get 4G without losing voice I'd be all set. Little by little...
---------- Post added at 05:25 AM ---------- Previous post was at 05:23 AM ----------
If I go to Settings -> Cellular Network Settings ->Access Point Names, I get a message that says "APN settings are not available for this user". Is that normal? I seem to remember I had a list of APNs.

I've got the exact same problem with the CM13 nightlies on Ting. I've tried a bunch of them all the way back to April and can't get LTE to work on any of them.
If I go back to the stock ROM, it works fine. If I go back to CM11, it works fine.
I don't know if its related or not, but in the SatStat app, it shows a bunch of dashes under LTE and some long numbers like 21474 83647. This line disappears and reappears every few seconds while the app is open.

abortretryfail said:
I've got the exact same problem with the CM13 nightlies on Ting. I've tried a bunch of them all the way back to April and can't get LTE to work on any of them.
If I go back to the stock ROM, it works fine. If I go back to CM11, it works fine.
I don't know if its related or not, but in the SatStat app, it shows a bunch of dashes under LTE and some long numbers like 21474 83647. This line disappears and reappears every few seconds while the app is open.
Click to expand...
Click to collapse
If it works in CM11 but not CM13, then something changed... Please submit logs to the CM maintainer (radio logs will probably be necessary). Of course make sure the correct settings have been applied.

Red Pocket Mobile APN Settings
arrrghhh said:
If it works in CM11 but not CM13, then something changed...
Click to expand...
Click to collapse
Following this procedure allowed me to use Voice, SMS MMS and internet (both 3G and 4G) on PAC-ROM and builds of Cyanogen Mod up to and including 12.1. I have not tried 13.
Code:
1. click "Mobile networks" to access the settings
2. Data enabled checked
3. Data Roaming unchecked
4. Battery Saving Mode unchecked
5. Set preferred network type to: CDMA+LTE/EvDo
6. System select - set roaming mode to Home Only
7. Set CDMA subscription to NV
8. Create a New APN with these values:
a. Name: Red Pocket
b. APN: n.r6.ispsn
c. Proxy: Not set
d. Port: Not set
e. Username: ##########@redpocket.sprintpcs.com
replace ########## with your red pocket mobile phone number
e. Password: Not set
f. Server: Not set
g. MMSC: http://mms.sprintpcs.com
h. MMS proxy: 68.28.31.7
i. MMS port: 80
j. MCC: 310
k. MNC: 120
l. Authentication type: Not set
m. APN type: default, mms
n. APN protocol: IPv4/IPv6
o. APN roaming protocol: IPv4/IPv6
p: Unspecified
q. MVNO type: None
r. MVNO value: Not set
s. save changes
9. Set the Red Pocket APN as your active one.
10. reboot

Net10 APN Settings?
I am giving you how I went from point A to B in this post. My next post will be the correct settings for my new Sprint mvno: Net10.
After getting voice, data, sms and mms working in the rooted stock ROM, I install the xposed framework for Android 4. Reboot
Open Play store and install "Hidden Android Settings" and "NoHiddenPasswords". NoHiddenPasswords is an xposed tool, but does not show up if you do a search in the xposed manager app. Open xposed and Enable NoHiddenPasswords. Reboot.
Back-up your tweaked Stock ROM with TWRP.
Install Cyanogen. When Cyanogen boots up, go to Settings-"Mobile Networks", my educated guess is that the settings for
Data enabled
Data Roaming unchecked
Battery Saving Mode unchecked
Preferred network type: CDMA+LTE/EvDo
System select - set roaming mode to Home Only
Set CDMA subscription to NV
I can at least confirm those work with the two mvno's I have used: Red Pocket & Net10.
The first thing I tried was to the same settings as I showed in my prior post.
I tried changing 8.e. to ##########@net10.sprintpcs.com. Then I tried ##########@sprintpcs.com. Neither of those worked, so I knew I needed to find the value using some tool in the Stock ROM. I googled Android APN settings app, and found "Hidden Android Secrets". It has a APN settings viewer. When I looked at the ones in my phone, I saw some password fields that it would not show me without the help of NoHiddenPasswords.
Then I used Notepad++ on my laptop to copy the information shown in each access point in the stock rom on my phone. I did a new tab for each access point.
It seemed pretty obvious that at least 8e would need changed.
I tried changing 8e to ##########@net10.sprintpcs.com
I then tried ##########@sprintpcs.com
Voice works & SMS worked, but no data nor MMS over 4g.
I notice that none of the access points in my stock ROM has any reference to n.r6.ispsn. There is one with an APN n.t9.ispsn. That is very similar so I changed 8.b. to that. Miracle, I now have LTE data!
Unfortunately, though, the MMS is till not working over LTE.
In my stock ROM, there is one and only one APN with APN Type: default,mms
BTW, there is no space after the comma in the stock ROM, so I changed that.
I merged its values into my APN.
This did not kill my data; so, I tried sending and receiving MMS. Tada, that's it.

APN Settings for Net10
RandyB201 said:
... the correct settings for my new Sprint mvno: Net10...
Click to expand...
Click to collapse
Code:
1. Open Settings
2. click "Mobile networks" to access the settings
3. Data enabled checked
4. Data Roaming unchecked
5. Battery Saving Mode unchecked
6. Set preferred network type to: CDMA+LTE/EvDo
7. System select - set roaming mode to Home Only
8. Set CDMA subscription to NV
9. Create a New APN with these values:
a. Name: Net10
b. APN: n.t9.ispsn
c. Proxy: Not set
d. Port: Not set
e. Username: none
e. Password: none
f. Server: Not set
g. MMSC: http://mms.sprintpcs.com
h. MMS proxy: 68.28.31.7
i. MMS port: 80
j. MCC: 310
k. MNC: 120
l. Authentication type: Not set
m. APN type: default, mms
n. APN protocol: IPv4
o. APN roaming protocol: IPv4
p: Bearer: LTE
q. MVNO type: None
r. MVNO value: Not set
s. save changes
10. Set the Net10 APN as your active one.
To be clear, the username and password are not an empty / null string. They are the word "none" all lowercase letters...

Virgin Mobile PRL Disappears From Custom ROM [Motorola Moto G 2015]

When flashing the Motorola Moto G 2015 with any custom ROM (Cyanogenmod, Resurrection Remix, Lineage), the PRL information sticks until a reboot from custom ROM.
When rebooting, the phone has internet access (including Hotspot), however no text messages, inbound/outbound phone calls do not work. The fix has been flashing Virgin Mobile stock ROM in TWRP recovery, programming the phone (##72786#) and then restoring a backup from custom ROM via TWRP recovery. Then the phone will again be able to send/receive text messages and phone calls - until the next reboot.
Would like to know if there is a fix to bypass reflashing stock ROM if phone needs rebooting from custom ROM. This process takes about 15 - 20 minutes. Big nuisance.
Any assistance would be appreciated.
------------

NetSpeedZ said:
Any assistance would be appreciated.
Click to expand...
Click to collapse
Copy this APN (see the attachments), to system/etc and set permissions to 0644 or rw-r--r-- with a root explorer. Reboot. Go to settings>more>cellular networks, select LTE in Preferred network type, and RUIM/SIM in system select. Tap the "carrier settings" option at the very bottom. All the radios will reset and come back on in a few seconds, and everything should work after that. Let me know if you need any more assistance, I'll be happy to help. I've had to deal with this issue since day one.
Edit; You will only have to do this after flashing a ROM, and this includes updates too. It can also be done through TWRP's file manager immediately after flashing before you even boot it the first time, and without root.

Spaceminer said:
Copy this APN (see the attachments), to system/etc and set permissions to 0644 or rw-r--r-- with a root explorer. Reboot. Go to settings>more>cellular networks, select LTE in Preferred network type, and RUIM/SIM in system select. Tap the "carrier settings" option at the very bottom. All the radios will reset and come back on in a few seconds, and everything should work after that. Let me know if you need any more assistance, I'll be happy to help. I've had to deal with this issue since day one.
Edit; You will only have to do this after flashing a ROM, and this includes updates too. It can also be done through TWRP's file manager immediately after flashing before you even boot it the first time, and without root.
Click to expand...
Click to collapse
Cyanogenmod 12.1 does not have the menu - settings>more>cellular networks. Is this done via stock ROM?
Also, don't have RUIM/SIM in system select. Only 'Home Only' and 'Automatic'.
------------

NetSpeedZ said:
Cyanogenmod 12.1 does not have the menu...
Click to expand...
Click to collapse
Try rebooting the ROM without your sim card in. Then put it back and reboot once more. It should reset. I didn't realize you were still using cm12. Those settings are only found in 6.0.1 and up. The apn settings not being visible has something to do with us being CDMA. I think it's the sim cards virgin uses.
You also need to add these lines to the end of your build.prop too. (Not needed on MM+)
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
ro.telephony.default_network=8
telephony.slteOnCdmaDevice=1

Spaceminer said:
Try rebooting the ROM without your sim card in. Then put it back and reboot once more. It should reset. I didn't realize you were still using cm12. Those settings are only found in 6.0.1 and up. The apn settings not being visible has something to do with us being CDMA. I think it's the sim cards virgin uses.
You also need to add these lines to the end of your build.prop too. (Not needed on MM+)
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
ro.telephony.default_network=8
telephony.slteOnCdmaDevice=1
Click to expand...
Click to collapse
While waiting for your reply, I copied the APNS-Conf.xml file attached to your original reply to the system/etc folder on phone and rebooted. Inbound/outbound phone calls and text messages seem to be working now. Even performed a backup in TWRP and then rebooted again. All seems to be operating properly.
I did not add the build-prop text you gave in previous reply. What exactly does this build-prop text do? I'm hesitant in adding it as everything is operational - the old saying 'don't fix what isn't broken'.
I was using Cyanogenmod 13, however, I did not like some of the Cyanogenmod 13 apps, i.e., text messaging app. The Cyanogenmod 12.1 texting app has many features that CM 13 doesn't. Also, CM 12.1 seemed to run smoother on the Motorola Moto G 2015 phone I'm currently using.
Also would be interested in knowing where the apns-conf.xml file was pulled from and what all this file did to make everything work again.
FYI, as standard procedure I always mount system and then flash the Virgin Mobile APNFix (which I've attached for anyone running across this thread in need of this file) in TWRP after flashing a new ROM and associated GAPPS , however, it seems that the apns-conf.xml file became corrupt/unusable somewhere along the line.
Your efforts in helping me solve this issue are appreciated.
------------

NetSpeedZ said:
I did not add the build-prop text you gave in previous reply. What exactly does this build-prop text do? I'm hesitant in adding it as everything is operational - the old saying 'don't fix what isn't broken'. ....
Also would be interested in knowing where the apns-conf.xml file was pulled from and what all this file did to make everything work again.
Click to expand...
Click to collapse
If everything is working properly, then don't worry about adding those lines. I had to add those and the apn to get LTE working on the older test builds of cm12. As far as I know, it just locks you to virgin. It was likely fixed in later builds of cm12.
The APN I pulled from an older build of cm13. When flashing the older ones, the install process would locate and copy virgin's current apn to /system/etc and rename Motorola's default APN to .bak. (The giant 500kb+ APN with all the carriers found in stock.) It would also add a US Cellular APN. I discovered at some point from poking around enough, that deleting the .bak and US Cellular APNs got LTE working if I reset the radio afterwards.

Spaceminer said:
If everything is working properly, then don't worry about adding those lines. I had to add those and the apn to get LTE working on the older test builds of cm12. As far as I know, it just locks you to virgin. It was likely fixed in later builds of cm12.
Click to expand...
Click to collapse
This is a nice and informative thread for anyone that has the same issues that you and I have had with Virgin Mobile APN's. Hopefully it will be added to Google searches soon.
Appreciate all the help.
------------

Visible Wireless and Custom Roms

Has anybody gotten visible Wireless to work correctly on custom roms? I got it up and running no problem on oxygen OS, but for some reason I just can't get it going on customs.
It's literally driving me insane.

I'm bumping this thread... been trying out some custom roms (Havoc and trying Bliss now) but haven't been able to get any Visible Wireless (by Verizon) signal on my phone.
Does anyone know if ANY custom ROM works? Particularly interested in ASOP ROMs, not ones based on OOS.

dizM0nkey said:
I'm bumping this thread... been trying out some custom roms (Havoc and trying Bliss now) but haven't been able to get any Visible Wireless (by Verizon) signal on my phone.
Does anyone know if ANY custom ROM works? Particularly interested in ASOP ROMs, not ones based on OOS.
Click to expand...
Click to collapse
Yes, you can get visible wireless to work on all custom roms now. Used to not be able to because custom roms wouldn't detect Verizon Sims, but that's been fixed for a couple months now. Only thing that needs to be done is updating the apn config. The instructions to replace the apn config file are located here. The only difference is on Android 10, it's located in /system/product/etc/ instead of /system/etc/ that is lit used to be on Android 9. I've uploaded the new apn config file that you need to use.

jeffsga88 said:
Yes, you can get visible wireless to work on all custom roms now. Used to not be able to because custom roms wouldn't detect Verizon Sims, but that's been fixed for a couple months now. Only thing that needs to be done is updating the apn config. The instructions to replace the apn config file are located here. The only difference is on Android 10, it's located in /system/product/etc/ instead of /system/etc/ that is lit used to be on Android 9. I've uploaded the new apn config file that you need to use.
Click to expand...
Click to collapse
Awesome... I opened in Notepad++ and searched for "VSBL" ... four entries were found. I was able to combine most of the entries into 'apn carrier="Visible Internet"'
<apn carrier="Visible Internet"
mcc="311"
mnc="480"
apn="VSBLINTERNET"
type="default,dun,supl,fota,ims,mms,ia,cbs"
mmsc="http://mms.vtext.com/servlets/mms"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
profile_id="0"
modem_cognitive="true"
max_conns="20"
max_conns_time="300"
wait_time="0"
read_only="false"
mvno_type="GID"
mvno_match_data="BAE1000000000000"
/>
Data, MMS, etc all working great. Thanks for sharing!

it works
Wow. I just got a H830 unlocked lg g5 running lineage 17.1 working with visible LTE. I merely switched the apn.xml file as you said and switched my preferred network mode to LTE. THANK YOU!!
---------- Post added at 01:33 AM ---------- Previous post was at 01:26 AM ----------
Burt Squirtz said:
Has anybody gotten visible Wireless to work correctly on custom roms? I got it up and running no problem on oxygen OS, but for some reason I just can't get it going on customs.
It's literally driving me insane.
Click to expand...
Click to collapse
Yes!!! I finally did! Lineage 17.1 on a lg g5 h830 and on lineage 17.1 galaxy s9. Both working. WOOHOO! Merely swap apn.xml, chmod, reboot, reset settings, then click visible internet, then set network mode to "LTE"

I have a OP8 Pro that I've been trying to get work with Visible and custom roms (Resurrection Remix and/or crDroid specifically), but have hit a dead end.
crDroid doesn't let me edit any of the "Network Settings," the option is grayed out entirely with the Visible SIM inserted (but the lock screen shows "No SIM inserted - Visible," giving the impression that the phone sees the SIM in one slot, knows it is Visible, but won't connect or register it to allow changing settings).
Resurrection Remix will recognize the SIM, and I can get into Network Settings. I've tried to add all 4 APNs manually after flash and can't get it to get a signal at all, leading me to believe that there's further, "deeper" integration that I don't have access to after flashing is complete and system partitions are locked as read-only.
TWRP 3.40-14 by mauronofrio works with Resurrection Remix flashed, but System, Vendor, Product, etc. are all locked as read-only, so editing the apn-conf.xml file can't be edited. And, sadly, that's where I'm at. A bit frustrating that OOS stock recognizes everything instantly upon initial boot, but custom roms won't. If there's any information I can provide to help get universal support for this carrier, I would be more than happy to help contribute.

lee_d said:
I have a OP8 Pro that I've been trying to get work with Visible and custom roms (Resurrection Remix and/or crDroid specifically), but have hit a dead end.
crDroid doesn't let me edit any of the "Network Settings," the option is grayed out entirely with the Visible SIM inserted (but the lock screen shows "No SIM inserted - Visible," giving the impression that the phone sees the SIM in one slot, knows it is Visible, but won't connect or register it to allow changing settings).
Resurrection Remix will recognize the SIM, and I can get into Network Settings. I've tried to add all 4 APNs manually after flash and can't get it to get a signal at all, leading me to believe that there's further, "deeper" integration that I don't have access to after flashing is complete and system partitions are locked as read-only.
TWRP 3.40-14 by mauronofrio works with Resurrection Remix flashed, but System, Vendor, Product, etc. are all locked as read-only, so editing the apn-conf.xml file can't be edited. And, sadly, that's where I'm at. A bit frustrating that OOS stock recognizes everything instantly upon initial boot, but custom roms won't. If there's any information I can provide to help get universal support for this carrier, I would be more than happy to help contribute.
Click to expand...
Click to collapse
I have a Pixel 4a and none of the custom ROMs except 1, which naturally was the last one I tried, worked. The ROM that worked had this dir /product/etc/CarrierSettings/ with a config for each carrier, Visible's config filename being visible_us.pb, and this dir was missing from the ROMs that Visible did not work on. Note the stock firmware had the same dir and Visible config as well. I also have /product/etc/apns-conf.xml in my ROM that works on Visible but the Visible APNs are NOT in that config so it's pulling it from the visible_us.pb.
It's clearly a firmware issue on some level. I suspect it's simply a matter of getting the system to use the proper APNs. It seems to me that the only way to do that is by building the ROM with the Visible APNs baked in the /product/etc/CarrierSettings/visible_us.pb, or /product/etc/apns-conf.xml, depending on where your implementation gets these default values from — or maybe it's the implementation that makes the difference, I'm not sure.
What doesn't make sense to me is why adding the APNs in settings manually had zero effect. I got the same default APNs to select from when I insert the SIM with ROM that did not work as you, StraightTalk, Verizon, and Xfinity. I also noticed that intermittently it would automatically load the VSBLINTERNET APN from the SIM but nothing would work.
I think the next step is to try to get the devs to include the Visible APNs to apns-conf.xml in the next build. I suspect that will cure this. Too bad Android make the system RO or it would be trivial.
Links that may be of interest..
This is my ROM for Pixel 4a that does work on Visible forked from ASOP.
https://forum.xda-developers.com/t/official-superioros-xcalibur-android-11.4181587/
https://github.com/daradib/carriersettings-extractor
https://www.reddit.com/r/oneplus/comments/g36mxn
https://github.com/GrapheneOS/os_issue_tracker/issues/153

guru6969 said:
I have a Pixel 4a and none of the custom ROMs except 1, which naturally was the last one I tried, worked. The ROM that worked had this dir /product/etc/CarrierSettings/ with a config for each carrier, Visible's config filename being visible_us.pb, and this dir was missing from the ROMs that Visible did not work on. Note the stock firmware had the same dir and Visible config as well. I also have /product/etc/apns-conf.xml in my ROM that works on Visible but the Visible APNs are NOT in that config so it's pulling it from the visible_us.pb.
It's clearly a firmware issue on some level. I suspect it's simply a matter of getting the system to use the proper APNs. It seems to me that the only way to do that is by building the ROM with the Visible APNs baked in the /product/etc/CarrierSettings/visible_us.pb, or /product/etc/apns-conf.xml, depending on where your implementation gets these default values from — or maybe it's the implementation that makes the difference, I'm not sure.
What doesn't make sense to me is why adding the APNs in settings manually had zero effect. I got the same default APNs to select from when I insert the SIM with ROM that did not work as you, StraightTalk, Verizon, and Xfinity. I also noticed that intermittently it would automatically load the VSBLINTERNET APN from the SIM but nothing would work.
I think the next step is to try to get the devs to include the Visible APNs to apns-conf.xml in the next build. I suspect that will cure this. Too bad Android make the system RO or it would be trivial.
Links that may be of interest..
This is my ROM for Pixel 4a that does work on Visible forked from ASOP.
https://forum.xda-developers.com/t/official-superioros-xcalibur-android-11.4181587/
https://github.com/daradib/carriersettings-extractor
https://www.reddit.com/r/oneplus/comments/g36mxn
https://github.com/GrapheneOS/os_issue_tracker/issues/153
Click to expand...
Click to collapse
This was extremely informative! Hopefully this will be helpful to somebody else seeking the info and scouring the web for answers.
I'm on stock OOS right now on an unlocked OP8 Pro. There is no CarrierSettings on this rom, so maybe it's just the APN file? I couldn't find a visible_us.pb file either. But I've also had a dev whip up a Magisk module that supposedly added the APN settings in, to no avail. Perhaps "baking in" is different than trying to overwrite via Magisk.
Of course, I say all of this pleading ignorance to what may be obvious to actual contributors. I have virtually no idea what I'm doing and am probably talking out my ass.

lee_d said:
This was extremely informative! Hopefully this will be helpful to somebody else seeking the info and scouring the web for answers.
I'm on stock OOS right now on an unlocked OP8 Pro. There is no CarrierSettings on this rom, so maybe it's just the APN file? I couldn't find a visible_us.pb file either. But I've also had a dev whip up a Magisk module that supposedly added the APN settings in, to no avail. Perhaps "baking in" is different than trying to overwrite via Magisk.
Of course, I say all of this pleading ignorance to what may be obvious to actual contributors. I have virtually no idea what I'm doing and am probably talking out my ass.
Click to expand...
Click to collapse
Old thread but I am just discovering (via Oxygen Updater) that the IN2015 I purchased from eBay thinking it was a US Open model, not a Visible Frankenstein's monster, will not update from 10.5.4 IN68CE via Oxygen Updater in April 2021.
I just canceled eBay return (128GB was listed as 256GB) but kept based on like new condition and assuming I could easily bootloader unlock, root, flash International Oxygen 11 and use dual SIM tray (eBay order).
Wondering if anyone has successfully updated (via fastboot flashing) a OP8 Visible version to a true carrier free model.

KnowNadda said:
Old thread but I am just discovering (via Oxygen Updater) that the IN2015 I purchased from eBay thinking it was a US Open model, not a Visible Frankenstein's monster, will not update from 10.5.4 IN68CE via Oxygen Updater in April 2021.
I just canceled eBay return (128GB was listed as 256GB) but kept based on like new condition and assuming I could easily bootloader unlock, root, flash International Oxygen 11 and use dual SIM tray (eBay order).
Wondering if anyone has successfully updated (via fastboot flashing) a OP8 Visible version to a true carrier free model.
Click to expand...
Click to collapse
I sold mine and went for the 8 pro, so I'm not aware of anything. I couldn't get it to do anything but run the visible software, unfortunately.

Bummer! Before I follow up my recent eBay return of the blacklisted OP7 Pro I received with a return of this, I guess I'll get familiar with MSM Tool and try to flash different versions of Android 10 and see if I can get something running that I can upgrade. I need non carrier restricted OOS so it will recognize two SIMs. Question is if I can even utilize 2 SIMs with a single IMEI device.
Looking like another eBay return is in my future.