Database Info

Calling testers who are on stock rom(Magisk V15/15.1 update thread)

need small help which would benefit others too.
anybody who are ready to format device or has a good backup
try to flash latest magisk 15.0 on u'r device- Ohh, don't flash directly 15.0- i already tried it and it wouldn't work or change device to generic
our device was working perfectly with magisk upto 14.5 but it lost support later
An user in magisk forum with huawei device claimed that- u need to check 2 options which are under safety net check
tick these options
Preserve force encryption
Preserve AVB 2.0
(Check attached pic)
flash 14.5 magisk- then update magisk to 15.0 within the magisk manager checking the above mentioned options
I invested lot of time this morning to troubleshoot this but couldn't get it right but above mentioned method seems reasonable- so anyone who has backup of entire device or going to format device soon- just try whether this method works and report back.

sreekantt said:
try to flash latest magisk 15.0 on u'r device- Ohh, don't flash directly 15.0- i already tried it and it wouldn't work or change device to generic
our device was working perfectly with magisk upto 14.5 but it lost support later
Click to expand...
Click to collapse
Damn, i was updating to my latest build last week and immediately after i flashed TWRP, Magisk V14.6, i was on V14.5 before the update and since that only after this i went to check phone info, noticing the model changed to generic_a15, i thought that i made something bad. It was Magisk's fault so instead! I restored a previously took backup made before updating and now i have to doing again the update. This time i won't flash nothing above V14.5.

RedSkull23 said:
Damn, i was updating to my latest build last week and immediately after i flashed TWRP, Magisk V14.6, i was on V14.5 before the update and since that only after this i went to check phone info, noticing the model changed to generic_a15, i thought that i made something bad. It was Magisk's fault so instead! I restored a previously took backup made before updating and now i have to doing again the update. This time i won't flash nothing above V14.5.
Click to expand...
Click to collapse
Yes exactly- 14.6 and 15.0 are changing vendor partition .....few claim that preserving force encryption and dm verity does the trick

https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
looks like this method is working on huawei p9

sreekantt said:
https://forum.xda-developers.com/showpost.php?p=74968881&postcount=108
looks like this method is working on huawei p9
Click to expand...
Click to collapse
Thanks for sharing. I'm taking a nandroid backup, testing it in 5 minutes...

RedSkull23 said:
Thanks for sharing. I'm taking a nandroid backup, testing it in 5 minutes...
Click to expand...
Click to collapse
good lord ! waiting for results :fingers-crossed:

sreekantt said:
good lord ! waiting for results :fingers-crossed:
Click to expand...
Click to collapse
It worked

RedSkull23 said:
It worked
Click to expand...
Click to collapse
Ooo !!! yeah--- finally :highfive:

sreekantt said:
Ooo !!! yeah--- finally :highfive:
Click to expand...
Click to collapse
After some tests, personally i don't advice to update it to V15.0 yet. Most is working fine by what i've saw, but i've noticed that on MiX it's not possible to modify some system files after updating. I presume that some error is still under-the-hood and even if the update went fine, there must be some lil' issue. In fact i restored the backup took before upgrading Magisk. I'll wait a bit before update it again

RedSkull23 said:
After some tests, personally i don't advice to update it to V15.0 yet. Most is working fine by what i've saw, but i've noticed that on MiX it's not possible to modify some system files after updating. I presume that some error is still under-the-hood and even if the update went fine, there must be some lil' issue. In fact i restored the backup took before upgrading Magisk. I'll wait a bit before update it again
Click to expand...
Click to collapse
Yeah ...may be regular early stage bugs...that explains viper npt working on many phones after v15...lets wait

I've a nice update for you and every EMUI user man; latest Magisk update, V15.1, solved the vendor issue and now it's everything good. I tested it, look here... no need to keep AVB2.0 ticked before updating, just direct install it through Magisk Manager and you're ready to go

RedSkull23 said:
I've a nice update for you and every EMUI user man; latest Magisk update, V15.1, solved the vendor issue and now it's everything good. I tested it, look here... no need to keep AVB2.0 ticked before updating, just direct install it through Magisk Manager and you're ready to go
Click to expand...
Click to collapse
TFS
did u update from v15 ??
btw- Hide u'r IMEI in 2nd pic
Edit - Updated from v15 to 15.1 successfully with AVB 2.0 unchecked and everything is intact as of now
Update- seems like updating from faulty v15 caused issues- Play store was not able to detect apps, not able to change boot animation etc
So i planned to clean install with Magisk 15.1 - uninstalled every trace and rebooted which caused NRD test keys build
Could be the issue caused by magisk modifying vendor partition and couldn't restore properly
Luckily, i had a complete TWRP backup - wiped everything(including cust, vendor, product) except internal storage > restored(including vendor, product)
flashed magisk 15.1 and everything working perfectly without any issue of modified vendor.
Update 2 - Damn EMUI- No sound
flash stock firmware > locked bootloader > unlock again > restore TWRP backup(only data, system, boot)- Vendor restore never worked for me

