Development [ROM][13.0_r30][OFFICIAL] Evolution X 7.6.2 [03/03/2023]

Search This thread


Senior Member
Oct 18, 2009
Google Pixel 6 Pro
Thanks Dev, another great ROM option. Install was easy, no issues at all. Haven't tried any Kernels, or root yet. My only "issue" is Call Screening activating. I have the Google phone app, and it's updated. Hopefully it fixes itself, as that feature is indispensable

-edit/update. After a Google assistant update, once I prompted it with "hey Google" the call assistants are all preset, hold for me, call screening etc.
Last edited:
  • Like
Reactions: AnierinB


Senior Member
Oct 18, 2009
Google Pixel 6 Pro
I had the same issue flashing radioactive in fkm; I re-fastbooted the vendor.img; then adb sideloaded the rom without wiping. My data was still there. I then patched the evox kernel and I have root. Custom kernels may not work with this build.
I flash Kiri's kernel without issue... Screenshot_20230130-185738_Settings.png
For me I did a clean flash of the stock firmware again and started the whole process. It worked flawlessly.

But here are a few things you must do to make it work:

1. Make sure the downloaded files are in the same folder as your platform tools.
2. Use USB A to USB C cable.
3. Be on the latest platform tools.
Thx. Did you have issues with USB C to C?
  • Like
Reactions: w_tapper


New member
Jan 31, 2023
Thank you for the work! I've always been a fan of the Evolution ROM! Glad to be back on it. I installed and ran into all of the issues in the previous messages.

After the point I flashed the January stock firmware;

1) I opened an elevated Command Prompt in the directory of the most recent platform-tools and loaded into Powershell
2) I entered ./adb reboot bootloader
3) I used ./fastboot flash vendor_boot vendor_boot.img
4) Entered ./fastboot reboot recovery
5) Within recovery on my phone I chose the ADB Sideload option
6) Back in Powershell I entered ./adb sideload (Obviously you just need the file name from your download..)

After that everything just worked.

Before this exact process I tried manually changing my PATH to the newest adb.exe and ran into all the same issues folks have already mentioned regardless. I am not sure what this hiccup was but the moment I ran the commands with the ./ prefix in an elevated PowerShell terminal within the directory of the platform-tools, it worked fine.

I found the freezing disappeared once I connected to a USB 2.0 port instead of trying to use a spare USB 3.0 A port. Seems strange but is likely having to do with the differences between the USB 2.0 and 3.x protocol?


Make sure you are in the right directory of the most recent platform-tools, open POWERSHELL as Administrator and use the ./ prefix before your fastboot/adb commands like people have mentioned already and this WILL work..
Last edited:


Recognized Developer
adb sideload is taking forever
anyone else facing this?

Can I flash this with fastboot update ?

Stuck here for the last 20 mins:

C:\_Android\platform-tools_r33.0.3-windows\platform-tools\Evo-X>adb sideload
serving: '' (~2%)

need some help. used multiple cables and ports but no GO.
serving: '' (~3%)

was stuck here for more than an hour till I aborted.

Trying again.
On my phone it says:

"Verifying update package..."

On the CMD, I am stuck here for the last 10 mins:

C:\_Android\platform-tools_r33.0.3-windows\platform-tools>adb sideload
serving: '' (~0%)

Same as these guys except im only at 1%

Still unable to get it to work. It gets to about 6% and freezes.

Apparently this was resolved by formatting data before starting the sideload. I've updated the installation instructions to reflect that, good luck.


May 9, 2012
It might sound crazy, but it's like this:
I had the same problem installing another ROM. Reason: My laptop only has USB ports with USB 3.0. Then I switched a USB hub with USB 2.0 in between and the sideload worked without any problems. Really true - I'm not kidding
I agree. I too learnt this the hard way

