yashsingh1/xdaforums huggingface dataset:
[Magisk] sawdoctor:
I'm on QPR2 beta 1 on the pixel fold running the previous canary magisk that was updated to fix the zygisk issue. I always update with direct install, i was holding off on this week's update but will test to confirm if it was an isolated issue
[Magisk] Wotanstahl:
thank you so much, so i will try it with twrp. just booting into that recovery and than installing the package?
[Magisk] Lord Sithek:
Yea. But make a backup of your data just in case, you know that wierd things happens 😉 Dont wanna be blamed for your data loss 😅
[Magisk] pndwal:
I believe you can flash Magisk from LOS recovery also...

That just won't decrypt data (I think reasoning was that that makes LOS recovery easier to support for various devices) but should be able to flash magisk.zip from accessible SD card etc... PW
[Magisk] hanschke:
sawdoctor this is how I do it all the time. I use the same settings now like before and you and all works fine. At the moment I dont have the time to do a better bug report and update magisk manager directly and lose root again. I think if you will do the update like me before you will get the same result. Sorry about not doing a better report for now. Maybe in a few days but I wait for an important call and cannot miss it.​
[Magisk] Wotanstahl:
i found this post here: https://xdaforums.com/t/guide-magisk-on-lineageos.4371987/

so looks like it should work 🙂

Yes, of course. I mean in worst case i have to set up the tab again. It does not really contains any important data.
[Magisk] ricpdjrr:
I just rooted my S8 Tablet on android 14. My first try was with the latest Magisk release, however that did not work. it was suggested to try Magisk 26.0 . That worked perfectly. I am a avid Tasker user and now when I go to import a Taskernet link I get the message... (Using Chrome)

Important:​

To import this into Tasker you need to be on an Android device.

You can either:

Open this page on an Android device

Click here to reveal a link that you can then send to your device remotely with Join.

Download XML File and manually import it.

In any case click below to install Tasker

any ideas why the taskernet site does not think I am on a android device?

Thanks, Rich..
[Magisk] pndwal:
Latest Stable or Canary build doesn't work on S8? PW
[Magisk] ricpdjrr:
That was experience. I only tried once with latest stable and It I got a error screen on boot that said version 'data may be corrupt ' . Here is the post I followed

Post in thread 'Root Guide for Galaxy Tab S8/S8+/S8Ultra' https://xdaforums.com/t/root-guide-for-galaxy-tab-s8-s8-s8ultra.4423095/post-89189950

And

Post in thread 'Root Guide for Galaxy Tab S8/S8+/S8Ultra' https://xdaforums.com/t/root-guide-for-galaxy-tab-s8-s8-s8ultra.4423095/post-89211522
[Magisk] J.Michael:
If your browser is set to request desktop pages, the clever web site might think you are not on Android.

Google for a web page that will tell you what your UserAgent string is. Or check your browser settings. Or use another browser -- one you don't usually use and therefore are unlikely to have reconfigured.
[Magisk] ricpdjrr:
haha.... Thanks for the tip, reading that site docs had me check the desktop site option in chrome. That is all it was. It did the same thing on my not rooted pixel 2XL.

After just rooting I ASSumed it was a root issue and found it to be just another of many "User-ERROR'

Thanks, Rich..
[Magisk] pndwal:
So not actually latest Magisk release, just latest "public" release...

Seems fix was already merged from 26403 Canary build (two weeks ago) w/ this commit:

Fixes for Android 14 QPR2 B2 … Added new method signatures and arguments

KieronQuinn authored and topjohnwu committed 2 weeks ago

Original PR comment:

https://github.com/topjohnwu/Magisk/pull/7620#issue-2036772290

👀 PW
[Magisk] sawdoctor:
I have a feeling this is the issue that was affecting the Pixel fold as well so fingers crossed the next update works

suppprt `init` that does not directly invoke `/system/bin/init` · Issue #7661 · topjohnwu/Magisk

