Database Develop

[MODULE] App Shortcut & Widget In Notification Area

Introduction:
A Very Simple Module To Make The Following Apps Work As A System Apps To Achieve The Best Performance, Systemlessly.
- This Module Gives The Ability To Add App Shortcut Or App Widget To Notification Area Which Consists Of 2 Apps [Widget Shortcut App To Create The Required Widgets Inside It & Bar Launcher App To Add The Required Apps To The Notification Area Such As Widget Shortcut]
- This Module Is Mostly Used In The Following Cases {Quick Access To The Apps Such As Calc - The Ability To Recall A Widget Functionality At Any Time Such As Tasker Task [Because Some Launchers Do Not Support The Widgets / Some Users Do Not Prefer To Create The Widgets On The Home Screen / Some Apps Do Not Have A User Interface (Just A Widget)]}
Current Version: 1.0.1
Special Thanks To:
- Johannes Obermair
- dim_san
Created: Mar.29.2018
Updated: Mar.30.2018
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To The Latest Version Which Is Currently v17.3(17300)
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It With TWRP Recovery
General Info:
- To Disable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It Thru TWRP Recovery
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It Thru TWRP Recovery
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It Thru TWRP Recovery
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Microsoft Intune Company Portal Hider - Other Modules
----------------------------------------------------------------------------------------------------------------

Reserved for News/Updates #1

Reserved for News/Updates #2

Example Of Using This Module (AppShortcut&WidgetInNotification4Magisk) With Tasker For Hiding MagiskSu
>>> Hide-Unhide MagiskSu Via Tasker (+Notification Area) V2.1 <<< & >>> Hide-Unhide MagiskSu Via Tasker (+Notification Area) V2.2 <<< & >>> Hide-Unhide MagiskSu Via Tasker (+Notification Area) V2.4 <<<

Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)

[MODULE] Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner)

It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Clear The Data Of Google Play Store & Google Play Services.
- One Of The Methods To Solve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- After The Installation & 1st Reboot, It Clears The Data Of PS-GMS & Disables Itself
- After Doing Its Functionality, Check PlayStore Device Certification Status (Google PlayStore --> Settings --> Play Protect/Device Certification) Which Should Be Hidden For A While During Getting Its Status From Google
- Enabling The Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- The Module Is Just A Step To Solve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status Which Means Maybe You Need To Do Additional Steps To Solve The Issue
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of ClearPlayStoreWithServicesData
- For Activating The Functionality Of ClearPlayStoreWithServicesData, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> PlayStoreWithServicesData --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Created: May.13.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru TWRP Recovery
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
- Or Using A Flash-Tool (Flasher) Such FlashFire, Flashify Or Rashr --> Flash ZIP File (Flash A Flashable ZIP File) --> Choose The Downloaded File --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Clear Dalvik Cache - Core Only Mode - Other Modules
----------------------------------------------------------------------------------------------------------------

Reserved for News/Updates #1

I'm confused about this.... Is it the same as clicking clear date in app settings?

yung40oz84 said:
I'm confused about this.... Is it the same as clicking clear date in app settings?
Click to expand...
Click to collapse
Yes, But One Of Its Advantages Is Giving The System An Opportunity To Detect The Change At The Booting Stage.

yung40oz84 said:
I'm confused about this.... Is it the same as clicking clear date in app settings?
Click to expand...
Click to collapse
Did You Try The Module?

For Magisk v1400, Download ClearPlayStoreWithServicesData4Magisk-v1.0.0(v1400)(3MF).zip

Dreamer(3MF) said:
For Magisk v1400, Download ClearPlayStoreWithServicesData4Magisk-v1.0.0(v1400)(3MF).zip
Click to expand...
Click to collapse
Link is dead. Can you relink please
edit. got off internet site
---------- Post added at 05:07 PM ---------- Previous post was at 04:15 PM ----------
Is 1400 newest?

mattie_49 said:
Link is dead. Can you relink please
edit. got off internet site
---------- Post added at 05:07 PM ---------- Previous post was at 04:15 PM ----------
Is 1400 newest?
Click to expand...
Click to collapse
I Relinked The Title With The File Again. You Can Also Download The Module From OP(The 1st Post) Under The Attached Files Section.

Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)

Dreamer(3MF) said:
Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.00(1400) To v15.3(1531)
- For The Modules Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)
Click to expand...
Click to collapse
That explains why 1400 was causing madness on Oreo with 16.4 Magisk. Should just be one. Everyone has surely updated to latest haven't they?

