yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro Questions & Answers] tdamocles:
I have done it both ways and both don't work. Custom roms are a little unstable right now for me to try. I had to use file commander because for some reason root explorer doesn't work correctly. I'm on oos 10.

View attachment 4837137View attachment 4837139
[OnePlus 7 Pro Questions & Answers] jeffsga88:
That's odd that it's not working. I personally use total commander to do it, although any file explorer with root should work. Also, using TWRP should work no matter what as well. Only thing I did differently on OOS was I did a clean install and then before even booting into OOS for the first time (so after clean install reboot to recovery) I replaced the apns-conf.xml and when I booted into system everything worked. The other ways should work on OOS even after the os is already set-up as well, although only personally tested them on Omni. Only reason I did it right away with OOS is didn't want to setup OOS and then do it to find out it wasn't working What is showing up on your access point names? Can you provide screen shot.
[OnePlus 7 Pro Questions & Answers] tdamocles:
HereView attachment 4837149View attachment 4837151View attachment 4837153View attachment 4837155
[OnePlus 7 Pro Questions & Answers] jeffsga88:
I'm starting to wonder something. First time I tried editing the apns-conf.xml and getting everything working when Android 10 first released I couldn't get it to work either, but always had done that on a already setup OOS. I'm wondering if me replacing the apns-conf.xml before first boot is reason it worked. Try taking out sim card and do it from twrp then once booted up insert sim card and try reset apns.
[OnePlus 7 Pro Questions & Answers] tdamocles:
I'm reflashing 10 right now and before I boot into the os I will transfer apn via twrp.
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Okay, let me know if that works for you or not. Make sure you reboot to recovery after flashing 10 before replacing the apn config and ch mod to 0644.
[OnePlus 7 Pro Questions & Answers] tdamocles:
It's going to take a few......

Going to flash android10,twrp twice. Going to transfer apns twice, then before booting OS I'm going to flash magisk. Last, going to re-insert sim card. Reboot!

---------- Post added at 09:28 PM ---------- Previous post was at 08:32 PM ----------

Nope, Did a lot of flashing and things and it still doesn't see the apns. Any other ideas?
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Did you do a clean install? Wipe and format data or just installed over current install? Check the /data/data/com.android.providers.telephony/databases/ and take a screenshot. Also did you install OOS and twrp then reboot to TWRP and replace the apn config and chmod? My exact steps with OOS we're boot to TWRP, format, factory reset, reboot to TWRP install OOS and TWRP reboot to TWRP install magisk and replace apn config, chmod to 0644 and then boot into system and had sim card in whole time.
[OnePlus 7 Pro Questions & Answers] tdamocles:
Just did exactly what you said and it didn't help....need a phone tomorrow. going back to .13.

View attachment 4837187
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Okay so did a little testing and restoring default apn messed things up on OOS even though it's necessary on custom ROMs. Anyways, me replacing it before booting is why it worked although I was able to get it working again after messing it up without reinstalling OOS. I took the Verizon apn lines completely out of the apns-conf.xml and am attaching the new config file. The way I got it to work after messing it up was to boot into twrp, mount system, remove apns-conf.xml and replace it with the new apns-conf.xml and chmod to 0644. When booted back into OOS I skipped the reset to default in apns and it automatically loaded the correct apns and selected visible by default. Hopefully this works for you if you get a chance to test on 10 again.
[OnePlus 7 Pro Questions & Answers] tdamocles:
I'll try tomorrow, it's time to go to bed.
[OnePlus 7 Pro Questions & Answers] oRAirwolf:
I would be interested to know if this is a problem with the Visible application not applying the APN's correctly or a problem with Oxygen OS. It would be nice to know who needs to fix this.
[OnePlus 7 Pro Questions & Answers] tdamocles:
Seriously don't think it's the visible app adding anything. I can install the Android pie .13 visible compatible version without the app and I still get signal.
[OnePlus 7 Pro Questions & Answers] jeffsga88:
It's OOS that's the issues, the app doesn't have anything to do with it. When OnePlus started working on Android 10 they never pushed the changes from 9.5.13 that added the visible apns into their Android 10 source. Hopefully they fix it on the next release, but it's up to OnePlus to fix not visible. Also, until they do fix it at least there are work arounds.
[OnePlus 7 Pro Questions & Answers] adame09:
Trying this now.
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Let me know if you have any issues with it. If you use restore apn to default make sure you reboot after and once OOS is back up go into access points and you should be able to select the VSBLINTERNET apn.
[OnePlus 7 Pro Questions & Answers] tdamocles:
I give up....I've used the new apns and it still doesn't see visible apns! Very annoying!
[OnePlus 7 Pro Questions & Answers] jeffsga88:
I sent a pm if you're still on Android 10 and want to try a couple more things to get it to work, pm me back. It would be easier to pm than trying to troubleshoot on this thread. To anyone else, it would be helpful to have feedback if you were successful or are having issues as well. It should work without issues and works for me on both OOS and Omni, but obviously it's not working for everyone.
[OnePlus 7 Pro Questions & Answers] adame09:
Didnt work for me either. I'm back on PIE. I do want to get it to work still
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Okay well I'll test some other things later. Only thing I can think of is that I replaced the apns-conf.xml before first boot on OOS. I'll try without doing that and see if I can get it to work still. It may also help to replace the telephony.db file as that stores the apns as well. I've attached the db with the Verizon apns replaced with visible apns. The file goes in /data/user_de/0/co.android.providers.telephony/databases/

