Develop Bugs

[Q] Sprint Note 2 rootted stock now an update nag

Device Info: Sprint Galaxy Note 2 Running rooted stock Android 4.4.2. (chainfire auto root using odin)
Wifi only unit. I have no sprint contract purchased it used (I'm new to customizing android- I have flashed an old palm pda, but only via guidance)
Situation: Rooted the unit and have customized it as mine
1. No custom backup and would like to do that
2. Do not like all the bloatware apps
3. Now a system update has been downloaded asking to install (I've not okayed it)
So please help me with each of these
1. Please point me in the direction of best way to take a backup of existing rom ( I do have philz downloaded, but I'm not sure about how to ?
2. Would that deal with the persistent update request? Would it be good to update?
3. and then the bloatware removal, should I use an app that removes system apps? ( I have titanium, but I'm not good at knowing which apps to touch and not to touch) Thanks in advance and no I'm not in a hurry as yet.

Hi,
I will have your thread moved to your device section so the experts who own your device can help you.
Good luck!

Point to links please
If someone doesn't want to tackle this whole question I'd just appreciate links on how to step by step. I'd appreciate any help at all, I'm just a bit fearful of bricking the device, but if the instructions are clear I can definitely do this.
The first is issue is backup that is my priority at the moment. The second is whether to install the update or not and how to get rid of the nag. thanks

Not sure about backing up the ROM itself... but what I do is just back up the apps with Titanium and then re-load the apps (or just data) when I have to re-install my ROM like I did a couple of weeks ago. Prior to the Note II, I had an HTC Hero (stop laughing) and would do nandroids for that device. Don't know that you need that for Samsung devices, but somebody may be better to explain than I am.
ETA: here's an article on creating a nandroid, FWIW
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
If you are rooted, I don't know that the persistent update will actually apply/install. I'm on Classic Stock 4.4.2 and I also had the same nag. Here's a link on how to disable the update nag. This is what I did, as my phone would not apply the update so I just disabled the persistent reminder using the steps below.
http://forum.xda-developers.com/showthread.php?t=2442207
With respect to removing system apps, not sure I can offer much direction other than to suggest removing obvious apps (maybe like the Sprint Zone app) and then just doing a search on each app that looks like you can/want to delete or uninstall. Probably a bit time consuming, however, I am not aware of a "bloatware list" or anything which outlines safe-to-remove apps.

Much appreciated Lenny
When I did the root, I didn't really want a custom rom, just stock with root. Now that I've used titanium backup and have removed the install update nag- I'm set for a while!

lost in cyberspace said:
Much appreciated Lenny
When I did the root, I didn't really want a custom rom, just stock with root. Now that I've used titanium backup and have removed the install update nag- I'm set for a while!
Click to expand...
Click to collapse
You might also look at adding a free version of BusyBox (I use stericson's, and jrummy also has one out there).
Also might want to look at an install of AdAway, which you'll need to install manually (not available from the Play Store). You don't have to install the whole F-Droid package, you can download only the AdAway apk if you want.
https://f-droid.org/repository/browse/?fdid=org.adaway
One last piece of info, you may want to turn off automatic updating for apps, as the SuperSU app can have problems after an update and you might have to re-root your phone. Here's what I ran into.
http://forum.xda-developers.com/showpost.php?p=58955076&postcount=10

lennykravitz2004 said:
You might also look at adding a free version of BusyBox (I use stericson's, and jrummy also has one out there).
Also might want to look at an install of AdAway, which you'll need to install manually (not available from the Play Store). You don't have to install the whole F-Droid package, you can download only the AdAway apk if you want.
https://f-droid.org/repository/browse/?fdid=org.adaway
One last piece of info, you may want to turn off automatic updating for apps, as the SuperSU app can have problems after an update and you might have to re-root your phone. Here's what I ran into.
http://forum.xda-developers.com/showpost.php?p=58955076&postcount=10
Click to expand...
Click to collapse
Thank you! I've side loaded adb adblock is adaway better? I use App Ops to turn off specific things within each app such as location finding, I like MW apps manager to add more apps to the multiwindow feature., and I've turned off most apps auto update, but some apps I've left auto update. I've just turned off auto update on super user -- even though, I've not yet experienced any major issues as yet.

lost in cyberspace said:
Thank you! I've side loaded adb adblock is adaway better? I use App Ops to turn off specific things within each app such as location finding, I like MW apps manager to add more apps to the multiwindow feature., and I've turned off most apps auto update, but some apps I've left auto update. I've just turned off auto update on super user -- even though, I've not yet experienced any major issues as yet.
Click to expand...
Click to collapse
Don't know if adb adblock is better - I've never used it. Didn't see you mention a couple of these things when you said you were "all set for awhile", so I was just trying to offer a few other things to consider and look into. Sounds like you're already on the ball though!
Personally, I'm happy with stock. Big reason for me to root was getting rid of ads. I've tried some of the other ROMs but I've always come back to the stock look and feel. I've had the device since about 1 week after it came out in Fall 2012. Of course, I am also on my third one since I totaled two other ones. I absolutely love it, and am in no hurry to upgrade (if possible). Hope you enjoy it as I have... lots of good stuff from devs here!

[Q] reboot manager

Hi all, I am certain others are having this problem, but I couldn't find any threads about it.
Does anyone know how to get a reboot widget to work? I used to keep Quick Reboot on my home screen just to have easy access to recovery and other stuff. Since the Lollipop update, none of the reboot managers on the play store work.
Anyone know of a work around or alternative?

Is your phone rooted, from what i understand the app you're referring to or any like it requires it. If you are rooted most any custom rom will have the boot menu your looking for just not as a widget.

Holo Reboot works for me on OB7.
https://play.google.com/store/apps/details?id=com.scartech.holoreboot
It has a dark and bright widget.
Sent from my SM-N910P using Tapatalk

samep said:
Holo Reboot works for me on OB7.
https://play.google.com/store/apps/details?id=com.scartech.holoreboot
It has a dark and bright widget.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Dang, it doesn't work for me. It asks for root privileges and I grant them, then says your phone will reboot....but never does. It behaves the same way all reboot managers do, just bombs out.
It has been like this on every ROM I've used (Noterized, Alliance), including stock. WTF?? Are you certain it is rebooting your Note when you ask it to?
Even apps Like Synapse that came with my ROM cannot reboot. The Xposed module reboot function fails too. Like I said, it isn't specific to this ROM, it has always been like this for me on the NOTE 4.

pinetreehater said:
Dang, it doesn't work for me. It asks for root privileges and I grant them, then says your phone will reboot....but never does. It behaves the same way all reboot managers do, just bombs out.
It has been like this on every ROM I've used (Noterized, Alliance), including stock. WTF?? Are you certain it is rebooting your Note when you ask it to?
Even apps Like Synapse that came with my ROM cannot reboot. The Xposed module reboot function fails too. Like I said, it isn't specific to this ROM, it has always been like this for me on the NOTE 4.
Click to expand...
Click to collapse
I was using it with rooted OB7 stock using beta 2.49 SuperSU apk. Just flashed a custom ROM that uses 2.46 and does just as you say.
Try the beta 2.49. It was made for the lollipop kernel enforcing vs permissive mode issue.
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1 Shouldn't be beta, IMO.
Edit: that didn't fix it on custom ROM for me either. I'll look deeper into this.
Sent from my SM-N910P using Tapatalk

samep said:
I was using it with rooted OB7 stock using beta 2.49 SuperSU apk. Just flashed a custom ROM that uses 2.46 and does just as you say.
Try the beta 2.49. It was made for the lollipop kernel enforcing vs permissive mode issue.
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1 Shouldn't be beta, IMO.
Edit: that didn't fix it on custom ROM for me either. I'll look deeper into this.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have found that applications that issue a reboot command(like xposed), also fail to result in a reboot. However, interestingly enough, I just noticed that the reboot command from within Titanium works (it is inside the menu list).
Sometimes I notice when I try to reboot with a app, a toast message comes on a says "Reboot:Null" or "that function doesn't exist (or something like that)" as if that command functionality doesn't exist on the Note 4. I know it isn't a Lollipop issue, because my wife's G2 has Lollipop and Quickboot works flawlessly.
When Titanium successfully rebooted, it flashed a toast message (the first time). I didn't have a chance to read it all, it was long. But it seems to be using another method to initiate a reboot. Dunno, I am stumped.

pinetreehater said:
I have found that applications that issue a reboot command(like xposed), also fail to result in a reboot. However, interestingly enough, I just noticed that the reboot command from within Titanium works (it is inside the menu list).
Sometimes I notice when I try to reboot with a app, a toast message comes on a says "Reboot:Null" or "that function doesn't exist (or something like that)" as if that command functionality doesn't exist on the Note 4. I know it isn't a Lollipop issue, because my wife's G2 has Lollipop and Quickboot works flawlessly.
When Titanium successfully rebooted, it flashed a toast message (the first time). I didn't have a chance to read it all, it was long. But it seems to be using another method to initiate a reboot. Dunno, I am stumped.
Click to expand...
Click to collapse
I got some ideas just slow going setting up a fresh ROM. For stock, I had a highly customized setup, look and feel but everyone's preferences are not alike so I can't complain. Even with Titanium and TWRP tar to pull from, I had system customized too. I've got apps and lib folder to edit; some to copy over and some to delete. Keyboards have got to go; back to custom Swype with top number row and directional left right arrows. There's always the nandroid to restore but I'll try to set this up for a backup.
I'll chime in if I figure it out. Maybe just a matter of time. Not out of ideas yet. If someone has a solution, chime in.
Sent from my SM-N910P using Tapatalk

Non responsive touches on rooted 13B

I just updated to 13B, rooted it, restored user apps using Titanium Backup, installed xposed, and am having a weird issue with non responsive touches when trying to install an app or grant root to apps. When I try to click on install, the screen doesn't allow me to choose it. I am however able to chose cancel. Also when an app is requesting root, the grant permission screen is completely unresponsive. I can't choose grant, deny, anything. I was able to grant root right after rooting the phone. Any ideas?
Sent from my VS986 using Tapatalk

Solved! I guess lux may change the way certain screens interact. So I just enabled alternate overlay in lux and that fixed it!
Sent from my VS986 using Tapatalk

Nova Launcher Lost Root Options After Jan Update

This is driving me nuts and kinda want to know if I'm the only one. Originally rooted w/Magisk 15.2, uninstalled Magisk/modules, manually flashed Jan. system image (removed -w option), rebooted, re-rooted via TWRP booting, all is fine and well with the exception of Nova Launcher. It literally lost the root options in Nova Settings/Look and Feel. The option to use root to expand notifications and to remove the clock are just gone. I've tried uninstalling Nova, clearing data, rebooting in between both, I just don't know. What's weirder is that the option in the main Nova settings page under advanced for the screen lock method still has the root option, and enabling it triggers the SU request, but only for that action. The options to expand notifications and hide the clock using root are simply GONE. Anyone on the current firmware showing this? I don't think it's a Magisk issue...same Magisk and Nova's root options worked fine (and appeared) on the Dec build. Asside from a full wipe, which I honestly don't think will do anything, I'm at a loss here and stuck with a slow notification shade gesture.

annoyingduck said:
This is driving me nuts and kinda want to know if I'm the only one. Originally rooted w/Magisk 15.2, uninstalled Magisk/modules, manually flashed Jan. system image (removed -w option), rebooted, re-rooted via TWRP booting, all is fine and well with the exception of Nova Launcher. It literally lost the root options in Nova Settings/Look and Feel. The option to use root to expand notifications and to remove the clock are just gone. I've tried uninstalling Nova, clearing data, rebooting in between both, I just don't know. What's weirder is that the option in the main Nova settings page under advanced for the screen lock method still has the root option, and enabling it triggers the SU request, but only for that action. The options to expand notifications and hide the clock using root are simply GONE. Anyone on the current firmware showing this? I don't think it's a Magisk issue...same Magisk and Nova's root options worked fine (and appeared) on the Dec build. Asside from a full wipe, which I honestly don't think will do anything, I'm at a loss here and stuck with a slow notification shade gesture.
Click to expand...
Click to collapse
Are you sure you had it on december ?
I already missed it since december, and i thought nova remove it

Is it possible that you're not actually rooted?
Several original Pixel XL users (including me) are unable to root the January update by flashing SuperSU in TWRP. I've never used Magisk though.

Really guys
Of course I'm sure it was working prior and of course I'm sure I'm rooted. I can't emphasize this detail enough: The options in Nova settings under Look & Feel that offers to expand the notification shade using root and the option to remove the clock using root are GONE after updating from the December build - they WERE there before and worked on the Dec build. I've tried everything except for a full wipe, which I'm not doing for this issue. Is anyone showing the same result?

annoyingduck said:
Really guys
Of course I'm sure it was working prior and of course I'm sure I'm rooted. I can't emphasize this detail enough: The options in Nova settings under Look & Feel that offers to expand the notification shade using root and the option to remove the clock using root are GONE after updating from the December build - they WERE there before and worked on the Dec build. I've tried everything except for a full wipe, which I'm not doing for this issue. Is anyone showing the same result?
Click to expand...
Click to collapse
I have the same result as you. But, in my case BEFORE, removing the clock on the home screen, caused problems with Nova Launcher on the Dec build. So, I never used it.

I'm still on the Dec 5 patch and have none of those options in novas look and feel section. I'm using Nova prime 5.5.2
Sent from my Pixel 2 XL using XDA Labs

dinkoh said:
I have the same result as you. But, in my case BEFORE, removing the clock on the home screen, caused problems with Nova Launcher on the Dec build. So, I never used it.
Click to expand...
Click to collapse
Ok, so the Jan build caused those options to disappear for you (just like me) correct? I don't use the clock option, I use the expand notification option. I never realized how important that root option was until now. I'm always rooted and have always used that option.
S8ntsHaz3 said:
I'm still on the Dec 5 patch and have none of those options in novas look and feel section. I'm using Nova prime 5.5.2
Click to expand...
Click to collapse
I'm assuming your rooted correct? Prior to this current issue, those options would not appear in Nova's settings if Nova doesn't detect root. This seems to be the issue, Nova is not seeing root. I'm wondering now if disabling magisk hide will allow Nova to see the su binary.
Sent from my Pixel 2 XL using XDA Labs

I am rooted with magisk. I'm on a Google store xl2 still on the Dec 5 patch stock. I've used Nova on every phone I've had and know what your referring too but I don't recall it ever asking for root since I got my xl2 the last week of October when it was downloaded and used everyday since. Maybe I just never noticed but I just checked my superuser in magisk and Nova is not there nor are the options in Nova.
Sent from my Pixel 2 XL using XDA Labs

Have you tried turning it off and on again?

annoyingduck said:
This is driving me nuts and kinda want to know if I'm the only one....
Click to expand...
Click to collapse
Put down the pipe, Chris... close your eyes and breathe slowly

The same thing happened to me. When I checked the version I notices that it was Nova 5.2 and not 5.4 Beta. I uninstalled Nova and installed the 5.4 Beta and my Root options are back!
annoyingduck said:
This is driving me nuts and kinda want to know if I'm the only one. Originally rooted w/Magisk 15.2, uninstalled Magisk/modules, manually flashed Jan. system image (removed -w option), rebooted, re-rooted via TWRP booting, all is fine and well with the exception of Nova Launcher. It literally lost the root options in Nova Settings/Look and Feel. The option to use root to expand notifications and to remove the clock are just gone. I've tried uninstalling Nova, clearing data, rebooting in between both, I just don't know. What's weirder is that the option in the main Nova settings page under advanced for the screen lock method still has the root option, and enabling it triggers the SU request, but only for that action. The options to expand notifications and hide the clock using root are simply GONE. Anyone on the current firmware showing this? I don't think it's a Magisk issue...same Magisk and Nova's root options worked fine (and appeared) on the Dec build. Asside from a full wipe, which I honestly don't think will do anything, I'm at a loss here and stuck with a slow notification shade gesture.
Click to expand...
Click to collapse

DIXZ06 said:
The same thing happened to me. When I checked the version I notices that it was Nova 5.2 and not 5.4 Beta. I uninstalled Nova and installed the 5.4 Beta and my Root options are back!
Click to expand...
Click to collapse
Wut? Currently Prime version is 5.5.2 ... 5.4 was back in September, bro!

Ever figure this out? I'm on December build of Android and use root on Nova to lock the screen while still preserving the ability to fingerprint unlock. Granted superuser rights to Nova and Magisk shows that Nova has superuser rights. But like you, no root options exist on Nova other than for screen lock.
I'm on Nova 5.5.2, so maybe it was removed previously?

For what it's worth there is no listed change that I can find on the most recent Nova launcher update. Odds are they removed the options.

I've contacted the dev(s) of Nova and they told me this feature is broken on Google's end, and have removed the option until they can find a fix. I'm using an app called "Clock Block" from the Play Store as a temporary workaround. You can choose which apps will cause the clock to hide and I've chosen Nova. It works well enough as a temporary workaround, but it's not perfect. For example, bringing down the notification shade or even tapping on a folder to expand it will reveal the clock again. It's somewhat hit or miss but it's doing the job until Nova brings the option back; hopefully the dev(s) can find a fix soon!

Won't help with the clock but I just started using "custom navigation bar" and you can add an additional button to the nav bar specifically to pull down the tiles\notifications. Just like novo being able to do it with the home button but always available.
_tsp

Worth Rooting?

Hi all,
Joining Team Pixel tomorrow after my debacle with the Huawei Mate 20 Pro and the green screen fiasco.
Just wondering if its still worth rooting the Pixel? If i do it i wanna do it straight away to save wiping my data again when unlocking the BL. My main reasons would be for Adaway, Removing the Nav Bar, Swift theme installer and Viper.
Most of these can be done via ADB now so is it still worth rooting?

Rooting this phone is pretty easy and it doesn't impact the updating process much if you know what you're doing, so I vote that it is definitely worth rooting.
I don't use a lot of root apps, but the two main ones are worth it to me. I use AdAway for ads (VPN ad blockers are slower and have several cons) and an app called Sa2ration to compensate for the screen's weak color.
I have everything working the way I want without any compromises. Very happy with my setup.

It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.

I've always had an Android phone that has been able to be rooted. Adaway, V4A, Substratum, Sa2ration, Titanium Backup and removing the stock navigation buttons are the biggest things for me currently with the Pixel 3 XL.

I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
So, in my opinion, unlocking the bootloader is a no brainer on these phones, right from the get-go.
With that said, rooting is much more user preference. I found no reason to root my OnePlus 6. However, with the 3 XL my sole reason for rooting is to edit the build.prop to properly hide the nav bar at the system level, allowing me to use gesture controls without issue. You can use ADB commands to achieve this as well. But my experience in trying to hide the nav bar with ADB commands on this phone has caused some wonky things to happen, such as status bar notifications not going away and volume controls getting cut off when watching something in landscape mode. Rooting the phone and editing the build.prop was the only solution that worked for me to hide the nav bar without running into unforeseen issues.
If you are one to do other things like use Magisk modules and such, then rooting will be a no brainer for you. Also, as someone else mentioned, rooting this phone is the most straight forward/simple experience I've had rooting a phone in years.

Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one

Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
Try this: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76 do #4 then #8 if you want root. Also, Prerequisites has a link to download SDK Platform tools r28.0.1, if it needs updating.

gettinwicked said:
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
Click to expand...
Click to collapse
I'm perfectly happy with the stock experience on this phone. I have no need for anything that requires root. I've rooted a lot of phones in the past, but there's something about this one that I just feel no need to do so. To me that says a lot for how far Google has come.

I'm getting my pixel 3 xl in a few hours today and I've been up all night watching pixel 3 xl videos. I was just about to post a question like this, but thanks to you I don't have to! The wonders of searching.
Anyways, I agree for adway and maybe even mods.
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
I also want to do it out the box.
Also don't know about the new gesture stuff, so if I don't like it, I'd probably want to mod it.

Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
That is exactly what I did with both a Pixel 3 and a Pixel 3 XL. Just don't do a permanent install of TWRP on the XL unless you want to lose your touch screen in TWRP with no way out of TWRP when it boots back in there. I ended up having to hold the power button down until I forced the device off. Booted back into bootloader and ran the temp TWRP (which strangely works fine for touch) and then ran Magisk again to get back to the OS. Strange, the regukar Pixel 3 took permanent TWRP after Magisk, rebooted to TWRP was still able to use touch commands and ran Magisk again to get back to the proper boot image. I can even go to TWRP normally, and touch is functioning normally. I'll have to write the stock boot image when I get home today so I can get back to stock recovery until TWRP for XL is fixed.

GunToYoMouth123 said:
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
Click to expand...
Click to collapse
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.

I've been learning to live with stock ROMS, BUT, I still need my root. Adaway, TiBu, Substratum, LMT Launcher. I can't give 'em up.

Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
Ohh okay, thanks for that input !
My pixel 3 XL just got here !
Going to see what's up !

Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in

J32A said:
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
Click to expand...
Click to collapse
Not sure, I haven't encountered this.
I find that when an app has detected root, sometimes they retain this information even through reboots. In those situations, clearing all data from the app often fixes it.
Something else to be aware of is that if you have a widget for an app that detects root, it's not uncommon for the widget to load before Magisk finishes loading and hiding after a reboot. On my Pixel 2 I had one app where after each reboot it would load first (due to a widget being present) and would detect root and block itself. I had to remove the widget and just just use a normal shortcut to the app instead, as I would never manually open it before Magisk finished loading up fully.

I just got pixel 2 xl this thing is a beast came with 5g and unlimted data when I got tablets for kids literally no download it's all instant. every phone I have had b4 is rooted most still work. My question will I improve anything by rooting with this speed? I don't think a VPN blckr would slow it down. How hard is it to reverse root if I need warranty? Is this speed the 5g or just Google built a great product?

sn0warmy said:
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
<snip>
Click to expand...
Click to collapse
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.

bobby janow said:
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
Click to expand...
Click to collapse
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Sent from my Pixel 3 XL

Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
No I don't think so. If you bl unlock it will be detected. There are kernels that will fix that but stock unlocked is a trigger.

Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
Yes. As @bobby janow said, some apps treat bootloader unlock as having root. DirecTV Now is a prime example. Also, Netflix won't even appear in the app store and would have to be sideloaded. Although, all of those can be worked around it is sometimes a pain.