Develop Bugs

New update?

Is anyone else getting prompted for a system update? I'm rooted so I don't want to install. Update is 154.6 MB.
UPDATE: DO NOT install the update if you don't have stock recovery. You will end up in a boot loop.
Sent from my LG-D851 using XDA Free mobile app

Lol I just created a thread myself! I am rooted and custom rom so I am totally waiting.

i just got it too, it said android update but I'm not entirely sure what it's for

InsaneJester17 said:
Is anyone else getting prompted for a system update? I'm rooted so I don't want to install. Update is 154.6 MB.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I also did, I am on sky rom and it probably won't work, but I don't want to try to install it.

Well its quite a small update at 154 mb

Installed update
Hey guys I just installed the update and it broke my root :cyclops:

Were you able to root again?

Apparently it's D85110m update. So it's updating from D85110c to m. The person that I saw that updated hadn't rooted so no clue on the rooting thing.

Count me in the group with system update notification. I got rid of it by installing xposed module GravityBox, going under status bar settings - ongoing notification blocker - Google Play services (picture looks like that of update) - reboot.
I don't know what other notifications this may block, but for now, it gets rid of that. Also of note, I would NOT take the OTA. Usually it breaks root and/or bootloops you.

HELP
So in my half awake brilliance, I installed the update. My phone is now boot cycling to the TWRP recovery. Any ideas?

zcgofaster said:
Were you able to root again?
Click to expand...
Click to collapse
I haven't tried to re-root yet. I was rooted with stump root earlier. Stump root doesn't work again because it thinks that my phone is already rooted. I'm going to do some light battery tests before trying to root again, this time with purple drake.

Maybe i might restore the slimkat alpha and hide there until this gets sorted out

I decided not to update to fear my bootloader/root so I tried to extract this with file manager and kept crashing. I can only post the name of the file but above users are correct contains 10m from 10c hopefully devs can find out exactly what's in the update. b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip

thiefinthenight said:
So in my half awake brilliance, I installed the update. My phone is now boot cycling to the TWRP recovery. Any ideas?
Click to expand...
Click to collapse
I would try and follow this guide:
http://forum.xda-developers.com/showthread.php?t=2818667

Wonder if i could do a restore and keep wifi off so it won't download

hawkstwelve said:
I would try and follow this guide:
http://forum.xda-developers.com/showthread.php?t=2818667
Click to expand...
Click to collapse
Will this reset the phone? Will I lose all data?

thiefinthenight said:
Will this reset the phone? Will I lose all data?
Click to expand...
Click to collapse
I believe so yes. But if you are truly bootlooping, I don't believe you have many (if any) other choices than wiping clean and starting fresh.

I'm all stock so I upgraded.
It is in fact D85110m
I've only had it up and running for a few minutes and I already noticed two things.
- There is a slider feature added to the lock screen to instantly open the camera.
- I didn't think the phone was sluggish or laggy out of the box but I immediately could tell it runs smoother now with transitions between screens/apps. e.g. There used to be a bit of lag when opening the Recent Apps. Not anymore.
We'll see how it goes.

The IR blaster works better for me now. I guess the update made it more powerful somehow.

if you have twrp installed or have modified /system you should not take this OTA. if on twrp things will get weird(as evidenced above..) and if removing/modding any default files in /system the zip will most likely fail.. as it checks for all original files first before the OTA update gets patched in.
as for the twrp issue.. I can only assume that it's due to the update/phone expecting stock recovery... and not getting it. there are flags set in the phone that tell the phone what mode to boot into... since you dont have stock recovery the phone is confused. check out this thread - http://forum.xda-developers.com/showthread.php?t=2451696
the fota and misc partitions are tied to this... try to zero out fota first. if that alone doesnt let you out of twrp... you may need to wipe misc. be sure to backup any partition to computer(dont just save on phone sdcard.. never know when it could get wiped..) before erasing anything.
as for this update(10m)... anyone taking it should be careful that the bootloader/downgrades have not been locked/blocked. I'll be waiting for others to take that risk first before even considering taking the ota.
*update* can confirm update is safe.. bootloader is not locked.. still rootable.
as for root... I doubt purple drake is blocked.. but is possible. I'm very sure Stump is still available as an option(tho app may need update).
if you got the update and dont want to take it.. and want the notification gone you should be able to use a file explorer to delete the update zip from the the /cache directory... as well as rename the LGFOTA.apk file in /system to LGFOTA.apk.bak.
I can also confirm that disabling OTA updates in the hidden menu works. the moment I set it back to "on" (i set mine to off day 1) and rebooted the update came in.
d851 hidden menu > wlan test > ota setting > off > reboot (if you have been notified of an available update do NOT reboot until you have deleted the ota zip first)