and needs permissions 0660 to be set. Also after replacing the file you need to reset apns in sim and network settings. Also you must have already replaced the apns-conf.xml file from before. Just make sure to backup your telephony.db first in case of issues. I removed my sim card info from the file and it should auto populate yours on boot. By the way you have to remove the .zip extension from my attachment, only way I could upload it was to add it.

Edit:

After doing more testing it seems on some ROMs including OOS that after replacing the apn config file, visible sim only works when inserted in sim 2 slot and not in sim 1 slot. I tested and got visible working on Omni 10, PA 10 and OOS 10 stable. On Omni and OOS, I only got visible to work in sim slot 2 after replacing the apn config in twrp. On PA I was able to get visible to work using either sim slot after replacing the apn config in twrp. Not sure why it would work in one sim slot and not the other, but that's what was happening during testing.
[OnePlus 7 Pro Questions & Answers] tdamocles:
The sim slot 2 testing, is that with the telephony change and the XML change? Originally The sim slot change did not help me but that was only with the XML change.
[OnePlus 7 Pro Questions & Answers] jeffsga88:
It was just changing the xml in twrp and chmod, resetting default apn in sim and network and putting sim card in slot 2. This was all done on fresh installs of each ROM that I tested. If that alone doesn't work I would replace the telephony.db and reset apns as well and try. Also changing the sim slot was using the 2nd apn xml file I posted not the 1st one. Hopefully all this will be fixed when they release the Android 10 hotfix later this month. It was posted by funk wizard that they stopped Android 10 rollout and will push a new one with bug fixes later this month, hopefully visible apns is one of the bug fixes. Although in custom ROMs, replacing apn config will still probably be necessary until devs update the config that ships with the ROMs.
[OnePlus 7 Pro Questions & Answers] motoridersd:
I tried to activate Visible after upgrading to 10, and the app never sees the SIM card. What else changed in 10 vs 9.5.13 that would prevent the app from activating the SIM card? I tried it in both slots. Haven't tried the APN changes mentioned above, it's possible the app is not moving on because it's not able to get the APN to work on 10 until I make those changes
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Activate on 9.5.13 first. I was already activated on 9.5.13 and then moved to 10 and did the apn changes. You don't need to worry with the app once you've activated the sim card.
[OnePlus 7 Pro Questions & Answers] motoridersd:
Eh, I've been considering going back to 9.5.13 to do it, but it's not critical at the moment. I just wanted to test the service. I tried to go back once and then ran into the whole Android 10 vs 9 encryption incompatibilities, and after hours of filtering through incorrect solutions in multiple threads, I was finally able to recover my 10 Backup. Haven't tried to go back since then, even though I now have my 9 and 10 backups safely stored elsewhere.

I'm half just waiting for an OOS 10 update that will make it work.
[OnePlus 7 Pro Questions & Answers] adame09:
Just do this:

Flash OOS 9.5.13

Flash TWRP installer V-70

Format Whole data partition

The ROM should boot up and then you can go back and flash a kernel or magisk if you need to.
[OnePlus 7 Pro Questions & Answers] texasaggie1:
It works fine for me!
[OnePlus 7 Pro Questions & Answers] adame09:
Tried on OOS couldn't get it to work. Trying on PA now.
[OnePlus 7 Pro Questions & Answers] motoridersd:
I tried this last night and... it didn't work... Being encrypted, this is a lot more complicated. Either way, I realized Visible is compatible with the Pixel line, so I dusted off my Pixel 1 and was able to activate.

