Develop Bugs

how to unlock bootloader????

im getting the pixel 2xl tomorrow from google. .. i want unlock bootloader . could someone that has success unlocking boatloader, please make a quick step by step guide for windows.
i have latest ADB installed in windows.

Should be the same as the XL. Go into fastboot and type in:
fastboot flashing unlock
fastboot reboot

first go to developer settings and check oem unlocking

Same as the Pixel 1...

ok... i thought i read it was different somewhere. i been trying to find post.

in google site they have an extra line https://developers.google.com/android/images#taimen
''
If necessary, unlock the device's bootloader using one of the following methods:
If you are updating a Nexus or Pixel device that is manufactured in 2015 or later, run this command:
fastboot flashing unlock
For some devices, for example, Pixel 2 XL, the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command:
fastboot flashing unlock_critical
"
what is this unlock critical thing

abogrhen said:
in google site they have an extra line https://developers.google.com/android/images#taimen
''
If necessary, unlock the device's bootloader using one of the following methods:
If you are updating a Nexus or Pixel device that is manufactured in 2015 or later, run this command:
fastboot flashing unlock
For some devices, for example, Pixel 2 XL, the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command:
fastboot flashing unlock_critical
"
what is this unlock critical thing
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/1...become-common-for-many-devices-in-the-future/
The critical unlock goes a step further and allows users to flash custom bootloaders, which are usually only necessary for removing certain security restrictions or occasionally for adding special features.
Click to expand...
Click to collapse
Huh...

subhumanderelict said:
http://www.androidpolice.com/2015/1...become-common-for-many-devices-in-the-future/
Huh...
Click to expand...
Click to collapse
thanks
so critical only for flashing other bootloader
which is something i never heard before

Can anyone confirm whether running fastboot flashing unlock_critical will wipe your device? I've already run fastboot flashing unlock, which of course does wipe the device, but now I need to know if this new command will do so as well. EDIT: After reading over that android police link, this appears to be nothing new so I doubt this will be required on the Pixel XL 2 now in order to have root since it wasn't required for the 6P or the OG Pixels. This could have changed with the new Pixels, so we'll have to figure out if the critical command is actually needed.

do you think the critical unlock would work against magisk in anyway? I just want to unlock so i can root and get adaway, but use magisk when available to still have android pay and netflix

Mr. Steve said:
Can anyone confirm whether running fastboot flashing unlock_critical will wipe your device? I've already run fastboot flashing unlock, which of course does wipe the device, but now I need to know if this new command will do so as well. EDIT: After reading over that android police link, this appears to be nothing new so I doubt this will be required on the Pixel XL 2 now in order to have root since it wasn't required for the 6P or the OG Pixels. This could have changed with the new Pixels, so we'll have to figure out if the critical command is actually needed.
Click to expand...
Click to collapse
i say
don't flash the unlock_critical
no one mention that it is needed
if in the future you need it (oh well backup and do it )
---------- Post added at 06:37 PM ---------- Previous post was at 06:31 PM ----------
fergdizzle9090 said:
do you think the critical unlock would work against magisk in anyway? I just want to unlock so i can root and get adaway, but use magisk when available to still have android pay and netflix
Click to expand...
Click to collapse
i "think"
the unlock_critical is not needed for now
you only need it is flashing a custom bootloader
but for anything else you don't need it
root- recovery -roms - oem update - original bootloader
at least that what the dev google site says

I'm still waiting for the TWRP boot loader to be ready for 2XL. Seeing that I'm probably getting the phone either the end of this week or next week, we still have time.

FYI...you don't have to unlock your bootloader to achieve root. You can still root a phone and have a locked bootloader. Unlocking the bootloader is to allow custom recovery flashing, such as TWRP. Personally, TWRP is a must for me and I always unlock my phone.

js042507 said:
FYI...you don't have to unlock your bootloader to achieve root. You can still root a phone and have a locked bootloader. Unlocking the bootloader is to allow custom recovery flashing, such as TWRP. Personally, TWRP is a must for me and I always unlock my phone.
Click to expand...
Click to collapse
how do you plan on rooting with a locked bootloader? I don't believe this is possible on the Pixel/Pixel 2.