[Help]Anyone facing this?

My Facebook and messenger apps crashes when i open them from the recent apps and even instagram crashes, most of the time when i shuffle between 3-4 apps.
Is this the condition with everyone?

Are you on Stock with a locked bootloader? Are you on any customer rom, have you made any changes to the rom you are using, etc... many questions need to be filled first to help. The more information you supple the easier it can be to offer a solution.

Jimi Mack said:
Are you on Stock with a locked bootloader? Are you on any customer rom, have you made any changes to the rom you are using, etc... many questions need to be filled first to help. The more information you supple the easier it can be to offer a solution.
Click to expand...
Click to collapse
No bootloader unlocked.
No Root.
No this type of changes in the device.
Android 7.0 with April security patch.

Yash24 said:
No bootloader unlocked.
No Root.
No this type of changes in the device.
Android 7.0 with April security patch.
Click to expand...
Click to collapse
Thanks, by chance have you tried uninstalling both, just reinstalling one and see if the issue repeats, then after you feel everything is fine add the 2nd app and see if the issue then shows up gain. This would then steer you into the thought the problem is one of the apps. At worst, do a complete reset and start fresh completely from scratch.

Jimi Mack said:
Thanks, by chance have you tried uninstalling both, just reinstalling one and see if the issue repeats, then after you feel everything is fine add the 2nd app and see if the issue then shows up gain. This would then steer you into the thought the problem is one of the apps. At worst, do a complete reset and start fresh completely from scratch.
Click to expand...
Click to collapse
Will try.
Thanks!

Nexus 5x is slow now, root without data loss?