mattie_49 said:
That explains why 1400 was causing madness on Oreo with 16.4 Magisk. Should just be one. Everyone has surely updated to latest haven't they?
Click to expand...
Click to collapse
No, I Hope That The Latest Version Of Magisk To Be Suitable For All Devices But It Relies On Many Factors Such As Boot Image, Kernel, Rom & Magisk Itself.

Are you sure that a SafetyNet infection is not more complicated?
I would really appreciate your input on this, as my Galaxy S5 on stock 6.0.1 is infected by SafetyNet. I re-flashed to stock and am about to flash Magisk 16.4. I am trying to decide whether a dreaded factory reset to wipe /data is necessary to get rid of the SafetyNet failed state. What I am afraid of is that there may be a cross-infection between /data/data (gapps) and installed apps that cooperate closely with SafetyNet.
In particular in my case, for example, an app "NOAA Weather" reports frequently back to Google and warned me to to update Play Services after I restored Play Services to a stock version. Poking around in Play Services SqLite databases in /data/data (...gms) I found an unencrypted database listing the NOAA Weather app executable name. I am afraid that the NOAA Weather app's data may also have my device blacklisted. And who knows where else in /data the SafetyNet failed state may be flagged?? What is your opinion about this?
Thank you!

BruceElliott said:
I would really appreciate your input on this, as my Galaxy S5 on stock 6.0.1 is infected by SafetyNet. I re-flashed to stock and am about to flash Magisk 16.4. I am trying to decide whether a dreaded factory reset to wipe /data is necessary to get rid of the SafetyNet failed state. What I am afraid of is that there may be a cross-infection between /data/data (gapps) and installed apps that cooperate closely with SafetyNet.
In particular in my case, for example, an app "NOAA Weather" reports frequently back to Google and warned me to to update Play Services after I restored Play Services to a stock version. Poking around in Play Services SqLite databases in /data/data (...gms) I found an unencrypted database listing the NOAA Weather app executable name. I am afraid that the NOAA Weather app's data may also have my device blacklisted. And who knows where else in /data the SafetyNet failed state may be flagged?? What is your opinion about this?
Thank you!
Click to expand...
Click to collapse
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Enable WiFi --> Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Magisk Manager --> Tap To Start SafetyNet Check --> Send Its Screenshot
- Install SafetyNet Helper Sample From PlayStore & Send Its Screenshot
- Magisk Manager --> Modules --> Send Its Screenshots
- Magisk Manager --> SuperUser --> Send Its Screenshots
- From Settings --> About Phone --> SELinux Status --> Send Its Screenshot
- Complete Info About The Device, The Used Rom & The Used Kernel
- Send Full Logcat (Download Logcat Extreme From PlayStore) & Magisk Log (Magisk Manager --> Log --> Magisk & SuperUser)
- Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write magiskhide --ls --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which su --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write getenforce --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write sestatus --> Click On Enter --> Send Its Screenshot
General Steps For Passing The SafetyNet & Certifying The Device:
- Download ClearPlayStoreWithServicesData4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Download SELinuxModeInverter4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix&Pokemon-Go From PlayStore
- If It Didnot Work, Download DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Download ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
General Steps For Using Netflix:
- Uninstall Netfilx If Installed
- Download ClearPlayStoreWithServicesData4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download Netflix Enabler From This Thread https://forum.xda-developers.com/apps/magisk/module-netflix-enabler-enable-netflix-t3708126 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Disable Netflix Enabler From Magisk Manager
- Download Liboemcrypto Disabler From This Thread https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download SELinuxModeInverter4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore

Jvirg said:
Magisk manager?
Click to expand...
Click to collapse
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse

BruceElliott said:
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse
Regarding busybox, I did not install one specifically; however Titanium installs with its own. I believe that there may also be a system busybox, but not sure.
Click to expand...
Click to collapse

BruceElliott said:
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
According To The Sent Screenshots, PlayStore Device Certification Status Is Certified & Your Device Passed The SafetyNet. Is There Anything Else You Want To Check?

BruceElliott said:
BruceElliott said:
Regarding busybox, I did not install one specifically; however Titanium installs with its own. I believe that there may also be a system busybox, but not sure.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot

Dreamer(3MF) said:
Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
Click to expand...
Click to collapse
I believe that I am good on this thread, Dreamer; thank you!

This is an excellent script and did what I struggled to do manually.
I feel there's a noticeable difference in the battery consumption post this script as I'm being a bit more conscious about what Google options to permit this time around.
Great work.
Sent from my SM-N910F using Tapatalk

-------------------------------------------------------------------------------------------------------------------------

[MODULE] Google Pay (Tez & GPay) Hider (Tez Hider)

