I have a feeling the pixel is going to be like the htc one m9 where we all had to ship our phones to someone with an java card / clip to get s-off... already seeing that the group says they'll be supporting the pixel (it is an htc phone afterall)... .cannot wait for more info on that one..
Except Pixel doesn't have the same unlock mechanism as other HTC phones, and the S-XXX flag is more or less useless, it appears to be set to S-OFF on the device, but device reads it as S-ENG
Step 1: Temp root
Step 2: Change buildprop
Step 3: enable oem unlocking from settings (or enable it in buildprop)
Step 4: fastboot oem unlock(i've read somewhere that there is a new command that replaces this)
Step 5: have fun
Step 1: Temp root
Step 2: Change buildprop
Step 3: enable oem unlocking from settings (or enable it in buildprop)
Step 4: fastboot oem unlock(i've read somewhere that there is a new command that replaces this)
Step 5: have fun
10-25 22:11:19.754 4025 4044 W OobConfig: Device configuration has not been retrieved.
10-25 22:11:23.663 4217 4234 V OneTimeService: Device Policy is owner: false, is admin:false
10-25 22:11:23.663 4217 4234 V OneTimeService: Disabling Device Policy, as it is not in use.
10-25 22:15:02.363 1109 1109 I DevicePolicyManagerService: Set ro.device_owner property to false (**DISREGARD** this one is present on GS variant**)
I have been cracking away at this today. I own both the GS variant and VZW variant Pixel.
1. SetupDevice is installed on the VZW variant, not on the GS variant
2. SetupDevice is OobConfig, OobConfig is present on both variants in /system/priv-app
3. On boot for the VZW variant I get a logcat entry for OobConfig in which is says something to the effect of "allow OEM_UNLOCK, false".
I am wondering if we can force our own config to be downloaded, or if we can decompile the apk ( I have been trying all day), modify, and install, thus replacing the current version.
Let me know what everyone thinks.
David
Now you won't be able to sleepI found this also
GS - "adb getprop" - [ro.boot.cid]: [11111111]
[ro.boot.oem_unlock_support]: [1]
[ro.oem_unlock_supported]: [1]
[sys.oem_unlock_allowed]: [1]
VZW - "adb getprop" - [ro.boot.cid]: [VZW__001]
[ro.boot.oem_unlock_support]: [0]
[ro.oem_unlock_supported]: [1]
[sys.oem_unlock_allowed]: [0]
I am assuming at this point that the "ro.oem.unlock" prop refers to carrier locked. I had a list minute idea to check before bed.
I have been cracking away at this today. I own both the GS variant and VZW variant Pixel.
1. SetupDevice is installed on the VZW variant, not on the GS variant
2. SetupDevice is OobConfig, OobConfig is present on both variants in /system/priv-app
3. On boot for the VZW variant I get a logcat entry for OobConfig in which is says something to the effect of "allow OEM_UNLOCK, false".
cc @beaups
Its over, this is @KrAsH86 's verizon pixel
https://twitter.com/firewaterdevs/status/791116513939902465
long shot but do you think a similar implementation is possible on other veeizon devices?
of course assuming they have some of the same restrictions/blocks in place?
edit: specifically the verizon lg v20..
Wonder if Darth or MTM share this sentiment. Hell Jcase who is a senior moderator is the one who cracks them. Thoroughly confused. Are we being punked?
They must have been threatened by Google or Verizon.