Can't get Magisk to work on LineageOS 15.1 (Sailfish) - LineageOS Questions & Answers

I have pixel (sailfish) running lineage 15.1 w/ microG and I've followed the exact steps from the official Magisk install page using Magisk v18.1 with manager 7.0 only to get the same safetynet api error. Ive even tried other suggested installation methods from: https://android.gadgethacks.com/how-...el-xl-0177522/
And it left me in a bootloop whereby I had to wipe and reinstall everything.
Anybody please help!
**I already tried clearing my Manager data and also testing MagiskHide by adding a root app to the Hide list and still get the same error

Related

Mi5s and magisk

While unlocking and rooting works like a charm... - was anyone successful with installing root "the magisk way" maintaining complete safetynet validity?
I had no problems with installing magisk. Have root an Pogo running now
Hi strange.... What steps did you perform?
This is what I do:
- unlock bootloader, install twrp
- check: pogo works, safetynet is positive
- install magisk v8 in twrp
- reboot, no root, safetynet still positive
- install phh superuser 259 in twrp
- reboot, no root, safetynet fails its response
- installing magisk manager and phh superuser from playstore
- root is OK, but safetynet response negative, pogo not working
I tried both:
MIUI Global 8 stable (8.0.10.0.0 (MAGCNDH))
MIUI 8.1 by xiaomi.eu 6.10.27 | Beta
Anybody else tested this?
I wonder, can you run normal Pokemon Go from Play store?
There is one user who pretends that he got it working - but even after several tries I cannot confirm this.
http://forum.xda-developers.com/showpost.php?p=69404055&postcount=5339

Magisk - Unable to install modules

Hey all. Recently unlocked bootloader + root. Everything is stock. I'm a new Magisk user so hopefully I'm not doing anything wrong, but when I attempt to install a module, I'm presented with:
/data/magisk isn't setup properly!
Please install Magisk v14.0+!
failed!
Installation error!
Anyone ever came across this? On the main menu, my latest Magisk version is v14.4, installed Magish version is v14.4, 14.4:MAGISKSU (topjohnwu)
Edit: This happened with the Youtube background play module (iYTBP for Magisk) but I was able to install the Busybox module. So maybe it was just module specific?
I'm having the same problem. I was able and install busybox module but same error on YouTube module and unified adaway. I installed the YouTube module manually and adaway APK so I haven't worried about it much. Would be nice to know what the problem is though.
Ah good to know! Is there an apk for the Youtube module?

Magisk SafetyNet fails after awhile

I've been experiencing losing SafetyNet pass with Magisk after the phone has been on for awhile. Has anyone seen this issue before?
I'm on Magisk v14.5 with Magisk Manager v5.4.0, on Android 8.1 (happened on 8.0 too). I already tried flashing a different kernel, but this issues still happens.
SafetyNet passes again after restarting my phone.
Any help will be appreciated. Thanks!
Try updating magisk to 5.4.3 that's the newest one. I'm also on the beta channel you can change it in the setting. And you should be good.
Edit
Link to the newest magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I was on the new magisk 5.4.3, and the failure still happens. I only downgraded to 5.4.0 to avoid the dtbo.img failure right now.

Oneplus 5T with OxygenOS, TWRP and Magisk 17.1 SafetyNet fail after a few hours

I have a OnePlus 5T that passes fully the SafetyNet test, but after a few hours it gives false in ctsProfile and BasicIntegrity, I am with Android 8.1 OxygenOS 5.1.5 (I already tried with 5.1.4 doing a thorough cleanup between rom exchange and also unsuccessful ), I unlocked Bootloader and installed TWRP 3.2.3 Blu spark v9.85, then i flash Root Magisk 17.1 by twrp, Installed from a clean ROM and I've already tried with 17.2 and It's the same thing at the end, I have also tried to install Magisk 16.0 from a clean rom and then upgrade to 17.1 directly via Magisk Manager but it was the same, already activated the Magisk Hide in all necessary applications, I hid the Magisk Manager, I've tried flashing Petnoire's SafetyNet Spoofer and me too changed the device fingerprint by MagiskHide Props Config but nothing solved my initial problem, every time I restart the device it passes on the SafetyNet again but after a few hours it fails again, Now i tried to flash the module Universal SafetyNet Fix v3 beta1(MG v17 fix) by Magisk Manager, but Magisk Manager stopped opening even uninstalling the application and installing other versions, I tried more than once and the installation of this module always presents this problem even flashing by TWRP, and after a few hours too SafetyNet failed, Can inform me the latest version of OxygenOS for OnePlus 5T that passes on SafetyNet without any problem? Even though OxygenOS is perfect for me, I'm willing to change rom in the last case, because the most important thing for me is to go through SafetyNet to use the applications I need.
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
anatoly1983 said:
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Click to expand...
Click to collapse
I tried to do this yesterday but the initial problem persisted, every time I restart the device it passes on the SafetyNet again but after a few hours or minutes it fails again.
yoye_cros said:
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
Click to expand...
Click to collapse
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Mega_Monster_X said:
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Click to expand...
Click to collapse
Honestly, I didn't have found any bug. I tried crDroid but I wasn't really happy, and CNP is for my use very stable without bug. I don't know if Volte or VoWifi is working because I don't use this. Also, it's very easy to install compared to other Pie Roms. I just can advise you to try it.
Try a different play services apk. This was the case with me previously.
Seagorilla2 said:
Try a different play services apk. This was the case with me previously.
Click to expand...
Click to collapse
I've tried this but to no avail
With Magisk 16.0 everything went fine, the problem is the Magisk modules I used that are not compatible, but I'll search here to see if I find the modules I want for Magisk 16.0.
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
floborg said:
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
Click to expand...
Click to collapse
I have not found a solution yet, when I fail on SafetyNet I reboot the device and pass SafetyNet a few times for a short time and sometimes lasts several hours but then fails again , I'm using Magisk 18 in OOS Open Beta 20 Android 9.0

How can I modify what I perceive as a rooted device?

Hi. I was install LineaseOS 17.1 to xz2c. Then, installed the app that I use.
But, Some apps not work because, Rooting detected from my Phone.
Of course, I didn't rooting. (Wipe and only installed LOS and gapps)
I think I recognize it as a Rooted device due to the settings such as build.prop.
To solve this problem, I've tried Magesk or some other method( LOS Recovery -> pull build.prop and Modify), and there's still a problem.
I want to know which part of build.prop or what elements of something else are recognized as a routing device and how to solve this problem.
How should I fix something?
Previously, I tried to solve this problem with Magisk and Module, but it didn't work perfectly.
I have installed magisk and installed magiskHide Props Config 5.4.0 and universal safety net fix 1.1.1.
But Safetynet ctsProfile failed, and some apps works well, but others didn't.
There are only LOS and Gapps now.( Not Uninstall, Full Wipe and reflashing LOS17.1)

Categories

Resources