Introduction:
Simple Module To Hide The Root From Google Pay (Tez) [Google Mobile Payments Service For India].
- After The Installation & 1st Reboot, It Hides The Rooting & Disables Itself [P.S. Disabling Itself For Some Versions]
- Enabling This Module From Magisk Manager = Doing Its Functionality & Disabling Itself (Next Reboot) [P.S. Disabling Itself For Some Versions]
Current Version: v0.1.2.1AND
- Magisk Hide Must Be Working Properly Which Is A Main Point To Use The Module
- Passing The SafetyNet Means Also Magisk Hide Is Working So Check The General Steps
- Some Issues Which Are Related To Magisk/Rom/Kernel/GApps Itself Can Be Solved By Using A Different Versions Of The Module [Where v0.1.2.1A/v0.1.2.1AD Can Be Downloaded From The Same Download Link Inside The Folder Of Special]
- Some Versions Of The Module & Some Roms/Kernels/GApps Have Some Effect On Sync That Will Be Reflected On Apps Which Need Sync So To Solve The Issue, Do The Following [Disable The Module & Reboot To Use The Other Apps Which Need Sync] Or [Enable The Module & Reboot To Use Tez]
- It Is Recommended To Clear Magisk Hide List Including Each App/Activity/Process Before Flashing The New One So Use The Module Of ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208
- For Google Pay (Tez & GPay), Check These Posts https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post79008117 & https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post79194395
Created: Apr.18.2018
Updated: Feb.11.2019
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The General Steps)
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To The Latest Version Which Is Currently v18.1(18100)
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru TWRP Recovery
Magisk Hide:
- Tez Will Be Added Automatically To The List Of Magisk Hide
- Some Apps Will Be Added Automatically To The List Of Magisk Hide Such As Google Play Services, Google Play Store, Google Services Framework, Phone Apps & Phone Services
Recommendation:
- Check The General Steps From This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76816985
- In-Case Of Failure, Check This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76675913
- For Passing The SafetyNet & Certifying The Device, Check This Post https://forum.xda-developers.com/ap...playstore-services-data-t3789498/post76682978
Beta Version:
- Check This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76650492
General Info:
- To Disable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It Thru TWRP Recovery
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It Thru TWRP Recovery
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It Thru TWRP Recovery
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Device Spoofing Tool - Core Only Mode - Other Modules
----------------------------------------------------------------------------------------------------------------
P.S. You Can Update Tez App As You Want Without Any Effect On The Module Unless The Changes Of Tez App Are Related To The Root Detection. But Everyone Here Will Help Us To Figure Out The Solution.
----------------------------------------------------------------------------------------------------------------
The Old Thread (Tez App Is Not Working On Custom Rom Or Rooted Device)
----------------------------------------------------------------------------------------------------------------

Reserved for News/Updates #1

Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)

Reserved for News/Updates #1

Beta Version:
Current Beta Version: -
Changelog: -

Thanks for the life saver module

charlessxavier said:
Thanks for the life saver module
Click to expand...
Click to collapse
Thanks. Could I Ask You To Try The Beta Version & Send The Feedback?

I Am Asking Our Mates To Check The Stable&Beta Versions And Share The Feedbacks/Ideas/Questions To Enhance/Modify The Module.

Beta version seems to be not working for me.

Dreamer(3MF) said:
Thanks. Could I Ask You To Try The Beta Version & Send The Feedback?
Click to expand...
Click to collapse
Done. No issues with this version. Was able to transfer money successfully.

Tried beta version didn't worked on official magisk v16 , cleared data & cache of tez - downloaded & flashed beta zip - rebooted - tried registration - detected
(Using RR custom Oreo rom )

H4CK_H0PP3R said:
Tried beta version didn't worked on official magisk v16 , cleared data & cache of tez - downloaded & flashed beta zip - rebooted - tried registration - detected
(Using RR custom Oreo rom )
Click to expand...
Click to collapse
- Did You Enable Phone Permission Of Google Play Services?
- Did You Use The Stable Version? & What Is The Feedback?

Able to register, but not able to add bank account..
Magisk 16.4 , Tissot with liquid remix rom

