Part of Redmi guides, DerpFest guides, 2023 guides.

DerpFest comes out of the AOSiP side of the custom ROM world, and you notice that immediately. The phone boots and there is nothing between you and the system. No skin, no wall of vendor apps, no second guessing how the settings should be arranged.

The Redmi K50i has the hardware to make a clean build fly, and an AOSP base is what lets it. Here is what it looks like, what actually changed, what is broken, and who should install it.

What it looks like

The launcher is close to the Pixel launcher. The notification shade is plain and fast. Quick settings are the stock tiles, not Xiaomi's version of them, and the settings app follows Android rather than MIUI. If you have used a Pixel or any AOSP build, you already know the layout, and it takes about an hour to feel at home.

The screen benefits from this. With less running in the background, scrolling and app switching feel lighter than on a stock build. That is not a benchmark, it is just what a leaner system does on hardware like this.

What changed

• The whole interface. Dialer, launcher, quick settings and settings app are AOSP, with none of MIUI's layer over the top.
• Customization. DerpFest carries the options you would expect from a build in this family — status bar tweaks, gesture controls and behavior settings that stock MIUI buries or never offers.
• Vendor apps gone. Nothing is fighting you for the default dialer, or pushing its own version of a system app.
• The camera. The stock MIUI camera app is not here. The AOSP camera is a different animal, and that is the biggest thing you give up.

What you trade

• The MIUI camera. If you shoot a lot, you will miss it. The replacement does not behave the same way.
• Some Xiaomi habits. Little conveniences you stopped noticing because you used them every day simply do not exist here.
• Gapps are usually separate. On most AOSP builds you flash Google apps yourself, so plan for a second zip in the same recovery session unless your build includes them.
• Play Integrity. Banking apps and some payment apps treat custom ROMs badly. Test the ones you rely on early.

What is broken or rough

Honest answer: it depends on your build. DerpFest on this phone is a community build on MediaTek hardware, which is the least forgiving combination there is.

• Support moves build to build. Something that works in one release can break in the next.
• Battery behavior wants a few days before you judge it.
• Aim for a clean install. Dirty flashing over an older base is where the strange little bugs come from.
• Keep a path back to stock. This is not the phone to experiment on without a way home.

What you need before you flash

• Unlocked bootloader. On this phone that is step zero, and it wipes the phone the first time.
• Platform tools on a PC.
• A recovery built for the K50i or its known counterpart. TWRP or OrangeFox, not the stock recovery — the stock one will not do this.
• The ROM zip on internal storage.
• vbmeta on hand. AOSP builds usually need it, and going in without it is how you end up with a bootloop instead of a boot.

The install, in short

1. Unlock the bootloader and install TWRP or OrangeFox for this device.
2. Copy the ROM zip and vbmeta to internal storage.
3. Reboot to recovery and check that touch works and storage is readable. If not, stop and fix recovery first.
4. Wipe data, cache and dalvik, then format data.
5. Flash vbmeta the way your build's instructions say, then flash the ROM zip.
6. Reboot and leave the phone alone for the first boot. It is slow.

If you are unsure about the exact vbmeta step for your build, follow the instructions that came with the ROM rather than guessing at a filename. Getting that one wrong is the most common reason a clean flash turns into a bootloop.

Who should install it

Install DerpFest if you want a clean AOSP phone, you are comfortable with recovery and fastboot, and you are willing to test the build yourself before trusting it.

Skip it if the MIUI camera is why you bought the phone, or if you need a specific app that has to work without argument. On MediaTek, every custom ROM is a test first and a daily driver second.

Keep your stock firmware and know the way back before you start. That habit is the difference between a fun experiment and a long night.

If the driver and platform tools side is where you usually stall, the free Rom Flasher tool on GitHub bundles the ADB and fastboot driver install into a couple of clicks. It is free, and the link is in the downloads section.

Full description from the video

DerpFest on the Redmi K50i — an AOSP based custom ROM review, plus an honest look at what you gain and what you give up.

DerpFest comes out of the AOSiP side of the custom ROM world, and you feel it the second the phone boots. There's no MIUI skin in the way. The whole thing sits closer to Pixel than to anything Xiaomi shipped on this phone, and that's the entire point of flashing it. The K50i has the hardware for a fast, clean build, and an AOSP base lets it stretch.

📱 Device : Redmi K50i

🧩 ROM : DerpFest (AOSP based)

📌 What Stood Out

• A clean AOSP interface with next to no manufacturer clutter
• Customisation options you'd expect from a DerpFest build
• A ROM that respects the screen and the chip on this phone
• No extra layer fighting you for the dialer, the launcher or the quick settings

🔍 What You Trade

• The stock MIUI camera app is gone — the AOSP camera is a different animal
• Some Xiaomi specific habits simply don't exist here
• On most AOSP builds you flash GApps separately, so plan for it

❓ Quick Answers

• Does it need an unlocked bootloader? Yes, and that's step one.
• Do I need vbmeta? On AOSP builds, usually yes. It's in the links below.
• Is it daily driver material? That depends on your build and your usage, so keep a path back to your stock setup.
• Can I keep the stock recovery? No. Use TWRP or OrangeFox.

Common questions

More for Redmi K50i