yashsingh1/xdaforums huggingface dataset:
[Magisk] revengineer:
After trying for the last two hours, I decided that I need help installing HMA. I installed the 3.04 beta app but I get error "Module Not Activated". I thought it was related to LSPosed not being installed, so I tried installing LSPosed 1.8.4 but the error remains. It looks like I somehow need to flash Zygisk-HideMyApplist.zip but this file is nowhere to be found. Help appreciated.

EDIT: Got a step further: HMA now shows "Module Activate". However, when I try to hide the magisk app, the detection test still recognized the app. I am clearly too dense to use this but if there is any help, I will take it.
[Magisk] ipdev:
Late to the BONVoY party.. 😛

I borked my Pixel 6 yesterday and had to factory reset.

Still in the process of setting it up (off and on while doing other things).

Pixel 6 (a12L)

One of these days I will upgrade it to a13. 🙃​

Magisk Debug (snapshot builds).

MHPC

USNF (test build w/o the PI fix).

Shamiko

LSPosed (Zygisk).

BONVoY:

Adding it to HMA did nothing.

Blacklist includes com.topjohnwu.magisk and com.tsng.hidemyapplist​

Adding to the DenyList did nothing to start with.

Enabled or Disabled

Renaming the Magisk app was the key for me.

With BONVoY in the denylist (disabled) and Shamiko taking over..

Cheers. :cowboy:

PS.

Remember to Force stop and clear storage and cache for any app that you are testing before/after every change. 🙃

- If an app detects root or something it does not like, it might cache the result. So even if you fix what it does not like, it will still return the cached error.
[Magisk] pndwal:
I can help later, but I didn't need HMA with my setup so it may only be a few apps like "Official TWRP App" (confirmed), perhaps a Titanium Backup etc that are detected... May be simpler just to uninstall any suspect apps to see if it helps; don't forget to clear Bonvoy data before each test...

Which apps do you intend to hide (or uninstall) anyway? PW
[Magisk] badabing2003:
You had your chance when you had to do factory reset.

Any reasons why you're holding off?
[Magisk] revengineer:
With renaming the Magisk app, do you mean "Hide the Magisk app" is Magisk settings? This seesm to assign a random file name.
[Magisk] pndwal:
Found a few HMA tips I posted recently...

Hide my Applist LSP module is a convenient way to hide Magisk App better and hide all root apps / managers / utilities/ LSPosed modules etc for some banks... Also you'll need latest beta (3.x.x) release for A13... (HMA now also hides /data/data for A11+)

See:

- https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87608273

- https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87623757

Also, ensure you use LSPosed 'parasitic' Manager and hide HMA itself plus any other LSP modules from Bonvoy etc... 😉 PW
[Magisk] pndwal:
I believe you said you've taken this option?... (essential).