ztotherad said:
how do you plan on rooting with a locked bootloader? I don't believe this is possible on the Pixel/Pixel 2.
Click to expand...
Click to collapse
Yeah, I guess you're right. It depends on the phone and root method. If you're using SuperSU or magisk you'd have to unlock the bootloader. IDK. Just forget everything I said. LOL

js042507 said:
Yeah, I guess you're right. It depends on the phone and root method. If you're using SuperSU or magisk you'd have to unlock the bootloader. IDK. Just forget everything I said. LOL
Click to expand...
Click to collapse
it'd be pretty awesome if someone found a way to root with a locked bootloader. I believe the S8/Note 8 has been rooted with a locked bootloader, now only if this was somehow brought into the world of the pixel. lol.

https://www.androidexplained.com/pixel-unlock-bootloader/

abogrhen said:
i say
don't flash the unlock_critical
no one mention that it is needed
if in the future you need it (oh well backup and do it )
---------- Post added at 06:37 PM ---------- Previous post was at 06:31 PM ----------
i "think"
the unlock_critical is not needed for now
you only need it is flashing a custom bootloader
but for anything else you don't need it
root- recovery -roms - oem update - original bootloader
at least that what the dev google site says
Click to expand...
Click to collapse
Unlock_critical is needed to even flash stock bootloader's. To flash 8.1 preview I had to unlock_critical to update the boatloader to even get passed. It's a required check.
Sent from my Pixel 2 XL using Tapatalk

bryantjopplin said:
Unlock_critical is needed to even flash stock bootloader's. To flash 8.1 preview I had to unlock_critical to update the boatloader to even get passed. It's a required check.
Click to expand...
Click to collapse
Does unlock_critical also wipe the device like regular bootloader unlock?

Jexx11 said:
Does unlock_critical also wipe the device like regular bootloader unlock?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using Tapatalk

failed remote: flashing is not allowed for critical partitions

Hi,
Apparently, I'm misunderstanding something. I'm trying to root my 2XL. I have unlocked the phone successfully, I believe. I have the notification screen at bootup. When I get to the task of flashing a factory image, I get the Failed notification, "FAILED (remote: Flashing is not allowed for Critical Partitions)". This occurs after ... writing 'bootloader_b'.
I was able to get Magisk installed but only 14.0 and I don't have root.
I haven't rooted anything in over 5 years so most of this stuff is pretty foreign.
Any advice would be welcome.

fastboot flashing unlock
then
fastboot flashing unlock_critical

uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?

slingblade01 said:
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
Click to expand...
Click to collapse
Unlock critical first then flash 8.1. Make a backup because this will wipe user data.

I am already unlocked and flashed 8.0 manually. I went to flash 8.1 today and got the OPs error. Are you saying that fastboot flashing unlock_critical will also wipe data? Damn that sucks if true.

SirVilhelm said:
I am already unlocked and flashed 8.0 manually. I went to flash 8.1 today and got the OPs error. Are you saying that fastboot flashing unlock_critical will also wipe data? Damn that sucks if true.
Click to expand...
Click to collapse
Oh yeah! It's definitely true. Unfortunately

uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thx you saved my life <3

uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I get an error saying "device already unlocked" but it still won't let me flash my bootloader... (Hope you're still active here...)

clarkcant said:
I get an error saying "device already unlocked" but it still won't let me flash my bootloader... (Hope you're still active here...)
Click to expand...
Click to collapse
Are you on Pie or Oreo? Is your platform-tools up to date? Have you tried different USB A to USB C cables and ports?

uicnren said:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thanks man u saved my life. btw im not using a pixel, im in a xiaomi a3 but it worked!!

It doesnt work ....Help me to unlock critical

sadatkabir55 said:
It doesnt work ....Help me to unlock critical
Click to expand...
Click to collapse
Without details from you, we can't help you. For example, are you on the latest update? What else did you try? What worked for you and what didn't? Seriously, we can't read your mind. We can't see your phone. We can't perform miracles. It's a bit tiresome to have to ask you for things you should have already provided so we CAN help you.
Since you haven't given any details for anyone to go on, all I can tell you is that depending on the version of Android you are running, the "unlock critical" command may no longer be required, in which case you will get a message when executing the command.

