When a dev build checking via Supported devices for the command line Install page for the the device, then Downloads /e/OS build; open the /e/image ROM page https://images.ecloud.global/dev/pstar/ shows that an Android version upgrade is required (in this case e-1.19.1-s to e-1.20-t ) then a manual Upgrade is required.
Sorry, I missed the change from s to t version. I need to install it manually.
Thanks!
Yes the installation will have to be manual. Take a backup first of all you important data.
@Manoj can we give users any further guidance on whether all /e/OS T ROM are fully loaded with necessary vendor parts ?
We read back in August 2023
but now the advice is limited to
In order to verify that an /e/OS T build is “fully loaded” I have referred to that device’s LineageOD device page from https://wiki.lineageos.org/devices/ → Upgrade page link, to check that no “return to Stock ROM” is mentioned there.
Before attempting such S → T upgrade over cautiously (?) after downloading the e-1.2x-t ROM I would extract as required [Footnote 1] to inspect the ROM.zip for good evidence of vendor parts.
Clearly the advice to
Take a backup first of all your important data.
is required.
Footnote 1
Referring to [Walkthrough] Extract eRecovery and boot images using payload-dumper-go
for this purpose the command can be simplified to
$ ./payload-dumper-go <your e ROM filename.zip>
Example satisfactory output from this advice
$ ./payload-dumper-go e-1.20-t-20240222382228-dev-enchilada.zip
Found partitions:
boot (67 MB), dtbo (8.4 MB), system (3.0 GB), vbmeta (8.2 kB), vendor (1.1 GB)
The builds are made automaticaly by running scripts. Additional partitions where required should be a part of the build. It would be helpful if the specific device build is mentioned where the partitions are missing.
1 Like
That was really easy. Thx
This topic was automatically closed after 7 days. New replies are no longer allowed.