Related
Hi all - my phone is a Star S5 MTK6589T 2gb RAM 1.5Ghz
Could someone be so kind to tell me, what I am missing out here...?
I have tried different custom roms, made for my mtk6589t. Some of them does not "support" my carrier or something like that, I have no carriers to choose from when I wan't to "select carrier manually"??? - It's just showing some numbers without carrier names, but my APN settings are as they should be...
All from working ROM:
So I have tried copy/pasting modem.img
Copy/paste the baseband file in the mddb folder (working baseband for me is : MOLY.WR8.W1248.MD.WG.MP.V7.P1, 2013/04/10 00:41)
Copy/paste all in the firmware folder
Flash Baseband recovery from SD
Nothing seems to work, even though I have compared contents of the mddb folder and firmware folder to be exactly the same, I can only find/choose my carrier in one of the roms???
I don't understand this,.. Both or several ROM's are made for the Star S5 MTK6589, but there is a difference in this for some - meaning me.
Are there something that I need to do different, for it to work?
How can I modify the ROM I wanna use, with info regarding carrerinfo/3G from the working ROM in order to get it to work?
I would really like to understand this...
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.
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...
Mod edit: Thread closed due to the below linked subject matter related thread! Oswald Boelcke, Senior Moderator
Hello everyone,
here's a magisk module which enables VoLTE & VoWiFi & 5G:
[MOD]MagiskModule - VoLTE & VoWifi & 5G in unsupported countries | Pixel 4a 5G & 5 & 5a
Introduction I would like to share a magisk module, which: - enables 5G, - enables VoLTE, - enables VoWiFi, - loads MBNs properly after loosing connection with network provider, - does not enforce 5G. Module is created by me, latest release...
forum.xda-developers.com
Old post(original)
Spoiler: OLD THREAD
I wanted to share my knowledge in single thread how to enable VoLTE and VoWiFi in unsupported countries
Requirements:
- Windows,
- ROOT via MAGISK,
- Around 30 minutes of free time.
Full guide is here.
GitHub - stanislawrogasik/Pixel5-VoLTE-VoWiFi
Contribute to stanislawrogasik/Pixel5-VoLTE-VoWiFi development by creating an account on GitHub.
github.com
YouTube video presenting how to do it:
I attach required files(as repo zip) with full README.
Vortuks said:
Hello everyone,
I wanted to share my knowledge in single thread how to enable VoLTE and VoWiFi in unsupported countries
Requirements:
- Windows,
- ROOT via MAGISK,
- Around 30 minutes of free time.
Full guide is here.
GitHub - stanislawrogasik/Pixel5-VoLTE-VoWiFi
Contribute to stanislawrogasik/Pixel5-VoLTE-VoWiFi development by creating an account on GitHub.
github.com
YouTube video presenting how to do it:
I attach required files(as repo zip) with full README.
Click to expand...
Click to collapse
First of all, thank you for the time and effort you put into creating this guide. It is really appreciated.
I have a few questions I need to ask, if I may:
1. What is the difference between your method and that other method on 4a 5G forum that says to just flash the magisk module? As I am currently running the second method I must say I do get 5g icon/speed and also volte/vowifi works ok where I live (Romania, Bucharest). However, I am aware I might be missing some features like 4G Carrier Aggregation (I think that is 4g+) and proper band allocation for 5G. Will your method unlock these too? Granted that I will need to use the correct mbn for my operator.
2. I read on your github description that the magisk module you mention changes some build.prop values. If I want to add/change more values besides the ones you mention, how can I achieve that? I have no technical knowledge on how to modify an existing magisk module..
3. If I am going to use your method, will it be required to repeat the qpst/efs steps each and every time I perform an OTA update?
4. Based of your method, how can I also unlock 5G access ? What additional files I need to edit in order to achieve this?
Hopefully you can provide some answers, for which I would be very grateful.
mightyvenom said:
First of all, thank you for the time and effort you put into creating this guide. It is really appreciated.
I have a few questions I need to ask, if I may:
1. What is the difference between your method and that other method on 4a 5G forum that says to just flash the magisk module? As I am currently running the second method I must say I do get 5g icon/speed and also volte/vowifi works ok where I live (Romania, Bucharest). However, I am aware I might be missing some features like 4G Carrier Aggregation (I think that is 4g+) and proper band allocation for 5G. Will your method unlock these too? Granted that I will need to use the correct mbn for my operator.
2. I read on your github description that the magisk module you mention changes some build.prop values. If I want to add/change more values besides the ones you mention, how can I achieve that? I have no technical knowledge on how to modify an existing magisk module..
3. If I am going to use your method, will it be required to repeat the qpst/efs steps each and every time I perform an OTA update?
4. Based of your method, how can I also unlock 5G access ? What additional files I need to edit in order to achieve this?
Hopefully you can provide some answers, for which I would be very grateful.
Click to expand...
Click to collapse
About the guide - no problem. I just want to share knowledge
1.) The difference is that I'm modyfing(in fact reseting) only the necesary props and adding selected MBN to the modem partition. Module mentioned "overwrites" the system MBN's, while I'm adding a new one directly to the modem. Also, this module modifies a lot of props and resets them to specified values - I'm doing only the necessary ones.
Currently my method doesn't unlock 5G - but also on the same page(4a 5G) they've used the same method.
I've just copied all the details into single guide, so everyone, who wants to have a working VoLTE and VoWiFi can use my guide without searching whole forum for posts etc.
I've tried to use this Magisk module, but it didn't work with my country(Poland) with my operator(Orange) - so I'm using this method. It should work on pretty much every Android version, while I can't guarantee that the mentioned module will.
2.) If you want to edit more props, you can add them to my module or create your own.
Developer Guides
The Magic Mask for Android
topjohnwu.github.io
Topjohnwu have a great guide how to do it and how to build your own magisk module.
3.) Yes, you need to do it after OTA, because OTA is updating modem partition and overwriting changes.
4.) I don't have access to 5G right now, but @Kars88 wrote it perfectly:
Module to enable 5G/VoLTE/VoWIFI on Pixel4a 5G/Pixel5
Update (9 Oct 2022): Upload module here. Update (7 Apr 2021): If you are looking for the manual way to add 5G support besides the magisk module way or the module does not work for you. Please refer to #54 for the detailed steps. Thanks again to...
forum.xda-developers.com
EDIT:
Btw. @mightyvenom Thanks for reminding me about that module, probably I'll create my own based on the one that you've mentioned - I just saw some new flags, that may be helpful with my research
Vortuks said:
About the guide - no problem. I just want to share knowledge
1.) The difference is that I'm modyfing(in fact reseting) only the necesary props and adding selected MBN to the modem partition. Module mentioned "overwrites" the system MBN's, while I'm adding a new one directly to the modem. Also, this module modifies a lot of props and resets them to specified values - I'm doing only the necessary ones.
Currently my method doesn't unlock 5G - but also on the same page(4a 5G) they've used the same method.
I've just copied all the details into single guide, so everyone, who wants to have a working VoLTE and VoWiFi can use my guide without searching whole forum for posts etc.
I've tried to use this Magisk module, but it didn't work with my country(Poland) with my operator(Orange) - so I'm using this method. It should work on pretty much every Android version, while I can't guarantee that the mentioned module will.
2.) If you want to edit more props, you can add them to my module or create your own.
Developer Guides
The Magic Mask for Android
topjohnwu.github.io
Topjohnwu have a great guide how to do it and how to build your own magisk module.
3.) Yes, you need to do it after OTA, because OTA is updating modem partition and overwriting changes.
4.) I don't have access to 5G right now, but @Kars88 wrote it perfectly:
Module to enable 5G/VoLTE/VoWIFI on Pixel4a 5G/Pixel5
Update (9 Oct 2022): Upload module here. Update (7 Apr 2021): If you are looking for the manual way to add 5G support besides the magisk module way or the module does not work for you. Please refer to #54 for the detailed steps. Thanks again to...
forum.xda-developers.com
EDIT:
Btw. @mightyvenom Thanks for reminding me about that module, probably I'll create my own based on the one that you've mentioned - I just saw some new flags, that may be helpful with my research
Click to expand...
Click to collapse
Thanks for your answers. I will try your method and compare the results with the initial solution I have found.
Let us know if you make any progress in changing the magisk module from the Pixel 4a 5G forum. I am particularly interested to achieve 4G CA more than 5G to be honest, maybe this is doable.
mightyvenom said:
Thanks for your answers. I will try your method and compare the results with the initial solution I have found.
Let us know if you make any progress in changing the magisk module from the Pixel 4a 5G forum. I am particularly interested to achieve 4G CA more than 5G to be honest, maybe this is doable.
Click to expand...
Click to collapse
@mightyvenom
It should enable CA(I guess), because you're essentially loading a proper MBN for your network provider - those files contains data about CA. At least in Poland it works.
nothing done on my side yet, when 2022.12 update will be out I'll try to create a proper Magisk module and share results.
@mightyvenom
if you want, you may test out this module.
It it unfinished, todo:
- fix path for MBNs,
- new github repo,
- test for 5G(need to retweak system.prop).
I've added two props:
persist.vendor.radio.mbn_load_flag=3
persist.vendor.radio.mbn_wait_s=60
I've flashed November Full IMAGE(without deleting data), applied Magisk, applied this module and I got VoLTE&VoWiFi (in IMS it is registered).
If you didn't the method with flashing through efsTools.exe it should enable you a VoLTE/WiFi.
I read here https://support.google.com/pixelphone/answer/12240791?hl=en that they have added volte support. But it seems like many people still do not have VoLTE. I am so confused.
I'm not sure, that done right, after your last post, but after placing latest module to magisk - nothing has changed. I see an option to enable volte/vowifi, but still no success with calling. After making a call it still switch to 3g/hsdpa. I'm on pixel 5 and tmobile (pl).
Is there still needed to create an mbn file with efstool?
Edit
I've solved with this thread https://forum.xda-developers.com/t/module-to-enable-5g-volte-vowifi-on-pixel4a-5g-pixel5.4207725/ just to let you know, for me works only applying magisk module . Really not sure why, because I haven't apply mbn file. But as you can see here - I can call over LTE and my phone is registered https://101010.pl/@inzaghi89/109661148495494919
I appreciate the work you've put in, but I'm finding the instructions a little unclear. Could someone please give another description of the process to follow? Thanks in advance.
Mctrixy said:
I appreciate the work you've put in, but I'm finding the instructions a little unclear. Could someone please give another description of the process to follow? Thanks in advance.
Click to expand...
Click to collapse
Go to this post:
[MOD]MagiskModule - VoLTE & VoWifi & 5G in unsupported countries | Pixel 4a 5G & 5 & 5a
Introduction I would like to share a magisk module, which: - enables 5G, - enables VoLTE, - enables VoWiFi, - loads MBNs properly after loosing connection with network provider, - does not enforce 5G. Module is created by me, latest release...
forum.xda-developers.com
It should work for you as this is Magisk Module only
its not working on my P5a using indonesian carrier telkomsel.