yashsingh1/xdaforums huggingface dataset:
[Magisk] bombadier:
I have always have problems with magisk and bug reports think I have even failed with the debug version lol, although its closed I have added that the bug is not present with the debug version
[Magisk] pndwal:
Just open another with "version code: 27002" somewhere in first post, explain you tested both but issue is with Canary only, not Debug... Supply logs from broken build and wait for further instructions from Devs... Template requires the version code (or bot closes) + logs (or Devs will often close with comment like "no log no fix")...👍 PW

Edit: Someone opened proper issue following template just now:

https://github.com/topjohnwu/Magisk/issues/7921

Looks to me like this commit has issues:

Always update stub APK when upgrade​

committed5 days ago
[Magisk] traversone:
just tried installing over Samsung S4 LOS 18.1 (A11 32bit)

- Target image: /dev/block/mmcblk0p20

- Device platform: armeabi-v7a

- Installing: 81658d45 (27002)

- Unpacking boot image

Parsing boot image: [/dev/block/mmcblk0p20]

HEADER_VER [0]

KERNEL_SZ [4382168]

RAMDISK_SZ [910748]

SECOND_SZ [0]

EXTRA_SZ [0]

OS_VERSION [11.0.0]

OS_PATCH_LEVEL [2024-02]

PAGESIZE [2048]

NAME []

CMDLINE [androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 buildvariant=userdebug]

CHECKSUM [2d94db34875fc6fe561ba651ad6a41b1409cbf98000000000000000000000000]

! Could not find zImage gzip piggy, keeping raw kernel

KERNEL_FMT [zimage]

RAMDISK_FMT [xz]

SAMSUNG_SEANDROID

unexpected ASN.1 DER tag: expected SEQUENCE, got APPLICATION [19] (primitive)

- Checking ramdisk status

Loading cpio: [ramdisk.cpio]

Loading cpio: [ramdisk.cpio]

Extracting entry [.backup/.magisk] to [config.orig]

- Magisk patched boot image detected

Restore [.backup/init.xz] -> [init]

Removed entry [.backup]

Removed entry [overlay.d]

Removed entry [overlay.d/sbin]

Removed entry [overlay.d/sbin/magisk32.xz]

Removed entry [overlay.d/sbin/stub.xz]

Dumping cpio: [ramdisk.cpio]

- Patching ramdisk

- Pre-init storage partition: userdata

Loading cpio: [ramdisk.cpio]

unsupported file type

Failed to process cpio

! Unable to patch ramdisk

! Installation failed
[Magisk] gvmiguez:
I just tapped on the update notification of Magisk and now I can't access to the app. It was hidden and and in Canary channel, now I have this window all the time, click on ok to update but nothing happens, what can I do?
[Magisk] J.Michael:
Uninstall the hidden manager app.

If you have an unhidden manager app, and it's not Canary, uninstall it, too.

Install the Canary apk.
[Magisk] BrimoFan123:
Stuck at download when trying to update Magisk Canary app to 27002.

That is because I have Magisk hidden, so first I unhide Magisk.

Then Update to 27002 was successfully completed.

Next step: update Magisk - also successfully completed, reboot done.

Then trying to Hide Magisk - toast "Failed!"

Rebooted to TWRP and flashed apk in there.

After the reboot trying to Hide again but still the same result - Failed!

Is it a bug in 27002 or is it possible to Hide Magisk 27002? If so then what steps?

[EDIT 1] It looks like a bug: https://github.com/topjohnwu/Magisk/issues/7921#

[EDIT 2] I installed Magisk Debug Manager 27002. With this version Hide Magisk works but Momo detects Magisk and 'su' and therefore many apps don't open with warning "it is rooted device".

How to fix this? What are the steps to rollback to Magisk Canary 27001 or how to successfully hide Magisk Manager 27002?
[Magisk] J.Michael:
If you have the apk for Magisk Canary 27001, make a copy with extension .zip, then install that as if it were a module in Magisk manager.
[Magisk] gvmiguez:
Thanks for the help, I had to update with the debug apk because canary fails to hide Magisk, then select the canary update channel again

Edit: I have problems with the Canary and debug installation, Magisk app force to unhide the app, anyone else?
[Magisk] swieder711:
I updated the app and System to 27002. Update went fine, but also getting a Failed message when trying to rehide.

Edit - switched from Canary to Debug and I was able to hide Magisk.
[Magisk] Gemini3B9TL:
How I do jt
[Magisk] J.Michael:
Read a lot of posts in this thread.

John Wu's original instructions still apply.

Read the PixelFlasher thread. PixelFlasher automates a lot.

