Database Info

[Q] chat-ril and AT comand reference for MDM 6600 (Motorola Atrix 4G modem)

Hi,
can anyone tell me if you can use /system/bin/chat-ril to communicate with Motorola Atrix 4G modem?. The modem is MDM 6600 (I presume Qualcomm manufacturer). Manual page (or source code) would be great.
I need to send AT command to change frequency band form USA to EURO.
Also, If anyone has or can get the AT command reference for the MDM 6600 modem used in Motorola Atrix 4G?
This is a sample form logcat -b radio while setting USA radio band:
Code:
[5387]> QUERY_AVAILABLE_BAND_MODE
onReq: reqCode = 66, dataLen = 0
Ch4 > 5908AT+GRDE=10012,0,0,0
Read Ch4 << 5908+GRDE=10012,0,0,8,8001E80
[5387]< QUERY_AVAILABLE_BAND_MODE {2, 2}
[5388]> SET_BAND_MODE 2
onReq: reqCode = 65, dataLen = 4
Ch4 > 5909AT+SRDE=10012,0,0,8,0000A
Read Ch4 << 5909+SRDE=OK
[5388]< SET_BAND_MODE
What the hell is AT+GRDE ???

hi
i am also at the same point. i am in europe and selected usa gsm band. i am not able to use gsm. have you found something or any progress?

No, I haven't.
But, I this situation if you would have the AT&T SIM and account, you wouldn't be able to use your cell phone anywhere but in USA. The roaming wouldn't work.
This is just wrong!

gogy22 said:
No, I haven't.
But, I this situation if you would have the AT&T SIM and account, you wouldn't be able to use your cell phone anywhere but in USA. The roaming wouldn't work.
This is just wrong!
Click to expand...
Click to collapse
so there should be a solution.
how to update atrix firmware?

Same problem here...
We could try an "AT&F" to restore factory settings.
Not sure about the chat-ril syntax. Found the chat man page. Tried:
$ chat-ril '' 'AT&F'
[2] - Stopper (tty output) chat-ril "" AT
But does not seem to work. Is this the correct syntax ?

Cheshire Cat said:
Same problem here...
We could try an "AT&F" to restore factory settings.
Not sure about the chat-ril syntax. Found the chat man page. Tried:
$ chat-ril '' 'AT&F'
[2] - Stopper (tty output) chat-ril "" AT
But does not seem to work. Is this the correct syntax ?
Click to expand...
Click to collapse
Where did you find chat man page? Please share!

