yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Go to Xiaomi.eu forum, search for Stable 12 ROMs - thread will be closed but in the post #1 you must find the links

MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE

STABLE RELEASE 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

Find the ROM you have (per device) extract boot.img and flash

You cannot use stock boot.img with custom Xiaomi.eu

Or take Fastboot/tgz stock ROM and flash (with Factory reset) to switch to stock
[Magisk] iXeNIV:
Link is dead unfortunately, and I can't register there to ask for re-upload, I don't know why I can't register, and can I use 12.5.8 boot.img instead of the same version? because I found that one and downloaded it, otherwise switching to stock does it wipe data & apps?
[Magisk] zgfg:
OMG, which link is dead?!

Screenshots attached, directly from there
[Magisk] iXeNIV:
this one is dead, tried 12.5.8 boot.img xiaomi eu (recovery) which is different from fastboot stock in size, didn't work.
[Magisk] zgfg:
I don't know why would be dead but sorry I'm not going to search among the list for your device, version and test if downloads

You can download from SFG only from PC or by enabling Desktop site in mobile browser. Not directly from the browser on the phone

Anyway, you must NEVER mix boot or recovery from one ROM with another ROM. If you cannot find the same version, then flash another full version., like 12.5. Follow their instructions, google if needed, ask on Xiaomi.eu forum. Good luck

I don't understand how did you think to use stock boot with Xiaomi.eu. Or boot.img from Xiaomi eu MIUI 12.5 to your 12.
[Magisk] iXeNIV:
I searched myself, and gave you results, I didn't ask you to do that for me, just showed you it's dead, why I don't know either. Also for sourceforge they don't have 12.5.5 only 12.5.8.

Why I used stock boot.img because I don't have Xiaomi eu rom, well it booted and works fine except for WiFi can't enable it, I uninstalled magisk and re-applied V26.1, and it showed it has installed wifi and patched boot.img, yet still not working, thank you for your time I have no other solution then revert to stock and re-flash the phone.
[Magisk] J.Michael:
How did you get the custom ROM in the first place?

Like @zgfg said, take any complete ROM and flash that. You apparently got away with using most of one ROM with a boot image from another ROM. That's just dumb luck, there is no point in trying to track down the few detected problems.

As for which operations require a wipe of data: I don't think anything ever takes off and wipes; I think if a wipe is required you will be asked -- just say no and try something else.
[Magisk] pulpf:
Thanks.it's ok
[Magisk] iXeNIV:
I got it 2 years ago is it that hard to understand? it's Poco X3 NFC an outdated phone, and I already re-flashed the phone with stock, then installed latest custom rom MIUI 14, phone is working fine now.
[Magisk] ipilcher:
Anyone here using Shamiko?

If so, where did you download it? I found something that purports to be it's GitHub page[1], but there doesn't seem to be any actual source code or documentation there.

[1] https://github.com/LSPosed/LSPosed.github.io
[Magisk] J.Michael:
Releases has Assets. One is named "sources".
[Magisk] Lord Sithek:
Because Shamiko is closed source
[Magisk] ipilcher:
Yes, but that ZIP file only contains the stuff that is found in the GitHub repo, which doesn't contain any source code.
[Magisk] badhabit_wb:
I have a pixel 8 pro. On the latest beta version I can't get zygisk to work. Magisk installs with no issues and I have root. I wiped the phone again and reinstalled android, installed magisk, patched the init_boot, and got root again with no issues. I still can't get zygisk to work. I can turn it on in settings and reboot and it still says not but it shows on in settings. I'm using the latest canary build. Any ideas?
[Magisk] Lughnasadh:
Known issue. A PR has apparently fixed it. Should be in the next Canary release.
[Magisk] badhabit_wb:
Thank you
[Magisk] weissco:
How often do the canary builds get updated? Pixel 8 owner here as well. I tried to do a build myself from the latest repo but failed.
[Magisk] sawdoctor:
Have you tried the debug build if you are on beta 2.? You need to name it zip and flash then name it back to apk and install, it's a signature issue
[Magisk] weissco:
I installed the debug build from the apk. Didn't have any signature issues (that I noticed, anyway). It installed just fine, but still was unable to get zygisk to work with it. Will try flashing it and see if that makes a difference. Thanks!
[Magisk] weissco:
New canary (and debug) versions just dropped with the latest updates for the QPR2 beta. and Zygisk is all fixed.

