[ROM][SNAPSHOT][7.1.2] AOSP Nougat for Xperia X Performance - Sony Xperia X Performance ROMs, Kernels, Recoverie

[ROM][SNAPSHOT][7.1.2] AOSP Nougat for Xperia X Performance - Sony Xperia X Performance ROMs, Kernels, Recoverie

{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
Requirements
Xperia X Performance : Meant for F8131, others to verify and would need changes
Bootloader : Unlocked bootloader to flash new bootimage
Stock version : Recent Nougat Stock release (39.2.A.0.xxx)
Downloads Links
AOSP 7.x Nougat (Unlocked Bootloader) :
Test : https://mega.nz/#F!D98GiJrA!trPA7QZGkLEju5Qv_cz-Og
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM64, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
MultiROM TWRP or Normal TWRP : https://forum.xda-developers.com/showpost.php?p=69036502&postcount=2
About AOSP : Repositories available on https://android.googlesource.com/
About GApps : Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
AOSP clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to lose data)
- Flash the AOSP ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
AOSP update / upgrade :
- (Information) Don't wipe anything unless you want to
- Flash the latest AOSP ROM zip from the Recovery
- (Optional) Flash the GApps if you want to, otherwise preserved.
- (Optional) Every additional zip you want to flash
- Reboot
About the builds
Development project : https://github.com/AdrianDC/aosp_development_sonyaosp
Device tree : https://github.com/AdrianDC/device-sony-dora/commits/master
Kernel sources : https://github.com/AdrianDC/kernel-sony-msm/commits/aosp/LA.UM.5.5.r1
Vendor blobs : http://developer.sonymobile.com/open-devices/list-of-devices-and-resources/
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
Q&A - FAQ
Q : Is root access included into AOSP ?
A : No but you can root with SuperSU.
Q : Is the ROM suited for daily usage ? With GApps too ?
A : Not yet, work in progress. OpenGApps recommended.
Q : I see errors during the installation, is it normal ?
A : If it is E:unknown command [log] , ignore it for now
Q : Where can I change the Quick Tiles and Status Bar ?
A : Long press the Settings icon in the notifications drawer.
> You will have access to the SystemUI Tuner from Marshmallow.
Q : The AOSP Keyboard does not support swipe gestures ?
A : UNTESTED YET: Unfortunately the sources for swipe gestures are not available
and Google still requires their prebuilt library to be there for AOSP Keyboard.
Download the following libjni_latinimegoogle.so API 23 from OpenGApps
and push it to /system/lib/libjni_latinimegoogle.so using root access,
or use my one-time install zips : https://mega.nz/#F!ThEAkCRa!byhSwuoTbf6lnC1JxgKrig.
AOSP available for Dora also thanks to :- The Android Open Source Project
- The Sony Open Devices Program
XDA:DevDB Information
AOSP Nougat 7.1.2, ROM for the Sony Xperia X Performance
Contributors
Adrian DC
Source Code: https://android.googlesource.com/
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Snapshot
Created 2017-01-29
Last Updated 2020-08-15

Reserved
FEATURES AND ISSUES
Official platform functionality list: http://developer.sonymobile.com/open-devices/current-platform-functionality/
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- WiFi : Ok
- Bluetooth : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok, only Ext4 support missing from AOSP
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Fingerprint sensor : Partially / broken
- AOSP sensors : Ok
- Touchscreen : Ok
- FM Radio : Broken
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Work in Progress
- Graphics : Ok, Work in Progress
- 3D Rendering : Ok, Work in Progress
- Clock : Ok
- Offline Charging : Broken, boots to Android
- USB OTG : Broken
- Encryption : Status unknown
- SEPolicies : Permissive
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds

