Develop Bugs

Pixel C is not loaded (not boot)

Hello. I received the OTA update, install it pressed and then I have not loaded tablet.
What should I do?
I Tried:
- wipe data/cache
- charge device
Unlock OEM is not allow (in setting). And I can't unlock bootloader

I dot no my friend but, ota today ? New ota ?
Or it this your first boot on new tablet?
Anyway good luck, wait for pro advice , maybe with PC/cable.

Nothing new Snegovik for your problem ?

xennos said:
Nothing new Snegovik for your problem ?
Click to expand...
Click to collapse
No, I have not solved the problem. The tablet is not loaded, and I can't flast it.
My advice: Allow OEM unlocking the bootloader in the Setting

sad...

I need to find an OTA update on flash recovery. But I can not find it ((

are you using the new unlock command.?
you may also want to update the sdk or whatever adb/fastboot package you use.

dkryder said:
are you using the new unlock command.?
you may also want to update the sdk or whatever adb/fastboot package you use.
Click to expand...
Click to collapse
What you mean?)

Who can get OTA link?
Please see:
http://www.droid-life.com/2014/06/05/download-nexus-ota-url-file/
I want a try flash a OTA from adb sideload)

SnegovikRZN said:
What you mean?)
Click to expand...
Click to collapse
you were saying that pixel c would not unlock and i was asking if you are using the new unlock command. the pixel c uses the nexus 6p unlock
command. not the old one.
it is no longer "fastboot oem unlock"
it is now for pixel c "fastboot flashing unlock"
you need to update your fastboot/adb package you use in case the one you are using does not recognize the new commands.

dkryder said:
you were saying that pixel c would not unlock and i was asking if you are using the new unlock command. the pixel c uses the nexus 6p unlock
command. not the old one.
it is no longer "fastboot oem unlock"
it is now for pixel c "fastboot flashing unlock"
you need to update your fastboot/adb package you use in case the one you are using does not recognize the new commands.
Click to expand...
Click to collapse
Unfortunately this does not work (

Maybe you need to install ADB USB driver manually.
Once fastboot is working .. fastboot flashing unlock

generally that message is shown when the allow oem unlock switch in developer options is not set on.

dkryder said:
generally that message is shown when the allow oem unlock switch in developer options is not set on.
Click to expand...
Click to collapse
yes...
but I can not set it in Setting, because my device is not bott

well, if you still have the device then one possibility is to post your issue to this group,
https://groups.google.com/a/chromium.org/forum/#!forum/chromium-os-discuss
to see if there is a flag in the vbnv that can be set with fwtool. [similar to fastboot issue] to get it to boot.

Pixel C bootloop[
SnegovikRZN said:
yes...
but I can not set it in Setting, because my device is not bott
Click to expand...
Click to collapse
Even i am facing the same problem with my Pixel C device. is there any way to unlock the boatloader ? if it is not set in Settings. or only option left is replacement from google?

vtirugudu said:
Even i am facing the same problem with my Pixel C device. is there any way to unlock the boatloader ? if it is not set in Settings. or only option left is replacement from google?
Click to expand...
Click to collapse
Yes you can unlock same as you would a Nexus device.

bill3508 said:
Yes you can unlock same as you would a Nexus device.
Click to expand...
Click to collapse
How to unlock the device?

HI there,
I get same problem, not possible to active Debug & Dev on android setting, because the tablet dosnt load to android !
I tried with Nexus Root Toolkit no success also

replacement device unlocking question

So, i broke my direct from google pixel xl, that was unlocked. I had insurance through verizon and they sent me a new one. Now, i know the verizon versions are locked, which is what i didn;t want, but i had no choice through asurion. The phone i received is on NHG47L which isn't the verizon version, but the OEM unlock is still grayed out. can anyone tell me why i can't unlock even though this seems to be a google fi/tmobile build?
i have no put a sim in it yet, i've only connected it to wifi. i'm waiting till i have a firm answer one way or the other.

@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3

cam30era said:
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
Click to expand...
Click to collapse
i did connect it to wifi, it did not change the OEM unlock option.

@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.

cam30era said:
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
Click to expand...
Click to collapse
Would flashing a factory image do anything, maybe a previous version?

Legacystar said:
Would flashing a factory image do anything, maybe a previous version?
Click to expand...
Click to collapse
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.

cam30era said:
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
Click to expand...
Click to collapse
so, if the bootloader was never unlockable, how would one change the software version?

Legacystar said:
so, if the bootloader was never unlockable, how would one change the software version?
Click to expand...
Click to collapse
ADB sideload. Or wait for OTA to be pushed.

cam30era said:
ADB sideload. Or wait for OTA to be pushed.
Click to expand...
Click to collapse
i meant, how did this phone's software get changed?

Legacystar said:
i meant, how did this phone's software get changed?
Click to expand...
Click to collapse
The firmware is downloaded based on the sim in the device. Not where it was purchased

pcriz said:
The firmware is downloaded based on the sim in the device. Not where it was purchased
Click to expand...
Click to collapse
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?

mattwheat said:
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
Click to expand...
Click to collapse
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.

pcriz said:
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
Click to expand...
Click to collapse
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.

mattwheat said:
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
Click to expand...
Click to collapse
Verizon isn't the only carrier to lock it down. Google has never been implicitly root friendly, also I'm sure a partner ship with verizon is to their benefit. Like getting their foot in the door to a wider market. The trade off is the bootloader.

[SOLVED] Locked down bootloader?

EDIT: Solution: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?

frap129 said:
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?
Click to expand...
Click to collapse
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Sent from my MHA-L29 using Tapatalk

danon.brown said:
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Click to expand...
Click to collapse
I already tried that command as I said in my post (unless there's one other than "fastboot flashing unlock" that I'm not seeing in the essential forum)

Can you see your phone with fastboot devices?
Sent from my MHA-L29 using Tapatalk

A few others with the phone have reported the same issue in the "rooting" thread...not sure what's going on!

I had the essential phone and had to get a more current Version of adb.
Sent from my MHA-L29 using Tapatalk

did you enable developer settings and see if there is a setting to allow OEM unlock?

Code:
fastboot flashing unlock
will unlock it

When I first booted the phone and enabled USB debugging, the OEM Unlock was greyed out. I had to put my sim card in for it to allow me to enable it. Then using the fastboot flashing unlock worked from bootloader.

fastboot flashing unlock worked for me.

Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over

@frap129 hope you get it sorted. Glad to see you got a 2 XL as well! Would love to eventually see Carbon and Electron on the 2 XL. Have been missing them since I RMA'd my 6P for an XL. :good:

What is the point if the stock android phone has locked bootloader!
I miss NEXUS phones

This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..

Thanks for all the responses, I guess it's just my fastboot version. I have the latest that's on the aur, but I'll try manually downloading from Google's site.

I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.

cryppie said:
This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..
Click to expand...
Click to collapse
Disagreed. This was not necessary with the OG Pixel.
Further, I think most people here know that the chances of unlocking a Verizon bought Pixel are slim to none.

dirtyfingers said:
I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.
Click to expand...
Click to collapse
Ive been using adb reboot the whole time and can't get it to work, thanks for the heads up!

UPDATE: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Sorry for the double post, I just wanted to make sure anyone following this with the same issue gets the solution.

cwalker0906 said:
Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over
Click to expand...
Click to collapse
You could have also used the sdk manager to update the platform-tools.

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.