yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] coolhandz:
Eagerly awaiting. I've been watching this thread from the beginning and am so excited to see this get solved! I wish I could code at all, but watching you guys trouble shoot and brainstorm is still cool.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Built, now the edits and rebuild.. Youve already pointed out several, although prob dont need to remove all traces, just enough to make it permissible.

#### make completed successfully (02:00:55 (hh:mm:ss)) ####
[Google Pixel XL Guides, News, & Discussion] treIII:
Looks like someone else is figuring it out also
[Google Pixel XL Guides, News, & Discussion] blueyes:
About time. People reading this thread probably thought I was full of s**t.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
In that file there is a policy restriction set to true to disable the unlock. I set it to false and restarted the phone and I was no longer grey and the line no longer exists in that file. So my thought is when he erased his phone and had the supercid in it may have thought to not enforce the policy on the user.
[Google Pixel XL Guides, News, & Discussion] blueyes:
One references icon and fingerprint.(0.xml). Other references allowing unknown sources and uid
[Google Pixel XL Guides, News, & Discussion] death2all110:
Interesting. Just tried it but no luck.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Doesn't look grey. Can you toggle it?
[Google Pixel XL Guides, News, & Discussion] blueyes:
If you get bored, take a look at my github, Marlin device repo. See what you think needs reverting. You found those variables regarding the data block.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
guess i'll root and give it a try.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Yea, I can toggle it.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Do you have the supercid on your phone?
[Google Pixel XL Guides, News, & Discussion] blueyes:
I do, but dit it after cracking the toggle switch.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Interesting, has anyone tried your stuff on P yet?
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
I did that and while the line disappeared I still can't toggle the switch.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Not on P anymore. :)
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Can you PM me a how to and I will try this, please? I'm pretty smart guy but would need a precise how to.
[Google Pixel XL Guides, News, & Discussion] xdadevnube:
Guys, I wanted to chime in. Perhaps this will help.

Please see Post #32 in this thread:

http://xdaforums.com/showpost.php?p=69356304&postcount=32

Have you guys made attempts while keeping the Pixel from connecting to internet? I expect that this could be part of the problem in that the device is calling home over the internet to verify and set its security policy.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
I got it it's so simple lol

---------- Post added at 07:10 PM ---------- Previous post was at 07:10 PM ----------

Change the true to false in text editor then it's makes a.bak copy of original delete that then reboot profit lol
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Also I'm on x rooted with twrp and custom kernel Woo hoo lol
[Google Pixel XL Guides, News, & Discussion] psychatog64:
From what I noticed while driving and doing this lol is that if the orginal copy that gets changed to .bak after editing doesn't get deleted phone will force itself back to that one during boot up
[Google Pixel XL Guides, News, & Discussion] cam30era:
Would you mind listing the exact steps and file(s) you edited?
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Sure I used root explorer went to data system users then opened 0.xml file in text editor changed the true to false in the OEM unlock line hit top right corner to save and exit said orginal was named to o.xml.bak deleted that one then reboot and worked
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
I'm guessing that you also need the custom kernel with permissive. Because I did this and it is still greyed out for me and I have the default kernel.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Maybe I didn't change anything other then flash the ex kernel

---------- Post added at 07:34 PM ---------- Previous post was at 07:33 PM ----------

Unless ex kernel has permissive then no you dont
[Google Pixel XL Guides, News, & Discussion] coolhandz:
I found 0.xml using root explorer and see "true", but i can't change it there. I'm not sure what you mean by opening it in text editor.

Edit: i got it. Push and hold on the 0.xml and choose the option to open in text editor.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
I did it once where just changed it and rebooted didn't stick then rebooted did it again and deleted it stuck so idk

---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------

When you see the file hold down on it then click in right corner of screen menu option then open in text editor
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
That's what t is you need to have the custom kernel as well. Can someone tell me how to change the cid completely as well for the hell of it?
[Google Pixel XL Guides, News, & Discussion] psychatog64:
That idk didn't even try to do that
[Google Pixel XL Guides, News, & Discussion] coolhandz:
So i edited the 0.xml to say false, saved it, then deleted 0.xml.bak and rebooted.

Still greyed out. Now when i open 0.xml there is nothing there for oem.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
You need to toggle the switch if it says that now you should be good

---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------

That's what mine says now

---------- Post added at 07:48 PM ---------- Previous post was at 07:48 PM ----------

Screen shot your toggle
[Google Pixel XL Guides, News, & Discussion] coolhandz:
Here you go
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Flash the ex kernel then do it
[Google Pixel XL Guides, News, & Discussion] coolhandz:
I take it the ex kernel is ElementalX correct?
[Google Pixel XL Guides, News, & Discussion] cam30era:
Are these all the steps that you did?

