• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Noob Bootloader Unlock Guide: Answers to several questions and solutions to problems.

Search This thread

C4sp3R911

Senior Member
Feb 6, 2008
85
25
Wherever they send me
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***

A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.

The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:



1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?

Solutions and answers:

1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:

If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:

-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)

Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging

Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok

Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)

2)-This step fixes the driver issue that likely causes problem #1.

Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio

Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish

If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.

To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.

WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!

Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.

Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on

3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google

4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet

5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.

6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.

Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.
 

C4sp3R911

Senior Member
Feb 6, 2008
85
25
Wherever they send me
Saved

Update:
How to fix SafetyNet failure:

Get Root
-Follow this link: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-auto-root-tool-oneplus-7t-pro-t4079355#post82221323
This is hands down the easiest root method I have ever seen for any device. HUGE shoutout to @daxiaamu and @mauronofrio for this!

Install Magisk Manager
On Your phone go to https://github.com/topjohnwu/Magisk/releases/
and download the latest version of Magisk Manager.
Allow unknown sources> install

Update Magisk
Once in Magisk Manager it will prompt you to install some updates for our phone. Install them and let it reboot.

Install Magisk Hide
Open Magisk>Three lines in top left corner>Downloads>MagiskHide Prop Config>download>install

Test
Once your phone has rebooted open Magisk>SafetyNet Check Status>Prosper!

Thank you to the Magisk team for making this hands down the easiest experience I have ever seen on Android and to @daxiaamu for making a truly one-click install that works flawlessly!
 
Last edited:

otto888

Senior Member
This should be pinned, but I have ctsProfile: false.
Is that expected?

If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853

Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.
 
  • Like
Reactions: lucfig

C4sp3R911

Senior Member
Feb 6, 2008
85
25
Wherever they send me
This should be pinned, but I have ctsProfile: false.
Is that expected?

Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:

Open Magisk>settings>turn off magisk hide

Magisk>Downloads>MagiskHide Props Config> Download and reboot

Magisk>Settings>Turn on MagiskHide

Test again should be good
 

lucfig

Senior Member
Feb 19, 2008
895
261
Rio das Ostras
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:

Open Magisk>settings>turn off magisk hide

Magisk>Downloads>MagiskHide Props Config> Download and reboot

Magisk>Settings>Turn on MagiskHide

Test again should be good

Hope it gets more visibility, is the most detailed and easy to follow instructions.

I figured that out. Without riru or edxposed the Magisk hide works great.
 

C4sp3R911

Senior Member
Feb 6, 2008
85
25
Wherever they send me
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853

Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.

We were able to fix it through MagiskHide. Both methods above worked.
 

Attachments

  • Screenshot_20200514-133941.jpg
    Screenshot_20200514-133941.jpg
    121.9 KB · Views: 254

MDRZN

Member
Nov 13, 2015
24
5
Hey guys, I just received my OP7T today (upgrading from the 5T), and I see that there's no official TWRP yet. I've been looking around to see if it's worth it to root the phone already.
Is the rooting already stable enough, or should I wait a couple more months for full modded roms to come out? 'cause I really enjoy having the root features that some apps offer, but I also definitely need MagiskHide to work so my bank app won't have any issues with the unlocked bootloader.
If the guide above is up to date and working like C4sp3R911 posted, I'd be down to try it today.
 

mel2000

Senior Member
Apr 26, 2011
191
26
Could I still use the the following command if OEM Unlocking is grayed out in Settings? Thanks.
"fastboot flashing unlock"
or
"fastboot OEM unlock"
 

Skinpipe

Senior Member
Apr 5, 2013
427
170
West Midlands
What?... You need to learn a bit more before messing with bootloader unlocking, fastboot flashing unlock is not a command and will do nothing... Check yourself before you wreck yourself as the saying goes,

If it's greyed out doesn't that mean the BL is already unlocked?
 

spamerobaldomero

New member
Feb 14, 2021
3
0
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***

A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.

The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:



1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?

Solutions and answers:

1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:

If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:

-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)

Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging

Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok

Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)

