Develop Bugs

phhusson Android P 9.0 Treble GSI (WiFI Working)

Decided to create a new thread on the SE forums since we now have our own forum.
So phhusson made a treble GSI for Android P and I got further with it than with any of the other GSIs.
WIFI and BLUETOOTH both work with this GSI.
Here's what I did to get it working (your mileage may vary and I am not responsible for any broken/ bricked devices as a result of these instructions, ALWAYS MAKE SURE YOU TAKE A FULL TWRP BACKUP OF YOUR DEVICE BEFORE ATTEMPTING THIS):
Unlock bootloader.
Download the latest TWRP from here and flash it. Make sure you're running at least version 3.2.3.
Boot into TWRP, tap on Wipe and then tap on "Format Data" and enter yes. Once it's done, reboot into recovery.
Next flash the latest Xiaomi.EU MiUI 10 Beta rom from here. Download it, transfer it to your phone's storage and then use TWRP to install the zip.
After it has installed, tap on Wipe on the TWRP main menu and swipe to factory reset.
Next flash the treble GSI for Lineage 15.1 from here. Download it, transfer to your phone's storage and then use TWRP to install the image file by tapping on Install, then "Install Image" on the bottom right and then select the Lineage image you transferred earlier. Select the "system" partition on the next screen and install.
Now reboot your phone and wait for Lineage to boot up. Once it has booted successfully, reboot into recovery. Use TWRP to factory reset your device again.
Now follow the steps for an A-Only device on this article
*BUT BEFORE YOU REBOOT, GO INTO THE ADVANCED MENU ON TWRP AND TAP ON "INSTALL ROOT"*. Once Magisk has been installed, reboot into system and hopefully you should boot. If not, try rebooting again and it should work.
Bugs (that I know of):
Audio is really broken and sounds horrible even with headphones plugged in.
You can fix media audio only by flashing the ViPER4Android module through Magisk Manager.
This doesn't fix it for ringtone/notification or alarms though.
FIX FOR NOTCH:
https://github.com/pravsterrr/treble-overlay-xiaomi-mi8se/blob/master/dist/treble-overlay-xiaomi-mi8se.apk?raw=true
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
let me know if you find anything.

pravsterrr said:
Decided to create a new thread on the SE forums since we now have our own forum.
So phhusson made a treble GSI for Android P and I got further with it than with any of the other GSIs.
WIFI and BLUETOOTH both work with this GSI.
Here's what I did to get it working (your mileage may vary and I am not responsible for any broken/ bricked devices as a result of these instructions, ALWAYS MAKE SURE YOU TAKE A FULL TWRP BACKUP OF YOUR DEVICE BEFORE ATTEMPTING THIS):
Unlock bootloader.
Download the latest TWRP from here and flash it. Make sure you're running at least version 3.2.3.
Boot into TWRP, tap on Wipe and then tap on "Format Data" and enter yes. Once it's done, reboot into recovery.
Next flash the latest Xiaomi.EU MiUI 10 Beta rom from here. Download it, transfer it to your phone's storage and then use TWRP to install the zip.
After it has installed, tap on Wipe on the TWRP main menu and swipe to factory reset.
Next flash the treble GSI for Lineage 15.1 from here. Download it, transfer to your phone's storage and then use TWRP to install the image file by tapping on Install, then "Install Image" on the bottom right and then select the Lineage image you transferred earlier. Select the "system" partition on the next screen and install.
Now reboot your phone and wait for Lineage to boot up. Once it has booted successfully, reboot into recovery. Use TWRP to factory reset your device again.
Now follow the steps for an A-Only device on this article
*BUT BEFORE YOU REBOOT, GO INTO THE ADVANCED MENU ON TWRP AND TAP ON "INSTALL ROOT"*. Once Magisk has been installed, reboot into system and hopefully you should boot. If not, try rebooting again and it should work.
Bugs (that I know of):
Audio is really broken and sounds horrible even with headphones plugged in.
Notch still isn't really recognized by the system.
let me know if you find anything.
Hope someone finds a fix for the audio
Click to expand...
Click to collapse
Hi guy,my mi8 also have audio bugs,do you fix it?

Qian Lee said:
Hi guy,my mi8 also have audio bugs,do you fix it?
Click to expand...
Click to collapse
You can fix media audio only by flashing the ViPER4Android module through Magisk Manager.
This doesn't fix it for ringtone/notification or alarms though.

pravsterrr said:
You can fix media audio only by flashing the ViPER4Android module through Magisk Manager.
This doesn't fix it for ringtone/notification or alarms though.
Click to expand...
Click to collapse
THX,I had fixed media audio,and I knows someone use an app to change ringtone,then the ringtone sounds ok
ps:I am sorry for my poor english，hope you can understand :victory:

The phone app,contacts,etc,moat of the system apps might FC.Which annoyed me is the input app,it will FC too

linqihao2333 said:
The phone app,contacts,etc,moat of the system apps might FC.Which annoyed me is the input app,it will FC too
Click to expand...
Click to collapse
最新的pe gsi并没有这些问题。

Qian Lee said:
THX,I had fixed media audio,and I knows someone use an app to change ringtone,then the ringtone sounds ok
ps:I am sorry for my poor english，hope you can understand :victory:
Click to expand...
Click to collapse
Which app // 你用过什么应用程序

great to see mi8 SE moving development

Got the notch detection working with help from phh.
Not responsible for any damage to your device / for any broken devices as a result of these instructions.
FIX FOR NOTCH:
https://github.com/pravsterrr/treble-overlay-xiaomi-mi8se/blob/master/dist/treble-overlay-xiaomi-mi8se.apk?raw=true
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"