Suggestions
- Uninstall Any Other Rooting Tool Completely Such As SuperSu & Lineage-AddOnSU Which Is Used With Magisk
- Download A Different Version Of TezHider4Magisk Module From This Link https://androidfilehost.com/?w=files&flid=284689 Then Flash It Thru Magisk Manager Then Reboot
- Try DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435
- Try SELinuxModeInverter4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271
- Try To Disable Phone Permission Of Google Play Services (From Settings --> Apps --> Google Play Services --> Permissions --> Disable Phone)
- Try To Install The Latest Version Of Magisk (Stable/Beta) Or One Of The Modified Magisk Versions From This Link https://androidfilehost.com/?w=files&flid=274603
- Do A Clean Flash For The Same Used Rom Or Change The Rom Or Change The Kernel
For Any Issue, Send The Issue Along With The Following
- Enable WiFi --> Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Magisk Manager --> Tap To Start SafetyNet Check --> Send Its Screenshot
- Install SafetyNet Helper Sample From PlayStore & Send Its Screenshot
- Magisk Manager --> Modules --> Send Its Screenshots
- Magisk Manager --> SuperUser --> Send Its Screenshots
- From Settings --> About Phone --> SELinux Status --> Send Its Screenshot
- Complete Info About The Device, The Used Rom & The Used Kernel
- Send Full Logcat (Download Logcat Extreme From PlayStore) & Magisk Log (Magisk Manager --> Log --> Magisk & SuperUser)
- Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write magiskhide --ls --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which su --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write getenforce --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write sestatus --> Click On Enter --> Send Its Screenshot

vygavedha said:
Able to register, but not able to add bank account..
Magisk 16.4 , Tissot with liquid remix rom
Click to expand...
Click to collapse
Kindly Check This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76675913. And Did You Install Stable/Beta Version?

I found something mate.
When I already have tez registered using the stable module and on top if I flash the beta version there seems to be no problem.
Whereas, if I install the beta version first and register tez it's failing.

About Sending The Full Logcat: You Can Use One Of The Following Methods
- Download Terminal Emulator From PlayStore & Write logcat | grep nbu > log.txt
- Download Logcat Extreme (Or Catlog) From PlayStore
- Write adb logcat -d > log.txt For ADB

prakashait9 said:
Beta version seems to be not working for me.
Click to expand...
Click to collapse
Kindly Do The Following
- Flash Stable Version --> Reboot --> Register Tez
- Flash Beta Version --> Reboot --> Try To Transfer Money

Dreamer(3MF) said:
Beta Version:
Current Beta Version: 0.1.3.1(Beta)
- Firstly Flash Stable Version --> Reboot --> Register Tez
- Secondly Flash Beta Version --> Reboot --> Try To Transfer Money
Changelog: Disabling Some Permissions Of Phone Services.
Thanks Again To Our Mate prakashait9 Who Suggested The Modification
Click to expand...
Click to collapse
Dreamer(3MF) said:
- Did You Enable Phone Permission Of Google Play Services?
- Did You Use The Stable Version? & What Is The Feedback?
Click to expand...
Click to collapse
Did You Enable Phone Permission Of Google Play Services? : I did nothing as per new beta version it changes permission by self so didn't changed any permission
- Did You Use The Stable Version? & What Is The Feedback - No beta version i tried as I thought it worked for some people .

H4CK_H0PP3R said:
Did You Enable Phone Permission Of Google Play Services? : I did nothing as per new beta version it changes permission by self so didn't changed any permission
- Did You Use The Stable Version? & What Is The Feedback - No beta version i tried as I thought it worked for some people .
Click to expand...
Click to collapse
Use The Stable Version From OP(1st Post) Under Attached Files Section & Kindly Do The Steps As Per Mentioned In This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76675913#post76675913.

[MODULE] Core Only Mode (Bootloop/Bootscreen/Blackscreen Solver For Modules)

It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Open Magisk In Core Only Mode.
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Flash This Module
- This Module Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot (Rebooting The Android Is Required To Load The Rest Of Modules)
- Core Only Mode Gives The Device The Ability To Get Into The Android Directly With User Interface Which Means The User Can Use The Device With All Features/Functionalities Except Magisk Modules Even Before Removing The Module(s) Which Caused The Bootloop/Issue
- Enabling Core Only Mode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled
- After The Installation & Booting, It Opens Magisk In Core Only Mode & Disables Itself
- Enabling This Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- For Using The Module Thru ADB Shell/TWRP Terminal [The Module Must Be Pre-Installed Via Magisk Manager/TWRP Recovery/ADB Sideload], Write The Following Commands --> rm -f /data/DreamerMods/MultiFunctions/MagiskCoreOnlyMode/Active/disable (Click On Enter) --> reboot (Click On Enter)
Created: July.17.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Flash It Thru TWRP Recovery
- Or Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Clear Dalvik Cache - Other Modules
----------------------------------------------------------------------------------------------------------------

Reserved for News/Updates #1

Reserved for News/Updates #2

I Am Asking Our Mates To Check The Stable Version And Share The Feedbacks/Ideas/Questions To Enhance/Modify The Module.

