[ROM][13.0_r43][OFFICIAL] Evolution X 7.9 [05/03/2023]

Search This thread

Neontc

Senior Member
Aug 10, 2012
167
21
Well dang, I suppose it's not a FW issue since I have OnePlus 8 pro. Anything else I can check?
 

KrazyKlutt

Senior Member
Jul 30, 2014
153
28
Do I keep magisk root after adb sideloading the f62 firmware?

[ UPDATE] Yeah I read that it does, and it does. I just wanted to make sure
 
Last edited:

moccor

Senior Member
Apr 3, 2011
326
57
hello I'm new how do you replace "rom" with the real file name) thank you for your help
Easiest way is to right click the zip in file explorer, click "rename", the name is highlighted automatically, then press ctrl+C, then in Windows right click to paste the name. If its a zip, you need to add ".zip" to the end of it without quotes
 

lagaff4437

Member
Jul 20, 2014
21
4
60
Tours
Le moyen le plus simple est de cliquer avec le bouton droit sur le zip dans l'explorateur de fichiers, de cliquer sur "renommer", le nom est automatiquement mis en surbrillance, puis d'appuyer sur ctrl + C, puis dans Windows, de cliquer avec le bouton droit pour coller le nom. Si c'est un zip, vous devez ajouter ".zip" à la fin sans guillemets
ok merci je vais essayer
 

TechForEver

Senior Member
Sep 2, 2017
88
14
How to update firmware:
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!!

Method 1:
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 shell su cat /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.

Method 2
8 (instantnoodle)
8 Pro (instantnoodlep)
8T (kebab)
9R (lemonades)
Hello
This needed if i in latest oxygen 13?
Mean ddr5/4 check needed anymore if someone in oo13 latest?
 

KrazyKlutt

Senior Member
Jul 30, 2014
153
28
This maybe not related to Evolution X but I'm recently noted a subtle display issue along the whole edge of the screen where the power button i located.

It keeps doing this minuscule shift in brightness, easiest notable using dark mode and observing the dark color bg shifting at random.

Looking at it overall I've noted a uniformity issue where that part of the display is slight brighter. So it's possible that the whole display is shifting but it's more notable at that part of the screen.

I've checked this of course with auto brightness off and at a few different brightness levels.

Any thoughts or similar issues?

[UPDATE] Disabling "Smart Display " seems to remedy the flickering, probably caused by the display going from 60-120 back and forth.
I've enable force 120hz in the developer settings instead. Might cause a slight raise in battery usage but that no real issue.

The uniformity issue is this there though, it might be a slight green tint. Reading about those dreaded green bar issues got me thinking that the uniformity is a hardware issue and that it could get progressively worse in time.
 
Last edited:

jabashque

Senior Member
Feb 17, 2017
240
241
Nextbit Robin
LeEco Le Pro3
Has anyone tried a USB C to HDMI adapter with the OP8 and this ROM? It seems like on OOS11, it worked fine for everyone. And then apparently newer OOS it no longer worked. I don't own the adapter so I can't confirm that, but many people say it. So I wonder if it was something Oneplus broke and never fixed, which might work AOSP ROMs 🤔
I noticed that no one replied to you. Yes, this should work, since the fix for that was merged some time ago.
 
  • Like
Reactions: moccor and AnierinB

arslanejaz33

Senior Member
Sep 14, 2013
71
22
Internet
Hello, thanks for the awesome rom VoLTE doesn't worked on any official rom but worked on your rom . One minor thing is how to make Netflix app work it just stays on the logo and then give error device failure 500.-172.Google is of no help
 

scorpio76r

Senior Member
Jan 10, 2016
1,560
568
All over like street lights
Hello, thanks for the awesome rom VoLTE doesn't worked on any official rom but worked on your rom . One minor thing is how to make Netflix app work it just stays on the logo and then give error device failure 500.-172.Google is of no help
In my experience with the volte issue on other official roms, I found that once you boot the rom and notice volte not working if you flash the rom again it usually brings volte back. I have noticed this with custom kernels too. I first noticed this on the oneplus 6t and, later on the one plus 8. You are correct though that this rom works out of the box on first install.
 
  • Like
Reactions: arslanejaz33

vecifiko

