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

Search This thread

AnierinB

Recognized Developer

AnierinB,​

Could you please help? Tried to ADB sideload the latest rom. Now I'm getting this error:

"Active slot: a
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."


I'm heartbroken if I lose my data... :cry:
Did you not bother reading the message right above yours before doing so?..
 

NYFan

Senior Member
May 12, 2011
124
9
OnePlus 8T
So I accidently hit the emergency button the other day and it told me it could not complete the call and to dial an emergency response number. Which leads me to wonder if 911 will work. Can anyone confirm 911 works?
 

AdmiralKirk

Senior Member
Feb 13, 2012
87
88
Manchester
So I accidently hit the emergency button the other day and it told me it could not complete the call and to dial an emergency response number. Which leads me to wonder if 911 will work. Can anyone confirm 911 works?
That is actually an extremely good question. Unfortunately, I haven't had a chance to update to the latest Evo ROM, or I'd offer to test it myself. Currently, running LOS, although I'll be switching back to EvoX after the new year (seriously, after having used OOS11/12/13 and LOS, EvoX seems to be the superior option for my use cases). You can easily test 911 by following the procedure laid out here (https://www.911.gov/calling-911/frequently-asked-questions/) which involves calling your local 911 Administrator's non-emergency number and making sure it's ok to do a test at that time. If they say it's ok at that time, they will tell you exactly what to say once you've dialed 911 to make sure no one gets mad at you. Back when I installed VoIP systems for a living, I had to do this many times. It would probably not be a bad call if someone with the latest Evo were to give this a try (specifically from the lock-screen emergency dialer). That's definitely something you want to make sure is working.
 

NYFan

Senior Member
May 12, 2011
124
9
OnePlus 8T
That is actually an extremely good question. Unfortunately, I haven't had a chance to update to the latest Evo ROM, or I'd offer to test it myself. Currently, running LOS, although I'll be switching back to EvoX after the new year (seriously, after having used OOS11/12/13 and LOS, EvoX seems to be the superior option for my use cases). You can easily test 911 by following the procedure laid out here (https://www.911.gov/calling-911/frequently-asked-questions/) which involves calling your local 911 Administrator's non-emergency number and making sure it's ok to do a test at that time. If they say it's ok at that time, they will tell you exactly what to say once you've dialed 911 to make sure no one gets mad at you. Back when I installed VoIP systems for a living, I had to do this many times. It would probably not be a bad call if someone with the latest Evo were to give this a try (specifically from the lock-screen emergency dialer). That's definitely something you want to make sure is working.
Great response!! I'm going to try this. Didn't know such a thing existed so you taught me something today. Yes this is critical God forbid there is an emergency. That being said Evo-X has been an excellent rom. Not sure about battery life though. Mine is mediocre at best. I did replace the battery right before installijg Evo and it could just be a crappy 3rd party one. Can't find original batteries from one plus anywhere though and they want you to ship them the phone so they can do it if you want one. That's hard to swallow without a backup.
 

AnierinB

Recognized Developer
I didn't. But now I did. For anyone interested, I was able to recover my 8 Pro and data by installing an older version of Evolution X.

IMHO, it should be very clear and documented that updating Evo will only work with a factory data reset...
"Very clear and well documented", you mean as I had mentioned in the previous post as well as all over the device support telegram group? Lol
That is actually an extremely good question. Unfortunately, I haven't had a chance to update to the latest Evo ROM, or I'd offer to test it myself. Currently, running LOS, although I'll be switching back to EvoX after the new year (seriously, after having used OOS11/12/13 and LOS, EvoX seems to be the superior option for my use cases). You can easily test 911 by following the procedure laid out here (https://www.911.gov/calling-911/frequently-asked-questions/) which involves calling your local 911 Administrator's non-emergency number and making sure it's ok to do a test at that time. If they say it's ok at that time, they will tell you exactly what to say once you've dialed 911 to make sure no one gets mad at you. Back when I installed VoIP systems for a living, I had to do this many times. It would probably not be a bad call if someone with the latest Evo were to give this a try (specifically from the lock-screen emergency dialer). That's definitely something you want to make sure is working.
I've tested this on a handful of occasions and It works as intended.
 

centaurium

