yashsingh1/xdaforums huggingface dataset:
[Magisk] zzz2002:
i am not asking you to play Google.

I am trying to find out if this is normal for a device which does NOT have Magisk installed.

brief history -

added lsposed (sp) and Shamiko to device, install acted suspiciously, advised on this forum to wipe and try again. started to have problems.

wiped device using TWRP,

flashed using Odin (had to build windows system) - rom from Sammobile, installed TWRP,

flashed lineage 12 (ivan meler build),

added Rootbeer & YASNAC, both act as though Magisk was installed.
[Magisk] Spartacus500:
This is just information if there is a TWRP folder, I checked myself on 9.0 Pie NFE, just rename the TWRP folder to ".TWRP" and the information in the MOMO application about the detection of Magisk or TWRP will disappear 👍
[Magisk] zzz2002:
Thanks for the idea.

Unfortunately has no effect.

oops, I got that wrong.
[Magisk] kings121:
Can magisk be run from adoptable storage without any errors?
[Magisk] martyfender:
From what I recall, no.
[Magisk] zgfg:
Please carefully read and take literally what Momo detects

Obviously, if it detects your custom ROM, TWRP folder, that your /data is not encrypted - how could that depend if Magisk is installed or not

Momo inspects your phone (Bootloader, ROM, files, etc) not only if Magisk is installed or not

It's not the fault of Magisk v24 - and Magisk can not hide, and it's not its purpose, if you run an ancient ROM that does not encrypt /data (Momo considers that unsafe), if your ROM maybe runs SELinux in Permissive mode, if you have TWRP installed (and you didn't delete/rename its folder to hide from Momo), etc
[Magisk] Spartacus500:
Is it possible to hide "SELinux rules are modified" which detects MOMO on Samsung🤔 Anyone know which file, path on the system is responsible for this 🤔 I will immediately write that I have enforcing in all lines in getprop. And the [ro.build.selinux] [1] line is missing from my Rom 😐
[Magisk] zgfg:
getenforce ?
[Magisk] Spartacus500:
Yes 🤔 SELinux modified i block some applications (checked), and these applications show that root detected 🤕
[Magisk] zzz2002:
Sorry I was not trying to get at anybody.

Thank you, yes - its a custom ROM, with TWRP and I chose not to encrypt as nothing confidential is stored on the device.

What I do have is some apps that behave as though Magisk (rel <= 23) is installed.

The reason I am questioning things is that when I tried to in stall 24 + I got asked a lot of weird questions (sorry i don't remember them). When I asked about these here, I was advised to take evasive action. I am trying to determine is I have taken enough action and if not what to do next?
[Magisk] zgfg:
If you return to Magisk v23 and you run Momo it will report the same -just that in the good old days you didn't use Momo (although, it was developed few months before Magisk Canary v24 and specially Stable v24 was delivered)

That's about Momo

About 'banking' apps - maybe you didn't hide things properly but apps also get updated and more smart in detections

E.g, if a new version of certain banking app now looks whether /data is encrypted or not (hint their devoperrs could have picked up here from our discussions about Momo) then their new version would detect that and complain that you are 'rooted' no matter if you run Magisk v23, v24 or uninstall Magisk

Unfortunately, it's also true that some of the earlier detectors were developed as open source, making it easier for developers of 'banking' apps to incorporate more advanced detection methods they would otherwise not know about

And then there are still people here who complain why Momo is not an open source project

Neither MagiskHide/DenyList, Shamiko, hiding Magisk, etc, could not hide/protect our discussion here (and on the other forums, TG channels, etc) from curious developers who could read and use that knowledge tomorrow - they don't need to develop banking apps themselves, they can sell their detectors as SDK (for good money) to banks /banking apps developers

It's never ending mice and cat game
[Magisk] trentini:
I root my S10+ using magisk v24.1 and after installed TWRP . Everything went fine. Root granted, installed magisk props. For some reason that I dont know how, root was disabled and phone was never rebooted or turned off. It just happened after 2 days on....any clues ? Android 11, stock rom.
[Magisk] Eng.Raman:
InitRcHider and Shamiko both use exactly w/ 100% the same code to hide init.rc traces modified by magisk ( imported/copied from service.sh of riru-momohider 0.0.7/0.0.8 module by canyie ).
[Magisk] zgfg:
Are you sure you didn't receive OTA - for A/B devices (I don't know if your Sammy is A/B), it could be applied pretty seamlessly (inactive slot gets updated in the background, that slot was not patched by Magisk to interfere with OTA, the phone finally shortly reboots - maybe some [default] setting allows all that without asking the user)
[Magisk] Danny94:
Is there any disadvantage patching boot.img instead of recovery.img ? (Like less hidden...)

Because i got into bootloop and while fixing my issue i had to reflash my patched recovery, but this time my recovery gets replaced again (no clue how i was able to make it work last time ;)), so i propably gona patch boot.img this time.
[Magisk] HippoMan:
I like my ROM which doesn't force me to encrypt /data (and I don't do so), and I like TWRP for nandroid backup and restore. I also don't mind permissive Selinux mode.