Member
Jan 30, 2014
19
5
OnePlus 8T
Redmi Note 10 Pro
Thinking about going on this rom from stock oos13. My main question is how is the phone performing in terms of heating while normal usage ? Also does it heat using on stock 65w charger(before stock oos13 I was on derpfest and never experienced phone heating this much it all started after going to stock rom) so I would like to know how is on evolution x?

Thanks
 

scorpio76r

Senior Member
Jan 10, 2016
1,560
568
All over like street lights
Thinking about going on this rom from stock oos13. My main question is how is the phone performing in terms of heating while normal usage ? Also does it heat using on stock 65w charger(before stock oos13 I was on derpfest and never experienced phone heating this much it all started after going to stock rom) so I would like to know how is on evolution x?

Thanks
I have not experienced any over heating issues on the oneplus 8 at all. Also this rom is 100% better than stock. Just my 2 cents.
 
  • Like
Reactions: vecifiko

nkhater

Senior Member
Dec 1, 2006
661
203
Jerusalem Palestine
Thinking about going on this rom from stock oos13. My main question is how is the phone performing in terms of heating while normal usage ? Also does it heat using on stock 65w charger(before stock oos13 I was on derpfest and never experienced phone heating this much it all started after going to stock rom) so I would like to know how is on evolution x?

Thanks
I see myself charging twice a day, similar ROMs behaviors are the same with manual brightness
 

Kooahe

Member
Nov 2, 2020
26
2
I have an 8t and I'm on another rom. I have already flashed the fw (Wishmasterflo) on the two partitions to install it.

can i skip the step 6 "sideload copy_partitions" and go directly to step 7 for the rom?
 

KrazyKlutt

Senior Member
Jul 30, 2014
153
28
I read that Evolution launcher is replaced with Pixel Launcher, which is a shame, is there an option to apply custom icon packs to the Pixel Launcher? I know that it isn't natively supported but my question is that if the new rom build have an option to do that?
 

BrickL0rd

Senior Member
Dec 29, 2010
247
37
near Vienna
OnePlus 8T
Screenshot_20230329-202532_Pixel Launcher.png

