Hello,
I want to try to include some change on vendor/build.prop in my magisk module, is that possible to do that?
If i try to put string on system.prop (resetprop), it'll write at build.prop not vendor/build.prop, how can i write into that file with magisk module?
Thank you...
Magisk's resetprop tool (that you use when you add stuff to the system.prop file in a module) does not write anything to the build.prop files, neither in /system or /vendor. They simply load new values over the stock ones. As long as you want to just load new prop values you don't have to bother with the files at all.
Related
Hello.
I know you can overwrite layouts, resources and other properties using an xposed module.
My question is - is it possible to write a module to alter an APK's manifest properties once it loads? (kinda like post-inflate hooks)?
Thanks
Theoretically yes, check PackageParser class or so..
I've installed magisk.
I need to modify /system/emui/base/xml/hw_clone_app_list.xml.
How to edit this file systemless with RootExplorer?
Just edit it, and it will be systemless ?
Or I should to modify the file in /sbin/.core/mirror/system/... ?
To modify it systemlessly you need to create a Magisk module that mounts your edited file over the original.
Instructions here:
https://github.com/topjohnwu/Magisk/blob/master/docs/modules.md
And in the module template:
https://github.com/topjohnwu/magisk-module-template
Didgeridoohan said:
To modify it systemlessly you need to create a Magisk module that mounts your edited file over the original.
Instructions here:
https://github.com/topjohnwu/Magisk/blob/master/docs/modules.md
And in the module template:
https://github.com/topjohnwu/magisk-module-template
Click to expand...
Click to collapse
OK, thanks.
So modify the file in /sbin/.core/mirror/system/ is not systemless?
dawnc said:
OK, thanks.
So modify the file in /sbin/.core/mirror/system/ is not systemless?
Click to expand...
Click to collapse
No worries, and no it's not.
dawnc said:
OK, thanks.
So modify the file in /sbin/.core/mirror/system/ is not systemless?
Click to expand...
Click to collapse
Hello,
You can create a magisk module that copy the specifiq file into your mod path, edit it using sed (for exemple), all theses steps could be done into post-fs-data stage, so at each phone boots.
Take the module template from the link of Didgeridoohan, and put necessary cmd lines into post-fs-data.sh file:good:
Why is it so hard to do such a system modification with Magisk... smh.
I'm trying to create a module where I need to replace a /system/priv-app/<filename>.apk with another one but it depends on the running Android version (API Level). Can this be scripted somehow with Magisk or would I need to create a module for each API Level I need/want to support?
You're on a roll today, aren't you?
What you're asking for is quite easy with a Magisk module. It's already implemented in the template:
https://github.com/topjohnwu/magisk...META-INF/com/google/android/update-binary#L62
You can place the different versions of the apk you want to use in the /common folder, name them accordingly, and then use the $API to install the correct one. Example:
Code:
cp $INSTALLER/common/apkname-$API.apk $MODPATH/system/priv-app/apknamefolder/apkname.apk
I just want to make sure I do this module correctly and don't break anything when sharing the module with everyone.
Should I just place the copy command directly in the "update-binary" file or create a "custom function" inside my config.sh and and call that inside "update-binary"? What's the recommended approach here?
I'd create a function in config.sh and call that inside update-binary. That way it'll be a lot easier for you to update to a new template further on.
Thank you
Hello to all!
Who can create a module for magisk that would allow to change the build.prop in the system folder "vendor"?
If you change something there manually, the settings are returned again after the phone is rebooted.
There is already a module.. MagiskHide Props Config..
I know that if I am going to substitute a file regardless of its original content, I only need to put the new file at
Code:
system/<directory to substitute>
However, I need to change a file which may vary between different devices.
In addition, my module may upgrade regularly. Is it possible to regenerate the file to modify and substitute from the original one instead of the previously modified one?
Use the module customize.sh (during install) or post-fs-data.sh (at every boot) scripts to grab the file you want from /sbin/.magisk/mirror. That's were all the original system files are mounted. Once you have it in your module directory you can edit it to your hearts delight.