Ah yes, I remember your RealMe passing...
Note to Me; Bin RedMi, get Real... PW
Ah yes, I remember your RealMe passing...
Did you try with no modules active? Could be Hex Installer or other module issue I'm guessing (if you tried clearing dalvik cache etc I mentioned). PW
getprop ro.build.ab_update true
getprop ro.build.system_root_image false
Can't speak to your specific device, but I have 3 a/b devices (all Pixels) and I just flash the Magisk patched boot image like...2) Now a newbie's question.
Since Lisa (Xiaomi 11 Lite 5g NE) is the a/b device:
should I flash Magisk patched boot img to boot, or to boot_a, or both to boot_a and boot_b?
Per my understanding, boot will refer to the current slot (boot_a) while boot_b will be used for next OTA - hence even better not to patch boot_b
I also passed the S-pushtan root detectionThanks! ... Guess you have public Beta if 24.0. (The debug logging enabled synchronised Canary version is 24001.)
Please remind me what phone you have; MIUI OS that appears to have issues with HMA method now while other devices / OSs can pass easily. Also, can you show us Momo screenshot? PW
Pls read OP posts.
Why the Bold Circle flashing at launch of latest Magisk v24 beta?This is a discussion and help thread for the newer versions of Magisk.
The main goal of this thread is to help users migrate to Magisk v24+
Basic integrity Pass
CTS profile match Pass
- Play Protect certification
Device is certified
Feel free to discuss or give links to other Magisk related issues.
Fixes for gPay, banking apps and/or other apps and games that detect a 'compromised' Android system.
Please try to restrain from discussing alternative (unofficial) Magisk builds that include changes that were removed or can not be included in the official Magisk builds.
Please read John's State of Magisk (medium.com)
Starting with the Magisk 23 (23010) canary builds.
- MagiskHide is removed.
MagiskHide masked the sensitive properties of the device to hide it from SafetyNet.Renaming (repackaging) the Magisk app is/was not part of MagiskHide.
You still have the option to Hide the Magisk app under setting.
- Magisk Module online Repo is removed.
The Magisk Module online Repo is still available and can be accessed outside of the Magisk app.
- Everything SafetyNet is removed.
This includes the SafetyNet check that was incorporated into the Magisk app.
- Zygisk is introduced.
Zygote + Magisk = Zygisk
- The Deny list replaces the Hide list.
The Hide list (more or less) hid Magisk from the process on the list.
The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.
Starting with the Magisk 23 (23017) canary builds.
- Magisk supports update channels per module.
Each module can include it's own update link.
- Hide Magisk offline.
You do not need internet connection to rename (repackage) the Magisk app.
What does this mean?
Not much.It is just the next step in Magisk's development.Zygisk is a big step forward.
Even before these changes in Magisk, the xda family and the Android community have always been active and willing to share.
Magisk General thread, Dec 6, post #49346:
On the screenshot you can see that "Found Magisk" was not present
At that time I was running Alpha 23015 and some earlier versions of Shamiko and LSPosed. All the rest regarding Magisk, modules, LSPosed and its modules, root apps was the same
Yup, you need both; Shamiko initially only hid Zygisk (it's akin to RiruHide), then ability to hide Isolated process leaks etc were added... You may not even notice it's affect until you use bank apps etc that detect modified TEE by means other than relying on SafetyNet API.If it is relevant..
.when I briefly tried Shamiko it didn't work and lost Google certification. That was v23 too.
But I don't want to misdirect in case I missed a step and actually Shamiko v23 might be okay:.
I had downloaded and installed Shamiko then re-selected the 2 required GMS services into the deny list in Magisk that USNF disables, and then turned off the deny list in Magisk per Shamiko instructions. I turned off USNF. And then rebooted.
...I had lost CTS and Google certification in the Play Store realise not the same problem your trying to fix here but are the Shamiko alpha momentarily not working as intended? Or was removing USNF my error (you said earlier that it serves different purpose)
Yup, very first A12 release previews worked w/ Magisk on some (many?) devices before John made any changes for compatibility!...I see in the changelog of v24:
"[General] Support Android 12"
What does that mean?
I have been running v23 (stable channel) with Android 12 for some time now with no issues. It is not supposed to work? SafetyNet passes, Google Play is certified, banking apps work.
Yup, very first A12 release previews worked w/ Magisk on some (many?) devices before John made any changes for compatibility!...
When moving to a different desert (Android version) previously, Magisk had often spat it out until it grew up a bit / a taste was acquired, so this was a bit of a fluke & surprised even John...
Since then various fixes have been made for proper Android 12 compatibility, eg:
Support code injection on Android 12,
boot image header v4 - supports brand new devices launched with Android 12 w/ v4 boot images),
Target SDK 31 - This is the main reason for note in change log; - proper API (Application Programming Interface) Level 31 (Android 12) support.
Note: all the above ([General] Support Android 12) fixes arrived with the first Canary Magisk not synced w/ 23.0 back in October, ie. 23010 (many fixes since then too). The last 2 were authored by vvb2060 and were available in her Alpha builds months before that too!
Hey, thanks for that! I did read the OP posts but didn't see anything related to Riru/LSPosed. Will try your method then.Pls read OP posts.
Also, you can follow my post #14 from two days ago
- Uninstall all Riru modules, reboot
- If you had your Magisk app in Magisk v23, hidden, Restore Magisk app from its Settings.
Or uninstall that hidden Magisk app that you renamed/repackaged/hid
- Update from Magisk v23 to Canary v24 (read below about):
There are several possible paths. As it said in post #14, carefully read Magisk Documentation, Installation guide available from Magisk Github
E.g , I would prefer installing Magisk Canary v24 app, then patching the image, and flashing (details described in the mentioned guide)
But if you used to install your old Magisk v23 through TWRP, it should still work
You are talking about upgrading Msgisk but yoz also mention A12 - I doubt thar you had Magisk v23 on A12. In that case fully uninstall Magisk v23 and first upgrade your phone to A12.
Similarly if you need to update your A11
- then follow post #14
- after all that, install Zygisk-LSposed and your LSPosed modules, configure them
Nah just the childishness nonsense you mention. I was on a few Android groups at one point and they were all pretty obnoxious. That and when I tried having a public profile getting random "Hey are you THE osm0sis from xda? Cool! Just checking." roughly every couple days was ridiculous. Made me fairly certain I'm doing just fine with xda, Twitter, email, GitHub, Slack and TWRP's Zulip.I am just curious why you don't want to install telegram. About a year ago, or so, I uninstalled telegram because I got tired of the juvenile, posts on an android app dev forum, lspeed. I feel now that telegram is better moderated, but that is mostly based on the magisk alpha, lsposed. etc that I am now on. Is there some other security issues with it that I am not aware? I have most notification in it turned off so it doesn't constantly annoy me.
Sigh.. guess I'll secretly install Telegram just to download things.Seems not, but Canyie has fixed her GitHub link to Momo from MomoHider page https://github.com/canyie/Riru-MomoHider ('depreciation notice' introduces Shamiko - MomoHider may not be a 'thing' anymore...) however (Link to momo apk is dead #22 / Fix #22, 54d76a6), so at least we can link to that on XDA since we can't post TG links as file source...
Momo is linked under 'Test':
Momo complains about broken TEE because of the way OnePlus implemented hardware key attestation. The same happens on my 8T.What do you'll think about this Xposed module?
I can't find an app that doesn't work...momo still complains about broken tee.
4.1.1 momo, 1.3.7 privacyspace, 0.5.0 shamiko and 1.8.3 lsposed
notes.mdfile is the change log.
app-debug.apkis Magisk canary.
app-debug.apkand choose View Raw or click on the Download option.