Database Develop

Development [ROM][13][UNOFFICIAL] LineageOS 20 for Xiaomi 12 Pro - 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 bootloader​Note: 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 partitions​Warning: 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 bootloader​Note: 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 partitions​Warning: 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

Related

GOOGLE PIXEL C - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
NOTE: There is no insecure kernel available yet so those options have been disabled in the Toolkit. I will make some and enable the options as soon as possible.
The Unified Android Toolkit brings together all the Nexus, Google, OnePlus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On newer device you will also need to make sure "enable/allow OEM unlock" is ticked in developer options.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your Bootloader Mode
1. Turn your device off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into Bootloader Mode
How to get into your Fastboot Mode
1. First boot into Bootloader Mode as described above
2. Select 'Switch to fastboot mode' using the volume button and press the power button. The device will say 'Waiting for fastboot command...'
How to get into Recovery
1. First boot into Bootloader Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.

** ChangeLog **

** FAQ **

Hi,
Does everything works?
We can unlock and root with that tool ?
Envoyé de mon LG-H815 en utilisant Tapatalk

misteurz said:
Hi,
Does everything works?
We can unlock and root with that tool ?
Envoyé de mon LG-H815 en utilisant Tapatalk
Click to expand...
Click to collapse
I don't want to sound like a douche, but its in the third line of the post that there's currently no root available.
tldr: no

Oh sorry, I have a piece of meat in the eyes
Envoyé de mon LG-H815 en utilisant Tapatalk

Awesome! Welcome mskip!

misteurz said:
Hi,
Does everything works?
We can unlock and root with that tool ?
Envoyé de mon LG-H815 en utilisant Tapatalk
Click to expand...
Click to collapse
Bootloader unlock should work fine (if someone can confirm this for me please).
As stated as soon as a custom recovery becomes available then I can easily enable root functions in the Toolkit.
Mark.

Can anyone who has selected this module fro mthe Toolkit please confirm that it passes the config section and proceeds to the Main Menu (where you can unlock, flash stock, etc).
I have a user who is getting an error at "Checking files are all present" stage and I cannot recreate this problem. Also I cannot see any problems in the code that would cause this error to occur.
Thanks (and Merry christmas for people who missed my messages online), MArk.

DEVICE MODULE V1.0.1 UPDATE AVAILABLE FOR ALL USERS (PRO AND PUBLIC)
Changelog:
+Fixed error at files check stage on some systems
Pro users can just start the Toolkit as normal. After you have selected your device you will be notified there is an update available and can auto update. SIMPLE.
Non Pro users have a few extra steps.
1. Exit the Toolkit if it is open.
2. Run ToolkitClean.exe from the intallation folder (or the Start Menu)
3. Select the device (GooglePixelC) from the list
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. Restart the Toolkit, select the device and new module files will be downloaded/installed
If you want to donate to the Google Pixel C project please do it through the Toolkit (after selecting the device at startup) so you get the right code fast.
Enjoy, Mark.

But I can root on Google Pixel C with 6.0.1 (MXKB48J)?? ASAP

Scarfacez2007 said:
But I can root on Google Pixel C with 6.0.1 (MXKB48J)?? ASAP
Click to expand...
Click to collapse
Yes you can! ASAP

Really? Don't you mind can give me the link ?

Scarfacez2007 said:
Really? Don't you mind can give me the link ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3289357

Now I wondering if I get update Pixel C 6.0.1 (MXB48T) still on root?

Scarfacez2007 said:
Now I wondering if I get update Pixel C 6.0.1 (MXB48T) still on root?
Click to expand...
Click to collapse
No, just flash system and vendor.

Or I can downgrade?

Scarfacez2007 said:
Or I can downgrade?
Click to expand...
Click to collapse
You can flash the whole system image but can't guarantee root will work on it.

