yashsingh1/xdaforums huggingface dataset:
[Magisk] osm0sis:
A-only FBE should work on its own as long as /data/adb is accessible for the addon.d script, I think it's just A-only FDE that remains unsupported.

As for when to reflash Magisk in recovery, it'd only be necessary if there were updates to the Magisk addon.d script, since it only gets placed by flashing the zip in recovery. 👍
[Magisk] SteweEliteModder:
However this sounds like you've flashed a custom recovery without patched vbmeta...
[Magisk] pndwal:
Latest Canary + Debug builds:

Magisk (b38ab2a7) (27004)​

[General] Add support for RISC-V

[App] Major internal code refactoring

[App] Support Android 13+ built-in per-app language preferences

Diffs to v27.0​

[General] Support 16k page size

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

[Core] Remove unnecessary mirror for magic mount

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

[MagiskPolicy] Preserve sepolicy config flag after patching

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

[DenyList] Support enforcing denylist when Zygisk is disabled

[Resetprop] Improve implementation to workaround several property modification detections

[Resetprop] Update to properly work with property overlays

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

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

[MagiskBoot] Support spliting kernel images without decompression

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

👍 PW
[Magisk] cry4help:
oppo a15 cph2185 rootable via magisk?
[Magisk] pndwal:
Looks like some have done it... Unlocking bootloader seems to be the difficult part... Have you done that? 🤠 PW
[Magisk] cry4help:
I'm new to it. Was hoping to do so understand some experts advice if you may help me out 😊 I'd be thankful
[Magisk] pndwal:
There are a number of users giving various proofs of having rooted Oppo A15 and various web instructions for unlocking your device... Some indicate it's very difficult and that unlocking and rooting this device may be more fraught than for most... This one however, looks simple enough at a glance:

https://whatmydevice.com/unlock/oppo-a15

but I can't really know as I've never had Oppo, let alone Oppo with MTek SOC...

You need to do your homework and back up everything before proceeding... Once unlocked, I'd recommend avoiding installing a custom recovery unless you find custom ROMs available which is doubtful as very little custom development seems to exist for Oppo A15. Follow official Magisk GitHub instructions to patch boot image and flash using fastboot, and this part should be a cinch. 🙂 PW
[Magisk] traversone:
hello community,

just for common information, I have successfully upgraded my android box (A9) to Magisk 27004 + latest 1.1.344 Shamiko. Actually it happens that all the (3 only) apps in denylist hang just after launch ..... if replacing built-in Zygisk by ZygiskAssistant 1.6.2 all works well again.

Thank you
[Magisk] Lughnasadh:
Heads up with this issue with Canary 27004:

Online update module will not auto install​

(Manually updating mods still works though.)
[Magisk] pndwal:
But not sure exactly what you mean... Built in Zygisk can be replaced with ZygiskNext, but ZygiskAssistant is alternative root hiding, ie replacement for Shamiko, and it's supposed to work as parallel hiding also but was already reported to break things with Shamiko on some devices...

Does Shamiko and apps in denylist work for you if ZygiskAssistant is disabled? 🙂 PW
[Magisk] traversone:
sorry!! I meant Zygisk Next not Assistant
[Magisk] vMAC:
So just installed the latest debug, after the update and when I go to hide Magisk, it gives me an error that root is lost. Then asks me to restore the Magisk app. I have to then go and manually uninstall the "hidden" magisk, while the regular magisk is still installed.

