Problems signing/recovery Pixel Experience for Oneplus Nord #186

MrDuartePT · 2023-10-09T07:30:18Z

I having problems signing the PE OTA image for Oneplus Nord this means i will need to use another custom rom our i can solve it by build the rom and enable vbmeta headers (if possible)

➜ Oneplus ./avbroot ota patch
--input PixelExperience_Plus_avicii-13.0-20231003-1348-OFFICIAL.zip
--privkey-avb ./custom-keys/avb.key
--privkey-ota ./custom-keys/ota.key
--cert-ota ./custom-keys/ota.crt --rootless
[] Replacing zip entry: META-INF/com/android/otacert
[] Copying zip entry: apex_info.pb
[] Copying zip entry: care_map.pb
[] Patching zip entry: payload.bin
[] Extracting from original payload: vbmeta
[] Extracting from original payload: vbmeta_system
[] Extracting from original payload: recovery
[] Patching boot images: recovery
[*] Patching vbmeta images: vbmeta
Error: Failed to patch OTA zip

Caused by:
0: Failed to patch payload: payload.bin
1: vbmeta header flags disable AVB 0x3

pascallj · 2023-10-09T08:30:52Z

Hi, please have a look at #60 and Clearing vbmeta flags.

This might work for you as well.

MrDuartePT · 2023-10-09T09:12:35Z

Ok I will test later and let you know.
Thanks for the fast reponse👍

MrDuartePT · 2023-10-09T12:51:24Z

Can confirm that it works, thanks.

MrDuartePT · 2023-10-09T12:53:59Z

@pascallj this is kinda of topic but i also need to patch my twrp/OrangeFox Recovery?

chenxiaolong · 2023-10-09T16:04:44Z

I wouldn't recommend using a custom recovery if possible. Almost anything you flash from a custom recovery would make the partition signatures invalid.

However, if you would like to do so anyway, you can add --replace recovery /path/to/custom/recovery.img to the patch command.

MrDuartePT · 2023-10-09T16:10:41Z

Well i will always sign my ota and use adb sideload but i would like to still use OrangeFox. But I will see probably i will use the recovery that is included with Pixel Extended

MrDuartePT · 2023-10-13T16:46:24Z

@chenxiaolong I getting a strange behaviour if a flash the extracted files the device boot fine on PE but the recovery give me a black screen.
Both OrangeFox as the Pixel Experience recovery didnt try twrp but if a flash the unsigned recovery image it boots in to recovery fine

MrDuartePT · 2023-10-13T17:09:18Z

This output is expected [the frist line is equal to the Readme just worry about the /system]? (using unsign recovery and everthing else sign):

[    2.449171] (1)[1:init][    2.449167]@1 init: [libfs_avb]Returning avb_handle with status: Success
[    2.450299] (1)[1:init][    2.450295]@1 init: [libfs_avb]: Error verifying vbmeta image: OK_NOT_SIGNED
[    2.450335] (1)[1:init][    2.450332]@1 init: [libfs_avb]Found unknown public key used to sign /system
[    2.450351] (1)[1:init][    2.450348]@1 init: [libfs_avb]Returning avb_handle for '/system' with status: VerificationError
[    2.451536] (1)[1:init][    2.451530]@1 init: [libfs_avb]Built verity table: '1 /dev/block/dm-7 /dev/block/dm-7 4096 4096 234780 234780 sha1 92f8d04b6b85b99c10ad1784381cb974896206d1 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-7 fec_roots 2 fec_blocks 236631 fec_start 236631 restart_on_corruption ignore_zero_blocks'
[    2.465337] (3)[1:init][    2.465330]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-8 /dev/block/dm-8 4096 4096 86750 86750 sha1 19daf5cd7bb360889c3c72b9bb6f4ba0d23ce0fb e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-8 fec_roots 2 fec_blocks 87435 fec_start 87435 restart_on_corruption ignore_zero_blocks'
[    2.470639] (3)[1:init][    2.470632]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-6 /dev/block/dm-6 4096 4096 407562 407562 sha1 74905fd3c824dbbca500138f68a615ddd0365ee4 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-6 fec_roots 2 fec_blocks 410773 fec_start 410773 restart_on_corruption ignore_zero_blocks'
[    2.475746] (3)[1:init][    2.475740]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-9 /dev/block/dm-9 4096 4096 209646 209646 sha1 3d97cb5d9f16a3d9ce2c2056ab8b3a2050646e5f e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-9 fec_roots 2 fec_blocks 211298 fec_start 211298 restart_on_corruption ignore_zero_blocks'
[    2.481295] (3)[1:init][    2.481288]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-5 /dev/block/dm-5 4096 4096 15444 15444 sha1 7a8c095c71489e62b242b7b137d099d1f36a4f68 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-5 fec_roots 2 fec_blocks 15566 fec_start 15566 restart_on_corruption ignore_zero_blocks'```

