yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
Do you have any idea whether you have root capability? The best case is the first screen of the Magisk manager app saying that Magisk is installed. If the manager is locked out because of another instance of the manager, I think you would still have root capability, and would be able to find signs, like apps that had already been granted root privilege would continue to have that privilege, or an executable named "magisk" would be available on the command line.

Can you see the contents of the /data/adb directory? Can you delete it? Maybe the change in Magisk version is so great that you need to delete the old Magisk database and let Magisk build a new one.

Where did this bash script come from? Were you supposed to adjust it before running it?

Can someone explain to me the sense of burning several images to the same partition? ("cust" and "super") How is that different than just burning the last image to each partition?
[Magisk] devand11:
Ok sorry, I missed the screenshot request.

Yes, after flashing the patched image Magisk is shown to be installed in the manager .

I'm quite sure that last time I did not hide the app at all.

With the patched image, I do have root access: Adaway works and root explorer as well. Went to Magisk manager, deinstalled the only module which was active (seemless something) and removed the manager, rebooted again. But the warning messages keep popping up and Google doesn't work.

Tried to install Magisk again and here it asks whether I would like to upgrade (1.0 -> 26.3) so I guess you are right and there is a hidden app :( So I did not upgrade but in the app drawer there is now an app Magisk with a strange icon (looks similar). When starting it, it asks whether I would like to fully install magisk. Instead, I de-installed that app, rebooted again. But it keeps coming back. It's probably a feature when detecting a patched image..?
[Magisk] devand11:
I do not have a folder /data/adb. Only data/app, data/data and data/user

The bash script comes with the device-specific package and does not need to be modified or adjusted:

MIUI 14 - MIUI 14 STABLE RELEASE

Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...

xiaomi.eu

So far I never experienced any issues with these stable ROMs (14-06, 14-09) in combination with Magisk. And I did always use the latest Magisk version.
[Magisk] badabing2003:
That's correct, the latest version creates a stub with version 1.0 so that you can easily install / upgrade the manager.

This happens when the app is uninstalled but the boot partitions is patched.

One other thing to pay attention to is if you patched the matching boot.img / inint_boot.img and and are not flashing some other boot's patch..

You need to su to root to see /data/adb
[Magisk] zgfg:
You must have adb and tens of other folders on /data

Seems you are looking with an app (file mngr) without the root grant

Edit:

Btw, I'm also on Xiaomi.eu, MIUI 14 Stable (Mi 11 Lite 5G NE)

First time I installed with their script and later (two Xiaomi.eu upgrades) upgraded by Updater and TWRP

Always patched the boot.mg and flashed

And never had a problem (updated also Magisk many times - now on the latest Canary 26302)
[Magisk] zgfg:
Have you downloaded and installed the Magisk Canary app and installed it (if I recall, that's your Magisk version)?

And did you maybe play (now or earlier) with the Settings / Hide Magisk app option?
[Magisk] zgfg:
If you switched to Xiaomi.eu Stable from Xiaomi.eu Weekly or from any other ROM, you had to use First time script - ie, you had to Format Data / Factory reset (that's clearly written in the post #1 instructions on Xiaomi.eu Forum)

Only if you already had Xiaomi.eu Stable and you upgraded to the newer Stable version, then you will use the script that does not Format Data

So please check that - without Formatting Data you still have some mess from before switching to Xiaomi.eu Stable (if you switched to Stable without formatting Data)
[Magisk] J.Michael:
How did you "Went to Magisk manager, deinstalled the only module" when "modules section in magisk manager is grayed out"?

If Magisk manager says Magisk is installed, then the one problem you are not having is a misplaced, renamed, manager.

Point of fussy: Nothing is "detecting a patched image". Magisk *is* the patched image. If Magisk is running, it's because you booted a patched image. Magisk is detecting that you do not have a manager app, and so is installing one.

Go back to where you got the ROM and ask if anyone has installed Magisk, and which partition gets patched. Maybe ask specifically if vendor_boot should be patched.
[Magisk] devand11:
I already came from a stable version. Same procedure as last time when I upgraded from 14-06 to 14-09
[Magisk] devand11:
Sorry, my bad, the section is only grayed out in the unpatched version of course (the one with google warnings).

In the past I always patched the boot.img and not the vendor_boot (at least the name was boot.img all the time).

I will try to get some info from the ROM guys. And I will try to go back to 14-9 in order to have a working phone until I find a solution.

Thanks a lot for your support, I really appreciate that!
[Magisk] devand11:
yes, it's the 26302. Just noticed that the magisk manager closes itself after some seconds of not doing anything.

I did not hide it this time. Also I did not install additional modules if I remember correctly.
[Magisk] devand11:
I checked again with root and I do have the following folders in data/adb:

magisk

modules

post-fs-data.d

service.d

plus a file called magisk.db
[Magisk] J.Michael:
What are "google warnings"?

If you get google warnings before you have tried to install Magisk, why consider them a Magisk problem?
[Magisk] devand11:
Right after booting with the patched boot.img I get warning popups that Google play services keeps crashing. Without the patched image there are no warnings (and no root :D).

I'm not an expert and I don't know if that's a ROM issue or Magisk or a general Android one. Just trying to find a solution.
[Magisk] zgfg:
Please show the screenshot of your modules. And DenyList
[Magisk] J.Michael:
"the section is only grayed out in the unpatched version of course (the one with google warnings)."

???
[Magisk] pndwal:
Assuming you are patching/flashing boot.img extracted from current XiaomiEU ROM (Nb. Problems occur if a mismatched boot image is used), I suggest forcing a rebuild of Magisk configuration files which may have become corrupted...

Nb, an initial (clean) setup can be obtained by reinstalling after taking in-App Uninstall Magisk --> Complete Uninstall option but isn't necessary... With root, simply delete all contents of /data/adb then reboot... Magisk will rebuild fresh/clean configuration...

Of course you'll need to reinstall modules (but any corrupted configuration for previous ones will be gone), re-select denylist entries, allow Superuser permissions again etc, but issues with incompatible magisk.db etc from previous versions will be eliminated...

Hope it helps, 🤠 PW
[Magisk] zgfg:
Oh man, you're alive😀
[Magisk] devand11:
Yes, sorry that was wrong and led to the misunderstanding. It's the patched one which shows the messages.
[Magisk] devand11:
I will do so and try from scratch. Thanks a lot!
[Magisk] Applyingmore:
Is it possible to get rid of safetynet on emulators? I have tried many with the usual steps to bypass safetynet on most of these emulators and none of them work
[Magisk] RaWPuNdiSh:
No, you can't.
[Magisk] crapa:
Has anyone managed to root Xiaomi 13T Pro (Redmi K60 Ultra)? I searched Internet and couldn't find something.

If yes, can you post instructions?
[Magisk] pndwal:
If you mean to pass SafetyNet/Play Integrity verdicts, yes it has been done... See this POC:

https://xdaforums.com/t/info-play-integrity-api-replacement-for-safetynet.4479337/post-89125128

👀 PW
[Magisk] devand11:
I went straight to the "complete uninstall" option and this one finally worked :)

Thank you sooo much guys, you saved my weekend! Really appreciate that!
[Magisk] zgfg:
Magisk v26.4​

Repository: topjohnwu/Magisk · Tag: v26.4 · Commit: 6c807d3 · Released by: topjohnwu

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

Full Changelog: here​
[Magisk] pndwal:
Latest official Canary & Debug Magisk:

Magisk (aa6c7c15) (26401)​

Sync with public release

Diffs to v26.4​

N/A

👍 PW
[Magisk] pndwal:
From OP/Author (Newly pinned):

www.twitter.com/topjohnwu/status/1721431805478519209

Also:

www.twitter.com/topjohnwu/status/1721432694889095561

👍 PW
[Magisk] matfcb:
26.4 stuck at Miui logo. I had to do unroot in TWRP to have phone working at work. Did it remove root only or uninstalled my modules as well? I will install at home 26.3.
[Magisk] pndwal:
So Apparently Fix fd sanitization (topjohnwu committed 5 days ago) is still broken...

It apparently included @canyie's closed fix: Fix fd sanitization which also apparently works properly in Alpha Magisk but the TJW fix needs work...

👀 PW
[Magisk] pndwal:
No new issues yet, but this from Alpha (Chinese) discussion:

lovesykun = Master Xi

aviraxp = Qianqian

canyie = Xiaoyeye

👀 PW
[Magisk] HippoMan:
Google Translate results for the original Chinese:
[Magisk] zgfg:
Please shortly in plain words, what is the corresponding bug/issue to be seen on the user side?

Thx
[Magisk] pndwal:
Per @canyie's linked PR,

Fix broken logic introduced by commit 79a1c39 which modify fds_to_ignore when android_log_close is called, where fds_to_ignore was already read and converted into a C++ vector, so our hacks never take effect. This fixes Zygisk's FD sanitization broken on 26302 #7448

The previous logic rely on android_log_close to close logd_fd in zygote and causes logd_fd being closed and re-acquired too many times. Update fds_to_ignore in zygote process as well to avoid that case.

The issue linked above (#7448) - to be fixed - was originally entitled "Apps not working properly" and details were given for Duolingo, Soundcloud and Chrome...

Seems these issues with other symptoms are duplicates:

- After update , SoundAssistant on Samsung not working properly and lsposed too #7453

- Apps are crashed when they are in denylist #7468

Samsung and Xiaomi devices are represented...

Yeah... So for clarity, "zygisk fd is still broken, don’t use it... There are no new features or new fixes from bb39a524-alpha to TJW-26.4 anyway. Since alpha has already correctly fixed the fd problem (and the latest build is good) the version based on latest TJW release will not be released until the official channel fixes fd sanitisation issue... It (the new TJW release) doesn't have anything new except new bugs to offer (considering that this issue is already fixed and the other changes are already implemented in Alpha)...

👀 PW
[Magisk] zgfg:
Ok, thanks. Seems something specific to particular devices/ROMs/apps and maybe to A10 (I see that detail in common for both tickets)
[Magisk] mkcs:
Home launcher crashes after I upgraded to official 26.4, sadly the stable versions are no longer stable after version 26
[Magisk] woozie.2007:
After upgrade magisk from 26.3 to 26.4 my phone xiaomi mi 9t its unsuable because i don't have signal, i can't do anything on it, i reverted to 26.3 but my mobile banking doesn't work anymore, what can i do please? Thank you
[Magisk] Lord Sithek:
:LOL: true, all of them are stay-away-able
[Magisk] dosbuddy:
same here (Xiaomi Poco X3 NFC, on 12.5.8 xiaomi.eu-ROM)

Reverted to 26.3, including "play integrity fix" so safetynet passed and banking apps are working again.
[Magisk] woozie.2007:
what is play integrity fix? safetynet passed for me too
[Magisk] dosbuddy:
because of my "old" ROM, I have to use "play integrity fix", you will find it here on XDA.
[Magisk] woozie.2007:
i tried now and it is the same, the banking apps don't work anymore, even the safetynet passed
[Magisk] dosbuddy:
With appropriate configured and forced deny list and zygisk enabled?
[Magisk] woozie.2007:
yes
[Magisk] dosbuddy:
It may help to hide the magisk app. If that does also not succeed, I have no more ideas...

ok, one more: try to freeze the magisk app (by "titanium backup", or "ice box")
[Magisk] woozie.2007:
i did hide the magisk app, i always did, otherwise the banking apps don't work, but they worked perfectly until this update....
[Magisk] woozie.2007:
i don't have twrp installed, i only use the magisk app for root, with patched boot img
[Magisk] woozie.2007:
i uninstalled magisk with restore image and all work good, but not some apps which depend of root
[Magisk] pndwal:
Did you check Play Integrity DEVICEINTEGRITY verdict passes (using Play Integrity API Checker, inbuilt Play Store checker w/ it's Developer options enabled, etc) again since reverting?.... Nb. SafetyNet API is deprecated and banks have migrated to PI API now...

If no DEVICEINTEGRITY you may need to wipe Google Play Services data or disable your USNF/PIF solution, reboot, re-enable, reboot again...

If have DEVICEINTEGRITY, may not need to clear Bank app data and set up again...

🤠 PW
[Magisk] woozie.2007:
i don't understand exactly what you mean, please tell me what to do step by step if you want of course, thanks
[Magisk] pndwal:
Simple way: get Play Integrity API Checker from Play Store and run it...

Next, depending on results an assuming you know how to clear app data, follow the steps above...

You may also need to install a (different) forked build of USNF that allows MEETSDEVICEINTEGRITY if your current solution isn't working properly...

🤠 PW
[Magisk] woozie.2007:
i have 3 results, 1 its ok 2 its ok and 3 isn't....

meets_strong_integrity failed

is there anything i can do?
[Magisk] BillGoss:
That's fine. You'll always get 3 failed if you've unlocked the bootloader.
[Magisk] zgfg:
Nothing related to Strong Integrity with unlocked BL and modded phone
[Magisk] pincopallowfs:
Hello, please I'd be very grateful if anyone has suggestions...

I updated magisk to v26.4 on my mix3 running a miuimix based on Android 10, everything went perfectly. I updated magisk to v26.4 on my k20 pro running a miuimix based on Android 11 and after restarting my phone was showing the lock screen but there was the icon of the missing sim, swiping to unlock the screen took me to a black screen and after a while a pop up said system.ui was not responding, taking down the notifications drawer there was no wifi and all the slots for Bluetooth, sim, wifi and so on were blank . I assume there was something wrong with the system apps and something even deeper about the missing sim which of course was inserted. Rebooted to twrp, flashed magisk v26.3 zip and now everything is working again... Though I'd be happy to be able to update magisk... Any suggestion maybe?

Thanks...
[Magisk] mkcs:
Same here on Redmi K20 Pro xiaomi.eu 12.5.6. Magisk v26.4 is buggy, revert to Magisk Canary 26302 works fine.
[Magisk] rocagi:
I have the same problem, after successfully updating to 26.4, it stops showing the SIM PIN screen, and just shows the phone unlock screen.

Once unlocked, the screen is black and just shows the time and that I have no SIM at the top.

Restore the 26.3 boot and problem solved.

In github there is a user issue with the same problem, but it has been closed due to lack of reposting an error, but how do you do that if the phone doesn't work?

Device: xiaomi mi9

Android version: 11 (xiaomi.eu 12.5.6)

Magisk version name: 26.4

Magisk version code: 26400
[Magisk] pincopallowfs:
Yeah, it seems something related to xiaomi on miui android 11...

I too wouldn't know what to post to help tracking down the problem...
[Magisk] WANTEDJAAT:
@pincopallowfs @rocagi @mkcs
​

No Its Not any Device Specific Problem..

My LG Phone Also Got in Same Problem Stuck & stopped showing the SIM PIN screen and after opening showing Black Screen.

I also Downgraded to 26.3

@topjohnwu requesting you to Please Look into the issue..​

​
[Magisk] pincopallowfs:
Don't know, my mix3 on Android 10 updated flawlessly...
[Magisk] pndwal:
... New fix proposal:

Prevent Zygisk from closing new fds created by Zygote itself

#7487 opened 5 hours ago by canyie

👍 PW
[Magisk] J.Michael:
@rocagi @pincopallowfs You need to post on github to have any hope of bringing this to the attention of developers.

Somewhere on github (probably near the Magisk thread) will be a list of what they want.

The first step will be locating the latest debug / canary build, installing it, collecting a log file.

Given the speed at which some of these developers move there's a chance you will not be able to reproduce your problem. In that case post that your problem seems to have been fixed and just use the debug build.
[Magisk] pincopallowfs:
An issue regarding this matter has been closed due to the lack of provided details. But I don't know how to extract details from a phone that doesn't work, also after reflashing 26.3 I can't find the relevant logs.
[Magisk] J.Michael:
You described some functions not working, not being unable to boot.

Try connecting to a PC with a cable. That should allow you to retrieve files. The most important file will be the log file created by the debug Magisk. Start by checking the Downloads directory.
[Magisk] zgfg:
Which Android version is yours (On Xiaomi they had A11)?
[Magisk] pincopallowfs:
Some function including system.ui not working, so it's a bit tricky to operate...
[Magisk] domcars0:
Same on my Redmi Note 9S MIUI 12.5.3 , revert to Magisk v26.3
[Magisk] pndwal:
Of course if anyone wants to try Canary 26401 with @canyie fix, CI build is available from Magisk GitHub actions:

Prevent Zygisk from closing new fds created by Zygote itself Magisk Build #3658

This only builds Prevent Zygisk from closing new fds created by Zygote itself on top of Canary 26401 commits... I'd be interested if the app/UI issues are all gone with fd fix... I'd try but Alpha (fixes earlier) is working fine for me...

🤠 PW
[Magisk] shohabmsk:
Hello, im getting bootloop on my Samsung A13(android 13, OneUI core 5.1), with Magisk 26.4! Magisk 26.3 worked fine.
[Magisk] pndwal:
FWIW, @canyie has just committed her improved file descriptor sanitization logic fix in TJW Magisk master:

Prevent Zygisk from closing new fds created by Zygote itself

canyie committed 3 hours ago

This is good news... Other merges just in are more exciting however:

Refactor hookJniNativeMethods …Utilize NativeBridgeRuntimeCallbacks we obtained from native bridge to directly fetch and modify registered native JNI methods. By doing so, we do not need to keep a copy of every single JNINativeMethod registered in order to provide JNI hooking functionality.

Co-authored-by: LoveSy <shana@zju.edu.cn>

topjohnwu and yujincheng08 committed 4 hours ago

Obtain NativeBridgeRuntimeCallbacks for future use …

NativeBridgeRuntimeCallbacks can be used for better JNI method hooking

Co-authored-by: topjohnwu <topjohnwu@gmail.com>

yujincheng08 and topjohnwu committed 11 hours ago

Refactor zygisk to use native bridge to inject …

Co-authored-by: vvb2060 <vvb2060@gmail.com>

Co-authored-by: topjohnwu <topjohnwu@gmail.com>

3 people committed 14 hours ago

Guessing 26402 may be early release 27.0 w/ NB loaded Zygisk... Or (just possibly) a 27.0 public beta release may be next...

I'll be moving back to official Magisk very soon by the looks... Official Magisk + Shamiko will be the go again with (hideable ) NB-Zygisk merged...

And alternative ptrace+fuse loaded Zygisk in ZygiskNext may be another module to try/watch...

👀 PW
[Magisk] rocagi:
I tried with debug and canary version aa6c7c15 (26401) and same problem.

Since I can't do anything other than see a black screen and restart in recovery, I've restarted in recovery, I've connected it to the PC in order to find a LOG in the downloads folder, but there's nothing there.

So I'm back again to version 26.3, I don't know how to help with this problem.
[Magisk] J.Michael:
I was just guessing about where the log file would be.

Do you have any modules installed? If so, try deleting or disabling all modules before installing 26.4.

Or, having installed 26.4, try booting to Safe Mode, then reboot and see if UI is better.

Or, with 26.4 installed, connect to PC and maybe ADB will be able to access the directory (whose identity I do not know) where the Magisk log is.

@Didgeridoohan had an extensive write-up on logging in Magisk, but I can't find it now.

Maybe if you post on github a problem description with a request for instructions on how to locate the log, someone will answer. Maybe like XDAforums there is a special place to post general questions.
[Magisk] Lughnasadh:
Is this what you're referencing?
[Magisk] J.Michael:
https://www.didgeridoohan.com/magisk/MagiskHideHelp

https://didgeridoohan.com/magisk/MagiskHelp

It is indeed.

(Operator error: I found a link to MagiskHelp, which would have worked as well as MagiskHideHelp if I hadn't reflexively clicked "Stop! Do not allow" when I got an Invalid Certificate warning.)
[Magisk] 911-Future_Maker:
Same with magisk 26.4 on poco x3 pro miui 12.5 A11 everything was crashing i was freaked i lost everything on my phone and i need full wipe. xD
[Magisk] Utini:
I just re-rooted after updating A14 to November build.

After the boot (right after rooting) I noticed that some root request was automatically rejected by magisk.

This is part of the log. Does this look okay or fishy?
[Magisk] Varrkan82:
Same problem on same device and ROM with Canary version if Zygisk enabled. After disabling Zygisk and upgrading to 26.4 - all works. If enable Zygisk again on 26.4 - problem returns back. Downgraded to 26.3. Waiting for fix.
[Magisk] pndwal:
"New and more exciting stuffs for v27!" merged already:

The next official Canary or public Magisk build (with 'massive' refactoring, particularly the move to native bridge loaded Zygisk from Metagisk fork like Alpha) will bring major changes and fix some stagnant issues...

Refactor zygisk to use native bridge to inject …

Co-authored-by: vvb2060 <vvb2060@gmail.com>

Co-authored-by: topjohnwu <topjohnwu@gmail.com>

3 people committed 2 days ago

And just now we also got:

Zygisk refactoring part 2

topjohnwu committed 3 hours ago

(Fun fact: Original native bridge loading implementation, which was actually a first for Android code full stop, was from @canyie and used by @RikkaW for Riru.)

... As long as we still have working USNF/PIF, 27.0's gonna be HUGE folks!... Coming to a device near you... Soon(ish)...

It will also fix a raft of other Magisk issues, even 'wontfix' ones... Eg Zygisk should now start working on Samsung devices like S7 and S8 with stock kernel/ROM as kernel won't be incompatible any longer... These are the advertised reasons for NB-Z adoption...

🤠 PW
[Magisk] boltes:
I have exact the same problem (identical setting).
[Magisk] kaodd:
hallo guys

i'm a blast from the past and have'nt posted since idk around 2016 (not even sure 😃)

my problem is - i can't flash nothing with magisk, get the same message everytime.

device: moto g5 plus, rooted with magisk, rom arrows 10. everything's working fine, even pass safetynet.

have tried and bricked and again and again now I'm tired. please help!!

the last time i rooted was with CHAINFIRE SU!! so I'm not very familiar with magisk.

here is the message:

-device platform: arm64-v8a

-installing: 26.4 (26400)

-processing zip file

! no boot image found

! process error

! installation failed