pravsterrr said:
Got the notch detection working with help from phh.
Not responsible for any damage to your device / for any broken devices as a result of these instructions.
FIX FOR NOTCH:
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
Click to expand...
Click to collapse
It's good to see someone trying to make this rom works. Hope that audio problems will be fixed soon

Great, thank you. I will try it after its done first release with fixed sound issue.
pravsterrr said:
Got the notch detection working with help from phh.
Not responsible for any damage to your device / for any broken devices as a result of these instructions.
FIX FOR NOTCH:
https://github.com/pravsterrr/treble-overlay-xiaomi-mi8se/blob/master/dist/treble-overlay-xiaomi-mi8se.apk?raw=true
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
Click to expand...
Click to collapse

I will try this as well once I get a type c adaptor for my usb otg. Thanks for the tutorial.

The Mi 8 SE isn't my daily driver yet. Should I flash for testing or hold off?

Sorry but how to flash V4A through Magisk?
{
"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"
}

Silver Wind said:
Sorry but how to flash V4A through Magisk?
Click to expand...
Click to collapse
Download the zip via Magisk Manager and then flash using custom recovery

What's not working???

pravsterrr said:
Got the notch detection working with help from phh.
Not responsible for any damage to your device / for any broken devices as a result of these instructions.
FIX FOR NOTCH:
https://github.com/pravsterrr/treble-overlay-xiaomi-mi8se/blob/master/dist/treble-overlay-xiaomi-mi8se.apk?raw=true
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
Click to expand...
Click to collapse
Hey man, can you make a notch detection for android 8.1 vesion? Hope you can help me with it

new release is up, changelog:
https://github.com/phhusson/treble_experimentations/releases
September security patch
[Samsung Galaxy Note 9] Fix WiFi, brightness and fingerprint sensor
[Samsung Galaxy S9] Support assistant and partial "home" button on S9
Include phh su
[Xiaomi Mi 6X] Fix backlight control on
[Xiaomi ...] Fix sound on Mi 8 *, Poco,
[Xiaomi Mi Mix 2S] Delete fingerprint key event
[Treble app] [Huawei] Setting for hwcomposer overlay bypass option to workaround blur issue
[Treble app] minor fixes
Add support for status bar reduction for notches
Fix webview issue when not using gapps
[Known regression of this version] Broke ro.sf.hwrotation (needed for screen rotation on some devices)
Maybee our sound issue is fixed IT doesnt fixed
New PixelExperience release is up too...
https://github.com/EnesSastim/Downloads/releases

Any issues with mtp? Thanks

technoboi1 said:
new release is up, changelog:
https://github.com/phhusson/treble_experimentations/releases
September security patch
[Samsung Galaxy Note 9] Fix WiFi, brightness and fingerprint sensor
[Samsung Galaxy S9] Support assistant and partial "home" button on S9
Include phh su
[Xiaomi Mi 6X] Fix backlight control on
[Xiaomi ...] Fix sound on Mi 8 *, Poco,
[Xiaomi Mi Mix 2S] Delete fingerprint key event
[Treble app] [Huawei] Setting for hwcomposer overlay bypass option to workaround blur issue
[Treble app] minor fixes
Add support for status bar reduction for notches
Fix webview issue when not using gapps
[Known regression of this version] Broke ro.sf.hwrotation (needed for screen rotation on some devices)
Maybee our sound issue is fixed IT doesnt fixed
New PixelExperience release is up too...
https://github.com/EnesSastim/Downloads/releases
Click to expand...
Click to collapse
is the notch auto detected ?

[OFFICIAL] LineageOS 18.1 for D6603 Xperia Z3

{
"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"
}
Introduction​LineageOS 18.1 is an open-source Android distribution based on the Android Open Source Project (AOSP) version 11 (R). This is the official LineageOS 18.1 thread for the Sony Xperia Z3 (D6603).
Installation​If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below. There are also inofficial TWRP recovery builds available - if you want to use TWRP you need to ensure that it is compatible with Android 10 or later.
If you are coming from stock or other ROMs, you need to make a factory reset. You also will need a factory reset if you come from LineageOS 17.1 with encryption enabled.
For upgrading from an earlier LineageOS version, please follow the instructions here.
As always, make sure to backup before installing this ROM.
Detailed installation instructions​Install LineageOS on z3
Downloads​
ROM and Recovery: LineageOS Downloads for z3
Google Apps (optional): Recommended Google Apps can be found here.
Source Code​The source code of LineageOS is available here. If you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The z3 device tree is available here.
The kernel is based on V3.4 and source code for this device is available here. The used configuration is lineageos_shinano_leo_defconfig available at arch/arm/configs/lineageos_shinano_leo_defconfig in the kernel source.
Changelog​Changes for z3
Bug reports​How to submit a bug report
LineageOS GitLab
Contributors​NeoArian, Myself5, Mr.Tom_Tom
If you want to donate to support development:
Donate via PayPal to NeoArian
Donate via PayPal to LineageOS

