Related
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
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
If you don't or can't get hotspot enable you may have to root to get it. Plenty of info on how.
FYI
Since you are on Sprint I'm going to guess you bought directly from Google. To my knowledge you can disregard any convos about updates locking you down. That only seems to affect devices bought through Verizon.
FernBch said:
If you don't or can't get hotspot enable you may have to root to get it. Plenty of info on how.
FYI
Since you are on Sprint I'm going to guess you bought directly from Google. To my knowledge you can disregard any convos about updates locking you down. That only seems to affect devices bought through Verizon.
Click to expand...
Click to collapse
Yes sprint and bought directly from play store.
Guess I'll start with this tool eH?
forum.xda-developers.com/pixel/development/tool-skipsoft-android--google-t3482761
Problem is, I already updated via OTA to latest version. Am I screwed?
Screwed?? If you mean BL locked, no. I have the Verizon branded variant but unlocked, rooted, and flashed SU. When I saw NMF26Q was available from Google I downloaded it, installed via flash-all from fastboot, then rerooted and flashed SU again no problem.
chugger93 said:
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
Click to expand...
Click to collapse
Please look at OP install instructions in this thread.
Please look at OP install instruction in TWRP thread.
I guess you aren't on Telus in Canada or your hotspot would work. When you give no information, too hard to help. But I read this forum so even though I don't have Sprint or Verizon as my provider, I know there are many threads about turning hotspot on for unlimited data plans. Guidance: read those threads too!
Then ask for specific guidance. I don't want to reread for 25 min to find and copy and paste to spoonfeed when you should read. Much nicer to fill in a few missing spots than hold your hand not having a clue of your technical knowledge and skills.
Happy holidays.
Specific guidance: update SDK tools before you start!
Sent from my sailfish using XDA Labs
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent? or can I now relock bootloader since I'm rooted?
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent?
Click to expand...
Click to collapse
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent?
Click to expand...
Click to collapse
joetheshmo said:
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Nothing to worry about. I just ignore it.
joetheshmo said:
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
That's Verizon's equivalence of "Sorry sucka, you're on your own!"
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent? or can I now relock bootloader since I'm rooted?
Click to expand...
Click to collapse
Do not relock your bootloader unless you are fully 100% stock or you run the risk of bricking your phone
Sent from my Pixel using Tapatalk
joetheshmo said:
Do not relock your bootloader unless you are fully 100% stock or you run the risk of bricking your phone
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
chugger93 said:
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
Click to expand...
Click to collapse
If you're rooted and have done the tether hack you're no longer stock. Don't lock the bootloader unless you are COMPLETELY stock.
robocuff said:
If you're rooted and have done the tether hack you're no longer stock. Don't lock the bootloader unless you are COMPLETELY stock.
Click to expand...
Click to collapse
Which tether hack? This one? http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
If so, I have not done any tether hack yet....still reading since there are multiple ways to do it. (sprint variant/google play store)
chugger93 said:
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
Click to expand...
Click to collapse
No, having SuperSU means you are no longer stock. You need all stock images to lock bootloader.
If you need a locked bootloader for Android Pay or some other apps. Install one of the customer kernels, they hide it. You still need to remove SuperSU though. From what I've seen its a bit harder to hide that for now. So you can root, make change for hotspot and remove root.
Otherwise nothing hurts to have your bootloader unlocked. It gives you more options if anything ever goes wrong. You need unlocked bootloader to even load Google factory images.
PS. I'd recommend Franco kernel as it imporoves battery life.
Sent from my Pixel using Tapatalk
chugger93 said:
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
Click to expand...
Click to collapse
No you don't have to root to have hotspot enabled, it's a build-in function. Simply set it up in “wireless & networks” and you are ready to go:laugh:
eos9d said:
No you don't have to root to have hotspot enabled, it's a build-in function. Simply set it up in �wireless & networks� and you are ready to go[emoji23]
Click to expand...
Click to collapse
Depending on his plan, he may not have that option. Many do not, hence still need the tether hack.
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Nick_Gl said:
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Click to expand...
Click to collapse
Nothing it will work just fine. From what I understand just a slight difference for Europe. It will be fine.
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
You probably wouldn't get any updates. The trigger for that version probably wouldn't get to you. But I am not certain on that. Might be able to pull it via wifi with no SIM in it.
Do NOT relock your bootloader unless it is just before you are going to put it in a box to send back for warranty.
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
bobby janow said:
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
Click to expand...
Click to collapse
He made it sound like his pixel is from Verizon. In that case he can't lock and unlock the bootloader whenever he wants.
To the OP. What are you trying to do? It doesn't matter if you are on V. If it makes you feel better just flash U then. As long as you don't have twrp or root you will still get OTAs. Why would you want to lock your bootloader? You can have an unlocked bootloader and still take normal OTAs just fine . it its a Verizon sold pixel you won't be able to unlock once you lock.
fritzgerald said:
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Click to expand...
Click to collapse
Thanks wasn't sure. I'll just remember to side load the correct one in February.
aholeinthewor1d said:
He made it sound like his pixel is from Verizon. <snip>
Click to expand...
Click to collapse
It was certainly a little bit confusing, however, the last part of his post it said.. (device from Google) so I figured it was a GPixel activated on Verizon.
I want to update everything except leave the bootloader on 7.1. Will this work?
LoliSmith said:
I want to update everything except leave the bootloader on 7.1. Will this work?
Click to expand...
Click to collapse
I don't believe that will work. Why do you want to do that? 7.1.1 won't relock it if that is what you are worried about....as long as you are already unlocked.
TonikJDK said:
I don't believe that will work..
Click to expand...
Click to collapse
I think I will try it.
TonikJDK said:
Why do you want to do that?
Click to expand...
Click to collapse
I want to be able to lock and unlock if I need to.
LoliSmith said:
I think I will try it.
I want to be able to lock and unlock if I need to.
Click to expand...
Click to collapse
Once you are unlocked it does not matter what version you are on you can lock and unlock all you want. I advise strongly against relocking. You very well might brick yourself. Has happened to a fair number of people already. Also remember unlocking or relocking will wipe your phone.
TonikJDK said:
Once you are unlocked it does not matter what version you are on you can lock and unlock all you want.
Click to expand...
Click to collapse
http://theroot.ninja/depixel8.html
"DO NOT RELOCK YOUR BOOTLOADER, unless you have restored it back to 100% stock and are sure you won't want it unlocked again."
TonikJDK said:
O I advise strongly against relocking. You very well might brick yourself. Has happened to a fair number of people already.
Click to expand...
Click to collapse
Were they still on 7.1 bootloader? Or had they upgraded to 7.1.1 bootloader?
LoliSmith said:
Were they still on 7.1 bootloader? Or had they upgraded to 7.1.1 bootloader?
Click to expand...
Click to collapse
Don't know, didn't pay that much attention.
TonikJDK said:
Don't know, didn't pay that much attention.
Click to expand...
Click to collapse
My guess is they upgraded to the 7.1.1 bootloader and that caused the issues relocking.
LoliSmith said:
My guess is they upgraded to the 7.1.1 bootloader and that caused the issues relocking.
Click to expand...
Click to collapse
It has nothing at all to do with the bootloader.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
It has nothing at all to do with the bootloader.
Click to expand...
Click to collapse
So what does it have to do with then?
LoliSmith said:
So what does it have to do with then?
Click to expand...
Click to collapse
No one knows for sure. Well some must know but they're not saying. Maybe imei. Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Click to expand...
Click to collapse
Right but if I stay on 7.1 bootloader, then it doesn't matter.
I am on 7.1. still. I want the bootloader to stay on 7.1. I think people who experienced problems relocking had upgraded their bootloader to 7.1.1.
LoliSmith said:
Right but if I stay on 7.1 bootloader, then it doesn't matter.
I am on 7.1. still. I want the bootloader to stay on 7.1. I think people who experienced problems relocking had upgraded their bootloader to 7.1.1.
Click to expand...
Click to collapse
There has been posts about problems relocking before 7.1. Bottom line is if you have a Verizon Pixel, you don't want to do it unless you are completely stock. Regardless of the version of your bootloader. Why would you want to lock it again anyway? Under the context you are using here, it makes no sense. Keep an old bootloader so you can lock and unlock at your choosing. I can see reasons for relocking it but i can't see any reason why you'd want to unlock, then relock, then unlock, etc. Leave it unlocked and enjoy the benefits. I'm not really sure what it is you're wanting here. As has been said before, once unlocked, you'll remain unlocked. Regardless of any update with an updated bootloader. Once unlocked, the only way for you to end up with a locked bootloader is if you issue the necessary fastboot commands. Leave it unlocked. Enjoy. Just my two cents worth.
bobby janow said:
No one knows for sure. Well some must know but they're not saying. Maybe imei. Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Click to expand...
Click to collapse
There's actually a total of 5 bootloaders
robocuff said:
Bottom line is if you have a Verizon Pixel, you don't want to do it unless you are completely stock.
Click to expand...
Click to collapse
I would never try to relock without being completely stock.
robocuff said:
Why would you want to lock it again anyway?
Click to expand...
Click to collapse
More secure.
LoliSmith said:
I would never try to relock without being completely stock.
More secure.
Click to expand...
Click to collapse
I can't argue with that but how much security are losing by staying on that version and not installing the monthly updates? They are mostly security related updates. Seems to me you'd be trading one security issue for a whole bunch more. That said, if you stay on 7.1 you should be able to lock it and unlock it again in the future if that's what you want to do.
robocuff said:
I can't argue with that but how much security are losing by staying on that version and not installing the monthly updates?
Click to expand...
Click to collapse
As long as they are released as flashable files, I can flash them. But if not then yeah, I am missing out on those.
robocuff said:
That said, if you stay on 7.1 you should be able to lock it and unlock it again in the future if that's what you want to do.
Click to expand...
Click to collapse
Yes, that is what I want to do. The only thing I am not sure on is if I flash everything else, will the phone work with an older bootloader version. It always worked with my motorola and nexus phones but of course, that doesn't mean it will work with a Pixel.
With motorola I did have to keep the partition table consistent with the bootloader version and that could create a problem if the system partition of later versions was larger.
I plan on staying on Nougat with this phone so it shouldn't be a problem.
LoliSmith said:
As long as they are released as flashable files, I can flash them. But if not then yeah, I am missing out on those.
Yes, that is what I want to do. The only thing I am not sure on is if I flash everything else, will the phone work with an older bootloader version. It always worked with my motorola and nexus phones but of course, that doesn't mean it will work with a Pixel.
With motorola I did have to keep the partition table consistent with the bootloader version and that could create a problem if the system partition of later versions was larger.
I plan on staying on Nougat with this phone so it shouldn't be a problem.
Click to expand...
Click to collapse
I don't really know what to tell you about it. The bootloader may work fine but who's to say the vulnerability that depixel8 exploits is in the bootloader? It could be software related, it could be hardware related. I really have no idea. Also, I did a bit of searching about this and from what I read, it sounds as if it might not be possible to unlock it again if you've already taken the security patch that patched the exploit. I could be wrong but it sounds as if that may be the case. Look, at the last paragraph of this article . From what that says, it sounds as though it isn't possible to unlock even on an older version of Nougat once you've taken that security patch. If that's the case, it would seem the the exploit must have targeted something at a very low level. Something other than the OS or the bootloader.
Also, even if you can do what you want to do, I don't know if you can install the updates without installing the one that patches the exploit. I really have no idea. I've seen it said that they are cumulative and in order to install the newest updates, you have to install all the previous ones first. I really have no idea if that is correct or not but if it were me, I'd tread lightly on this one unless you're willing to risk the possibility of not being able to unlock it again. These are just some of my thoughts about it all. I don't have the answers to my thoughts but if it were me, I wouldn't lock it again without knowing for sure it can be unlocked again.
robocuff said:
I could be wrong but it sounds as if that may be the case. Look, at the last paragraph of this article . From what that says, it sounds as though it isn't possible to unlock even on an older version of Nougat once you've taken that security patch.
Click to expand...
Click to collapse
Right because it updated both the bootloader and the kernel. I would only be updating the kernel, not the bootloader. And I am assuming that as long as the bootloader is on 7.1, I can downgrade the kernel, system, etc. as long as the files are signed.
robocuff said:
If that's the case, it would seem the the exploit must have targeted something at a very low level. Something other than the OS or the bootloader.
Click to expand...
Click to collapse
I am not going to ever take any OTAs. Presumably aboot.img is the bootloader but I am not sure what bootlocker.img and keymaster.img are so I would need to research that further. Do you know what they are?
robocuff said:
I've seen it said that they are cumulative and in order to install the newest updates, you have to install all the previous ones first.
Click to expand...
Click to collapse
Are you talking about flashing or taking OTAs?
robocuff said:
I really have no idea if that is correct or not but if it were me, I'd tread lightly on this one unless you're willing to risk the possibility of not being able to unlock it again. These are just some of my thoughts about it all. I don't have the answers to my thoughts but if it were me, I wouldn't lock it again without knowing for sure it can be unlocked again.
Click to expand...
Click to collapse
Thanks. I am OK with not being able to unlock again.
LoliSmith said:
keymaster.img
Click to expand...
Click to collapse
Yeah, definitely won't be updating that:
https://source.android.com/security/keystore/
Hello guys.
I'm going to buy used and bootloader unlocked Verizon Pixel tomorrow and I'm interested in couple of things:
1. Can I flash all the ROMs that are available for Pixel on Verizon version too?
2. Can I properly install TWRP, root using Magisk, etc?
3. Can I properly flash (and downgrade if needed) official system images (and are they ever available for Verizon models?)
4. Can I take part in Android Beta program?
5. Is there anything I should be afraid of?
Thanks in advance.
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that are bootloader unlocked. You need that to do the items on you list.
TonikJDK said:
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that area bootloader unlocked. You need that to do the items on you list.
Click to expand...
Click to collapse
As I already stated, bootloader is already unlocked.
No one has an answer?
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
I got a replacement about a month ago on my small Pixel and that one was unlocked. However, the one I got from Verizon in store did not have an unlocked bootloader. I'm not sure what the deal is, but maybe getting a replacement from an "accidental" break might do the trick. just to clarify, my first Pixels' usb port got completely fried and started to smell bad whenever it charged, and the phone would get really hot. I am now on 8.1 with an unlocked bootloader but have yet to actually root the phone
KittyRgnarok said:
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
Click to expand...
Click to collapse
Thank you!
gb_14 said:
Thank you!
Click to expand...
Click to collapse
Np