Database Users

[XPOSED] [5.0+] [Disable Apk Signature Comparison] Super User Mode X - v1.0.0

Features:
- Disable checking of app signatures in the Package Manager Service core, allowing modded/signed apks be installed, or even granting them system privileges
Requeriments:
- Xposed Framework for Lollipop / Marshmallow / Nougat
Install:
TRY IT OUT AT YOUR OWN RISK!!!
1. Download and install always the latest version (attached)
2. Open Xposed Installer and activate it under Modules
3. Reboot
4. Done!
This module has no UI (settings screen)!!
Warning:
If you have any modded/signed apk like SystemUI.apk, and this module activated, DO NOT DEACTIVATE IT, OR YOU WILL END UP WITH A BOOTLOOP (unless you have a patched services.jar)!!!
Edit.: REMOVED CHECK APP DUE SELINUX ISSUE ON ANDROID MM/N !!
How do we know if Super User Mode is really working?
Install attached Serajr_Super_User_Mode_Check.apk and toggle Airplane mode through it (only system apps signed with platform keys have this privilege).
Without Super User Mode, system (Package Manager Service) will refuse even to install and later toggle it!
Special thanks:
- @rovo89
Enjoy it!

Nice bro @serajr
You rock \m/
Sent From Cybertron On MWA V2.6.0

How does dis really works... If we have patched services.jar do we still need dis?
BigUps @serajr brov.

whalesplaho said:
How does dis really works... If we have patched services.jar do we still need dis?
BigUps @serajr brov.
Click to expand...
Click to collapse
No you don't!! This module is meant for those with stock services.jar (odexed or deodexed).
It is redundant on a system with an already patched services.jar!

serajr said:
No you don't!! This module is meant for those with stock services.jar (odexed or deodexed).
It is redundant on a system with an already patched services.jar!
Click to expand...
Click to collapse
Okay brov.... Thanks!
Awaiting yur xperia xposed for MM.

This will help loads of people who don't know what it's about. And development by linking to this. Great work serajr!

Thanks a lot

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can toggle airplane ✈ mode, its ok?

Metallijim said:
This will help loads of people who don't know what it's about. And development by linking to this. Great work serajr!
Click to expand...
Click to collapse
AK2H said:
Thanks For Your Great Efforts!
Click to expand...
Click to collapse
Funkmasterchilla said:
Thanks a lot
Click to expand...
Click to collapse
Thank you!!
dex87xda said:
I can toggle airplane ✈ mode, its ok?
Click to expand...
Click to collapse
You're done!

@serajr:
Thank you so much for yet another wonderful work! :good:
Hope this will help me to install (downgrade to) the old good Sony Dialer & Contact Apps from KK on my Z3+/Z4 running MM. Really don't like Dialer & Contact actually since LP times.

