Related
Google in the update from Android KitKat to Android Lollipop has introduced a new type of restriction that blocks the execution of non-PIE binary.
This block mainly forces the user to copy the binaries he wants to run in /system/bin, /system/xbin, or in /sbin.
This restriction stops executing some apps (also app no-root), this Magisk module disable this restriction.
Who needs this module ?:
This modulr can be useful if you run the following statement while you are running a binary:
Error: only available independent executables (PIE) are supported.
How does the module work ?:
The operation is really simple, I checked the commit of the aosp source to identify the changes made to linker.cc responsible for the PIE restriction and I removed the part of code that blocks the execution of non-PIE binaries then it was enough to compile the linker and create a Magisk module with modified binaries.
Compatibility:
Android 7.1.X (probably also 7.0 but has not been tested)
Architectures: all
Flash in Magisk Manager or TWRP, NEEDED MAGISK 13.1 OR NEWER
The source for now is not available, will be released on the following days (Monday at maximum)
Working on Samsung Galaxy S7 edge nougat 7.0
Spartacus500 said:
Working on Samsung Galaxy S7 edge nougat 7.0
Click to expand...
Click to collapse
Did you try to run a non-PIE binary?
No, I did not try, I just installed the module.
ErnyTech said:
Did you try to run a non-PIE binary?
Click to expand...
Click to collapse
Hi! Small understanding info on my language on net. Its security restrictions for PIE added,removed by Google in different versions of Android. But in newer buidls his add this check,and any modern OS too have it. In two words tell me why i need bypass this sec.system(e.g disable security)? For exploits?
sorry,Eng is not my native lang.
zentao78 said:
Hi! Small understanding info on my language on net. Its security restrictions for PIE added,removed by Google in different versions of Android. But in newer buidls his add this check,and any modern OS too have it. In two words tell me why i need bypass this sec.system(e.g disable security)? For exploits?
sorry,Eng is not my native lang.
Click to expand...
Click to collapse
Unfortunately in some roms there are, for example, the Oxygen OS and sometimes also the Lineage. The mod need for users who have to run a binary but its execution is blocked by PIE verification, probably most of the users do not need
Yes may be most of the users don't need but thanks for your efforts
If I use this Magisk module, I cannot take any photo with my camera. Disabling this module, everything is ok again.
I have got a HTC One M8 with LineageOS 14.1.
Herbie_2005 said:
If I use this Magisk module, I cannot take any photo with my camera. Disabling this module, everything is ok again.
I have got a HTC One M8 with LineageOS 14.1.
Click to expand...
Click to collapse
Uhm what rom?
LineageOS 14.1 (CM 14.1)
is it will work on latest LineageOS 14.1??
Edit :: Yes.! it works ...but can u please make a zip for supersu user??it will be really helpful.
Does this work on stock Android 8.0?
I cannot pass the "Starting apps" if i use this module
Darkaxis said:
I cannot pass the "Starting apps" if i use this module
Click to expand...
Click to collapse
What rom you're using?
I started working on this almost 8 months ago. Originally (and possibly at some point in the future) my goal was to provide a slightly modified kernel from the source code Xiaomi releases on Github for MIUI that is modified to allow CN or other hardware to boot with the Global ROM and pass a SafetyNet check. Ultimately, I had given up on this endeavor because I was able to accomplish that using the Magisk module I created and posted here. Due to needing to have a device that was not rooted (running it for work with both personal and work SIM, and Airwatch detects Magisk no matter what I do), I came full circle.
Due to a design decision made by Google, I have found it is possible to make the androidboot.verifiedbootstate show up in a manner that is perceived by Google as "green" without triggering the bootloop code that is included in the system services that Xiaomi is running. To that end, I am posting an AnyKernel3 file here with the stock Global 10.3.2.0 ROM kernel, configured in such a manner as to bypass SafetyNet checks.
I only have one device to test this with, so hopefully it works for you too.
Edit: The patcher version should work on most versions of anything MIUI. It does not contain a kernel, it simply patches the CMDLINE to make it pass SafetyNet.
Standard Disclaimer: I have tested this, and it's a stock kernel, just with modifications to the kernel boot cmdline. I am not responsible if your device bursts into flames, fails to alarm clock and you are late for work, sends inflamatory SMS messages to Kim Jun Un, etc.
Patcher V2: Updated with AnyKernel3 changes:
Download V2
NOTE: I was not able to get my device to allow Google Pay with this. I believe Google is doing even more stringent checking now. If others want to test and report back, please do. This sets androidboot.verifiedbootstate=green now, and sets the ro.boot.hwc to GLOBAL and ro.boot.hwcountry to GLOBAL to avoid the bootloop in Xiaomi's services.
Generalized version:
Download Patcher
10.3.2.0 Specific:
Download
Edit: I was just messaged via Github by someone from Xiaomi that they are aware the source no longer works. They provided patches that *should* fix it. If that ends up working out, my intent is to provide a compiled from source version, possibly with some optimizations, and certainly using Linaro.
The patcher version linked above does not contain a kernel image. It just patches the cmdline and should work on all Xiaomi ROMS, atleast for the Mix 3. I have not tested it outside of the global ROM. I spent about 25 hours in the last two weeks working to try to backport the patches that were suggested as fixes to get the kernel to boot, but it is not done yet.
Updated Patcher above. I believe the new attestation api changes are stopping anything like this from working.
is it support miui 12 eu now ?
thx
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
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.
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.