yashsingh1/xdaforums huggingface dataset:
[Magisk] Mitezuss:
not problem dude.

anyway, if anyone know what are i am talking about (about property context) then know how is the real path on android (or the relative path on windows (unpacked image -> copy&paste the relative path)) (do you know what i mean ?)

So, about my question: any idea how add property context using magisk ?

Note: if the property context is not defined -> a App can warn (or crash) (so i need define a property context)

Note: i can add directly to the system image... but how i said: want to do using magisk (if is possible...)

PD: if there are no method to ADD PROPERTY CONTEXT to the system... maybe magisk should implement that feature ?

Regards
[Magisk] oopps24:
Where i can find Magisk Canary >26404? i cant install Shamiko.

i have Magisk 26.4 (26400)
[Magisk] Lughnasadh:
GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] Nergal di Cuthah:
Under downloads https://github.com/topjohnwu/Magisk

Edit: ninja'd by lug
[Magisk] amajamar:
Did you get this to install? When I attempt to install it, it seems to install, but doesn't actually.
[Magisk] oopps24:
Yes
[Magisk] oopps24:
New way to set bypass is very confused.

i installed magisk, zygisk, lsposed, playintegry mod zip, safety zip, magisk hide props and every time i get only meets:basic_integrity.

On my phone doesnt work. Google wins.
[Magisk] oopps24:
Maybe u have hide magisk? return that. install canary and then u can hide magisk again.
[Magisk] amajamar:
Thanks! You right!
[Magisk] amajamar:
Now trying to figure out how to do the pif fingerprint thing... I'm totally lost now...
[Magisk] oopps24:
I have the same problem. actually is my brain on fire xD
[Magisk] oopps24:
i installed over magisk playintegrityNEXT.zip, Shamiko, Zgiysk by LSPosed and magiskhideprops config and now it works. Wallet works now.
[Magisk] amajamar:
OK, I'll have to give all that a try. Thanks for sharing that!
[Magisk] oopps24:
Dont forget magisk hide, activate Zygisk in magisk setting und disable denial. list in magisk settings.
[Magisk] amajamar:
Thanks. How do you install the playintegrynext zip? That's not a module right?
[Magisk] amajamar:
I got it! I didn't need to use magiskhideprops config. Thanks for your help!
[Magisk] RaskarKapak45:
Hello,

I currently have my phone with LineageOS and Magisk installed. I want to flash it with the last LineageOS with MicroG version, and stop using Magisk (I only use Magisk so I can get signature-spoofing, but the ROM that I will flash will have signature-spoofing built in so Magisk will not be necessary anymore). Do I need to uninstall Magisk before I do a clean install of the new ROM?

I am afraid of having any bootloop issue if I mess up with something. That is one of the reason I want to stop to use Magisk
[Magisk] J.Michael:
Does "clean install" include wiping data? If so, there can be no remnants of anything you did before.

Even if you do not wipe data, once you replace the boot partition, there will be nothing of Magisk in the "system". You might still have files in /data/adb, but noone will be using them. And if you no longer have root privilege, you won't be able to see them.
[Magisk] RaskarKapak45:
Yes, it include wiping data.

I was actually unsure that the boot partition would be replaced. I am flashing my phone once in every 2 years approximately so I have to learn everything again each time :)

Thanks!
[Magisk] Pete.Spencer:
Someone successfully rooted S24 SM-S921B just with magisk ap patching method?
[Magisk] Nergal di Cuthah:
Probably best handled in your device's board, but maybe someone has the same device idk
[Magisk] shohabmsk:
@topjohnwu Magisk 26.4 doesn't boot my system if I patch tar using it.

Magisk 26.3 does boot system. It's been a problem since release of 26.4. I've commented it earlier. My device is Samsung A13 4g, This issue is happening to Samsung A12 user too. I'm not good at logging. I hope you check what's problem.

Edit- tried with oneui 6(android 14) today, still this issue present.

Issue:

1. Patch tar files using magisk 26.4 apk.

2. Flash using odin.

3. System doesn't boot.

But:

1. Patch tar files using magisk 26.3 and earlier.

2. Flash using odin.

3. System boots fine.

But after system boots using 26.3, then update to 26.4 works fine. There's might be a problem Patching tar files using 26.4. please check thanks.
[Magisk] pndwal:
Latest Canary + Debug builds:

