[ROM][UNOFFICIAL][13.0] LineageOS 20 for Galaxy Tab S6 Lite - Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri

[ROM][UNOFFICIAL][13.0] LineageOS 20 for Galaxy Tab S6 Lite - Samsung Galaxy Tab S6 Lite ROMs, Kernels, Recoveri

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.

Related

[Recovery][Qualcomm] Official TWRP for the Galaxy S7 edge (hero2qltechn)

Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 edge stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2qltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22

As a joke, here you go USA!
https://idlekernel.com/twrp/hero2qlte/twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!

You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.

travis82 said:
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
Click to expand...
Click to collapse
It doesn't matter, dm-verity isn't enabled in the fstab, nor does the TWRP image contain any verity signatures to enforce.

finally...

thank god!finally!but the front cam issue have been solved?

Anyone know what roms work with this device? Also how to return to stock?

When compression is enabled on backups the device freezes.

What happened to CROM Service? It's not in the Galaxy Apps and .apk's from mirror websites crash when opened.

I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?

ryan49er said:
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
Click to expand...
Click to collapse
this recovery is for unlocked bootloaders only. IE chinese and hong kong models only.

Well that sucks

Report...
jcadduono said:
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 edge stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2qltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
Click to expand...
Click to collapse
I had G9350ZCU2APK2 ROM (China), so I installed the Hong Kong ROM G9350ZHU2APK2 (I needed the google services) and the phone work great except the part of receiving or sending SMS's, I have two sim cards cards (China Telecom and China Mobile), if I sent a message from the CT the message was sent also from CM, if I send from CM is not working, when I receive messages I received on both sim cards... , big problem for me, so, I installed the last G9350ZCU2APL3 ROM (China) and is working ok but no google services...
I've tried your method and is working... (kind of) once I installed the TWRP and the last SuperSU the phone had no Wifi and no network signal, so I put back the original firmware...
All I need are the google services because Signal is not working without, the email client is not receiving the email (automatically) without and so on... I've tried all the "possible" ways, no luck...google installer v2 and so on...
Any ideas on how to put the google services?
----- Edit - 28 January 2017 ----
I reinstalled the TWRP provided in the first post and the phone is working, has signal (China Telecom and China Mobile) and also the WIFI is working, I didn't install the SuperSU, kind of weird, with SuperSu installed the phone has no WIFI and no signal...
I've tried to install the gapps pico and the TWRP is saying that "could not mount/data and unable to find crypto folder", "Failed to mount '/data' (invalid argument)", "Unable to recreate /data/media folder", "failed to mount '/data' (Invalid argument)", "Unable to mount storage" , "Unable to mount / data/media/TWRP/. twrps.
The last error is: "Failed to mount'/data' (invalid argument)
After reading more posts on the forum I found the following:
"You CANNOT mount an encrypted partition in TWRP.
You do NOT wipe the partition.
Use the FORMAT DATA button. It's right there under the WIPE options next to the ADVANCED WIPE button."
Probably I will try this method when I am in the mood...

This works for SM-G935P? It says manufactured in china on the back.

Salanrm said:
This works for SM-G935P? It says manufactured in china on the back.
Click to expand...
Click to collapse
The post is for the Qualcomm, Galaxy S7 Edge SM-9350, China Open and Hong Kong, same hardware, different software (the Chinese one has no google services).
For your phone SM-G935P, search on google and you will find more instructions, I don't know if I am allowed to post here links from other websites.

jcadduono said:
As a joke, here you go USA!
twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
good afternoon
Reference is unfortunately not working
Can somebody share twrp-3.0.2-0-hero2qlte.tar.md5
thank you in advance for your response

So, this will 100% NOT work for the g935A? (Att s7 edge)

Craz Basics said:
So, this will 100% NOT work for the g935A? (Att s7 edge)
Click to expand...
Click to collapse
No. Locked bootloader
Sent from my SM-G935T using Tapatalk

Ahhh. That's some crap. Think it will ever be able to be unlocked?

Craz Basics said:
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Click to expand...
Click to collapse
It's a serious long shot but it is slowly being worked on.. check out this thread. It's for t mobile but the solution if found will apply to all us carriers as we all use the same method to root on marshmallow.
https://forum.xda-developers.com/showthread.php?t=3544220
Sent from my SM-G935T using Tapatalk