Top Liked Posts

  • 2
    weird it just works fine for me
    Tried flashing Kiri's kernel with Kernel Flasher, ExKM & FKM. It's bootlooped every time!
    yeah I think it only works on raven
    I had the same issue on raven using kernel flasher when I tried to install Kiri after installing this ROM. I've been to scared to try again 🤣🤣
    Same happens to me
  • 2
    I've been searching and tried all the custom ROMs out there and this one is literally the best one.

    So many customizations definitely recommended for all pixel 6 pro users (raven)
    Yes! - Big "thanks" to the best maintainer ever -> AnierinB
    weird it just works fine for me
    Tried flashing Kiri's kernel with Kernel Flasher, ExKM & FKM. It's bootlooped every time!
    Looks like a new update was posted on Sourceforge, but the OTA isn't showing an update available
    seems it's because he hasn't updated the version on git , i was looking forward to the changelog of this update , i updated and nothing new but 3 buttons on the multitasking screen , and the error gcam lag when turning off navigation bar is still there
    Long camera loading on Bluejay

    Bug description: When switching between modes in camera on evox, it loads the picture for 5 seconds everytime. On stock it was okay.
    How to reproduce:
    1. Open your camera (tried with shipped and downloaded GCam)
    2. Switch modes
    Screenshots: please see attached

    Thanks, hope this is the right place to post.
    Getting some random reboots on oriole; specifically I'm finding it on the "password required after system restarts" screen when it's been left untouched for a couple of hours. Logs state "APC Watchdog" as the reason. Going to disable LSposed for a while to clean up the logs and then get some logs of this (and also the weird "first call immediately after being idle for a while doesn't connect" thing) if possible, but that may be a bit being that both seem random for me.
  • 35
    Evolution X 7.6.2 for the Google Pixel 6, 6 Pro & 6a [oriole][raven][bluejay]


    Living, Breaking, Keep Evolving.
    Pixel UI, customization and more, we are Evolution X!

    - Team Evolution X -
    @joeyhuab (Founder/Lead Developer)
    @RealAkito (Project Manager/Co-Founder)
    AnierinB (Project Specialist/Co-Founder)

    Reach us on Twitter! @EvolutionXROM

    Check out our website!


    - Theming Settings (Style, Color Source, Accent Color, Accent Background, Background Color, Luminance, Chroma, Tint Background)
    - Custom Themes (Black, Clear, Vivid, Paint In The Snow, Espresso)
    - Dark Theme Schedules
    - Lock screen Clock Fonts (16 Fonts)
    - Headline/Body Fonts (53 Fonts)
    - SB Icon Packs (10 Styles)
    - SB Signal Icon Packs (14 Styles)
    - SB WiFi Icon Packs (10 Styles)
    - System Icon Shape Packs (16 Styles)
    - 3 Button Navbar Styles (10 Styles)
    Status bar
    - Status Bar Lyrics
    - Clock Styles (Right, Center, Left)
    - Clock & Date Configs (Auto Hide, Hide Duration, Show Duration, Seconds, AM/PM, Font Size, Date Position/Case/Format)
    - SB Logo Pack (20 Styles, Right/Left)
    - Network Traffic Indicators
    - Battery Icon Styles (19 Styles)
    - Battery Percent (Hidden, Inside Icon, Next To Icon)
    - Battery Bar (Thickness, Alignment, Blend Colors, Reverse Direction, Colors, Animation)
    - System SB UI Tuner
    - Data Disabled Icon (On/Off)
    - Old Style Mobile Data
    - 4G Instead Of LTE
    - Roaming Indicator
    - WiFi Type Icon
    - Colored Icons
    - Notification Count
    - Bluetooth Battery Status
    - Mic/Camera Privacy Indicator
    - Location Privacy Indicator
    - Media Projection Privacy Indicator
    - ReTicker
    - App Colored Background For Reticker
    - Heads Up (Time Out, Importance Threshold, Less Boring, Stoplist/BlockList)
    - Force Expand Notifications
    - Notification Sound If Active
    - Kill App Button
    - Blink Flashlight For Incoming Call (When Ringing, When Silent, When Entierly Silent, Always)
    - Blink Flashlight For Notifications
    - In-Call-Vibrations (Connect, Waiting, Disconnect)
    Quick Settings
    - Clock
    - Clock Font Size
    - Date
    - Battery Style (15 Styles)
    - Battery Percent Location (Hidden, Inside Icon, Next To Icon)
    - Battery Estimates
    - Secure QS Tiles Requires Unlocking
    - Quick QS Pulldown (Disabled, Right, Left, Always)
    - Brightness Slider (Never, Expanded, Always)
    - Brightness Slider Position (Top, Bottom)
    - Auto Brightness Icon
    - Hide Labels
    - Label Text Size
    - Smart Pulldown
    - Vertical Layout
    - Columns In Portrait (2-5)
    - Columns In Landscape (2-6)
    - QS Tile Animation Style (3 Styles)
    - QS Tile Animation Druations (3 Speeds)
    - QS Tile Animation Interpolator (8 Styles)
    - Vibration On Touch
    - Vibration On Touch Duration
    - QS Footer Warnings
    - Show Data Usage
    - User Account Icon
    - Edit Icon
    - Power Menu Shortcut
    - Running Services Shortcut
    - Settings Shortcut
    - Clear All Button (10 Styles, 5 Backgrounds)
    Power Menu
    - System Settings (Hold PWR Assistant + Hold Duration)
    - Disable Power Menu On LS
    - Power
    - Restart
    - Advanced Reboot Options
    - Screenshot
    - On-The-Go Mode
    - Settings
    - Lock Down
    - Emergency
    - Device Controls
    - Users
    - Logout
    - Bug Report
    - System Settings
    - Quick Tap
    - Volume Button Playback Control
    - Swipe To Screenshot
    - Brightness Control
    - PWR Button Torch
    - Double Tap To Sleep Status Bar
    - Double Tap To Sleep Lock screen
    - AOSP Gestures
    - Pill Length
    - Pill Radius
    - Hide IME Button Space
    - Back Gesture Animation
    Lock screen
    - Edge Light
    - Always On Fingerprint
    - UDFPS Icon Picker (55 Styles)
    - UDFPS Animation Picker (38 Styles)
    - Lock screen Charging Info
    - Hide Status Bar
    - Hide QS During Secure Lock screen
    - Media Cover Art (5 Filters)
    - Ripple Effect
    - Fingerprint Authentication Vibration
    - Fingerprint Error Vibration
    - Navigation Bar
    - Compact Layout
    - Invert Layout
    - Show Vol Panel On Left
    - Per App Vol Control
    - On-Screen NavBar
    - Reorient Volume
    - Volume Rocker Wake
    - Keyboard Cursor Control
    - Alert Slider Notifications
    - Alert Slider Pulse
    - Block Alert Slider In Pocket Mode
    - Click To Partial Screenshot
    - Screen Off Animation (3 Styles)
    - Power Menu Animations (11 Styles)
    - Android P Animation Style
    - AOD Display Schedule
    - Google Services
    - Parallel Space
    - Game Space
    - Smart Pixels
    - App Lock
    - Launch Music App On Headset Connection
    - Unlimited Photos Storage
    - Unlock Higher FPS In Games
    - Netflix Spoof
    - Pulse Music Visualizer (Navbar, LS, Ambient)
    - Volume Panel Timeout
    - Jitter Test
    - Ignore Secure Window Flags
    - Show CPU Info
    - Toast App Icon
    - Sensor Block Per Package
    - Wakelock Blocker
    - Alarm Blocker
    - Default USB Configuration
    - Radio Info
    Evolution X Launcher
    - Icon Packs
    - Notification Dots
    - Icon Size
    - Icon Font Size
    - Max Lines For App Label
    - Lock Layout
    - Add App Icons To Home
    - Dark Status Bar
    - Double Tap To Sleep
    - Wallpaper Scrolling
    - Wallpaper Zooming
    - At A Glance
    - Swipe To Access Google Feed
    - Hide/Show Status Bar
    - Top Shadow
    - Icon Labels On Desktop
    - Hotseat Background
    - Google Search bar
    - Themed Icons
    - Corner Radius
    - Themed Icons In App Drawer
    - App Drawer Search bar
    - Icon Labels In App Drawer
    - App Drawer Row Height
    - App Drawer Background Opacity
    - Recents Background Opacity
    - Recents Scroll Vibration
    - Recents Screenshot
    - Recents Google Lens
    - Recents Clear All
    - Suggestions In All Apps List
    - Suggestions On Home
    - Blocked Suggestions
    - Parallel Space
    - Taskbar
    - Rotation
    - Hidden & Protected Apps


    You tell me :cool:



    Please note that the Required February firmware images are shipped with these builds. However, you will need to be on STOCK stable January/February prior to following these instructions, not QPR BETAS OR A14DP! This includes having custom kernels installed. STOCK MEANS STOCK!

    First Time Install
    1. Download vendor_boot & rom for your device from here
    2. Reboot to bootloader
    3. fastboot flash vendor_boot vendor_boot.img
    fastboot reboot recovery
    4. While in recovery navigate to Factory reset -> Format data/factory reset and confim to format the device.
    5. When done formatting, go back to the main menu and then navigate to Apply update -> Apply from ADB
    6. adb sideload (replace "rom" with actual filename)
    7 (optional). Reboot to recovery to sideload any add-ons (e.g magisk)
    8. Reboot to system & #KeepEvolving

    1. Reboot to recovery
    2. While in recovery, navigate to Apply update -> Apply from ADB
    3. adb sideload (replace "rom" with actual filename)

    4 (optional). Reboot to recovery to sideload any add-ons (e.g magisk)
    5. Reboot to system & #KeepEvolving


    1. Check for update. If available, select "Download and install" (approx 10-15 min)
    2. Reboot & #KeepEvolving


    Commonly asked questions & answers:

    Q: Why am I getting "error cannot read" while attempting to sideload the ROM
    Well, you should be using the latest platform-tools and have it added to PATH. A lot of unofficial drivers floating around on the internet install outdated adb/fastboot along with the drivers. Please refrain from installing these as well as minimal adb & fastboot; Use the official google driver and official platform-tools instead.

    Alternatively you can prefix each adb/fastboot cmd with ./ while in the platform-tools folder via powershell or bash, etc.

    For example:
    ./adb sideload ./

    This basically tells the shell "Hey, I want to execute this local binary rather than the one in PATH".

    Q: I'm a windows user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?

    Q: I'm a linux user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?

    Q: Will you release builds in the format?
    No, we will not be releasing builds in that format due to a handful of reasons; The main reason being that it is not able to be installed via OTA and is incompatible with our official devices infrastructure.

    Q: Why is MTP and/or Android Auto not working?
    Set the default USB configuration in Settings > The Evolver > Miscellaneous > USB Configuration

    Don't see your question? Well, feel free to post a comment in this thread, we will reply as soon as we can. We'd appreciate if users used XDA FIRST and the telegram group as a LAST RESORT.

    To be continued (I'm sure).

    Custom Kernels:

    Custom kernels may be flashed at YOUR OWN RISK. However, we will not provide extended support regarding such and it is up to YOU, the end user to make your reports in the appropriate thread for X kernel, not in this thread.

    Obtaining root:
    Let it be known that we will not assist anyone with bug reports until they have disabled all modules and restored to the default, unpatched kernel that is shipped with the ROM!

    Root can be obtained by either one of the following methods.

    1. Download the Magisk.apk on your pc (you can change the file extension to .zip if you wish, though it is not required.
    2. Reboot to recovery
    3. Navigate to Apply update -> Apply from ADB
    4. adb sideload magisk.apk (replace "magisk" with actual filename)
    1. Download the full from post #2 of this thread
    2. Download payload-dumper-go that corresponds to the architecture of your pc
    3. Run payload-dumper-go against the
    4. Grab boot.img from the extracted folder and transfer it to your device
    5. Patch the boot.img with the magisk application and transfer the patched image to your pc
    6. Reboot to bootloader
    7. fastboot flash boot boot.img (replace "boot" with actual filename)

    When an OTA update is available, let it download and install. Before rebooting simply open Magisk Manager and click on the first "install" button and select "install to inactive slot". Once it's done, reboot and enjoy.

    Reporting bugs and submitting logs:

    In most cases logs should be provided when reporting bugs. This can be done by enabling USB debugging in developer options of the device, connecting it to your PC and running one of the following cmds depending on the type of bug/issue while reproducing it:

    General system log
    adb logcat > logcat.txt

    Kernel log
    adb shell su -c dmesg > dmesg.log

    Please provide a detailed description of the bug/issue as well as link/upload the log you had taken.
    There are exceptions to this as some issues are unable to be caught in logs. In this case, it is expected that users provide clear and accurate steps to reproduce the issue.

    Getting involved in the development:

    We've set everything up in such a way where all you need to do is install AOSP build dependencies, initialize a repo client, init the tiramisu-pixel branch of our manifest, sync the code and lunch your device (e.g lunch evolution_cheetah-userdebug); Roomservice will automatically sync all device specific dependencies for you to compile without error. There is no need to manually clone anything due to this and applies to Pixel 6, 6 Pro, 6a, 7 & 7 Pro (oriole, raven, bluejay, panther & cheetah).

    Device and ROM source changes can be submitted on github to the appropriate repositories by making pull requests via comparing forks. Please follow the google patch format for commits and triple check your changes by compile testing and verifying they're correct. Please retain proper authorship if you are not the author!
    custom kernel blu_spark etc. in 2023-02-12 version not work, error vendor_dlkm. Previous version Evolution, custom kernel work fine.

    Not my problem to deal with.