Remarks, Questions & Answers
Known Major Issues
Thermal throttling of CPU cores: Due to a design issue of the thermal manager ("Thermanager") when used with older kernels like ours you have to expect that the frequency throttling of the CPU cores may fail, especially after(!) the device was getting hot and is recovering. This may lead to performance issues until reboot and other issues. Workaround: reboot device after heavy use.*
Currently we are looking into a potential issue with SD cards formated as "internal" memory:
Problems with SD card (#2573) · Issues · LineageOS / issues / android · GitLab
I did latest update of lineage but sd card is corrupt. Therefore tried reformatting again. When format as internal but the sd card is corrupt. But when trying...
gitlab.com
Miracast is currently disabled.
You tell us (with logs please)...
* To our knowledge, these are general issues on all AOSP/LineageOS based custom ROMs for this device family (Shinano).
Further hints
This ROM currently does not work with the Z3 Dual SIM variant. Here's a build for the Z3dual.
TWRP recovery (inofficial build, optional): TWRP
If you need Google Apps we recommend the OpenGApps "nano" package.
Magisk - see this post for issues with latest Magisk versions and a workaround
If you need to install a lot of apps you may run out of internal DATA storage capacity, especially if you install one of the larger GAPPS packages. These apps are initially placed on the system partition and do not cost you DATA capacity. However, every update which comes over the Play Store then fills up your data partition. Using an SD card formated as "external" storage does not help you much (unless you use a tool like app2sd which is no more recommended) and isn't encrypted. Formating the SD card as "adoptable storage" comes with the drawback that some apps do not allow to be migrated to this storage, and unfortunately this is true for some streaming music/video apps which need to store a lot of data obviously (for offline use). The solution I am using is to partition a SD card as "mixed", which gives you the possibility to offload at least some apps to adoptable storage while you still have a classical external FAT32 partition where e.g. your streaming app can save its offline files:
Find a large (I tested a 400GB microSDXC card) and fast ("A1" or higher) Micro SD card.
Follow this guide to partition your SD card. Note: all data on the card will be lost.
Restart your phone.
When you are notified that a new storage card has been detected, use it as "external". (Your internal partition has been recognized at that point already and does not need interaction.)
Go to settings / Storage. Verify that you see three entries: 1. Your internal phone storage of 16GB. This includes your SYSTEM partition. 2. Your SD card with an SD card symbol. The size shown should be the full capacity of the card. If you click on it, your "external" partition is shown (misleading) as "System" and blocked. Click on migrate data to migrate all possible apps to your adoptable storage. 3. Your sd card partition formated as mobile storage (unencrypted!).
Spoiler: How to create logs
Follow How To Logcat
When creating a log, can you make sure you run the command with the -b option to include kernel messages:
Code:
adb logcat -b all
If your device randomly reboots:
Go to Settings -> System -> Advanced -> Developer options -> Store logger data persistently on device. After the reboot occured: Pull the logs from /data/misc/logd/ (root required).
If your device crashes during boot and reboots to recovery:
Code:
adb pull /proc/last_kmsg
Please submit logs from clean systems without "Exposed" or similar modifications in place
Your feedback is wanted regarding the following topics
Reported size of adoptable storage - there was an issue in Lineage 17.1 - does it work in 18.1?
Formating SD cards as "internal storage" - there was an issue in Lineage 17.1 - does it work in 18.1?

Does anyone experience a kernel wakelock for SMD like on the Z3 Compact where it prevents deep sleep?

Amazing on d6603! Thank you!

Seems like magisk is still not flashable if installed in TWRP.
The workaround to flash magisk 20.4 first doesn't work anymore, since the installation aborts because it can't mount /vendor.
Patching a boot.img via magisk manager and flashing it doesn't work either.

MartinX3 said:
Seems like magisk is still not flashable if installed in TWRP.
The workaround to flash magisk 20.4 first doesn't work anymore, since the installation aborts because it can't mount /vendor.
Patching a boot.img via magisk manager and flashing it doesn't work either.
Click to expand...
Click to collapse
This one should work, see https://github.com/topjohnwu/Magisk/issues/3636

Samare said:
This one should work, see https://github.com/topjohnwu/Magisk/issues/3636
Click to expand...
Click to collapse
Awesome, it's fixed
I hope the Magisk Collaborators have enough rights to merge PR's and create new magisk releases.
(Or maybe the repo need to get forked)

Hello,
1. Magisk 23.0 isn't flashable on latest version (lineage-18.1-20210729-nightly-z3-signed.zip), but old version(0715, 0722) worked. >> #6 one works.
2. Cannot connect 2.4G wifi with 802.11n, but 802.11g works.
Thank you for all the contributions.

penguin Lin said:
Cannot connect 2.4G wifi with 802.11n, but 802.11g works.
Click to expand...
Click to collapse
Can you provide logs please?

Mr.Tom_Tom said:
Can you provide logs please?
Click to expand...
Click to collapse
I captured logs with terminal from rooted(#6) device.

Here is locat.txt.
Edit:
I cannot attach file on XDA...
I tried upload to google drive, thanks.

penguin Lin said:
Cannot connect 2.4G wifi with 802.11n, but 802.11g works.
Here is locat.txt.
Click to expand...
Click to collapse
The interesting part is:
Code:
07-31 03:03:34.675 2734 2734 I wpa_supplicant: wlan0: Trying to associate with SSID '[SSID Name]'
07-31 03:03:34.863 2734 2734 I wpa_supplicant: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=10:bf:48:[...] status_code=18
Status Code:
18Association denied due to requesting station not supporting all of the data rates in the
BSSBasicRateSet parameterWill happen if the rates in the assoc request are not in the BasicRateSet in the beacon.
Hard to tell for me if the root cause for this lies in the handheld device or the access point. I am not 100% sure but I guess my devices connect fine to an 802.11n 2.4GHz network. Look if you have some exotic features enabled in your router, like proprietary bandwidth settings or something like that. If you are interested in digging a bit deeper install this ROM please (just for testing) and send me a log via PM.

Mr.Tom_Tom said:
The interesting part is:
Code:
07-31 03:03:34.675 2734 2734 I wpa_supplicant: wlan0: Trying to associate with SSID '[SSID Name]'
07-31 03:03:34.863 2734 2734 I wpa_supplicant: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=10:bf:48:[...] status_code=18
Status Code:
18Association denied due to requesting station not supporting all of the data rates in the
BSSBasicRateSet parameterWill happen if the rates in the assoc request are not in the BasicRateSet in the beacon.
Hard to tell for me if the root cause for this lies in the handheld device or the access point. I am not 100% sure but I guess my devices connect fine to an 802.11n 2.4GHz network. Look if you have some exotic features enabled in your router, like proprietary bandwidth settings or something like that. If you are interested in digging a bit deeper install this ROM please (just for testing) and send me a log via PM.
Click to expand...
Click to collapse
I use the Z3 with a Fritz!Box 7490 and 802.11g+n (Wi-Fi 4) without problems.
I also use WPA3 with WPA2 fallback (I am not sure at the moment if the Z3 has WPA3 support)

MartinX3 said:
I also use WPA3 with WPA2 fallback (I am not sure at the moment if the Z3 has WPA3 support)
Click to expand...
Click to collapse
Unfortunately our chipset doesn't seem to support WPA3, at least there's no firmware available which supports is. Therefore the next official build will include this:
https://review.lineageos.org/c/LineageOS/android_device_sony_msm8974-common/+/309145

Mr.Tom_Tom said:
Unfortunately our chipset doesn't seem to support WPA3, at least there's no firmware available which supports is. Therefore the next official build will include this:
https://review.lineageos.org/c/LineageOS/android_device_sony_msm8974-common/+/309145
Click to expand...
Click to collapse
Is it really needed?
I just added the Z3 to the WPA3 network without specifying WPA2 in the settings.
My bad.
I was connected to the WPA2 guest network all the time.
I can confirm that the device won't connect to the normal WPA3/2 wifi network.

penguin Lin said:
Hello,
1. Magisk 23.0 isn't flashable on latest version (lineage-18.1-20210729-nightly-z3-signed.zip), but old version(0715, 0722) worked.
2. Cannot connect 2.4G wifi with 802.11n, but 802.11g works.
Thank you for all the contributions.
Click to expand...
Click to collapse
For magisk try https://github.com/topjohnwu/Magisk/files/6330986/Magisk-v22.1_mod_sony.zip it will work

is EdXposed working ?

Mitezuss said:
is EdXposed working ?
Click to expand...
Click to collapse
I've read in many threads that edXposed breaks SafetyNet. In general, they advise to try LSPosed, instead.

Hi, is it a problem ? :
/sys/devices/system/cpu/cpu1/cpufreq/scaling_cur_freq no such file
/sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq no such file

giúp tôi! Tôi không thể hợp nhất các biểu tượng trong một thư mục. xin vui lòng hướng dẫn tôi làm thế nào để làm điều đó, cảm ơn!

[ROM][UNOFFICIAL][12.1][DISCONTINUED] LineageOS 19.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

{
"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 is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820/tree/lineage-19.1

Requirements:
Any Q, R or S based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and Lygisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Known issues
VoLTE/VoWiFi
You tell me

Good job as usual!! So live display and natural (sRGB) profile doesn't work yet?

Hi @Linux4 ,
ROM boots fine, was a little put off by the change back to nice old lineage recovery style. Two issue I have encountered:
- /sdcard won't mount in recovery so I have to sideload
- I can't skip signature verification so no gapps install right now (I have tried bitGapps but to no avail either)
ROM boots unbelievably fast

Is Material You (Monet) included?

No source code? Whaat

Razuuu said:
No source code? Whaat
Click to expand...
Click to collapse
Read the posts... Bottom of first post: "Source Code: Coming soon"
Thanks a lot for your work Linux4!!

So far the Rom is really smooth and has great battery life.
Unfortunately we are getting a 403 forbidden when trying to download Gapps. Also the Rom asks to format the sdcard for some reason.
Other than that great work guys!

mike_app said:
So far the Rom is really smooth and has great battery life.
Unfortunately we are getting a 403 forbidden when trying to download Gapps. Also the Rom asks to format the sdcard for some reason.
Other than that great work guys!
Click to expand...
Click to collapse
He gave us another Gapps link.
Sdcard can't be mounted for some reason...

@Linux4 , great work, thanks a lot!
I was wondering about firmware updates. Do they come with lineageos updates or do we need to update/flash firmware still manually?

Apologies but I don't know how to do logcats, as I am new to this. However I experienced flickering once I use google maps. Also, there is this instance that the banking app I use treats the phone as emulator and not an actual device. And during login in mobile legends, gboard or the built in android aosp keyboard does not pop up whenever I try to tap the field to login my credentials.
So far, these are the things that I encountered. Other than that rom is great and smooth

mcgi5sr2 said:
Hallo @Linux4 ,
ROM bootet gut, war ein wenig abgeschreckt von dem Wechsel zurück zum netten alten Lineage Recovery-Stil. Zwei Probleme, auf die ich gestoßen bin:
- /sdcard wird bei der Wiederherstellung nicht gemountet, also muss ich seitlich laden
- Ich kann die Signaturüberprüfung nicht überspringen, daher werden derzeit keine Gapps installiert (ich habe bitGapps ausprobiert, aber auch ohne Erfolg)
ROM bootet unglaublich schnell
Click to expand...
Click to collapse
you can use the unofficial LOS18.1 recovery to install the mtg package, as well as to install magisk

does it work if i sideload magisk?

efkhai469 said:
does it work if i sideload magisk?
Click to expand...
Click to collapse
Answer at the bottom of the second post... (item number 5 + final note at the end of the post)

Hi Colleagues
everything is fine for me on this room, I don't know how to send logs, the only issue what I see just like comment.
1. Google Maps has a zoom in on A12, this also happens with other ports.
2. at least for me the audio in calls through Bluetooth, don't work it sound like a robot, in both versions, in both apps of Google Phone and on Lineage Phone app.
The rest it is working fine, just I miss advanced restart for don't make always the key combinations hehehehe.
Regards and Thanks really good job.

Thanks alot for your hard work..
Is it just me or the in-call speaker voice is so low at high-level in every AOSP rom in comparison to stock?

kachoman said:
Hi Colleagues
everything is fine for me on this room, I don't know how to send logs, the only issue what I see just like comment.
1. Google Maps has a zoom in on A12, this also happens with other ports.
2. at least for me the audio in calls through Bluetooth, don't work it sound like a robot, in both versions, in both apps of Google Phone and on Lineage Phone app.
The rest it is working fine, just I miss advanced restart for don't make always the key combinations hehehehe.
Regards and Thanks really good job.
Click to expand...
Click to collapse
Second one will be fixed later during 19.0 bringup (lineage had some patch for that which isn't in 19.0 yet)
Also advanced reboot is a lineage feature so that's why it's not there yet.
It's more or less plain AOSP at the moment

Linux4 said:
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Known issues
VoLTE/VoWiFi
LineageOS specific features like livedisplay (for now)
You tell me
Click to expand...
Click to collapse
Another issue: the apps installed on my device can't access the phone's storage, even if I grant access to it.

ThePS4Gamer said:
Another issue: the apps installed on my device can't access the phone's storage, even if I grant access to it.
Click to expand...
Click to collapse
This isn't an issue is the consequences of the fact that selinux is enforced...

[ROM][UNOFFICIAL][MONTHLY][EAS][R-HALs] Pixel Experience 13 [NORMAL/PLUS] for Xiaomi Mi5

{
"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"
}
PixelExperience for Xiaomi Mi 5 [Gemini]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 13.0
Whats working?
Wifi
Wifi hotspot
RIL
Mobile data
GPS
Sensors
Camera
Flashlight
Camcorder
Bluetooth
NFC/GPAY
Lights
Sound / vibration
Fingerprint
WiFi Display
VoLTE
Double Tap To Wake
Buttons swap
Google Voice Match
SELinux enforcing
Safetynet
DON'T FLASH GAPPS, ALREADY INCLUDED
Download standard version from Android File Host
Download PLUS version from Android File Host
​
Flashing Instructions:
Pre-installation:
Pixel Experience Recovery (Download from here)
First time installation:
Fastboot or flash recovery image
Reboot to new recovery
Click on Factory Reset --> Format data/factory reset
Click on apply update and sideload the zip file or install it using an USB OTG
Enjoy
About Camera App: default camera app is GCAM version SGCAM_8.4.400.42.XXX_STABLE_V35 by Shamim. Everything works fine except 240 fps (1/8) slow motion videos
mandayugana shared his config xml file, which add the specific noise model for Gemini with Shamim GCAM, dowload it from my Github (sgcam-8.4-v35-pe13.xml) or from his post, apply to GCAM following this tutorial and say thanks to him for his great work
XDA:DevDB Information
Pixel Experience, ROM for the Xiaomi Mi 5
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
ROM Firmware Required: MIUI V10.2.2.0.OAAMIXM as minimum target
Based On: AOSP
Source Kernel repo: Link
Gemini device tree repo: Link
Xiaomi msm8996-common repo: Link
Vendor repo: Link
Special thanks to
LineageOS
Pixel Experience
Shamim
xNombre
mandayugana

I'm currently using PixelExperience_gemini_12.1
Is it possible to directly update it via twrp? (I don't have a PC to install PErecovery)

ademuhamad said:
I'm currently using PixelExperience_gemini_12.1
Is it possible to directly update it via twrp? (I don't have a PC to install PErecovery)
Click to expand...
Click to collapse
I haven't tried but could work. Just be sure to format internal storage before rebooting into system

the rom is very laggy, and cpu usage between 50%-100% with nothing open :/

Echidna_Kawaii said:
the rom is very laggy, and cpu usage between 50%-100% with nothing open :/
Click to expand...
Click to collapse
Check what process is eating your cpu in the background, i have no problems at all with cpu usage on screen and with deep sleep

and also this giving Random reboot here :/

Echidna_Kawaii said:
and also this giving Random reboot here :/
Click to expand...
Click to collapse
No one reported random reboots, i never had once in a week of usage. Logs or never happened

-+BB+- said:
I haven't tried but could work. Just be sure to format internal storage before rebooting into system
Click to expand...
Click to collapse
ERROR:1 )l

暗夜很无语 said:
ERROR:1 )l
Click to expand...
Click to collapse
That's why I wrote could, I haven't tried and there are multiple versions of TWRP, if you experience problems flashing the ROM use my recovery

pretty much very stable rom... working everything very smothly...but one issue...after usung 1 or 2 shot with gcam its freeze the cam...and then can't open the gcam anymore...

Unfortunately I can't install it. It would be great if there was a zip file that can be installed with twrp. Thanks for your effort anyway.

after using 2-3 days.. i found some bug
1. after activated vibration mode no vibration icon showing in status bar
2. gcam not working (tried many version)
and after some times phone autometically try to reboot itself but stuck at mi logo.. have to forcefully tap on power button to reboot manually (happened every time i install different version of gcam) i had same issue in lineageOS 19
3. no ota updater option (maybe because its unofficial or i don't know)
4. don't have the option double tab on status bar area to lock screen
5. not showing am/pm in time

İST1907 said:
Unfortunately I can't install it. It would be great if there was a zip file that can be installed with twrp. Thanks for your effort anyway.
Click to expand...
Click to collapse
Could you please post the log of the error during the flash?
mrinfinity0007 said:
after using 2-3 days.. i found some bug
1. after activated vibration mode no vibration icon showing in status bar
2. gcam not working (tried many version)
and after some times phone autometically try to reboot itself but stuck at mi logo.. have to forcefully tap on power button to reboot manually (happened every time i install different version of gcam) i had same issue in lineageOS 19
3. no ota updater option (maybe because its unofficial or i don't know)
4. don't have the option double tab on status bar area to lock screen
5. not showing am/pm in time
Click to expand...
Click to collapse
1 and 5 are AOSP/PE bugs, hopefully will be fixed in QPR2 release
2 don't use Gcam for now, i've fixed hdr+ photos on recent Gcam version in my internal builds but it's still crashing causing a reboot after a minute, i had no time to inspect yet because i was focused on EAS and power HAL port
3 correct, no OTA update app on unofficial builds
4 i'm not 100% sure but if i remember well it's a feature of plus version

@-+BB+-
Thanks for sharing your Mi5 rom with us.
Since Android 12 the Mi5 phone is missing a working TWRP recovery, with support of the fbe encryption. This prevents many users from trying all the new roms, because there is no way to take full backups.
Can you tell me what is the reason?
I would be glad to help the development, but I don't know where to start. If I had someone who can guide me in the process I could do my part. Being part of a team would be ideal.

JackSlaterIV said:
@-+BB+-
Thanks for sharing your Mi5 rom with us.
Since Android 12 the Mi5 phone is missing a working TWRP recovery, with support of the fbe encryption. This prevents many users from trying all the new roms, because there is no way to take full backups.
Can you tell me what is the reason?
I would be glad to help the development, but I don't know where to start. If I had someone who can guide me in the process I could do my part. Being part of a team would be ideal.
Click to expand...
Click to collapse
Unfortunately Pixel Experience doesn't support natively TWRP compiling, and i don't have space on my NVME for another build enviroment. Also as far as i know they did not release yet an Android 13 recovery, they are working right now on it, but i don't know if works. Do you know if TWRP supports FBE on other devices? if TWRP supports FBE then best thing would be compile TWRP in an Android 12 build enviroment with a 4.4 kernel with FBE support. you can use my repos or los repos, it' the same. The only requested changes are a makefile with a basic conf for mi5 and convert the fstab in a compatible version for TWRP
@mrinfinity0007 not fixed yet but probably i've understood what's happening... Could you please try to put selinux in permissive mode and use the camera? You can do with adb:
Code:
adb root
adb shell setenforce 0
adb shell getenforce
The last command checks that selinux is correctly disabled, the output must be 0 or permissive

@-+BB+-
Thank you. Yes, from what I see TWRP supports FBE and A12 on other devices.
But I guess that porting it on our device is not that easy as one could think.
My problem is finding detailed guides to start understanding the process, or at least having a overall view.
Anyway I don't want to post too many OT messages on your thread.

-+BB+- said:
That's why I wrote could, I haven't tried and there are multiple versions of TWRP, if you experience problems flashing the ROM use my recovery
Click to expand...
Click to collapse
Let me try another TWRP version

-+BB+- said:
@mrinfinity0007 not fixed yet but probably i've understood what's happening... Could you please try to put selinux in permissive mode and use the camera? You can do with adb:
Code:
adb root
adb shell setenforce 0
adb shell getenforce
The last command checks that selinux is correctly disabled, the output must be 0 or permissive
Click to expand...
Click to collapse
i don't root my phone? does it work without it?

JackSlaterIV said:
@-+BB+-
Thank you. Yes, from what I see TWRP supports FBE and A12 on other devices.
But I guess that porting it on our device is not that easy as one could think.
My problem is finding detailed guides to start understanding the process, or at least having a overall view.
Anyway I don't want to post too many OT messages on your thread.
Click to expand...
Click to collapse
I will take a look this weekend and let you know because I don't remember where but I'm pretty sure that I read a tutorial for TWRP compiling some years ago
暗夜很无语 said:
Let me try another TWRP version
Click to expand...
Click to collapse
If your goal is to flash the ROM without format the internal memory won't work, you may be able to flash the zip but after the flash you'll be forced to format the internal memory without fbe support
mrinfinity0007 said:
i don't root my phone? does it work without it?
Click to expand...
Click to collapse
Yes it's a root shell, you have root permissions only with ADB, not in your phone. If you want to roll back to selinux enforcing and stop the rooted shell simply reboot the phone, that changes doesn't survive after the reboot

@JackSlaterIV found it, it's old and some things may be slightly different but this is a good tutorial.
Here's the link of the minimal manifest 12.1 is the correct branch but decryption is WIP at the moment, don' t think will work, unless you don't set a password/PIN/pattern, in that way should be fine
@mrinfinity0007 never mind, i've fixed It, Gcam was crashing because it was trying to use hexagon for HDR+, but SELinux was blocking it. Now it's wotking fine even in enforcing mode
PS: i've decided to upload the latest personal build i made, some thing may change because i'm still testing them, but more or less (on device side) this will be the next official release when PE devs will merge QPR2 changes and feb security patch.
Here's the direct link
And here's the changelog:
ROM:
- Synced code with latest PE changes
Kernel
- Ported EAS and set it as default scheduler
- Ported Stune Boost and use it as default
- Fixed almost all compiling warns
- Ported misc optimisations from infinity kernel
- Fixed a bug that could cause the boot to fail (Mi logo --> Black screen --> Mi logo again)
- Misc fixes from upstream
Recovery
- Fixed a bug that could cause the boot to fail (Mi logo --> Black screen --> Mi logo again)
Device Tree
- Ported EAS
- Move to EAS compatible power HAL
- QCOM audio HAL: add missing audio power hints support
- Fixed Google Camera crash when trying to use Hexagon
- Camera: move to Gcam Version MGC_8.1.101_A9_GV2b_ENG big thanks to BSG. Camera can be updated with all APKs released by BSG, just be sure to download the ENG version
- SELinux: fixed all denials
- Ported various improvements from my old 12.1 ROM
- Tuned ZRAM size for 3Gb devices
- Camera: improved camera HAL + misc fixes
- Configure SQLite to operate in MEMORY mode
- Set CFQ as default scheduler
- Added pixel animated wallpapers to build
For more detailed changes take a look at my repos
PS: i cannot test GPAY at the moment because i'm testing other things and i'm running in permissive mode, if someone decide to try the update and use GPAY please let me know if works, i made some changes to sepolicy and i want to be 100% sure that Google pay isn't broken before the official release.

[TESTING] TrebleDroid - Android 13 for SM-A730F/DS

{
"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"
}
A couple of days ago my mom gave me this phone. So, i want a new Android (and kick the s**t out all the bloatware of Samsung). After several tries, i make TrebleDroid vanilla works. And really good! Hell, even shows dual sims!
...And since there's no trace of someone doing this (or a guide), here are the steps. It was trial and error but i did it and it worked. (Sorry for english, i'm a native spanish speaker):
On original firmware:
- Activate OEM unlock in Developer Options
- Enable USB debugging
This is the version I used for Android 13 (at the moment, system-td-arm64-ab-vndklite-vanilla.img.xz from ci-20230510)
Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations
github.com
Vendor-Quack is required for SaR.
[SAR][Vendor][10][A530F/A530W/A730F] Vendor Quack V2.5 For Galaxy A8/A8+ 2018
Dude did you tried to enable magisk hide from settings? That should pass safety net on all Android 10+ roms :) Hey, i'm succesfully flashed magisk 21.1 beta version with safety net passed on Android R
forum.xda-developers.com
Vendor-Quack_V2.6
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
To load TWRP and change the system to Treble-compatible, instructions here. Download TWRP-jackpot2lte-Treble.img and TrebleCreator-A730F.zip
[GUIDE][TREBLE][A730F] Project Treble Guide for Galaxy A8+ 2018 (18/04/2019)
Project Treble Guide for Samsung Galaxy A8+ Just to make it clear I'm not responsible for whatever damage this could possibly cause to your device. Treble is everywhere, so why shouldn't we join it? I'm proud to announce that Galaxy A8+...
forum.xda-developers.com
ONCE TWRP IS LOADED, THE PHONE SHOULD NOT BE RESTARTED OR IT WILL BE OEM LOCK AND YOU WILL HAVE TO INSTALL THE ORIGINAL FW AND DO THE TRICK TO ELIMINATE THE KG-RMM STATUS:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
download patch:
https://forum.xda-developers.com/attachments/rmm_bypass_v3_corsicanu-zip.4778435/
YOU MUST LOAD THE PATCH.
In my case to not wait 7 days:
RMM a730f
I commented my experience on my a730f with bit 4, 1.- After flash rom, select a manual date 10 days before the current date. 2.- remove the automatic update option, and select manual download, then restart. 3.- Verify that the phone shows the...
forum.xda-developers.com
1.- After flashing OEM rom, select a manual date 10 days before the current date of the phone.
2.- remove the automatic update option, and select manual download, then restart. Check that developer options is disable.
3.- enter google and samsung account on the phone.
4.- wait 3 hours (in my case, less. 1 hour), enable developer options and there will be the OEM unlock enabled.
With ODIN load TWRP-jackpot2lte-Treble.img (it's version 3.2.3 - 3.3.0 didn't give me good results)
All of the following steps refer to TWRP:
- After installing TWRP without entering the rom, /data must be formatted. After that, reboot into recovery mode using the reboot menu. If /data is not formatted, the partitions will remain encrypted and the rest cannot be wiped.
-------------------------------------------------- -----------------------
From now on, every time you make a change, you must reboot, because without this step, loading anything via TWRP will fail (if you didn't reboot, the rom will not start or froze, or the zip will not load correctly, or you'll see partition access errors on the log). ALL STEPS MUST BE FOLLOWED OR THE SYSTEM WILL REMAIN ON THE ANDROID LOADING SCREEN FOREVER.
-------------------------------------------------- -----------------------
- After reboot, Wipe in /cache,/vendor (if it exists. Otherwise it will be created later),/system,/data,/dalvik. Reboot into recovery mode using the reboot menu.
- Load TrebleCreator-A730F.zip. It will create the partitions for treble. It has an automatic reboot. After the reboot it should show the script and then reboot again and go back to TWRP. If the automatic reboot does not happen and the script screen doesn't show up, you will have to start again from the /data format step. It is vital since the automatic reboot and script screen indicates that the partitions were all correctly loaded.
- Load RMM_Bypass_v3_corsicanu.zip. This is to bypass the OEM lock. It should be done before Vendor-Quack, as the vendor zip encrypts the /vendor partition and makes it inaccessible. Reboot into recovery mode using the reboot menu.
- Load Vendor-Quack_V2.6.zip. Reboot into recovery mode using the reboot menu.
- Finally, the .img of Android 13. One last reboot to recovery and THEN reboot to system.
After this the rom should start without problems. TWRP builds with treble are now LOCKED once booted. When trying to enter recovery, they get frozen at the TWRP boot screen. In order to load gapps, you must load the "latest" version of TWRP (in quotes because TWRP version 3.7.0 does not load since it is larger than the /boot partition. In this case, you must load 3.6.2 ) using Odin and Download mode.
Download TWRP for jackpot2lte
Download TWRP Open Recovery for jackpot2lte
dl.twrp.me
Once the latest version of TWRP is loaded, the zips can be loaded without problems. IN THIS VERSION OF TWRP IT IS SUGGESTED NOT TO MAKE ANY CHANGES. ZIP INSTALLATION ONLY. Surely something will ruin this version of twrp if something is done with it since it does not show the /vendor partition.
Gapps that works: NikGapps. That's it
Go! Get crazy and share the results!
THINGS THAT DONT WORK SO FAR:
- Lantern (with the system doesn't work. If u use flash on camera, WORKS)
- Brightness is very picky. (on settings you'll find "Phh Treble Settings". There are some extra functions disabled -- by default? -- go check and see whats best for u. BUT! Careful, Icarus. Don't mess with stuff u dont know.)
- i don't have a SIM at the moment, so i can't tell if phone works.
- Root? Don't need it. Don't know if it's working.
THANKS TO:
@phhusson for TrebleDroid and Exynos updates, and aaaall his long work!
@prashantp01 for Vendor_Quack, Treble, and the patched TWRPs for this phone.
@corsicanu and all the people behind the KG bypass patch.
@juankp9086 for the guide to reset KG status.
aaand finally the team behind TWRP.

Is this a GSI? If not, you MUST provide the source you used for your kernel, as required by the GPL Policy.
Further, did you base this on someone else's work? You MUST give credit where due, per the Forum Rules.

V0latyle said:
Is this a GSI? If not, you MUST provide the source you used for your kernel, as required by the GPL Policy.
Click to expand...
Click to collapse
Yes. It's a GSI from @phhusson. All vanilla, no modification whatsoever. Kernel is included on Vendor_Quack, a SaR posted here too, from @prashantp01 . All is based on guides and files from this same forum (and all files and sources are linked here), except the steps.
V0latyle said:
Further, did you base this on someone else's work? You MUST give credit where due, per the Forum Rules.
Click to expand...
Click to collapse
No problem. I'll quote everyone involved for making this Done
As for the steps, as i said, it was trial and error. There was no guides or something that i know of (FOR ANDROID 13). I just take a leap of faith based on last good know version working (Android 11) and use that, since Android 12 was no good in some details.

BernoO said:
Yes. It's a GSI from @phhusson. All vanilla, no modification whatsoever. Kernel is included on Vendor_Quack, a SaR posted here too, from @prashantp01 . All is based on guides and files from this same forum (and all files and sources are linked here), except the steps.
Click to expand...
Click to collapse
A GSI does not include a kernel, but since you linked to an established project that already has a published source, everything is good.
Thank you for adding credits.
I don't know if you saw this, but the Magisk installation instructions include details on how to defeat KG/Vaultkeeper.

Did Android 13 worked for you , and did you try setting lock as that seems to cause a bootloop .
If it worked can you tell me how you did it as my phone's seems to bootloop after trying to set a lock (pin,etc) on Android 12 and 13 and I have already tried PixelExperience and LineageOs .

NVM wrong topic

AlphaMaster08 said:
Did Android 13 worked for you , and did you try setting lock as that seems to cause a bootloop .
If it worked can you tell me how you did it as my phone's seems to bootloop after trying to set a lock (pin,etc) on Android 12 and 13 and I have already tried PixelExperience and LineageOs .
Click to expand...
Click to collapse
Can confirm. Since i was just testing, didnt need to lock it. After trying to set a pattern or pin lock (and systemUI crashes), ive reboot and then a soft bootloop (for 3 seconds i can see lock screen, then android boot screen, 3 sec lock screen and so...).
After another reboot, bootloop.
I dont have this issue since lock screen was just sliding.
Another issue: bluetooth is working, but when wireless speakers are on sync, no sound whatsoever. A common fault on several android 13 installations as i can tell.
Remember that @phhusson is adding exynos updates on TrebleDroid, so we should expect (or beg, cant tell ) that more fixes are on the way?

And BTW if Someone needs it the best Roms/GSI for A8+ are TreeUi(S20 Port) , PixelExperience (11) and FusionX(10,maybe) and Don't try Android 12 /13Gsi as they don't work currently.

AlphaMaster08 said:
And BTW if Someone needs it the best Roms/GSI for A8+ are TreeUi(S20 Port) , PixelExperience (11) and FusionX(10,maybe) and Don't try Android 12 /13Gsi as they don't work currently.
Click to expand...
Click to collapse
Thanks!
This guide most of all was because a couple of users were asking if there's a way to run Android 13 on their A8s. So there's an answer for that now. Almost.