You don't just text "root" to 666. You need to do some setup before you can do anything else. You need to understand some of what you are trying to do. Some steps vary according to your phone model.

If you are hoping for pre-digested instructions, you need to identify your phone, identify the OS (Android version), say whether you have access to a PC, whether it's Windows. Maybe mention whether you are familiar with Windows and Linux.
[Magisk] sawdoctor:
Not sure if the fix has been pushed yet but looking at GitHub it's been sorted
[Magisk] Nergal di Cuthah:
Not pushed yet according to my magisk app.

Luckily i don't hide or need to hide; this is a sad bug and i hope, for others' sake, it's pushed as soon as the developers can. But that's also why it's canary and not beta or release, it's why (or should be why) we use canary, to squash bugs before the rest experience them.
[Magisk] sawdoctor:
Revert "Upgrade AGP" by yujincheng08 · Pull Request #7924 · topjohnwu/Magisk

Reverts #7893

github.com

Just waiting for a review and then it should be merged
[Magisk] pndwal:
Not pushed yet... Looks like recent Android Gradle plugin upgrade just didn't build properly... Guess a new build may come once Upgrade AGP is reverted but may not happen till AGP upgrade is redone. 🤪 PW
[Magisk] osm0sis:
Heads up for this upcoming (next canary) breaking change from established Magisk/root behavior:

Refactor magic mount by yujincheng08 · Pull Request #7685 · topjohnwu/Magisk

Mirror was previously used for accessing the original file during magic mount when we are using a tmpfs to cover the target. However, since we introduce atomic mount, we switch all tmpfs mount in w...

github.com

😒

Edit: I guess there is a viable workaround built in with the more recent changes to the `magisk --denylist` command, so we might be fine once people adapt their scripts/apps. 👍
[Magisk] Lughnasadh:
It's merged now (different PR than original).

fix: AGP and upgrade to 8.3.1 by JasonKhew96 · Pull Request #7926 · topjohnwu/Magisk

fix #7921 close #7924

github.com
[Magisk] traversone:
do you think this behaviour is not worth being investigated?
[Magisk] pndwal:
Honestly, could be issues Devs may not be interested in tackling since it's a custom ROM and Kernel 6 android iterations removed from last stock it seems... If latest stock ROM for this device was Android 5.01 they won't touch that either...

Could just be problems with this buggy Magisk build anyway... I'd wait for next Canary with fixes, but you could always open a proper GitHub issue with logs (run Debug build) and see what Devs say. 🙃 PW
[Magisk] pulpf:
same problem with canary I was not root and I could not hide magisk

it works with debug
[Magisk] SOCOM-HERO:
Is 27003 coming soon to fix this? Looks like the issue tracker for the bug with 27002 canary magisk hide glitches were closed in Github.
[Magisk] Nergal di Cuthah:
Just awaiting a push is my understanding of that
[Magisk] pndwal:
Of course merged commits always have associated CI test builds... If you're desperate to try now, just extract them from artifacts here (just need GitHub account): Upgrade AGP to 8.3.1...

Nb. More changes/tests may (likely) occur before next Canary build is pushed and the CI build may have unresolved bugs... 🤠 PW
[Magisk] stormy1777:
Noticing strange behavior with mount --bind on Magisk v27.

Android 9, Redmi 7A, Magisk v27 appears to handle mount --bind different than v26.4?

Tried mounting using "su" or "su -M" however, only ROOT users can see these mounts, non-root and all apps cannot see them!!

Tried changing namespace to inherent or Global in Magisk (with reboot), the mounts work ok, but, only for ROOT users!

/mnt/media_rw/EFC3-28AB/Download 117910912 96477312 21433600 82% /mnt/runtime/default/emulated/0/Download
/mnt/media_rw/EFC3-28AB/Download 117910912 96477312 21433600 82% /mnt/runtime/read/emulated/0/Download
/mnt/media_rw/EFC3-28AB/Download 117910912 96477312 21433600 82% /mnt/runtime/write/emulated/0/Download

that df view is seen only as ROOT user, as soon as normal user (or , any app) looks, nothing appears mounted... multiuser mode is set to 'root owner' not sure if that is relevant.

Kept testing, then flushed v26.4 magisk zip from twrp, after boot, INSTANTLY all folders mounted correctly for all users.. appears to be a Magisk v27 issue.. for time being left it as v26.4 for the engine, and v27 magisk Manager, seems to work.

Is this a known issue, or any tips how to debug?
[Magisk] pndwal:
I mentioned new 'atomic mount'

Make tmpfs mount of magic mount atomic​

... This avoid system libraries disappear temporarily during magic mount, which causes some dynamic executables fails to run during post-fs-data.