Edit: don't use these steps. [MENTION=3566041]psychatog64[/MENTION] did something different.

Edit 2: removed
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Yeah just flash the ex kernel now and that's it I have it now.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
[MENTION=6207927]blueyes[/MENTION] so you think this can be done on a locked device using dirtycow?
[Google Pixel XL Guides, News, & Discussion] AllusionPDX:
This worked for me. Dont forget to DELETE the backup file.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Can some one tell me how to change the cid all the way please? I was able to get the toggle to unlock by modifying the file mentioned and then installing a custom kernel. Now I believe if I change my cid to the super cid and then start all over again it will be unlocked by default in the modified file.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Also I fastboot the kernel v8

No twrp then kernel then su then edit and yes ex is the elemental kernwl
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
I don't see the file there. Am I using a certain program to see it or? I even tried to pull it from adb and don't see it there either.
[Google Pixel XL Guides, News, & Discussion] cam30era:
Would you mind modifying and reposting the steps? So I don't have to guess.... Thanks.

Not for me, but or others who will be along shortly.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Mind you I was already unlocked, twrp installed, and rooted, on the WETA rom, I just flashed the ElementalX-PXL-1.00 via TWRP after doing the steps below and rebooted and I could toggle it at that point.

Screen shots attached on exactly what to do with root explorer. My oem lock line is gone now but you will.

From the menu choose open with text editor

Change true to false in OEM unlock line

Hit top right corner to save. Exit.

Delete 0.xml.bak

Reboot
[Google Pixel XL Guides, News, & Discussion] vacaloca:
The more interesting question now is what causes that setting to be populated in /data/system/users/0.xml in the first place on a VZW device, considering that the factory images are identical. CID? Something else?
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
It's got to be the cid and I would love to get an answer on what steps to take to get it changed to the super cid so I can test the theory by reinstalling everything.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Sorry I couldn't get back right away. We definitely need to look at how this is set. I always assumed it was Cid but was always told no. What probably wasn't looked at is how it seems to only be a policy restriction which could be based off Cid.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Add ro.boot.cid=11111111

To the END of your build.prop
[Google Pixel XL Guides, News, & Discussion] blueyes:
I Agree. Why you may actually need to boot wth some sort of net connection. Because in marlins many make files it says if v_1 do this , v_2 that. How else is the net manager to know without the NET
[Google Pixel XL Guides, News, & Discussion] blueyes:
Sweet. Ben wanting to tag this (f-u-vzw) thread with SOLVED. Lol

Before I jump the gun, how many have actually achieved it??
[Google Pixel XL Guides, News, & Discussion] blueyes:
I'm sure , I'll have to brush up in my skills for diPixel8's file, it's a elf file. Executable Linkable file for the most part not humanly readable. Easier to make one that open it. But I'll look. Never had any need to reverse engineer one. I have made a dirty cow myself to gain temp root. Fairly easy.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Attached screen shot.

Question though. I was able to edit the build.prop via root explorer and added that line and rebooted but it still shows the vzw cid even though that line I added is still in the end of the build prop.. Do I need to pull the file and then push it back via adb? Thanks bub.
[Google Pixel XL Guides, News, & Discussion] blueyes:
You remember me saying persists are like overrides.. My last line actually reads persist.boot.cid=111111111
[Google Pixel XL Guides, News, & Discussion] neilrl79:
I've been following the thread since the start, unfortunately I don't have my XL yet so I couldn't participate. I am assuming, once this is done it wouldn't survive a data wipe, would it?
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Argh thank you first of all but, I've tried adding it at the very end of build prop " ro.boot.cid=11111111 " saving it and deleting the bak file and adding it at the end of the build properties, instead of the very end of the build prop. I've just tried adding persist.boot.cid=11111111, in all three spots in the build.prop one at a time of course and nothing is working there. I've tried adding persist.ro.boot.cid=11111111 every where as mentioned as well. I still return ro.boot.cid=vzw_001 after rebooting and checking it. My guess is there are three steps to doing this and I only have one.

---------- Post added at 10:36 PM ---------- Previous post was at 10:26 PM ----------

