[OnePlus 7 Pro Guides, News, & Discussion] pr3dicament:
Short answer: Yes, you can go back to stock. No, there's no KNOX tripping, as your phone is not a Samsung. You simply would re-lock it via ADB. I unlocked my boot loader for my OnePlus 6T and that's how I installed TWRP and everything else. Now, unlocking it can trip SafetyNet, but OnePlus doesn't have the whole Samsung Knox battle going on.. You have to do a lil' bit of research, but generally, you can end up unlocking your boot loader. From there, in recovery, you'll be given many more options. Also.. you can always re-lock the boot loader and reset everything to factory defaults and you wouldn't have a problem.. maybe a warranty issue, at worst.

LONG ANSWER: If you have to ask this question, then you clearly need to do some more research on this. Here's what'll happen.. you unlock your boot loader, you then install TWRP, then you install your actual Oxygen OS v10 or 11 or whichever ROM of your choosing, assuming it's compatible with your OnePlus 7 Pro. Then you'd flash Magisk in order to get your phone rooted and working. Magisk is pretty much your only choice anyway. You are likely able to re-lock the boot loader, because an unlocked boot loader is something that trips SafetyNet. However, all of that said, after you're rooted, you wouldn't pass SafetyNet, especially when unlocking the boot loader.

You'd need to install the MagiskHide Props Config module (search for it in Magisk Manager) so you can actually change the fingerprint of your device to a simulate a fingerprint of a compatible device. Hell, it could be a google pixel that you choose.. but with OOS, just go with the OnePlus option. When you do this, you usually have to Force BASIC key attestation among other things (see below) and SafetyNet notices this, and therefore asks for the aforementioned phone fingerprint, thus returning a string with something that is compatible with your ROM and device, thus passing SafetyNet. It will show up as a red dialogue if it fails and a blue one if it succeeds/passes. This is a very short version of what actually happens, because this is under the assumption that you know how to use MagiskHide and that you were to realize it's DISABLED BY DEFAULT, so you MUST ENABLE MagiskHide and hide just about all Google APPS; most, if not all.. I do EVERY SINGLE ONE in MagiskHide, though that's not usually necessary. Ideally you usually would just need to hide the following:

Google

Google Play Store

Google Play Services

Google Services Framework

Google Pay

Google Home --- This app is usually optional and probably not necessary, but I'd do it anyway if it's not gonna cause a problem.

Other Important Apps that seek to find "root" i.e. Banking Apps. Always add anything like that to the list. Don't add apps that require root access though--Then Magisk won't be able to grant it root privileges.

You'll need to *Hide Magisk Manager* as well. This isn't the same as MagiskHide. It's located under Magisk Manager's settings. Doing this will repackage it and rename it with a random package name. When you do this, you'll notice a screen pop up after it's finished repackaging; this pop up is going to give you an opportunity to add a shortcut to the home screen for the newly minted (and now hidden) Magisk Manager. It will literally ask you to name it something that isn't obvious. ***DO NOT*** IGNORE THIS

After you do this, clear your storage AND cache for ALL of the above apps that you placed under MagiskHide by using the Oxygen OS Settings Manager; Just go to "Apps and Notifications" and go to the top right where there's a little search box icon. Press that, type in an app name, for instance, "Google Services Framework" and you will see it, so press on the App that appears from Searching. Once you do that, it will immediately bring you to the "App info" screen. You'll see "Storage & cache" .. go to that, and then press CLEAR STORAGE. Do this for each app listed above, ESPECIALLY the google ones. This is honestly MUCH easier than this mini-guide seems to lead on, I can tell you that. Another quick wrinkle:

After that, you'd run MagiskHide Props Config with the Terminal Emulator app. You can get Terminal Emulator from the Google Play Store. Install it, open it, grant Terminal Emulator ROOT privileges by typing the following in Terminal Emulator:

su

