Same thing happened to me using Waze with Evo 7.8 last week.
I haven't had this problem yet with version 7.9.
[ROM][13.0_r49][OFFICIAL] Evolution X 7.9.2 [06/02/2023]
- Thread starter Manidweep
- Start date
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!
unfortunately no , i tried various methods that my L1 certification will remain intact and certain ID number should be 5 digits but it always show 8 digits so i stopped trying. not worth the effort
I woke up with exactly this issue, power + vol up only way to boot. It's concerning because I use the phone as a sleep alarm as many do.
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..
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?
Hi every one, I hope I'm doing nothing wrong asking here for help 
I made a series of mistakes, I hope someone can help me.
I have a DDR4 256GB EU version of OP8T, I flashed some days ago the firmware version F63 (first mistake, I read in OP forums it had heavy battery drain, as I noticed).
I flashed the F62 (Maybe second mistake). It seemed all great, but suddently the phone got stuck for a couple of minutes (screen on or off, no responses con buttons or touch) and then it rebooted (on for a couples of minutes, the all again)
I had the 230505 rom, so I decided to flash the 230405 (third fatal mistake).
Now I can get to the recovery and sideload, but I cannot sideload any rom with success, and the system boot warns me to boot due to failure. If I try to reboot anyway, It just asks me for Factory Data Reset.
1. Have I lost my sdcard data forever? (adb pull sdcard/) gives me errors, other tools make me browse sdcard, but it seems void. I tried an unofficial TWRP but it got worse
2. If I did lose all my data and proceed with factory reset, I risk to get worse? any suggestion to recover the phone at least?
I attached the recovery logs so far.
PS: I'm not new with Custom Roms, but my las one was on Nexus 5at least 6y ago.
I love this rom by the way.
Thanks!
EDIT:
I recovered most of my sdcard files looking under /data/media/0 instead of /sdcard loading OrangeFox recovery. (adb pull gave me errors due to files name). Then I wiped all the personal data and it booted properly.
I made a series of mistakes, I hope someone can help me.
I have a DDR4 256GB EU version of OP8T, I flashed some days ago the firmware version F63 (first mistake, I read in OP forums it had heavy battery drain, as I noticed).
I flashed the F62 (Maybe second mistake). It seemed all great, but suddently the phone got stuck for a couple of minutes (screen on or off, no responses con buttons or touch) and then it rebooted (on for a couples of minutes, the all again)
I had the 230505 rom, so I decided to flash the 230405 (third fatal mistake).
Now I can get to the recovery and sideload, but I cannot sideload any rom with success, and the system boot warns me to boot due to failure. If I try to reboot anyway, It just asks me for Factory Data Reset.
1. Have I lost my sdcard data forever? (adb pull sdcard/) gives me errors, other tools make me browse sdcard, but it seems void. I tried an unofficial TWRP but it got worse
2. If I did lose all my data and proceed with factory reset, I risk to get worse? any suggestion to recover the phone at least?
I attached the recovery logs so far.
PS: I'm not new with Custom Roms, but my las one was on Nexus 5at least 6y ago.
I love this rom by the way.
Thanks!
EDIT:
I recovered most of my sdcard files looking under /data/media/0 instead of /sdcard loading OrangeFox recovery. (adb pull gave me errors due to files name). Then I wiped all the personal data and it booted properly.
Last edited:
What instructions to follow for coming from another custom ROM? Dirty flash (update) or clean?
AnierinB
Recognized Developer
That has already been added back and will be available in June releases. In the meantime, you can use this newer version of the launcher:
First of all I like to thank all the developers who worked so hard to import the rom for OnePlus 8.
I was using Redmi K20 pro with this rom, where the stock camera was included in the rom. It would be great if stock camera or ANX Camera would be included instead of the provided camera so that we can have a better experience. The provided camera has a very limited feature which made it unusable.
Moreover, the stock rom has Dolby Atoms and Dolby Vision. If that would be imported, that would be best!
I was using Redmi K20 pro with this rom, where the stock camera was included in the rom. It would be great if stock camera or ANX Camera would be included instead of the provided camera so that we can have a better experience. The provided camera has a very limited feature which made it unusable.
Moreover, the stock rom has Dolby Atoms and Dolby Vision. If that would be imported, that would be best!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
Nameless AOSP is a nice one, along with CrDroid. You'll have to get into their telegram groups for updates, nameless does not use XDA much abs CrDroid has a few hotfixes only on telegram. -
68Evolution X 7.9.2 for the OnePlus 8, 8 Pro, 8T & 9R [instantnoodle] [instantnoodlep][kebab][lemonades]
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)
Check out our website!
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 AppsCode: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
• Google restore isn't functioning at this time.
You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
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)- Android version: 13.0_r49
- Security patch level: May 2023
- Build author: Anierin Bliss
- Kernel Source: https://github.com/Evolution-X-Devices/kernel_oneplus_sm8250
- Clang version: 14.0.6
- ROM Developer: joeyhuab
- Source code: https://github.com/Evolution-X
25rom:
recovery:
vbmeta:
rom:
recovery:
vbmeta:
rom:
recovery:
vbmeta:
copy_partitions:
rom:
recovery:
vbmeta:
copy_partitions:
17Updates 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
#KeepEvolving13
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".12Commonly 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 runadb/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 runadb/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!
New posts
-
-
-
[Guide] Convert OnePlus 8T Cyberpunk Edition- Latest: EnriqueHodges
-