yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Yup, @osm0sis is trying to keep this working/as is (it's his handiwork/baby after all), but Magisk Devs have in mind to remove addon.d:

https://github.com/topjohnwu/Magisk/issues/3820#issuecomment-1364700096

Shana has produced a POC addon.d module:

https://github.com/topjohnwu/Magisk/issues/3820#issuecomment-1364699640

It remains to be seen how such module support will work for custom ROM users or how long native addon.d will stay, but hopefully all @osm0sis' code/work can be retained/keep working for LineageOS users etc as before...

👀 PW
[Magisk] shoey63:
Takes about 20 seconds for 2.9 GB

True that.

Totally useless if you have only one unrooted phone😊

However, the pc version should do the same, without bothering with python.
[Magisk] Lughnasadh:
Yeah, I'm aware that back in June vvb2060 stated that the OTA feature in Magisk doesn't work on Pixels because the partition digest calculations were not overwriting the original values . To my knowledge, no one has submitted a PR for that issue. Nor am I aware of any changes since then to the digest checks.

There is also a related issue here.

Nonetheless, as stated earlier, some people have had success as recently as last month's January security update. It still holds, though, that the majority of people are unsuccessful, at least in my observation. So I wouldn't say it was "broken", per se, but rather "much of the time does not work as intended". I still advise people to not use this method.

On a side note, I have also seen a few people who were able to successfully take an OTA while rooted. Of course they lost root after they rebooted, but they were still able to successfully update while rooted even though the update should have failed due to the pre-OTA block verifications.

Below is a quick sample of success stories, from July to last month (I think 3 of them are in December). There are others and I have also seen people report on Telegram that they were successful.

https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4505353/post-88003359

https://xdaforums.com/t/updating-after-root.4526975/post-87831189

https://xdaforums.com/t/updating-after-root.4526975/post-87838227

https://xdaforums.com/t/updating-after-root.4526975/post-87862649

https://xdaforums.com/t/your-device...-with-magisk-ota-method.4515951/post-87843083

https://xdaforums.com/t/february-1-...ure-major-android-betas.4508257/post-87639909

https://xdaforums.com/t/method-to-u...data-and-retaining-root.4356065/post-87474201

https://xdaforums.com/t/guide-pixel...ate-root-pass-safetynet.4356233/post-87299859

https://xdaforums.com/t/guide-pixel...ate-root-pass-safetynet.4356233/post-87133287
[Magisk] pndwal:
So that'd be Payload Dumper Go for Android...

payload-dumper-go (ported the original Python payload_dumper into Go) is officially pre-built for macOS, Windows and Linux...

So Payload Dumper Go may now be the go-to, way-to-go solution for PC etc...

But, aside from initial Magisk installation it seems Payload Dumper Go for Android can be used for OS updates while being very useful for avoiding transferring full OTA to PC to me, no? 🤔

I have no experience with A/B devices and payload.bin format for seamless streamed updates, but for updating already rooted A/B devices can't we avoid transferring full OTA to PC this way by

1) downloading full OTA directly to device

2) extracting boot.img using Payload Dumper Go for Android

3) taking update* and rebooting to new unrooted slot

4) patching boot.img w/ Magisk App

5) Transferring patched-boot.img (only) to PC

6) using patched-boot.img to fastboot boot (temp boot) system with root and then Magisk App Direct install to permanently root system, or

6b) fastboot flashing patched-boot.img to permanently root system?

* Nb Users should turn airplane mode on before rebooting to prevent PI deviceIntegrity failure and device becoming uncertified due to loss of root after rebooting... Turn airplane mode off after root and USNF are restored... Thanks @BillGoss! 👍

... Please say if I'm missing something..🙃 PW
[Magisk] BillGoss:
You need to turn airplane mode on in step 3 before rebooting otherwise your phone will become uncertified since it's unlocked and unrooted after rebooting.

Once you've rooted it and installed USNF, then you can turn airplane mode back off.

PS: sent you a PM
[Magisk] shoey63:
I can think of a few scenarios.

- Updating from old firmware, when the OTA method still worked.

- Forced update, even though rooted.

- Confusing an OTA update they did on an older Pixel where it still works and reporting it as working on 6/7.

- Trolling 😂
[Magisk] Lughnasadh:
One problem is that the Pixel 7 was released in October, well after vvb2060 said in June that the method didn't work on Pixels.