Interesting things I noticed. The Pixel had signal right away, even before activation. Something the OP does not have in OOS 10. So I think the issue we are having is tied to the phone maybe not recognizing the SIM card and registering on the Verizon network because of that, or, the phone is not reporting the SIM card to Verizon properly.

Would be nice to know exactly what changed between 9.5.13 and 10.0.

I replaced the apn-conf.xml and telephony.db files that you've posted and I still didn't have a signal before activating. I also tried wiping data on TWRP after replacing both files, and nothing.

I do want to point out that I went from 9.5.11 to 10.0, I never installed 9.5.13 because I was running a Magisk module that only worked on 11. Maybe the difference is the modem baseband version. Mine is:

MPSS.HE

1.0.c11.1-00007-SM8150_GEN_PACK-2.222787.1.222952.1

I just ran logcat when activating the Visible slot (Slot 2 on my phone, shows up as simSlotIndex 1 in the logs, 0 is Slot 1) and I see no 'Visible' entries in the logs. All I see is Verizon:

10-10 06:54:21.536 3012 3012 D SimEnablerPreference(1): update(){id=2, iccId=[****] simSlotIndex=1 carrierId=2146 displayName=Verizon carrierName=Emergency calls only nameSource=3 iconTint=-13408298 mNumber=[****] dataRoaming=0 iconBitmap=android.graphics.Bitmap@c7ede93 mcc 311 mnc 480mCountryIso=us isEmbedded false accessRules null cardString=891480000[****] cardId=2 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = [311480] hplmns = [311480] subscriptionType=0 mGroupOwner=null}
10-10 06:54:21.536 3012 3012 D SimEnablerPreference(1): update: isSubValid true provision status[1] = 1
10-10 06:54:21.536 3012 3012 D SimEnablerPreference(1): setChecked: uiccProvisionState truesir:{id=2, iccId=[****] simSlotIndex=1 carrierId=2146 displayName=Verizon carrierName=Emergency calls only nameSource=3 iconTint=-13408298 mNumber=[****] dataRoaming=0 iconBitmap=android.graphics.Bitmap@c7ede93 mcc 311 mnc 480mCountryIso=us isEmbedded false accessRules null cardString=891480000[****] cardId=2 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = [311480] hplmns = [311480] subscriptionType=0 mGroupOwner=null}

I would expect these entries to come up as Visible instead of Verizon, at least the Pixel does this.

I manually flashed the 9.5.13 baseband and for a second the SIM slot was recognized as Visible, but now both slots are inactive and not working (not even my Tmo SIM). I'll fix by restoring everything to stock OOS 10 for now.
[OnePlus 7 Pro Questions & Answers] jeffsga88:
The baseband version you listed is correct for OOS 10, so that's not the issue. Also, because visible uses same mcc mnc (311 480) as Verizon, that's why it shows Verizon and not visible. Also why when I edited those files I replaced all the 311480 entries of Verizon to visible except the Verizon emergency apn which is what showing in your log, that should stay as Verizon emergency. If you're still on OOS 10 can you try to replace the apns-conf.xml (using the 2nd one I posted) in twrp, ch mod to 0644 and then also replace the telephony.db in twrp at same time and chmod 0660 then when you boot back into OOS go into sim and network and restore default apns (probably have to reboot after doing that), unless you already did it that way. Doesn't make sense how I got it to work doing that and it's not working for others, so still trying to figure that one out. I remember when I first went to 10, no matter what I couldn't get it to work so I reverted to 9.5.13, then wanted to test Omni 10 and upgraded to 10 again and flashed Omni over it and got visible working with the apns-conf.xml edit so decided to go back to OOS 10 and see if it worked and it did with replacing the xml in OOS. Now even on a clean flash without replacing the apns-conf.xml it's working, so I wonder if getting it to work in Omni first was the key. Doesn't make sense to me because flashing OOS 10 in TWRP should be overwriting everything in system.
[OnePlus 7 Pro Questions & Answers] motoridersd:
Did you ever apply the OOS 10 OTA upgrade from 9.5.13? Or have you always flashed the 10 ROMs through TWRP?

The current apn-conf.xml file on my phone is the one you provided, I checked the md5sum and it's the same on the phone vs my download. I also replaced the telephony.db file at some point, after replacing the apn xml, reset the APN settings, and nothing. I don't think this is where the problem is at the moment. The phone should still connect to the network and show a signal level, without the APN we just won't have data, but the failure to even connect and being stuck in Emergency Mode.

