Database Info

Magisk v14 - does it offer root without tripping Knox?

Hi guys
Magisk v14 has been released and it now offers installation without using custom recovery and still avaialble to use OTA's - does this mean I can root with Magisk (which it says is done by ADB) without tripping Knox? Description is below
"New Installation Method
Nearly a month ago, I introduced a way to install Magisk through ADB. This is nice for devices with no custom recovery support, or for people like me who wants to preserve stock recovery to apply OTAs. To make things even easier, I have added this feature natively into Magisk Manager. In Magisk Manager you can provide your stock boot image (in both raw image format or tar-ed up ODIN flashable format), the app will then patch the provided image. Other required files and scripts are extracted within the app's data, and will be picked up automatically while booting up once with a magisk patched boot image. Check the new instructions in the OP for more info.
Once your device has Magisk installed, you can install Magisk modules through Magisk Manager without custom recoveries. The powerful systemless interface means that you can literally do anything to your device - of course systemless-ly!"

I'm also interested in this. Hope someone knows if we can finally get root without tripping Knox.

Exactly.... if so then it really is the best of all worlds in my eyes

No, absolutely not. It still mods the boot.img which requires an unlocked bootloader. As soon as you unlocked the bootloader and it detects anything custom (Does not matter how it got there, if it's there, it's there) it will trip the fuse.

But doesn't the g955f already have an unlocked bootloader.. hence why it was easier to root before the g955u?

Knox is secure. It is only secure because the phone is not modified.
If you could root the phone and still use Knox then you (or someone else) could hack Knox. Do you want that?

RR-99 said:
Knox is secure. It is only secure because the phone is not modified.
If you could root the phone and still use Knox then you (or someone else) could hack Knox. Do you want that?
Click to expand...
Click to collapse
[upvote]

meddylad said:
But doesn't the g955f already have an unlocked bootloader.. hence why it was easier to root before the g955u?
Click to expand...
Click to collapse
It's bootloader doesn't work the same way a normal bootloader does. It still detects anything custom and will trip Knox if it does.
If you don't check the OEM Unlock option in settings, your phone will brick because the bootloader is locked. If you do check it, it's unlocked but still checks for custom firmware which then trips Knox.

Interceptor777 said:
It's bootloader doesn't work the same way a normal bootloader does. It still detects anything custom and will trip Knox if it does.
If you don't check the OEM Unlock option in settings, your phone will brick because the bootloader is locked. If you do check it, it's unlocked but still checks for custom firmware which then trips Knox.
Click to expand...
Click to collapse
through "embedded flash"
can be ignored Knox

And I got my hopes up for being able to root this phone I'll be getting in my post this week... Well, two years without root on that one it'll be unless some genius finds a way.

Interceptor777 said:
It's bootloader doesn't work the same way a normal bootloader does. It still detects anything custom and will trip Knox if it does.
If you don't check the OEM Unlock option in settings, your phone will brick because the bootloader is locked. If you do check it, it's unlocked but still checks for custom firmware which then trips Knox.
Click to expand...
Click to collapse
The G955u doesn't trip Knox with root, but it's system level because of the locked bootloader. What it does break though is SafetyNet which kills Samsung Pay and such.

I really need the auto recording feature which is blocked in my country. So need to root this without tripping.

google pay not work on pixel 3 unlock?

I have been root and flash kernel my pixel 3 before, but I want use google pay, so I flash factory img to my pixel 3.
But i use google pay it is still doesn't working. Is cause i root before?

Have you re-locked the bootloader? An unlocked bootloader will cause Google Pay to not work on stock firmware.

JujuYuki said:
Have you re-locked the bootloader? An unlocked bootloader will cause Google Pay to not work on stock firmware.
Click to expand...
Click to collapse
Is it a good practice to relock the bootloader after root? I though it will reenable signature checks and brick the phone?

