yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
The adb shell getprop ro.boot.cid says

:\adb>fastboot getvar cid

getvar:cid FAILED (remote: unknown command)

finished. total time: 0.052s

fastboot while in fastboot bootloader mode states

\adb>fastboot oem readcid

...

FAILED (remote: unknown command)

finished. total time: 0.012s

I installed the cid getter which line tells me the cid so I can find it easier because there is a lot of stuff it spits out and I don't see it sticking out like a sore thumb here?
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
[MENTION=6207927]blueyes[/MENTION] every time I modify the boot.img and try to test it with fastboot boot boot_a.img it fails to boot and boots me back into fastboot?
[Google Pixel XL Guides, News, & Discussion] death2all110:
CID should be in red letters across the top.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
There's nothing across the top in red or down through any of the information it spits out either.

---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------

When in OS not in bootloader mode I tried the adb read command and it returned what I stated, when in bootloader mode, I ran the fast boot command and it returned what I stated. Don't believe I'm confusing anything here.

My bad, I was wrong I got it.

C:\adb>adb shell getprop ro.boot.cid

VZW__001

C:\adb>

Also the google one,

C:\adb>adb shell getprop ro.boot.cid

11111111

C:\adb>

I know where this is headed by seeing the difference in the cid.

We just need to write the cid on the vzw one to be 11111111..
[Google Pixel XL Guides, News, & Discussion] jjayzx:
I have mine showing all 1's but it's not actually written in cause it comes right back if I remove the command.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
I couldn't edit in pictures.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
I tried writing the cid using the fastboot command while in bootloader mode and it failed as an unrecognized command.

My google pixel I can just simply turn on oem unlock in developer options. I can't figure out how to write the cid though on my verizon version.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
I'm confused all I had on my phone was root ex kernel and twrp edited the 0.xml file deleted orginal and rebooted I didn't have to set any permissions or reset selinux or whatever and mine worked np how is that so?
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Can't speak for twrp, I know that not all root file managers restore permissions, and some file managers don't restore the selinux context, and some do it automatically. I can only speak to what caused my device to boot loop, after modifying the 0.xml
[Google Pixel XL Guides, News, & Discussion] raycaster3:
I know what it was and why, I was just putting the information out there in case anyone else sees it and wk sees if that means something is amiss, which it isn't.

Device memory as in sdcard? Nope. System? Not that either.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Ah OK ic thank you for clearing that up I was gonna say lol like how the hell did I figure this out and not have to do any of that when I fist posted how I got it working lmao
[Google Pixel XL Guides, News, & Discussion] blueyes:
If you flashed the modified ex, then you booted up selinux permissive mode.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Never flashed the modded one yet

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

I have it downloaded but never flashed it

---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------

Only kernel I had was the normal ex kernel v 0.8 at the time of doing this
[Google Pixel XL Guides, News, & Discussion] TechBSwift:
other than having access to the unlock slider, what's the long term benefits of this?
[Google Pixel XL Guides, News, & Discussion] blueyes:
Benefit from now , if you wanted or needed, you can lock and unlock the bootloader using only fastboot. Just as if you bought it from Google. You can send Verizon a good "nice try" message.
[Google Pixel XL Guides, News, & Discussion] cam30era:
[MENTION=4821597]social-design-concepts[/MENTION],

I ran the test. After flashing the stock V boot.img and relocking the bootloader, the unlock toggle did NOT persist. In case anyone else was wondering.
[Google Pixel XL Guides, News, & Discussion] TechBSwift:
So here's my question, if I unlocked the bootloader, then enable and slide this unlocked using this method. What happens if I factory flash google firmware, while wiping my date. Will I be able to go into developer settings and unlock using the unlock slide? I'm trying to determine if we ever make this phone a true google 'like' version, or will will always return back to verizon.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Yep enabling the toggle has no real benefit then , confirmed that device gets locked down again after re-locking so don't lock your bootloader ever. back to figuring out how to prevent VzW from getting device ownership and loading that policy.
[Google Pixel XL Guides, News, & Discussion] cam30era:
Same result for me. Agree with you conclusion, as things stand now.
[Google Pixel XL Guides, News, & Discussion] DA6030:
Access to persist and bootloader variables

[MENTION=4821597]social-design-concepts[/MENTION] [MENTION=451347]blueeyes[/MENTION] [MENTION=3953174]jjayzx[/MENTION]

Out of curiosity, have any of you run the fastboot flashing unlock_critical command? (as opposed to fastboot flashing unlock)

