Skip to content

Latest commit

 

History

History
119 lines (89 loc) · 4.07 KB

readme.md

File metadata and controls

119 lines (89 loc) · 4.07 KB
Raw

Automatic script for PIF config generation

What is this?

This repo has scripts for generating custom PIF config files to use with PIF v14.

How to use this?

  • The script has two files. The first one is clone_device.sh and the second is gen_pif_custom.sh modified from @osm0sis' original gen_pif_custom.sh
  • You first need to copy a device repo from the dump (link in step 1) and paste it when prompted after running the first script.

The structure

  1. (New) skip running all the scripts individually by running start.sh file instead. Running them individually can still be useful if you just want to repeat regenerating the json files only.

    • Make start.sh exectuable and run 
      chmod +x start.sh
# Run the script
./start.sh

  2. The first script clones a repo from a device repo link the user will provide from the dump repo: https://dumps.tadiphone.dev/dumps/. It inits the git repo without checkout so that we don't have to download unnecessary files.

    • Make sure the script is exectuable first:

      chmod +x clone_device.sh
# Then run
./clone_device.sh

# Pro tip:
# If you are lazy you can always type the first couple of lines and
# add the '*' to search for the trailing letters/characters of the file
# name as long as no file has a similar name to the script
./clone*

  3. We only need two files for gen_pif_custom.sh to generate the config file:

    • build.prop from system and vendor directories are cloned.
    • For just in case, the build.prop from system/product is also cloned if available.
    • *Do not worry if the script outputs some errors. As long as the end result has at least 2 files, you are good.

  4. The script will then move and rename files appropriately for the second script to use in the root of the repo directory.

  5. Run the second script.

    • Make sure the script is exectuable first:

      chmod +x gen_pif_custom.sh
# Then run
./gen_pif.custom.sh

# Or use the shortened version
./gen*

  6. The second script automagically generates a pif.json

  7. The generated pif is automatically added to custom.pifs.json file in the directory.

  8. Repeat as needed.

  9. Copy a pif from the custom.pifs.json file to a file named pif.json and move it inside /data/adb folder on your device using your favorite root explorer, or use an application like pixelflasher to easily edit your pif.son

For manual generation

If you would like to take on the tedious task of finding each prop value and then copying it to your json file, here is a list of prop names that each json config property corresponds to:

  • PRODUCT:
    • ro.product.name
    • ro.product.system.name
    • ro.product.product.name
  • DEVICE:
    • ro.product.device
    • ro.product.system.device
    • ro.product.product.name
  • MANUFACTURER:
    • ro.product.manufacturer
    • ro.product.system.manufacturer
    • ro.product.product.manufacturer
  • BRAND:
    • ro.product.brand
    • ro.product.system.brand
    • ro.product.product.brand
  • MODEL:
    • ro.product.model
    • ro.product.system.model
    • ro.product.product.model
  • FINGERPRINT:
    • ro.build.fingerprint
    • ro.system.build.fingerprint
    • ro.product.build.fingerprint

Then save your file like this:

{
  "PRODUCT": "taimen",
  "DEVICE": "taimen",
  "MANUFACTURER": "Google",
  "BRAND": "google",
  "MODEL": "Pixel 2 XL",
  "FINGERPRINT": "google/taimen/taimen:8.1.0/OPM4.171019.021.R1/4833808:user/release-keys",
  "SECURITY_PATCH": "2018-07-05",
  "FIRST_API_LEVEL": "26"
}

*Above fingerprint is already banned and is only an example.

Credits