yashsingh1/xdaforums huggingface dataset:
[Magisk] Frans:
Sorry, my wording is indeed unclear.

I've uninstalled 26.4 verified that using Applist Detector. Then downloaded 27.0 from TopJohnWu github, that installs. When running it asks to install the complete manager, and when I do so it installs the full manager but when I start that one It still says on the overview screen that 26.4 is installed:

Note that this is after installing the 27.0 apk from TopJohnWu Github.

I suspect the update to the full manager pulled in the 26.4 version or it retrieves it somewhere from my tablet (although I deleted the magisk cache).

Pressing Update again does download the apik again but installing seems to fail. It returns very fast and no action seems to happen. UI stays the same.

And if I manually install the downloaded apk I get this

"App not installed as package conflicts with an existing package"

EDIT: after writing I was wondering if this could be related but it is a Samsung Exynos 7870 based device.

It supports arm64-v8a armeabi-v7a, armeabi ABI's

I installed root checker basic. This one prompts for root access and if I give it it reports back that I am root.
[Magisk] skorpiodav:
Now commands can find Magisk (attached results)

This is what happened:

Magisk was hidden, I updated to 27 and Rebooted.

After the Reboot the App (Magis Manager) returned the error "Since you lost the root, the hidden app cannot work, try to reinstall the App), I tried to reinstall by the option provided inside the App itself but it failed. I tried to reinstall manually the App (version 27) before removing the hidden App ("Settings") but the app showed "Magisk N/A" and I did not have root. I tried to uninstall the hidden app "Settings" (I did not have the option to unhide since the app did not start) without changes (still no root), probably I reinstalled the magisk App also after uninstalled the hidden app but I don't remember. Then I uninstalled the App 27 too and fixing with uninstalling and reinstalling by TWRP as I described.

Yes, I have zygisk-detach, but I had other modules too, I think another one to detach only youtube (don't rember if it was enabled) and one to hide magisk to some apps (Shamiko), don't know if I tried the "zygisk" hide option before Shamiko or just used that (now it working with only zygisk hide)

Could you please write down the procedure you used to fix after updating from hidden? Surely I will unhide Magisk in the future before update but it could be useful to have a plan B :)
[Magisk] pndwal:
... This one's getting attention now:

My device can't use the latest Magisk

👀 PW
[Magisk] rodken:
Maybe, if your method was utilized, it might prevent some headaches.
[Magisk] Wolfcity:
Check the modules I'm using in the attached screenshot.

Your second point: Sometimes magisk refused to unhide itself (I'm running a Xiaomi mi9t, maybe that's one reason).

In that case (as mentioned) look in settings - apps - name of the hidden magisk app and just delete it from there.

Reboot.

Now you may have no magisk icon on your home screen but the newly installed one in your launcher.

Everything I had to do was checking if it's installed correctly and hide it again (if wanted). That's nothing new, it's the usual way if you forgot to unhide before updating or magisk refused to do it by it's own.

If you get any problems with something like "magisk not installed" or N/A in the magisk app just reflash your patched boot image by fastboot and reboot. That should do the job.

In case you've updated your OS at the same time (very rare case) don't forget to patch the boot image from the firmware you're updating to.

Writing this on my way back from work, I hope I didn't forget anything serious.

If yes just ask again in the thread or per PM.
[Magisk] HJarausch:
On my resurrection remix 6.0 Samsung S5 the update from Magisk 26.3 to 27.0 broke my phone.

I can't boot my phone (boot loop) and I cannot boot into my recovery system to restore a backup.

What can I do to recover my phone.

Many thanks for a hint

Helmut
[Magisk] Spartacus500:
Enter TWRP and restore boot.img and the system will boot without root and the data will remain.
[Magisk] Wolfcity:
It seems he cannot boot into recovery. He said so.

@HJarausch : Download your current ROM (resurrection remix ), unpack it, take the boot.img and flash it by fastboot or in your case maybe with Odin.

I'm not a Sammy user.
[Magisk] J.Michael:
Perhaps you need to be more persistent in trying to get to recovery.

If you hold the power button down (a long time, minutes before giving up) do you get a shutdown menu?

