Database Info

Installed wrong version

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.

Updating Verizon Pixel unlocked bootloader with depixel8

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/

Time to Complain to Samsung for the Locked Oreo Bootloaders

I think it would be a good idea to start complaining on how Samsung has locked down their phones with Oreo. Call them out on Twitter and other threads. Who is with me?

Psyscope said:
I think it would be a good idea to start complaining on how Samsung has locked down their phones with Oreo. Call them out on Twitter and other threads. Who is with me?
Click to expand...
Click to collapse
it would not help, samsung, Dell, HP and so on, everyone has patched their bootloaders or bios/os microcode updates cause of specte/meltdown. there is no manufacturer that allows to downgrade after a update for meldown/spectre has been applied. it has nothing to do with samsung, it's just a way of protecting their consumers.

Psyscope said:
I think it would be a good idea to start complaining on how Samsung has locked down their phones with Oreo. Call them out on Twitter and other threads. Who is with me?
Click to expand...
Click to collapse
They did not lock anything down that was not locked down already

That is not true, In Oreo you can no longer use the OEM unlock option. You can not flash Oreo bootloaders. You get an FRP boot loop. This is a new change that forces Oreo users who are on custom roms to stay on Nougat Bootloaders.

Psyscope said:
That is not true, In Oreo you can no longer use the OEM unlock option. You can not flash Oreo bootloaders. You get an FRP boot loop. This is a new change that forces Oreo users who are on custom roms to stay on Nougat Bootloaders.
Click to expand...
Click to collapse
For exynos phones? Post a link to this issue.

peachpuff said:
For exynos phones? Post a link to this issue.
Click to expand...
Click to collapse
This person does not realize the change.
https://forum.xda-developers.com/galaxy-s8/help/oreo-android-8-firmware-rooted-s8-t3750526
You have to go through this process to flash Oreo, however you will get custom firmware bootloop if you flash bootloader on custom rom.
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-flash-crap-using-odin-s8-t3748571

Psyscope said:
I think it would be a good idea to start complaining on how Samsung has locked down their phones with Oreo. Call them out on Twitter and other threads. Who is with me?
Click to expand...
Click to collapse
I actually called and asked to speak to someone about this and they basically have me the run-around. Then I asked to speak to any developer and they told me they couldn't do that and to have a nice day........I figured I'd try.

Psyscope said:
That is not true, In Oreo you can no longer use the OEM unlock option. You can not flash Oreo bootloaders. You get an FRP boot loop. This is a new change that forces Oreo users who are on custom roms to stay on Nougat Bootloaders.
Click to expand...
Click to collapse
People in the Oreo threads are saying you have to wait 7 days and you can not turn the phone off or reboot in those 7 days for the unlock option to show up. If you turn it off or reboot the counter resets. I can't confirm this, just relaying what everyone is saying.

I remember when I thought my opinion mattered.

Psyscope said:
That is not true, In Oreo you can no longer use the OEM unlock option. You can not flash Oreo bootloaders. You get an FRP boot loop. This is a new change that forces Oreo users who are on custom roms to stay on Nougat Bootloaders.
Click to expand...
Click to collapse
That's completely untrue, you have to wait 7 days without the phone turning off even once and this option will appear again

sofir786 said:
That's completely untrue, you have to wait 7 days without the phone turning off even once and this option will appear again
Click to expand...
Click to collapse
But you still can't flash Oreo bootloader and modem on a phone with a custom recovery. Even with oem unlock on. It will bootloop with that message.

Psyscope said:
But you still can't flash Oreo bootloader and modem on a phone with a custom recovery. Even with oem unlock on. It will bootloop with that message.
Click to expand...
Click to collapse
Back you up with that from chat on telegram. Only a few official beta testers never got RMM state prenormal but it's true. Even after 7 days you cannot flash Oreo bootloader

Latest S8 Oreo firmware, updated 2 days ago restarted 1 day ago. G950F

If Samsung persists with this I want my Knox reset and the s8 can go on eBay, I'll buy a pixel 2
Sent from my Nexus 7 using Tapatalk

