Database Info

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.

unpack payload and images or root with rw permissions

hello to everyone​ i,m op8 os12 stock rom user and rooted as well
but i need to modify system few parts like build prop etc
i try many things to get rw access but failed
so there,s my first Q IS THIS POSSIBLE TO GET RW ACCESS IN OS12?
if possible then how? but incase its not possible then is this possible to unpack payload.bin
and modify system/vendor/product?
payload extracting is easy but is there any tool or kitchen which support these partitions unpack repack?

Why not just use a Magisk module?
Also, please make the font on your post more clear. The "black on gray" text is really cumbersome to read.

Xryphon said:
Why not just use a Magisk module?
Also, please make the font on your post more clear. The "black on gray" text is really cumbersome to read.
Click to expand...
Click to collapse
Hi thanks for time and showing your experience may i know which module you talk about and it'll be greatly appreciated if you pass the link
And sorry about font i create thread by pc in pc its looks very good
I'll edit tomorrow by pc

Mr Hassan said:
Hi thanks for time and showing your experience may i know which module you talk about and it'll be greatly appreciated if you pass the link
And sorry about font i create thread by pc in pc its looks very good
I'll edit tomorrow by pc
Click to expand...
Click to collapse
I believe an application is on the Play Store where you can edit your build. prop.
There's modules such as Pixelify that "change" your device into a Pixel.

Xryphon said:
I believe an application is on the Play Store where you can edit your build. prop.
There's modules such as Pixelify that "change" your device into a Pixel.
Click to expand...
Click to collapse
Bro build prop editing is easy once get rw
Ok I'm sure your talk about this module
[MAGISK] Pixelify
Pixelify Magisk Module A magisk module was created to make your android phone close to pixel devices. Current version - 2.2 So Features does this module provide? - Next Generation Assistant - Call Screening - Direct my call - Hold for me - Next...
forum.xda-developers.com
But still there's 2 thing's
1st this module just add few custom thing like boot animations etc not get rw
2nd in thread he already mentions oneplus os12 not support

Mr Hassan said:
Bro build prop editing is easy once get rw
Ok I'm sure your talk about this module
[MAGISK] Pixelify
Pixelify Magisk Module A magisk module was created to make your android phone close to pixel devices. Current version - 2.2 So Features does this module provide? - Next Generation Assistant - Call Screening - Direct my call - Hold for me - Next...
forum.xda-developers.com
But still there's 2 thing's
1st this module just add few custom thing like boot animations etc not get rw
2nd in thread he already mentions oneplus os12 not support
Click to expand...
Click to collapse
Oh. I had assumed you were on a custom ROM. It works best on there.

Xryphon said:
Oh. I had assumed you were on a custom ROM. It works best on there.
Click to expand...
Click to collapse
No no bro its stock rom

Question Is there anyway to run 32 bit apps?

I don't know if this is the right place to ask or if it already has been or not, but is there any possible way to get 32 bit apps to run in some type of compatibility mode or something like that? For the most part the majority of my old apps came over from my old phone, however there are some apps I have and used regularly which are not compatable with this phone and I am not sure if the developers are still active or not. I'm assuming the answer is no, or would require root if it were possible and rooting is out of the question for me because I have Verizon. I am expecting to be SOL but figured it was worth asking about here.

This question has been asked and discussed in length, try search

I will not be rude and the short answer is no. Apps on the play store had roughly 2 years to switch 64 bit. For s**ts and giggles I did try to do a search with zero results.

If the devs are still active and they havn't updated to 64bit by now then they are a lost cause.

No Google's heads up to devs gave them ample amounts of time to switch all their apps from 32bit over to 64bit. Tough shiz if the devs didn't take the arning seriously and switched their apps over whenthey had the cance to do so. I'm genuinely curious of 32bit compatibility is a concern and/or a necessity for you why you would buy a smartphone that doesn't support it? I really don't see how that makes much sense when you could have chose from a lot of other new flagships with 32bit support in tact.

