yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
In the quoted post I didn't say a word about magiskpolicy

The post was about terminology and how the applets work (applets are symlinked to binaries and binaries check the command-line arguments to recognize which applet was called)

However, in one of the earlier post today I agreed/confirmed about the Magisk v25 binaries (magisk, magiskpolicy) and their respective applets (su, resetprop and supolicy)
[Magisk] meric57:
Hello, talking to you busybox me I have the apk to install the best these to put the magisk modules or I keep the current apk. Also I read this

So if I update magisk 25.0, checking recovery mode will put it or I will always have the same problem starting in a loop on the logo
[Magisk] pndwal:
Well sorry for mentioning the difference...

You did say "Follow-up to the discussion on applets between @DiamondJohn and @pndwal".

This has related quite specifically to whether or not magiskpolicy is/was an applet of the magisk binary from the get-go... PW
[Magisk] DiamondJohn:
So, if I understand it right, a single binary, can contain multiple applets. Applets are executables.
[Magisk] zgfg:
If your system is an old Android without the read-only SAR (System As Root), then the old BusyBox app would work (installing/copying the applets directly to /system/bin or so)

However, on modern Androids SAR is read-only and you cannot make hard changes there - instead you must use systemless mechanism provided by Magisk: no changes are made to SAR, instead modules use the Magisk systemless mechanism to mount the changes on every reboot.

And if you simply disable the module(s) and reboot, the corresponding changes are disabled

Even for the old Androids Systemless mounting has advantages: you disable the systemless modules (or just boot with Magisk disabled, ie with the stock img not patched by Magisk) and you have the intact system partitions (good for OTA and so)

If not familiar with SAR, Systemless mounting, etc,