[ROM][UNOFFICIAL][12.1][DISCONTINUED] LineageOS 19.1 for Galaxy Tab S6 Lite Exynos

Requirements:
Any R 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
Magisk
I strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
Known issues
LineageOS specific features like livedisplay (for now)
You tell me

I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!

fzzt said:
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
Click to expand...
Click to collapse
Always follow this rule of thumb: it is never safe to dirty flash a completely different build on top of an older build (i.e. flashing 19.0 on top of 18.1, or 18.1 on top of 17.1, etc.). At best, you'll find yourself having random problems all over the place; at worst, the ROM will refuse to load. Best thing to do whenever going from one major release to another (or from one completely different ROM to another) is backup your apps and data, wipe data and caches and perform a clean flash, then restore your apps and data. It's a fair bit of work, to be sure, but it's the best way to avoid problems.

Sim card dont work, IMEI dont show, gapps cant install. Any ideas?

electro_vinyl said:
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
Click to expand...
Click to collapse
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?

Macuway said:
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Click to expand...
Click to collapse
With the latest build, it's all fixed!

Installed Lineage 19 last weekend on my P-610. You can flash the rom.zip, GApps and Magisk in Recovery from SD-card, so no need to sideload with adb. I have a problem with Google Playstore, it lags a lot (pending...) and installing an app like Gmail takes a long time. Now it even stopped working. Will try it later with NikGApps for Android S

Hi, it seems audio is not working.
It's just me?
Any help please.
M

minoltista said:
Hi, it seems audio is not working.
It's just me?
Any help please.
M
Click to expand...
Click to collapse
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9

Linux4 said:
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Click to expand...
Click to collapse
Just installed and it works! Thanks !!!

guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab

langamer101 said:
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
Click to expand...
Click to collapse
got it working guys. no need to help anymore.

Does anyone know why gboard force closes every time i try to install? I cleared all storage, played with permissions. Nothing worked.

First of all, I want to say thank to @Linux4 for this release Secondly, I want to ask comrads how to install MicroG on this build? If you can step by step, I'm new to custom firmware

how is newest recovery

Screenshots please

Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.

lobotomite said:
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
Click to expand...
Click to collapse
I have the same thing with any sound on the tablet This is especially noticeable when playing songs on spotify.

[ROM][UNOFFICIAL][12][OTA][OSS] LineageOS 19.1 for Galaxy S9/S9+ Exynos

Requirements:
Latest firmware
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, Bixby and Power to boot recovery
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

This build does not use the stock vendor, instead it's built on top of new trees which have been worked on for some time. The source is on our github, link in OP. You also get a few neat features like fingerprint gestures, and bixby button that actually works with both normal and long press.
I suggest using OpenCamera since stock one has some issues with flash.
These builds are signed with our release keys.
star2lte and crownlte support will come a bit later as i don't own the devices, but they will be supported eventually.
THESE BUILDS HAVE FORCE ENCRYPTION ENABLED, AND ONLY LINEAGE RECOVERY IS SUPPORTED. THESE THINGS WILL NOT CHANGE. IF YOU DON'T USE LINEAGE RECOVERY, AND SUFFER FROM DATA LOSS, DON'T COMPLAIN HERE.

Build uploaded, enjoy

Woah!!! Nice

How did you get OTA to work, I wanna try it too

nice
will try
been trying your work in PE, congrats on that and now curious to try this rom,
if I understood correctly this is your work along with Rob now?
Keep up the good work and thanks once again for reviving our devices

does LTE is supported in this ROM ?

quakze said:
does LTE is supported in this ROM ?
Click to expand...
Click to collapse
LTE/4G works with this ROM

Hey, thank you very much for this ROM, it's really smooth! Everything works except my second SIM.
For the first release this is pretty nice... and ... this is my first experience with Android 12 / LineageOS 19

star2lte build is up as well, find it at the link in the OP

BIG THANKS to the devs... NOW my S9+ will get a new life.
Edit: Did a test with 2 SIMs and only SIM1 is detected - no SIM2 so far... the Rest is really great work!!!

Great Job, Fresh install and my S9+ is (almost) Brand New!
I installed it with Samsung tool Odin recovery Lineage
Installing the rom with a sd card in de recovery, no sideload use! That works great!
Keep up the great work!