I did not notice this was the forum dedicated to Pixel devices, sorry. I re-did my message in the Oneplus Nord dedicated forum regarding my issue that, however, seems to be the same as the one people encountered here.
Here is the link if anyone feels like helping me : https://forum.xda-developers.com/t/...itions-need-assistance-details-below.4274551/

slingblade01 said:
Lord, you were fast.
Do I need to redo fastboot flashing unlock again before I flash the critical?
Also, my phone was on the latest 8.0.0. Would you recommend that I flash the new 8.1?
Click to expand...
Click to collapse
yeah he was like in 1 min

I have oneplus 8 5g IN2017. I was flashing the global rom.I unlocked the bootloader. but fastboot flashing unlock is taking too long. It just keep running and did'nt finish. Please guide. I am so tired of this.

Also Device is stuck in bootloader.

Khateeb2110 said:
I have oneplus 8 5g IN2017. I was flashing the global rom.I unlocked the bootloader. but fastboot flashing unlock is taking too long. It just keep running and did'nt finish. Please guide. I am so tired of this.
Click to expand...
Click to collapse
You'll need to read about your own phone. This thread is about the Pixel 2 XL. Different manufacturers tend to have different ways to unlock the bootloader.
Also, people who follow this thread are unlikely to know about OnePlus. Find a OnePlus-thread to ask for help.

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.

Question How to relock bootloader on Pixel 6 Pro

I have to return my old phone today and need to lock the bootloader back. I already did a factory reset which did not work. Could someone please give me the directions on how to relock it so I can get it sent off? Thanks.

Oaklands said:
I have to return my old phone today and need to lock the bootloader back. I already did a factory reset which did not work. Could someone please give me the directions on how to relock it so I can get it sent off? Thanks.
Click to expand...
Click to collapse
Haven't done it in a while but I'm sure it's the same. Go into fastboot and make sure the device is recognized with "fastboot devices" then " fastboot flashing lock " and it will wipe device and reboot.

bobby janow said:
Haven't done it in a while but I'm sure it's the same. Go into fastboot and make sure the device is recognized with "fastboot devices" then " fastboot flashing lock " and it will wipe device and reboot.
Click to expand...
Click to collapse
Thank you. I will give it a try.

That did not do it. What I tried was flashing the Raven Rom again with a standard flash-all.bat.
The bootloader was still locked then I ran the "fastboot flashing lock" command and it worked.

Oaklands said:
That did not do it. What I tried was flashing the Raven Rom again with a standard flash-all.bat.
The bootloader was still locked then I ran the "fastboot flashing lock" command and it worked.
Click to expand...
Click to collapse
Maybe this isn't up to date, then? Weird. Not so uncommon if it is out of date, but it's such a big thing I would expect it to be up to date. You're using the latest Platform Tools, correct? I'm confused because you start the first sentence "That did not do it" but then say "and it worked" at the end, so I'm missing something.
https://source.android.com/setup/build/running#relocking-the-bootloader
Re-locking the bootloader​To re-lock the bootloader:
For newer devices (2015 and higher):
fastboot flashing lock
For older devices (2014 and lower):
fastboot oem lock
Note: Re-locking the bootloading on a
Click to expand...
Click to collapse

You could also try the flashing tool from Google that makes it extremely easy. Before you flash you can choose to lock the bootloader as one fo the options. https://flash.android.com/welcome?continue=/back-to-public

liljq said:
You could also try the flashing tool from Google that makes it extremely easy. Before you flash you can choose to lock the bootloader as one fo the options. https://flash.android.com/welcome?continue=/back-to-public
Click to expand...
Click to collapse
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.

roirraW edor ehT said:
Maybe this isn't up to date, then? Weird. Not so uncommon if it is out of date, but it's such a big thing I would expect it to be up to date. You're using the latest Platform Tools, correct? I'm confused because you start the first sentence "That did not do it" but then say "and it worked" at the end, so I'm missing something.
https://source.android.com/setup/build/running#relocking-the-bootloader
Click to expand...
Click to collapse
Just running the command he gave me did not work. The phone would not respond to locking the bootloader. I updated again using the standard .37 image with the -w command. The ran the "fastbopt flashing lock" command and it then responded fine.