sreekantt said:
TFS
did u update from v15 ??
btw- Hide u'r IMEI in 2nd pic
Edit - Updated from v15 to 15.1 successfully with AVB 2.0 unchecked and everything is intact as of now ??
Click to expand...
Click to collapse
Whoops, didn't noticed the visible IMEI usually i remove it... thanks for the heads-up. I've updated by V14.5 anyway

I have trouble when update magisk to v15!
no sound at all!!
no mic...no camera, no call, no audio playing,no video playing!
I had a backup but when restored it...problem persist
what can I do!
plz help
GR5 2017 BLL-L21

Med Benarfa55 said:
I have trouble when update magisk to v15!
no sound at all!!
no mic...no camera, no call, no audio playing,no video playing!
I had a backup but when restored it...problem persist
what can I do!
plz help
GR5 2017 BLL-L21
Click to expand...
Click to collapse
Completely uninstall Magisk through Magisk Manager and reboot. Then flash your original boot.img from your build, reboot, reinstall Magisk Manager again and this time directly flash Magisk V15.1. It should work

RedSkull23 said:
Completely uninstall Magisk through Magisk Manager and reboot. Then flash your original boot.img from your build, reboot, reinstall Magisk Manager again and this time directly flash Magisk V15.1. It should work
Click to expand...
Click to collapse
how can i get the boot.img and how can i flash it???

