Related
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Fastboot flashing lock? Or oem lock?
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
Fastboot flashing lock? Or oem lock?
Click to expand...
Click to collapse
It's that simple? Just run the fast lock command?
shibbnasty said:
It's that simple? Just run the fast lock command?
Click to expand...
Click to collapse
I think lol it's been awhile since I locked a phone
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
I think lol it's been awhile since I locked a phone
Click to expand...
Click to collapse
I guess I should have mentioned as well it's a Verizon pixel xl and I had to use depixel8 to unlock it
shibbnasty said:
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Click to expand...
Click to collapse
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
lyall29 said:
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
Click to expand...
Click to collapse
All I have done is unlock it. I have not flashed any kernels or mods or anything.
shibbnasty said:
All I have done is unlock it. I have not flashed any kernels or mods or anything.
Click to expand...
Click to collapse
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
lyall29 said:
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
Click to expand...
Click to collapse
Thank you very much!
@shibbnasty. Actually, relocking the bootloader may not wipe data. I can't remember. Let me know if it does or not.
Yes it does.
Rank N00b here... just getting that out of the way.
Device: Verizon Pixel XL
Build: NDE63X
Bootloader: unlocked via dePixel8 (done after Nov update)
So the phone is stock and I'm not really keen on modding right now. I don't want to use a alpha build of TWRP and SuperSU seems to be in flux too. These aren't criticisms by the way; I realize this a very new handset and those kinds of tools take time to develop. Nothing happens overnight.
So, anyway, my phone is currently unlocked and I'm wondering if I'm not better off relocking it? As a stock unit, it should still get OTA's, right? Like I said, total n00b here...
@loaba,
There's absolutely no reason to relock your bootloader, unless you are annoyed by the Google bootloader unlock warning during boot, or if you are planning on returning it or selling it. Otherwise, leave it unlocked. Gives you much greater flexibility to recover if something goes wrong.
@cam30era,
Thanks for the reassurance.
loaba said:
@cam30era,
Thanks for the reassurance.
Click to expand...
Click to collapse
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
michaelbsheldon said:
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
Click to expand...
Click to collapse
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
loaba said:
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
Click to expand...
Click to collapse
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
michaelbsheldon said:
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
Click to expand...
Click to collapse
About the OTA's - that was my big concern for now. Cool.
OP - thread derailed... sorry, man.
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Khanusma said:
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Click to expand...
Click to collapse
Most of the custom kernels fix that. Root is the hard one to hide.
Since I have enrolled my Pixel XL in Android beta program, I have received Oreo 8.1 update OTA last night. After the update, OEM unlock in developer options does not work. Anyone have the same issue ? Thanks
Fine here
netma2k said:
Since I have enrolled my Pixel XL in Android beta program, I have received Oreo 8.1 update OTA last night. After the update, OEM unlock in developer options does not work. Anyone have the same issue ? Thanks
Click to expand...
Click to collapse
Same problem the button is gray and says bootloader already unlocked.
That is normal if you are already unlocked, and it was like that before 8.1. It won't un-gray until you issue the fastboot command to relock it. It stops you from sliding while unlocked and creating a situation where you are bricked.
TonikJDK said:
That is normal if you are already unlocked, and it was like that before 8.1. It won't un-gray until you issue the fastboot command to relock it. It stops you from sliding while unlocked and creating a situation where you are bricked.
Click to expand...
Click to collapse
But I never unlocked my boot loader and still it appears to be grayed out. Thanks for your reply.
netma2k said:
But I never unlocked my boot loader and still it appears to be grayed out. Thanks for your reply.
Click to expand...
Click to collapse
Is your device a "Google phone" or is it through a carrier?
DR3W5K1 said:
Is your device a "Google phone" or is it through a carrier?
Click to expand...
Click to collapse
Mine is an unlocked phone purchased from Google Store and never buy phones from Carrier. Thanks for asking
netma2k said:
Mine is an unlocked phone purchased from Google Store and never buy phones from Carrier. Thanks for asking
Click to expand...
Click to collapse
Is it stuck in the locked position or the unlocked position?
Stuck in locked position
TonikJDK said:
Is it stuck in the locked position or the unlocked position?
Click to expand...
Click to collapse
Stuck in locked position
netma2k said:
Stuck in locked position
Click to expand...
Click to collapse
I would unenroll, which will wipe your phone and then hit the slider and leave it there. It might be a bug that will be fixed later but I wouldn't chance it if I wanted to unlock later on.
netma2k said:
Stuck in locked position
Click to expand...
Click to collapse
That is very strange
You are using beta software.
Google doesn't want you to lock the bootloader when using beta software.
Go back to 8.0 and see what happens.
Sent from my Pixel C using Tapatalk
Then, could I downgrade safely to Android 6??
Navalon said:
Then, could I downgrade safely to Android 6??
Click to expand...
Click to collapse
If you can pull it off, let us know!
Sent from my Pixel C using Tapatalk
pkelly517 said:
If you can pull it off, let us know!
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
If the bootloader is unlock, the rollback protection will be desactivated. Not?
I can confirm on mine that OEM unlock is also grayed out on 8.1 DP. Also grayed out in the screenshots on Android Police.
Sent from my Pixel using Tapatalk
Navalon said:
If the bootloader is unlock, the rollback protection will be desactivated. Not?
Click to expand...
Click to collapse
I think the joke was, this device never came with Marshmallow. They were saying if you can get Marshmallow to run on this, then let us know.
Unlocked rooted 8.0 not enrolled in beta.
My unlock button is Not grayed out. Wish it was as it would be easy to accidentally tick the button. Maybe 8.1 fixed this?
Born<ICs said:
Unlocked rooted 8.0 not enrolled in beta.
My unlock button is Not grayed out. Wish it was as it would be easy to accidentally tick the button. Maybe 8.1 fixed this?
Click to expand...
Click to collapse
An accidental tick won't hurt you, you still have to hit it with fastboot and issue the command.
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pixel-2-xl/development/tool-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
oliverfongftw said:
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
Click to expand...
Click to collapse
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
If you have the stock recovery and can boot into it you can adb sideload the most recent ota zip.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
ram4ufriends said:
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
Click to expand...
Click to collapse
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
You can get the bootloader lock status simply by booting into the bootloader. Locked or unlocked? You don't "think" it has a working recovery is not good enough to help you. If it does have a stable recovery, you can flash the OTA. If it does not and the bootloader is locked you are S.O.L. and the phone is dead. Follow this video and let us know.
oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
If you can hold down volume and hit power to get into bootloader and choose Recovery, you can fix this phone.
Go here: read instructions at top. You will be booting to bootloader, then to recovery, then choose Apply Update from ADB.
Then give adb OTA command as described. Don't skip or modify any step.
https://developers.google.com/android/ota
I am in this exact same situation. Did you ever figure it out? Or did anyone figure it out?
Got this exact problem with a locked bootloader and no recovery, any solution?
0x0null said:
Got this exact problem with a locked bootloader and no recovery, any solution?
Click to expand...
Click to collapse
How did you lose the recovery with a locked bootloader?
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
How did you lose the recovery with a locked bootloader?
Click to expand...
Click to collapse
Got it that way thinking i could use recovery to recover the phone
0x0null said:
Got it that way thinking i could use recovery to recover the phone
Click to expand...
Click to collapse
It came without a recovery.
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
mookiexl said:
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
Click to expand...
Click to collapse
Locked bootloader wont let me use the script.
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Strephon Alkhalikoi said:
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Click to expand...
Click to collapse
Yea, your on point. Only edl firehose may save me
0x0null said:
Locked bootloader wont let me use the script.
Click to expand...
Click to collapse
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
mookiexl said:
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
Click to expand...
Click to collapse
It Unlocks only if 'oem unlock' is engaged from the booted system.
0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Which is exactly why it should never be in the locked position...
Sent from my Pixel 2 XL using XDA Labs
0x0null said:
Yea, your on point. Only edl firehose may save me
Click to expand...
Click to collapse
and save me to. I try to find firhose for my pixel 2xl but I didn't find it. Hope someone can provide QFIL Firmware to save as.
Sent from my MI 9 using Tapatalk
0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Did you try? I used it with no 0S installed so oem unlock couldnt have been engaged.
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
You may have to call Google. I think that some versions sold/purchased in the EU have a 6 month waiting period before they can get an unlocking code ?
sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
If it originally came from EE it is locked, but EE can unlock it. Did you factory reset it? That also was a bug and the reset cleared it.
Badger50 said:
You may have to call Google. I think that some versions sold/purchased in the EU have a 6 month waiting period before they can get an unlocking code ?
Click to expand...
Click to collapse
The device is from usa
sabi95190 said:
The device is from usa
Click to expand...
Click to collapse
Factory reset it then connect to the internet. Early on Google shipped a bunch that had this problem. The fixed it on their end but it requires a fact reset.
TonikJDK said:
Factory reset it then connect to the internet. Early on Google shipped a bunch that had this problem. The fixed it on their end but it requires a fact reset.
Click to expand...
Click to collapse
I reset it from the settings?
sabi95190 said:
I reset it from the settings?
Click to expand...
Click to collapse
Yep...settings/system/reset options :good:
Badger50 said:
Yep...settings/system/reset options :good:
Click to expand...
Click to collapse
Done but nothing change
sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
Just to be clear, being SIM unlocked and bootloader unlocked are two completely different things. Are you sure the advertising for it being "unlocked" wasn't referring to the SIM status?
Namolas said:
Just to be clear, being SIM unlocked and bootloader unlocked are two completely different things. Are you sure the advertising for it being "unlocked" wasn't referring to the SIM status?
Click to expand...
Click to collapse
Yes I knew that but I thought that the Google Version have a unlockable bootloader...
sabi95190 said:
Yes I knew that but I thought that the Google Version have a unlockable bootloader...
Click to expand...
Click to collapse
Google version does have an unlockable bootloader. The question is are you 100% positive it's the Google version you bought/received and not the Verizon version?
Namolas said:
Google version does have an unlockable bootloader. The question is are you 100% positive it's the Google version you bought/received and not the Verizon version?
Click to expand...
Click to collapse
I looked for the cid of the phone and it appears that the phone isn't from Verizon. And the seller also told me that he bought the phone from Google store
It's likely the previous owner tried to unlock the bootloader and failed. By the looks of things the only current way to fix it is RMA to Google.
https://issuetracker.google.com/issues/68897739
ImWarped said:
It's likely the previous owner tried to unlock the bootloader and failed. By the looks of things the only current way to fix it is RMA to Google.
https://issuetracker.google.com/issues/68897739
Click to expand...
Click to collapse
I don't think it will be possible I'm not original owner
sabi95190 said:
I don't think it will be possible I'm not original owner
Click to expand...
Click to collapse
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.
uicnren said:
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.
Click to expand...
Click to collapse
delete
uicnren said:
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.
Click to expand...
Click to collapse
It didn't work
Edit: I verified the IMEI in a website and it shows as a verizon device...
I got replacement pixel 2 xl on android 10 security patch October 6/2019 I tried everything from fastboot I get error saying locked I don't know what carrier I checked imei and meid all good its networked unlocked I even went into safe mode and removed guest rebooted nothing …...I hate android 10 my signal sucks compared to android 9
oem unlock bootloader is grayed out
fryedmonk911 said:
I got replacement pixel 2 xl on android 10 security patch October 6/2019 I tried everything from fastboot I get error saying locked I don't know what carrier I checked imei and meid all good its networked unlocked I even went into safe mode and removed guest rebooted nothing …...I hate android 10 my signal sucks compared to android 9
oem unlock bootloader is grayed out
Click to expand...
Click to collapse
Sounds like you got a Verizon variant device instead of a google one. If you can't toggle OEM unlocking from the get go, you really can't unlock the bootloader. Sorry man
Badger50 said:
Sounds like you got a Verizon variant device instead of a google one. If you can't toggle OEM unlocking from the get go, you really can't unlock the bootloader. Sorry man
Click to expand...
Click to collapse
I'm Canadian and I got three pixel 2 refurbs before giving up. There's a huge support thread about how all refurb bootloaders cannot be unlocked. Not sure why. I had a slot unbootable error, this was on my non xl variant.
crixley said:
I'm Canadian and I got three pixel 2 refurbs before giving up. There's a huge support thread about how all refurb bootloaders cannot be unlocked. Not sure why. I had a slot unbootable error, this was on my non xl variant.
Click to expand...
Click to collapse
thank you all for responding , I did contact google yesterday and was told all pixel devices that come from google are fully unlock they told me to call Verizon up I did last night and it is one of there phones I am sending it back to the seller and explaining to him what I want .were I live we have a hybrid tower and for some reason android 10 sucks compard to 9
Mine have oem unlock option but can't unlock the bootloader. tried all the commands but won't let me unlock the bootloader. any help will be greatly appreciated. running android 10
sinkoo1979 said:
Mine have oem unlock option but can't unlock the bootloader. tried all the commands but won't let me unlock the bootloader. any help will be greatly appreciated. running android 10
Click to expand...
Click to collapse
Are platform-tools up to date?
Are you using a USB a to USB C cable?
Does your phone get recognized when you type in fastboot devices?
Are you using power shell?
Is USB debugging turned on?
Badger50 said:
Are platform-tools up to date?
Are you using a USB a to USB C cable?
Does your phone get recognized when you type in fastboot devices?
Are you using power shell?
Is USB debugging turned on?
Click to expand...
Click to collapse
didn't check
yes
yes
yes
yes
sinkoo1979 said:
didn't check
yes
yes
yes
yes
Click to expand...
Click to collapse
Check your platform-tools, and don't use power shell commands. Open your command prompt directly on your platform-tools folder.
Badger50 said:
Check your platform-tools, and don't use power shell commands. Open your command prompt directly on your platform-tools folder.
Click to expand...
Click to collapse
will try. Thank you
Update: unlocked bootloader with minimal adb and fastboot.
sinkoo1979 said:
will try. Thank you
Update: unlocked bootloader with minimal adb and fastboot.
Click to expand...
Click to collapse
Congrats :good: However, I would recommend getting rid of minimal adb and just use platform-tools going forward. Minimal adb can cause problems when it comes to fastbooting factory images :good:
fryedmonk911 said:
thank you all for responding , I did contact google yesterday and was told all pixel devices that come from google are fully unlock they told me to call Verizon up I did last night and it is one of there phones I am sending it back to the seller and explaining to him what I want .were I live we have a hybrid tower and for some reason android 10 sucks compard to 9
Click to expand...
Click to collapse
I'm guessing when Google told you that all phones coming from Google were fully unlocked they were talking about being carrier unlocked instead of having the capability of unlocking the bootloader.
When buying a LG phone (e.g. Pixel 2 XL) it's good to have the seller run an IMEI check and post the screenshot for you from this site... https://www.imeipro.info/check_lg.html
Under they buyer name you can tell if you are getting a Google or Verizon variant.
Badger50 said:
Congrats :good: However, I would recommend getting rid of minimal adb and just use platform-tools going forward. Minimal adb can cause problems when it comes to fastbooting factory images :good:
Click to expand...
Click to collapse
Since all Minimal ADB and Fastboot does is bundle up the platform tools and add a Windows executable stub to them, removing it isn't a bad idea. An alternative - that I took - would be to update the platform tools in the Minimal ADB folder with the latest from Google.