2)-This step fixes the driver issue that likely causes problem #1.

Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio

Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish

If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.

To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.

WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!

Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.

Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on

3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google

4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet

5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.

6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.

Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.


Just bought the op7t pro and followed your guide step by step, but still fastboot devices does not show nothing to me

Tried in 2 different windows pc with same results, don't know how to do now
 

doncheadlesdriveway

New member
Jun 9, 2021
2
0
Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.
 

doncheadlesdriveway

New member
Jun 9, 2021
2
0
Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.
Great. Thanks for the help.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    ***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***

    A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.

    The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:



    1) ADB was not functioning properly with Windows 10.
    2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
    3) After Unlocking the bootloader I hit a "checking info" loop with Google.
    4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
    5) What does a SafetyNet failure result in?
    6) Will every app work with an unlocked bootloader?

    Solutions and answers:

    1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:

    If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:

    -Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
    -Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)

    Now to get Developer options:
    -On your phone>settings>about phone>Tap build number until it says you are a developer
    -Settings>system>developer options>turn on USB debugging

    Getting ADB set up on your computer:
    -Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
    -on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
    -Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
    -Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
    click ok>ok>ok

    Testing ADB:
    -Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
    -Plug your phone into the computer
    -In Command Prompt type "adb devices" and hit enter
    -You should now see your phone ID
    -Type "adb reboot bootloader" and hit enter
    -Your phone will reboot into bootloader
    -Type "fastboot devices" and hit enter
    -If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)

    2)-This step fixes the driver issue that likely causes problem #1.

    Get the newest Android drivers:
    -Download and install Android Studio: https://developer.android.com/studio
    -Launch Android Studio
    -Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
    -At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
    -Click Finish and close Android Studio

    Installed drivers for fastboot:
    -Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
    -windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish

    If that doesn't work and you get "Windows was unable to install driver" error do the following:
    -click search for updated drivers on windows update>a new window will come up> Update and restart your computer
    -Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.

    To Test if this fixed the issue:
    open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.

    WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!

    Now to unlock the bootloader:
    -In Admin Command prompt type "fastboot oem unlock" and hit enter
    -On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.

    Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on

    3) If you hit the "checking info" Google loop follow these steps:
    -Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
    -Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
    -Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
    -----Select Google play store >Storage & cache>Clear Storage
    -----Press Back
    -----Select Download manager> Storage & cache>Clear Storage
    -----Press Back
    -----Select Google play services> Storage & cache>Clear Storage>Clear All Data
    -Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
    -Restart device
    -Connect to Wifi
    -Go to Settings >Accounts>Add Account>Google

    4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet

    5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.

    6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.

    Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.
    4
    Saved

    Update:
    How to fix SafetyNet failure:

    Get Root
    -Follow this link: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-auto-root-tool-oneplus-7t-pro-t4079355#post82221323
    This is hands down the easiest root method I have ever seen for any device. HUGE shoutout to @daxiaamu and @mauronofrio for this!

    Install Magisk Manager
    On Your phone go to https://github.com/topjohnwu/Magisk/releases/
    and download the latest version of Magisk Manager.
    Allow unknown sources> install

    Update Magisk
    Once in Magisk Manager it will prompt you to install some updates for our phone. Install them and let it reboot.

    Install Magisk Hide
    Open Magisk>Three lines in top left corner>Downloads>MagiskHide Prop Config>download>install

    Test
    Once your phone has rebooted open Magisk>SafetyNet Check Status>Prosper!

    Thank you to the Magisk team for making this hands down the easiest experience I have ever seen on Android and to @daxiaamu for making a truly one-click install that works flawlessly!
    2
    This should be pinned, but I have ctsProfile: false.
    Is that expected?

    Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:

    Open Magisk>settings>turn off magisk hide

    Magisk>Downloads>MagiskHide Props Config> Download and reboot

    Magisk>Settings>Turn on MagiskHide

    Test again should be good
    1
    This should be pinned, but I have ctsProfile: false.
    Is that expected?

    If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
    https://twitter.com/topjohnwu/status/1251712525843918853

    Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.