Pakabidu said:
Is it a good practice to relock the bootloader after root? I though it will reenable signature checks and brick the phone?
Click to expand...
Click to collapse
If you flashed the factory image you're stock and not rooted, right? But yes you shouldn't lock the bootloader again after modifications. You can relock it after flashing factory image from google though if you fon't flash anything else and don't modify it. That's also the only way to get google pay to work without root and Magisk hide.
Also, as long as you don't untick "enable oem unlocking" in developper settings, you can still unlock if it bricks, as long as you have fastboot access. So if you happened to brick by relocking, just unlocking again (and flashing if needed) would solve it anyway.

JujuYuki said:
If you flashed the factory image you're stock and not rooted, right? But yes you shouldn't lock the bootloader again after modifications. You can relock it after flashing factory image from google though if you fon't flash anything else and don't modify it. That's also the only way to get google pay to work without root and Magisk hide.
Also, as long as you don't untick "enable oem unlocking" in developper settings, you can still unlock if it bricks, as long as you have fastboot access. So if you happened to brick by relocking, just unlocking again (and flashing if needed) would solve it anyway.
Click to expand...
Click to collapse
Thanks man, I'm thinking i have to re lock my phone now, or just wait new magisk can hide google pay.

Awesome how google sells a phone that is unlockable and easily rootable, but then blocks a service to the device. Luckily, where I am google pay is not an option, but I sympathize with you all.

Edemilorhea said:
I have been root and flash kernel my pixel 3 before, but I want use google pay, so I flash factory img to my pixel 3.
But i use google pay it is still doesn't working. Is cause i root before?
Click to expand...
Click to collapse
There is a ton of information on the Magisk page about running Google Pay on an unlocked/rooted device. I use it on both a Pixel 3 and Pixel 3 XL. Locking your bootloader is not necessary right now.

https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
this works.

Followed instructions and edited db and rebooted. Works great in Android 10 on Pixel 3. Thanks for this. I was wondering why wouldn't work on my new phone. So dumb to lock this down.

Relocking bootloader

So I want to root my phone only so I can use it with my daydream vr viewer. In order to do that I have to edit the build.prop and I think also some xml file.
My issue is that by unlocking the bootloader you lose widevine l1 so no more netflix HD.
So my question is: Can I unlock, root, edit the files, unroot, relock the bootloader and if I do, will my build.prop remain the same one or is it overwritten when relocking the bootloader? Also does the widevine l1 status come back after relocking?
Thank you in advance

Relocking the bootloader with mods such as root and/or custom recovery TWRP will typically lead to no boot. My understanding, is that the phone needs to be fully stock when locking the bootloader (for the reason stated). Not sure what the result will be from changing build.prop, then removing all other mods (root, custom recovery) and relocking the bootloader. But I'd say it is risky. May lead to no boot, and possibly even resorting to the unbrick tool to get it going again.
Another thing to be aware, is that modifying build.prop may have some undesired side effects. Better to use one of the Magisk modules to get Daydream running, which you can then turn the Magisk module off when not needed (not using Daydream). On my OnePlus 3T, the modified build.prop for some reason caused glitches with the stock camera app (would not take any video) for some reason. I've only played around a little bit with Daydream (and corresponding Daydream enabler Magisk module). I haven't noted any side effect (like I did with the 3T and the camera app). But it's something to at least be aware of.
https://forum.xda-developers.com/mo...agisk-daydream-cardboard-enabler-nfc-t3917601

Correct me if I am wrong, but to use magisk wouldn't I need to be rooted? so again I would not have netflix HD.

You're better off flashing a completely unmodified version of OOS then follow these instructions

poulidis said:
Correct me if I am wrong, but to use magisk wouldn't I need to be rooted? so again I would not have netflix HD.
Click to expand...
Click to collapse
Once you unlock the bootloader, Widevine gets lost permanently. No going back even if you relock. Also Magisk is your root access.

Zocker1304 said:
Once you unlock the boot loader, Widevine gets lost permanently. No going back even if you re lock. Also Magisk is your root access.
Click to expand...
Click to collapse
Please stop spreading lies. Once you unlock boot loader yes you do lose widevine (drops down to l3 so 480p playback) you definitely can get it back by simply flashing another stock zip from oneplus and rebooting and relocking the bootloader. Once done it will restore your widevine. Please do research before you attempt to state something that isn't fact. Also doing the msm download tool will always relock your bootloader and restore widevine back to its original state.