I only just remembered this might exist on the Pixel, and might open more doors for us (e.g., to write values in fastboot).
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
I'm going to have to do it again now lol, but didn't really test anything bootloader related before, I have found my self in QCOM Download Mode a couple of times that freaked me out the first time.
[Google Pixel XL Guides, News, & Discussion] treIII:
I have used this command. It brings up bootloader is unlocked if I recall
[Google Pixel XL Guides, News, & Discussion] psychatog64:
There talking about while we have access to the toggle have you ran it since applying the 0.xml edit?
[Google Pixel XL Guides, News, & Discussion] treIII:
No I have not. I misunderstood. But yes I've ran it since bing unlocked without the toggle being usable.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Sorry, tied up with the kids. Dude I ran every command that bootloader printed on a grep. Locking it was just one of many in several useless instructions I found. Locking made sense if was butt hurt upset over security policies. Wasn't remotely afraid of it not relocking. Unlock_critical is useless , it differs in it supposedly allows modifying the bootloader itself. Another angler has is unlock-go , it just quickly reboots after unlocking.

I was running the 7.1.1 prev with the pixel mods. The mod changed device model & model number. It fools the play store into thinking it's indeed a Marlin. Hell angler thought it was a pixel. Booted up "Welcome to your Pixel XL".

Was unlocked, rooted , permissive. Bored with it, flashed a cm based n7 rom. Clean.

That's the end of the story. Long lost 6P was murdered by cm. CM continues to be one of the very few that don't adjust the security settings. They force encryption, just like stock. The combo of it being so far to the side of zero selinux it didn't know it's name to all the way the other direction with encryption and dm-verity is the only thing I can figure.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Never had any issues with it before. Love it. Funny how I only found out about all its defects after it goes south.

http://xdaforums.com/nexus-6p/help/bootloop-google-logo-plz-help-t3496692

http://xdaforums.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518

http://xdaforums.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709

[Announcement] TWRP 3.0.2-1 has a fatal bug!… | Huawei Nexus 6P

http://xdaforums.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
[Google Pixel XL Guides, News, & Discussion] jjayzx:
I think I tried it before the 0.xml edit. I tried a lot of different commands, even made up ones, lol.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
My daydream head set came :)
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Mine should be here any day now! Congrats!
[Google Pixel XL Guides, News, & Discussion] treIII:
What do I need to flash to get stock recovery back? I'm on the V build but I am rooted and had ex kernel. I've already flashed system and system other.img and the bootloader from the V build. How do I open up the stock zip from Google and stop it from wiping my data of I flash the factory V image? Thanks
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Edit the flash-all and remove the -w,

To get recovery back you need to flash the boot.img to both slots to be safe
[Google Pixel XL Guides, News, & Discussion] treIII:
How do I remove the w? Thanks
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
I've edited the -w in the past and have never successfully flashed the flash-all script with my Mac. I've always had to do the radio, system, and boot separately.
[Google Pixel XL Guides, News, & Discussion] treIII:
I flashed all this separatelyand phone keeps bootlooping. I don't want to lose my data
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
I've never really had a successful save from a bootloop issue without wiping and reflashing. Good news is mostly everything I need gets restored through Google.... Just slowly. And I have to sign back into every app that has a login
[Google Pixel XL Guides, News, & Discussion] treIII:
I don't want to lose my text messages. Those don't get restored do they?
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
I use Verizon messages strictly for that purpose. It's not the best app, but it works over wifi on Verizon and it saves 3 months of text messages and restores them
[Google Pixel XL Guides, News, & Discussion] treIII:
My phone just went to the circle data screen and said it was erasing out of nowhere. Dangit I lost mybtexts
[Google Pixel XL Guides, News, & Discussion] cam30era:
If one is using the flash-all script, why is it necessary to flash the boot.img separately?
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
They don't, it was 2 questions, how to restore factory recovery, and how to flash the whole package with out having data wiped.
[Google Pixel XL Guides, News, & Discussion] cam30era:
Ah. Got it. Thanks.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
The phone gets real hot real quick, and not a lot of content yet,
[Google Pixel XL Guides, News, & Discussion] treIII:
I and side loaded the latest update from V to 26J and I set the file in data system user and I can no longer toggle OEM unlocking as it now looks like this and yes I removed the .bak file and have rebooted twice
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
My brother's s7 had the same issue at first and they had to patch it and it still has some issues. The content part sucks to hear. Hope that changes.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Flash the custom kernel yet?
[Google Pixel XL Guides, News, & Discussion] treIII:
I didn't know there was an updated custom kernel for the new build. Lol. My phone is also encrypted now
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Not sure there is but the custom kernel was masking the bootloader being already unlocked which was why the toggle was functional.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Wasn't technically a custom kernel just for this just flash ex kernel people said you can still but will loose the rise to wake feature only until ex updates kernel to next version though

