| Version | Country | File Name | Type | Size | md5sum |
| 2412 | Global | Di3.0_13.1.33.2412190.1.18.3.5.2411180.2.zip | Full OTA (see BYD/Upgrading/UpdateFull.zip) |
3.7G | 184807d30d2b4ee4d14445e2fb81466d |
| 2410 | Global | Di3.0_13.1.33.2410130.1.zip | Full OTA (see BYD/Upgrading/UpdateFull.zip) |
3.3G | fce05f43bd5e08f471c5ecc8cafa3fc3 |
| 2407 | Global | Di3.0_13.1.33.2407240.1.zip | Full OTA (see BYD/Upgrading/UpdateFull.zip) |
3.3G | 44db26577659eb28ef2da1b3b5e476ce |
| 2403 | Global | Di3.0_13.1.33.2403010.1.18.3.3.2402270.2.zip | Full OTA (see BYD/Upgrading/UpdateFull.zip) |
3.7G | be8c50fabed8fff23e8ca87132f24d12 |
| 2401 | AU | 13.1.33.2401-partitions-from-diff.tar.bz2 | Partitions (see BYD/Upgrading/Fastboot) |
2.9G | af3b44b4ba9e540353a0746db7b956cc |
| 2307 | Global | Di3.0_13.1.33.2307210.1.18.3.2.2307190.2.zip | Full OTA (see BYD/Upgrading/UpdateFull.zip) |
3.7G | 4db4fec9e70f0426620b76853bf279ae |
These packages contain the updates for the Android system only. They do not contain updates for the ADAS modules or other components of the vehicle. If you wish to install these Android updates directly, particularly the ‘partitions’ version, I strongly advise letting the official OTA updater update everything else first. If it fails to update Android then reports the update is still pending, update again until it eventually says you're already on 1.0 or 1.1, even if it lists the old version in the software versions screen. This will ensure the ADAS is up to date before manually updating the Android system.
The 2401 ‘Partitions’ package listed has been created by manually applying the 2401 OTA differential update (from Australia) on top of the Global 2307 full update partition images.
To obtain the base partition images, the 2307 UpdateFull.zip is unzipped, as well as the update.zip contained within it, which will create a file called payload.bin (as well as other files which can be ignored for this purpose). This payload.bin is then unpacked using an Android update payload unpacker. There are a couple available but I used this one specifically because it supports payloads from differential updates as well as the ‘puffin’ compressor they use.
Afterwards, the update payload unpacker tool linked to above is given the base partition images from 2307 as input along with the differential OTA package's payload.bin (located inside /data/ota_package/ota/package/media/multimedia.zip on the device after it reports an OTA update is available for installation) and the result is 2401 versions of the individual flash partitions, which then need to be written to the device using fastboot and fastbootd, explained here. I have successfully applied this to my Seal Premium without issue.
As of version 2310 (not listed here, I don't have it nor do I know where to source it), there appears to be no direct way to enable ADB or third party package installation without first downgrading to a version prior to 2310 (such as 2307).
The steps involved are:
If any issues are encountered and the Android system is corrupted or stuck in a boot-loop, there is a method for recovery described here which doesn't require USB ADB or fastboot access, only a USB disk. Note though that this recovery process initiates a factory reset before writing the Android image to flash, which will result in user data being wiped including any sideloaded applications ie the ADB switch tool and unlocked package installer. Another thing to note about this approach is that it requires a complete updateFull.zip package as a starting point, of which only 2307 is available as of this writing, so it will downgrade as a matter of course. You can then attempt a vanilla OTA or retry manually upgrading though after recovery, once you identify the reason for the initial failure and resolve it.
I have a Magisk-patched boot.img working on my 2401 Seal for root access. I'll write up the process soon. To write this patched boot.img is the same as writing the original boot.img in the BYD/Upgrading/Fastboot section. You will need USB ADB to boot into fastboot mode and then use that to write to the boot partition.
There is also a mechanism to have ADB run as root on the Android system, but this requires injecting a public key into the system partition and changes the ADB context away from the IVI guest container. Both of these points require further elaboration which will be explained here when I have time.