Temp Root Bounty for Verizon Variants

[djmouse]

It's 100 percent verizion,Google sends there phones unlocked from them.The only good out of this is Google sends unlocked phones,probably creates what verizion wants or since there partners ina sense,says lock all verizion units see if anyone can find a back door.I don't know if anyone with the skills has actually tried,but at least is shows there taking security more serious witch is good,in it's own way.

 

[kitila]

It's 100 percent verizion,Google sends there phones unlocked from them.The only good out of this is Google sends unlocked phones,probably creates what verizion wants or since there partners ina sense,says lock all verizion units see if anyone can find a back door.I don't know if anyone with the skills has actually tried,but at least is shows there taking security more serious witch is good,in it's own way.

Google creates the operating system then sends the operating system out to all major carriers to allow the major carriers to install their bloatware and all their dirty dealings on to Google's operating system. once the carriers in the manufacturers do all their bloatware and put all their dirty hands into a software it is didn't sent back to Google and Google then approves it and then Google sends it out over the air.. so at the end of the day Google had to approve of the locked bootloader Google has the ability to unlock the bootloader since it is Google's software

 

[Strephon Alkhalikoi]

This is true of most phones, but not the Nexus or Pixel devices. If Verizon had modified the P2XL firmware, Verizon would be hosting the firmware package. However, if you head over to Google's download pages for Nexus and Pixel devices, you will find the current firmware package available for the P2XL. There are two variants there. One is for Telstra devices, but the other is for the rest of the world, including Verizon. I don't recall instances of Google Store-purchased devices using Verizon SIMs ending up bootloader locked. Thus the bootloader included within the firmware package is not locked.

The problem people on this thread are having is they are unable to find the trigger that locks the bootloader. I can only speculate here, but I think during the "checking for updates" process in Android setup, the setup routine transmits the IMEI to Google, which then compares it to a list of Verizon devices. If a match is found, either a command to encrypt the bootloader is sent, or an encrypted bootloader is silently installed in place of the unencrypted one. Setup than continues. This ability to directly update the device during setup has existed since at least the Nexus 6. Prior to that Samsung had a similar setup that pre-installed specific apps based upon the region code of the device, but the Samsung setup was easily modified by changing the region code.

The net result is a device with a locked bootloader. And yes, Google did agree to the locked bootloader, as it likely was part of the sales agreement between Google and Verizon. That agreement likely also precludes them from ever unlocking the bootloader.

 

[slogar25]

This is true of most phones, but not the Nexus or Pixel devices. If Verizon had modified the P2XL firmware, Verizon would be hosting the firmware package. However, if you head over to Google's download pages for Nexus and Pixel devices, you will find the current firmware package available for the P2XL. There are two variants there. One is for Telstra devices, but the other is for the rest of the world, including Verizon. I don't recall instances of Google Store-purchased devices using Verizon SIMs ending up bootloader locked. Thus the bootloader included within the firmware package is not locked.

The problem people on this thread are having is they are unable to find the trigger that locks the bootloader. I can only speculate here, but I think during the "checking for updates" process in Android setup, the setup routine transmits the IMEI to Google, which then compares it to a list of Verizon devices. If a match is found, either a command to encrypt the bootloader is sent, or an encrypted bootloader is silently installed in place of the unencrypted one. Setup than continues. This ability to directly update the device during setup has existed since at least the Nexus 6. Prior to that Samsung had a similar setup that pre-installed specific apps based upon the region code of the device, but the Samsung setup was easily modified by changing the region code.

The net result is a device with a locked bootloader. And yes, Google did agree to the locked bootloader, as it likely was part of the sales agreement between Google and Verizon. That agreement likely also precludes them from ever unlocking the bootloader.

Unfortunately I believe this is the case as well.

 

[bobby janow]

Unfortunately I believe this is the case as well.

This seems to be the going theory ATM. Just to clarify the above post by @Strephon Alkhalikoi it's not the bootloader that Google / Verizon locks or unlocks but the toggle that allows it. I'm sure that was understood but it jumped out at me.

This idea has been given credence in the past day or two when Google was able to turn on battery saver just by flipping a switch server side. And this is not even at bootup, it's while your phone was active. So how difficult would it be to simply gray out and make inactive a toggle? It must be an identifier on the device that a server will check against. Seeing what Google did yesterday I do believe we're out of options. The only thing Verizon does is tell them which devices to lock. They have no other input imo. Once your device is in that database you are SOL.

 

[infamousvincci]

Someone posted this in g+ guys. Idk if it works or it will help you guys.

 

[lucky_strike33]

Someone posted this in g+ guys. Idk if it works or it will help you guys.

Nope it doesn't work

 

[Hexlay]

Nope it doesn't work

Anyone tried disabling apps in recovery, without phone even entering setup?

 

[Strephon Alkhalikoi]

This seems to be the going theory ATM. Just to clarify the above post by @Strephon Alkhalikoi it's not the bootloader that Google / Verizon locks or unlocks but the toggle that allows it. I'm sure that was understood but it jumped out at me.

This idea has been given credence in the past day or two when Google was able to turn on battery saver just by flipping a switch server side. And this is not even at bootup, it's while your phone was active. So how difficult would it be to simply gray out and make inactive a toggle? It must be an identifier on the device that a server will check against. Seeing what Google did yesterday I do believe we're out of options. The only thing Verizon does is tell them which devices to lock. They have no other input imo. Once your device is in that database you are SOL.

I actually did think it was the bootloader itself, but the clarification is welcome. TBH I didn't even think of Google locking out the toggle, as I haven't read the article about battery saver turning itself on...yet.

 

[bobby janow]

