Custom ROMs for the Samsung Galaxy A04 (including variants like the A04e and A04s) generally aim to solve the lag inherent in Samsung's budget-tier One UI Core. Because this device uses entry-level hardware like the MediaTek Helio P35, a custom ROM can significantly improve responsiveness by removing "bloatware." Available Options
As of early 2026, the custom ROM scene for the A04 relies heavily on Generic System Images (GSIs) due to its Project Treble compatibility.
LineageOS 22.1 (Unofficial): Ported versions based on Android 15 are available for specific models like the A04e. It offers a "vanilla" Android experience that is much lighter than Samsung's stock software.
Other GSIs: Popular options include crDroid and Rising OS, which are frequently updated to the latest Android versions. Performance & User Experience
The quest for a custom ROM on the Samsung Galaxy A04 is a journey of turning a budget-friendly device into a high-performance, personalized machine. While the A04 is an excellent entry-level smartphone with its 5,000mAh battery AI power management
, many power users find its stock software limited. Custom ROMs offer a way to unlock the phone’s true potential by stripping away "bloatware" and adding features typically reserved for flagship models. Why Consider a Custom ROM?
The primary motivation for modding a device like the A04 is often performance optimization
. The stock One UI Core software, while functional, can sometimes feel heavy on the A04's hardware. By installing a custom ROM, users can: Remove Pre-installed Apps: Free up valuable internal storage. Update Android Versions:
Access newer Android features (like Android 15 or 16) through community-developed GSI (Generic System Image) ROMs even after Samsung stops official updates. Enhanced Customization: Change everything from system fonts to advanced UI layouts. The Path to Installation
Modifying the Galaxy A04 requires a specific technical process. First, the device must be put into Download Mode
by holding the volume buttons and connecting it to a charger. Once the Bootloader is unlocked , users typically install a custom recovery like For many Galaxy A04 users, —such as Evolution X
—are the most accessible options. These can be "side-loaded" using tools like ADB Sideload once the device is in recovery mode. Risks and Rewards
The "custom ROM" life isn't without its hurdles. Unlocking the bootloader voids your warranty
and can disable security features like Samsung Knox or certain banking apps. There is also the risk of "bricking" the device if the process isn't followed correctly.
However, for those willing to take the risk, the reward is a Samsung Galaxy A04
that feels faster, cleaner, and entirely unique. It transforms a standard budget phone into a tailored tech experience. step-by-step guide
on how to unlock the bootloader for the A04, or are you looking for a list of stable ROMs currently available?
Samsung Galaxy A04 (SM-A045X) has a growing development scene aimed at replacing the heavy Samsung One UI with lighter, faster software. Users often seek these ROMs because the original software can become sluggish over time. Available Custom ROMs
Several AOSP (Android Open Source Project) based ROMs are currently available for the device, primarily hosted on platforms like SourceForge
: Known for being a clean, stable, and "de-Googled" experience.
: Focuses on performance and reliability by stripping away bloatware. : Aimed at making your A04 feel like a Google Pixel device. samsung a04 custom rom
: Offers a blend of features from various ROMs with a focus on customization. RisingOS-Revived
: A newer project focused on performance and UI enhancements. SourceForge Why Users "Rome" the A04 Performance Issues
: Many users report that the device "lags" or "freezes" under standard One UI updates. Virtual RAM Limitations
: While Samsung provides a "RAM Plus" feature to increase memory virtually, it uses internal storage and may not provide the same speed boost as a lightweight custom ROM. Experimental Support
: Beyond standard Android, the A04 is even being tested for alternative operating systems like postmarketOS , which is based on Alpine Linux. Important Considerations Bootloader Unlocking
: This is a mandatory first step and will factory reset your device. Custom Recovery : You typically need a recovery like (Team Win Recovery Project) to flash these ROMs. Official Stance
The Samsung Galaxy A04 (SM-A045) Go to product viewer dialog for this item.
is a budget-friendly entry into the Samsung ecosystem, but its official One UI Core software can sometimes feel sluggish on its MediaTek Helio P35 processor. Installing a custom ROM is a popular way for enthusiasts to improve performance, customize the interface, and access newer Android versions. 1. Prerequisites for Flashing
Before you begin, ensure you have the following ready. Note: Flashing custom software will wipe all data and permanently void your warranty by tripping the Knox security flag.
Backup Your Data: Use tools like the Samsung Smart Switch or Google One to back up your photos, contacts, and apps.
Drivers and Tools: Install the Official Samsung USB Drivers and the Odin Flash Tool on your PC.
Battery Level: Ensure your device is charged to at least 60% to prevent it from powering off during the process. 2. Unlocking the Bootloader
Unlocking the bootloader is the essential first step to allow third-party software like custom recoveries and ROMs.
Enable Developer Options: Go to Settings > About Phone > Software Information and tap Build Number seven times until "Developer mode has been enabled" appears.
Enable OEM Unlock: In Settings > Developer Options, toggle on OEM Unlocking and USB Debugging.
Enter Download Mode: Power off your device. Hold both Volume Up + Volume Down buttons while connecting it to your PC via USB.
Unlock: Follow the on-screen prompts on the "Warning" screen, long-pressing Volume Up to enter the bootloader unlock menu, and confirm the unlock. 3. Custom Recovery: TWRP vs. SHRP
The Galaxy A04 sat in its drawer like a quiet ghost. It wasn’t broken. It just wasn’t alive.
Mira had bought it two years ago as a backup phone. Plastic body. 6.5-inch LCD. The MediaTek Helio P35 chipset that had never been fast, now felt like cold honey in winter. OneUI Core 4.1 was polite but heavy. Every swipe had a micro-stutter. Every app opened with a sigh.
“I can’t take it anymore,” she whispered, after the camera took four seconds to launch. Custom ROMs for the Samsung Galaxy A04 (including
Her main phone was a flagship. But this A04—this little trooper—had her second SIM, her music, her offline maps. She wanted it to feel light.
That’s when she found the forum.
A thread with only 14 replies. No fancy graphics. Just a title: [GSI] AOSP 13 for A04 (SM-A045F). The original poster had a strange username: Helio_Hacker.
Most people had given up on the A04. No official LineageOS. No TWRP thread with pretty screenshots. Just scattered posts about Project Treble and “GSI” — Generic System Images.
“The A04 has Treble support,” the post read. “But you must unlock the bootloader first. And Samsung doesn’t like that.”
Mira had never done this before.
That night, with a cup of tea gone cold, she enabled Developer Options. Tapped “OEM Unlocking” seven times until it blinked. Powered off. Held Vol Up + Vol Down while plugging the USB into her laptop.
Warning: Custom OS can cause critical problems.
She pressed Vol Up to continue. The screen went black. Then a green Android logo lying on its back, chest open. Download Mode.
The first hurdle: VBMETA. Samsung’s Verified Boot meant she had to flash a custom vbmeta_disabled.tar via Odin. Her hands shook. One wrong click, and the A04 would become a shiny black brick.
But Odin passed. Blue box. “PASS!”
Then the hardest part: booting into a custom recovery. No official TWRP for the A04. Only a patched recovery.img from a Russian forum. She flashed it using heimdall on her Linux laptop.
The screen flickered. For five seconds, nothing. Then—orange text. TWRP 3.7.0.
She almost cried.
From there, she wiped everything. System. Data. Dalvik. The A04 was now a blank slate, neither Samsung nor Google. Just raw metal and silicon waiting for a soul.
She downloaded lineage-20.0-20250211-UNOFFICIAL-treble_arm64_bvS.img.xz. A pure Android 13 GSI without GApps.
Using fastboot, she flashed it to the system partition.
fastboot flash system lineage-20.0.img
fastboot -w
fastboot reboot
The A04 rebooted.
The Samsung logo appeared—then vanished faster than usual. A new animation. Simple. Gray circles spinning. Then:
“Welcome.”
Setup took 30 seconds. No Samsung account. No Bixby. No Theme Store. Just Android. Pure, naked, beautiful Android.
Mira swiped up.
The app drawer opened instantly.
She opened the camera. Snap. 0.5 seconds.
She opened Chrome. Two seconds flat.
The A04 felt like a different phone. The Helio P35 was never slow—it was just suffocating under Samsung’s skin. Now it breathed.
Over the next week, Mira installed F-Droid. Added NewPipe for YouTube without ads. Installed K-9 Mail. No Google Play Services meant the battery lasted two days. The 5,000 mAh battery, once drained by background processes, now felt endless.
The only downside? No VoLTE. And NFC didn’t work (but the A04 never had it anyway). Banking apps complained, so she used the web versions.
She named the ROM “HelioWing.”
On the forum, she posted her results. The 14 replies grew to 87. Someone fixed the brightness slider bug. Another person compiled a minimal kernel with lower latency.
Six months later, a teenager in Brazil messaged her: “Your guide saved my A04. My family couldn’t buy a new phone. Thank you.”
Mira smiled at her drawer phone—still plastic, still humble, but no longer a ghost. The Samsung A04 had become something Samsung never intended: truly, freely hers.
And sometimes, that’s the whole point of custom ROMs. Not specs. Not benchmarks. Just the right to decide what runs on the glass and metal you paid for.
This is a deep review and analysis of the current state of Custom ROMs for the Samsung Galaxy A04.
To understand the custom ROM scene for this device, we must first understand the device itself. The Galaxy A04 is an entry-level budget device released in late 2022. It typically ships with Android 12 or 13 (depending on the region) and runs on the UNISOC SC9863A chipset.
Here is a detailed breakdown of what you need to know before flashing, what is available, and the pros and cons of doing so.
If there is a stable build available for your variant, LineageOS is the gold standard. It offers a clean, bloatware-free experience very close to "Stock Android."
| Problem | Solution |
|--------|----------|
| No SIM detection | Flash your stock modem.bin via Odin (CP tab). |
| Camera crashing | Use Open Camera from Play Store instead of stock camera. |
| Banking apps fail | Install Magisk + Play Integrity Fix module + enable Zygisk. |
| Battery draining fast | Calibrate battery: drain to 0%, charge to 100% without interruption. |
| VoLTE not working | Most custom ROMs don’t support VoLTE on Unisoc chips. Use 3G calls. |
One UI Core, while feature-rich, is heavy for the Exynos 850. Custom ROMs like LineageOS or Pixel Experience strip away the bloatware (Facebook services, Microsoft apps, Samsung push services). Users report a 30-40% increase in app launch speed and multitasking fluidity.
The Samsung A04 uses the Unisoc SC9863A chipset (not Exynos or Snapdragon). This makes development harder, but the community has made progress. Here are the most stable options: The Galaxy A04 sat in its drawer like a quiet ghost