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

Search This thread

AnierinB

Recognized Developer
Amazing ROM running perfect on my pixel 7 pro thank you to everyone.

Any help i followed the steps to patch the .img boot for magisk everything installed but magisk is still showing installed N/A
Do I need to download the original firmware boot?.

Cheers
Did you sideload magisk directly after sideloading the ROM?
Sideloading the ROM installs to the inactive slot. Magisk installs to the active slot.

When you reboot after sideloading the ROM, the previous inactive slot (the one you just installed to) becomes the active slot; Which is why you need to reboot to recovery after sideloading the ROM prior to sideloading magisk.
 
Last edited:

Crazyiain

Member
May 16, 2019
14
1
Did you sideload magisk directly after sideloading the ROM?
Sideloading the ROM installs to the inactive slot. Magisk installs to the active slot.

When you reboot after sideloading the ROM, the previous inactive slot (the one you just installed to) becomes the active slot; Which is why you need to reboot to recovery after sideloading the ROM prior to sideloading magisk.
Thank you so much all sorted and hopefully now working lol time to test some modules..
 
  • Like
Reactions: AnierinB

zacattackkc

Member
Feb 24, 2011
29
18
OnePlus 9
Google Pixel 7 Pro
Do you guys flash using a proper data cable? Some time ago I was using a not that good cable for sideloading ROMs on my Pixel 6 and it got stuck again and again until I used the original cable. By now I got me a high quality pretty long cable and all works. Seems like the newer Pixels in combination with some USB hubs/controllers don't like every cable.
I noticed when flashing to always use powershell if you're using windows 11, and ALWAYS on any windows environment or any terminal app, if it seems to get stuck, its because you pushed it into a background process. while its flashing, don't touch your pc. if you do have to press off of the window while flashing, click back on it and press the down arrow key.. mine freezes sometimes until I do this. See if this helps.
 

Lughnasadh

Senior Member
Mar 23, 2015
4,947
5,704
Google Nexus 5
Huawei Nexus 6P
Do you guys flash using a proper data cable? Some time ago I was using a not that good cable for sideloading ROMs on my Pixel 6 and it got stuck again and again until I used the original cable. By now I got me a high quality pretty long cable and all works. Seems like the newer Pixels in combination with some USB hubs/controllers don't like every cable.
Yeah, there are a ton of stories from people with Pixel 6 & 7s where just a change in cables and/or ports fixed flashing problems.

Seems like using an A to C cable with USB port 2.0 is a popular remedy.
 
  • Like
Reactions: t-ryder

Confetti_Lemon

New member
Jul 16, 2022
2
0
I don't know if it's just me but I noticed a bug where media sound only plays through the top speaker and ring only plays through the bottom speaker
 

jacobas92

Senior Member
Dec 21, 2010
900
208
Bristol, TN
Has anyone had issues passing safetynet with magisk? I used kdrag0ns fix and made sure to do all necessary denylist config. still getting cts profile mismatch. I guess my next step is to try spoofing that but I can't for the life of me recall what magisk module I'd need for that. Also I did disable the netflix enable switch in the evolver.
 

AnierinB

Recognized Developer
Has anyone had issues passing safetynet with magisk? I used kdrag0ns fix and made sure to do all necessary denylist config. still getting cts profile mismatch. I guess my next step is to try spoofing that but I can't for the life of me recall what magisk module I'd need for that. Also I did disable the netflix enable switch in the evolver.
It's a server side issue on googles end regarding CTS since this morning on multiple device, not just p7 series running customs. Please keep in mind this is separate from SN not passing by default without modules (which was already fixed, but now there's this).
 

fuadhdmini

Senior Member
Oct 16, 2010
545
121
Xiaomi Mi 10
Google Pixel 5
Hi. Thanks for the rom. gonna try it tonight. And for the guide to root just by sideloading magisk.apk, thats really a nice one.

So moving forward, if there's an OTA update, I can just check in system updater app and trigger update and right before restart, open magisk app to install to inactive slot?
 

AnierinB

Recognized Developer
Hi. Thanks for the rom. gonna try it tonight. And for the guide to root just by sideloading magisk.apk, thats really a nice one.

So moving forward, if there's an OTA update, I can just check in system updater app and trigger update and right before restart, open magisk app to install to inactive slot?
Correct
 

Tintin62

Senior Member
Aug 1, 2020
75
24
Yous said 'Be on the official stock January release from google'.
My Pixel 7 Pro is with February release. Can i install EvoX despite everything.
Is vendor_boot always correct, should I wait for the EvoX update (February) ?
 

donpablo80

Member
Dec 12, 2011
37
9
Google Pixel 7 Pro
Hi! Thanks fot the rom! The fingerprint issue that a lot of users have in stock rom is gone! really quick now.
I only have a problem flashing magisk:

ERROR: recovery: footer is wrong
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21

What to do?