Razuuu said:
LTE/4G works with this ROM
Click to expand...
Click to collapse
does not work, JIO which works on only VoLTE.
When accessing the *#*#4636#*#* service menu (Testing) → Phone information, all the toggles for: VoLTE, Video Calling, WiFi Calling, EAB are off and greyed out (unable to be toggled on).
From the ... drop menu → IMS Service Status:
IMS Registration: Not Registered
Voice over LTE: Unavailable
Voice over WiFi: Unavailable
Video Calling: Unavailable
UT Interface: Unavailable

quakze said:
does not work, JIO which works on only VoLTE.
When accessing the *#*#4636#*#* service menu (Testing) → Phone information, all the toggles for: VoLTE, Video Calling, WiFi Calling, EAB are off and greyed out (unable to be toggled on).
From the ... drop menu → IMS Service Status:
IMS Registration: Not Registered
Voice over LTE: Unavailable
Voice over WiFi: Unavailable
Video Calling: Unavailable
UT Interface: Unavailable
Click to expand...
Click to collapse
See my picture

Feels damn fast but no second sim in S9

Can someone tell me why Lineageos Recovery is the only way to go?
And does it bring the same features as TWRP or is it really based for LineageOS?
Thanks for the info!
Since Magisk Guru is working for Google I hear a lot of complains about Magisk 24.
Does anyone have some good experience with Magisk 24 and rooting and hiding?

Mr-Dutch said:
Can someone tell me why Lineageos Recovery is the only way to go?
And does it bring the same features as TWRP or is it really based for LineageOS?
Thanks for the info!
Since Magisk Guru is working for Google I hear a lot of complains about Magisk 24.
Does anyone have some good experience with Magisk 24 and rooting and hiding?
Click to expand...
Click to collapse
I don't know the reasons (time/effort?), but TWRP doesn't support encrypted partitions which this rom forces.

Is there a list of working/non working features in this rom?

I just wanna say : This ROM is amazing, is blazing fast, super easy install flow, no problems at all; I have no seconds SIM to test however, in my phone the "App Switcher" from the bottom nav bar isn't working, I'm the only one? Keep the amazing work @DeHuMaNiZeD

Development [ROM][Unofficial][pdx225][13] Lineage 20 For SONY XPERIA 10IV