installed the 26404 apk. extracted boot.img from rom (e-1.17-q.zip). pushed the boot.img to device and using the magisk app created the attached patched boot.img. Pulled the patched boot.img. Reboo...

github.com
[Magisk] HippoMan:
I'm trying to accomplish something which might be impossible, but I'm posting here to see if perhaps there's a way. I want to be able to run Magisk and also run TWRP via "adb reboot recovery", which currently doesn't work for me.

I'm running stock Android 11 on a Pixel 5. There is a workable TWRP for that OS/device. I'm also running Magisk Kitsune 26403.

The way I set this up is ...

(1) Install A11 stock.

(2) Unlock bootloader.

(3) Via the bootloader, do a "fastboot boot [TWRP img file]"

(4) Via TWRP, install the TWRP installation file.

(5) Reboot to system.

(6) Install the kitsune APK file

(7) In the Kitsune manager, patch the boot.img from my Android 11 OS bundle.

(8) Go back to bootloader and flash the patched boot image.

(9) Reboot to system and finish setting up kitsune.

If I stop at step 5, i can get into TWRP via "adb reboot recovery", but of course, Magisk isn't installed at that point.

Once I finish all 9 steps, Magisk is fully functional, of course, but "adb reboot recovery" just gets me to a dead android screen, and I understand why this occurs: it's because step 8 overwrites the TWRP-resident boot image.

I can still get into fully functional TWRP any time I want by going into the bootloader and re-running step 3. But is there any way that I can perfrom a different installation procedure which will allow me full Magisk Kitsune capabilities *and* the ability to get into TWRP via "adb reboot recovery"?

Thank you in advance for any ideas and suggestions.
[Magisk] dcarvil:
In step 7, shouldn't you be patching the TWRP modified boot image from your device, instead of the image from A11? I've never tried this, and don't use Kitsune, so I am just speculating.
[Magisk] HippoMan:
Yes, thank you. I thought of that possibility, but by step 7, I still don't have root permissions, and so I can't access the boot image from my device.
[Magisk] J.Michael:
Check whether your TWRP offers to "back up" specific partitions. If it does, and you can get the backup placed somewhere non-privileged...

Or try installing TWRP *after* installing Magisk. If TWRP installs itself in the recovery part of the initrd, maybe it won't disturb what Magisk did.
[Magisk] dcarvil:
It's been a very long time since I have used TWRP, but I thought TWRP provided a way to copy the boot image.
[Magisk] HippoMan:
Thank you, but for Android 11, TWRP doesn't install in the recovery partition, but rather in the boot partition. If I flash TWRP after installing Magisk, then I lose Magisk.

That's a result of one of the "improvements" (ha ha!) that the Googlefrinchians instituted starting with Android 11.
[Magisk] dcarvil:
Another possible way, if you cannot copy the boot image with TWRP, is to temporarily boot a rooted image without flashing it at step 5. Then you can use dd to copy the TWRP modified boot image.
[Magisk] HippoMan:
Yes, I was considering something like that.

But just now, I figured out how to solve my problem!!! It involves utilizing the older Magisk installation procedure from back in the Stone Age days of Magisk 23.0 ...

Steps 1 through 5 are the same as above. And then ...

(6) Copy kitsune.apk to kitsune.zip on the desktop computer.

(7) adb push kitsune.zip /sdcard/

(8) adb reboot recovery

(9) In TWRP, install the kitsune.zip file from /sdcard/

(10) Reboot to system

(11) Finish setting up Magisk

Doing it this way allows Magisk to patch the currently existing boot image, which is the one where TWRP is already resident and functional.

Now, Magisk is running fine, and I can boot normally into recovery via adb and from the device itself.

Thanks again to both of you, and Happy New Year to you.

Excelsior!
[Magisk] J.Michael:
Did you actually try flashing TWRP after installing Magisk?