Thanks!
 

jacobas92

Senior Member
Dec 21, 2010
900
208
Bristol, TN
It's a server side issue on googles end regarding CTS since this morning on multiple device, not just p7 series running customs. Please keep in mind this is separate from SN not passing by default without modules (which was already fixed, but now there's this).
Ah, gotcha. thanks. That makes a lot of sense now as I wasn't even rooted and got smacked by google while I was finishing up my grocery shopping yesterday haha. Still my favorite rom so far.
 

AnierinB

Recognized Developer
Yous said 'Be on the official stock January release from google'.
My Pixel 7 Pro is with February release. Can i install EvoX despite everything.
Is vendor_boot always correct, should I wait for the EvoX update (February) ?
It is advised to wait if you want to use Feb fw. The instructions are written the way they are for a reason.
Hi! Thanks fot the rom! The fingerprint issue that a lot of users have in stock rom is gone! really quick now.
I only have a problem flashing magisk:

ERROR: recovery: footer is wrong
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21

What to do?

Thanks!
That's because magisk isn't signed. Click yes when it asks you to continue anyways
 
  • Like
Reactions: donpablo80

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    For convenience of anyone wanting root with the 03-07-23 version (Feb firmware) of Evo, here's the Magisk-rooted init_boot.img that is flashed from bootloader mode.
    3
    Can not sideload latest file. No matter what I try I get:

    Code:
    serving: 'evolution_cheetah-ota-tq1a.230205.002-03070323-unsigned.zip'  (~0%)    adb: failed to read command: Success

    I had to load the old version - that worked. Question is why?
    EDIT: The latest file is ½ the size! I'm guessing it's incomplete or incremental.

    Code:
    serving: 'evolution_cheetah-ota-tq1a.230205.002-02122115-unsigned.zip'  (~47%)

    And why have the last two OTA updates taked over an hour to install?
    1. Being fixed as I type this - SF derped my upload
    2. It's normal for sideloading to stop at 47%.The rest of the process takes place on the device.
    3. We don't use performance mode in our update engine, which prioritizes the process.
    3
    Is used EvoplutionX on my last device and i took the step to flash on my Pixel and was not disappointed.
    Thanks to deliver us this superb Rom, flashing was easy.
    2
    Where do I find the boot.img? In the evolution x file I downloaded or the original stock rom file? I'm trying to root
    Maybe read the OP... Spoiler: you can root by adb sideloading magisk.

    If you want to do it the good ole fashioned way of manually patching you have to use a payload dumper utility to dump the payload.bin inside the Evolution X file. And remember, it's not boot.img (that's for older devices). It is init_boot.img that needs patched for cheetah and panther
    2
    Anyway to pass safety net. I searched for an answer and nothing valid popped up. Thanks
    If you don't root, safety net passes out of the box. If you root here is what I always do to pass safetynet:

    I use Magisk 25.2 delta-6 and Magiskhide is built in. If you use official Magisk you might need the module? idk. But: enable zygisk, hide Google Play Store and Google Play Services in Magiskhide, and flash the latest displax safetynet mod fix as a magisk module: https://github.com/Displax/safetynet-fix/releases

    Reboot. Clear app data on Google Play Store and Google Services.

    Reboot. Check Play Store and your device is Play Certified. Check YASNAC and you'll pass safety net.
  • 42
    Evolution X 7.6.2 for the Google Pixel 7 & 7 Pro [panther][cheetah]

    Banner.png


    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!

    wjBJ2Hk.png


    Code:
    Themes
    
    - 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
    
    Notifications
    
    - 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
    
    Gestures
    
    - 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
    
    Buttons
    
    - 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
    
    Animations
    
    - Screen Off Animation (3 Styles)
    - Power Menu Animations (11 Styles)
    - Android P Animation Style
    
    Miscellaneous
    
    - 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

    sxs3pbW.png


    You tell me :cool:

    DO NOT FLASH GAPPS, ALREADY INCLUDED

    VvzRh0K.png

    Please note that the Required February firmware images are shipped/flashed with these builds!

    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 rom.zip (replace "rom" with actual filename)
    7 (optional). Reboot to recovery to sideload any add-ons (e.g magisk)
    8. Reboot to system & #KeepEvolving

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

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

    OTA

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






    S2t0kJ9.png


    16
    5ac2ab61387ede01016f92acfa122a08338.png
    Commonly asked questions & answers:

    Q: Why am I getting "error cannot read" while attempting to sideload the ROM or are unable to fastboot flash vendor_boot
    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 ./rom.zip

    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 update.zip 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 rom.zip 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 rom.zip
    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!
    11
    It's a server side issue on googles end regarding CTS since this morning on multiple device, not just p7 series running customs. Please keep in mind this is separate from SN not passing by default without modules (which was already fixed, but now there's this).
    Anyways, this was resolved. Builds will be out sometime tomorrow.