From completely shut down, hold power until the first sign of life, then switch to holding one of the volume buttons until it gets to recovery or clearly has gotten past that. Then shut it eown again and try again with the other volume button.
[Magisk] nityam_kaushik:
This is thermal mitigation boost for nothing phone 2... My phone matches all the requirements but it says magisk 26.X is needed i have magisk 27.0 would it work??
[Magisk] J.Michael:
Usually when something says "requires Magisk 26.x" it means "at least v26". Ultimately, *you* will have to tell *us*.
[Magisk] nityam_kaushik:
Thnx i tried it worked already
[Magisk] HJarausch:
@Wolfcity

Thanks to all who helped to recover my S5 (RR) from a boot loop. Flashing boot.img using Odin3 safed my phone.

Now I have to install Magisk again. Currently, I don't dare to install version 27.0.

Since I have upgraded Magisk many times in the past (using the direct method) I wonder why the upgrade failed this time.

Has version 27.0 any known problems? Where can I find such a list of bugs.

Many thanks again

Helmut
[Magisk] Nergal di Cuthah:
Did you have modules, if so maybe one is not happy with the zygisk changes?
[Magisk] J.Michael:
A lot of people reported what sounded to me like what you described. I think every case came down to incompatible modules. I am less sure that they all suffered from the same module.

Unhide Magisk manager. Rename "/data/adb/modules", then delete everything else in "/data/adb" so the new Magisk will build a new database. Then try flashing the patched image.
[Magisk] pndwal:
User here with bootloop issue + link to 27 GitHub issue:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89331104

👀 PW
[Magisk] VelvetB:
Help fixing Magisk please. I have a moto E6 running Android 9 that had Magisk 23 and Orange Fox. I tried upgrading to Magisk 26 by installing it like a zip module. It now boots okay but Magisk crashes so I can't uninstall any Magisk remnants with Magisk but could with Android. I can boot to bootloader and adb is ok but Recovery is broken so no Orange Fox. I still have all the moto images, Magisk 23 patched images and Orange Fox image. So I could fastboot install any of those or try to install Magisk app 26 or 27 on phone and create new images. How should I try to fix it?
[Magisk] zgfg:
If you phone had a syndrome that Magisk app was displaying Randisk No, although you have separated Boot and Recovery, then some v26 versions (I always used only Canary, never Stable, but the same bug was in Stable - in later v26 Canary versions it was fixed but Stable upgrades less often and bugs stay longer) had the bug that Direct install or installations through TWRP broke Recovery/TWRP

If so, repair by reflashing recovery/TWRP from fastboot

Then upgrade from your previous Magisk version by patch and flash method, not from TWRP or by Direct Install

When patching, take care that you un-tick Recovery option that Magisk app will wrongly tick by default

Or use newer Magisk versions - I don't know was it fixed already in Stable v26.4
[Magisk] VelvetB:
It showed using SAR, Ramdisk no.
[Magisk] zgfg:
I said Ramdisk No, like on the screenshot (where I have Ramdisk Yes)

It's nothing about SAR = System As Root

PS: I see, you have edited and added that you have Ramdisk No. So try as described earlier by un-ticking Recovery while patching. And first restore your Ramdisk
[Magisk] thomasswan5547:
Wait SN doesn't pass with viper? or is it that SN doesn't pass with SE linux permissive?
[Magisk] Captain_Throwback:
Yes, just normal "Settings" i.e. com.android.settings. I just tried it on my A9 and was able to enroll successfully.

You also have to hide from Agent, of course.

Also, my SafetyNet passes all checks, so it seems you have an additional problem.
[Magisk] psychatog64:
I need help can I install this on my Google pixel XL ?
[Magisk] Captain_Throwback:
No.

P.S. Read the release thread.
[Magisk] psychatog64:
Why? Is it cause of the dual partitions on the pixel cause we have twrp and systemless root

---------- Post added at 12:43 AM ---------- Previous post was at 12:41 AM ----------

Yup just saw what you where talking about in the release thread didn't notice that before
[Magisk] HamsterHam:
For me sn doesn't pass with selinux permissive. With phh superuser and magisk I can't get v4a to work with selinux enforcing.
[Magisk] nohctis:
Anyone managed to make v9 work with Samsung Note 5 (N920I) ?

Stock Rom

Magisk V9

Phh 266-2 root

Hide enabled

Still cannot pass.
[Magisk] return.of.octobot:
Is there anyone here that can confirm or deny the compatibility of modules designed to write apps to system with V9, WITHOUT referencing app systemizer?