then press Enter/Return. The dialogue to give it root access will then magically appear; GRANT IT ACCESS. After that, if you've installed the MagiskHide Props Config module as mentioned above (Just go to modules, search to download it, FLASH it, reboot, just like you would with any other Module), then all you need to do is type this in Terminal Emulator:

props

.. Then, you'll notice that it starts running. It's text-based, but it's very simple and easy to navigate. You'll be prompted to do many different things including Device Emulation and to FORCE BASIC KEY ATTESTATION. You can find more information by searching "MagiskHide Props" in the forums here at xda. This is pretty much where it ends. Also, make sure you edit a CUSTOM prop in MagiskHide Props Config, and it's ro.build.version.security_patch --- You'll be changing the date to something like the 1st March 2020. Anything past March 1, 2020 is when it will fail.. until, lately, that is.. it seems to me that whilst writing this guide, I actually reset that prop value and it still passes SafetyNet (without EdXposed) .. it used to require me to have my patch level below March 2, 2020, so I always used March 1, 2020. So you might be able to skip the custom prop.. not sure what happened with Google's end but they were ****ing around with something that changed this. See, this thread is about EdXposed. You said you're kinda new to this.. well, EdXposed is for advanced users. There are guides to get that installed and it really isn't hard. It's all Graphical User Interface. All of this is. Arguably, the hardest part, would be understanding what you're doing.

See how you're posting in a thread that's supposed to be about EdXposed/SafetyNet testing and you're just essentially asking if whether or not rooting your phone is worth it because of the tug-a-war with Google? This thread is ALL about EdXposed only. We haven't even gotten there yet within this hypothetical synopsis of what's likely to happen if you were to correctly follow the instructions I just gave. Once you install EdXposed, it WILL NOT pass SafetyNet no matter what you do until further notice, basically. But.. people do not take kindly to this. Trust me, just about every user looked at this post and just skimmed right over it or went elsewhere immediately. Just make sure you post in the right places. Otherwise, you won't get any answer, especially in that form of a question. I decided to have some mercy here and give you a guide along with some references, along with some do-nots, and this is a do-not. Someone will probably try to bite my head off for writing this and I'm sure they'll find something that I missed or whatever but.. see below lol.

This guide honestly just stems off of the top of my head because I've had to do this so many times while troubleshooting. I suggest that you look in the OnePlus 7 Pro forums for the best answer(s), because if you have to ask this question, then you probably should stay away from trying to modify your device. Is there something in particular that you enjoy with having the su binary (root access) readily available? Do you need it? Honestly though, this thread is about EdXposed, not whether or not you should even bother with root access due to Google being soul-less dogs. That's something you need to decide. If you've gotten by without it, why bother then? Just a thought that's piggybacking on your question. People on here DO NOT LIKE questions like yours in these types of threads, and believe me.. I've been there. I checked the OnePlus 7 Pro Forums and immediately found a tutorial, such as:

https://xdaforums.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368

^ The above should suffice It has everything I mentioned. Just do the work, make sure you keep researching, know what you're doing, and you'll be alright. Research MagiskHide Props on xda forums or at Magisks' git. Make sure to install the BusyBox for Android NDK Module (BusyBox v 1.31.1) within Magisk (Just search for it in Magisk Manager). DO NOT use ANY of the BusyBox **** from the Google Play Store. Not even the "official" one.

Alright, I'm wrapping this up. Good luck, my friend. My sincerest apologies to the rest of you; You guys don't even need to read this--Only the person that's quoted.

T.L.D.R? .. ..Good luck. It's best you just read it. If it was that easy for me for something as simple as root access, then it should be fairly easy for you. I sure hope so because I spent a good half hour writing this for you, and I promise you, no one here even gives a **** about this. This is all about EdXposed. Remember to look at the topic being posted. 99% of the users will overlook anyone asking if it's "worth it" .. just trust me. You either want to follow the guide or you don't. That's all I've got for you. I hope you appreciate my candor at the least.