gogy22 said:
Where did you find chat man page? Please share!
Click to expand...
Click to collapse
If you are on UNIX, just type "man chat" on the console.
Otherwise search "chat man page" on the Internet (sorry, I'm not yet allowed to post links here ).

I've have managed to get GSM. I can make and receive call and 2G works, but not 3G. I don't know why... yet.
So, this is what I have done:
1. Boot Atrix holding the Volume Down key (Volume Up key is select so don't press it yet).
2. Select BP HW Bypass BP Only by pressing Volume Up key. There will be 5 new devices that Windows detects.
3. You will need MDM6600 Baseband drivers. The drivers I found are for Windows 7 x64 and they are not signed. So I needed to boot Windows (F8 key) with option "Disabe driver signature enforcement"
4. Then, you will need Qualcomm QPST or new QXDM. I used QPST 2.7 build 355.
5. Open QPST RF NV Item Manager. You need to select COM port assigned to MDM6600 Baseband Diagnostic Interface
I would suggest to be very careful with this tool since you can screw your phone beyond imagination. Just don't use any command that writes to phone.
6. select File -> Read form phone.
7. you need to find NV_BAND_PREF_I item. There should be 2 parameters NAM = 0 and BandPref = 0. At least I had those.
Just to remind, you do this at your own risk. My techincal skills are good, but not that good. I realy don't know what all the parametars mean. I did this and got GSM only. So think twice before you do this.
I would like to ask any of the developers to help on this matter. Now, if you feel lucky proceed with next step.
8. Before doing this read this whole thread! In BandPref enter 65535 or in hex FFFF and press button above "Write NV". The value FFFF should mean "Automatic band selection".
9. reboot the phone by removing the battery (don't know any other way)
The phone should register to network upon bootup.

Cheshire Cat said:
If you are on UNIX, just type "man chat" on the console.
Otherwise search "chat man page" on the Internet (sorry, I'm not yet allowed to post links here ).
Click to expand...
Click to collapse
I've gave up trying since if I manage to send AT commands to modem, I still don't know the AT command to send.

gogy22 said:
I've have managed to get GSM. I can make and receive call and 2G works, but not 3G. I don't know why... yet.
So, this is what I have done:
1. Boot Atrix holding the Volume Down key (Volume Up key is select so don't press it yet).
2. Select BP HW Bypass BP Only by pressing Volume Up key. There will be 5 new devices that Windows detects.
3. You will need Motorola USB drivers. The drivers I found are for Windows 7 x64 and they are not signed. So I needed to boot Windows (F8 key) with option "Disabe driver signature enforcement"
4. Then, you will need Qualcomm QPST or new QXDM. I used QPST 2.7 build 355.
5. Open QPST RF NV Item Manager. You need to select COM port assigned to MDM6600 Baseband Diagnostic Interface
I would suggest to be very careful with this tool since you can screw your phone beyond imagination. Just don't use any command that writes to phone.
6. select File -> Read form phone.
7. you need to find NV_BAND_PREF_I item. There should be 2 parameters NAM = 0 and BandPref = 0. At least I had those.
Just to remind, you do this at your own risk. My techincal skills are good, but not that good. I realy don't know what all the parametars mean. I did this and got GSM only. So think twice before you do this.
I would like to ask any of the developers to help on this matter. Now, if you feel lucky proceed with next step.
8. In BandPref enter 65535 or in hex FFFF and press button above "Write NV". The value FFFF should mean "Automatic band selection"
9. reboot the phone by removing the battery (don't know any other way)
The phone should register to network upon bootup.
Click to expand...
Click to collapse
Great job ! Have you tried forcing "CDMA only" ?
Same setup here, but can't get my Win7 systems (both 64 and 32 bit) to install the MSM6600 device drivers. Tried all Motorola drivers from 4.7 to 4.9 but none of the 5 devices are recognized.
Which drivers did you use ?

RESOLVED
Resolved flashing leaked firmware 1.5.2:
http://forum.xda-developers.com/showthread.php?t=991072
WARNING: Flashing 1.5.2 will restore the device to factory settings. BACKUP !

Cheshire Cat said:
Great job ! Have you tried forcing "CDMA only" ?
Same setup here, but can't get my Win7 systems (both 64 and 32 bit) to install the MSM6600 device drivers. Tried all Motorola drivers from 4.7 to 4.9 but none of the 5 devices are recognized.
Which drivers did you use ?
Click to expand...
Click to collapse
If you are still interested I'll try to find driver pack I've installed...
Cheshire Cat said:
Resolved flashing leaked firmware 1.5.2:
http://forum.xda-developers.com/showthread.php?t=991072
WARNING: Flashing 1.5.2 will restore the device to factory settings. BACKUP !
Click to expand...
Click to collapse
Regarding the firmware, couple of questions.
1. Are you in Europe? Does the 3G (UMTS/HSUPA/HSDPA) connection works?
I'm asking this because I have realized that the WCDMA I Band (2100 MHz) is not enabled, so the modem when searches the band automatically will not even include 2100 Mhz band.
2. When you uploaded the new firmware can you still boot Atrix to HW BP Bypass mode?
3. Can you get root with the new firmware?

gogy22 said:
If you are still interested I'll try to find driver pack I've installed...
Click to expand...
Click to collapse
Yes. Please let me know at least the driver version.
gogy22 said:
Regarding the firmware, couple of questions.
1. Are you in Europe? Does the 3G (UMTS/HSUPA/HSDPA) connection works?
I'm asking this because I have realized that the WCDMA I Band (2100 MHz) is not enabled, so the modem when searches the band automatically will not even include 2100 Mhz band.
Click to expand...
Click to collapse
I am in Europe.
- Dial: *#*#4636#*#*"
- Select: "Phone info"
- Select "GSM/CDMA (auto PRL)"
With this setting, my phone is currently displaying:
- Network type = UMTS
- Notification bar shows "H+"
- A few speed tests reach rx speed of about 4 Mbps, so it is definitely working
gogy22 said:
2. When you uploaded the new firmware can you still boot Atrix to HW BP Bypass mode?
Click to expand...
Click to collapse
Yes.
gogy22 said:
3. Can you get root with the new firmware?
Click to expand...
Click to collapse
Haven't tried yet.

Cheshire Cat said:
Yes. Please let me know at least the driver version.
Click to expand...
Click to collapse
Sorry, my bed. Actually, you need MDM6600 driver . Here you are. I have only x64. If you need x86 google it, I found these that way. Or tell me, I try to find where I got these.
Cheshire Cat said:
I am in Europe.
- Dial: *#*#4636#*#*"
- Select: "Phone info"
- Select "GSM/CDMA (auto PRL)"
Click to expand...
Click to collapse
This is the first thing I've tried, no luck. Which country are you in? Does your operator use WCDMA 2100 frequency or other?
Cheshire Cat said:
With this setting, my phone is currently displaying:
- Network type = UMTS
- Notification bar shows "H+"
- A few speed tests reach rx speed of about 4 Mbps, so it is definitely working
Click to expand...
Click to collapse
If its not a problem for you when you install the drivers can you send me your QCN file so I could compare with my values. You can use NV Item Manager to read from phone and write to file (sorry if I'm playing smart but I don't know you level of experience).

If anyone is interested, I managed to flash Atrix with OLYFR_U4_1.5.2_SIGNED SBF image. After the flash I have UMTS/HSDPA connectivity and the cell phone stayed unlocked.
I reviewed the modem configuration file .QCN files for both configurations. I seems the only difference is NV_BAND_PREF_I parameter.
With USA band selected it is:
NAM = 0 and BandPref = 0
And with the new flash image is:
NAM = 0 and BandPref = 384 (decimal, or 180 Hex)
( not the FFFF that I have stated before)

Gogy,
glad to know you have your Atrix working again.
Sorry for not getting back to you sooner.
My Atrix is gone. Dismissed. This phone is crawling with bugs and I am really becoming allergic to bugs due to very long daily exposure since I was a child...
Cheers.

Not pleased to hear that. Bugs? What bugs?
I didn't come accross any... yet, and I hope I won't.
Sent from my HTC Desire using XDA App

gogy22 said:
Not pleased to hear that. Bugs? What bugs?
I didn't come accross any... yet, and I hope I won't.
Click to expand...
Click to collapse
Lots of random issues.
Audio glitches, stuttering. Sudden resets when both cores are under stress. Reboot loops. Not powering up even if attached to the charger.Hot device even if apparently idle. Battery from 30% to 0% in 20 minutes. Buggy multimedia subsystem drivers. Cheap and noisy camera sensors.
All of the above also with stock firmware.
May well be hardware related, but really I don't want to find out.
Apart from issues, the user experience is crap: Motoblur lags behind competing products. Contacts images are not synced with Exchange servers. UI widgets are few and poorly designed. Mail and Calendar apps are a pain to use.
Google's crappy/broken/incomplete/poor Android API and the absurd choice of Java as the programming language have their responsibilities. But competing Android products do much better to work around these issues.
You asked me and I am just reporting my personal experience and opinion. YMMV.

motorola atrix 4g - usa band selected, no more euro service
currently living in the uk with an unlocked at&t motorola atrix 4g. accidently selected 'usa band' and have since not been able to locate service for any of the uk / european networks providers (eg, orange, o2, t-mobile) that were previously available.
i'm having a hard time deciphering whether or not this issue has been resolved:
1) has this issue been resolved by anyone as of yet? and if so,
2) can someone please provide clear step-by-step instructions, from start to finish, to demonstrate how to reach this resolution? i'm a bit of a layman
thank you all!

galthouse9 said:
1) has this issue been resolved by anyone as of yet? and if so,
Click to expand...
Click to collapse
Yes.
You just have to flash the non-official firmware 1.5.2 - ... at your own risk.
galthouse9 said:
2) can someone please provide clear step-by-step instructions, from start to finish, to demonstrate how to reach this resolution? i'm a bit of a layman
Click to expand...
Click to collapse
No problem.
This is the thread with the step-by-step instructions:
http://forum.xda-developers.com/showthread.php?t=991072
WARNING: Flashing 1.5.2 will restore the device to factory settings. BACKUP ALL YOUR IMPORTANT DATA !

Convert H990DS AME to AU and get VOLTE (Root)

Hi there,
First, my apologies for my English ( I am not English native speaker) anyhow,
Today I managed to change my LG V20 H990DS AME ( Middle east ) to AU (Australia).
And one of the bounces I got is VoLte icon (Still didn't confirm if it is actually working)
The procedure doesn't require to flash a new rom, all what you need to do is the following:
- go to the root and find the folder /CUST (Use any root explorer)
- Open "open_path_mapping.cfg" and "op_list.cfg"
- You will see AU and AME have unique values ( in my case 57 for AU and 71 for AME).
- in both files write AU value for AME and vice versa.
- do factory reset ( all AU APKs and frameworks will be installed automaticly instead of AME stuff).
- once your mobile opened, in initialization wizard, Australia will be the default country.
- You will find the VoLte in the hidden tiles.
I am still exploring new changes.
Wish you all the luck.
Regards...
Note:
- This is experimental procedure, do it on your own responsibility.
- You can backup all your apps and files using LG backup, and you can restore them once the procedure is done.
- Same procedure can be done to all LG V20 phones

Wouldn't it have been easier using KDZWriter?

This is only sn alternative way of doing it.
Moreover, KDZWriter didn't work in my case.

why do you need volte in middle east anyway ?
lg v20 h990ds here with latest gcc rom and mk2000 v1.5 kernel systemless root magisk xposed

sniper9911 said:
why do you need volte in middle east anyway ?
lg v20 h990ds here with latest gcc rom and mk2000 v.15 kernel systemless root magisk xposed
Click to expand...
Click to collapse
I don't understand the reason for this question, but the answer, because most of the mobile networks here support VoLTE.
H990DS for GCC doesn't support VoLTE.

yeah i know they support ... but what is the actual advantage ... i dont see it sorry
if you know what kind of applications for this volte service let me know

sniper9911 said:
yeah i know they support ... but what is the actual advantage ... i dont see it sorry
if you know what kind of applications for this volte service let me know
Click to expand...
Click to collapse
I assume that the OP is living in India, and an user of Reliance Jio. In case you don't know, that particular Indian carrier only has 4G bands, so if your phone doesn't support VoLTE, you won't be able to make calls at all on that carrier.....
Not without Jio's app I guess. But everyone seem to hate it.

phamanhvu01 said:
I assume that the OP is living in India, and an user of Reliance Jio. In case you don't know, that particular Indian carrier only has 4G bands, so if your phone doesn't support VoLTE, you won't be able to make calls at all on that carrier.....
Not without Jio's app I guess. But everyone seem to hate it.
Click to expand...
Click to collapse
wow ... why would they limit themselves for that band only .... thanks for the answer

sniper9911 said:
wow ... why would they limit themselves for that band only .... thanks for the answer
Click to expand...
Click to collapse
I dunno, cost-cutting I guess since Jio has some of the cheapest plan in Inida. You're welcome though.

Did it work for you?
T-Mobile US H990DS user here, I converted to ESA instead of AU and have not factory resetted (is it really necessary). I also edited my MCC and MNC into the config files for ESA and the icon does show up but IMS never connects.\
I posted further on this here:
https://forum.xda-developers.com/v20/development/enabling-ims-v20-h990ds-t3790486

p7810456 said:
Did it work for you?
T-Mobile US H990DS user here, I converted to ESA instead of AU and have not factory resetted (is it really necessary). I also edited my MCC and MNC into the config files for ESA and the icon does show up but IMS never connects.\
I posted further on this here:
https://forum.xda-developers.com/v20/development/enabling-ims-v20-h990ds-t3790486
Click to expand...
Click to collapse
Yes, it is required to do a factory resit, as e.g. some of AME apps are different than AU apps and those apps will be installed during first run after device format.
In your case the information only will be cganged, but not the apps as well.

MaZeNsMz said:
Yes, it is required to do a factory resit, as e.g. some of AME apps are different than AU apps and those apps will be installed during first run after device format.
In your case the information only will be cganged, but not the apps as well.
Click to expand...
Click to collapse
What partitions do I format and can I keep my internal storage if not my apps?

p7810456 said:
What partitions do I format and can I keep my internal storage if not my apps?
Click to expand...
Click to collapse
TO be hones I am not sure, please check yourself if formatting "Storage" partition is the one. Of course all your data will be deleted. So, in all cases back up all partitions using TWRIP and move your data to external io external flash before proceeding.
You may also use LG backup, to back up all apps and their data, so after formatting "Storage" you will be able to restore all apps and their data.
Please do a little search about this procedure.
Regards...

MaZeNsMz said:
Hi there,
First, my apologies for my English ( I am not English native speaker) anyhow,
Today I managed to change my LG V20 H990DS AME ( Middle east ) to AU (Australia).
And one of the bounces I got is VoLte icon (Still didn't confirm if it is actually working)
The procedure doesn't require to flash a new rom, all what you need to do is the following:
- go to the root and find the folder /CUST (Use any root explorer)
- Open "open_path_mapping.cfg" and "op_list.cfg"
- You will see AU and AME have unique values ( in my case 57 for AU and 71 for AME).
- in both files write AU value for AME and vice versa.
- do factory reset ( all AU APKs and frameworks will be installed automaticly instead of AME stuff).
- once your mobile opened, in initialization wizard, Australia will be the default country.
- You will find the VoLte in the hidden tiles.
I am still exploring new changes.
Wish you all the luck.
Regards...
Note:
- This is experimental procedure, do it on your own responsibility.
- You can backup all your apps and files using LG backup, and you can restore them once the procedure is done.
- Same procedure can be done to all LG V20 phones
Click to expand...
Click to collapse
Were you able to connect ?

p7810456 said:
Did it work for you?
T-Mobile US H990DS user here, I converted to ESA instead of AU and have not factory resetted (is it really necessary). I also edited my MCC and MNC into the config files for ESA and the icon does show up but IMS never connects.\
I posted further on this here:
https://forum.xda-developers.com/v20/development/enabling-ims-v20-h990ds-t3790486
Click to expand...
Click to collapse
nkirk said:
Were you able to connect ?
Click to expand...
Click to collapse
Connect to what ?!

MaZeNsMz said:
Connect to what ?!
Click to expand...
Click to collapse
Volte and make calls?

nkirk said:
Volte and make calls?
Click to expand...
Click to collapse
My cell number is from "Zain", in Zain they allow Wifi calling and VoLte for Iphones only. So I didn't test that.

MaZeNsMz said:
My cell number is from "Zain", in Zain they allow Wifi calling and VoLte for Iphones only. So I didn't test that.
Click to expand...
Click to collapse
Ok. Are you able to see the options in the call setting to enable advanced calling /Volte?

VoLte is not there, I found it only in the main sliding menu in the main screen.
https://ibb.co/jx6rFo

Ok. Sometime back I also managed to enable the hidden menu options (ims)with lots of XML edits in cust folder and a factory reset. But volte never connected. Also the options were not visible in call settings menu. I had to stop testing as this was my main device. Need to test more but the factory rest is keeping me from doing it.
Would you know any region which has VOLTE enabled by default for global carriers? I could try flashing the cus partition and see. Mine is sea. Only has official VOLTE enabled for SG and TW carriers.

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.

Magisk module need help testing for China and Korea users.

The firmware does not contain carrier files for China and Korea carriers.
I made a magisk module that installs these carrier files systemlessly.
I don't live in China or Korea so I have no way to test this.
If you're living in China or Korea, please help me test the module to see if it works.
Thanks.

Hi swangjang, thank you for sharing your module! I used QPST to replace the modified xml files to enable 5G, and now I installed your module. The 5G runs well, but I can't tell if it is enabled by your module.
For VoLTE, the switcher appeared in the option, but it dosen't work. When I made a phone call, the network drop to 3G. (My carrier is China unicom)

q.snake said:
Hi swangjang, thank you for sharing your module! I used QPST to replace the modified xml files to enable 5G, and now I installed your module. The 5G runs well, but I can't tell if it is enabled by your module.
For VoLTE, the switcher appeared in the option, but it dosen't work. When I made a phone call, the network drop to 3G. (My carrier is China unicom)
Click to expand...
Click to collapse
Thank you for testing.
I think due to dm-verity, the module files don't actually get placed in the system. I'll need to wait until we get TWRP to disable verity.
Can you try and change sim cards to force the phone to reload the mbn file?

swangjang said:
Thank you for testing.
I think due to dm-verity, the module files don't actually get placed in the system. I'll need to wait until we get TWRP to disable verity.
Can you try and change sim cards to force the phone to reload the mbn file?
Click to expand...
Click to collapse
I'll test it later.

q.snake said:
I'll test it later.
Click to expand...
Click to collapse
Tbh, I don't think it will work.
I plan to install a custom rom (custom roms don't have dm-verity) in the weekend and see if the module works on there. As long as dm-verity is enabled, I don't think any /system modifcation by magisk will work.

swangjang said:
The firmware does not contain carrier files for China and Korea carriers.
I made a magisk module that installs these carrier files systemlessly.
I don't live in China or Korea so I have no way to test this.
If you're living in China or Korea, please help me test the module to see if it works.
Thanks.
Click to expand...
Click to collapse
Hi, I live in south korea and I have UK version of Pixel 5(GTT9Q).
I'll try this module tonight and see if it works.
May I ask you where did you get mbn files for korean carrier? In my experience, KT and LGU need some efs modification especially for google pixel series, so directly injecting mbn from other device won't work well.

cdexswzaq said:
Hi, I live in south korea and I have UK version of Pixel 5(GTT9Q).
I'll try this module tonight and see if it works.
May I ask you where did you get mbn files for korean carrier? In my experience, KT and LGU need some efs modification especially for google pixel series, so directly injecting mbn from other device won't work well.
Click to expand...
Click to collapse
That attached module is very outdated. Please download from here:
GitHub - swangjang/Pixel-Redbull-Carrier-Patch: This is a Magisk module (in testing) for Pixel 4a (5G) and Pixel 5 that enables 5G for Unlisted Countries, VoLTE switches in the settings and add support for more countries/carriers.
This is a Magisk module (in testing) for Pixel 4a (5G) and Pixel 5 that enables 5G for Unlisted Countries, VoLTE switches in the settings and add support for more countries/carriers. - GitHub - swa...
github.com
I got the mbn files from Xiaomi Redmi K30. The K30 uses the same chipset as Pixel 5.

Just tested module in south korea, but it doesn't works.
It seems that magisk module is doing it's job. I run root explorer and confirmed that mbm_sw.txt and other additonal korea and china mbn successfully loaded.
But when I run efs explorer, Banner shows "SW_DEFAULT" instead of "LGU".
Maybe Pixel 5 can't load LGU mbn because of some other reason.

cdexswzaq said:
Just tested module in south korea, but it doesn't works.
It seems that magisk module is doing it's job. I run root explorer and confirmed that mbm_sw.txt and other additonal korea and china mbn successfully loaded.
But when I run efs explorer, Banner shows "SW_DEFAULT" instead of "LGU".
Maybe Pixel 5 can't load LGU mbn because of some other reason.
Click to expand...
Click to collapse
Thank you for testing. Did you install the A or B? could you try the other one as well to see if it works? Please make sure to uninstall first.
Also maybe take out sim card and insert again?

swangjang said:
Thank you for testing. Did you install the A or B? could you try the other one as well to see if it works? Please make sure to uninstall first.
Also maybe take out sim card and insert again?
Click to expand...
Click to collapse
I used A. and took out & changed sim card several times.
I'll check B tonight.

cdexswzaq said:
I used A. and took out & changed sim card several times.
I'll check B tonight.
Click to expand...
Click to collapse
I read on a Korean forum that you may need to visit your carrier customer centre to register your device
???ۺ????丮 [??????, ???÷???, ????? ?ؿ??? Ŀ?´?Ƽ] : ???̹? ī??
cafe.naver.com
Under section 3. part (4), "VoLTE calls can be made only by registering OMD (Open Model Device) as a VoLTE capable model name with each mobile operator".
Also, after installing the module, maybe reboot the device once?

swangjang said:
Thank you for testing.
I think due to dm-verity, the module files don't actually get placed in the system. I'll need to wait until we get TWRP to disable verity.
Can you try and change sim cards to force the phone to reload the mbn file?
Click to expand...
Click to collapse
Hi, I changed the SIM card of another carrier but the 5G is still enabled, even after I installed magisk completely and restore the original files with QPST, the 5G is still there...
I doubt that the new firewares (Feb and Mar updates) canceled the carrier limitation for 5G.

cdexswzaq said:
I used A. and took out & changed sim card several times.
I'll check B tonight.
Click to expand...
Click to collapse
Hi, I made more variations of the module using different mbn files for Korean carriers. Could you please them one at a time. It would be greatly appreciated.

I tried this with korean LGU, SKT simcard, but efs explorer shows SW_DEFAULT or Wildcard banner randomly.
I did sim tray out and in several times, and did WI-FI, Mobile Bluetooth reset on android settings-system menu.
And I also tried Taiwanese Chunghwa Telecom sim card which i got during taiwan travel, (Chunghwa Telecom is one of supported carrier for pixel 5) And It reports CHT banner correctly.
I don't know why, but it seems that pixel 5 refuses to load korean mbns for some reason.

cdexswzaq said:
I tried this with korean LGU, SKT simcard, but efs explorer shows SW_DEFAULT or Wildcard banner randomly.
I did sim tray out and in several times, and did WI-FI, Mobile Bluetooth reset on android settings-system menu.
And I also tried Taiwanese Chunghwa Telecom sim card which i got during taiwan travel, (Chunghwa Telecom is one of supported carrier for pixel 5) And It reports CHT banner correctly.
I don't know why, but it seems that pixel 5 refuses to load korean mbns for some reason.
Click to expand...
Click to collapse
Thank you.
So "pr-red", "nokia" and "mi9t" all not working for korean sim?

swangjang said:
Thank you.
So "pr-red", "nokia" and "mi9t" all not working for korean sim?
Click to expand...
Click to collapse
Yes, I tried all of 6 mbns, but no luck. All recognized as SW_DEFAULT or Wildcard banner.
I'm trying to figure out why only pixel rejects those mbns. Maybe there's some hidden policy to reject unsupported country's sim?

cdexswzaq said:
Yes, I tried all of 6 mbns, but no luck. All recognized as SW_DEFAULT or Wildcard banner.
I'm trying to figure out why only pixel rejects those mbns. Maybe there's some hidden policy to reject unsupported country's sim?
Click to expand...
Click to collapse
I don't think there would be something that will reject it. Other people reported they got VoLTE working for their 'unofficial' carrier.

Question Cross-Flashing Mi 11 Ultra (Snapdragon 888) - Lahaina Modem Image to ROG for more carriers compatibility ??

Hey Guys,
So along with my struggle of loading MBN files, I eventually used a Xiaomi Mi 11 Ultra (Global Edition) for a few days. This is another device that runs on the Same Snapdragon 888 SOC, and has the exact same Modem (Codename Lahaina). On the Mi 11 Ultra, Both my carriers have 5G / VoLTE working perfectly fine and had no issues whatsoever.
I opened up both the modem.img files (Can be viewed with 7Zip) and even the file structure is identical including the codenames, with the difference Xiaomi modem having more MBN files for many more carriers (I posted the MBN file extracted over here), (including the two MBN files my carriers use). On the other hand ASUS Modem.img has a very limited number of MBN files, which looks like they haven't updated it since the summer of 1969.
This is the Xiaomi Mi 11 Ultra Modem.img
File on MEGA
mega.nz
This is the ZS673KS (ROG 5) Modem.img
File on MEGA
mega.nz
Since there is no way to upload MBN files to the ROG 5 - Does anyone know whether we can fastboot flash the Modem image ?

Edl try

Akkaya34 said:
Edl try
Click to expand...
Click to collapse
Modem can be flashed over Fastboot.
Not required EDL.
But need to verify whether this has any risks. Only the chip (SOC) brand is same, but internally there might be other differences, and the image sizes are not the same either. So worried of hard brick.

BLOB images have the same code but very different interface to the kernel in most cases, so it's not likely anything will work

yurishouse said:
BLOB images have the same code but very different interface to the kernel in most cases, so it's not likely anything will work
Click to expand...
Click to collapse
Thanks a lot of the headsup !

Would the idea work better with rog 5 u.s modem blob?

Heero0101 said:
Would the idea work better with rog 5 u.s modem blob?
Click to expand...
Click to collapse
US version might have hardware differences .. So im not really sure.

Confirmed not working, restored partitions previously backed up for next surgical op.

katalinscrob said:
Confirmed not working, restored partitions previously backed up for next surgical op.
Click to expand...
Click to collapse
Thanks a lot for trying! Much appreciated!!

No pb! The main issue now that I have volte working along real 5G on both sim slots, is vowifi... PDC was the ideal method, but if sysprop vendor.usb.diag 1 command triggers correct diag mode, then for sure is another issue here, A11 related I guess...

katalinscrob said:
No pb! The main issue now that I have volte working along real 5G on both sim slots, is vowifi... PDC was the ideal method, but if sysprop vendor.usb.diag 1 command triggers correct diag mode, then for sure is another issue here, A11 related I guess...
Click to expand...
Click to collapse
How did you get VoLTE working?
Did you have the MBN inside already?
PDC is sadly blocked in A11 OS mode. However OnePlus Users They have a FTM mode - Which allows Efs tools / PDC to communicate. Hopefully something should come around for Asus.

You need root first of all.
There are 2 ways for permanent volte/vowifi toggle menus:
1. *#*#4636#*#*, set preffered network type NR/LTE, then back to original.
2. Magisk module Pixel5_VoWIFI.VoLTE_magisk_module_V1-MINI.zip (search github)
After this, via EfsTools method just copy to NV your carrier mbn from attached folder, reboot. Tried all of them until found compatible one from my carrier but no VoWIFI sadly.

katalinscrob said:
After this, via EfsTools method just copy to NV your carrier mbn from attached folder, reboot. Tried all of them until found compatible one from my carrier but no VoWIFI sadly.
Click to expand...
Click to collapse
Which thread did you follow?
I had a problem with my device not connecting via WIFI.

Full support 5G+VoLTE+VoWIFI:
1. Flash last A11 firmware WW-18.0840.2201.229 and root it.
2. Through QPST and AsusVOLTE apk, connect via wifi /same IP option ( I used IPV4+IPV6).
3. Download and unrar attached EfsTools, which contains the mcfg.mbn** and load it to NV.
4. Flash A12 firmware WW-31.0810.1226.57.
5. Root again, install voenabler*** module in magisk, restart.
**A11 banner mbn in .rar is for GermanyVodafone.
*** voenabler or any other method you agree with for enabling 4G/VOWIFI menus in settings.
In A12 banner is HW_DEFAULT instead any previous A11 carrier specific mbn, which means that ASUS finally resolved this problem for good.
Later edit: will try to extract and upload modem.img already modded for easy fix this entire stupid issue which Asus could have been more responsive to buyer's needs ...
Enjoy!

Since after .77 update lost again volte and vowifi, so disapointed... Respawned .mbn and voila, back in time with only volte capability, no vowifi.
Because I don't want to get through previous posted procedure, as I would be stuck in .57 basically, I found an alternative solution that could offer updates advantages and minimum-hassle procedure for regaining volte/vowifi, which basically is copying working mbn unpacked files to efs partition via efsExplorer in QPST. I tried mbn from an identical X60 qualcomm/lahaina chipset (found on xiaomi12t) and volte/vowifi working again, but no 5G this time. Anyway, is a matter of pacience and time for testing.
Another solution would be modifying modem.img extracted from Asus payload.bin but I didn't found an easy way to unpack/repack, only managed to open it through 7zip and get some resources. If you can find a solution to this, I think this would be the most elegant way for us to have all modem's capabilities activated, by simply restore modified-modem.img after every update.
And yes, tried AIK, various .img unpackers etc...