Device Module Auto Updates Available
This has been a special round of updates for the latest google monthly updates and does not affect my commitment to updating the Samsung modules with the latest builds and procedures.
Google Pixel C update [V1.0.2] 02ND FEB 2016
+Added Support for Android 6.0.1 MXB48T
+Added Android 6.0.1 MXB48T stock image to download/flash directly from Toolkit
+Updated checksum file for verifying stock image download
+Minor updates and bug fixes
If you want to donate to a device project to receive the pro updates please do it through the Toolkit (after selecting the device at startup) so you get the right code fast. Alternatively you can go to http://www.skipsoft.net/?page_id=703 and select the device you wish to activate.
On a side note I have not enabled root functions yet as it seems hit and miss and errors can lead to devices being bricked. Also im not sure about the current state of custom recovery and whether it is stable yet. If anyone can give more information about recovery/root on the Pixel C I may enable root functions and could possibly adapt the current procedure with any extra steps needed.
Enjoy, Mark.

I did buy Pro for Google Pixel C but I got unlocked and I still cant get root because of "disable" something I miss it?

This version of TWRP works on the Lenovo TB-X505F (wifi).
For the TB-X505X, see this thread. For the TB-X605F/L, see this thread.
For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC.
Code:
#include <std_disclaimer.h>
/*
* We are 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 us for messing up your device, we will laugh at you.
*/
Working:
AFAIK, everything is working including:
data decryption
MTP
Known issues:
time not adjusting for Daylight Saving
OTA (for a workaround see this post)
Before installing TWRP
Before you install TWRP, upgrade your tablet to the Android 9 (Pie) or Android 10 (Q) stock ROM.
This tablet shipped with Android 8 (Oreo), in which the bootloader did not allow unlocking. When you tried to unlock the bootloader, it gave this error message:
Code:
fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Installation
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.apk to your MicroSD or OTG device. Get the latest Magisk apk file here. Rename the filetype from apk to zip (for example Magisk-v22.0.zip)
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
01/03/2023 - bug fix: data partition again backs up and restores correctly
20/01/2023 - add TW_EXTRA_LANGUAGES and TB_X505F_S001149_221115_ROW kernel (credit to @Tonyha7 )
30/12/2022 - add system partition to AdvancedWipe (TB_X505F_S001147_220830_ROW firmware only)
15/11/2022 - TWRP 3.7.0-0 update
- support for TB_X505F_S001147_220830_ROW
18/12/2021 - TWRP 3.6.0-0 update
- support for A12 decryption (keymaster)
27/03/2021 - TWRP 3.5.1-0 update
- change to landscape mode for tablets
01/01/2021 - TWRP 3.5.0-0: initial release
Downloads
TWRP 3.7.0-0 for X505F: twrp-X505F_11.img (for TB_X505F_S001147_220830_ROW and above)
TWRP 3.6.0-0 for X505F: twrp-X505F_11_2021.img (for earlier stock ROMs)
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
https://github.com/Yahoo-Mike/recovery_device_lenovo_X505F/tree/android-11.0
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Tonyha7
Last Updated 2023-03-01 (fix /data backup/restore)
Created 2021-01-01

reserved

Thanks for useful post,
Possible to reboot into recovery from fastboot?

zubair1836 said:
Thanks for useful post,
Possible to reboot into recovery from fastboot?
Click to expand...
Click to collapse
Not that I know of. The bootloader accepts the command fastboot reboot recovery, but boots to system anyway.

Hello there, I've been looking how to install this on my slow tablet for almost like an hour. Could there be some tutorial or extended explanation to the process and installation, I'm such a noob, sorry.

This worked for me. Thank you for your effort and the TWRP!

Worked for me too - many thanks!
Can't wait for a custom ROM!
TWRP Recovery Installation Steps
1. Download android platform tools
2. Unlock developer mode on the M10
3. Enable USB debugging on the M10
3. OEM unlock enable on the M10
4. XDA download TWRP copy to sd
5. Download Magisk app (from Github!!! johnwu), change extension to .zip
6. Adb to fastboot
7. fastboot flash recovery [filename.img]
8. Turn off device
9. Turn on device holding all 3 buttons, release when see Lenovo splash screen
10. In TWRP find Magisk zip
11. Install Magisk
Stock ROM Recovery
1. Download qualcomm drivers 64 bit install
2. Download Lenovo recovery and image tool windows app from Lenovo support website
3. Fastboot oem edl
4. Turn off M10
5. Start recovery windows app, wait till instructions
6. Hold volume up (up is the side of the button closest to the front camera) and insert cable
7. Release button after windows app detects device
8. Troubleshoot by checking windows device manager for the M10 appears as a Qualcomm device

