Related
Long story short, I rooted my phone a long time ago (with the intention of installing a root-access wifi app). Foxfi started to work, so I never went any further than unlocking the bootloader, installing root, and installing superuser.
Since then, I got the OTA update to 4.1. I tried to uninstall the superuser app, but I'm not able to uninstall it. At this point, I would like to simply uninstall super user and maybe re-lock the bootloader.
I've looked around online and found some instructions, but they are generally for ICS or gingerbread. So my first question is if that matters. Secondly, all the instructions refer to flashing a stock ROM, and wiping data. I already have the stock ROM, so I don't know if I just skip certain steps in the process, or what.
My questions are probably pretty basic, I just want to make sure I don't brick anything, or totally reset my phone (if it isn't necessary).
Thanks!
dorklord said:
Long story short, I rooted my phone a long time ago (with the intention of installing a root-access wifi app). Foxfi started to work, so I never went any further than unlocking the bootloader, installing root, and installing superuser.
Since then, I got the OTA update to 4.1. I tried to uninstall the superuser app, but I'm not able to uninstall it. At this point, I would like to simply uninstall super user and maybe re-lock the bootloader.
I've looked around online and found some instructions, but they are generally for ICS or gingerbread. So my first question is if that matters. Secondly, all the instructions refer to flashing a stock ROM, and wiping data. I already have the stock ROM, so I don't know if I just skip certain steps in the process, or what.
My questions are probably pretty basic, I just want to make sure I don't brick anything, or totally reset my phone (if it isn't necessary).
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1572307
You are stock rooted so flash factory and this will clear your phone to pure stock. To relock bootloader at the end just fastboot oem lock. Your phone will be like it is out of the box. If you choose to unlock again remember that does wipe your SD. There really is no need to lock bootloader unless shipping for warranty reasons.
jayjay3333 said:
http://forum.xda-developers.com/showthread.php?t=1572307
You are stock rooted so flash factory and this will clear your phone to pure stock. To relock bootloader at the end just fastboot oem lock. Your phone will be like it is out of the box. If you choose to unlock again remember that does wipe your SD. There really is no need to lock bootloader unless shipping for warranty reasons.
Click to expand...
Click to collapse
I'm still a little confused, do I need to download a ROM from that thread? I've never installed a different ROM, so don't I already have a factory ROM?
Also, as a note, I've got a Nexus S 4G from sprint.
Try this. http://forum.xda-developers.com/showthread.php?p=15628028
Sent from my Nexus S 4G using xda app-developers app
dorklord said:
I'm still a little confused, do I need to download a ROM from that thread? I've never installed a different ROM, so don't I already have a factory ROM?
Also, as a note, I've got a Nexus S 4G from sprint.
Click to expand...
Click to collapse
You said you "would like to simply uninstall super user and maybe re-lock the bootloader." You have factory but rooted (superuser)
So flash factory which will remove SU and make it as if "out-of-box"
This may make help you more.
http://forum.xda-developers.com/showthread.php?t=1785672
Go here https://developers.google.com/android/nexus/images
- get the Factory Images "sojus" for Nexus S 4G (d720) -- >Android 4.1.1 (JRO03R)
Follow the instructions to a T and all will be fine. Need Android SDK working for your phone for fastboot http://developer.android.com/sdk/index.html
Google guides to set it up if you don't have it already. You should if your rooted, but it sounds like you don't flash so maybe not.
Old sticky here http://forum.xda-developers.com/showthread.php?t=895545 to help get SDK in part 1. Part 2 to lock fastboot oem lock
Give it a go. Ask for help and I or others will help you out.
Cheers
Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
CoinCoin88 said:
Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
Click to expand...
Click to collapse
Just to make sure you do have SuperUser, SuperSU, and I generally prefer to include BusyBox all into the mix. Also, if you would download Root Checker by Joey Krim in the Play store. Just to confirm and we know you are missing root click the verify should indicate the appropriate SU's are red and not engaged, slide to the right verify BusyBox, chances are it is green, if so you are in good condition. With Busybox in green, exit go into SuperUser and update the binaries, once that is completed go into SuperSU and click the update. Go back to Root Checker and double check, click verify root on SuperUser/SuperSU and should be green = rooted. :good:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
CoinCoin88 said:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
Click to expand...
Click to collapse
If the color is Red all around then yes, there is little you can do. However, there are ways to get out of this and gain root without waiting even if they have Jelly Bean 4.1.1. For instance those on JB that own the XT926 can use the Droid Razr HD Utility 1.10 > go back to ICS 4.0.4 > apply the 1st update > Root > Voodoo OTA, SU Backup > apply the JB 4.1.1 update. I have done this twice and have been quite successful on my XT926 with Verizon.
But, in general going back to the discussion. If after the update the Supers are not showing, as long as Busy Box is Green and in place, Root can be restored by updating the binaries.
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
tech_head said:
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
Click to expand...
Click to collapse
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
CoinCoin88 said:
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
Click to expand...
Click to collapse
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
tech_head said:
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
Click to expand...
Click to collapse
edit the XML ?? I'm new to RSD lite, but from what I've understood so far, edit the xml is only neededn when flashing via RSDLite/fastboot so that you don't end-up with the "unknown fastboot command" or something like that (by removing 2 lines in the fw xml file, indeed).
How is this related to going back from JB to ICS ? I'm not sure that's possible with a locked bootloader (which I'm probably not going to unlock). Also, how is my carrier related to this operation ? (the phone was SFR simlocked, but I bought an unlock code online and I'm no using it on Free Mobile)
Or did I miss something ? (btw, no mention of a JB root for the Razr HD, only for the Razr M, and it is assumed it won't work on HD because for reasons I am yet to find)
So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Rey0 said:
So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Click to expand...
Click to collapse
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
jagreci said:
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
Click to expand...
Click to collapse
Sounds cool then. Thanks
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
crucialcolin said:
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
Click to expand...
Click to collapse
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
beekay201 said:
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
Click to expand...
Click to collapse
I've actually been spoiled by nandroid on the HP TouchPad with CM. Really nice to have a complete backup image. Wish I would have thought about unlocking and rooting before I got a bunch of stuff on my Nexus setup the way I like it. Sort of stuck since you have to unlock the boot loader for a custom recovery. Thus is life though.
I haven't tried it yet but it looks like Adb can do it on a stock device.
ex: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
I'm actually extremely torn on the OTA thing. I find it just so damn convenient with the admission I've gotten lazy of late Otherwise I have a tendency to never update.
Hi,
apologies if this has been asked before. I have received messages to update to marshmallow OTA, but my phone has an unlocked bootloader and is rooted. From what I understand the bootloader is not a problem, but the rooted phone is. I have also seen references to TCRW recovery, but I'm not sure if I have that (I forget now how I rooted the phone...)
So what steps should I take in order to update? Is it easier to just download and flash the MM firmware directly, or should I unroot the phone and then do it OTA? Easy instructions for either approach would be much appreciated!
Thanks.
eelgc said:
Hi,
apologies if this has been asked before. I have received messages to update to marshmallow OTA, but my phone has an unlocked bootloader and is rooted. From what I understand the bootloader is not a problem, but the rooted phone is. I have also seen references to TCRW recovery, but I'm not sure if I have that (I forget now how I rooted the phone...)
So what steps should I take in order to update? Is it easier to just download and flash the MM firmware directly, or should I unroot the phone and then do it OTA? Easy instructions for either approach would be much appreciated!
Thanks.
Click to expand...
Click to collapse
You need stock recovery and an unrooted phone to apply the update. You can flash stock MM firmware and then get the OTA. WAIT FOR SOMETIME.
Hi, thanks for the reply. Is there any way of unrooting without relocking the bootloader? It would make it easier to reroot once I upgrade to MM I imagine, but all the instructions I can find online do both - any links to a reliable set of instructions would also be appreciated!
eelgc said:
Hi, thanks for the reply. Is there any way of unrooting without relocking the bootloader? It would make it easier to reroot once I upgrade to MM I imagine, but all the instructions I can find online do both - any links to a reliable set of instructions would also be appreciated!
Click to expand...
Click to collapse
You do not, actually can not, relock the bootloader. You just need stock recovery, meaning no TWRP, and remove root and any significant changes made to the system with root.
There are no real instructions needed and it kind in some ways depends what you have done with root... if you have done heavy modifications to /system then you might as well just reflash the factory image. If you have done only a handful things, you MIGHT be able to take the OTA if you undo them, such as remove Xposed and it's modules, use the SuperSU app to do a full unroot (it's an option in the menu, just look for it), and you have to find the stock recovery for you device and flash it with fastboot.
There is no step-by-step tutorial because every situation is different, everyone does different things to their phone... If you are unsure you can do it, perhaps just flashing the factory image will do what you need? It will wipe everything, but nothing you can do will lock/relock your bootloader.
Thanks for the explanation, that makes sense. Some of the links I found implied that you could relock the bootloader (with 'fastboot oem lock begin'), but in any case, I think that step can be skipped anyway, and everything else seems straightforward.
I actually haven't done anything with root except install adaway (from what I remember! nothing fancy in any case), and am still on stock firmware, so will just do as you suggest and unroot with supersu and flash the stock firmware..
Cheers!
acejavelin said:
You do not, actually can not, relock the bootloader. You just need stock recovery, meaning no TWRP, and remove root and any significant changes made to the system with root.
There are no real instructions needed and it kind in some ways depends what you have done with root... if you have done heavy modifications to /system then you might as well just reflash the factory image. If you have done only a handful things, you MIGHT be able to take the OTA if you undo them, such as remove Xposed and it's modules, use the SuperSU app to do a full unroot (it's an option in the menu, just look for it), and you have to find the stock recovery for you device and flash it with fastboot.
There is no step-by-step tutorial because every situation is different, everyone does different things to their phone... If you are unsure you can do it, perhaps just flashing the factory image will do what you need? It will wipe everything, but nothing you can do will lock/relock your bootloader.
Click to expand...
Click to collapse
eelgc said:
Thanks for the explanation, that makes sense. Some of the links I found implied that you could relock the bootloader (with 'fastboot oem lock begin'), but in any case, I think that step can be skipped anyway, and everything else seems straightforward.
I actually haven't done anything with root except install adaway (from what I remember! nothing fancy in any case), and am still on stock firmware, so will just do as you suggest and unroot with supersu and flash the stock firmware..
Cheers!
Click to expand...
Click to collapse
Relocking the bootloader was possible with some older Moto G models, but I believe everyone with the 3rd Gen that has tried it has failed. Make sure any tutorials or guides you use are for the Moto G 3rd Generation or 2015 model, although previous models are similar there are definite differences.
I just ordered Moto G Turbo (which is probably the same as the normal Moto G 2015 phone.)
Quick question: I would like to keep it as stock, since it is for my parents' use. If I update it to the latest OTA (6.x), will I lose ability to unlock the BL?
Coming from the Droid's background, unlocking the BL is a complicated affair. But I hear things are simpler with the 'normal' Motos.
Hello,
I've been out of the rooting scene for a while now (last phone had a damn permalocked bootloader!) and wanted to be clear on a few things before rooting this phone.
1. I am aware that doing any sorts of modifications to the system will disable OTA updates and those have to be done manually, the question is when I restore my phone (removing root, going back to stock recovery, etc) will automatic OTA updates be re-enabled? Is the stock recovery image even available, or is this even possible? because...
2. When I am looking to sell the phone in the future, I want to be sure that the phone doesn't show any signs of tampering. I am wondering this because the last phone I rooted was the Motorola z2 force, which was the first phone I've ever seen with that "unlocked bootloader" warning when powering on. And with that phone even after all the images were returned to stock, there was still a "your device has loaded a different os" warning, even if it was the stock image. The CTS system functioned similarly to Samsung's knoxs system, where once it was tripped, there was no going back and I wasn't aware of this...
TL;DR: If I ever wish to sell the phone to completely stock (relocked bootloader, stock recovery img, etc), will the phone be permanently tainted with a message like with the image attached? thanks!
PhantomSoul said:
Hello,
I've been out of the rooting scene for a while now (last phone had a damn permalocked bootloader!) and wanted to be clear on a few things before rooting this phone.
1. I am aware that doing any sorts of modifications to the system will disable OTA updates and those have to be done manually, the question is when I restore my phone (removing root, going back to stock recovery, etc) will automatic OTA updates be re-enabled? Is the stock recovery image even available, or is this even possible? because...
2. When I am looking to sell the phone in the future, I want to be sure that the phone doesn't show any signs of tampering. I am wondering this because the last phone I rooted was the Motorola z2 force, which was the first phone I've ever seen with that "unlocked bootloader" warning when powering on. And with that phone even after all the images were returned to stock, there was still a "your device has loaded a different os" warning, even if it was the stock image. The CTS system functioned similarly to Samsung's knoxs system, where once it was tripped, there was no going back and I wasn't aware of this...
TL;DR: If I ever wish to sell the phone to completely stock (relocked bootloader, stock recovery img, etc), will the phone be permanently tainted with a message like with the image attached? thanks!
Click to expand...
Click to collapse
If you flash stock image and relock bootloader no one will ever know.
As far as otas while rooted, this device will allow you to accept, it will just overwrite root.
Sent from my Pixel 3a using Tapatalk
In your image it's because it's a Motorola, not a good manufacturer with bootloader (but not the worst).
There is 3 big ways with bootloader:
#1 (the best) : The unlock method is 100% in the "code" and you can unlock and relock it yourself (Google with Nexus and Pixel)
#2 (good but not the best) : The unlock method is in the code BUT the manufacturer has a part of the method (an unique code) and you can't do it without register your IMEI on the website, so the manufacturer know it, you lose the warranty... (Motorola, Sony).
#3 (the worst) : You just can't because the manufacturer doesn't want. (Nokia)
jmtjr278 said:
If you flash stock image and relock bootloader no one will ever know.
As far as otas while rooted, this device will allow you to accept, it will just overwrite root.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
alliance1975 said:
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
Click to expand...
Click to collapse
Yes, sir. I'm not sure what method you used other than flashing the rooted boot.img but if am update comes out either patch the new kernel or wait for pbanj to post the modified img. That's it. Easy peasy
Sent from my Pixel 3a using Tapatalk
alliance1975 said:
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
Click to expand...
Click to collapse
You can't install ota on rooted phone. It will fail in recovery.
The steps you need to do is as follows:
1. boot to bootloader, use fast boot to flash stock boot.img
2. go to recovery, apply ota.zip using adb sideload
3. boot back to bootloader, flash the patched boot.img with root
4. reboot and enjoy with root and all your apps/data intact.
googlephoneFKLenAsh said:
You can't install ota on rooted phone. It will fail in recovery.
The steps you need to do is as follows:
1. boot to bootloader, use fast boot to flash stock boot.img
2. go to recovery, apply ota.zip using adb sideload
3. boot back to bootloader, flash the patched boot.img with root
4. reboot and enjoy with root and all your apps/data intact.
Click to expand...
Click to collapse
Wow a slightly different procedure. So it would appear I need the stock boot image when I want to do an OTA. Thanks.
There have been lots of issues with Google pay and securehub (if you work at a big company and want company email on your phone) and unlocked bootloader. Yes, magisk does eventually find workarounds, just depends on how much time you want to spend screwing around knowing it'll break relatively often. Also, we don't have many developers on board yet, so as far as custom roms and kernels go, it's slim pickings.
All that being said, rooted stock is great as long as you don't mind resetting everything to unlock the bootloader.
As you have noted, if you unlock the bootloader you will get the warning when booting. However, unlike your previous phone, you can reflash to stock and relock your bootloader very easily.
Obtaining root and then accepting OTA updates is also much easier with the Pixel phones (and really any phone that is now using A/B partitions). Here is a to some magisk tutorials that show you how easy it is to take an OTA update. https://topjohnwu.github.io/Magisk/tutorials.html
Also as noted previously, it can be tricky to get Google Pay set up with a rooted device. It is possible, but it takes some effort. Personally I don't use Google Pay, so it's no loss to me and I haven't bothered trying to get it to work. Otherwise root is very important to me. I use several mods/apps that are very important to me. Viper4Android, Advanced Charging Control, Ad blocking, Youtube Vanced, and Active Edge Mod (a unique mod for Pixel devices with the active edge gesture) as well as root explorer, tasker (and related apps like secure settings) and titanium backup.
To me, having access to those mods and apps are well worth seeing the warning message and having to manually accept a OTA update and having an extra step or two in the update process.