yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Yeah, the Devs often push a Shamiko build for Canary if a Shamiko enhancement comes after they've successfully pushed a needed commit to official Magisk, or builds requiring Alpha if a PR is still not merged. But they basically only build fixes for Alpha that they're confident will be accepted in official Magisk. Ie. Alpha is no rogue for doing it's own thing... So Shamiko builds generally become compatible with public Magisk builds eventually, even if only for Alpha, then Canary, initially...

Seems latest is still Shamiko-v1.0.1-341-release, exclusively for latest Alpha... I think Shamiko-v1.0.1-300.works with 27.0+ however (?).

🤠 PW
[Magisk] Iridule:
Would there be any major benefit to switching to Magisk alpha vs Canary?
[Magisk] wilsonhlacerda:
Latest ones must be installed together, they available only in Telegram and not pushed for update as usual yet:

[Discussion] Magisk Alpha (Public Released) fork - @vvb2060

This is the spot for the General Support Discussion of Magisk Alpha "Public Released" fork created by @vvb2060. Disclaimer: This Magisk Alpha fork is not supported by @topjohnwu and is not an official channel for him. Use at your own risk...

xdaforums.com
[Magisk] pndwal:
Not major for hiding AFAICS... Shamiko change is just a compatibility fix for issue after latest Alpha changes... Check those Diffs here:

https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-89524006

Used to be major advantage before TJW Magisk got native bridge Zygisk loading like Alpha... Currently, ZygiskNext next has the advantage with ptrace+fuse method. 🤠 PW
[Magisk] NoobMonkey:
First of all, thnx for pointing the right direction earlier. Now I have wallet working, etc. Just one banking app that detects root for somehow.

This is the app that detects root: https://play.google.com/store/apps/details?id=fi.spankki&hl=fi&pli=1

Current version is 2.29.0. The app stopped working after an update so might get it working with older version, but not sure where to find it. The previous versions worked with denylist and enforcing denylist enabled.

So I've tried the following methods with no luck:

Disable Zygisk - the app crashes without even opening

Zygist enabled, denylist configured but enforce dnylist disabled - the app crashes before opening

Zygisk enabled, denylist configured and enforce denylist - app opens but after like 5s it throws me to their website saing my phone is rooted

Zygisk enabled, denylist configured, disable enforcing and installed Shamiko - still detects the root.

Between every method I've deleted the app's cache and data and rebooted the phone.

Here's where I'm at:

OP 7tpro

Latest LOS 21

Magisk27 + Shamiko + PIFix

Meets device and basic integrity

Play protect certified

Yasnac passes both

Googlet wallet working

Any tips how to get this app working? I have PC with adb so I can use it also if needed.
[Magisk] Legoman6:
You could try Zygisk-Assistant: https://github.com/snake-4/Zygisk-Assistant

I have this module installed alongside Shamiko (they will co-exist).

Are you hiding the Magisk app? (I use HMA).
[Magisk] samhhmobil:
You're on the right way.

You have basic and device integrity

Your device is certfied (Google PlayStore)

Both is important. Don't change that now!!!!

You have your banking app in denylist.

