Hello, I've owned a LG G7 G710ULM (US Unlocked) , and cross flashed to G710EM (EU Firmware)
Trying to modify this phone's modem to support carrier aggregation
Here's what I've modified:
/nv/item_ files/rfnv/00028874
added Taiwan operators ca combos
/policyman/carrier_policy.xml
added Taiwan ca combos strings
btw, found something strange
These values in /oem/OP/OPEN_EU/cust.prop
Code:
ro.vendor.lge.build.target_region=EU
ro.vendor.lge.build.target_operator=OPEN
ro.vendor.lge.build.target_country=EU
if I change these to:
Code:
ro.vendor.lge.build.target_region=ESA
ro.vendor.lge.build.target_operator=OPEN
ro.vendor.lge.build.target_country=TW
I can lock bands to 07 08, but can't do with original values
and QPST EFS Explorer Banner would be "DCM_Row"
So I tried to modified to OPEN/KR
Code:
ro.vendor.lge.build.target_region=KR
ro.vendor.lge.build.target_operator=KT
ro.vendor.lge.build.target_country=KR
QPST EFS Explorer Banner changed to "ROW"
It's so weired
Modified 28874, carrier_policy.xml, cust.prop and rebooted but still can't get carrier aggregation
Don't know how to insert uploaded images to thread, and sorry for my bad English
Hope someone would join this and discuss
Hey, interesting post. I have the same phone (LG G7 ULM) and I'm also interested in modifying CA combos but for LATAM.
Did you have to root to do all of this?
Related
Hi everyone.
The latest version of OOS 11.0.6.8 on the 8t EU seems to have enabled 5g in the settings / connection in France.
These network parameters are not yet available for the 8 pro.
As any luck is that a charitable soul could put me please a link drive or other of the two following files:
- carrier_policy.xml
- carrier_policy.xml_Subscription01
These two files can be found in the policyman folder using the qpst explorer.
These two files contain the operator parameters to activate 5g in particular.
I am in a 5g zone but these settings have not been activated for the 8 pro.
Thank you again for the one who will waste some of his time for this request
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.
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...
Can anyone extract and share their mbn files for this device? My Vivo X Note has the same Qualcomm SM8450 Snapdragon and since there is no mbn file for my carrier on this device I need to add the mbn for my carrier (Rogers, but any other carrier that support VoLTE will do) from the Galaxy 22 Ultra (for which my carrier supports VoLTE) in order to force VoLTE. With the shutdown of 3g networks in the United States VoLTE is necessary for voice calls.
I know it's possible but I'm not sure how to do it.
The Verizon modem file is loaded with coding to disable 5G, I know for a fact it has at least 2 methods to disable 5g, I found a way around those but still can't get it to connect to 5g but it sees the 5g is available. Which is the step in the right direction as stock mbn file with no mods results in the phone never seeing 5g as being available period.
So what I'm suggesting might work is swapping the Verizon modem mbn file with one from a phone that works on Verizon's 5G,like a s20 or similar or perhaps the Verizon's UW model also(heard the chipset needs to be the same on the device's)
Can anyone assist? Or point me in the right direction???
I think I have the same issue now. Verizon, I assume, somehow disabled the 5G functionality after some sort of update and I can't get it back. I use T - Mobile.
this may help https://forum.xda-developers.com/t/guide-fix-enable-5g-and-dss.4206461/ (look in other OnePlus phones like 10 or 8t )
After a bit of trial and error, I got 5G to work again on my device (IN2019). I had to replace the carrier_policy.xml files with another one from XDA in order to enable the network again.
@intheb0x Have you found a solution to this? I am interested in the same thing, I have a Korean S20 that does not have the info for North American/US NR5G bands. Other than software/firmware differences the Korean S20 is identical to the US versions, even the pit files are the same when examined with PIT Magic.
I've unpacked various modem images from XAA and TMB roms and then compared to Korean (KOO) roms and found the 549_10_0.mbn and 549_11_0.mbn to be missing a lot of data on the Korean roms. Looking at these files with a hex editor I can see that the US roms definitely have information regarding additional bands.
I have tried copying over the files and repacking the modem.img but the phone fails to load the files I copy. I believe this is because they are signed with a different signature than the Korean files.
I'm wondering if there is a way to disable signature verification on the modem files, maybe something like this?:
[Magisk MODULE] Patch SecureFolder - Disable Signature Verification - Flag Secure - Biometrics after reboot
SAMSUNG GENERAL PATCHER V2.2 SUPPORT: TELEGRAM CHANNEL - TELEGRAM GROUP - SUPPORT ME ABOUT THIS: Magisk module to automatically patch the services.jar of Samsung devices, based on Dynamic Installer The compatibility is relative but Android...
forum.xda-developers.com
I know I can edit the policy.xml with tools like QPST, EFS Explorer, QFIL but I have yet to find anywhere that I can load the additional info for these bands.
Any help would be much appreciated