Oem unlock is still available, let the devs update theur stuff for the oreo bootloader and everyrhing will be fine

goRt said:
If Samsung persists with this I want my Knox reset and the s8 can go on eBay, I'll buy a pixel 2
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
you cannot gt the knox reset without replacing the motherboard. it is a physical fuse.

djisgod said:
you cannot gt the knox reset without replacing the motherboard. it is a physical fuse.
Click to expand...
Click to collapse
Yes, I'm aware of that, but if Samsung is changing the rules it can bear the costs!

goRt said:
Yes, I'm aware of that, but if Samsung is changing the rules it can bear the costs!
Click to expand...
Click to collapse
good luck getting them to agree to that.

djisgod said:
good luck getting them to agree to that.
Click to expand...
Click to collapse
I'm not expecting it to be easy, but if I feel I'm being pushed around I'm very successful at recovering monies.
Sent from my SM-G950F using Tapatalk

Psyscope said:
I think it would be a good idea to start complaining on how Samsung has locked down their phones with Oreo. Call them out on Twitter and other threads. Who is with me?
Click to expand...
Click to collapse
There's no way in hell they'd go for it

7 day wait for oem

why for S9 and s9+ there's a 7 day Wait period for OEM unlock?

Lol... ask samsung.
But this is nothing new, started last fall with the note 8 so i dont know why so many S9 users are surprised really.
sent from my Exynos S9 plus, Pixel 2 XL or Note FE

It gives enterprises 7 days to locate/wipe lost/stolen phones.
When you see RMM state: Prenormal in download mode you are within this period. (RMM = Remote Management & Monitoring).

RMM not unlocking...
Hi Gang!
I've got an international S9+ (SM-G965F/DS) and I've got a working SIM in it. But, after the 168 hrs of uptime, it's still showing as PRENORMAL. I've got developer mode enabled because I want to root this device. But, I can't get to the OEM Unlock until this thing switches to normal mode. Any clues as to why it's not going to Normal mode?
TIA

taichichuan said:
Hi Gang!
I've got an international S9+ (SM-G965F/DS) and I've got a working SIM in it. But, after the 168 hrs of uptime, it's still showing as PRENORMAL. I've got developer mode enabled because I want to root this device. But, I can't get to the OEM Unlock until this thing switches to normal mode. Any clues as to why it's not going to Normal mode?
TIA
Click to expand...
Click to collapse
Do you have a pending ota update? If so you need to take it to get out. It won't reset your 7d wait the whole "up time" thing is complete nonsense anyway ?

My phone is in prenormal state. I have stock firmware and tried to install twrp but decided to just stay stock. Now i cant use google pay..will it work after 7 days?

Hmm... OK, I'll apply the OTA update and see what happens.
TNX,
Mike

So this OEM unlock wait time thing applies to the US SD model as well?

W00fah said:
So this OEM unlock wait time thing applies to the US SD model as well?
Click to expand...
Click to collapse
no sir, yours will never show up. Besides with a locked bootloader there is nothing you can do with it anyway.

force70 said:
no sir, yours will never show up. Besides with a locked bootloader there is nothing you can do with it anyway.
Click to expand...
Click to collapse
Bummer. Hope something comes out for it soon.

W00fah said:
Bummer. Hope something comes out for it soon.
Click to expand...
Click to collapse
Sorry to be negative here, but it won't.

partcyborg said:
Sorry to be negative here, but it won't.
Click to expand...
Click to collapse
Even if it became available Im still trying to figure out the purpose of even flipping the switch on locked down snap models?
You cant flash anything so I dont see the purpose here and yet everyone keeps asking?

I waited the 7 days and got oem unlock back..it is unlocked atm my status is official but i still cant download Netflix or use google pay? says my syetm is modified..Knox hasnt even been tripped.

partcyborg said:
Sorry to be negative here, but it won't.
Click to expand...
Click to collapse
Damn. I'm really gonna have to get a Pixel phone when I do my upgrade. Sucks that nothing is working out for the US model of this phone.

I don't care about root, but can we get just a vanilla AOSP 10 on this device?

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