Thank you brother :highfive:

image18 said:
Thank you brother :highfive:
Click to expand...
Click to collapse
Did you try?
Sent from my MIX 2 using Tapatalk

amour9999 said:
Did you try?
Sent from my MIX 2 using Tapatalk
Click to expand...
Click to collapse
yes

I wonder...
How can we get into magisk manager to use this module when having bootloop problem?

bnwg said:
I wonder...
How can we get into magisk manager to use this module when having bootloop problem?
Click to expand...
Click to collapse
In-Case Of Facing A Bootloop Issue Due To Flashing A Module, You Need To Put A Copy Of CoreOnlyMode4Magisk On SD-Card/Internal Memory Then Flash This Module Thru TWRP Recovery. This Module Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing The Module Which Caused The Bootloop From The Section Of Modules In Magisk Manager.

Hello,
Thanks for that.
It's a little similar to the first feature of mm module (https://github.com/Magisk-Modules-Repo/Magisk-Manager-for-Recovery-Mode), but yours one directly enable the "Core Only Mode" of Magisk, the differences are that all modules are disabled as u said on your OP and it disable the "Magisk Hide" and "Host systemless support" features, that's it, right ?
Effectivly it could be usefull in case the mm module don't works for any reason or if one or several hiders/hosts module(s) cause bootloops on a device.

Rom said:
Hello,
Thanks for that.
It's a little similar to the first feature of mm module (https://github.com/Magisk-Modules-Repo/Magisk-Manager-for-Recovery-Mode), but yours one directly enable the "Core Only Mode" of Magisk, the differences are that all modules are disabled as u said on your OP and it disable the "Magisk Hide" and "Host systemless support" features, that's it, right ?
Effectivly it could be usefull in case the mm module don't works for any reason or if one or several hiders/hosts module(s) cause bootloops on a device.
Click to expand...
Click to collapse
Thanks For Your Interest. As For Magisk Manager For Recovery Mode & Core Only Mode, Both Of Them Are Sharing The Same Target But Not The Same Concept. Core Only Mode Gives The Device The Ability To Get Into The Android Directly With User Interface Which Means That The User Can Use The Device With All Features/Functionalities Except Magisk Modules Even Before Disabling/Removing The Module(s) Which Caused The Bootloop/Issue.
Enabling Core Only Mode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled.

This module is usefully! THANKS BRO!

Fdraco10 said:
This module is usefully! THANKS BRO!
Click to expand...
Click to collapse
Thanks! You Can Also Check Another Useful Modules From This Link >>>Other Modules<<<.

thanks man! your module is my device savior

This module is useful

Deleted

peterlee928 said:
much thanks for sharing this lovely tool. this will save me much time going forward.
Dreamer(3MF) said:
In-Case Of Facing A Bootloop/Bootscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It Thru TWRP Recovery.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@peterlee928 Nice To Hear It Worked. And You Can Try Also The Following Useful Modules
- ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264
- ClearPlayStoreWithServicesData4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498

Very nice module, it is great to save you from bootloop, same as entering in Safe Mode on PC!!
But how disable Core Only Mode after removing the problematic module???
I delete guilty module and rebooted, but still Magisk in Core mode only!
I removed the module Core Only Mode, and rebooted and still Magisk in Core Only Mode
How to get back to default working Magisk State??
Thx.

saoudien07 said:
Very nice module, it is great to save you from bootloop, same as entering in Safe Mode on PC!!
But how disable Core Only Mode after removing the problematic module???
I delete guilty module and rebooted, but still Magisk in Core mode only!
I removed the module Core Only Mode, and rebooted and still Magisk in Core Only Mode
How to get back to default working Magisk State??
Thx.
Click to expand...
Click to collapse
Check The Following Post.
Dreamer(3MF) said:
Introduction:
Simple Module To Open Magisk In Core Only Mode To Help For Removing Any Module Which Causes A Bootloop.
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, You Need To Put A Copy Of CoreOnlyMode4Magisk On SD-Card/Internal Memory Then Flash This Module Thru TWRP Recovery
- This Module Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot (Rebooting The Android Is Required To Load The Rest Of Modules)
Click to expand...
Click to collapse

Dreamer(3MF) said:
Check The Following Post.
Click to expand...
Click to collapse
Thx for the fast answer
so was in Magisk "SETTING"
Nothing to do with uninstalling of the module.
Btw u got great modules, they are must have and should go to toolbox of every Rom tweaker

