Develop Bugs

Verizon Pixel Unlocked Bootloader Question

Just got my pixel xl today, unlocked immediately. Question is if i update the bootloader from the factory images, am i going to lose my unlock or will this stick until i manually lock it (which i won't )? Thanks!

It will stick, no problem. Update away.

So just to clairfy because i'm paranoid about these things, I can run the flash-all script for the Feb update and my bootloader will remain unlocked correct?

danielson2047 said:
So just to clairfy because i'm paranoid about these things, I can run the flash-all script for the Feb update and my bootloader will remain unlocked correct?
Click to expand...
Click to collapse
Correct. Your bootloader will remain unlocked, unless you execute the following command: fastboot oem lock

With the Verizon bootloader, I used Depixel8 how do I work with the boot slots? I have been modifying since the LG ally but the table has changed and I don't want to end with a brick. Could I flash the bootloader to two slots?

Safest thing to do is to dePixel8 right off the bat, and then take an OTA before you do anything else. The OTA installs on the other slot, guaranteeing that you have a bootloader on both slots before you start monkeying around.

JU57US said:
Safest thing to do is to dePixel8 right off the bat, and then take an OTA before you do anything else. The OTA installs on the other slot, guaranteeing that you have a bootloader on both slots before you start monkeying around.
Click to expand...
Click to collapse
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?

palvarez05 said:
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?
Click to expand...
Click to collapse
No, unfortunately not.

I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.

Falargi said:
I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.
Click to expand...
Click to collapse
No it wont relock at all. ONly way for it to relock is to run the command for lock through download mode.

Falargi said:
I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.
Click to expand...
Click to collapse
Follow this guide, it's in the guides section
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886

The only way to relock your bootloader is if you type "fastboot flashing OEM lock" once you have unlocked it, never never never relock it (VZW models only) only lock it if you need to do a RMA. Once unlocked you can flash whatever factory image your heart desires.

palvarez05 said:
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?
Click to expand...
Click to collapse
Are you positive that it had had to build out of the box? Or did it simply get upgraded before you checked? Either way you cannot now unlock the bootloader, but it is worthwhile to note whether or not Verizon is updating the phones before boxing them and shipping them. Check the side of your box your phone came in, to see the original build number that the phone had on it when it was boxed up.

help: can't OEM unlock Pixel 2 XL anymore

I can not OEM unlock my Pixel 2 XL anymore. It is running a custom ROM that is not being updated anymore. In the developer settings, "OEM unlocking" is gray, and it says "Connect to the Internet or contact your carrier". The phone is connected to the internet and the internet is working flawlessly. This is NOT a Verizon version and there already IS a custom ROM on it, so it's been unlocked in the past.
I have tried to factory reset numerous times, and the option still did not become available.
What else could I try?

oUkcpV9ykzUC said:
I can not OEM unlock my Pixel 2 XL anymore. It is running a custom ROM that is not being updated anymore. In the developer settings, "OEM unlocking" is gray, and it says "Connect to the Internet or contact your carrier". The phone is connected to the internet and the internet is working flawlessly. This is NOT a Verizon version and there already IS a custom ROM on it, so it's been unlocked in the past.
I have tried to factory reset numerous times, and the option still did not become available.
What else could I try?
Click to expand...
Click to collapse
Is it grayed out in the on or off position? Which is not uncommon on custom roms.

Do you have access to the the ROM if you need to reinstall it?
I would backup everything you can using twrp make a full and then also make sure you have boot.img backed up then try flashing factory image or whatever ROM you want to move to if you have an issue just switch back if it will take at all
Sent from my Pixel 2 XL using Tapatalk

So you unlocked it and flashed a custom ROM and then reinstalled the stock recovery and locked it like that for Android pay? Maybe the custom ROM was based off of a Verizon install so you phone thinks it's a Verizon phone now. You may be out of luck.

nukeruss said:
Maybe the custom ROM was based off of a Verizon install so you phone thinks it's a Verizon phone now. You may be out of luck.
Click to expand...
Click to collapse
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.

sublimaze said:
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
Click to expand...
Click to collapse
Forgot to mention, this is NOT a ROM that uses TWRP, but its own recovery. Maybe I'm not understanding you right, but how do I flash a factory image if I can't OEM unlock?

gjkrisa said:
Do you have access to the the ROM if you need to reinstall it?
I would backup everything you can using twrp make a full and then also make sure you have boot.img backed up then try flashing factory image or whatever ROM you want to move to if you have an issue just switch back if it will take at all
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's not a ROM that uses TWRP but its own recovery. Not sure what you mean by "if you have an issue just switch back if it will take at all".

sublimaze said:
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
Click to expand...
Click to collapse
Flashing the factory image using Deuce's script will fix this.
Don't skip any steps.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Mine is grayed out with a notification underneath telling me the bootloader is already unlocked.

Larzzzz82 said:
Mine is grayed out with a notification underneath telling me the bootloader is already unlocked.
Click to expand...
Click to collapse
What do you get when you run...fastboot oem device-info...?
Is it grayed out in the on or off position?

Grayed off. Can't fastboot now but will when i can. This is not the vzw version and was unlocked within 10 minutes of unboxing it. The option didn't become available until it connected to a network...

Have you tried adb reboot fastboot?
Larzzzz82 said:
Grayed off. Can't fastboot now but will when i can. This is not the vzw version and was unlocked within 10 minutes of unboxing it. The option didn't become available until it connected to a network...
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

gjkrisa said:
Have you tried adb reboot fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I was no where near a computer... Is that a valid adb command? I go adb reboot- bootloader then fastboot devices before i do anything else.
---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------
The get device-info returned:
Verity mode: true
Device unlocked: true
Charger screen enabled: true

How to Lock Bootloader

Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.

Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I do have a computer, a Windows 10 Pro

Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.

sliding_billy said:
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
Click to expand...
Click to collapse
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.

eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.

eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.

coolhandz said:
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
Click to expand...
Click to collapse
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".

sliding_billy said:
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
Click to expand...
Click to collapse
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.

Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.

sliding_billy said:
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
Click to expand...
Click to collapse
Yeah, so I locked using "fastboot flashing lock" but then it doesn't start, saying that there is no operating system or something like that. I freaked out and was able to unlock again using "fastboot flashing unlock". Now all is wiped. I guess I need to flash the oem rom first, then lock. I'll have to do this all later tonight. Just glad that I didn't brick it yet.

eec007 said:
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Click to expand...
Click to collapse
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.

bobby janow said:
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
Click to expand...
Click to collapse
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.

eec007 said:
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
Click to expand...
Click to collapse
One thing I would do before I relocked the bl would be to do the full login procedure, email everything other than apps. Then make sure you're on the Nov update in about phone, I'm sure you will be, and then fastboot relock the bl with the proper command. It will wipe the device again but it's a small price to pay for about 10 minutes of work. Then once it reboots and there is no more error message you'll be fully stock. Enable dev options again and make sure the oem switch is active allowing bl unlock. Then you're done. I've gotten to the point on my 5X where I even flip the oem switch so it can't be bl unlocked until I go in and flip it back. Dangerous if you're flashing stuff but not so much if you're just taking OTAs. That's of course your call entirely. Good luck.

eec007 said:
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
Click to expand...
Click to collapse
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.

eec007 said:
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Click to expand...
Click to collapse
They're right to mention that relocking a modified device can result in a brick.
Your best bet is to go to https://developers.google.com/android/images#taimen
Follow the directions to the "T", then relock it if you are really really sure that the unlock screen bothers you.
Would suggest to do this anyway, no matter future unlock status.

TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
I agree with most of your post other than waiting for the next OTA before you lock the bootloader. Why would he need to do that? If he's stock, and he'll see that immediately, then relock it. He doesn't want root or Magisk but only wants banking and Pay. With the slider allowing bl unlock he's in no danger whatsoever. Lock and relock whenever he wants. OTA will not disallow the slider once it's set.

TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
Thank you for explaining this. I had thought that the Developer Option slider was to unlock the bootloader, but your explanation clarifies it, the slider is to allow the bootloader to be unlocked...

Ok, so I tried to flash the factory image using adb flash-all and it keeps getting the error:
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Now the phone is not working at all and says that "device is corrupt" and will not boot past the white google screen. I can try again using adb, but it is the same error each time. I tried to download the image again and same sparse error. I can also fastboot in TWRP, but not sure what to do in there. What am I doing wrong? I guess I should've rooted and used Magisk like others have said.

turns out changing to a different cable resolved my sparse error and I was then successfully able to apply the factory image and lock the device. Thanks everyone for the help.

Unlocked Bootloader leads to System Integrity being Compromised?

So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:
https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.
Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance

binary**# said:
So Moto One Action keeps on surprising every now and then. The latest addition to it is the System Integrity is Compromised message. This is how I end up doing so:
https://photos.app.goo.gl/8Q5xZXTzGWGVMZX48
Unlocked the device's bootloader.
Rooted the device successfully using Magisk patched boot image and Moto One Vision's vbmeta file.
Then I had to unroot my device (for some reason), so flashed the stock firmware using Moto Smart Assistant Tool. But kept the device's bootloader in an unlocked state.
Now I have a stock ROM on my device, unrooted without any modification to the /system partition. The only modification is the unlocked bootloader.
Then I went to System > Advanced > System Updates and then got greeted with the message that I am no longer eligible for software updates. Although not an issue as I could still flash the stock firmware by one way or the other, I am just curious to know whether it is indeed a result of an unlocked bootloader or not. All the users who have unlocked their bootloader kindly let me know in the comments whether they have the same message or not. Thanks in advance
Click to expand...
Click to collapse
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.

Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?

binary**# said:
Hey, sorry if I am wrong but I highly doubt this claim of yours: "you need a locked bootloader for OTA". True to my knowledge, I don't think any OEM really blocks OTA on an unlocked bootloader device. Until we modify system files, we are safe to get OTA updates. That's what I always knew and every time it stood correct. Isn't it?
Click to expand...
Click to collapse
I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.

tys0n said:
Yeah you need locked bootloader for OTA. Same on One Vision.
Magisk will hide the unlocked status while you're rooted so that you can check for OTA, but I believe it will fail to install during update. Never tyried but that's how it is on Motorola One and One Power.
fastboot flash if you're unlocked and want to update.
Click to expand...
Click to collapse
tys0n said:
I don't know about all oem's but I believe samsung blocks ota if bootloader is unlocked.
I read somewhere in G7 forum that Moto support had told that OTA is disabled on that device if you're on unlocked bootloader, so I guess Moto changed their policy about that too.
Click to expand...
Click to collapse
Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:
"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."
Anyways, thanks for your inputs.....

binary**# said:
Not sure about Samsung, but was going through Motorola's official blog, and this is what they have to say:
"Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola."
Anyways, thanks for your inputs.....
Click to expand...
Click to collapse
Oh I see. I don't know then.
You could ask here:
https://forums.lenovo.com/t5/motorola-one-action/bd-p/motorola_one_action_en
They should be able to give a proper answer.

I got a XT2013-4 US - Unlocked boot loader, but the root method doesn't work for the US Firmware (Hear the EU Firmware works for someone in Canada) but I am unable to check for updates being fully stock, unrooted, and only an unlocked bootloader so yes if the OS can read that the bootloader is unlocked then it won't let you check for updates (At least on the US Firmware) but then we aren't Android One though on the XT2013-4

If you are on Stock Firmware, unrooted but your Bootloader is Unlocked, you'll not get any OTA despite the Motorola Support page you've posted (It might be old information, just look the phone they used on the top).

Is it possible to relock it?

ReConfirmed: Official OTA Updates is possible after Unlocked Bootloader.
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.

binary**# said:
Just to reiterate the facts (in response to #2 and #8), I guess my assumption was well and truly correct. This is because I did end up receiving an OFFICIAL OTA update from Motorola, a few days back. And at this point, my BOOTLOADER IS STILL UNLOCKED! The first image attached below shows the OTA update notification as well as the proof that my Bootloader is unlocked. The second one provides details about that OTA.
Click to expand...
Click to collapse
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.

tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
No, my device isn't rooted. The only modification is the unlocked bootloader. I did this when I saw enrolled users getting beta Android 10 updates for Moto One Power. Since One Action has released almost a year after Power, I thought the soak test would just be around the corner for our device as well. But here we are with One Power receiving Stable Android 10 update, and there is no news of the same for our device. I have got myself enrolled in the MFN and just keeping my fingers crossed.

binary**# said:
No, my device isn't rooted. The only modification is the unlocked bootloader.
Click to expand...
Click to collapse
Ok, thanks. That's intresting.

tys0n said:
Rooted with Magisk? That would explain why OTA would work. It tries to hide the unlock/root status.
Click to expand...
Click to collapse
One more doubt. I tried the root hide via Magisk for some apps like Google Pay or Pokemon Go and it worked pretty well. But could it trick OEMs as well into thinking the device is unrooted, so that the device may receive OTA updates? I guess probably not, but need some more weight on this opinion.

It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..

aditya7286 said:
It's possible to relock the bootloader and get ota functionality back.. just use 'fastboot oem lock' command and then reflash the original firmware..
Click to expand...
Click to collapse
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response

Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.

arsradu said:
Unlocking bootloader on its own does not lead to that message. So I'm guessing it's probably something specific to that ROM, or....something else entirely.
Click to expand...
Click to collapse
binary**# said:
Bootloader Locking/Unlocking has nothing to do while receiving OTAs. As I have mentioned in my other post, I have already received Android 10 OTA on an unlocked bootloader. And as far as the response to my own question goes, it was regarding whether one could hide root from the system as we do for Google Pay and get OTAs. The answer is nopes. I tried hiding root from all the necessary files related to Motorola's system OTA via Magisk but didn't get the update. As soon as I unrooted, BOOM the Android 10 update was right there!
Anyways thanks for your response
Click to expand...
Click to collapse
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.

methuselah said:
I am getting same thing on my moto g8 plus. just flashed omni and now when i returned the device shows this message.
Click to expand...
Click to collapse
You mean "System Integrity Compromised" or something else?
Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.
Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.
Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.
So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.
Sent from my motorola one action using Tapatalk

arsradu said:
You mean "System Integrity Compromised" or something else?
Omni, if we're talking about OmniROM, is a custom, pre-rooted ROM, right? So...maybe that's why.
Interesting though that people with stock ROM, who only unlocked the bootloader (no root) are getting the same message.
Personally, I never rooted this phone and I'm not planning to. Also never seen that message on my phone. However, it was bootloader unlocked and now it's back to locked again.
So... For custom ROMs I can understand why it would show you this. For stock ROM with no root, that doesn't make much sense to me. But maybe I'm missing something.
Sent from my motorola one action using Tapatalk
Click to expand...
Click to collapse
The issue in brief.
Well the thing is i have again flashed back stock that with blankflash file. Before april update i had locked bootloader. But now nothing is happening. As soon as i flash stock ROM(clean stock) and relock the bootloader, the phone just says it is corrupted. But at the same time when i unlock the boot loader it boots.

Question Flash Google Global Firmware on Verizon Firmware

Is there a way to flash unlock google global version firmware onto the Verizon pixel 6 pro without root/unlock bootloader like there use to be. Can't believe nobody has asked this yer

dprscorpio7 said:
Is there a way to flash unlock google global version firmware onto the Verizon pixel 6 pro without root/unlock bootloader like there use to be. Can't believe nobody has asked this yer
Click to expand...
Click to collapse
Haven't tried it yet, but I'm assuming the Android Flash Tool would work.
Android Flash Tool
flash.android.com

DarkusRattus said:
Haven't tried it yet, but I'm assuming the Android Flash Tool would work.
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Also, just to confirm there is no bootloader unlock for Verizon version right

dprscorpio7 said:
Also, just to confirm there is no bootloader unlock for Verizon version right
Click to expand...
Click to collapse
Correct, and likely never will have bootloader unlock (for this or any future Verizon phone) except perhaps paying someone to do so once anyone figures out some way to hack it. I wouldn't hold my breath, though. The only way in the past has been by vulnerabilities/hacks, or the one time Verizon accidentally let those on Android 7.10 on the Pixel 1 the ability to toggle OEM Unlocking, but they patched it in Android 7.11.

dprscorpio7 said:
Is there a way to flash unlock google global version firmware onto the Verizon pixel 6 pro without root/unlock bootloader like there use to be. Can't believe nobody has asked this yer
Click to expand...
Click to collapse
Unless you'll be using the device on an international carrier Google doesn't compile for, there's no reason to do so that I'm aware of, as the images aren't for branded devices, but for the carrier the device is being used on.

JW09I4 said:
Unless you'll be using the device on an international carrier Google doesn't compile for, there's no reason to do so that I'm aware of, as the images aren't for branded devices, but for the carrier the device is being used on.
Click to expand...
Click to collapse
I need the unlocked version from Google store. I still have a Verizon security check on the phone and I bought it unlocked from best buy... So that is the reason. I want to know if I can flash Google store stock firmware on this phone?

dprscorpio7 said:
I need the unlocked version from Google store. I still have a Verizon security check on the phone and I bought it unlocked from best buy... So that is the reason. I want to know if I can flash Google store stock firmware on this phone?
Click to expand...
Click to collapse
You can only flash a full firmware image with the bootloader unlocked, however you should be able to flash the OTA update required (you could also use Google's online Android Flash Tool).
AFAIK, there is no difference in the firmware between the unlocked vs branded devices besides bloatware from the carrier.
My understanding of the different images Google has compiled for specific carriers has to do with tweaks to the radio software and/or how the firmware interacts with the radio to ensure the best possible experience across carriers.

JW09I4 said:
You can only flash a full firmware image with the bootloader unlocked, however you should be able to flash the OTA update required (you could also use Google's online Android Flash Tool).
AFAIK, there is no difference in the firmware between the unlocked vs branded devices besides bloatware from the carrier.
My understanding of the different images Google has compiled for specific carriers has to do with tweaks to the radio software and/or how the firmware interacts with the radio to ensure the best possible experience across carriers.
Click to expand...
Click to collapse
Well I've got a best buy unlocked version and yes I can unlock bootloader no problem and still getting a Verizon security check on hotspot which is the reason for me needing different firmware on phone. So I'll go ahead and unlock the bootloader if you can point me in the direction links of information on the flash tool and firmware I'm looking for that would be great. I want the global firmware unlocked for pixel 6 pro link

Here's the image.

dprscorpio7 said:
Here's the image.
Click to expand...
Click to collapse
That's likely not going to go away with the Global image since the only differences between the images have to do with how the radios communicate with the arbitrary carrier [AFAIK]. If you're using Verizon, the Verizon image is the correct image to use.
For your issue, there are ways to get around it, possibly via the build.prop, but if not, then likely via a Magisk module.
The last Pixel I had before the 6 Pro was the Pixel XL and tethering up until then was controlled via a true/false [1/0] value within the build.prop, however that may have changed, but tethering is software-controlled, not radio-controlled.
Full firmware image (instructions) vs OTA image (instructions)

dprscorpio7 said:
Well I've got a best buy unlocked version and yes I can unlock bootloader no problem and still getting a Verizon security check on hotspot which is the reason for me needing different firmware on phone. So I'll go ahead and unlock the bootloader if you can point me in the direction links of information on the flash tool and firmware I'm looking for that would be great. I want the global firmware unlocked for pixel 6 pro link
Click to expand...
Click to collapse
I'm not entirely sure what you mean by Verizon security check. Do you have Verizon as your provider? If so then you're out of luck no matter what firmware you flash, hotspot will cost you. I'm not sure about what happens if you root though but that's a horse of another color. Lots of threads on bypassing hotspot restrictions if you have root.

This security check does not happen if you buy directly from Google store, so I need that firmware serial number and download file with how to flash it on my device.

dprscorpio7 said:
This security check does not happen if you buy directly from Google store, so I need that firmware serial number and download file with how to flash it on my device.
Click to expand...
Click to collapse
Please see my prior comment

roirraW edor ehT said:
Correct, and likely never will have bootloader unlock (for this or any future Verizon phone) except perhaps paying someone to do so once anyone figures out some way to hack it. I wouldn't hold my breath, though. The only way in the past has been by vulnerabilities/hacks, or the one time Verizon accidentally let those on Android 7.10 on the Pixel 1 the ability to toggle OEM Unlocking, but they patched it in Android 7.11.
Click to expand...
Click to collapse
That was awesome...

dprscorpio7 said:
This security check does not happen if you buy directly from Google store, so I need that firmware serial number and download file with how to flash it on my device.
Click to expand...
Click to collapse
This isn't even a security check? Did you read the pop up? It clearly states to call customer service to subscribe and activate the hotspot. If you don't pay for hotspot, it won't work.... Also, if you bought the unlocked version from Best Buy.. then it is unlocked... There is no other software to flash. However, if you bought (which I'm sure you did) the Verizon version from Best Buy then it is a carried branded device, and it is unfortunately not unlocked straight from Google.

teegraves58 said:
This isn't even a security check? Did you read the pop up? It clearly states to call customer service to subscribe and activate the hotspot. If you don't pay for hotspot, it won't work.... Also, if you bought the unlocked version from Best Buy.. then it is unlocked... There is no other software to flash. However, if you bought (which I'm sure you did) the Verizon version from Best Buy then it is a carried branded device, and it is unfortunately not unlocked straight from Google.
Click to expand...
Click to collapse
It is a security check, I promise you. I've had the pixels in the past and bad the same issue I'll show you that when I flash this unlocked firmware from Google store I guarantee you the security check or please subscribe will not pop up and will allow me to enable hotpsot

dprscorpio7 said:
It is a security check, I promise you. I've had the pixels in the past and bad the same issue I'll show you that when I flash this unlocked firmware from Google store I guarantee you the security check or please subscribe will not pop up and will allow me to enable hotpsot
Click to expand...
Click to collapse
Have you tried to install global firmware on verizon Pixel?

teegraves58 said:
This isn't even a security check? Did you read the pop up? It clearly states to call customer service to subscribe and activate the hotspot. If you don't pay for hotspot, it won't work.... Also, if you bought the unlocked version from Best Buy.. then it is unlocked... There is no other software to flash. However, if you bought (which I'm sure you did) the Verizon version from Best Buy then it is a carried branded device, and it is unfortunately not unlocked straight from Google.
Click to expand...
Click to collapse
It's a config file security check on carriers who charge separately for the ability to tether and has nothing to do with a carrier lock - if the device is bootloader unlocked, this could be bypassed previously​​​
georgesurgeon said:
Have you tried to install global firmware on verizon Pixel?
Click to expand...
Click to collapse
Please see prior comment​