Database Info

Is it possible to pass SafetyNet with Magisk?

I have tried to bypass SafetyNet with my F3113 using the guide to root and the "How to install Magisk" but the creator (rrvuhpg) mentioned something about having the internal memory encrypted and i tried but without luck.
So i decided to open a thread if anyone has a clue to do it or have succeeded bypassing SafetyNet with Magisk´s Root.
I will paste my last experience:
Try to encrypt phone right away (Rooted with Magisk)
It freezes at logo after reboot.
Searched Google and found it hangs at Logo when rooted.
Learned to Hard Shutdown with vol+ & Power.
Unrooted, flashed boot.img, rebooted to system.
Start encryption again, ends successfully.
Rebooted to TWRP and flashed Magisk 12, then rebooted
Opened Magisk manager, Magisk is installed but root permissions not present, still fails at basic integrity &CTS.
Rebooted to TWRP, uninstalled Magisk 12, rebooted and installing Magisk 11.6
Root present, encrypted internal memory, but fails at Basic Integity and CTS.
This is my Newest experience:
Unlocked Bootloader
Flashed with 0.9.23.2 Flashtool 33.2.A.4.70 Stock Firmware
Booting to system, executing SafetyNet test
Test Passes
Flashed boot & recovery from root guide
Booted to system & executing SafetyNet test
Test fails
Installing Magisk in TWRP anyway
Keeps failing SafetyNet
That is how i did but failed any help is apreciated. Thanks.

That's the Google OTA / DM verity reset kicking in when it detects modification.. The next roadblock is Sony RIC

Problems about safetynet checks is related to the way that Google use to check it and the updates of Magisk to bypass it. Generally it works after a new Magisk update until Google update the safetynet test again.

SIM Card not found after Magisk Module Install

I'm on OOS 9.5.8 with Magisk and TWRP, I used Oxygen Updater to update to 9.5.8 and reflashed TWRP and Magisk right after. I had no modules installed.
I tried installing a module recently (YouTube Vanced) and my phone told me it could not find a SIM after reboot. This persisted through reboots until I finally uninstalled the module and rebooted, in which normal data function resumed. This happens with every module I install. Anyone have a solution or similar problem on their OnePlus?

flash the full rom in system update and try again.

Hmm. That's odd. I had the same problem with flashing a few kernels, but when I rebooted it went away.

It seems like cache wipe fixes this. Apparently, this cache wipe is required after each module installation in order to avoid this issue. Also, if you have this problem with Magisk installed in general (IE no modules installed and lose SIM after vanilla Magisk installation) make sure you have latest TWRP installed to both A/B slots prior to Magisk installation.

Booting into magisk boot.img my phone bootloops

Google pixel 3 Android 10 (blue line)
Because of a module I've already installed which my phone didn't like (which is causing the boot loop) I can't get into my phone when I enter through the magisk boot img and have to stick with my non rooted img. Any help on how to delete a module without having magisk? (ALREADY TRIED GETTING RID OF DATA IN MAGISK SETTINGS!)

See this thread.
https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433

Getting bootloop after flashing Magisk!

I flashed OxygenOS 10.0.1 by the fastboot method. Then flashed modded TWRP and then Magisk. This all happened successfully. I wanted to install Youtube Vanced but stock Youtube was causing it to not show up. So I tried uninstalling Youtube through Titanium Backup but it said 'apk not found'. So I downloaded some other app (I think it was named 'System App Remover'). Since then I have been getting bootloops. Phone gets stuck on 'Bootloader unlocked warning' screen then goes into Fastboot mode. I had to uninstall Magisk through TWRP to boot the phone. I don't understand what's wrong in this entire process. Please help.

I think the issue is with the System App Remover. I tried using possibly the same exact app previously but I also got boot loops. I would try a factory reset, reflash twrp and magisk and try the Magisk module "Debloater".

You have to clean temporary magisk files.
Probaby you had enabled some magisk modules on previous system and you forget disable them.

Thanks for the replies. I fixed the problem by restoring System from an earlier TWRP backup.

Usually bootloops from Magisk modules can be fixed by deleting problematic module from twrp file explore /data/adb/modules
Don't have to fart around with uninstalling entire Magisk or installing Magisk debloater anymore

[SOLVED] Magisk install methods suddenly no longer work

Hi all,
Yesterday I was messing around with V4A and following the final installation steps my phone got stuck in fastboot. To fix it I did the following:
1. I extracted the stock boot.img from my current OS version (10.3.12) and flashed it to boot_a and boot_b using fastboot. This restored the phone's ability to boot.
2. I booted the phone and went into the Magisk app to disable/unhide as much as possible and uninstalled the V4A app.
3. Rebooted into fastboot and booted into TWRP to remove Magisk, V4A and Vanced stuff from data/adb with the file manager.
4. Booted and flashed various combinations of TWRP versions (Mauronofrio, Bluspark) and Magisk (from 19.4 to 23.0). TWRP flashes fine and allows system to boot, but as soon as Magisk is flashed and a reboot is tried into system, it gets stuck on bootloader again and I have to repeat step 1.
(5. Tried patching stock boot.img file with the Magisk app. Same results as step 4.)
Does anyone here know what might be wrong? Is there another method I can try to regain Magisk without losing data?
Thanks in advance!
EDIT: really at a loss here. Idk why but as soon as magisk is flashed, the system refuses to boot. Without flashing magisk, system boots fine – am typing from it now. I figured at first that it had to do with remnants of AML, V4A and other Magisk modules not being properly removed, but I've removed those through TWRP file manager.
Really hoping one of you can point out something I've missed or think of something else I can try.
EDIT: solved! See update below.

UPDATE: solved it by forcing a local upgrade of the full OTA through phone settings (same version as mentioned above), causing it to switch slots. On the other slot, the system managed to boot after flashing TWRP and Magisk (latest versions).