But did you hide Magisk inside itself with a random name? (Don't use HMA for magisk!)

And now it'll become tricky, because...

Many apps are looking for other traces in your system, and all have different techniques, so you've to fiddle out by yourself, what it is looking for.

I can't assist in this way, because your app "isn't available in my country".

But I know about many apps with different behavior:

- some apps are looking for the existence of /system/addon.d/99-magisk.sh

- some apps are looking for the existence of other apps which are known to need root, f.e. TitaniumBackup or others

- some apps are looking for TWRP-folder

- some apps are looking by itself for open bootloader

- some apps are looking for traces of customROMs (f.e. for the string "lineage" in /system/build.prop)

- some apps are looking for... ... ...

- some apps are looking for other... ... ...

- your app is looking for ... ... ... (you tell us!)

Have luck!!

samhhmobil
[Magisk] NoobMonkey:
Thnx for the suggestion, but Zygisk-Assistant didn't helped either.

Tried HMA also to hide Magisk but that just ended up crashing the banking app right on starting the app.
[Magisk] NoobMonkey:
I've renamed tha Magisk to "Magical manager", not sure if it's different enough.

Thnx for trying to install it... I've read that they have blocked identification outside Finland, but didn't know they blocked the whole app.

So how do dig out what this app is looking for? I assume some how look up logs after running it, but how?
[Magisk] samhhmobil:
Did you just only "renamed" it in your launcher? (This will NOT work!)

Or did you "hide"(!!!) it inside(!) the settings of Magisk, with a new random name?

samhhmobil
[Magisk] NoobMonkey:
At the first time after intalling Magisk I recall it asked if I want to hide it by renaming it so I assume I did it inside Magisk. It shows every where on the name I entered.
[Magisk] samhhmobil:
Please show a screenshot of your magisk "Home" page
[Magisk] samhhmobil:
That's OK. You're magisk is correctly hidden (see the random "package" name).

So... now you've to fiddle out, for what traces your finnish banking app is looking for, additional to root, PlayIntegrity, DeviceCertification...

I know, it's not easy.

samhhmobil
[Magisk] wilsonhlacerda:
You can get/install older version with Aurora Store (available on F-Droid; use anonymous login).

The internal Play Store version is different from what you see by app itself. For instance for your current 2.29.0 it is 26924. Aurora Store will show you that.

On Aurora just search it/open its link and on top right menu choose Manual Download. And go trying to download 26923, 26922,.....till it is available/download start. This is not really incremental, may have lots of skipped ones, but it will be a number lower than current one.

You can do that with any app. Any old version (just keep decreasing the internal version number to get what you want).

To downgrade an app you must first unistall newer version. Or have an LSPosed/Magisk module that enable downgrade inatalls.
[Magisk] trevtdogg:
this sounds like a great idea, can you recommend a particular module that does this well?
[Magisk] trevtdogg:
have you tried Momo? I've never needed to use it, but have seen others use it for this purpose.
[Magisk] wilsonhlacerda:
CorePatch, XDowngrade, Let Me Downgrade, Dia, Smali Patcher, there are some others. I'm not sure but I think even App Manager only can do that.
[Magisk] NoobMonkey:
Thnx. Only had to go down to 26321... Just a "few" tries before found the previous one. But that one doesn't Crash or detect root.
[Magisk] Iridule:
Is it worth trying to hide from momo? Still shows zygote injection and custom rom along with broken tee.
[Magisk] J.Michael:
If you can figure out how to hide from Momo, you can apply the same technique to real apps.

If all apps you care about are running, there is no need to obsess over Momo.
[Magisk] Bladius:
16.2 doesn't work. Only 1 test passes
[Magisk] Untitled_neo:
Yes, I followed this instruction.

[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)

Preamble: After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85). The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG)...

xdaforums.com

I didn't upgrade my firmware not to lose root (and I still don't know why I should do. it can only slow your device).

My Boot.img still available here

[IMG][STOCK][PATCHED] Boot, Vbmeta and Recovery: Images Partitions for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)

Original Stock BOOT.IMG for MERLIN + Magisk Patched BOOT.IMG for MERLIN + Original Stock VBMETA.IMG for MERLIN + Original Stock RECOVERY.IMG for MERLIN Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G Firmware Versions: - (Engineering)...

xdaforums.com
[Magisk] badabing2003:
The below process with PixelFlasher can be used with any phone, even though the tool is named PixelFlasher.

Check the guide here.

Do everything that says in the pre-requisites part except Android Pixel phone part

Then do Usage | Basic Mode parts 1,2,3

Click on Settings and enable Offer Patch Methods

Download locally on your PC, the Magisk version that you want to use.

Then click on the Patch button and choose Patch custom boot/init_boot

Select the stock boot.img file that you download from your links.

When the patch options are offered, select Other Magisk

This should create a Magisk patched boot.img and show it in the boot list.

Select it and click on the button (on the right) Flash Boot

Your phone will reboot to bootloader and flash the patched image,

When it reboots, you should be rooted.

Install the same version of Magisk that you used to create the patch and run it, if it asks you that it needs to perform some actions, accept it.

If it doesn't go according to the plan, create a support file in PixelFlasher and post it in PixelFlasher threads, don't clutter this thread unnecessarily.
[Magisk] Mister Floppy:
"ExSDcard" module is working, but can't be installed normally in "newer" versions of Magisk

Since nobody could answer my question in the "ExSDcard" thread at https://xdaforums.com/t/module-exsdcard-write-access-enabler-5-0-8.3670428/ , I decided to repeat it here. Working download URL for this module is: https://web.archive.org/web/2021031...3pxdhg/ExSDCard_Write_Access_Enabler_v3.5.zip

I had v3.5 of this module working fine for years on my Xiaomi smartphone (Pocophone F1, Android Pie, stock ROM from the manufacturer) running Magisk v27.