Magisk (356ee1fe) (26405)​

Minor bug fixes

Diffs to v26.4​

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

[ResetProp] Add new wait for property feature resetprop -w

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

👍 PW
[Magisk] pndwal:
Assuming you're properly transferring files with ADB, flashing all 4 binaries together (not just AP) etc, you need to test with latest Canary or Debug builds to know if there are already fixes for issues downstream... 🤠 PW
[Magisk] zgfg:
Btw, tophohnwu is not participating on XDA for several years.

He rarely reads (and answers even less)

Open an Issue on the Magisk GitHub repo if you really want to reach Magisk developers
[Magisk] sawdoctor:
If you submit an issue on GitHub read the guidelines and use Magisk debug or the magiskbot will close it
[Magisk] zgfg:
Using since yesterday, working fine
[Magisk] osm0sis:
This message has now been removed from where I saw it. Not sure what this means, but I guess we'll see in a month or so when they're rumored to resume development. 🤔
[Magisk] sawdoctor:
Just a warning to others. Got an update this morning for Magisk 27001, everything went ok but it's no longer compatible with shamiko
[Magisk] xcl1pse:
It works just fine?
[Magisk] dipseeet:
Magisk 27.0

what is inside: SUList or DenyList?!
[Magisk] sawdoctor:
I got unsported environment so had to downgrade to v0.7.5. Let me try updating again and I'll report back

Edit

Still getting unsupported environment
[Magisk] xcl1pse:
Denylist. SUlist only delta/kitsune and never implement on TJW magisk
[Magisk] zgfg:
For me everything works perfect, Canary v27001 and Shamiko v101

Screenshots attached I have also tested TB Checker, S-Check and Hunter and everything works fine (no detections) as previously

PS: I don't run ZygiskNext or things like that
[Magisk] xcl1pse:
Try disable all modules and enable just shamiko
[Magisk] J.Michael:
Does Shamiko need Zygisk? Do you have Zygisk enabled?
[Magisk] pndwal:
Latest Magisk public Beta Stable build:

Magisk​

2024.2.3 Magisk v27.0​

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

[ResetProp] Add new wait for property feature resetprop -w

Full Changelog: here​

[Promoted to public Stable]

👍 PW
[Magisk] pndwal:
Latest Magisk Canary+ Debug builds:

Magisk (3d91a561) (27001)​

Minor bug fixes

Diffs to v26.4​

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

[ResetProp] Add new wait for property feature resetprop -w

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

Compared with 26.4 because 27.0 is Beta, not Stable? (A first ?) 🤔

👍 PW
[Magisk] sawdoctor:
Tried with both zygisk next and built in zygisk. I'm on latest qpr2 beta if that makes any difference.

I'll try disabling everything apart from shamiko

Yes have zygisk and shamiko v 0.7.5 still works just latest version doesn't same as it doesn't work with Magisk alpha anymore
[Magisk] sawdoctor:
Just an update incase anyone else has the same issue. I had zygisknext installed but not activated/toggled on in magisk. Shamiko must have been detecting it even though it was toggled off. Removing the module fixed the unsupported environment
[Magisk] Spartacus500:
Magisk 27.0 work Perfect 👍
[Magisk] dadnammit:
I'm seeing the Github release for v27.0.

But my Magisk app (v26.4) doesn't give the option to upgrade (on stable channel).

Github doesn't show what channel v27.0 is. How could I find that?
[Magisk] Lughnasadh:
The latest release is Beta (and Canary), not Stable. Stable should come shortly.
[Magisk] Cipcino81:
Hello,

I have tried this version 27 beta but for me with only Shamiko latest version , it does not pass play integrity check. So I reverted to version 26.3 that works fine for me. ( Version 26.4 do not work for me because I have the problem with the "blank" screen no app icons/no app drawer ).
[Magisk] Nergal di Cuthah:
Why would you pass integrity with only shamiko. You need a PIF (fix, fork or next) to pass pi
[Magisk] Cipcino81:
I don't know. With version 26.3 I pass with just Shamiko. Maybe the fix is integrated with Lineage OS Tomoms Rom version. Anyway with 27 I tried to install play integrity fix and next but it never passes ..
[Magisk] Nekromantik:
the reset props change in magisk 27 is it same as the reset pops fix that kitsune has?
[Magisk] xcl1pse:
No
[Magisk] wugga3:
I'm gonna say it's a kernel issue in Lineage OS.... If I understand correctly and I may not understand... But it's been discussed here:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