poulidis said:
Correct me if I am wrong, but to use magisk wouldn't I need to be rooted? so again I would not have netflix HD.
Click to expand...
Click to collapse
Magisk is the root method. So, yes, you would need to be rooted (and bootloader unlocked) to use the module. I'm suggesting the module as an alternative to "manually" changing build.prop, not as an alternative to rooting.

To add from my post above here is proof. Before this I was on Omni bootloader unlocked. I noticed TMobile dropped 9.5.9 and I wanted to test it. So I used the msm tool to go back to TMobile and took the ota updates to 9.5.9 now here I am with l1 access and full hd Netflix.

blackknightavalon said:
You're better off flashing a completely unmodified version of OOS then follow these instructions
Click to expand...
Click to collapse
I don't think you are properly understanding what the top poster is trying to do (or asking). He wants to keep(restore) Widevine L1 status (by relocking the bootloader) while still having a modified build.prop (so Daydream VR will work, which it will not on a fully stock 7 Pro).

redpoint73 said:
I don't think you are properly understanding what the top poster is trying to do (or asking). He wants to keep(restore) Widevine L1 status (by relocking the bootloader) while still having a modified build.prop (so Daydream VR will work, which it will not on a fully stock 7 Pro).
Click to expand...
Click to collapse
It won't work as dm verity will kick in and not allow the phone to boot. It checks if anything has been modified and if it has it will flag the phone and make it unbootable