chenxiaolong · 2023-10-13T22:02:00Z

I getting a strange behaviour if a flash the extracted files the device boot fine on PE but the recovery give me a black screen.
Both OrangeFox as the Pixel Experience recovery didnt try twrp but if a flash the unsigned recovery image it boots in to recovery fine

Hmm, that's weird. Can you post the command you're running to patch the ROM + recovery? I'll test it on my end and compare the signed and unsigned recovery images to see if there's something weird going on. I can't really think of anything obvious--the only change avbroot does to that partition is update the certificate inside the recovery ramdisk's system/etc/security/otacerts.zip and then sign it.

This output is expected [the frist line is equal to the Readme just worry about the /system]? (using unsign recovery and everthing else sign):

Is there any chance that the recovery might be modifying /system? Even mounting it as rw once will break the signatures. I've also seen some ROMs before that modify /system during boot. Hopefully that's not the case here because that'd be fundamentally incompatible with avbroot.

The signatures for all partitions seem to be valid when running:

avbroot ota verify -i PixelExperience_Plus_avicii-13.0-20231003-1348-OFFICIAL.zip

(If you want to run this command against a Pixel Experience OTA, you'll need #190 (download), which isn't in a stable avbroot release yet.)

Previously, the AVB `algorithm_type` field was unconditionally being set to a value that is compatible with the AVB private key. However, for indirectly-signed boot images, the value should be set to `None`. Pixel bootloaders accept the incorrect value, but other devices' bootloaders might not. Issue: #186 Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>

MrDuartePT · 2023-10-13T22:22:43Z

I getting a strange behaviour if a flash the extracted files the device boot fine on PE but the recovery give me a black screen.
Both OrangeFox as the Pixel Experience recovery didnt try twrp but if a flash the unsigned recovery image it boots in to recovery fine

Hmm, that's weird. Can you post the command you're running to patch the ROM + recovery? I'll test it on my end and compare the signed and unsigned recovery images to see if there's something weird going on. I can't really think of anything obvious--the only change avbroot does to that partition is update the certificate inside the recovery ramdisk's system/etc/security/otacerts.zip and then sign it.

This output is expected [the frist line is equal to the Readme just worry about the /system]? (using unsign recovery and everthing else sign):

Is there any chance that the recovery might be modifying /system? Even mounting it as rw once will break the signatures. I've also seen some ROMs before that modify /system during boot. Hopefully that's not the case here because that'd be fundamentally incompatible with avbroot.

The signatures for all partitions seem to be valid when running:
avbroot ota verify -i PixelExperience_Plus_avicii-13.0-20231003-1348-OFFICIAL.zip
(If you want to run this command against a Pixel Experience OTA, you'll need #190 (download), which isn't in a stable avbroot release yet.)

For flash I just using the same script of the readme I unpackaged the file using avbroot and then flash everything I will try again tomorrow but this time flash both particion a and b

Output of the command:

