Magisk and camera2api breaks after Lineage OS update - Xiaomi Redmi Note 5 Pro Questions & Answers

I'm on the official Lineage OS builds. I unlocked my bootloader last week and immediately flashed LOS. Magisk 17.1 followed next. Tried the camera2api enabler magisk module which doesn't work weirdly for some reason, I mean the build prop file was not edited. So I manually edited the build.prop to enable camera2api. All was good until, the latest build hit the update. Update went smoothly but Magisk was uninstalled, camera2api reverted back and a MI A2 camera mod was also removed.
I used Lineage OS 14.1 on Redmi Note 3 pro(kenzo) but never faced such issue on that. Magisk usually had a script that enabled itself during the OTA and it almost never broke. Camera2api too persisted
As for the mod, it is my first time experimenting with a camera mod so dunno if I have to flash it after every OTA.
Can anyone explain what might have caused this?

Related

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.

Prevent files, flashed through TWRP, being replaced by stock one, without root.

I have a Oneplus 5T and i'm struggling to install a google camera fix patch for my device but in the same time keep my phone root-free because i use a bank app called "BT pay" which detects magisk even with magisk hide, even with magisk manger hidden/uninstalled, i tried many times, can't get it done with root.
I keep tried to install TWRP (even if it being replaced by stock recovery evey boot) and install my gCam fix zip from there. but it seems like those files are replaced by stock files TOO...
I also tried to prevent TWRP from being replaced by deleting "install-recovery.sh" from /system/bin but this didn't work either.
Note that i have the official rom (oxigenOS beta 15) for my phone (official kernel too) which have Treble support, (the TWRP/gCam fix are also treble versions).
I take it you were using the MagiskHide Props Conifg Module right with Magisk 17.1? That is the only way you will pass Safety Net. Does your banking app still not work like that? (With a certified fingerprint)

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

Can't get Magisk to work on LineageOS 15.1 (Sailfish)

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

[A320] Viperfx with stock rom

Hi
Im back to stock after months of struggling with Lineage bugs.
All i need is viperfx, which improves internal speaker so much, whem properly configured !
I guess the only way to get it is by using magisk (i tried with a supersu root and a viperfx flash but it didnt work).
So I just spent many hours trying to get magisk to run properly but failed.
I flashed 17.1 in twrp, seemed to work, but it didnt find any module to install, so i updated magisk manager to latest version.
Then i was unable to run magisk manager, instant crash at launch, fc.
Any tip please ?
Thanks

Categories

Resources