So much for Momo and anything which depends upon it (sigh).

And my device is rooted via Magisk and passes SafetyNet.

I'm running Magisk 23.0 on stock Android 10. I hope I never have to upgrade to Android 11 or beyond. I see no advantages in any of these later Android versions ... certainly nothing which would make all this current complexity with using Magisk and related utilities under these OS's to be worthwhile.

Perhaps some day this complexity will be ameliorated, and if so, *maybe* I'll then consider upgrading the OS and Magisk.
[Magisk] zgfg:
Everybody on Xiaomi devices patches boot.img - why don't you try

It will not affect you recovery (you have custom rom hence you are not concerned about stock recovery needed for ota but you probably want to have twrp in recovery

Brw, if you rename magisk apk to zip (not even needed for twrp 3.6.0) and flash through twrp, it would also install magisk to boot
[Magisk] zgfg:
All fine - but then you are not somebody who just recently got obsessed with momo (so many of them, I was also the one two months ago) and then starts asking why momo detects this, that, etc; how to 'fix' that, why Magisk does not 'fix' that, why it was not considered as a problem with Magisk v23, etc

You know 'limitations' of your old rom and you probably never even bothered to test with momo
[Magisk] Lord Sithek:
To clarify - not all of us are "obsessed" with Momo, some just are curious of what is being detected and want to learn more about 😏
[Magisk] daveseris:
I'm hoping someone has had this happen and remedied it or just has an idea what may be wrong. I have successfully regained root after several factory image updates (no wipe) with no problems by using the patched boot.img . The latest factory image applied with no problem, but I cannot get Magisk (Canary 24102) to patch the boot image. I get to the install screen which only has select and patch as an option. I select the boot.img but when Magisk returns to the install screen, "Let's go" is greyed out. The Select and Patch a file radio button is lit. I'm hoping someone has an idea to avoid the dreaded wipe install. Pixel 6 Pro.
[Magisk] Spartacus500:
Unfortunate, I cannot find a solution for the SELinux modification 😔

@pndwal
[Magisk] trentini:
I root my S10+ using magisk v24.1 and after installed TWRP . Everything went fine. Root granted, installed magisk props. For some reason that I dont know how, root was disabled and phone was never rebooted or turned off. It just happened after 2 days on....any clues ? Android 11, stock rom.

Will check again for that as I am not sure. I was not aware that OTA could be instaled without my consent...
[Magisk] zgfg:
And if you click again to Select and patch, nothing will happen?

And you have to go back to the main screen and again into Install to continue

You could reproduce the same if you went for selecting and then you change your mind and go back without selecting the boot.img

If it happens for you when you really did select (the valid boot.img) then you probably have problem with your file explorer

Maybe you have 'stock' explorer and a second one you installed over.

Try changing the file explorer - when you enter Select and patch, go to the top-left menu (on my phone) and change the way/file explorer how you would pick-up the boot img
[Magisk] Danny94:
I have stock global miui pie, but yeah i dont update so it doesnt matter.

Thats how i have installed magisk for ages but according the magisk install page:

"This installation method is deprecated and is maintained with minimum effort. YOU HAVE BEEN WARNED!"

So i followed the new procedure.

Well if it doesnt change anything than i gona patch boot.img ;).
[Magisk] daveseris:
Dragon Kumera sent me his Magisk Patched boot.img, I used it and have root back with no problems.
[Magisk] martyfender:
For those who posted this,yes, if you rename the TWRP folder, momo does not detect it. However, if you reboot to TWRP it will create a new TWRP folder that is detected. If you delete that folder, again, it will not be detected in momo.
[Magisk] martyfender:
I have 2 Onn 8 first gen, Android 9 tablets. They appear to have the same hardware, Android version but the newer one has a much newer Android security update. They are on the newest magisk alpha. By adding shamiko, lsposed and enhanced mode for HideMyApplist, I can can completely report no abnormal modifications in momo on the older tablet. The same config on the newer Android tablet always reports bootloader unlocked in momo. everything else in momo is hidden. In Oprek the tablets both report as healthy.