---------- Post added at 06:04 AM ---------- Previous post was at 05:59 AM ----------

I would edit thread to not reflect solved in the sense that this didn't really give any benefit to us other then just officially having access to whole phone should only get the true label of solved when and if we can make it stick permanently just my opinion
[Google Pixel XL Guides, News, & Discussion] blueyes:
Stock boot image put a double whammy on you. It's going to encrypt every time. Unless you edit the fstab

.marlin and fstab.recovery. Both have the "forecencryption" flag.
[Google Pixel XL Guides, News, & Discussion] blueyes:
I was thinking about editing the solved, just not yet sure how I want it to reflect. We manages to duplicate the switch becoming functional, but it turned out we didn't duplicate the system configuration. My device has been modified somehow, it's continuing to set up as a google carrier would. Surviving several resets flashing the factory images. I have not modified the 0.xml on any of the flashes, nor have I modified it at any point. I've never touched that file. Never lost the switches functionality. I've sent as far as locking the bootloader, booting up locked before unlocking it back in fastboot. I definitely was optimistic we'd found a fairly easy way to get it done. Have to work backwards from that file until getting to something permanent.

I'm positive it'll happen.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Happy Thanksgiving, is their somewhere we can chat in real time at some point, have a couple ideas to run by you.
[Google Pixel XL Guides, News, & Discussion] treIII:
Anybody know what persist radio rate adapt enable = 1 may do? Possibly throttling data speeds?
[Google Pixel XL Guides, News, & Discussion] lucky_strike33:
Try it and report back [emoji3]
[Google Pixel XL Guides, News, & Discussion] treIII:
It already says that in the build.prop that's why I posted a screenshot of the build prop
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
still no closer to figuring out what make a vzw pixel not a gs pixel :(
[Google Pixel XL Guides, News, & Discussion] treIII:
It's the Cid. I dont have the knowledge to change it but it's linked to that as it is firmware on other HTC phones. If someone figures out how to change the CID and it doesn't remove the phone thinking it's a Verizon model id be very surprised
[Google Pixel XL Guides, News, & Discussion] Fate0n3:
I also would like to know this mine is grayed out but it says bootloader is already unlocked grayed out below it. I wasn't for sure if it matters.
[Google Pixel XL Guides, News, & Discussion] Reechings:
I don't get it, every time I restore with google all my apps are just like I just installed them and I have to set up the app preferences again. Thank God for titanium backup.
[Google Pixel XL Guides, News, & Discussion] 318sugarhill:
Well yeah.... But restoring data in titanium has caused me a set of problems in the past. I still don't understand why android doesn't have a computer backup system the way itunes does for iPhone. ITunes is horrid, but for that one aspect it's useful
[Google Pixel XL Guides, News, & Discussion] blueyes:
Certainly, send me your Gmail if you want to use hangouts. Or pm me the alternative.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Explains why the volte provisioning flag won't stay on. Verizon sim connected , but GCC cant figure this out so it assigned the default "Preferred System".
[Google Pixel XL Guides, News, & Discussion] psychatog64:
So there's no way we can compare a Google xl on vzw with a vzw xl and see exactly what is causing the restriction policy to be written to the device and go from there to try and change it permanently?

---------- Post added at 01:33 AM ---------- Previous post was at 01:23 AM ----------

Or the key has to do with firmware p your edits and then booting up with a non Verizon sim with your edits

---------- Post added at 01:36 AM ---------- Previous post was at 01:33 AM ----------

Blueyes I would like to flash back to p and do all the edits in order to the best you can remember and check after each edit until it happens or doesn't so when you have time would like to work with ya doing everything on p and see what we can come up with
[Google Pixel XL Guides, News, & Discussion] DA6030:
Has anyone checked if Google Store devices also have data/property/persist.sys.oem_unlock_allowed? I'm inspired that at least part of the policy is stored on the data partition.

[MENTION=451347]blueeyes[/MENTION], in attempt to recreate the unique situation you have, have you only tried cloning files from boot and system partition, or have you tried the policy files on /data as well?

In other words, rather than trying to trick the device into getting a different policy file from the server, just overwrite the policy file directly (using adb restore and adb push to get them onto a non-rooted target device). Certainly that policy runs the risk of getting overwritten by the server, but if restoring it is easy via adb, that might be good enough for most people.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Pretty sure policy is on the phone from the get go. What we need to figure out is what does it use to enact it, like Cid or imei.
[Google Pixel XL Guides, News, & Discussion] neatojones:
Can someone who uses the mod listed on the first page but hasn't edited their prop files otherwise (besides) [MENTION=6207927]blueyes[/MENTION] (who used another method) show their getprop listing for [persist.sys.oem_unlock_allowed] ?

I am hoping it will give a clue if it still says 0. I think the problem is that we need to get the change to the bootloader unlock status inside the "persist" partition. My thought is that if you can get it to be unlocked here, it *should* stay even after a flash because system updates *shouldn't/won't* modify that partition.

Could someone give me this readout on your device?

# ls -al /dev/block/platform/soc/624000.ufshc/by-name

I think we are most likely looking for the location of whatever is called "persist"

Alternatively, I found that on a prior Nexus at least, the unlock status persists at the location of the FRP and is found here at this location: ro.frp.pst

According to our getprop from earlier in the thread, that should be here:

/dev/block/platform/soc/624000.ufshc/by-name/frp

My working theory here is: This isn't a problem with the prop setting or the missing file at /data/property/persist.sys.oem_unlock_allowed. This just reflects whether the settings are true or not on bootup. If we can copy the persistent partition, it may allow us to have the persistent unlock. And, having the correct persist information will change those settings. In other words, you can trick the getprop printout, but that doesn't add the appropriate persistent files, which is what we need to do.

I'm getting my device in a few days and can test it then if no one else gets a chance first.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Persist is sdd3
[Google Pixel XL Guides, News, & Discussion] BakedTator:
I'm running weta rom with Franco kernel and was able to get my switch to be toggled using the method in the op...I didn't mod the kernel or anything...and given the fact that the xml file get edited after every boot, this should persist with updates as well...not sure if it will survive a data wipe though

Did this on 5" Verizon pixel
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
if your running the Franco kernel guess what you modified the kernel, I think i could explain this a million times but here goes again, the reason the toggle becomes functional after making the changes to the 0.xml file is because the custom kernels used to get android pay working mask that the bootloader is already unlocked, in android 7.1 it is supposed to be grayed out when the bootloader is unlocked but it's suppose to be grayed out in the toggled on position.

i'm actually alot more familiar now with the parts of the OS that manages this function with the exception of what actually lifts the restriction, the restriction looks to actually be enabled by default and then is removed.

We really need to see cat /proc/cmdline from a GS pixel,
[Google Pixel XL Guides, News, & Discussion] BakedTator:
Franco kernel dont have the safety net patch (as far as I know) like ElementalX...

And what I said was I myself, didn't modify the kernel in the way the op said he had to get his toggle working

Next question, could a modified file be made for this with locked bootloader and this be push through abd? Just a thought
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
only system apps with UserManager permissions can touch that restriction, but until google changes how the oem unlock restriction is managed any future exploit that can modify that file directly could be leveraged to enable oem unlocking in the future. sorry about the confusion i took your didn't modify comment the wrong way.

On a side note i found a way to bypass FRP on the Pixel's waiting to see if it still works after the next update to report it to Google and share.
[Google Pixel XL Guides, News, & Discussion] BakedTator:
It's all good man...

I went to proc/cmdline but I can't edit it...says 0 bytes file size so I'm guessing it's symlink'd to the /proc folder but not sure...I see something in it that suggests it could also assist in keeping the bootloader locked
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
you have to be root to read it, the bootloader passes some information to the OS through the cmdline
[Google Pixel XL Guides, News, & Discussion] BakedTator:
I'm rooted but can't edit the file...it's odd
[Google Pixel XL Guides, News, & Discussion] lucky_strike33:
Did you allow superuser to edit or did you even choose text editor??
[Google Pixel XL Guides, News, & Discussion] BakedTator:
Of course I chose text editor... Been doing this for quite some time...I think it's symlink'd elsewhere but it says nothing of where

I edited it then save it but it doesn't change or make a .bak file of the original
[Google Pixel XL Guides, News, & Discussion] BakedTator:
If you look at cmdline, it has 0 file size but there is a line that says

androidboot.oem_unlock_support=0

I think if that could be changed to =1, then the unlock switch may persist and allow for the bootloader to be unlocked without using depixel8

Could someone with a Google store Pixel or xl post these same screenshots so we can see if there is a difference