I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.

Heeni said:
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Click to expand...
Click to collapse
Confirmed working normally.

zubair1836 said:
Confirmed working normally.
Click to expand...
Click to collapse
Many thanks.

Thank you! TWRP is working fine!
Stupid me flashed before I installed the Android 10 OTA, so I had to temporarily go back to stock recovery. Unfortunately beamingbadger's method didn't work for me.
This is how it worked for me:
Download the OTA via Lenovo's "Rescue And Smart Assistant"
The stock recovery image will be in the Download folder (default path: C:\ProgramData\LMSA\Download\RomFiles) called "recovery.img"
Flash the recovery.img the same way as you would with the twrp img (adb reboot bootloader -> fastboot flash recovery recovery.img)
fastboot reboot
Install OTA
Flash TWRP recovery + Magisk again (follow the steps from the first post, skip bootloader unlock)

The method I use to install OTAs is:
open Magisk App
select "Uninstall Magisk", then the "Restore Images" option
reboot to Android (you will have no root access and stock recovery is restored)
apply OTA
re-flash twrp and install Magisk
NOTE 1: if you've unencrypted your data partition, it will be re-encrypted by this process.
NOTE 2: the new Magisk App (v22) can be installed in TWRP by renaming the *.apk to *.zip. See the new install instructions.

What's involved with running gsi ROMs on this device? It's got the same SoC as my Samsung Tab, which runs them well, so I'm assuming that this tab will also, but I'd like to know if there are any traps that I need to be aware of.

I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.

Heeni said:
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
Click to expand...
Click to collapse
That's great news. Well done.
Heeni said:
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Click to expand...
Click to collapse
On my X605F I do this in twrp for a new GSI install:
format (not wipe) data partition. This is the option where you have to confirm by swiping.
factory reset. This clears the caches.
restore the stock boot and vendor partitions (from a backup I made). This is because Magisk can touch these partitions.
install the GSI system image
install anything else I need like disable_Dm-Verity, Magisk, gapps etc
I don't know what LOS R Mod //LiR does to your system. If it touches any other partitions, you should restore those to stock too.

Thanks for that. It gives me something to go on with. I've downloaded the stock ROM from lolinet, so I can grab the boot and vendor images from that.

I was able to try a couple of other GSI ROMs and I've settled on AndyYan's LineageOS 17.1 for now. The only serious installation issue I had - which I can laugh about in hindsight - was thinking I'd got myself into a very bad bootloop, when all I needed to do was let go of the power button after the Lenovo logo appeared.
On this tablet, there is no navigation capability at all (no navbar, no gestures, no setting to configure them) on installation, and I have to set it using adb. I suspect it goes back to PHH basic ROMs, but I don't feel like doing yet another install and testing right at this moment. Is this happening on the other tablets that you're testing, or is it unique to this one?

I just posted the v3.5.1 update to twrp.
It's also changed to landscape mode, as many of you requested.

Quick question, how do i apply new system updates with twrp installed? Should i not bother? Also, i forgot how to block check for updates!

will this allow flashing of stock roms download from lenovo recovery? ive been stuck on an ancient android 9 version because the ota updater fails.

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.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Pixel 5a Barbet
​
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 barbet​WARNING: 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 partition​warning
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 bootloader​info_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 partition​warning
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

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

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

Features
SELinux enforcing
AES-256-XTS FBE encryption
Known issues
VoLTE/VoWiFi
You tell me
Likely more

If we already have LOS 19.1 and recovery, do we still need to install the new recovery and factory reset?
edit: I renamed the new recovery image to recovery.img and then used 7zip to make recovery.tar and flashed it with Odin. But when I booted to recovery, all I got was a blank screen. Had to reflash the 19.1 recovery to get it back.

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

HippoInWindow said:
May I ask for screenshots? This is amazing work
Click to expand...
Click to collapse
It appears the dev wants you to use Telegram for support and doesn't answer questions here in XDA. But I didn't get much support there either. When I asked what gapps to use, It just pointed to the Nikgapps site. But when I flashed the CORE version for T, Play Store didn't recognize the internet connection. Tried to revert to 19.1 and it wouldn't let me. Claimed it was a downgrade and not allowed. Had to flash the latest stock version via Odin, with all of the Samsung and Google bloat.