I not exactly sure where/when this started but it's relatively one of the newer issues in that thread that they are trying to find a method to correct with may be done success... But since I don't have that specific kennel issue, I can't advise any further to a solution (cause I don't need to understand that problem)

Hope that helps to point you to the right place/information... Look for user "osmosis" and lineage os kernel as I do know that user has been busy with others on this kennel issue. Good luck
[Magisk] xcl1pse:
First of all, he asked resetprop thingy in magisk v27 is same as kitsune magisk, I say NO. Second it doesn't matter for Play Integrity Fix, resetprop doesn't care about your device pass Play Integrity or not even with LineageOS and their kernel. Third all my device pass device integrity with my custom kernel. This changes are maybe A/B testing since I heard even stock unlock bootloader without custom kernel also not passing device integrity so no clear solution for now either change your kernel version or check your environment.

Hope my answer is clear.
[Magisk] Fishawy:
Got prompted through the app to update from Magisk stable 26.4 to Magisk stable 27.0 (not beta), updated the app and Magisk, rebooted, lost root.

Trying to root using various methods (commands, patched image, PixelFlasher), no luck. Only way I could obtain root back was to downgrade to 26.4 stable.

Not sure what's happening, since my update channel is set to stable (the app is still prompting me to update), and there's no stable release on Github. Weird.
[Magisk] sawdoctor:
What modules do you have installed? I had similar issue a while ago, every time I updated I lost root and it was magical overlays module causing the issue
[Magisk] Fishawy:
I do have Magical Overlays module. Did you manage to update to 27 normally?
[Magisk] sawdoctor:
Yes but had to remove magical overlays and everytime i installed it again i lost root.

I did read on telegram someone fixed the issue by removing all modules updating and then installed each module one by one. I just stopped using magical overlays
[Magisk] Fishawy:
Thanks for that, I'll remove it and give it another go.
[Magisk] gloops100:
Hello all,

I wanted to install the latest OTA update, and I've been trying to do it using this guide. I'm stuck on step 2:

When I follow these instructions, I get this error:

=> I've followed a guide to flash the init_boot.img with FKM ; then install "directly" with Magisk.

=> Now the phone boot direclty on Fastboot.

I've tried to boot on partition "b" ; I've boot loop.

I've tried :

adb wait-for-device shell magisk --remove-modules

but nothing happen. (

adb shell

adb.exe: no devices/emulators found

)

