Develop Bugs

Downgrade from 7.1.1

Anyone know if it's possible to downgrade from 7.1.1 so I can run depixel8 and unlock the bootloader?

ashish8 said:
Anyone know if it's possible to downgrade from 7.1.1 so I can run depixel8 and unlock the bootloader?
Click to expand...
Click to collapse
I'm not Verizon but I have some experience and can tell you 100% no doubt that you're stuck if you're on the latest update from Verizon and do not have an unlocked bootloader.
There is no way to go back just to unlock the bootloader.
Sorry.

@CZ Eddie is right. No way to go back with a locked bootloader on a VZW phone running 7.1.1.

CZ Eddie said:
I'm not Verizon but I have some experience and can tell you 100% no doubt that you're stuck if you're on the latest update from Verizon and do not have an unlocked bootloader.
There is no way to go back just to unlock the bootloader.
Sorry.
Click to expand...
Click to collapse
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL

grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Click to expand...
Click to collapse
I'll defer this question to the more Verizon knowledgeable.
My suspicion is you're good to go but I'm only 70% sure about that.

CZ Eddie said:
I'll defer this question to the more Verizon knowledgeable.
My suspicion is you're good to go but I'm only 70% sure about that.
Click to expand...
Click to collapse
grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL
Click to expand...
Click to collapse
It will not re-lock your bootloader. I'm on Verizon with the Verizon variant of the Pixel XL. I took the 7.1.1 update and my bootloader stayed unlocked.

grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL
Click to expand...
Click to collapse
Updates can't lock your bootloader.

thecarp1975 said:
It will not re-lock your bootloader. I'm on Verizon with the Verizon variant of the Pixel XL. I took the 7.1.1 update and my bootloader stayed unlocked.
Click to expand...
Click to collapse
airmaxx23 said:
Updates can't lock your bootloader.
Click to expand...
Click to collapse
Thanks guys! Just wanted to be absolutely sure.
Sent from my Nexus 6 that thinks it's a Pixel XL

is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?

raybonz420 said:
is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?
Click to expand...
Click to collapse
It's not necessarily impossible --nobody seems to have a 100% understanding of what the dual slots are doing on this phone. People who were on custom Roms and rooted have reported successfully taking a stock OTA update without boot looping their phones, although it did wipe out root and the custom recovery. But it's not a great idea to do it the way you suggest and basically hope you get lucky. You would be much better off unlocking the bootloader at least temporarily and flashing a full stock image from Google.

raybonz420 said:
is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?
Click to expand...
Click to collapse
No, because you would not be able to properly sign the file you created so your phone would reject it. The whole Certificate signing thing is what I speak of, if the file isn't signed with a google cert the ota would fail.

TonikJDK said:
No, because you would not be able to properly sign the file you created so your phone would reject it. The whole Certificate signing thing is what I speak of, if the file isn't signed with a google cert the ota would fail.
Click to expand...
Click to collapse
could it be signed using chainfires AVB?

raybonz420 said:
could it be signed using chainfires AVB?
Click to expand...
Click to collapse
No, an ota has to be signed by google.

Pixel 2 XL no operating system fix

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.

OEM Locked, Fastboot Locked, And also no valid OS

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.

nexus 6p Your device is corrupt.itt cant be trusted and may not work prop no recovery

Hi anyone i have buy a nexus 6p.
my device stuck on
your device software cant be checked for corruption.please lock the bootloader
then i lock boot loader and a new massage come
Your device is corrupt.itt cant be trusted and may not work properly
i cant go in recovery i become a bootloop.
i dont now what can i make.i try to flash firmware thats not helped.
please help me

caplagi21 said:
Hi anyone i have buy a nexus 6p.
my device stuck on
your device software cant be checked for corruption.please lock the bootloader
then i lock boot loader and a new massage come
Your device is corrupt.itt cant be trusted and may not work properly
i cant go in recovery i become a bootloop.
i dont now what can i make.i try to flash firmware thats not helped.
please help me
Click to expand...
Click to collapse
Unlock your bootloader and reflash factory image. Also, this is Pixel XL section.

help: can't OEM unlock Pixel 2 XL anymore

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

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

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

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

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

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

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

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

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

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

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

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

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