I have seen it reported not to obsess with momo. Does anyone know how to hide the bootloader, to obsess?
[Magisk] HippoMan:
Exactly, and I agree with your putting the word "limitations" in quotes, because in reality, I don't see the characteristics of my ROM to be negative or substandard in any way. And I do see some things discussed here and elsewhere about using Android 11 and above which indeed seem like OS limitations to me.
[Magisk] pndwal:
No - other way round!

Magisk in recovery is very inconvenient as need special key combo & timing to boot with Magisk every time... Also, many updated OSs, Sammy etc, now won't boot to special modes w/o USB PC or headphone connection in addition to key combo...

It's just that for most type III devices there is simply no choice! -

• Can't install Magisk in boot partition.

• Cant boot normally.

• Can't install or update via old Custom Recovery zip flash method (as recovery partition ramdisk has been 'hijacked').

... But due to Xiaomi leaving boot-ramdisk compatibility (inexplicably) in bootloader despite OEM not including ramdisk in boot (cos it's type III), you do generally get the choice! ... John mentions this in his Installation Instructions too...

Neither installation should be 'more or less hidden'.

I think you finally managed to boot initially into System w/ Magisk via recovery instead of directly into unrooted system...

👍 PW
[Magisk] zgfg:
For me, Xiaomi Mi 9T, TWRP 3.6.0_9 official, upon renaming TWRP folder to TWRP.bak, my TWRP does not create new folder but it uses the renamed TWRP.bak folder when doing Backup/Restore

And the same on my Xiaomi 11 Lite 5G NE, with SHRP 3.1 unofficial.

Also happily uses renamed

TWRP.bak folder when doing Backup/Restore

And renaming to TWRP.bak is enough to prevent Momo to detect TWRP

(I don't install that TWRP application as offered by TWRP.

But my renamed TWRP.bak folder does contain the saved .twrps settings and TWRP/SHRP finds them properly)
[Magisk] svendsvin:
I recently updated to 24.1. After I did some snooping around in the /data folder and found 4 similar folders with a boot.img.gz file inside each. Not sure what they are. Maybe some old backups of stock boot.img? Can I safely delete them?

I'm on MIUI 12.5.3 stock rom.
[Magisk] Lughnasadh:
Yes, they are backups of the stock boot image. You should keep the latest one so you can use the uninstall option in Magisk, if needed, as well as "install to inactive slot" option if your device supports that.
[Magisk] LLStarks:
John just instructed the Magisk alpha fork team to rename their project and perhaps even remove translations other than Chinese.
[Magisk] Stillhard:
带面具的愤怒女孩俱乐部 maybe? 🤣

Mod Translation

Angry Girls with Masks Club maybe? 🤣
[Magisk] Philnicolls89:
S10+ is not an A/B device so no OTA's can be installed without your knowledge. Also samsung has security measures in place to automatically replace your modified recovery image with the stock one on certain devices. You need to flash multidisabler through TWRP to prevent this from happening.

That's assuming you gained root by patching the AP file and TWRP file, if you gained root by installing a custom kernel that comes with magisk already then i have no idea!
[Magisk] wugga3:
Why angry??? Lol I'm hoping that translated correctly! Sorry for the off topic....
[Magisk] ipdev:
If you follow the naming of their other projects..

More likely something along these lines. 🙃

たまさくらちゃん

Cheers all. :cowboy:
[Magisk] HippoMan:
Yes, but that's hiragana (Japanese), and we have this ...

> John just instructed the Magisk alpha fork team to rename their project and perhaps even remove translations other than Chinese.

... and would they really name something "Little cherry blossom testicles" ? :)
[Magisk] zgfg:
Time to move on - today switched also my second phone from Alpha 24102 to Canary 24102:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86418925
[Magisk] raulci:
I own a Xiaomi Mi9 with Android 10.

I tried to update from v23 to v24.1 using Magisk Manager update feature, but it didn't work.

Then I read John's doc and found also that twrp instructions and the warning. As you, I've been installing Magisk using twrp for years, so after crossing my fingers, I tried twrp method again and fortunately it worked like a charm.

