Development [ROM][13.0_r82][OFFICIAL] Evolution X 7.9.8 [09/24/2023]

Search This thread

Crush505

Member
Mar 28, 2023
9
2
As reported on the open post you should be on January or February firmware, before flashing the rom

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

There is no such thing here. Please give a link to the full instructions.
 

sronweb

Senior Member
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

There is no such thing here. Please give a link to the full instructions.
Sure? Read just before First Time Install...
 
  • Like
Reactions: Crush505

Crush505

Member
Mar 28, 2023
9
2
There were no instructions before installation. Let me write my first message in English
Hello everyone I have such a problem... I want to download Evolution X to my phone (Pixel 6). I'm doing this for the first time (not an update), everything is according to the instructions. Drivers and all that are installed, the phone is visible in the terminal ( cmd , powershell), executes commands. But when downloading, zip stops with an error of always 47%. The error is this :
ERROR recovery : failed to verify whole-file signature Update package verification work (result 1).
ERROR : recovery : Signature verification failed
ERROR : recovery : error : 21
Install from ADB completed with status 2.
Installation aborted.
After such an installation, it is written in red text at the top: WARNING : Previous installation has failed. Your device may fail to boot if you reboot or power off now.
All these errors come out in one installation. Please tell me how to overcome this problem.
 
Hello everyone I have such a problem... I want to download Evolution X to my phone (Pixel 6). I'm doing this for the first time (not an update), everything is according to the instructions. Drivers and all that are installed, the phone is visible in the terminal ( cmd , powershell), executes commands. But when downloading, zip stops with an error of always 47%. The error is this :
ERROR recovery : failed to verify whole-file signature Update package verification work (result 1).
ERROR : recovery : Signature verification failed
ERROR : recovery : error : 21
Install from ADB completed with status 2.
Installation aborted.
After such an installation, it is written in red text at the top: WARNING : Previous installation has failed. Your device may fail to boot if you reboot or power off now.
All these errors come out in one installation. Please tell me how to overcome this problem.
VvzRh0K.png


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!

Instructions are in the OP. The above is copied from the first post. @sronweb was trying to tell you.
 

Crush505

Member
Mar 28, 2023
9
2
VvzRh0K.png


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!

Instructions are in the OP. The above is copied from the first post. @sronweb was trying to tell you.
VvzRh0K.png


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!

Instructions are in the OP. The above is copied from the first post. @sronweb was trying to tell you.
I'm sorry, I missed this moment. It turns out that before installing Evolution X 7.6.2 I need to install a stable version January or February?
 

maharotzkie

Member
Jul 5, 2010
13
0
im so excited to install the latest 'tq2a.230305.008.c1-04021632 ' on my 6a (bluejay), even though im not sure yet if it will be the official release :D and this one minor thing ive noice. setting a lockscreen shortcuts, from homescreen.
 

Attachments

  • 20230403_093648.mp4
    51.3 MB · Views: 0

kpirnie

Recognized Contributor
Aug 29, 2012
8,710
7,481
MA
kevinpirnie.com
Google Pixel 6 Pro
OnePlus 11
the nice thing is that I already use arch on my pc so I won't have to deal with a vm or wsl
Nice! Unfortunately, I'm stuck relying on Windows. I manage 400+ websites, and the hosting for them... some of them are .Net, so I have to be able to compile once in a great while.

However, I do have a Ubuntu install on an external NVME that I do use on another machine once in a while... but that machine doesn't have nearly enough RAM to compile even a kernel for us LOL
 
  • Like
Reactions: w_tapper

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    9/24 update is tested and confirmed perfect:

    Screenshot_20230924-085602_Settings.png
    2
    Someone help
    I keep getting:
    FAILED (remote: partition (boot) not found)
    Use platform-tools r33.0.3, open a command prompt in the Platform-tools folder.
    Note: The files you are fast booting or side loading also have to be in the Platform-tools folder where the files adb.exe and fastboot.exe are located.
    2
    So just OTA updated and lost "System Updater" from System. I still got the Evolver and Pixel Parts, just the update is now gone.

    Should I just adb sideload the zip?
    As per the changelog, the updater has been disabled in preparation for a14.
    1
    Unlimited Google photos not working.... I have personally using this rom for unlimited Google photos and now it is not working... I hope it is just a bud with the latest build.. nothing else..
    That feature will be removed entirely going forward.

    FYI, The above was posted a few weeks ago by the OP.
  • 48
    Evolution X 7.9.8 for the Google Pixel 6, 6 Pro & 6a [oriole][raven][bluejay]

    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
    - 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

    sxs3pbW.png


    DO NOT FLASH GAPPS, ALREADY INCLUDED

    VvzRh0K.png


    First Time Install
    1. Download boot, dtbo, vendor_boot & rom for your device from here
    2. Reboot to bootloader
    3. fastboot flash boot boot.img
    fastboot flash dtbo dtbo.img
    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


    19
    5ac2ab61387ede01016f92acfa122a08338.png
    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 ./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!

    evox.png
    10
    WOW, I just read through this entire forum thread, every page, word for word (to get up to speed with my PX6Pro) before I flashed it. I did this so I don't have to come here and re-ask the same damn question (a 100th time), instead I RESEARCH it prior!

    I have to say, I am always amazed to see how many greedy, selfish, and unthankful people there are in this world. Us DEVS do this on our OWN time, yet some of you think we OWE it to you. We waste our time to deliver custom ROMs, apps, scripts, ETC., to users with asking for ANYTHING in return. This time could be better spent with our families, or work, or having fun, so NO, we don't owe you a damn thing! This post isn't pointed to any one person, so no one take offense per se, BUT COME, show a little gratitude, or thanks, instead of all the pointless BS! WE need to be kissing the devs butts, to have them continue to bake the ROMs for us. I won't do it anymore, I gave up years ago, after baking ROMs since ICS, but I could NOT HANDLE the attitudes of the users. The demands, demands, demands, with little to no thanks, and getting back NOTHING but grief, so please be careful. If we lose this dev, we won't have this ROM anymore. I am just asking users to wake up and be polite, use a little common courtesy, do some research PRIOR to asking, and do NOT demand, but be thankful!

    THANK YOU AnierinB, I APPRECIATE your time!!! This ROM is amazing!!!