Reserved
Recent branches commits
Devices + common projects: https://github.com/AdrianDC/aosp_development_sonyaosp/branches/all
Changes log (https://developer.sonymobile.com/open-devices/latest-updates)
09/06 : New release on Android 7.1.2_r17 sources (June CVE patches), new blobs (v05). Improved camera and stability / Fixed video recording
24/04 UNRELEASED : New release on Android 7.1.2_r2 sources (April CVE patches / Pixel), new blobs (v04). Camera minor hardware risk.
13/03 : New release on Android 7.1.1_r25 sources (March CVE patches / Pixel)
25/02 : Maintenance release with update device and kernel sources
15/02 : New release with updated blobs (AOSP_N_MR1_DEV_v03)
11/02 : New release on Android 7.1.1_r20 sources (February CVE patches / Pixel)
29/01 : Initial release for Dora, Android 7.1.1_r9
Original AOSP 7.1 sources with following relevant additions
Build: Backup tool full support (GApps)
Build: Minor improvements for development purposes
Core: Disabled flash_recovery service from AOSP
Music: Minor fix to permissions
Toybox: Support for init_sony boot selection
Current local manifest
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://android.googlesource.com/platform/manifest -->
<manifest>
<!-- See https://github.com/AdrianDC/aosp_development_sonyaosp -->
</manifest>

Hi @Adrian DC, should this be flashed from nougat only?
I flashed from M (.297) last night and roughly five minutes after the amazingly fast boot up, I had a system freeze, had to do power/volume combo to restart. Also had an issue with twrp not responding to touch at all. Im now back on N (.386) and wondering if I should flash from here. Thanks.

Yeaa! Finally some progress on roms for my x performance! Was looking for a ss or htc already

Yes! nice one. will be checking this out!

Great!!! Just wanna know hows the camera quality, and is it stable to use as daily driver?

Is support for dual sim(f8132)?

I want to install this as my primary rom but it is always asking me for a password after the installation. I have performed a clean install and I also wiped the dalvik/cache but nothing.
Is there a way to bypass this?

13lizzard said:
I want to install this as my primary rom but it is always asking me for a password after the installation. I have performed a clean install and I also wiped the dalvik/cache but nothing.
Is there a way to bypass this?
Click to expand...
Click to collapse
Enter recovery and wipe data, dalvik cache and cache at least 3 times. Then reboot.

There's no 3 times cache wiping or such way to fix it.
You have to do a factory reset to have the data partition formatted instead of 'wiped',
that way the encryption sector is properly erased.

Post screenshots

Why 7.1.2 is not out yet?

patrick4a17 said:
Why 7.1.2 is not out yet?
Click to expand...
Click to collapse
Because we're waiting for a new set of vendor blobs.
The current ones do work, but the camera actuator makes a small noise, so not taking any risk with a public build.

When are you going to update? Expect beta or stable version

hellyjia said:
When are you going to update? Expect beta or stable version
Click to expand...
Click to collapse
You have my answer in the previous post .

Consult, F8131 can brush F8331 Rom? Both hardware seems to be the same

Will there be a recent update?

The fingerprint sensor is broken? Can it be used for screen unlock??

ANT+ works?

Related

[ROM][FINAL] Resurrection Remix v6.2.0 [8.1.0_r46][athene]

[size=+2]Resurrection Remix Oreo for the Moto G4/G4 Plus[/size]
{
"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"
}
Code:
#include <std.disclaimer>
/*
* 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... a lot.
*/
[size=+2]About Resurrection Remix[/size]
Resurrection Remix ROM is the ultimate full featured, stable ROM combined with the best features of open source ROM's. We
are also providing lot of awesome original Resurrection Remix ROM features in the builds. It includes the best of performance,
customization, power and the newest features on your device! So please, enjoy!
[size=+1]INSTALLATION INSTRUCTIONS[/size]
-- Coming from Stock or another Custom ROM --
** xt164x users must be on latest modem/baseband version or you will have issues registering fingerprints. **
- Download the latest build
- Download GApps (OpenGapps Nano recommended)
- Optional: Download Magisk
- Make a backup in TWRP Recovery
- Full wipe (system, data, cache, dalvik/art cache)
- Flash ROM
- Flash GApps
- Optional: Flash Magisk
- Reboot && Profit
[size=+1]UPDATE INSTRUCTIONS[/size]
-- Upgrading from previous build (dirty flashing) --
- Download the latest build
- Make a backup in TWRP Recovery
- Flash ROM
- Flash GApps (may not be needed)
- Optional: Flash Magisk
- Wipe cache & dalvik/art cache
- Reboot && Profit
[size=+1]INSTALLATION FILES[/size]
- Official: https://downloads.resurrectionremix.com/athene
NOTE: Please don't pay attention to the 'Download Latest Version' button at the top.
You only have to look at the contents of the folder!
- GApps: https://opengapps.org (Nano version recommended)
- TWRP Recovery: TWRP 3.2.1 64-bit Recovery (NOTE: Can use this with ALL ROM's, 32+64bit)
- Changelog: Latest changes
[size=+1]SOURCES[/size]
- Resurrection Remix: https://github.com/ResurrectionRemix
- Device Tree: device_motorola_athene
- Kernel Source: kernel_motorola_msm8952
[size=+1]Reporting Issues[/size]
- If you have used any additional mods, please make sure it's unrelated and mention it
- Make sure the issue hasn't already been mentioned (use search function)
- Mention the steps to reproduce and take logs
- A logcat after a reboot is useless (unless you can get it just before the reboot happens), otherwise after the reboot has finished,
- provide the files located at /sys/fs/pstore/
[size=+1]Social Link[/size]
- Official Telegram Chat: https://t.me/resurrectionremixchat
- Official Telegram Channel: https://t.me/ResurrectionRemixChannel
[size=+1]Special Thanks[/size]
- XDA-Developers
- The LIneageOS Team
- Dirty Unicorns
- OmniROM
- The Slim Team
- And everyone else involved
XDA:DevDB Information
Resurrection Remix v6.2.0, ROM for the Moto G4 Plus
Contributors
Jleeblanch, Nikit, The Resurrection Remix Team: akhilnarang, mracar, varund7726, westcrip
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS, AOSP
Version Information
Status: Stable
Current Stable Version: v6.2.0
Stable Release Date: 2018-09-15
Created 2018-02-11
Last Updated 2018-09-16

Changes, Updates, etc...
[size=+1]+++ Release - RR-O-v6.1.0-20180613-athene-ARM-Official.zip +++[/size]
+ md5sum - 101ca8a321a815e287d928d22dcc4249
+ Changelog - 32-bit
[size=+1]+++ Release - RR-O-v6.1.0-20180612-athene-ARM64-Official.zip +++[/size]
+ md5sum - 7985b5c31674d3f8f34cde695bdac63c
+ Changelog - 64-bit
++ RR Changelog for v6.1.0 ++
-> RR v6.1.0 release
-> June Security Patch (android-8.1.0_r30)
-> Fixed WiFi MAC address (now retains stock wifi mac address)
-> Reduced amount of lower CPU frequencies
-> And many other fixes and some new features!
===================================
===================================
[size=+1]+++ Release - RR-O-v6.0.0-20180520-athene-ARM-Official.zip +++[/size]
+ md5sum - 4ba284524ad89819222d1f98c8b9f4d9
+ Changelog - 32-bit
[size=+1]+++ Release - RR-O-v6.0.0-20180521-athene-ARM64-Official.zip +++[/size]
+ md5sum - 1be491f5736a0a734e2624c918f1b91d
+ Changelog - 64-bit
Both 32bit and 64bit builds are now available!
There will not be an OTA for these releases. I'm working on a way to ensure that users on the 32bit version don't get an OTA notification for the 64 bit version, and users on the 64bit version don't get an OTA notification for the 32bit version. So be patient, I will figure out a way soon!
The changelogs will be close to the same regarding RR's source, the main differences are in my sources for athene (but also similar in some ways too).
-> Live Display is working on both versions of the ROM, so you're welcome for that
-> SafetyNet passes on both versions
-> Kernel features are the same between both versions (RK arm + RK arm64) Use your favorite kernel manager to checkout and tweak to your liking
-> RR source is the same between both versions and both have the May 5th Security Patch (android-8.1.0_r26)
-> Flashlight tile is still non-functional
-> Chop Chop works on both versions
-> Moto Actions is the same on both versions
-> The kernel now properly uses the lower frequencies (battery life improvement?)
-> Camera is still what it is. Results may vary between the two versions of the ROM
I hope you enjoy!

FAQ, reporting bugs, etc...
[size=+2]READ THIS POST BEFORE POSTING IN THIS THREAD[/size]
Resurrection Remix || Google Plus Community
>> RR 'Oreo' FAQ || https://plus.google.com/+MattThomas83/posts/Zz6UEBdetKN
>> Info on Bug Reporting || https://plus.google.com/+MattThomas83/posts/RAuHneppoKa
>> RR Posting Rules (G+) || https://plus.google.com/+MattThomas83/posts/DvbzAgp2549
[size=+1]** Reporting issues in this thread - PLEASE READ! **[/size]
If you want to report an issue or bug and don't want me to ignore your post, then you need to include the following information in your posts.
Your device variant (E.g. "XT162x" or" XT164x")
ROM version and DATE of build (E.g. "RR 32bit" or "RR 64bit" + "date of build")
Your install process (E.g. "Clean flash" or "Dirty flash")
A DETAILED description of the issue/bug.
Whether you're using any mods, custom kernels, or themes.
And, if necessary:
A logcat of the issue. Use MatLog if taking logs on your device. Otherwise READ THIS.
Any screenshots or videos that clearly show the issue.
Which GApps you used (E.g. "opengapps, nano, mini, stock, aroma, etc...")
If your post does not contain at LEAST the first 1-5 things stated above, than your post may be ignored. It's as simple as that!
If you're experiencing a random reboot, a logcat is useless unless you get it just before the reboot happens.
After the reboot occurs, use a root explorer and go to /sys/fs/pstore and copy the files located there to your internal storage or sdcard. There will be 2 to 3 files there, grab them all and zip them up and post a link so that I can download and review them.

One more, just in case

Amazing!!

FYI, currently ROM has the same few issues as most every other Oreo based ROM for athene has. As stated in the nougat thread, currently only 64-bit version for now.
Recommended TWRP, GApps, etc are all linked in the OP. The ROM has a lot of cool features for an initial release, so enjoy

Loved the new bootanimation....clean room...good battery life..... Common camera and flashlight issue
[Request]
Remove device is he capable
Add pixel 2 launcher

Thx I'll take this ツ

Is the GPS working?

Yes it is working
Volte is working
Rom is ultra smooth only contains athene oreo specific bugs thnx alot dev for the rom?

What is the bugs?

al3al3al3jandr0 said:
What is the bugs?
Click to expand...
Click to collapse
Flash light not natively Working and a few minor ones. Nothing huge or anything. I'm going to flash this today

Thank
Ayan Uchiha Choudhury said:
Flash light not natively Working and a few minor ones. Nothing huge or anything. I'm going to flash this today
Click to expand...
Click to collapse
Thank you I'll try it anyway :good:

My phone is not charging even by percent...I it room but?
Edit - working after some restarts.

Super smooth...stable....love it....

Wait was worth it.i will flash this asap
keep rocking you guys

Can anyone confirm that Safetynet is not broken in this ROM

:good:

avsgod21 said:
[Request]
Remove device is he capable
Click to expand...
Click to collapse
Use the Notification Off app from playstore, grant root access to the app, find org.codeaurora.ims and uncheck the package. You're all set. The icon will be removed immediately. Use the following link:
https://play.google.com/store/apps/details?id=com.aboutmycode.NotificationsOff

Is magisk included in the zip file just like nougat roms? Or we need to flash manually.?

[8.1][UNOFFICIAL]LineageOS-15.1[Z00L/Z00T]

{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo) which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS GitHub repo and if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website
Official LineageOS changelogs
About the LineageOS 15.1 features
Downloads Links
GDrive
Google Applications (optional) :
OpenGapps (Use packages for ARM64, Android 8.1.x, Micro)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Audio Workaround for ZE601KL (Not Officially Supported) Users by Superbezo: Mega | AFH
Flashing and updating
LineageOS clean install :
- Flash the LineageOS ROM zip from recovery
- (Optional) Flash a GApps package to have the Google Applications
- (Optional) Every additional zip you want to flash
- Wipe the dalvik & cache
- Reboot
LineageOS addonsu for root access :
- (Download) Download the addonsu for arm64
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot
About the builds
- Device Side Sources are here.
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error
LineageOS available for Z00L/T also thanks to :
- LuK1337
- Google AOSP
- The LineageOS Team
- CodeAurora Forums
- The CyanogenMod Team
XDA:DevDB Information
LineageOS-15.1, ROM for the Zenfone 2 Laser
Contributors
TheImpulson
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 15.1
Stable Release Date: 2018-03-31
Created 2018-03-31
Last Updated 2019-01-09

FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- LED Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- Touchscreen : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- DRM : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok
- SEPolicies : Enforcing

Changelogs:
Code:
[B]20180625[/B]
[B]Device Changes:[/B]
- Shorten wait time to optimize shutdown time
- Shorten wait time for services exit to optimize shutdown time
- Disable SystemUI anti-falsing on the lock screen
- Build text classifier's smart selection
- Use sched_fifo for render thread and activity manager
- Inform Trust about legacy encryption support
- Disable QS panel transparency
- Switch to unified fstab
- Use sdfat instead of vfat
- Use sdfat for exfat (Asus used to ship native exfat module with stock)
- Move device dependent modules to /vendor
[B]Kernel Changes:[/B]
- Import sdfat & port to 3.10
- Regenerate defconfigs
- Fix "hide su" patch for 3.10
[B]Vendor Changes:[/B]
- Hexedit GPS blobs to load config files from the vendor
Other Lineage OS-15.1 specific changes up to 25/06/2018
[B]20180615[/B]
- Disabled display transformation support to fix lags during live display.
- Replaced current GPS configs with stock configs to fix location issues.
- Implemented a dummy qti-telephony-service to enable SIM card to enable/disable options (Might be buggy).
- Implemented ZenfoneDoze (Might consume more battery if enabled).
- Added vendor security patch level for Trust
- Updated bspcapability string and added permissions to fix Pixel master camera support.
[B]20180606[/B]
- Removed HWC2 Support & binderized Live display
- Imported GPS configs from klte-common
- Enabled Internal Storage view by default in File Manager
[B]20180531[/B]
- Removed Shutdown timeout to fix buggy reboot options
- Binderized Live display and added overlay for HWC
- Updated extract and makefile scripts
- Enabled Automatic brightness and disabled Bluetooth on first boot.
- Added location overlay
- Removed deprecated Snap camera overlay
- Other Lineage OS related changes
[B]20180526/27[/B]
- Added back btnvtool to fix Bluetooth MAC address. Thanks to @AmolAmrit
- Reverted back to OSS liblight to fix notification LED
- Removed ZuK Doze for now
- Fix a bunch of SELinux denials
- Other Lineage OS specific changes [URL="https://lineageos.org/Changelog-18/"]here[/URL]
[B]20180520[/B]
- Fixed more audio related SELinux Denials
- Added Advance Doze options ported from ZuK Devices
- Updated F2FS

Another Reserve

cant wait releases for z00t, many thanks devs !!!

Is the ROM smooth and reliable
Is there any issues that are very complex and deal breakers

No words can express how much I'm thankful for continuous work with this device! I will try and flash this soon.

Nova Sangeeth said:
Is there any issues that are very complex and deal breakers
Click to expand...
Click to collapse
Check 2nd post

Owh god you are awesome man..... I am very much happy now

This phone is not complete with out this rom. Thank you dev.

Pushed Z00T build.

TheImpulson said:
Pushed Z00T build.
Click to expand...
Click to collapse
will try soon thank you:good:

Hello and thank you for your work. Can you please tell, will you become Z00T maintainer for Lineage OS, or are these builds completely unofficial (I mean without further possibility to go official 15.1 build) and we better stick to AEX 5.X?
Also can you tell, are there any differences between your build and Luke's last one, apart from Fire Kernel?

casper_wh said:
Hello and thank you for your work. Can you please tell, will you become Z00T maintainer for Lineage OS, or are these builds completely unofficial (I mean without further possibility to go official 15.1 build) and we better stick to AEX 5.X?
Also can you tell, are there any differences between your build and Luke's last one, apart from Fire Kernel?
Click to expand...
Click to collapse
I doubt it will become official ever first of all. All HAL1 devices are not yet official due to camera issues and will probably won't. Apart from FireKernel difference is that I compiled it using SDCLANG, did some updates for GPS, and other files, Disabled transparent QS and fixed video recording partially by importing commits from xperia devices. Nothing more.

TheImpulson said:
I doubt it will become official ever first of all. All HAL1 devices are not yet official due to camera issues and will probably won't. Apart from FireKernel difference is that I compiled it using SDCLANG, did some updates for GPS, and other files, Disabled transparent QS and fixed video recording partially by importing commits from xperia devices. Nothing more.
Click to expand...
Click to collapse
Ok, thank you for your answer. Do I understand correctly that all the LOS 15.1 changes for the past month also included, I mean, is it based on the last builds, right?

casper_wh said:
Ok, thank you for your answer. Do I understand correctly that all the LOS 15.1 changes for the past month also included, I mean, is it based on the last builds, right?
Click to expand...
Click to collapse
I synced yesterday and compiled. So, yes all changes by lineageOS till yesterday are there.

TheImpulson said:
I synced yesterday and compiled. So, yes all changes by lineageOS till yesterday are there.
Click to expand...
Click to collapse
Great to hear that, downloading the ROM

TheImpulson said:
I doubt it will become official ever first of all. All HAL1 devices are not yet official due to camera issues and will probably won't. Apart from FireKernel difference is that I compiled it using SDCLANG, did some updates for GPS, and other files, Disabled transparent QS and fixed video recording partially by importing commits from xperia devices. Nothing more.
Click to expand...
Click to collapse
So kind of you , I will wait for official one

TheImpulson said:
I doubt it will become official ever first of all. All HAL1 devices are not yet official due to camera issues and will probably won't. Apart from FireKernel difference is that I compiled it using SDCLANG, did some updates for GPS, and other files, Disabled transparent QS and fixed video recording partially by importing commits from xperia devices. Nothing more.
Click to expand...
Click to collapse
Hi @TheImpulson I read on one of the other threads that the video recording bug was completely fixed. AEX if I'm not wrong. I hope I'm not mistaken. If it is fixed, is there a chance of it becoming official?

Whiskeym said:
Hi @TheImpulson I read on one of the other threads that the video recording bug was completely fixed. AEX if I'm not wrong. I hope I'm not mistaken. If it is fixed, is there a chance of it becoming official?
Click to expand...
Click to collapse
Let's see. All there left is a green line to be fixed and if it does, I will apply for official tag.

[ROM][10.0][User build][Signed] Lineage-17.1-X00TD-Asus Zenfone Max Pro M1

{
"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"
}
About LineageOS
Lineage-17.1-X00TD-Asus Zenfone Max Pro M1
Build type : UNOFFICIAL
Build and signed by @[email protected] | Rajesh R
Disclaimer : ROMs are built for development purpose only. Use at your own risk.
This ROM completely compiled on lineage source code and with minimum workarounds for a successful build. Builds are signed with release-keys.Before installing, refer instructions and changelog for each builds.
About build variants
ROM-Signed release key-user build
My Projects
lineage-17.1-20210606-X00TD-user-signed.zip
fastboot-lineage-17.1-20210606-X00TD-user-signed-images.zip
lineage-17.1-20210606-recovery-X00TD.img
Features
*Gesture navigation android 10.
*Enforcing selinux and user build properties
* Certified device status under google play
* SafetyNet Test is passed
* Smooth ROM experience
Instructions
Backup procedure and precaution information
Must read before unlocking bootloader and flashing custom ROM
Some explanation regarding the whole widewine L1-L3-Qbeta etc ( Info @ https://t.me/ASUSX00TD from a member )
Starting from Q builds Asus has begun wiping DRM keys if bootloader is unlocked on that build, which is actually default behavior among most other OEMs like pixels, oneplus. Flashing Q builds (Stock beta 1 or latest) or custom ROM on unlocked bootloader through TWRP will permanently loose their L1 certification. widewine keys will be wiped by firmware itself as it detects unlocked bootloader. This also explains why some people, who flashed previous stock Q beta before on locked bootloader, even though first stock Q beta had L3 which means they hadn't fixed L1 on that beta that time , retained their L1/DRM keys on reverting to pie via downgrade zip provided by asus. So in conclusion Asus Q builds/custom ROM will wipe your DRM keys if flashed on Unlocked bootloader. Flashing on locked bootloader shouldn't be any problem!
Also those who have their persist partition backed up in pie should have no problem restoring their DRM keys in case thet got wiped by Q firmware/builds
How to Backup Persist ?
Dump all partitions and make complete backup | Partition layout and structure
Recovery method
use recoveries which support persist partition backup (eg. Orangefox)
Go to recovery > Backup > tick persist > backup > store it safe somewhere with multiple copies.
How to Restore Persist ?
Go to recovery > Restore menu > select backup > tick persist partition > Restore (process similar/different for different recoveries)
Upgrading to LineageOS 17.1
1. Make a backup of your important data
2. Download the build and also Gapps.
3. Download proper addons packages GApps for Android 10/Lineage OS 17.1
4. Make sure your recovery and firmware are up to date
5. For clean flash, Format your system,vendor,data and cache partition partition to install ROM and Gapps.
6. For installing updates format system,vendor and cache partition. keep data partition intact to flash ROM and Gapps.
Secure ROM experience
Avoid permissive selinux and rooting methods for secure ROM experience.
Refer
1. Root & SELinux Risks
2. TWRP password protection
3. TWRP encryption
Screenshots
Upcoming builds ( Only for volunteer testers )
lineage-17.1-20210512-X00TD-user-signed
* Check if audio distortion present at peak volume.
* Based on new device trees and kernel.
* Only clean flash recommended.
To test any ROM
Requirements:
Windows/linux Pc
adb drivers
Usb cable.
Steps to take log:
1. Install adb drivers in pc and enable usb debugging mode in phone. Also enable root debugging if needed.
2. Connect phone through usb and type the command "adb logcat -d>logcat.txt" in adb command window.You can choose any name you want for txt file. If needed give admin privilege for adb command window.
3. This procedure can also be used to watch occurance of bugs at realtime by connecting phone at adb mode to pc.
Steps to take boot log:
1. Make sure adb is enabled in phone. Connect the phone in usb mode to pc and open adb command window.
2. Switch off the phone and type "adb logcat -d>bootlog.txt".
3. Initially "waiting for the device" message is noticed on adb command window and switch on the phone now. once the device powers on, boot log is recorded.
log text files are stored in location where adb drivers are installed.
Note : Test builds are released here and intended to test upcoming fixes and features.
Source Code
Kernel source code : https://github.com/SagarMakhar/android_kernel_asus_sdm660
Kernel developer credits : @SagarMakhar
Credits
Google's AOSP Project.
Lineage OS for the source code and The Open GApps Project.
Contribute to Lineage OS at https://paypal.me/LineageOS
Contribute to Gapps at https://www.paypal.com/donate/?toke...EScTbkNmciIDl9n5LyDW&country.x=US&locale.x=US
Thanks to developers and their contribution on custom ROM development for Asus zenfone max pro M1. Thanks @Patching.Unconditionally, @patkk for testing builds.
Special thanks for the build server admin and @abhishekt295 , TheButti for upload server.
It's all free, but donations are welcome
Donations will be contributed to server maintenance
Support developers on their respective threads.
Feedback and bug reports are welcome.
Kindly use english language on comment section

Changelog
24. OTA : lineage-17.1-20210606-X00TD-user-signed.zip
* Synced with source updates and fixes.
23. OTA : lineage-17.1-20210603-X00TD-user-signed.zip
* OTA support to lineage-17.1-20210531-X00TD-user-signed.zip
* Sound output Fixes
22. Build : lineage-17.1-20210531-X00TD-user-signed.zip
* FBE-File-Based Encryption implementation. Only clean flash recommended. It is not OTA release
* Updated media configs from stock.
* Update fingerprint to UL-ASUS_X01BD-WW-17.2018.2012.438-user
* Upgradable to build lineage-18.1-20210525-X00TD-user-signed.zip through dirty flash.
21. Build : lineage-17.1-20210526-X00TD-user-signed.zip
* AVB disabled and Verity Enabled.
* Locking bootloader supported. Works only with lineage recovery.
Note : Lock only if lineage recovery is flashed. If bootloader locked with twrp. Device fails to boot and only fastboot mode helps to solve the issue to unlock bootloader again.
* Dirty flash on previous lineage-17.1 builds wont work. It is not OTA release. Only clean flash recommended.
* Sound control features added.
* Adaptive sleep features.
* Upgradable to build lineage-18.1-20210525-X00TD-user-signed.zip through dirty flash.
20. OTA update : lineage-17.1-20210518-X00TD-user-signed
* Device tree updates.
* Synced with lineage source updates.
* Update to lineage-18.1 through OTA is supported.
19. OTA update : lineage-17.1-20210404-X00TD-user-signed
* KSM tunning
* Removal of SoterService
18. OTA update : lineage-17.1-20210327-X00TD-user-signed
* VoLTE icon support on status bar.
* Updated audio drivers.
* KSM tunning.
17. OTA update : lineage-17.1-20210306-X00TD-user-signed
* CAF audio.
* Updated audio configs from stock 10 release.
16. OTA update : lineage-17.1-20210204-X00TD-user-signed
* Kernel updates
* Sepolicy updates on enforcing selinux.
* Fingerprint biometrics fixes.
* Safetynet fixes.
15. OTA update : lineage-17.1-20210103-X00TD-user-signed
* Sepolicy updates on enforcing selinux.
* Fingerprint biometrics fixes
* MusicFX Equalizer (Download optional add-on )
14. OTA update : lineage-17.1-20210101-X00TD-user-signed (Optional download)
*Permissive selinux .
13. Build name :lineage-17.1-20201229-X00TD-user-signed
* OTA support through lineage updater.
* Sepolicy cleanup
* MusicFX Equalizer (Download optional add-on )
12. Build name :lineage-17.1-20201215-X00TD-user-signed
* Security patch update
* Updated Fingerprint driver from asus android 10 beta.
11. Build name :lineage-17.1-20201112-X00TD-user-signed
* Security patch update
*Added Fingerprint driver
10. Build name : lineage-17.1-20201101-user-signed
* Safetynet fixes and sepolicy updates.
9. Build name : lineage-17.1-20201017-user-signed
Status : Working fine
Bugs: Fingerprint missing
8. Build name : lineage-17.1-20201015-user-signed
*Charging current restored to Stock values.
* Improvements in battery backup.
* Camera2api support for snap camera.
* Ambient display
* Scoped storage related fixes.
* Dirty flash Supported over lineage-17.1-20201005-X00TD-user-signed build
Status : Working fine
7. Build name : lineage-17.1-20201005-user-signed
* Enforcing selinux and user build properties
* Certified device status under google play
* SafetyNet Test is passed
* Dirty flash supported over lineage-17.1-20201003/20200927-userdebug-signed builds
Status : Working fine
6 .Build name : lineage-17.1-20201003-userdebug-signed
* Enforcing selinux
* Certified device status under google play
* SafetyNet Test is passed
* Dirty flash supported over lineage-17.1-20200927-userdebug-signed
Status : Working fine
5 .Build name : lineage-17.1-20200927-userdebug-signed
* Permissive boot
Status : Working fine
4. Build name : lineage-17.1-20200926-userdebug-signed
* Permissive boot
Status : booted but no display
3. Build name : lineage-17.1-20200925-user/userdebug-signed
Status : bootloop
2. Build name : lineage-17.1-20200924-user/userdebug-signed
Status : bootloop
1. Build name : lineage-17.1-20200923-X00TD-user-signed
* Lineage-17.1-20200923 | Android10_r41
* release key user build
* Status : Experimental release-not booting

Rom doesnt boot
I installed everything and the rom reboots to LOS Recovery

Andys4c said:
I installed everything and the rom reboots to LOS Recovery
Click to expand...
Click to collapse
Did you clean flash.? Facing bootloop.? Or not even booting rom.?
This rom uses stable trees from corvus ROM. I will checkout issues. Meanwhile try out userdebug rom by changing kernel or permissive boot.:good:
This build project aims to replicate stock ROM properties and has its first experimental build. Wait for the stable build.:good:

[email protected] said:
Did you clean flash.? Facing bootloop.? Or not even booting rom.?
This rom uses stable trees from corvus ROM. I will checkout issues. Meanwhile try out userdebug rom by changing kernel or permissive boot.:good:
This build project aims to replicate stock ROM properties and has its first experimental build. Wait for the stable build.:good:
Click to expand...
Click to collapse
i always cleanflash. The rom hang on lineage Logo and then rebooted to lineage Recovery

Andys4c said:
i always cleanflash. The rom hang on lineage Logo and then rebooted to lineage Recovery
Click to expand...
Click to collapse
If you see lineage boot animation (logo) it is bootloop. Changing kernel or permissive boot may help. To fix ROM, I am building new userdebug enforcing build. Kindly wait.:fingers-crossed: Once we succeed userdebug build then its is worth trying user build with signed release keys:good:
Advantage of release key builds : Building an Android OS image using make will sign all .apk files using the test-keys. Since the test-keys are publicly known, anybody can sign their own .apk files with the same keys, which may allow them to replace or hijack system apps built into your OS image. For this reason it is critical to sign any publicly released or deployed Android OS image with a special set of release-keys that only you have access to.
Build Variants :
eng - Engineering build comes with default root access.
user-debug - User debug build does not come with default root access but can be rooted. It also contains extra logging.
user - User build is the one flashed on production phones. Has no root access.
Source : https://stackoverflow.com/questions/13950589/difference-between-eng-and-user-debug-build-in-android
Most of the custom ROMs are userdebug and stock ROMs are user builds.

i seen that you uploaded new buld. Does it boot?

still doesnt boot
I tried every build, changing kernel etc... but i give up.This is the poorest buildbotting i ever seen

Andys4c said:
I tried every build, changing kernel etc... but i give up.This is the poorest buildbotting i ever seen
Click to expand...
Click to collapse
Did you try permissive boot.? I used device source code from previous successful builds. I came to know asus ROM development is not user friendly and also not intended to perfection. Not a healthy coordination across developers. All development stops at engineering builds because of its complexity involved.
The truth is even stock ROM lack some features . It's the best secure build to be trusted with android secure properties.:good:

how to make rom permissive? by creating permissive kernel?
??

Bro check before uploading if it boots or not coz..many of us don't have pc ? after that we can test n tell bugs thankyou

Andys4c said:
??
Click to expand...
Click to collapse
All userdebug enforcing ROM support permissive boot by including the line "androidboot.selinux=permissive" on the kernel command line. Kernel command line is found on boot.img. You can reverse engineer boot.img by using this tool https://github.com/xiaolu/mkbootimg_tools. Test this only on userdebug builds.
For easy , I will upload permissive boot ROM:good:

lineage-17.1-20200927-X00TD-userdebug-signed.zip
* Release key signed build.
* Updated with latest source based on lineage-17.1
* Permissive boot.

[email protected] said:
lineage-17.1-20200927-X00TD-userdebug-signed.zip
* Release key signed build.
* Updated with latest source based on lineage-17.1
* Permissive boot.
Click to expand...
Click to collapse
finally!! Btw, do you have the device or buildbotting blindly?

Andys4c said:
finally!! Btw, do you have the device or buildbotting blindly?
Click to expand...
Click to collapse
Didnt give up till it boots.My builds are built using server and volunteerly tested. As mentioned before blindly taking source from successful xda ROM threads are not working. They needed some fixes. Next thing is to push this builds to enforcing boot. Hereafter, only successful builds will be updated.:good:

New update
Build name : lineage-17.1-20201003-userdebug-signed
* Enforcing selinux
* Certified device status under google play
* SafetyNet Test is passed
Status : Working fine

wow, Amazing. Does F2FS partition support?

a_fahruddin said:
wow, Amazing. Does F2FS partition support?
Click to expand...
Click to collapse
Not sure..check source code ..if not i will add support in upcoming builds..Next thing is to push the build project to user build properties like stock ROM.:good:

thanks sir

i hope in the next update sound is more louder.

[ROM][AOSP][EAS][13.0][UNOFFICIAL][chiron] StagOS 13.0

Features / Changelog 2022-12-08
- Sources updated
- kernel:
-- Switch to LLVM tools for compiling
-- Xiaomi updates
-- Backport binder from 5.4-lts
-- Lots of commits/patches
- Blobs and HALs updated:
-- GPS from LA.UM.9.6.3.r1-06200-89xx.0
-- Graphics from LA.UM.10.6.2.r1-01900-89xx.0 (OpenGL ES 3.2 [email protected])
-- DRM from LA.UM.9.6.2.r1-04200-89xx.0 and Coral Tiramisu/TPP1.220114.016/8158200
- Reenabled thermal-engine
- Dropped soundtrigger (is not working good)
- Dropped GCam and GrapheneCam (install the one you want)
Features / Changelog 2022-11-10
- Fixed NFC
- Fixed Night Light
Features / Changelog 2022-11-09
- Vendor tree updates
-- Blob cleanup
-- Update ANT+, Bluetooth and PowerOffAlarm blobs
- Replace Pixel Launcher with mod (allow more desktop grids)
- Replace GrapheneOS Camera with latest one from GrapheneOS repos
- Source updates
-- Upgrade to release 13
-- November security patch
-- Readded FaceUnlock
Features / Changelog 2022-10-25
- Fixed SoftAP settings
Features / Changelog 2022-10-24
- SoftAP:
-- Add AP band preference
-- Add list to select Country Code spoof
- Added Graphene Camera v16
- Added GoogleCamera to MGC-8.4.300_Parrot043_V1.5 (on GApps version)
- Selinux Enforcing

Reserved

Flashed this yesterday. So far so good, some animation/transition stutterings once a while, but I think it's because the hardware can't keep up with. Thank you for this great build. This is a perfect fit for me, minimum and without GAPPS.

OP updated!

Update flashed, so far so good. Thank you for this great rom

OP updated!

Is this ROM gonna get update like the others?

Give me 5 minutes...

OP updated!

Wow, that was quick! Thank you so much!

Open Camera has problem saving picture, but video shooting works. Switching to Camera 2 API result in a message saying "Serious Camera Problem" after taking picture. The built-in AOSP camera works without problem. It's dirty flash on previous version of Stag

scubajeff said:
Open Camera has problem saving picture, but video shooting works. Switching to Camera 2 API result in a message saying "Serious Camera Problem" after taking picture. The built-in AOSP camera works without problem. It's dirty flash on previous version of Stag
Click to expand...
Click to collapse
I have the same problem with Evolution-X rom , Open Camera has problem saving picture but video shooting works

Camera problems are solved on new versions... but on last attempts StagOS didn't boot... it stays at MI logo and nowadays IDK why. I cannot debug it becuase I can't get logs...
I'll try to bring it back to life... but if it keeps failing to boot I'll drop this ROM, sorry.

[ROM][AOSP][EAS][13.0][UNOFFICIAL][chiron] CherishOS v4.8 [10/06/2023]

{
"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 workInstallation
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

Develop Bugs

welcome