[Discussion] Magisk - The Age of Zygisk.

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+
SafetyNet
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)
State of Magisk: 2021
State of Magisk: 2020
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.
Jump to Post​Magisk - Modules - Apps - Force Basic Attestation - Basic Attestation - Adjust Prop values - Notes - Points of Interest​
This is post will be updated once Magisk v24 is released.​

Magisk​The Magic Mask for Android.​
Magisk Links:
GitHub
Installation Instruction
Frequently Asked Questions
Magisk Documentation
Magisk Troubleshoot Wiki (by Didgeridoohan)
Release Notes
Download Links:
Stable and Beta releases.
GitHub
Canary
GitHub
The notes.md file is the change log.
The app-debug.apk is Magisk canary.
Click on app-debug.apk and choose View Raw or click on the Download option.​
Credits:
topjohnwu
All who contribute and support this project.

Modules​
MagiskHide Props Config
This module allows you to add, change and adjust prop values systemlessly using Magisk.​
MagiskHide Props Config Links:
GitHub
xdaThread
Download Links:
GitHub
Credits:
Didgeridoohan
All who contribute and support this project.
Universal SafetyNet Fix
It has been a year now since kdrag0n figured out how to 'trick' SafetyNet.
This 'trick' has been implemented properly into quite a few custom roms.
For custom roms that do not include it and/or stock roms, he turned it into a module.​
Universal SafetyNet Fix Links:
GitHub
xdaThread
Download Links:
GitHub
Credits:
kdrag0n
All who contribute and support this project.

Apps​
Fox's Magisk Module Manager
This app allows you to manage and install Magisk modules.
Including from an online repo.​
Fox's Magisk Module Manager Links:
GitHub
Download Links:
GitHub
Credits:
Fox2Code
All who contribute and support this project.
Play Intergrity API Checker
This app shows info about your device integrity as reported by Google Play Services.
If any of this fails could mean your device is rooted or tampered in a way (for example you have an unlocked bootloader).​
Development:
GitHub
Download Links:
PlayStore
Credits:
1nikolas
All who contribute and support this project.
YASNAC - Yet Another SafetyNet Attestation Checker
YASNAC (short for Yet Another SafetyNet Attestation Checker) is an Android app that demonstrates SafetyNet Attestation API.​
YASNAC Links:
GitHub
PlayStore
Download Links:
GitHub
PlayStore
Credits:
RikkaW
All who contribute and support this project.

Force Basic Attestation​
Newer devices are designed to support hardware attestation.
Currently there is no way to hide the sensitive device properties when checked using hardware attestation.​
To get around this, kdrag0n figured out how trick SafetyNet that the device does not support hardware attestation.
SafetyNet will then fall back to check using basic attestation.
Note:
This method will work for devices that support hardware attestation and devices that do not.
Enable Zygisk.
Install the USNF module.
Reboot
To keep posts short, the instructions are hid by spoiler tags.
Spoiler: Instructions
If you have not installed Magisk.
Follow the installation link in the Magisk post.​
Download the Universal SafetyNet Fix module.
Download link is in the Modules post.​
Enable Zygisk
Open the Magisk app.
Go to Settings.
Scroll down to the Magisk section.
Toggle Zygisk on.
Go back to the Magisk Home screen.
Go to Modules.
Select Install from storage.
Navigate to the Universal SafetyNet Fix module zip file and select it.
Reboot.
The USNF module will adjust the sensitive props that are needed to pass SafetyNet.
Depending on the device and system (ROM) configuration, you might need to adjust a few more.
See the Adjust Prop values post.​

Basic Attestation​<Reserve>
Older devices that can not support hardware attestation there are other options.
Enable Zygisk.
Enable Denylist.
Add com.google.android.gms.unstable to the Denylist.
Add com.google.android.gms to the Denylist if needed.
Reset the sensitive prop values for the device.
Click to expand...
Click to collapse
Due to other modules and methods that require DenyList to be inactive, this method is more for reference.
For ease of use and compatibility, I would recommend using the USNF module instead.
See the Force Basic Attestation post.​
This post will be updated in a few days.​

Adjust Prop values​<Reserve>
Reset sensitive prop values.
Spoiler: Instructions
Download the MagiskHide Props Config module.
Open the Magisk app and select the Modules option.
Select Install from storage option.
Navigate to where you saved the MHPC module and select it.
When the install is done, reboot.
Open a terminal app (or adb shell) and type props in the command line.
Make sure to grant root access
Select the Edit MagiskHide props (active) option.
(Currently option number 4)
It will show you the sensitive props that need to be adjusted.
If they all show (active) no changes needed.
If there is a prop value that shows as (enabled, not active) then you need to activate it by selecting it or a for all.
You will be prompted to set MagiskHide sensitive props?
Enter y(es), n(o) or e(xit):
If you are using a custom rom, you might also have to adjust the build fingerprint and security date.
From the MHPC main menu select Edit device fingerprint option.
(Currently option number 1)
Select Pick a certified fingerprint option.
(Currently option f)
Select the latest certified print for your device.
If your device is not listed, choose a device that is close to yours.​
This post will be updated soon.​