and some associated issues back here:

This was added in 26403, so you've missed it if not running Canary...

This (and associated commits) has caused issues like these:

- Magisk not working after 27.0 update #7820

- Magisk 27.0 no longer works with easySSHFS "fuse.sshfs is not in /proc/mounts" - Mount Namespace Modes issue #7822

Looks like these (and more) may be fixed by upcoming

Remove unnecessary mirror for magic mount​

... Mirror was previously used for accessing the original file during magic mount when we are using a tmpfs to cover the target. However, since we introduce atomic mount, we switch all tmpfs mount in worker and then move to the target at once. It means that we can still access the original file when we are constructing the tmpfs mount point. Thus we no longer need mirror.

+ Let magic mount optional etc.

So further behavioural changes especially for Devs (removal of mirror etc) are coming too... 👀 PW
[Magisk] stormy1777:
Oh dear.. sounds like v27.0 is marked 'stable' when in fact it is not (yet) :)

Is there any workaround until update comes? a custom channel? how to access exactly?

From reading, one suggested using Magisk-Alpha, (never heard of it)

App Center

install.appcenter.ms

some say it is "better" at hiding the root/safetynet checks, (which my device does not pass using normal magisk...) any tips welcomed, thanks for the quick confirmation!!
[Magisk] waldmax:
Sorry to bother with maybe a stupid question.

I am using Magisk and root for a long time on my Poco F2 Pro with latest xiaomi.eu ROM and XiamiEUModule App for NFC payment.

Everything was working fine with Magisk 26.4

A few days ago I updatet to Magisk 27.0 since then my normal banking app of an Austrian bank gives me a warning, but is still working. No problem witih NFC payment.

Would be nice to get rid of this warning again, have you any idea how to do so, or how to find out the reason.

*******************

On my new phone, Xiaomi 14 Ultra Global Edition FW 1.0.4 I applied for unlocking bootloader, did the unlock yesterday, which caused factory reset.

I patched init_boot.img after installing Magisk 27.0, enabled Zygisk, hide Magisk, installed PlayIntegrityFix_v15.9.6, Enforced Deny List, Added necessary services to deny list, in Developer Options of Google Play I meet Basic and Device Integrity. Banking App Works, but also the warning about root detected.

So I flashed FW 1.0.2 via Fastboot with Clean_All Option, made update to 1.0.4 with the updater app (flashing 1.0.4. with fastboot failed, so I made safe bet with flashing 1.0.2. what I have already done successful this morning).

Then agan the same procedure but with Magisk 26.4, enabled Zygisk, hide Magisk, installed PlayIntegrityFix_v15.9.6, Enforced Deny List, Added necessary services to deny list, in Developer Options of Google Play I meet Basic and Device Integrity. Banking App works without any warning.

Can you tell me why this behaviour with older Magisk or how to find out?

**************

Bonus info- NFC Payment with the app of my bank (not Google Wallet) does not work on Xiami 14 Ultra, but it did also not work as long bootloader was locked. Hoping for xiaomi.eu ROM for Aurora, and working NFC...
[Magisk] pndwal:
Difference may be related to new "atomic mount" I mentioned above, not sure, but be aware that DenyList is NOT designed for (proper) root hiding... I'd be trying with Shamiko which just hijacks list from DenyList but runs in hidelist mode. Nb. The same Devs responsible for most recent major refactoring in Magisk also maintain Shamiko.

Also, Hide the Magisk app (ie. Magisk in stub) is broken in 27.0... You may need that. 🤠 PW
[Magisk] waldmax:
Thanks for your reply.

So I stay for the moment at Magisk 26.4 für my Xiaomi 14 Ultra. Because there is xiaomi.eu ROM for my phone available since 2 hours, I will flash this tomorrow und with the Module from Xiaomi.eu Team I do not need Playintegrity anymore.

So do I understand correct, to hide root I should use Shamiko? Latest Shamiko can be found here https://github.com/LSPosed/LSPosed.github.io/releases correct?
[Magisk] zgfg:
Since Xiaomi eu is a custom ROM, their devs made the injector, 'module' that tricks DroidGuard and injects the spoofs with no need for Magisk/root and Zygisk

And as that, you achieve Device Integrity without the Magisk.

But if you install Magisk, you have to hide Magisk and Zygisk by your own

So yes, you can use Shamiko and it should work (I used that kind of setup at the beginning of this year, for like two weeks, with no problems)

But then ask yourselves - what for do you need Magisk. If using like Viper4Android, useful LSPosed modules - then, yes