hi guys,
my nexus 5x is getting a bit old and is very very slow a lot of the time. i see 2 options:
1: factory reset and hope it speeds up
2: root, and install a light weight ROM ( crDroid looks good) and also use root features like disable auto start on apps.
i feel like the 2nd option would be best, i think a major issues with my phone is that i have a lot of apps that i use maybe once a week, but its impossible to disable auto-start apps without root based on my knowledge (Ive tried several apps, it doesn't work). and i dont want to install/reinstall a dozen apps each month.
i have google backup enabled, and i also backed up my SMS data with a 3rd party app (apparently google doesn't back up SMS). if i were to unlock bootloader and flash a new ROM, would i loose any data thats currently on my phone (ie, data/apps that wont come back after restoring backup)?
Thanks

haxxo said:
hi guys,
my nexus 5x is getting a bit old and is very very slow a lot of the time. i see 2 options:
1: factory reset and hope it speeds up
2: root, and install a light weight ROM ( crDroid looks good) and also use root features like disable auto start on apps.
i feel like the 2nd option would be best, i think a major issues with my phone is that i have a lot of apps that i use maybe once a week, but its impossible to disable auto-start apps without root based on my knowledge (Ive tried several apps, it doesn't work). and i dont want to install/reinstall a dozen apps each month.
i have google backup enabled, and i also backed up my SMS data with a 3rd party app (apparently google doesn't back up SMS). if i were to unlock bootloader and flash a new ROM, would i loose any data thats currently on my phone (ie, data/apps that wont come back after restoring backup)?
Thanks
Click to expand...
Click to collapse
If your bootloader is not unlocked then absolutely. Unlocking it will wipe the device.
Sent from my [device_name] using XDA-Developers Legacy app

Yes - unlocking bootloader will wipe everything, so make sure photos/videos/music/sms/mms is backed up in cloud or on PC.
Since you're gonna lose everything anyway, why not try factory reset (but backup the things I mention above first Then see how your phone acts when adding back the 3rd party apps.
Have you taken all OTA's? 8.1 is out for Nexus 5X.
I'm on it now and not rooted. Have rooted up to now, but so far I am impressed with stock non-rooted performance.

haxxo said:
hi guys,
my nexus 5x is getting a bit old and is very very slow a lot of the time. i see 2 options:
1: factory reset and hope it speeds up
2: root, and install a light weight ROM ( crDroid looks good) and also use root features like disable auto start on apps.
i feel like the 2nd option would be best, i think a major issues with my phone is that i have a lot of apps that i use maybe once a week, but its impossible to disable auto-start apps without root based on my knowledge (Ive tried several apps, it doesn't work). and i dont want to install/reinstall a dozen apps each month.
i have google backup enabled, and i also backed up my SMS data with a 3rd party app (apparently google doesn't back up SMS). if i were to unlock bootloader and flash a new ROM, would i loose any data thats currently on my phone (ie, data/apps that wont come back after restoring backup)?
Thanks
Click to expand...
Click to collapse
If you can live without root I think you should try first the wiping/factory reset. Performance is pretty good with 8.1 stock for me.One restart everyday is recommended also.

the 8.1 OTA update worked great for 24 hours, and after that it became incredibly slow again. for some crazy ass reason, every single app is running all the time, even if i limit background process and even disable apps with background check. when there is a heavy computing load, random apps that are rarely ever used start crashing (not responding error). and since you cant stop apps from running anymore without root, i think a root is required or a new phone as its unusable 75% of the time.
if i use google backup, and backup my sms through a 3rd app, will i be able to restore everything on my phone after root? if not, what will go missing so i can back it up separately.
if google backup includes all apps/app data, contacts, pictures/videos and call history, and i backed up my sms with a 3rd party app. seems like everything should get restored after root.

I was watching catlog *:W and *:E and saw that OOM killer was failing and a bunch of errors, even with the Jan 5 2018 / 8.1.0 r7 update. The phone is ridiculously slow at starting chrome, loading webpages, downloading attachments from email, updating apps from the play store.
I deleted the dalvik-cache and cache and started every app manually and rebooted a bunch of times, but the phone seems to degrade into this pathetically slow mode. It seems as if the flash is 10-100x slower than it should be.

mickrussom said:
[...]It seems as if the flash is 10-100x slower than it should be.
Click to expand...
Click to collapse
This is what I'm too afraid off. Maybe Google has done something to slow the device down like Apple did recently?

How are you guys seeing 8.1 already? I'm on T-Mobile. TIA.

7carisfast said:
How are you guys seeing 8.1 already? I'm on T-Mobile. TIA.
Click to expand...
Click to collapse
Updates arrive at different intervals for Nexus devices. If you do not want to wait, adb sideload the full OTA image:
https://developers.google.com/android/ota
Sent from my Nexus 5X using Tapatalk

Questions about running stock rooted ROM / XPosed (Gravity Box) / Substratum

Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:

Ghisy said:
Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Click to expand...
Click to collapse
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!

rickysidhu_ said:
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Click to expand...
Click to collapse
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.

Ghisy said:
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Click to expand...
Click to collapse
Unlocker is to support dev as well as it unlocks the ultimate notification controls which has a trial period
Ota are fine but we all prefer to flash the whole image because it is recommended and hardly comes up with errors
If you install magisk module for xposed then you would only need to re install magisk zip and your previous modules would be still installed
For substratum you need to disable overlays before updating and just re enable them after updating to latest update
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs

rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
Click to expand...
Click to collapse
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!

Ghisy said:
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Click to expand...
Click to collapse
Which version of Xposed did you flash? And which version of the Xposed installer did you install?

rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
Click to expand...
Click to collapse
Ditto.

rickysidhu_ said:
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
Click to expand...
Click to collapse
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.

Ghisy said:
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Click to expand...
Click to collapse
Glad you got it working.
I downloaded the Xposed APK in the Magisk thread and installed Xposed within the app; after reboot everything seems to work normally for me.
The way you did it is also fine though:good:

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.