Anyone else seeing this behavior?
[Magisk] pndwal:
Yeah... Issues with this on many devices despite various 'fixes' since, well, since forever... (Not just Debug builds either... but shouldn't use that for daily use anyway.) 🙃 PW
[Magisk] pndwal:
Bit further; just happened to me again too... Hiding the Magisk app continues to be fickle and I'm not sure why one attempt will succeed while another fails to complete, but for second attempt I had Zygisk disabled (must reboot) and then the process completed with full app removed and Magisk in stub working properly... May help others. 👍 PW
[Magisk] vMAC:
I switched from Canary to Debug because others told me it was fixed in Debug branch. Oh well.

FYI after like 20 attempts I got it to work after a restart, similar to you. So there is hope it is being resolved.
[Magisk] pulpf:
Hi, How do I update to 27004? The download is successful but the installation is not?
[Magisk] J.Michael:
How did you try to install?

What are you interpreting as "installation was not successful?

There have been reports of the "direct" methods ("Direct Install" from within the Magisk manager app; flashing the zip file from TWRP; maybe even installing the zip as if it were a module) not working for some releases. As far as I know, just following the instructions to patch and flash as for an initial installation always works.
[Magisk] pulpf:
The 1st step is to update the application, which is not done automatically.
[Magisk] zgfg:
Did you click to that Update/Install?

Maybe it downloaded the APK but did not install. Find the downloaded APK and install manually, or download also manually from the GitHub link lower on you Magisk app screen

From the screenshot, your old Magisk app was hidden, make sure to un-hide or uninstall that old Magisk app first!!!

Read the posts preceding to yours on this same page
[Magisk] pulpf:
Thank you very much, it was because the application was hidden.
[Magisk] pndwal:
For those with custom ROMs and encryption issues/disabled (getting "Unable to find preinit dir" error):

It seems there's been an issue with new pre-init partition detection mechanism (since 26.0) and directory path couldn't be established... Looks like fix is Fix preinit on unencrypted device #8221, so you may now be able to achieve full root with corresponding CI actions build until merged/built in a Canary or public release. 👀 PW
[Magisk] HippoMan:
I got Magisk TJW 27004 successfully installed on my stone-age Pixel 5 running stock A11. It previously was running TJW 27002. It's pointing to the "Debug" update channel, and I was recently notified in the Magisk app that 27004 is ready.

It was very complicated to actually complete the 27004 update, but I finally managed. The following description of everything I did is very detailed, but it might be helpful to others to list all the following detailed steps that I took:

(1) I un-hid Magisk

(2) I rebooted (just in case)

(3) I then launched the unhidden Magisk app, where I see this:

Magisk Install
Installed 81658d45 (27002) (D)
Zygisk Yes
Ramdisk Yes

APP Update
Latest bb38ab2a7 (27004) (D)
Installed 81658d45 (27002) (D)
Package com.topjohnwu.magisk

(4) I clicked on Update

(5) I got a screen showing the diffs from the earlier Magisk version with "CANCEL" and "INSTALL" at the bottom.

(6) I clicked on INSTALL

(7) I just got back to the same Magisk screen that shows up in step 3, above. I checked everywhere on my device, but no download of anything has taken place. I repeated step 6 over and over, and I still got these same results with nothing having been downloaded.

(8) I read the following above from @zgfg : "... or download also manually from the GitHub link lower on you Magisk app screen". However, I can't find any GitHub link anywhere on my Magisk app screen, nor anywhere within the settings of the Magisk app. Only the 27000 release for last February 3 is shown as a GitHub link on the Magisk app screen.

(9) I read the 27004 release notice above from @pndwal, and I went to https://github.com/topjohnwu/magisk-files/blob/ad9ae1442af88b56cf382f987624d823b897a72a/notes.md as given in that release notice , but I can't find any download link for the 27004 release there.

(10) I went to https://github.com/topjohnwu/Magisk , but again, the only release shown is for 27000 from last February 3.

(11) I finally did a search for "Magisk 27004 download", and one of the pages it returned is this one: https://github.com/topjohnwu/magisk-files/blob/master/canary.json .

(12) On that page in the "Magisk" section was a listing for "versionCode": "27004" with ""link" pointing to https://cdn.jsdelivr.net/gh/topjohn...88b56cf382f987624d823b897a72a/app-release.apk . That turned out to be the 27004 download link.

(13) I downloaded and installed that APK, and then I restarted the Magisk app.

(14) I then clicked on "Install" and selected "Direct install", and the installation took place.

(15) I selected "Reboot", and then I tested Magisk. It worked.

(16) I then re-hid the Magisk app.

(17) I rebooted, just in case.

(18) I then re-tested Magisk, and it's working.

Anyway, how does anyone get the download link for TJW Magisk 27004 without having to perform steps 11 and 12?
[Magisk] Lughnasadh:
The link you used in Step 10 leads you to the download section. The Canary and Debug apks there are the latest (27004).
[Magisk] HippoMan:
Aha! Now I see them: they're black-and-orangy-red buttons which say "Magisk Canary" and "Magisk Debug", and which I previously overlooked because I was only looking in the "Releases" section and missed the "Downloads" section.

Thank you very much!
[Magisk] HippoMan:
Also: to @pndwal ...

It would be helpful if you added the https://cdn.jsdelivr.net/gh/topjohn...88b56cf382f987624d823b897a72a/app-release.apk link to your 27004 release notice posted above, in addition to that ".../notes.md" link.
[Magisk] rodken:
Another alternative is to utilize this method after your first 2 steps which has been my go-to process when updating/upgrading.

As a side note, I also take the liberty of backing up the /data/adb/magisk.db file which is located in the /data/adb folder before updating/upgrading Magisk and moving that file back which will overwrite the newer version of said file after succesfully completing the updating/upgrading of Magisk.

The purpose of replacing the magisk.db file with the backed up version is to simply restore the table policies in the Magisk database /data/adb/magisk.db and root enabled apps along with the settings in one fell swoop.

Some would argure that it's a risky move to perform such an action with the /data/adb/magisk.db file, but I can attest that I haven't had any issues thus far.
[Magisk] HippoMan:
Thank you very much.

Your "this" method link points to a way to downgrade Magisk or change from one Magisk release to another (TJW to Alpha, Alpha to TJW, etc.)

All I wanted to do was *upgrade* from TJW 27002 to TJW 27004, but I guess your "this" method would also work in that case, correct?

But anyway, your "this" method says, "... install official Debug App ...", and my original problem was that I didn't know how to find that Debug App in the first place. That's why I ended up requesting that @pndwal adds the following link to his post above with the 27004 release notice:

https://cdn.jsdelivr.net/gh/topjohn...88b56cf382f987624d823b897a72a/app-release.apk

That would be the "official Debug App" to install when following your "this" method in order to upgrade to TJW 27004. This will make it easier for people who read that 27004 release notice to perform the steps necessary to install or upgrade to 27004.
[Magisk] badabing2003:
YAM (Yet another method) :D
[Magisk] HippoMan:
Yes, PixelFlasher is always a good alternative for lots of things we want to do with our Android devices.
[Magisk] rodken:
Even though the aformentioned link points to downgrading or changing from one version to another, I've been using said method to update and/or upgrade regardless of it's sole intentions.
[Magisk] zgfg:
You're not the only one but I was always generally surprised how ppl are unfamiliar with the Magisk app (and Magisk GitHub ReadMe) although using Magisk for years

That also explains why ppl are also not familiar with Installation procedures and other documentation (eg, ppl ask how to make their own Magisk module but they have never seen and read Developer documentation) provided by Magisk GitHub ReadMe and stuff

Or for years we had here 'Senior' XDA members who were surprised with Patch and Flash (officially recommend installation method already for couple of years) but knew only for the stone-aged Magisk installation via TWRP (and got shocked if there were no custom recoveries for the brand new phones)

Screenshots below
[Magisk] HippoMan:
Thank you!

Over the years, I rarely used to upgrade Magisk, and only lately have I started upgrading it more frequently.

Until I did this today, the "Update" link I'd get always managed to download the APK, and then I could just continue with Install=>Direct ... so I never needed to actually search for the APK on line before today.

Anyway, it will indeed be helpful to others that you posted the screenshots with the red arrows.
[Magisk] zgfg:
It's not only about updating but also about reading Instructions and Documentation (common case, before asking here), reporting Issue (and/or reading Issues reported by others), supporting developers, etc
[Magisk] pndwal:
That would be the GitHub OctoCat symbol for TJW...

Not sure about this... 🤔

From there, just click magisk-files at very top to go up a level and Voila!... app-release.apk is Canary and app-debug.apk is Debug build.

FWIW, https://github.com/topjohnwu/magisk-files/blob/ad9ae1442af88b56cf382f987624d823b897a72a/ is the static URL for 27004 files... https://github.com/topjohnwu/magisk-files/tree/canary is currently the same but will always be the latest...

Latest update .json files are here: https://github.com/topjohnwu/magisk-files/tree/master and clicking history (clock) symbol will give you the historical list... Click 'Browse files' within each...

If you examine the .json files you'll also have the alternative cdn.jsdelivr.net links you found which App calls per channel settings...

Well I think links for that build or one for Debug can be found easily enough; John has the repo for builds pinned anyway (only 6 pinned repos)... I just started adding link for notes when a member wanted citations for that a few years ago...

And I'm not trying to get people to download from anywhere other than John's home page links for latest builds... If people want historical builds it's nearly always best to use a public one per Releases link.

🤠 PW
[Magisk] HippoMan:
Of course.

And since there is no OP for this thread filled with docs, the docs I've had to use for Magisk are those which I saved on my computer that I collected over the years by reading here and copying-and-pasting to my docs when I would perform Magisk upgrades, and those docs were outdated, since I hadn't upgraded Magisk very often until recently.

And the searches I did today in this thread about where to find the APK pointed me to the github site, but as you can tell from what I wrote here, I already knew how to find and go to that github site and went there, but I originally only found the 27000 APK from February since I didn't read the github page carefully and overlooked the "Downloads" section ... which I already explained here.

My locally saved docs have now been updated.
[Magisk] pndwal:
Nah... app-release.apk is Canary build. (Been built as release for some time now to be more appropriate (less demanding on resources) for daily use. Debug build (considerably larger) is always app-debug.apk. 😜 PW
[Magisk] HippoMan:
Oh ... OK. I got confused between "canary" and "debug" APK names.

So the link for the debug one, instead, perhaps?
[Magisk] pndwal:
Already answered above:

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

Please check that response to you... 🙃

Also, if you go to pined magisk-files repo from topjohnwu GitHub, don't forget to click Canary branch in drop-down (except for .json files)...

🤠 PW
[Magisk] HippoMan:
Oh ... sorry ... I missed that one. I see the explatation now. Thank you!
[Magisk] HippoMan:
Oh ... I knew about the OctoCat symbol being github. I originally didn't explain clearly in my message that I knew where that link pointed and that I did indeed go to that github page.

However, I initially overlooked the part of that page where "Downloads" were discussed. I only initially looked in "Releases" and only saw the February 27000 release.

After I realized that error of mine, I fixed that number (8) in my original post to make this clear, but that was apparently after you quoted and responded to that original post.

Anyway, my only problem was initially overlooking that "Downloads" section of that page, and that got me very confused until I figured out my error.
[Magisk] pndwal:
I was just explaining what link @zgfg was (likely) referring to since you said:

There's actually 5 GitHub links, but you only need top-cat. 😉

... If you did know he meant that link, it seemed to be the opposite to me. 😬

Yeah... Releases only include public builds...

Also, it's assumed that Canary or Debug users only need the latest (so no need for a historical list of Canary/Debug builds)... Especially for issues, John doesn't want any bug report logs from anything but latest Debug build for obvious reasons.

Yup, and that's why I only provide the link for quoted changelog/notes. These "Latest Canary + Debug Magisk" notices contain changelog/notes about key changes for users convenience but are not intended as download source.

Anyone needing Canary/Debug builds other than latest should be familiar with pinned magisk-files repo anyway, as well as being au fait with Magisk documentation, relevant issues and PRs, how to search, etc etc. 😉 PW
[Magisk] HippoMan:
That's understandable, and that's why I went back to clarify what I wrote once I re-read my post.

So yes, I knew it was the github link, although not because of the shape of the link's icon, which, by the way, never would have suggested a cat to me. In the past, I just clicked on those weird (to me) links to see where they pointed, and that's how I learned that they were all pointers to github.

And anyway, I can't figure out how a cat image would suggest "github".

I'm rather icon-challenged ... although there's one exception: I don't have any trouble recognizing hippopotamus-shaped icons. :)

PS: And I this is the first time I've seen Top Cat since something like (censored) years ago in my youth!
[Magisk] pndwal:
Yup:

... 5-armed 'Octopuss' renamed OctoCat to bypass iStock!...

https://en.wikipedia.org/wiki/GitHub#Mascot

Check these:

https://myoctocat.com/gallery/

So post octo-hippo-cat here:

https://x.com/hashtag/myoctocat

Wow... They censored TopCat? 🤷 PE
[Magisk] TKruzze:
Several years ago I created a couple dynamic web sites with links to the latest Magisk versions. I did it for my personal use, but anyone is welcome to use them as they are dynamically updated whenever Magisk is updated. The download links are direct links to John's github. Nothing hosted here at all.

https://stable.adjclub.com

https://beta.adjclub.com

https://canary.adjclub.com

https://debug.adjclub.com
[Magisk] HippoMan:
You can tell how much I pay attention to the provenance of corporate trademarks by the fact that now is the initial moment when I am first becoming aware that OctoCat is a GitHub trademark. I am now a better person for finally being in possession of this vital knowledge.

Unfortunately, I have never in my life logged into x.com, nor even heard of it. And therefore, I don't have a user ID nor password there. If I could get to that link, maybe I'd figure out a way to post an OctoHippo image that doesn't even remotely resemble a cat.

Well, only the number of years since I last encountered TopCat has been censored. It's great to see TopCat in your earlier message! And this means that TopCat himself is still enjoying uncensored freedom after I last encountered him (censored) years ago.

Maybe I can also post a TopHippo hashtag on that x.com site.
[Magisk] Nergal di Cuthah:
Lol it's twitter, sorry for ot
[Magisk] pndwal:
Wow... Were've you been?... The 'vital knowledge' included that Simon Oxley apparently designed both the Twitter blue bird and the GitHub OctoCat...

Musk has now given you the X... Magisk has yet to lose the bird... Hope GitHub keeps the cat... Looks good in Magisk App!... 😜 PW
[Magisk] zgfg:
Share on-line👍
[Magisk] beeshyams:
Thanks for a helpful guide.

When you do direct install of Magisk (su), it says "let's go" and proceeds with existing patched boot file in downloads. There isn't a file selector to point it select debug app... Unless I misunderstood you
[Magisk] pndwal:
Since 22.0 (Magisk Manager is dead. Long live the Magisk app! eddition), binaries for patching are bundled with the App, so Magisk patched always corresponds with App installed. Even if Chanel is changed it won't affect Magisk patching as update JSON now only affects App updates...

Also, doesn't use anything in downloads; directly patches partion used for booting...

So just install Debug App first... 👍 PW
[Magisk] HippoMan:
These docs are in a group of short *.txt files that I keep in the ${HOME}/etc directory of my computer. They have mnemonic names such as "magisk-apks.txt", and they mostly just consist of lists of things like file/module names, URL's, code snippets, etc., and sometimes also short phrases to jog my memory.

I need to write README-file-type text that people other than myself can understand before I can share this on line in any kind of useful form.

And that's exactly what I usually do when I post things like my recent message in this thread describing my step-by-step procedure for having installed Magisk version 27004.

You can see a couple of other examples of such messages of mine among the recent posts in the Magisk Alpha thread.
[Magisk] 8y73:
Hello together.

Today I got an update to the latest Magisk Canary version (27004). Since this version, I can no longer install modules via Magisk. Magisk simply crashes when the installation starts. At least, this happens when updating two of my modules. I haven't installed any new/other modules yet, but I think the same problem exists there.

Have anyone the same problem with the newest Canary version?
[Magisk] Nergal di Cuthah:
Just tried to install play int fork (over an already existing install) and it installed fine (pixel 6 pro, stock rom stock kernel) maybe it's a specific module or have you tried others?
[Magisk] andy356:
LOS Recovery keeps the data partition encrypted though. I suppose devices with TWRP have this convenient functionality.
[Magisk] HippoMan:
I do not have that problem. I recently explained above how I installed and tested version 27004 and how it is working for me.

I also explained what device I am using and which version of Android I am running on that device.

Which device are you using, and what version of Android?

Also, to be clear, did you install Alpha Magisk 27004 or "standard" TJW Magisk 27004?

And what exact steps did you take to install this Magisk Canary update?
[Magisk] 8y73:
Tried an other module and the installation works fine.

:)

Problem are updates from YT Revanced + YT Revanced Music. But it looks like they aren't even new versions. *Problem solved*
[Magisk] HippoMan:
Oh, that's great!

I never have been using those modules, and so I can't say whether or not they would work for me. But again, I'm glad you got it working!
[Magisk] pndwal:
Issue when updating only (known):

Online update module will not auto install, app, regression, #8208 opened last week by vvb2060

'Install from storage' works fine.

👀 PW