Database Develop

Install Android Q in Mi A1 (Android Q A/B GSI Ports)

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements:
# treblized vendor (P or O)
How to install:-
1. Enable Developer options in Settings app
2. Check Enable OEM Unlocking
3. Reboot to fastboot mode
4. Unlock your bootloader
5. Install TWRP-fastboot only through fastboot boot command (Extract the .img file from the zip)
6. Flash CosmicDan's TWRP Installer through your current TWRP. Credits to @CosmicDan for his TWRP and @mohancm for official TWRP sources.
7. Reboot to TWRP recovery
8. Go to WIPE then ADVANCED then click FORMAT data. This will remove Encryption on your device and allows you to set new passwords when installing the GSI. Note that this will format your internal storage.
9. Treblelize through TWRP Tissot Manager (Go to advanced, click Tissot Manager and choose the repartition userdata option. Select singleboot option then click repartition)
10. Flash Boot image
11. Flash Pie Vendor ( VENDOR_A1_PIE-NFE_20181011 ) by Adb sideload
12. Install System Image (Q_AB_v0.3.img.7z)
13. Flash permissiver_v2.zip or make your boot partition selinux permissive
14. Flash FixZygote.zip
15. Reboot To system
16. Special thanks to @erfanoabdi for porting the Q A/B GSI.
Bugs:-
1. Volte Fully Broken
2. Camera Not Working
3. Wifi Broken ( Connection seems but not connected)
XDA:DevDB Information
Android Q, ROM for the Xiaomi Mi A1
Contributors
Sonudbm, Erfanoabdi
Source Code: https://mega.nz/#F!CYQxgCDK!Dl4kKANVDRy5kOFkNsuMVw
ROM OS Version: 9.x Pie
ROM Firmware Required: treblized vendor (P or O)
Based On: GSI
Version Information
Status: Beta
Stable Release Date: 2019-03-17
Beta Release Date: 2019-03-15
Created 2019-03-19
Last Updated 2019-03-19

Duplicate thread closed.
Please use this one instead.
Funk Wizard
Forum Moderator

[UNOFFICIAL][TWRP][Recovery] TWRP 3.3.1-0 [Onc/Onclite]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
/*
* Your warranty is now void.
*
* 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.
*
*/
CHANGELOG for 3.3.1-0:
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
Install guide:
Install fastboot tools from google's sdk on your PC
Enter fastboot mode
Unlock your bootloader
Download recovery-20190820.img
Run "fastboot flash recovery recovery-20191120.img in command line
Reboot and enjoy it
Download:
recovery.img [20/11/19]
XDA:DevDB Information
Twrp, Tool/Utility for the Xiaomi Redmi 7
Contributors
RevanthTolety, Flex
Kernel Source Code: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/onc-p-oss
Version Information
Status: Stable
Stable Release Date: 2019-11-20

i wonder if this could work with the pixel experience rom

So many of you might wonder about the need of a new recovery since there are already many recoveies floating around, but there are few things that are different about this one
This recovery sets the proper codename for your device i.e.: Onc & Onclite for Redmi 7 Global & All Other Variants
This Recovery Is Built With Proper Source Code & Correct Partition Sizes With the Ability to Flash Custom Roms
Last But Not the least, Some ScreenShots

Do this support encryption??

Zac_1 said:
Can I use this recovery for the pixel experience ROM?
---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------
Can you please try it and give us feedback?
Click to expand...
Click to collapse
you could like , try it yourself...I'm happy with miui 10 and waiting for miui globe 11

Do this support miuimix 2.0 + gsi?

RevanthTolety said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
/*
* Your warranty is now void.
*
* 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.
*
*/
CHANGELOG for 3.3.1-0:
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
Install guide:
Install fastboot tools from google's sdk on your PC
Enter fastboot mode
Unlock your bootloader
Download recovery-20190820.img
Run "fastboot flash recovery recovery-20190820.img in command line
Reboot and enjoy it
Download:
recovery.img [28/08/19]
XDA:DevDB Information
Twrp, Tool/Utility for the Xiaomi Redmi 7
Contributors
RevanthTolety, thelazyindian
Kernel Source Code: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/onc-p-oss
Version Information
Status: Stable
Stable Release Date: 2019-08-28
Created 2019-08-28
Last Updated 2019-08-27
Click to expand...
Click to collapse
It can decrypt android 10?

I wonder what's the difference between this and the official version found in TWRP's site.

Can i flash onc and onclite roms with this?

Andrica said:
Can i flash onc and onclite roms with this?
Click to expand...
Click to collapse
Yeah U Can
Darth Bidder said:
I wonder what's the difference between this and the official version found in TWRP's site.
Click to expand...
Click to collapse
I Dont Know About That Though, But mine is Built with Proper Twrp Trees & Correct Partition Sizes & Adds Both Onc & Onclite Codename

Time for quick update
Changelog
Mounting And Unmounting Of Partitions Fixed
Now Roms can be backed up and restored
Fixed "zip_compatible_err" while flashing a few roms
Links are updated in op enjoy [/QUOTE]

While backing up, it's not able to mount partitions...keeps asking for decryption password...
Edit: You need to select Wipe > Format Data first

Can it decrypt Android Q ? Btw thanks

Time For a Quick Update
- Fixed Compatibility_Zip Error Permanently
- Full Support to Flash Source Built Vendor Based Roms
Download Link Updated in OP

