Develop Bugs

[x Force] Installing Magisk Root & Universal Systemless Interface

Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Code:
adb reboot fastboot
Temporarily boot into into TWRP
Code:
fastboot boot C:\twrp-3.0.2-0-clark.img
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased

JimyKK said:
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Temporarily boot into into TWRP
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
Click to expand...
Click to collapse
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.

sam00561 said:
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
Click to expand...
Click to collapse
Maybe™
My banking app uses google's inbuilt SafteyNet library to detect root and from my understanding that is also how android pay works as well. Magisk's hide function seams to bypass this detection even though on the main screen of Magisk management app the SafetyNet check fails.

For this procedure is necesary unlock the bootloader?

Cameronbrujah said:
For this procedure is necesary unlock the bootloader?
Click to expand...
Click to collapse
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.

Yemble said:
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Click to expand...
Click to collapse
Thanks a lot for your prompt response!!!
I'll do it.

Cameronbrujah said:
Thanks a lot for your prompt response!!!
I'll do it.
Click to expand...
Click to collapse
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.

Yemble said:
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Click to expand...
Click to collapse
actually I have Nougat 7.0 Official and only for the moment I will to root the phone. In a near future, of course I will change the ROM to the CrashXXL
Thanks a lot for all your help.
Regards from Mexico!

And how are we gonna unlock the bootloader?
Is there a way to do 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)

[App] [SafetyNet Passer] Pass SafetyNet after 2017-07-17 on Magisk V13

Hello XDA,
As we are all aware that once again Google broke SafetyNet Passing as they have extended their property scanning | Original Article here
The temporary fix was originally mentioned on this thread by @[email protected]
However you had to do the terminal commands after every reboot, thus Me and a few friends took this idea and created an app that does the same for you in the background and thus an easy temporary fix.
All you have to do is to install the apk as usual, grant it supersu permission and click to fix :laugh:
GitHub: https://github.com/Agusyc/SafetyNetPasser | Credits @Agusyc15
Download APK
Made a Quick Video Here
Tested Working on Oneplus 5 & Pixel XL | Magisk V13.2
Development Credits: @Agusyc15 & @unknownblkman
Magisk Credits as always @topjohnwu
Original Fix & ADB Commands: @[email protected]
PS: This is a temporary fix, I am sure @topjohnwu is aware of this situation and an official fix should be out soon :fingers-crossed:
Never Settle :highfive:

Reserved

You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol

Interceptor777 said:
You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol
Click to expand...
Click to collapse
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?

Bewildered Wolf said:
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?
Click to expand...
Click to collapse
Resurrection Remix with Spectrum kernel app, running lightning kernel LOS version which supports it.
The symbol on the quick settings is a quick profile switcher for spectrum, this is what it looks like on balanced profile.
Also, theme is also called spectrum on the play store.

Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.

GitHub along with the Updated apk now uploaded on the OP | Credits @Agusyc15

hachamacha said:
Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.
Click to expand...
Click to collapse
Please try the new apk uploaded on the OP :fingers-crossed:

Funk Wizard said:
Please try the new apk uploaded on the OP :fingers-crossed:
Click to expand...
Click to collapse
Just tried it and it works fine as did your first. Thanks!

@Funk Wizard you can also purpose the recovery flash solution (by noahajac) available from Github : here
Personaly i prefer flash the fix by this way instead of install a apk/service for fix SafetyNet each boot

Magisk 13.2 has been released and fixes the SafetyNet test failing.
Magisk 13.2
I can confirm that it's working for me.

Magisk 13.3 already available, and everything is fixed

Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?

13.3 fixed for me

Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.

Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.

crumble6 said:
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.
Click to expand...
Click to collapse
That didn't work for me unfortunately.
ArkAngel06 said:
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.
Click to expand...
Click to collapse
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Thanks guys!

Binary Assault said:
That didn't work for me unfortunately.
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Click to expand...
Click to collapse
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.

crumble6 said:
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.
Click to expand...
Click to collapse
Ya, I just discovered this. I actually noticed a few things,
My original issue was caused by a module I installed
It seems anything I flash via TWRP makes Magisk manager fail.
Most modules I installed in TWRP that fails, will properly install within Magisk manager.
For me, the culprit was doze for Google play services. Even installing it via Magisk manager froze Magisk manager.
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.

Binary Assault said:
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.
Click to expand...
Click to collapse
Just delete the module folder from /magisk and reboot. You will need root access for this but from what I've found, root access still works even though Magisk Manager is not responding.

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

Latest Magisk crashes

So I tried to root a Pixel 2 XL with Android 8 and 9, installed the Magisk apk 7.5.1 and when it comes to patch the boot.img, it always requires to update the manager first. I didnt choose update, but it wont let me use the old version anymore, might be a bug.
However, when I then use the latest Magisk APK, it crashes when I select "Install". Any ideas what to do?

You could basically just flash the latest magisk canary build (the beta one) with twrp and you'll have root on your device in no time.
BTW this method is tested by me on android 11, and if it works on android 11 I think it'll work on previous versions of android as well. But, just to be on the safer side make sure you backup your device beforehand.

MridulDR said:
You could basically just flash the latest magisk canary build (the beta one) with twrp and you'll have root on your device in no time.
BTW this method is tested by me on android 11, and if it works on android 11 I think it'll work on previous versions of android as well. But, just to be on the safer side make sure you backup your device beforehand.
Click to expand...
Click to collapse
Thanks for the hint. I used the zipped Magisk and flashed it with TWRP. It still crashes when hitting the "Install" button but since the phone is rooted is not really necessary. Also, installing modules is
now possible again. Only renaming Magisk (for hiding) is something I didnt find yet, but the "Magisk Hide" Option should do the job.

Venomiz said:
Thanks for the hint. I used the zipped Magisk and flashed it with TWRP. It still crashes when hitting the "Install" button but since the phone is rooted is not really necessary. Also, installing modules is
now possible again. Only renaming Magisk (for hiding) is something I didnt find yet, but the "Magisk Hide" Option should do the job.
Click to expand...
Click to collapse
Which version of magisk are you using?
If you are on normal magisk manager(not canary), I'd suggest flashing the canary build(v21.0) and see if you are able to rename magisk manager.