Related
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)
- MultiFunctionsPlus Is The Successor Of MultiFunctions
- The Main Difference: The Pre-Activated Functions = Flashing MultiFunctionsPlus + Activator = Flashing MultiFunctions Only Or Deactivating The Pre-Activated Functions = Flashing MultiFunctionsPlus Only = Flashing MultiFunctions + Deactivator
Click to expand...
Click to collapse
MultiFunctionsPlusPage 1 Of 2Introduction:
A Module To Do The Next Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value, Keeping MagiskDaemon-MagiskHide Running, Changing DoubleTap2Wake(DT2W) Status, Fixing PlayStore Device Certification Status - Passing SafetyNet, Enabling The Low Ram Configurations, Disabling The Other Magisk Modules, Disabling The Magisk General Scripts & More].
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules, Scripts Or HideList, Check Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList) In Below
- P.S. All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Below
- P.S. All Functions Can Be Used With Any-Rooting-Tool Except The Ones For Magisk Users Only As Described In Below
Current Version: MultiFunctionsPlus v1.0.3.4.2.4B7 - Activator v1.0.0.17A4.0.0 - QuickFix4Busybox v0.0.0.0.0.3
Recommendations:
- For Magisk Users Only, Disabling MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager & Rebooting The Device Are Required To Load The Modules
- For Activating Any Function Using Any Root File Explorer Such MiXplorer To Access The Part Of Data Thru Root, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/<TheFunction>/Inactive And Then Reboot The Device
- P.S. In-Case Of Moving/Deleting The File Of Disable In Error, Deleting The Folder Of Status (/data/DreamerMods/MultiFunctionsPlus/Status) & Rebooting The Device Will Create The File Of Disable Again
- Activator Is A Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList (P.S. MultiFunctionsPlus Is Required To Be Flashed Before Using Activator) So Actually There Is No Needing To Flash It To Use Any Function Such SELinuxModeInverter
- After Flashing The Module Of Activator & Rebooting The Device, It Will Do Its Functionality & Remove Itself
- P.S. For Any Magisk Version Below v14.0(1400), Use Any Method To Flash The Module As Described In Below Except Magisk Manager
- P.S. For Some Versions Of Magisk, Use QuickFix4Busybox As A Resolver For The Issue Of Internal Magisk Busybox Which Prevents Some Of Commands From Executing
Created: Nov.30.2019
Updated: Feb.22.2020
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The Description)
** Magisk Installer: It Supports Magisk Only
- 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 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 v20.1(20100)
- For The Module Which Is Ended Its Name With v19000P (Or MMTEx1.x), It Supports Magisk v19.0(19000) To The Latest Version
** Unity Installer: It Supports Any-Rooting-Tool Such SuperSU, Lineage-AddOnSU & Magisk
- P.S. If You Flash The Same Version Of Module Twice, The Module Will Remove Itself But If The Version Of Second Time Is Higher Than The Version Of First Time, The Module Will Update/Upgrade Itself
- For The Module Which Is Ended Its Name With Unity1.5.x, It Supports Magisk v15.3(1530) To The Latest Version
- For The Module Which Is Ended Its Name With Unity1.5.4Ax, It Supports Magisk v8(800) To The Latest Version
- For The Module Which Is Ended Its Name With Unity4.x, It Supports Magisk v18.0(18000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity5.x, It Supports Magisk v19.0(19000) To The Latest Version
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru A Custom-Recovery Such TWRP Recovery --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload TheFileNameOfModule.zip --> Reboot (P.S. Renaming The File To Have A Short One Is Recommended Such mfm.zip Before Using ADB Sideload)
- Or Using A Flash-Tool (Flasher) Such EX Kernel Manager, FK Kernel Manager, FlashFire Or Flashify --> Flash ZIP File --> Reboot
The Description: (1)
1- DalvikCache Cleaner (Advanced Dalvik/ART Cache Cleaner)
- Clearing The Dalvik Cache
- Doing The Same Functionality Of Wiping Dalvik/ART Cache Thru TWRP Recovery
- Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Maybe It Takes About 5 Min. To Finish The Process
- After Doing Its Functionality, Check The Free Space Of Internal Storage Which Should Be Increased/Maximized A Little Bit
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of DalvikCacheCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/DalvikCacheCleaner/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
2- PlayStoreWithServicesData Cleaner (Advanced PS-GMS Data Cleaner)
- Clearing The Data Of Google Play Store & Google Play Services
- One Of The Methods To Resolve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- 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
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of PlayStoreWithServicesDataCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/PlayStoreWithServicesDataCleaner/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
3- MagiskHideList Cleaner (Including MagiskHide Enabler & MagiskHideList Backup) [For Magisk Users Only]
- Clearing MagiskHideList [All Added Apps/Activities/Processes In MagiskHideList]
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To MagiskHide, Use The Function To Clear All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue
- Activating The Function = Doing Its Functionality, Taking A Backup Of HideList & Disabling Itself
- For Activating The Functionality Of MagiskHideListCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/Inactive And Then Reboot The Device
- Additional Feature (Deactivating The Main Function + Activating The Sub-Function Of BackUp [Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/Inactive And Then Reboot The Device] = Taking A Backup Of HideList)
- Additional Feature (Deactivating The Main Function + Putting A Copy Of The File Of HideList.txt Into The Folder Of Retrieving [Copy The File Of HideList.txt From /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/HideList.txt To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/Retrieving And Then Reboot The Device] = Retrieving/Restoring The Last Saved MagiskHideList)
- Additional Feature (Activating The Sub-Function Of HideEnabler [Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/Hide/Inactive And Then Reboot The Device] = Enabling MagiskHide Once At Every Booting)
Click to expand...
Click to collapse
4- SELinuxMode Inverter (Advanced SELinux Mode Changer/Manager)
- Inverting The Default Android SELinuxMode During Startup ([From Permissive To Enforcing] Or [From Enforcing To Permissive])
- The Function Changes The SELinuxMode For The Entirety Of The Device's Uptime Until Next Reboot
- The Default Android SELinuxMode Can Be Either Enforcing Mode Or Permissive Mode Which Depends On The Installed/Flashed Rom/Kernel
- SELinux Enabled Kernel/SELinux Development Mode Is A Main Point To Use The Function (The Installed/Flashed Rom/Kernel Must Have The Ability To Switch Between Enforcing Mode & Permissive Mode)
- Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SELinuxModeInverter, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Rooting-Tool/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinuxMode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinuxMode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter/Wait/Active And Then Reboot The Device
=============================
The General Steps- SELinux Enabled Kernel/SELinux Development Mode Is Required Which Means The Installed/Flashed Rom/Kernel Has The Ability To Switch Between Enforcing Mode & Permissive Mode
- To Check The Above Mentioned Ability, Install Terminal Emulator From PlayStore --> Open It -->
-----> For Getting The Current Android SELinuxMode, Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter
-----> For Setting The Current Android SELinuxMode, Write su --> Click On Enter --> Write setenforce 0 (For Permissive Mode) Or setenforce 1 (For Enforcing Mode) --> Click On Enter
-----> Check Again The Current Android SELinuxMode
-----> If The Mentioned Steps Worked/Succeeded, Activate The Function Of SELinuxModeInverter
-----> Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
-----> If The Mentioned Steps Didn't Work/Succeed, It Means The Flashed Rom/Kernel Hasn't The Ability To Switch Between Enforcing Mode & Permissive Mode So Flash Another Rom/Kernel Which Supports The Ability Of Changing SELinux Mode
- P.S. Maybe The Flashed Rom/Kernel Hasn't The Ability To Switch Between Permissive Mode & Enforcing Mode During Startup So You Can Use Only The Wait Mode (Not The Fast Mode)
Click to expand...
Click to collapse
5- SafeMode Enabler
- Booting The Android Into SafeMode
- In-Case Of Facing A Bootloop Issue Due To Installing/Configuring An App, Use The Function To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The NormalMode)
- The Function Disables All Installed Apps (User Apps) & Also The Root Access By Enabling SafeMode & After Booting, Remove The Data/Uninstall Any App Which Caused The Bootloop/Issue (From Settings --> Apps --> The App --> Storage --> Clear Data/Uninstall) Then Reboot
- SafeMode Gives The Device The Ability To Not Open Any App Which Is Installed As A User App, And A "Safe Mode" Badge Will Appear In The Lower Left Corner Of The Screen
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of SafeModeEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SafeModeEnabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
6- MagiskCoreOnlyMode Enabler [For Magisk Users Only]
- Opening Magisk In CoreOnlyMode
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Use The Function To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules)
- The Function Disables All Magisk Modules By Enabling MagiskCoreOnlyMode & After Booting, You Can Disable MagiskCoreOnlyMode 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
- CoreOnlyMode 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 CoreOnlyMode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskCoreOnlyModeEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskCoreOnlyModeEnabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
7- Swap Controller (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- The Function Is Divided Into 2 Sub-Functions [SwapEnabler & SwapDisabler] For Improving Responsiveness/Performance
- SwapEnabler Re-Calculates Swap Space & Sets The New Size But SwapDisabler Sets Swap (Total) Size To Be 0 [It Can Be Checked Using DiskInfo From PlayStore]
- The Default Swappiness Value Is 35 For SwapEnabler & 0 For SwapDisabler
- The Function Disables Also KSM/UKSM For Reducing The Battery Drain & Lowering The CPU Usage
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SwapEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwapController/Enabler/Inactive And Then Reboot The Device
- For Activating The Functionality Of SwapDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwapController/Disabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
8- Swappiness Changer (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- There Are 3 Levels Of Swappiness Value [Low For 10, Mid For 30 & High For 60] For Improving Responsiveness/Performance [It Can Be Checked Using DiskInfo From PlayStore]
- The Function Disables Also KSM/UKSM For Reducing The Battery Drain & Lowering The CPU Usage
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Low Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/Low/Inactive And Then Reboot The Device
- For Activating The Functionality Of Mid Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/Mid/Inactive And Then Reboot The Device
- For Activating The Functionality Of High Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/High/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
9- MagiskDaemonHide Keeper (MagiskDaemon-MagiskHide Running Keeper) [For Magisk Users Only]
- The Function Is Divided Into 2 Sub-Functions [HideKeeper & DaemonKeeper] For Keeping Both Of MagiskDaemon & MagiskHide Running (Which Is Recommended To Be Used If Only Needed)
- HideKeeper Aims To Resolve The Issue Of Intermittent Work Of MagiskHide By Re-Enabling MagiskHide Every A Certain Time
- DaemonKeeper Aims To Resolve The Issue Of Losing Root Access Randomly (Or Magisk Is Not Installed) By Re-Starting MagiskDaemon Every A Certain Time
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of HideKeeper, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Hide/Inactive And Then Reboot The Device
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Enabling MagiskHide Every 36 Min. & The Fast Mode Can Be Used Re-Enabling MagiskHide Every 18 Min.]
-----> For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Hide/Wait/Active And Then Reboot The Device
- For Activating The Functionality Of DaemonKeeper, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Daemon/Inactive And Then Reboot The Device
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Starting MagiskDaemon Every 10 Min. & The Fast Mode Can Be Used Re-Starting MagiskDaemon Every 5 Min.]
-----> For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Daemon/Wait/Active And Then Reboot The Device
Click to expand...
Click to collapse
10- DT2WStatus Inverter (DoubleTap2Wake Enabler/Disabler)
- Inverting The Default DT2W Status During Startup ([From Disabled To Enabled] Or [From Enabled To Disabled])
- The Function Changes The DT2W Status For The Entirety Of The Device's Uptime Until Next Reboot
- The Default DT2W Status Can Be Either Enabled Or Disabled Which Depends On The Installed/Flashed Rom/Kernel
- The Installed/Flashed Rom/Kernel Must Support The Feature Of DT2W (DoubleTap2Wake)
- Activating The Function = Inverting The Default DT2W Status
- For Activating The Functionality Of DT2WStatusInverter, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/DT2WStatusInverter/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
11- MagiskDeviceSpoofingTool Enabler (Device Emulator For Device Certification & SafetyNet) [For Magisk Users Only]
- Fixing PlayStore Device Certification Status & Passing SafetyNet
- The Function Changes Some Properties Of Build.Prop For The Entirety Of The Device's Uptime Until Next Reboot
- The Function Changes The Device Fingerprint To Another Certified One (Currently Pixel 2 XL)
- MagiskHide Must Be Working Properly Which Is A Main Point To Pass SafetyNet
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of MagiskDeviceSpoofingToolEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDeviceSpoofingToolEnabler/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Blackscreen & The Fast Mode Can Be Used For Resolving The Issue Of Non-Persistent After Rebooting]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDeviceSpoofingToolEnabler/Wait/Active And Then Reboot The Device
- P.S. The Device's Fingerprint Can Be Checked Using Device Info HW From PlayStore - SafetyNet Can Be Checked Using Either Magisk Manager Itself Or SafetyNet Helper Sample From PlayStore - Root Detection Can Be Checked Using RootBeer Sample From PlayStore
- P.S. Maybe Activating Both Functions Of PlayStoreWithServicesDataCleaner & DalvikCacheCleaner Are Required
- P.S. The Most Famous Reasons Of Root Detection Are Magisk Itself, Installed Rom/Kernel, Loaded Prop, Installed App, File/Folder In The Internal/External Storage & External Connection Thru Internet
Click to expand...
Click to collapse
12- LowRamConfig Enabler (RAM Management)
- Enabling The Low Ram Configurations For Low Ram Device
- The Function Changes The Low Ram Configurations For The Entirety Of The Device's Uptime Until Next Reboot
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of LowRamConfigEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/LowRamConfigEnabler/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Rooting-Tool/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Blackscreen & The Fast Mode Can Be Used For Resolving The Issue Of Non-Persistent After Rebooting]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/LowRamConfigEnabler/Wait/Active And Then Reboot The Device
Click to expand...
Click to collapse
13- MagiskModules Disabler [For Magisk Users Only]
- Disabling The Other Magisk Modules
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Use The Function To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskModulesDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskModulesDisabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
14- MagiskGeneralScripts Disabler [For Magisk Users Only]
- Disabling All Magisk General Scripts Of /data/adb/service.d & /data/adb/post-fs-data.d
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module Or Placing A Script, Use The Function To Remove That Script Manually
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskGeneralScriptsDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskGeneralScriptsDisabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
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], Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/Status/Active And Then Reboot The Device
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Delete The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/Status/Active And Then Reboot The Device
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Re-Flash The Module
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
MultiFunctionsPlusPage 2 Of 2
Changelog:
v1.0.3.4.2.4B7: Improving The Code & Updating The Function Of [MagiskDeviceSpoofingTool Enabler] To Emulate "Pixel2XL"
v1.0.3.4.2.4B6: Fixing Minors, Improving The Code & Supporting All Magisk Versions From Magisk v8(800) To The Latest Version
v1.0.3.4.2.4B4: Fixing Minors, Improving The Code & Supporting All Magisk Versions From Magisk v13.1(1310) To The Latest Version
v1.0.3.4.2.4B0/2: Improving The Code & Updating To Magisk v20.x
v1.0.3.4.2.4/4A1: Fixing Minors & Improving The Code
v1.0.3.4.2.3L: Improving The Code
v1.0.3.4.2.3F: Improving The Code, Adding The Function Of [MagiskModules Disabler] For Disabling The Other Magisk Modules & The Function Of [MagiskGeneralScripts Disabler] For Disabling The Magisk General Scripts
v1.0.3.4.2.3A/B: Improving The Code, Adding The Function Of [MagiskDeviceSpoofingTool Enabler] For Passing The SafetyNet & The Function Of [LowRamConfig Enabler] For Enabling The Low Ram Configurations
v1.0.3.4.2.2: Initial Release
Click to expand...
Click to collapse
The Description: (2)
*** Re-Flashing The Module Of MultiFunctionsPlus With Keeping The Same Configurations:
- Re-Flash The Module Of MultiFunctionsPlus (Don't Reboot) & Move The Folder Of MultiFunctionsPlus From The Folder Of 4U [/data/DreamerMods/4U/MFP] To The Folder Of DreamerMods (/data/DreamerMods) Then Reboot
Click to expand...
Click to collapse
*** Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList): Activating Some Functions Of MultiFunctionsPlus For Once To Resolve Some Issues (P.S. MultiFunctionsPlus Is Required To Be Flashed Before Using Activator)
- Flash The Module Of MultiFunctionsPlus (Don't Reboot) & Flash The Module Of Activator (Reboot Now) For Activating Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler, MagiskCoreOnlyMode Enabler, MagiskModules Disabler & MagiskGeneralScripts Disabler] For Once To Resolve Some Issues
- Booting The Android Into SafeMode For Giving The Ability To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The NormalMode)
- Clearing DalvikCache For Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Clearing All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Disabling The Other Magisk Modules Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Disabling All Magisk General Scripts Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Opening Magisk In CoreOnlyMode To Deactivate All Modules For Giving The Ability To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules) [For Magisk Users Only]
- Flashing/Re-Flashing The Module Of Activator Will Activate The Above Mentioned Functions (Even-If Magisk Is In Core Only Mode For Magisk Users)
Click to expand...
Click to collapse
*** Execution Mode: The Execution Mode Of Script/Module
- There Are 2 Modes [Execution In Normal Mode & Execution In Background Mode]
- Execution In Normal Mode: Executing The Script/Module Based On The Priorities Of Rooting-Tool/Rom/Kernel Itself Is Maybe A Proper Mode For Some Cases
- Execution In Background Mode (The Default One): Resolving The Issue Of Blocking The Other Scripts/Modules From Starting Early Due To The Execution Time Of Code Is Long & Also Related To Rooting-Tool/Rom/Kernel Itself (Such Losing The Functionality Of Xposed After Installing The Module Or Activating Any Function)
- For Activating Execution In Normal Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/Status/Background/Active And Then Reboot The Device
- For Activating Mode Of Execution In Background Mode, Delete The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/Status/Background/Active And Then Reboot The Device
Click to expand...
Click to collapse
*** FAQ/Notes:
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules, Scripts Or HideList, Check Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList) In Above
- After Flashing The Module Of Activator, MagiskHideList Will Be Cleared And For Retrieving/Restoring The Last MagiskHideList, Check The Function Of MagiskHideList Cleaner In Above
- All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Above
- In Case Of Deleting The Folder Of Any Unwanted Function Such SELinuxModeInverter (/data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter) & Rebooting The Device, The Code Will Not Check The Unwanted Function Which Is Equivalent To The Permanent Deactivation/Removal Of The Unwanted Function So The Same Step Can Be Done With Any Unwanted Function (P.S. For Retrieving/Restoring The Unwanted Function, Deleting The Folder Of Status & Rebooting The Device Are Required)
- P.S. Deleting The Folder Of Status (/data/DreamerMods/MultiFunctionsPlus/Status) & Rebooting The Device Will Create The File Of Disable Again
- For Activating Any Function, Copying The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/<TheFunction>/Inactive (P.S. Negating The Negation Is A Form Of Affirmation) & Rebooting The Device Are Required
- Disable MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules)
- For Re-Flashing The Module Of MultiFunctionsPlus With Keeping The Same Configurations, Check The Details In Above
Click to expand...
Click to collapse
*** In-Case Of Failure: After Doing Successfully The Above Mentioned Steps
- During The Installation Process, Take The Screenshot After Flashing The Module & Send It
- Send These Logs (/data/MultiFunctionsPlus.log, /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlus.log, /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlusData.log & /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlusOld.log)
- Complete Info About The Device, The Used Rom, The Used Kernel & The Used Rooting-Tool
- Send The Folder Of DreamerMods (/data/DreamerMods)
- Send The Screenshots Of (Magisk Manager --> Main Screen, Magisk Manager --> Modules, Magisk Manager --> SuperUser & Magisk Manager --> Log --> SuperUser) [For Magisk Users Only]
- Send Magisk Log (Magisk Manager --> Log --> Magisk) [For Magisk Users Only]
- Send The Screenshot Of SuperUser Of The Used Rooting-Tool [For Non-Magisk Users]
- Send Full Logcat (Using Logcat Extreme From PlayStore)
Click to expand...
Click to collapse
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved For News/Updates #0
Reserved For News/Updates #1
Reserved For News/Updates #2
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
u81 said:
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Could I Ask You To Send The Screenshots Of The Following?
-Settings --> Apps --> Instagram --> Storage
-Settings --> Apps --> WhatsApp --> Storage
-Settings --> Apps --> Messenger --> Storage
-Settings --> Apps --> SoundCloud --> Storage
u81 said:
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Check This Post https://forum.xda-developers.com/ap...al-media-cache-advanced-t3799155/post76705484.
Don't have sound cloud
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YouTube attached as well
Sent from my SM-N910F using Tapatalk
YouTube screenshot
Sent from my SM-N910F using Tapatalk
I'm only updated to Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify a few hours ago so the current storage usage is possibly much smaller than normal. (Data not wiped)
It should be up to normal size by tomorrow, I'd say.
Sent from my SM-N910F using Tapatalk
u81 said:
I'm only updated to Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify a few hours ago so the current storage usage is possibly much smaller than normal. (Data not wiped)
It should be up to normal size by tomorrow, I'd say.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Kindly Send Also A Screenshot Of Your Internal Storage (Unhide Option Should Be Selected)
Is this what you're looking for?
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
u81 said:
Is this what you're looking for?View attachment 4517147
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
Click to expand...
Click to collapse
No, From Your File Browser.
Is this what you're looking for?
If not, please share your screenshot and I'll find how to get that screenshot from my phone
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
Deleted
Will these do?
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
I was thinking about one thing related to your modules. They're useful, but it'll be kinda messy sometime, since you're creating a lot of different modules, separately.
Since all of them have similar purposes (clear caches from something), how about you merge all of them into a single module, with an interactive terminal interface? I guess it'd be a great update, and not only easier to you to maintain and organize all of those modules, but easier to others to find them and use. Just a quick thought.
abacate123 said:
I was thinking about one thing related to your modules. They're useful, but it'll be kinda messy sometime, since you're creating a lot of different modules, separately.
Since all of them have similar purposes (clear caches from something), how about you merge all of them into a single module, with an interactive terminal interface? I guess it'd be a great update, and not only easier to you to maintain and organize all of those modules, but easier to others to find them and use. Just a quick thought.
Click to expand...
Click to collapse
Currently There Are 8 Modules [WiFi Connection State On Status Bar - App Shortcut & Widget In Notification Area - SELinux Mode Inverter (Advanced SELinux Mode Changer) - Microsoft Intune Company Portal Hider - Tez Hider - Clear Dalvik Cache (Advanced Dalvik/ART Cache Cleaner) - Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner) - Clear Social Media Cache (Advanced Social Media Apps Cache Cleaner)] So What Do You Think?
Dreamer(3MF) said:
Currently There Are 8 Modules [WiFi Connection State On Status Bar - App Shortcut & Widget In Notification Area - SELinux Mode Inverter (Advanced SELinux Mode Changer) - Microsoft Intune Company Portal Hider - Tez Hider - Clear Dalvik Cache (Advanced Dalvik/ART Cache Cleaner) - Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner) - Clear Social Media Cache (Advanced Social Media Apps Cache Cleaner)] So What Do You Think?
Click to expand...
Click to collapse
Nice, but I was talking specifically about these cache related modules, not the others, I forgot to mention that. Merging them into a single module seems to be a nice idea. But well, just a thought as I said.
[MODULE] Device Spoofing Tool (Device Emulator For Device Certification & SafetyNet)
It Is Now A Part Of The Main Module Of MultiFunctionsPlus & Its Thread https://forum.xda-developers.com/apps/magisk/module-social-media-cache-advanced-t3799155.
Click to expand...
Click to collapse
Introduction:
Simple Module To Convert UnOfficial Version To Official One, Fix Uncertified Status In PlayStore & Pass The SafetyNet.
- This Module Changes Some Properties Of Build.Prop For The Entirety Of The Device's Uptime Until Next Reboot
- This Module Emulates That Your Device Is Another Certified One
- This Module Doesn't Change The Values Permanently So That You Can Disable It From Magisk Manager Then Reboot For Returning To The Default Values
Current Version: 1.0.1.1AL
- Magisk Hide Must Be Working Properly Which Is A Main Point To Use The Module So Check The General Steps
- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Versions Of The Module [Where v1.0.1.1ALP/v1.0.1.1ALS Can Be Used To Resolve The Issue Of Not Persistent After Rebooting - v1.0.1.1AL/v1.0.1.1ALS Can Be Used For Resolving The Issue Of Blackscreen - v1.0.1.1AL/v1.0.1.1ALS Can Be Used For Resolving The Issue Of Preventing Some Other Modules From Loading/Working - v1.0.1.1ALP/v1.0.1.1ALS Can Be Downloaded From The Same Download Link Inside The Folder Of Special]
- It Should Work With Any Device/Rom
Created: June.27.2018
Updated: Dec.03.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
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru TWRP Recovery
Recommendation:
- Check The General Steps From This Post https://forum.xda-developers.com/ap...ll-modules-magisk-v13-3-t3800435/post77044632
- In-Case Of Failure, Check This Post https://forum.xda-developers.com/ap...ll-modules-magisk-v13-3-t3800435/post77078832
- For More Info About Passing The SafetyNet & Certifying The Device, Check This Post https://forum.xda-developers.com/ap...playstore-services-data-t3789498/post76682978
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
I Am Asking Our Mates To Check The Stable Version And Share The Feedbacks/Ideas/Questions To Enhance/Modify The Module.
Does this work even with xposed installed?
lambstone said:
Does this work even with xposed installed?
Click to expand...
Click to collapse
Kindly Be Informed That
- One Of The Main Points To Pass The SafetyNet Is Disabling/Uninstalling BusyBox/Xposed So That The Most Thing You Can Do Is Disabling BusyBox/Xposed To Pass The SafetyNet
- This Module Emulates That Your Device Is Another Certified One
Dreamer(3MF) said:
One Of The Main Points To Pass The SafetyNet Is Disabling/Uninstalling BusyBox/Xposed. This Module Emulates That Your Device Is Another Certified One.
Click to expand...
Click to collapse
So it is like default Magisk with Magisk Hide on + module MagiskHide Props Config (to set fingerprint)? Or does your module adds something on top of that?
Your module does not help with busybox/xposed as I could understand from you. Am I wrong?
wilsonhlacerda said:
So it is like default Magisk with Magisk Hide on + module MagiskHide Props Config (to set fingerprint)? Or does your module adds something on top of that?
Your module does not help with busybox/xposed as I could understand from you. Am I wrong?
Click to expand...
Click to collapse
Kindly Be Informed That
- This Module Changes Some Properties Of Build.Prop For The Entirety Of The Device's Uptime Until Next Reboot
- This Module Doesn't Change The Values Permanently So That You Can Disable It From Magisk Manager Then Reboot For Returning To The Default Values
- Currently There Is No Solution To Hide BusyBox/Xposed From The SafetyNet But The Most Thing You Can Do Is Disabling BusyBox/Xposed To Pass The SafetyNet
It works on Huawei P20 pro running on EMUI 8.1. Thanks for this module.
Before this module: Google Play / Settings it shows uncertified
After this module: Google Play / Settings it shows certified
Well done and thanks.
The General Steps:
- Disable WiFi & Data
- Uninstall Any Other Rooting Tool Completely Such As SuperSu & Lineage-AddOnSU Which Is Used With Magisk
- Uninstall The Following Modules MagiskHide Props Config, Universal SafetyNet Fix, Safety Patch, PetNoires SafetySpoofer, SaMoDX SafetySkipper & Play Store Visa From Magisk Manager (Magisk Manager --> Modules --> Tap On The Bin Icon For Each Mentioned Module) Then Reboot
- Download DeviceSpoofingTool4Magisk From This Link https://androidfilehost.com/?w=files&flid=276428 Then Flash It Thru Magisk Manager Then Reboot
- 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
- 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 5 Min. Then Enable WiFi/Data
- Wait About 15-30 Min. Then Check PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification) & This Time Should Be Certified
- Check The SafetyNet (Enable WiFi --> Magisk Manager --> Tap To Start SafetyNet Check Or Download SafetyNet Helper Sample From PlayStore)
- If It Didn't Work, Disable Magisk Hide Then Enable Magisk Hide From The Section Of Settings In Magisk Manager & Reboot
- Check Again The SafetyNet & If It Didn't Work, Disable/Uninstall BusyBox/Xposed Then Reboot
- Check Again The SafetyNet & This Time Should Be Passed
- In-Case Of Failure, Check This Post https://forum.xda-developers.com/ap...ll-modules-magisk-v13-3-t3800435/post77078832
Not working yet. Tell me what to do next.
Seagold said:
Not working yet. Tell me what to do next.
Click to expand...
Click to collapse
Kindly Do The Following
- Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
- Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Install SafetyNet Helper Sample From PlayStore & Send Its Screenshot
- Enable WiFi --> Magisk Manager --> Tap To Start SafetyNet Check --> Send Its Screenshot
- Magisk Manager --> Modules --> Send Its Screenshots
- Magisk Manager --> SuperUser --> Send Its Screenshots
- From Settings --> About Phone --> SELinux Status --> Send Its Screenshot
- Did You Do All Steps Of This Post https://forum.xda-developers.com/ap...l-modules-magisk-v13-3-t3800435/post77044632?
What's the advantages and disadvantages of certified and uncertified devices
Seagold said:
What's the advantages and disadvantages of certified and uncertified devices
Click to expand...
Click to collapse
For More Information About
- Device Certification, Check This Link https://www.guidingtech.com/71735/google-certified-android-devices/
- SafetyNet, Check This Link https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/
Updated DeviceSpoofingTool4Magisk To v1.0.1!
Changelog: Changing More Properties & Adding Some Apps-Services To Magisk Hide List
I Am Asking Our Mates To Check The Stable&Beta Versions And Share The Feedbacks/Ideas/Questions To Enhance/Modify The Module.
Works perfectly. Thank you! :good:
Kindly Be Informed That
- 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 v16.6(1662)
Seagold said:
What's the advantages and disadvantages of certified and uncertified devices
Click to expand...
Click to collapse
Give A Try To The New Update Of DeviceSpoofingTool4Magisk.
This module did what it should https://s.kaskus.id/images/2018/07/15/9649273_201807151224260192.png
But still cant access my mobile banking https://s.kaskus.id/images/2018/07/15/9649273_201807151225550122.png
Rootbeer with rootbeer unhide from magisk https://s.kaskus.id/images/2018/07/15/9649273_201807151226420018.png
Rootbeer hide from magisk https://s.kaskus.id/images/2018/07/15/9649273_201807151227280060.png
Thanks..it works for me.
On Android 8.0 Oreo, after enable modue XInternalSD, all the apps like Power Toggles which can control airplane mode and GPS through root all stop working.
As we know, after Android 4.2, apps only can control airplane mode through root by
Code:
su (get root permission)
settings put global airplane_mode_on 1 (Turn off Airplane mode is 0)
am broadcast -a android.intent.action.AIRPLANE_MODE --ez state false
As the same way, when XInternalSD actived, I try to active airplane mode manually by above command also failed. if XInternalSD doesn't actived, it woks well.
And this bug can easily reappear on Android Emulator(SDK 26 x86 image), I tested. And it happened on my phone (LG V20 US996). So I think it happened in all Android Oreo (xposed v90 beta3).
So that means, I can't use XInternalSD and some apps like Power Toggles to control airplane mode and GPS at the same time. And I also no idea why it cause that.
(emmmm, I guess, it seems XInternalSD cause broadcast unable sending or settings vaule unable to write)
And I also check the source code of XInternalSD and I no idea too... Just some hook of storage.
And.... Even I disabled all the features in XInternalSD (uncheck Custom path tointernal SD; uncheck full access to external sd; uncheck Enable for apps..etc; ), just make the module actived, the problem also be caused.
And...This module work fine in Android 7.1 and before. No those problem.
Anybody can help me deal with it?
Finally I found a module called XCoolDroid and it works well on Android Oreo with no that problem.
[MODULE] MultiFunctions (+Bootloop/Blackscreen Resolver For Apps, Modules & HideList)
Check The Module Of MultiFunctionsPlus From This Thread https://forum.xda-developers.com/apps/magisk/module-social-media-cache-advanced-t3799155:
- MultiFunctionsPlus Is The Successor Of MultiFunctions
- The Main Difference: The Pre-Activated Functions = Flashing MultiFunctions Only = Flashing MultiFunctionsPlus + Activator Or Deactivating The Pre-Activated Functions = Flashing MultiFunctions + Deactivator = Flashing MultiFunctionsPlus Only
Click to expand...
Click to collapse
MultiFunctions
Introduction:
A Module To Do The Next Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value, Keeping MagiskDaemon-MagiskHide Running & Changing DoubleTap2Wake(DT2W) Status].
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules Or HideList, Check The Pre-Activated Functions (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList) In Below
- P.S. All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Below
- P.S. All Functions Can Be Used With Any-Rooting-Tool Except The Ones For Magisk Users Only As Described In Below
Current Version: MultiFunctions v1.0.3.4.1.6A9 - Deactivator v1.0.0.1
- For Magisk Users Only, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function (Disabling Magisk Core Only Mode & Rebooting The Device Are Required To Load The Modules)
- For Activating Any Function, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Function --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
Changelog:
v1.0.3.4.1.6A8/9: Improving The Code & Executing The Code In The Background To Overcome The Issue Of Blocking The Other Scripts From Starting Early Due To The Execution Time Of Code Is Too Long Which Is Also Related To Rooting-Tool/Rom/Kernel Itself
v1.0.3.4.1.6A6: Taking A Copy Of The Current Config [/data/DreamerMods/MultiFunctions] To [/data/DreamerMods/4U] During The Upgrading Process
v1.0.3.4.1.6: Fixing Minors, Adding [Vnswap & Zswap] To The Function Of [Swap Controller], Adding [UKSM & KSM] To The Functions Of [Swap Controller & Swappiness Changer] & Supporting More Devices For The Function Of [DT2WStatus Inverter]
v1.0.3.4.1.5: Fixing Minors
v1.0.3.4.1.4B8: Fixing Minors & Adding Function [DT2WStatus Inverter] For Changing DoubleTap2Wake(DT2W) Status
v1.0.3.4.1.4B6: Fixing Minors & Adding Sub-Function [Hide Enabler] To The Function Of [MagiskHideList Cleaner] For Enabling MagiskHide Once At Booting
v1.0.3.4.1.4: Fixing Minors & Adding One More Function [MagiskDaemonHide Keeper]
v1.0.3.4.1.3: Adding A Backup Feature To The Function Of MagiskHideList Cleaner
v1.0.3.4.1.2: Adding More Functions [Swap Controller & Swappiness Changer]
v1.0.3.3: Adding More Functions [DalvikCache Cleaner, PlayStoreWithServicesData Cleaner, MagiskHideList Cleaner, SELinuxMode Inverter, SafeMode Enabler & MagiskCoreOnlyMode Enabler]
v1.0.3.0: Initial Release
Created: May.09.2019
Updated: Nov.17.2019
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The Description)
** Magisk Installer: It Supports Magisk Only
- 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 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 v20.1(20100)
- For The Module Which Is Ended Its Name With v19000P, It Supports Magisk v19.0(19000) To The Latest Version
** Unity Installer: It Supports Any-Rooting-Tool Such SuperSU, Lineage-AddOnSU & Magisk
- P.S. If You Flash The Same Version Of Module Twice, The Module Will Remove Itself But If The Version Of Second Time Is Higher Than The Version Of First Time, The Module Will Update/Upgrade Itself
- But For The Module Which Is Ended Its Name With Unity1.5.x, It Supports Magisk v15.3(1530) To The Latest Version
- But For The Module Which Is Ended Its Name With Unity4.x, It Supports Magisk v18.0(18000) To The Latest Version
- But For The Module Which Is Ended Its Name With Unity5.x, It Supports Magisk v19.0(19000) To The Latest Version
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru A Custom-Recovery Such TWRP Recovery --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload TheFileNameOfModule.zip --> Reboot (P.S. Renaming The File To Have A Short One Is Recommended Such mfm.zip Before Using ADB Sideload)
- Or Using A Flash-Tool (Flasher) Such EX Kernel Manager, FK Kernel Manager, FlashFire Or Flashify --> Flash ZIP File --> Reboot
The Description:
1- DalvikCache Cleaner (Advanced Dalvik/ART Cache Cleaner)
- Clearing The Dalvik Cache
- Doing The Same Functionality Of Wiping Dalvik/ART Cache Thru TWRP Recovery
- Resolving/Fixing Some Issues With The Installed Apps
- Removing All Remnants Of The Uninstalled Apps
- Maybe It Takes About 5 Min. To Finish The Process
- After Doing Its Functionality, Check The Free Space Of Internal Storage Which Should Be Increased/Maximized A Little Bit
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of DalvikCacheCleaner, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> DalvikCacheCleaner --> Delete The File Of Disable From The Folder Of Active --> Reboot
Click to expand...
Click to collapse
2- PlayStoreWithServicesData Cleaner (Advanced PS-GMS Data Cleaner)
- Clearing The Data Of Google Play Store & Google Play Services
- One Of The Methods To Resolve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- 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
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of PlayStoreWithServicesDataCleaner, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> PlayStoreWithServicesDataCleaner --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
3- MagiskHideList Cleaner (Including MagiskHide Enabler & MagiskHideList Backup) [For Magisk Users Only]
- Clearing MagiskHideList [All Added Apps/Activities/Processes In MagiskHideList]
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To MagiskHide, Flash This Module
- Activating The Function = Doing Its Functionality, Taking A Backup Of HideList & Disabling Itself
- For Activating The Functionality Of MagiskHideListCleaner, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideListCleaner --> Delete The File Of Disable From The Folder Of Active --> Reboot
- Additional Feature (Deactivating The Main Function + Putting A Copy Of The File Of HideList.txt Into The Folder Of Retrieving [Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideListCleaner --> BackUp --> Copy The File Of HideList.txt To The Folder Of Retrieving --> Reboot] = Retrieving/Restoring The Last MagiskHideList Before Activating The Function)
- Additional Feature (Deactivating The Main Function + Activating The Sub-Function Of BackUp [Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideListCleaner --> BackUp --> Delete The File Of Disable From The Folder Of Active --> Reboot] = Taking A Backup Of HideList)
- Additional Feature (Activating The Sub-Function Of Hide Enabler [Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskHideListCleaner --> Hide --> Enabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot] = Enabling MagiskHide Once At Booting)
Click to expand...
Click to collapse
4- SELinuxMode Inverter (Advanced SELinux Mode Changer)
- Inverting The Default Android SELinux Mode During Startup ([From Permissive To Enforcing] Or [From Enforcing To Permissive])
- This Function Changes The SELinux Mode For The Entirety Of The Device's Uptime Until Next Reboot
- The Default Android SELinux Mode Can Be Either Enforcing Mode Or Permissive Mode Which Depends On The Installed/Flashed Rom/Kernel
- SELinux Enabled Kernel/SELinux Development Mode Is A Main Point To Use The Function (The Installed/Flashed Rom/Kernel Must Have The Ability To Switch Between Enforcing Mode & Permissive Mode)
- Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SELinuxModeInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]
- For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Wait --> Reboot
- For Activating The Wait Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Delete The File Of Disable From The Folder Of Wait --> Reboot
=============================
The General Steps- SELinux Enabled Kernel/SELinux Development Mode Is Required Which Means The Installed/Flashed Rom/Kernel Has The Ability To Switch Between Enforcing Mode & Permissive Mode
- To Check The Above Mentioned Ability, Install Terminal Emulator From PlayStore --> Open It -->
-----> For Getting The Current Android SELinux Mode, Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter
-----> For Setting The Current Android SELinux Mode, Write su --> Click On Enter --> Write setenforce 0 (For Permissive Mode) Or setenforce 1 (For Enforcing Mode) --> Click On Enter
-----> Check Again The Current Android SELinux Mode
-----> If The Mentioned Steps Worked/Succeeded, Activate The Function Of SELinuxModeInverter
-----> Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
-----> For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager
-----> For Activating The Functionality Of SELinuxModeInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode At Booting]
-----> For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Wait --> Reboot
-----> For Activating The Wait Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Delete The File Of Disable From The Folder Of Wait --> Reboot
-----> If The Mentioned Steps Didn't Work/Succeed, It Means The Flashed Rom/Kernel Hasn't The Ability To Switch Between Enforcing Mode & Permissive Mode So Flash Another Rom/Kernel Which Supports The Ability Of Changing SELinux Mode
- P.S. Maybe The Flashed Rom/Kernel Hasn't The Ability To Switch Between Permissive Mode & Enforcing Mode During Startup So You Can Use Only The Wait Mode (Not The Fast Mode)
- For Magisk Users, If You Want To Get Accurate Feedback From getenforce/sestatus, Disable Magisk Hide (Magisk Manager --> Settings --> Disable Magisk Hide) And After Finishing, Enable Magisk Hide Again [P.S. Magisk Hide Will Hide That Your Device Is In Permissive Mode To Pass The SafetyNet]
Click to expand...
Click to collapse
5- SafeMode Enabler
- Booting The Android Into Safe Mode
- In-Case Of Facing A Bootloop Issue Due To Installing/Configuring An App, Flash This Module
- The Function Disables All Installed Apps (User Apps) & Also The Root Access By Enabling Safe Mode & After Booting, Uninstall Any App Which Caused The Bootloop/Issue (From Settings --> Apps --> The App --> Storage --> Clear Cache --> Clear Data --> Uninstall) Then Reboot (Rebooting The Android Is Required To Get Back To The Normal Mode)
- Safe Mode Gives The Device The Ability To Not Open Any App Which Is Installed As A User App, And A "Safe Mode" Badge Will Appear In The Lower Left Corner Of The Screen
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of SafeModeEnabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SafeModeEnabler --> Delete The File Of Disable From The Folder Of Active --> Reboot
Click to expand...
Click to collapse
6- MagiskCoreOnlyMode Enabler [For Magisk Users Only]
- Opening Magisk In Core Only Mode
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Flash This Module
- The Function 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
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskCoreOnlyModeEnabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskCoreOnlyModeEnabler --> Delete The File Of Disable From The Folder Of Active --> Reboot
Click to expand...
Click to collapse
7- Swap Controller (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- The Function Is Divided Into 2 Sub-Functions [Enabler & Disabler] For Improving Responsiveness/Performance
- Swap Enabler Re-Calculates Swap Space & Sets The New Size But Swap Disabler Sets Swap (Total) Size To Be 0 [It Can Be Checked Using DiskInfo From PlayStore]
- The Default Swappiness Value Is 35 For Swap Enabler & 0 For Swap Disabler
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SwapEnabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwapController --> Enabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of SwapDisabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwapController --> Disabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
8- Swappiness Changer (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- There Are 3 Levels Of Swappiness Value [Low For 10, Mid For 30 & High For 60] For Improving Responsiveness/Performance [It Can Be Checked Using DiskInfo From PlayStore]
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Low Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> Low --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of Mid Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> Mid --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of High Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> High --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
9- MagiskDaemonHide Keeper (MagiskDaemon-MagiskHide Running Keeper) [For Magisk Users Only]
- The Function Is Divided Into 2 Sub-Functions [Hide & Daemon] For Keeping Both Of Magisk-Daemon & Magisk-Hide Running
- Hide Keeper Aims To Resolve The Issue Of Intermittent Work Of MagiskHide By Re-Enabling MagiskHide Every A Certain Time
- Daemon Keeper Aims To Resolve The Issue Of Losing Root Access Randomly (Or Magisk Is Not Installed) By Re-Starting MagiskDaemon Every A Certain Time
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Hide Keeper, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskDaemonHideKeeper --> Hide --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Enabling MagiskHide Every 20 Min. & The Fast Mode Can Be Used Re-Enabling MagiskHide Every 10 Min.]
-----> For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskDaemonHideKeeper --> Hide --> Copy The File Of Disable To The Folder Of Wait --> Reboot
- For Activating The Functionality Of Daemon Keeper, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskDaemonHideKeeper --> Daemon --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Starting MagiskDaemon Every 5 Min. & The Fast Mode Can Be Used Re-Starting MagiskDaemon Every 2 Min.]
-----> For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> MagiskDaemonHideKeeper --> Daemon --> Copy The File Of Disable To The Folder Of Wait --> Reboot
Click to expand...
Click to collapse
10- DT2WStatus Inverter (DoubleTap2Wake Enabler/Disabler)
- Inverting The Default DT2W Status During Startup ([From Disabled To Enabled] Or [From Enabled To Disabled])
- This Function Changes The DT2W Status For The Entirety Of The Device's Uptime Until Next Reboot
- The Default DT2W Status Can Be Either Enabled Or Disabled Which Depends On The Installed/Flashed Rom/Kernel
- The Installed/Flashed Rom/Kernel Must Support The Feature Of DT2W (DoubleTap2Wake)
- Activating The Function = Inverting The Default DT2W Status
- For Activating The Functionality Of DT2WStatusInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> DT2WStatusInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
*** Re-Flashing The Module Of MultiFunctions With Keeping The Same Configurations:
- Re-Flash The Module Of MultiFunctions (Don't Reboot) & Move The Folder Of MultiFunctions From The Folder Of 4U [/data/DreamerMods/4U] To The Folder Of DreamerMods (/data/DreamerMods) Then Reboot
Click to expand...
Click to collapse
*** The Pre-Activated Functions (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList): Activating Some Functions For Once To Resolve Some Issues
- Flash The Module Of MultiFunctions (Reboot Now) For Activating Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler & MagiskCoreOnlyMode Enabler] For Once To Resolve Some Issues
- Booting The Android Into Safe Mode For Giving The Ability To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The Normal Mode)
- Clearing DalvikCache For Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Clearing All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Opening Magisk In Core Only Mode To Deactivate All Modules For Giving The Ability To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling Magisk Core Only Mode & Rebooting The Device Are Required To Load The Modules) [For Magisk Users Only]
- Flashing/Re-Flashing The Module Of MultiFunctions Will Activate The Above Mentioned Functions (Even-If Magisk Is In Core Only Mode For Magisk Users)
=============================
*** P.S. IF You Want To Flash The Module Of MultiFunctions With Dectivating The Pre-Activated Functions, Do The Next Steps ***- Flash The Module Of MultiFunctions (Don't Reboot) & Flash The Module Of Deactivator (Reboot Now)
Click to expand...
Click to collapse
*** FAQ/Notes:
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules Or HideList, Check The Pre-Activated Functions (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList) In Above
- After Flashing The Module Of MultiFunctions, MagiskHideList Will Be Cleared And For Retrieving/Restoring The Last MagiskHideList, Check The Function Of MagiskHideList Cleaner In Above
- For Flashing The Module Of MultiFunctions With Deactivating The Pre-Activated Functions, Check The Pre-Activated Functions In Above
- All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Above
- In Case Of Deleting The Folder Of Any Unwanted Function Such SELinuxModeInverter (/data/DreamerMods/MultiFunctions/SELinuxModeInverter) & Rebooting The Device, The Code Will Not Check This Part/Function Which Is Equivalent To The Permanent Deactivation/Removal Of This Part/Function So The Same Step Can Be Done With Any Unwanted Function (P.S. For Retrieving/Restoring This Part/Function, Deleting The Folder Of Status & Rebooting The Device Are Required)
- For Activating Any Function, Deleting The File Of Disable From The Folder Of Active (Or Copying The File Of Disable To The Folder Of Inactive) From /data/DreamerMods/MultiFunctions/TheFunction (P.S. Negating The Negation Is A Form Of Affirmation) & Rebooting The Device Are Required
- Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function (Disabling Magisk Core Only Mode & Rebooting The Device Are Required To Load The Modules)
- For Re-Flashing The Module Of MultiFunctions With Keeping The Same Configurations, Check The Details In Above
- The Current Version Of MultiFunctions4Magisk Resolved The Issue Of Blocking The Other Scripts From Starting Early Due To The Execution Time Of Code Is Too Long Which Is Also Related To Rooting-Tool/Rom/Kernel Itself (Such Losing The Functionality Of Xposed After Installing The Module Or Activating Any Function)
Click to expand...
Click to collapse
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 --> Copy The File Of Disable To The Folder Of Status --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> Delete The File Of Disable From The Folder Of Status --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Re-Flash The Module
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved For News/Updates #1
Reserved For News/Updates #2
Updated MultiFunctions4Magisk To 1.0.3.4.1.2!
Changelog: Adding More Functions [Swap Controller & Swappiness Changer]
- 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
Very handy module! Thanks for this
Just saved me from a bootloop with a bad app
This is a life saver! Thank you!
Install core module only
Hello, I have used coreonly module v1.0.0A(1800) successfully on pie on a galaxy A8 2018, please can you explain how to only install core only module from the multi function version.
Is there a way to only flash what you need as I tried the multi function zip but then had to setup magic hide list etc as the zip wiped the settings.
Thank you
Phil
Very nice module.:good:
philcoo2 said:
Hello, I have used coreonly module v1.0.0A(1800) successfully on pie on a galaxy A8 2018, please can you explain how to only install core only module from the multi function version.
Is there a way to only flash what you need as I tried the multi function zip but then had to setup magic hide list etc as the zip wiped the settings.
Thank you
Phil
Click to expand...
Click to collapse
Using The Latest Version Which Is Currently 1.0.3.4.1.3, Copying The File Of HideList.txt To The Folder Of Retrieving & Rebooting The Device For Getting Back The Last Magisk Hide List Before Activating The Function Of MagiskHideList Cleaner (/data/DreamerMods/MultiFunctions/MagiskHideListCleaner/BackUp).
=============================
Updated MultiFunctions4Magisk To 1.0.3.4.1.3!
Changelog: Adding A Backup Feature To The Function Of MagiskHideList Cleaner
- 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
This module is garbage.
This is the most worthless piece of ****!
Polmk099 said:
This module is garbage.
This is the most worthless piece of ****!
Click to expand...
Click to collapse
Don't use it then. You can always give constructive feedback rather than being and complete idiot.
For Activating The Functionality Of DalvikCacheCleaner, Use Any Root File Explorer Such MiXplorer...
I need create folders in data?
mkdante381 said:
For Activating The Functionality Of DalvikCacheCleaner, Use Any Root File Explorer Such MiXplorer...
I need create folders in data?
Click to expand...
Click to collapse
No, You Don't Need To Do That But You Need To Access The Mentioned Path & Do What Are Mentioned Using Any Root File Explorer To Enable Its Functionality.
=============================
Updated MultiFunctions4Magisk To 1.0.3.4.1.4!
Changelog: Fixing Minors & Adding One More Function [MagiskDaemonHide Keeper]
- 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
Dreamer(3MF) said:
No, You Don't Need To Do That But You Need To Access The Mentioned Path & Do What Are Mentioned Using Any Root File Explorer To Enable Its Functionality.
=============================
Updated MultiFunctions4Magisk To 1.0.3.4.1.4!
Changelog: Fixing Minors & Adding One More Function [MagiskDaemonHide Keeper]
- 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
Click to expand...
Click to collapse
I don't have this folders, after installing this module. How activate 1 option, example clear dalvik cache?
mkdante381 said:
I don't have this folders, after installing this module. How activate 1 option, example clear dalvik cache?
Click to expand...
Click to collapse
Kindly Send The Reply For The Following
- Did You Download The Proper Version For The Used Rooting-Tool?
- Did You Reboot The Device After Flashing The Module?
- Are You A Magisk User? And If So, Send The Screenshot Of The Main Screen Of Magisk Manager, The Screenshot Of The Flashed Modules (Magisk Manager --> Modules), The Screenshot Of SuperUser Of Magisk (Magisk Manager --> SuperUser) & Magisk Log (Magisk Manager --> Log --> Magisk)
- Which File Explorer Do You Use? And Did You Grant Root Access To It?
I have Magisk 19.3. Your instructions are incomplete. I don't have this folders, after installing this magisk module. Pls for instruction step by step.
Old your module are super simple. You install clearcachedalvikcache and after restart module clear cache and dalvik.
Where download your old modules?
Edit:
Ok after installing all folders are in data folder. All is OK.
In My opinion better installer is in Unity, but with choosing function. Example put 1 to clear dalvik and data cache, put 2...
[BUG] Cannot Remove Module
This module did not disable swap on my OnePlus 7 Pro. Therefore, I tried to remove it from Magisk, and it keep showing up under Modules. I can disable it, but cannot remove it. It just keeps saying "Module will be removed at next reboot." The /data/DreamMods directory is still there.
I have Magisk 19.3 / 7.3.0, and used MultiFunction v1.0.3.4.1.4(v19000). I tried reinstalling, and deleting again, but no good - it's still there.
I found that the module's uninstall.sh script has no functionality in it - just comment lines from the Magisk template.
Also, I noted that after installing, it boots to Safe mode with continual 'Phone is starting' message. Have to force power down. (Very bad.) Then on powering up the phone, it reboots. (Probably a crash.) The third time, it finally comes up.
Any clue how to get rid of it completely?
jdhedden said:
Any clue how to get rid of it completely?
Click to expand...
Click to collapse
I removed the /data/DreamerMods and /data/adb/modules/Multifunction dirs, and that seemed to do it. However, I can't be sure it didn't leave anything behind elsewhere. <sigh>
Bad programmer. No cookie.
jdhedden said:
This module did not disable swap on my OnePlus 7 Pro.
Therefore, I tried to remove it from Magisk, and it keep showing up under Modules. I can disable it, but cannot remove it. It just keeps saying "Module will be removed at next reboot." The /data/DreamMods directory is still there.
I have Magisk 19.3 / 7.3.0, and used MultiFunction v1.0.3.4.1.4(v19000). I tried reinstalling, and deleting again, but no good - it's still there.
I found that the module's uninstall.sh script has no functionality in it - just comment lines from the Magisk template.
Also, I noted that after installing, it boots to Safe mode with continual 'Phone is starting' message. Have to force power down. (Very bad.) Then on powering up the phone, it reboots. (Probably a crash.) The third time, it finally comes up.
Any clue how to get rid of it completely?
Click to expand...
Click to collapse
jdhedden said:
I removed the /data/DreamerMods and /data/adb/modules/Multifunction dirs, and that seemed to do it. However, I can't be sure it didn't leave anything behind elsewhere. <sigh>
Bad programmer. No cookie.
Click to expand...
Click to collapse
Check The Following Quotes:
Introduction:
A Module To Do The Following Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value & Keeping MagiskDaemon-MagiskHide Running].
- After The Installation [Flashing/Re-Flashing] & 1st Reboot, Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler & MagiskCoreOnlyMode Enabler] Are Activated To Resolve Some Problems & Disabling Themselves After Doing Their Functionalities
Click to expand...
Click to collapse
*** Activated Functions After Flashing/Re-Flashing The Module Do The Next Procedures/Steps
- After The Installation [Flashing/Re-Flashing] & 1st Reboot, Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler & MagiskCoreOnlyMode Enabler] Are Activated To Resolve Some Problems & Disabling Themselves After Doing Their Functionalities
- Booting The Android Into Safe Mode For Removing Any App/Its Data Which Maybe Caused The Bootloop/Issue [Rebooting The Device Manually Is Required After That]
- Clearing DalvikCache
- Clearing All Added Apps/Activities/Processes In Magisk Hide List Which Maybe Caused The Bootloop/Issue [For Magisk Users]
- Opening Magisk In Core Only Mode To Deactivate All Modules For Removing Any Module Which Maybe Caused The Bootloop/Issue [For Magisk Users]
- Flashing/Re-Flashing The Module Will Activate The Above Mentioned Functions Even-If Magisk Is In Core Only Mode [For Magisk Users]
Click to expand...
Click to collapse
Current Version: 1.0.3.4.1.4
- 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 Any Function
- For Activating Any Function, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Function --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
Click to expand...
Click to collapse
7- Swap Controller
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- The Function Are Divided Into 2 Sub-Functions [Enabler & Disabler] For Improving Responsiveness/Performance
- Swap Enabler Re-Calculates Swap Space & Sets The New Size But Swap Disabler Sets Swap (Total) Size To Be 0 [It Can Be Checked Using DiskInfo From PlayStore]
- The Default Swappiness Value Is 35 For Swap Enabler & 0 For Swap Disabler
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SwapEnabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwapController --> Enabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of SwapDisabler, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwapController --> Disabler --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
8- Swappiness Changer
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- There Are 3 Levels Of Swappiness Value [Low For 10, Mid For 30 & High For 60] For Improving Responsiveness/Performance [It Can Be Checked Using DiskInfo From PlayStore]
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Low Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> Low --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of Mid Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> Mid --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- For Activating The Functionality Of High Swappiness, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SwappinessChanger --> High --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Click to expand...
Click to collapse
Man just give us the seperate modules