Part of POCO guides, HyperOS guides, 2026 guides.

I pulled my daily phone off its usual ROM to test this, which should tell you how curious I was about an Android 17 Canary build on the POCO X7 Pro. Here is what it is, how it flashes, and where it hurts.

Short version: it is a Pixel-style AOSP build, not HyperOS with a coat of paint. Clean flash only. Never dirty flash this one over anything.

What it looks like once it boots

The Pixel personality is all there. Google dialer and messages are in place, the wallpaper style is the Pixel default, and the home screen uses glass-style effects that only show themselves properly after the phone has finished doing its background work.

The animations land nicely. If you have used a Pixel, you will find the layout instantly familiar, and the differences are small touches rather than a different phone.

How the install runs

The package gives you three routes: an installer batch file for Windows, a script for Linux, and an Android route if you want to flash straight from the phone with Termux instead of a PC. I went with the PC route because it is easier to watch what is happening.

The shape of it is the same as any AOSP build on this phone:

• Unlock the bootloader if you have not already, and accept that it wipes the phone.
• Put your platform tools, the ROM package and the images in one folder so nothing is missing at the wrong moment.
• Boot to fastboot and confirm the PC sees the device before you flash anything.
• Run the installer batch file and let it work through the images in order.
• Boot into recovery when it tells you to, format data, and let the ROM install.
• Flash the certification and integrity fix right after the ROM, before you sign into anything.

Do it as a clean flash. A dirty flash on a base this new is asking for a boot loop you will spend the evening undoing.

The first ten minutes

Right after first boot, everything feels a little laggy. Resist the urge to judge it. The system is downloading and restoring apps in the background, and it needs roughly ten to fifteen minutes to finish that. Once it does, the glass-style effects on the home screen show up properly and the general smoothness arrives.

If you start swiping around and call the build slow at minute two, you are measuring the setup, not the ROM.

What works and what is broken

This is the honest section, and it is why you read these things.

• Open Camera works. It opens, it shoots, no drama.
• GCam does not work on this build. If a Google camera port is the reason you flash ROMs, that is a real dealbreaker and you should wait.
• Google dialer and messages are in place. Calls and texts feel like a Pixel.
• Play Store certification needs the fix. Flash the integrity and certification patch straight after the ROM, or the Play Store keeps complaining at you.

Who should install it

Treat a Canary build like a Canary build. The Pixel feel is there and the animations land nicely, but you are on an early base and small things show it.

Install it if you can live without GCam and you are comfortable flashing the certification fix in the same session. Install it if you want to spend a day seeing where Android is heading on this hardware. Do not install it as your only phone if a broken camera app would ruin your week.

For the PC side, the free Rom Flasher tool covers the ADB and fastboot driver setup, so the batch file has a phone it can actually talk to.

Full description from the video

Android 17 Canary on the POCO X7 Pro (Rodin) — a Pixel-style AOSP build installed clean from Fastboot, then pushed through a first look at the UI, the bugs, and whether it can hold up as a daily driver.

I pulled my phone off its daily ROM for this, which tells you how curious I was. Do it as a clean flash, never a dirty flash. The package carries an installer batch file for Windows, a script for Linux, and an Android route if you're flashing from the phone itself.

Right after first boot everything feels a little laggy, and that's normal. The system is still downloading and installing apps in the background. Give it ten to fifteen minutes. The glass-style effects on the home screen show up properly once things settle.

The camera is the honest part: Open Camera works fine, GCam does not. If GCam is a dealbreaker for you, wait on this build. And the integrity and certification fix is not optional here — flash it after the ROM or Play Store keeps complaining.

📱 Device : POCO X7 Pro (Rodin)

🧩 ROM : Pixel-style AOSP, Android 17 Canary

👤 Credits : ido, Omkar Parte and Ruben (AOSP device tree) · Eix (batch script and testing) · Saan (help and support)

🔬 What Was Tested

• Clean flash through the installer batch file, start to finish
• First boot behaviour, including the early lag while apps install
• Home screen look — the Pixel wallpaper style and glass effects
• Google dialer and messages in place, plus Open Camera working
• GCam checked, and it isn't working on this build
• Play Store certification state and the integrity fix
• General smoothness once the background work finished

📊 Verdict

It's a Canary build, so treat it like one. The Pixel feel is there and the animations land nicely, but you're on an early base and that shows in small places. As a daily driver? Only if you can live without GCam and you're comfortable flashing the certification fix right after the ROM. Otherwise it's a great build to try for a day and learn from.

❓ Common Questions

• Can I dirty flash it? No. Clean flash only.
• Do I need a PC? It's the easier route, but there's an Android installer option too.
• Is GCam working? Not on this build — use Open Camera.
• Do I need the integrity fix? Yes, flash it right after the ROM.

Common questions

More for POCO X7 Pro