Because of some unsolvable quirks, recently I had to start from scratch and downgrade from Magisk v27 to v26.3 by removing Magisk completely and with that all modules I had installed. But before doing that, I manually backed up my folder "modules" and its' subfolders residing under "/sbin/.magisk/modules".

I had to reinstall each of my beloved Magisk modules which worked without any problem - besides of the "ExSDCard Write Access Enabler" one.

According to the attached screenshot, it did install, but:

1. after reboot, ExSDcard did not appear along with other modules

2. log did not record any information on the installation

3. looking under "/sbin/.magisk/modules", no "ExSDCard" folder shows up

Then I tried the following workaround: I manually copied my saved "ExSDCard" folder to "/sbin/.magisk/modules" and rebooted the device. After that, the "ExSDCard Access Enabler" entry reappeared in Magisk like any other module I installed the "normal" way.

The module does actually work fine, and it is toggleable and removable.

But why can't the module be installed in "newer" versions of Magisk? I saw that another user running Magisk v25.2 has the same problem https://xdaforums.com/t/module-exsdcard-write-access-enabler-5-0-8.3670428/post-88028851

Also, I don't know if it's relevant or not, but when I manually copied my saved "ExSDCard" folder to "/sbin/.magisk/modules", I had to confirm a box appearing in my file manager app asking "Remount drive as "readable/writeable" using command mount -o rw,remount /sbin/.magisk/modules" ?"
[Magisk] J.Michael:
In spite of the success you report, I don't think you should have backed up and restored that folder.

Modules go in /data/adb/modules. If Magisk maintains /sbin/.magisk/modules, it does it with Magisk magic, probably by overlaying with /data/adb/modules.

So you being asked to remount /sbin is not a surprise. What is surprising is that it was so easy to do -- maybe thanks to your system predating so many of Google's improvements.

I'm also surprised you have bee running Magisk 27 for years -- I thought it only came out within the last year.

If the "normal way" to install a module is to open the Magisk manager app and tell it to install a module, then someone else will have to explain why this one module can't be installed that way.

Have you rebooted since you wrote directly to /sbin? Can you see (in the output of "mount") what is being mounted on /sbin? Is this ExSDCard in /data/adb/modules? Can you tell if it was put there when you installed it normally, or when you forcibly wrote to /sbin?
[Magisk] zgfg:
Looking to your screenshot, your module 'requires' Magisk v17 or higher. Developer could not foresee and put it that his module requires Magisk v17-v20.4 or so

This is a way OLD module, Magisk v17 was from 2016 or so, the times of Android 7. Magisk has been seriously redesigned after. Your module was not upgraded or you don't have the latest version

With the old Magisk v17, maybe up to v19 or v20.4 (guessing) it would install fine.

For newer versions ask developer to upgrade the module (if never upgraded for the last 6+ years, it must have been abondonded)

Magisk installs modules to /adb/data/modules - maybe in the OLD days of Magisk it was your path and your OLD module expects to be installed there. As said, ask the module developer to upgrade or look for alternative, up-to-date replacement

Alternatively, you maybe installed that module originally with an ancient version of Magisk and it installed fine. You later gradually upgraded Magisk and it didn't affect your module installed to the old path - but now, module cannot install with the new versions of Magisk ('new' = maybe 3-4 years old Magisk versions), except when you manually copied it's stuff to that old installation folder

Look to /data/adb/modules and you will find all your modules there. I doubt you will find any other module in that old path on /sbin - except if you also have the other old modules from that time

---

'New' modules, when installing, require Magisk v20.4 or higher

META-INF/com/google/android/update-binary

You will find close to the top

require_new_magisk() {
ui_print "*******************************"
ui_print " Please install Magisk v20.4+! "
ui_print "*******************************"
exit 1
}
[Magisk] Mister Floppy:
Thank you for the detailed explaination!

I compared the modules under "/data/adb/modules" with the ones under "/sbin/.magisk/modules" - they are absolutely identical, even newer ones which are updated regularely by the developers.

I remember that I installed the "ExSDCard" module years ago the normal way (I think it was under Magisk v23). I think that the developer has abandoned it.

As long as "ExSDCard" is working fine, I can live with the requirement to copy it manually.
[Magisk] vpvfi:
I've been able to make this app work by freezing Magisk with Hail. It probably only freezes the app and not all the background stuff.
[Magisk] benlge:
Bonjour la communauté ;-)