V0latyle said:
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.
Click to expand...
Click to collapse
I didn't know about this tool beforehand. I have unlocked and rooted a phone in a few years. It's like learning it all over again. I appreciate you letting me now about this.

Oaklands said:
I didn't know about this tool beforehand. I have unlocked and rooted a phone in a few years. It's like learning it all over again. I appreciate you letting me now about this.
Click to expand...
Click to collapse
This tool is specific to Pixel devices only and cannot be used with any other platform.

V0latyle said:
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.
Click to expand...
Click to collapse
I concur!

Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
So i saw here the command: fastboot flashing lock
or to use the google tool
https://flash.android.com/welcome?continue=/back-to-publicdoes the usage of the tool meaning that the device will be wiped? (I have the stock rom ->rooted -> uninstall magisk) and I want to be original with that stock to get updateds,
Thanks

I7210I said:
Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
So i saw here the command: fastboot flashing lock
or to use the google tool
https://flash.android.com/welcome?continue=/back-to-publicdoes the usage of the tool meaning that the device will be wiped? (I have the stock rom ->rooted -> uninstall magisk) and I want to be original with that stock to get updateds,
Thanks
Click to expand...
Click to collapse
As you may know, even though you uninstalled Magisk and don't have root, you could still have modified partitions on the phone.
You can use:
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
(same as your link) but uncheck the option to wipe, then the phone won't be wiped.
Only then re-lock the bootloader.

roirraW edor ehT said:
As you may know, even though you uninstalled Magisk and don't have root, you could still have modified partitions on the phone.
You can use:
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
(same as your link) but uncheck the option to wipe, then the phone won't be wiped.
Only then re-lock the bootloader.
Click to expand...
Click to collapse
Thank you, the lock of the bootloader will be how?
And in that point i'm going back to the start right?

I7210I said:
Thank you, the lock of the bootloader will be how?
And in that point i'm going back to the start right?
Click to expand...
Click to collapse
You're welcome. I believe you have the lock command correct. See here -> Re-locking the bootloader
Keep in mind that when you do that, it will factory reset your device, and there's no way around that. Every single time you unlock the bootloader or lock it, it forces the phone to factory reset.
Also note that after re-locking the bootloader, you should toggle OEM unlocking in Developer options back to disabled.

roirraW edor ehT said:
You're welcome. I believe you have the lock command correct. See here -> Re-locking the bootloader
Keep in mind that when you do that, it will factory reset your device, and there's no way around that. Every single time you unlock the bootloader or lock it, it forces the phone to factory reset.
Also note that after re-locking the bootloader, you should toggle OEM unlocking in Developer options back to disabled.
Click to expand...
Click to collapse
and....when I will do factory reset = the device will be wiped , right? no way to do it without that

I7210I said:
and....when I will do factory reset = the device will be wiped , right? no way to do it without that
Click to expand...
Click to collapse
Correct.
Looks like @fil3s gave you some of this information in the separate thread you created here. Since I haven't used Official Google Android Flash Tool, I forgot that it appears there's an option right on that site to lock the bootloader. You should follow the directions that @fil3s gave you there, and yes, it will wipe. Factory Reset = Wipe

Ok no way so no way
Will do that
Thank you

I7210I said:
Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
Click to expand...
Click to collapse
Everything @roirraW "edor" ehT said, but just to be clear, if you only have the bootloader unlocked but nothing else modified, you should still be able to take OTAs. You don't need a locked bootlaoder to take OTAs.

Lughnasadh said:
Everything @roirraW "edor" ehT said, but just to be clear, if you only have the bootloader unlocked but nothing else modified, you should still be able to take OTAs. You don't need a locked bootlaoder to take OTAs.
Click to expand...
Click to collapse
So I think I will leave it like this if I will still get the OTAs, there is no problem with that right?
Thanks

Question Unable to lock the bootloader

