Develop Bugs

[G4/G4 Plus] How to Install Magisk and pass safetynet?

Disclaimer
Your warranty is now void. I am not responsible if this in anyway bricks your device or anything else that might go wrong and you cant restore it back. It is assumed that you are familiar with TWRP environment and fastboot in case you need to restore stock.
Click to expand...
Click to collapse
This was last updated on 07/02/2017
This guide will tell you how to install magisk (or magiskify as the app calls it) in order to make systemless mods possible for everything. The thing about magisk is as everything is systemless you can just uninstall magisk in the end and take an ota update without having to worry about what in your system had changed. For custom roms, though not as important, systemless mods are useful for stuff like passing safetynet.
For G4/G4 plus there is no support for Android Pay(at least where I live as there is no h/w for NFC) but various banking apps and apps like Pokemon Go.
First of all, if you want to pass safetynet you will need to use the MagiskSU method to root. This root is based on phh Superuser.
This means if you have anything like SuperSU or phh Superuser then you need to unroot first. Magisk will still work if its systemless but safetynet will not.
Also if you have Xposed installed and enabled, then it will not pass safetynet.
Requirements
1. Unlocked bootloader
2. TWRP installed
This is untested in stock NPJ25-93.11/12/14. If someone can test and report I can update this.
Please flash a custom kernel like elementalX if you are on stock rom
If you are stuck in a bootloop the you need to restore your current boot.img and everything will return back to as it was.
Steps
Take a TWRP backup of current rom. Just the boot image should be enough but everything will make it safer.
1. If you are using a custom rom, I recommend you start from a fresh flash. A dirty flash works as well.
A clean boot.img is recommended as debugging is more difficult without it.
A unrooted rom (Like official Lineage-OS) is best but if you are using a pre-rooted rom then you would need to use the UnSU script by osm0sis (tested on unofficial Lineage by Silesh.Nair)
Get UnSU script from here:
https://forum.xda-developers.com/showthread.php?t=2239421
https://forum.xda-developers.com/showpost.php?p=63615067
2. Download the latest magisk zip and uninstaller from the Magisk release thread.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. After flashing your ROM (or your clean stock rom if you will), flash the magisk zip using TWRP. If your rom is unrooted, Magisk will provide a root solution. If you are rooted with systemless SuperSU, magisk integrates itself there but you will not pass safetynet.
4. Reboot and install magisk manager from play store. Enable Magisk Hide. You can pass safetynet now.
Magisk also supports systemless host files(for Adaway) and busybox support from the app itself. You can just enable and reboot.
If you are on MM, then you can install xposed through magisk itself(but no safetynet support in this case)
Also magisk already has ports of Viper4Android as well. Creating your own mod is simple as well. For further guide search in the Magisk forum. Excellent guides are published there.
Credits:
topjohnwu for Magisk and MagiskSU development
osm0sis for unSU script
shreps for porting TWRP
mrinmaydhar for kernel info
None of this is my work. All I did was compile it so that it becomes easier for others.
If I missed anything please remind me. This is my first thread so everything might not be smoothest.

Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.

mrinmaydhar said:
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
Click to expand...
Click to collapse
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.

guessingagain said:
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
Click to expand...
Click to collapse
So without custom kernel, it bootloops. Any custom kernel would do

mrinmaydhar said:
So without custom kernel, it bootloops. Any custom kernel would do
Click to expand...
Click to collapse
OP updated. thanks for this info.

I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu

aSuperSaiyanG0D said:
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
Click to expand...
Click to collapse
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.

mrinmaydhar said:
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
Click to expand...
Click to collapse
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?

aSuperSaiyanG0D said:
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
Click to expand...
Click to collapse
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?

guessingagain said:
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
Click to expand...
Click to collapse
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error

If I do a ROM update do I need to unSU and flash Magisk again?

Covalex said:
If I do a ROM update do I need to unSU and flash Magisk again?
Click to expand...
Click to collapse
As every ROM update flashes a clean boot.img it's necessary to flash magisk again. If your ROM comes prerooted you need to unsu otherwise not needed.
But you have to flash magisk Everytime after a ROM update. As long as you don't uninstall before updating, all your settings should be fine though.

aSuperSaiyanG0D said:
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
Click to expand...
Click to collapse
Did ElementalX help? Any problems after that?

guessingagain said:
Did ElementalX help? Any problems after that?
Click to expand...
Click to collapse
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?

aSuperSaiyanG0D said:
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
Click to expand...
Click to collapse
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).

guessingagain said:
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
Click to expand...
Click to collapse
Yes titanium backup works fine with my SuperSU on stock, and on my tablet (Nexus 7 2013) I installed magisk and titanium works as intended.
So maybe something was just iffy with titanium backup last night, actually come to think of it I don't think Resurrection Remix comes with BusyBox.
I'll try again but install BusyBox first when I get more time.

