Verizon Pixel XL- Toggling the oem unlock switch *SOLVED*

[blueyes]

I have the Verizon Pixel XL and can now toggle the oem unlock switch in developers settings. Annoyed with the "grey out" I have done several things to make the switch useable. Well... Something worked. Now it's time to figure out what did the trick.


Solved. Using a root file explorer, got to /data/system/users/ 0.xml Open it up and edit it to reflect no restrictions. Or clone mine, might wanna remove my name though.. One requirement for this to work, all testing shows it will not work on stock kernel. Not sure if its a selinux issue or not but the modified ElementalX I made does boot up permissive and removes forceencryption. And using it Confirmed working..

 

[blueyes]

I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.

 

[jjayzx]

So you added the supercid through the kernel editing?

 

[dualityim]

I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.

Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?

 

[death2all110]

I'm guessing one of the unlock properties is what did it. I think something on the phone is recognizing it as a VZW model and is setting one of the properties to 0 and graying it out. I'll do some digging this weekend

 

[blueyes]

Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?

To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications

 

[blueyes]

So you added the supercid through the kernel editing?

Just added it to the kernel cmdline

 

[jjayzx]

Just added it to the kernel cmdline

Thanks. I'll be back in a moment.

Update: It didn't work that way. Trying something a little different.
Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.

 

[blueyes]

Thanks. I'll be back in a moment.

Update: It didn't work that way. Trying something a little different.
Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.

The kernel cmdline has to be edited before flashing. Try adding the persist.sys.oem_unlock... Line. Before run su , then set enforce 0

 

[Rootuser3.0]

Why is being able to toggle it a big deal? If your unlocked then why does that matter ?

 

[blueyes]

Why is being able to toggle it a big deal? If your unlocked then why does that matter ?

Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.

 

[blueyes]

Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.

And it's not just about being greyed out. I can now lock my bootloader and unlock it without any exploits. Simply using fastboot. Which sir, I do find to be a nice feature...

 

[Rootuser3.0]

Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.

I never said you said" it was a big deal" I said that. Go kick rocks

 

[jjayzx]

I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.

 

[treIII]

To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications

Did you do the kernel command on the phone? How do I edit default. Prop? I feel like that's where the transformation takes place since it's not editable like the build prop

 

[blueyes]

I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.

Did you add the line persist.sys.oem_unlock_supported=1.
Persists seems to be equivalent to a system override

 

[blueyes]

I never said you said" it was a big deal" I said that. Go kick rocks

Go troll somewhere else.

 

[blueyes]

Did you add the line persist.sys.oem_unlock_supported=1.
Persists seems to be equivalent to a system override

Here's my build.prop

https://www.dropbox.com/s/bxgrk7ug66jiuz1/logs.zip?dl=0

 

[treIII]

Use Android Image Kitchen > http://forum.xda-developers.com/showthread.php?t=2073775

Ok thank you and is this done through terminal or pc

 

[treIII]

There are Windows and Linux versions (which I use). There's also a mobile version, but I've never used it.. Read @osm0sis thread. Very helpful.

That may be over my head as far as my abilities and I hate to create a new brick