J’ai désinstallé Magisk, je l’ai flashé. ZIP par TWRP, installé l’APK, mais je reçois toujours ce même message qui revient. Pouvez-vous m’aider à résoudre ce problème ?

Merci.

Benoit

Mod Edit: English Translation Below

Hello community ;-)

I uninstalled Magisk, I flashed it. ZIP by TWRP, installed the APK, but I always get this same message that comes back. Can you help me solve this problem?

Thank you.

Benoit
[Magisk] BillGoss:
Please read rule "4.Use the English language" in https://xdaforums.com/t/xda-developers-forum-rules.4200559/
[Magisk] J.Michael:
I think it is saying, yes, you have installed Magisk once. Now, with Magisk installed, you have to use the Magisk manager app and install Magisk again.

There is something called "Direct Install" -- I've never used it, I have just read about it, but I think it is an option in the manager app. That might do it.

Or you could try taking the apk file you used to install the manager app, make a copy with the extension changed to ".zip", and then tell the manager app to install the zip file as if it were a module. That would be in the Modules section in the manager app.

Or, use the manager app to patch the boot image, then flash the patched boot image.

If the only way you know to flash an image is via TWRP, you'll have to wait for someone else to chime in. I know some files can be flashed in some TWRPs, but I'm not sure which combinations.
[Magisk] pndwal:
Just take Magisk Install, Direct Install from within the app to fix incomplete installation...

Installation from custom recovery now only partially installs root. Module/selinux rules cannot be set unless patching is done while Android system is running since major refactoring (made Magisk compatible with more devices).

For the few devices that don't support Direct Install (due to unmounted partitions while Android is running), you'll need to extract your boot image from ROM or use a boot partition backup made in TWRP, then patch that in Magisk App from Magisk Install, Select and Patch a File before flashing that using fastboot or TWRP.

🤠 PW
[Magisk] SteweEliteModder:
With latest version v27.0 the Samsung Galaxy S22 Ultra loses the root in every way, both with direct installation and with the patched boot.img flashed by odin, older vetsion 26.4 works perfectly instead... 😑
[Magisk] xerves78:
Hi,

i cant install magisk on the newest release of lineage21 for oneplus 9 pro

i did

install magisk beta 27.0

patching boot.img from the rom

flashing patched boot.img in fastboot

--> bootloop at the lineage boot sequence

if i flash the original boot.img, lineage boots, so the patched image is the problem

what did i wrong ?

thx
[Magisk] J.Michael:
Maybe you're not supposed to patch the boot image for Lineage 21. Check to see if it also has an "init_boot.img".

Also, check to see if Lineage 21 has built-in root -- this can interfere with Magisk.

And make sure you don't have modules in /data/adb/modules. If you didn't wipe /data, and you had modules with the previous system, they are still there waiting for a chance to screw you.

