January Patch NMF26U and dePixel8 - Google Pixel Questions & Answers

I just received a warranty replace device with NMF26U preinstalled, now i know i can't unlock the bootloader with this android version. How do i downgrade so i can unlock the device? Any ideas?

Verizon version or Google? If Verizon, you are out of luck. You can't downgrade a locked BL phone.

sliding_billy said:
Verizon version or Google? If Verizon, you are out of luck. You can't downgrade a locked BL phone.
Click to expand...
Click to collapse
verizon

palvarez05 said:
verizon
Click to expand...
Click to collapse
Can't do anything. No downgrading. You're out of luck.

When Verizon issued the patch to prevent unlocking the BL they also blocked the ability to downgrade. As far as finding a new exploit I wouldn't hold my breath. I have never seen a Verizon device that has successfully been exploited twice. Ever.

Did you order the warranty device through Verizon or Google?
My wife has a new Verizon Pixel on the way straight from Google. Despite being BL unlocked and rooted, it automatically updated. For some reason the update broke all audio on the phone. I'm really hoping google has a stockpile of verizon phones that aren't updated.

Related

XT1028 (USA VZW PP) Flash to another carrier?

Okay so I bought a used XT1028 on Amazon, and was disappointed that I couldn't root it due to the eternally locked bootloader (thanks to stock 4.4.4).
So I decided to stick with stock until the Lollipop update comes. I talked to Motorola, who told me to contact VZW. I called VZW, and after a few forwards, found out my device is "PIB Locked" which means it needs to be scanned at a Verizon store so it can be activated.
I don't want to do that, nor do I think that'll help.
So after some research, found out that I might need to flash another carrier to be able to get the Lollipop update.
How true is that, and how do I do so? I'm no stranger to flashing a ROM, but a carrier might require some learning.
PCJAndroid said:
Okay so I bought a used XT1028 on Amazon, and was disappointed that I couldn't root it due to the eternally locked bootloader (thanks to stock 4.4.4).
So I decided to stick with stock until the Lollipop update comes. I talked to Motorola, who told me to contact VZW. I called VZW, and after a few forwards, found out my device is "PIB Locked" which means it needs to be scanned at a Verizon store so it can be activated.
I don't want to do that, nor do I think that'll help.
So after some research, found out that I might need to flash another carrier to be able to get the Lollipop update.
How true is that, and how do I do so? I'm no stranger to flashing a ROM, but a carrier might require some learning.
Click to expand...
Click to collapse
And again for flashing you need to unlock your bootloader
S0bes said:
And again for flashing you need to unlock your bootloader
Click to expand...
Click to collapse
Dang.
PCJAndroid said:
Dang.
Click to expand...
Click to collapse
you could possibly downgrade the to 4.3 then root but don't downgrade the bootloader. also you must use official motorola signed software. some had success others were pissed.

Flash Google store Pixel image over Verizon Pixel phone???

Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!
Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk
newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...
newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs

Can all versions of Pixel be rooted?

Can all versions of Pixel have their bootloader unlocked and be rooted? Or are there some versions that cannot be rooted? In the past I had misfortune with carrier branded phones from Canada that it was impossible to unlock bootloader. It want to confirm this is not the case before gettinga Pixel. Thanks in advance.
Just to be clear I'm talking about the Pixel with 5.0" screen, so not the XL.
Google version can be unlocked. There is a tool available to unlock the Verizon version but it was patched with December's update. If you plan to get it through Verizon I would hurry up and get it because it's likely not updated yet. Then you can take out the sim and skip connecting to wifi during setup and then unlock the bootloader before updating.
It is VERY unlikely that a new exploit will be found ever for the Verizon pixel. From my understanding it was a very simple exploit that was pretty much found by mistake.
lightningglasses said:
Can all versions of Pixel have their bootloader unlocked and be rooted? Or are there some versions that cannot be rooted? In the past I had misfortune with carrier branded phones from Canada that it was impossible to unlock bootloader. It want to confirm this is not the case before gettinga Pixel. Thanks in advance.
Just to be clear I'm talking about the Pixel with 5.0" screen, so not the XL.
Click to expand...
Click to collapse
All Canadian versions of the pixel/XL are carrier unlocked and can have their bootloader's unlocked as well. And can be rooted.
aholeinthewor1d said:
Google version can be unlocked. There is a tool available to unlock the Verizon version but it was patched with December's update. If you plan to get it through Verizon I would hurry up and get it because it's likely not updated yet. Then you can take out the sim and skip connecting to wifi during setup and then unlock the bootloader before updating.
It is VERY unlikely that a new exploit will be found ever for the Verizon pixel. From my understanding it was a very simple exploit that was pretty much found by mistake.
Click to expand...
Click to collapse
Why is it "Very Likely"?
There have been plenty of phones to lose bootloader unlock exploits only to never get them back. Guaranteed unlock exploits is a thing of the past... Get in while you can or deal with it when it never becomes an option again.
scryan said:
Why is it "Very Likely"?
There have been plenty of phones to lose bootloader unlock exploits only to never get them back. Guaranteed unlock exploits is a thing of the past... Get in while you can or deal with it when it never becomes an option again.
Click to expand...
Click to collapse
Read my post again lol. I said "very unlikely".