RevanthTolety said:
Time For a Quick Update
- Fixed Compatibility_Zip Error Permanently
- Full Support to Flash Source Built Vendor Based Roms
Download Link Updated in OP
Click to expand...
Click to collapse
Thank you very much.
In OP (Install guide) there is an error because now "Download recovery-20190820.img" should be "Download recovery-20191120.img".

I install the twrp.img but am unable to boot in to twrp.
Any solutions?

Can't install arm64 Gapps. TWRP forces me to flash arm version but when I boot into LineageOS there are no Gapps at all.

This Is a pretty good build of TWRP but can't decrypt and doesn't install GApps (Shows arm instead of arm64)
Otherwise, works like a charm

does this handle decryption and can disable dm-verify?

Installing GSI ROM on realme XT RMX1921

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.
*
*/
Hi guys!
I just want to share how to flash GSI on our realme XT RMX1921.
I've testing Phh's Quack (Android 10) and booted.
You maybe can test another GSI and then report it here.
I haven't testing another AOSP GSI or even OEM GSI like OOS / MIUI / H2OS.
I'll update if I was testing it and boot successfully.
If you have simpler way to install GSI then tell me tho.
Here is the steps :
1. Unlock your XT's bootloader and make sure you have installing adb fastboot on your Windows / Linux / Mac
2. Flash TWRP by thesprintster here : https://forum.xda-developers.com/re...ecovery-unofficial-twrp-realme-5-pro-t3985459
3. Download LineageOS by thesprintster here : https://forum.xda-developers.com/realme-xt/development/rom-lineageos-16-0-t3985463
4. Open LOS zip and take the boot.img
5. Download vbmeta by thesprintster here : https://drive.google.com/drive/folders/1JwIpix76opSAToa-4X4YdT_SH5JUOxJQ
6. Download Phh's Quack here : https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559 (select arm64-ab-gapps or arm64-ab-vanilla)
6a. You can download another GSIs like ExpressLuke GSIs here : https://forum.xda-developers.com/project-treble/trebleenabled-device-discussion/gsi-expressluke-built-gsis-t4003457 and make sure you download the ARM64 AB variant.
7. Boot to TWRP and backup your vendor image (or maybe all your vendor + system + boot + data if you want to back to ColorOS) incase to avoid any error
8. Wipe all except vendor
9. Back to bootloader / fastboot, put your vbmeta.img to your adb fastboot folder
10. Flash vbmeta.img by typing fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
11. Boot to TWRP and copy Phh's Quack System image and LOS boot.img to your rXT
12. Flash boot and system image
13. Flash Gapps (if you download the vanilla variant) or if you want Google-less you can skip this
14. Reboot to system
15. Wait for booting aprrox. 4 minutes
Bug list on Phh's Quack GSI (and another Phh's based GSIs) tested on rXT 8/128 :
- Fingerprint not working (realme disable fingerprint since bootloader unlocked)
- VoLTE not working (global GSI bugs)
- Status bar on side (like battery and clock) got cropped and mis-positioned How to fix clock and battery logo : Go to Settings - Phh Treble Settings - Misc features - Set rounded corners diameter : 15 (or above 15, just fill with values you want)
- Bluetooth Media not working
- you tell?
Tested GSIs :
- Quack Phh-Treble arm64-ab-gapps v202 by phhusson
- Evolution-X 3.3 20191111 ARM64-AB by turbolukex5
Enjoy! :fingers-crossed:

You can correct status bar cropping by enabling developer options and selecting cutout.

I'll just add this here in case anyone needs it.
Also , if anyone finds workarounds for VoLTE, please feel free to post it.

Make any GSI work fully on the Xiaomi Redmi 8

Code:
/*
* Your warranty is now void lol.
*
* 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 tutorial
* 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.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * 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...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial

Forgot to mention that magisk WONT WORK on roms that use android 11!!
Its a limitation of android 11 and i cannot fix this.

Seems promising. Would try on weekend and cast vote.
Thanks for you efforts for community.

Realized once again that you dont even need to boot, just flash the lineageOS rom, then the GSI on top.

thank you very much its working the problem i always encounter is my bluetooth but now its working fine sorry for my bad english BTW i use havoc <3

I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?

thanks, in the evening I will check and tell exactly what works and what does not work, probably all GSIs are giving me some problems (problem with brightness or bluetooth headphones)

Thank you for this guide. I installed havoc os 4.1 using this exact method wiped everything formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?

Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?

Dragonnuu said:
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Click to expand...
Click to collapse
We need LOLZ because the lineage kernel gets carried over and its broken (Try booting lineage clear, you wont get far)

mwaseem851 said:
I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?
Click to expand...
Click to collapse
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.

I have done lots of experimentation since last post and finally settled with Havoc OS 3.12 (all android 11 roms are still buggy).
Thanks.
boofiboi said:
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.
Click to expand...
Click to collapse

boofiboi said:
Code:
/*
* Your warranty is now void lol.
*
* 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 tutorial
* 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.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * 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...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial
Click to expand...
Click to collapse
Can you flash the AOSP beta GSIs from released on the Android website? For example the Android 12 Beta GSI?
I tried installing Android 12 on Redmi 8 but it did something perplexing.
TWRP said no OS was installed. Rebooting had the phone boot back into TWRP. I tried installing through both fastboot and TWRP. Installations were successful tho.

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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
To find out more about LineageOS visit the official Website.
All the source code for LineageOS is available in the LineageOS Github organization. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation
Warning: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements​
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
LineageOS is provided as-is with no warranty. While we attempt to verify everything works you are installing this at your own risk!
Warning: Before following these instructions please ensure that the device is currently using Android 13 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 13, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Unlocking the 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