Just my experience, I didn't understand completely how to install Magisk with current suggested method so lucky me that twrp method still was working for me.
[Magisk] Danny94:
Yeah in the end i have flashed it via twrp method which seem to be pretty equal to the patched boot.img method. Maybe because on newer phones this method does not work its not recommended anymore.
[Magisk] Mighty_Rearranger:
I tried doing the exact same thing, except I did file transfers using ADB from the beginning. Still have the IMEI error. From what I've gathered, something in the latest updates caused Magisk to somehow mess up the IMEI. Users with A325MUBU1AUG1 report no problems with imei disappearing.

I want to help but I have no idea where to start from. Rollback is out of the question since the binary check number has changed, but is there any way to check what changed between updates that could be clashing with Magisk?
[Magisk] Stillhard:
You should see why from JW replied to other's q:
[Magisk] rodken:
Is that an indication that folks on Alpha should prepare to migrate to Canary or will the Alpha team still keep that version updated?
[Magisk] zgfg:
Please take a look to the old General Magisk thread, posts from yesterday

You can also check the publicly available Magisk Alpha TG channel (with Google Translation)

They were asked by TJW to change the name, package name...
[Magisk] GreekPilot:
@zgfg Is it necessary to hide magisk app (also reverted to canary, following you) as momo says normal environment and my apps work fine?
[Magisk] zgfg:
Momo does not look for any app (Magisk app, LSPosed app, etc).

You can scroll down through Momo and read what they explain.

Some banking apps do look for apps (you may need to hide for them), but it has nothing with Momo, neither with SafetyNet