How did you get your cid to change step by step please?
[Google Pixel XL Guides, News, & Discussion] blueyes:
Easiest way is to flash my modified boot
[Google Pixel XL Guides, News, & Discussion] blueyes:
I'll. Edit ElementalX's newest. It's twrp flashable and doesn't hurt root or twrp
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Would me pulling something from the google phone I have help?
[Google Pixel XL Guides, News, & Discussion] treIII:
With this being said do you have a Verizon sim installed?
[Google Pixel XL Guides, News, & Discussion] blueyes:
Has to be PERSIST, at end of build.prop:laugh:
[Google Pixel XL Guides, News, & Discussion] blueyes:
https://www.dropbox.com/s/dluw4y7ktqql8dt/ElementalX-P-1.00-modified.zip?dl=0
[Google Pixel XL Guides, News, & Discussion] treIII:
Do you mean in capitals?
[Google Pixel XL Guides, News, & Discussion] blueyes:
Honestly there's so many variables, if you willing pull as much information as you can. If you have both versions you'll know what differs. You could adb pull some of these folders we've been looking at. Just remove any personal info
[Google Pixel XL Guides, News, & Discussion] blueyes:
No. Lol. Being a smartass. Sorry. ;)
[Google Pixel XL Guides, News, & Discussion] treIII:
Have I seen this before
[Google Pixel XL Guides, News, & Discussion] blueyes:
Nope
[Google Pixel XL Guides, News, & Discussion] blueyes:
Persist
[Google Pixel XL Guides, News, & Discussion] psychatog64:
K flashed twrp rebooted to bootloader fastboot flash ex kernel reboot recovery flash su.zip reboot open root explorer go to data system users hold down on 0.XML click menu button too right corner open in text editor then change true to false in the OEM line then hit menu right corner save and exit then delete orginal named 0.XML.bak reboot
[Google Pixel XL Guides, News, & Discussion] blueyes:
Look at this mess. Got some of dePixel8 by readelf

https://www.dropbox.com/s/9cn4ts2aph8u89s/dePixel8.xml?dl=0
[Google Pixel XL Guides, News, & Discussion] blueyes:
Seems like everyone's all over the place. I'm getting lost. Who other than myself can now use the toggle? What do you think did it? We need to get this organized. Lol
[Google Pixel XL Guides, News, & Discussion] psychatog64:
I can only change true to false in 0.xml folder with a custom kernel already installed
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Yes I do. I tried every way possible up to and including the way blue eyes stated and I still return the vzw cid.

---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------

OK, I was able to and I posted what I did. I simply flashed the element kernel and changed oem unlock flag to false. That's all that needs to be done, two simple steps.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
No custom kernel needed just need to change that in 0.xml reboot and a simple prop change.

I'd they don't close this in the Dec. update looks like bootloader unlock can be achieved as long as tmp root exploit can be found.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Yes you have to have a none permissive or permissive whatever kernel installed because it didn't work until I installed the element kernel.

Flash Depixel8 to unlock bootloader

Flash TWRP

Flash SuperSU via TWRP

Flash ElementalX-PXL-1.00 via TWRP

Once booted install Root Explorer.

Using Root Explorer, go to Data/System/users and long press the file 0.xml

From the menu choose open with text editor

Change true to false in OEM unlock line

Hit top right corner to save. Exit.

Delete 0.xml.bak

Reboot

Those are the steps from the beginning to the end from a non unlocked bootloader.
[Google Pixel XL Guides, News, & Discussion] treIII:
Root and permissive kernel
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Ok so we know exactly what to do to get this activated now the cid part please. Sorry I see how now at the top thank you blue eyes.

Again just so we don't lose the valuable information on getting this toggle to work here it is from the beginning to the end from a non unlocked bootloader.

Flash Depixel8 to unlock bootloader

Flash TWRP

Flash SuperSU via TWRP

Flash ElementalX-PXL-1.00 via TWRP

Once booted install Root Explorer.

Using Root Explorer, go to Data/System/users and long press the file 0.xml

From the menu choose open with text editor

Change true to false in OEM unlock line

Hit top right corner to save. Exit.

Delete 0.xml.bak

Reboot

Also setting it the way you stated above blue eyes, see attached screen shot and even after flashing your modified element kernel I still have the vzw cid see second attached screen shot. I am 100% able to toggle oem unlock bootloader though at this point based on the simple method listed above, see third attached screenshot.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
It has nothing to do with a permissive kernel, what the custom kernel does is mask that the bootloader is unlocked. The option is actually supposed to be greyed out after its been enabled but I believe is supposed to be greyed out toggled on. You can achieve the same effect of masking the fact the device is unlocked already with a prop change.

The prop change wouldn't be needed on a locked devices what this means is as long as a privilege escalation exploit is available that can modify that file enabling OEM unlock is possible.

I already did it no custom kernel no twrp just root and prop rest

When the bootloader being unlocked isn't masked:
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Ok whatever, you're right I am wrong " we're both right " but still it stands we are able to do it the way I mentioned. Just like blue eyes did. His is setup the same way I was able to get mine setup which is that it is toggle-able.