Actually a forced update on the Pixel 6 moving from A12 to A13 while rooted isn't inconceivable since they really wanted people to update, especially given the new anti-rollback protection situation that came with the A13 bootloader. If memory serves correctly in this old brain of mine, some of the instances where people were able to update while rooted may have occurred while moving from A12 to A13. But I would think users would know when they had a forced update versus manually updating through the Magisk OTA feature.

Confusion and trolling....well, what can I say 😅

I can actually think of a few reasons why it didn't work when it should have, aside from the partition digest checking scenario:

-They had Magisk mods installed that needed updating and weren't disabled, causing a bootloop. They then assumed the OTA method didn't work because it bootlooped, rather than thinking a mod may have caused it (this happens quite often).

-They were using a custom kernel at the time of the update. The Magisk restore function won't return all the images a custom kernel modifies to stock since custom kernels involve modifying the boot (P6 & 7), dtbo (P6 & 7), vendor_boot (P6 only), vendor_kernel_boot (P7 only), and vendor_dlkm (P6 & &7) images.

Also, on the P7 the vbmeta image has to be modified to flash a custom kernel (via disabling verity and verification). In the early days on the P6 the vbmeta image also had to be modified to be able to flash a custom kernel, although you could do it by just disabling verity and leaving verification alone.

-They modified some other partition/image which wasn't returned to stock beforehand.

Probably a couple more scenarios that aren't creeping into my brain at the moment given the cobwebs and coffee still brewing 🙃

I think there are just too many examples where it worked to say that it is completely broken. On the other hand, there are too many examples where it didn't work, and code changes, to say that it does work properly.
[Magisk] shoey63:
For pixel 6 you nailed it, and @BillGoss ,s airplane mode trick is something I hadn't thought of and will try.

My other slot A/B device is (as you are aware) is ROG phone 3, which is a strange beast.

Not only do you unlock the bootloader with their "special app" instead of fastboot (no OEM unlock option in developer options), but updating if rooted is weird as well.

You download the new firmware to internal storage and reboot.

Then you get a notification about a new update and after accepting, it installs to the opposite slot.

From there it's a simple matter of installing magisk to the opposite slot after OTA and rebooting. No restoring of images required.

Different horses for different courses 😋
[Magisk] BillGoss:
Fyi, I got the the airplane mode trick from @osm0sis in https://xdaforums.com/t/tools-zips-...ices-platforms.2239421/page-149#post-84764713
[Magisk] topperdoggle:
+1 from me. Metro Bank was working fine until a couple of days ago. Following with interest.
[Magisk] xabier-bo:
Hello