Amazing turnaround time, thank you!
[Magisk] Lughnasadh:
https://twitter.com/i/web/status/1735018220552343781
[Magisk] atlaspsp3:
my a3 2017 had efs mount sdcard problem bootloop etc magisk was da only solution to bring it back incredible🐰
[Magisk] hanschke:
I only get the 1.0 APK after install and the Download dont Work from magisk.
[Magisk] polish_polisher:
i have been trying to install magisk on moto z2 play and i'm stuck on this error

what did i do wrong and how do i fix it.

google didn't help
[Magisk] J.Michael:
Did you unlock your bootloader?

Is the device working otherwise? (Boot to Android, connect to wifi, make phone call?)

It might help if you specify what version of Android you have, what version of Magisk apk is installed, what you are using to "flash".
[Magisk] J.Michael:
What is "the 1.0 APK"? Not likely to be a Magisk manager apk.
[Magisk] polish_polisher:
bootloader unlocked

device is working correctly

android 8.0.0

magisk 26.4

what exactly do you mean by "what you're using to flash"?
[Magisk] Nergal di Cuthah:
What method are you using to copy the patched boot into the phone's boot (adb, twrp, pixel flasher)
[Magisk] polish_polisher:
adb
[Magisk] Nergal di Cuthah:
Gonna list a few troubleshooting questions

Have you tried another cable?

Can you flash a not rooted boot or does that fail too?

Are you typing each command or (as your image seems to portray) a script?

What version platform tools?

Update google drivers?
[Magisk] polish_polisher:
cable is good

flashing non rooted works

i'm typing/copy pasting commands

?

drivers are as new as possible
[Magisk] Nergal di Cuthah:
SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

What version
[Magisk] polish_polisher:
was outdated, now newest, error changed slightly
[Magisk] badabing2003:
If flashing stock is working but not flashing the patch, redo the patching in Magisk, make sure the transfer between the PC and the device is done over adb and not MTP
[Magisk] pndwal:
Latest Canary and Debug Magisk release notes:

Update Canary Channel: Upstream to d7750b72

Magisk (d7750b72) (26403)​

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

Diffs to v26.4​

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

Sorry , bit late with this... 👍 PW
[Magisk] J.Michael:
It might not be possible to patch this device. Find a Moto thread and see if anybody knows.

(There's a Samsung thread where people were happily patching boot and installing Magisk until Samsung released an improved bootloader. Once you let it update the bootloader past v3 you could no longer run a patched boot image, and you could not roll back the bootloader because the bootloader protects itself. All this in spite of still having an "unlock bootloader" option, it just doesn't mean what a reasonable person expects.)

It's also possible you are not patching the right partition. Could this be a device where you are supposed to patch init_boot rather than boot?
[Magisk] simplepinoi177:
I've only been in the Google Pixel-sphere, but is there other devices other than the Google Pixels (post Pixel 7 at that) that need the init_boot patched instead of the standard boot partition? I always figured it was unique to the Pixel line as I've never encountered it on other devices, but then again like I said I've only really been in the Pixel-sphere...
[Magisk] HippoMan:
I asked the following question in the appropriate device-specific thread, but it's not a very widely used thread, and I haven't gotten a response. So, I'm now asking here:

I have a Pixel 5 device running the stock version of Android 11. I'd like to choose between the latest Magisk utilities (official TJW, Alpha, Kitsune) that work on stock A11 for the Pixel 5.

Does anyone know which of these Magisk utilities would work on my A11 Pixel 5 device, and which is the latest version of each such Magisk utility that would function on my device?

Thank you very much.
[Magisk] HippoMan:
Please forgive me if I overlooked something in these 50,000-plus messages concerning what I'm about to ask.

My Pixel 5 device running stock A11 does not have a recovery partition.

I want to install Magisk *and* TWRP, but it seems like they overwrite each other in the boot partition.

What a mean is this:

(A) To install Magisk, I know that I use the Magisk Manager to patch the boot.img for my device (it doesn't have any init_boot.img), and then I subsequently flash the resulting patched Magisk boot image into the "boot" partition.

(B) To install TWRP, I "fastboot boot" the TWRP *.img file, and then when I am in TWRP I use TWRP's install to flash the TWRP installation *.zip file. Based on the messages that print out, this procedure patches boot also.

If I do "A" by itself, Magisk works fine.

If I do "B" by itself, TWRP works fine, and I can boot into TWRP via "adb reboot recovery".

However ...

If I do "A" first and then "B", I lose my Magisk installation, but I can boot into TWRP via "adb reboot recovery".

And if I do "B" before "A", Magisk works fine, but I can no longer successfully do "adb reboot recovery" to get into TWRP, and when do that, I get the dead Android icon.

When there is no recovery partition, does anyone know whether there is any way to have both TWRP and Magisk running properly on the same device, given that they "seem" to overwrite at least part of their respective installation data in the boot partition?

Thank you in advance.
[Magisk] simplepinoi177:
You can....but it's been a long time since I've been on my Pixel 5; I never upgraded to Android 12 because of the lack of TWRP and you'd have to wipe to update...

But from what I recall, you temp boot to fastboot boot TWRP, then install TWRP. Then you reboot to TWRP and install Magisk using the .zip. It shouldn't overwrite the existing boot partition, just "patch" it. But maybe Magisk has changed since I was on A11. If anything, maybe using very old versions of Magisk do it correctly where it doesn't do so much on the boot partition that it makes the recovery inaccessible. Or maybe an older version of TWRP is required. 🤷‍♂️
[Magisk] HippoMan:
Thank you very much! I'll give all of that a try.

Luckly, I can at least always boot into TWRP via "fastboot boot /path/to/twrp.img" and then do nandroid backups and restores, so if this method doesn't work, at least I could restore my system.
[Magisk] simplepinoi177:
Oh you know what! This is jogging my memory...I believe you can't install Magisk from the temp fastboot boot twrp.zip...it must be when the recovery part of the boot partition is already replaced....

I dunno if that's how you were doing it (i doubt it), but if you were, that might explain why it didn't take and it was either/or....
[Magisk] en11gma:
i have (Galaxy S20+ Exynos) sm-g985f/ds (Android 13 WB1) security patch level march 01, 2023

phone is bootloader unlock.

I did have magisk 26.4 working fine by patching my boot.img and vbmeta.img.

i am not rooted now as i just went back to stock with odin 3.14.

im trying to pretty much make my phone into a raspberry pi and i have debloated with adbappcontrol 1.8.3 uninstalled 140 packages.

my kg status is stick "checking" and all is good.

what i want to know is there options for magisk to disable knox and selinux when it actually patches those files?

im new to magisk and i know not very much about its options and modules or even its default settings when it does patch boot.img and vbmeta.img.

i have looked on the internet and i am still looking now for info/options/modules on this matter.

btw can i safely update to the very last stock official firmware from samsung which is Android 13 WJD with security patch level 11-01-2023 without any side effects?

i do not think i will be installing twrp as when im rooted and debloated on the stock offiical rom its close to what i want.

all i need now is selinux = disabled and knox disabled too.

i think that would get me close to a regular (linux) like install and i can remove almost all bloat and be fine.

thanks for the great program!
[Magisk] HippoMan:
Your suggested method worked! Thank you again!

Here are the steps I performed:

(1) Completely uninstall my current Magisk installation.

(2) Reboot the device

(3) adb reboot bootloader

(4) fastboot boot /path/to/twrp.img

(5) Once in TWRP adb push /path/to/twrp-installer.zip /sdcard

(6) Within TWRP, flash twrp-installer.zip from /sdcard/

(7) Reboot back to the system. Everything came up fine.

(8) adb reboot recovery ... this worked, as expected.

(9) Copy Magisk-v26.4.apk to Magisk-v26.4.zip on my desktop machine

(10) adb push Magisk-v26.4.zip /sdcard/

(11) Within TWRP, flash Magisk-v26.4.zip from /sdcard/

(12) Reboot back to the system. Everything comes up fine.

(12) Launch Magisk.

(13) Click INSTALL and select direct install

(14) Device reboots, and the system comes up fine.

(15) adb reboot recovery ... I properly get into TWRP now!

(16) Perform a nandroid backup. It succeeded.

Now that I have accomplished this, I will *never* (!!!!!!) install a higher version of Android than A11, and I won't do it on any Pixel that's newer than Pixel 5.

My reasons for this are ...

... it's very important for me to be able to reliably perform nandroid backups and restores.

... the GravityBox utility only works properly up to and including A11, and it's important for me to be able to use GravityBox to alter (in other words, "improve"!!) the apperance and performance of my Android device.

Anyway, thank you again!!!
[Magisk] Nergal di Cuthah:
That's the one thing i miss coming from pixel 2xl with android 8 (frozen there cause i wasn't versed in android at that point) and gravitybox to pixel 6p and no gravitybox (or xposed at all)
[Magisk] HippoMan:
There's something called PixelXpert which is the new fork of AOSPMods. It provides some of the GravityBox features for A12 and higher on Pixel devices.

