Documentation instructions to extract dtbo.img and vendor_boot.img from e-Recovery zip file
- /e/ version: latest
- Device model(s): guacamole renoir dubai hotdog (perhaps others)
- Developer mode enabled: yes
- Device rooted: no -- new install
- Trackers blocker enabled: no
Summary
In certain Documentation install pages [1] users are told as this example
First unzip the /e/OS Recovery file linked in the section marked Downloads for renoir . The following files would show up in the location where you unzipped the contents of the eRecovery zip file
dtbo.img
vendor_boot.img
The problem
Steps to reproduce
Attempt to follow instructions Navigate to https://images.ecloud.global/dev/renoir/
Users report that it is not possible to extract dtbo.img | vendor_boot.img
Revision of reported issue (not a bug)
Put simply, this seems an issue of Documentation being in advance of published files.
For "eRecovery zip file" we must read "a new type of bundled Recovery file". When published it might look like which is a .zip file.
Example from https://images.ecloud.global/dev/hotdogb/:
In other words the wording "First unzip the /e/OS Recovery file" does correctly apply when the files are published in the format used on this page: https://images.ecloud.global/dev/lemonade/.
Solutions
Perhaps users need to be aware to wait for the images to be published in the intended format and use the Workaround till then.
Workaround
-
Extract from the /e/OS ROM.zip using a method proposed https://community.e.foundation/t/week-41-2023-development-and-testing-updates/52543
-
Download latest release of payload-dumper-go (https://github.com/ssut/payload-dumper-go/releases) to the same directory (*) where you downloaded the /e/OS T build ZIP file
-
Open terminal and cd to (*) directory
-
Extract the zip file by running this command
unzip e--s--dev-lemonadep.zip payload.bin
Here the example of the lemonadep file has been taken. Replace with the zip file of your zip
-
Extract payload-dumper-go by running this command
tar xzvf payload-dumper-go_1.2.2_linux_amd64.tar.gz payload-dumper-go
-
now run
./payload-dumper-go -partitions -o dtbo,vendor_boot
Adjust for the .img files needed
-
Here the two partition files expected for this device dtbo and vendor_boot are mentioned
Footnotes
[1] Install pages affected
https://doc.e.foundation/devices/guacamole/install#flashing-additional-partitions
https://doc.e.foundation/devices/renoir/install
https://doc.e.foundation/devices/dubai/install
Reports on community forum
https://community.e.foundation/t/oneplus-platform-how-to-get-dtbo-img-vbmeta-img/52571
https://community.e.foundation/t/cant-unzip-recovery-file-to-get-files-for-flashing-partitions/52545
https://community.e.foundation/t/motorola-edge-30-dubai-documentation-suggestions/48006/7