[Android 12] [EXPERIMENTAL] [RE-UPLOADED] AOSP Android 12 for A21s - Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O

[Android 12] [EXPERIMENTAL] [RE-UPLOADED] AOSP Android 12 for A21s - Samsung Galaxy A21s ROMs, Kernels, Recoveries, & O

WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser app is not installed by default. Installing Firefox or Chrome from Google Play is recommended
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6/U7, please use the recovery tar for U6/U7.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img. boot.img, dtbo.img, recovery(U5), recovery(U6), recovery(U7)
- ADB and Fastboot
- Odin
- Kernel Source
- Google Apps(Flame)
WARNING: A BUG WHICH CAN POTENTIALLY LEAD TO BOOT LOOP ON U7 WAS FOUND. IF YOU ARE ON U7, PLEASE DO NOT FLASH THIS ROM UNTIL THIS IS FIXED.
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
Changelogs:
2021-10-19: Initial Release (AOSP 12.0.0_r2)
2021-10-21: Updated to AOSP 12.0.0_r3
2021-11-03: Updated to AOSP 12.0.0_r13 & added U7 support
2021-11-22: Fixed graphics issue, fixed battery issue (when battery level sometimes dropped by more than 2-3% on reboot), and fixed force crash when choosing Battery Manager in Settings
2021-11-25: Updated to AOSP 12.0.0_r15, changed battery mechanism to make it more accurate
2021-11-27: Kernel GPU driver update (R33P0 -> R34P0), LTE is now enabled by default
2021-12-10: Updated to AOSP 12.0.0_r16, removed the annoying search box widget on the home screen
2022-01-01: EGL graphics driver update to improve performance, minor bug fixes related to some apps.
SCREENSHOTS:
{
"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"
}

EDIT: the boot issue has been fixed, and you can now download the ROM.

This is great!
Do you working on this ROM for A21s, or you working on LineageOS 18 A11, paralel with this ROM?

grccorps said:
EDIT: the boot issue has been fixed, and you can now download the ROM.
Click to expand...
Click to collapse
instead of fastboot can we sideload super,boot etc?

Zdivan said:
This is great!
Do you working on this ROM for A21s, or you working on LineageOS 18 A11, paralel with this ROM?
Click to expand...
Click to collapse
Yes. I am also working on Lineage 18. Actually, the source code for this ROM is based on the source code for the Lineage 18. (of course, along with some modifications)

NuzzaimStark said:
instead of fastboot can we sideload super,boot etc?
Click to expand...
Click to collapse
I'm really sorry, but it is not possible to adb sideload images.

i got this when type and enter "fastboot flash boot boot.img"
C:\Users\nussa\Downloads\platform-tools>fastboot flash boot boot.img
< waiting for any device >
nothing showing in phone log

grccorps said:
I'm really sorry, but it is not possible to adb sideload images.
Click to expand...
Click to collapse
I am a bit sad because gaming time screen is flickering... Grrcorps pls check in your phone

