[ROM][OFFICIAL] Evolution X 9.0 [07/06/24] (2024)

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?

Use the official Google USB driver

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?

Set up udev rules

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

Firmware update:

FLASHING THE WRONG DDR TYPE WILL SEMI BRICK YOUR DEVICE. THE ONLY WAY TO RECOVER FROM THIS IS BY PURCHASING AN EDL DEEP FLASH CABLE AND USING IT IN-CONJUNCTION WITH MSMTOOL!!

1. Check your DDR type using the following command:
adb shell getprop ro.boot.ddr_type

0 = ddr4
1 = ddr5

if getprop returns an empty value, use the following commands instead (requires root):
adb shellsucat /proc/devinfo/ddr_type
DDR4 = DDR4
DDR5 = DDR5

1. Download and flash the firmware zip that matches your device and DDR type:
8 (instantnoodle)
8 Pro (instantnoodlep)
8T (kebab)
9R (lemonades)

2. Reboot to recovery and then sideload the ROM.

8 (instantnoodle)
8 Pro (instantnoodlep)
8T (kebab)
9R (lemonades)

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)

Retaining root across OTA updates:
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 branch of our manifest, sync the code and lunch your device (e.g lunch evolution_instantnoodlep-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 OnePlus 6, 6T, 7, 7 Pro, 7T, 7T Pro, 8, 8 Pro, 8T, 9R, 9 & 9 Pro (enchilada, fajita, guacamoleb, guacamole, hotdogb, hotdog, instantnoodle, instantnoodlep, kebab, lemonades, lemonade & lemonadep).

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!