Search results

Nop, device bought in Best Buy i NY. So would have to bring it overseas from Europe, because in my country Google doesn't sell devices.

So I did. With the mouse, I was able to sign in Google account and unroll from the beta program. I immediately received OTA with android 9 form June, but after a downgrade, my touchscreen still doesn't work. How the heck is it possible? The screen is connected to the motherboard with only one...

I didn't know that. Thanks for the tip.

It's exactly like You said. I'm able to flash Android Q beta DP4 OTA, but after rebooting I'm stuck at welcome screen and the touchscreen doesn't work. But once, when I removed the SIM card and popped it right back, a popup window for SIM unlock appeared and I was able to input pin (after that...

I know that, but IP rating doesn't mean that your phone is absolutely 100% safe, and maybe this time I got run out of luck. I'm just patiently waiting for beta 5 to be announced and then we'll see.

Maybe someone could upload it's "un-roll" OTA. So I could try to flash it and find out is it software or hardware issue.

The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.

My touchscreen doesn't work, so I can't pass the initial set-up. I just hope Google will release DP5 within a couple of weeks. Or maybe the touchscreen is broken? I guess I have to wait. BTW Now I'm rocking old Lumia 550 on WM10 and it's a real pain in the a.ss without google services.

Because my bootloader is locked I just can't flash system image and so far there's no method to unlock Verizon variant. Only OTA newer than Q beta4.

My Pixel 2XL has locked bootloader and from yesterday I'm having some issues with touchscreen not responding. I spill some coffee on display - just a few drops of cold coffee - but quickly wiped out. The phone was OK, but in the evening the touchscreen stopped working. My first impression was...

Sudenly touchscreen on my Verizon Pixel (Q beta 4) stopped responding so I couldn't even unlock it. I managed manually to boot into recovery mode and tried to re-flash with OTA via ADB. Unfortunately, I got this error while flashing E:signature verification failed E:error: 21 Is it because of...

So You're saying it allows to enable OEM unlocking in a system menu, but in fastboot doesn't work?

I've just bought Pixel 2XL, I was in a hurry because the phone was in mint condition and the price for 128GB variant was super nice - I live in Europe and here, Pixels are quite expensive - and I forgot that it may be Verizon's device. And indeed it's Verizon model. Hopefully, someone will...

I did a factory reset and first few weeks was ok - much better than on nugat. But now after two month of use I see that slowdowns and lags are more common. Especially when the phone gest worm it can literatury stars to crawl. Actually I'm thinking to upgrade to U11

Got update two days ago - Poland

By the time Ultra will get Oreo, Pixel will be running Android P DP3.

Nothing in Poland

Not much change since Android 6.0.1 -SOT on LTE is around 3h. On WiFi it's a bit better - around 4,5h

I'm flashing manualy via fastboot - just system and vendor images. This way I don't need to re-flash kernel or SuperSU