Develop Bugs

[ROM][13][T][OFFICIAL] Evolution-X [Z01R][22/10] - Asus Zenfone 5Z ROMs, Kernels, Recoveries, & Othe

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Evolution X 7.2 for the Asus Zenfone 5Z [Z01R]
Code:
/*
* Your warranty is void. Or valid, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
- Report in comments if you find any
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Reboot to Recovery
2. Download the proper ZIP for your device
3. Wipe Data/Cache/System when coming from non-AOSP ROMs
4. Flash the ROM and TWRP.
5. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper ZIP for your device
3. Flash the ROM and TWRP
4. Reboot to System and #KeepEvolving
Light Screenshots / Dark Screenshots / Download
Donate to me! / Official Chat / Device Support
Android OS version: 13.0.0_r11
Security patch level: October 2022
Build author: Aryan Arora
Source code: Evolution-X
Kernel Source code: Kernel
ROM Developer: joeyhuab

Downloads
Official Download Link: https://sourceforge.net/projects/evolution-x/files/Z01R
For guide on how to flash, make use of the following guides:
Rohan's Guide
My Guide
Screenshots have been attached below and in the op.

11th October 2019
1. Initial Ten build.
2. Kernel upstreamed to 4.9.196
27th November 2019
1. Right side notch fix (credits @Rohan purohit)
2. Version bumped to Evo 3.3
3. November security patch.
5th December 2019
1. Update Evo version from 3.3 Wicked to 3.4 Storm.
2. December security patch.
17th December 2019
1. Bump version to 3.5 Wonderland.
2. Add user selectable VoLTE icons
3. Force show date and weather info on lock screen.
And much more…
25th December 2019
1. Upstream kernel version to 4.9.206 (credits: Kailash and @G.S.T)
2. Added asus cam pre-built (credits @Rohan purohit)
13th January 2020
1. January Security patch.
2. Apex supported (Google play security updates enabled)
3. Asus Gallery included (had to remove Google voice recorder, can be installed via play store anyways)
4. Bumped version to Evo 4.0
5. Tons of ROM side changes.
18th January 2020
-Fix Notch Hide(thanks Rohan and GST)
-Start using vendor overlay
-configure vsync event phase offsets
-enable notcutout overlay
-add tweaked init.qcom.post_boot.sh and define contexts
-build powerhal to vendor overlay
-enable UXE in perfconfigstore
-BoardConfig:switch to cortex a-75 CPU_VARIANT
(Credit: GST)
Update 24th February 2020
* Feb Patch.
* Upstream kernel to 4.9.214 (Kailash's Kernel)
* Improve notch.
* Tons of source side changes
Update 4th March 2020
* March Patch.
* Switched to stock kernel 4.9.206
* Evo version bumped to 4.1.69
* Better notch.
Update 14th March 2020
- Fix slow app opening times
- Re-enable apex
- Bring back older vibration pattern
Update 31st March 2020
- Smart Charging Test
- Latest Source
- Upstream stock kernel to 4.9.216
Update 8th April 2020
- Update to Coral's Apr 2020 build fingerprint
- Version bumped to 4.20
- Touchscreen gestures now work
- Use gcc 9.3 to build kernel
- SHRP prebuilt instead of TWRP
- April patch.
- Face unlock and gradients introduced.
Update 1st May 2020
- Re-enable Asus Doze and Pocketmode (Display > Lockscreen > Advanced Settings)
- Added aptx overlay (by Rohan)
- Add pixel offline charging animation (beta)
- Enable wifi_ext
- Move to Derpfest kernel 4.9.220 (by Kailash)
- Removed Smart Charging (didn't work anyway)
- Nuked Snap Cam
Update 20th May 2020
- Introduce Asus Settings (multi vibrations support, log tile and fps overlay tile)
- Add SIM disable toggle
- Fixed touch gestures
- Nuked Asus Cam and Gallery (available as Magisk Module)
- Kernel upstreamed to 4.9.223 (By Kailash)
Update 19th June 2020
- Fix WFD (by Jackeagle).
- Upstream kernel to 4.9.227 (by Kailash).
- Updated to latest touchscreen drivers from 87 update (by Kailash)(should improve gaming).
- Improve face unlock.
Update 18th July 2020
- Add more touchgestures
- Kernel upstreamed to 4.9.230 (by Kailash) and built using gcc 10
- Enable Zygote Preforking (makes app launch faster)
- Add lottie animation in DeviceSettings
- TWRP 3.4 is now prebuilt.
Update 17th August 2020
- Add support for battery health
- Introduce Doze menu in Asus Settings
- Upstream kernel to 4.9.232 (by Kailash)
Update 19th December 2020
- Initial A11 release
- Fixed Bluetooth Audio
- Added Notch Hide (in Developer Options)
- Added DeviceSettings from Android 10
- Add support for battery health
- Upstream kernel to 4.9.247 (by Kailash)
Update 25th January 2021
- Enabled NFC
- Added Touchgestures
- Fixed Notification LED
- Updated kernel to the latest CAF Tag (4.9.227) (by Kailash)
- Minor fixes to improve stability
Update 28th February 2021
- Fix APEX (Google Play Security Update)
- Fixed OK Google Detection
- CTS now passes even if unrooted
- Added Glove Mode ('Increase Touch Sensitivity' in Display Settings)
- Merge latest CAF Tag into kernel (4.9.227) (LA.UM.9.3.r1-01000-sdm845.0)
Update 14th March 2021
- Fixed Biometric Authentication for all apps (by adeveloper79)
- [TEST] ldac audio support for compatible headsets
Update 12th June 2021
- Based on newer LOS based trees and vendor (by Marc)
- Support encryption and enforcing
- Fixed WFD
- Fixed the camera crash bug in some apps
- Nuked NFC till it's fully fixed
- Slightly faster app opening times
- Bring back snap cam
- Hid magisk better (more banking apps should work now)
Update 21st August 2021
- Fixed NFC
- Fixed Google Play System Update and FPS Info for enforcing builds
- Better Deep Sleep
- Upstreamed kernel to 4.9.273 (by Kailash)
- Misc stability fixes
Update 21st December 2021
- Initial Release based on Android 12
- Implemented Signed Build
- Added padding so clock doesn't cutout
- Upstream kernel to 4.9.292 (by Kailash)

There is no evolutionX customisation option in settings.
There is no evolutionX customisation option in settings.

MR.SHEKHARROY said:
There is no evolutionX customisation option in settings.
Click to expand...
Click to collapse
This is just the initial release build, features will be added in later builds.

i think this update messed up my phone because i cant flash any custom rom now. im just getting (ErrorCode:KPostinstallRunnerError) updater process ended with ERROR: 1

idk_anymore said:
i think this update messed up my phone because i cant flash any custom rom now. im just getting (ErrorCode:KPostinstallRunnerError) updater process ended with ERROR: 1
Click to expand...
Click to collapse
That error comes when you don't wipe correctly. Follow the guide correctly and you should be good to go.

AryanAA said:
That error comes when you don't wipe correctly. Follow the guide correctly and you should be good to go.
Click to expand...
Click to collapse
i did wipe dalvik cache, data and system but its not working

idk_anymore said:
i did wipe dalvik cache, data and system but its not working
Click to expand...
Click to collapse
Can you elaborate the exact process you followed?

AryanAA said:
Can you elaborate the exact process you followed?
Click to expand...
Click to collapse
1. I change slot to my inacctive slot
2. installed twrp and went into recovery
3. change back to the first slot and wiped data, dalvik and system
4. installed disable force encryption on both slots
5. tried to install the rom on the first slot and sencond slot

idk_anymore said:
1. I change slot to my inacctive slot
2. installed twrp and went into recovery
3. change back to the first slot and wiped data, dalvik and system
4. installed disable force encryption on both slots
5. tried to install the rom on the first slot and sencond slot
Click to expand...
Click to collapse
You need to reboot to recovery after changing slots. You didn't do it in step 3. You only need to flash ROM on inactive slot.

idk_anymore said:
1. I change slot to my inacctive slot
2. installed twrp and went into recovery
3. change back to the first slot and wiped data, dalvik and system
4. installed disable force encryption on both slots
5. tried to install the rom on the first slot and sencond slot
Click to expand...
Click to collapse
I always had a similar issue even doing all the steps right; in your case, don't do the step 3, rest is fine.
Apparently i found, you need to wipe internal storage via fastboot after flashing DFE.
If I flash DFE (even after wiping internal via twrp) and try to flash a ROM I get similar error 1, wiping internal via fastboot seems to work.

Xadus said:
I always had a similar issue even doing all the steps right; in your case, don't do the step 3, rest is fine.
Apparently i found, you need to wipe internal storage via fastboot after flashing DFE.
If I flash DFE (even after wiping internal via twrp) and try to flash a ROM I get similar error 1, wiping internal via fastboot seems to work.
Click to expand...
Click to collapse
thank you. i followed your step but i wiped both slots after i installed DFE, I then installed twrp and flashed the rom

idk_anymore said:
thank you. i followed your step but i wiped both slots after i installed DFE, I then installed twrp and flashed the rom
Click to expand...
Click to collapse
Cool, glad it worked.
You wiped both the slots from fastboot or twrp?

Xadus said:
Cool, glad it worked.
You wiped both the slots from fastboot or twrp?
Click to expand...
Click to collapse
i wiped them from fastboot

mine says " Updater process ended with ERROR :1 error installing zip file

nimajneb25 said:
mine says " Updater process ended with ERROR :1 error installing zip file
Click to expand...
Click to collapse
Take a little effort to read, the issue was literally discussed in the preceding few posts.

Hello, i tired clean flashing the 3.0 (1011) and for some reason it doesn't boot.
I can see the Google boot animation and the bar below Google logo loading but the ROM doesn't boot; even after keeping it like that for 15-20 mins.
I tired doing this twice, same result; am I doing something wrong, because the 2.1 (0916) version works perfectly fine which I was using until now.

Xadus said:
Hello, i tired clean flashing the 3.0 (1011) and for some reason it doesn't boot.
I can see the Google boot animation and the bar below Google logo loading but the ROM doesn't boot; even after keeping it like that for 15-20 mins.
I tired doing this twice, same result; am I doing something wrong, because the 2.1 (0916) version works perfectly fine which I was using until now.
Click to expand...
Click to collapse
Hmm that shouldn't happen. Can you elaborate your flashing process as pie and ten have the same procedure

AryanAA said:
Hmm that shouldn't happen. Can you elaborate your flashing process as pie and ten have the same procedure
Click to expand...
Click to collapse
I literally followed the tutorial from scratch.
I was on 2.1 previously and flashed stock .98 vendor; followed the entire guide (except flashing DFE because it never works for me even after -w from fastboot) and flashed the ROM in twrp, flashed permanent twrp on both slots, rebooted to twpr and rebooted to system.
I can then see the Google boot animation and that's it, it just keeps loading.

Related

Code:
[COLOR="grey"]/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/[/COLOR]
Introduction
- This ROM is for the Amazon Fire Phone codenamed Kodiak.
Prerequisites for Installation
- Must be running Safestrap v4
Project Status
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
updated: 07 Jan 2016
Reporting Bugs
- Please report bugs here
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...
Fresh Installation
- From Safestrap, go into Wipe Menu and Swipe to perform a factory reset.
- Installation in the Stock Slot is Mandatory
- Flash the ROM File
- Flash Open Gapps of your choice (any arm 4.4 version) - Except Aroma Version
- Flash the latest SuperSU package if you want root
- Reboot
- Enjoy!
Upgrading to new Version
- Flash the ROM
- Reboot
- Enjoy!
- If you previous had GAPPS it will be preserved automatically
- To preserve root between upgrades, you need to setup SuperSU to survive OTA updates.
Changing from another ROM to this one
IMPORTANT: Do NOT reboot until the end of the process
Within Safestrap
- Copy the latest Lineage ROM, Gapps, SuperSU-2.4.6 and cleansystempartition.zip to your phone
- Factory reset
- Flash cleansystempartition.zip
- Flash the rom
- Flash gapps (use latest opengapps, pico or nano)
- Flash supersu 2.4.6
- Reboot
Downloads
*** Please do NOT create any mirrors ***
- LineageOS-11 for Amazon Fire Phone
- Open Gapps
- Latest Xposed for KitKat
- Solarwarez Patched Xposed
Other Downloads
*** Please do NOT create any mirrors ***
- I modified safestrap to protect the /system partition
- So only use this if you need to do a clean install
- To use you flash this first, then immediately flash new, gapps and supersu before rebooting
- Clean System Partition Flashable zip
Source Code
- Kernel Source: Kodiak stock kernel, build number update-kindle-35.4.6.6_user_466000820
Credits
- Cyanogenmod
- LineageOS
- CAF
XDA:DevDB Information
LineageOS-11 Amazon Fire Phone, ROM for the Amazon Fire Phone
Contributors
ggow
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock base of 461-466 and Safestrap v4
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-07-06
Last Updated 2019-05-04

Release Notes / Changelog
04 May 2019
- Security patches up to April 2019
21 December 2018
- Security patches up to December 2018
30 November 2018
- Retire AOSP Browser due to security holes
- Please install an up to date browser of your choice
- Upgrade external/openssl: 1.0.1e -> 1.0.1j
- ANT+: Update to v4.0.0
- giflib: Update to v5.1.4
- bsdiff: Check for corrupt patch
- jhead: Update to cm-13.0 branch
- libexif: Update to android-5.1.1_r38 branch
- e2fsprogs: Update 1.41.14 -> 1.42.9
2018-09-04
- Security patches up to August 2018
- Fixed Youtube crashing (need more testing to confirm)
2018-06-01
- Security patches up to March 2018
- There are no relevant security patches after this date to now.
- Fix Bluetooth LE issue
2018-02-24
- Security patches up to Feb 2018
2017-10-08
-Ported relevant security patches up to October 2017
Older History
2017-10-03
-Ported relevant security patches up to September 2017
- All bluebourne patches are included
2017-07-20
- Security patches up to July 2017
- Fixed boot-loop on upgrade
- Fixed Xposed compatibility - Standard Xposed Framework Build should work
- Added option in Developer Options to Enable/Disable Signature spoofing
- Download link on OP now lists all Lineage-11.0 releases
- Linked latest KitKat Xposed in OP downloads section.
2017-07-05
- Security patches up to June 2017
2017-06-05
- Security patches up to May 2017
2017-04-24
- Ported security patches up to April 2017
2017-03-25
- Ported security patches up to March 2017
2017-01-05
- Switch to LineageOS repository
- Ported December 2016 Security Patches
- Fixed issues preventing latest gapps from being used
2016-11-22
- Ported November 2016 Security Patches
- Add camera HAL wrapper (Work in progress)
2016-10-16
- Ported October 2016 Security Patches
- Removed CM Updater app (not required for unofficial builds)
- Updated backlight auto adjustment
2016-10-11
- Build logcat from source - can now use logcat -C for colour output
- Clean up media codecs
- Xposed fixed: borked implementation of security update was the cause
2016-10-02
- This is a BETA release
- Fixed bluetooth tethering
- Fixed USB tethering
- Adjusted display auto backlight values
- Fixed bug in dual band WiFi detection
- Enabled WiFi background scanning
- Enabled WiFi batch scanning support
2016-09-15
- Ported September 2016 Security Patches
- bsdiff: Add overflow check when checking for a corrupt patch
2016-08-06
- Ported August 2016 Security Patches
- There will be no more updates from Cyanogenmod in this ROM.
- Going forward I will implement/backport fixes etc as necessary
2016-07-26
- Use liboemcrypto.so from hammerhead
- Fix loading of widevine firmware
- Fix loading of keymaster firmware
- Ported July 2016 Security Patches
2016-06-19
- Fix swipe functionality on AOSP keyboard
- Fix crash of AOSP Keyboard on fresh install
- Updated CM Code
2016-06-09
- June 2016 Security Patches Included
- Enable Swipe functionality on AOSP keyboard (Broken)
- Updated CM Code
2016-05-12
- May 2016 Security Patches Included
- Updated CM Code
2016-04-07
- April 2016 Security Patches Included
- Updated CM Code
2016-03-17
- 01 March 2016 Security Patches Included
- Updated CM Code
2016-03-10
- Implemented new backport of Signature spoofing primarily for microG framework
- Signature spoofing now needs to be enabled in Settings->Developer options->Allow signature spoofing
- Fixed crash on initial Setup Wizard
- Updated CM Code
2016-02-16
- Updated CM Code
2016-02-03
- Updated CM Code
- 01 February 2016 Security Patch Included
2016-01-26
- Updated CM Code
2016-01-18
- Fixed battery stats - readings should be as accurate as with FireOS
- Updated CM Code
2016-01-14
- Switch to using Amazon 4.6.6 US Binaries
- Removed CM Camera App due to instability and Flash not working
- Snap Camera HDR or Open Camera are the most stable options
- Fixed 5 GHz WiFi issue (Amazon 4.6.6 binaries)
- Update CM Code
2016-01-11
- Fixed HDCP for wireless display - Enjoy Netflix via Miracast
- Fixed compass, should now show the correct direction
- Improved GPS accuracy - needs testing
- Add voice-handset-hac entry to mixer_paths.xml from Stock 4.6.3 firmware
- 01 January 2016 AOSP security patches included
- Updated CM-11 Code
2016-01-04
- Cleaned up build.prop
- Add launcher rotation setting to build.prop (disabled by default)
- Add lock screen rotation setting to build.prop (disabled by default)
- Updated CM-11 Code
2015/12/23
- Updated CM-11 Code
2015/12/09
- Updated CM-11 Code
- Making baby steps with Camera
- Now able to load the OV680 firmware but still no benefit at the moment
2015/11/25
- Updated CM-11 Code
- NFC is now working
- Fixed bug which prevents phone from entering Deep Sleep Mode
2015/11/19
- Updated CM-11 Code
- Xposed now installs correctly
- Remaining Stagefright fixes are included
2015/11/15
- Updated CM-11 Code
2015/10/24
- Updated CM-11 Code
- Back port signature faking to enable use of microG framework
2015/09/30
- Updated CM-11 Code
- In camera app, fixed upside down orientation for rear camera in portrait and landscape
- In camera app, fixed video recorder crashes
2015/09/25
- Updated CM-11 Code
- Establish 3G/LTE connection faster
- Switch to using 4.6.3 binaries
2015/09/16
- Updated CM-11 Code
2015/08/29
- Updated CM-11 Code
2015/08/10
- Updated CM-11 Code
- Stagefright patches included
- Dirty Flash should be fine.
2015/07/26
- Added back Stock Browser App
- Added back Stock Calendar App
- Changed recommended Gapps in the OP to PA Gapps Modular Pico
- Added Known Issues to OP
- Remove Stock Camera App
2015/07/25
- Updated CM-11 Code
- Build PowerHAL from source
- Fixed random crash occurring in PowerHAL
- Build memtrack library from source
- Build keystore library from source
- Removed oemcrypto library (Responsible for a lot of google play service crashes)
- Haven't had a single crash yet running HDX Nexus Gapps which had the highest rate of occurrences (But early days)
- Setup hardware key options correctly
- Ignore the stock camera app, I was using it for debugging purposes and forgot to remove it.
2015/07/15
- Camera button fixed for taking photos
- Torch fixed
- Made a change to WiFi config - may help with 5GHz connecting without needing channel changes.
- I don't have 5GHz so can't test
- Disabled NFC for now, this should improve battery life due to no repeated startup and failure of service.
2015/07/08
- Partially fixed up camera: Use Open Camera from Playstore
- Selecting video mode in Google Camera crashes the App, need to clear app data to make it work again.
- Pictures taken with the flash are washed out.
- Fixed Battery Stats
- Implemented NFC - Not working
- Removed Stock Calendar app
- Removed Stock Browser app
- Removed Stock Camera app
- Removed unnecessary media kernel modules just taking up space.
2015/07/07
- Fixed Media Playback
v2015/07/06
- Initial BETA Release

Frequently Asked Questions
Question 1:
I installed HDX Nexus Gapps and now want to use Mini Gapps package. However CM-11 seems to preserve HDX Nexus Gapps. How do I fix this?
Answer:
- Flash this in Safestrap
- This wll clean the /system partition ready for fresh installation.
- You will then need flash a new ROM, Gapps etc.
- This is required, as a result of a change I made in the recovery code to protect Safestrap from been wiped out.
Question 2:
My phone doesn't show up when connecting via USB, what's going on?
Answer
- This may help
- Go into Settings->Storage
- Click on the 3 vertical dots in the top right corner
- Select "USB computer connection"
- Then select Connect as "Media device (MTP)"
- Your phone should then appear as a Media Device
Question 3:
How do I get into Amazon's stock recovery?
Answer
- With the phone powered off
- Whilst holding the volume up key, press the power button.
- When it power's on let go of the power button (still holding the volume up key)
- You should end up in stock recovery.
Question 4:
The camera button isn't working on the 2015/07/25 build, how do I fix it?
Answer
- On the lock screen look for the camera icon in the bottom right corner
- swipe it left and select which camera you want as default
Question 5:
When will we get CM-12?
Answer
- Hold the phone, we only just got CM-11 - enjoy!
- We need an updated kernel so we need FireOS 5 with working root
Question 6:
Contribution by: @hijax2001
How do I reset to Factory Stock 4.6.1 - removing CM11/root/Safestrap in the process?
Answer
1) Downloaded Minimum ADB tools, installed to C:\ADB for convenience
2) Downloaded 4.6.1 stock image from http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-33.4.6.1_user_461013320.bin, saved it to C:\ADB and renamed this file update.bin
3) Followed these steps to gain ADB USB access. Alternately, I found out later I could go to Settings on the phone, then to Device, then to "Get info about your Fire" and then tap on the Model Number several times until "Developer Options" comes up. Clicking that will take you to the option to enable "USB Debugging".
4) I also grabbed the Kindle Fire ADB drivers from here for convenience in Step 7 (below)
4) Rebooted into stock recovery by holding Power and Volume Up. Yes, you can do this from anywhere - phone on or off. And yes, you can still get to stock recovery this way even if you have Safestrap recovery installed
5) Use volume down to reach "Apply update from ADB" option then press Power
6) Open Command Prompt from Windows, reach your ADB folder (mine is C:\ADB in this example), type ADB devices. If you see what looks like a serial number (letters and numbers), then ADB is seeing your phone and you can skip to Step 8. If nothing there, follow Step 7.
7) For me, ADB did not initially detect my phone. I ended up having to go into Control Panel in Windows, to Device Manager, find the Fire phone, choose Update Drivers, then Browse My Computer, Let Me Pick, Show All Devices, Have Disk, then find the folder from Step 4 (above) and add Android Composite ADB Interface by hand. Once I did that, I unplugged and replugged the USB to the phone and then typed "ADB devices" again at the ADB command prompt, like in Step 6. There it is! Ok, next step...
8) Type the command ADB sideload update.bin and let the magic happen. When done, reboot the phone and everything is reset.
9) If you're going to sell the phone, or if you don't want all of your Android apps from before repopulating (because some of them just aren't going to work or work correctly under Fire OS), immediately go to Settings/Device and "Factory reset your Fire" - this will wipe the SD partition where the old apps are saved.
Cool side-note, regarding Step 9... I still had Nova launcher available. Running it under Fire OS works great! Nice to have the stability of the Fire OS the hardware desires, along with a zippy, traditional launcher to navigate.
Question 7:
Contribution by: @DatwasEz
MUTE Button does not work during calls, what can I do about this?
Answer:
- Btw on a side note I have noticed that although mute button doesn't work during calls, you can press the pause button for hold, this acts like mute and they can't hear tested myself last night
-
Question 8
Contribution by: @gooserayos
How do I configure Snap Camera HDR for my Fire Phone?
Answer:
- Click the bottom left menu icon then click the "Other" tab
- Check "Show Advanced Settings"
- Go back to "Photo" tab
- Check "Zero Shutter Lag" and (optional) "Denoise"

Congrats
Sent from my SD4930UR using XDA Free mobile app

I wish best of luck for your work
Do you have donation button? Everybody likes coffee

bufferfree said:
I wish best of luck for your work
Do you have donation button? Everybody likes coffee
Click to expand...
Click to collapse
Thank you. Look on one of my posts and it's the yellow button just below my avatar.

Let the games begin
- The Files are up now.
- Appreciate any testing and feedback/comments
- Please report bugs as per the OP.
- Enjoy - it's been long overdue.

ggow said:
- The Files are up now.
- Appreciate any testing and feedback/comments
- Please report bugs as per the OP.
- Enjoy - it's been long overdue.
Click to expand...
Click to collapse
awsome
thanks for your hard work

I'll use my unlocked fire phone as a guini pig
Now to root flash etc on osx lol

hi cant install cm11.zip with safestrap
get failed
phones rooted

m4nik10 said:
hi cant install cm11.zip with safestrap
get failed
phones rooted
Click to expand...
Click to collapse
Can you tell me what the error is you get?
EDIT: Just tried flashing again and it works fine here.

m4nik10 said:
hi cant install cm11.zip with safestrap
get failed
phones rooted
Click to expand...
Click to collapse
Your phone is rooted, right?

sergio687 said:
Your phone is rooted, right?
Click to expand...
Click to collapse
Hello sergio687, did the zip file flash ok for you?

Package can't install over incompatible data

ggow said:
Hello sergio687, did the zip file flash ok for you?
Click to expand...
Click to collapse
I'm at work right now. I'll see if it flashes tonight (Central Time). Which bugs have been reported?
Thanks for your hard work by the way

m4nik said:
Package can't install over incompatible data
Click to expand...
Click to collapse
Before installing perform a factory reset from Safestrap Wipe menu - that should fix it.
I'll add a instruction to the OP.

m4nik10 said:
hi cant install cm11.zip with safestrap / Package can't install over incompatible data
Click to expand...
Click to collapse
I bet 10$ (@ ggow) that the device is not properly wiped. ^^
@ m4nik10 Please choose "wipe" from the (safestrap) recovery menu ➜ swipe to 'factory reset' ➜ reboot into recovery ➜ choose "install" ➜ try the CM11 zip file again.

sergio687 said:
I'm at work right now. I'll see if it flashes tonight (Central Time). Which bugs have been reported?
Thanks for your hard work by the way
Click to expand...
Click to collapse
I have put some known issues in the OP, nothing more that I have seen yet.
No worries

Bingo Bronson said:
I bet 10$ (@ ggow) that the device is not properly wiped. ^^
@ m4nik10 Please choose "wipe" from the (safestrap) recovery menu ➜ swipe to 'factory reset' ➜ reboot into recovery ➜ choose "install" ➜ try the CM11 zip file again.
Click to expand...
Click to collapse
Snap
I have updated the Fresh install instructions in the OP.

2 more bugs... phone tells me “sim card not present“ and Bluetooth can not be enabled.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 17.1 for Galaxy S10 Series​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Working:
- Wifi
- Sound
- mali drivers
- USB tethering
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- GPS
- Cameras (All of them)
- HWcomposer (HWC)
- Signal indicator
- Double tap to wake
- Wireless PowerShare
Not Working
- VoLTE and VoWiFi will not be implemented (for now) as they heavily depand on samsungs framework
To properly report a bug (Please dont report things already on the Not Working list)
a) Logcat
b) /proc/last_kmsg (or /proc/kmsg)
c) /data/tombstones
d) dmesg
Please do not report bugs if you have performed any system modifications excluding gapps installation
Installation instructions
Make sure you are on Q stock firmware (All of the Q firmwares are tested and confirmed to be working, This should be the case with new fws too as long as Samsung doesnt significantly change bootloader trustzone bits)
Download Q twrp from this thread
flash twrp as per given instructions
if you are coming from stock and have encryption enabled format data (Note i said format, Wiping it in twrp is not the same as formating it)
wipe cache, dalvik cache and system
flash LineageOS
If you want to have gapps flash them right after flashing the rom before first booting
Reboot the device
Downloads:
Google drive
Mega.nz
(Select build coresponding to your devices codename, S10e = beyond0lte | s10 = beyond1lte | s10+ = beyond2lte)
sha256 checksums
Code:
93ca94478bd8fa8e95fd513d8aae82b8e3aa0d21484e31ba2098c1e5e6693990 lineage-17.1-20210112-UNOFFICIAL-beyond2lte.zip
afb505986373bbeb10ade91f67765d800f504a933c6b94d88c4013382ab32270 lineage-17.1-20210112-UNOFFICIAL-beyond1lte.zip
06a334e091bdaac91f6c64559b5c9746559178facc7364b5676c39ddaa826a18 lineage-17.1-20210112-UNOFFICIAL-beyond0lte.zip
4668a9cc55f6135403120370e668548a beyond2lte-boot-magisk.img
4954c5f2cbedbc2bbd90362745d93a1d beyond1lte-boot-magisk.img
84ec49e64560477e1df87417dbc4890e beyond0lte-boot-magisk.img
If you need general help or questions feel free to join Telegram group
Gapps
READ BEFORE INSTALLING MAGISK
I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler
Based On Android Q
Changelog
01.12.2021.
- Merged january security update
- Updated magisk boot image to magisk 21.2
- Misc performance and security updates
12.12.2020.
-Merged december security update
- Merged december vendor security update
- Updated magisk images to 21.1
- Synced with los source
11.09.2020.
- Updated vendor to XXU9DTJA
- Switched to more calibrated sensor for Adaptive Brightness
- Merged November 2020. Security update
- Synced with LOS source
10.08.2020.
- Updated vendor to FXXS9DTI8
- Fixed camera and bt issues present in previous build
- Merged october 2020 security update
- Synced with LOS source
- Updates magisk images to latest canary build (turns out it was more stable than beta version)
09.10.2020.
- Merged OneUI 2.5 Kernel and vendor (DTH7)
- Enabled 5GHz tethering
- Updated Magisk images
- Merged September 2020 Security update
- Tuned little core optimizations
- Enabled vibrator intensity control (under accesibility)
- Misc performance and stability improvements
- Synced with LOS source
08.05.2020.
- Imported G97*FXXU8CTG4 vendor changes
- Merged August 2020 system and vendor security updates
- Improved system security and stability
- Synced with LOS source (Check out new extended volume panel)
07.08.2020.
- Imported G97*FXXS7CTF3 vendor changes
- Merged July 2020 security update for both system and vendor
- Misc performance and stability improvements
06.11.2020.
- Merged G97*FXXU7CTF1 kernel source
- Imported G97*FXXU7CTF1 vendor changes
- Removed proximity from always on display (again)
- Updated magisk images to G97*FXXU7CTF1
- Camera and wifi stability and performance improvements
- HWC stability and performance improvements
- Fixed issue where USB tethering under linux would cause kernel panic
- Synced with LOS source
06.03.2020.
- Merged June 2020 System security patch
- Merged June 2020 Vendor security patch (G97*FXXU3ASJD)
- Improved completely back theme
- Misc performance improvements
- Synced with LOS source
05.21.2020.
- Fixed DT2W on AOD
- Added completely black theme (You can access it thru styles settings entry)
- Removed blinking proximity sensor from AOD
- Added usb trust hal that can prevent usb devices from being used if plugged in while device is locked
- Exposed mdnie screen tuning modes
- Moved pin entry area above fingerprint on s10 and s10+ so they dont overlap with sensor
- Cleaned up DT2W implementation
- Added high touch sensitivity mode (Glove mode) (This can also help when using screen protectors)
- Implemented mDNIe powered color calibration (Settings>Display>LiveDisplay)
- Implemented color profiles so you can use natural colors if you wish to do so (Settings>Display>LiveDisplay)
- Next update should add even more color modes powered by mDNIe like negative and greyscale
- Updated magisk kernel images
- Synced with LOS source
05.15.2020
- Fixed boot on latest CTD1 firmware
- added ctd1 dtbo
- exposed all camera instances to external apps
- started working on HRM sensor
- merged CTD1 kernel source
- updated magisk images
- misc performance and stability improvements
05.05.2020.
- Merged G97*FXXS5CTD1 blobs with may 2020 security update
- Merged may 2020 system security update
- Fixed usb tethering issues
04.14.2020.
- Fixed significant motion sensor detection
- merged April system security update
- Added vbmeta into the zip
- Removed unused radio(ril) interfaces
- Merged Note and s10 5g kernels into same tree for easier maintanance
- Switched to source built dtbo
- Updated magisk kernel images
03.31.2020.
- April vendor security update (System is still march as april tags havent been released on aosp yet)
- Rebased kernel on top of G97*FXXU4CTC9
- Added dt and dtbo images to rom
- merged G97*FXXU4CTC9 vendor binaries
- Removed simstat service as samsung fixed dual sim device detection
- Updated boot images to Magisk 20.4
- Misc performance and stability improvements
03.03.2020.
- Merged march system security update
- Merged latest feature drop
- Synced with los source
- merged G97*FXXS4BTB3 vendor binaries
02.27.2020.
- Fixed camera cutout on S10
- Enabled proximity sensor in all apps with proper permissions
- Rewrote sensor impl
- Removed unused parts of lights hal
- Added vendor to the build (This is why rom is larger now)
- Cleaned up lights overlays and power hal handling
(This means vendor partition also gets built from source and can be more customized per aosp needs
instead of relaying on bind mounting over existing drivers)
02.19.2020.
- Fixed BT calls on some devices that had issues with WBS
- Fixed issue where on clean install or after factory reset there were no default notification sounds and ringtones set
- Synced with LOS source
02.11.2020
- Merged 4BTA8 kernel source
- Merged February security update
- Fixed MTP/USB tethering while ADB is enabled
- Synced with LOS source
02.05.2020.
- Rebased kernel on top of samsungs G975FXXU3BSKO source
- Fixed kernel not properly reporting deep sleep state to userspace
- Reimplemented sensor reporting to allow access to proximity sensor to more apps
- Updated build fingerprint to Q one
- Updated TARGET_BOARD_PLATFORM flag to reflect samsungs changes to same
- Removed releasetools which was failing on new-ish twrp releases anyway
- Removed P vndk libs
- Fixed power hal race condition
- Fixed manual network selection
- Performance and stability improvements
26.11.2019.
- Added FOD icons for S10 and S10+
(This will show up any time system or app needs to use fp sensor and will help users locate the sensor)
- Fixed detection of dual sim devices
- Misc performance and stability improvements
20.11.2019.
- Initial public release
XDA:DevDB Information
[ROM] LineageOS 17.1 for S10E/S10/S10+ Exynos , ROM for the Samsung Galaxy S10
Contributors
Ivan_Meler
Source Code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-17.1
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Any stock Q firmware, Latest is recommended
Version Information
Status: Stable
Current Stable Version: 1.7.5
Stable Release Date: 2020-11-09
Created 2019-11-20
Last Updated 2020-11-09

Reserved
Reserved

Reserved
Magisk boot images are provided within each device folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine, Source for given kernel is available at GitHub if you want to compile kernel yourself just run source build.sh devicename e.g. source build.sh beyond2lte, It will produce new boot image in build/ folder, To update magisk you can follow instructions given at this commit enjoy
Do note that you will have to reflash magisk boot image when updating rom

Great job, thank you so much!

I wait for m'y s10e will i be able to keep the original samsung theme from the menu ect ..?

Very nice, thanks for your hard work

:fingers-crossed::fingers-crossed::fingers-crossed:
Welcome LOS 17.0 to S10 exynos family.

thank you ivan u d the best for our samsuung s10, can't wait for the s10 reguler edition

Finally
Btw, magisk still doesn't work?

My only concern is the camera, is there a way we can install the stock S10 camera or a Google camera port on this?

Thanks Ivan!

does magisk work on this buld?

Builds for S10e and S10 are up

Thanks @Ivan_Meler. Nice work, much appreciated. Two questions: Will encryption work? Would you consider releasing the source so we can build and patch in some things?

catormeme said:
does magisk work on this buld?
Click to expand...
Click to collapse
I will post working magisk soon
wora92 said:
Thanks @Ivan_Meler. Nice work, much appreciated. Two questions: Will encryption work? Would you consider releasing the source so we can build and patch in some things?
Click to expand...
Click to collapse
Encruyption will work if you manually enable it in fstab as multidisbaler disabled it, I will release source in near in near future, Just want to sort out note10 series first

Screenshots?
Thanks to the nice work !

Encryption
Ivan_Meler said:
I will post working magisk soon
Thanks Ivan!
Encruyption will work if you manually enable it in fstab as multidisbaler disabled it, I will release source in near in near future, Just want to sort out note10 series first
Click to expand...
Click to collapse
Alternatively you can enable full disk encryption:
Download multidisabler-samsung-1.7
Open the Zip file and navigate to META-INF\com\google\android\
Open update_binary with a text editor
Search for fileencryption=. . . 2/g and add "footer"
so that the line looks like:
fileencryption=[^,]*\(.*\)$/# &\n\1encryptable=footer\2/g
Save the changed update_binary
Install (flash) multidisabler-samsung-1.7 now with the changed fileencryption instructions with TWPR.
Unmount the data partition in TWRP (if it is mounted).
Goto Advanced and open the Terminal in TWRP or use the ADB shell alternatively.
Find your data partition. For the S10/512 GB it should be sda31...
Enter "e2fsck -f /dev/block/sda31".
For the 512 GB device there will be 122804224 blocks.
Resize with "resize2fs /dev/block/sda31 122804220" (in order to make 4 blocks available for the FDE keys).
Check with "e2fsck -f /dev/block/sda31" if all went well. You should see now the size of 122804220 blocks.
Clear Cache and reboot to System.
Now you should be able to encrypt your data in LOS17 with full disk encrpytion.

Magisk guide has been posted here make sure you read it and understand what you are doing before installing it, also do not post any bug reports if you are running any magisk modules that might have caused them

byteXpression said:
Alternatively you can enable full disk encryption:
Download multidisabler-samsung-1.7
Open the Zip file and navigate to META-INF\com\google\android\
Open update_binary with a text editor
Search for fileencryption=. . . 2/g and add "footer"
so that the line looks like:
fileencryption=[^,]*\(.*\)$/# &\n\1encryptable=footer\2/g
Save the changed update_binary
Install (flash) multidisabler-samsung-1.7 now with the changed fileencryption instructions with TWPR.
Unmount the data partition in TWRP (if it is mounted).
Goto Advanced and open the Terminal in TWRP or use the ADB shell alternatively.
Find your data partition. For the S10/512 GB it should be sda31...
Enter "e2fsck -f /dev/block/sda31".
For the 512 GB device there will be 122804224 blocks.
Resize with "resize2fs /dev/block/sda31 122804220" (in order to make 4 blocks available for the FDE keys).
Check with "e2fsck -f /dev/block/sda31" if all went well. You should see now the size of 122804220 blocks.
Clear Cache and reboot to System.
Now you should be able to encrypt your data in LOS17 with full disk encrpytion.
Click to expand...
Click to collapse
Thanks. Did you try FBE too? I tried FBE on LOS 16 but this ended up in a bootloop.

Thx Ivan ! Great work... :good:I really love your work and appreciate the afford.
Looking forward to the source code release making signature spoofing for microg possible.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1 for Galaxy S10 Series​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Working:
- Wifi
- Sound
- mali drivers
- USB tethering
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- GPS
- Cameras (All of them)
- HWcomposer (HWC)
- Signal indicator
- Double tap to wake
- Wireless PowerShare
Not Working
- VoLTE and VoWiFi will not be implemented (for now) as they heavily depand on samsungs framework
To properly report a bug (Please dont report things already on the Not Working list)
a) Logcat
b) /proc/last_kmsg (or /proc/kmsg)
c) /data/tombstones
d) dmesg
Please do not report bugs if you have performed any system modifications excluding gapps installation
Installation instructions
Make sure you are on Q stock firmware (All of the Q firmwares are tested and confirmed to be working, This should be the case with new fws too as long as Samsung doesnt significantly change bootloader trustzone bits)
Download Q twrp from this thread
flash twrp as per given instructions
if you are coming from stock and have encryption enabled format data (Note i said format, Wiping it in twrp is not the same as formating it)
wipe cache, dalvik cache and system
flash LineageOS
If you want to have gapps flash them right after flashing the rom before first booting
Reboot the device
Downloads:
Google Drive
Mega.nz
(Select build coresponding to your devices codename, S10e = beyond0lte | s10 = beyond1lte | s10+ = beyond2lte)
sha256 checksums
Code:
c8b961734a7972e9db9110785ba622d48c65a3c8ada9c611165864b0411f6699 lineage-18.1-20211111-UNOFFICIAL-beyond2lte.zip
fea1d76cb049cf3d83b9863da19dd0c46b70f91cec7c2a820915adb8943a671c lineage-18.1-20211111-UNOFFICIAL-beyond1lte.zip
540c111583147e94076959fdf3ff51c3f8fc2f29ec98949c6a105d936882f8ce lineage-18.1-20211111-UNOFFICIAL-beyond0lte.zip
If you need general help or questions feel free to join Telegram group
READ BEFORE INSTALLING MAGISK
Gapps
I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler
Due to requests from some users I added signature spoofing support to the rom which allows usage of MicroG
you can simply install MinMicroG and grant it needed permissions for signature spoofing to make it work as intended
Based On Android R
Changelog
12.11.2021.
- Merged November 2021. security update
- Further Improved bluetooth in call handling
- Added more advanced burn in protection
- Misc performance and stability improvements
- Synced with LOS source
06.10.2021.
- Merged October 2021. security update
- Improved bluetooth in call handling
- Synced with LOS source
10.09.2021.
- Merged September 2021. Security update
- Synced with LOS source
06.08.2021.
- Merged August 2021. Security update
- Synced with LOS source
10.07.2021.
- Merged July 2021. Security update
- Performance and stability improvements
- Changed sensors handling in doze mode to prevent battery drain
- Synced with LOS source
10.06.2021.
- Merged June 2021. Security update
- Synced with LOS source
06.05.2021.
- Added wifi and portable hotspot overlays
- Merged May 2021. Security update
- Synced with LOS source
08.04.2021.
- Fixed USB C audio input/output
- Fixed charging with device powered off (It also has nice new animation now)
- Merged April 2021. Security update
- Misc performance and stability improvements
- Synced with LOS source
08.03.2021.
- Added signature spoofing support
- Synced with LOS source
05.03.2021.
- Merged March 2021. Security update
- Performance and stability improvements
- Synced with LOS source
06.02.2021.
- Merged February 2021. Security update
- Misc performance and stability improvements
- Modernized AdvancedDisplay app codebase
- Cleaned up the source
- Updated magisk boot images
- Synced with LOS source
06.01.2021.
- Merged January 2021. Security update
- Fixed OpenGapps installation from lineage recovery
- Fixed features that broke with initial 18.1 merge
- Misc performance and stability improvements
- Synced with LOS source
09.12.2020.
- Merged December 2020. security update
- Merged December 2020 feature drop
- Merged S9DTK9 vendor blobs
- Switched to full vndk30 vendor
- Fixed ADB inside of lineage recovery
- Improved brightness handling even more
- Performance and stability improvements
- Updated recovery images provided in 3rd post
- Synced with LOS source
10.11.2020.
- Further improved auto brightness handling
- Merged November 2020. security update
- Performance and stability improvements
- Updated recovery images provided in 3rd post
- Synced with LOS source
03.11.2020.
- Fixed issues with overlays and s10 camera cutout
- Enabled access to fingerprint for apps that were looking for secure biometics device (e.g. paypal)
- Improved automatic brightness handling (Switched to calibrated sensor virtual device which calculates brightness more precisely)
- Pinned SystsemUI and SurfaceFlinger to ram to imrpove responsivness
- Added blur to dropdrown notifications panel
- Enabled device controls from power menu
- Synced with LOS source
- Misc performance improvements
22.10.2020.
- Merged october security update
- Added back mDNIe display tuning options
- Added back a lot of previously non working los features
- Misc performance and stability improvements
- Synced with los source
07.10.2020.
- Initial public release
XDA:DevDB Information
[ROM] LineageOS 18.0 for S10E/S10/S10+ Exynos , ROM for the Samsung Galaxy S10
Contributors
Ivan_Meler
Source Code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-18.0
ROM OS Version: 11.0
Version Information
Status: Stable
Created 2020-10-07

Reserved

Magisk
Magisk boot images are provided in this google drive folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine, Source for given kernel is available at GitHub if you want to compile kernel yourself just run source build.sh devicename e.g. source build.sh beyond2lte, It will produce new boot image in build/ folder, To update magisk you can follow instructions given at this commit enjoy
Do note that you will have to reflash magisk boot image when updating rom

Wow ! Man, very nice job !
So, you stop release for Lineage 17 ?

troufiniou said:
Wow ! Man, very nice job !
So, you stop release for Lineage 17 ?
Click to expand...
Click to collapse
Nah will update that too, Just felt like releasing this because i had some time to sort out issues with it

The version of gapps doesnt matter even if this is android R right?
I can still flash android 10.0 gapps right?

Eidluci said:
The version of gapps doesnt matter even if this is android R right?
I can still flash android 10.0 gapps right?
Click to expand...
Click to collapse
there is link for android 11 gapps in first post under download section

Ivan_Meler said:
there is link for android 11 gapps in first post under download section
Click to expand...
Click to collapse
Oh thank you, my bad

Hi @Ivan_Meler i'm looking to change rom (i'm on hades rom but this one is not support anymore). And i just want to know if i need a custom kernel to improve battery life on LoS rom (this one or 17.1)?
Thanks for your precisions and your work to maintain on devices uptodate !

[Legenda] said:
Hi @Ivan_Meler i'm looking to change rom (i'm on hades rom but this one is not support anymore). And i just want to know if i need a custom kernel to improve battery life on LoS rom (this one or 17.1)?
Thanks for your precisions and your work to maintain on devices uptodate !
Click to expand...
Click to collapse
Battery life should be fine with stock kernel too as most of things are improved power hal side of things

Ivan_Meler said:
Battery life should be fine with stock kernel too as most of things are improved power hal side of things
Click to expand...
Click to collapse
Great. Thanks. I'll go on 17.1 LoS for awhile and will install this one when it will be more "polish".

Hi I don't know why but on previous lineage os ROMs, when I use TWRP and boot.img it would always boot back to recovery everytime I flashed a ROM.

Can you use lineage recovery to flash ROMs?

Ivan_Meler said:
If you want to root build you will have to use Magisk Canary from here, Once in app download Lineage Recovery for your device from Google Drive or Mega Patch image within manager and flash patched image to recovery partition, When booting hold recovery key combination till you get to first warning screen after that release keys and let system continue booting normally
Magisk curently has some issues properly detecting 2si devices so thats why we cant use boot.img without need for key combo for magisk right now, I will look into that in coming days but till then this is viable solution
Click to expand...
Click to collapse
Tried but says magisk still isn't installed please help.

Il be installing it soon to test it, very hype for android 11

FreeRunner2017 said:
Tried but says magisk still isn't installed please help.
Click to expand...
Click to collapse
make sure you followed instructions closely
1. Download recovery image
2. Download magisk canary app and patch recovery image
3. Flash magisk patched recovwry image (lineage recovery) to recovery partition
4. reboot and hold key combination for recovery until first warning screen shows up, after that release key combo
5. you should be in system with root
if you need further assistance im sure someone from telegram group can help you a bit more

Ivan_Meler said:
make sure you followed instructions closely
1. Download recovery image
2. Download magisk canary app and patch recovery image
3. Flash magisk patched recovwry image (lineage recovery) to recovery partition
4. reboot and hold key combination for recovery until first warning screen shows up, after that release key combo
5. you should be in system with root
if you need further assistance im sure someone from telegram group can help you a bit more
Click to expand...
Click to collapse
I did that but I still have no magisk

SD cards on the s10e just dont work, they keep saying its corrupted even after you format them in android itself ive also tried formatting in windows and twrp but same problem.
network traffic indicator can be turned on but never actualy shows up.
after installing magisk it takes apps 20 seconds to open.
if you need logs i will be happy to do so (if i can remember how to do so)

Wow, already an android 11 ROM ? Nice !
Is there the same issues as on L17 regarding bluetooth and front camera ?

Hi Ivan
Thanks for the great work! Awesome to have Android R available so early. Rom is solid.
On S10e i can confirm, it does not read MMC, i also tried formatting etc, not a biggy
On Bluetooth i can confirm that devices working, headphone sound, speakers etc. But on call when phoning, the sound does not come over to the headset.
HDMI Out is glitchy, creates flickering on secondary display, but is random....
Other than that, the rom is smooth and fast. Still checking battery...
Looking forward to developments...

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: Disclaimer
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
EvolutionX for Mi Mix 2 [chiron]
* Evolution X allows users to experience Google's latest Pixel updates while integrating useful features from known custom ROMs.
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Encryption on f2fs doesn't work​Installation
Choose your flavor
1. You can choose between the traditional EXT4 or the new EROFS. This fs affect only to /system and /vendor partitions
2. Magisk doesn't work on EROFS at the moment. Anyway I've included KernelSU on kernel, so you can install if you want KernelSU app in order to get root and flash magisk modules
3. Once selected root partitions fs, you can choose fs for /data and /cache partitions between traditional EXT4 or F2FS
4. Note that EXT4 comes with encryption by default and F2FS comes unencrypted
Decide if you want encryption or not
1. If you want encryption, use EXT4 on /data partition
2. If you prefer to go unencrypted, then use F2FS on /data partition
First Time Install / Clean Flash
1. Due to latest changes, is mandatory to use my last TWRP posted below
2. Reboot into recovery mode
3. Go to Wipe --> Advanced Wipe --> Select Data/Cache --> Swipe to Wipe --> Reboot into recovery
4. If you already have /data on f2fs (or ext4 unencrypted) and want stay that way, skip step 5
5. Go to Wipe --> Format Data (internal storage will be wiped too, backup your data) --> Type yes and accept -->
Reboot into recovery
6. Download the ROM and copy it into internal storage
7. Flash the ROM (and magisk if you consider it, but ONLY on EXT4 version, over EROFS will bootloop)
8. Reboot to system
Dirty Flash over previous Evolution X v7.8
NOTE: Do not dirty flash over old versions earlier than v7.8. In that case do a clean flash
1. Due to latest changes, is mandatory to use my last TWRP posted below
2. Reboot into recovery mode
3. Download the ROM and copy it into internal storage. You must use the same version alteady installed (EROFS or EXT4)
4. Flash the ROM (and magisk if is already installed, but ONLY on EXT4 version, over EROFS will bootloop)
5. Reboot to system
Change /cache and /data filesystem from ext4 to f2fs
1. You must format /data partition, so all your data and internal storage will be deleted. Please backup your files
2. Reboot into recovery mode
3. If already encrypted: Go to Wipe --> Advanced Wipe --> Select Cache and Data --> Swipe to Wipe --> Reboot into recovery
4. Go to Wipe --> Format Data --> Type yes and accept --> Reboot into recovery
5. Go to Wipe --> Advanced Wipe --> Select Data --> Repair or Change File System --> Change File System --> F2FS --> Swipe to Change
6. Repeat step 5 but selecting Cache
Change /cache and /data filesystem from f2fs back to ext4
1. You must format /data partition, so all your data and internal storage will be deleted. Please backup your files
2. Reboot into recovery mode
3. Go to Wipe --> Format Data --> Type yes and accept --> Reboot into recovery
5. Go to Wipe --> Advanced Wipe --> Select Cache --> Repair or Change File System --> Change File System --> EXT4 --> Swipe to Change
Hybrid Mode
You can have /cache and /ext4 on different filesystems, so follow previous instructions to put the partitions on your desired filesystem
Download EXT4 version
googledrive / mediafire
MD5: 0b60ab8b443b3c71c341b09bc921bbec
SHA1: f86bcb67e42cdeb89ff30c586c43dd88a7f35669
Download EROFS version
googledrive / mediafire
MD5: b194ede1855579f244eef66854f0aa8d
SHA1: 079a1561c5f4d17500ca20f992a5bdad2ef448a3
Download latest TWRP
googledrive / mediafire
MD5: 5c4845b2f5378abba303688aca000c46
SHA1: a2d71742f2928817fc3426ecba843c50f3cc4291​
Android OS version: 13.0.0_r43
Build ID: TQ2A.230505.002
Security patch level: May 05 2023
Build author/Device Maintainer: Huexxx
Source code: EvolutionX GitHub repos
Trees and Kernel: Huexxx GitHub repos
Status: Stable
SELinux Status: Enforcing
Release date: 2023-05-07
Buy me a Beer!​

Features / Changelog 2023-05-07
- kernel:
-- Switch to EROFS legacy version (less changes to base 4.4 kernel avoiding possible problems)
-- Switch to Simple Low Memory Killer
-- Add SchedTune and CpuSets Assist
-- Several EAS tweaks
-- Several sched/mm/cpufreq commits
- Source updated (upgraded to android 13.0.0_r43)
Features / Changelog 2023-04-26
- kernel:
-- Backported support for EROFS fs
-- Backported support for Cgroup v2 Freezer
-- Switched to 2SI (two stage init)
-- Added KernelSU support
- Source updated (upgraded to android 13.0.0_r41)
Features / Changelog 2023-03-26
- kernel:
-- Reverted some not wanted commits
-- Some logspam removed
-- Boot time has been reduced by 26 seconds
Features / Changelog 2023-03-07
- Source updates (upgraded to android 13.0.0_r30)
- Kernel: Added several commits regarding EAS and cpufreq
- Trees: Added quota flag to data mount (needed TWRP 3.7.0 with quota support)
- Sepolicy: Address some denials
- Dropped Go version
Features / Changelog 2023-01-28
- Source updates
- New Go version! (with Go Gapps)
Features / Changelog 2023-01-21
- Source updates
- Launcher3:
-- Import widget overlap from Lawnchair
- Kernel updates
- Dropped Flipendo, Turbo and Turboadapter
- Some commits on qcom-caf display hal
Features / Changelog 2023-01-09
- Sources updates
- Switch to OSS libnotifyhal (make proximity sensor work without binder, new lineageos approach)
- Drop vndk-ext packages
- Switch BTAudio to AIDL
- Switch to common fingerprint HIDL
- Config SQLite to operate in MEMORY mode
Features / Changelog 2022-12-28
- Sources updates
-- Switch to EvoX modded Launcher3
- kernel:
-- Some QCom commits
- Downgraded audio and listen blobs to older revision
- Drop Soundtrigger, Renderscript and qti perf stack
- Updated sepolicies
- Misc tweaks
Features / Changelog 2022-12-01
- Fixed problem on latest release (EvoX sources related)
- Update GPS hal and blobs from LA.UM.9.6.3.r1-06200-89xx.0
Features / Changelog 2022-11-29
- Source updates
- kernel:
-- Switch to LLVM tools for compiling
-- Xiaomi updates
-- Backport binder from 5.4-lts
-- Lots of commits/patches
- Updated audio, listen, thermal-engine, display and DRM blobs
- OpenGL ES driver updated to OpenGL ES 3.2 [email protected]
- Updated Display HAL to LA.UM.10.6.2.r1-01900-89xx.0
- Fixed soundtrigger (Ok Google)
- Reenabled thermal-engine
- Lots of thing that I forget now...
Features / Changelog 2022-11-10
- Source updates
- Fixed Night Light
- Fixed LiveDisplay
Features / Changelog 2022-11-08
- Source updates
-- Upgrade to release 13
-- November security patch
-- Readded FaceUnlock
- Screen recorder
-- Limit to 60fps
-- Use AVC 3.2 for performance
Features / Changelog 2022-11-03
- Source updates
- Vendor tree updates
-- Blob cleanup
-- Update ANT+, Bluetooth and PowerOffAlarm blobs
- Avoid dexpreopting prebuilts to save space
- Add more gapps now that system image is smaller
- Add support for Smart Charging
- Replace Pixel Launcher with mod (allow more desktop grids)
- Replace GrapheneOS Camera with latest one from GrapheneOS repos
- Improve selinux policies
Features / Changelog 2022-10-16
- Source updates
Features / Changelog 2022-10-11
- SoftAP:
-- Add list to select Country Code spoof
-- Reenabled ACS
-- Fixed problems disabling hotspot
-- Extend funcionality to QS button
- Fixed DocumentsUI
- Some selinux denials addressed
Features / Changelog 2022-10-08
- SoftAP: Add AP band preference
- Fixed security settings page
- Selinux Enforcing
Features / Changelog 2022-10-06
- Fixed 5GHz hotspot
-- Spoof country code to use US (best option)
-- ACS disabled (it avoids 5GHz bands sometimes)
- Debloated a bit, so many gapps by default
- Added Graphene Camera v16
- Added GoogleCamera to MGC-8.4.300_Parrot043_V1.5
- Selinux permissive atm

Reserved

You are the best Huexxx! Once again, our Mix 2 will be able to enjoy the latest software for another year.
I've been using it for a few weeks now and it works incredibly well. Better performance and battery life than with Android 12.

Is the proximity sensor working properly? Thanks

Yeah, working.

Thanks @Huexxx for your hard work and keeping our Mix 2 alive and up to date!

Hello, I've installed your rom, and it seems to work correctly, but fails the call recording with "Cube recorder" app:
With crDroid rom it worked like a charm, but with this rom, it can record my voice, but not the other side (very bad recording, unusable); I've also tried to install pixelify magisk's module to use its call recording feature, but when I try "record" within a call, it shows "recording failed".
Thanks !

Excellent rom, thank you very much for your great work

PS one question: is it possible to change the carrier name?

rogerty said:
Hello, I've installed your rom, and it seems to work correctly, but fails the call recording with "Cube recorder" app:
With crDroid rom it worked like a charm, but with this rom, it can record my voice, but not the other side (very bad recording, unusable); I've also tried to install pixelify magisk's module to use its call recording feature, but when I try "record" within a call, it shows "recording failed".
Thanks !
Click to expand...
Click to collapse
Take a logcat just after the problem and I can look into it... maybe is selinux related.
Also, A13 is relatively young, and some apps aren't prepared for it.

spoo333 said:
PS one question: is it possible to change the carrier name?
Click to expand...
Click to collapse
IDK man, I haven't navigated through all the settings :/

Thanks for the update
Coming from LineageOS (Android 11) I followed the steps in #1 and updated to recommended TWRP. No problems so far. GPS, NFC, Fingerprint, Bluetooth not tested yet.
SafetyNet pass with Magisk Universal SafetyNet Fix 2.3.1 is working.
P.S. The Quick Settings menu in Android 13 is looking pretty ugly.

ty so much. I cant believe this old device can experience the latest system.

I also come from lineage and I find that the device has become faster with the EvolutionX rom .
Question: Does this unofficial version get any ota updates?
Thanx

rmax78 said:
I also come from lineage and I find that the device has become faster with the EvolutionX rom .
Question: Does this unofficial version get any ota updates?
Thanx
Click to expand...
Click to collapse
It won't probably get OTA updates ever... becuase I'm not planning to make it official.

New release on OP!

@Huexxx Do you plan to release regular (or monthly) updates to all of your 13.0 ROMs (Evolution X, CherishOS, StagOS) in the future?

11insomnium said:
@Huexxx Do you plan to release regular (or monthly) updates to all of your 13.0 ROMs (Evolution X, CherishOS, StagOS) in the future?
Click to expand...
Click to collapse
Yes, I plan to "mantain" them.

Great work, thanks. I wish to have opportunity for automated updates for this ROM installable from settings, or should switch to some other 13 ROM?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: Disclaimer
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CherishOS for Mi Mix 2 [chiron]
* Has a Pixel UI noodles by Hung Phan. So many features that you probably won't find in any ROM. All you can dream of and all you'll ever need. Just flash and enjoy...
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Encryption on f2fs doesn't work​Installation
Choose your flavor
1. You can choose between the traditional EXT4 or the new EROFS. This fs affect only to /system and /vendor partitions
2. Magisk doesn't work on EROFS at the moment. Anyway I've included KernelSU on kernel, so you can install if you want KernelSU app in order to get root and flash magisk modules
3. Once selected root partitions fs, you can choose fs for /data and /cache partitions between traditional EXT4 or F2FS
4. Note that EXT4 comes with encryption by default and F2FS comes unencrypted
Decide if you want encryption or not
1. If you want encryption, use EXT4 on /data partition
2. If you prefer to go unencrypted, then use F2FS on /data partition
First Time Install / Clean Flash
1. Due to latest changes, is mandatory to use my last TWRP posted below
2. Reboot into recovery mode
3. Go to Wipe --> Advanced Wipe --> Select Data/Cache --> Swipe to Wipe --> Reboot into recovery
4. If you already have /data on f2fs (or ext4 unencrypted) and want stay that way, skip step 5
5. Go to Wipe --> Format Data (internal storage will be wiped too, backup your data) --> Type yes and accept -->
Reboot into recovery
6. Download the ROM and copy it into internal storage
7. Flash the ROM (and magisk if you consider it, but ONLY on EXT4 version, over EROFS will bootloop)
8. Reboot to system
Dirty Flash over previous CherishOS v4.7.5 or later
NOTE: Do not dirty flash over old versions earlier than 4.7.5. In that case do a clean flash
1. Due to latest changes, is mandatory to use my last TWRP posted below
2. Reboot into recovery mode
3. Download the ROM and copy it into internal storage. You must use the same version alteady installed (EROFS or EXT4)
4. Flash the ROM (and magisk if is already installed, but ONLY on EXT4 version, over EROFS will bootloop)
5. Reboot to system
Change /cache and /data filesystem from ext4 to f2fs
1. You must format /data partition, so all your data and internal storage will be deleted. Please backup your files
2. Reboot into recovery mode
3. If already encrypted: Go to Wipe --> Advanced Wipe --> Select Cache and Data --> Swipe to Wipe --> Reboot into recovery
4. Go to Wipe --> Format Data --> Type yes and accept --> Reboot into recovery
5. Go to Wipe --> Advanced Wipe --> Select Data --> Repair or Change File System --> Change File System --> F2FS --> Swipe to Change
6. Repeat step 5 but selecting Cache
Change /cache and /data filesystem from f2fs back to ext4
1. You must format /data partition, so all your data and internal storage will be deleted. Please backup your files
2. Reboot into recovery mode
3. Go to Wipe --> Format Data --> Type yes and accept --> Reboot into recovery
5. Go to Wipe --> Advanced Wipe --> Select Cache --> Repair or Change File System --> Change File System --> EXT4 --> Swipe to Change
Hybrid Mode
You can have /cache and /ext4 on different filesystems, so follow previous instructions to put the partitions on your desired filesystem
Download EXT4 version - Vanilla
googledrive / mediafire
MD5: d3566ba4e209c9787475ba03c8de6a3c
SHA1: 658bae71db757c1508dd76e62a1baad42758b881
Download EROFS version - Vanilla
googledrive / mediafire
MD5: e4f61ade8c0c4673ccb1e695a85a644d
SHA1: 6f20c5f42b5061032c5429f71b9a9e3beb108e96
Download EXT4 version - GApps
googledrive / mediafire
MD5: e5d05a9a40db2c48b33708c7e92851df
SHA1: ae69120b7d25cf4cdb7b0889eacb9f4bfbf8769e
Download EROFS version - GApps
googledrive / mediafire
MD5: 5053f017308d9eaf2845089bbe51a06f
SHA1: a84cb0b0c37a7803f89170115ab4fc35c85c770e
Download latest TWRP
googledrive / mediafire
MD5: 5c4845b2f5378abba303688aca000c46
SHA1: a2d71742f2928817fc3426ecba843c50f3cc4291​
Android OS version: 13.0.0_r43
Build ID: TQ2A.230505.002
Security patch level: May 05 2023
Build author/Device Maintainer: Huexxx
Source code: CherishOS GitHub repos
Trees and Kernel: Huexxx GitHub repos
Status: Stable
SELinux Status: Enforcing
Release date: 2023-06-10
Buy me a Beer!​

Features / Changelog 2023-06-10
- Launcher3:
-- Changed to real modded CherishOS base
-- Switch from Google's Smartspace to Quickspace
-- Option to force monochrome non-themed icons
- ThemePicker:
-- Changed to moded ProtonPlus base
-- Allow color picker on vanilla versions too
- Removed keyguard Google's Smartspace
- Add Omnijaws Weather API
- Add Jelly browser on vanilla version
- Kernel:
-- Update kernelsu
Features / Changelog 2023-05-09
- Source updated
- Fixed Wallpaper & Style (basic colors)
Features / Changelog 2023-05-06
- kernel:
-- Switch to EROFS legacy version (less changes to base 4.4 kernel avoiding possible problems)
-- Switch to Simple Low Memory Killer
-- Add SchedTune and CpuSets Assist
-- Several EAS tweaks
-- Several sched/mm/cpufreq commits
- Source updated (upgraded to android 13.0.0_r43)
Features / Changelog 2023-04-27
- kernel:
-- Backported support for EROFS fs
-- Backported support for Cgroup v2 Freezer
-- Switched to 2SI (two stage init)
-- Added KernelSU support
- Source updated (upgraded to android 13.0.0_r41)
Features / Changelog 2023-03-26
- kernel:
-- Reverted some not wanted commits
-- Some logspam removed
-- Boot time has been reduced by 26 seconds
Features / Changelog 2023-03-09
- Source updates
- Encryption fixed!
Features / Changelog 2023-03-07
- Source updates
- Temporary removed forced encryption from device trees
Features / Changelog 2023-03-06
- Source updates
- ReAdded option to install custom themed icon packs for Launcher3
- Kernel: Added some commits regarding EAS and cpufreq
- Some adjusts in a try to make encryption work
- Sepolicy: Address some denials
Features / Changelog 2023-03-01
- Source updates (upgraded to android 13.0.0_r30)
- Removed the option to install additional themed icons from Launcher3 (I'll study to return it)
- Some kernel commits
- Some device tree commits
Features / Changelog 2023-01-28
- Source updates
Features / Changelog 2023-01-20
- Source updates
- Launcher3:
-- Bring back 'At a Glance'
-- Import widget overlap from Lawnchair
- Kernel updates
- Gapps slimming diet (many apps have been dropped)
- Some commits on qcom-caf display hal
Features / Changelog 2023-01-19
- Source updates
- Improved sepolicies
- Imported Launcher3 from EvoX:
-- Adapted to work with CherishOS
-- New app icon and modified name
-- Removed 'At a Glance' due to CherishOS sources
-- (I'll try to restore it)
Features / Changelog 2023-01-17
- Source updates
- Improved sepolicies
Features / Changelog 2023-01-10
- Sources updates
- Switch to OSS libnotifyhal (make proximity sensor work without binder, new lineageos approach)
- Drop vndk-ext packages
- Switch BTAudio to AIDL
- Switch to common fingerprint HIDL
- Config SQLite to operate in MEMORY mode
Features / Changelog 2022-12-28
- Sources updates
- Downgraded audio and listen blobs to older revision
- Downgraded display drivers to fix camera problems
- Drop Soundtrigger, Renderscript and qti perf stack
Features / Changelog 2022-12-01
- Source updates
- kernel:
-- Switch to LLVM tools for compiling
-- Xiaomi updates
-- Backport binder from 5.4-lts
-- Lots of commits/patches
- Updated audio, listen, thermal-engine, display and DRM blobs
- OpenGL ES driver updated to OpenGL ES 3.2 [email protected]
- Updated Display HAL to LA.UM.10.6.2.r1-01900-89xx.0
- Update GPS hal and blobs from LA.UM.9.6.3.r1-06200-89xx.0
- Fixed soundtrigger (Ok Google)
- Reenabled thermal-engine
- Many more...
Features / Changelog 2022-11-10
- Fixed Night Light
- Fixed LiveDisplay
Features / Changelog 2022-11-09
- Source updates
Features / Changelog 2022-11-08
- Source updates
-- Upgrade to release 14
-- November security patch
-- Readded FaceUnlock
Features / Changelog 2022-11-03
- SoftAP:
-- Add AP band preference
-- Add list to select Country Code spoof
-- Extend funcionality to QS button
- Added GrapheneOS Camera v56 from GrapheneOS repos
- On GApps version:
-- Replace Pixel Launcher with mod (allow more desktop grids)
-- Added GoogleCamera to MGC-8.4.300_Parrot043_V1.5
- Selinux Enforcing

reserved

OP Updated.

OP Updated-

OP Updated!

OP Updated!

Man I'm so glad someone hasn't given up on this phone. It's pretty awesome with how thin and lightweight is. I've got the Mix3 and it's a heavy brick. Thanks for keeping the Dev going. Definitely going to download and give it a shot.

OP Updated.

have this rom installed(latest), gps green light is always on. and it says that its being used by google play services.and it cant be disabled. or there is any option to disable it?
one more bug found:
when i'm trying make(not to attach existing one) and send photo in Telegram or WhatsApp - it hangs.

when i'm trying make(not to attach existing one) and send photo in Telegram or WhatsApp - it hangs.
Same result for me. Video clip is recording and available for editing (via long tap), but when trying to make photo - Telegram hangs just after the tap and the flash fires.

OP updated!

Huexxx said:
OP updated!
Click to expand...
Click to collapse
Hi, Google drive link for GAPPS image seems to be broken for me. Thanks for updates

Have you checked sha1 or md5 hashes?
Have you managed to download from mediafire?
Is the first complain in that way so maybe is an isolated problem...
If someone else reports the same I'll re-upload it.

Huexxx said:
Have you checked sha1 or md5 hashes?
Have you managed to download from mediafire?
Is the first complain in that way so maybe is an isolated problem...
If someone else reports the same I'll re-upload it.
Click to expand...
Click to collapse
I've downloaded and installed image from Mediafire - it's OK.
Link from Google Drive - it says error "File not found" - so I can't even check it.

Strange, I've just downloaded it from link without problems... maybe it was an isolated problem.

I faced a problem but solved it.
I had the official CherishOS (Android 11) for chiron installed with the latest official TWRP for chiron. When I installed the Nanhumly built TWRP it couldn't decrypt. So I went back to the official TWRP and flashed this CherishOS (Android 13) with NikGapps and Magisk. It installed and system booted up alright. When I went back to recovery, now the official TWRP couldn't decrypt. So I flased the Nanhumly build and it could decrypt now.
So I figured that the official one works up to Android 11 and the Nanhumly build is for 12 and above. I'm a n00b so this is a revelation for me. That's why I'm sharing the experience for fellow n00bs.
Great build Huexxx. It's running smoothly. I'll report back after few days of use.
Happy New Year! Cheers!

picchishaitan said:
I faced a problem but solved it.
I had the official CherishOS (Android 11) for chiron installed with the latest official TWRP for chiron. When I installed the Nanhumly built TWRP it couldn't decrypt. So I went back to the official TWRP and flashed this CherishOS (Android 13) with NikGapps and Magisk. It installed and system booted up alright. When I went back to recovery, now the official TWRP couldn't decrypt. So I flased the Nanhumly build and it could decrypt now.
So I figured that the official one works up to Android 11 and the Nanhumly build is for 12 and above. I'm a n00b so this is a revelation for me. That's why I'm sharing the experience for fellow n00bs.
Great build Huexxx. It's running smoothly. I'll report back after few days of use.
Happy New Year! Cheers!
Click to expand...
Click to collapse
Exactly, I recommend in my op to use nanhumly's build to use encryption (or not).

OP Updated!
NOTE: I haven't tested this build by myself, so make a backup prior to flash it.

Tried out 2023-01-10 (Vanilla)
That camera issue seems to be fixed.
For some reason the the CherishOS Launcher has been removed and replaced with a plain .launcher3 launcher. (No customizing settings available)
Does any one know where I can get an APK for the CherishOS Launcher? (Was available in 2022-12-01)
Edit: As an added benefit of the new launcher is that it is compatible with any Launcher that has Quickswitch support. So I was able to install the latest Lawnchair 12.1 dev and still have working gestures