how to remove this?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Anyone else been having issues with the phone randomly turning off? I think it's been happening since I updated to 7.7, and has continued to happen on 7.8.

    To be more clear, it's not exactly the phone powering off per se - it randomly will completely shut down, not even holding the power button turns it back on - and I've only been able to get out of this state by holding power + volume up to force a restart. I haven't noted any pattern to it or preceding events; the screen just freezes for a few seconds before going off and then I can only fix it by the aforementioned method. It has happened both when on youtube, instagram, and many times when the screen is already off (I just notice I can no longer open my phone and have to restart). Doesn't seem to be related to the battery either. Generally it's not a big problem, as it's only happened like max 3x/week, but the biggest problem is when it randomly turns off in the middle of the night, thus making it so any alarms I have set won't go off.

    I can't entirely say it's the ROM fault as I also am rooted, but I never had this problem prior to updating to 7.7 so the timeline certainly coincides. Just wanted to hear if anyone has had similar issues. I haven't been able to make a log or bug report due to the unpredictable nature to it.
    Same thing happened to me after update to 7.9 today. Never happened before.
    2
    As I said above, I had this problem with EvoX 7.8.
    I tried the latest build of LineageOS 20 for a few days and surprise .... yesterday my OnePlus 8T shut down the same way.

    I wonder if it could be a battery issue?

    Since last night, my OnePlus 8T has been running on EvoX 7.9
    No problem but it's too early to see if it will turn off again..
    Unfortunately, I have this same issue to,o found my phone off twice sitting by itself now (v7.9). If this happened to you on Lineage, must be something in the shared code. Unfortunately i'm rooted (no modules) so can't blame rom. Wonder, are you also rooted?
    2
    Same thing happened to me using Waze with Evo 7.8 last week.
    I haven't had this problem yet with version 7.9.
    I also haven't had this since updating to 7.9, which is typically longer than I went prior to updating before having the issues. I'll keep a lookout for this, but based on what I can see it seems like 7.9 may have fixed the issue! Awesome and thank you Anierin!
    1
    Well, besides this fc, I've got non-working hotspot, I can't limit the battery charge, can't copy text from recent apps screen like before and some notifications disappear time to time (particularly Gmail, reset and relogin helps until next update). no complains, but updating without resets seem to break things very quickly
    1. That fc is due to users not clearing data of the app to remove old saved preference states as I have mentioned here 3 times now.
    2. Hotspot works completely fine on my end and you're the only person who's said anything about it so far.
    3. Smart charging is making it's way back into upcoming releases.
    4. Select from recents is a proprietary feature of pixel launcher. So that's why you can't use it anymore, because we switched back to our Launcher3 fork, Evolution X Launcher.
    1
    Oh now I see, thanks. Hotspot somehow is greyed out, I just can't turn it on. Not a problem, I don't use it. I'm trying to reset the OPextras data now and I'm not sure i understand how should I, the menu is seen as com.android.settings in recent applications. Should I clear the settings or do you mean a complete reset of app data?

    You can't access the apps info panel from recents as it is injected into settings via IA and launched from there, so it will show up as Settings. You need to go into the actual app list for system apps and find OPlusExtras, clear its data and reboot.
  • 66
    Evolution X 7.9 for the OnePlus 8, 8 Pro, 8T & 9R [instantnoodle] [instantnoodlep][kebab][lemonades]

    Banner.png


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

    - Team Evolution X -
    @joeyhuab (Founder/Lead Developer)
    @peaktogoo (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
    Code:
    My signature Universal OPlusExtras application:
    - Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer/Notification & Ringer/Refresh rate/ExtraDim/NightLight/ColorSpace)
    - Ambient display gestures (raise2wake)
    - Kcal
    - Per-app refresh rate
    - DC-Dimming toggle
    - Auto HBM toggle (with lux adjustment preference)
    - Power efficient Workqueue toggle
    - MSM touchboost toggle
    - fsync toggle
    - Adrenoboost preference (off, light, medium, aggressive
    - FPS overlay (9 Positions, 11 Colors & accent, 9 Sizes
    - Powershare toggle
    - Game mode toggle (240hz touch sampling rate)
    - USB-OTG toggle
    - USB2.0 Fastcharge toggle
    - System Vibration Strength preference

    sxs3pbW.png

    • Google restore isn't functioning at this time.
    You tell me :cool:

    DO NOT FLASH GAPPS, ALREADY INCLUDED

    VvzRh0K.png

    DO NOT flash instantnoodlep (8 Pro) on instantnoodle (8) or vice versa, else you 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.

    Please note that we ship OOS13 F.10 abl.img on 8, 8 Pro, 8T & 9R to bypass the BL unlocked warning!
    Please note that we ship a Custom logo.img on 8, 8 Pro, 8T & 9R to better match the ROM!


    First Time Install (8 & 8 Pro)
    1. Be on any version of OOS12 or OOS13 (F.63 firmware is included in these builds)
    2. Download vbmeta, recovery, and rom for your device from here
    3. Reboot to bootloader
    4. fastboot flash vbmeta vbmeta.img
    fastboot flash recovery recovery.img
    fastboot reboot recovery
    5. While in recovery, navigate to Apply update -> Apply from ADB
    6. adb sideload rom.zip (replace "rom" with actual filename)
    7. Format data, reboot to system & #KeepEvolving

    First Time Install (8T & 9R)
    1. Be on the latest OOS13 (F.63 for 8T & F.22 for 9R)
    2. Download copy_partitions, vbmeta, recovery, and rom for your device from here
    3. Reboot to bootloader
    4.fastboot flash vbmeta vbmeta.img
    fastboot flash recovery recovery.img
    fastboot reboot recovery
    5. While in recovery, navigate to Apply update -> Apply from ADB
    6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
    7. Repeat step 5 and adb sideload rom.zip (replace "rom" with actual filename)
    8. Format data, reboot to system & #KeepEvolving

    Update (8, 8 Pro, 8T & 9R)
    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. Reboot to system & #KeepEvolving

    OTA

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

    Firmware Update (8, 8 Pro, 8T & 9R)

    24



    17
    Updates are out!

    If coming from the previous 09/16/2022 release, OTA will work. For anyone who hasn't updated to that build, you will need to use the new recovery with support for erofs as pointed out here in order to flash the latest build.

    Changelog:
    • kernel: Enable wireguard kernel backend
    • sm8250-common: Fix disabling A2DP offload
    • sm8250-common: Import audio policy configurations from audio HAL
    • Instantnoodlep: Use 1080p resolution by default
    • base: Save user preferred resolution into persistent data store (restores user set resolution on boot)
    • AlertSlider: Allow UI to work with multiple resolutions
    • SystemUI: Use max Display.Mode in AuthController as well
    • Catch IllegalArgumentException for invalid phone id
    • Fix action bar font family on material themes
    • Fix crash occurred due to null pointer exception
    • KeyguardIndication: Fix glitchy charging info on lock screen
    • Settings: Allow Configuring Navbar Radius
    • StatusBarIconController: Guard yet another function from cast exception
    • SystemUI: Allow using tuner API for Global settings
    • SystemUI: Clean up and fix status bar logo feature
    • SystemUI: More rounded corners
    • SystemUI: Tiny expanding improvement
    • ThemeOverlayController: Remove repeated monet check
    • Use alphaoptimized layout for icons on left
    • base: use a double click effect for charging if there is no amplitude control support
    • core: Fix menu popup ripple
    • core: Fix NPE
    • fixup! frameworks: Add support for clock auto-hiding
    • Reland "Don't enable jdwp by default on userdebug builds"
    • SystemUI: Re-inflate keyguard status bar on theme change
    • SystemUI: Set heap tracking default also with a property like all the other flags
    • base: AudioService: bail out if ringer mode is not recognized
    • apns: Clean up Austrian carriers
    • Evolver: Bring back HeadsUp snooze and timeout options
    • Evolver: Bring back HeadsUp blocklist/stoplist
    • Fix Dark Theme "TURN ON UNTIL SUNRISE" not retained after reboot
    • Fixes crash/race condition when destroyActivity
    • Improve PendingIntent security check compatibility
    • Settings: Add charging vibration settings

    #KeepEvolving
    13
    Not sure why you sound so bitter. Everyone makes his own choices, however one can't deny the reality - the stock OS is better at this point of time than any other ROM.

    I've seen people updating to the latest build of Evo and their data wiped without warning. The developer didn't say a word of precaution in this forum that the users data would be wiped upon the update. That's a critical oversight and logcats will not help getting your data back.

    I won't say anything about other issues I encountered myself. I mentioned them earlier in this forum thread but never got any reply.

    While the sixth version of EvoX (Android 12), which was based on OOS 11 worked quite well (I was very happy with it at some point), everything went downhill when the base was changed to OOS 12, including the newly-introduced absence of OOS cam.

    OnePlus 8 Pro can make some beautiful videos with hyperstabilization, which no other camera applications are capable of. However, the developer straight up said he will never add the native camera back. I understand that quite a number of people couldn't care less about OOS cam, but for many that's something that would prevent from using this ROM.

    Some other Android 13-based custom ROMs for OnePlus 8 series do have OOS cam, which means that the absence of it in EvoX isn't a result of a technical limitation, but rather a result of the developer's unexplained reluctance to implement the feature.

    Everyone has their own views and this is mine. I do understand that all of these custom ROMs are provided for free and on "as is" basis. What I'm saying is that this one In particular isn't stable and feature-rich enough to be a daily driver.
    1. Those builds for OnePlus 8/8Pro were updated to use qcom wrapped key encryption changes (which was clearly in the changelog). It should be a given that any changes to encryption would result in having to format data. I also intentionally mismatched the hashes in our OTA updater system so OTA would fail due to such. You know, there's a "Device Support" link in the OP thread you also could have joined to ask.

    2. I've explained my stance on OOS cam multiple times. Just because "other ROMS" include it doesn't mean I have to. My ROM, my rules. Use something else if you have an issue with that as you're under no obligation to use my ROM, just as I am under no obligation to add anything I don't want to. Also, there are very impressive GCAM mods (with the appropriate XMLS) for OnePlus 8 series and we now ship Aperture from LOS, which just added support for OIS as well as 4k/60fps video recording on main lens + aux lenses.

    3. "What I'm saying is that this one In particular isn't stable and feature-rich enough to be a daily driver." The ROM is pretty stable and full of features, so I don't understand what made you come to that conclusion though you are entitled to your own opinion (emphasis on opinion, as it isn't factual). I believe my user count, the amount of work I put into squashing bugs & working directly with OnePlus LOS devs to fix issues in the base device trees, etc shows the complete opposite of your "opinion".
    12
    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: 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 shell su cat /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.

    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!