Notes​and​Common Issues​<Reserve>
Spoiler: SafetyNet
<Reserve>
Spoiler: Play Protect certification
<Reserve>
Spoiler: PlayStore App Purchases and Updates
<Reserve>

Points of Interest.​
LSPosed
Zygisk releases are now included.
Download Links:
GitHub - Releases
Shamiko
Download Links:
GitHub - Releases
Denylist Unmount
Download Links:
GitHub - Releases

Yay! I get post no. 10!
Good to see this thread up Doc! ... How are you linking / promoting it?
Want mentions in Magisk General Discussion thread, or not for now?...
I note that this thread has the advantage of having an active OP...
So what? - Means I can post rubbish and it will be cleaned! ... Love a clean house... Hope you're a good housekeeper @ipdev! PW

zputnyq said:
Hi all,
I'm on TJW's canary 23019.
Does anyone know/could explain what is/are the difference(s) with enforce denylist activated and not activated ?
Click to expand...
Click to collapse
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...
Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW
Edit: Lets kickstart things here!

pndwal said:
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...
Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW
Edit: Lets kickstart things here!
Click to expand...
Click to collapse
Ok, I get it. Thank you.
I was confused since I use an old device which doesn't really need this part to do the hiding & on v23017 John made that part work along with the configure denylist, I mean configure denylist is greyed out when denylist part isn't active.

zputnyq said:
Ok, I get it. Thank you.
I was confused since I use an old device which doesn't really need this part to do the hiding & on v23017 John made that part work along with the configure denylist, I mean configure denylist is greyed out when denylist part isn't active.
Click to expand...
Click to collapse
You could do worse than read the first 5 posts here! PW