please read the Magisk GitHub Development documentation, google or even search through the earlier posts in this thread (sorry, don't want to describe/answer further again and again about the same)
[Magisk] huskydg:
Look in the source code you will know how binary perform different program with different name
[Magisk] zgfg:
Binary is the executable program (command-line application). Applets are executable symlinked 'copies' under the specific names that the binary recognizes when parsing the command-line arguments

Eg,, in case of toybox or busybox, those applets are standard UNiX/Linux tools, but tens of them packed and distributed as a single executable binary
[Magisk] zgfg:
I know how the discussion originally began but I followed exactly to what you started with in your particular post, as on the screenshot

(Anyway, stopping now my discussions and going to beach - tomorrow ending the vacations😩)
[Magisk] huskydg:
From 24302, magiskpolicy is no longer an applet of magiskinit to reduce the size of binary while compiling magiskinit.
[Magisk] Timmmy001:
I am trying to get to the current version using the factory boot image.

At least I thought that would be the correct way.

I also read on GitHub-Magisk that an OTA update does not work with the Pixel6.

Bootloop after OTA #5959

The goal is of course for me to keep the data incl. root with the update.
[Magisk] pndwal:
Seems that's for sure...

Seems the binary is the executable, but I guess applets could also be termed executables (they execute 😛) since they are 'built-in utility programs' that can share code...

This example explained it nicely for me:

https://man.archlinux.org/man/busybox.1.en#USAGE

🙂 PW
[Magisk] meric57:
Hello, some manage to update magisk 25.0 me in stable impossible and beta the same. There is in the update channel there is to put a direct link not where to find it this link. thank you
[Magisk] zgfg:
Of course. Just read the posts and youl'll see how many installed v25 seamlessly (see also the screenshot)

Also written many times that Stable is still on v24.3, hence you could not install/update to the yet non-existent Stable v25

I also suggested not to use Beta channel. If you are afraid of taking Canary, then stay on Stable v24.3 and wait until Stable would be updated to v25

In short - currently the Beta 25000 and Canary 25001 are built from the same code - hence they are 'same". If there is a bug (specially,preventing you to install v25 to your phone), it will be more likely fixed in the sooner Canary 25002 or so (Betas are less frequently released)

If you have problem installing v25 to your phone then provide as many details as you can: phone model, ROM, Android version, describe better with screenshots (sorry, your posts are hardly understandable/readable) how exactly are you installing/updating

I'd suggest:

Uninstall your Magisk application. From TJW Magisk Github page click to Magisk Canary to download that apk and install (see the screenshot)

It will be Canary app 25001. Then patch and flash as the recommended method is very well described also on the Magisk GitHub official page

Note: If you have Xiaomi, then do not patch/flash Recovery img but Boot img, even if Magisk app says Ramdisk No (for what TJW suggests to patch Recovery, not Boot)
[Magisk] pndwal:
Well you can't!...

Just flashing patched boot image will basically only give you any updates to the kernel... You need to flash the complete ROM to get updates to /system and other partitions...

I think vv's just saying that Magisk's 'install to inactive slot' for 'out-of-the-box OTA installation w/ Magisk preserved after installation' isn't working w/ these devices... I could be wrong; her comment certainly isn't clear...

Looks like you need to do standard OTA or ROM install, ie. restore stock images, take OTA or flash ROM, boot up system (you will loose root), then do standard Magisk initial installation again, ie. patch and flash new ROM's boot.img.

This user confirms that Magisk app → Install → Install to Inactive Slot after OTA fails, but standard patch / flash image w/ fastboot after OTA still works:

https://github.com/topjohnwu/Magisk/issues/5959#issuecomment-1152861547

In case if issues, try the procedure w/ newest Canary build; it has many fixes including several for Pixel 6 on Android 13; some of these may affect installation w/ Android 12 too...

Other Pixel 6 users may advise you further... PW
[Magisk] Skjold3:
I've got an incredibly stupid question. I've been messing with the Magisk app some time ago and I think I've hidden it, but I don't remember its name xD And there is nothing suspicious in the app list. Re-installing the 24.3 Manager doesn't help, it can't initialize (it opens with the Requires Additional Setup window, but if I select OK it immediately says "Setup failed"). The root and installed Magisk modules still work fine. Is it possible to find the hidden Manager app without remembering the name? Or is it possible to manually remove everything that might prevent it from setting up again?
[Magisk] pndwal:
Go right through list in device Settings, Apps. Default name for hidden app is 'Settings' which you may have altered or changed entirely... Look for instances of Magisk also... PW
[Magisk] martyfender:
By default, the hidden app is named settings, just like the Android settings app, unless you chose to rename it.

Or if not, if you have root, go to /data/app/ and look for a folder with a random package name that contains the apk. Atleast in my use case, I've never seen a reason to rename the hidden app to anything but it's default: settings.
[Magisk] xunholyx:
I'm not sure if this has been reported, but A13 beta3.3 makes it unable to install modules from storage.

The Magisk app just FCs as soon as I tap on the module.zip (I've tried with a few)

Fox's Mmm shows a toast that says "your current file picker could not access this file"

I've been looking into a way to fix it myself, but I'm running out of ideas.
[Magisk] zgfg:
Install abother file explorer.

In Magisk app, when you start browsing for the zip file, you can change the file explorer you use

Btw, last week or so there was a similar issue/solution (not to mention that from rtime to time the other users ask similarly)
[Magisk] xunholyx:
Cool, thanks. I'll try that. I have a couple of them installed. I was using SE which always worked for me. I should have thought to try that since I saw the other explorers in the list. I'll give it a shot with Total Commander 👍
[Magisk] xunholyx:
TC worked without an issue. Thanks again.
[Magisk] Skjold3:
Found it in Settings/Apps, thanks. For some reason Nova Launcher stopped showing it in the app drawer and it wasn't in the list of apps hidden from the drawer either. Weird. Anyway, removing it and re-installing fixed everything.
[Magisk] pigbedleg:
What is the checksum of the official github build?
[Magisk] Finnzz:
Are Zygisk and modules supposed to work when using fastboot boot magisk_patched_boot.img?

I only have tethered root, so I can only load magisk in memory from fastboot boot. By doing this superuser works, but I can't get zygisk to install/load. And the modules icon remains grayed out.
[Magisk] huskydg:
Boot a boot image temporarily or permanently doesn't make any different

Try 24.3

25.0 has know issue that zygisk cannot active on some mtk devices
[Magisk] zgfg:
Interesting. Since you have root, with a root explorer (like Magisk) inspect /data/adb:

- do you have that adb folder

- does it contain magisk.db, magisk folder and modules folder

Btw, once you fastboot boot ..., cannot you take Direct install (Magisk) from Magisk app?
[Magisk] Finnzz:
I'm working with an Amlogic device, I'm not sure if that makes any difference?

The same issue was present on 24.3 as well.
[Magisk] Finnzz:
Yes there's:

data/adb/magisk.db
data/adb/magisk/addon.d.sh
data/adb/magisk/boot_patch.sh
data/adb/magisk/BusyBox
data/adb/magisk/ChromeOS
data/adb/magisk/magisk32
data/adb/magisk/magiskboot
data/adb/magisk/magiskinit
data/adb/magisk/magiskpolicy
data/adb/magisk/util_functions.sh

No modules folder though

Ok the issue may be due to the ramdisk work around then. This is a FireTV 2nd gen Cube.

https://xdaforums.com/t/temporary-unlock-root-twrp-magisk-firetv-2nd-gen-cube-raven.4445971/

The device does not have a ramdisk in the boot partition, but it will process the ramdisk that magisk creates with the boot batch. I had seen an older post that said to use the boot.img patch with recovery mode option. This seems to work to give SU access, but no zygisk. I tried the regular magisk boot patch without recovery mode and that results in a mount / unmount loop during bootup.

After fastboot boot, magisk manager shows that magisk is installed, but there is no direct install option. I did try flashing the boot partition, and this will only load if I'm booting a modified bootloader with a tethered computer. So I'm assuming that the patched boot IMG fails a signature check by the native bootloader.
[Magisk] huskydg:
Do not set RECOVERYMODE to true if patching boot image.

Next time you should include some information such as Magisk log, installation log to find out the problem clearly
[Magisk] meric57:
Hello zgfg, complicated for me who am French who speaks no English so I go through google translation.

In my signature my smartphone model is noted, Samsung s10 4G G973F exynos A12 UI 4.1 TRWP 3.6.2 and magisk, I will wait for the final magisk update as I am rooted.

Good Sunday
[Magisk] Finnzz:
I realize this is not recommended. But it is a work-around that works for some Xiaomi devices without a ramdisk in the boot.img. And it appears to also work for at least this Amlogic device.

FireOS (based on Android) does not have a recovery menu with user options. Booting to recovery leaves me with no option to boot to FireOS. Patching the recovery IMG with magisk just drops me in recovery where I'm stuck.

This Amlogic device does see and process the mini ramdisk that magisk creates on the boot.img, just like the Xiaomi devices I referred to. This is evident by the boot logs and the fact that SU works with magisk.

Creating a boot.img without the recovery mode option results in a boot.img that does not boot. It gets stuck in a mount / unmount loop.

[ 22.122204@2] magiskinit: Skip invalid androidboot.slot_suffix=[normal]
[ 22.122352@2] magiskinit: open: /proc/bootconfig failed with 2: No such file or directory
[ 22.123358@2] magiskinit: fopen: /.backup/.magisk failed with 2: No such file or directory
[ 22.124504@2] magiskinit: open: /.backup/init failed with 2: No such file or directory
[ 22.125383@2] magiskinit: open: /.backup/.magisk failed with 2: No such file or directory
[ 22.126422@2] magiskinit: linkat magisk->magisk failed with 17: File exists
[ 22.199763@4] magiskinit: open: /sbin/magisk32.xz failed with 2: No such file or directory
[ 22.215770@5] magiskinit: mount .magisk/selinux/load->/sys/fs/selinux/load failed with 2:y
[ 22.216394@5] magiskinit: mount .magisk/selinux/enforce->/sys/fs/selinux/enforce failed wy
[ 22.218313@5] magiskinit: opendir: /magisk-tmp/.magisk/mirror/cache/magisk failed with 2:y
[ 22.234154@5] magiskinit: Skip invalid androidboot.slot_suffix=[normal]
[ 22.234303@5] magiskinit: open: /proc/bootconfig failed with 2: No such file or directory
[ 22.235309@5] magiskinit: fopen: /.backup/.magisk failed with 2: No such file or directory
[ 22.236430@5] magiskinit: open: /.backup/init failed with 2: No such file or directory
[ 22.237334@5] magiskinit: open: /.backup/.magisk failed with 2: No such file or directory
[ 22.238371@5] magiskinit: linkat magisk->magisk failed with 17: File exists
........

When booting with the boot.img created with recovery mode checked, the magisk log doesn't show any errors. I just 4 lines ending with

late start service mode running

Boot-complete triggered

But no modules or zygisk.

I have tried a number of builds between 24.300 and 25.0, which is what I'm on now. There was another issue with magisk not liking the slot suffix name that Amlogic was using. This got fixed in one of the Magisk Canary builds after 24.300. So the device will not work with any Magisk build 24.300 or older.
[Magisk] huskydg:
Have you reported this to magisk github?
[Magisk] zgfg:
For the matter of fact I have one Xiaomi (Mi 9T) where Magisk app reports Ramdisk No, pndwal another, and some other users here as well.

There are also guides around here on XDA (for Redmi K20 Pro, etc)

It was also discussed here. We just patch boot.img, without checking Recovery option and flas that patched boot img to Boot - and Magisk installs/updates perfectly
[Magisk] Finnzz:
I figured I'd start here by checking that zygisk should work when booting with fastboot boot from memory. So I'll go over there and see if it's a bug, and if it can be fixed.

Ok, that's good to know that those Xiaomi devices are not using the recovery mode while making the boot.img.

I could try reporting the mount/unmount loop issue on GitHub, assuming that if I can get that worked out that maybe zygisk will work too without the recovery mode option.

I don't know if there is a way to get the bootup log from a device that gets stuck in a loop? Before I was using UART, but I really don't want to have to open up the device again and go back to relying on serial output.
[Magisk] zgfg:
Check the Magisk logs at /data/cache or /cache if you can access
[Magisk] Finnzz:
Yes I do, unfortunately they don't provide any information on the kernel boot up, or what magisk might be doing to cause loop. It's probably back to opening up the device and using uart for logging.
[Magisk] zgfg:
Btw, Stable, Beta, Canary and Debug Channels just got v25.1 updates this morning:

Magisk Changelog

The Magic Mask for Android

topjohnwu.github.io

Maybe you could check the Changelog and your luck with
[Magisk] Spaceoid:
I just updated to 25.1 stable via the app.

Is it normal that the new 25.1 app _itself_ wants root rights?

I also had some problems repacking my Manager app - Magisk would firstly say that repacking failed, but now it seems to have worked either way.
[Magisk] zgfg:
Updated Canary from 25001 to 25101 with no surprises.

I don't hide Magisk app
[Magisk] Spaceoid:
Everything seems fine now. I guess hiding the Manager just shortly confused my system.
[Magisk] meric57:
Hello, I think my concern comes from there as I did like this to install TRWP and magisk. I have to uninstall magisk and redo the tutorial with magisk 25.zip offered here for my S10 G973F exynos

https://xdaforums.com/t/tutorial-ro...android-12-one-ui-4-1-stock-firmware.4394629/
[Magisk] pndwal:
Latest Official TJW public Stable (release) Magisk build:

Magisk​

Magisk Changelog​

v25.1​

[MagiskBoot] Fix ramdisk backup being incorrectly skipped

[MagiskBoot] Add new feature to detect unsupported dtb and abort during installation

[Zygisk] Change binary hijack paths

[App] Fix incorrect recovery mode detection and installation

[MagiskInit] Fix config not properly exported in legacy SAR devices

[General] Enforce the Magisk app to always match or be newer than magiskd

Release Notes:

https://topjohnwu.github.io/Magisk/releases/25100.html

For remaining diffs to public Stable 24.3, see Changelog for public Beta 25.0:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86993241

🎉🎉 👍 PW
[Magisk] meric57:
Hello pndwal, I know I'm looking to update magisk complete, as I put the link I went through this tutorial to root. I think I have to redo this tutorial and uninstall 23.4 to put the 25.1 APK to modify AP then flansher with odin.
[Magisk] pndwal:
This release marks the first Stable Magisk build with Stable Zygisk!

Further, :

👀 PW
[Magisk] pndwal:
Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

Magisk (9183a0a6) (25101)​

Sync to public release

Diffs to v25.1​

None

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

👍 PW
[Magisk] pndwal:
Not normal...

Full Magisk App has been failing to recognise / remove hidden app and vice versa for some time and this results in two apps competing with one showing the other's superuser permission request...

I've simply ignored requests in these cases and, if updating, uninstalled the hidden (stub) app to fix issues before taking Hide the Magisk app again...

If this occurs during hiding, ignore requests and uninstall the unhidden (full) app and hidden app should work fine.

If the issue occurs during restoring, ignoring requests and uninstalling the hidden (stub) app should fix the full app...

... You may possibly need to uninstall hidden (stub) and take Hide the Magisk app again if stub data has failed to populate properly when hiding, but I haven't normally found this necessary...

🤠 PW
[Magisk] meric57:
hello pndwal, I just redo my rooting from A to Z with magisk25.1 . Rooted with AP modify magisk canary then flash with odin demarage ok so rooting ok, now TRWP I will modify TRWP.img with magisk then either I go through TRWP.APK or odin in AP.
[Magisk] GauchoTche:
Hello, my phone doesn't have TWRP support, so i need to extract the boot.img from it so that I can install magisk. I am able to root it with KingoRoot. So How to extract boot.img from a rooted phone without twrp?
[Magisk] zgfg:
What is your Android version (supposidely something old if you could root with Kingo root)?

Consider, isn't the old SuperSU more appropriate for the old Android

Check on Magisk GitHub what Android versions are supported.

Be aware that eg Shamiko, Zygisk-LSPosed require A 8.1 or higger
[Magisk] GauchoTche:
Android 11. Phone is Ulefone armor x10 pro
[Magisk] saar17:
There is a new version of magisk, is it possible to upgrade to it with a rooted phone with losing root or bricking the phone? Or it can only happen when update the phone firmware?

Thank
[Magisk] zgfg:
Usually, boot.img should be extracted from the ROM zip file. Eg, from the OTA update.zip

You need to find where can you download the ROM that you are using (vendor or somebody usually provide a storage with ROM downloads for all stock ROMs)
[Magisk] casouzaj:
Or , if his/her phone is already

rooted by other means, through a dd command.
[Magisk] xunholyx:
Just use the update options offered in the app. When you get to the install Magisk part, use the recommended direct install
[Magisk] GauchoTche:
Hey pal, I've pm'ed you about how to do it.
[Magisk] huskydg:
The important changes of v25.1:

After you update to v25.1, you cannot downgrade Magisk app version. Magisk daemon will forcefully uninstall the app.

Magisk Debug build will not be affected by this change
[Magisk] hjjiang:
not sure what to say, i tried to upgrade from 24.3 -> 25.1 and it just boots then shuts down

my device is:

Oneplus 8 Global (in2015 c.11 Android 12)

i have fastboot flashed back my old boot.img 24.3 and it still works.

when i try to patch the above (boot.img 24.3) file and then do

```

fastboot boot magisk_patched-25100_IER3I.img

```

it jsut shuts down again
[Magisk] zgfg:
Search in this thread, how-to dd (post #50673):

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86395561
[Magisk] meric57:
Hello, I reinstalled magisk25.1 using the johnwu method, just magisk, not trwp. As I know, if I flash TRWP with odin or trwp.apk, no more startup. Just to know the security message there is a way to remove it without going through TRWP no, there is not a module to remove these red yellow triangle message.

thank you
[Magisk] asripath:
It still does in 25101.

Was on Canary 24312.

Unhide Magisk.

Updated app to 25101 and then Direct Install upgrade to 25101.

Went fine after two reboots.

Hide Magisk again...takes few tries

1st attempt failed to hide magisk error

2nd attempt two magisk apps created and the new one asks for root permission

Delete new hidden app

3rd attempt hide success ...takes a while longer than usual
[Magisk] casouzaj:
It seems to be device/maker dependant, because I have always updated magisk app, including the latest one, keeping it renamed/hidden, in my Sony XZ2 (H8296) running AwakenOS 2.8 (Android 12.1), and just the updated renamed/hidden app shows up in the apps drawer.
[Magisk] GauchoTche:
thanks pal! Phone is Uleafone Armor X10 Pro. With Mediatek chip. Will fastboot work?
[Magisk] zgfg:
Don't know -try, but you will first need to search for their appropriate drivers for PC

It's been several years since I had Mediatek. There was SP Flash Tool...
[Magisk] zgfg:
Be aware of that site with bogus tutorials how to root:

Root » TheNextDroid

www.thenextdroid.com

If you search for your phone model, there is a high chance you will find each. I searched for Xiaomi, they have tens and tens of models, including all the latest phones with A11 and A12

But the tutorial is always the same. They have a template and they just find/replace the phone model.

Tutorials claim that all these phones can be rooted by either:

1) KingRoot app on the phone

2) KingoRoot app on the phone

3) KingoRoot app from the PC

4) By entering (stock) recovery and Installing SuperSU or Magisk zip

There is no word about unlocking Bootloader. No word about installing custom recovery for (4)

Well, back then in 2015 or so, in the times of Android JellyBin and Lollypop it worked.

I had cheap Ulefone and two Elephone phones and for one of them KingRoot app worked (I simply switched then to SuperSU), for the other KingoRoot from PC worked and the third indeed had CyanogenMod stock recovery (you know, navigating by Vol Up/Down and with Power button for taking the option) and I used it to flash SuperSU zip (it was before the era of TJW and Magisk)

But those times have past long ago (except for few who may still have those old phones at home).

Android security requirements by Google are stringent and AFAIK no vendor could put to the market an A10/11/12 (or even A8/9 if it didn't start already with A6.1) phone with unlocked Bootloader (hence I cannot believe that just as simple as King or Kingo may root any) and stock recoveries allow only Factory reset, installing OTA and so (not flashing a 3rd party zip like Magisk)

Hence if you search and find the rooting 'guide' for your phone, enjoy reading (asking yourself why the hell you had to mess up with unlocking BL and so while the prehistoric King(o) can root root for you with no troubles)😁