[WARNING] Whole-file signature is valid, but its trust is unknown
[*] Verifying payload
[*] Extracting partition images to temporary directory
[*] Extracting from the payload: abl, aop, bluetooth, boot, devcfg, dsp, dtbo, featenabler, hyp, imagefv, keymaster, logo, modem, odm, product, qupfw, recovery, storsec, system, system_ext, tz, uefisecapp, vbmeta, vbmeta_system, vendor, xbl, xbl_config
[*] Checking ramdisk's otacerts.zip
[*] Verifying AVB signatures
[WARNING] vbmeta has a signed vbmeta header, but parent does not list a trusted key
[*] vbmeta_system has a signed vbmeta header
[*] Verifying hash descriptor for: boot
[*] Verifying hash tree descriptor for: vendor
[*] Verifying hash tree descriptor for: system
[*] Verifying hash descriptor for: recovery
[*] Verifying hash tree descriptor for: product
[*] Verifying hash tree descriptor for: odm
[*] Verifying hash tree descriptor for: system_ext
[*] Verifying hash descriptor for: dtbo
[*] Signatures are all valid!```

MrDuartePT · 2023-10-13T22:28:37Z

I using the new version of avbroot you seen i gonna recreate the patched zips

MrDuartePT · 2023-10-13T22:38:37Z

I can also verify with new release the new patched zips have valid signatures:

➜  Oneplus ./avbroot ota verify --input PixelExperience_Plus_avicii-13.0-Orangefox-noroot.zip --cert-ota custom-keys/ota.crt --public-key-avb custom-keys/avb_pkmd.bin
[*] Verifying whole-file signature
[*] Verifying payload
[*] Extracting partition images to temporary directory
[*] Extracting from the payload: abl, aop, bluetooth, boot, devcfg, dsp, dtbo, featenabler, hyp, imagefv, keymaster, logo, modem, odm, product, qupfw, recovery, storsec, system, system_ext, tz, uefisecapp, vbmeta, vbmeta_system, vendor, xbl, xbl_config
[*] Checking ramdisk's otacerts.zip
[*] Verifying AVB signatures
[*] vbmeta has a signed vbmeta header
[*] vbmeta_system has a signed vbmeta header
[*] Verifying hash tree descriptor for: odm
[*] Verifying hash tree descriptor for: system
[*] Verifying hash descriptor for: dtbo
[*] Verifying hash tree descriptor for: system_ext
[*] Verifying hash descriptor for: recovery
[*] Verifying hash tree descriptor for: vendor
[*] Verifying hash descriptor for: boot
[*] Verifying hash tree descriptor for: product
[*] Signatures are all valid!
➜  Oneplus ./avbroot ota verify --input PixelExperience_Plus_avicii-13.0-OrangeFox.zip --cert-ota custom-keys/ota.crt --public-key-avb custom-keys/avb_pkmd.bin
[*] Verifying whole-file signature
[*] Verifying payload
[*] Extracting partition images to temporary directory
[*] Extracting from the payload: abl, aop, bluetooth, boot, devcfg, dsp, dtbo, featenabler, hyp, imagefv, keymaster, logo, modem, odm, product, qupfw, recovery, storsec, system, system_ext, tz, uefisecapp, vbmeta, vbmeta_system, vendor, xbl, xbl_config
[*] Checking ramdisk's otacerts.zip
[*] Verifying AVB signatures
[*] vbmeta has a signed vbmeta header
[*] vbmeta_system has a signed vbmeta header
[*] Verifying hash tree descriptor for: vendor
[*] Verifying hash tree descriptor for: system
[*] Verifying hash descriptor for: dtbo
[*] Verifying hash tree descriptor for: system_ext
[*] Verifying hash tree descriptor for: odm
[*] Verifying hash descriptor for: recovery
[*] Verifying hash descriptor for: boot
[*] Verifying hash tree descriptor for: product
[*] Signatures are all valid!
➜  Oneplus

MrDuartePT · 2023-10-13T22:46:13Z

Tomorrow I will flash and see if reports success and the recovery works.
Well probably if this go well I think I will try make a unofficial graphene os build for the Oneplus I have the vendor files from Pixel Experience that should work.

Previously, the AVB `algorithm_type` field was unconditionally being set to a value that is compatible with the AVB private key. However, for indirectly-signed boot images, the value should be set to `None`. Pixel bootloaders accept the incorrect value, but other devices' bootloaders might not. Issue: #186 Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>

chenxiaolong · 2023-10-13T22:57:58Z

When you try again tomorrow, can you use #191 (download)? It might potentially fix the signed recovery black screen issue.

MrDuartePT · 2023-10-13T22:59:35Z

Ok I will use. Thanks a lot for the help😄

MrDuartePT · 2023-10-14T12:46:51Z

well i getting black screen if i flash recovery using the script but using fastboot it work i gonna flash the recovery seperate via fastboot and see if stop getting black screen.

Edit: when flashed again both recovery still produce blackscreen but they boot with fastboot boot command
I can try use LineageOs recovery

MrDuartePT · 2023-10-14T13:12:04Z

dmesg produce with OrangeFox/PE recovery:

Nord:/ # dmesg | grep libfs_avb
[    2.105147] (3)[1:init][    2.105142]@3 init: [libfs_avb]Returning avb_handle with status: Success
[    2.106293] (3)[1:init][    2.106289]@3 init: [libfs_avb]: Error verifying vbmeta image: OK_NOT_SIGNED
[    2.106329] (3)[1:init][    2.106326]@3 init: [libfs_avb]Found unknown public key used to sign /system
[    2.106344] (3)[1:init][    2.106342]@3 init: [libfs_avb]Returning avb_handle for '/system' with status: VerificationError
[    2.107533] (3)[1:init][    2.107526]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-7 /dev/block/dm-7 4096 4096 234780 234780 sha1 92f8d04b6b85b99c10ad1784381cb974896206d1 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-7 fec_roots 2 fec_blocks 236631 fec_start 236631 restart_on_corruption ignore_zero_blocks'
[    2.120063] (3)[1:init][    2.120057]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-8 /dev/block/dm-8 4096 4096 86750 86750 sha1 19daf5cd7bb360889c3c72b9bb6f4ba0d23ce0fb e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-8 fec_roots 2 fec_blocks 87435 fec_start 87435 restart_on_corruption ignore_zero_blocks'
[    2.125275] (3)[1:init][    2.125269]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-6 /dev/block/dm-6 4096 4096 407562 407562 sha1 74905fd3c824dbbca500138f68a615ddd0365ee4 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-6 fec_roots 2 fec_blocks 410773 fec_start 410773 restart_on_corruption ignore_zero_blocks'
[    2.130372] (3)[1:init][    2.130366]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-9 /dev/block/dm-9 4096 4096 209646 209646 sha1 3d97cb5d9f16a3d9ce2c2056ab8b3a2050646e5f e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-9 fec_roots 2 fec_blocks 211298 fec_start 211298 restart_on_corruption ignore_zero_blocks'
[    2.135838] (3)[1:init][    2.135832]@3 init: [libfs_avb]Built verity table: '1 /dev/block/dm-5 /dev/block/dm-5 4096 4096 15444 15444 sha1 7a8c095c71489e62b242b7b137d099d1f36a4f68 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-5 fec_roots 2 fec_blocks 15566 fec_start 15566 restart_on_corruption ignore_zero_blocks'

dmesg produce with LineageOS recovery:

Nord:/ # dmesg | grep libfs_avb
[    1.977591] (5)[1:init][    1.977587]@5 init: [libfs_avb]Returning avb_handle with status: Success
[    1.978731] (5)[1:init][    1.978727]@5 init: [libfs_avb]: Error verifying vbmeta image: OK_NOT_SIGNED
[    1.978767] (5)[1:init][    1.978764]@5 init: [libfs_avb]Found unknown public key used to sign /system
[    1.978783] (5)[1:init][    1.978780]@5 init: [libfs_avb]Returning avb_handle for '/system' with status: VerificationError
[    1.979964] (5)[1:init][    1.979958]@5 init: [libfs_avb]Built verity table: '1 /dev/block/dm-7 /dev/block/dm-7 4096 4096 234780 234780 sha1 92f8d04b6b85b99c10ad1784381cb974896206d1 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-7 fec_roots 2 fec_blocks 236631 fec_start 236631 restart_on_corruption ignore_zero_blocks'
[    1.992533] (5)[1:init][    1.992526]@5 init: [libfs_avb]Built verity table: '1 /dev/block/dm-8 /dev/block/dm-8 4096 4096 86750 86750 sha1 19daf5cd7bb360889c3c72b9bb6f4ba0d23ce0fb e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-8 fec_roots 2 fec_blocks 87435 fec_start 87435 restart_on_corruption ignore_zero_blocks'
[    1.997677] (5)[1:init][    1.997671]@5 init: [libfs_avb]Built verity table: '1 /dev/block/dm-6 /dev/block/dm-6 4096 4096 407562 407562 sha1 74905fd3c824dbbca500138f68a615ddd0365ee4 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-6 fec_roots 2 fec_blocks 410773 fec_start 410773 restart_on_corruption ignore_zero_blocks'
[    2.002824] (5)[1:init][    2.002818]@5 init: [libfs_avb]Built verity table: '1 /dev/block/dm-9 /dev/block/dm-9 4096 4096 209646 209646 sha1 3d97cb5d9f16a3d9ce2c2056ab8b3a2050646e5f e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-9 fec_roots 2 fec_blocks 211298 fec_start 211298 restart_on_corruption ignore_zero_blocks'
[    2.008406] (5)[1:init][    2.008399]@5 init: [libfs_avb]Built verity table: '1 /dev/block/dm-5 /dev/block/dm-5 4096 4096 15444 15444 sha1 7a8c095c71489e62b242b7b137d099d1f36a4f68 e663c83cb79b4c815f3391f136b313ab1de19cbe9ffbd971fe88a2a86882ed0d 10 use_fec_from_device /dev/block/dm-5 fec_roots 2 fec_blocks 15566 fec_start 15566 restart_on_corruption ignore_zero_blocks

Edit: dmesg output its the same and LineageOs recovery also produce dark screen but it boot on recovery mode with fastboot boot

MrDuartePT · 2023-10-14T13:30:21Z

I forget to send the command i use to sign.
OrangeFox recovery:

./avbroot ota patch \
    --input PixelExperience_Plus_avicii-13.0-20231003-1348-OFFICIAL.zip \
    --privkey-avb ./custom-keys/avb.key \
    --privkey-ota ./custom-keys/ota.key \
    --cert-ota ./custom-keys/ota.crt --clear-vbmeta-flags --magisk Magisk.v26.3.apk --magisk-preinit-device metadata --replace recovery OrangeFox-R12.1_1-Unofficial-avicii.img -o PixelExperience_Plus_avicii-13.0-OrangeFox.zip

link for recovery
Lineage Os Recovery:

./avbroot ota patch \
    --input PixelExperience_Plus_avicii-13.0-20231003-1348-OFFICIAL.zip \
    --privkey-avb ./custom-keys/avb.key \
    --privkey-ota ./custom-keys/ota.key \
    --cert-ota ./custom-keys/ota.crt --clear-vbmeta-flags --magisk Magisk.v26.3.apk --magisk-preinit-device metadata --replace recovery recovery-lineageos.img -o PixelExperience_Plus_avicii-13.0-LineageOS.zip

link for recovery

chenxiaolong · 2023-10-14T20:41:36Z

Does adb shell work when it's sitting at the black screen or is the device just completely frozen? I have no idea why it would work via fastboot boot, but not when it's flashed.

Can you post exactly how you're flashing everything? Are you just sideloading the OTA zip or is there anything else you're doing besides that?

If you haven't already tried this, I suggest:

Boot any recovery with fastboot boot.
Sideload either PixelExperience_Plus_avicii-13.0-OrangeFox.zip or PixelExperience_Plus_avicii-13.0-LineageOS.zip. Don't extract or flash anything else manually.
See if rebooting into recovery still results in a black screen.

MrDuartePT · 2023-10-14T20:45:06Z

For flashing I using this script:

# Flash the boot images that were extracted
for image in extracted-PE-root/*.img; do
	partition=$(basename "${image}")
	partition=${partition%.img}

	fastboot flash "${partition}" "${image}"
done

# Flash the AVB signing public key
fastboot erase avb_custom_key
fastboot flash avb_custom_key custom-keys/avb_pkmd.bin

I only have acess to adb on OrangeFox Recovery.
I gonna try adb sideload the zip and see what happen

MrDuartePT · 2023-11-08T11:52:24Z

Well after a busy week. I will try this week doing the adb sideload

Issue: #186 Issue: #195 Issue: #212 Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>

MrDuartePT · 2023-12-08T17:34:51Z

I gonna close the issue since oneplus broke the functionality on android 12 bootloader.
Let see if devices with android 13 bootloader have that fix (also oneplus fix Windevine in android 13 bootloader when using custom roms)

MrDuartePT closed this as completed Oct 9, 2023

chenxiaolong self-assigned this Oct 9, 2023

MrDuartePT reopened this Oct 13, 2023

MrDuartePT changed the title ~~Problems signing Pixel Experience for Oneplus Nord~~ Problems signing/recovery Pixel Experience for Oneplus Nord Oct 13, 2023

chenxiaolong mentioned this issue Oct 13, 2023

boot: Avoid setting signature algorithm when image is indirectly signed #191

Merged

chenxiaolong mentioned this issue Nov 27, 2023

Recovery image not sign/boot correctly #212

Closed

chenxiaolong added a commit that referenced this issue Dec 3, 2023

README.md: Document OnePlus boot issues

1a18eb7

Issue: #186 Issue: #195 Issue: #212 Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>

MrDuartePT closed this as completed Dec 8, 2023

chenxiaolong mentioned this issue Dec 24, 2023

Add support for replacing otacerts.zip in the system image #240

Merged

chenxiaolong mentioned this issue May 31, 2024

Supported devices #299

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problems signing/recovery Pixel Experience for Oneplus Nord #186

Problems signing/recovery Pixel Experience for Oneplus Nord #186

MrDuartePT commented Oct 9, 2023

pascallj commented Oct 9, 2023

MrDuartePT commented Oct 9, 2023

MrDuartePT commented Oct 9, 2023

MrDuartePT commented Oct 9, 2023 •

edited

Loading

chenxiaolong commented Oct 9, 2023

MrDuartePT commented Oct 9, 2023 •

edited

Loading

MrDuartePT commented Oct 13, 2023

MrDuartePT commented Oct 13, 2023 •

edited

Loading

chenxiaolong commented Oct 13, 2023

MrDuartePT commented Oct 13, 2023 •

edited

Loading

MrDuartePT commented Oct 13, 2023

MrDuartePT commented Oct 13, 2023 •

edited

Loading

MrDuartePT commented Oct 13, 2023

chenxiaolong commented Oct 13, 2023

MrDuartePT commented Oct 13, 2023 •

edited

Loading

MrDuartePT commented Oct 14, 2023 •

edited

Loading

MrDuartePT commented Oct 14, 2023 •

edited

Loading

MrDuartePT commented Oct 14, 2023

chenxiaolong commented Oct 14, 2023

MrDuartePT commented Oct 14, 2023 •

edited

Loading

MrDuartePT commented Nov 8, 2023 •

edited

Loading

MrDuartePT commented Dec 8, 2023

Problems signing/recovery Pixel Experience for Oneplus Nord #186

Problems signing/recovery Pixel Experience for Oneplus Nord #186

Comments

MrDuartePT commented Oct 9, 2023

pascallj commented Oct 9, 2023

MrDuartePT commented Oct 9, 2023

MrDuartePT commented Oct 9, 2023

MrDuartePT commented Oct 9, 2023 • edited Loading

chenxiaolong commented Oct 9, 2023

MrDuartePT commented Oct 9, 2023 • edited Loading

MrDuartePT commented Oct 13, 2023

MrDuartePT commented Oct 13, 2023 • edited Loading

chenxiaolong commented Oct 13, 2023

MrDuartePT commented Oct 13, 2023 • edited Loading

MrDuartePT commented Oct 13, 2023

MrDuartePT commented Oct 13, 2023 • edited Loading

MrDuartePT commented Oct 13, 2023

chenxiaolong commented Oct 13, 2023

MrDuartePT commented Oct 13, 2023 • edited Loading

MrDuartePT commented Oct 14, 2023 • edited Loading

MrDuartePT commented Oct 14, 2023 • edited Loading

MrDuartePT commented Oct 14, 2023

chenxiaolong commented Oct 14, 2023

MrDuartePT commented Oct 14, 2023 • edited Loading

MrDuartePT commented Nov 8, 2023 • edited Loading

MrDuartePT commented Dec 8, 2023

MrDuartePT commented Oct 9, 2023 •

edited

Loading

MrDuartePT commented Oct 9, 2023 •

edited

Loading

MrDuartePT commented Oct 13, 2023 •

edited

Loading

MrDuartePT commented Oct 13, 2023 •

edited

Loading

MrDuartePT commented Oct 13, 2023 •

edited

Loading

MrDuartePT commented Oct 13, 2023 •

edited

Loading

MrDuartePT commented Oct 14, 2023 •

edited

Loading

MrDuartePT commented Oct 14, 2023 •

edited

Loading

MrDuartePT commented Oct 14, 2023 •

edited

Loading

MrDuartePT commented Nov 8, 2023 •

edited

Loading