If not, better uninstall Magisk and you will only have Xiaomi.eu injector. Btw, yes, it is rather injector than a module, it's full name is XiaomiEUInject

Regarding the prints - there are now no more publicly available working prints, hence a vast majority of rooted users use the prints 'stolen' from the Xiaomi.eu injector. When Google bans them, both sides will be equally affected. And assuming that Xiaomi.eu team quickly publishes their new version of injector, (last time it was in a matter of hours) with the new prints, all those rooted users will jump again to their new prints from tha new injector (new version of PIF was published less than an hour upon the Xiaomi.eu injecto was updated)

But if Google makes a slaughter like last time (now there are about 20 times less working prints than previously) and if Xiaomi.eu team does not come up (quickly) with the new injector (and the new working prints), than better don't think what could happen.

Btw, Wallet can run about half a day on the cached previous Play Integrity pass

Hence, with the Xiaomi.eu injector or with PI Fix (with its built-in prints), PI Fork with the corresponding autopif script, etc, you are equally exposed to the Google's mercy

Therefore, if you really need Magisk, you can also keep using the PI Fix/For with the disabled Xiaomi.eu injector. It will be easier for your maintenance than to struggle with both worlds in parallel (although, that can work as well)
[Magisk] waldmax:
Thanks for your reply!

I have some Soundprofile & Tasker Jobs with require Root for convinience.

I have already on my old Poco F2 Pro xiaomi.eu ROM + Injector + Magisk - no PI and is working well.

Will try the same with Xiaomi 14 Ultra step by step. First ROM + Injector, test banking Apps and NFC payment and then I will root with Magisk 26.4 and hide Magisk again.
[Magisk] ctcx:
I'll go briefly offtopic, with the topic of zero-padding boot images, if I'm allowed.

I know the post is from one year ago and it was already discussed back then; I just thought I could propose few ideas for scripting both padding and un-padding, now that I briefly went a bit into the topic...

First, some od command nearly exact equivalents:

hexdump -C boot.img | tail
od -A x -t x1z boot.img | tail
xxd -a boot.img | tail

Though yes, probably in the case of the od command it's a bit more useful with "-A d" option

Now, to display the next one byte after byte number <n>:

hexdump -e '1/1 "%02x"' -s <n> -n 1 boot.img
od -A n -t x1 -j <n> -N 1 boot.img | tr -d ' '
xxd -s <n> -l 1 -p boot.img

Finally, proposing for un-padding:

TOT_SIZE=$(wc -c boot.img | awk '{ print $1 }')
REV_OFFSET="1"
LAST_B=$(od -A n -t x1 -j "$(( $TOT_SIZE - $REV_OFFSET ))" -N 1 boot.img | tr -d ' ')
while [ "$LAST_B" = "00" ]; do
: $(( REV_OFFSET += 1 ))
LAST_B=$(od -A n -t x1 -j "$(( $TOT_SIZE - $REV_OFFSET ))" -N 1 boot.img | tr -d ' ')
done
echo "$(( $TOT_SIZE - $REV_OFFSET + 1 ))"

This returns the last byte number before all the zeros towards the end of file. If there's no tailing zero-padding at all, last byte will be just file's size in bytes.

Now, to perform the actual un-padding, and also padding itself if desired, one can use dd tool, like already mentioned.

All this was tested also in Busybox, except xxd because this one is not included there.

Outside Busybox, there this command "truncate -s" as well for both padding and un-padding.

Hope I didn't bother too much.

Thanks.
[Magisk] HippoMan:
I'm now having a problem hiding the TJW Magisk 27002 app ...

I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

(1) Unhide Magisk

(2) Update Magisk (27002 was listed)