If you don't have a recovery partition, then what you call "flashing TWRP" *must* be "modifying boot image so TWRP replaces whatever is in there to provide a recovery function". So if you do that after installing Magisk, it should be able to replace the recovery part of the initrd without disturbing Magisk. In theory. Which, as Yogi supposedly said, isn't the same.
[Magisk] HippoMan:
Yes I did, and I definitely lost Magisk. The TWRP installation actually posts a message on the screen saying something like "You now no longer have Magisk enabled".

And after rebooting to system, Magisk was indeed no longer installed.

Whatever TWRP does in the boot image when it's installing itself ends up removing whatever Magisk might have previously done in that same boot image.

But what I described in this message did indeed work:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-89250820
[Magisk] zgfg:
You must first successfully install TWRP, backup your boot.img already patched with TWRP, then patch that backed up boot img file from Magisk app, then finally flash it again in TWRP to the Boot partition

Then, you will have both Magisk and TWRP in the same Boot partition.

Not sure does it work with Kitsune but in Magisk it works - I do it for two+ years with A11, A12 and A13 on Xiaomi, with all the Magisk Canary version in the meantime (the procedure was generally discussed here)

But it is crucial that you first install TWRP and backup Boot with the TWRP already installed - when Magisk patches, it will leave TWRP, hence you will have both at the end

If you go the other way, TWRP will remove Magisk patch from Boot and only TWRP will remain - that's the issue on TWRP side for devices with Recovery imbedded to Boot.

Maybe some TWRP versions/ports could do that correctly, but if you go with TWRP first, Magisk second, then you should be ok
[Magisk] HippoMan:
Thank you. Yes, I understand about backing up the boot.img that's already been patched with TWRP, then patching that from the Magisk app, etc.

However, that requires more manual steps to take than the way I did it here ...

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

By copying magisk.apk to magisk.zip and flashing that from within TWRP, the TWRP-based boot.img ends up getting properly patched by Magisk in the same way that you outlined above.

And as I've mentioned, after I did it this way, Magisk and TWRP are both working with no problem on my Pixel 5.
[Magisk] shoey63:
I thought flashing Magisk as a zip in Twrp was discouraged, if not deprecated?
[Magisk] HippoMan:
I think it may not be reliable in some cases, depending on the version of Android and the version of TWRP and the version of Magisk and maybe the phone itself, but it worked for me.

Mine: Pixel 5, Stock Android 11, TWRP 3.7.0_11-0, Magisk Kitsune.
[Magisk] zgfg:
Why do you need to archive patched boot img to the zip

You just do additional reboot(s) to install TWRP, backup Boot, patch it by Magisk and then to flash it over.

One short time booting to the upgraded System without root, to patch the new boot.img with the TWRP already in, will not cause you to loose anything (root apps, modules, etc)

Ii don't have Pixel but probably PF can do the steps

For custom ROMs, their (full) OTA/upgrade zips may already include TWRP (some custom Recovery) integrated to the boot img. Hence you don't need to reinstall TWRP to the Boot and to backup the Boot then

Eg, for my Xiaomi.eu custom ROM, it comes with TWRP integrated into the boot.img

Hence I download Xiaomi.eu upgrade zip, extract boot.img, patch from Magisk app (all before upgrading), reboot to TWRP, flash Xiaomi.eu zip AND STAY in TWRP to flash also my newly patched boot img and ONLY THEN I reboot to the System - at that time I already have Magisk again, with the preserved TWRP that was pre-installed to the Recovery embedded into the boot img as distributed with Xiaomi.eu OTA zip. So I can reboot to TWRP or to the System with Magisk
[Magisk] HippoMan:
Yes, but I don't know how to back up the TWRP-based boot.img without already having root, and investigating and testing that would have taken me more time. If I already knew how to do that, it possibly could have been done quickly.

The procedure I used took me around 3 minutes:

(1) cp magisk.apk magisk.zip

(2) adb push magisk.zip /sdcard/

(3) boot into TWRP and install /sdcard/magisk.zip

(4) restart device

PS:

My Pixel 5 A11 device does not come pre-installed with TWRP, so when I extract its original boot.img, that is non-TWRP. After I flash TWRP, then I have a device whose boot.img is based on TWRP, but without having root, there is no way that I know of to extract *that* TWRP-based boot.img for later patching with Magisk.
[Magisk] zgfg:
Don't understand why do you need ROOT (Magisk)

For (re)nstalling TWRO you may need Fastboot and then you need only TWRO to backup the Boot

You only need to have Bootliader unlocked but that is irrelevant of your OTA - and if OTA would lock BL you would have general.ptobkems, and packing to zip would not help
[Magisk] HippoMan:
I didn't understand how to extract boot.img from the TWRP-installed OS.

You're saying that this can be done somehow via fastboot. I'll check the help text for fastboot after posting this.

But like I said above, given that I didn't know this, and since it would have taken me time to discover how to do it, I opted for the "old fashioned" way to install Magisk via TWRP, and it quickly worked.

In the future, if I ever want to do such a thing again, I'll consider doing it via a fastboot-based extract of the TWRP-enabled boot.img.

UPDATE: After checking the fastboot help text, I see now that "fastboot fetch" seems to be able to extract boot.img.
[Magisk] HippoMan:
% fastboot fetch boot.img twrp-based-boot.img

fastboot: error: Unable to get max-fetch-size. Device does not support fetch command.

So that doesn't seem to work on my A11-based Pixel 5.

Oh well ... (sigh)

Given that flashing magisk.zip from within TWRP is deprecated, I guess I'm just lucky that it worked on my device and OS, just like I'm UN-lucky about "fastboot fetch" not working for me.
[Magisk] zgfg:
You need Fastboot just for fastboot boot into TWRP, then you will permanently install TWRP in the TWRP itself, and then - still staying in TWRP you will backup the Boot partition

Those steps depend on the installation procedure for TWRP

However, in my case TWRP (or it could be some other custom Recovery) comes preinstalled into the boot.img packed in my Xiaomi eu custom ROM update

So I let their Updater to download the zip but don't let it to reboot to upgrade the ROM. Or I download the OTA package manually. One way or another, it is the same zip package.

I open that zip from Mixplorer and copy the boot img out. I patch it from the Magisk app (all on the phone and before really upgrading the ROM)

Then I reboot to TWRP, and flash two files in a row - ROM upgrade zip package and the boot img I had just patched before, and in that order

Again, that's simple for me bcs Xiaomi eu custom ROM is distributed with the custom Recovery in boot.img - since they need custom recovery for their OTA procedure

If I would not have Magisk, their Updater would download OTA zip, it would reboot to TWRP, flash the OTA zip and reboot back to System. And after the upgrade TWRP will be again in the Boot bcs Xiaomi eu needs the same TWRP again for the next ROM upgrade

Some LOS ROMs may do things similarly, with the LOS custom Recovery instead of the TWRP
[Magisk] HippoMan:
Oh, OK. So just back up Boot via TWRP.

I did so, and when I examine that backup on my device, it isn't a ZIP file. It's just a directory with the following name:

2024-01-02--13-31-13_RD1A2008110020

And when I look at the contents of that directory, it contains 3 files:

boot.emmc.win

boot.emmc.win.sha2

recovery.log

When I do "file boot.emmc.win", I get this result:

boot.emmc.win: Android bootimg, kernel (0x1c59868), ramdisk (0x62c)

Does this mean that it's a bona fide boot.img file?

And PS, I don't even need fastboot to get into TWRP. I can just do "adb reboot recovery".
[Magisk] zgfg:
boot.emmc.win

is your backed-up boot img (with the TWRP in, if you had permanently installed TWRP before backup and after the ROM upgrade) - it does not matter how is it called, give it (with that name) to Magisk app to let it patch, and try

TWRP can be usually installed by:

fastboot boot <twrp.img>

(not fastboot flash boot ...)

