It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Clear The Data Of Google Play Store & Google Play Services.
- One Of The Methods To Solve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- After The Installation & 1st Reboot, It Clears The Data Of PS-GMS & Disables Itself
- After Doing Its Functionality, Check PlayStore Device Certification Status (Google PlayStore --> Settings --> Play Protect/Device Certification) Which Should Be Hidden For A While During Getting Its Status From Google
- Enabling The Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- The Module Is Just A Step To Solve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status Which Means Maybe You Need To Do Additional Steps To Solve The Issue
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of ClearPlayStoreWithServicesData
- For Activating The Functionality Of ClearPlayStoreWithServicesData, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> PlayStoreWithServicesData --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Created: May.13.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru TWRP Recovery
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
- Or Using A Flash-Tool (Flasher) Such FlashFire, Flashify Or Rashr --> Flash ZIP File (Flash A Flashable ZIP File) --> Choose The Downloaded File --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Clear Dalvik Cache - Core Only Mode - Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved for News/Updates #1
I'm confused about this.... Is it the same as clicking clear date in app settings?
yung40oz84 said:
I'm confused about this.... Is it the same as clicking clear date in app settings?
Click to expand...
Click to collapse
Yes, But One Of Its Advantages Is Giving The System An Opportunity To Detect The Change At The Booting Stage.
yung40oz84 said:
I'm confused about this.... Is it the same as clicking clear date in app settings?
Click to expand...
Click to collapse
Did You Try The Module?
For Magisk v1400, Download ClearPlayStoreWithServicesData4Magisk-v1.0.0(v1400)(3MF).zip
Dreamer(3MF) said:
For Magisk v1400, Download ClearPlayStoreWithServicesData4Magisk-v1.0.0(v1400)(3MF).zip
Click to expand...
Click to collapse
Link is dead. Can you relink please
edit. got off internet site
---------- Post added at 05:07 PM ---------- Previous post was at 04:15 PM ----------
Is 1400 newest?
mattie_49 said:
Link is dead. Can you relink please
edit. got off internet site
---------- Post added at 05:07 PM ---------- Previous post was at 04:15 PM ----------
Is 1400 newest?
Click to expand...
Click to collapse
I Relinked The Title With The File Again. You Can Also Download The Module From OP(The 1st Post) Under The Attached Files Section.
Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)
Dreamer(3MF) said:
Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.00(1400) To v15.3(1531)
- For The Modules Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)
Click to expand...
Click to collapse
That explains why 1400 was causing madness on Oreo with 16.4 Magisk. Should just be one. Everyone has surely updated to latest haven't they?
mattie_49 said:
That explains why 1400 was causing madness on Oreo with 16.4 Magisk. Should just be one. Everyone has surely updated to latest haven't they?
Click to expand...
Click to collapse
No, I Hope That The Latest Version Of Magisk To Be Suitable For All Devices But It Relies On Many Factors Such As Boot Image, Kernel, Rom & Magisk Itself.
Are you sure that a SafetyNet infection is not more complicated?
I would really appreciate your input on this, as my Galaxy S5 on stock 6.0.1 is infected by SafetyNet. I re-flashed to stock and am about to flash Magisk 16.4. I am trying to decide whether a dreaded factory reset to wipe /data is necessary to get rid of the SafetyNet failed state. What I am afraid of is that there may be a cross-infection between /data/data (gapps) and installed apps that cooperate closely with SafetyNet.
In particular in my case, for example, an app "NOAA Weather" reports frequently back to Google and warned me to to update Play Services after I restored Play Services to a stock version. Poking around in Play Services SqLite databases in /data/data (...gms) I found an unencrypted database listing the NOAA Weather app executable name. I am afraid that the NOAA Weather app's data may also have my device blacklisted. And who knows where else in /data the SafetyNet failed state may be flagged?? What is your opinion about this?
Thank you!
BruceElliott said:
I would really appreciate your input on this, as my Galaxy S5 on stock 6.0.1 is infected by SafetyNet. I re-flashed to stock and am about to flash Magisk 16.4. I am trying to decide whether a dreaded factory reset to wipe /data is necessary to get rid of the SafetyNet failed state. What I am afraid of is that there may be a cross-infection between /data/data (gapps) and installed apps that cooperate closely with SafetyNet.
In particular in my case, for example, an app "NOAA Weather" reports frequently back to Google and warned me to to update Play Services after I restored Play Services to a stock version. Poking around in Play Services SqLite databases in /data/data (...gms) I found an unencrypted database listing the NOAA Weather app executable name. I am afraid that the NOAA Weather app's data may also have my device blacklisted. And who knows where else in /data the SafetyNet failed state may be flagged?? What is your opinion about this?
Thank you!
Click to expand...
Click to collapse
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Enable WiFi --> Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Magisk Manager --> Tap To Start SafetyNet Check --> Send Its Screenshot
- Install SafetyNet Helper Sample From PlayStore & Send Its Screenshot
- Magisk Manager --> Modules --> Send Its Screenshots
- Magisk Manager --> SuperUser --> Send Its Screenshots
- From Settings --> About Phone --> SELinux Status --> Send Its Screenshot
- Complete Info About The Device, The Used Rom & The Used Kernel
- Send Full Logcat (Download Logcat Extreme From PlayStore) & Magisk Log (Magisk Manager --> Log --> Magisk & SuperUser)
- Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write magiskhide --ls --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which su --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write getenforce --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write sestatus --> Click On Enter --> Send Its Screenshot
General Steps For Passing The SafetyNet & Certifying The Device:
- Download ClearPlayStoreWithServicesData4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Download SELinuxModeInverter4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix&Pokemon-Go From PlayStore
- If It Didnot Work, Download DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Download ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
General Steps For Using Netflix:
- Uninstall Netfilx If Installed
- Download ClearPlayStoreWithServicesData4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download Netflix Enabler From This Thread https://forum.xda-developers.com/apps/magisk/module-netflix-enabler-enable-netflix-t3708126 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Disable Netflix Enabler From Magisk Manager
- Download Liboemcrypto Disabler From This Thread https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download SELinuxModeInverter4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
Jvirg said:
Magisk manager?
Click to expand...
Click to collapse
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse
BruceElliott said:
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse
Regarding busybox, I did not install one specifically; however Titanium installs with its own. I believe that there may also be a system busybox, but not sure.
Click to expand...
Click to collapse
BruceElliott said:
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
According To The Sent Screenshots, PlayStore Device Certification Status Is Certified & Your Device Passed The SafetyNet. Is There Anything Else You Want To Check?
BruceElliott said:
BruceElliott said:
Regarding busybox, I did not install one specifically; however Titanium installs with its own. I believe that there may also be a system busybox, but not sure.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
Dreamer(3MF) said:
Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
Click to expand...
Click to collapse
I believe that I am good on this thread, Dreamer; thank you!
This is an excellent script and did what I struggled to do manually.
I feel there's a noticeable difference in the battery consumption post this script as I'm being a bit more conscious about what Google options to permit this time around.
Great work.
Sent from my SM-N910F using Tapatalk
-------------------------------------------------------------------------------------------------------------------------
Related
Hi Guys!
I've been following the topic about the TEZ app and I have a similar problem with Santander app. When I used the Android N with SuperSU, Santander has worked and still works today in my old S7. When I upgraded my Note 8 for Android Oreo the application didn't work anymore, not even open. I've tried a couple of 5 custom rom and none worked.
Last week I read the topic about TEZ and removed phone permission to the google phone play services and Santander ran until yesterday, but I lost the root in Magisk and restarted the Note 8 and the Santander didn't open more. I've uninstalled and reinstalled the Magisk and Santander and not solved.
Does anyone have any suggestions?
RRFERA said:
Hi Guys!
I've been following the topic about the TEZ app and I have a similar problem with Santander app. When I used the Android N with SuperSU, Santander has worked and still works today in my old S7. When I upgraded my Note 8 for Android Oreo the application didn't work anymore, not even open. I've tried a couple of 5 custom rom and none worked.
Last week I read the topic about TEZ and removed phone permission to the google phone play services and Santander ran until yesterday, but I lost the root in Magisk and restarted the Note 8 and the Santander didn't open more. I've uninstalled and reinstalled the Magisk and Santander and not solved.
Does anyone have any suggestions?
Click to expand...
Click to collapse
I'll Try To Make a Module For Santander App Like Tez Hider But I Need Firstly To Get the Following
- Full Logcat
- A Copy Of App
Dreamer(3MF) said:
I'll Try To Make a Module For Santander App Like Tez Hider But I Need Firstly To Get the Following
- Full Logcat
- A Copy Of App
Click to expand...
Click to collapse
Thanks! But I dont know how to do full logcat and copy app. Can you help me?
RRFERA said:
Thanks! But I dont know how to do full logcat and copy app. Can you help me?
Click to expand...
Click to collapse
I've tested the UK app, and all I need to do for it to start is to add it to the Hide list. Nothing else... If I don't, it complains about root and doesn't start. It looks like a very simple root detection.
Didgeridoohan said:
I've tested the UK app, and all I need to do for it to start is to add it to the Hide list. Nothing else... If I don't, it complains about root and doesn't start. It looks like a very simple root detection.
Click to expand...
Click to collapse
I did it and not solve! Santander is add to the Hide list in Magisk!
RRFERA said:
I did it and not solve! Santander is add to the Hide list in Magisk!
Click to expand...
Click to collapse
I got that, all I'm saying is that it's possible to hide root from the app... And that the root detection doesn't seem that sophisticated.
There might be something about your ROM that you're using. Do you pass SafetyNet, and does all checks in Rootbeer Sample return ok if you add it to the Hide list?
RRFERA said:
Thanks! But I dont know how to do full logcat and copy app. Can you help me?
Click to expand...
Click to collapse
As For Logcat, Send The Full Logcat Of Santander Via One Of The Following Methods
-----> Download Terminal Emulator From PlayStore & Write logcat | grep santander > log.txt
-----> Download Logcat Extreme (Or Catlog) From PlayStore
-----> Write adb logcat -d > log.txt For ADB
As For Santander App, Send Its Link On Google PlayStore
---------- Post added at 02:52 PM ---------- Previous post was at 02:43 PM ----------
RRFERA said:
I did it and not solve! Santander is add to the Hide list in Magisk!
Click to expand...
Click to collapse
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Check The SafetyNet From Magisk Manager, PlayStore Device Certification Status & Netflix From PlayStore
I have same problems to logcat....
See the pic
Santander app:
https://play.google.com/store/apps/details?id=com.santander.app
I dont have BusyBox and Xposed, have SafetyNet green, and my google play is not certificated (i dont know how!).
RRFERA said:
I have same problems to logcat....
See the pic
Santander app:
https://play.google.com/store/apps/details?id=com.santander.app
I dont have BusyBox and Xposed, have SafetyNet green, and my google play is not certificated (i dont know how!).
Click to expand...
Click to collapse
I can't get that one to trigger at all... And I can't test much since I'm not a customer.
According to Rootbeer you do have busybox, so maybe it comes with the ROM. Check for that.
And, since the app is asking for phone permissions, have you also added the phone to the Hide list? That works for some of these apps...
Didgeridoohan said:
I can't get that one to trigger at all... And I can't test much since I'm not a customer.
According to Rootbeer you do have busybox, so maybe it comes with the ROM. Check for that.
And, since the app is asking for phone permissions, have you also added the phone to the Hide list? That works for some of these apps...
Click to expand...
Click to collapse
I dont understand, caus Rootbeer show busybox binary X.
And phone is add ti the Hide list.
I dont know why my Note 8 have play store uncertified.
RRFERA said:
I dont understand, caus Rootbeer show busybox binary X.
Click to expand...
Click to collapse
That means that Rootbeer is detecting busybox. All the green check marks mean that that particular sign of your device being rooted was not found.
I dont know why my Note 8 have play store uncertified.
Click to expand...
Click to collapse
If you can pass SafetyNet, clear data for the Play Store and possibly reboot. After that the status should be certified, but it might take a while for it to show.
If you can pass SafetyNet, clear data for the Play Store and possibly reboot. After that the status should be certified, but it might take a while for it to show.[/QUOTE]
Did it and now its certificated! Thanks!
Now, only problem is Santander app!
Didgeridoohan said:
I can't get that one to trigger at all... And I can't test much since I'm not a customer.
According to Rootbeer you do have busybox, so maybe it comes with the ROM. Check for that.
And, since the app is asking for phone permissions, have you also added the phone to the Hide list? That works for some of these apps...
Click to expand...
Click to collapse
A) For Enabling ADB Debugging On Your Device
HTML:
To use adb with a device connected over USB, you must enable USB debugging in the device system settings, under Developer options.
On Android 4.2 and higher, the Developer options screen is hidden by default. To make it visible, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options at the bottom.
On some devices, the Developer options screen might be located or named differently.
You can now connect your device with USB. You can verify that your device is connected by executing adb devices from the android_sdk/platform-tools/ directory. If connected, you'll see the device name listed as a "device".
B) Kindly Check Also This Post https://forum.xda-developers.com/ap...device-certified-custom-t3769069/post76595671
C) Send A Screenshots Of The Installed Magisk Modules From Magisk Manager, A ScreenShot Of The Main Interface Of Magisk Manager After Checking The SafetyNet & Also A Screenshots Of The Installed Apps From Settings-->Apps
D) What About Your Phone Model, The Flashed Rom & The Android Version?
Didgeridoohan said:
That means that Rootbeer is detecting busybox. All the green check marks mean that that particular sign of your device being rooted was not found.
If you can pass SafetyNet, clear data for the Play Store and possibly reboot. After that the status should be certified, but it might take a while for it to show.
Click to expand...
Click to collapse
Dreamer(3MF) said:
A) For Enabling ADB Debugging On Your Device
HTML:
To use adb with a device connected over USB, you must enable USB debugging in the device system settings, under Developer options.
On Android 4.2 and higher, the Developer options screen is hidden by default. To make it visible, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options at the bottom.
On some devices, the Developer options screen might be located or named differently.
You can now connect your device with USB. You can verify that your device is connected by executing adb devices from the android_sdk/platform-tools/ directory. If connected, you'll see the device name listed as a "device".
B) Kindly Check Also This Post https://forum.xda-developers.com/ap...device-certified-custom-t3769069/post76595671
C) Send A Screenshots Of The Installed Magisk Modules From Magisk Manager, A ScreenShot Of The Main Interface Of Magisk Manager After Checking The SafetyNet & Also A Screenshots Of The Installed Apps From Settings-->Apps
D) What About Your Phone Model, The Flashed Rom & The Android Version?
Click to expand...
Click to collapse
Hi friends! Show screenshots!
My phone is Note 8 with EchoeRom v2, android 8.0.0. And now my playstore is certificated!
RRFERA said:
Hi friends! Show screenshots!
My phone is Note 8 with EchoeRom v2, android 8.0.0. And now my playstore is certificated!
Click to expand...
Click to collapse
Have you checked if the ROM includes busybox by default? Check with the developer, or you could just try to run it... In a terminal emulator, just type busybox (it's possible you need to run su first) and see if you get a result.
Didgeridoohan said:
Have you checked if the ROM includes busybox by default? Check with the developer, or you could just try to run it... In a terminal emulator, just type busybox (it's possible you need to run su first) and see if you get a result.
Click to expand...
Click to collapse
Look the screenshot my friend!
RRFERA said:
Look the screenshot my friend!
Click to expand...
Click to collapse
So yes, the ROM comes with busybox included.
I haven't checked your log (it's no fun reading logs on a phone), so I don't know if there's anything in there about the app triggering because of that. But, it's certainly a possibility
You could try a different ROM that doesn't include busybox. If you then do need busybox, the best option is to install the busybox Magisk module from the Manager Downloads. That won't be detected.
Didgeridoohan said:
So yes, the ROM comes with busybox included.
I haven't checked your log (it's no fun reading logs on a phone), so I don't know if there's anything in there about the app triggering because of that. But, it's certainly a possibility
You could try a different ROM that doesn't include busybox. If you then do need busybox, the best option is to install the busybox Magisk module from the Manager Downloads. That won't be detected.
Click to expand...
Click to collapse
I tried Dr Ketan, Deluxe and NoName roms and all have the same problem!
[MODULE] Santander Hider (Trial/Beta Version)
Introduction:
Simple Module For Hiding The Root From Santander.
Current Version: 0.0.8
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
----------------------------------------------------------------------------------------------------------------
Dreamer(3MF) said:
[MODULE] Santander Hider (Trial/Beta Version)
Introduction:
Simple Module For Hiding The Root From Santander.
Current Version: 0.0.8
Thanks To:
- RRFERA
Created: May.26.2018
Updated: -
Download Link: Attached
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It With TWRP Recovery
Magisk Hide:
- Santander Will Be Added Automatically To The List Of Magisk Hide
- Some Apps Will Be Added Automatically To The List Of Magisk Hide Such As Google Play Services, Google Play Store, Phone Apps & Phone Services
Recommendation:
- In-Case Of Using SuperSu with Magisk, Uninstall SuperSu (Maybe SuperSu Causes Problems To Magisk Hide)
- Clear Data&Cache Of Santander
- Enable Phone Permission Of Google Play Services
In-Case Of Failure Of Passing Santander Test: Kindly Send Your Answer For The Following
- Did You Try The Latest Update Of SantanderHider4Magisk?
- Did You Enable Phone Permission Of Google Play Services?
- Did You Add Santander To The List Of Magisk Hide?
- Did You Clear Data&Cache Of Santander --> Reboot --> Try Again?
- Did You Try To Hide Magisk Manager (Magisk Manager --> Settings --> Hide Magisk Manager)?
- Which Version Of Magisk Do You Use?
- Do You Use An Official ROM (Stock/Custom)?
- Is Your PlayStore Device Certification Status, Certified?
- Did Your Phone Pass The SafetyNet?
- Do You Use Any Other Rooting Tool Such As SuperSu with Magisk?
- Did You Try To Uninstall Magisk & Reinstall It Again?
- Did You Try To Install The Latest Version Of Magisk (Stable/Beta)?
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed -> Reboot --> Try Again
- Try This Module SELinuxModeInverter4Magisk
- Try To Disable Phone Permission Of Google Play Services
- Install RootBeer Sample From PlayStore --> Open It --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Full Logcat Is Required
- Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write magiskhide --ls --> Click On Enter --> Send Its Screenshot
- Try This Alternative Solution Hide-Unhide MagiskSu Via Tasker
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
----------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Hello my friend!
First, thank you very much for your attention and help!
I did all the procedures indicated and unfortunately didn't work, Santander does not work.
See screenshots.
Introduction:
Simple Module To Hide The Root From Google Pay (Tez) [Google Mobile Payments Service For India].
- After The Installation & 1st Reboot, It Hides The Rooting & Disables Itself [P.S. Disabling Itself For Some Versions]
- Enabling This Module From Magisk Manager = Doing Its Functionality & Disabling Itself (Next Reboot) [P.S. Disabling Itself For Some Versions]
Current Version: v0.1.2.1AND
- Magisk Hide Must Be Working Properly Which Is A Main Point To Use The Module
- Passing The SafetyNet Means Also Magisk Hide Is Working So Check The General Steps
- Some Issues Which Are Related To Magisk/Rom/Kernel/GApps Itself Can Be Solved By Using A Different Versions Of The Module [Where v0.1.2.1A/v0.1.2.1AD Can Be Downloaded From The Same Download Link Inside The Folder Of Special]
- Some Versions Of The Module & Some Roms/Kernels/GApps Have Some Effect On Sync That Will Be Reflected On Apps Which Need Sync So To Solve The Issue, Do The Following [Disable The Module & Reboot To Use The Other Apps Which Need Sync] Or [Enable The Module & Reboot To Use Tez]
- It Is Recommended To Clear Magisk Hide List Including Each App/Activity/Process Before Flashing The New One So Use The Module Of ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208
- For Google Pay (Tez & GPay), Check These Posts https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post79008117 & https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post79194395
Created: Apr.18.2018
Updated: Feb.11.2019
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The General Steps)
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To The Latest Version Which Is Currently v18.1(18100)
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru TWRP Recovery
Magisk Hide:
- Tez Will Be Added Automatically To The List Of Magisk Hide
- Some Apps Will Be Added Automatically To The List Of Magisk Hide Such As Google Play Services, Google Play Store, Google Services Framework, Phone Apps & Phone Services
Recommendation:
- Check The General Steps From This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76816985
- In-Case Of Failure, Check This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76675913
- For Passing The SafetyNet & Certifying The Device, Check This Post https://forum.xda-developers.com/ap...playstore-services-data-t3789498/post76682978
Beta Version:
- Check This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76650492
General Info:
- To Disable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It Thru TWRP Recovery
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It Thru TWRP Recovery
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It Thru TWRP Recovery
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Device Spoofing Tool - Core Only Mode - Other Modules
----------------------------------------------------------------------------------------------------------------
P.S. You Can Update Tez App As You Want Without Any Effect On The Module Unless The Changes Of Tez App Are Related To The Root Detection. But Everyone Here Will Help Us To Figure Out The Solution.
----------------------------------------------------------------------------------------------------------------
The Old Thread (Tez App Is Not Working On Custom Rom Or Rooted Device)
----------------------------------------------------------------------------------------------------------------
Reserved for News/Updates #1
Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)
Reserved for News/Updates #1
Beta Version:
Current Beta Version: -
Changelog: -
Thanks for the life saver module
charlessxavier said:
Thanks for the life saver module
Click to expand...
Click to collapse
Thanks. Could I Ask You To Try The Beta Version & Send The Feedback?
I Am Asking Our Mates To Check The Stable&Beta Versions And Share The Feedbacks/Ideas/Questions To Enhance/Modify The Module.
Beta version seems to be not working for me.
Dreamer(3MF) said:
Thanks. Could I Ask You To Try The Beta Version & Send The Feedback?
Click to expand...
Click to collapse
Done. No issues with this version. Was able to transfer money successfully.
Tried beta version didn't worked on official magisk v16 , cleared data & cache of tez - downloaded & flashed beta zip - rebooted - tried registration - detected
(Using RR custom Oreo rom )
H4CK_H0PP3R said:
Tried beta version didn't worked on official magisk v16 , cleared data & cache of tez - downloaded & flashed beta zip - rebooted - tried registration - detected
(Using RR custom Oreo rom )
Click to expand...
Click to collapse
- Did You Enable Phone Permission Of Google Play Services?
- Did You Use The Stable Version? & What Is The Feedback?
Able to register, but not able to add bank account..
Magisk 16.4 , Tissot with liquid remix rom
Suggestions
- Uninstall Any Other Rooting Tool Completely Such As SuperSu & Lineage-AddOnSU Which Is Used With Magisk
- Download A Different Version Of TezHider4Magisk Module From This Link https://androidfilehost.com/?w=files&flid=284689 Then Flash It Thru Magisk Manager Then Reboot
- Try DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435
- Try SELinuxModeInverter4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271
- Try To Disable Phone Permission Of Google Play Services (From Settings --> Apps --> Google Play Services --> Permissions --> Disable Phone)
- Try To Install The Latest Version Of Magisk (Stable/Beta) Or One Of The Modified Magisk Versions From This Link https://androidfilehost.com/?w=files&flid=274603
- Do A Clean Flash For The Same Used Rom Or Change The Rom Or Change The Kernel
For Any Issue, Send The Issue Along With The Following
- Enable WiFi --> Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Magisk Manager --> Tap To Start SafetyNet Check --> Send Its Screenshot
- Install SafetyNet Helper Sample From PlayStore & Send Its Screenshot
- Magisk Manager --> Modules --> Send Its Screenshots
- Magisk Manager --> SuperUser --> Send Its Screenshots
- From Settings --> About Phone --> SELinux Status --> Send Its Screenshot
- Complete Info About The Device, The Used Rom & The Used Kernel
- Send Full Logcat (Download Logcat Extreme From PlayStore) & Magisk Log (Magisk Manager --> Log --> Magisk & SuperUser)
- Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write magiskhide --ls --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which su --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write getenforce --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write sestatus --> Click On Enter --> Send Its Screenshot
vygavedha said:
Able to register, but not able to add bank account..
Magisk 16.4 , Tissot with liquid remix rom
Click to expand...
Click to collapse
Kindly Check This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76675913. And Did You Install Stable/Beta Version?
I found something mate.
When I already have tez registered using the stable module and on top if I flash the beta version there seems to be no problem.
Whereas, if I install the beta version first and register tez it's failing.
About Sending The Full Logcat: You Can Use One Of The Following Methods
- Download Terminal Emulator From PlayStore & Write logcat | grep nbu > log.txt
- Download Logcat Extreme (Or Catlog) From PlayStore
- Write adb logcat -d > log.txt For ADB
prakashait9 said:
Beta version seems to be not working for me.
Click to expand...
Click to collapse
Kindly Do The Following
- Flash Stable Version --> Reboot --> Register Tez
- Flash Beta Version --> Reboot --> Try To Transfer Money
Dreamer(3MF) said:
Beta Version:
Current Beta Version: 0.1.3.1(Beta)
- Firstly Flash Stable Version --> Reboot --> Register Tez
- Secondly Flash Beta Version --> Reboot --> Try To Transfer Money
Changelog: Disabling Some Permissions Of Phone Services.
Thanks Again To Our Mate prakashait9 Who Suggested The Modification
Click to expand...
Click to collapse
Dreamer(3MF) said:
- Did You Enable Phone Permission Of Google Play Services?
- Did You Use The Stable Version? & What Is The Feedback?
Click to expand...
Click to collapse
Did You Enable Phone Permission Of Google Play Services? : I did nothing as per new beta version it changes permission by self so didn't changed any permission
- Did You Use The Stable Version? & What Is The Feedback - No beta version i tried as I thought it worked for some people .
H4CK_H0PP3R said:
Did You Enable Phone Permission Of Google Play Services? : I did nothing as per new beta version it changes permission by self so didn't changed any permission
- Did You Use The Stable Version? & What Is The Feedback - No beta version i tried as I thought it worked for some people .
Click to expand...
Click to collapse
Use The Stable Version From OP(1st Post) Under Attached Files Section & Kindly Do The Steps As Per Mentioned In This Post https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567/post76675913#post76675913.
[MODULE] 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.
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Open Magisk In Core Only Mode.
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Flash This Module
- This Module Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot (Rebooting The Android Is Required To Load The Rest Of Modules)
- Core Only Mode Gives The Device The Ability To Get Into The Android Directly With User Interface Which Means The User Can Use The Device With All Features/Functionalities Except Magisk Modules Even Before Removing The Module(s) Which Caused The Bootloop/Issue
- Enabling Core Only Mode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled
- After The Installation & Booting, It Opens Magisk In Core Only Mode & Disables Itself
- Enabling This Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- For Using The Module Thru ADB Shell/TWRP Terminal [The Module Must Be Pre-Installed Via Magisk Manager/TWRP Recovery/ADB Sideload], Write The Following Commands --> rm -f /data/DreamerMods/MultiFunctions/MagiskCoreOnlyMode/Active/disable (Click On Enter) --> reboot (Click On Enter)
Created: July.17.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Flash It Thru TWRP Recovery
- Or Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Clear Dalvik Cache - Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved for News/Updates #1
Reserved for News/Updates #2
I Am Asking Our Mates To Check The Stable Version And Share The Feedbacks/Ideas/Questions To Enhance/Modify The Module.
Thank you brother :highfive:
image18 said:
Thank you brother :highfive:
Click to expand...
Click to collapse
Did you try?
Sent from my MIX 2 using Tapatalk
amour9999 said:
Did you try?
Sent from my MIX 2 using Tapatalk
Click to expand...
Click to collapse
yes
I wonder...
How can we get into magisk manager to use this module when having bootloop problem?
bnwg said:
I wonder...
How can we get into magisk manager to use this module when having bootloop problem?
Click to expand...
Click to collapse
In-Case Of Facing A Bootloop Issue Due To Flashing A Module, You Need To Put A Copy Of CoreOnlyMode4Magisk On SD-Card/Internal Memory Then Flash This Module Thru TWRP Recovery. This Module Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing The Module Which Caused The Bootloop From The Section Of Modules In Magisk Manager.
Hello,
Thanks for that.
It's a little similar to the first feature of mm module (https://github.com/Magisk-Modules-Repo/Magisk-Manager-for-Recovery-Mode), but yours one directly enable the "Core Only Mode" of Magisk, the differences are that all modules are disabled as u said on your OP and it disable the "Magisk Hide" and "Host systemless support" features, that's it, right ?
Effectivly it could be usefull in case the mm module don't works for any reason or if one or several hiders/hosts module(s) cause bootloops on a device.
Rom said:
Hello,
Thanks for that.
It's a little similar to the first feature of mm module (https://github.com/Magisk-Modules-Repo/Magisk-Manager-for-Recovery-Mode), but yours one directly enable the "Core Only Mode" of Magisk, the differences are that all modules are disabled as u said on your OP and it disable the "Magisk Hide" and "Host systemless support" features, that's it, right ?
Effectivly it could be usefull in case the mm module don't works for any reason or if one or several hiders/hosts module(s) cause bootloops on a device.
Click to expand...
Click to collapse
Thanks For Your Interest. As For Magisk Manager For Recovery Mode & Core Only Mode, Both Of Them Are Sharing The Same Target But Not The Same Concept. Core Only Mode Gives The Device The Ability To Get Into The Android Directly With User Interface Which Means That The User Can Use The Device With All Features/Functionalities Except Magisk Modules Even Before Disabling/Removing The Module(s) Which Caused The Bootloop/Issue.
Enabling Core Only Mode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled.
This module is usefully! THANKS BRO!
Fdraco10 said:
This module is usefully! THANKS BRO!
Click to expand...
Click to collapse
Thanks! You Can Also Check Another Useful Modules From This Link >>>Other Modules<<<.
thanks man! your module is my device savior
This module is useful
Deleted
peterlee928 said:
much thanks for sharing this lovely tool. this will save me much time going forward.
Dreamer(3MF) said:
In-Case Of Facing A Bootloop/Bootscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It Thru TWRP Recovery.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@peterlee928 Nice To Hear It Worked. And You Can Try Also The Following Useful Modules
- ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264
- ClearPlayStoreWithServicesData4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498
Very nice module, it is great to save you from bootloop, same as entering in Safe Mode on PC!!
But how disable Core Only Mode after removing the problematic module???
I delete guilty module and rebooted, but still Magisk in Core mode only!
I removed the module Core Only Mode, and rebooted and still Magisk in Core Only Mode
How to get back to default working Magisk State??
Thx.
saoudien07 said:
Very nice module, it is great to save you from bootloop, same as entering in Safe Mode on PC!!
But how disable Core Only Mode after removing the problematic module???
I delete guilty module and rebooted, but still Magisk in Core mode only!
I removed the module Core Only Mode, and rebooted and still Magisk in Core Only Mode
How to get back to default working Magisk State??
Thx.
Click to expand...
Click to collapse
Check The Following Post.
Dreamer(3MF) said:
Introduction:
Simple Module To Open Magisk In Core Only Mode To Help For Removing Any Module Which Causes A Bootloop.
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, You Need To Put A Copy Of CoreOnlyMode4Magisk On SD-Card/Internal Memory Then Flash This Module Thru TWRP Recovery
- This Module Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot (Rebooting The Android Is Required To Load The Rest Of Modules)
Click to expand...
Click to collapse
Dreamer(3MF) said:
Check The Following Post.
Click to expand...
Click to collapse
Thx for the fast answer
so was in Magisk "SETTING"
Nothing to do with uninstalling of the module.
Btw u got great modules, they are must have and should go to toolbox of every Rom tweaker
[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