Customrombay database

A repository for syncing data with custom ROMs' creators. It includes files for hundreds of devices and scripts for synchronizing the data with upstream repositories.

State of scripts for synchronizing with different custom ROMs' creators:

[✓] LineageOS - conflicts fixed here, using the mainstream device directory, 437/437 devices supported
[✓] PixelExperience - using the mainstream devices.json file, 142/142 devices supported
[✓] ArrowOS - using the mainstream arrow_ota.json file, no support for checking if a device is discontinued found, 90/90 devices supported
[✓] EvolutionX - using the mainstream devices.json file, 69/69 devices supported
[✓] PixelOS - using the mainstream devices.json file, 45/45 devices supported
[✓] PixysOS - using the mainstream devices.json file, 28/28 devices supported
[✓] SuperiorOS - using files from the official_devices and official_devices-gapps repositories, 29/29 devices supported
[/] crDroid - using a mainstream file from the official website, an important issue ignored by the authors, 159/171 devices supported
[/] HavocOS - using a local copy of the OTA repository due to an issue in a JSON file, fix requested, 88/107 devices supported
[/] CorvusOS - using a local copy of the devices.json file due to duplicate declarations, fixes requested, 47/52 devices supported
[/] xiaomi.eu - using the official MIUI 14 STABLE RELEASE thread, no support for automation, 84/132 devices supported
[\] /e/OS - using a local copy of the devices directory due to duplicate declarations, 252/270 devices supported
[-] GrapheneOS - no parsable file found, devices added manually and not synced
[-] AwakenOS - no parsable file found, devices added manually and not synced

State of scripts for synchronizing with custom recoveries:

[/] TWRP - using the twrpme repository, 311/827 devices supported
[/] OrangeFox - using the official API, 87/142 devices supported