Senior Member
Mar 7, 2013
97
24
Budapest
OnePlus 8
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".

I think that it should have been the task of the developer to draw attention to the data loss here in this forum and not to expect the user to find out from other forums what the dangers of the update are!!
 

AnierinB

Recognized Developer
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)
 
Last edited:

vacs03

Senior Member
Aug 28, 2010
269
81
QPR1 (December patch) updates based on OOS13 fw/kernel/libs are out now!

8/8 Pro can be updated via OTA as we ship the full firmware package for these devices. Data format is not required for these builds.

need help, i went to update my 8 pro via ota from the 11/25 build, after rebooting it went to recovery and says "can't load android system, your data maybe corrupt", after that i tryed adb sideload and the same thing, I can't boot

my phone was rooted and i applied magisk to inactive slot like always, after the sideload attempt i didn't try to root, but still same error

edit: i tried sideloading the 11/25 build but still can't boot due to data corruption...any way to save my data?
 
Last edited:

Marcyvee

Senior Member
Oct 9, 2015
329
35
need help, i went to update my 8 pro via ota from the 11/25 build, after rebooting it went to recovery and says "can't load android system, your data maybe corrupt", after that i tryed adb sideload and the same thing, I can't boot

my phone was rooted and i applied magisk to inactive slot like always, after the sideload attempt i didn't try to root, but still same error

edit: i tried sideloading the 11/25 build but still can't boot due to data corruption...any way to save my data?
mmmm... I've just finish the download of the OTA on the same device, from the same build... now its finalising the installation.
What do we do?

When did you format data the last time?
 

vacs03

Senior Member
Aug 28, 2010
269
81
mmmm... I've just finish the download of the OTA on the same device, from the same build... now its finalising the installation.
What do we do?

When did you format data the last time?

when I installed evo x sometime begining of november, updated to latest oos12 first and then did a clean install
 

vacs03

Senior Member
Aug 28, 2010
269
81
I didn't. But now I did. For anyone interested, I was able to recover my 8 Pro and data by installing an older version of Evolution X.

IMHO, it should be very clear and documented that updating Evo will only work with a factory data reset...

which older version?

Perfect. We're on the same boat... I'd better to stop the installation.
Which recovery do you have?

evo x, the one that installs with the rom...i tried downgrading the recovery to 11/25 also but no luck
 

Tins790

Member
Aug 1, 2016
12
1
Sorry but i didn't understand. I on oos12 based rom (lastest build). how update che last update? Where is the procedure? Sideload the oos13 rom and after i sideload the lastest build rom?
 

vacs03

Senior Member
Aug 28, 2010
269
81
edit: nevermind

still don't know how to safe my 8 pro data
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    anyone confirming if this bug is still present after this update(20/02) too? I canceled those updates(20/02 & 16/02) just because of it as most of my work apps work on full screen with buttons on both top & bottom edges if the screen.
    I know it is a very low priority bug , but voting it up just for the possible attention of the dev.
    Thank you to the dev(s) for the hard work & dedication.
    The bug is fixed in the latest build. Thank you @AnierinB
    2
    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.
    1
    Hey! Everything works perfectly fine on my Oneplus 8, except one thing: The UBS Access App. This is a Banking authorization app for a Swiss Bank UBS. It just simply gives me an error.
    I know that this ROM passes all safetynet checks, but still this one specific app (which is very important) doesn't work. Can you PLEASE help me?!View attachment 5847197
    Did you try the Shamiko 0.6 Module for Magisk? I have also one Banking App that only works with Shamiko.
    1
    Hello developer, I noticed a bug: if you enable "Additional brightness reduction" then the fingerprint scanner will work very poorly or not work at all, as soon as you disable the option, then everything works
    1
    That is because you use the wrong firmware. Be on F15 and flash EvoX and after everything will work properly.

    Although I don't know if latest build is based on latest F62 firmware, so check OP post.
    I have flashed EvoX on F62 and it works very well 👍
  • 65
    Evolution X 7.6.2 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


    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.62 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.62 for 8T & F.21 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

    Please note that if you are not on F.15 (kebab) or F.19 or above (lemonades) firmware, your proximity sensor will cease to function until you update to said firmware!!

    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!