joemossjr said:
It won't work as dm verity will kick in and not allow the phone to boot. It checks if anything has been modified and if it has it will flag the phone and make it unbootable
Click to expand...
Click to collapse
That was basically what I suspected (see Reply #2 above) but thanks for confirming/explaining it.
My reply that you quoted was in response to Reply #5 above, where the person seemed to misunderstand the original question, to be "how do you relock the bootloader" which isn't what was being asked (I was simply explaining the original question).

poulidis said:
So I want to root my phone only so I can use it with my daydream vr viewer. In order to do that I have to edit the build.prop and I think also some xml file.
My issue is that by unlocking the bootloader you lose widevine l1 so no more netflix HD.
So my question is: Can I unlock, root, edit the files, unroot, relock the bootloader and if I do, will my build.prop remain the same one or is it overwritten when relocking the bootloader? Also does the widevine l1 status come back after relocking?
Thank you in advance
Click to expand...
Click to collapse
You should better just flash Magisk through your TWRP and in Magisk Manager "hide" your root access in "Magisk Hide" menu. After that, you need to download and install "MagiskHide Props Config" module in the "Downloads" section and reboot your device.
I don't have Google Services to confirm it, but you can give it a try.

redpoint73 said:
That was basically what I suspected (see Reply #2 above) but thanks for confirming/explaining it.
My reply that you quoted was in response to Reply #5 above, where the person seemed to misunderstand the original question, to be "how do you relock the bootloader" which isn't what was being asked (I was simply explaining the original question).
Click to expand...
Click to collapse
Your fine I didn't mean to quote you lol

How To Guide [ROOT][GAPPS] Root and install GApps on stock Edge S/Chinese version

So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.

unlock the BL and get root is will make some apps fingerprint and face ID fail?

kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.

HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.

kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.

HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.

kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.

kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.

HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.

HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?

Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.

kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.

I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.

kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related

Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?

kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.

RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/

HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .

kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...

kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.

Question Re-lock bootloader after root?

Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
I like to think I'm quite tech savvy but the guides for the P7Pro have gone over my head :/

Connorsdad said:
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Click to expand...
Click to collapse
Not unless you want to brick your device. You need to be completely stock before relocking your bootloader (unless using avbroot, but you should have a deep understanding about how it works beforehand).
Connorsdad said:
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
Click to expand...
Click to collapse
Pixel Flasher will work fine for updating.

Lughnasadh said:
Not unless you want to brick your device.
Click to expand...
Click to collapse
Huh, learn something new every day I guess...

Lughnasadh said:
Not unless you want to brick your device. You need to be completely stock before relocking your bootloader (unless using avbroot, but you should have a deep understanding about how it works beforehand).
Pixel Flasher will work fine for updating.
Click to expand...
Click to collapse
Awesome, thanks a lot for your reply, much appreciated.

never ever* lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
* exception

alecxs said:
never ever lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
Click to expand...
Click to collapse
And you can't flash a factory image to fix a phone on your own when it's soft bricked. It might have to go to a shop for repairs.

Connorsdad said:
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
I like to think I'm quite tech savvy but the guides for the P7Pro have gone over my head :/
Click to expand...
Click to collapse
AFAIK, relocking the bootloader requires wiping the device -- much like unlocking does -- and if you're unwilling to set everything (including anything on your /sdcard internal storage, not to mention all apps and their settings & system settings) back up from scratch (as any good complete backups require root access), this might not be what you wish to do.
And, if you had managed to successfully relock the bootloader, you could simply run the in-system update (OTA) that would update without wiping -- or even manually applying OTA from the recovery.
But there are hardly any benefits in re-locking the bootloader (after unlocking it) -- even if one was to a paranoid degree of security; which is the only major reason to (I can point you to the discussions that had taken place on it here, if you wish). If you don't want to run into any issues, you could simply run the stock ROM without root and be hardly impacted by it; with the added benefit of having the option to advanced recovery options and/or rooting options open to you in the future if need be...
alecxs said:
never ever lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
Click to expand...
Click to collapse
*it just occurs to me you meant to never lock bootloader because it limits options; not the risk of hard-bricking the device -- in which I wrote the following with that assumption. I'll leave the following comment as it is still sound advice, but I apologize in advanced that it doesn't quite relate to what you meant...
I mean, I feel doing Google's official Android Flash Tool is a safe enough method; it wouldn't do well if Google's own tool bricked their devices using their tool...at the very least the tool ensures that the stock factory firmware flashed matches the bootloader version and automates the fastboot commands so when re-locking the bootloader, it has the least potential to brick the device...

Exactly. there is no official flash tool from google, that's why I personally won't recommend to keep bootloader locked. If it's bricked with no working recovery mode, not even repair shop can fix it. all you can do is RMA to google get new device. no edl mode or anything else will help, fastboot is the official flashing method.
If you're referring to the "Android Flash Tool" that's no flash tool at all. I haven't tested it, but to me it looks like a WebUSB browser plugin. Reading the requirements it works with adb commands, usb-debugging and fully booted android is required. Therefore cannot unbrick devices.

Doesn't unlocking the bootloader break saftynet so then you have to root to use gpay?

iRhyiku said:
Doesn't unlocking the bootloader break saftynet so then you have to root to use gpay?
Click to expand...
Click to collapse
I'll just chime in here because I have recently unlocked my bootloader but I haven't been able to root it yet and I haven't had any issues with safety net.

Trippyy Doee said:
I'll just chime in here because I have recently unlocked my bootloader but I haven't been able to root it yet and I haven't had any issues with safety net.
Click to expand...
Click to collapse
Interesting, I thought unlocking would break it. I'll have to unlock then for the extra safty!

iRhyiku said:
Interesting, I thought unlocking would break it. I'll have to unlock then for the extra safty!
Click to expand...
Click to collapse
That's of course another aspect. Good point. If you rely on SafetyNet or it's successor Play integrity, do not unlock bootloader. AFAIR the latter one can't be cheated.

simplepinoi177 said:
But there are hardly any benefits in re-locking the bootloader (after unlocking it)
Click to expand...
Click to collapse
There are some benefits like some banking apps, streaming apps and games beginning to work. So it really depends on what is important for the user. I don't like flashing random mods to make apps work on rooted/ bootloader unlocked devices, primarily banking apps.