||| Why this guide? |||
Since the "EdXposed" project doesn't reveice the attention it should get in our device section, I decided to make a quick guide for you how to get a Xposed Framework on your OnePlus 6 running Android 9 and 10! :highfive:
I'm not the developer of EdXposed or Riru, nor in any way related to them. Just an ordinary user, who can confirm that it's working on the latest stock OOS 9.x-x with Magisk >18.1 and OOS 10 with a custom Magisk build (20), though not all available Xposed modules work. The list of known working and non-working apps can be found here (spoiler alert: Greenify (beta) and Xprivacylua (beta) are fully working :good - better check that thread before you complain afterwards
If you're asking yourself now, what EdXposed actually is, here's the description of the developer solohsu:
EdXposed: A Riru module trying to provide a ART hooking framework (initially for Android Pie) which delivers consistent APIs with the OG Xposed, leveraging YAHFA hooking framework.
Click to expand...
Click to collapse
But what is Riru?
Riru is a very simple but useful thing. Only requires to replace one system file, it will provide the ability to Riru modules to run their code in apps' or system server's process.
Click to expand...
Click to collapse
Got it? :fingers-crossed:
||| Notes |||
EdXposed is still in beta stage. Not all modules work and some bugs might occur, so please, make backups! At least take a full nandroid backup and save your important data (photos, documents, etc.) from your internal memory in a safe place.
Even though you don't need TWRP for the installation and usage of EdXposed, I'd highly recommend to have it in place for two reasons: 1. To take backups and 2. To be able to flash the EdXposed Uninstaller zip in case something went wrong.
On Android 10, SafetyNet does not pass! I'll update this thread as soon as a fix is available! Also, if you upgrade from 9 to 10, make sure to deactivate or uninstall all Magisk and Xposed modules. Some of them might not be support Android 10 right now, activate them one by one (with reboot), after the whole upgrade process is done. For example: "Audio Modification Library" and/or "Audio Compatibility Patch" *work", but make recording of Whatsapp voice messages fail. Be aware that those issues might occur until all modules are updated to support Android 10.
||| Requirements |||
Android 9:
rooted with Magisk >18.x
optional: TWRP (blu_spark TWRP >3.2.3+ highly recommended)
Android 10:
rooted with custom Magisk 20 by soloshu
unlike on pie, TWRP for Android 10 is needed (blu_spark >=v9.107 recommended)
||| Installation |||
Android 9:
It's quite simple, just follow those steps:
(I flashed everything in magisk, since EdXposed and Riru Core are technically magisk modules)
Download the files mentioned in the downloads for Android 9 section on your phone
Have you done your backup(s)? If not, do it now -just in case!
Flash the (latest) Riru Core zip in Magisk or TWRP (magisk-riru-core-vXX.X.zip)
Flash the (latest) EdXposed zip in Magisk or TWRP (magisk-EdXposed-vX.X.X.X_beta-release.zip; YAHFA highly recommended!)
reboot
Install the EdXposed Installer (EdXposedInstaller_vX.X.X-release.apk)
Done!
Open up the EdXposed Installer and check if the Xposed Framework status is active and "green".
Android 10:
If you had EdXposed on your device on Android 9 and now just want to upgrade to 10, you don't have to install Riru Core and EdXposed Manager if the latest versions were already installed.
Download the files mentioned in the downloads for Android 10 section on your phone
Have you done your backup(s)? If not, do it now -just in case!
reboot to TWRP (blu_spark >=v9.107)
Flash the (latest) custom Magisk build by soloshu in TWRP (>= v20.0(20001); Magisk-v20.x.zip)
reboot
Flash the (latest) Riru Core zip in Magisk or TWRP (>= 19.5; magisk-riru-core-vXX.X.zip)
Flash the (latest) EdXposed zip in Magisk or TWRP (>= v0.4.6.0_beta; magisk-EdXposed-vX.X.X.X_beta-release.zip, YAHFA highly recommended!)
reboot
Open Magisk Manager, go to settings->update channel and paste the this custom path: "https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json"
Install the EdXposed Installer (EdXposedInstaller_vX.X.X-release.apk)
Done!
||| Downloads |||
Android 9:
Riru
EdXposed Installer, Uninstaller and flashable zip
(at the date of publishing this thread, the latest Riru version is v17.1, EdXposed is v0.3.1.2_beta)
Android 10:
Riru
EdXposed Installer, flashable zip
Custom Magisk Build
TWRP blu_spark v9.107
||| Source code / Github links |||
EdXposed
Riru
||| Screenshots |||
{
"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"
}
||| Thanks & Credits |||
@rovo89 - who made all this possible with his Xposed Framework
@topjohnwu - for his awesome Magisk root environment
@solohsu[Github] - for his EdXposed and customized Magisk builds
@Rikka apps[Github] - for their Riru Core
@eng.stk - for his blu_spark TWRP and awesome kernels
@Uraniam9 - for his list of working modules
reserved
Does it pass Safetynet unlike the previous Xposed Magisk modules?
Sent from my OnePlus 6 using XDA Labs
kunalgupta1 said:
Does it pass Safetynet unlike the previous Xposed Magisk modules?
Click to expand...
Click to collapse
Yes
Sent from my OnePlus 6 using XDA Labs
Have xposed on pie since last week and running well.
App running is gravitybox 9.0 beta 2
And no problems with safetynet.
Very interesting indeed. Thanks man! Gonna check it out over the weekend.
No problem on oos 9.04
How are some of the root sensitive apps working, like Android Pay? Will we be able to update some sensitive apps like Netflix and Mario Run in the Play Store?
I just came from the Axon 7 where it was either Xposed or passing SafelyNet, but not both. I'm gonna look into this for sure! Thanks!
HallOfPromise said:
How are some of the root sensitive apps working, like Android Pay? Will we be able to update some sensitive apps like Netflix and Mario Run in the Play Store?
I just came from the Axon 7 where it was either Xposed or passing SafelyNet, but not both. I'm gonna look into this for sure! Thanks!
Click to expand...
Click to collapse
Take a look at the screenshots I posted. SafetyNet passes! And even better, you can "blacklist" specific apps, which means that they're not touched/hooked in any way. Very useful for banking apps or sensitive apps like password-manager :good:
I'm quite sure that you can use Android Pay, though I can't tell for sure since I don't use it. The Xposed gets hardly detected because it "basically" isn't the "pure" XPosed, but a module of Riru. Simply spoken: Riru is a module of Magisk. And EdXposed is a module of Riru
Depressed T.Bear said:
Take a look at the screenshots I posted. SafetyNet passes! And even better, you can "blacklist" specific apps, which means that they're not touched/hooked in any way. Very useful for banking apps or sensitive apps like password-manager :good:
Click to expand...
Click to collapse
I totally missed the screenshots the first time around. Awesome! After I get my OTG extra storage and make a new backup (large backup) I'm gonna jump on this!
Do we have a thread for GravityBox P on our OnePlus 6 and all the things working and not working? I would start one but I'm working and technically shouldn't be doing this haha
HallOfPromise said:
I totally missed the screenshots the first time around. Awesome! After I get my OTG extra storage and make a new backup (large backup) I'm gonna jump on this!
Do we have a thread for GravityBox P on our OnePlus 6 and all the things working and not working? I would start one but I'm working and technically shouldn't be doing this haha
Click to expand...
Click to collapse
Don't worry I added them just recently
Not for our device specifically. In fact I made this guide here because most people didn't even know that there's a Xposed solution for Pie . But according to the thread I mentioned, it's reported to work. And since OxygenOS is quite close to vanilla Android, I'd assume it will work flawlessly
Sent from my OnePlus 6 using XDA Labs
sakerhetz said:
Have xposed on pie since last week and running well.
App running is gravitybox 9.0 beta 2
And no problems with safetynet.
Click to expand...
Click to collapse
In my case i am running amplify, greenify, ... without any problems. But gravitybox throws me startup error "framework not responding" and quits. Do you use an specific vetsion of gravitybox?
(Moderator Edit: reference to Warez removed - as per XDA's Forum Rules)
elmarian756 said:
In my case i am running amplify, greenify, ... without any problems. But gravitybox throws me startup error "framework not responding" and quits. Do you use an specific vetsion of gravitybox?
(Moderator Edit: reference to Warez removed - as per XDA's Forum Rules)
Click to expand...
Click to collapse
Did you enable the module gravitybox in xposed?
And which version of gravitybox do you use?
sakerhetz said:
Have xposed on pie since last week and running well.
App running is gravitybox 9.0 beta 2
And no problems with safetynet.
Click to expand...
Click to collapse
sakerhetz said:
Did you enable the module gravitybox in xposed?
And which version of gravitybox do you use?
Click to expand...
Click to collapse
Wiped dalvik cache and now it works like a charm! I am using version 9.0.0 beta 4
can i
i once flashed aosip 9.0 on my honor 5x(kiwi),and flashed edxposed 0.3.1.2,it works well.
but the rom lag,so i want flash back to 8.1,but failed.
when i reflash the aosip then flash edxposed,i got a "screenshot" --only one shot on screen,and the screen flash of status bar and back key in navibar for every 30seconds.
i tried 0.3.1.7 the same issue,
i tried edxposed uninstaller,it says not detect magisk, flash end with error 1
i don't want to give up this
what can i do
sakerhetz said:
Have xposed on pie since last week and running well.
App running is gravitybox 9.0 beta 2
And no problems with safetynet.
Click to expand...
Click to collapse
hello, Where can i find this module ?
rhabhab said:
hello, Where can i find this module ?
Click to expand...
Click to collapse
https://www.google.nl/amp/s/forum.x...vitybox-v9-0-0-beta-1-android-9-t3908768/amp/
---------- Post added at 09:42 AM ---------- Previous post was at 09:27 AM ----------
booykean said:
can i
i once flashed aosip 9.0 on my honor 5x(kiwi),and flashed edxposed 0.3.1.2,it works well.
but the rom lag,so i want flash back to 8.1,but failed.
when i reflash the aosip then flash edxposed,i got a "screenshot" --only one shot on screen,and the screen flash of status bar and back key in navibar for every 30seconds.
i tried 0.3.1.7 the same issue,
i tried edxposed uninstaller,it says not detect magisk, flash end with error 1
i don't want to give up this
what can i do
Click to expand...
Click to collapse
I assume that you flashed a custom ROM and that doesn't work well with gravitybox for pie.
i have no gravitybox installed
sakerhetz said:
https://www.google.nl/amp/s/forum.x...vitybox-v9-0-0-beta-1-android-9-t3908768/amp/
---------- Post added at 09:42 AM ---------- Previous post was at 09:27 AM ----------
I assume that you flashed a custom ROM and that doesn't work well with gravitybox for pie.
Click to expand...
Click to collapse
gravitybox is available for Android Pie, can someone please test with edxposed https://forum.xda-developers.com/xposed/modules/app-gravitybox-v9-0-0-beta-1-android-9-t3908768
JerryGoyal said:
gravitybox is available for Android Pie, can someone please test with edxposed https://forum.xda-developers.com/xposed/modules/app-gravitybox-v9-0-0-beta-1-android-9-t3908768
Click to expand...
Click to collapse
Been using for a few weeks, works great op6t.. so should be fine on op6, it's the same phone..
Related
Motorola Stock Kernel with f2fs patched and kcal added
Disclaimer: Your warranty is now void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Why this kernel exists:
As many of you know, there is a bug with the f2fs filesystem in the stock kernel which makes it nearly impossible to use systemless modifications (SuperSU, Magisk) on the Moto Z Play. The flaw and its solution are described here.
I started this project for myself to be able to use systemless modifications again, but I hope some of you will find it useful as well. The kernel for Android 6.0 is based on Motorolas source code release (MPN24.104-44) from here and includes security fixes up to december 2016. The Android 7.0 kernel is based on release MMI-NPN25.137-15 with patch date 2017-01. It has been developed and tested with the European model and ROM, but should work on other variants as well as all retail models share the same boot image.
As of patch level 2017-03, Motorola included the f2fs fix in the official kernel. However, I will continue to work on this kernel for those of you who need the verifiedbootstate patch and kcal.
Warning
This kernel is not meant for 7.1.1 and will break your camera and probably more! Once Motorola release the source code you will find an update here.
Features:
f2fs patched to allow systemless modifications to work
kcal color control
Thats all for now, let me know if you need something else ...
Instructions:
If you previously rooted your phone with the chinese TWRP in system mode I would advise to un-root the phone from the SuperSU app and restore a factory image. However, deleting userdata is not necessary except for the SuperSU app. It might not recognize the new systemless mode otherwise.
Optional, unroot via SuperSU app
Reboot to boatloader / fastboot mode
Flash modified TWRP image Flash @Alberto97 latest TWRP from here
Reboot directly into recovery
Optional, remove forced encryption (see below)
Check with TWRP file manager that /data/.supersu is not present, otherwise delete the file.
Flash kernel zip
Flash SuperSU
Reboot the device
Remove forced encryption (optional):
Download attached RemoveForceEnc.zip
Flash file from TWRP
Wipe userdata (in TWRP or use 'fastboot erase userdata' in fastboot mode)
Credits:
Thanks to @Alberto97 for his work on addison.
Thanks to @erfanoabdi and @ryzion for the RemoveForceEnc.zip found on the Moto Z forum (in this post).
@fortunz for testing kcal functionality
Download:
03/22/2017 - Android 7.0.0 Kernel v03: Mega
03/23/2017 - Android 6.0.1 Kernel v03: Mega
Archive:
Modified TWRP: androidfilehost No longer needed, flash latest TWRP from @Alberto97
02/18/2017 - Android 7.0.0 Kernel v02: androidfilehost, Mirror: Mega
02/02/2017 - Android 6.0.1 Kernel v02-test: androidfilehost
01/28/2017 - Android 6.0.1 Kernel v01: androidfilehost
Sources: Github
Changelog:
03/22/2017 | 6.0.1 / 7.0.0 | v3
Added kcal color control. Patch
02/18/2017 | 7.0.0 | v2
Remove verifiedbootstate flag to pass SafetyNet checks. Patch
02/17/2017 | 7.0.0 | v1
Initial release for 7.0
02/02/2017 | 6.0.1 | v2-test
Test build to pass safetynet checks. Removes verifiedbootstate flag. See this patch
01/28/2017 | 6.0.1 | v1
Initial release based in MPN24.104-44 and security bulletins up to december 2016
Is it just enough to flash the sprasechunks ? Is there any need to delete userdata?
Yeah, system sparsechunks should be enough. Additionally, make sure the file '/data/.supersu' does not exist. There was one guide which required the file to force system mode for supersu.
tomparr said:
Yeah, system sparsechunks should be enough. Additionally, make sure the file '/data/.supersu' does not exist. There was one guide which required the file to force system mode for supersu.
Click to expand...
Click to collapse
Great job, it worked, I flashed the lastest SR3-supersu without any issues:good::good::good:
Ran into a bit of trouble, everything flashed without any issues but when I went into the SuperSU APK " no binary is installed" so it seems even though I did flash the sparsechunks , you may need to delete user data.
I was already rooted with the SuperSU that I extracted from the Chinese TWRP.
flashallthetime said:
Great job, it worked, I flashed the lastest SR3-supersu without any issues:good::good::good:
Ran into a bit of trouble, everything flashed without any issues but when I went into the SuperSU APK " no binary is installed" so it seems even though I did flash the sparsechunks , you may need to delete user data.
I was already rooted with the SuperSU that I extracted from the Chinese TWRP.
Click to expand...
Click to collapse
Thanks for testing. Have you tried to delete SuperSU and its app data and flash SR3 again?
Thanks a lot OP, I've been waiting for something like this. I'll give it a go.
tomparr said:
Thanks for testing. Have you tried to delete SuperSU and its app data and flash SR3 again?
Click to expand...
Click to collapse
No I didn't.
Edit: You need to also re-flash the kernel as well as the sparsechunks. It works and I'm rooted with SR3.
Sent from my XT1635-02 using XDA-Developers Legacy app
Hi I have stock reteu with this version twrp of alberto and root with super his SR3 2.79 is this for me? Thank you
{
"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"
}
regards
So if a install this i finally will be able to install adaway? Cause with the root i have i just cant
Sent from my XT1635-02 using XDA-Developers Legacy app
elgringoloco77 said:
So if a install this i finally will be able to install adaway? Cause with the root i have i just cant
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, running AdAway (and Titanium Backup) was the main reason I started building the kernel.
iron maiden said:
Hi I have stock reteu with this version twrp of alberto and root with super his SR3 2.79 is this for me? Thank you
regards
Click to expand...
Click to collapse
Depends, if you are ok with system mode root, you don't need this.
tomparr said:
Depends, if you are ok with system mode root, you don't need this.
Click to expand...
Click to collapse
Hello and how can I know that I do not need this? What is the advantage of doing those steps? I do not know if you understand me, I feel my English, thank you.
regards
iron maiden said:
Hello and how can I know that I do not need this? What is the advantage of doing those steps? I do not know if you understand me, I feel my English, thank you.
regards
Click to expand...
Click to collapse
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
tomparr said:
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
Click to expand...
Click to collapse
Main advantage is that Magisk is supposed to work, and that f2fs is working properly.
Systemless root already does work fine using phh superuser without this kernel.
To have AdAway functionality - which systemless needs SuperSU or Magisk, both don't work without this kernel - you may use dns66 which does not modify hosts, but instead runs a local DNS server. It has very similar functionality and doesn't even need root.
I'd like to have f2fs working, but currently don't have the time to do backup, restore in twrp doesn't work maybe because of broken f2fs, do 4 times update etc. This kernel probably will help me and I thank you very much for publishing it. We'll see when I find the time to test it.
tomparr said:
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
Click to expand...
Click to collapse
Hi and what flash of these? Does magisk work to hide root in some applications? Do I have to reinstall the firmware before doing this process?very thanks
Flash SuperSU / Magisk / Systemless modification
iron maiden said:
Hi and what flash of these? Does magisk work to hide root in some applications? Do I have to reinstall the firmware before doing this process?very thanks
Flash SuperSU / Magisk / Systemless modification
Click to expand...
Click to collapse
hello what supersu, magisk and systemless I have to install
I have the house z I have reflated the stock now would be good time to install this system no?
iron maiden said:
hello what supersu, magisk and systemless I have to install
I have the house z I have reflated the stock now would be good time to install this system no?
Click to expand...
Click to collapse
You can use the regular SuperSU and Magisk versions from here and here.
tomparr said:
You can use the regular SuperSU and Magisk versions from here and here.
Click to expand...
Click to collapse
Hi, okay, this system is running smoothly. And that twrp? thank you very much @tomparr
Something has failed? Install magisk 10.2 and sr3-supersu-v2.79 thanks
Unistalled Sr3 v279 and installer phhsupersu
regards
iron maiden said:
Hi, okay, this system is running smoothly. And that twrp? thank you very much @tomparr
Something has failed? Install magisk 10.2 and sr3-supersu-v2.79 thanks
regards
Click to expand...
Click to collapse
Root and Magisk look fine. The SafetyNet test is required for Android Pay and other "secure" apps. From what I read, it can fail on newer versions when the bootloader is
unlocked. I found a temporary patch for the kernel in the OnePlus forum which might solve it. I'll prepare a test version for you soon.
tomparr said:
Root and Magisk look fine. The SafetyNet test is required for Android Pay and other "secure" apps. From what I read, it can fail on newer versions when the bootloader is
unlocked. I found a temporary patch for the kernel in the OnePlus forum which might solve it. I'll prepare a test version for you soon.
Click to expand...
Click to collapse
Hello ok very very thanks for job
regards
The program allows to block undesirable incoming and outgoing calls and SMS. There is a support Dual SIM phones. The rights of root are necessary for full functioning.
Blocking is carried out at system level, the program doesn't miss the first call, the screen isn't lit and there is no window of a dialer.
Features:
- Blocking incoming SMS and MMS on Android 4.4 above without appointment as its program for SMS processing.
- Blocking of outgoing calls and SMS.
- Support the Dual SIM phones with opportunity to set various parameters of blocking for everyone
SIM.
- Private conversation. Possibility of replacing the incoming call number.
Screenshots:
{
"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"
}
To use the program on Android 7.x with the latest versions of SuperSU, you need to put file radio.sh https://goo.gl/BhjW3J to folder /su/su.d, set permission to read and execute and restart the phone.
When using MagiskSU before Oreo, use Magisk-module magisk-radiofix-script https://goo.gl/e7usCV or you can to put the file radio_magisksu.sh https://goo.gl/jsTSvQ to /magisk/.core/service.d(/sbin/.core/img/.core/service.d for Magisk 16.3+) folder, set permission to read and execute and restart the phone.
You do not need any magisk module and the radio.sh file for Android 8+.
If you have any ideas, suggestions or you found a bug/mistake, let me know.
Email: [email protected]
Downloads:
Google Play https://play.google.com/store/apps/details?id=com.mdnsoft.callsmsmanager
Google did not allow to use permissions for SMS and CallLog in version of the program from Google Play.
You can download the full version or RCSMModule for the version from Google Play.
Full version
1.23 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.23.apk
-Fixes for Android 12
-Improvements and fixes
1.22 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.22.apk
1.21 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.21.apk
1.20 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.20.apk
1.19 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.19.apk
1.18 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.18.apk
1.17.2 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.17.2.apk
1.17.1 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.17.1.apk
1.17 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.17.apk
RCSMModule for version from Google Play https://www.mdnsoft.ru/Files/RootCallSMSManager/RCSMModule1.0.apk
No issues with 8.1.0 a root call\sms blocker that works well,
thanks mdn80.
This program works great. I did support Root call Blocker and Private space but neither support Magisk and I don't think the developer has any interest in so. Root Call Manager is the perfect replacement for both and works great with Magisk on my Mi Note 2 with the new Global Rom 9. Just needs a good online English manual to describe all of the settings.
Hello
I have a rooted galaxy s9 but i dont have the option To bo answer method block
I dont understand why the app works only the first time I receive call. Reject method (blacklist) for calls.
I have to delete app datas and reconfigure it each time...
App use with xposed and magisk modules, lineageOs 14.1
Thanks
Envoyé de mon GT-I9506 en utilisant Tapatalk
I Could not get it to work on Lineage 15.1 z00t,
tried with latest SU (2.82) and Radio.sh the same way which worked perfectly on same devices with 14.1 lineage ,
then Tried as Beta Tester, and later with latest Xposed Framework installed on device.
under About "Xposed" is mentioned in red, am i missing a module or any install process?
i've noticed that if i changed Reject on blacklist to anything else such as "kill" or "mute" the call is answered automatically upon receiving it.
also missing the functionality for restarting and disabling service which was great with earlier version.
Great APP- the only one that works on Qualcomm dual sim, hopeful i'll get it to work on Lineage 15.1 so i can permanently update to Oreo.
jeepcook said:
I dont understand why the app works only the first time I receive call. Reject method (blacklist) for calls.
I have to delete app datas and reconfigure it each time...
App use with xposed and magisk modules, lineageOs 14.1
Thanks
Envoyé de mon GT-I9506 en utilisant Tapatalk
Click to expand...
Click to collapse
You added program to energy saving exceptions? Write please to [email protected] if you have any problems with program, I need logs.
z00tme said:
I Could not get it to work on Lineage 15.1 z00t,
tried with latest SU (2.82) and Radio.sh the same way which worked perfectly on same devices with 14.1 lineage ,
then Tried as Beta Tester, and later with latest Xposed Framework installed on device.
under About "Xposed" is mentioned in red, am i missing a module or any install process?
i've noticed that if i changed Reject on blacklist to anything else such as "kill" or "mute" the call is answered automatically upon receiving it.
also missing the functionality for restarting and disabling service which was great with earlier version.
Great APP- the only one that works on Qualcomm dual sim, hopeful i'll get it to work on Lineage 15.1 so i can permanently update to Oreo.
Click to expand...
Click to collapse
You need Xposed for full work app with Oreo. You must enable program module in Xposed Installer.
Write please to [email protected] if you have any problems with program or questions.
RBJ26 said:
No issues with 8.1.0 a root call\sms blocker that works well,
thanks mdn80.
Click to expand...
Click to collapse
how did you get it to work, mine is not working on Oreo 8.1
zaffar.mughal said:
how did you get it to work, mine is not working on Oreo 8.1
Click to expand...
Click to collapse
You need Xposed for full work app with Oreo.
Write please to [email protected] if you have any problems with program or questions, I need logs.
mdn80 said:
You need Xposed for full work app with Oreo.
Write please to [email protected] if you have any problems with program or questions, I need logs.
Click to expand...
Click to collapse
Yeah, this is pretty broken on 8.1 (Google Pixel). Xposed is activated and green text.
YandereSan said:
Yeah, this is pretty broken on 8.1 (Google Pixel). Xposed is activated and green text.
Click to expand...
Click to collapse
Also try to put daw "Process Voip calls" in program settings.
So to have it work with Oreo 8.1 (with Magisk), you need to install Xposed systemless. Do you need any additiaonl Xposed modules? Do you also have to install the Magisk module that's mentioned for Android 7 (magisk-radiofix-script_v1)?
solara1973 said:
So to have it work with Oreo 8.1 (with Magisk), you need to install Xposed systemless. Do you need any additiaonl Xposed modules? Do you also have to install the Magisk module that's mentioned for Android 7 (magisk-radiofix-script_v1)?
Click to expand...
Click to collapse
You do not need any additiaonl Xposed modules, Xposed module is built into the program. You do not need to install any Magisk modules for Oreo.
mdn80 said:
You do not need any additiaonl Xposed modules, Xposed module is built into the program. You do not need to install any Magisk modules for Oreo.
Click to expand...
Click to collapse
So you mean we just check the 'Xposed' checkbox under System settings for the app? That's it? I think you meant I do not need any additional Xposed module, but I still need to install Xposed via its installer or through the Magisk Xposed module (I am using Magisk), right?
solara1973 said:
but I still need to install Xposed via its installer or through the Magisk Xposed module (I am using Magisk), right?
Click to expand...
Click to collapse
Yes, you need to install Xposed and activate program Xposed module in Xposed Installer.
mdn80 said:
Yes, you need to install Xposed and activate program Xposed module in Xposed Installer.
Click to expand...
Click to collapse
Well tried to install systemless Xposed from within Magisk but got bootloop. I probably didn't do it right. Formatted my data and reloaded all my app. Side note: Remove phone password before rebooting after installing anything that might cause bootloops! TWRP can't decrypt if you use a Pattern. So I couldn't disable Xposed easily since I couldn't ADB or manually create that Disable file. I also couldn't get it to disable itself by pushing buttons during the boot process.
Turns out Root Call SMS works fine as it was! Oreo 8.1 rooted with Magisk with latest security updates through May on Moto x4. No other modules installed, no Xposed installed and is unchecked in settings. I tested calling and texting via online websites and it blocks them fine. I set it so I get no notifications but it does show up logged in the Journal.
solara1973 said:
I set it so I get no notifications but it does show up logged in the Journal.
Click to expand...
Click to collapse
You can set deleting calls from system journal in program settings.
solara1973 said:
So to have it work with Oreo 8.1 (with Magisk), you need to install Xposed systemless.
Click to expand...
Click to collapse
Really? So Magisk + Xposed via TWRP on Oreo 8.1 doesn't work? It has to be Systemless Xposed? @mdn80
I guess it might be worth a shot, because right now Root Call SMS Manager is behaving like it doesn't register Xposed at all, even though it's clearly working with my other modules.
YandereSan said:
Really? So Magisk + Xposed via TWRP on Oreo 8.1 doesn't work? It has to be Systemless Xposed? @mdn80
I guess it might be worth a shot, because right now Root Call SMS Manager is behaving like it doesn't register Xposed at all, even though it's clearly working with my other modules.
Click to expand...
Click to collapse
Write please to [email protected] if you have any questions or problems with program.
I just upgraded to Oxygen OS 10.0.1.GM57AA from 9.5.8 (if I remember rightly, from India ).
I tried the following with Magisk 19.3 and 20:
1. No other Magisk modules only Riru Core - no problems.
2. Install Riru latest Ed xposed YAHFA. Device didn't get booted. Booted into TWRP side loaded Magisk Manager, set to core only mode Magisk and rebooted into system and uninstall YAHFA.
3. Tried step 2 with latest Sandhook. Same result
4. Uninstalled all Magisk modules and From EdXposed manager installed Riru core. No problem. Installing YAHFA or Sandhook from Manager, same result - device doesn't boot and spinning dots continue
Has anybody got it working? I searched the forum and elsewhere but couldn't find anything related to our device.
Please explain how you did it
Edit 1
1. Flashing Riru Core and Riru YAHFA/ Sandhook from TWRP (this worked for One Plus 7 Pro) didn't help. Same story of stuck at boot animation.
2. Flashing YAHFA from GravityBox for 10 also had the same problem.
3.. Flashing Canary version of YAHFA (v0.4.5.5_beta(4470) worked and I am able to use Xposed modules ! I don't know how stable this would be but at least I have got the modules I need like XPrivacy Lua installed and working. I didn't try Sandhook because I always found YAHFA to be stabler though slower.
Edit2
Canary version above created drag and gravitybox had a lot of issues. Credit to @C3C076 who pointed out to use YAHFA modified from here https://forum.xda-developers.com/showpost.php?p=80392829&postcount=30 and use the installer 2.2.4 from here https://github.com/solohsu/XposedInstaller/releases/tag/Ed_v2.2.4.
ALL fine
Please update what method you used and which modules used to help others . Thanks
{
"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"
}
Prerequisites:
Magisk 20.1
Android 10 set to English (US)
QuickSwitch module
Pixel Launcher apk
Device Personalization Services module
Steps:
Install Pixel Launcher apk but do not set it as your default launcher yet.
Install QuickSwitch Magisk module in Manager. Reboot
Open QuickSwitch app and select Pixel Launcher as recents provider. Reboot. Set Pixel Launcher as your default launcher.
Install Device Personalization Services Magisk module. Reboot.
Open Pixel Launcher settings. Select Suggestions and enable both options. Done.
I can't download device personalization module
[email protected] said:
I can't download device personalization module
Click to expand...
Click to collapse
I replaced the link with mirror. Please try again.
Using your Device Personalization Service module results in a bootloop. Had to uninstall and reinstall Magisk to get it booting again.
Anyone else?
I got bootloops after flashing the Device Personalization Service module. Had to delete the folder from magisk folder in TWRP recovery to boot onto system.
Bootlooped here too
Only installed the Pixel Launcher and used Quick Switch, works like it should.
Funny, it even automatically put my icons and widgets exactly where they was on my previous ROM, wierd !
Totone56 said:
Only installed the Pixel Launcher and used Quick Switch, works like it should.
Funny, it even automatically put my icons and widgets exactly where they was on my previous ROM, wierd !
Click to expand...
Click to collapse
Correct me if I'm wrong, but without the Device Personalization module thing, the dock when you swipe up to Recents is the same dock from your home screen, right? Not the frequently-used dock?
adeklipse said:
Correct me if I'm wrong, but without the Device Personalization module thing, the dock when you swipe up to Recents is the same dock from your home screen, right? Not the frequently-used dock?
Click to expand...
Click to collapse
Looks like it, yep ! Probably also enables the copy/paste feature, i can't get it to work like in the first screenshot.
Hey guys, just a heads up, it appears as if the Device Personalization Module needs to be installed via TWRP and not Magisk. I've tried this multiple times on both a 6 and a 6t, and if you flash the module via Magisk, you'll get a bootloop, but if you flash it via TWRP, everything works fine. OP's guide is a bit confusing (when I saw "Install Device Personalization Services Magisk module", I assumed it meant VIA magisk), but I figured it out, and the recent apps and copy and paste work great if you do it this way. Thank you OP for posting the guide, I'd maybe amend the part about the DPS Module to make it clear that it needs to be installed via TWRP, but other than that, you've made me love my phone even more. Oxygen OS with a fully integrated Pixel Launcher is maybe the best phone experience I could ask for.
DFSVegas said:
Hey guys, just a heads up, it appears as if the Device Personalization Module needs to be installed via TWRP and not Magisk. I've tried this multiple times on both a 6 and a 6t, and if you flash the module via Magisk, you'll get a bootloop, but if you flash it via TWRP, everything works fine. OP's guide is a bit confusing (when I saw "Install Device Personalization Services Magisk module", I assumed it meant VIA magisk), but I figured it out, and the recent apps and copy and paste work great if you do it this way. Thank you OP for posting the guide, I'd maybe amend the part about the DPS Module to make it clear that it needs to be installed via TWRP, but other than that, you've made me love my phone even more. Oxygen OS with a fully integrated Pixel Launcher is maybe the best phone experience I could ask for.
Click to expand...
Click to collapse
I flashed in TWRP 3.3.1-70 and bootlooped. Maybe it's because I'm on OnePlus 7 Pro OOS 10
You can uninstall the module with TWRP if you go to /data/adb/modules, in case it bootloops.
Also, maybe the reason for the bootloop is because i have Lawnchair installed. Will experiment an will tell ya
Edit: Not related to Lawnchair
robertelam83 said:
I flashed in TWRP 3.3.1-70 and bootlooped. Maybe it's because I'm on OnePlus 7 Pro OOS 10
Click to expand...
Click to collapse
Same here. Repeated and got same result. Just doesn't seem to work on OP7pro on latest beta for whatever reason...
Out of curiosity, why wouldn't this work for android 9?
DFSVegas said:
Hey guys, just a heads up, it appears as if the Device Personalization Module needs to be installed via TWRP and not Magisk. I've tried this multiple times on both a 6 and a 6t, and if you flash the module via Magisk, you'll get a bootloop, but if you flash it via TWRP, everything works fine. OP's guide is a bit confusing (when I saw "Install Device Personalization Services Magisk module", I assumed it meant VIA magisk), but I figured it out, and the recent apps and copy and paste work great if you do it this way. Thank you OP for posting the guide, I'd maybe amend the part about the DPS Module to make it clear that it needs to be installed via TWRP, but other than that, you've made me love my phone even more. Oxygen OS with a fully integrated Pixel Launcher is maybe the best phone experience I could ask for.
Click to expand...
Click to collapse
I tried to flash it in TWRP on my 6T and it still caused bootloop
It looks like this Module isn't granting all of the permissions needed by Device Personalization Services. Android crashes if any requested priv-app permissions aren't in the priv-app permission whitelist. From the logcat that one user sent me:
Code:
11-26 16:46:16.856 8439 8439 E System : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.as: android.permission.CAPTURE_MEDIA_OUTPUT, com.google.android.as: android.permission.MONITOR_DEFAULT_SMS_PACKAGE, com.google.android.as: android.permission.CAPTURE_AUDIO_HOTWORD, com.google.android.as: android.permission.WRITE_SECURE_SETTINGS, com.google.android.as: android.permission.MODIFY_AUDIO_ROUTING, com.google.android.as: android.permission.LOCATION_HARDWARE, com.google.android.as: android.permission.MODIFY_PHONE_STATE, com.google.android.as: android.permission.MANAGE_SOUND_TRIGGER, com.google.android.as: android.permission.REQUEST_NOTIFICATION_ASSISTANT_SERVICE, com.google.android.as: android.permission.CAPTURE_AUDIO_OUTPUT, com.google.android.as: android.permission.READ_OEM_UNLOCK_STATE, com.google.android.as: android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME, com.google.android.as: android.permission.CONTROL_INCALL_EXPERIENCE}
I have added these permissions to the privapp-permissions whitelist. Please try the module attached to this post.
MishaalRahman said:
It looks like this Module isn't granting all of the permissions needed by Device Personalization Services. Android crashes if any requested priv-app permissions aren't in the priv-app permission whitelist. From the logcat that one user sent me:
Code:
11-26 16:46:16.856 8439 8439 E System : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.as: android.permission.CAPTURE_MEDIA_OUTPUT, com.google.android.as: android.permission.MONITOR_DEFAULT_SMS_PACKAGE, com.google.android.as: android.permission.CAPTURE_AUDIO_HOTWORD, com.google.android.as: android.permission.WRITE_SECURE_SETTINGS, com.google.android.as: android.permission.MODIFY_AUDIO_ROUTING, com.google.android.as: android.permission.LOCATION_HARDWARE, com.google.android.as: android.permission.MODIFY_PHONE_STATE, com.google.android.as: android.permission.MANAGE_SOUND_TRIGGER, com.google.android.as: android.permission.REQUEST_NOTIFICATION_ASSISTANT_SERVICE, com.google.android.as: android.permission.CAPTURE_AUDIO_OUTPUT, com.google.android.as: android.permission.READ_OEM_UNLOCK_STATE, com.google.android.as: android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME, com.google.android.as: android.permission.CONTROL_INCALL_EXPERIENCE}
I have added these permissions to the privapp-permissions whitelist. Please try the module attached to this post.
Click to expand...
Click to collapse
It Boots! thanks UwU. Now onto trying that whole thing
adeklipse said:
Using your Device Personalization Service module results in a bootloop. Had to uninstall and reinstall Magisk to get it booting again.
Anyone else?
Click to expand...
Click to collapse
Simpa539 said:
I got bootloops after flashing the Device Personalization Service module. Had to delete the folder from magisk folder in TWRP recovery to boot onto system.
Click to expand...
Click to collapse
[email protected] said:
Bootlooped here too
Click to expand...
Click to collapse
DFSVegas said:
Hey guys, just a heads up, it appears as if the Device Personalization Module needs to be installed via TWRP and not Magisk. I've tried this multiple times on both a 6 and a 6t, and if you flash the module via Magisk, you'll get a bootloop, but if you flash it via TWRP, everything works fine. OP's guide is a bit confusing (when I saw "Install Device Personalization Services Magisk module", I assumed it meant VIA magisk), but I figured it out, and the recent apps and copy and paste work great if you do it this way. Thank you OP for posting the guide, I'd maybe amend the part about the DPS Module to make it clear that it needs to be installed via TWRP, but other than that, you've made me love my phone even more. Oxygen OS with a fully integrated Pixel Launcher is maybe the best phone experience I could ask for.
Click to expand...
Click to collapse
robertelam83 said:
I flashed in TWRP 3.3.1-70 and bootlooped. Maybe it's because I'm on OnePlus 7 Pro OOS 10
Click to expand...
Click to collapse
xxBrun0xx said:
Same here. Repeated and got same result. Just doesn't seem to work on OP7pro on latest beta for whatever reason...
Click to expand...
Click to collapse
zhenliang1102 said:
I tried to flash it in TWRP on my 6T and it still caused bootloop
Click to expand...
Click to collapse
For those of you who had bootloop issues, the Device Personalization Services Magisk Module in the OP wasn't made correctly. Please try the one I added here: https://forum.xda-developers.com/showpost.php?p=81023021&postcount=16
LuciferIII said:
It looks like this Module isn't granting all of the permissions needed by Device Personalization Services. Android crashes if any requested priv-app permissions aren't in the priv-app permission whitelist. From the logcat that one user sent me:
It Boots! thanks UwU. Now onto trying that whole thing
Click to expand...
Click to collapse
Did you flash thru magisk or TWRP?
robertelam83 said:
Did you flash thru magisk or TWRP?
Click to expand...
Click to collapse
It's a Magisk Module, so flash it through Magisk Manager.
Hi,
I'm thinking of upgrading to android 11 but I won't do it without the option of using FingerFace for those apps I have that are not using the newer api's for biometric authentication. Has anyone got FingerFace working on Android 11?
yes it does work. I'm on 11 beta 3 and fingerface works, but you have to install the prereleased Riru-edxposed for android R or else you'll bootloop when you install edxposed and reboot. That's what I experienced unless there's a fix I don't know about. However, you might not need xposed or fingerface anymore. I found that the 2 apps I needed fingerface for - Lastpass and Chase app - they've since updated so that you can use face authentication.
neo_lithic3K said:
yes it does work. I'm on 11 beta 3 and fingerface works, but you have to install the prereleased Riru-edxposed for android R or else you'll bootloop when you install edxposed and reboot. That's what I experienced unless there's a fix I don't know about. However, you might not need xposed or fingerface anymore. I found that the 2 apps I needed fingerface for - Lastpass and Chase app - they've since updated so that you can use face authentication.
Click to expand...
Click to collapse
You have the links for riru edxposed for Android R?
You'll need to install Edxposed manager first. Then Go to the third tab called Canary. Select the v0.5.0.6 for android r option and click install. It'll download a file to your phone that you install as a module in magisk. That's how I did it; don't know if there's an easier way
Jiggs82 said:
You have the links for riru edxposed for Android R?
Click to expand...
Click to collapse
This worked for me for release Android 11.
It's pretty hit and miss on what Xposed modules work properly, but FingerFace works.
PSA, do not enable Xposed functionality for MaxLock by Maxr1998... you'll never get to your lockscreen until you somehow disable it.
neo_lithic3K said:
You'll need to install Edxposed manager first. Then Go to the third tab called Canary. Select the v0.5.0.6 for android r option and click install. It'll download a file to your phone that you install as a module in magisk. That's how I did it; don't know if there's an easier way
Click to expand...
Click to collapse
I updated to 11 via fastboot and factory images & magisk. You know, the usual process. But when I went to edxposed it said framework not active. Using latest canary magisk & canary edxposed v0506. I figured it wasn't working for 11 yet (I didn't try and of the 11 Betas) so I rolled back to the July update any help?
I tried Sandhook because I was experimenting... it never worked. Normally I use YAHFA hooking and it worked fine here.
This worked for me on both 11 beta 3 and 11 stable. After you downloaded canary edxposed v0.5.0.6., did you manually install it into magisk using "Install from storage?" Basically:
1) Open Magisk manager canary and go to the Modules page.
2) Click Search and look for: Riru - core. Install it once you find it. Don't reboot.
3) While you're still in Magisk Manager's Modules page, click on "Install from storage" at the top. Select and install the 0.5.0.6. file you downloaded from edxposed earlier.
4) Riru-Edxposed v0.5.0.6. android_r will appear as an installed module. (I installed the sandhook version.)
5) On the safe side, you should probably uninstall any unactivated xposed modules ... if you're able to. This way you're rebooting without any xposed modules installed. I've had a few times where the module wasn't compatible and I was bootlooped.
6) Reboot phone. and both magisk and edxposed should be active.
Suavie103 said:
I updated to 11 via fastboot and factory images & magisk. You know, the usual process. But when I went to edxposed it said framework not active. Using latest canary magisk & canary edxposed v0506. I figured it wasn't working for 11 yet (I didn't try and of the 11 Betas) so I rolled back to the July update any help?
Click to expand...
Click to collapse
neo_lithic3K said:
yes it does work. I'm on 11 beta 3 and fingerface works, but you have to install the prereleased Riru-edxposed for android R or else you'll bootloop when you install edxposed and reboot. That's what I experienced unless there's a fix I don't know about. However, you might not need xposed or fingerface anymore. I found that the 2 apps I needed fingerface for - Lastpass and Chase app - they've since updated so that you can use face authentication.
Click to expand...
Click to collapse
Thank you! For some reason I just saw this post had replies now ?
Just installed and it's working great ?
neo_lithic3K said:
This worked for me on both 11 beta 3 and 11 stable. After you downloaded canary edxposed v0.5.0.6., did you manually install it into magisk using "Install from storage?" Basically:
1) Open Magisk manager canary and go to the Modules page.
2) Click Search and look for: Riru - core. Install it once you find it. Don't reboot.
3) While you're still in Magisk Manager's Modules page, click on "Install from storage" at the top. Select and install the 0.5.0.6. file you downloaded from edxposed earlier.
4) Riru-Edxposed v0.5.0.6. android_r will appear as an installed module. (I installed the sandhook version.)
5) On the safe side, you should probably uninstall any unactivated xposed modules ... if you're able to. This way you're rebooting without any xposed modules installed. I've had a few times where the module wasn't compatible and I was bootlooped.
6) Reboot phone. and both magisk and edxposed should be active.
Click to expand...
Click to collapse
What edxposed mods do you use. I use gravity box. But I don't think it's supporting 11 yet.
Yeah, GravityBox for 11 hasn't been released yet. I use fingerface, AFwall+, and Root calll sms manager.
Suavie103 said:
What edxposed mods do you use. I use gravity box. But I don't think it's supporting 11 yet.
Click to expand...
Click to collapse
Any chance you have a link to the 5.0.6? i cannot seem to find it
EDIT: Figured it out
neo_lithic3K said:
This worked for me on both 11 beta 3 and 11 stable. After you downloaded canary edxposed v0.5.0.6., did you manually install it into magisk using "Install from storage?" Basically:
1) Open Magisk manager canary and go to the Modules page.
2) Click Search and look for: Riru - core. Install it once you find it. Don't reboot.
3) While you're still in Magisk Manager's Modules page, click on "Install from storage" at the top. Select and install the 0.5.0.6. file you downloaded from edxposed earlier.
4) Riru-Edxposed v0.5.0.6. android_r will appear as an installed module. (I installed the sandhook version.)
5) On the safe side, you should probably uninstall any unactivated xposed modules ... if you're able to. This way you're rebooting without any xposed modules installed. I've had a few times where the module wasn't compatible and I was bootlooped.
6) Reboot phone. and both magisk and edxposed should be active.
Click to expand...
Click to collapse
Just curious what everyone's safetynet status is after having edxposed active on 11? I have it with fingerface and I'm failing CTS profile and basic integrity. If I remove edxposed, I'm back to passing everything. I have the "Pass SafetyNet" option enabled in edxposed manager also.
1dopewrx05 said:
Just curious what everyone's safetynet status is after having edxposed active on 11? I have it with fingerface and I'm failing CTS profile and basic integrity. If I remove edxposed, I'm back to passing everything. I have the "Pass SafetyNet" option enabled in edxposed manager also.
Click to expand...
Click to collapse
I found a flashable magisk mod that allows my pixel 4 xl to pass safety net and cts profile. However my eval type comes back "BASIC" forgot what it means but I'll post the forum link where I found it as well.. Running Android 11, September security patch, stock root & also Gpay works. The mod gives me no issues, try it out. I'll post it in a drive link.
https://forum.xda-developers.com/ap...systemless-t3432382/post83028387#post83028387
https://drive.google.com/file/d/152l4_qIQ7VzSzUpFnNc3Eh61GV7Hgrj4/view?usp=drivesdk
{
"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"
}
Suavie103 said:
I found a flashable magisk mod that allows my pixel 4 xl to pass safety net and cts profile. However my eval type comes back "BASIC" forgot what it means but I'll post the forum link where I found it as well.. Running Android 11, September security patch, stock root & also Gpay works. The mod gives me no issues, try it out. I'll post it in a drive link.
https://forum.xda-developers.com/ap...systemless-t3432382/post83028387#post83028387
https://drive.google.com/file/d/152l4_qIQ7VzSzUpFnNc3Eh61GV7Hgrj4/view?usp=drivesdk
Click to expand...
Click to collapse
That's extremely strange for me, I use this module as well (have been even before trying edxposed) and as soon as I install the 2 edxposed modules to get xposed set up, I fail safetynet. With the hardware bypass module installed or not installed, I automatically fail safetynet when edxposed is installed on my phone.
I have Magisk (21.3), EdXposed (0.5.0.6), Fingerface (1.1.0) enabled, however I cannot see it working in an application whatsoever, everyone informs me that my device does not support fingerprint Android 11, November update ... Could someone tell me how to adjust?
Haylander Landim said:
I have Magisk (21.3), EdXposed (0.5.0.6), Fingerface (1.1.0) enabled, however I cannot see it working in an application whatsoever, everyone informs me that my device does not support fingerprint Android 11, November update ... Could someone tell me how to adjust?
Click to expand...
Click to collapse
I have the same problem, I think it is the November update :crying:
It's not the November update alone. Fingerface still can work with the coral-rp1a.201105.002 update.
Haylander Landim said:
I have Magisk (21.3), EdXposed (0.5.0.6), Fingerface (1.1.0) enabled, however I cannot see it working in an application whatsoever, everyone informs me that my device does not support fingerprint Android 11, November update ... Could someone tell me how to adjust?
Click to expand...
Click to collapse
Got it!
I removed EdXposed, Magisk and restored the boot.img.
That done:
Installed:
Magisk (Canary 21101)
** restarted the device
MagiskHide Props Config (Latest version)
Systemless Hosts (Latest version)
** restarted the device
Riru (Riru - Core) (21.2)
** restarted the device
Riru - EdXposed (0.5.0.6-android_r (4561) (YAHFA)
** restarted the device
HiddenCore Module (Latest version)
Fingerface (1.1.1)
In MagiskHide I selected, all the way around, Google apps, searching for "google" in the search field
In EdXposed I enabled App List Mode and Pass SafetyNet
At the moment Fingerface works perfectly and SafetyNet has passed!
Video