Sept P Factory images now have three variants anyone know the differences.

Doubled checked and noticed that three variants of Factory Images exist. Factory, Telus, and Verizon. Since I have a Verizon locked BL and have unlocked. Is this a backdoor to "correct" the problem. Just like what happened with Pixel 2 Verizon before 8.1 when that exploit existed. Reason why I ask, I had a Pixel 2 factory unlocked and after a (4) refurbish channel replacement with NO UNLOCK ability don't want to see if this is a end around to Lock up Pixels.
If you have a Verizon phone, you should only flash the Verizon ROM (or OTA update). If your phone is already bootloader unlocked, updates should not relock the bootloader, unless you specifically go through the process to relock it. If the bootloader is locked and you flash an update, the update may potentially nullify the method used to unlock the bootloader. In that case, it is best to wait and see what others report.
I have flashed the September Verizon variant (factory image and not OTA) on a Pixel and Pixel XL (both unlocked with dePixel at the very beginning). Nothing happened to the already locked devices. I have little doubt that it would have patched the exploit on a still locked device.
Thank You sliding_billy that was the answer I needed. Not that I will relock, but the fact that others might thought would be good to get verification. Waiting for more drop in price on Verizon locked ones with Pixel 3 release. I want to pick up more used ones. This device has become my #1 after all my Nexus 5X's suffered blod.

Will Verizon lock a phone if it's unlocked?

Getting an Unlocked Pixel 2 off EBay.
Once I unlock the bootloader, and put in my Verizon sim.......will Verizon lock my bootloader?
z
I don't think any carrier has control over locking the bootloader. They can however keep you from unlocking it, just not the other way around
zardiw said:
Getting an Unlocked Pixel 2 off EBay.
Once I unlock the bootloader, and put in my Verizon sim.......will Verizon lock my bootloader?
z
Click to expand...
Click to collapse
As long as it actually was through Google and not a Verizon one you will be fine. Make sure it's not just carrier unlocked, since the Verizon ones will still be considered unlocked due to being able to use it on other carriers.
Keithn said:
As long as it actually was through Google and not a Verizon one you will be fine. Make sure it's not just carrier unlocked, since the Verizon ones will still be considered unlocked due to being able to use it on other carriers.
Click to expand...
Click to collapse
The op is talking about bootloader being unlocked and your talking about the carrier/sim lock... Verizon pixels that were on a certain firmware were able to have their bootloader unlocked, and then it was patched. So pretty much all Verizon pixel 2 are not able to have the bootloader unlocked. Pixels straight from Google are able to have the bootloader unlocked. Now as far as the carrier/sim lock, either version, Verizon or Google, they come unlocked and. I'm pretty sure they can't be relocked. I believe they would just blacklist the device.
ice711 said:
The op is talking about bootloader being unlocked and your talking about the carrier/sim lock... Verizon pixels that were on a certain firmware were able to have their bootloader unlocked, and then it was patched. So pretty much all Verizon pixel 2 are not able to have the bootloader unlocked. Pixels straight from Google are able to have the bootloader unlocked. Now as far as the carrier/sim lock, either version, Verizon or Google, they come unlocked and. I'm pretty sure they can't be relocked. I believe they would just blacklist the device.
Click to expand...
Click to collapse
No, I am talking about both. I only mentioned to be aware that the device may be listed as unlocked due to not having carrier restrictions, but might still be a "Verizon Edition" with a non unlockable bootloader.
Keithn said:
As long as it actually was through Google and not a Verizon one you will be fine. Make sure it's not just carrier unlocked, since the Verizon ones will still be considered unlocked due to being able to use it on other carriers.
Click to expand...
Click to collapse
Keithn said:
No, I am talking about both. I only mentioned to be aware that the device may be listed as unlocked due to not having carrier restrictions, but might still be a "Verizon Edition" with a non unlockable bootloader.
Click to expand...
Click to collapse
Ahh gotcha. Sorry didn't get that when I read it the first time. When you put it this way, I now get what you were saying. Good advise! :good: :good:

Categories

Resources