Would using the wrong unSU version affect safetynet detection?

Covalex said:
Would using the wrong unSU version affect safetynet detection?
Click to expand...
Click to collapse
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?

guessingagain said:
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
Click to expand...
Click to collapse
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.

Covalex said:
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Click to expand...
Click to collapse
You used this right?
https://forum.xda-developers.com/showpost.php?p=63615067
Or is there another unSU script that is updated? If so can you link that?

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.

For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.

Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:

neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?

Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.

That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.

Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.

neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.

Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.

I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.

Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)

Magisk on Android p?

Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?

marvi0 said:
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
Click to expand...
Click to collapse
Yes, it works for me and I installed couple of modules as well...

Great thanks will try again.

Wow I thought I was the only one. Modules not showing up here either and I've tried reinstalling in a bunch of different ways.

marvi0 said:
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
Click to expand...
Click to collapse
marvi0 said:
Great thanks will try again.
Click to expand...
Click to collapse
gigatex said:
Wow I thought I was the only one. Modules not showing up here either and I've tried reinstalling in a bunch of different ways.
Click to expand...
Click to collapse
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:

Badger50 said:
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Click to expand...
Click to collapse
For me I noticed I have to reboot when I install each and every module. On my oneplus-5t I could install a bunch and then reboot once but on the pixel presumably due to the new firmware, you have to reboot after each module is installed and this definitely helped me.

Badger50 said:
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Click to expand...
Click to collapse
I don't think its a module specific compatibility issue. Every single module I try to install seems to install fine but just doesn't show up in the list of modules. I've tried a lot of different ones.

gigatex said:
I don't think its a module specific compatibility issue. Every single module I try to install seems to install fine but just doesn't show up in the list of modules. I've tried a lot of different ones.
Click to expand...
Click to collapse
Interesting. That's kinda weird because I've seen many users running them on the DP's. Does clearing magisk manager app cache/data help at all? And I'm sure you've granted storage permissions as well.

Badger50 said:
Interesting. That's kinda weird because I've seen many users running them on the DP's. Does clearing magisk manager app cache/data help at all? And I'm sure you've granted storage permissions as well.
Click to expand...
Click to collapse
Yep, tried that and also installing through manually patching boot image, flashing through TWRP and installing through direct installation through magisk manager. Sometimes the installation fails and on reboot it'll say it's installed but safetynet will fail. Even when it installs fine modules never work though. Module downloading is all fine, during installation it goes ahead just fine as well but the modules just don't show up in the list after installation/reboot.

gigatex said:
Yep, tried that and also installing through manually patching boot image, flashing through TWRP and installing through direct installation through magisk manager. Sometimes the installation fails and on reboot it'll say it's installed but safetynet will fail. Even when it installs fine modules never work though. Module downloading is all fine, during installation it goes ahead just fine as well but the modules just don't show up in the list after installation/reboot.
Click to expand...
Click to collapse
Don't know what to tell you my friend. Grab some install logs and head over to the magisk forums for some additional help is all I can suggest. I wish you luck :good:

I'm trying to figure out where i went wrong, because the last time i tried ROOTing PDP3, i couldnt boot and i am yet to see and PDP3 Patched_Boot.img or TWRP Recovery...
I did the following:
-Fastboot Flash-ALL PDP3
-Boot and set-up device PIN
-Boot into Fastboot
-Fastboot boot TWRP3212.img
-Use TWRP Installer to install Custom Recovery on device
-Reboot Recovery
-Flash Magisk v16.4
-REBOOT SYSTEM
-I think i ended up Looping @ G

Riru Core EdXposed Magisk

