• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][11.0_r39][OFFICIAL] Evolution X 5.9 - Immortal [07/29/2021]

Search This thread

blasios

New member
Jun 12, 2021
2
1
Hello, can someone help?
I get the error applying update 7 kinstalldeviceopenerror and i don't know what am i doing wrong.
I flashed the recovery and downloaded the rom and use adb sideload command...

Thanks for help!
 

Ramme

Senior Member
Dec 19, 2017
98
38
OnePlus 8T
Slow/Dirty EvoX Fingerprint Recognition Solution:

I almost left this ROM due to the bad/slow/dirty fingerprint reading i was experiencing that i didn't have on OOS stock. I have finally figure out why and corrected the issue by flashing a backup copy of my persist.img i had from OOS OB4 then deleting the fingerprints and then adding them back. The fingerprint recognition is super fast, and never complains now!

Method:

In ADB Shell, enter this command to backup a current copy of the Persist partition (just to be safe)
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist_EvoX.img

Move that from your SD card to a safe storage place.

Note: If you don't have a good persist backup, flash back to STOCK OOS that the fingerprint works good with and use the method above to save a good copy of persist.

Now restore your good Persist image you made or already had from OOS 11:

While on EvolutionX ROM using fastbootd (you MUST be in fastboot D):
Code:
fastboot flash persist persist_backup.img

Just reboot after flashing, then delete your fingerprints and re-add them back.

I am currently also considering switching back to a/this custom rom, but it bothers me a lot that the fingerprint problems are present on all custom roms. If your solution works it would be sensational. Therefore my question, could the developer directly the "persist.img" of OOS in the Rom plant?
Second question: has anyone tried this step and can confirm that it works?
Thank you.
 

Imprezzion

Senior Member
Dec 12, 2011
665
236
Gorredijk
OnePlus 8 Pro
Worked great for me. FP was basically as fast as OOS after doing this. Only reason I went away from this ROM is the fact AOD doesn't turn off with proximity sensor in pocket / wallet cover. Every other ROM does this but even with pocket mode activated the screen just stays on 24/7. Very burn-in intensive and wastes battery like mad.

DotOS and CrDroid both turn off AOD just fine in pocket for example.
 
  • Like
Reactions: Ramme and zement

hd2002

Member
Jan 16, 2011
7
0
I can'n install room v5.8 on 8T- because error 7.
Steps
1- flash recovery 8T
2- format factory
3- apply adb sideload room--> flash 47% error 7
 

Download the ROM and the payload dumper tool. Extract the fastboot files from the downloaded ROM using the payload dumper
Login to fastboot and run the following commands

fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img

Edit:

Or download the attached zip. It will have the payload dumper as well.
1)Download ROM
2) Copy the payload.bin file from the ROM zip to payload_dumper/input directory
3) Run payload_dumper.exe
4) FIles will be extracted to payload_output
5) Copy those files to the fastboot_installer directory
6) Run ROMinstaller.bat
 

Attachments

  • Evolution-X Fastboot ROMinstaller.zip
    10.7 MB · Views: 22
Last edited:
Failing at 47% is normal. Did you actually start the phone afterward?
For me it didnt even start installing. I got a similar error (dont remeber the exact one) like "error applying update 7 kinstalldeviceopenerror " and it failed. But i didnt actually start the phone.

Tried with the recovery mentioned in this thread and also with LOS latest recovery, gor similar error. so went with the payload method.
 