Med Benarfa55 said:
how can i get the boot.img and how can i flash it???
Click to expand...
Click to collapse
The boot.img is backed up (I don't know the exact folder), then flash it using TWRP

Med Benarfa55 said:
how can i get the boot.img and how can i flash it???
Click to expand...
Click to collapse
To get and flash a clean boot.img, you need to:
1 read your build number from phone info
2 download the update.zip matching your build (BLL-L21C432Bxxx, for example) from Hwmt.ru site
3 extract the update.app from the zip file
4 using Huawei Update Extractor program on PC, open the update.app and extract from it the boot.img
5 flash the boot.img by fastboot typing "fastboot flash boot boot.img" (remember to completely uninstall Magisk before doing this, if not you'll face issues)
and that's all. After that, you can reflash Magisk V15.1 back through TWRP
PalakMi said:
The boot.img is backed up (I don't know the exact folder), then flash it using TWRP
Click to expand...
Click to collapse
Yeah it's backed up, but if it's backed up with a supersu app active on system, the su binary files would be already "dirty"... I flash a clean boot.img before every update because if not, the update verification on boot before update will fail, even if stock recovery is clean

So when backing up superSU or magisk, the boot.img is modified! Good to know

PalakMi said:
So when backing up superSU or magisk, the boot.img is modified! Good to know
Click to expand...
Click to collapse
Exactly! Discovered it by myself during updates :cyclops:

Problem with internal storage message

Hello, I updated to 5.1.9 and after update as usual I flashed twrp 3.2.2.0 and then the installer, rebooted then flashed magisk 16.7. Now Everytime I reboot I get this message "There is a internal problem with your device, please contact your manufacturer for details" I see this is a harmful message but Everytime I reboot it gives me this message. How do I fix this?

Flashing magisk 16.4 or a custom kernel should fix it. Issue with dmverity afaik.

adizz4 said:
Flashing magisk 16.4 or a custom kernel should fix it. Issue with dmverity afaik.
Click to expand...
Click to collapse
Flashed magisk 16.4, the message doesn't go and I don't want to flash a custom kernel

Ｉdo have the similar issue as well after upgraded to 5.1.9
had updated 5.1.9 through OTA update and tried to install Magisk again before rebooting, but didn't help to keep the root.
fastboot boot with twrp to install twrp
then flash magisk and reboot into system then start getting that message "There's an internal problem with your device. contact your manufacturer for details"
after hitting ok, phone still works fine, except finger print and wifi isn't worki
anyone know how can I fix this issue?
Thank you

Harsh Keswani said:
Flashed magisk 16.4, the message doesn't go and I don't want to flash a custom kernel
Click to expand...
Click to collapse
Did you flash first the magisk-uninstaller before flashing the magisk 16.4?

joskhki said:
Did you flash first the magisk-uninstaller before flashing the magisk 16.4?
Click to expand...
Click to collapse
No

Harsh Keswani said:
No
Click to expand...
Click to collapse
Do that and it should work.

I also have this issue, will Uninstal magisk now and then reinstall fix this?

leonalewis said:
I also have this issue, will Uninstal magisk now and then reinstall fix this?
Click to expand...
Click to collapse
Uninstall Magisk and then install Magisk 16.4. Let Magisk update itself after that. Every time I tried to flash 16.6 or 16.7 I got that error message. Just use 16.4 to get it installed, then let Magisk handle updating to newer versions.

[ROOT] and [Solve] every issue in oxgyen os open beta {1/2/3} (Android pie 9.0)

I've managed to solve all problem by rooting and installing magisk
1. Some apps may not work properly
I have tried every app I used in oreo and each app works fine (I know this is not a solution )
2. Google pay not works
Solution-Google pay works by using a magisk module called
*tezhider4magisk*
https://androidfilehost.com/?fid=5862345805528042557
3. Google play shows device not certified
Solution - Google play shows device is certified using magisk module called
*ClearPlayStoreWithServiesData4Magisk*
https://androidfilehost.com/?fid=890278863836289937
4. Safety net not passed in magisk on open beta 1/2/3
Solution - for safety net to pass in magisk we need to edit a line in build.prop (have to some file explore like es file explorer or root explorer to edit build.prop)
Replace
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1808301430:user/release-keys
Click to expand...
Click to collapse
With
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Click to expand...
Click to collapse
5. For rooting oxgyen os open beta 1/2/3
Follow guide from developer [Manikandanguru] (all thanks to him?)
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853

Is there a fix yet for aod/ambient display yet?

Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/

For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.

sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Doesn't work, crashes display settings.

sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?

Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
For me aod/ambient display works perfectly
Have you dirty flashed new beta
Try doing a factory reset I hope that will fix it

BossNexusS said:
For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.
Click to expand...
Click to collapse
Try clearing cache from recovery that solves a lot of issues

Gmos24 said:
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?
Click to expand...
Click to collapse
Woah! Sorry about that, I guess I should have tested it first on P. I'll flash OOS Open Beta 2 today and then try this mod. Will update if it works.
And status bar issue is a strange one, no idea about that!

Can we get incremental ota update even when unlocked and magisk installed (no twrp)?

I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now

droid-devz,
Flash Oos ob02, then twrp blu spark.
Reboot to twrp to check if it's working. Flash Magisk 17.1.
Reboot to system.

Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Yess i just updated from beta 1 to beta 2 no problem
You'll just lose root everytime you update and have to install just magisk again
Don't install custom recovery that causes problems I guess use the above method (in the thread)

droid-devz said:
I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now
Click to expand...
Click to collapse
Official twrp doesn't work only blue star twrp works

Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Probably not..magisk root rewrites the boot image..safest bet would be to use update manager to flash whole rom updates, then reinstall magisk.

CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?

JRevenge said:
CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?
Click to expand...
Click to collapse
does not happen with me !!!

Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?

digidude512 said:
Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?
Click to expand...
Click to collapse
safety net passes with current canary build of magisk
plug this into the custom section in the magisk settings under update channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json

sorry, hit send before it finished uploading

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)

You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.

DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.

The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.

tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk

s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.

You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.

mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3

MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part

You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2

Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!

Next time don't be a twrp and use twrp

dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update

Android 11 Beta 1 (Jun 2020)

Hi guys,
I hvae flashed Android 11 Beta 1 on my Pixel 4 (not XL, i am posting here as we have more activity) , below what i have tried so far and sucessfully worked
to download
https://developer.android.com/preview/download
* Face unlock did not worked at the begining as it told me to delete the old face data first, so i hade to factory rest the phone from settings at the first launch then it worked perfectly
* the issue with Face unlock caused by Android DP4, is gone
* i have successfully rooted through Magisk Canary update, uploaded Magisk manager canary APK, once you install it make sure to change the update channel to canary and then update to the latest version
* Enable Soli worked perfectly with Magisk with v1.2, uploaded
i have no issues at all with this release, and very stable and fast.
hope you enjoying as i do, happy flashing

Can you root with the patched magisk boot.img way?

sruel3216 said:
Can you root with the patched magisk boot.img way?
Click to expand...
Click to collapse
Yes just patch the boot image with the canary magisk and flash it via fastboot.
Google Pay seems hard, im with latest magisk manager. Enabled the following packages in magisk hide. Safety net is ok
com.google.android.ext.services
com.google.android.apps.walletnfcrel
com.google.android.gms
com.google.android.gsf
com.paypal.android.p2pmobile
Click to expand...
Click to collapse
And the database patched with sqlite3 but still i cant add cards

fuarkgl3 said:
yes just patch the boot image with the canary magisk and flash it via fastboot
Click to expand...
Click to collapse
Is canary a special magisk for beta?

sruel3216 said:
Is canary a special magisk for beta?
Click to expand...
Click to collapse
For Android 11 dp and beta yes

Does anyone have the magisk patched boot.img handy?

fuarkgl3 said:
For Android 11 dp and beta yes
Click to expand...
Click to collapse
I'm stock rooted on Android 10. Can I simply flash the 11 system image without the -w, uninstall current magisk app, then install canary magisk?
Thanks

tonyfiore75 said:
Does anyone have the magisk patched boot.img handy?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-ePR1oRNBjs86WM0V2oiewZ1iNSKpDB3/view?usp=drivesdk
For pixel 4 XL patched with latest magisk canary
sruel3216 said:
I'm stock rooted on Android 10. Can I simply flash the 11 system image without the -w, uninstall current magisk app, then install canary magisk?
Thanks
Click to expand...
Click to collapse
You need to wipe all your data. I had to flash the image with -w twice because face unlock wasn't working so i had to go to stock recovery and wipe from there (titan m wipe) and flash again

fuarkgl3 said:
https://drive.google.com/file/d/1-ePR1oRNBjs86WM0V2oiewZ1iNSKpDB3/view?usp=drivesdk
For pixel 4 XL patched with latest magisk canary
You need to wipe all your data
Click to expand...
Click to collapse
Uhhh damn it. Il wait for some reviews on 11 and see if it's worth wiping for

Does Pokemon go work?
Sent from my Pixel 2 XL using Tapatalk

Gpay doesnt work even with unrooted and locked bootloader. I

cimbajunior said:
Gpay doesnt work even with unrooted and locked bootloader. I
Click to expand...
Click to collapse
It was the same way last year with the Android 10 Betas. The betas are not considered a supported version by Gpay.

Hey anyone on 11 beta 1 and rooted , on dark mode can you share your Settings app screen because I read online the app icons are now dark instead of white but for me only the Wifi (network and internet) icon is dark but all the others are white. See here
https://drive.google.com/file/d/1IY8vRIpm53RckReMq92KgApKdtVc2E1d/view?usp=drivesdk

I don't know if anyone is on Google Fi here but I noticed that after installing the 11 beta my Google Fi VPN no longer seems to work. Anyone else have this experience?

Jiggs82 said:
Hey anyone on 11 beta 1 and rooted , on dark mode can you share your Settings app screen because I read online the app icons are now dark instead of white but for me only the Wifi (network and internet) icon is dark but all the others are white. See here
https://drive.google.com/file/d/1IY8vRIpm53RckReMq92KgApKdtVc2E1d/view?usp=drivesdk
Click to expand...
Click to collapse
Screenshot attached (hopefully).

tonyfiore75 said:
Screenshot attached (hopefully).
Click to expand...
Click to collapse
Hmm weird idk why my icons in settings show mostly white still .. hope I don't have to factory reset ugh lol

cimbajunior said:
Gpay doesnt work even with unrooted and locked bootloader. I
Click to expand...
Click to collapse
yes i have tried to fix gpay but it does not work on dp1 even when cts profile and basicintegrity pass... i have added sq lite and busy box and have even tried the command prompt hack to edit the .db and no go..'
also cannot make bubbles work. when i enable .... and receive a message it does not come thru.

Sweet.

tonyfiore75 said:
I don't know if anyone is on Google Fi here but I noticed that after installing the 11 beta my Google Fi VPN no longer seems to work. Anyone else have this experience?
Click to expand...
Click to collapse
Never mind. I got it fixed. I had to delete the old VPN first. Then I reapplied the Google Fi VPN and it worked. I never had to do that before so that's sort of interesting. I hope this helps someone but hopefully no one has to deal with it at all.

my CTS profile passes, even without Magisk...though I installed cleanslate kernel which is AWESOME even without root.