Momo screenshot attached
[Magisk] casouzaj:
In my Sony Xperia XZ2 phone, after Magisk Alpha has been renamed to `Alpha`, modules which work with Zygisk, such as Shamiko and USNF, complain that it is not enabled, although it is. Turning Zygisk off and back on, and rebooting, multiple times, doesn`t change anything. Will try the Canary path for the time being.

EDIT: Magisk Canary is working pretty much like Alpha prior to its latest update.
[Magisk] pndwal:
Latest Alpha? - Others are reporting Zygisk is broken... also, strangely, that magiskhide is back... PW
[Magisk] casouzaj:
Since Magisk Alpha updated itself and appeared as just Alpha in the apps drawer.
[Magisk] Peter the Great:
Edit: Actually my understanding of this was flawed. You need your root key to be signed by the Google hardware attestation root certificate anyways, which they won't do for you unless you ask very nicely /s.

Hello all, this is my first message in this thread I believe. I've been searching through the thread to see if there's been any discussion about this and I don't believe there is. On Windows Subsystem for Android (WSA), I can easily pass Momo using Shamiko and modifying LSPosed's system.prop file to make it only partially activated. Interesingly, Momo only checks if your bootloader is either unlocked or locked, but doesn't check if it's unknown, as is the case with a virtual machine like WSA, so Momo passes when it really shouldn't. The Key Attestation app correctly checks for this. Momo also doesn't check for SafetyNet, as why would it when YASNAC exists.

Regardless of all that, I was researching if there was a way to pass safetynet with an emulator or VM. Obviously, this question has been asked over a million times, with the same answer every time. I'm not here to have the same discussion that's already been had elsewhere. I've been doing some research and have found some succesful emulators for the TEE/TrustZone. One such example is OP-TEE's optee_os (source on GitHub), Another one, Open-TEE, got it working on Android 5.0 to 5.1.1, called opentee-android (source on GitHub). These projects are meant for development purposes however we could make one for our own purposes I assume. I'm asking about this because the future Play Integrity API surely will force hardware-based key attestation, and so something drastic like emulating the TEE might be necessary to pass PI by spoofing the bootloader unlocked status.

Does anyone here have any knowledge or experience with emulating the TEE? Any ideas?
[Magisk] martyfender:
Yes, I get the same result with the latest magisk alpha. Finally a major bug for many of us, but then, after all, it is labeled alpha for a reason. It has had a good track record for me for a long time.
[Magisk] pndwal:
Good info / thinking re. future with HKA deployed.

Zero experience, but John's original thoughts (March 2020) may have some bearing... You probably read these too:

https://twitter.com/i/web/status/1237656703929180160

See 4 posts there... Interesting that some thought it was time to wind up Magisk / systemless root way back then! See phh's (Pierre-Hugues Husson of SuperUser, treble GSIs) comments. 😛

Think John said much more about HKA around that time to. PW
[Magisk] pndwal:
Think the build is taken down from TG now... (Yup, it's often more bleeding edge than Canary... you can get cut.) PW
[Magisk] Peter the Great:
Look what I found:

https://twitter.com/i/web/status/1299905865135190016

Looks like emulating the TEE could actually work then. I was under the impression that this emulated TEE would still need Google's private key to sign the root key, though I'm not sure after reading this.

Edit: nvm lol:

https://twitter.com/i/web/status/1462383098667040770
[Magisk] zgfg:
Sorry, I stopped monitoring the Alpha side. I see a version from Feb 11 (TG) - I never updated to that one but switched to Canary

Hence, did they have a newer version on TG that was then pulled off?

Renamed (and repackaged?), where they even re-enabled MagiskHide option?
[Magisk] dr4go:
The newest version available to date (4c808089) at least causes zygisk not being able to load - at least not on my device (S10).

Additional problem: I couldn't downgrade to d021bca6, because it failed with a "Download error" when modifying the custom channel. Then I thought: ok, plan c like "restore (i.e. unhide) the manager, uninstall, reinstall and rehide", unfortunately the restore also didn't work. So I uninstalled, installed the old alpha, but of course Magisk wasn't detected". Rebooted, then the new "Alpha" App appeared, which needed to download the full app... after that I was finally able to grant root to the old Magisk app and finally flashed the old (d021bca6) image... uninstalled "Alpha", rebooted and re-hid... jeez...

To the other thing: so I've seen that you have switched back to canaray and I had the same plan, at first... but after it's now possible to still have a non-chinese Alpha, I'll stick to it for another bit.bMy reasoning: that's going to hurt zygisk, because I think that shamiko, lsposed, etc. might stop fully working on Magisk at some point in time. That's why I stick to the dark ("Alpha") side, at least for now... 😉
[Magisk] pndwal:
Yup, today, I just downloaded source... This change log:

# alpha changelog

## Magisk (4c808089-alpha)

- [App] Support SharedUserId

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [App] Compatible with Android 12L

- [MagiskInit] Refactor the processing method of two-step startup

- [App] Added crash statistics

- [Script] Support init_boot partition

- [App] Allow loading zygisk modules

- [App] Delete unsuccessful install session files

- [App] Front-end interface tracking ignores root pop-up interface

- [App] Directly forward file stream when installing

- [App] The update completion notification is also displayed when the stub is normally updated to the full version

### ....

Seems Zygisk etc broken & taken down quickly... Package test may cause issues...

One comment re MagiskHide here:

https://t.me/c/1414270883/48080

I can't voch for these reports... Some there think telemetry means remote fixes! 😛 PW
[Magisk] dr4go:
Sorry to ask... how to join this Telegram group? I'm not a member and therefore only see the message "Not a member, banned by admin."
[Magisk] pndwal:
Sorry too; no idea now... No trouble when I joined... 🙁 Others may help you... PW
[Magisk] zgfg:
Invitation is maybe on some other (Chinese) groups or something.

In the old time group was opened

But here and there somebody new is accepted (screenshot) maybe you could try asking somehow
[Magisk] dr4go:
Strange... the only alpha group I find is this one: https://t.me/magiskalpha

But apparently that's not "your" alpha group...
[Magisk] zgfg:
Group as on the screenshot but invitation link was long ago removed.

And strictly in Chinese
[Magisk] pndwal:
Another go at Latest Unofficial vvb2060 Alpha:​

alpha changelog​

Magic (4c808089-alpha)​

[App] Support SharedUserId

[App] Delete the backup file after restoring the boot image

[App] Built-in current version update log

[General] No longer automatically unlock device blocks

[App] Adapt to Android 12L

[MagiskInit] Refactor the processing method of two-step startup

[App] Add crash statistics

[Script] Support init_boot partition

[App] Allow loading zygisk modules

[App] Delete unsuccessful install session files

[App] Front-end interface tracking ignores root pop-up interface

[App] Directly forward file stream when installing

[App] The update completion notification is also displayed when the stub is normally updated to the full version

https://github.com/vvb2060/Magisk/b...2d9cc178362/app/src/main/res/raw/changelog.md

Download:

https://github.com/vvb2060/magisk_files/tree/fbc9b19c3c142e165afc87a7262324f569d63e35

😬 PW
[Magisk] rodken:
All is functioning with the latest Alpha.

I just had to remember to uninstall the Magisk app as the latest Alpha installs a renamed version.