{
"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 our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-CC54 (If it does not work, please report below)
Make sure you have gone through the installation guide once before proceed!
Installation:
Extract the rom and the extract the payload and the continue with steps below (note usb does not work in recovery yet so transfer rom to sdcard)
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not 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
Flash the downloaded image files to your device by typing:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
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 LineageOS package
On the device, select "Apply Update", then "Apply from sd card" to begin flashing rom
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from sdcard", then chosse your packages in.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
https://drive.google.com/drive/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR?usp=sharing
Device Trees & Kernel Source:
https://github.com/XperiaBrickers-10IV/kernel_sony_murray
https://github.com/XperiaBrickers-10IV/device_sony_murray
https://github.com/XperiaBrickers-10IV/device_sony_pdx225
https://github.com/XperiaBrickers-10IV/vendor_sony_murray
https://github.com/XperiaBrickers-10IV/hardware_sony
Current Bugs:
None
Many thanks to:
@clfbbn
@loipuru
@WindowsDev0
@dylanneve1
@Sakuu
Special thanks to
Sony
@jerpelea
For sending me the device

If some moderator could make us a device forum that would be lovely

King081 said:
View attachment 5856369
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 our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-CC54 (If it does not work, please report below)
Make sure you have gone through the installation guide once before proceed!
Installation:
Extract the rom and the extract the payload and the continue with steps below (note usb does not work in recovery yet so transfer rom to sdcard)
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not 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
Flash the downloaded image files to your device by typing:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
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 LineageOS package
On the device, select "Apply Update", then "Apply from sd card" to begin flashing rom
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from sdcard", then chosse your packages in.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
http://GDrive
https://drive.google.com/drive/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR?usp=sharing
Device Trees & Kernel Source:
https://github.com/XperiaBrickers-10IV/kernel_sony_murray
Device Trees will be public soon
Current Bugs:
Sound does not work
screen flickers black
vibration does not work
USB doesn't work in recovery
takes about 3 buttton presses to get out of deep sleep
ENG build so you will get a red border
Many thanks to:
@clfbbn
@lolipuru
@WindowsDev0
@dylanneve1
Click to expand...
Click to collapse
What device is this ROM for?

TheWorldYT said:
What device is this ROM for?
Click to expand...
Click to collapse
pdx225 Xperia 10IV

Lovely! Was thinking of building by own with the open devices guide from Sony, but looks like you were faster
It really would be great if we have a device forum.

litelinux said:
Lovely! Was thinking of building by own with the open devices guide from Sony, but looks like you were faster
It really would be great if we have a device forum.
Click to expand...
Click to collapse
It's not sodp based, it's stock based

Could Be Anyone said:
Thanks for your hard work.
Looking forward to the bugs getting squashed.
Unfortunately my 10 IV is my only phone so can't help test since I need sound for work calling.
Glad the 10 IV is getting custom rom love, it's the smallest width device I could find to replace my broken XZ2C.
Click to expand...
Click to collapse
Yeah, don't worry it's my development device, so don't need testers, this is for those that like Trying stuff and mainly to get a forum

Join my telegram group for now https://t.me/Xperia007

King081 said:
It's not sodp based, it's stock based
Click to expand...
Click to collapse
How does that make a difference in terms of hardware / firmware support or elsewhere? I'm very new to ROM development, sorry if I sound stupid

litelinux said:
How does that make a difference in terms of hardware / firmware support or elsewhere? I'm very new to ROM development, sorry if I sound stupid
Click to expand...
Click to collapse
SODP tries to open source all the blobs, while stock based doesn't, due to the difficulty sodp is not really stable compared to stock base

Could Be Anyone said:
Thanks for your hard work.
Looking forward to the bugs getting squashed.
Unfortunately my 10 IV is my only phone so can't help test since I need sound for work calling.
Glad the 10 IV is getting custom rom love, it's the smallest width device I could find to replace my broken XZ2C.
Click to expand...
Click to collapse
Yup, it's the closest thing to my previous phone (xz5c) I can fond on the market! Even the outer frame feels similar.

Could Be Anyone said:
I miss the xperia compacts.
Got small hands and the compacts were perfect.
10 IV is all right but I wish the width was smaller, 65mm would be amazing.
I guess I should be thankful it's just 67mm and not 77mm like the newer google pixels
Click to expand...
Click to collapse
Lol me with the Google Pixel 7

Update available
Changelog:
Sound and Mic now working
download here at
https://drive.google.com/drive/u/0/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR

Update available
Changelog:
Vibration and SDM work so screen does not flicker anymore and does not take 3 button presses to wake display
Current Bugs:
camera
ENG build
download here at
https://drive.google.com/drive/u/0/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR
it is now a usable device,
device trees will be public today

Device Tree are now public link available on first post

Could Be Anyone said:
Thanks so much.
Will install and provide feedback.
Is there lineageos recovery? I couldn't find one.
Click to expand...
Click to collapse
You'd have to extract the payload.bin file and flash boot vendor_boot and dtbo in fastbootD then reboot to recovery and flash rom.zip

Could Be Anyone said:
Keep getting an error.
E:Signature verification failed
E:error: 21
Install from SD card completed with status 2
Installation aborted
Click to expand...
Click to collapse
That's weird never happened to me before

Could Be Anyone said:
Well that's weird since I followed your instructions to a T.
Could you port lineageos recovery as well? It'll fix this problem since the stock recovery doesn't have the option to bypass signature verification.
Click to expand...
Click to collapse
You didn't listen then, extract ROM zip extract payload.bin, then flash vendor_boot boot and dtbo then reboot to recovery (Los one) then flash rom zip

Could Be Anyone said:
I couldn't find the los recovery on the first page.
Click to expand...
Click to collapse
I just said to extract it

Could Be Anyone said:
Ah, I my bad, I thought it was just a normal zip you meant to install, sorry about that.
Click to expand...
Click to collapse
No worries lol

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

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

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

nice work !! thanks

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

Thank you for your work!

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

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

God bless you

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

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

Thank you for your efforts！

Thank you! You made this device 10x better!

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

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

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

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

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

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

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

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

Database Develop

welcome