Related
I want to know if I will forever lose the ability to install stock updates once I root my device. Can I "unroot" it in the future to seamlessly install stock updates? I don't want to mess with this too much as I want to rely on it for notes.
Yes. Use OTA rootkeeper to backup your root, then just temp unroot, install update, and restore root. Catch is, if you make any system changes that you can only make with root permissions, you'll likely not be able to get OTA updates. So just keep your system stock.
sputnik767 said:
Yes. Use OTA rootkeeper to backup your root, then just temp unroot, install update, and restore root. Catch is, if you make any system changes that you can only make with root permissions, you'll likely not be able to get OTA updates. So just keep your system stock.
Click to expand...
Click to collapse
If I were to modify the Snote app, I guess that may mess with the OTA update right? What if I backup the unmodified app and then replace the modified one with the unmodified one when I want to do an OTA update, I guess that should be fine?
litetaker said:
If I were to modify the Snote app, I guess that may mess with the OTA update right? What if I backup the unmodified app and then replace the modified one with the unmodified one when I want to do an OTA update, I guess that should be fine?
Click to expand...
Click to collapse
Depends on what you mean by modify. If you remove built in apks, yes, it'll keep you from getting OTA updates. If your modification requires root permissions, you run the chance of not getting OTA updates. Otherwise, you shouldn't have issues. In any case, restoring the stock app should allow you to get updates assuming nothing else is changed.
sputnik767 said:
Depends on what you mean by modify. If you remove built in apks, yes, it'll keep you from getting OTA updates. If your modification requires root permissions, you run the chance of not getting OTA updates. Otherwise, you shouldn't have issues. In any case, restoring the stock app should allow you to get updates assuming nothing else is changed.
Click to expand...
Click to collapse
Are there any "non-root" mods for the S-note? Or perhaps can I install another version of s-note as a "non-system" app? I want to keep rooting as the last resort. Specifically, I am looking into modifying the background of a template.
I know I can manually choose a different background for the note, but I noticed that the option to insert a voice memo and the button to insert any object vanish after I change the background. See attached pictures. Is there a fix for this?
https://www.dropbox.com/s/b9krlhjzy1mmjsp/2013-10-10 16.50.50.png
https://www.dropbox.com/s/olsor30fl74077p/2013-10-10 16.49.19.png
litetaker said:
Are there any "non-root" mods for the S-note? Or perhaps can I install another version of s-note as a "non-system" app? I want to keep rooting as the last resort. Specifically, I am looking into modifying the background of a template.
I know I can manually choose a different background for the note, but I noticed that the option to insert a voice memo and the button to insert any object vanish after I change the background. See attached pictures. Is there a fix for this?
https://www.dropbox.com/s/b9krlhjzy1mmjsp/2013-10-10 16.50.50.png
https://www.dropbox.com/s/olsor30fl74077p/2013-10-10 16.49.19.png
Click to expand...
Click to collapse
I don't have an answer for you unfortunately as my use of s note is very basic. I hope someone else can answer your questions.
If you root at all you lose OTA even if you do nothing and unroot. (I just went through this) Have you looked at any other apps that offer similar functionality to SNote or are you looking for multivendor? I know I we tried Papyrus and SPen voice but they were overkill for my needs.
Sent from my GT-N5110 using Tapatalk 4
CASz said:
If you root at all you lose OTA even if you do nothing and unroot. (I just went through this) Have you looked at any other apps that offer similar functionality to SNote or are you looking for multivendor? I know I we tried Papyrus and SPen voice but they were overkill for my needs.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
I just figured out how to fix my problems with SNote. So I can stick with stock still.
CASz said:
If you root at all you lose OTA even if you do nothing and unroot. (I just went through this) Have you looked at any other apps that offer similar functionality to SNote or are you looking for multivendor? I know I we tried Papyrus and SPen voice but they were overkill for my needs.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Absolutely false. I have been through probably 5 different OTA updates on my stock, rooted Note 8, and restored root with OTA rootkeeper every time. You're doing something wrong. I have never flashed anything to the device, and once you start messing with recoveries, etc, you are no longer stock and will not get OTA updates.
sputnik767 said:
Absolutely false. I have been through probably 5 different OTA updates on my stock, rooted Note 8, and restored root with OTA rootkeeper every time. You're doing something wrong. I have never flashed anything to the device, and once you start messing with recoveries, etc, you are no longer stock and will not get OTA updates.
Click to expand...
Click to collapse
Once I used the ToolKit to root, without a custom recovery, any attempt to update showed as altered and unavailable for updates even though I didn't flash anything. Whatever ToolKit did, triggered the need for triangle away on my Note 8. Moot point now as I have no plans to root again but if I do, I will look into OTA rootkeeper.
---------- Post added at 01:51 AM ---------- Previous post was at 01:51 AM ----------
litetaker said:
I just figured out how to fix my problems with SNote. So I can stick with stock still.
Click to expand...
Click to collapse
What did you do?
CASz said:
Once I used the ToolKit to root, without a custom recovery, any attempt to update showed as altered and unavailable for updates even though I didn't flash anything. Whatever ToolKit did, triggered the need for triangle away on my Note 8. Moot point now as I have no plans to root again but if I do, I will look into OTA rootkeeper.
Click to expand...
Click to collapse
I don't know what the ToolKit does or what else you used it to do or what else you did with the system after rooting, but just plain root does not alter the system. Even apps like Adfree that modify the hosts file don't cause the system to be altered. If you remove system APKs though, that will do it. Like I said, I am still rooted despite all of the updates that I received. And I do not temp unroot prior to searching for updates, I temp unroot once the update is already downloaded.
CASz said:
What did you do?
Click to expand...
Click to collapse
My concern was how to obtain a custom background for the notes in S-note. I did it using the "change background" feature but I did so with the "memo" template. And the memo template doesn't have certain features like inserting images, audio memo etc. Given that I am new to Samsung and touchwiz I was unaware about this. I fixed this "problem" by putting my custom background on one of the other templates...
The only other thing I need root for is for removing Ads. BUT, thankfully there is the "Adblockplus" android app on their website that allows me to do this WITHOUT root! :highfive: On Android, nothing is impossible!
Unroot
I have rooted my device as well. What i want to ask is, is there a way to completely unroot and have the device check whether there are any updates?
I did use the unroot function but when I checked for any updates, it told me that the device had been modified..
thx
athosk said:
I have rooted my device as well. What i want to ask is, is there a way to completely unroot and have the device check whether there are any updates?
I did use the unroot function but when I checked for any updates, it told me that the device had been modified..
thx
Click to expand...
Click to collapse
Sounds like you modified the system in some way. Only way out is to unmodify it ie: ODIN or use kies to go back to stock. Might as well just use kies to install the latest update.
sputnik767 said:
Sounds like you modified the system in some way. Only way out is to unmodify it ie: ODIN or use kies to go back to stock. Might as well just use kies to install the latest update.
Click to expand...
Click to collapse
When that happened to me, I couldn't even use Kies to recover so I used the ToolKit and triangle away to get a stock ROM on it.
I have the same problem. As far as I know I've only done a standard root, but OTA says the device has been modified and Kies says my firmware version doesn't support upgrading. Obviously something has modified something
As I'm in Australia we probably won't get a 4.2.2 upgrade anyway so at the moment I wouldn't have anything to upgrade to even if I could...
Sent from my Galaxy Note 8 using Tapatalk
You Can Do It
CASz said:
If you root at all you lose OTA even if you do nothing and unroot. (I just went through this) Have you looked at any other apps that offer similar functionality to SNote or are you looking for multivendor? I know I we tried Papyrus and SPen voice but they were overkill for my needs.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
If you first use supersu option to unroot you can can get ota. Been there done that.
There is a post on this forum somewhere. Can't remember where, but it can be done if you follow the instruction in the post.
Do a search of the forums to find it. It's there!
My question is regarding the system notification that says "system update downloaded" bassicly this update is a February 2016 security patches for Nexus 5X. Now my question is : Is it safe for me to install it ? ( I am rooted ( systemless), have twrp installed while on stock rom), if it isn't then how can I get rid of this notification?
yes, you can safely install it. no you won't be able to without further setup because of the way OTAs work (manual flashing via PC, FlashFire by Chainfire). you should be able to get rid of the notification by long-pressing it (which may disable other notifications as well).
Broken303 said:
yes, you can safely install it. no you won't be able to without further setup because of the way OTAs work (manual flashing via PC, FlashFire by Chainfire). you should be able to get rid of the notification by long-pressing it (which may disable other notifications as well).
Click to expand...
Click to collapse
"yes, you can safely install it. no you won't be able to without further setup because of the way OTAs work"
I am sorry maybe I am having troubles with reading with understanding but can I safely install it or can't I?
wojwem19 said:
"yes, you can safely install it. no you won't be able to without further setup because of the way OTAs work"
I am sorry maybe I am having troubles with reading with understanding but can I safely install it or can't I?
Click to expand...
Click to collapse
sorry, wasn't the best way of explaining it. you are safe to flash it, in the sense that it won't (or shouldn't) mess up your system. the system won't let you though, because in the process of the OTA update your system gets checked for modifications (root, adblockers, xposed...). if that process failes, so does the OTA update process and you get send back to your OS as it was and eventually the notification will pop back up again. therefore if you want to take the update, you have to flash it another way. one way is using your pc, there are even toolkits which automate most of the process and guide you through it (there are some very detailed and useful guides here on the forum, just do a quick search). another option is Chainfires FlashFire (which still has its quirks).
So, can you tell us how to install it via PC or provide the link that explains how to do it? Because the notification in not.center is a bit of annoying. Thanks!
Bottom line: you can not install an OTA if you have modified the system which means if you are rooted or have installed a custom recovery the OTA will fail. Even if you use a PC and use the ADB program, it will fail. There are many ways to update your system to the latest release using fastboot. Searching this forum has spelled out this process countless times. the search bar is your friend.
Problem that I now have is that it restarts to update, then it enters TWRP custom recovery. I flashed back the stock recovery to keep important OTA updates.
Yaz75 said:
the search bar is your friend.
Click to expand...
Click to collapse
exactly, thank you.
just as an example: searching the N5X forum for 'toolkit' leads me to several threads. this is one of those and further leads me here. oh, look, there is even a faq-section there and more specifically several possible solutions using this toolkit alone.
i don't intend to sound mean here, but with quick checks like that you can not only safe yourself some time.
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
sliding_billy said:
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
Click to expand...
Click to collapse
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
pcriz said:
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
Click to expand...
Click to collapse
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
sliding_billy said:
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
Click to expand...
Click to collapse
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
pcriz said:
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
Click to expand...
Click to collapse
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
sliding_billy said:
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
Click to expand...
Click to collapse
I can't see the initial process of loading it changing. Right now there are issues with restoring but if you don't make a back up it won't affect a thing but it will make flashing mods and updates to the TWRP easier.
Aside from using a tool kit, installing it seems to be spot on so long as all the steps are followed.
So once a stable build comes out I will simply flash in the TWRP I currently have.
I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!
If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?
jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.
alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?
The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?
Hi I've never wanted to root or custom ROM. I read the instructions and they are pages deep and the issues that come up and are discussed in threads have such confusing back and forth discussions using lingo and abbreviations that make my head spin.
However... Oneplus did their last update on my 5t my fourth oneplus phone... With an already old security update.
Is the only way to not throw away a perfectly working, phone with good Ram and a fairly new battery I paid to have installed just months ago?
If I'm wanting to hold on another year or 2 use the only option custom ROMs that contain security updates?
Is there a way to add security updates without a ROM? Or maybe at least just learn to root and then add just updates or is it only in ROMs?
I could probably happily use my phone as is but worried what effect no security updates really is to my use.
I really tried videos on doing so this myself I'm not comfortable if problems happen. Not very techy.
Any help appreciated
Unfortunately you can no longer get security updates once your device is deemed as old.
Your options will be to get an antivirus app on your phone, install a custom ROM (like LOS or pixel exp), or you can get a new phone.
Since you're new to this stuff I highly recommend you just get a new phone or simply install an antivirus.
Not sure which anti virus is better than which. But I'm confident in Avira, McAfee, and Norton. You may want to purchase their plan though.
Hope I helped.
Thanks alot for the reply. I'll start with an antivirus.
Hello,
I have similar issue, since I would need security patch update to keep running company mails and apps.
I have 2 doubts:
- if I root and install Android 11 custom ROM, security patches will be updated too?
- after this, would I be able to unroot and install company mail apps ( if rooted they will not work) ?
Thanks
Personally I think that your company has put an unfair burden on you to run company mail and apps on your personal phone while expecting you to have an updated phone at the same time. An updated phone should have been "given" to you.
That being said, you can actually flash and run a custom rom without root. Root is optional.
Process is as follows: (you'll need a PC for this)
1. Backup ALL your data
2. Unlock the bootloader
3. Install custom recovery and reboot to recovery
4. Wipe cache & system and format internal memory
5. Copy custom rom & gapps to internal memory
6. Flash custom rom & gapps and reboot system
miloinodense said:
Hello,
I have similar issue, since I would need security patch update to keep running company mails and apps.
I have 2 doubts:
- if I root and install Android 11 custom ROM, security patches will be updated too?
- after this, would I be able to unroot and install company mail apps ( if rooted they will not work) ?
Thanks
Click to expand...
Click to collapse
Yes if you install custom ROM you'll have security updates. It doesn't have to be Android 11 and you don't need root to install a custom ROM.
Also make sure to follow a precise guide about it so you don't encounter any issues. Always make a backup even if you're 100% sure you won't need it.
As far as I know mail apps don't check the integrity or do a SafetyNet check, so even if you root or don't it will work fine.
If you mean banking apps then you can install some modules to bypass the check or just completely remove root. Assuming that you rooted the device.
It shows my lack of knowledge never ever did I think you could Flash a ROM without being rooted.
Thanks
I successfully installed custom ROM w/o root.
But regarding company mail apps, I would need to hide bootloader unlocked status.
maybe it's impossible, if someone has a good idea...
miloinodense said:
I successfully installed custom ROM w/o root.
But regarding company mail apps, I would need to hide bootloader unlocked status.
maybe it's impossible, if someone has a good idea...
Click to expand...
Click to collapse
My banking apps working fine without root with crdroid 7.3 and flamegapps. Might work for your company mail app too.
Some roms readily hide bootloader status
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
Hence that's why the burden should be on the company to provide the "up to date" phone
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
And that's why the burden should be on the company to provide the "up to date" phone
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
I think if you change build.prop to some other phone with recent security patches you can bypass this.
XDHx86 said:
I think if you change build.prop to some other phone with recent security patches you can bypass this.
Click to expand...
Click to collapse
Today, I was thinking that this could be good way.
Root, change build.prop, and then unroot.
If you have a link for a good tutorial on change bulid.prop would be nice, thanks.
miloinodense said:
Today, I was thinking that this could be good way.
Root, change build.prop, and then unroot.
If you have a link for a good tutorial on change bulid.prop would be nice, thanks.
Click to expand...
Click to collapse
Just for update:
I tried to Root a stock ROM, edit build.prop (security patch date), unroot, and then lock bootloader.
But even if it was a stock ROM, OP5T was not booting.
Booloader was stopping boot since it was detecting a non-stock ROM.
Indeed, I had to unbrick OP5T since I was not possible to unlock bootloader.
So, still not solved
miloinodense said:
Just for update:
I tried to Root a stock ROM, edit build.prop (security patch date), unroot, and then lock bootloader.
But even if it was a stock ROM, OP5T was not booting.
Booloader was stopping boot since it was detecting a non-stock ROM.
Indeed, I had to unbrick OP5T since I was not possible to unlock bootloader.
So, still not solved
Click to expand...
Click to collapse
Just edit build.prop and use magisk hide module from magisk manager.
XDHx86 said:
Just edit build.prop and use magisk hide module from magisk manager.
Click to expand...
Click to collapse
Edit build.prop w/o root and unlock bootloader is not possible...
Moreover, hiding root will not work with more recent android updates and for sure it will not hide unlock bootloader.
miloinodense said:
Edit build.prop w/o root and unlock bootloader is not possible...
Moreover, hiding root will not work with more recent android updates and for sure it will not hide unlock bootloader.
Click to expand...
Click to collapse
Yeah I assumed you would know that you should root first. But seeing you even attempted to lock bootloader after modifying the device, seems I assumed wrong.
Magisk hide is working fine on later android versions like 8+. And for the bootloader it only trips CTS if your bootloader is using hardware backed key - Which is the case with OP5 - as CTS check also has hardware attestation. But it is possible to bypass said check by using SafetyNet Fix module, of course you will also install that from magisk manager.