PixelXpert offers a lot of features, but some of what I really like in GravityBox are missing. For example, in GravityBox, I can map long-press on the "Back" key to kill the foreground app. PixelExpert only offers something like that if you're using swipe-based navigation (instead of button-based).

Anyway, as far as I'm concerned, there is nothing worthwhile at all in Android 12, 13, or 14 that could motivate me to abandon A11 ... nor would I be likely to want any "enhancements" (ha-ha!) that the Googlefrinchians offer in Android 15 and beyond.
[Magisk] BillGoss:
It's an Android thing, not specific to Pixels.

From https://source.android.com/docs/core/architecture/partitions/generic-boot :

"For devices launching with Android 13, the generic ramdisk is removed from the boot image and placed in a separate init_boot image. This change leaves the boot image with only the GKI kernel.

For upgrading devices that continue to use Android 12 or older kernel versions, the generic ramdisk remains where it was with no requirement for a new init_boot image."
[Magisk] J.Michael:
Look for device specific threads.

In the threads for the SM-T290/295 people became unable to patch their devices once the bootloader got past rev-3. I don't remember the date, I don't remember whether it was tied to an Android version. I just know that if you have successfully installed Magisk and are considering updating, you should look at the new ROM and check the bootloader version number.

At one time @Talich52 described doing a little dance wherein you modify the ROM so that it will be (re)installing an older bootloader along with the shiny new Android. I don't remember if that stopped working.
[Magisk] pndwal:
Latest Shamiko v0.7.5

0.7.5​

Refine hide mechanism, passing more detection (e.g., E-CNY, 12306 play ver)

👍 PW
[Magisk] nylium:
Hi, thanks for the reply.

I followed your suggestion but unfortunately there is not change in behavior.

Magisk Manager ran the update

Magisk seems to be installed: I still have SU access and I'm seeing magisk mentioned in the log

I installed, uninstalled using app info, then re-installed version 2.1 which is what I originally had

I've also tried installing every version from 2.0 to 2.4 but there is no change

Whenever I run Magisk Manager after installing it shows the slpashscreen, exits, then uninstalls itself.

I have attached a log showing an install and crash.

Timestamp 12-19 13:13:54.345 shows the most recent install attempt.
[Magisk] J.Michael:
Did you ever hide the Magisk manager app?

Check your app drawer for the hidden app. Try to open it and unhide it. If you can't open it, just uninstall it from Android "app info".
[Magisk] pndwal:
Are you trying to install an older Magisk App that the core Magisk installed?... Or changing from official to a forked or CI build or vice versa?... Anti-downgrade and anti-signature (changes by vvb2060) will prevent this... magisk.d (daemon) in core Magisk is checking and will force uninstall the App...

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

👀 PW
[Magisk] IronTechmonkey:
During the latest update of Magisk app from 26.3x to 26.4x one of my devices experienced a glitch which was relatively easy to work around but remains unexplained and sounds similar to some recent reports in this thread so for what this is worth from Stock Moto (G Power 2021) Android 11 rooted with Magisk, hidden with Deny List enabled:

A few days ago, I updated the Magisk app and Magisk itself from within the Magisk UI, after which SU access seemed OK as did an app which requires the deny list, but as discovered days later Magisk (original or renamed) was missing from app drawer and when run from a homescreen shortcut the Magisk UI did not open; instead, there was a message stating that the full version of Magisk would be required. This precluded opening Magisk to create a new home screen shortcut but since the issues seem to be just with the app and not with the core functionality I downloaded and installed the latest version of the Magisk app (26.4), after which the Magisk app runs OK (having preserved settings) and only required being hidden again.