Have you any idea how to solve this ? (1# solve the boot on fastboot or 2# solve the boot loop with partition B)

Thank you in advance
[Magisk] gloops100:
Solved !

Just reflash the stock boot.img

==> fastboot flash boot boot_stock.img

Have you any idea how to avoid this issue to do the OTA upgrade ? :

When I follow these instructions, I get this error:
[Magisk] Wolfcity:
That is a message that tells you that for what reason ever magisk hasn't made a backup of your boot.img or that it has been deleted.

Just use the boot.img of your latest firmware instead.

-------------

Edit: Ok, I was to fast. You've solved the problem.(y)

Just remember that the stored stock boot.img from magisk is the same as the one you took from your firmware and patched it at that moment.

Don't mix up the different boot images.
[Magisk] gloops100:
Thank you for your answee, but I don't know how to solve the issue for the OTA process.

Any idea ?

Do I need to flash boot.img with Magisk ??
[Magisk] J.Michael:
Your "issue" was you couldn't use the instructions to remove Magisk before allowing the OTA update to be applied.

If you have reflashed the correct, stock, images, you have removed Magisk and restored the device to the state expected by the OTA update. Now you can move to the next step, allow the update.

(I have not looked at the instructions you say you are following. I have never done an OTA update. If these instructions are some clever sequence that supposedly makes it easier to apply an OTA update and end up with Magisk reinstalled, you will have to pay attention -- one extra reboot could make it impossible to follow the rest of the instructions.

If an OTA update is an incremental update, the two challenges are restoring the device to the state expected by the update, and then getting a copy of the new boot image to patch with Magisk. It would be more straightforward if you located a complete ROM that includes the update and follow the usual procedure of installing the ROM, then extracting the boot image from the ROM file, patching with Magisk, and flashing the Magisk-patched image.)
[Magisk] gloops100:
Thank you I understand better, but to avoid issue, have you any link to follow the process ?

For information, the phone is the Xiaomi Mix Fold 3. For the root, it's needed to flash the init_boot.img instead of boot.img.
[Magisk] nek46:
greetings from greece, install magisk the last version 27.0 and play integrity 15.5 and i saw this

test with Gpay all ok device htc u ultra rom, custom lineageOSandroid 12
[Magisk] J.Michael:
John Wu's original instructions.

You might like @badabing2003's PixelFlasher. Whether you have a Pixel or not, it can help you manage some of the fussy details, like keeping track of which extracted boot image came from which ROM, which version of Magisk produced which patched image file,...

It's not an Android app, you won't click "Install" and start using it. It runs on a real computer, and requires a certain amount of infrastructure. Read a hundred posts in the thread and you'll see that a lot of people find it useful.
[Magisk] gloops100:
I understand, it's not easy :)

the phone is the Xiaomi Mix Fold 3.

For the root, it's needed to flash the init_boot.img instead of boot.img

Do I need to put the stock "boot.img" or "init_boot.img" somewhere ?
[Magisk] Nergal di Cuthah:
You probably ahould be asking this in your device's board instead of the general magisk topic.
[Magisk] gloops100:
My phone (Xiaomi Fold 3) was rooted with patched init_boot.img (doesn't work with boot img).

In your process, do I need to replace "boot.img" by "init_boot.img" ?

On the phone thread @B!GBOY explain this process :

Should it works ?
[Magisk] zgfg:
Not sure what you mean by 'replacing'.

You should not flash (patched or not) boot.img over init_boot or vice versa

But as described above, try by preparing the patched init_boot img

After upgrading, use

fastboot boot patched-init_boot.img

(replace to your actual patched img file name, or rename your patched img file)

to temporarily boot into the Magisk on the upgraded System and then apply Direct install

Sorry, I'm not going to describe every single detail,please google if not familiar with.

Eg, it's important to understand the difference between fastboot boot vs fastboot flash boot, etc

Further, if you have TWRP, you can upgrade the ROM and simply flash Magisk through TWRP.

Both Direct method (above) and TWRP will know and take care themselves to permanently patch the correct img
[Magisk] gloops100:
Clear, thank you !

I'll test this process and I'll backup the new init_boot.img and patched_init_boot.img.

To save these files, the only way is to download the upgrade.zip with a computer ?
[Magisk] zgfg:
I usually download and unzip by MiXPlorer on the phone, and store/share to the clouds Mega)

PC is needed only for fastboot and if you would have to dump payload.bin (although there is also Payload Dumper for the phone, but I didn't try)

To download the correct OTA zip, install MIUIDownloader app from Playstore

Besides - do you have MIUI 14 (or older, 13) or HyperOS?

Did you test your TWRP and does it boot and correctly decrypt the Storage with your pin?

For your OTA upgrade, are you staying on the same Android version (otherwise, TWRP may not work after the upgrade)

Last but not the least, did you consider switching to Xiaomi.eu - do they have Stable or Weekly for your device
[Magisk] pndwal:
I may not have read all answers here properly or properly understood your method, but there may be several issues involved, especially with Install to inactive slot method...

Not sure why stock image backup was missing... Maybe your initial flash method using Franco Kernel Manager?... Strange you needed direct install after that too... Usually only needed to complete root after .zip flash while system is not booted. (Unless booted system can't set up selinux/modules rule directory any longer, since random seed no longer used for setting path)...

Are you perhaps using an old Magisk version not updated for init_boot patching?... Cos I don't understand why flashing stock boot.img fixes stuff on you device either; Magisk shouldn't have touched boot.img on your A13 LV device...

Did you use TWRP retention script from @osm0sis described too?... I don't know much about that, but guess it may (possibly) mess with boot.img, especially if an old version... @osm0sis might pitch in on this possibility.

Supposing late Magisk and properly restored stock images, Flash to inactive slot method described in official OTA page:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md

may work, but there's a reason it got unlinked from Magisk documentation page; the method became unreliable for a number of reasons (due to Android changes), some of which were fixed, but for late devices (eg pixel 6,7,8) many report issues with this method... According to @vvb2060, new ROMs/updates are now enforcing partition digest checks after booting to updated slot so the slot is marked bad on rebooting since Magisk patching was done before the reboot... I put a link re. vv's comment about Install to inactive slot broken here:

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

Strangely, some late Pixel users still report success... I don't know if OEMs other than Google have adopted these checks either, so this may or may not be an issue for your A13 LV Xiaomi device...

... Seems you suspect incompatible modules also... If this is the case I'd be using a method in Magisk FAQs to remove them... Nb. The instructions for Magisk Safe Mode may be quite misleading due to timing differences for key press detection; if you want to use this method please see my revised instructions:

https://github.com/pndwal/Magisk/bl...led-a-module-and-it-bootlooped-my-device-help

(I have this PR: Update faq.md)

🤠 PW
[Magisk] J.Michael:
Even when you think that you are replying to the last post in the thread, you should do something to indicate to whom you are speaking.
[Magisk] pndwal:
You will always need to replace "boot.img" with "init_boot.img" in patching/flashing instructions if they were written for devices launched before Android 13... If you patch and flash boot.img on yours you'll have issues... even if boot.img (yours contains only GKI kernel) still functions, when taking OTA and system expects stock images the process will fail... Maybe that's what you did above?

I thought that was basically what you were trying to do... No reliable way to say it will work... See my post above and recommend you become familiar with official OTA doc @J.Michael already linked here:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md

for better understanding... Modules will be preserved if it works as after reboot and inactive slot becomes active as you still have the same data... Magisk modules and other configuration files reside at /data/adb. PW
[Magisk] Feenix0:
I've just installed LineageOS for MicroG on my OnePlus 7T (hotdogb), and the basic installation boots fine. I installed the Magisk 26.4 app, and followed the instructions here to patch my boot.img, noting that the device does use a ramdisk. After Magisk created a patched boot image, I rebooted into fastboot and flashed the patched image as instructed. After doing so, the phone only boots into fastboot, bootloader, or recovery. If I reflash the original boot.img, the phone will boot up as normal.

LOS for this device comes with boot.img, dbto.img, recovery.img, super_empty.img, vbmeta.img, and the zip file. Did I patch and flash the wrong image? I'm sure I followed the instructions. Is there something different I have to do because it's LOS?
[Magisk] pndwal:
@gloops100

Please see edits in my posts above incl. link for official Magisk OTA doc... Seems it wasn't linked before so you probably never saw it. 🙃 PW
[Magisk] zgfg:
Post the screenshot (even better the log) when you were patching boot.img

You can still do it, boot without Magisk but with the Magisk app

And a screenshot how Magisk app reports Ramdisk Yes or No

---

When you patch the image, inspect did Magisk app enable/tick Recovery option

Make sure you disable that Recovery option before patching, and try to boot with that patched img

fastboot boot patched-boot.img
[Magisk] pndwal:
Magisk is always in ramdisk!... Just some A9 LV A-only devices (legacy SAR) only have ramdisk in /recovery partition so Magisk may need to be installed there... Yours is a 2SI device anyway so certainly has ramdisk in /boot.

You should be patching and using boot.img from current ROM... (boot.img contains the kernel as well as ramdisk and must match system from ROM.) If you patched and used stock boot.img, that's wrong... 🤠 PW
[Magisk] Feenix0:
This is a fresh install, not OTA.

I used the boot.img that I downloaded from https://download.lineage.microg.org/hotdogb/

As it turns out, the instructions I found here got me most of the way there. After sideloading the Magisk zip and rebooting, Magisk complained about needing to reboot to do some configuring. Then apparently Magisk 27.0 just dropped, so I installed the app, rebooted, then ran the direct install for the Magisk flash, and now it seems to be working. This is very confusing. I'm not sure how I'm going to replicate this if needed!
[Magisk] pndwal:
🤔 ... That user was trying to install Magisk to inactive slot after OTA... Why are you mentioning that?

Oh... Hope you definitely matched the correct image version then... Looks like an easy way to get the wrong one... Most users just extract boot.img from current custom ROM archive per instructions...

Suggest just following official instructions... Generally not confusing at all... 🙃 PW