Well, I got it to work in spite of the lack of support. Had to use the OMNI version of Nikgapps instead to CORE. One little nit pick discovered so far. /Setup/System/Status Bar setting to change the battery icon to text and show percent doesn't work. But that is easy to live with.

lewmur said:
If we already have LOS 19.1 and recovery, do we still need to install the new recovery and factory reset?
edit: I renamed the new recovery image to recovery.img and then used 7zip to make recovery.tar and flashed it with Odin. But when I booted to recovery, all I got was a blank screen. Had to reflash the 19.1 recovery to get it back.
Click to expand...
Click to collapse
https://dl.linux4.de/lineageos/releases/gta4xlwifi/
LOS 20 recovery here. I do think we have to use same recovery version as the instructions say.
The image has been updated today and now I see the lineage OS 20.0 recovery.

xsw2 said:
https://dl.linux4.de/lineageos/releases/gta4xlwifi/
LOS 20 recovery here. I do think we have to use same recovery version as the instructions say.
The image has been updated today and now I see the lineage OS 20.0 recovery.
Click to expand...
Click to collapse
if flashed it with the old recovery but the zip check false and then you have to flash anyway
i check and the file size of both recovery where the same thought that is just for the ones that need it for flash for the first time

Just downloaden every thing with a AVG Antivirus alert.
For now I'll wait and maybe test later.
edit: the alert was from a know false positive.
For me better safe than sorry.

reef2009 said:
Just downloaden every thing with a AVG Antivirus alert.
For now I'll wait and maybe test later.
View attachment 5705853
Click to expand...
Click to collapse
Well I built that zip myself, I can assure you there's no malware.
BTW Antivirus apps on android are only a waste of resources.

Updated with September securitypatch and more lineage features

Is the changelog link broken? When I try it to see if I want to flash the latest version, it just times out.

lewmur said:
Well, I got it to work in spite of the lack of support. Had to use the OMNI version of Nikgapps instead to CORE. One little nit pick discovered so far. /Setup/System/Status Bar setting to change the battery icon to text and show percent doesn't work. But that is easy to live with.
Click to expand...
Click to collapse
You're not owed support by anyone. OP could flip off every user and **** off forever, but they'd still have done their work for the community. Thanks for the tips, though!

okno13 said:
You're not owed support by anyone. OP could flip off every user and **** off forever, but they'd still have done their work for the community. Thanks for the tips, though!
Click to expand...
Click to collapse
I didn't claim I was owed support. I merely stated that I didn't get any and that I was able to get it working in spite of that.

Device reboots after opening camera. Probably issues with camera hal

So far so good, except I cannot for the life of me get the Google keyboard to work...all other gapps are fine...

Well, the dev for this ROM has convinced me to sell my S6 and buy a newer tablet that has support here in XDA. Apparently, he will only offer support in Telegram because, in that app, he can ban anyone who disagrees with him. So, no support if you want, TWRP, Magisk, Nixgapps, custom kernels or anything else he doesn't like.

lewmur said:
Well, the dev for this ROM has convinced me to sell my S6 and buy a newer tablet that has support here in XDA. Apparently, he will only offer support in Telegram because, in that app, he can ban anyone who disagrees with him. So, no support if you want, TWRP, Magisk, Nixgapps, custom kernels or anything else he doesn't like.
Click to expand...
Click to collapse
What reason would we have to ban people who want support? He doesn't provide support for TWRP because it's a discontinued project and because it worked terribly on the tablet. That's like asking Samsung for help on a flip phone you bought in 1994 that's been discontinued for quite a while. I don't think I recall him actively rejecting people's technical support for Magisk, NikGapps, or Custom Kernels when I was in his Telegram, he only said that he recommends alternatives to Magisk and NikGapps. I don't know if you're writing this after you were banned but the only time he proactively rejected support in people's devices is when TWRP was in the equation.

{Mod edit: Quoted post has been deleted}
It is being actively supported by legacy devices that can't handle encryption and on ROMs made by unknowingly devs.
Also you were told multiple times that encryption is not an optional thing, especially on T. And some users do care about their data not being just accessible when the device gets stolen.