Week ago I flashed the android 14 dev, don't liked it and yesterday flashed A13 (TQ1A.230205.002) with Android Flash Tool. Today I saw that I can't add my credit card to the Google Pay. I checked in settings and found out that my bootloader unlocked but the button is unavailable.
What can I do?

If your phone was rooted, then do a factory reset. Download and install the Google Platform tools, or if adb and fastboot drivers are installed system-wide, that's fine.
Connect phone to PC in fastboot mode
Enter the first command "fastboot devices"
Then type, "fastboot flashing unlock"
Confirm on your device to lock the bootloader
That's it. If you want a detailed guide, here are the instructions on how to unlock/relock the bootloader on a Pixel phone.

wrkadung said:
If your phone was rooted, then do a factory reset. Download and install the Google Platform tools, or if adb and fastboot drivers are installed system-wide, that's fine.
Connect phone to PC in fastboot mode
Enter the first command "fastboot devices"
Then type, "fastboot flashing unlock"
Confirm on your device to lock the bootloader
That's it. If you want a detailed guide, here are the instructions on how to unlock/relock the bootloader on a Pixel phone.
Click to expand...
Click to collapse
Locking with adb will erase all my data?

max_134 said:
Locking with adb will erase all my data?
Click to expand...
Click to collapse
Yes, of course! Unlocking and relocking will erase and factory reset your phone, I use Google One to take backups.

Alternatively, you can also use the Android flash tool, and it will automatically do it for you. You just have to follow the on-screen instructions, and it will ask for your confirmation to lock the bootloader, and you also get the option to wipe data (never tried unchecking the wipe data option).
Here is the video tutorial, if you need it.

EDIT: apologies for covering much of what has already been discussed by @wrkadung, got ninja'd a bit there...
I wouldn't risk locking the bootloader via platform-tools....so many instances from all the way back from the original Pixel has had countless members hard-brick their Pixel's relocking the bootloader.
The safest way to go about it is to use the Android Flash Tool to flash both slots and relock bootloader; most hard bricks happen when it's not flashed to both slots and/or the improper factory image is used...
But the OEM unlocking being greyed out is sometimes SOP after unlocking the bootloader. It's not really anything to be concerned about. If Wallet isn't working properly, it is doubtful it is simply having the unlocked bootloader; Wallet usually doesn't work when rooted than it is the fact of an unlocked bootloader. You should try Force Stop-ing and Clear Data Wallet first. Then even "uninstall updates" and/or revert to an older version before locking the bootloader. ESPECIALLY if you don't wish to wipe the device by relocking the bootloader...

max_134 said:
Week ago I flashed the android 14 dev, don't liked it and yesterday flashed A13 (TQ1A.230205.002) with Android Flash Tool. Today I saw that I can't add my credit card to the Google Pay. I checked in settings and found out that my bootloader unlocked but the button is unavailable.
What can I do?
Click to expand...
Click to collapse
Google pay will work with an unlocked bootloader.

simplepinoi177 said:
EDIT: apologies for covering much of what has already been discussed by @wrkadung, got ninja'd a bit there...
I wouldn't risk locking the bootloader via platform-tools....so many instances from all the way back from the original Pixel has had countless members hard-brick their Pixel's relocking the bootloader.
The safest way to go about it is to use the Android Flash Tool to flash both slots and relock bootloader; most hard bricks happen when it's not flashed to both slots and/or the improper factory image is used...
But the OEM unlocking being greyed out is sometimes SOP after unlocking the bootloader. It's not really anything to be concerned about. If Wallet isn't working properly, it is doubtful it is simply having the unlocked bootloader; Wallet usually doesn't work when rooted than it is the fact of an unlocked bootloader. You should try Force Stop-ing and Clear Data Wallet first. Then even "uninstall updates" and/or revert to an older version before locking the bootloader. ESPECIALLY if you don't wish to wipe the device by relocking the bootloader...
Click to expand...
Click to collapse
Yes, definitely, a stock factory image is required. Most people directly lock the bootloader on a rooted phone using adb & fastboot commands, which results in bricking the phone.
On stock firmware, it is working perfectly. Right now I am working on a video tutorial for Pixel 7 and it worked fine without any issues, it was just bootloader unlocked device (not rooted).