On another similar device (Stock Moto (G Power 2020) Android 11 rooted with Magisk, hidden with Deny List enabled). Both the Magisk app and Magisk were updated via the UI, one immediately after the other with no similar problems.

Since these issues were not immediately evident I was not closely tracking this timeline but in retrospect I’m wondering if there are issues running app 26.4 with core 26.3 (unlikely) or if something went wrong with the Magisk update and subsequent reboot on that first attempt on first device (more likely).
[Magisk] badabing2003:
I think the issue lies in the unhiding of Magisk.

I have seen often that the unhide operation either fails to remove the stub after creating the app from the stub data, or not managing to properly unhide (create the app).

In the case of the former, what ends up happening is that root continues to work, but Magisk app reports that Magisk is not installed.

Only after uninstalling the stub, Magisk reports correctly that it is installed.

That part of Magisk code that manages hiding / unhiding or with the newer version stub auto-installing if the app is removed has some glitches.
[Magisk] IronTechmonkey:
If the Magisk app update automatically handles unhiding > updating >, rehiding > restoring/maintaining settings... then yes all symptoms I've seen are consistent with your description. Installing latest Magisk app (without uninstalling anything manually) seems to have set things right, except for the rehide (but the deny list was remembered). Thanks again for the explanation.
[Magisk] en11gma:
sm-g985f/ds (Android 13 WI7) Security Patch Level 10-01-2023

i did magisk v26.4 on my stock official AP file and flashed along with my other AP files (not home csc).

after i setup i transfered over the MM.apk and installed it again.

it updated and rebooted and root checker was granted root permissions and passed).

played around with root for awhile and decided i want to start fresh from stock again so..

i then "uninstalled" MM and rebooted.

i then shutdown and flash the full stock WI7 firmware.

reboot and setup phone with internet = on

oem unlock greyed out and on in developer settings.

looks like brand new setup so i do my settings etc...

lock screen = none

(1) why is enable oem unlock greyed out but "on" in dev options? >>>solved<<< go into dload mode and long press vol up

in adb shell:

'adb reboot-bootloader' = entering fastboot mode... (pic below).

(2) why is it trying to enter fastboot mode and win11 not recognizing device warning coming on at that screen? >>>solved<<< this is expected behavior and only accepts limited fastboot commands.

you can get into recovery mode which has reboot to bootloader where you can do some of the fastboot commands:

vol up + power button + plug in type c then release both buttons. its very fast and before the warning screen. almost as soon as phone comes on.

(3) why cant i manually get into recovery with the volume up + power button anymore and when i do get to desktop it shows that other pop up message in pic below? >>>solved<<< with phone off hold vol up + power and plugin. let go before unlocked bl warning

ok. i think it was just me not understanding stuff.

everything is working as it should be.

ok now im going to root again.

here we go :)
[Magisk] J.Michael:
You have fastboot on a Samsung?

I don't understand why you uninstall Magisk manager.

The greyed out but on OEM unlock is normal. It means the bootloader is unlocked. (Really unlocked. Initially, you toggled that switch to allow yourself to unlock the bootloader, but you had to do some funny boot to get the chance to actually unlock.)
[Magisk] en11gma:
it can be relocked but you dont use fastboot to do it. you have to shut phone off and then vol up + vol down and plug phone in to get back to download mode and then hold volume up again (just like when you unlock bl).

so thats a good thing. it did make status go back to official

still have problem with that 'adb reboot-bootloader' going to that screen where it says entering fastboot mode....

it is taking the last ota update right now.

so thats good
[Magisk] badabing2003:
I don't know if Magisk update automatically does unhide + update + rehide, I don't think so, but I could be mistaken,

Settings / denylist / sulist is stored in Magisk core's database which is in /data/adb/magisk.db so even if you uninstall the App (manager) those settings would be kept unless you uninstall core (unroot).
[Magisk] Shemploo:
Thanks for the update Captain.

This is why forums are a bad system for this type of world, (xda), there should be a better system organized around issues, not posts.

Anyway, as to your post here, I found that when I enable hide, most system apps check themselves in the hide menu, and even if I uncheck them all, and reopen the menu, they all are showing back as checked again.
[Magisk] Captain_Throwback:
Logcat?