I suggest that e developers provide copies of dtbo.img, vendor_boot.img & e-recovery matching the eos downloads. Just like LOS do.
Or at least re-visit this issue to align Oneplus 9 install guide with oneplus 9 pro guide.
I would suggest adding in a paragraph to carry out the copy-partitions step directly after “Temporarily booting a custom recovery using fastboot”:
Ensuring all firmware partitions are consistent
Tip: The steps below only need to be run once per device.
In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot.
To do this, sideload the copy-partitions-20220613-signed.zip
package by doing the following:
- Download the
copy-partitions-20220613-signed.zip
file from here. It should have a MD5 sum of79f2f860830f023b7030c29bfbea7737
or a SHA-256 sum of92f03b54dc029e9ca2d68858c14b649974838d73fdb006f9a07a503f2eddd2cd
. - Sideload the
copy-partitions-20220613-signed.zip
package: * On the device, selectApply Update
, thenApply from ADB
to begin sideload. * On the host machine, sideload the package using:adb sideload copy-partitions-20220613-signed.zip
- Now reboot to recovery by tapping
Advanced
, thenReboot to recovery
.
Also this:
Why not remove this page from op9/9pro device info pages?