Thanks @ipdev
I tried to put a short help for probably the most frequent posts/questions soon to expect.
(Sorry for cross-posting, I first put to the old and cluttered General Magisk thread but this is now better place)
===
Please carefully read Magisk Changelog and OP posts in this thread
Study the Magisk documentation from the official Magisk Github page - particularly about installing Magisk (if not familiar with patching the image in Magisk app and flashing the patched img from Fastboot- different from the old school about flashing Magisk zip through TWRP)
a) No more MagiskHide. New technology instead (for more or less the same - to help hiding root): Zygisk+DenyList
b) No more built in SafetyNet checker. Install from PlayStore e g: YASNAC to check your SN
c) Modules window does no more connect to the old Modules repository.
You must download module zip files manually and "Install from local storage".
Or search for and install Fox Magisk Module Manager (Fox Mmm) app - it will connect to the new, alternative repository and the old 'official' repo, allowing you to install from both
---
0) If upgrading Magisk and if you previously did "Hide Magisk app/Mngr" from Magisk app/mngr - always "Restore Magisk app/Mngr" before upgrading Magisk
1) Make sure that both Magisk app and Magisk are installed and updated to the new version v24 version. Inspect version numbers on the main Magisk window/page
2) Make sure to uninstall all Riru modules (Riru is not compatible with Zygisk that comes with Magisk v24)
3) Settings, Enable Zygisk and reboot.
Then check on the main window does it show Zygisk Yes
4) Settings, enable Enforce DenyList.
Configure DenyList, enable filters to Show OS and System apps.
Find Google Play Services and check-in only the two processes ending with gms and gms.unstable.
You will have to check in all your banking apps and so as you used with MagiskHide.
Always reboot upon reconfiguring DenyList
5) If SafetyNet does not pass, install USNF 2.2.1 and test again.
Always reboot upon installing a module, also if/when you enable Systemless Hosts
Note: Once you install/enable USNF 2.2.1, it will remove Google Play Services from your DenyList - but don't worry, USNF takes care of GMS
6) If you are on non-certified custom ROM and you still don't pass SN - then you will need Magisk Hide Props Config module - check for and consult the MHCP thread
---
If you want to hide Zygisk, then instal Shamiko module - and you must disable Enforce DenyList (although DenyList must stay configured).
But Shamiko is really not essential (might help for some banking apps but it's irrelevant for SafetyNet)
---
Banking apps - out of scope for this post (also, this thread is about the Magisk v24 itself, not abkut the particular banking apps)
Go to Magisk Github documentation, read Wiki, there is a section with tips you should try first
If putting your banking app to DenyList (now, instead of the old Magisk Hide) and hiding Magisk app does not help, and the other tips from Wiki do not help (like renaming TWRP folder and so), search in this thread how to use Hide My Applist (Zygisk-LSPosed module)
Every time you apply another tip to your troublesome banking app - go to Settings, Apps, and delete Cache and Data for that banking app before you try to open it again (some apps will cache that they previously found the phone was rooted)
Even with HMA, there are certain banking apps that cannot be tricked (on some phones like Xiami, etc)
---
Momo - absolutely not essential for your life
When you pass SN, Momo might still detect that your Bootloader is unlocked - you cannot hide it from Momo on e.g. Xiaomi phones
Generally, treat Momo as 'banking' apps (add to DenyList and reboot)
Momo does not look for apps (Magisk app, LSPosed mngr, LSPosed modules), hence for Momo you don't need to bother with HMA
Basic tips for Momo: Remove/rename TWRP folder, disable USB Debugging - for the rest, search for Momo posts in this thread - but still, there will be findings you could not hide from Momo (not encrypted Data, custom ROM, etc)
===
PS: Magisk Alpha v24.1 (vvb2060 and her team) has departed their way (different package name, revival of MagiskHide?), hence this post is now (mainly) for the official TJW Magisk Stable and Canary v24
(Some parts do apply also to Alpha but use Alpha on your own risk and ask the other Alpha users about the Alpha status and practices)
===
Last but not the list - there night be specifics for certain phones (like flashing with Odin for Samsung, end so on)
This post is generic, for your specific practices read/search through this thread and also on your phone/model subforuns on XDA

Hello - sorry if obvious but I'm having issues getting some apps checking for root to pass. I think the issue might well be the statement related to "Google Play Services and check-in only the two processes ending with gms and gms.unstable."
Regardless of whether I tick just these two, or if I tick the whole of Google Play Services, once I reboot and if I go back into Magisk the app reports that these services are no longer hidden.
This is Pixel6Pro Stock, January update, Magisk canary (but 24001 that synced with the public build) + Zygisk + USNF 2.2.1
Thank you
Chris

@ipdev
Thread was pinned. Thx for your effort

Nice. Will we be able to run a module like fakegapps without riru/LSPosed?

crypticc said:
Hello - sorry if obvious but I'm having issues getting some apps checking for root to pass. I think the issue might well be the statement related to "Google Play Services and check-in only the two processes ending with gms and gms.unstable."
Regardless of whether I tick just these two, or if I tick the whole of Google Play Services, once I reboot and if I go back into Magisk the app reports that these services are no longer hidden.
This is Pixel6Pro Stock, January update, Magisk canary (but 24001 that synced with the public build) + Zygisk + USNF 2.2.1
Thank you
Chris
Click to expand...
Click to collapse
No, you don't need to add Play Services processes w/ Zy-USNF as I explained here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86321879
Download YASNAC and check if you pass SafetyNet, then that you have Play Protect Device is certified in Play Store settings... If you have these, Bank app is using its own custom detection methods... PW

kurtn said:
Nice. Will we be able to run a module like fakegapps without riru/LSPosed?
Click to expand...
Click to collapse
Yes, Use Zygisk-LSPosed. PW

pndwal said:
No, you don't need to add Play Services processes w/ Zy-USNF as I explained here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86321879
Download YASNAC and check if you pass SafetyNet, then that you have Play Protect Device is certified in Play Store settings... If you have these, Bank app is using its own custom detection methods... PW
Click to expand...
Click to collapse
Yes I appreciate that. I guess my question was if it is correct that after reboot USNF deselects the gms and gms.unstable
Thanks for the explanation.
FYI found what was triggering the app and got it working. Before I had just renamed Magisk (I renamed to MagicApp if that matters) but that didn't work. Also "pausing" the app wasn't enough.
I needed to actually uninstall the Magisk Manager app itself.
So the mechanism being used by the other app wasn't looking for Magisk/SU, but the app iself.
The App failing doesn't have any local file permissions so must've been something else.
Actually I found two apps failing root check and both were resolved by uninstalling the (renamed) Magisk APK.
So I wondered if the app was simply listening to debug messages.
So I reinstalled and then reproduced the failure looking into ADB logcat.
I could see during opening and just before the protection was triggered logcat events against the ".Magisk" app related to denying access. Uninstalling Magisk app stopped those messages and then the app was able to start.
Should Magisk "hiding" the magisk manager app by renaming it from ".Magisk" also have relabelled all of the messages and such related to the app?