grccorps said:
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
It has been only 2 weeks since Android 12 came out, so there may be some instability / bugs. I will try to work it out as time goes by. Also, when Lineage 19 is released, I will try to port it too. (Shouldn't be too hard though, as Lineage is quite similar to AOSP)
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
The network is set to 3G by default, so in order to use LTE, you should go to Settings->Network and Internet->Internet and change the default network setting from 3G to LTE.
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser and Music/Video Player apps are not installed by default. Installing Chrome and YouTube music from Google Pay is recommended
The search bar on the home launcher is useless until "Google" app or "Google Go" app is installed.
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img, boot.img, dtbo.img (Download all three)
- Recovery(for U5) / Recovery(for U6) / Recovery(for U7: coming soon)
- Google Apps
- ADB and Fastboot
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
SCREENSHOTS:
View attachment 5436707View attachment 5436709View attachment 5436711View attachment 5436713View attachment 5436731
Click to expand...
Click to collapse
only 1 sim card is work or 2 sim cards is working ?
( A217F ) , EGY

NuzzaimStark said:
I am a bit sad because gaming time screen is flickering... Grrcorps pls check in your phone
Click to expand...
Click to collapse
I'm really sorry, but could you please tell me which game it is?

ayman9321 said:
only 1 sim card is work or 2 sim cards is working ?
( A217F ) , EGY
Click to expand...
Click to collapse
As of now, this ROM is for single sim variant...

grccorps said:
As of now, this ROM is for single sim variant...
Click to expand...
Click to collapse
how can i fix it or can you help me to make 2 sim cards work ?
i install pit file for my country from the csc.tar from the android 11 firmware but not work after i install the stock android 11 firmware that is says your sim cards is changed restart to apply the changes .

grccorps said:
I'm really sorry, but could you please tell me which game it is?
Click to expand...
Click to collapse
Watch my gameplay I screen recorded it

NuzzaimStark said:
Watch my gameplay I screen recorded it
Click to expand...
Click to collapse
It said EXPERIMENTAL.
This ROM is not good enough for daily driver.
Wait for new version or install Lineage 18, or continue use this rom for testing.

Can anyone guide me how to root this rom?

Is this the s
grccorps said:
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
It has been only 2 weeks since Android 12 came out, so there may be some instability / bugs. I will try to work it out as time goes by. Also, when Lineage 19 is released, I will try to port it too. (Shouldn't be too hard though, as Lineage is quite similar to AOSP)
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
The network is set to 3G by default, so in order to use LTE, you should go to Settings->Network and Internet->Internet and change the default network setting from 3G to LTE.
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser and Music/Video Player apps are not installed by default. Installing Chrome and YouTube music from Google Pay is recommended
The search bar on the home launcher is useless until "Google" app or "Google Go" app is installed.
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img, boot.img, dtbo.img (Download all three)
- Recovery(for U5) / Recovery(for U6) / Recovery(for U7: coming soon)
- Google Apps
- ADB and Fastboot
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
SCREENSHOTS:
View attachment 5436707View attachment 5436709View attachment 5436711View attachment 5436713View attachment 5436731
Click to expand...
Click to collapse
Is this the stock Samsung Android 12 ROM?

NuzzaimStark said:
Can anyone guide me how to root this rom?
Click to expand...
Click to collapse
Patch the boot.img with magisk, same as how you root any other ROM
Maxis89 said:
Is this the s
Is this the stock Samsung Android 12 ROM?
Click to expand...
Click to collapse
No it is AOSP, it is written in the OP and also the screenshots are quite clearly AOSP

Do you need any logs or bug reports? If so, how to get them? Will the Lineage OS method work?
Add.: Gapps installation error: !Wrong android version detected. This package is for android 10.0 only. Your ROM is Android: 12. Blame, blind.

I tried rooting. There is no option ( root permission for usb debugging ) developer setting.
And I get these

NuzzaimStark said:
I tried rooting. There is no option ( root permission for usb debugging ) developer setting.
And I get these
Click to expand...
Click to collapse
Patch the boot.img with magisk app. Then reboot fastboot and flash the patched.img with fastboot.
This is, and will always be, the recommended way of installing magisk and getting root.

Related

[GUİDE] [ROM] [10] How to install Pixel Experience ROM for Redmi 8 [GSI]

First of all, the download link of all the files required for this "ROM" is taken from the "xda developers forum" posts.
I was constantly experimenting with GSI roms for Redmi 8. I was able to install the Pixel ROM on Redmi 8. I don't think you will have a problem if you follow the steps I shared with you one by one.
I do not take responsibility for the ROM. RESPONSIBILITY IS ENTIRELY YOURS.
Not working
-Face unlock
-Radio
-VoLTE
(You need to make a setting for the camera, notch, LTE Mobile Network and auto-brightness. I told you how to make the settings.)
NOTE: A computer is required to make this ROM setup. It must also be installed in ADB on your computer.
Note: You can install this ROM Google Camera as apk. Unfortunately, there are no features such as Portrait, night mode in the original camera application of the device. However, you can use it if you install it as an apk.
Please download that files:
Download - Pixel Experience ROM GSI file
Download --- Sky Hawk Recovery file
Download - Permissiver V5
Download -Certification Patch for Redmi 8
Download -Treble overlay for Redmi 8
Download --- Lastest Magisk-v20.4
Here -Get the TWRP Official for Redmi 8
Download - vbmeta.img
Note: Please charge your phone at least 60%
First, take the necessary backups as your phone will be completely reset.
1- Unlock your bootloader. For unlocking follow this: http://en.miui.com/unlock/
2- Copy all the files to your SD Card (PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img, SHRP_v2.2.zip, Permissiver_v5.zip, Certification_Patch.zip, Magisk-v20.4.zip, treble-overlay-xiaomi-redmi8.apk)
3-Enable USB debugging. Connect the phone your computer Then copy the twrp.img and vbmeta.img files to the adb folder.
Note: If the name of your twrp file is not twrp.img, please set its name to twrp.img.
4- Go to your computer, open adb folder in cmd, write that:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
5- Now we will go to the restart phone command. At that moment, you should quickly hold down the volume up key and power button of your phone. Enter this command:
fastboot reboot
Then, hold down the power button with quick boost and turn on twrp.
6- Install Magisk-v20.4.zip in twrp.
Then restart the phone. After the phone reboots, check if Magisk is installed. Once you see it installed, reboot the phone in recovery mode.
7- Install SHRP_v2.2_olive.zip then reboot recovery.
8- Now find the wipe button and tap it. Then press the format data and confirm by typing yes.
9- Then tap wipe again and click on the wipe button at the bottom right.
10- Tap the wipe again and tap on advanced wipe. Select the Dalvik, data, cache, system partitions and reset them.
11- Now return to the main menu screen and tap flash. Select your SD card in the lower right section and tap the PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img file. Then select it as system image and install it.
12- Return to the main menu and come to the flash section and install the file Permissiver_v5.zip.
13- Then go back to the flash section and install the Certification_Patch.zip file.
14- Return to the main menu, tap wipe and complete the wipe from the button on the bottom right.
15- Reboot the system. Your device will either boot in fastboot mode or be bootloop. (If you see it open normally and no problems occur, you can skip step 18.)
16- Go to fastboot mode.
17- Connect the phone to the computer and open the adb folder on cmd. Type:
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
The phone will reboot and turn on. Please set up the phone and turn USB debugging back on.
18- After doing setup and enabling usb debugging, reboot to recovery mode and install magisk.zip. Then reboot the phone.
19- Install build prop editor(https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en&pli=1) and root browser(https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en) from the Play Store.
20- Open root browser and allow root access then go to your SD card and find treble-overlay-xiaomi-redmi8.apk
21- Copy to treble-overlay-xiaomi-redmi8.apk on Root Directory/system/overlay/ folder.
22- Select treble-overlay-xiaomi-redmi8.apk file on overlay folder and tap the three dots in the top right and tap the properties.
23- Click on the Permissions at the top bar.
24- Select like this photo (link: https://lh3.googleusercontent.com/p...VrSOGT_V9Q2bzgy5IuE9nIfPslILJ1Vz=w429-h904-no ) and click apply then reboot system.
25- Open the build prop editor and allow root access. then tap the 3 dots in the upper right and tap new.
name= persist.camera.HAL3.enabled
value= 1
Set it to and save it. Restart the system.
26- Go to the dialer and dial *#*#4636#*#*. Tap Phone information and set "set preffered network type: LTE only." Then reboot system.
27- Finally, if you want to fix the appearance of the screen notch go to
developer settings >> display cutout and select corner cutout.
That was it. Please note that I am not a developer, so I cannot resolve any errors. I believe that if you apply them like me, you won't have a problem. I will be waiting for your comments. Have a nice day.

I´ll give it a try in my wife´s redmi 8, cus I had tried to flash a bunch of roms in that device and I had not success. Thanks

dngr.fun said:
I´ll give it a try in my wife´s redmi 8, cus I had tried to flash a bunch of roms in that device and I had not success. Thanks
Click to expand...
Click to collapse
You're welcome. If you encounter any problems, please let me know. If you follow what I wrote under normal conditions step by step, you won't have a problem.

Query before flashing
Hello Boss,
on checking the system by "Treble Check" app, it is showing that it is A-type System partition. And the ROM you suggested is AB type. Is there any thing i should worry about before flashing.
I am currently using Lineage OS (unofficial), and following functions doesn't work on it.
Finger print
VOLTE
Radio
face unlock
What about this ROM functionality.

hrwt20 said:
Hello Boss,
on checking the system by "Treble Check" app, it is showing that it is A-type System partition. And the ROM you suggested is AB type. Is there any thing i should worry about before flashing.
I am currently using Lineage OS (unofficial), and following functions doesn't work on it.
Finger print
VOLTE
Radio
face unlock
What about this ROM functionality.
Click to expand...
Click to collapse
At first I tried installing A-only on my device but it didn't work. It worked when I installed A / B. So please try A / B GSI. Because the device you have is probably A / B, not A-Only.
Finger print is working and face unlock is not have in Pixel Experience ROM.
VOLTE and Radio is not working bro.
I will list all the features that work by edit the post today or tommorrow bro

Certification_patch.zip
Whats the use for certification_patch.zip file?
Does it fixes the certification status in google play store?
Also, Can this file be used in any othe gsi too?

coolboyforeva said:
Whats the use for certification_patch.zip file?
Does it fixes the certification status in google play store?
Also, Can this file be used in any othe gsi too?
Click to expand...
Click to collapse
This file exists to integrate the model of the device into rom. I don't know much about google play and you can also install this and permissiver_v5 with other gsi roms. These only for Redmi 8.

hrwt20 said:
Hello Boss,
on checking the system by "Treble Check" app, it is showing that it is A-type System partition. And the ROM you suggested is AB type. Is there any thing i should worry about before flashing.
I am currently using Lineage OS (unofficial), and following functions doesn't work on it.
Finger print
VOLTE
Radio
face unlock
What about this ROM functionality.
Click to expand...
Click to collapse
Before system-as-root was used only on A/B devices but now all devices that ship with Android 9 must use system-as-root. Because of this reason you need to flash A/B roms on A-Only on these devices. As you can see from this page's device list, Redmi 8's image type is A/B so you need to flash an A/B image: https://github.com/phhusson/treble_experimentations/wiki

Does the sensor work? I tried other gsi and custom roms and sensors like accelerometer doesnt work..

Abdul Aziz Shakib said:
Does the sensor work? I tried other gsi and custom roms and sensors like accelerometer doesnt work..
Click to expand...
Click to collapse
All sensors working

i tried it and the sensors didn't work. i needed to flash stock rom and then pixel rom over the stock rom to get it work. seems logical, had no issue so far except the camcorder. when i record a video, lets say i recorded a video for 10 second. but when i play the video, it becomes 1hour video and the sound doesn't sync with the video. video stays frozen the whole time and plays normally at the last few seconds. i tried other gsi and had the same issue. is something wrong? any known solution? are you facing the same problem? if not, then which camera app you are using? thanks in advance because pixel experience is working now after following ur steps

Yes, there is a problem in this regard. Unfortunately, I could not solve this problem. I usually use Instagram cam for video. You can try bro

Abdul Aziz Shakib said:
i tried it and the sensors didn't work. i needed to flash stock rom and then pixel rom over the stock rom to get it work. seems logical, had no issue so far except the camcorder. when i record a video, lets say i recorded a video for 10 second. but when i play the video, it becomes 1hour video and the sound doesn't sync with the video. video stays frozen the whole time and plays normally at the last few seconds. i tried other gsi and had the same issue. is something wrong? any known solution? are you facing the same problem? if not, then which camera app you are using? thanks in advance because pixel experience is working now after following ur steps
Click to expand...
Click to collapse
I use havocOs gsi. It has same problem. Solution:
1. record a video.
2. do not close camera app.
3. open video from the camera app not from gallery.
4. play the video once.
if that plays then you can open that same video from any app.
try that, might work.

kouseralamin said:
I use havocOs gsi. It has same problem. Solution:
1. record a video.
2. do not close camera app.
3. open video from the camera app not from gallery.
4. play the video once.
if that plays then you can open that same video from any app.
try that, might work.
Click to expand...
Click to collapse
it works sometimes but not always.. Currently I am using Havoc OS and it doesn't have a gallery app. So I downloaded "Gallery Go" from playstore and when I try to open the video from the camera app, it opens with gallery go app.
to be noted, i have added some commands in build.prop..
media.camera.ts.monotonic=0
debug.stagefright.ccodec=0
persist.camera.HAL3.enabled=1
i don't know what these do but these commands were mentioned somewhere to enable camera2api..
am i missing something?

kouseralamin said:
I use havocOs gsi. It has same problem. Solution:
1. record a video.
2. do not close camera app.
3. open video from the camera app not from gallery.
4. play the video once.
if that plays then you can open that same video from any app.
try that, might work.
Click to expand...
Click to collapse
try this for video recording , go to phh treble settings, go to Misc, go to camera force timestamp, clock boottime

Redmi 4A abdal said:
try this for video recording , go to phh treble settings, go to Misc, go to camera force timestamp, clock boottime
Click to expand...
Click to collapse
Thanks, I tried it in the havocOs and it is fully ok now.

Hello, is Bluetooth audio working?

Is there an option for internet speed indicator on this rom?

IS TBH
sessionid0 said:
First of all, the download link of all the files required for this "ROM" is taken from the "xda developers forum" posts.
I was constantly experimenting with GSI roms for Redmi 8. I was able to install the Pixel ROM on Redmi 8. I don't think you will have a problem if you follow the steps I shared with you one by one.
I do not take responsibility for the ROM. RESPONSIBILITY IS ENTIRELY YOURS.
Not working
-Face unlock
-Radio
-VoLTE
(You need to make a setting for the camera, notch, LTE Mobile Network and auto-brightness. I told you how to make the settings.)
NOTE: A computer is required to make this ROM setup. It must also be installed in ADB on your computer.
Note: You can install this ROM Google Camera as apk. Unfortunately, there are no features such as Portrait, night mode in the original camera application of the device. However, you can use it if you install it as an apk.
Please download that files:
Download - Pixel Experience ROM GSI file
Download --- Sky Hawk Recovery file
Download - Permissiver V5
Download -Certification Patch for Redmi 8
Download -Treble overlay for Redmi 8
Download --- Lastest Magisk-v20.4
Here -Get the TWRP Official for Redmi 8
Download - vbmeta.img
Note: Please charge your phone at least 60%
First, take the necessary backups as your phone will be completely reset.
1- Unlock your bootloader. For unlocking follow this: http://en.miui.com/unlock/
2- Copy all the files to your SD Card (PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img, SHRP_v2.2.zip, Permissiver_v5.zip, Certification_Patch.zip, Magisk-v20.4.zip, treble-overlay-xiaomi-redmi8.apk)
3-Enable USB debugging. Connect the phone your computer Then copy the twrp.img and vbmeta.img files to the adb folder.
Note: If the name of your twrp file is not twrp.img, please set its name to twrp.img.
4- Go to your computer, open adb folder in cmd, write that:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
5- Now we will go to the restart phone command. At that moment, you should quickly hold down the volume up key and power button of your phone. Enter this command:
fastboot reboot
Then, hold down the power button with quick boost and turn on twrp.
6- Install Magisk-v20.4.zip in twrp.
Then restart the phone. After the phone reboots, check if Magisk is installed. Once you see it installed, reboot the phone in recovery mode.
7- Install SHRP_v2.2_olive.zip then reboot recovery.
8- Now find the wipe button and tap it. Then press the format data and confirm by typing yes.
9- Then tap wipe again and click on the wipe button at the bottom right.
10- Tap the wipe again and tap on advanced wipe. Select the Dalvik, data, cache, system partitions and reset them.
11- Now return to the main menu screen and tap flash. Select your SD card in the lower right section and tap the PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img file. Then select it as system image and install it.
12- Return to the main menu and come to the flash section and install the file Permissiver_v5.zip.
13- Then go back to the flash section and install the Certification_Patch.zip file.
14- Return to the main menu, tap wipe and complete the wipe from the button on the bottom right.
15- Reboot the system. Your device will either boot in fastboot mode or be bootloop. (If you see it open normally and no problems occur, you can skip step 18.)
16- Go to fastboot mode.
17- Connect the phone to the computer and open the adb folder on cmd. Type:
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
The phone will reboot and turn on. Please set up the phone and turn USB debugging back on.
18- After doing setup and enabling usb debugging, reboot to recovery mode and install magisk.zip. Then reboot the phone.
19- Install build prop editor(https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en&pli=1) and root browser(https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en) from the Play Store.
20- Open root browser and allow root access then go to your SD card and find treble-overlay-xiaomi-redmi8.apk
21- Copy to treble-overlay-xiaomi-redmi8.apk on Root Directory/system/overlay/ folder.
22- Select treble-overlay-xiaomi-redmi8.apk file on overlay folder and tap the three dots in the top right and tap the properties.
23- Click on the Permissions at the top bar.
24- Select like this photo (link: https://lh3.googleusercontent.com/p...VrSOGT_V9Q2bzgy5IuE9nIfPslILJ1Vz=w429-h904-no ) and click apply then reboot system.
25- Open the build prop editor and allow root access. then tap the 3 dots in the upper right and tap new.
name= persist.camera.HAL3.enabled
value= 1
Set it to and save it. Restart the system.
26- Go to the dialer and dial *#*#4636#*#*. Tap Phone information and set "set preffered network type: LTE only." Then reboot system.
27- Finally, if you want to fix the appearance of the screen notch go to
developer settings >> display cutout and select corner cutout.
That was it. Please note that I am not a developer, so I cannot resolve any errors. I believe that if you apply them like me, you won't have a problem. I will be waiting for your comments. Have a nice day.
Click to expand...
Click to collapse
Is there a way to flash it without SD card???my adb sideloader also doesnt open

I will try it tank you

[GUIDE][SM-T290/SM-T290N] Samsung Galaxy Tab A 8.0 (2019) - How to Install LineageOS 18.1 (GSI) + Gapps

Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
Some Things To Note
Below I'll list the software/firmware I used in this process. You don't necessarily need to follow this exactly but I don't see any reason not to. The end result is a working install of LineageOS with GApps so if that's what you want I would just follow along step-by-step. ALSO I'm writing this from memory so if I make a mistake please let me know and I'll try and correct it.
Click to expand...
Click to collapse
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
If you don't see this setting try connecting to wifi, changing your date and time to around two months prior (I set mine to back to May 2021 since the firmware I was using was set in July 2021), then go back to your developer settings and switch them off and back on again. You should now see the OEM Unlock option.
Click to expand...
Click to collapse
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Now, a lot of people run into a problem when trying to install Gapps which is your device complaining about no more available space in the system partition. If this is the case, go back to Wipe and select Advanced Wipe. Select your system partition and then select Change or Repair Partition. Once you're here you should see the size and available space of your partition. You'll want to hit Resize Partition and let it do it's thing. To confirm it worked, go back to Wipe->Advanced Wipe->Select System->Change or Repair Partition and your available space should be much larger now. Now just attempt to install MindTheGapps again.
Click to expand...
Click to collapse
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!

How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS

kkdamion said:
How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS
Click to expand...
Click to collapse
It runs surprisingly well! Much better than stock. There’s virtually no input lag and the battery life is also very solid on lineage.
Where i run into some lag is when trying to use apps that have embedded video in them. For whatever reason the T290 cannot handle video very well at all.
So yeah I would definitely recommend trying it, it’ll really breathe new life into that tablet

i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app

kkdamion said:
i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app
Click to expand...
Click to collapse
Glad it worked out for you! Let me know if you have any more questions and I'd be happy to help.

Hi! is this applicable also for SM-T295?

for those trying to figure out the Google Play Certified page with the adb command
Code:
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"'
do : adb shell
first then paste in :
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"
and it shouldn't give you the error

i must say. linageos on my sm-t290 is really nice
its fast and smooth way much better then stock fw
i would reccomend anyone with a t290/t295 to install this GSI

Im into a bootloop right now after a few fails with installing Lineage on my SM-T290..
Seems like i cant install any rom? not sure how to fix this issue, can anyone point me in the right direction?
Im able to get into TWRP and download mode. but cant install any rom?

thepalek1ng said:
Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!
Click to expand...
Click to collapse
bro, I have a problem, my tablet is in a bootloop and I don't know what to do, try with other custom roms but it's the same, what do I have to do so that when I install a custom room it doesn't give me that error?

Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)

V0latyle said:
Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)
Click to expand...
Click to collapse
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.

Do you have any video to teach better ???

HyruleanKnight said:
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.
Click to expand...
Click to collapse
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am

V0latyle said:
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am
Click to expand...
Click to collapse
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!

Just Mike said:
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!
Click to expand...
Click to collapse
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?

V0latyle said:
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?
Click to expand...
Click to collapse
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.

Just Mike said:
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.
Click to expand...
Click to collapse
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?

V0latyle said:
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?
Click to expand...
Click to collapse
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?

Just Mike said:
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?
Click to expand...
Click to collapse
Trying to get back into TWRP, just a sec...
-arm64_bgS.img
Flashing the vndklite one now to see if it works
If I can get this working, I plan on using a bgN flavor so I can just install Magisk, since I don't use SuperSU
Edit: vndklite is bootlooping too

Development [ROM][13][barbet] PixelExperience [AOSP][OFFICIAL]&[UNOFFICIAL]

What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Downloads:
OFFICIAL:
https://download.pixelexperience.org/barbet
UNOFFICIAL:
Standard
PixelExperience_barbet-13.0-20230109-0542-UNOFFICIAL.zip
drive.google.com
Plus ver.
PixelExperience_Plus_barbet-13.0-20230109-0353-UNOFFICIAL.zip
drive.google.com
Stay tuned
Our Official Telegram channel
Our blog
Install PixelExperience on barbetWARNING: I copy and pasted thes instuctions. Please go to the offical guide for your device Barbet https://wiki.pixelexperience.org/devices/barbet/install/
WARNING: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
warning
WARNING: Before following these instructions please ensure that the device is on the latest Android 13 firmware.
This is not necessarily the newest available version! Please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
Flashing the vendor boot partitionwarning
WARNING: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.
Download this vendor_boot.img file.
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power.
Flash a the downloaded images to your device by typing (replace <vendor_boot> with the actual filename!):
fastboot flash vendor_boot <vendor_boot>.img
Unlocking the bootloaderinfo_outline
NOTE: The steps below only need to be run once per device.
warning
WARNING: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from PixelExperience once installed.
Enable OEM unlock in the Developer options under device Settings, if present.
Connect the device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
Now type the following command to unlock the bootloader:
fastboot flashing unlock
info_outline
NOTE: At this point the device may display on-screen prompts which will require interaction to continue the process of unlocking the bootloader. Please take whatever actions the device asks you to to proceed.
If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing the vendor boot partitionwarning
WARNING: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.
Download this vendor_boot.img file.
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power.
Flash a the downloaded images to your device by typing (replace <vendor_boot> with the actual filename!):
fastboot flash vendor_boot <vendor_boot>.img
Temporarily booting a custom recovery using fastboot
Download the PixelExperience Recovery. Simply download the latest recovery file.
Connect your device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable (preferably use a USB Type-A 2.0 one or a USB hub) and port!
check
TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ... , fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Temporarily flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
fastboot flash boot <recovery_filename>.img
info_outline
NOTE: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.
Installing PixelExperience from recovery
Download the PixelExperience installation package that you would like to install or build the package yourself.
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Down + Power. Then use the menu to select Recovery Mode.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the PixelExperience .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
TIP: Normally, adb will report Total xfer: 1.00x, but in some cases, even if adb: failed to read command: Success/No error. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.
info_outline
NOTE: The first boot usually takes no longer than 15 minutes, depending on the device. If it takes longer, you may have missed a step, otherwise feel free to get assistance
check
TIP: If the installation process reports the message "(~47%) adb: failed to read the command: No error", do not worry, the process was completed successfully and you can restart the device.
I am not connected to Pixel Experience rom in any way.
Just posting to share.
I am not providing help and am not responsible for anything that happens.
Help each other!
If a P.E. maintainer wants this down. Please do so.

RESERVED:

Jan. Changelog:
January and December (2022) security patch
Google Apps updated
Fixed battery drain and lag spike caused by Pixel Launcher (Need to uninstall previous updates of Android System Intelligence or do a clean flash if the issue persists)
Minor issues fixed

Plus Version:
13 Plus version is here!First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Clean flash is not required if coming from normal version
Click to expand...
Click to collapse
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There is more stuff one can unearth – this list was just a start off for the long feature list we have.

Just to be clear. Not a maintainer. Not affiliated with PixelExperience. Not Responsible for your choices!
Just creating a thread to spread the word my friends

Thanks for this, exactly what I've been looking for (stock ROM with volume button playback control, let's go!)
Flashed using instructions (factory reset, sideload). No issues, things seem to be working smoothly. Will observe battery life over the next few days but not expecting much difference either way.

Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?

ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
No. Not that i know of. Give thanks to the PE team.

rhewins2268 said:
No. Not that i know of. Give thanks to the PE team.
Click to expand...
Click to collapse
Who is know?

ALWA7SH6 said:
Who is know?
Click to expand...
Click to collapse
I am just saying that i don't know of any Official PixelExperience Android 11 (Plus edition)

rhewins2268 said:
I am just saying that i don't know of any Official PixelExperience Android 11 (Plus edition)
Click to expand...
Click to collapse
TY

ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
there is none, pixel experience crew stopped with support for android 11, all projects moved to android 12

ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
you might be able to build your own rom and switch to the branch eleven-plus, but not sure if it would actually work or not. also i am sure it would be outdated for kernel security patches and other updates. build time on my dual cpu e5-2667v2 (32 cores total), 160gb of mem, WD SN750 1tb nvme and 1gbp internet running debian bookwork with tkg kernel is about 2hrs from start to finish. i just build a twelve-plus yesterday and i was surprised that everything worked out of the box using adb sideload on the unoffical twrp. the experience recovery actually installed and worked this time. rom is very smooth or i should say smoother than it was. a few new features were added. some were moved to a different spots. magisk install was easy with the working experience recovery allowing adb sideload to flash magisk. i might actually stick with this rom for a while.

rchris494 said:
you might be able to build your own rom and switch to the branch eleven-plus, but not sure if it would actually work or not. also i am sure it would be outdated for kernel security patches and other updates. build time on my dual cpu e5-2667v2 (32 cores total), 160gb of mem, WD SN750 1tb nvme and 1gbp internet running debian bookwork with tkg kernel is about 2hrs from start to finish. i just build a twelve-plus yesterday and i was surprised that everything worked out of the box using adb sideload on the unoffical twrp. the experience recovery actually installed and worked this time. rom is very smooth or i should say smoother than it was. a few new features were added. some were moved to a different spots. magisk install was easy with the working experience recovery allowing adb sideload to flash magisk. i might actually stick with this rom for a while.
Click to expand...
Click to collapse
Can you share it ty?

ALWA7SH6 said:
Can you share it ty?
Click to expand...
Click to collapse
yeah.
steps
1. unlocked bootloader
2. flashed fresh factory image (12.1.0 (SP2A.220405.003, Apr 2022)) from google dev site (check marked full wipe & force flash all partitions)
3. waited for phone to fully boot up. did offline setup skipping everything until i hit home screen
4. went to settings enabled developer mode & usb debugging
5. rebooted to bootloader (adb reboot bootloder)
6. toggled bootloader until i seen recovery then booted into stock reocovery
7. power + vol up for 3 sec then release you should get the stock recovery menu. do a factory reset / wipe data
8. reboot back to bootloader in the menu options of stock recovery
9. boot unoffical trwp from nijel8 (fastboot boot twrp-3.6.0_11-0-barbet.img)
10. in twrp go to advanced and adb sideload. set twrp to adb sideload
11. download https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (sha-256 checksum) or https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (untouched rom direct from pixel experience) if you don't care about checksum you can skip it.
12. adb sideload the rom (PixelExperience_Plus_barbet-12.1-20220423-2211-UNOFFICIAL.zip) note it fails at 47% and you might see a bunch of red warning on twrp. just ignore them and reboot the phone. pixel experience is now loaded on the phone. i had to do the whole process twice because twrp messed up the first time due to it not being officially up to 12 and sideload sometimes being flaky.
13. after setup was done i enabled debugging again and booted to bootloader, then recovery mode. pixel experience recovery should now be loaded. its touch screen or volume controlled. select adb sideload and side load magisk 24.3.apk or you can rename it to zip. doesnt matter. reboot phone. check app drawer. magisk will be there. if not give it a second it will pop up. tap the app to download full version. enjoy rooted & pixel experience
the rom is compiled directly from pixel experience source. i do not mod or edit anything. i just let my computer sweat at 100% usage for 2hrs and hope like hell the rom works.
i can try an eleven-plus build if you want but i doubt it will work and would probably end up bricking your phone.
this is the process i used. i take not responsibility if you brick your phone.
usually your brick is a soft brick holding power + vol up + vol down for 30sec will force restart your phone. then power off then power + vol dow to get back to bootloader so you can work with it again (factory flash or whatever)
android base is 12.1.0_r4

rchris494 said:
yeah.
steps
1. unlocked bootloader
2. flashed fresh factory image (12.1.0 (SP2A.220405.003, Apr 2022)) from google dev site (check marked full wipe & force flash all partitions)
3. waited for phone to fully boot up. did offline setup skipping everything until i hit home screen
4. went to settings enabled developer mode & usb debugging
5. rebooted to bootloader (adb reboot bootloder)
6. toggled bootloader until i seen recovery then booted into stock reocovery
7. power + vol up for 3 sec then release you should get the stock recovery menu. do a factory reset / wipe data
8. reboot back to bootloader in the menu options of stock recovery
9. boot unoffical trwp from nijel8 (fastboot boot twrp-3.6.0_11-0-barbet.img)
10. in twrp go to advanced and adb sideload. set twrp to adb sideload
11. download https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (sha-256 checksum) or https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (untouched rom direct from pixel experience) if you don't care about checksum you can skip it.
12. adb sideload the rom (PixelExperience_Plus_barbet-12.1-20220423-2211-UNOFFICIAL.zip) note it fails at 47% and you might see a bunch of red warning on twrp. just ignore them and reboot the phone. pixel experience is now loaded on the phone. i had to do the whole process twice because twrp messed up the first time due to it not being officially up to 12 and sideload sometimes being flaky.
13. after setup was done i enabled debugging again and booted to bootloader, then recovery mode. pixel experience recovery should now be loaded. its touch screen or volume controlled. select adb sideload and side load magisk 24.3.apk or you can rename it to zip. doesnt matter. reboot phone. check app drawer. magisk will be there. if not give it a second it will pop up. tap the app to download full version. enjoy rooted & pixel experience
the rom is compiled directly from pixel experience source. i do not mod or edit anything. i just let my computer sweat at 100% usage for 2hrs and hope like hell the rom works.
i can try an eleven-plus build if you want but i doubt it will work and would probably end up bricking your phone.
this is the process i used. i take not responsibility if you brick your phone.
usually your brick is a soft brick holding power + vol up + vol down for 30sec will force restart your phone. then power off then power + vol dow to get back to bootloader so you can work with it again (factory flash or whatever)
android base is 12.1.0_r4
View attachment 5597359
Click to expand...
Click to collapse
(a few new features were added)
Like what?

ALWA7SH6 said:
(a few new features were added)
Like what?
Click to expand...
Click to collapse
rhewins2268 said:
Plus Version:
April Update: 12 Plus version is here!First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There are more stuff one can unearth – this list was just a start off for the long feature list we have.
Click to expand...
Click to collapse

How is fingerprint sensor working, does it also have lag if AOD is not enabled? March update introduced 2 seconds delay after FP sensor registers your finger before it shows you your home screen. If you use AOD that issue is not present.

rhewins2268 said:
Plus Version:
April Update: 12 Plus version is here!First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There are more stuff one can unearth – this list was just a start off for the long feature list we have.
Click to expand...
Click to collapse
I noticed that sometimes the scanner simply refuses to understand the finger, I also noticed that when AOD is on, if you put the phone with the screen down, it does not go out, but if you turn up the screen and close the proximity sensor, it goes out

fackstrot said:
I noticed that sometimes the scanner simply refuses to understand the finger, I also noticed that when AOD is on, if you put the phone with the screen down, it does not go out, but if you turn up the screen and close the proximity sensor, it goes out
Click to expand...
Click to collapse
Please open bug on pixel experience GitHub, since main developer is not following this thread and PE community usually only fixes issues reported on official page.
Issues · PixelExperience/android-issues
Issue tracker. Contribute to PixelExperience/android-issues development by creating an account on GitHub.
github.com

[ROM][UNOFFICIAL][2022 MODEL] LineageOS 20.0 for Galaxy Tab S6 Lite 2022 (Qualcomm)

{
"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"
}
Disclaimer:
I'm not responsible of any damage made to your device by installing this ROM
Following the installation process will trip Knox, thus your device warranty may be void.
Click to expand...
Click to collapse
What's working?
- Audio
- Bluetooth
- LTE
- Display
- WiFi
- Charging
- Location
- Encryption
- Camera
- S-pen
- Enforcing SELinux
What's not working?
- You tell me
Installation instructions
Spoiler: Installation instructions
Installation requirements
- A computer
- ADB installed on the computer, you can find a guide here
- Odin (v3.14.1 is verified to work fine), you can find it here
- A decent battery level on the device
Step 1 - Unlocking the bootloader
You may skip this section if you have already unlocked your device
- Enable developer options
- In developer options, toggle the "Allow OEM unlocking" setting
- Reboot into download mode following the instructions below
- Once into download, long press the volume up button and follow the instructions on the screen
- After the bootloader is unlocked, your data will be erased, so make sure to back it up first.
- Now, once the system has finished booting, you MUST connect to a WiFi network, enable developer options again, and make sure that the OEM unlocking toggle is on and grayed out. If you do not see the toggle on the developer settings, close the settings and try again a few times.
- Once you see the toggle greyed out, all is set.
Step 2 - Installing the LineageOS recovery
In order to flash the ROM, you need a custom recovery, which you can find on the downloads section.
For installing the recovery:
- Boot into download mode as described below
- Press the volume up button a single time to fully enter download mode
- Connect your device to your computer
- Once you are in download mode, open Odin and make sure that it detects your device
- Go to options on Odin, and disable auto-reboot (DO NOT ENABLE ANY OPTIONS OTHER THAN F. Reset Time and Auto-Reboot)
- Download the vbmeta.tar file from the downloads section
- Select on the "Ap" button the vbmeta.tar file and then click "Start"
- Download the recovery.tar file from the downloads section
- Select on the "Ap" button the recovery.tar file and then click "Start"
If Odin gets stuck (specially when flashing recovery.tar), you might try the following:
- After you flash vbmeta, reboot into download again, and directly flash the recovery (once you have flashed the vbmeta once you shouldn't need to flash it again)
- Try a different PC or USB cable
- Try a different version of Odin
Click to expand...
Click to collapse
- Once the flashing completes, power off your device by pressing power + volume down, and after the screen turns off, quickly press the key combination for booting into recovery
- If everything went fine, you should be now on the LineageOS recovery
Warning: if you boot into the OneUI again, it will overwrite the custom recovery and you'll need to install it again!
Step 3 - Installing the ROM
- Download the ROM from the downloads section (make sure you download the .zip file and not the .sha256sum file)
- Once in recovery, go to the "Apply update" section, and click "ADB sideload"
- Connect your device to the computer, and sideload the update with adb sideload path/to/file
An example of the command on Windows can be adb sideload C:\Users\myuser\Downloads\lineage-20.0-20230223-unofficial-gta4xlveu.zip
Click to expand...
Click to collapse
- Your device should start verifying and installing the update
- After the installation has finished, you need to format the data partition (Factory reset -> Format data/factory reset)
- Now, click "Reboot to system"
- If everything went correctly, you should be booting LineageOS
How to boot into recovery/download modes:
Spoiler: Booting into recovery/download
Download
- For booting into download, you will have to press at the same time the power and the two volume buttons until the "Download" screen shows up.
- If you want to boot into download with the device powered on, you have to press the reboot option and right after that, press the key combination as mentioned above.
Recovery
- First, make sure to connect the device to a computer, otherwise the tablet won't allow you to boot into recovery (it's a Samsung restriction).
- For booting into recovery, just press the power and volume up buttons. Once the Samsung logo / bootloader unlocked warning has appeared, you can release the buttons and press the power button to skip the warning screen.
- Just like with the download mode, if you want to boot into recovery with the device powered on you just have to press the keys right after pressing the reboot button.
DownloadsAll files (ROM, recovery and vbmeta) are available at https://files.danielml.dev/android/gta4xlveu/.
Both models (WiFi and LTE) are compatible with the same ROM zip (gta4xlveu).
Help and supportJoin the Telegram group for getting support
Other details:
Kernel source: https://github.com/gta4xlve-dev/android_kernel_samsung_gta4xlve
Device source: https://github.com/gta4xlve-dev/android_device_samsung_gta4xlveu

Reserved

Thank you very much, i will test it next week.

Testing out the new ROM, glad to see one for the Qualcomm 2022 version.
Battery stats works
Camera works
Using lawnchair 2 and it works! Pixel keeps crashing (?)
Thanks!

K9droid56 said:
Testing out the new ROM, glad to see one for the Qualcomm 2022 version.
Battery stats works
Camera works
Using lawnchair 2 and it works! Pixel keeps crashing (?)
Thanks!
Click to expand...
Click to collapse
Glad to see that you liked the ROM.
Here Pixel launcher works, not sure why it doesn't there.
Anyways, I'll remove GApps by default on future builds so the Pixel launcher won't be present. (Of course, you'll be able to install a custom GApps package).

Thank you! Also started to test now. I disabled most of google app from the start and went fdroid/aurora way (waiting with anticipation for no google version). Nothing crashed yet.

btw, how to root this image? is patching boot.img and replacing it in zip and then flashing as above enough, or is there any changes required for vbmeta?

bugit said:
btw, how to root this image? is patching boot.img and replacing it in zip and then flashing as above enough, or is there any changes required for vbmeta?
Click to expand...
Click to collapse
Well, I didn't try, but just flashing Magisk *should* be enough.

daniml3 said:
Well, I didn't try, but just flashing Magisk *should* be enough
Click to expand...
Click to collapse
unfortunately this method does not work: during sideload it fails with `Unable to repack boot image` and recovery logs are somehow empty, but still managed to boots after this error
i will try with patching boot.img when i will have more time

ok, i managed to flash image with patched boot.img (extract zip, uload boot.img to device, patch with magisk, download patched boot.img, remake zip image),
but just flashing patched image from recovery made my existing system unbootable
and i had to reflash stock firmware and then repeat flashing steps from scratch
(flash vbmeta/recovery, and then flash patched image),
with this the device is booting and root is working
notes:
- the unbootable state from above was device going into black screen just after samsung logo, with no hints of activity (10 min was max i waited)
- only pressing all tree keys (power, volume up and down) made it reboot with about one second of turn off state (so one can't actually power off the device, it just boots up again into black screen after logo)
- after reboot i was not able to enter recovery or download mode by just pressing known combinations of buttons, and the only way to enter download mode was: during this 1 second power off state to press volume up and down keys and connect usb cable (spend some time finding this solution)
- during flashings after uploading vbmeta i could not flash recovery right after vbmeta (it gets stuck during upload) and i had to reboot again into download mode and then flash recovery (this happened both during my first try to install this image, and with the patched image)
- for some reason in this image i have two sets of navigation buttons at the bottom of the screen (the triangle, circle and square buttons), one is standard android set and one compressed to the right side of nav.bar; stopping pixel launcher removes the compressed one, but the square button (task switching) stops working
- after installing patched image i also noticed (in hindsight) that actually during first install the scroll was very choppy (and the system was kind of slow), but in second install this problem went away

Thanks a lot for the ROM. The following steps for rooting lead to success for me:
1. flashing according to the instructions as described by daniml3.
2. copy Magisk 25.2 to the external SDCARD and rename to .zip
3. reboot in recovery
4. factory reset -> format data/factory reset
4. do not boot, but install Magisk from tablet via ADB from SDCARD
5. reboot
6. rename magisk to .apk again and install the app
7. set up Magisk
8. after reboot be sure to complete ANDROID setup
It rocks!
The navigation buttons are also duplicated for me.
I hope I could help.
I wish a LineageOS without Google.

Thanks everyone for the feedback! There are a few notes:
- I'll release a version without Google Apps as soon as possible (most likely this weekend).
- The lag when booting is caused due to some overlay issue, I still have to look into it, but as it doesn't affect much to the functionality after a few seconds its not a "priority".
- The duplicated navigation buttons are actually an issue from the Google Apps (maybe the Pixel Launcher?). This will be fixed with the Google app-less version of the ROM. If you switch to gesture navigation this issue dissapears.

Is there a possibility for SM-P619 LTE version?

Razor64 said:
Is there a possibility for SM-P619 LTE version?
Click to expand...
Click to collapse
As I said on the post, if you have the LTE model, and want to try a build, just let me know (preferably by Telegram).

Uninstalling the pixel launcher via adb removes the extra icons.
Small lag at start-up but other wise a smooth-running rom.
Thanks!

Today (if everything goes as planned) I'll publish a new update for the WiFi-only model, including:
- Enforcing SELinux
- Removed GMS by default (you can install them as a separate package, personally BitGapps worked perfectly)
- Fixed some background services crashing
This will probably be the last update in a (few) week(s), as I'm working on an source-built-vendor device tree, which may take some time.
I'm also working on a build for the LTE variant, which will be published as soon as I verify that it works correctly.

At the moment I am not at home. After my short vacation I am looking forward to try it at the end of the week.
Many thanks for your work.

A new update for the SM-P613 (gta4xlvewifi) was published just now with the following changes:
- Enforcing SELinux
- Removed GMS by default (you can install them as a separate package, personally BitGapps worked perfectly)
- Fixed some background services crashing
Download it at https://sourceforge.net/projects/gta4xlve-dev/files/gta4xlvewifi/lineage-20.0/
Warning: If you used GMS, you'll need to manually install them (I use BitGapps and they work correctly).

Latest update runs really smooth with bitgapps. Lawnchair works with no problems. Thanks again for this ROM!

Bit of a stretch to ask, but would it be possible for the build to identify itself as a tablet, rather than a phone? And the possibility of defaulting the orientation to landscape? (90 degree rotation as default rather than 0)

Development [ROM][13][UNOFFICIAL] LineageOS 20 for Xiaomi 12 Pro

{
"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.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
To find out more about LineageOS visit the official Website.
All the source code for LineageOS is available in the LineageOS Github organization. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation
Warning: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
LineageOS is provided as-is with no warranty. While we attempt to verify everything works you are installing this at your own risk!
Warning: Before following these instructions please ensure that the device is currently using Android 13 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 13, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Unlocking the bootloaderNote: The steps below only need to be run once per device. They require a machine running Windows 7 or newer.
Warning: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed.
Tip: It is highly recommended to have the latest official MIUI stable package installed on the device, before proceeding with unlock.
Create a Mi account on Xiaomi’s website. Beware that one account is only allowed to unlock one unique device every 30 days.
Add a phone number to your Mi account.
Insert a SIM into your phone.
Enable developer options in Settings > About Phone by repeatedly tapping MIUI Version.
Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status.
Download the Mi Unlock app (Windows is required to run the app).
Run the Mi Unlock app and follow the instructions provided by the app. It may tell you that you have to wait up to 30 days. If it does so, please wait the quoted amount of time before continuing to the next step!
After device and Mi account are successfully verified, the bootloader should be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing additional partitionsWarning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from the download section below.
boot.img
dtbo.img
vendor_boot.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash boot <boot>.img
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
Booting a custom recovery using fastboot
Download Lineage Recovery from the download section below. Simply download the latest recovery file, named recovery.img.
Important: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!
Connect your device to your PC via USB if it isn’t already.
If your device isn’t already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable (preferably use a USB Type-A 2.0 one or a USB hub) and port!
Tip: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to recovery__a /recovery__b rather than recovery_a / recovery_b if you try to flash recovery. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to recovery__a, you must flash to recovery_a.
Now reboot into recovery to verify the installation.
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Note: If your recovery does not show the LineageOS logo, you accidentally booted into the wrong recovery. Please start at the top of this section!
Installing LineageOS from recovery
Download the LineageOS installation package from the download section below that you would like to install or build the package yourself.
(Optionally): If you want to install an application package add-on such as Google Apps (use the arm64 architecture), please read and follow the instructions on Google Apps page
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the main menu.
Sideload the LineageOS .zip package but do not reboot before you read/followed the rest of the instructions!
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Tip: Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
All set!Once you have installed everything successfully, you can now reboot your device into the OS for the first time!
Click the back arrow in the top left of the screen, then “Reboot system now”.
Note: The first boot usually takes no longer than 15 minutes, depending on the device. If it takes longer, you may have missed a step, otherwise feel free to get assistance.
Download link:
Builds are released here: Releases on GitHub
Warning: These releases include builds for other devices i own, make sure to download files from a release for Xiaomi 12, for example: "LineageOS 20.0 for Xiaomi 2201122G (zeus)"
Note: There are two variants which are not necessarily released at the same time. Vanilla builds are pure LineageOS without additional apps and GMS builds include Google services. The GMS builds are too big for github releases, so they will be uploaded to this shared folder on Google Drive instead
Source Code
Please read this thread about the OSS kernel on Xiaomi 12 series.
All kernel related source code can be found here.
Device trees for LineageOS can be found here.
For all development related questions please refer to this thread.
Donate to support development:
Donate via PayPal to ArianK16a
Donate via PayPal to LineageOS

So,2 threads for same rom?
For the gapps, can we flash them directly now or use Magisk?

nice work !! thanks

Nicee gonna try this tonight! Thanks for the great work!

Thank you for your work!

NOSS8 said:
So,2 threads for same rom?
For the gapps, can we flash them directly now or use Magisk?
Click to expand...
Click to collapse
This thread is for discussion about the build from a user-perspective while the other thread aims to bring the build process closer to other developers and discussion about the source code.
GApps situation on the vanilla build is still the same but i have also built one with google apps integrated.
The relevant files can be downloaded here.

NeoArian said:
This thread is for discussion about the build from a user-perspective while the other thread aims to bring the build process closer to other developers and discussion about the source code.
GApps situation on the vanilla build is still the same but i have also built one with google apps integrated.
The relevant files can be downloaded here.
Click to expand...
Click to collapse
Gapps.
Yep, I had seen it but it dated back to February and now it's up to date.
You worked hard, thanks.

God bless you

Nice working bro.
Waiting for too long to use the stable aosp ROM

I have created a magisk module to get the MiuiCamera application working on LineageOS.
I missed two libs in vendor which are meant to be in the ROM, i have added them into the magisk module for now so that bokeh mode works.
If the module does not work for you please run the following commands, clear the app data and reboot
Code:
adb shell restorecon vendor/lib64/libmibokeh_mask.so
adb shell restorecon vendor/lib64/libmiphone_capture_bokeh.so
edit:// seems like you need to clear the apps data everytime you use the app. I forgot to include the fix in source of the ROM. The next lineage build will fix this issue!
Please use v1.08 on builds that are newer than 20230625.

Thank you for your efforts！

Thank you! You made this device 10x better!

First of all superb job on first AOSP rom for Zeus, or atleast what I know. Nearly perfect from the start. However I've noticed very minor bugs (wont affect use) like time untill fully charged on lockscreen is missing 2nd digit of the time and back gesture doesnt work properly when keyboard open (I'm using GSM release so I have GBoard). Other than that I've found 0 major issues so far and everything seems to work as it should. Keep up the good work, and THANKS for saving Xiaomi 12 Pro.

Rakpere said:
First of all superb job on first AOSP rom for Zeus, or atleast what I know. Nearly perfect from the start. However I've noticed very minor bugs (wont affect use) like time untill fully charged on lockscreen is missing 2nd digit of the time and back gesture doesnt work properly when keyboard open (I'm using GSM release so I have GBoard). Other than that I've found 0 major issues so far and everything seems to work as it should. Keep up the good work, and THANKS for saving Xiaomi 12 Pro.
Click to expand...
Click to collapse
Battery usage seems to be reported wrongly, not a big deal.

Few issues so far:
AptX Adaptive bluetooth codec doesn't seem to be present at all
Brave Browser (could also be any chromium based browser but unsure) freezes once in a while and completely dies with Sync Chain on (also read this might be a Magisk issue so this may be unrelated)
There are a few stutters and lag spikes here and there when the screen is transitioning to 120Hz
No way to change resolution to 1080p to save battery life
Either way, amazing work and thank you for everything!

Ghesun said:
Few issues so far:
AptX Adaptive bluetooth codec doesn't seem to be present at all
Brave Browser (could also be any chromium based browser but unsure) freezes once in a while and completely dies with Sync Chain on (also read this might be a Magisk issue so this may be unrelated)
There are a few stutters and lag spikes here and there when the screen is transitioning to 120Hz
No way to change resolution to 1080p to save battery life
Either way, amazing work and thank you for everything!
Click to expand...
Click to collapse
I have the same issue when using browser to view page with too much text or js. I have solve by deactivating the auto frame rate, it makes my screen 60 Hz always. I think the problem is cause of kernel.

Ghesun said:
Few issues so far:
AptX Adaptive bluetooth codec doesn't seem to be present at all
Brave Browser (could also be any chromium based browser but unsure) freezes once in a while and completely dies with Sync Chain on (also read this might be a Magisk issue so this may be unrelated)
There are a few stutters and lag spikes here and there when the screen is transitioning to 120Hz
No way to change resolution to 1080p to save battery life
Either way, amazing work and thank you for everything!
Click to expand...
Click to collapse
Forgot a few:
Sometimes a random flicker occurs at the left side of the status bar, very weird graphical issue (Was downloading songs from Tidal during this)
Animations and UI elements that are usually tied to where the physical buttons are (volume slider, AOD off animation) are not placed correctly
Sorry if these are issues already known or to be considered as cherry pick issues!

GMS version:
Connecting earphones to usb, the headphone icon is displayed but indicates that the device is charging.
Only the links sent by my banking application on Google messages are inactive (not this problem with the previous version 20230606).
The association of my GTR4 require 2 Bluetooth associations, concerning the second,for calls, the code is indeed sent to the watch and the phone but during the association, it returns a second code, which causes the association to fail (same on the previous version).
Browser freeze more frequent than the previous version.
Call recorder"Basic Call Recorder" (Magisk) works perfectly.
Basic Call Recorder is a no-nonsense call recording solution for rooted devices
Thanks to this Magisk module, you can now enable the call recording feature on any Android device running Android 10-13. Read on!
www.xda-developers.com

NeoArian said:
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.
*/
Introduction
To find out more about LineageOS visit the official Website.
All the source code for LineageOS is available in the LineageOS Github organization. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation
Warning: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
LineageOS is provided as-is with no warranty. While we attempt to verify everything works you are installing this at your own risk!
Warning: Before following these instructions please ensure that the device is currently using Android 13 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 13, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Unlocking the bootloaderNote: The steps below only need to be run once per device. They require a machine running Windows 7 or newer.
Warning: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed.
Tip: It is highly recommended to have the latest official MIUI stable package installed on the device, before proceeding with unlock.
Create a Mi account on Xiaomi’s website. Beware that one account is only allowed to unlock one unique device every 30 days.
Add a phone number to your Mi account.
Insert a SIM into your phone.
Enable developer options in Settings > About Phone by repeatedly tapping MIUI Version.
Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status.
Download the Mi Unlock app (Windows is required to run the app).
Run the Mi Unlock app and follow the instructions provided by the app. It may tell you that you have to wait up to 30 days. If it does so, please wait the quoted amount of time before continuing to the next step!
After device and Mi account are successfully verified, the bootloader should be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing additional partitionsWarning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from the download section below.
boot.img
dtbo.img
vendor_boot.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash boot <boot>.img
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
Booting a custom recovery using fastboot
Download Lineage Recovery from the download section below. Simply download the latest recovery file, named recovery.img.
Important: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!
Connect your device to your PC via USB if it isn’t already.
If your device isn’t already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable (preferably use a USB Type-A 2.0 one or a USB hub) and port!
Tip: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to recovery__a /recovery__b rather than recovery_a / recovery_b if you try to flash recovery. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to recovery__a, you must flash to recovery_a.
Now reboot into recovery to verify the installation.
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Note: If your recovery does not show the LineageOS logo, you accidentally booted into the wrong recovery. Please start at the top of this section!
Installing LineageOS from recovery
Download the LineageOS installation package from the download section below that you would like to install or build the package yourself.
(Optionally): If you want to install an application package add-on such as Google Apps (use the arm64 architecture), please read and follow the instructions on Google Apps page
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the main menu.
旁加载 LineageOS .zip 包，但在阅读/遵循其余说明之前不要重新启动 ！
在设备上，选择“应用更新”，然后选择“从 ADB 应用”以开始旁加载。
在主机上，使用 adb sideload filename.zip 旁加载包。
提示： 通常情况下，adb 会报告 Total xfer: 1.00x，但在某些情况下，即使进程成功，输出也会停止在 47% 处并报告 adb: failed to read command: Success。在某些情况下，它会报告 adb: failed to read command: No error 或 adb: failed to read command: Undefined error: 0 这也可以。
可以了，好了！成功安装所有内容后，您现在可以首次重新启动设备进入操作系统！
单击屏幕左上角的后退箭头，然后单击“立即重新启动系统”。
注意： 首次启动通常不会超过 15 分钟，具体取决于设备。如果需要更长的时间，您可能错过了某个步骤，否则请随时寻求帮助。
下载链接：
版本在此处发布：GitHub 上的版本
警告：这些版本包括针对我拥有的其他设备的构建，请确保从小米 12 的版本下载文件，例如：“ LineageOS 20.0 forxiaomi 2201122G (zeus) ”
注意：有两个变体不一定同时发布。Vanilla 版本是纯粹的 LineageOS，无需额外的应用程序，而 GMS 版本则包含 Google 服务。GMS 版本对于 github 版本来说太大，因此它们将被上传到Google Drive 上的此共享文件夹
源代码
请阅读这篇有关小米 12 系列 OSS 内核的帖子。
所有内核相关的源代码都可以在这里找到。
LineageOS 的设备树可以在这里找到。
对于所有与开发相关的问题，请参阅此主题。
捐赠支持发展：
通过 PayPal 捐赠给 ArianK16a
通过 PayPal 向 LineageOS 捐款
Click to expand...
Click to collapse
good work！

Ghesun said:
Beberapa masalah sejauh ini:
AptX Adaptive bluetooth codec sepertinya tidak ada sama sekali
Peramban Berani (bisa juga peramban berbasis krom apa pun tetapi tidak yakin) membeku sesekali dan benar-benar mati dengan Rantai Sinkronisasi aktif (baca juga ini mungkin masalah Magisk jadi ini mungkin tidak terkait)
Ada beberapa gagap dan lonjakan lag di sana-sini saat layar beralih ke 120Hz
Tidak ada cara untuk mengubah resolusi ke 1080p untuk menghemat masa pakai baterai
Either way, kerja luar biasa dan terima kasih untuk semua
Click to expand...
Click to collapse
Root via magisk

Database Develop

welcome