I've been using a personally written module to systemlessly flash a group of apps to system/app, system/priv-app respectively. This has worked flawlessly for me thus far. Yesterday, I flashed v9 on top of v8 and the module in question continued working fine and all my system apps remained intact. However, due to the conflicting reports I've seen I suspect that the next time I go to do a clean install using v9 right off the bat this module will fail and bootloop as many are reporting similar system app modules doing.

Everytime someone has asked this or a similar question, the poster has been referred to the App Systemizer module. That's a neat little module, sure, but I don't want to move apps that are already installed as user apps to system, I want to push apps that are not currently installed at all to system/app, system/priv-app.

Looking for a clean cut, potentially multi-part answer here, is this possible with Magisk V9, or is it not? If it is, will the previous method continue to work as it has or does v9 require a new implementation? If it does, are there any existing examples of this implementation available?

I'm a little leary about v9 in general, sure resetprop is a very cool addition but the fact that a large majority of pre-exisiting modules seem to break with little to no documentation available as to how to properly update them is a little disconcerting.
[Magisk] Nomelas:
So I have this set in config.sh:

# Set to true if you need automount

# Most mods would like it to be enabled

AUTOMOUNT=false

# Set to true if you need post-fs-data script

POSTFSDATA=true

# Set to true if you need late_start service script

LATESTARTSERVICE=false

Then this in post-fs-data.sh:

/data/magisk/resetprop --delete ro.qc.sdk.audio.fluencetype;

/data/magisk/resetprop persist.audio.fluence.voicerec true;

/data/magisk/resetprop persist.audio.fluence.speaker false;

/data/magisk/resetprop use.voice.path.for.pcm.voip true;

should that do it???
[Magisk] Captain_Throwback:
I probably use Magisk more than anyone else, and I have no issue with any module I've made that adds apps to system app or priv-app, with either v8 or v9.

I have not had to change any of my module zips, either.
[Magisk] dimm0k:
any suggestions on why Magisk v9 isn't able to flash any modules, whether it be custom or from the Downloads section? this was working fine previously...
[Magisk] Captain_Throwback:
None. Flashing modules still works perfectly fine for me.

In fact, since installing v9 and the latest Magisk Manager, I created and added a self-made Call Recording module for my device. It flashed with no issues.
[Magisk] westeight:
[MENTION=1162986]Captain_Throwback[/MENTION] Where can I download most of those Magisk modules?

They are not showing under the 'Download' section.
[Magisk] Captain_Throwback:
That's because they only exist on my device, lol.

Most of them are HTC 10 specific, so I didn't bother uploading them anywhere. And they're specific for my device's firmware in some cases, so I didn't want to break people's devices that shouldn't be using them.
[Magisk] :
Am getting this error log in twrp when updating to v9. V8 however works fine for me. Am using Huawei p8 lite. Any fix?
[Magisk] mycnam:
Magisk v9 will cause Pixel C to be in a recovery boot loop, i.e. the Pixel C will always boot into recovery, no matter what option chosen.
[Magisk] knipp21:
I still have the issue of losing root after a reboot. Riot lasts for about 30 seconds then I no longer get prompted when installing or dealing with new root requests.

Doesn't seem to effect apps already granted access
[Magisk] TotallyAnxious:
In regards to the not a module zip issue. The one module that wasn't working for me had all its files inside one folder and then was turned into a zip. Unzipping and rezipping with all files at the root folder fixed the issue. Not sure why the zip got changed but that fixed my issue.
[Magisk] dimm0k:
do you mind sending me that zip file just so I can see if it would flash on my end? I'm completely lost as to why I can't flash anything in v9...
[Magisk] TotallyAnxious:
Unzip whatever module you're trying to install. And post a screenshot.
[Magisk] SteweEliteModder:
Tested magisk v27.0 on the Galaxy S21 Ultra with latest firmware (G998BXXS9FWL9) and it works...
[Magisk] VelvetB:
Thank you
[Magisk] pndwal:
Did you sort that?... Interesting (rare) A/B legacy SAR device with recovery_a/_b it seems... May have some advice if you're still struggling... PW
[Magisk] bs3pro:
I can't believe lsposed is dead. No reason to root anymore. Wtf
[Magisk] badabing2003:
Fork works

GitHub - pumPCin/LSPosed: LSPosed Framework

LSPosed Framework. Contribute to pumPCin/LSPosed development by creating an account on GitHub.