When I look at LTE Discovery, the phone is switching between 310 410 (AT&T) and 310 260 (T-Mobile) and I don't see it trying to connect to 311 480. I think the problem our phones are having is that the modem does not know that the Visible SIM is supposed to connect (or is allowed to connect) to 311 480. If I do a manual network selection and select Verizon from the list, I get an error. So I think the issue is more base level than APN and Telephony DB. At least in my case. It looks like tdamocles is having the same problem, where their phone is not connecting to the network either (look at the screenshots posted, the signal icon is empty, just like on mine).
[OnePlus 7 Pro Questions & Answers] jeffsga88:
Always flashed through TWRP and I had the same issue originally when on OOS 10. It wasn't until I flashed Omni 10 and did the apn replacing that I was able to first get visible to work on OOS. But even after flashing OOS again after being on Omni 10, it did same thing of emergency only and no signal shown until I replaced the apn config. So not really sure. But we wouldn't get signal without apns correct as we use lte and volte for phone calls (cdma less). We have to at least have the VSBLMS apn to get signal and VSBLINTERNET apn for data. Maybe it had something to do with being on Omni and getting it to work first but not sure. I have it working on all Android 10 ROMs nowb including OOS.
[OnePlus 7 Pro Questions & Answers] tdamocles:
If anyone cares, ob3 works on visible..
[OnePlus 7 Pro Questions & Answers] motoridersd:
Oxygen Updater just prompted me about OOS 10.0.1. There were no release notes, but figured, why not install it. I had downgraded to 9.5.13 and got Visible working.

I can confirm that 10.0.1 is Visible compatible. At least after upgrading from 9.5.13. We'll probably get more info later on. Patch level is still September tho.

Filename is OnePlus7ProOxygen_21.O.21_OTA_021_all_1910071446_6f7c731d5aa7dbe.zip

edit: Baseband got updated to 1.0.c11.1-00007-SM8150_GEN_PACK-2.223543.1.223599.1
[OnePlus 7 Pro Questions & Answers] oRAirwolf:
Nice! Thanks for testing it out.
[OnePlus 7 Pro Questions & Answers] oRAirwolf:
Just upgraded to OOS 10.0.1 from 9.5.13. Visible is working for me as well.
[OnePlus 7 Pro Questions & Answers] crunchybutternut:
I'm just switching to Visible (from Verizon) but am unable to get the SIM to activate. Running OOS 10.0.3.

Anyone else upgraded, and still working?

(Spent 5 hours in chat, with no luck resolving.)
[OnePlus 7 Pro Questions & Answers] reaper000:
Spent an hour this morning in chat with Visible support... And still can't get the SIM to be recognized by their app. At least Verizon prepaid SIM still works (in slot 2). Visible escalated my case up their support chain and I'm supposed to hear from them via email in 24-48hrs(!?).

Running OOS 10.3.0. The phone recognizes Visible SIM in slot 1 under Settings > Network, but their app doesn't and only emergency calls can work.

The support rep seemed pleasant enough, but not particularly impressed so far. Leaving me hanging for 2 days is hardly a good way to start.
[OnePlus 7 Pro Questions & Answers] tcfiero:
I switched from Vzw to Visible before I updated to 10.3.0. I did not have any problems switching over.
[OnePlus 7 Pro Questions & Answers] reaper000:
Well, it's been 15 hours since my initial AM chat with Visible customer service. No indication a damn thing is being done, except i got platitudes of "you deserve the best service" and "everything is being done to push activation to the SIM".

Why in the blue hell would it take Visible 15 HOURS (and counting) to get me on their network when it took their parent company less than 15 MINUTES to essentially do the same damn thing?!

The fact that I'm waiting for an email from them notifying me that they've done something also sticks in my craw.

This isn't any model of customer service that the average consumer would want. As a vzw shareholder, this experience is making my skin crawl.

Update: It took nearly 30 hrs, but Visible emailed me to say that they resolved their issue and my SIM was now active. Which my phone confirmed. Now running on OOS 10.3.0 on Visible's network. Finally.
[OnePlus 7 Pro Questions & Answers] non1oson:
hey guys I got my one7pro in the UK. what's the difference between EU and non EU updates. should I just do the EU one?

thanks

ps i tired searching but couldn't find the difference :o
[OnePlus 7 Pro Questions & Answers] gapp:
Oneplus 6T not working on Visible