serajr said:
How do we know if Super User Mode is really working?
Install attached Serajr_Super_User_Mode_Check.apk and toggle Airplane mode through it (only system apps signed with platform keys have this privilege).
Without Super User Mode, system (Package Manager Service) will refuse even to install and later toggle it!
Click to expand...
Click to collapse
I'm using an App called "Timed Toggles" since many years to automatically turn Airplane Mode ON at night and then again OFF in the morning. Here is the link on PlayStore: Timed Toggles
This App (version 1.5.1), after granting Root only, works flawless on latest MM 6.0.1 (32.2.A.0.224, same as for the Z5) on my Z3+/Z4. I've not made it a System App or anything, just granted Root. So this contradicts "only system apps signed with platform keys have this privilege".
But now, trying the same with Power Toggles (version 6.0.4) does not work. Not with Root, not even after making it a System App.
Both Apps issue the same commands (from the logs in SuperSu), so that is:
Turn ON:
setting put global airplane_mode_on 1
am broadcast -a android.intent.action.AIRPLANE_MODE --ez start true
Turn OFF:
setting put global airplane_mode_on 0
am broadcast -a android.intent.action.AIRPLANE_MODE --ez start false
Only difference is... "Timed Toggles" sends it in two takes (and so there're actually two separate lines in the SuperSu log) like:
setting put global airplane_mode_on 1
am broadcast -a android.intent.action.AIRPLANE_MODE --ez start true
...whereas for failing "Power Toggles" the log shows only one single line like:
"setting put global airplane_mode_on 1; am broadcast -a android.intent.action.AIRPLANE_MODE --ez start true"
I'm really not the one to judge, but I think it could be related to what Chainfire wrote here:
3. How to call su
3.1. Common pitfalls
Runtime.exec() and ProcessBuilder
It is tempting to use Runtime.getRuntime().exec("su -c [command]");, but you should be aware that [command] should be a single parameter, and thus may require quoting. Unfortunately both quoting the [command] parameter as well as passing the paramaters as separate variables to either Runtime.exec() or ProcessBuilder does not work consistently across all Android versions, and thus this construct should be avoided entirely. It is not impossible to do this right - but there's a high risk of problems.
Click to expand...
Click to collapse
Nonetheless, "Timed Toggles" proof that a non-system App with Root only can toggle Airplane Mode ON/OFF.
Sorry for the lengthy post, happy to assist with more testing if needed

sxtester said:
... Nonetheless, "Timed Toggles" proof that a non-system App with Root only can toggle Airplane Mode ON/OFF.
Sorry for the lengthy post, happy to assist with more testing if needed
Click to expand...
Click to collapse
The app I shared for testing purposes only, doesn't make use of root. Super User Mode grants it privileges enough to perform system modifications!
This is not about root or toggling an specific mode!!

serajr said:
The app I shared for testing purposes only, doesn't make use of root. Super User Mode grants it privileges enough to perform system modifications!
This is not about root or toggling an specific mode!!
Click to expand...
Click to collapse
Huuuh!, seems I got a bit confused and mixed things up by Root, System Mode, System App etc. Sorry for bothering

When open check superuser.apk my z5 dual reboot everytime

rajdeep312 said:
When open check superuser.apk my z5 dual reboot everytime
Click to expand...
Click to collapse
Logcat can tells us what's happening!!

can i use in xperia p cm12.1???

why we crying with bootloop
we have pc companion!
Xperia E4 E2105 Works Good!!!!!!!!! and Material NXT Themes working really good with Serajr Xperia Xposed

serajr said:
Logcat can tells us what's happening!!
Click to expand...
Click to collapse
The same on my Z5c. Rooted, Xposed, installed module and activated, then istalled superuser mod check apk and when i want to open it my phone reboots?
What the problem?
How can i create a logcat about it?

Midleo said:
The same on my Z5c. Rooted, Xposed, installed module and activated, then istalled superuser mod check apk and when i want to open it my phone reboots?
What the problem?
How can i create a logcat about it?
Click to expand...
Click to collapse
Android SDK > Monitor.bat (always better choice)
Or install aLogrec (free) from Play Store, keep it running and then open the app.

serajr said:
Logcat can tells us what's happening!!
Click to expand...
Click to collapse
serajr said:
Android SDK > Monitor.bat (always better choice)
Or install aLogrec (free) from Play Store, keep it running and then open the app.
Click to expand...
Click to collapse
Thanks for the answer, first i tried with aLogrec free version. Attaching the logcat:
https://drive.google.com/file/d/0B4p2he4oSmN5WUFCN25uLTFXbnM/view?usp=sharing

[Guide] Universal SafetyNet Fix

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello Everyone, this is Rakesh today we are going to fix SafetyNet pass in MIUI8. As we all know about the google new policy regarding rooted devices and some applications like banking apps and railway reservation apps like IRCTC is we want to run this kind of apps in our rooted device we need to get SafetyNet pass with help of magisk.
So what is SafetyNet actually?
Google uses something called SafetyNet to detect whether your device is rooted or not, will block access to those features. Google isn’t the only one doing this even plenty of third-party apps also won’t work on rooted Android devices, although they may check for the presence of root in other ways. So I think now you guys have understood about this and I don’t want to push too much info into your brains, Let’s get into instructions how to get pass SafetyNet in MIUI8 ROMs. Know More About SafetyNet Here
Today I will Show You How To fix SafetyNet on MIUI8, as you already know MIUI is a very Heavily Skinned Android and it’s not easy to do modifications on it what we like to do. This a User-friendly Guide so you don’t need any diploma on Android and it’s a Universal Tutorial 5.0+
Let’s Start the Tutorial
As for your Information, I’m doing this Guide on multiROM.me 7.7.20 Global Beta.
Requirements
ZCX Recovery
MultiROM (optional)
MagiskSU
A Working Brain.apk
First of All
Reboot your Redmi Note 3 into Recovery Mode
Wipe Factory Reset ( optional wipe system dalvik/cache data)
Flash MultiROMReboot Your Device
Setup your Device Remember don’t add any account as of now,
( skip this if your ROM is not pre-rooted)
Go to SuperSU and Click on “Full Unroot” your device will automatically Reboot. Again Boot into Recovery
Flash Magisk v13.6
Flash USNF v2 b5
Reboot Your Device
Open Magisk and Check if your SafetyNet get Passed!!
If Not Passed then it will show like This “False”
Swipe The Left Edge
Open MagsikHide and Search Google and Tick on as shown below
Now Open Root Explorer or any other File Manager which can Edit build.pro
Go to root/system
Open Build.Pro
Search for ro.build.display.id=MMB29M
And add this after a space“release-keys”
Remove ” and copy/paste
Save it and Close Everything and now Boot into Recovery Mode again
Flash Magisk v14
Flash USNF v2 b5 hotfix
Reboot Your Device
Check Your SafetyNet Again and your Good to Go,
Now you can Add your Google Account and Play Store will Say that your device is “Certified”
for more information and downloads
http://redminote3.xyz/2017/09/10/univesal-safetynet-fix/
Thanks to redminote3.xyz for this wonderful guide.
Source :- http://en.miui.com/thread-825641-1-1.html
​

thank you so much, I just tick google play store and google services framework in magisk hide and everything change to true. tested on LeEco Le 2 x526 (MiuiPro 8.11.22)

I did an update, and now the safetynet test fails. I tried to reinstall the older version didn't work. I'm using Redmi Note 10 Pro device. Looking for the possible fix for this. Thank you!
Edit: It's working now, I have just reinstalled the MagiskHide Props Config

Samsung pay on watch when rooted

Hello, I have a new one plus 8 pro and I am rooted. I also have a Galaxy watch and when I install Samsung pay on the watch it says call customer service device has been compromised even though I have magiskhide for all the Samsung modules. Does anyone have any ideas how to get this working?
Thank you in advance...

I have the same problem. Completely stock. So I wonder if it's a Samsung issue. I had the 6t rooted and I was able to use Samsung pay without any problems

Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...

aaronc_98 said:
Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...
Click to expand...
Click to collapse
Is this still working for you? It's definitely not working on my end with my Pixel. The newest Magisk Manager also does not allow you to select any apps to hide, it's a simple toggle on or off for Magisk Hide and renaming the Magisk Manager didn't do anything.
Did you have to reboot after the rename?

Valiante said:
Is this still working for you? It's definitely not working on my end with my Pixel. The newest Magisk Manager also does not allow you to select any apps to hide, it's a simple toggle on or off for Magisk Hide and renaming the Magisk Manager didn't do anything.
Did you have to reboot after the rename?
Click to expand...
Click to collapse
Sorry - the Pixel was like 4 phones ago. I dont have any further info for you...

aaronc_98 said:
Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...
Click to expand...
Click to collapse
UPDATED Post : see next post for my solution that worked.
Hi aaronc_98,
Hope this is actually still working for you on your OP8 Pro!
When you say you need to rename the package, what are you referring to exactly?? The Samsung Pay app or Hide the Magisk App (renaming) in App settings?
Please provide more details on a step-by-step process you did to make it work on your OP device...if still working.
I have OP6T and it has stopped working recently and can't find a way to get back.
My setup:
OP6T, OOS 10.3.11
Galaxy Watch 46mm, latest OS installed (Jun 15, 2021)
Galaxy Wear App, SPAY Watch Plugin up to date. (Jun 15, 2021).
Thanking you in advance!

plepew said:
Hi aaronc_98,
Hope this is actually still working for you on your OP8 Pro!
When you say you need to rename the package, what are you referring to exactly?? The Samsung Pay app or Hide the Magisk App (renaming) in App settings?
Please provide more details on a step-by-step process you did to make it work on your OP device...if still working.
I have OP6T and it has stopped working recently and can't find a way to get back.
My setup:
OP6T, OOS 10.3.11
Galaxy Watch 46mm, latest OS installed (Jun 15, 2021)
Galaxy Wear App, SPAY Watch Plugin up to date. (Jun 15, 2021).
Thanking you in advance!
Click to expand...
Click to collapse
UPDATE,
Got it all to work!
Preparation:
- Install Galaxy Wearable
- Update Watch to the latest
- Install SP Watch Plugin (do not launch it at all)
Magisk Setup:
- Hide the following apps in MagiskHide: Hit the shield, Hit "MagiskHide" and select the apps:
a) Google Play Services
b) Samsung Health
c) SP Watch Plugin
* You can add banking apps here as well
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, recommend hiding the Magisk App itself for the setup. Here is how to do it:
- Hit "Settings" (within Magisk App)
- Hit "Hide the Magisk App" (I used MGKSettings).
Magisk will accept it and repopulate itself.
For good measure, I rebooted my device to recovery (TWRP in my case) wiped "Dalvik / ART Cache" and rebooted to system.
Once rebooted, go to the SP Watch Plugin App INFO (Do not launch the App), got to Storage & Cache & Clear Storage & Cache (should be 0 on both) for good measure!
Launch Galaxy Wear and (Strongly Recommended) scroll down to setup Samsung Pay and follow the steps. **(I don't recommend doing the SPay setup through the Watch Plugin.)**
If you get a notice within 10 seconds saying that the device is not secure (can't remember the message), you may have missed something and you need to start over with clean install of the SP Watch Plugin (storage & cache cleared).
Worst case they may have updated the Samsung Pay, Samsung Health Apps & OOS and it's been blocked again. Therefore we would need to restart the whole process from scratch or find another workaround.
PS. Some of you would probably like to restore or Un-Hide the Magisk App, so I went ahead and did it....so far SPay seems to be working. I have not reboot my device neither, which I rarely do. (I have rebooted my device several times since this post)
For any reason, in the coming days, there is an issue of any kind, I will report back here. If not, it's all good!
Hopefully this can help some of you out there!

worked for me, thanks a lot

OnePlus 6T on Oxygen OS 10.3.3 CtsProfile: false problem

I have a OnePlus 6T T-Mobile converted to unlocked global ROM. I had Magisk rooted and working on OOS 9 with no TWRP.
I recently updated to OOS 10.3.3 from 9.0.17 and now the CtsProfile returns false on a safetynet check.
Am I supposed to install safetypatcher module for magisk?
(https://forum.xda-developers.com/apps/magisk/module-safetypatcher-t3809879)
Or am I supposed to install MagiskHidePropsConfig module?
Also, how do I flash the busybox installer if I need to install MagiskHidePropsConfig?
Do I need to boot into TWRP?

Just enable MagiskHide on Magisk Manager, then Magisk Hide the Google Play Store and Google Framework Services.
Good luck

yot2703 said:
Just enable MagiskHide on Magisk Manager, then Magisk Hide the Google Play Store and Google Framework Services.
Good luck
Click to expand...
Click to collapse
Hi,
I had MagiskHide active already before updating from OOS 9 to 10, and checking the Magisk Hide list I already have Google Play Services checked on the list of applications to hide Magisk from (Google Play Store does not show up on the list so I can't have it checked).
For what its worth, I tried to find Netflix on the Play Store and it doesn't show up meaning the Play Store is definitely detecting something is off.
Is there a way to make Play Store show up on the list of Magisk hide apps? (its not showing up at the moment)

digitalsonic said:
Hi,
I had MagiskHide active already before updating from OOS 9 to 10, and checking the Magisk Hide list I already have Google Play Services checked on the list of applications to hide Magisk from (Google Play Store does not show up on the list so I can't have it checked).
For what its worth, I tried to find Netflix on the Play Store and it doesn't show up meaning the Play Store is definitely detecting something is off.
Is there a way to make Play Store show up on the list of Magisk hide apps? (its not showing up at the moment)
Click to expand...
Click to collapse
You need to enable Show System Apps on the MagiskHide tab.

yot2703 said:
You need to enable Show System Apps on the MagiskHide tab.
Click to expand...
Click to collapse
Hi,
I enabled "show system apps", which made "google framework services" and "google play store" show up. I tried adding them to the magisk hide list then rebooting the phone.
Unfortunately, I am still getting a "ctsProfile: false" result when I run a SafetyNet check (basicIntegrity: true passes).
Thanks for the suggestions so far.
Do you have anything else I could try or does anything I might have missed come to mind?

I think you have a bad fingerprint. The answer you're looking for might be in the following link.
https://github.com/Magisk-Modules-R...ices-fingerprint-to-pass-the-ctsprofile-check

Ended up installing Magisk Hide Props Config module. For future reference the answers to my questions in the original post:
MagiskHidePropsConfig module -> Change fingerprint on the device to a certified one.
Also, how do I flash the busybox installer if I need to install MagiskHidePropsConfig? -> Put the zip file on your phone's storage and install as a module from Magisk Manager.
Do I need to boot into TWRP? -> No need to boot into TWRP, installation can be done via Magisk Manager module installer.

digitalsonic said:
Ended up installing Magisk Hide Props Config module. For future reference the answers to my questions in the original post:
MagiskHidePropsConfig module -> Change fingerprint on the device to a certified one.
Also, how do I flash the busybox installer if I need to install MagiskHidePropsConfig? -> Put the zip file on your phone's storage and install as a module from Magisk Manager.
Do I need to boot into TWRP? -> No need to boot into TWRP, installation can be done via Magisk Manager module installer.
Click to expand...
Click to collapse
Just about to try this out myself - which option did you choose if you don't mind me asking?
The one I was going to choose looks to be what I already have? I wanted to confirm before proceeding. TIA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A6013 using Tapatalk

Nexus 6p - LineageOS 15.1 - Magisk - CTS Profile check failin

Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

StyleM said:
Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
Click to expand...
Click to collapse
Magisk looks like it's installed correctly.
Click on module icon
Try installing MagiskHide Props Config Module

sd_shadow said:
Magisk looks like it's installed correctly.
Click on module icon
View attachment 5324475
Try installing MagiskHide Props Config Module
Click to expand...
Click to collapse
i did that (in description)

fyi, i even flashed the original the stock android image and tried the process all over again (multiple times)