and then, while in TWRP, find a button for permanently installing TWRP (it does that then from itself, without the need for zip or img file)

Then, still in TWRP, backup to get that boot.emmc.win file

So you first upgrade the ROM, reboot to Fastboot, do as above, reboot to System without root, patch boot.emnc.win from Magisk app (if OTA did not wipe /data, you will still have Magisk app although withot root but it doesn't matter for patching), reboot to TWRP and flash the patched boot.ing and flash to bow the re-rooted System again
[Magisk] HippoMan:
Well, thank you very much, and I'm glad that I now know how to do that.

But if I ever need to redo this on my A11-based Pixel 5, I'll still just use the "flash magisk.zip via recovery" method, which I know works perfectly.

However, if I ever have a different device that runs TWRP and on which I want to install Magisk, I'll use this "backup boot" method.
[Magisk] Wotanstahl:
Hey again. Today i installed Magisk on my Samsung Tab S5e with LineageOS 20 via sideload in recovery mode. It was no problem and worked fine. Later the day i updated LineageOS via the auto updater. After this Magisk was not installed anymore. Is that normal? Do i have to install it again every time?
[Magisk] rogers11:
Yes, via Recovery after each update (put it on SD-card) and additionally from within Magisk after reboot.
[Magisk] Wotanstahl:
why sd card? first time i installed it via pc with usb-connection. booting into sideload-mode. How to do it with sd card?
[Magisk] rogers11:
Reboot into LOS-Recovery, choose update, from SD-card and select the Magisk.zip (renamed APK).
[Magisk] Wotanstahl:
the menu does not show this option - only "apply from adb". Is it only shown when a sd-card is installed? Currently i have none unfortunately.

edit: apply from adb is not possible?
[Magisk] rogers11:
Most probably yes. But I never tried it without.

This will work too.
[Magisk] Utini:
This is still an issue on a completely new Pixel 8 Pro after flashing todays January A14 update.

[UID] 10334

Target UID: 0 PID: 6330 Mount ns target PID: magiskd

/system/bin/sh

Denied

Could this be the original magisk app which also disappears right after starting the magisk app for the first time (since I am hiding magisk with my own app name)?!
[Magisk] pndwal:
Shamiko v1.0 Latest

Shamiko-v1.0-290-release

1.0​

Hide more traces of Zygisk, passing more detection (e.g., ACE, GoTyme Bank, MyTransport.SG, ZainCash, DBS PayLah!, Singpass, Marriott, BPI, Apps using liapp, Apps using Arxan like CaixaBank Sign, etc.)

Better support KSU

Hide some traces introduced by other modules (e.g. PlayIntegrityFix)

Guards the peace of Machikado

👍 PW
[Magisk] xcl1pse:
Add notes only work for magisk canary 26404+, magisk alpha 26404+ :)
[Magisk] pndwal:
Nah... Flashes fine w/ latest TJW Canary... But Shamiko-v0.8.0-210-release.zip and others required Alpha... PW

Edit: My bad!...
[Magisk] xcl1pse:
Latest canary TJW magisk is 26404. I mean work from 26404 and so on
[Magisk] traversone:
unfortunately, this version of Shamiko makes (at least 3-4 of them I tried in denylist) the relevant apps crash! I guess all the apps I want to hide the root from will be crashing. Of course latest canary is installed, my system runs Hades Rom A10 on Samsung S8. On other hand, on Samunsg S21 stock A13 no issues are found with same Magisk/Shamiki version. Thank you!
[Magisk] swieder711:
Currently running Shamiko .7.5 on January stock Pixel 8 Pro.

I tried to install Shamiko 1.0 with Magisk 26402 and it FAILED.

EDIT: Going to update to Magisk alpha 26404

