Key English
extracting-proprietary-blobs.md:2 ## Introduction
extracting-proprietary-blobs.md:4 Proprietary blobs can be extracted either from a device already running /e/OS or from an /e/OS installable zip. In this guide we will describe the steps required to extract proprietary files from installable zips.
extracting-proprietary-blobs.md:6 Before beginning, it is required to know the difference between the types of OTAs:
extracting-proprietary-blobs.md:8 * **Block-based OTA**: the content of the system partition is stored inside of an `.dat`/`.dat.br` file as binary data.
extracting-proprietary-blobs.md:10 * **File-based OTA**: the content of the system partition is available inside a folder of the zip named `system`.
extracting-proprietary-blobs.md:12 * **Payload-based OTA**: the content of the system partition is stored as an `.img` file inside of `payload.bin`.
extracting-proprietary-blobs.md:14 If your zip has no `system` folder or it is nearly empty and a file named `system.transfer.list` exists at the root level, then what you have is a block-based OTA. Jump to [Extracting proprietary blobs from block-based OTAs](#extracting-proprietary-blobs-from-block-based-otas) in this case.
extracting-proprietary-blobs.md:16 If you have the entire content of the system partition inside the `system` folder and no `system.transfer.list`, then what you have is a file-based OTA. See [Extracting proprietary blobs from file-based OTAs](#extracting-proprietary-blobs-from-file-based-otas).
extracting-proprietary-blobs.md:18 You may also have a payload-based OTA, which is what your device will use if it uses the A/B partitioning system. If that is what you have, jump to [Extracting proprietary blobs from payload-based OTAs](#extracting-proprietary-blobs-from-payload-based-otas).
extracting-proprietary-blobs.md:20 ## Extracting proprietary blobs from block-based OTAs
extracting-proprietary-blobs.md:22 Some block-based OTAs are split into multiple files, for the system partition and the other partitions like vendor, product, oem, odm and others. You can verify if yours is split by looking for the corresponding `*.transfer.list` files for each in the root of the installable /e/OS zip.
extracting-proprietary-blobs.md:24 If you have a split block-based OTA file then you will need to extract, decompress and convert each one in a similar manner to system and vendor as outlined below.
extracting-proprietary-blobs.md:26 If you do not have a split OTA file, you may skip any step that references `vendor.transfer.list` and `vendor.new.dat.br` or `vendor.new.dat`
extracting-proprietary-blobs.md:28 Create a temporary directory and move there:
extracting-proprietary-blobs.md:33 ```
mkdir ~/android/system_dump/
cd ~/android/system_dump/
```
extracting-proprietary-blobs.md:35 Extract `system.transfer.list` and `system.new.dat.br` or `system.new.dat` from the installable //e/OS zip:
extracting-proprietary-blobs.md:40 ```
unzip path/to/e-*.zip system.transfer.list system.new.dat*
```
where `path/to/` is the path to the installable zip.
extracting-proprietary-blobs.md:42 If your OTA includes `vendor.transfer.list` and `vendor.new.dat.br` or `vendor.new.dat` (other others), extract them from the installable /e/OS zip as well:
extracting-proprietary-blobs.md:47 ```
unzip path/to/e-*.zip vendor.transfer.list vendor.new.dat*
```
where `path/to/` is the path to the installable zip.
extracting-proprietary-blobs.md:49 In the case of `system.new.dat.br`/`vendor.new.dat.br`/etc. (a [brotli](https://en.wikipedia.org/wiki/Brotli) archive) exists, you will first need to decompress them using the `brotli` utility: