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.
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.
I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?
enginuity2 said:
I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?
Click to expand...
Click to collapse
Fastboot flashing lock.
toknitup420 said:
Fastboot flashing lock.
Click to expand...
Click to collapse
does this work? anyone tried?
mgear356 said:
does this work? anyone tried?
Click to expand...
Click to collapse
LOL of course it works, the command is directly from Google.
That easy! Here are the instructions from Google:
https://developers.google.com/android/images
Tells you the commands to unlock, flash stock rom and re-lock the bootloader...
This ain't no iPhone, son! Lol
You are allowed to do this stuff. All of the software to lock and unlock are provided by Google...
Sent from my [device_name] using XDA-Developers Legacy app
slaydog said:
That easy! Here are the instructions from Google:
https://developers.google.com/android/images
Tells you the commands to unlock, flash stock rom and re-lock the bootloader...
This ain't no iPhone, son! Lol
You are allowed to do this stuff. All of the software to lock and unlock are provided by Google...
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Cheers mate.. Was worried as my last phone was 6p.
My first pixel lol..
If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?
vibrantliker said:
If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?
Click to expand...
Click to collapse
Why you returning the phone in the first place?
Jiggs82 said:
Why you returning the phone in the first place?
Click to expand...
Click to collapse
Returning it to Google and re buying elsewhere for at least $200 less.
vibrantliker said:
If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?
Click to expand...
Click to collapse
when you lock or unlock, it wipes the phone.
uicnren said:
when you lock or unlock, it wipes the phone.
Click to expand...
Click to collapse
Just that I read in a couple of places when re locking some have had a "no os installed" result.
enginuity2 said:
I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?
Click to expand...
Click to collapse
You don't need to lock bootloader to return..I returned multiple devices without locking
vibrantliker said:
Just that I read in a couple of places when re locking some have had a "no os installed" result.
Click to expand...
Click to collapse
simply flash both partitions first then.
Just wipe it and ship it. Google will only inspect it for physical abuse and water damage. The don't care if it's unlocked. It Google, the sell us unlocked phones. I too have sent them back unlocked as have many others.
I just flashed the latest factory image then did a factory reset before I was going to re lock the bootloader. Now the oem unlock option on my phone is greyed out and adb/fastboot fives me errors trying to fastboot oem lock or fastboot flashing lock.
vibrantliker said:
I just flashed the latest factory image then did a factory reset before I was going to re lock the bootloader. Now the oem unlock option on my phone is greyed out and adb/fastboot fives me errors trying to fastboot oem lock or fastboot flashing lock.
Click to expand...
Click to collapse
The slider will stay gray until the fastboot commands relock it. What are the errors you are getting. Exact wording please.
Really, just ship it as is.
TonikJDK said:
The slider will stay gray until the fastboot commands relock it. What are the errors you are getting. Exact wording please.
Really, just ship it as is.
Click to expand...
Click to collapse
I'll try again tomorrow and get back.
You said earlier they just check for physical damage. Don't they turn on the phone?
They shouldn't care when the locked boot loader screen shows at boot?
vibrantliker said:
I'll try again tomorrow and get back.
You said earlier they just check for physical damage. Don't they turn on the phone?
They shouldn't care when the locked boot loader screen shows at boot?
Click to expand...
Click to collapse
I sent one back with the bootloader unlocked they don't care. I'd make damn sure it's completely stock before you relock it maybe Flash the factory image to both slots just to be sure.
mac796 said:
I sent one back with the bootloader unlocked they don't care. I'd make damn sure it's completely stock before you relock it maybe Flash the factory image to both slots just to be sure.
Click to expand...
Click to collapse
It is completely stock, but what does that mean
"Flash the image to both slots"?
vibrantliker said:
It is completely stock, but what does that mean
"Flash the image to both slots"?
Click to expand...
Click to collapse
Go to Google's factory image page download January's image and do the flash all to slot a. Then change to slot B.
Fastboot --set-active=b then flash all to slot B. Probably Overkill but you'll for sure be stock. Then issue you're relock command to both critical and the regular bootloader one. For one you need to make sure your fastboot is current if it's not up to date you're probably going to have problems.
Edit. I would just send it back the way it is
My pixel 2 xl got real hard brick, and I need some method to restore.
I tried LG UP with download mode, (Connect USB with volume +), It is impossible cause i could not find tot or kdz firmware for Pixel 2 XL.
Any help? T^T,,,,,
And also can you suggest me where can i buy pixel 2 xl's motherboard/logic board?
Contact Google if you have the packaging unless you bought it second hand. It's under warranty
Sent from my SM-G965U using Tapatalk
tylenol97 said:
My pixel 2 xl got real hard brick, and I need some method to restore.
I tried LG UP with download mode, (Connect USB with volume +), It is impossible cause i could not find tot or kdz firmware for Pixel 2 XL.
Any help? T^T,,,,,
And also can you suggest me where can i buy pixel 2 xl's motherboard/logic board?
Click to expand...
Click to collapse
Just outa curiosity, was your bootloader locked or unlocked? Also, can you get into stock recovery and bootloader mode??
Badger50 said:
Just outa curiosity, was your bootloader locked or unlocked? Also, can you get into stock recovery and bootloader mode??
Click to expand...
Click to collapse
Thank you for replying.
Everything got locked.. Bootloader locked of course, even OEM locked.
If i can boot into recovery, I can recover with OTA. and everything will be ok..
but OS has not installed, so It shows "Can't find valid operating system". (Status is same just like as Google's "NO OS on Pixel 2 XL" mistake)
I'm stupidest person in 2018. :crying::crying::crying:
tylenol97 said:
Thank you for replying.
Everything got locked.. Bootloader locked of course, even OEM locked.
If i can boot into recovery, I can recover with OTA. and everything will be ok..
but OS has not installed, so It shows "Can't find valid operating system". (Status is same just like as Google's "NO OS on Pixel 2 XL" mistake)
I'm stupidest person in 2018. :crying::crying::crying:
Click to expand...
Click to collapse
Can you get into fastboot? Power and volume down?
tylenol97 said:
Thank you for replying.
Everything got locked.. Bootloader locked of course, even OEM locked.
If i can boot into recovery, I can recover with OTA. and everything will be ok..
but OS has not installed, so It shows "Can't find valid operating system". (Status is same just like as Google's "NO OS on Pixel 2 XL" mistake)
I'm stupidest person in 2018. :crying::crying::crying:
Click to expand...
Click to collapse
Whatever you did doesn't make you stupid my friend. I've bricked 2 phones myself on my android learning experience. If you can get into recovery, you should be able to side load an OTA. Then again, I bet you already tried that.
Badger50 said:
Whatever you did doesn't make you stupid my friend. I've bricked 2 phones myself on my android learning experience. If you can get into recovery, you should be able to side load an OTA. Then again, I bet you already tried that.
Click to expand...
Click to collapse
Thanks.. but i can not get into recovery mode. It just say 'Can't find valid os'
I should go to LG tomorrow.
Thank you for replying!
Goog1e Phone said:
Can you get into fastboot? Power and volume down?
Click to expand...
Click to collapse
Thank you for reply
I can get into fastboot, but oem locked, bootloader locked, so I can't do anything with fastboot. just reboot command works well.
tylenol97 said:
Thank you for reply
I can get into fastboot, but oem locked, bootloader locked, so I can't do anything with fastboot. just reboot command works well.
Click to expand...
Click to collapse
Then you should at least try deuces recovery script. Who knows, it might work :good:
Or you can go to the proper people, aka google, stop doing whatever shady mess your doing and be careful next time.
Sent from my SM-G965U using Tapatalk
tylenol97 said:
Thank you for reply
I can get into fastboot, but oem locked, bootloader locked, so I can't do anything with fastboot. just reboot command works well.
Click to expand...
Click to collapse
..
tylenol97 said:
Thank you for reply
I can get into fastboot, but oem locked, bootloader locked, so I can't do anything with fastboot. just reboot command works well.
Click to expand...
Click to collapse
You can load the factory image from Google regardless if you're still OEM locked or not.
It's a signed image from Google... Signed images are accepted by the phone always.
The point of unlocking is to use unsigned images from developers other than google.
tylenol97 said:
My pixel 2 xl got real hard brick, and I need some method to restore.
I tried LG UP with download mode, (Connect USB with volume +), It is impossible cause i could not find tot or kdz firmware for Pixel 2 XL.
Any help? T^T,,,,,
And also can you suggest me where can i buy pixel 2 xl's motherboard/logic board?
Click to expand...
Click to collapse
I did the same thing and returned and got new device from Google
ImWarped said:
You can load the factory image from Google regardless if you're still OEM locked or not.
It's a signed image from Google... Signed images are accepted by the phone always.
The point of unlocking is to use unsigned images from developers other than google.
Click to expand...
Click to collapse
No. Even google said if user want to flash factory images, whatever it is stock & signed, user should unlock OEM and even bootloader. (Reference : https://developers.google.com/android/images)
I did several times, it didn't work without it.
I sent LG, because i live in korea.
It will be fine.
Thanks!
tylenol97 said:
No. Even google said if user want to flash factory images, whatever it is stock & signed, user should unlock OEM and even bootloader. (Reference : https://developers.google.com/android/images)
I did several times, it didn't work without it.
I sent LG, because i live in korea.
It will be fine.
Thanks!
Click to expand...
Click to collapse
Hi, I also meet the same problem like you. How ur phone right now and how u figure out the solution? Thank.
I can not OEM unlock my Pixel 2 XL anymore. It is running a custom ROM that is not being updated anymore. In the developer settings, "OEM unlocking" is gray, and it says "Connect to the Internet or contact your carrier". The phone is connected to the internet and the internet is working flawlessly. This is NOT a Verizon version and there already IS a custom ROM on it, so it's been unlocked in the past.
I have tried to factory reset numerous times, and the option still did not become available.
What else could I try?
oUkcpV9ykzUC said:
I can not OEM unlock my Pixel 2 XL anymore. It is running a custom ROM that is not being updated anymore. In the developer settings, "OEM unlocking" is gray, and it says "Connect to the Internet or contact your carrier". The phone is connected to the internet and the internet is working flawlessly. This is NOT a Verizon version and there already IS a custom ROM on it, so it's been unlocked in the past.
I have tried to factory reset numerous times, and the option still did not become available.
What else could I try?
Click to expand...
Click to collapse
Is it grayed out in the on or off position? Which is not uncommon on custom roms.
Do you have access to the the ROM if you need to reinstall it?
I would backup everything you can using twrp make a full and then also make sure you have boot.img backed up then try flashing factory image or whatever ROM you want to move to if you have an issue just switch back if it will take at all
Sent from my Pixel 2 XL using Tapatalk
So you unlocked it and flashed a custom ROM and then reinstalled the stock recovery and locked it like that for Android pay? Maybe the custom ROM was based off of a Verizon install so you phone thinks it's a Verizon phone now. You may be out of luck.
nukeruss said:
Maybe the custom ROM was based off of a Verizon install so you phone thinks it's a Verizon phone now. You may be out of luck.
Click to expand...
Click to collapse
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
sublimaze said:
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
Click to expand...
Click to collapse
Forgot to mention, this is NOT a ROM that uses TWRP, but its own recovery. Maybe I'm not understanding you right, but how do I flash a factory image if I can't OEM unlock?
gjkrisa said:
Do you have access to the the ROM if you need to reinstall it?
I would backup everything you can using twrp make a full and then also make sure you have boot.img backed up then try flashing factory image or whatever ROM you want to move to if you have an issue just switch back if it will take at all
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's not a ROM that uses TWRP but its own recovery. Not sure what you mean by "if you have an issue just switch back if it will take at all".
sublimaze said:
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
Click to expand...
Click to collapse
Flashing the factory image using Deuce's script will fix this.
Don't skip any steps.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Mine is grayed out with a notification underneath telling me the bootloader is already unlocked.
Larzzzz82 said:
Mine is grayed out with a notification underneath telling me the bootloader is already unlocked.
Click to expand...
Click to collapse
What do you get when you run...fastboot oem device-info...?
Is it grayed out in the on or off position?
Grayed off. Can't fastboot now but will when i can. This is not the vzw version and was unlocked within 10 minutes of unboxing it. The option didn't become available until it connected to a network...
Have you tried adb reboot fastboot?
Larzzzz82 said:
Grayed off. Can't fastboot now but will when i can. This is not the vzw version and was unlocked within 10 minutes of unboxing it. The option didn't become available until it connected to a network...
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
gjkrisa said:
Have you tried adb reboot fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I was no where near a computer... Is that a valid adb command? I go adb reboot- bootloader then fastboot devices before i do anything else.
---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------
The get device-info returned:
Verity mode: true
Device unlocked: true
Charger screen enabled: true