david

Yes, and the "real" test, of not being able to see Netflix or other @#$%ing apps in the Play Store that don't like users to be able to use their phones the way the users want to use them. 😠

Yes, that's what I mentioned above. Thanks for confirming. :-) But to be clear, that doesn't mean the latest OTA firmware is okay. It is still causing a problem with SafetyNet.

Thanks. I haven't used LineageOS, only an older Cyanogenmod, and it didn't have the built in root option, so I didn't realize it didn't give apps root permission. Nice that it can be flashed and undone from recovery though. I originally thought I would decrypt my /data partition (or at least try to do that), but I feel it is too risky. Not because of security risks, but because if I slip up and reboot when I'm temporarily unrooted, or if the system restarts itself without my blessing when I'm temporarily unrooted, or I get in a boot loop and have to disable root, then it will re-enc

I tried it. 1) It runs in portrait mode even if I have my phone in landscape or have my keyboard out (I'm using the auto-rotate option, not any forced rotate apps). 2) It failed safetynet every time I ran it. :-/ SafetyNet request: success Response validation: fail Error Msg: ApiException[7] 7:

That was using the SafetyNet Test app. I downloaded SafetyNet Evaluation and it passes every time. Magisk Manager's built in checker has worked every time too. I have had the issue with SafetyNet Test failing sometimes in the past, and I think I tracked that down to that a given app can only do a check a limited number of times in a given unit of time. That app is probably more popular, so it exceeds this limit faster than other apps, hence fails sometimes.

Where did you find out that it does that?

I installed this module. It required a reboot. When I ran the SafetyNet check after reboot, it still failed, stating it couldn't access the play services. I ran it again a few seconds later and it worked. I went into the Play Store and could see Netflix (I already have it installed). I disabled the module and rebooted and again can't pass SafetyNet and can't see Netflix in the play store. Enabled it again and rebooted. Can see Netflix and pass SafetyNet. But again, requires running the test a second time before it succeeds. In fact, it fails exactly every other time and succee

In Play Store->Settings->Play Protect certification, mine reads "Device not certified". This is with me rooted with Magisk.

Do you know if there is a way in LineageOS, if you are using the built in root option, to disable that root without booting into LineageOS? In other words, some way to disable it in LineageOS's recovery? I ask this, because a person might have an app that has super user privileges and it causing the phone to not boot into the OS. With Magisk, there is a Magisk Core method to still allow Magisk to run and to disable all Magisk modules. I've never done it, and it looks like a pain, but at least it is possible to do. Or maybe with a built in switch in settings, a person could boot in

I just compared the 20200106 boot image file to the 20200304 file with a hex compare tool and they are different.

Ah..I was looking at the end. I didn't look back far enough. :-)

See a few posts prior to this for the link. The OTA format is different than a regular factory image format. I've never messed with trying to do conversions, but I believe others documented this earlier in this topic. No idea if anything in the boot image changed. I guess, in theory, someone could use an old image and cross their fingers. :-)

I didn't see that you had a pointer over there. I still don't see one by you. :-)

Here is the 20200304 boot image file for anyone wanting to root from that point in time. http://www.mediafire.com/file/wq9eu0ysaojwke8/20200304_magisk_backup_boot.img.gz/file

Thanks! I put a pointer post in the other thread for people over there to follow back here if they are dealing with root issues.

I successfully did it when rooted with Magisk. See this for the discussion: https://community.fxtec.com/topic/2537-magisk-install-step-by-step-root/?do=findComment&comment=46376 And further down, this for the steps: https://community.fxtec.com/topic/2537-magisk-install-step-by-step-root/?do=findComment&comment=46403

Question on this. Are you saying this is because there is no normal OTA process for LineageOS, so every time you update LineageOS, you'll lose root anyway, and have to re-flash magisk?

I added this to my post above, but I'm duplicating it here in case anyone missed it because it is important. If you don't follow the steps properly the first time you root, you won't be able to do what I documented above (which has also been documented elsewhere on the forums by other people, but for people reading this topic, and not seeing the others, it is good to have it here as well). ... NOTE: You have to originally achieve root in the proper way for this method to work. And that proper way is for Magisk Manager to be given a non-patched boot image file that is identical to

Yeah, I forgot to comment on that. That message was really weird. There is no "Install now" button to select. And why in the world would it go into Recovery Mode to install an OTA update to an A/B device, since the whole point is that you can install it while you are using the phone and not need to restart until you want to. :-)

I uploaded them from my phone and posted it as-is, and then edited the post on my laptop. You caught it in between my edits. :-)

It worked. OTA info screen: I then went into Magisk Manager and uninstalled it, telling it to restore the previous image. Next, started the download for the OTA: One interesting thing was that it automatically started installing after the download. I thought in the past that it gave you an option tap something to start the install after the download was done, but I could be mistaken about that. This means it is important to uninstall Magisk before even starting the download. It also showed 100% complete immediately after the download was com

Did you disable encryption on /data somehow?

Also, going forward, if you have root, you can use various apps to to freeze the apps you want to get rid of instead of modifying /system to uninstall them. Alternatively, if the app has the "Disable" option in its system settings screen, you can use that to stop it from running.

Yeah, see my next post above.

Thinking about this more, the update is probably incremental, so it wouldn't have everything in it to replace everything in /system. I guess that could leave you in a weird state, depending on the exact changes to /system that you made vs what the incremental update is trying to modify. Hopefully it would recognize this and give you an error during the flash. If none of these methods work, then you could always go back to the factory image and do all the OTAs from there forward and reroot after that. UPDATE: I'm making educated guesses here. If anything looks out of pl