Related
So... here I will share 2 scripts I made to fix permissions for ViPER4Android running with enforced SELinux.
Why 2 scripts?
I like to keep everything open-source. Here I like to notice, Cyanogenmod is taking the wrong direction in my point of view. Every update takes out something of the customization possibilities of the user, so I am thinking of choosing new ROM. I faced real nightmare with SELinux permissions (well... SELinux is good, but Cyanogenmod doesn't provide any tool or way to manage those permissions). The more funny part is that with branch 13.0 of cyanogenmod there is no more init.d. Before someone corrects me - yeah... there is init.d, but SELinux blocks any script from executing at boot time, so don't use it. You will get your logs spammed by error messages. So... I've tried to enable init.d again, but there is no way to manage init.d to work as before. I've tried lots of different fixes from other posts, but nothing seems to work anymore, because of SELinux restrictions. I didn't managed to find any way to run scripts on boot time with root permissions in a suitable way... without messing with other system files or rebuilding build.img... so I came with those 2 solutions:
ViPER4Android (OpenSource) This is the solution I recommend to all of you. It is full open source. It doens't mess with you current system and it should work on any device/ROM. The zip file contains ViPER4Android app and driver, sepolicy-inject tool from setools-android so we can set permissions for ViPER4Android to work with enforced SELinux and Universal Init.d.
sepolicy-inject is open source equivalent to supolicy tool of Chainfire's SuperSU. I strongly recommend sepolicy-inject over supolicy, because every root closed source app should be threaten as security risk as the code can't be examined. I don't trust it esepcially when it is part of your android root manager
Universal init.d is just a application - it simulates init.d function. Imagine it like init.d on the user side... sadly enough you need to be pre-rooted to get it running.
ViPER4Android (Legacy) Maybe more of you will like this solution as it is more automated and it doesn't require any user action after installing the zip. This zip will do the same as the one above - it will install ViPER4Android removing all other DSP apps, but here come the difference - THIS SCRIPT WILL INSTALL CHAINFIRE'S SUPERSU in order to set SELinux policies for ViIPER4Android. Chainfire's SuperSU uses supolicy-tool - it let you manage SELinux policies on boot time. Chainfire's SuperSU will run everything in /system/su.d/ so again... you have init.d support - this is the real pain in the ass.
Before you download and flash, please read:
Both scripts WILL REMOVE other DSP apps from your device and will install ViPER4Android 2.4.0.1. I STRONGLY RECOMMEND TO USE SOLUTION 1 AS IT IS FULL OPEN SOURCE! Support open source software!!!
INSTRUCTIONS
ViPER4Android (OpenSource) - IN ORDER TO WORK, YOUR DEVICE MUST BE ROOTED! (Your device need to be rooted as Unversal Init.d needs root permissions in order to simulate init.d functionality)Download the .zip; Flash and reboot; Open Universal Init.d and grant root permission if asked; Reboot once more in case it don't work!
Sometimes Universal init.d is not fully initialized and needs some root permissions. That's why you need to reboot second time - then everything works. No further actions needed.
ViPER4Android (Legacy) - Just flash and reboot... but once more - SUPPORT OPEN SOURCE AND CHOOSE SOLUTION 1!!!!
For Samsung devices - if the scripts above doesn't work for you, check this post. Thx to Viper4713 for the instructions and voshchronos for solving the issue!!!
Hope to make someone happy
PS: If u want to make me happy with some beer, here you can donate a small amount. Thank you for your support.
Can i flash it on android one device running on 6.0.1
Yes. If you have any issues, please let me know!
rpangelov said:
Yes. If you have any issues, please let me know!
Click to expand...
Click to collapse
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
hiropandaz said:
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
Click to expand...
Click to collapse
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
rpangelov said:
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
Click to expand...
Click to collapse
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
hiropandaz said:
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
Click to expand...
Click to collapse
You are welcome! As I mentioned in the instructions - the legacy script will work always, but I don't like the implementation of it. I am working on new version of the opensource script, so there won't be any issues of that kind. When I am ready I will upload it here after updating my first post.
Greetz,
Angelov
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Primokorn said:
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Click to expand...
Click to collapse
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
rpangelov said:
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
Click to expand...
Click to collapse
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Primokorn said:
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Click to expand...
Click to collapse
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
rpangelov said:
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
Click to expand...
Click to collapse
I mentioned su.d because that's a solution with newer Android versions but I didn't say it's the best one. Using FLOSS softwares is a good move but you are using proprietary codes with CM.
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
trongtin64 said:
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
Click to expand...
Click to collapse
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
rpangelov said:
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
Click to expand...
Click to collapse
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
trongtin64 said:
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
Click to expand...
Click to collapse
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Primokorn said:
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Click to expand...
Click to collapse
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
trongtin64 said:
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
Click to expand...
Click to collapse
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Primokorn said:
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Click to expand...
Click to collapse
I'll use the one from my custom rom . Thank you for helping me :good:
It works great. thanks.
my bad for not following the instructions.
This is a flashable zip that enables init.d scripts to run depending on the root method you have installed.
To uninstall, just flash the zip again and it'll restore everything to how it was before
If magisk:
Boot scripts will be installed that will run all exectuable scripts in init.d as post-fs-data except any that end in '-ls' which will be run as late start. Also note that if you're trying to create the init.d folder, the original directory when using magisk is actually /sbin/.core/mirror/system/etc. It goes without saying that this could break safetynet (honestly though, just copy your script to /sbin/.core/img/.core/service.d or post-fs-data.d instead and set permissions to 0755 rather than creating an init.d directory - using the in-house magisk solution is always the better option. Magisk users have almost no reason to create an init.d directory)
The rest of this is for non-magisk/supersu installs
Otherwise: the boot img and part of the system will be modified to enable init.d support.
What it does:
Search for sysinit in any rc file. If found and seclabel is intact and equal to target seclabel for my init rc script, then that seclabel will be set to permissive in sepolicy if needbe instead of using my solution
If sysinit with seclabel isn't found, a custom rc file and system/bin/script file will be installed and sepolicy will be patched accordingly to add init.d support. Init.d scripts will be run the same way as with magisk installs above
Adds magiskpolicy to sbin. It's more up to date and complete than setools so why not?
If there is an error on unpacking your boot image, check the binary inclusion section here to see if your device needs one: https://github.com/osm0sis/AnyKernel3#-binary-inclusion
If it does, place it in addon/AnyKernel3/tools/arm (or x86 - whichever your architecture is - probably arm)
I am not responsible for any oddities that happen to your device because of this, use common sense. For example, if you know your device has a weird boot img, check first.
BACKUP BOOT AND SYSTEM PARTITIONS BEFORE FLASHING
Compatibility: Any device magisk is compatible with
Confirmed working (boot img method):
Nexus 5x
Verizon LG G2
Oneplus 3/3T
Oneplus 5T
Nexus 9
Redmi Note
Zuk Edge
Axon 7 (A2017U)
Nexus 5
SM-N900T
SM-T350
LeEco Pro 3
Confirm your device works and I'll add it to the list!
Special thanks to: @osm0sis, @CosmicDan, @Ricky Divjakovski, @JustArchi
Source: https://github.com/Zackptg5/Init.d-Injector
Download
Good stuff :good:
Good idea with the removal of other/old init.d capabilities. It's annoying that so many ROM's/kernels claim to have init.d but they're fake or hacky (well, I guess the sepolicy injection is pretty hacky too lol). You might also want to consider looking for install-recovery hijack method of init.d and disabling that too - shouldn't be too hard, just check if the file exists in known locations and grep for init.d. The harder part though is what to actually *do* if found - probably best to comment-out the line that contains "run-parts" and/or "init.d" rather than erase the whole file.
CosmicDan said:
Good stuff :good:
Good idea with the removal of other/old init.d capabilities. It's annoying that so many ROM's/kernels claim to have init.d but they're fake or hacky (well, I guess the sepolicy injection is pretty hacky too lol). You might also want to consider looking for install-recovery hijack method of init.d and disabling that too - shouldn't be too hard, just check if the file exists in known locations and grep for init.d. The harder part though is what to actually *do* if found - probably best to comment-out the line that contains "run-parts" and/or "init.d" rather than erase the whole file.
Click to expand...
Click to collapse
Good idea, I'll look into that. Thanks!
Will try this soon on Honor 8 Pro and report back.
Quick update to v1.1
Just bought a used nexus 9 and found that the boot partition layout for it and other nvidia tegra devices is different from typical android devices. So I added support for nvidia tegra devices
So github screwed with my EOL again and converted a few of the files to windows eol which broke everything. I just fixed it and reuploaded v1.1 with the fixes so just redownload it and flash away. Thanks to @dmgZero for finding the issue
Just updated to v1.2. I added support for pixels and nexus5x/6p avb-signing. I haven't been able to test it out myself as my bullhead doesn't even need signing to work so any feedback would be great. Also updated the OP on how to modify this for any weird boot imgs you may have
Edit: No point in spamming the thread with another post: updated to v1.3. Just adds capability to remove any init.d stuff present from install-recovery.sh. Thanks to @CosmicDan for pointing it out
Works fine on Redmi Note (a MediaTek Helio X20 device) running MIUI 9 (Android 6.0).
One tiny detail, maybe just do an mkdir /system/etc/init.d after the patch succeeds, if it doesn't already exist. I could imagine that some other zips could check for the existence of this folder for a simple way to determine if init.d is supported.
CosmicDan said:
Works fine on Redmi Note (a MediaTek Helio X20 device) running MIUI 9 (Android 6.0).
One tiny detail, maybe just do an mkdir /system/etc/init.d after the patch succeeds, if it doesn't already exist. I could imagine that some other zips could check for the existence of this folder for a simple way to determine if init.d is supported.
Click to expand...
Click to collapse
Sweet, I already have that in the sysinit script but it would make more sense to move that to the installer so I'll put that into the next version. Thanks!
Is that supposed to work systemlessly?
You should probably add Samsung to the weird/hexed/Satan kernels. Tried flashing your zip and recovery came back with Invalid Partition upon failure, my device is a Galaxy Note 5 running RR 7.1.2. I do love the idea and your work though bro. Thanks.
Metabolic12 said:
You should probably add Samsung to the weird/hexed/Satan kernels. Tried flashing your zip and recovery came back with Invalid Partition upon failure, my device is a Galaxy Note 5 running RR 7.1.2. I do love the idea and your work though bro. Thanks.
Click to expand...
Click to collapse
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
I completely understand, I wasn't gonna ask you to include my kernel regardless that's rather selfish, and I did follow your guide in the OP to get it to work. I was just suggesting maybe add Samsung kernels next to LG in your OP. Great work bro, thank you.
Zackptg5 said:
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
Click to expand...
Click to collapse
---------- Post added at 02:58 AM ---------- Previous post was at 02:51 AM ----------
I'm a retard, I read the OP wrong earlier. Disregard the adding Samsung part ha.
Zackptg5 said:
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
Click to expand...
Click to collapse
sscheib01 said:
Is that supposed to work systemlessly?
Click to expand...
Click to collapse
The boot img is not part of the system partition so that's systemless. However, it installs an addon.d script and modifies the sysinit and install_recovery files if present which are on the system. It won't break safetynet if that's what you're wondering
Zackptg5 said:
The boot img is not part of the system partition so that's systemless. However, it installs an addon.d script and modifies the sysinit and install_recovery files if present which are on the system. It won't break safetynet if that's what you're wondering
Click to expand...
Click to collapse
I thought *any* System modification trips the Safety net?
I use the Universal Safetynet Bypass module for Magisk so it doesn't bother me, but curious.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
I thought *any* System modification trips the Safety net?
I use the Universal Safetynet Bypass module for Magisk so it doesn't bother me, but curious.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
That's what I thought initially too but I've found lots of system modifications doesn't break safetynet such as editing the hosts file. Modifications to the zygote such as xposed framework for sure break safetynet but I'm not sure exactly which system modifications would. Other than testing them myself, I'm not really sure what would break it. I've found that you can completely alter parts of the system like with arise sound systems which adds a whole slew of libs and other modifications and safetynet still won't break (I found through my work there that having the system mounted as rw via a boot script will trigger safetynet but you can even go so far as to mount it as rw, make your changes, and then remount it as ro before boot completes and safetynet will still pass). It's weird man
Zackptg5 said:
That's what I thought initially too but I've found lots of system modifications doesn't break safetynet such as editing the hosts file. Modifications to the zygote such as xposed framework for sure break safetynet but I'm not sure exactly which system modifications would. Other than testing them myself, I'm not really sure what would break it. I've found that you can completely alter parts of the system like with arise sound systems which adds a whole slew of libs and other modifications and safetynet still won't break (I found through my work there that having the system mounted as rw via a boot script will trigger safetynet but you can even go so far as to mount it as rw, make your changes, and then remount it as ro before boot completes and safetynet will still pass). It's weird man
Click to expand...
Click to collapse
Kind of makes sense actually.
Hosts is in etc right, nothing in there is executable. So I imagine any changes to etc won't trip it because nothing in there would mess with device security. Sound mods... Well yeah they ADD libs but they don't replace any do they? They just add sound filters through the mixer configs in etc.
So I guess it makes sense. Sysinit is just added to xbin or whatever and I guess that doesn't trip it. But if you replaced, say, dex2oat with a proxy script to intercept oat generation, then it would definitely trip it.
Sent from my Redmi Note 4 using Tapatalk
Is it really needed??
I want to flash Dolby Atmos for Redmi Note 4, but init.d support is needed as mentioned by developer.
I tried Dolby Atmos without it sound is loud and great
I can't understand, why init.d is still needed?
Can anyone explain here?
amit.tiger12 said:
Is it really needed??
I want to flash Dolby Atmos for Redmi Note 4, but init.d support is needed as mentioned by developer.
I tried Dolby Atmos without it sound is loud and great
I can't understand, why init.d is still needed?
Can anyone explain here?
Click to expand...
Click to collapse
If it's working, then you don't need it or already have it. Init.d support is needed for Dolby if you are not using magisk or supersu and you have selinux set to enforcing
Zackptg5 said:
If it's working, then you don't need it or already have it. Init.d support is needed for Dolby if you are not using magisk or supersu and you have selinux set to enforcing
Click to expand...
Click to collapse
That's with respect to Dolby, what does it provide as a general point of view? What is it's significance?
Explain if you've enough time or just throw a link, it will help out.
[Mod announcement] This thread was closed due to a takedown request by author. You will find this module in the official Magisk repository and support channels can be found in the accompanied documents. Thank you for your interest and have a great stay on XDA.
Disclaimer: I will not be held responsible if your device stops working, catches fire and claims to have been modified before it was cool.
Description
Font Changer allows you to change the font on your Android device. (check the requirements section for more)
Requirements
root(magisk 20.0)
font changer(magisk modules)
terminal
busybox
custom recovery (not a requirement per-se, but highly recommended in case something goes wrong
install font changer modules once check active in magisk manager then reboot device
open terminal
#su
#font_changer(type in terminal)
would like to update the font list
Y/ n
select font
list downloadable fonts install and reboot
Supported ROM OS Version:
Q (Android 10) - OOS
@topjohnwu(magisk modules)
https://github.com/topjohnwu
Original author: @JohnFawkes
This sounds great, bu there's no link to the module....
docnok63 said:
This sounds great, bu there's no link to the module....
Click to expand...
Click to collapse
So you know you can search modules in Magisk Manager?
Not sure why you're didn't credit the creator @JohnFawkes....
TotallyAnxious said:
Not sure why you're didn't credit the creator @JohnFawkes....
Click to expand...
Click to collapse
Thanks..... Yea would be nice to be credited at least...... even say that the module is available officially in the magisk repo.......
docnok63 said:
This sounds great, bu there's no link to the module....
Click to expand...
Click to collapse
the module some time update or some Dev need to update that y not add to links one i share the experience bcoz many time serach android pei but not working on font so android working now android q i shared thank you
JohnFawkes said:
Thanks..... Yea would be nice to be credited at least...... even say that the module is available officially in the magisk repo.......
Click to expand...
Click to collapse
you know the reason thank buddy
george.simbu said:
the module some time update or some Dev need to update that y not add to links one i share the experience bcoz many time serach android pei but not working on font so android working now android q i shared thank you
Click to expand...
Click to collapse
i have no idea what your trying to say..... regardless i am the original creator and would really appreciate if you could at least credit me and say the module is available in magisk repo. or just read the readme file. or even just add my website. https://john-fawkes.com/Downloads/fontchanger.zip as the link
---------- Post added at 04:18 AM ---------- Previous post was at 03:52 AM ----------
george.simbu said:
you know the reason thank buddy
Click to expand...
Click to collapse
Please dont include the zip here......... this could cause issues in updates etc etc
JohnFawkes said:
i have no idea what your trying to say..... regardless i am the original creator and would really appreciate if you could at least credit me and say the module is available in magisk repo. or just read the readme file. or even just add my website. https://john-fawkes.com/Downloads/fontchanger.zip as the link
---------- Post added at 04:18 AM ---------- Previous post was at 03:52 AM ----------
Please dont include the zip here......... this could cause issues in updates etc etc
Click to expand...
Click to collapse
yes i add to credits thanks you buddy you have great work:angel:
george.simbu said:
yes i add to credits thanks you buddy you have great work:angel:
Click to expand...
Click to collapse
Thanks! I appreciate it! not sure if your in the telegram group but this is the message i posted there about FC earlier today
"ATTENTION ALL USERS!!!!!!!!
Im in the process of transfering my domain name john-fawkes.com to another provider! While this is happening EXPECT downtime in fontchanger! Downloading new folts/emojis will likely fail. fonts/emojis you already have in your fonts folder in fontchanger folder will still apply since the code checks for the font before it starts downloading it and if it exists already then it uses the on device one instead of downloading."
george.simbu said:
Disclaimer: I will not be held responsible if your device stops working, catches fire and claims to have been modified before it was cool.
Description
Font Changer allows you to change the font on your Android device. (check the requirements section for more)
Requirements
root(magisk 20.0)
font changer(magisk modules)
terminal
busybox
custom recovery (not a requirement per-se, but highly recommended in case something goes wrong
install font changer modules once check active in magisk manager then reboot device
open terminal
#su
#font_changer(type in terminal)
would like to update the font list
Y/ n
select font
list downloadable fonts install and reboot
Supported ROM OS Version:
Q (Android 10) - OOS
Credits
@JohnFawkes(font changer)
https://github.com/Magisk-Modules-Repo/Fontchanger/commits?author=JohnFawkes
@topjohnwu(magisk modules)
https://github.com/topjohnwu
you can download latest version on this
https://john-fawkes.com/Downloads/fontchanger.zip
Click to expand...
Click to collapse
Icon name in that ss ?
insaneparnoid said:
Icon name in that ss ?
Click to expand...
Click to collapse
linebit
I am getting this error while select rosemary font and also if i select any other font , the fonts dosent change for system , file i cant see fonts getting changed in my setting as posted in ss
insaneparnoid said:
I am getting this error while select rosemary font and also if i select any other font , the fonts dosent change for system , file i cant see fonts getting changed in my setting as posted in ss
Click to expand...
Click to collapse
"ATTENTION ALL USERS!!!!!!!!
Im in the process of transfering my domain name john-fawkes.com to another provider! While this is happening EXPECT downtime in fontchanger! Downloading new folts/emojis will likely fail. fonts/emojis you already have in your fonts folder in fontchanger folder will still apply since the code checks for the font before it starts downloading it and if it exists already then it uses the on device one instead of downloading."
george.simbu said:
"ATTENTION ALL USERS!!!!!!!!
Im in the process of transfering my domain name john-fawkes.com to another provider! While this is happening EXPECT downtime in fontchanger! Downloading new folts/emojis will likely fail. fonts/emojis you already have in your fonts folder in fontchanger folder will still apply since the code checks for the font before it starts downloading it and if it exists already then it uses the on device one instead of downloading."
Click to expand...
Click to collapse
just on more try and reboot you can change robotic to normal in font system settings
george.simbu said:
"ATTENTION ALL USERS!!!!!!!!
Im in the process of transfering my domain name john-fawkes.com to another provider! While this is happening EXPECT downtime in fontchanger! Downloading new folts/emojis will likely fail. fonts/emojis you already have in your fonts folder in fontchanger folder will still apply since the code checks for the font before it starts downloading it and if it exists already then it uses the on device one instead of downloading."
Click to expand...
Click to collapse
But fonts are getting downloaded, its giving copy error that it couldnt cp the downloaded font to destination , even if i move the required folder manually idk how to apply it
insaneparnoid said:
But fonts are getting downloaded, its giving copy error that it couldnt cp the downloaded font to destination , even if i move the required folder manually idk how to apply it
Click to expand...
Click to collapse
You need to download fonts copy to custom floder
connect to pc path: (Computer\GM1911\Internal shared storage\Fontchanger\Fonts\Custom)
or use root browser
and install custom font
Will this work on custom ROMs based on Android 10? Or is strictly for OOS?
sparky2029 said:
Will this work on custom ROMs based on Android 10? Or is strictly for OOS?
Click to expand...
Click to collapse
i am using oss only i tested
george.simbu said:
i am using oss only i tested
Click to expand...
Click to collapse
Okay thanks for the reply! Maybe I'll test it in a little bit and see if it works
Hi,
I am happy to share my Framework-res mod, specific for Oneplus 7 with Openbeta firmware.
My work includes the following changes:
- Disabled keyboard switcher notification
- Disabled high volume warning
- Enabled burnin protection
- Changed battery notification low level from 15% to 10%
- Enabled 360° rotation
- Reduced navigation bar height from 48dp to 41dp
It is a magisk module and I want to repeat that it can only be used on Oneplus 7 with Openbeta firmware
I'm trying it and it doesn't seem to show any problems but I still recommend making a backup before trying it.
To remove the mod, simply uninstall the module using magisk manager or, if this is not usable, from recovery twrp, using the file manager deleting the module "Framework-res mods" that you find at the following path:
/data/adb/modules
My big thanks go to @Tulsadiver, for giving me the right tips to be able to make the mod and for passing me the VRThemer module, without His help I would not have been able to avoid the bootloop
P.S. If you want the mod for other firmware versions, please send me your framework-res.apk and I will prepare the specific module.
If you want to try making the mod yourself, check out the tutorial here
Flashing always at your own risk!!!
20th March 2020 - Added OnePlus 7 OpenBeta 11 specific module
Thanks for your work, My kernel is Kirisakura-Kernel. Can I use it?
foolo said:
Thanks for your work, My kernel is Kirisakura-Kernel. Can I use it?
Click to expand...
Click to collapse
It works with any oxygenos based software (it doesn't work with AOSP rom) regardless of the kernel used
Could you pass me the framework-res.apk of the stable version? I would also like to prepare the specific mod for OxygenOS stable version.
Thank you.
Thanks. Worked perfectly.
Added OnePlus 7 OpenBeta 12 specific module to the first post
This is the framework-res.apk for the stable 10.3.1 oxygen os oneplus 7. Could you make a version for this too? I could help with the testing. Thank you!
(Uploading drive link cause xda doesn' t allow upload of apk more than 20MB.)
https://drive.google.com/file/d/1OagIggcj_WUKcuOYQKOsUNYaCQaA04Ev/view?usp=drivesdk
neildalal said:
This is the framework-res.apk for the stable 10.3.1 oxygen os oneplus 7. Could you make a version for this too? I could help with the testing. Thank you!
Click to expand...
Click to collapse
Done!
Added OnePlus 7 Oxygen OS Stable 10.3.1 specific module to the first post
dianoandr said:
Done!
Added OnePlus 7 Oxygen OS Stable 10.3.1 specific module to the first post
Click to expand...
Click to collapse
Just flashed via magisk and works perfectly fine!
Thank you!!
Added OnePlus 7 OpenBeta 13 specific module to the first post
Added OnePlus 7 OpenBeta 14 specific module to the first post
Added OnePlus 7 OpenBeta 15 module to the first post
dianoandr said:
Added OnePlus 7 OpenBeta 15 module to the first post
Click to expand...
Click to collapse
Thanks for u hard work .
Can you make mod for stable 10.0.6Gm57BA EU version?
M.Kader said:
Thanks for u hard work .
Can you make mod for stable 10.0.6Gm57BA EU version?
Click to expand...
Click to collapse
Sure it is possible!
I need the stock framework-res.apk from 10.0.6Gm57BA firmware, If You or Someone else who uses this firmware extracts it and sends it to me, I create the specific firmware magisk module
Added to the first post the module for OnePlus 7 OpenBeta 16 firmware.
Hi there @dianoandr
I have been trying to modify my OP7T framework-res apk to edit the vibe pattern which is contained under arrays.xml in values folder. However I haven't had any luck since I have always ended in a bootloop and needing to delete module. Could u help me out?
Thanks!
miguelang611 said:
Hi there @dianoandr
I have been trying to modify my OP7T framework-res apk to edit the vibe pattern which is contained under arrays.xml in values folder. However I haven't had any luck since I have always ended in a bootloop and needing to delete module. Could u help me out?
Thanks!
Click to expand...
Click to collapse
Hi @miguelang611,
Probably the bootloop occurs because you directly use the modified apk that is created by "apk tool", also I had this problem, try to use my module replacing the contents of the folder "vrtheme \ system \ framework \ framework-res.apk " with your modified files, extract the contents of your modified apk and copy in the magisk module everything EXCEPT for the meta-inf folder and the android-manifest file.
Try this and update me.
Regards!
dianoandr said:
Hi @miguelang611,
Probably the bootloop occurs because you directly use the modified apk that is created by "apk tool", also I had this problem, try to use my module replacing the contents of the folder "vrtheme \ system \ framework \ framework-res.apk " with your modified files, extract the contents of your modified apk and copy in the magisk module everything EXCEPT for the meta-inf folder and the android-manifest file.
Try this and update me.
Regards!
Click to expand...
Click to collapse
Thank u dude
The Friday after lot of tests reached to same conclusion as yours: copy everything from TMA (what I used to decompile) and once I removed the meta-inf and manifest, boom, it worked!
However, unfortunately I couldn't manage to edit vibration on arrays, since changing values there made 0 difference to actual phone vibration.
Saw that under public.xml there are also some vibe pattern, but neither worked
At least I got a way of fully modifying the framework and still booting
Thanks!
miguelang611 said:
Thank u dude
The Friday after lot of tests reached to same conclusion as yours: copy everything from TMA (what I used to decompile) and once I removed the meta-inf and manifest, boom, it worked!
However, unfortunately I couldn't manage to edit vibration on arrays, since changing values there made 0 difference to actual phone vibration.
Saw that under public.xml there are also some vibe pattern, but neither worked
At least I got a way of fully modifying the framework and still booting
Thanks!
Click to expand...
Click to collapse
No problem, it was a pleasure
If I make no mistakes, the vibration patterns are also determined by the kernel, but honestly, I never went into that.
Regards!
dianoandr said:
No problem, it was a pleasure
If I make no mistakes, the vibration patterns are also determined by the kernel, but honestly, I never went into that.
Regards!
Click to expand...
Click to collapse
With kernel y can change intensity, but I wanna change duration (just as clock, SMS or calls do)
Not found yet though, still looking for the way to go
Thanks again!
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.