You got Magisk installed on the stock Android 9 ROM? Awesome! But wait, there is more! ?
This thread is meant for the exchange of everyone's experience with Riru and Xposed modules running with EdXposed.
The installation is pretty simple: 1) In Magisk, install "Riru - Core", reboot, 2) install "Riru - EdXposed" (SandHook), reboot, 3) install "EdXposed Manager" (github.com/ElderDrivers/EdXposedManager/releases).
Once everything is set up, install Xposed modules like crazy ... and prepare yourself for a hell of crashes and boot halts ?. Since we do not have TWRP with data decryption yet, you have to be prepared for those boot halts. Therefore, install only one Xposed module at a time, reboot and check if everything is working. If Android does not boot, you can fix your phone using two methods:
Recovering from a boot halt - Method 1
The most obvious way to get around a boot hang is to 1) flash the original boot.img, 2) boot into the UI and uninstall the Xposed module causing the boot halt, and 3) flash "magisk_patched.img" and re-install Magisk from within the Magisk Manager ("Direct install"). SU might stop working if you forget to re-install Magisk (not the Magisk Manager).
The only possible downside is that Magisk and Xposed modules, like XPrivacyLUA, will be inactive during step 2). However, potential privacy/usability issues are less painful than not being able too boot up Android ?.
Recovering from a boot halt - Method 2
If you do not want to disable Magisk and Xposed, flashing the "magisk_patched.img" may make Android boot into the UI ... and give you 10 to 20 seconds before crashing. As a precaution, before you install Xposed modules, 1) remove PIN/password log-on and 2) place a shortcut to the EdXposed Manager and Magisk Manager onto a convenient spot on your desktop. For both managers, you can place a link directly to the Modules tab (at least with Nova launcher).
If things go well, you have 10 to 20 seconds to open the EdXposed Manager and disable the module causing the boot process to fail. If the boot process gets stuck again, even though you flashed "magisk_patched.img", you might succeed by flashing the "magisk_patched.img" several times before rebooting. Even removing the SIM or SD-card may make Android boot up.
If/when you succeed to disable the Xposed module that blocks the boot process, you have to re-install Magisk from within the Magisk Manager ("Direct install"). Otherwise, SU might stop working for you.
Here are Xposed modules that prevent your Pro1 from booting into Pie:
MyAndroidToolsXposed (surely)
DisableFlagSecure (probably)
Screenshot Delay Remover - Mod (probably)
Working fine are:
GravityBox
XPrivacyLUA
AFWall+
Scoop
App Locale 2
InstallerOpt (doesn't crash but doesn't seem to work either)
FakeGApps

I want to install Xposed mainly for MinMinGuard to get ride of these empty ads areas, is this module working fine?
OP 7 Pro Magisk

Sorry for the late reply...
So far, either no one ever tried to run MinMinGuard on the Pro1, or no one ever gave feedback

The riru core update 21.3 seems to remove the play services on my gt-n7000 with lineageos 16 and opengapps pico.

Is this thread for Lineage OS only?
Sorry to post here... but to answer your question, no I do not have Magisk installed. lol. As far as I know, TWRP is for Sailfish only. Also, I can't locate the F(X) Tec Pro 1 Boot image anywhere. Build= QX1000_EEA20200825231443.
Kindly, if you installed Magisk using the F(X) Tec Pro 1 boot image and the Magisk "Select And Patch A File" option... Please tell me where you located the boot image?

Antinee said:
Is this thread for Lineage OS only?
Sorry to post here... but to answer your question, no I do not have Magisk installed. lol. As far as I know, TWRP is for Sailfish only. Also, I can't locate the F(X) Tec Pro 1 Boot image anywhere. Build= QX1000_EEA20200825231443.
Kindly, if you installed Magisk using the F(X) Tec Pro 1 boot image and the Magisk "Select And Patch A File" option... Please tell me where you located the boot image?
Click to expand...
Click to collapse
You can install the Magisk zip via LineageOS recovery

Antinee said:
Is this thread for Lineage OS only?
Click to expand...
Click to collapse
No, this thread is for the stock ROM only
I changed the first posting accordingly.
On LOS, Magisk, Riru and all Xposed modules (that I have installed) work without any problems.
Since I switched to LOS, I won't/can't update the list of working Xposed modules for the stock ROM any more.

im on a moto g power. stock. installed riru. but when i try to install edxposed it fails and tells me i need install riru-core first. just doesnt seem to recognize riru for some reason.

cnoevl21 said:
im on a moto g power. stock. installed riru. but when i try to install edxposed it fails and tells me i need install riru-core first. just doesnt seem to recognize riru for some reason.
Click to expand...
Click to collapse
This is about the Fxtec Pro1. Anyway, that's because Riru is v22 or newer. EdXposes currently needs an older riru

Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks

peperu said:
Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks
Click to expand...
Click to collapse
https://github.com/RikkaApps/Riru/releases
But im in the same boat as you. Im not sure how far back we need to go to get a riru version that works with edxposed. nor do i know how to install it, since it wont be in magisk manager.

peperu said:
Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks
Click to expand...
Click to collapse
1. Riru Core has been renamed to Riru
2. you need to use Version 21
---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------
cnoevl21 said:
https://github.com/RikkaApps/Riru/releases
But im in the same boat as you. Im not sure how far back we need to go to get a riru version that works with edxposed. nor do i know how to install it, since it wont be in magisk manager.
Click to expand...
Click to collapse
Version 21 of Riru at that link. You can install it via the flash from storage button in the download modules page
EDIT: Direct link to the correct ZIP: https://github.com/RikkaApps/Riru/releases/download/v21.3/magisk-riru-v21.3.zip