I actually did think it was the bootloader itself, but the clarification is welcome. TBH I didn't even think of Google locking out the toggle, as I haven't read the article about battery saver turning itself on...yet.

Here it is, at least one of the threads. Not happy campers out there. https://www.reddit.com/r/GooglePixe...ses_power_saving_mode_turning_itself/e5xl907/

 

[Strephon Alkhalikoi]

@bobby janow: I read that after I posted. Definitely not a happy crowd. But at the same time they don't have many choices, unless they want to track down a Chinaphone.

 

[bobby janow]

@bobby janow: I read that after I posted. Definitely not a happy crowd. But at the same time they don't have many choices, unless they want to track down a Chinaphone.

I know it's crazy out there. But to bring it full circle, it seems like an easy task for Google to lock out the OEM switch on any device of their choosing. I even think they are doing it to their own refurbs but I can't be certain of that. Perhaps it was a test to see how many complained. At some point bl unlock, even on a Google device, will be history, imo.

 

[djmouse]

Google creates the operating system then sends the operating system out to all major carriers to allow the major carriers to install their bloatware and all their dirty dealings on to Google's operating system. once the carriers in the manufacturers do all their bloatware and put all their dirty hands into a software it is didn't sent back to Google and Google then approves it and then Google sends it out over the air.. so at the end of the day Google had to approve of the locked bootloader Google has the ability to unlock the bootloader since it is Google's software

I agree,but verizion had to make the request for the locked OEM toggle so i blame verizion,I was on ATT for almost 20 years I bought the HTC ONE A9,it was the same deal except if you wanted the option you had to request it on HTC site.why can't this be the same doesn't make sense.The only way you get the bloat is if you setup the phone with the verizion sim inserted,I factory reset about once a week just to keep my phone clean idk OCD anyway I set it up without my sim in and just do the my Verizon app to pay my bill.i haven't made it to the store yet to discuss my bill and OEM toggle but soon.So my IMEI is definitely locked to verizion,I have my theories but I'd be here for days.

 

[bobby janow]

I agree,but verizion had to make the request for the locked OEM toggle so i blame verizion,I was on ATT for almost 20 years I bought the HTC ONE A9,it was the same deal except if you wanted the option you had to request it on HTC site.why can't this be the same doesn't make sense.The only way you get the bloat is if you setup the phone with the verizion sim inserted,I factory reset about once a week just to keep my phone clean idk OCD anyway I set it up without my sim in and just do the my Verizon app to pay my bill.i haven't made it to the store yet to discuss my bill and OEM toggle but soon.So my IMEI is definitely locked to verizion,I have my theories but I'd be here for days.

Blame Verizon? I'm sorry what exactly do you mean? To me all they did was what they said they would do, lock the bootloader so corporate networks could buy the device without worry. There is no bloat that you can't delete. Those days are over as well. As for your IMEI locked to Verizon, that's not entirely correct. Your IMEI is registered with Verizon whether or not you have a VZW bought or Google bought phone. Nothing is locked. Your IMEI is listed as a VZW phone and as such you will not be allowed to unlock the bl no matter the provider. I hope I hope this is clear. As for them OEM unlocking your device... lol. Not a chance. But I do understand your frustration. Next time just...

 

[Strephon Alkhalikoi]

@djmouse: A more appropriate example than HTC is Lenovo / Motorola. They offer all the devices and accessories they make on their website for purchase. A device purchased from them will have a locked bootloader. However, all their phones except ones with the "Droid" branding can be unlocked by sending a request to Lenovo. "Droid" branded phones are permanently locked to Verizon and cannot be unlocked.

As to the bootloader unlock toggle, good luck with that. Verizon's stance on bootloader unlocking is crystal clear, and can be read in its entirety here. For those not wishing to click on the link, in short Verizon does not want "unapproved" firmware on their network (i.e. custom ROMs and mods) and doesn't want their help desk clogged with calls from idiots who have no business rooting their devices in the first place.

 

[t0xicdr3am]

"From idiots who.."

Go **** yourself.

@djmouse: A more appropriate example than HTC is Lenovo / Motorola. They offer all the devices and accessories they make on their website for purchase. A device purchased from them will have a locked bootloader. However, all their phones except ones with the "Droid" branding can be unlocked by sending a request to Lenovo. "Droid" branded phones are permanently locked to Verizon and cannot be unlocked.

As to the bootloader unlock toggle, good luck with that. Verizon's stance on bootloader unlocking is crystal clear, and can be read in its entirety here. For those not wishing to click on the link, in short Verizon does not want "unapproved" firmware on their network (i.e. custom ROMs and mods) and doesn't want their help desk clogged with calls from idiots who have no business rooting their devices in the first place.

Sent from my Pixel 2 XL using Tapatalk

 

[bobby janow]

"From idiots who.."

Go **** yourself.

Sent from my Pixel 2 XL using Tapatalk

Don't be a ****. No one is an idiot here.

Sent from my Pixel 2 using XDA-Developers Legacy app

 

[t0xicdr3am]

I didn't say that. He did. Which is why I said what I said. No one here is an idiot.

Don't be a ****. No one is an idiot here.

Sent from my Pixel 2 using XDA-Developers Legacy app

Sent from my Pixel 2 XL using Tapatalk

 

[Strephon Alkhalikoi]

Don't be a ****. No one is an idiot here.

And I never said anyone here was. Because we wouldn't be clogging a help desk clamoring for help. We'd fix the problem ourselves.

 

[t0xicdr3am]

A few posts up I said how I talked to Verizon and Google support about this.. which falls into what you said. So okay. Indirectly.

And I never said anyone here was.

Sent from my Pixel 2 XL using Tapatalk