After unlocking the Bootloader on my Pixel 2 XL (Android 8.1 DP1) my Play Store Device Certification as "Uncertified", is that normal??
Also, I've seen thread about the screen's Blue shifts and comparing build date but has anyone compared the Black smudge effect?
My RMAed Pixel2 XL (Build date 10/18) has it really bad. Is everyone experiencing this? Is it just part of the POLED Tech?
Lastly, has Android 8.1 DP1 been buggy for anyone? It's constantly crashing the Google app and sometimes doesn't register taps on my screen (across all apps different locations)
I've Factory resetted twice this week.
Thanks!
I unlocked my Pixel and this shows whenever I turn my phone on/off. I've never owned a Pixel or Nexus, is this normal?
rank78 said:
I unlocked my Pixel and this shows whenever I turn my phone on/off. I've never owned a Pixel or Nexus, is this normal?
Click to expand...
Click to collapse
Yes, that is normal. You need not worry.
Also, it cannot be removed. It will always show if you have an unlocked bl
You'll need to get used to that message...
Lawlrus said:
Also, it cannot be removed. It will always show if you have an unlocked bl
Click to expand...
Click to collapse
galaxys said:
You'll need to get used to that message...
Click to expand...
Click to collapse
Dammit, it's annoying as hell. Thanks guys.
Related
So I got a Verizon Pixel XL NDE63P and unlocked the bootloader. I then updated to NMF26U (Stock Image). If I lock the bootloader will it get stuck since it isn't a verizon Image? or will it be ok since it is a Pixel stock image? I'm trying to get rid of the ugly corruption message.
message will always be there. Do not relock the bootloader my friend.
Alright thanks.
Quite a few people here that tried it and now have completely bricked phones.
I'll just leave it alone then....
This may sound strange but if it really bothers you then you could see if someone on here with a locked vzw device is interested in a swap. It would require some trust but could be mutually beneficial.
efaden said:
So I got a Verizon Pixel XL NDE63P and unlocked the bootloader. I then updated to NMF26U (Stock Image). If I lock the bootloader will it get stuck since it isn't a verizon Image? or will it be ok since it is a Pixel stock image? I'm trying to get rid of the ugly corruption message.
Click to expand...
Click to collapse
There is absolutely no difference between the software you have and the software that's on a google bought pixel. They have been releasing the same exact build for both devices. There is no difference between the two. However if you ever lock your bootloader you will never be able to unlock again.
cntryby429 said:
This may sound strange but if it really bothers you then you could see if someone on here with a locked vzw device is interested in a swap. It would require some trust but could be mutually beneficial.
Click to expand...
Click to collapse
I want it unlocked. I just don't want the ugly screen.... but I can deal with it.
Don't mess with it.
One day we may have the ability to alter this screen. But people aren't working on that since it's so minor.
The Pixel XL shows that screen for less than 10 seconds. The Pixel C is over 30 seconds. I can live with 10 seconds.
Mike02z said:
The Pixel XL shows that screen for less than 10 seconds. The Pixel C is over 30 seconds. I can live with 10 seconds.
Click to expand...
Click to collapse
I consider it a "Badge of Honor".
Hey all,
I recently had to get my pixel replaced from Google and they sent me a refurbished one about a week ago. I updated to the July security update yesterday and over night my battery drained from 43% to 3% when I woke up. Took a shower and came back 15 mins later to find my pixel completely dead and wouldn't take a charge or anything. Weird thing is, my computer will find it in fastboot, but won't let me flash anything because it isn't the correct device even though I downloaded the factory images for the Verizon pixel XL, which I have. I'm just curious if anyone else experienced something like this after the update or if I got a bad refurb. Either way it's on its way back to Google now. I'm just curious before updating my broken phone to the new update
I'm not sure what you mean by it wasn't the correct device. If you were able to unlock the bootloader then Google didn't send you a Verizon Pixel XL which might be why you couldn't flash the Verizon image on your phone.
jhs39 said:
I'm not sure what you mean by it wasn't the correct device. If you were able to unlock the bootloader then Google didn't send you a Verizon Pixel XL which might be why you couldn't flash the Verizon image on your phone.
Click to expand...
Click to collapse
You can flash any of the pixel XL images to a pixel XL device. Whether it is Google or Verizon version makes no difference. Mines Verizon version running the T-Mobile build.
toknitup420 said:
You can flash any of the pixel XL images to a pixel XL device. Whether it is Google or Verizon version makes no difference. Mines Verizon version running the T-Mobile build.
Click to expand...
Click to collapse
I didn't know that. I thought maybe the build had to be the same variant that was originally shipped with the phone. Wonder what was meant by wasn't the correct device then?
jhs39 said:
I didn't know that. I thought maybe the build had to be the same variant that was originally shipped with the phone. Wonder what was meant by wasn't the correct device then?
Click to expand...
Click to collapse
I don't think his device was actually in the bootloader. Which could explain the incorrect device issue. I think he was in some Qualcomm mode. Which you need manufacturer tools to fix from there.
As we unlocked bootloader, the annoying screen stated that our device status currently unlocked is appeared. Hoping someone can get rid of the screen. thanks!
+1...this is annoying
Sent from my Mi A1 using Tapatalk
I can agree that it doesn't look nice, but how often do you reboot your phone for that screen to be relevant? It's a 5 second screen once during boot, hardly worth the effort, IMHO.
Localhorst86 said:
I can agree that it doesn't look nice, but how often do you reboot your phone for that screen to be relevant? It's a 5 second screen once during boot, hardly worth the effort, IMHO.
Click to expand...
Click to collapse
That's true i can live with it but if there is a solution to it then i will be more than happy but i doubt it
Dr Grato said:
As we unlocked bootloader, the annoying screen stated that our device status currently unlocked is appeared. Hoping someone can get rid of the screen. thanks!
Click to expand...
Click to collapse
+1
I don't think we can do that. i used to own a nexus 6p and there was never a way to get rid of that annoying unlocked bootloader screen.
Well i used OP3 before and someone tried and succeed to remove the unlocked bootloader screen. It just an idea. Who knows. ?
Pixel XL, stock ROM/ kernel, rooted with Magisk, TWRP recovery. Getting random reboots about every day or two, usually while it's sleeping in my pocket. This all started right after the June update with no other software changes. Anyone else seeing the same?
Been happening to me as well. I'm not on stock, but it seems to have smoothed out for now.
Search for your issue here https://issuetracker.google.com/ if someone has reported it Star it so gets more attention if it's not reported make a report yourself
Unless it's an issue by Magisk then obviously no support
Gulfstream 650 said:
Pixel XL, stock ROM/ kernel, rooted with Magisk, TWRP recovery. Getting random reboots about every day or two, usually while it's sleeping in my pocket. This all started right after the June update with no other software changes. Anyone else seeing the same?
Click to expand...
Click to collapse
Purely academic question - your phone comes fully encrypted, unbreakable, yet you chose to root/unlock bootloader to break that privacy protection. Is it worth it to you?
nabbed said:
Purely academic question - your phone comes fully encrypted, unbreakable, yet you chose to root/unlock bootloader to break that privacy protection. Is it worth it to you?
Click to expand...
Click to collapse
You just install security right back in phone, no breach
fiverings said:
You just install security right back in phone, no breach
Click to expand...
Click to collapse
Yeap. When you fall off a cliff, just come right back to life. No prob. Keep smoking them, bro!
nabbed said:
Yeap. When you fall off a cliff, just come right back to life. No prob. Keep smoking them, bro!
Click to expand...
Click to collapse
Well, it sounded plausible to me. If I'm wrong I'm wrong. Thanks for your imput.
nabbed said:
Purely academic question - your phone comes fully encrypted, unbreakable, yet you chose to root/unlock bootloader to break that privacy protection. Is it worth it to you?
Click to expand...
Click to collapse
I could be wrong, but I doubt he rooted it/unlocked its bootloader just to break a "privacy protection". He probably rooted it/unlocked its bootloader so he could get more functionality out of it.
fiverings said:
Well, it sounded plausible to me. If I'm wrong I'm wrong. Thanks for your imput.
Click to expand...
Click to collapse
No you are correct. There are far more benefits to being unlocked then locked.
Gulfstream 650 said:
Pixel XL, stock ROM/ kernel, rooted with Magisk, TWRP recovery. Getting random reboots about every day or two, usually while it's sleeping in my pocket. This all started right after the June update with no other software changes. Anyone else seeing the same?
Click to expand...
Click to collapse
Going back to the point on the topic, I also got my phone rebooting several times a day after the latest update. And now, it just stops ... booting*