Get a Galaxy S22 Ultra, Motorola Edge 30 Ultra or OnePlus 10 Pro. It's likely next year's flagships of any brand will be 64 bit only, so the forced shift is coming.

I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.
I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there would be a way around it but obviously not.

This might be of some help to run 32 bit apps you want:
GitHub - ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com

Interesting I will have to check this out

Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (
I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo.

VergeDX said:
Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (
I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo
Click to expand...
Click to collapse
Remove "stock' magisk
Install the patched magisk apk
Patch the stock init boot with the patched magisk apk
Flash the new patched init boot

on a clean install it works for me (beta: cheetah-t1b3.221003.008)

lunacies said:
I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.
I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there wld be a way around it but obvio
Click to expand...
Click to collapse
That's what I meant by and or sorry if me misinterpreting what you meant

bhammler said:
on a clean install it works for me (beta: cheetah-t1b3.221003.008)
Click to expand...
Click to collapse
I've compiled Magisk with the supplied patch from the repo and it isn't working for me. I've verified that the init does include the changes to override ro.zygote, however none of the Zygote processes start as the adb server never starts up, and well it doesn't boot.
Tested with the modified Magisk APK from the repo, same deal.
Strange that a clean install is necessary.

don't bother with a clean install, after I've installed some Mgaisk modules, I had a bootloop ;-)

It's nice to see there may be an option and I hope it works for everyone else. I am stuck with a Verizon phone so rooting is out of the question for me and I figured something like this would require root but hopefully other people are successful in getting it to work.

This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.

Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?
Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com

hahimot483 said:
Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?
Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
No as I discuss here.
Namelesswonder said:
Didn't sleep, I have gotten closer, but Magisk modules aren't going to be the solution.
The earliest Magisk allows you to modify properties is after the post-fs-data trigger, which is well inside the init.rc. This is problematic because the property needs to be set before init.rc is even read.
Using a Magisk module to replace the init.rc with something else also isn't possible, since Magisk doesn't setup the overlays until well into the boot process.
This replacing is necessary because init.zygote64_32.rc actually has the secondary zygote service disabled, so the file needs to be modified to enable it, or with control over init.rc just stuffing a custom zygote service into it.
I don't think slipstreaming a modified init.rc and init.zygote64_32.rc into the ramdisk in init_boot will work since they would be overwritten once the system partition mounts. Could just modify the system partition, but that'll be for another day.
Click to expand...
Click to collapse
Gerr1 said:
This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.
Click to expand...
Click to collapse
Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.

Namelesswonder said:
No as I discuss here.
Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.
Click to expand...
Click to collapse
Yes it works now with the new magisk Manager APK.

Replacing a modem mbn file

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

Android Security Update spoofing for Teams app

Hi All,
I'm opening this thread because I didn't find any info about my problem...
I have a couple of negative feelings with LineageOS 20 on my OP6 (okay, most of them are Android 13 specific not LOS20) and I decided to go back to the Stock OOS 11.
Unfortunately I have problem with the Stock ROM also because OP released the last Android Security Update for OP6 in 2021-NOV-1 and I want to use the Teams app on my phone but it needs Android Security Update from 2022-APR-15 and because of the outdated patch I'm not able to use it at all...
I was thinking on that maybe Magisk can help me in it to hide the real date of the security patch and "emulating/spoofing" a newer one to Teams app OR Android Faker trough LSposed/XPosed OR any other trick?
//Do you guys have any idea? (I've already tried to edit the " ro.build.version.security_patch" in build.prop but it didn't help and my phone went to bootloop (I'm absolute newby in editing the build.prop).)
Thank you in advance.
Best regards,
Peter

I don't know if build.prop spoofing is the way to go (these are just resulting infos, source is somewhere else, probably hard coded) but you must not modify build.prop because of dm-verity. better use magisk tools or magisk module
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com