Hi!
I just updated to latest Canary of Magisk(25210) and I just noticed AdAway stopped working. it says to reinstall the systems hosts file. when I make the attempt it fails silently.
is this happening to anyone else or is it just me?
Nope, not just you....I saw some bug posts in github so suspect there is a bug. I think you can wait for an update or possibly downgrade to 209. I think Ima just gonna wait a bit.
ok thanks! I'll wait as well.
DevilDaHusky said:
Hi!
I just updated to latest Canary of Magisk(25210) and I just noticed AdAway stopped working. it says to reinstall the systems hosts file. when I make the attempt it fails silently.
is this happening to anyone else or is it just me?
Click to expand...
Click to collapse
As cmh714 said...
Also, 25206 seems to be the last canary build without a "bug".
EDIT: I think 25209 may be ok.
25210 breaks module loading · Issue #6688 · topjohnwu/Magisk
Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...
github.com
Lughnasadh said:
As cmh714 said...
Also, 25206 seems to be the last canary build without a "bug".
25210 breaks module loading · Issue #6688 · topjohnwu/Magisk
Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...
github.com
Click to expand...
Click to collapse
thanks for the tip! I just so happen to have 25206 in my phone so I'll be reinstalling it.
edit: well nevermind that didn't work. it just autodownloaded the latest canary.
I'm using Magisk 25200 with zero issues🫠
25209 has no issues AFAIK
gpvecchi said:
25209 has no issues AFAIK
Click to expand...
Click to collapse
Worked perfectly for me until I updated
25208 works, too.
So I uninstalled 25210 apk. Installed 25208 apk downloaded previously. Opened Magisk 25208 and direct installed. Reboot.
Do not update the Magisk app until 25211 is released.
From Magiskokoro on the Telegram channel for Magisk:
"For anyone use official Canary Magisk, don't update to Magisk 25210, the module functions might not work.
Magisk Delta users won't be affect"
MArtyChubbs said:
25208 works, too.
So I uninstalled 25210 apk. Installed 25208 apk downloaded previously. Opened Magisk 25208 and direct installed. Reboot.
Do not update the Magisk app until 25211 is released.
Click to expand...
Click to collapse
25208 has issue hiding app.
How can I get 25209? Where do I get the older releases?
rester555 said:
How can I get 25209? Where do I get the older releases?
Click to expand...
Click to collapse
I think it is possible to find in the magisk-files repo,
Update Canary Channel: Upstream to 2717feac · topjohnwu/[email protected]
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com
i think this link is the 25209 apk: https://cdn.jsdelivr.net/gh/topjohn...8e568f9cc101eaf64bb5d9edb8a34/app-release.apk
larenhot said:
I think it is possible to find in the magisk-files repo,
Update Canary Channel: Upstream to 2717feac · topjohnwu/[email protected]
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com
i think this link is the 25209 apk: https://cdn.jsdelivr.net/gh/topjohn...8e568f9cc101eaf64bb5d9edb8a34/app-release.apk
Click to expand...
Click to collapse
It keeps forcing me to update the app to 25210
rester555 said:
It keeps forcing me to update the app to 25210
Click to expand...
Click to collapse
How is it actually forcing you? I've always seen it just prompting you to update app/magisk.
krakout said:
How is it actually forcing you? I've always seen it just prompting you to update app/magisk.
Click to expand...
Click to collapse
I ended up uninstalling the whole thing. I deprecated to 25206 and 25209... After installing both of those, I am still having an issue with systemless hosts installing and AdAway playing nice. I still get the error
Same issue but I am waiting for an official magisk update. Maybe today or tomorrow...
I wonder if this persists with a removal of -w with a new image. I would hate to have to wipe the whole phone to fix this issue.
rester555 said:
I wonder if this persists with a removal of -w with a new image. I would hate to have to wipe the whole phone to fix this issue.
Click to expand...
Click to collapse
This is a Magisk issue and not an Android 13 issue. So, you wouldn't need to wipe your phone if you had upgraded your Magisk app and flashed the updated, patched init_boot file. You will just need to upgrade the Magisk app to the 25211 build, patch another stock init_boot.img and flash that newly patched init_boot.img.
If you check on the Magisk GitHub page, the error was pointed out and resolved. In one of the changes, a programmer set the command to make a directory AFTER a command that makes that location privatized (and thus, the directory cannot be created). It was supposed to be the other way around.
NippleSauce said:
This is a Magisk issue and not an Android 13 issue. So, you wouldn't need to wipe your phone if you had upgraded your Magisk app and flashed the updated, patched init_boot file. You will just need to upgrade the Magisk app to the 25211 build, patch another stock init_boot.img and flash that newly patched init_boot.img.
If you check on the Magisk GitHub page, the error was pointed out and resolved. In one of the changes, a programmer set the command to make a directory AFTER a command that makes that location privatized (and thus, the directory cannot be created). It was supposed to be the other way around.
Click to expand...
Click to collapse
I understand this... I don't see 25211.
Related
Hi,
I don't know since when this error occurs, but I am not able to add or remove set fingerprints.
When trying to add one, I get the error that it hasn't been saved.
Why I tapping 'delete' after choosing one simply
nothing at all happens.
I bet this is some problem with permissions.
Anyone having an idea how to fix it?
I don't want to wipe my phone again...
I am using Emui 5 on B389 firmware (FRD-L09) with unlocked BL and magisk as root manager.
@hackslash
Try disabling Magisk Hide (go to Magisk Manager > Settings) and reboot the device.
That fixed it for me, thanks!
masterxxxxxl said:
That fixed it for me, thanks!
Click to expand...
Click to collapse
This means you're using an old version of Magisk. Try installing the latest Magisk Manager and Magisk systemless zip file since the issue is not present in latest releases.
hackslash said:
This means you're using an old version of Magisk. Try installing the latest Magisk Manager and Magisk systemless zip file since the issue is not present in latest releases.
Click to expand...
Click to collapse
Cool. That may be a life saver for many once they know what the issue is actually. Thanks for sharing info mate.
I'm on latest Firmware Rooted Using Magisk. Safety net failure even after Trying every fix modules hide options and what not. Kindly help.
It appears to be an issue with the newest release of the Magisk (the patch, not the app).
I can confirm mine was passing until installing an update to Magisk. After booting, it failed with or without the fix.
Found a fix on a telegram page, give full credits to modulesrepo and TeamFiles for finding this method.
-- Open Magisk and Flash Riru Core, But do not reboot.
-- Go back and flash Lsposed in magisk & reboot your device.
-- Now install XPrivacyLua apk
-- Open Lsposed and go to modules section and choose XPrivacyLua from there.
-- Select system framework, Settings storage and Google Play services there.(Uncheck the system apps from hide section settings for Play services to show up)
-- Reboot your device
-- Open XPrivacyLua and search google play services, click drop down menu in left of play services and tick 'use tracking' as shown in the screenshot.
-- Tick 'use tracking' on banking apps too and clear data of them after ticking
-- Now clear play services and play store data through your phone's settings.
-- Hide magisk and change name of magisk
-- Your Safetynet Should Pass Now!
Came across that a few days ago, but it seemed excessive.
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
Madbullben said:
Found a fix on a telegram page, give full credits to modulesrepo and TeamFiles for finding this method.
-- Open Magisk and Flash Riru Core, But do not reboot.
-- Go back and flash Lsposed in magisk & reboot your device.
-- Now install XPrivacyLua apk
-- Open Lsposed and go to modules section and choose XPrivacyLua from there.
-- Select system framework, Settings storage and Google Play services there.(Uncheck the system apps from hide section settings for Play services to show up)
-- Reboot your device
-- Open XPrivacyLua and search google play services, click drop down menu in left of play services and tick 'use tracking' as shown in the screenshot.
-- Tick 'use tracking' on banking apps too and clear data of them after ticking
-- Now clear play services and play store data through your phone's settings.
-- Hide magisk and change name of magisk
-- Your Safetynet Should Pass Now!
Click to expand...
Click to collapse
Thanks a lot, But thats a lot of modules for a phone without TWRP right now ....
I kept getting a failure error as well but now it's all good follow the instructions and links from this video. You don't have to follow the entire instructions you can skip to the part for the magisk safety net module and info
Now clear play services and play store data through your phone's settings ? how to do it ?
Deleted, posted in wrong thread, oops
Madbullben said:
Thanks! Really appreciated that you did this! The new chat bubbles are a good idea in theory but they are so bad and so much worse than the old chat heads and it was driving me crazy with the new chat bubble so this is amazing!
Click to expand...
Click to collapse
Did you make a wrong turn?
Did the fix. Safety net passes, Hulu and Disney+ work, but not Netflix
edit: got it working. restarting the first time didn't fix it, but the 2nd time did for some reason.
TiklMiPickles said:
Did the fix. Safety net passes, Hulu and Disney+ work, but not Netflix
edit: got it working. restarting the first time didn't fix it, but the 2nd time did for some reason.
Click to expand...
Click to collapse
Which one worked ?
Post #3 - The list or the video in Post #6 ?
JazonX said:
Which one worked ?
Post #3 - The list or the video in Post #6 ?
Click to expand...
Click to collapse
The video redirects to the latest canary build, so that is going to be broken.
twistedumbrella said:
The video redirects to the latest canary build, so that is going to be broken.
Click to expand...
Click to collapse
Loud and clear.
If no other option comes up, I will go with the guide with Riru.
It's a huge risk tbh, because ROG 5 doesn't have TWRP yet to revert if anything goes bad.
JazonX said:
Loud and clear.
If no other option comes up, I will go with the guide with Riru.
It's a huge risk tbh, because ROG 5 doesn't have TWRP yet to revert if anything goes bad.
Click to expand...
Click to collapse
Yeah. I'm waiting on the module to work. It's been converted to Riru, but both beta and canary builds of Magisk still fail. I haven't tested the stable one.
The one in the video works fine for me tho. Didn't work at first but for whatever magic reasons everything was fine after some restarts
twistedumbrella said:
Yeah. I'm waiting on the module to work. It's been converted to Riru, but both beta and canary builds of Magisk still fail. I haven't tested the stable one.
Click to expand...
Click to collapse
Just checked his github, sadly the latest version 2.1.0 seems to fix the issue - But it's a paid mod now.
Github has only 2.0.0 where the CTS still fails.
JazonX said:
Just checked his github, sadly the latest version 2.1.0 seems to fix the issue - But it's a paid mod now.
Github has only 2.0.0 where the CTS still fails.
Click to expand...
Click to collapse
It's not a paid mod. Only early access is paid - just wait until the developer releases it via github
twistedumbrella said:
Did you make a wrong turn?
Click to expand...
Click to collapse
Yep oops sorry about that
twistedumbrella said:
Yeah. I'm waiting on the module to work. It's been converted to Riru, but both beta and canary builds of Magisk still fail. I haven't tested the stable one.
Click to expand...
Click to collapse
As we don't have twrp, if something does fail can't we just use fastboot and flash the device again?
Madbullben said:
As we don't have twrp, if something does fail can't we just use fastboot and flash the device again?
Click to expand...
Click to collapse
Raw firmware can fix almost anything. Factory reset can fix the rest.
I don't know what i did wrong. Every rom i tried which had already passed safety net wasn't passing safety net. Now i installed elixir A12 rom and the safety net is still not passing even after magisk hide.
I followed every step carefully. Installed magisk with patched boot.img method and still to no use.
Dont install magisk and it will pass.
k3lcior said:
Dont install magisk and it will pass.
Click to expand...
Click to collapse
its failing regardless of having magisk installed or not! idk whats wrong here. is it a boot file problem or what
Well i can guarantee you ArrowOS 11 and 12 passes safetynet without Magisk, dont know about Elixir.
PixelExperience and PixelExperience Plus pass safetynet without magisk. Dont know how with magisk because i dont use
k3lcior said:
Well i can guarantee you ArrowOS 11 and 12 passes safetynet without Magisk, dont know about Elixir.
Click to expand...
Click to collapse
tried arrowOS. i love pixel goodies. idk why i didnt like it. i'll try arrow12.
lsander said:
PixelExperience and PixelExperience Plus pass safetynet without magisk. Dont know how with magisk because i dont use
Click to expand...
Click to collapse
i'll check with them. whats the diffrence between PixelExperience/PixelExperience Plus?
the only reason i am using elixer is because of pixel android 12 goodies. but this safety net update keeps failing!
i even followed this video but to no use
I dont know what is the difference. I just saw that plus version has much more downloads so took this one. You can find in google the difference. I also wait for a12 but pixel experience rom. Dont like arrow.
From what i saw in arrow os rom a12 it passes safetynet without magisk and additional tweaks
If you have installed Magisk and safetynet does not pass the test, install Magisk modules: Riru and safetynet fix. Should help
Spoiler: Modules
use magisk alpha
download it from their telegram
Lu5ck said:
use magisk alpha
download it from their telegram
Click to expand...
Click to collapse
did it work for you?
tried every method i could read on prop's github and tried safety-net fix universal but i am unable to pass safety net on Android 12(elixir build).
the author says it passes by default but it does not! i don't think i have done any step wrong.
the procedure i followed is:
unlock bootloader on 12.5.5 official build.
root device with magisk and did magisk hide.(passes cts profile)
download elixer Android 12 zip.
install zip
format data+dalvik+cache
boot to rom.
download magisk
patch boot.img of elixir rom because the rom is not rooted!
boots into rom and do magisk hide
check safety net
basic integrity passes
cts profile match failed
not sure what i am doing rom???
saudahmedbass said:
tried every method i could read on prop's github and tried safety-net fix universal but i am unable to pass safety net on Android 12(elixir build).
the author says it passes by default but it does not! i don't think i have done any step wrong.
the procedure i followed is:
unlock bootloader on 12.5.5 official build.
root device with magisk and did magisk hide.(passes cts profile)
download elixer Android 12 zip.
install zip
format data+dalvik+cache
boot to rom.
download magisk
patch boot.img of elixir rom because the rom is not rooted!
boots into rom and do magisk hide
check safety net
basic integrity passes
cts profile match failed
not sure what i am doing rom???
Click to expand...
Click to collapse
Aythor said it passes by default because it is patched to pass without root. If you install magisk then it may not pass. Try to use clean rom without magisk and check if it passes.
saudahmedbass said:
did it work for you?
Click to expand...
Click to collapse
i am not using a12 but from what i saw in the telegram, others seem to report positively about it
furthermore, magisk alpha is many many commits ahead of the official v23
v23 pretty much is outdated
lsander said:
Aythor said it passes by default because it is patched to pass without root. If you install magisk then it may not pass. Try to use clean rom without magisk and check if it passes.
Click to expand...
Click to collapse
yeap it passes before magisk. and now i know whats the reason. thankyou for shedding light!
Lu5ck said:
i am not using a12 but from what i saw in the telegram, others seem to report positively about it
furthermore, magisk alpha is many many commits ahead of the official v23
v23 pretty much is outdated
Click to expand...
Click to collapse
true. i just read magisk canary documentationa and comments section of the blog post. it seems the magisk developer was hired by google to remove magisk hide from magisk-canary and the support on Android 12 won't have magisk hide but zygisk-module which is left as a tempelate for developers to create onto. this means safety-net will fail on Android 12
i know magisk v23 works on Android 12 but it will start failing once the vendors updates their apps!
saudahmedbass said:
yeap it passes before magisk. and now i know whats the reason. thankyou for shedding light!
true. i just read magisk canary documentationa and comments section of the blog post. it seems the magisk developer was hired by google to remove magisk hide from magisk-canary and the support on Android 12 won't have magisk hide but zygisk-module which is left as a tempelate for developers to create onto. this means safety-net will fail on Android 12
i know magisk v23 works on Android 12 but it will start failing once the vendors updates their apps!
Click to expand...
Click to collapse
Just try magisk alpha, not canary
Lu5ck said:
Just try magisk alpha, not canary
Click to expand...
Click to collapse
if i am not wrong canary / nightly / alpha / dev are the same? or if its not same can you link the download to alpha build?
saudahmedbass said:
if i am not wrong canary / nightly / alpha / dev are the same? or if its not same can you link the download to alpha build?
View attachment 5458809
Click to expand...
Click to collapse
Magisk Alpha is maintained by vvb2060, people who prefer magiskhide use it
Magisk Canary is basically the official test version without magiskhide, using the new zygisk denylist
Source code
GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly
A Magic Mask to Alter Android System Systemless-ly - GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly
github.com
Release
Magisk alpha
带遥测的第三方Magisk版本,比Canary通道更加不稳定,与上游行为有较大不同,无安全性保证,无可用性保证,无隐私协议。 问题反馈请加群发送日志文件,非alpha独有问题建议先在GitHub反馈。
t.me
saudahmedbass said:
yeap it passes before magisk. and now i know whats the reason. thankyou for shedding light!
Click to expand...
Click to collapse
I told you this in a second post..
Lu5ck said:
Magisk Alpha is maintained by vvb2060, people who prefer magiskhide use it
Magisk Canary is basically the official test version without magiskhide, using the new zygisk denylist
Source code
GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly
A Magic Mask to Alter Android System Systemless-ly - GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly
github.com
Release
Magisk alpha
带遥测的第三方Magisk版本,比Canary通道更加不稳定,与上游行为有较大不同,无安全性保证,无可用性保证,无隐私协议。 问题反馈请加群发送日志文件,非alpha独有问题建议先在GitHub反馈。
t.me
Click to expand...
Click to collapse
i will need the apk unfortunately. i am unable to access telegram in my country due to ban! (
saudahmedbass said:
i will need the apk unfortunately. i am unable to access telegram in my country due to ban! (
Click to expand...
Click to collapse
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
A magisk module to be able to downgrade apps. I don’t want to use lsposed.
Arealhooman said:
A magisk module to be able to downgrade apps. I don’t want to sue lsposed.
Click to expand...
Click to collapse
What do you mean "downgrade apps", and how exactly do you think you're going to take legal action against a not for profit open development project that you use at your own risk?
V0latyle said:
What do you mean "downgrade apps", and how exactly do you think you're going to take legal action against a not for profit open development project that you use at your own risk?
Click to expand...
Click to collapse
What tf do you mean? What legal action?
OH LMAO I meant to say use not “sue”. My mistake.
V0latyle said:
What do you mean "downgrade apps", and how exactly do you think you're going to take legal action against a not for profit open development project that you use at your own risk?
Click to expand...
Click to collapse
i mean a module like “Let Me Downgrade”. Like from version 10 to version 9.
Arealhooman said:
i mean a module like “Let Me Downgrade”. Like from version 10 to version 9.
Click to expand...
Click to collapse
I'm still not sure what you mean. Are you saying you want to use Android 9 apps on Android 10? The apps should be the same, more or less, although it's up to the app developers as to what versions and platforms they support. You can typically find older versions on Apkmirror.
V0latyle said:
I'm still not sure what you mean. Are you saying you want to use Android 9 apps on Android 10? The apps should be the same, more or less, although it's up to the app developers as to what versions and platforms they support. You can typically find older versions on Apkmirror.
Click to expand...
Click to collapse
No, are you familiar with the “Let Me Downgrade” module? If I have the official YouTube app, and it’s on version 36.8.34 and I want that same exact app to become 36.8.32, I would not be able to do that without the downgrade module. Sadly, that module is made for LSposed. Is there one for magisk?
Arealhooman said:
No, are you familiar with the “Let Me Downgrade” module? If I have the official YouTube app, and it’s on version 36.8.34 and I want that same exact app to become 36.8.32, I would not be able to do that without the downgrade module. Sadly, that module is made for LSposed. Is there one for magisk?
Click to expand...
Click to collapse
Oh, I understand now. I am not sure.
I've generally been able to get around this restriction by clearing storage for that app, uninstalling it, then installing a previous version. No modules needed. And since you'd be sideloading the older app, it shouldn't be linked to the Play Store for updates...
Arealhooman said:
OH LMAO I meant to say use not “sue”. My mistake.
Click to expand...
Click to collapse
oh ok, i was very confused
V0latyle said:
Oh, I understand now. I am not sure.
I've generally been able to get around this restriction by clearing storage for that app, uninstalling it, then installing a previous version. No modules needed. And since you'd be sideloading the older app, it shouldn't be linked to the Play Store for updates...
Click to expand...
Click to collapse
I don’t mean sideloadin. Like downgrading the app. Look at the module I mentioned above.
Arealhooman said:
I don’t mean sideloadin. Like downgrading the app. Look at the module I mentioned above.
Click to expand...
Click to collapse
Okay...
The only version of an app that's going to be available on the Play Store is the latest release. To install a previous release you'd have to download it from somewhere like APKMirror and install it directly, which is sideloading. So unless there's a different way of rolling back to a previous version of an app that I'm not aware of...
V0latyle said:
Okay...
The only version of an app that's going to be available on the Play Store is the latest release. To install a previous release you'd have to download it from somewhere like APKMirror and install it directly, which is sideloading. So unless there's a different way of rolling back to a previous version of an app that I'm not aware of...
Click to expand...
Click to collapse
Sidelaod it’s but use it to update the official app. Looks at the module
“Android's app installation system does not allow users to downgrade to an older version of an app when they already have a newer version installed. Let Me Downgrade is an Xposed module for Android 12 and 13 that enables users to bypass this restriction.”
Arealhooman said:
“Android's app installation system does not allow users to downgrade to an older version of an app when they already have a newer version installed. Let Me Downgrade is an Xposed module for Android 12 and 13 that enables users to bypass this restriction.”
Click to expand...
Click to collapse
I understand that, that's why you have to remove the later version first before you attempt to install the older version. Are you talking about installing the older version as an "update" to the newer app?
V0latyle said:
I understand that, that's why you have to remove the later version first before you attempt to install the older version. Are you talking about installing the older version as an "update" to the newer app?
Click to expand...
Click to collapse
Yes
Arealhooman said:
No, are you familiar with the “Let Me Downgrade” module? If I have the official YouTube app, and it’s on version 36.8.34 and I want that same exact app to become 36.8.32, I would not be able to do that without the downgrade module. Sadly, that module is made for LSposed. Is there one for magisk?
Click to expand...
Click to collapse
Arealhooman said:
“Android's app installation system does not allow users to downgrade to an older version of an app when they already have a newer version installed. Let Me Downgrade is an Xposed module for Android 12 and 13 that enables users to bypass this restriction.”
Click to expand...
Click to collapse
V0latyle said:
I understand that, that's why you have to remove the later version first before you attempt to install the older version. Are you talking about installing the older version as an "update" to the newer app?
Click to expand...
Click to collapse
Arealhooman said:
V0latyle said:
I understand that, that's why you have to remove the later version first before you attempt to install the older version. Are you talking about installing the older version as an "update" to the newer app?
Click to expand...
Click to collapse
Yes
Click to expand...
Click to collapse
I am confused about what you are trying to accomplish.
During boot, apps are checked and if more than one instance is installed, the newest version is loaded.
For example.
If YouTube is included as a system app, updates are installed into userdata.
The updates can be removed but the version in system will always remain since system is read-only.
On boot, the newer (update) is found and loaded instead of the system version.
The update will still be treated as a system app.
If you want to downgrade YouTube to a version that is still above the version in system, just uninstall the update and reboot.
Then manually install the version (above system version) you want to use.
Make sure to turn off Auto-Update in PlayStore.
If you want to install a version below what is installed in system..
Then you have to disable the system version first.
You can do this with Magisk to make the system version fail to load.
Spoiler: Example
Replace System YouTube - [GitHub] - Link
Replace System YouTube Music - [GitHub] - Link
I have shared these in a Pixel thread or two.
Even though I archived the YT module, it still works for current Pixel builds.
(Maybe I should (de)archive it?
I am guessing that is (or similar to) what the LSPosed module does. ¯\_(ツ)_/¯
Cheers.
Edit:
Corrected links.
ipdev said:
I am confused about what you are trying to accomplish.
During boot, apps are checked and if more than one instance is installed, the newest version is loaded.
For example.
If YouTube is included as a system app, updates are installed into userdata.
The updates can be removed but the version in system will always remain since system is read-only.
On boot, the newer (update) is found and loaded instead of the system version.
The update will still be treated as a system app.
If you want to downgrade YouTube to a version that is still above the version in system, just uninstall the update and reboot.
Then manually install the version (above system version) you want to use.
Make sure to turn off Auto-Update in PlayStore.
If you want to install a version below what is installed in system..
Then you have to disable the system version first.
You can do this with Magisk to make the system version fail to load.
Spoiler: Example
Replace System YouTube - [GitHub] - Link
Replace System YouTube Music - [GitHub] - Link
I have shared these in a Pixel thread or two.
Even though I archived the YT module, it still works for current Pixel builds.
(Maybe I should (de)archive it?
I am guessing that is (or similar to) what the LSPosed module does. ¯\_(ツ)_/¯
Cheers.
Edit:
Corrected links.
Click to expand...
Click to collapse
Ty
ipdev said:
I am confused about what you are trying to accomplish.
During boot, apps are checked and if more than one instance is installed, the newest version is loaded.
For example.
If YouTube is included as a system app, updates are installed into userdata.
The updates can be removed but the version in system will always remain since system is read-only.
On boot, the newer (update) is found and loaded instead of the system version.
The update will still be treated as a system app.
If you want to downgrade YouTube to a version that is still above the version in system, just uninstall the update and reboot.
Then manually install the version (above system version) you want to use.
Make sure to turn off Auto-Update in PlayStore.
If you want to install a version below what is installed in system..
Then you have to disable the system version first.
You can do this with Magisk to make the system version fail to load.
Spoiler: Example
Replace System YouTube - [GitHub] - Link
Replace System YouTube Music - [GitHub] - Link
I have shared these in a Pixel thread or two.
Even though I archived the YT module, it still works for current Pixel builds.
(Maybe I should (de)archive it?
I am guessing that is (or similar to) what the LSPosed module does. ¯\_(ツ)_/¯
Cheers.
Edit:
Corrected links.
Click to expand...
Click to collapse
Is there any way to do this for any app? Not just youtube? I need to downgrade a system app to a lower version then supplied with the latest system update, withouth downgrading the whole system.
Pandoriaantje said:
Is there any way to do this for any app? Not just youtube? I need to downgrade a system app to a lower version then supplied with the latest system update, withouth downgrading the whole system.
Click to expand...
Click to collapse
Zgfg has a Systemless Debloater module that uses Magisk's 'replace' option.
Same as replacing the files manually with a zero byte file.
Magisk Module Systemless Debloater (REPLACE)
- Module - [GitHub] - Link
- Download(s) - [GitHub] - Link
- xda Thread - Link
Originally created for Xiaomi devices but works on all manufactures.
Zgfg just recently updated it to work with OnePlus' newer my_bigball directory.
Cheers.
ipdev said:
Zgfg has a Systemless Debloater module that uses Magisk's 'replace' option.
Same as replacing the files manually with a zero byte file.
Magisk Module Systemless Debloater (REPLACE)
- Module - [GitHub] - Link
- Download(s) - [GitHub] - Link
- xda Thread - Link
Originally created for Xiaomi devices but works on all manufactures.
Zgfg just recently updated it to work with OnePlus' newer my_bigball directory.
Cheers.
Click to expand...
Click to collapse
Thanks for the info. I've actually deepened myself into magisk modules, and came to the conclusion that creating a 'simple module' that replaces/mounts system files/apps is quite basic/easy, as it is built into magisk. unfortunately, in my case it also needs patches to the underlying system (removed/modified system calls). Thanks though.
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
Click to expand...
Click to collapse
Can you uninstall Magisk and install the stable or last working canary app?
simplepinoi177 said:
Can you uninstall Magisk and install the stable or last working canary app?
Click to expand...
Click to collapse
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
koberulz said:
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
Click to expand...
Click to collapse
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
simplepinoi177 said:
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
Click to expand...
Click to collapse
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
koberulz said:
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
Click to expand...
Click to collapse
Uninstalling the Magisk Manager app would not affect root; you might not be able to run certain rooted apps properly without granting them root access, but that's because of not having the Magisk app to grant it.
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings") so it's not detected by any root detection. In any case, you should be able to find it in the Apps list in Settings/Apps, and uninstall it that way.
As to what to install over the top of it, installing the latest stable 25.2 would be the best idea -- the Magisk App does not need to match the version that is patched and flashed to your boot partition...
simplepinoi177 said:
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
Click to expand...
Click to collapse
My understanding was that he got hired and they said he had to give it up, there was some negotiation and they let him continue working on it as long as Magisk Hide was removed as a feature.
But this isn't something that really interests me all that much, so I don't keep up with the news on it. I more just check in whenever I get a new phone in order to figure out how to root it.
simplepinoi177 said:
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings")
Click to expand...
Click to collapse
Yes, this is what I was referring to.
koberulz said:
Yes, this is what I was referring to.
Click to expand...
Click to collapse
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
Click to expand...
Click to collapse
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
simplepinoi177 said:
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
Click to expand...
Click to collapse
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
koberulz said:
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
Click to expand...
Click to collapse
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
simplepinoi177 said:
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
Click to expand...
Click to collapse
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
koberulz said:
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
Click to expand...
Click to collapse
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
What's the difference?
koberulz said:
What's the difference?
Click to expand...
Click to collapse
dcarvil said:
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
The first one is the first, general Magisk thread (that is still active and currently discussed). The second is as it is stated in the headline -- "This is a discussion and help thread for the newer versions of Magisk".
Most likely this is where you should go for your issues -- and to see how actively developed it is currently being.
It's just as you said, you've been away from rooting/Magisk for a while; the newer version of Magisk contains/employs Zygisk -- "Zygisk is new generation Magisk hide...Zygisk is what the Magisk developers call running Magisk in the Zygote Process of Android. The Zygote Process is the first process that the OS starts when it boots up, ... Since zygote starts first after system, it can hide root without sending data to apps." (source) As such, that's why a new thread was created and why it is sub-titled as "The Age of Zygisk"...
*but there are many more methods of hiding root than Zygisk (or in conjunction with); Shamiko, Magisk Delta, HideMyApp, etc.
In the end, I'm sure they'll suggest what I've suggested to you in some fashion -- you'll have to uninstall the Magisk Manager (hidden or not), and re-install the stable or earlier canary versions. But it'll be better coming from the people in that thread...
Good luck!