EDIT2: Shamiko 1.0 installed successfully with Magisk Canary 26404
[Magisk] sawdoctor:
Just a heads up a few people are losing root with the latest canary. I thought it was an issue with QPR2 beta but reading GitHub there's some other devices as well. Looks like there's a potential fix waiting to be merged
[Magisk] swieder711:
I have root with Magisk Canary 26404 on a Pixel 8P running the January update.
[Magisk] traversone:
Maybe some regression was introduced by shamiko 1.0 on A13- ?
[Magisk] xcl1pse:
This release mean to be focus on KernelSU and ZygiskNext. For A10 will address them later. Can I know what app is that?
[Magisk] traversone:
after the 1st reboot after latest Shamiko setup, Google Wallet hanged and then crashed, Outlook same, Bank app same, etc..etc... all of them are in denylist of course
[Magisk] xcl1pse:
Already test with clear data the app in denylist?
[Magisk] traversone:
yes...1st thing done by me
[Magisk] xcl1pse:
Shamiko in blacklist mode?
[Magisk] traversone:
yes
[Magisk] xcl1pse:
Ok so your using official magisk right? seems crashing happen on latest TJW commit
[Magisk] traversone:
currenty using Canary 65207f96 (latest canary)
[Magisk] xcl1pse:
So far I only got info from latest TJW magisk canary.

Edit: Also confirm latest shamiko cant work properly on A10
[Magisk] traversone:
thanks to developers: latest Shamiko-v1.0.1-300 works with no issue in the same A10 environment who failed earlier! thanks again
[Magisk] pndwal:
Zygisk-Next-v4-0.9.1.1-189-release Changelog:

1. Fix compatibility on Android 10 and some Magisk variants.

2. Requires Magisk 26402+ / KernelSU (Manager) 11425+.

3. Technical details: Zygisk Next is incompatable with kitsune Magisk's "sulist" feature. This is because Zygisk Next rely on ptrace init to inject into zygote, but it has already been traced by magiskd.

Bolding mine. 👀 👍 PW
[Magisk] pndwal:
Shamiko-v1.0.1-300-release Changelog:

Fix Android 10

👍 PW
[Magisk] pndwal:
Wow!... LSPosed Archived!?:

https://github.com/LSPosed/LSPosed

😦 PW
[Magisk] sawdoctor:
FFS , it really doesn't matter what happened no one should speak to anyone like that especially a dev/dev team that gives their work free to the community
[Magisk] pndwal:
So "Zygisk Next and Shamiko also stop maintenance"...

I can't post screenshots of immature and vulgar posts from Delta/Kitsune dev, but seems he's done his damage... TG link:

https://t.me/LSPosedArchives/4156?single

☹️ PW
[Magisk] xcl1pse:
Honestly the community has been unhealthy lately. Just enjoy it while it last~
[Magisk] osm0sis:
Hopefully they change their minds. ☹️

@vvb2060 @canyie @yujincheng08 are straight up geniuses, so it would be a shame if we lost them to this kind of bullsh*t.

The childish behavior from all needs to stop.
[Magisk] GohanBurner:
Shamiko has ceased development? Looks like I'm selling my Pixel 8 Pro then. No need for it if I can't use gPhotos without being able to also use work/banking apps.
[Magisk] HippoMan:
Unless I'm misunderstanding something, those remarks showed up (in the Delta/Kitsune TG channel?) in a conversation with the Kitsune/Delta dev, but he himself isn't the original author of those remarks.

This was discussed a little while ago in the PIF TG channel, but that channel got closed for commenting just now with its content deleted, and so I can't go back to copy-and-paste the comments that explained this.

UPDATE: Oh, the PIF TG channel has re-opened, but the legacy content is gone.
[Magisk] GN-z11:
I received multiple harassment recently as well so I kinda feel the same.
[Magisk] sawdoctor:
I can copy and paste it as i have anti delete on my telegram. How long ago was it?
[Magisk] huskydg:
Let ammonia reacts with hydrochloric acid to produce ammonium chloride

How to make smoke without fire

t.me

Let ammonia reacts with hydrochloric acid to produce ammonium chloride

How to make smoke without fire

t.me