(I know, without root it's hard to check. If you have TWRP, and it has file manager capability, use that. If you think you installed Magisk correctly, boot to Safe Mode. If you have trouble finding or performing the key sequence to boot to Safe Mode, someone recently posted that he installed Magisk, then temporarily booted the unpatched image with "fastboot boot unpatched.img". From standard, no Magisk, Android he had an option to boot to Safe Mode, but when it booted to Safe Mode it was using the patched boot image, so Magisk was running. Either he could use root privilege in Safe Mode, or just booting to Safe Mode caused the next boot to be with all modules disabled. Either way, he was able to get all modules disabled.)
[Magisk] pndwal:
Latest Canary (+ Debug)!:

Magisk (45fa1fce) (27003)​

[General] Support 16k page size

[MagiskPolicy] Preserve sepolicy config flag after patching

[MagiskPolicy] Optimize patching rules to reduce the amount of new rules injected

[Core] Remove unnecessary mirror for magic mount

[DenyList] Support enforcing denylist when Zygisk is disabled

[Resetprop] Improve implementation to workaround several property modification detections

[Resetprop] Update to properly work with property overlays

Diffs to v27.0​

[General] Use a minimal libc to build static executables (magiskinit and magiskboot) for smaller sizes

[MagiskInit] Rewrite 2SI logic for injecting magiskinit as init

[MagiskBoot] Support spliting kernel images without decompression

[App] Support patching Samsung firmware with images larger than 8GiB

[App] Use user-initiated job instead of foreground services on Android 14

https://github.com/topjohnwu/magisk-files/blob/e23b98f8a2ba47b5110dd3e2937231c6a42db0b6/notes.md

👍 PW
[Magisk] bombadier:
Is everything working on the new release 27003 ? Saw on the pif thread something about it breaks Shamiko 1.0.1(300)
[Magisk] traversone:
Unfortunately Shamiko is broken with this release, reverting back to 27.002.

Device is Samsung S23 stock A13
[Magisk] zgfg:
Or use Zygisk Assistant instead (supposidely better for hiding and open source)
[Magisk] sawdoctor:
There's an updated shamiko on telegram, not tested it and can't officially post it on here but if you want to test it and can't find it let me know and I'll drop you a pm
[Magisk] jobsense:
zygisk disable itself after soft reboot or restart , any way to handle it?
[Magisk] zgfg:
Probably not if it requires full Magisk re-initialization

To reach devs you will need to open Issue on GitHub (you need GH acc, Debug Magisk ver and logs) - good luck
[Magisk] pndwal:
V1.0.1 (343) still requires Alpha... 🫡 PW
[Magisk] sawdoctor:
Any downside switching from latest Canary to alpha? And thanks for the heads up
[Magisk] pndwal:
Yeah, I expect they're working on TJW compatible Shamiko...

Also, I recommend restoring Magisk App if hidden before updating as Cannot direct install after repackage app was not fixed for this build. However @aviraxp has just now (finally) submitted a PR to fix it. 👍 PW
[Magisk] pndwal:
You'd need to compare changelogs... Released Alpha is still based on 27002, but many commits are added before merged in TJW Magisk so it may include many 27003 commits and be not too dissimilar...

I expect we'll see both Shamiko for official Magisk as well as 27003 Alpha soon enough in any case. 😉 PW
[Magisk] Lughnasadh:
Shamiko was updated to support Canary Magisk 27003.
[Magisk] bombadier:
Thanks, am holding off updating but learned a while ago good practise is always unhide magisk before updating because of potential problems, also read that the Shamiko update only works with alpha, been on normal magisk debug version 27002 for ages anyways

Ha low and behold an update
[Magisk] sawdoctor:
I know you can't post the file but if you see an update on shamiko for latest Canary could you please let people know it's been released

Edit

Scratch that it's just been released
[Magisk] traversone:
actually it works now! till 4 minutes ago Zygisk Assistant was also performing well...thank you Lughnasadh
[Magisk] knoedelcc:
This new built won''t work with Shamiko v1.0.1.

Shamiko v1.1 is already released and should fix this but at least for me all apps on the DenyList won't start anymore/will hang/crash.

If you need any of those apps - in your DenyList/hidden by Shamiko - you might just want to wait until a new fix will be released.
[Magisk] sawdoctor:
Do you have zygisk assistant installed? If i have both latest shamiko and zygisk-assistant together then I can't open apps on the deny list. Either on there own work fine
[Magisk] knoedelcc:
No Zygisk Assistant, only PIFork, Shamiko and Systemless Hosts (Edit: Zygisk option in Magisk Manager enabled though).

Uninstalling Shamiko and switching to Zygisk Assistant helped in my case/with my apps (no side effects yet). Thanks!
[Magisk] gerald206:
So I can't update my magisk to canary version using direct install even flashing magisk.zip as a module doesn't work.

device: Infinix hot30i(X699)
[Magisk] kalehrl:
Is there a way to issue these commands using Magisk upon booting of the Android tv box:

settings put global device_provisioned 1
settings put secure user_setup_complete 1
settings put secure tv_usersetup_complete 1
[Magisk] zgfg:
Put that to the service.sh script and put the script to (if you have Systemless hosts enabled):

/data/adb/modules/hosts

until [ "$(getprop sys.boot_completed)" = 1 ]
do
sleep 1
done

settings put global device_provisioned 1
settings put secure user_setup_complete 1
settings put secure tv_usersetup_complete 1

Or put the script (with any name) to

/data/adb/service_sh

And reboot
[Magisk] kalehrl:
Thank you. But what if I don't yet have root access because the device has just booted with Magisk patched boot.img and I don't have a way to start Magisk app to finish Magisk setup. The box provider has disabled access to all apps until the initial setup has completed and box got activated by them.
[Magisk] zgfg:
If you have custom Recovery/TWRP, use its Advance, File Manager

Maybe you can use adb push to copy the files

Or (but then you need to do that every time upon booting) use like

adb shell settings put global device_provisioned 1

but maybe you will need (then the root is needed):

adb shell su -c settings put global device_provisioned 1