(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot

(4) Magisk 27002 indeed came up properly after reboot.

(5) Tried to perform Hide The Magisk App.

I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

What am I missing?

PS: Even if I try to hide using the "Settings" name which is specified as a default, Magisk still doesn't get hidden after clicking "OK" in the "Hide The Magisk App" dialog.
[Magisk] bombadier:
Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about it
[Magisk] Lughnasadh:
Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.

EDIT: Ninja'd 🙃
[Magisk] HippoMan:
Oh, thank you!
[Magisk] HippoMan:
Sorry ... I missed that in my earlier search. I'll use the debug app. Thank you.
[Magisk] Jaitsu:
Is the Magisk 27001 APK/zip still available anywhere? I'd like to downgrade, but I can only find 27000 on Github and 27002 via update. I don't want to go to Canary in case the mounting changes break anything, or Debug as I hear the extra logging etc. causes performance issues (correct me if I'm wrong).
[Magisk] zgfg:
Only v27000 is Stable. (and Beta). v27001 and v27002 are Canary or Debug

Set your Update Channel to Stable and you will see (just like you can see also on GitHub) that latest Stable is v27000, there was never Stable v27001 or v27002

Generally, Stable is always Nx100

So, you cannot downgrade to Stable v27001 but Canary v27001 should be just like Stable v27000 (same codebase). That's also the general policy, whenever Nx100 Stable is released, then immediately comes Canary Nx100 +1, on the same code-base

Therefore, downgrade to Stable v27000 instead
[Magisk] Jaitsu:
Gotcha. I misread a bit and was thinking Canary already had a new build out with the mount changes. Forgot I was already on Canary. 😅 And didn't realize 27001 = 27000, interesting.
[Magisk] pndwal:
Yeah... This has veered OT for PIF thread though, so moving conversation here (as I should have done earlier)...

To be clear, this is really about installing/updating Magisk using Recovery mode for some "Ramdisk = No" devices, "Late 2018 - 2019 devices that are A-only. The worst type of device to ever exist as far as Magisk is concerned." (A-only and L-SAR, launched with Android 9) and is not PIF related...

I last asked (in PIF thread):

Your deleted response was:

But

you are removing your Magisk-patched recovery.img (recovery mode Magisk) by flashing standard TWRP

!!!

Remember, Magisk resides in the /recovery partition in case of Galaxy S10+ etc unlike standard Boot mode Magisk installations!

So you could patch the TWRP .img file you have to inject magiskinit in recovery ramdisk... (This can work after a standard initial Magisk installation in AP and flash via Odin with other binaries incl. CSC for data wipe.)

Or assuming you don't need TWRP (and I don't know why you would want it, especially as "You CANNOT use custom recoveries to install or upgrade Magisk in this case!!" and you should therefore NOT be flashing .zip in TWRP as I keep telling you), simply follow official instructions and flash binaries (incl. AP patched via app w/ Recovery mode selected) with Odin...

Next (in either case) DON'T boot normally!...

Again, follow official instructions and do what I've told you; boot system via recovery:

Or as detailed in official Magisk Installation page:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

YOU MUST boot via recovery on your device at least once! After that you may be able to reboot to system with Magisk, but YOU WON'T have Magisk if you only boot up device normally. 🙃 PW
[Magisk] forserg:
Followed official instructions and flashed binaries (incl. AP patched via Magisk 27.0 w/ Recovery mode selected) with Odin and and booted to system with Magisk via recovery key combo. Got message to finish set up, I pressed OK. After reboot I have got Magisk, but it is still Magisk 26.1 which I uninstalled before, removed it via device settings, apps. How Can I completely delete old Magisk?
[Magisk] pndwal:
Not sure if you're taking about Magisk or Magisk App versions... Please post screenshot of Magisk app. PW
[Magisk] forserg:
:D
[Magisk] pndwal:
So appears you still have old Magisk app installed... If you patched with that, that's why you got old Magisk core installed... You need to update App first!

Patching is done with binaries from installed App (same version) since we got single-package Magisk in 22.0...

Also, to avoid issues with stub not being properly recognised, I suggest you take Restore the Magisk App option before updating App... Hide again afterwards. 👍 PW
[Magisk] zevozki:
Im using OnePlus 10 pro Oxygen 13. I fully wiped my device and magisk is gone. So the method patching boot.img with magisk app and fastboot boot boot.img is still valid with magisk ver2700 stable?
[Magisk] pndwal:
Wiping data or factory reset won't remove Magisk... Must flash back original images, eg by taking Uninstall, Restore Images option in Magisk App or by using fastboot...

fastboot boot boot.img doesn't work on all devices and won't install Magisk permanently... If it works, you can then take Install, Direct install option in App to install Magisk properly, otherwise use fastboot flash boot magiskpatchedboot.img

🤠 PW
[Magisk] forserg:
Restored, updated, flashed stock with patched AP, Rebooted with key combo, pressed ok to finish set up, after that App 27.0, but magisk still 26.1. I tried to updated Magisk through app (direct istall), reboot, bootloop "Samsung Galaxy S10+", Restored, updated, uninstalled, flashed stock with patched AP..... all the same result
[Magisk] J.Michael:
Have you changed your mind about whether to install Magisk in boot vs. recovery between these two versions of Magisk.

Given all the reports of problems installing v27, I don't understand why anyone is anxious to try. Wait for v28.
[Magisk] forserg:
The main reason for me to update Magisk 26.1 is simple, after google recent update I can't use my bank apps anymore. Modules installed: play integrity fix and shamiko, to update those modules I need at least Magisk 26.4. Magisk 27.0 just latest, that's all.