github.com
[Magisk] bs3pro:
Getting shell error on qpr3. Guess it won't work on beta
[Magisk] zgfg:
If development was unfortunately halted it doesn't mean that the last version does not work - to the contrary, it works,I use it and I see no reasons yet to switch to the fork(s), alternatives or to not root
[Magisk] Cipcino81:
Hello again, I was wrong: it was not magisk 27 fault, it was Shamiko v.1.X that triggers play integrity. Now I have installed Magisk 27 with shamiko 0.7.5 and everything is fine. I have just 1 app that doesn't work so I would have liked to upgrade shamiko to latest version which have better hiding abilities. Maybe you know why version 1.X doesn't work for me ?
[Magisk] bs3pro:
The release version, and fork version are NOT working on QPR3 beta. Its my fault, not the app. Hopefully a newer version will fix it for QPR3
[Magisk] sawdoctor:
Have you tried the debug version from the fork? You should be able to get some logs for the developer using that. There's also an lsposed thread on telegram ( unfortunately it's full of pictures of cats and posts about Chinese new year ATM).
[Magisk] bs3pro:
I tried the TG thread, but its a shtshow. Root and mods are seriously starting to fade away. Its a shame.
[Magisk] amk316:
can any one test this app and see if it work in a rooted phone

it was updated today and stop working
[Magisk] Spartacus500:
It doesn't work for me either, it crashes when I run the application. Apparently, programmers are adding better and better security, neither Magisk 27.0, nor Lsposed 1.7.2, nor HMA, nothing helps 🙄
[Magisk] IronTechmonkey:
Issue with app on deny list after update from 26.4 to 27?

Stock Moto G Power 2021 Android 11, Magisk 26.4 (app and core), Magisk hidden with Zygisk and Deny List enabled, and 2 apps in deny list

> updated Magisk app and core from 26.4 to 27 within Magisk app

= an app for which deny list previously worked well now will not run.

I've tried restoring the original Magisk app and renaming it with a unique previously unused name to no avail. I'm considering temporarily removing Magisk and root from the device then reinstalling Magisk (perhaps going back to 26.4, if possible) but, considering some recent feedback here I'm hesitant to try those things. Any suggestions would be appreciated. Thanks.

[EDIT] FWIW Diagnostically I will a similarly configured Moto G power 2020 Device which is still running Magisk 26.4 and on which the same app is allowed to work by the deny list. That is how the affected device described above functioned before the recent update.
[Magisk] IronTechmonkey:
FWIW, This app force closes immediately upon start on two devices. One is the device described in previous post which has new problems caused by the update to Magisk version 27. The other device is one which is still running Magisk 26.4 on which hiding the root from apps functions properly. Since you mentioned that the app was updated I think that in this case the issue might be with the app but that the other issues being reported with Magisk version 27 are with Magisk itself.
[Magisk] IronTechmonkey:
Regarding potential issues with Magisk 27 and deny list: Although there are no apparent new reports and github about this, the fact that this update substantially changed Zygisk and a few other people in this thread seemed to have had problems with it, and there is no indication of my devices falling out of supported range this would seem to be a bug or glitch rather than simple configuration issue. Could it also be app specific?

I will before long revert back to previous version of Magisk by removing root and uninstalling Magisk then reinstalling it with boot image created through installer for version 26.4 (please correct if wrong) but if there is interest in reporting the issue I can try to do so first.
[Magisk] Wolfcity:
As @zgfg said, that may be right but must not.

My device (Xiaomi Mi 9T, @zgfg owned the same model as far as I know) shows the same but magisk has to be installed into boot.img, not recovery.img (what you should expect).