Now I again ask why is it that my cid is not changing when I set it to exactly what blue eyes is setting his build prop to? See attached pictures.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Blueyes and I put our cid in the cmd file of the boot image, so it was essentially flashed in.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
I would thank you but I'm out of thank yous for the day. Which file is it please and where do you put the line in, and what is the exact line to add in please? I tried the build.prop and that is not working.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
It's not about being right or wrong, first if I offend you in some way i'm sorry was not my intention.

I was simply explaining what it was that the custom kernel was actually doing to make it so after the 0.xml modification the option to be able to toggle the oem unlock work while informing users that those that didn't yet want to flash a custom kernel or TWRP that there was still a way to archive it this.

personally i recommend editing the cmdline of the boot.img

androidboot.cid=11111111 androidboot.oem_unlock_support=1 androidboot.verifiedbootstate=green androidboot.selinux=permissive

example before:

console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=sailfish user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 cma=32M@0-0xffffffff buildvariant=user veritykeyid=id:7580d366b6e2804279fd88e290c82a5a7d5dd610

example after:

console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=sailfish androidboot.cid=11111111 androidboot.oem_unlock_support=1 androidboot.verifiedbootstate=green androidboot.selinux=permissive user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 cma=32M@0-0xffffffff buildvariant=user veritykeyid=id:7580d366b6e2804279fd88e290c82a5a7d5dd610

[MENTION=6207927]blueyes[/MENTION] wonder if this would work on other devices with policy based locks like this.

---------- Post added at 07:36 PM ---------- Previous post was at 07:12 PM ----------

[MENTION=6207927]blueyes[/MENTION] I believe OobConfig is what is setting the policy not sure what it uses to determine to enable that policy restriction.

did you see my explanation here : http://xdaforums.com/showpost.php?p=69718421&postcount=301
[Google Pixel XL Guides, News, & Discussion] blueyes:
Are you guys adding the second, more critical line, with the persist value?
[Google Pixel XL Guides, News, & Discussion] blueyes:
Those two line go in prop
[Google Pixel XL Guides, News, & Discussion] blueyes:
What's the boot state green line achieve?
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
If it is in the cmdline it makes the device think the bootloader is locked I don't think it affects Android pay but green is the state the device should be in when the bootloader is locked and booting a signed image.

Out side of root I had no modifications to my device other that editing 0.xml then used the resetprop tool to set ro.boot.flash.locked 1 to trick developer options to thinking the bootloader was locked.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
This is what I have blue eyes. see attached screen shot. I rebooted after setting the second line mentioned in build prop and I still get the cid vzw...

Sorry if I got offended social. Thank you for your help.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Your phones manager hasn't yet made a persist flag in /data/property . Make it yourself.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Sweet. Nice we got this mess knocked out. Tempted to send Verizon a message, "Nice try!".

Although the files in system/users/0.xml , for me say nothing about being oem locked or unlocked. And I never touched those. Not directly anyway.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Again, thank you seriously. It didn't work though. See attached. That's after rebooting.

Side question, if we get this to work on changing the cid, does it stick after flashing stock as well or does it change back to vzw?
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
I still intend to track what it is that is enabling the policy to get set in the first place but it's nice to know how to set it for now.
[Google Pixel XL Guides, News, & Discussion] neilrl79:
I asked before but the thread has been moving pretty fast, so for give me for asking again...

Once you've achieved being able to toggle OEM unlock and gotten it to show as super cid, what would happen after flashing a factory image and relocking the bootloader? I'm assuming you'd you'd be back to square one, needing depixel8 to unlock?
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Stock will revert it, there is to tool to set it in the bootloader yet.

---------- Post added at 02:26 AM ---------- Previous post was at 02:22 AM ----------

If the toggle is enabled it should remain enabled unless you do a factory rest from in android settings, I'll be testing in a couple of hours.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Nah, the cid change is just a cosmetic additional. Although we can print the supercid from a terminal, that's as far as it goes. Run fastboot oem getcid and you, me, and everyone else will get vzw_001
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
I've flashed the stock image using flash.all and it doesn't, relock your bootloader. Apparently the super cid will, change back to normal vzw... though.

That's what we need is a tool to change it in the bootloader, that makes sense.

I give up on changing the cid for now myself as I can't seem to get it to stick no matter how many things I do and like you guys said it will go right back to vzw unless we mod it in the bootloader anyway at this point.

Thank you, all of you. I'll give more upvotes tomorrow.
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
So trying to follow along but a lot of this is over my head..... This is not a way to unlock permanently like a play store pixel correct? It just removes the toggle from being greyed out?
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Something you did triggered a change in it and once it goes false there is no point in having it there I assume.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Had another Bliss dev try it, failed first, but after flashing my modified ElementalX it worked
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
still need to test but as long as you don't disable the toggle / perform a factory reset from within android settings you should be able to lock your device and still unlock it later.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Couldnt of done it without the guys who have been working in this thread, teamwork rules...