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/
Related
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.
How do I get to enable OEM Unlocking on a verizon Pixel with the 7.1.1 Update? I've already went to a verizon store and they told me to go check out the forums.
It's greyed out, too
Thanks
Haxel101 said:
How do I get to enable OEM Unlocking on a verizon Pixel with the 7.1.1 Update? I've already went to a verizon store and they told me to go check out the forums.
It's greyed out, too
Thanks
Click to expand...
Click to collapse
Can't on 7.1.1. You had to do it before it updated. No way possible now.
TonikJDK said:
Can't on 7.1.1. You had to do it before it updated. No way possible now.
Click to expand...
Click to collapse
Any way to revert the Android version?
Haxel101 said:
Any way to revert the Android version?
Click to expand...
Click to collapse
No, you are done. Sorry man.
TonikJDK said:
No, you are done. Sorry man.
Click to expand...
Click to collapse
Is it possible for there to be a method in the future?
Haxel101 said:
Is it possible for there to be a method in the future?
Click to expand...
Click to collapse
Anything is possible in the future. But not right now. And no word of any progress.
Sent from my Pixel using Tapatalk
This is where it sits currently.
If you want to unlock, install TWRP, etc. on the Verizon Pixel it MUST be done before updating to 7.1.1. The OTA permanently locks the bootloader UNLESS you unlocked before taking the OTA.
The OTA to 7.1.1 blocks the ability to unlock the bootloader with DePixel8. It also blocks the ability to fastboot an earlier build.
None of the developers are working on unlocking the Verizon devices running 7.1.1. The group that did it previously publicly stated they were not searching for a new exploit.
His guys just got the xzp and wow what a phone my only concern is root I have a locked bootloader and it's not unlockable but to be fair I've never unlocked a Xperia bootloader due to loosing drm keys etc
So my question is will we be able to get root on locked bootloaders like we did with past Xperia phones or are we stuck unless we unlock which in my case would mead no root ever :crying:
Thanks
Probably not would be my guess. You still need to unlock bootloader on previous models such as XZ/XZS.
FartyParty said:
Probably not would be my guess. You still need to unlock bootloader on previous models such as XZ/XZS.
Click to expand...
Click to collapse
Darn I love this device too but to never be able to have root might be a deal breaker
In service menu it says unlock bootloader allowed no but in developer options it give me the option to unlock the bootloader does this mean it's possible for me to unlock the bootloader
brockyneo said:
In service menu it says unlock bootloader allowed no but in developer options it give me the option to unlock the bootloader does this mean it's possible for me to unlock the bootloader
Click to expand...
Click to collapse
That setting is there regardless. If it says no its not possible.
FartyParty said:
That setting is there regardless. If it says no its not possible.
Click to expand...
Click to collapse
Ah OK no root for me then ever think it might have to be the oneplus 5 then I love this phone too
Wait for an Android vulnerability or someone find a way to backup the TA partition
ninjy said:
Wait for an Android vulnerability or someone find a way to backup the TA partition
Click to expand...
Click to collapse
But I cannot unlock the bootloader I was hoping for a root without unlocking the bootloader like the z3 which was my last Xperia device
One question if I stay with the xzp cam I at least flash the latest stock UK unbranded room with a locked bootloader so I can get rid of my carrier stuff thanks
brockyneo said:
But I cannot unlock the bootloader I was hoping for a root without unlocking the bootloader like the z3 which was my last Xperia device
Click to expand...
Click to collapse
It's what i'm saying
brockyneo said:
One question if I stay with the xzp cam I at least flash the latest stock UK unbranded room with a locked bootloader so I can get rid of my carrier stuff thanks
Click to expand...
Click to collapse
yes
ninjy said:
It's what i'm saying
yes
Click to expand...
Click to collapse
So what your saying is they maybe a work around getting root ect on locked bootloaders?
Thanks again
Like always, if a security breach is found on Android that allow getting root access, it will be possible to backup the DRM partition, then after if you like, unlocking the bootloader and then restore your DRM partition.
At least, it finished like this for the Z5, but you had to downgrade to Lollipop to get root access.
AFAIK, there is no known way to get root on Nougat today.
ninjy said:
Like always, if a security breach is found on Android that allow getting root access, it will be possible to backup the DRM partition, then after if you like, unlocking the bootloader and then restore your DRM partition.
At least, it finished like this for the Z5, but you had to downgrade to Lollipop to get root access.
AFAIK, there is no known way to get root on Nougat today.
Click to expand...
Click to collapse
So there is the Dirty Cow exploit that seems pretty pervasive and promising.
https://forum.xda-developers.com/general/security/dirty-cow-t3484879
EDIT: Nevermind I'm an idiot, I didn't realize the dates on dirty cow.
Question still stands though, do we know if there is anyone on the XZ Premium working on it?
topherhead said:
So there is the Dirty Cow exploit that seems pretty pervasive and promising.
https://forum.xda-developers.com/general/security/dirty-cow-t3484879
EDIT: Nevermind I'm an idiot, I didn't realize the dates on dirty cow.
Question still stands though, do we know if there is anyone on the XZ Premium working on it?
Click to expand...
Click to collapse
I don't think so, there will be more involved ppl when XZ1 will be released, since it's the same specs
hoping for this with the XZs updated to Oreo...
manilenio said:
hoping for this with the XZs updated to Oreo...
Click to expand...
Click to collapse
It's not possible anymore. You really need to unlock the bootloader in order to root. Something about patching the kernel.
I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
live4soccer7 said:
I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
Click to expand...
Click to collapse
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
TonikJDK said:
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
Click to expand...
Click to collapse
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
live4soccer7 said:
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
Click to expand...
Click to collapse
It requires a manual command in fastboot. Doubt you'll do that accidently.
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
KittyRgnarok said:
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
Click to expand...
Click to collapse
Thanks everyone, that's exactly what I was looking for. I'm curious, what happens if I toggle the OEM unlock option on/off?
live4soccer7 said:
I'm curious, what happens if I toggle the OEM unlock option on/off?
Click to expand...
Click to collapse
That switch has been grayed out after the Verizon unlock, and it reads "Bootloader is already unlocked", so as far as I know it's not possible to toggle.
Thanks! Much appreciated.
Enjoy your Pixel and happy modding mate
Specifically, this one. ATT branded, snapdragon sm-G955U s8+ device. Nothing fancy, no Xposed module, just vanilla AOSP 10 and maybe the current security patches.
I know this device had it's last year of firmware updates and while it still works fine, can it do more?
Thanks.
3drinks said:
Specifically, this one. ATT branded, snapdragon sm-G955U s8+ device. Nothing fancy, no Xposed module, just vanilla AOSP 10 and maybe the current security patches.
I know this device had it's last year of firmware updates and while it still works fine, can it do more?
Thanks.
Click to expand...
Click to collapse
No. That would require a unlocked boot loader
TheMadScientist said:
No. That would require a unlocked boot loader
Click to expand...
Click to collapse
Well I guess that settles that. That'll learn me to buy carrier flagships again.
3drinks said:
Well I guess that settles that. That'll learn me to buy carrier flagships again.
Click to expand...
Click to collapse
Yea
TheMadScientist said:
Yea
Click to expand...
Click to collapse
do you have a link to that boot. I have the exact phone
BRIANSLEARNING said:
do you have a link to that boot. I have the exact phone
Click to expand...
Click to collapse
You can't your bootloader is locked
TheMadScientist said:
You can't your bootloader is locked
Click to expand...
Click to collapse
I can't get my phone to open oem. The process doesnt work. Is there a master flash i can use. All my data backed up
BRIANSLEARNING said:
I can't get my phone to open oem. The process doesnt work. Is there a master flash i can use. All my data backed up
Click to expand...
Click to collapse
No. Again your bootloader is locked OEM unlock does not exist. You cannot flash custom roms no way no how