Oneplus 6T not working on Visible. I did get data working at one point. Any ideas? I'm running software 10.3.2.
[OnePlus 7 Pro Questions & Answers] rabidandroid9398:
I copied to the correct directory but the .xml file goes from 885kb to 0b for some reason. It's not allowing me to edit anything either
[LG V30 Questions & Answers] schwinn8:
Hey everyone,

So I did this on my personal phones a few years ago, and even my MIL's phone (Mother in law). I cut the SIM card in those cases, and plugged it into the new phone, and all worked just fine for the most part (MIL phone is having issues, maybe because I did a poor job of the manual cutting).

Anyway, now I'm on the FIL's phone (father in law). I activated a brand new phone on an old Droid Turbo phone, and it's working fine there. I moved the SIM to the new V30 (originally US998) and it's not registering on the network. I wonder if I just did this too quickly (I didn't let the SIM "sit" on the Turbo for very long)... which is why I moved it back there now. I figure I should let it sit there for a bit, and then try again?

Any ideas on what else I can try? Basically, the V30 was saying it saw the phone number, but it said IMS not registered... any ideas on how we can fix that? The *#*#4636#*#* doesn't work on the LG phones... I've used Shortcut Master before to register VOLTE, but I'm out of my realm here because the SIM is not registering the phone, so that's not an APN or VOLTE issue.

Any help or ideas are appreciated... thank you!

EDIT: One more comment. I'm hoping to go to VZ tomorrow and get a new card for the MIL phone. In order to activate that SIM, I'll have to activate that SIM on the Turbo, otherwise VZ will throw a hissyfit for the mismatched IMEI. So, I'm hoping I can repeat this process with the new SIM on that phone... I'm hoping we don't have this problem there too.

Ugh, VZ, why do you suck so bad.
[LG V30 Questions & Answers] cmrntnnr:
I've been down a similar path. I own the same phones. You didn't mention which rom is on the v30 but suspect it is a us998. I, too, had some difficulties getting my v30 to work properly on the vz network. The turbo with a stock verizon rom came in handy to set vz account/network options.

1) Install stock MM rom on the turbo. The debloated one by computer_freak works great. You can get it here: https://xdaforums.com/droid-turbo/development/computerfreek274mm1-0-android-6-0-1-t3503634

2) Pop the vz sim in the turbo

3) Activate: HD calling, visual voicemail in the dialer, and set up volte. I don't remember if vowifi is an option on the turbo. If it is, then turn it on, too.

4) Put sim in the v30 and enjoy.

Another and possibly better option to get the sim and phone working together is to cross-flash to the verizon vs996 rom. The advantage of the vs996 rom is that vowifi and visual voicemail will work. I've never succeeded in getting vowifi provisioned on the us998 open market rom. That is some vz-lg shennanigan.
[LG V30 Questions & Answers] 4stringenator:
I second what cmrntnnr stated above and emphasize flashing VS996 on the V30. Big Red can still tell what your phone actually is by its IMEI. My V30 originally was a LS998. I also had to manually set the MMS settings to keep Verizon firmware from thinking it is a Sprint phone. Please see this if you have issues with MMS. https://xdaforums.com/lg-v30/how-to/guide-how-fixed-mms-settings-flashable-t3856109
[LG V30 Questions & Answers] schwinn8:
Yes, I am on VS996 for this phone. And I did this very same process on my personal phones, but for some reason the new V30 isn't accepting the card, which is why I asked.

Yes, I know VZ can see it's not a true VS996. Thanks for the link to fix MMS, but I wanted to fix the lack of connection first before working on the other things.

I will try it again (maybe I swapped SIMs "too fast" for the VZ network to accept it or something?... though I swapped it back to the FIL's LG G3 with no issues... so very weird, and annoying).

All that said, we may just get them "true" VS996s instead, because that way they can still get help from VZ when they aren't nearby (they live in FL, while I'm in CT). It's not that VZ can't help, it's just that they won't... that's what pisses me off...

EDIT: Again, the question is, why isn't this phone connecting? It's seeing the phone number, sees the SIM fine, just wouldn't connect to the network and kept saying it wasn't registered... didn't know if there was a trick I could do or something to force it (probably not, as it may be a VZ-server thing, but who knows).
[LG V30 Questions & Answers] HueyT:
Try the Verizon secret menu and play around with the settings: *#*#4636#*#* or LG Secret Menu (must use stock LG dialer and not Google dialer): *#546368#*996#