[HTC Desire 526] BigCountry907:
Next up PG2FS partition #6

This is a very important partition.

We know it is all about the security configuration of the device.

Lucky for you I have a S-off device. (Fully Unlocked)

We could always flash the pg2fs image thats in the RUU.

~/Desktop/526-Completed/A13-Backup/RUU/ROM/firmware/pg2fs_ship_signkey.img

But do we really want to do that ??? :confused:

Lets answer that question country style......:cowboy::cowboy:

Yup you guessed it. We need to hexdump the file we pulled from the device and the Ruu pgsfs.img.

You should be catching on to the process by now.

This is fun right........you always wanted to know what goes into development. All this is just the tip of the iceberg.

Anyway lets get Cookin.

hexdump -C ~/Desktop/526-Completed/A13-Backup/RUU/ROM/firmware/pg2fs_ship_signkey.img
hexdump -C ~/Desktop/526-Completed/A13-Backup/pull/pg2fs_ship_signkey.img

And the data has come in.

You should observe that the pg2fs has a whole lot of code added to it.

We are going to use the unlocked version For Sure. :laugh:

You will notice some of the data in the file is the same.

But the end is very different as well.

There is a lot more data in the unlocked file. PAY ATTENTION TO BYTE ADDRESSES

It's obvious we would love to have this partition on our device with the unlocked data.

To load the uploaded pull from my backup on your device. ( IF You had a way to flash it)

Well would be ok as long as the IMEI MEID ESN or other device specific data is not found in this file at all.

What do these settings mean.

I would guess that they are something related to this.

<module id="SECURITY_CONTROL_CORE"><entry ignore="false"><description>contains the OEM public key hash as set by OEM</description><name>root_cert_hash</name><value>0000000000000000000000000000000000000000000000000000000000000000</value></entry><entry ignore="true"><description>SHA256 signed root cert to generate root hash</description><name>root_cert_file</name><value>./../../resources/testpki/qpsa_rootca.cer</value></entry><entry ignore="false"><description>PK Hash is in Fuse for SEC_BOOT1 : Apps</description><name>SEC_BOOT1_PK_Hash_in_Fuse</name><value>false</value></entry><entry ignore="false"><description>If PK Hash in Fuse is 0, then this index selects which of 16 keys in ROM to use</description><name>SEC_BOOT1_rom_pk_hash_index</name><value>0</value></entry><entry ignore="false"><description>Use Serial Num for secure boot authentication (0: Use OEM ID (Default), 1: Use Serial Num)</description><name>SEC_BOOT1_use_serial_num</name><value>false</value></entry><entry ignore="false"><description>PK Hash is in Fuse for SEC_BOOT2 : MBA</description><name>SEC_BOOT2_PK_Hash_in_Fuse</name><value>false</value></entry><entry ignore="false"><description>If PK Hash in Fuse is 0, then this index selects which of 16 keys in ROM to use</description><name>SEC_BOOT2_rom_pk_hash_index</name><value>0</value></entry><entry ignore="false"><description>Use Serial Num for secure boot authentication (0: Use OEM ID (Default), 1: Use Serial Num)</description><name>SEC_BOOT2_use_serial_num</name><value>false</value></entry><entry ignore="false"><description>PK Hash is in Fuse for SEC_BOOT3 : MPSS</description><name>SEC_BOOT3_PK_Hash_in_Fuse</name><value>false</value></entry><entry ignore="false"><description>If PK Hash in Fuse is 0, then this index selects which of 16 keys in ROM to use</description><name>SEC_BOOT3_rom_pk_hash_index</name><value>0</value></entry><entry ignore="false"><description>Use Serial Num for secure boot authentication (0: Use OEM ID (Default), 1: Use Serial Num)</description><name>SEC_BOOT3_use_serial_num</name><value>false</value></entry><entry ignore="false"><description>The OEM hardware ID</description><name>oem_hw_id</name><value>0x0000</value></entry><entry ignore="false"><description>The OEM product ID</description><name>oem_product_id</name><value>0x0000</value></entry><entry ignore="false"><description>used to configure the number of root certificates hashed into OEM_PK_HASH</description><name>mrc_cert_count</name><value>0</value></entry><entry ignore="false"><description>index is used to select the Root Certificate</description><name>mrc_pk_hash_index</name><value>0</value></entry><entry ignore="false"><description>index is used to select the Modem Root Certificate</description><name>modem_mrc_pk_hash_index</name><value>0</value></entry><entry ignore="false"><description>if true, disable APPS debug</description><name>apps_debug_disabled</name><value>true</value></entry><entry ignore="false"><description>allowing bus DCVS SW feature will require and set APPS_NIDEN_DISABLE to 0</description><name>allow_bus_dcvs</name><value>false</value></entry><entry ignore="false"><description>prevents the Watch Dog from being disabled by the GPIO, true: ignore GPIO, false: use GPIO</description><name>watchdog_enable</name><value>true</value>

Interesting Indeed.

Lets set our partition in the Generator and move on for now.

I highlighted the cells blue. We know we want to use the pulled pg2fs file but we need to double check and make sure it can go on your device.

The Readonly flag is FALSE

Boot Flag False

Filename = pg2fs