*AT ALL!!
I have a brick! It slightly vibrates after 30 seconds of combining Power and Vol Down buttons, but I can't get it into bootloader or any other booting sequence. The screen doesn't turn on, not even when charging. I can feel the phone is charging because is slightly warm (as usual) while charging.
I tried living the phone all night discharging the battery (unplugged) but still not able to recover it. I tried again charging it today, but still nothing. No chance to do fastboot or any adb, the phone is not even turning on. What should I do? RMA? Mine is a Pixel XL 128Gb (Verizon) with stock ROM not rooted.
infinito0174 said:
Going back to the point on the topic, I also got my phone rebooting several times a day after the latest update. And now, it just stops ... booting*

*AT ALL!!
I have a brick! It slightly vibrates after 30 seconds of combining Power and Vol Down buttons, but I can't get it into bootloader or any other booting sequence. The screen doesn't turn on, not even when charging. I can feel the phone is charging because is slightly warm (as usual) while charging.
I tried living the phone all night discharging the battery (unplugged) but still not able to recover it. I tried again charging it today, but still nothing. No chance to do fastboot or any adb, the phone is not even turning on. What should I do? RMA? Mine is a Pixel XL 128Gb (Verizon) with stock ROM not rooted.
Click to expand...
Click to collapse
Try holding down power about 8 or so seconds
Then while still holding it down, hold down the volume up for 6 seconds, then let it go if nothing, let power go.
nabbed said:
Purely academic question - your phone comes fully encrypted, unbreakable, yet you chose to root/unlock bootloader to break that privacy protection. Is it worth it to you?
Click to expand...
Click to collapse
Yes, very much worth it for the additional functionality. I use layered security that will keep the vast majority of snoops out so it strikes a good balance.
I am facing screen flickering issues on my 3xl under low brightness. This gave me daily headaches for one month seriously.
So I'm thinking to take the Google support in this matter. I'm not rooted but bootloader was unlocked. Will they consider it to service under warranty or not?
I'm from India.
Thanks for help
harigavara said:
I am facing screen flickering issues on my 3xl under low brightness. This gave me daily headaches for one month seriously.
So I'm thinking to take the Google support in this matter. I'm not rooted but bootloader was unlocked. Will they consider it to service under warranty or not?
I'm from India.
Thanks for help
Click to expand...
Click to collapse
Check that smart pixels is off.
Google does not care if it is unlocked, they will warranty it.
mgp53 said:
Check that smart pixels is off.
Click to expand...
Click to collapse
Where can i find it? I can't find it in phone settings.
harigavara said:
Where can i find it? I can't find it in phone settings.
Click to expand...
Click to collapse
I apologize. I don't think stock Pie has that option. I know the ROM I am using has it, and it caused a flickering issue.
mgp53 said:
I apologize. I don't think stock Pie has that option. I know the ROM I am using has it, and it caused a flickering issue.
Click to expand...
Click to collapse
Yes i am aware of that. I too used such Rom. But i don't know it removes flickering. But isn't that resulting dark or dull display?
harigavara said:
Yes i am aware of that. I too used such Rom. But i don't know it removes flickering. But isn't that resulting dark or dull display?
Click to expand...
Click to collapse
Look under Battery in settings?
Yeah they are fine with it, that's why I'm basically locked into Google phones for life, no other manufacturer for US phones is like this and supportive of the rooting community.