Top Liked Posts

  • 2
    Ok so yep there's definitely an issue with vibration.

    If you see the screenshots attached, you'll notice I've raised the only option plus additional one from Franco..

    Furthermore in the accessibility location when you turn on touch feedback you'll notice that it actually does vibrate to show that it's working but then any more touches don't react to touches.

    Altering the Franco one does indeed alter the strength but it doesn't react as it should except when in the dialer.

    Calls don't vibrate, nor do messages.

    Just thought I'd throw my two cents in there.

    Have tried a few scripts in Franco but no dice.

    Running latest version of Evo.
    1
    Not that I know of, I haven't personally done it on this phone but there is a thread dedicated to this in the guides section on the 8 pro, it's not hard, but the outcome it essentially the same as MSM which is why I'd recommend MSM over it.

    I've fastboot flashed on other phones, just takes longer.
    Thank you for taking the time to respond.
    1
    Can you please provide a link to this build?

    this has all the builds
    1
    I have vibration for messages and for alarm (today in the morning woke up with br br br br ;) ) but equal i set for example in Whatsapp the notification to "Long" its only a very very very short vibrate for all incoming messages.
    The only what i found was with the EVO settings + Franco settings > the vibrations is stronger.

    I think there is a bug in the notifications - vibrations start. So the vibrations-engine get a start flag but there is no time-flag how long... so it start only a 1ms vibrate.
    1
    I have vibration for messages and for alarm (today in the morning woke up with br br br br ;) ) but equal i set for example in Whatsapp the notification to "Long" its only a very very very short vibrate for all incoming messages.
    The only what i found was with the EVO settings + Franco settings > the vibrations is stronger.

    I think there is a bug in the notifications - vibrations start. So the vibrations-engine get a start flag but there is no time-flag how long... so it start only a 1ms vibrate.

    Yep but even feedback from touches aren't registered.

    Either way it's not right.
  • 8
    Someone please help me...I have no idea why this is happening! I need to be able to charge my device...why would something like this happen? I can't fix anything without fastboot right?

    EDIT: Well, after rebooting several times it seems to be working now. Odd. I switched to Radioactive kernel and everything is working as its supposed to.
    Tonight's upcoming releases with July security patch have my own personal kernel based on Los perf with added functionality and features. Hasty has had a lot of performance issues overall so figured it was time to start my own.

    A few things to look forward to:
    1. Compiled with proton clang (version 13.0.0)
    2. Lots of debugging/logspam disabled (saves battery)
    3. 900Mhz gpu OC from radioactive ☢️
    4. Forced (not just games) 240hz touchscreen sampling rate support with DeviceExtras side toggle (not enabled by default)
    5. USB 2.0 force fastcharge of up to 900mA with DeviceExtras side toggle (not enabled by default)
    6. Misc improvements here and there

    And much more to come.
    3
    Anyone know if the boot.img gets updated with every new release?

    Or is it safe to use boot.img from previous release if you're updating to latest build and want to keep magisk?
    The boot img is directly tied to the base you're using.

    EG: if you're on 7.7 on OOS then you'll require the 7.7 patched boot.img

    It's the same dance here, if you can do a dirty update then as the previous poster has explained just click install after OTA and it'll install to the other slot.

    Personally, I'd always do a clean install to avoid issues as it'll be the first thing that's recommended if you do encounter a problem.

    Especially if there's been a base change (5.5 - 7.7) then extract the boot.img and patch it myself then fastboot boot it, then install directly..

    Each to their own.

    In short yes;

    Dirty flash - use magisk OTA
    Clean flash - fastboot then direct
    2
    Anyone know if the boot.img gets updated with every new release?

    Or is it safe to use boot.img from previous release if you're updating to latest build and want to keep magisk?
    No need buddy.

    In the Magisk app, on the Install menu you should have "Install to Inactive Slot" as an option underneath Select & patch and Direct Install once you have it installed properly.

    You do an OTA update, don't reboot. Do the Inactive slot install, then reboot and you get both the OS update and keep magisk hassle free.
  • 34
    Evolution X 5.9 for the OnePlus 8, 8 Pro & 8T [Instantnoodle][Instantnoodlep][Kebab]

    image1.png



    6kaqOxu.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

    What are our features?

    Themes
    - Lockscreen Clock Styles (23)
    - Dark Theme Styles (11)
    - System Fonts (24)
    - RGB Accent Color Picker
    - Accent Colors Presets (64)
    - System Icon Shapes (11)
    - 2020 Pixel Live Wallpapers
    - G-Visual Mod
    - Volume Panel Styles (6)
    - Custom QS Header Images
    - QS Tile Diso
    - QS Tile Icon Styles (18)
    - QS Panel Color Configs

    Statusbar
    - Network Traffic Monitor
    - Clock & Date Options
    - Battery Bar
    - Battery Icon Styles & Percentage Configs (6)
    - System UI Tuner
    - Battery Percent Show/Hide Config
    - 4G/LTE Icon Toggle
    - Roaming Indicator Toggle

    Notifications
    - Heads Up
    - Notification Headers toggle
    - Alert Slider Notification Toggle (For OnePlus Devices Only)
    - Notification light Config
    - Kill App Button Toggle
    - Pulse Edge Lighting
    - In-Call Vibration Options (connect, waiting, end.)

    Quick Settings
    - Quick Pulldown (Right/Left)
    - Smart Pulldown
    - Vibrate On Touch
    - Disable When Locked
    - Hide Battery Icon
    - Notification Header Battery Precent Configs
    - Brightness Slider & Auto Brightness icon Configs
    - Quick Settings Layout Configs
    - Data Usage Visibility Configs

    Power Menu
    - Device Controls
    - Advanced Reboot
    - Optional User Actions (flashlight, etc)

    Gestures
    - AOSP Gestures
    - Back Gesture Configs
    - Toggle To Hide Navbar Pill
    - Advanced Gesture Configs
    - Swipe To Screenshot
    - Status Bar Brightness Control
    - Screen Off Power Button Torch
    - Double Tap To Sleep Status Bar
    - Double Tap to Sleep Lockscreen
    - Screen Off Gestures

    Lockscreen
    - Always On Display Schedule
    - Fingerprint Error Vibration Toggle
    - Fingerprint Authentication Vibration Toggle
    - Custom FOD Icons (26)
    - Custom FOD Recognizing Animations (24)
    - Pocket Detection
    - Charging Info
    - Lock Screen Shortcuts
    - Lock Screen Media Artwork/Notification Configs
    - Lock Screen Music Visualizer

    Navigation
    - Nav Bar Tuner
    - Invert Layout
    - Volume Key Answer
    - Volume Rocker Wake
    - Volume Rocker Playback Control
    - Volume Rocker Cursor Control

    Buttons
    - Volume Rocker Wake Toggle
    - Volume Key Playback Control
    - Keyboard Cursor Control
    - Left/Right Volume Panel Toggle

    Animations
    - Disable Transition Animations Toggle
    - Screen Off Animations (3)
    - Scrolling Cache Configs
    - QS Tile Animations (Flip/Rotate)
    - QS Tile Animation Duration & Interpolator configs

    Miscellaneous
    - Gaming Mode
    - Screenshot Configs
    - Launch Music App On Headset Connection
    - Sensor Block Per-Package
    - Default USB Config
    - Doze Brightness Configs

    sxs3pbW.png

    You tell me?

    DO NOT FLASH GAPPS, ALREADY INCLUDED

    VvzRh0K.png

    First Time Install / Clean Flash
    1. Be on the latest OOS 11!!
    2. Download ROM.zip (link in thread) & Recovery.img (from below)
    3. fastboot boot RECOVERY.img
    4. Reboot to recovery
    5. adb sideload BUILD.zip
    6. Format data
    7. Reboot to system & #KeepEvolving

    NOTE: It is recommended that you use the ROM installer for OnePlus 8T to avoid sideload/installation errors. You can find such installer
    here

    Update / Dirty Flash
    1. Boot into recovery
    2. adb sideload BUILD.zip
    3. Reboot to system & #KeepEvolving

    KEEP IN MIND THERE IS ALSO OTA UPDATES!


    S2t0kJ9.png


    16
    Built in Dolby & OnePlus camera support will be available in the next releases! Stay tuned & #KeepEvolving!
    10
    There was a beta that has the oos camera built in. AB is working on adding it in tho as a few posts have mentioned it's not quite working right yet. I'm hoping to see it soon but gcam is working pretty well
    OnePlus 8:

    OnePlus 8 Pro:

    OnePlus 8T: