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 bootloaderTo 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
Related
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Az Biker said:
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Click to expand...
Click to collapse
Only if you want to update the bootloader. That's the only thing I can see that critical does.
Sent from my Pixel 2 XL using Tapatalk
I believe unlock_critical is necessary if you want to be able to flash updates manually..
"For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
If you are updating an older device, run this command:
fastboot oem unlock "
Above quote is from Google Factory Image page.
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Badger50 said:
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Click to expand...
Click to collapse
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Wickidmasshole said:
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Click to expand...
Click to collapse
This is why I asked the question. I wasn't sure if doing the basic unlock prior to the critical unlock would be an issue.
I'm running the critical unlock when I get home tonight (I want to be able to update the bootlader in the future), I'll let you know what I run into, if anything.
Az Biker said:
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Click to expand...
Click to collapse
Didn't use any toolkits, just these 2 guides....
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176 https://forum.xda-developers.com/pixel-2-xl/how-to/guide-magisk-root-snoke-kernel-t3701930
....and didn't run into any problems at all. My P2XL is just humming right along. The battery on this thing is phenomenal! Takes me a good 2 days to knock it down to 10% :good:
Now we just need some TWRP to get Beans up and running :good::good:
Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
iamjimmy said:
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
Click to expand...
Click to collapse
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Badger50 said:
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Click to expand...
Click to collapse
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Sent from my [device_name] using XDA-Developers Legacy app
slaydog said:
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Click to expand...
Click to collapse
This one :good:
Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
marbertshere said:
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
Click to expand...
Click to collapse
I've unlocked the ordinary bootloader first, then the bootloader_critical without any problems :good:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
jaybird779 said:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
Click to expand...
Click to collapse
The bootloader_critical unlock has to be performed only if you want to flash the bootloader (e.g. when you flash a factory image), but, if you want to perform all the other operations, such as rooting, kernel flashing, etc., you have to unlock the ordinary bootloader, too.
So, these are the two Fastboot commands:
fastboot flashing unlock_critical (for bootloader flashing, you've already performed this)
fastboot flashing unlock (for all the other operations)
The request which appears on your phone, when you enter these two commands, is the same, and you have to allow the bootloader unlock in both cases :good:
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.
Is there no easy way to relock the bootloader without using the MSM Tool (which I've never done)? I relocked it in the normal way, fastboot oem lock, but that resulted in a "device is corrupt and will not boot" error. I unlocked it and it's fine, but... I want to re-lock it.
dmarden said:
Is there no easy way to relock the bootloader without using the MSM Tool (which I've never done)? I relocked it in the normal way, fastboot oem lock, but that resulted in a "device is corrupt and will not boot" error. I unlocked it and it's fine, but... I want to re-lock it.
Click to expand...
Click to collapse
On OOS? Run a full local upgrade to whatever your current version is and try again
Yeah, it was just running stock firmware... Ok, so full local upgrade and try fastboot oem lock again?
Worth a try I guess, thanks!!!
The local update is running now, hope it works since the MSM Tool gives me a "failed to start" "because of a side by side configuration" error... lol. Sheesh, never experienced trouble relocking a device before.
dmarden said:
Yeah, it was just running stock firmware... Ok, so full local upgrade and try fastboot oem lock again?
Worth a try I guess, thanks!!!
Click to expand...
Click to collapse
Just factory reset once and then lock from fastboot > fastboot OEM lock > Select Yes to confirm and the device will lock the bootloader and reboot into OS
No dice... same error... what the heck?!
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
null0seven said:
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
Click to expand...
Click to collapse
It wouldn't let me install the downgrade APK (maybe because it is not on A12), but I am downloading the downgrade/rollback package and will try it.
null0seven said:
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
Click to expand...
Click to collapse
No dice... I presume because it's an older version it needs that APK.
Ok... this is resolved, even if I don't know how. I literally just tried it a third time and it worked. *shrug*
Thanks to those that responded.
dmarden said:
Ok... this is resolved, even if I don't know how. I literally just tried it a third time and it worked. *shrug*
Thanks to those that responded.
Click to expand...
Click to collapse
This is how I always did it
Hello, i unlocked the bootloader of my motorola one action. And i installed lineage 18.1 official, but i want to lock the bootloader again. i tried locking the bootloader using this help thread https://forum.xda-developers.com/t/...-2019-ask-any-question-noob-friendly.4010875/ but it din't work. Can somewone help me?
raphaelgamer981 said:
Hello, i unlocked the bootloader of my motorola one action. And i installed lineage 18.1 official, but i want to lock the bootloader again. i tried locking the bootloader using this help thread https://forum.xda-developers.com/t/...-2019-ask-any-question-noob-friendly.4010875/ but it din't work. Can somewone help me?
Click to expand...
Click to collapse
NEVER lock a phone with custom firmware installed. This usually leads to bootloops.
georg3_ said:
NEVER lock a phone with custom firmware installed. This usually leads to bootloops.
Click to expand...
Click to collapse
No, I Didn't try to lock the bootloader with a custom firmware.
raphaelgamer981 said:
No, I Didn't try to lock the bootloader with a custom firmware.
Click to expand...
Click to collapse
What are the steps you took before relocking the bootloader?
In my experience, relocking the bootloader should be the last thing you do, after you've got a working/bootable stock ROM.
arsradu said:
What are the steps you took before relocking the bootloader? In my experience, relocking the bootloader should be the last thing you do, after you've got a working/bootable stock ROM.
Click to expand...
Click to collapse
So, after i installed the latest stock rom, the device worked normally, but after waiting a while for the oem lock option appear in development options, it din´t show up. so i just gave up and installed lineage 19.1 but if i can i want to lock the bootloader again.
Raphael, I think you might have quoted my post twice, but didn't add an actual answer. Or maybe I'm super blind and I can't see it.
arsradu said:
Raphael, I think you might have quoted my post twice, but didn't add an actual answer. Or maybe I'm super blind and I can't see it.
Click to expand...
Click to collapse
ohh sorry, i tried replying to your post in my ipad 3 and it din´t show up any caracters.
raphaelgamer981 said:
So, after i installed the latest stock rom, the device worked normally, but after waiting a while for the oem lock option appear in development options, it din´t show up. so i just gave up and installed lineage 19.1 but if i can i want to lock the bootloader again.
Click to expand...
Click to collapse
So, the OEM lock/unlock thing comes with a pretty big caveat, and you need to be aware of it: loss of data.
Every time you lock or unlock your bootloader, a wipe data is triggered.
Now, for as far as I know, to lock the bootloader, you need two things:
1. Stock ROM. Don't do this on a custom ROM!
2. following command, in Terminal/Cmd Prompt
fastboot oem lock
Of course, you need to be in fastboot mode, so if you're not, and if you're booted and connected via USB (USB debugging needs to be ON and RSA fingerprinting accepted), do:
adb devices
It should display your device here. This is just to make sure ADB is working properly.
adb reboot bootloader
At this point, the phone should reboot into bootloader, so now you can do the lock command
fastboot oem lock
Data should be erased and, in case it doesn't automatically boot up, you can reboot the phone.
Don't worry about the OEM unlocking option in Developer Options. You just make sure the stock ROM is functional before attempting to relock the bootloader.
arsradu said:
So, the OEM lock/unlock thing comes with a pretty big caveat, and you need to be aware of it: loss of data.
Every time you lock or unlock your bootloader, a wipe data is triggered.
Now, for as far as I know, to lock the bootloader, you need two things:
1. Stock ROM. Don't do this on a custom ROM!
2. following command, in Terminal/Cmd Prompt
fastboot oem lock
Of course, you need to be in fastboot mode, so if you're not, and if you're booted and connected via USB (USB debugging needs to be ON and RSA fingerprinting accepted), do:
adb devices
It should display your device here. This is just to make sure ADB is working properly.
adb reboot bootloader
At this point, the phone should reboot into bootloader, so now you can do the lock command
fastboot oem lock
Data should be erased and, in case it doesn't automatically boot up, you can reboot the phone.
Don't worry about the OEM unlocking option in Developer Options. You just make sure the stock ROM is functional before attempting to relock the bootloader.
Click to expand...
Click to collapse
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
raphaelgamer981 said:
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
Click to expand...
Click to collapse
raphaelgamer981 said:
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
Click to expand...
Click to collapse
But why do you say it didn't work? Do you get an error at any point during the process?
arsradu said:
But why do you say it didn't work? Do you get an error at any point during the process?
Click to expand...
Click to collapse
no, i run the command and it asks for changing the oem lock setting in developer options, i reboot the phone and run through the setup process. Then when i enable developer options and check the oem lock option, it is greyed out.
Is it greyed out in the on or off position? Can you attach a screenshot? I don't remember the operations sequence... But I think the option was automatically switched back to the original position (off) when you lock the bootloader. I could be wrong though. So...when you run the "fastboot oem lock" command, it asks you to....what?
Set the option to on or off? Some screenshots from both the PC, with the message, and the developer options might help to clarify this.
arsradu said:
Is it greyed out in the on or off position? Can you attach a screenshot? I don't remember the operations sequence... But I think the option was automatically switched back to the original position (off) when you lock the bootloader. I could be wrong though. So...when you run the "fastboot oem lock" command, it asks you to....what?
Set the option to on or off? Some screenshots from both the PC, with the message, and the developer options might help to clarify this.
Click to expand...
Click to collapse
it is greyed in the on position, i can´t add a screenshot because i am in lineage 19.1 with root and the option shows up,when i run the command in cmd, it says to me to check the oem lock option in developer options
raphaelgamer981 said:
it is greyed in the on position, i can´t add a screenshot because i am in lineage 19.1 with root and the option shows up,when i run the command in cmd, it says to me to check the oem lock option in developer options
Click to expand...
Click to collapse
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
ok thanks for your help!
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
hello, so i want to lock the bootloader again, how do i install the stock rom back?
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
so after running the fastboot oem lock command, it asked this in the cmd
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.080s]
finished. total time: 0.080s
when i rebooted the phone, it showed the screen saying that the bootloader was unlocked. also i had to re run the command because it was going to erase my phone but that din´t happend, after going to developer options the option was still greyed out.
The last 3 days i've tried some roms from here.first i've unlocked the bootloader in developer menu,then from fastboot with the unlock key provided by motorola website,i've tried different rom,didnt like that i cannot use bank apps.so i went for locking.full reset,adb enable,reboot bootloader,full flash stock rom (last one from Motorola),reboot to check,adb enable, reboot bootloader,run command " fastboot oem lock " once ,it asked for confirmation due to data loss,then run command " fastboot oem lock " once more,then reboot to os.everything went ok,device dont show that was unlocked
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).