... It does more than that; uninstalls full Magisk App completely and installs (tiny) stup app. The stub is then populated with Magisk binary (it's all now in app data) and you randomly name it also...

Full App = large app, very small app data (only for initial warning?)

Obfuscated stub = tiny app, large app data and special changes to the way Magisk (core/mask) and App communicate... PW
[Magisk] ipdev:
Staying with a12L for testing and to keep the bootloader anti-rollback out of play for now.

I have a 5a that is updated to a13 for testing so, no hurry to update my 6 to a13. 🙃

Cheers. :cowboy:
[Magisk] ipdev:
Yes.

Renaming the Magisk app with a different name.

Note:

When I added BONVoY to the denylist, it only included 4 of of the 5 processes.

I just left it that way.

Cheers. :cowboy:
[Magisk] revengineer:
Thank you! I am getting the hint of how HMA works but it has so far not resolved the issue.

Yes I have hidden the magisk app. i was just verifying with @ipdev that we are taking about the same thing.

So yes, I have done this.

Yup I tried this yesterday already. And I confirm that I am clearing data and cache of Bonvoy app between tries.

Ok, its enough for tonight. I wonder if it's time to show Marriott that the simple solution is to install the Hilton app. :)
[Magisk] revengineer:
Bingo!!! HMA did the trick after hiding anything that is remotely related to root apps. Not sure what the culprit ultimately was, but issue is solved! I really appreciated the help and handholding @pndwal !
[Magisk] pndwal:
Glad you didn't need to defect to Hilton!... And we'll done...

If you set up HMA templates you'll be able to apply these to other apps easily...

Nb if you further hide already hidden Magisk App (needed for some bank apps like S-Push-TAN) you'll need to add Magisk again after reinstalling or un-hiding/re-hiding even if same custom name is chosen...

If you do get a chance to test and narrow down which app(s) are actually detected, I'd be interested to know, and I'm sure other BONVoY users will find this discussion/solution too...👍 PW
[Magisk] c3k:
Witch magisk update you was installing?

I have a S21 and I remember the only option to install magisk is in the ramdisk and I used direct install update a couple of times without problems. Don't know if S21FE is different, seems strange...
[Magisk] pndwal:
Hope you sorted it...

Were you direct installing to update from 24xxx or under to 25000+ by any chance?...

Nb. Major refactoring of magiskinit injection in 25+ broke Direct Install (when updating previously patched boot images) in a number of 2SI boot type devices as images w/ patched fstab (no longer done) are now incompatible with magiskboot patching...

Instructions for patching / flashing Magisk from unpatched images still worked fine for those affected... Sammy users w/ A10+ and this issue should download ROM corresponding exactly with current version (especially if you took OTAs since first Magisk installation), patch the AP binary and Odin flash all 4 binaries per 'Samsung (System-as-root)' section in Installation Instruction page under 'Upgrading the OS' (even though you're not 😉 ): Flash magisk_patched.tar as AP, together with BL, CP, and HOME_CSC...

I posted alot about this refactoring (as well as major changes w/ sepolicy rules etc) here around June 23...

🙃 PW
[Magisk] 73sydney:
Like i dont want to start anything with you, because you live up a bell tower, and refuse to identify as an Aussie, but i do wish they would change the doc to stop people patching the entire AP file from Samsung firmware, because it takes an insane amount of time to patch (for my model) a 7.3Gb file, when if you:

- Download the firmware on PC

- Using 7-Zip extract the 4 files (AP,BL,CP, CSC (or CSC_HOME if you want to retain data))

- Open the AP file with 7-Zip and extract the boot.img.lz4 (and if it exists) the vbmeta.img.lz4 files

- Select the boot.img.lz4 (and if it exists) the vbmeta.img.lz4 files where you extracted them

- Right click and from the context menu select 7-Zip, Add To Archive, then change the Archive Format to tar and compress

- Move the tar file to device

- Patch the tar with magisk manager

Its much easier and even with these extra steps its MUCH quicker to patch

7.3Gb vs 20Mb file to patch....
[Magisk] ayambakargoreng:
-edited- found out the solution
[Magisk] zgfg:
adb shell pm list packages -f | grep magisk

will show a path where the Magisk app (if not hidden, ie package name not scrambled) com.topjohnwu.magisk is installed
[Magisk] rodken:
It's always a must [or at least helps] to have a backup phone that one can use as a test device and/or secondary phone.
[Magisk] bnsmb:
Hi

hmm, as far as I understand the config on the ramdisk is copied from the boot partition while booting the phone and the file in the boot partition is created while installing Magisk into the image .

>>For details, there was a quite a bit of discussion about it in earlier posts.

Which date (round about)?

regards

Bernd
[Magisk] pndwal:
... at least I have no bats in my belfry...

Good point...

I'm not a Sammy user and just repeating John's confirmed working solutions...

Guess you've found this is ok for updating... Not sure if it would work for initial installation which apparently requires a full data wipe... Also, do you flash with other binaries?... What about this advice:

Assuming all this is all ok, you may still be doing more than necessary... Is patching vbmeta still needed on Sammy devices in general?... I ask because while Magisk did this in 24.x and earlier in 2SI devices to facilitate fstab patching, the same refactoring I mentioned above means that vbmeta partitions are no longer patched (ie. AVB remains intact) in these devices w/ 25.0+...

AFAIK, vbmeta patching was never needed for legacy ramdisk or legacy SAR devices either, so I believe you'll only generally need to patch this for use with certain custom kernels these days... I know this is an option using a fastboot command for most devices but since it's apparently no longer done by default I'm not sure how you'd toggle vbmeta patching for Sammy .tar binaries anyway...

------

And now for something completely different...

Well wadoyaknow, a bingo jackpot!...

Wouldn't normally press the point, but it shows tools like Momo (which shows much insight on the part of experienced Devs also) can be very useful if used in combination with some deductive reasoning... I was fairly confident app detection was at play simply by eliminating differing Momo detections...

Momo has received quite a bashing here in recent times, and I don't think sparing users from some kind of 'self abuse' is a good enough excuse...

Nb. 2 of the 4 main Magisk Devs (see Magisk App main page) are responsible for Momo...

🙂 PW
[Magisk] revengineer:
Ok, I figured it out. It was the BusyBox Pro app from Stericson available in the play store that resulted in the BonVoy app detecting root access and preventing the app from launching. I also have Root Explorer, Titanium Backup, and Adaway installed, and removing these from HMA caused no problems. So put BusyBox (Pro) in addition to TWRP (reported elsewhere) to the list of apps that trigger root detection by BonVoy app.
[Magisk] revengineer:
So on my system Momo still reports "Found Zygisk". That begs the question, how do you hide this? During this adventure, I read that an increasing number of apps detect zygisk and it would be nice to be able to hide this as well. To be clear, it's not causing a problem right now with any of my apps.
[Magisk] pndwal:
Great to know!... Thanks...

Preferred busybox if still needed for use w/ Magisk is Magisk module BusyBox NDK:

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

I have it... No issues... PW
[Magisk] pndwal:
Mine too... Most have that... So even if your original result had shown that I would still have known it wasn't the issue in your case and concluded some app detection was the culprit...

Apparently some apps are doing so and ATM it's a choice between Zygisk and those apps... Canyie and LSP devs may well devise better Zygisk hiding... it's certainly not yet on par with Riru's integrated Riru-hide...

As I said I only use Momo for deductive diagnosis of detections however... A fix for recent Zygisk detections will be interesting but there's no chance I'll discover it so I'll just watch this space and not worry about it too much...

Happy days! 😋 PW
[Magisk] pndwal:
...Been in official instructions as long as I've been aware of them... 😜

Well it was technically needed (for all devices running A10+ aside from those launched with A9, ie all 2SI boot type devices) untill Magisk 25.0... But not anymore AFAIK...

That bad? 🙁... I already said it's nothing sudden... I think mine was the first mention of it here...

You might prefer to put screws in with a hammer, but if I've discovered the screwdriver and encourage a user to extract a screw with a that, I don't see why I should be criticised (or worse)!... And I'm not taking about your (mildly amusing) complaints in particular...

The Devs working on Momo, momohider, Shamiko, LSP, Magisk, Shizuku, Sui, Storage Isolation etc etc are clearly some of the best... Their diagnostic tools might not be for sooks but I can't see why these should be avoided (or be derided) any more than Magisk, LSP or root apps/utilities most users here are probably using... These are the same Devs behind Riru hooking and specialist root trace hiding modules like unshare, testing isolated process hiding w/ Magisk Lite etc as well as testing apps like YASNAC that most here will have appreciated... The same Devs are clearly among those John called "passionate about hiding" and encouraged "start doing their job", not to mention providing fixes for many Sammy, MediaTek, other incompatibilities in Magisk...

I've put up with the fairly constant inappropriate inuendo aimed particularly at users of Momo and Shamiko here but I don't get it, nor do I see the need...

Use another tool if you don't like it!... Maybe the claw end of a hammer; whatever gets the job done for you!... As for me I'm happy to use tools from these Devs, but to be honest I haven't really been promoting Momo anyway... Just a little deductive reasoning...

😬 PW

Off to ring a bell... with a big hammer... 🔨
[Magisk] 73sydney:
This sook stands corrected

Now, back up into your tower...
[Magisk] slapshot2286:
Hello all, having issues with patching with Magisk. I'm on a Pixel 7 (unlocked BL) running android 13. After an OTA update (I forgot to turn it off… new phone), I tried re-patching boot, but now am unable to obtain root. I've verified the version, have tried both the current and beta versions of Magisk, but cannot get root. I've also tried flashing both slots, as well.

Is there something in the Nov security patch, or in Android 13 in general, that may have changed the process and could be blocking it? Thanks…
[Magisk] Homeboy76:
Are you patching the init_boot.img that you extracted from the November 2022 factory image with magisk?

Are you flashing the magisk_patched....img with this command: fastboot flash init_boot magisk_patched...img?
[Magisk] slapshot2286:
deleted.
[Magisk] slapshot2286:
I am flashing boot.img, not init_boot.img. I've never had to flash init_boot.img before - would I be flashing that on its own or in addition to boot?
[Magisk] slapshot2286:
init_boot with boot did the trick. Thank you sir!
[Magisk] shoey63:
Things have changed for Pixel 7.

I suggest you go to their forums and do a bit of reading to get up to date.

Edit. Good to see problem solved.
[Magisk] 73sydney:
i had to do a double check having used a Pixel 2XL in the past and using boot.img, but thats correct

some light reading for you:

https://xdaforums.com/t/november-20...r-root-pixel-7-pro-cheetah-safetynet.4502805/

and a shout out to @Homeboy76 himself

https://xdaforums.com/t/guide-root-...nlock-bootloader-pass-safetynet-more.4505353/
[Magisk] zgfg:
It was discussed here and elsewhere (I don't have Pixel but I'm absolutely sure that I saw and read the posts about in several threads

init_boot.img for the new A13

Look through the older posts here and in the other related threads, specially for the Pixel device and A13
[Magisk] Homeboy76:
The Pixel 7/Pixel 7 Pro use the init_boot.img to root. [Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More

See OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with

Magisk

and Pass SafetyNet.

This Guide also works for the Pixel 7, as long as you download the Pixel 7 files.
[Magisk] slapshot2286:
Yeah I've seen it for other devices but I literally patched only boot.img for the last 2 updates so it's weird that it showed up all of a sudden.

Nonetheless, I get it now and appreciate everyone's help and the links to Homeboy's threads!
[Magisk] 10Maximus10:
hello i have a problem safetynet is passing even momo only detects unlocked bootloader nothing else but play integrity api MEETS_DEVICE_INTEGRITY and MEETS_BASIC_INTEGRITY don't pass and i can't use netflix and other apps. I recently flashed stock rom again because i broke it but before it worked now it doesn't with everything the same.
[Magisk] Homeboy76:
Just Curious

Which command did you use to flash the patched_magisk...img with?

fastboot flash init_boot magisk_patched...img

or

fastboot boot init_boot magisk_patched...img

I think they both will work. :)
[Magisk] 73sydney:
i think traditionally fastboot boot is good for one boot, fastboot flash is permanent....

its only seared into my brain because on 2XL before i departed we ended up not being able to fastboot flash TWRP, but just fastboot boot to it when needed...
[Magisk] ipdev:
Personally, unless booting an image is not an option..

I always test boot the Magisk patched image using fastboot boot NameOfFile.img instead of flashing it.

If it boots, Magisk will be active and I then use the Direct install option to make it permanent.

If it does not boot, then no harm since the stock boot image is still installed. 🙃​

Cheers. :cowboy:
[Magisk] shoey63:
Some have said it's a waste of time to test by booting first, then direct installing because you can just flash the stock image back if it doesn't work.

This maybe true, but directly flashing the patched image does NOT give Magisk the chance to back up the stock boot image, whereas booting then installing does.

This makes it easier to take an OTA update on devices that require everything to be pure stock before proceeding by using Magisk's restore images function.
[Magisk] slapshot2286:
I used flash (option 1). I did that for init_boot and boot, though I'm not sure if both were necessary.
[Magisk] soadfan:
Hey Guys,

can someone help me root my new Xiaomi POCO C40?

Short version: it's in a boot loop.

I have Xiaomi 11T PRO also, which I rooted almost the same way, successfully (the difference is I went full YOLO and flashed both boot partitions on it).

Long version:

Unlocked the bootloader (fastboot)

Downloaded the ROM from HERE and used its boot.img (the versions are the same, see attached).

Patched the boot.img

Flashed the patched boot.img to slot_a (currently active is b)

Set boot_a as active and rebooted.

(I'm glad I didn't go YOLO this time and flashed only one boot partition)

Then I came across the installation instructions on Magisk's GitHub:

Magisk says it has Ramdisk I have the boot.img and:

Now I'm not sure about the last part, because I didn't do it when I was flashing the 11T PRO.

Do I need to patch that image file in the Magisk app and flash it too? After that do I need to set it active with a command (if such a command exists) or it follows the active boot partition (if boot_a is active, use vbmeta_a)?
[Magisk] zgfg:
For Xiaomi phones it is enough to patch and flash the boot.img (disregarding ramdisk, vbmeta, etc)

I only don't understand why do you flash to another slot and switch the slot

(I have Xiaomi 11 Lite 5G NE, also dual slots, when I rooted stock A11 and A12 and now Xiaomi.eu A12 I never switch the active slot)

Why didn't you simply:

-patch the boot.img (without marking Recovery option)

- keep the same slot as it was

- fastboot flash boot <patched boot.img>

In your shoes, I would:

-switch back to the original slot the phone was before you switched;

-flash back the original boot.img (and recovery.img if you messed)

To come back to the starting point and the bootable phone

Then to root as above, without switching the slots

Btw, before permanently flashing the Magisk, you can one-time boot to test is it ok by:

fastboot boot <patched boot.img>

PS: Is your MIUI 13.0.6 still A12 or maybe a brand new A13 (in that case I don't know about its slots, partitions and rooting)?
[Magisk] pndwal:
Good point, and this is needed for now in P7 as Install to Inactivate slot method (for preserving Magisk thru OTA) is apparently broken for P7 (doesn't handle init_boot properly?)... But this fix in March seems good to me:

https://github.com/topjohnwu/Magisk/blob/master/scripts/util_functions.sh#L429

... I'm now wondering (if this way of initial setup is confirmed to properly back up init_boot) if it could be all that's needed for Preserve Magisk thru OTA w/ A/B Install to Inactive Slot method to work... Not sure anyone tried this!?...

Of course fastboot flash can be used, but nice to have Uninstall Magisk, Restore Images option, and OTA w/ Magisk preserved is even better...

... Not sure how this would have worked for P7 as 'generic ramdisk' is now moved out of boot.img...

FWIW, @osm0sis is now analysing the evolving complexity of boot image fragmentation and their various ramdisks all still under the v4 header umbrella:

www.twitter.com/osm0sis/status/1591052723818201089

Guess this will most likely lead to fixes for Preserve Magisk thru OTA w/ A/B Install to Inactive Slot method if still needed...

To qualify this, there have been a number of fixes allowing Magisk patching A13 boot.img's affected by GKI changes etc...

AFAIK, patching vendor_boot w/ magiskinit never worked, so it's been boot.img up until generic ramdisk was moved to init_boot, meaning init_boot patching is for A13 Launch Version devices only... So only Pixel 7 series for now apparently...

🤠 PW
[Magisk] pndwal:
Good advice above... No need for patching vbmeta or other generally these days (unless using custom kernel?) on stock MIUI... You can keep AVB intact...

Magisk should be installed to current slot unless using Preserve Magisk thru OTA w/ A/B Install to Inactive Slot method at OTA time... This is generally working again for Pixel devices; not sure about Xiaomi... If you want to try it w/ next OTA, guide / precautionary notes are here:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md#devices-with-ab-partitions

🤠 PW
[Magisk] pndwal:
So you need to fix these verdicts...

Have you installed @Displax's modded/forked USNF module w/ fix for deviceIntegrity?...

🙂 PW
[Magisk] soadfan:
I'm to the original slot (b) because after a few boot loops it switched back to it by itself.

About phone says it's Android 11 RD2A

I didn't flash recovery hence I don't want a custom recovery, I need just root.

It's working on Xiaomi 11T PRO, this is how I'm installing OTA updates.

I've tried to flash stock boot.img from the same archive to slot_a but it still won't boot.

Now I'm afraid to do anything with the current slot because if something fails it won't boot at all.

P.S.
[Magisk] pndwal:
... You're getting confused about recovery mode... But you won't have the option mentioned anyway since Ramdisk = Yes... That's only for 2018/2019 era A only legacy SAR devices anyway... Involves patching Magisk to ramdisk in recovery, ie 'Recovery Mode' as opposed to 'Boot Mode'... Custom recovery is something quite different, and I don't think it was suggested at all...

👍

I wouldn't worry you too much; if fastboot flash magisk-patched boot.img works you can always just fastboot flash unpatched boot.img again to restore if it bootloops anyway... I'd leave inactive slot for next OTA as intended...

If you really want to restore a working system there, why not just dirty flash a complete ROM to that slot?... Even better clean flash if there's no unique data to be lost there ... Sorry I don't have A/B and don't know the procedure... PW
[Magisk] shoey63:
Actually, install to inactive slot method after OTA has been borked for months on Pixel 6/6 Pro with no fix in sight. Refer to This issue

So my current method for Pixel 6 is : -

- Restore stock boot with Uninstall Magisk/Restore Images function.

- Take OTA update.

- While system is "optimising" after the update but before rebooting, dd the the new boot image from the inactive slot while still rooted.

- Patch it with Magisk, upload to Telegram and reboot phone when prompted.

- Get off couch, turn PC on, download the patched image, fastboot boot it followed by direct install, reboot and get back on couch😋

Rinse and repeat each month. Minimal effort, and only possible if you have Magisk back up the stock boot image by boot/direct install method.