Follow the steps he showed you in his response and flash and patch by fastboot.
[Magisk] J.Michael:
Instead of uninstalling Magisk, you might get away with renaming magisk.apk to .zip and installing it as a module in the manager app.
[Magisk] zgfg:
Yes, that was my point - if his phone shows Ramdisk No, he has to patch boot.img with disabled Recovery option that Magisk v26 will wrongly enable by default, etc... (I'm lazy to repeat, I posted him detailed instructions how to recover his broken Recovery and how then to patch and flash)
[Magisk] IronTechmonkey:
Interesting, but a catch - Magisk core on device is 27 which seems incompatible with app version 26.4. Built in updater offered app 26.4 to 27 first then only after app was updated to 27 did it offer core update 27. Also, in Magisk 27 manager, I Attempted to use custom update channel pointing to the web page for 26.4 - raw which did not install. As far as I can tell, in order to resolve this I will have to get the core back to 26.4.
[Magisk] SaidJan:
Mine was saying partially activated with latest 1.9.2

With this 1.9.3, it's fixed. Thanks 👍🏻
[Magisk] J.Michael:
If it works, you start with Magisk 27 and Magisk manager 27, install a new Magisk module, tell it to use the magisk-26-apk.zip, and it magically installs Magisk 26 -- bypassing certain downgrade restrictions. At that point you have Magisk 26 but manager 27, so I think it would make sense to uninstall the manager and install the 26 manager.
[Magisk] IronTechmonkey:
Ahhh, got it. So, that would install Magisk core 26.4 in addition to manager 26.4. Thanks for the tip. I'm going to wait a few days to see if more people report this and whether or not it is an issue likely to be addressed or some new limitation. Thanks again.
[Magisk] J.Michael:
I don't think installing the module affects the manager. Replacing the manager is a separate step.
[Magisk] IronTechmonkey:
The effect being, that I go from 27 of both to 26.4 of both.
[Magisk] pndwal:
Since 22.0 ("Magisk Manager is dead. Long live the Magisk app!" version) we've had single package Magisk... Binaries (core/mask) installed are the same version as the App installed...

Since then only the App is affected by the update JSON... App will say Update Magisk simply if core binaries are older than the installed App/package...

Since then @vvb2060 has added several features to protect users from themselves and from nefarious/malicious Magisk builds, and in particular anti downgrade (version checks) and anti non-matched Magisk (app signing checks) mechanisms cause confusion as in release builds Magisk’s root daemon will reject and forcefully uninstall any non-matching or older Magisk apps "to protect users".

You can bypass this behaviour by restoring unpatched boot.img of course, but you can still use existing root to to get your preferred Magisk App installed as I described For any wanting to downgrade, or change between Magisk forks from different Devs, or to CI builds from Magisk Actions etc here:

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

The Install Magisk as a module method has been mentioned above.

🤠PW
[Magisk] IronTechmonkey:
Thanks to you and @J.Michael for the input. One point of clarification: I previously misstated but I am actually using the current magisk app. I only referred to it as manager because I had seen that somewhere in the thread. As to the rest, it's clear that there is a way to do this without completely removing root and reinstalling Magisk but then I have this question. I sometimes refresh the stock ROM on the device which incidentally removes root and then I reinstall magisk so I'm comfortable doing that. Apart from the fact that root is maintained by the method you described, what other reasons would there be to use that method rather than remove root or refresh the device then reinstall magisk?
[Magisk] pndwal:
Sorry, not sure what "to do this" is... To fix issues?....To downgrade?... You can certainly downgrade while maintaining root, and clear any incompatible Magisk configuration also (forcing configuration rebuild, effectively restoring fresh installation).

Yes, installing a full ROM overwrites patched boot image...

Not much... Just a way to downgrade using existing root like upgrades and without needing PC connection, ie. using direct install (via Debug builds) or .zip installer scripts (install as module)... Removing both root and potentially corrupt/incompatible /data/adb configuration then reinstalling will be just as effective.

I don't think the move to native bridge loaded Zygisk is causing any issues. This has been a WIP in @yujincheng08's (LoveSy, Shana) LSPosed Metagisk fork since March and was well tested in Alpha and of late in TJW Canary. (For comparison, Delta fork used old Maru based NB-Z POC much earlier, and while benefiting from better injection hiding it had issues as the implementation was not being improved... Anyway, Delta/Kitsune has now moved to ptrace + fuse loaded Zygisk from the same Dev.) Native bridge is also the injection method adopted by @RikkaW's Riru years ago ('discovered' by @canyie) when refactored for proper hiding (RiruHide), so it's basis is solid and long used.

The issue getting attention for latest Magisk seems to have resolved itself into a problem for phhusson GSI's; phh GSI unmount magisktmp and is now simply labelled "not our issue" and "wontfix"... Not sure why Magisk Devs haven't answered his query here:

https://github.com/topjohnwu/Magisk/issues/7780#issuecomment-1937400721

... Maybe they just aren't aware of who this legendary Dev is?... but I can't imagine that...

If you can narrow down further issues with 27001 it would certainly be valuable to have a proper issue opened... Several are reporting issues with that and Shamiko, possibly LineageOS related, but you'll need to identify issues definitively, provide logs immediately using latest Debug build (don't use public builds), and be prepared to follow thru with requests for further logs, test CI action builds etc if needed. (I may be stating the obvious here, but just in case...)

🤠 PW