nift4 said:
1. Riru Core has been renamed to Riru
2. you need to use Version 21
---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------
Version 21 of Riru at that link. You can install it via the flash from storage button in the download modules page
EDIT: Direct link to the correct ZIP: https://github.com/RikkaApps/Riru/releases/download/v21.3/magisk-riru-v21.3.zip
Click to expand...
Click to collapse
Thank you. i did get it to work. but now the phone doesnt pass safetynet. Looks like canary fixes this, but it says its not stable. so i worry installing it would brick the phone.
Maybe i just need to get over having back button kill and double tapping recent for screenshot lol

cnoevl21 said:
Thank you. i did get it to work. but now the phone doesnt pass safetynet. Looks like canary fixes this, but it says its not stable. so i worry installing it would brick the phone.
Maybe i just need to get over having back button kill and double tapping recent for screenshot lol
Click to expand...
Click to collapse
Did you enable Pass SafetyNet in EdXposed settings

nift4 said:
Did you enable Pass SafetyNet in EdXposed settings
Click to expand...
Click to collapse
I did. still fails

cnoevl21 said:
I did. still fails
Click to expand...
Click to collapse
If App List mode is enabled, I can't help you

Hi,
Riru 23.1 (Magisk module) ignores the screen timeout. This makes battery drained. This should be resolved.
I use it on my Redmi Note 8 Pro (Android 10).
Does any one a fix or advice for that?
Thank you!

Rezazahmad01 said:
Hi,
Riru 23.1 (Magisk module) ignores the screen timeout. This makes battery drained. This should be resolved.
I use it on my Redmi Note 8 Pro (Android 10).
Does any one a fix or advice for that?
Thank you!
Click to expand...
Click to collapse
I just checked i have 23.2 installed not sure if the same issue is here

For some time, the riru core continues to have a very horrible bug for Samsung devices with Snapdragon, it is that once installed it affects the installation of apks and applications from the play store and also in the uninstallation of applications the "installer of packages stays frozen and does not advance "is a very random and very annoying error and you have to restart the device and sometimes it does not work. That's why I ask you to correct that error. It was tested on a S9 + g9600 and a note 9 N9600 both with a Snapdragon processor and latest riru core 25.4.2.

daniel_m said:
No, this thread is for the stock ROM only
I changed the first posting accordingly.
On LOS, Magisk, Riru and all Xposed modules (that I have installed) work without any problems.
Since I switched to LOS, I won't/can't update the list of working Xposed modules for the stock ROM any more.
Click to expand...
Click to collapse
Working also on Lineage 18.1?
I become an error Riru Core not found in memory

Problem with BHIM UPI and Adaway on rooted 10.3.2.HD65AA, OP7T India.

I am on 10.3.2, rooted with Magisk Manager version 07f712a1 and Magisk 87de0e7a. These are the version numbers I can see when i open Magisk Manager. Magisk Hide is enable for banking apps mainly, systemless host module is enabled and Magisk package name is also hidden.
Most apps needing root are working fine and most Banking apps requiring root to be hidden are also working fine.
However BHIM UPI is not working, I get a message of root detected after putting the PIN and it does not open. If I uninstall or clear storage and register my mobile again, it gives the root detected error but still logs in. However as soon as I exit and open again, it does not log in. Any way to get this working?
Adaway had been working properly but now it is not able to update hosts, says Root permission not granted, even though in Magisk default permission is Grant. I have tried to uninstall and reinstall, change options in Magisk, install F-droid version but nothing works. Systemless host is enabled. I have restored a working app version and data using Titanium backup so ad-blocking is working. But unable to update with new host file. How to fix this?

Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here

Macusercom said:
Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here
Click to expand...
Click to collapse
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.

^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019

gpz1100 said:
^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019
Click to expand...
Click to collapse
Is this meant as a reply to my post? My issue with Adaway on Magisk Canary is that suddenly it is not able to get root permission.

So it worked before? I had to mess with the systemless hosts to get it working. It didn't have issues acquiring root though.

jesrani said:
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.
Click to expand...
Click to collapse
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP

Macusercom said:
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP
Click to expand...
Click to collapse
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.

jesrani said:
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.
Click to expand...
Click to collapse
Afaik only for custom ROMs. Otherwise, you can still remove Magisk in Magisk Manager and then patch the boot.img with the stable Magisk version or you remove ALL modules first, then make an OTA update to your existing version.
Then patch boot.img and flash it via "fastboot flash boot.img".

@jesrani What was the solution finally ?

Yea I'm having the same issue, tried everything i could and even using 'hide my applist' and it IS working. Its just that all apps except BHIM just won't even open now.