Flashing a custom ROM on this device is notoriously difficult because: Locked Bootloaders
: You will need a reliable USB cable, a desktop computer running Windows or Linux, and a MicroSD card (up to 512GB) to hold installation files. Step-by-Step Installation Guide
The remains a popular budget smartphone, but its official software support ended years ago. If you want to breathe new life into this device using a custom ROM, you have likely encountered major hurdles. Because the phone uses a MediaTek Helio A22 chipset and has a locked bootloader, traditional custom ROM installation methods often fail, freeze, or bootloop.
As of early 2026, there are no "official" or widely stable custom ROMs for this device. Most community efforts focus on , which are universal Android builds that can run on any device supporting Project Treble. huawei y5 2019 custom rom fixed top
Navigate to /system/build.prop (or /vendor/build.prop ).
[Main Menu] ➡️ [Wipe] ➡️ [Format Data] ➡️ Type "yes" └── Removes EMUI Storage Encryption [Advanced Wipe] ➡️ Select [System Only] ➡️ Swipe to Wipe └── Erases Factory Huawei OS Framework
The stock camera framework of EMUI is missing, causing third-party camera apps to crash. Flashing a custom ROM on this device is
His mission wasn't just to fix it, but to strip away the bloated software and install a —something the community said was nearly impossible due to Huawei's refusal to provide bootloader unlock codes .
Many Treble ROMs fail to map the MediaTek backlight driver properly.
Save, reboot, and the top should re-align. Because the phone uses a MediaTek Helio A22
The Huawei Y5 (2019) ships with the entry-level , and EMUI 9.1 software . Over time, stock firmware updates bloat the system, leading to performance drops and system UI bugs. Users searching for a "fixed top" custom ROM are typically trying to resolve two primary problems:
: A Linux-based OS that has specific documentation for this model ( huawei-kansas ).
This happens because the ROM doesn't read the phone's ro.config.hw_notch_size or uses a wrong display cutout configuration.