I have had a problem with various complications (I won't explain them all), and now I have a working mobile, but I can't re-root again.

Device:

- Xiaomi Lisa

- It was rooted with Magisk 25.2

- And various modules

- It does not have TWRP recovery, and Orange Fox does not decrypt data on Android 13

Situation:

- I received the OTA Android 12-> 13 (MIUI 13->14) (stock EU).

- I decided to download it to extract boot.img and patch it.

- Against the usual (and configured), instead of waiting for confirmation to install (time to apply the standard OTA update procedure: restore stock images and flash Magisk to empty slot), it started the process.

- When I realized I did the restore images, and let it reboot

- It ended up in a strange bootloop (at least for me): a few seconds after booting, showing the launcher, and even being able to open some app, the phone reboots and ends up in MIUI recovery.

- (...)

- Finally I manage to reflash the new ROM ("except storage"), and the phone boots fine.

- I patch the new boot

- But when I do the standard boot on the patched image, the problem of that "strange" bootloop is reproduced.

- Attempts to apply uninstall.zip fail because the recovery does not mount data.

- ((Finally, at home we have another Lisa. I opted to completely uninstall Magisk, flash the new ROM, then boot with the patched image and install Magisk, and it did not give any problems. I'm thinking to do the same in future...)).

The questions begin. I will also appreciate any rectification if something I say is not correct, to continue learning:

- It seems that there was something left of Magisk that creates a conflict, no?

- Since the modules and Magisk are inside \data, it is not possible to uninstall with uninstall.zip, is it?

(in fact in one of the tests with OFox (which does not see \data) it instead installed Magisk, giving the same problem

- as the mobile is not really rooted, there is no chance I could delete modules folder, right?

- And only with the mobile rooted I could ask the Magisk Manager to uninstall completely, no?

But as it does not give me time to run it because the phone restarts, and when it does is without rooting, I can't

- The time to reboot with the mobile temporarily rooted begins once I have entered the unlock pin. As I said, it doesn't give me time enough to interact with the applications.

Would there be any script (I'm not a developer) that I can run from terminal as soon as I have unlocked the phone, so it has effect before the device restarts? (stop process, remove folder...)

- Any idea (that does not involve formatting data...)?

Thanks
[Magisk] pndwal:
Much in this section of @Didgeridoohan's Wiki:

https://www.didgeridoohan.com/magisk/MagiskModuleIssues#

Scroll down to Disabling/uninstalling modules manually... First option is w/ ADB from PC... Many more...

Look around that wiki first for other pointers too... It's old, but it's gold... 👀 PW
[Magisk] xabier-bo:
Thanks, so you give me some hope...!!!

As I said, for keep on learning: what I posted makes sense?

Or there is some mistake in the reasoning?

I'll read the wiki but was just thinking that a prepared and "fast" executed adb line to remove (knowing what to do!) moduls/Magisk, could do
[Magisk] xabier-bo:
Still facing some issues (don't know which module is causing problems), but

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

did it.

At least I've the phone rer-ooted

Thanks again
[Magisk] V0latyle:
Just FYI, Zygisk does not appear to work on the Android 14 Developer Preview. Magisk patch works fine, root is good, but Zygisk always shows No, even after toggling and rebooting.
[Magisk] pndwal:
Yup... Thought that would fix bootloop with root...

What other issues? I'm guessing S/N ctsProfileMatch and PI deviceIntegrity w/ USNF?... If so, many users now face this:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88114877

🙃 PW
[Magisk] pommedefrance:
Hello

with A13, I can't see the work profile apps anymore, so I can't hide them from magisk and they detect the root

Is there anything I can do?

a bug with shelter ?
[Magisk] V0latyle:
I really, really need to stay away from Reddit. The questions there. "How to flash modules in Magisk with locked bootloader?" 🤬
[Magisk] zgfg:
On Reddit, everything is possible. Sky is your limit😁
[Magisk] m0han:
Dread it. Run from it.... The hardest choices require the strongest wills.
[Magisk] V0latyle:
Dumb question...

Has anyone tried installing Magisk on an Android Device Emulator?
[Magisk] pndwal:
Good Question...

Not me... PW
[Magisk] meric57:
Hello, some emulator like bluestasks or nox these possible there are explanations on the web.

If you're talking about the other android emulator I think it must be possible, as it must run on Android so I think it's possible.

nox player there is root option in parameter

https://xdaforums.com/t/script-root...win-macos-win-google-play-store-apis.4218123/
[Magisk] V0latyle:
If I could figure out where the Ramdisk image is, I could patch it.

Interesting to note is that it includes debug root - meaning you can su in shell...but Magisk doesn't detect root. SELinux probably?
[Magisk] HippoMan:
Hmm ... I wonder whether there is some linux handheld device onto which such an Android emulator could be installed.
[Magisk] YLNdroid:
Lloyds Bank mobile app continues to detect root.

https://play.google.com/store/apps/details?id=com.grppl.android.shell.CMBlloydsTSB73&hl=en_GB&gl=US

Device and Model Number: Motorola G7 Power XT1955-4 (ocean)

Android running version: 10 - stock firmware

Procedure implemented:

Zygisk is enabled.

DenyList is enforced.

Lloyds Bank app was added to the DenyList.

Installed Universal SafetyNet Fix v2.4.0-Mod_1.1 modded by Displax, rebooted device; verified said app's presence in the DenyList.

Play Integrity API Checker app yields pass for Device Integrity and Basic Integrity.

Disabled Developer options.

Hid the Magisk app and renamed it using the in-built feature.

Froze the renamed Magisk app using the Ice Box app.

Lloyds Bank app was force stopped, cache and data were cleared; device was rebooted.

Attempt to authenticate into the said banking app, yielded the error depicted by the image below.
[Magisk] manlikesenku:
UK banking apps also stopped working for me.

I managed to get the chase banking app working again through this device id changer:

Device ID Changer - Apps on Google Play

Get, share and change the android device id for all Android version.

play.google.com

However my metro app doesn't show on the id changer list so I can't use that on it.

Any ideas?
[Magisk] pndwal:
I can't find list, at least on free version... Seems to change device ID globally... Does full app work differently?... Target only specific apps?... PW
[Magisk] uradryct:
Octopath traveler find root error 00000034 on Alioth device running Elixir ROM.

I tried everything offered on internet and nothing worked.

It seems to be a problem of a few...

Add it to the deny list works for almost everybody but not all of us
[Magisk] pndwal:
You should try with proper root hiding (denylist only hides by reverting / denying Magisk modifications in processes listed; it doesn't hide Zygisk, isolated process leaks, initrc changes or spoof sensitive props although USNF does fix props)... So install Shamiko and disable denylist enforcement...

If still detects, try LSPosed W/ Hide My Applist module adding already obfuscated Magisk stub app and all other root related apps and XPosed modules to a template set for use by your bank app...

No guarantees but... 🤠 PW
[Magisk] pndwal:
See post above...

Apart from root and applist, some apps detect TWRP folder, OEM unlock setting, USB debugging enabled etc... PW
[Magisk] uradryct:
Hi pndwal and thanks for this fast answer.

I tried shamiko already and hide my applist.

If I delete magisk related files from system/bin will it destroy magisk?
[Magisk] pndwal:
Probably... Why do that?...

Magisk used to install to /sbin, but with major changes in A11+ it is installed in other locations...

Type
su
magisk --path

in terminal emulator to find Magisk tmpfs mount path used...

Edit:

I'm actually not sure what should be installed in /system or why... (It seems Magisk should be installed within /dev if /sbin doesn't exist...)

What do you see in /system/bin other than Magisk module overlays?

Anyway, in case you're wondering, non-root apps won't have access to these locations...

🤠 PW
[Magisk] manlikesenku:
you need to open the drop down box and choose the app: com.etc....

Then hit random ID and restart.

I done this for the chase app and it started working but some apps are hidden in the drop down, including metro bank.
[Magisk] pndwal:
Ah yes... Missed that the yellow mark is a dropdown arrow...

I have chase app installed but can't even find that in list!...

Anyway, with my setup:

... Re. 'Metro' bank app, there's a plethora of them in Play store... Please say which one so I can check if I can pass... 👍 PW
[Magisk] topperdoggle:
It's this one: https://play.google.com/store/apps/details?id=uk.co.metrobankonline.mobile.android.production
[Magisk] uradryct:
I retried, again, the shamiko module and this time worked perfectly with Octopath Traveler
[Magisk] pndwal:
That one won't start w/ my setup... PW
[Magisk] topperdoggle:
:( So annoying. Starting to wish I'd never rooted my phone, but I "needed" an adblocker to be able to browse the web with some kind of sanity.
[Magisk] zgfg:
Working fine for me with Magisk Delta (I don't have acc to login)
[Magisk] topperdoggle:
I'm not very connected to the community. I read about Magisk Delta but it's still not clear to me - is this generally regarded as a better Magisk? Why would the Metro Bank app work with Delta but not original?
[Magisk] zgfg:
Because of a different mechanisms (MagiskHide instead of DenyList). And because the developer every couple of days updates the Delta when he improves something in Zygisk or so
[Magisk] topperdoggle:
Ah, so Delta is truer in character to the original Magisk? Can I install Delta on top of original? Is there any disadvantage to Delta?
[Magisk] zgfg:
Probably yes - it's been long ago when I switched:

- uninstall or disable Shamiko, you will not need

- make sure that DenyList is not enforced

You could (but it's not really necessary - just in case and for future):

- disable Zygisk

- purge your DenyList

- disable other modules

Then do:

- unhide/restore Magisk app if you previously did Hide Magisk app

- uninstall Magisk app (it doesn't mean to uninstall Magisk)

Now, flash Magisk Delta if you have proper TWRP (eg, if you previously installed official Magisk through TWRP) or:

- install Magisk Delta app

- then you can probably Install Magisk Delta through Delta app by Direct install (although patching and flashing the clean boot.img would be better - just in case)

Reboot, open Magisk Delta app and reboot if it asks

Then again open Delta app, go to Settings:

- make sure that Core only mode and SU list are not enabled, better also that new Zygisk loader is not enabled

- enable MagiskHide and configure its list, enable Zygisk and reboot (just in case, you could do that in two steps with rebooting in between)

Then enable your other modules (if you previously disabled them) but without Shamiko

PS: I use Delta Canary
[Magisk] huskydg:
Ptrace MagiskHide ported as Magisk module which allows user to hide without enabling Zygisk on Official Magisk v24.0+

GitHub - HuskyDG/MagiskHide: Portable MagiskHide

Portable MagiskHide. Contribute to HuskyDG/MagiskHide development by creating an account on GitHub.

github.com
[Magisk] huskydg:
Zygisk should get RIP of LD_PRELOAD
[Magisk] huskydg:
Heard "frog sitting at the bottom of the well" story?
[Magisk] huskydg:
Yes, it is unofficial "open source" magisk (not closed source like other) and a bit bleeding than official :)
[Magisk] zgfg:
I installed (MagiskHide, v1.1, release) to my second (older Xiaomi, official latest Canary, A11 but 6 GB RAM with 2 4 GB free and 18 GB Internal space free - hence not so bad)

I have disabled Zygisk, removed Shamiko, USNF and LSPosed

Tried to use my phone for over an hour (rebooted couple of times, trying to change the other things to help) but my phone was practically unusable:

- initializing MIUI after reboot and loading my widgets etc was taking me almost 5 minutes

- after that, upon clicking to an app icon (Magisk, Chrome, MiXPlorer, PI API Checker, whatever) I had to wait half a minute or so for the app to load and open

- clicking to something (to open Settings or Modules in Magisk, to open a Web page in Chrome or to scroll down in the opened Web page, to change a folder in MiXPlorer, anything) was also so slow that many times I was not sure have I clicked to something or not, have I scrolled or not, etc

- unlocking the screen by finger was slow that I was not sure did I touch properly, are my fingers wet or what

Eventually I disabled the MagiskHide module, rebooted and my phone became normally responsive that I was now able again to browse and download the Zygisk modules that I previously removed , to open Magisk app to enable Zygisk and manage and reinstall my Zygisk modules, to open XDA app and to write this post - to use the phone normally as usual
[Magisk] huskydg:
Run this command (use debug variant):

export MAGISKTMP="$(magisk --path)"

timeout 50 strace ./magiskhide 2>/sdcard/hide.txt

Open random apps and send me result
[Magisk] zgfg:
Ok, thx, will do this afternoon and send you by PM or TG
[Magisk] huskydg:
Sorry, this command is more correct (with -f to trace all fork):

export MAGISKTMP="$(magisk --path)"

timeout 50 strace -f ./magiskhide 2>/sdcard/hide.txt
[Magisk] pndwal:
Do you know the price of fish?...and what does that have to do with it?...

Are you just wanting to call me short-sighted and narrow-minded???... Why beat around the bush... Say what you mean man... You can't stop stirring the pot for some reason...

And please make clear which Magisk is closed source...

I guess if "original Magisk" is closed source, core AOSP is closed source!... And IOS core must be open!... 🙄 PW
[Magisk] zgfg:
Sent you the trace via XDA Private msg, thanks
[Magisk] mGforCe:
Hello All

Is there any way to find out how an app is detecting root? And can we patch that?

Issue at hand is using Intune + Outlook on rooted Redmi 10S running MIUI13 A12 build with Developer mode off, default stock recovery, no TWRP folder

I have tried various Magisk combinations as below but for some reasons Outlook always detected root (by showing Device Health with Red Exclamation)

Magisk 25.2 + Denylist + Shamiko + USNF Mod + Zygisk Lsposed + HMA + XprivacyLua

Magisk Delta Canary + Magiskhide + USNF Mod + Zygisk Lsposed + HMA+ XprivacyLua

Then I removed Xposed & all Xposed modules (apks) completely and Outlook started working.

So Outlook was detecting either LSposed (even with HMA) or Xprivacy. Hence wanted to know if there is a way to find how & what is Outlook detecting.

Also any way to hide XprivacyLua from detection over & above HMA.
[Magisk] zgfg:
Try Delta but without XPrivacy - and unfortunately, XPrivacy even when uninstalled, leaves some stuff that is detectable and you have to remove it manually (go to their GitHub site, I think it was described there)

Maybe you'll need some additional modules like App Data Isolation, Reset Sensitive props (that's not MHPC) and maybe even Hide My Apps

I don't have Intune but I did have problems with MS Outlook and Teams and with the setup as above, I was able to stop them complaining.

I even managed to make it work for me with another device mngmt solution (but I didn't play with Intune)

Make sure that you fully pass with TB-Checker (for the beginning) - except for the integrated PI API Strong Integrity.

Eg, it must not detect anything about XPrivacy (remove it properly) and about LSPosed/XPosed (hide it properly)

Then, there are also some tough banking apps - for two of them people did ask here or in the other Magisk thread this week and with my Delta setup I was able to make them work (on the other side, they detect official Magisk)