Development [CLOSED] [ROM][14.0_r25][OFFICIAL] Evolution X 8.3 [03/05/2024]

Status
Not open for further replies.
Search This thread

AnierinB

Retired Recognized Developer

Google Pixel 6, 6 Pro & 6a
[oriole][raven][bluejay]


banner_style_1.png


Pixel UI, customization and more, we are Evolution X!

Joey Huab - Founder/Lead Developer
Anierin Bliss - Co-Founder/Project Specialist
Akito Mizukito - Co-Founder/Project Manager

Reach us on Twitter! @EvolutionXROM
Check out our website!

features.png


Added features

known_issues.png


DO NOT FLASH GAPPS, THEY ARE ALREADY INCLUDED

installation.png


First Time Install
(Note: These releases include firmware)
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 confirm 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 (fully) 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


source.png
Android version: 14.0_r25
Security patch level: February 2024
Build author: Anierin Bliss
Kernel Source: https://github.com/Evolution-X-Devices/kernel_google_gs201
Clang version: 14.0.7
ROM Developer: Joey Huab
Source code: https://github.com/Evolution-X
 
Last edited:

AnierinB

Retired Recognized Developer
Latest releases

Simply install the updated apk, reboot and clear data for Play store. Afterwards, CTS/Play integrity API will pass again. Root is not required.

(Until this one stops working. In which case, check back here for an updated date and repeat as instructed above. This is not needed if the date above is lower than the date of the latest ROM zip)

(If you root with magisk, you will need to enable magisk hide/force deny list and hide magisk from gms & gms unstable.)



 
Last edited:

AnierinB

Retired Recognized Developer
evo_e.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.

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 discord group as a LAST RESORT.

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 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.img" 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

Build guide:

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!

keep_evolving.png
 
Last edited:

awenthol

Senior Member
Mar 31, 2009
412
28
Iowa, USA
Just bought and am getting my new P6 Pro ROM'd. I am rusty with everything, as I managed a year and a half without updating ROMs etc, on my previous phone (SGS20).

I am running SDK tools that I downloaded yesterday (from android.com)--adb/fastboot, etc dropped in to C:\windows.
Drivers were d/l yesterday (android.com) and attributed to the phone in device manager
Phone is on the Jan '23 official release
Phone is BL unlocked/rooted on stock
vendor_img flashed fine

sideload--Using cmd or powershell, i'm getting:

ERROR: recovery: footer is wrong
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
ERROR: recovery: Failed to find update binary META-INF/com/google/android/update-binary
Install completed with status 2
Installation aborted


Anybody have any advice--any support would be appreciated.
 

AnierinB

Retired Recognized Developer
Just bought and am getting my new P6 Pro ROM'd. I am rusty with everything, as I managed a year and a half without updating ROMs etc, on my previous phone (SGS20).

I am running SDK tools that I downloaded yesterday (from android.com)--adb/fastboot, etc dropped in to C:\windows.
Drivers were d/l yesterday (android.com) and attributed to the phone in device manager
Phone is on the Jan '23 official release
Phone is BL unlocked/rooted on stock
vendor_img flashed fine

sideload--Using cmd or powershell, i'm getting:

ERROR: recovery: footer is wrong
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
ERROR: recovery: Failed to find update binary META-INF/com/google/android/update-binary
Install completed with status 2
Installation aborted


Anybody have any advice--any support would be appreciated.
Sounds like you aren't in Evo recovery. Return to step 2 of the installation instructions and continue with the guide exactly as written.
 

awenthol

Senior Member
Mar 31, 2009
412
28
Iowa, USA
Sounds like you aren't in Evo recovery. Return to step 2 of the installation instructions and continue with the guide exactly as written.

Rebooted computer. Reinstalled drivers. Still nothing. Attached is where I'm doing the sideload...everything matches your instructions.

EDIT: managed to install a different ROM via this method. So, my assumption is there is something wrong with the package.
 

Attachments

  • 20230129_113841.jpg
    20230129_113841.jpg
    1.6 MB · Views: 1,320
Last edited:
  • Like
Reactions: Jan Skokan

AnierinB

Retired Recognized Developer
Rebooted computer. Reinstalled drivers. Still nothing. Attached is where I'm doing the sideload...everything matches your instructions.

EDIT: managed to install a different ROM via this method. So, my assumption is there is something wrong with the package.
There isn't anything wrong with the rom.zip or vendor_boot. Not quite sure what you're doing wrong however I've had multiple people from all three devices confirm the installation process worked for them. Good luck
 
Last edited:
  • Like
Reactions: david72262

bj_xda

Senior Member
Sep 24, 2012
78
14
Chennai
adb sideload is taking forever
anyone else facing this?

Can I flash this with fastboot update rom.zip ?

Stuck here for the last 20 mins:

C:\_Android\platform-tools_r33.0.3-windows\platform-tools\Evo-X>adb sideload evolution_oriole-ota-tq1a.230105.001.a2-01291005-unsigned.zip
serving: 'evolution_oriole-ota-tq1a.230105.001.a2-01291005-unsigned.zip' (~2%)
 
  • Sad
Reactions: darkerm
Status
Not open for further replies.

Top Liked Posts