Database Info

[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1

⚠ This project is no longer maintained. See below. ⚠
You are encouraged to migrate to the official nightly builds (huge thanks to @anishpratheepan and to the LOS team for bringing that up). If you update from an unofficial build, it is highly recommended that you opt-in for build signature check after the flash:
Open Settings
Privacy => Trust
Check "Build signature" at the very bottom
Note that you should be able to update from unofficial to official builds seamlessly, without wiping anything.
-----
{
"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 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock your bootloader
Backup everything, especially the "persist" partition
Make sure you're on a recent version of OxygenOS.
Download the latest build
Run the following commands:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot reboot recovery
Wipe all data from recovery.
(Optional) If you need GApps, NikGApps Core are known to work ("Apply update" => "Update from ADB", and then run adb sideload <NikGapps-xxx-arm64-11-yyy.zip>). Note that other variants than Core can crash.
Reboot.
Downloads:
https://drive.google.com/drive/folders/1V17qsn_wMpwPgJHMhCjfYYmZEPGzPvP2
Known issues:
Displays "Charging slowly" when it's actually not
Build signed with public keys for now
Reporting Bugs:
Make sure the bug you want to report isn't already known
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Since February 2021 (based on the official LineageOS device tree):
Device tree: https://github.com/LineageOS/android_device_oneplus_instantnoodle
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/TheMuppets/proprietary_vendor_oneplus
Before February 2021 (based on LuK1337's work on instantnoodlep with minor adjustments to the device tree):
Device tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/luk1337/proprietary_vendor_oneplus
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2021-01-07
Last Updated 2021-02-10

Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.

mattie_49 said:
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
Click to expand...
Click to collapse
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NikGApps are the best candidate.

KennyG9 said:
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NiksGApps are the best candidate.
Click to expand...
Click to collapse
Fair enough. Thank you for bringing this to the op8 community.

I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.

KennyG9 said:
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
Click to expand...
Click to collapse
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?

mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways.
I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to :
- get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
- extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py
- reboot to bootloader (adb reboot bootloader)
- flash the stock recovery you just extracted (fastboot flash recovery recovery.img)
- reboot into stock fastboot (fastboot reboot fastboot)
- flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………)
- follow LOS 18.1 flashing instructions from the first post

mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Spoiler
KennyG9 said:
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways. I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to : - get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300 - extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py - reboot to bootloader (adb reboot bootloader) - flash the stock recovery you just extracted (fastboot flash recovery recovery.img) - reboot into stock fastboot (fastboot reboot fastboot) - flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………) - follow LOS 18.1 flashing instructions from the first post
Click to expand...
Click to collapse
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with

SUPERUSER said:
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
Click to expand...
Click to collapse
I don't have a definitive answer to everything, but here are some remarks:
- Not sure what exactly your problems were and I'm unaware of any way to backup partitions using fastboot unfortunately. As far as I know, it was not possible to restore nandroid backups using mauronofrio's TWRP on Android 10 either. I think the best you can achieve for now is software and data backup (using "adb pull" and "OAndBackup+" or something else). I can also attest that I had way more weird partitioning issues when using TWRP than LOS' fastboot. Since I stopped using TWRP, I never had to use MSM again.
- What you may attempt to reduce the risk of bricking your device is to take advantage of the A/B partitioning. You can flash everything on the unused slot and switch back to the working slot if anything goes wrong. This can be done by running "fastboot getvar current-slot" to get the current slot, then "fastboot --set-active=a" to switch to slot a (or "fastboot --set-active=b" to switch to slot b, depending on which slot was active).
- I second your reluctance on using tools coming from untrusted sources. Please, don't get fastboot/adb from XDA, use the official Android builds. I can't help you regarding the drivers as I use Linux which ships with drivers, but if you use Windows try to get those drivers from either Microsoft, OnePlus or Qualcomm directly. My instructions to avoid flashing Android 11 with MSM makes you use an official image from OnePlus (which you have to trust anyways) + an open-source tool that's made by LOS developers (which you have to trust anyways). At this point, I think the weakest point of trust if you don't want to build LOS yourself is me.
- Regardless of what you attempt, always make sure you have backups of your valuable data, apps and persist partition. Especially given how capricious this device is .

working great so far. any way to re-enable the 90Hz refresh rate?
edit: found it in display options!

LuK1337 said:
OP8 is no longer supported so RIP.
Click to expand...
Click to collapse
New flash method for both 8p and 8t does not allow to use it on instantnoodle, migrated yesterday from there to this build and it's working perfect with NikGapps-core and Magisk, great job @KennyG9

any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?

Does OnePlus 8 tmobile version work with dual sim on this rom?

veridiam said:
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Click to expand...
Click to collapse
There's a lot of proprietary software/firmware (apart from the camera apk itself) that its not included in LOS. There have been some ports in the past (e.g. OnePlus6 OOS Camera port or oxy-ify) but all of them seem dead, maybe because google camera port working out of the box.
Creating a magisk module should be doable, but you need to start the app, let it crash and add the missing dep N times until you have all of them

@LuK1337 , please accept pull request: https://github.com/luk1337/android_kernel_oneplus_sm8250/pull/1

Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.

passion8059 said:
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
Click to expand...
Click to collapse
Thanks, just updated first post to mention that.

KennyG9 said:
Thanks, just updated first post to mention that.
Click to expand...
Click to collapse
Would you be able to look into face unlock? Handy feature for me especially at work.

passion8059 said:
Would you be able to look into face unlock? Handy feature for me especially at work.
Click to expand...
Click to collapse
Face unlock is an OxygenOS feature and I don't think AOSP or LineageOS supports something like that officially as it's quite terrible security-wise. GApps also dropped support for face unlock in Android 10 because of security concerns. So unless I'm missing something it probably won't happen anytime soon unless through some third-party module, sorry. It's not just about porting some blobs, it's a whole new OS feature.

Is WiFi calling and LTE calling working?

[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos

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

Requirements:
Any Q or 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
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!

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

This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com

KiwiNote+ said:
This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com
Click to expand...
Click to collapse
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)

Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL

PortentousLad said:
Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL
Click to expand...
Click to collapse
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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...
forum.xda-developers.com
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)

Linux4 said:
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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...
forum.xda-developers.com
Click to expand...
Click to collapse
...Well that explains it I guess.
Linux4 said:
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Click to expand...
Click to collapse
yeah... the wrong one.
Linux4 said:
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Click to expand...
Click to collapse
that was me being more stupid and no I did not try to boot before.
Linux4 said:
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)
Click to expand...
Click to collapse
that does nothing. I'll keep trying a bit before I move one.
Thanks for your quick response anyway.

I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)

stenncell said:
I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)
Click to expand...
Click to collapse
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed

Linux4 said:
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed
Click to expand...
Click to collapse
i joined the telegram group... i will try to install again.

Linux4 said:
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)
Click to expand...
Click to collapse
Thanks for providing the ROM! Does it support signature spoofing?

tempe222 said:
Thanks for providing the ROM! Does it support signature spoofing?
Click to expand...
Click to collapse
I don't include out-of-tree patches, sorry
However in my S10 Series thread there's another solution for this one
Anyways, read the OP, download links are taken down temporarily as some users apparently had problems with getting it to boot
Will be up again next week hopefully (will get a device myself by that time)

Fixed builds are now up

Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?

Donkey666 said:
Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?
Click to expand...
Click to collapse
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"

Linux4 said:
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"
Click to expand...
Click to collapse
@Linux4
I managed to install your version, its more stable than ivans version so thank you man great job, on ivans version had microphone issues and telephoto2x did not work, this one feels very good and probably usable as a daily driver phone..
I have a question for you, is there a way to add option in settings that blocks notification&quick-access-tiles from being accessed from locked screen?
And S-pen question: is there a way to make keyboard appear when I tap whit S-pen on txt field (it puts cursor there but keyboard does not apper until I tap there with finger.)

@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete

Donkey666 said:
View attachment 5367685
@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete
Click to expand...
Click to collapse
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe

Linux4 said:
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe
Click to expand...
Click to collapse
Yea you are right, I did pay closer attention to S-pen behavior and you are right, it is basicaly a mouse.. And issue solved, had magnetic case and that messed up S-pen behavior..

[GUIDE][RECOVERY] TWRP 3.6.0_9-0 Custom Recovery for Lenovo Tab3 8 | TB3-850F/M

{
"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"
}
Lenovo Tab3 8 Tablet
Models: TB3-850F/M
TWRP 3.6.0_9-0​OVERVIEW
The TWRP ports currently available for the Lenovo Tab3 8 are outdated by a number of years and are lacking in official support for more recent Android release versions. TWRP 3.6.0_9-0 was originally compiled using the Android 9 tree, and therefore supports all Android versions up to, and including, Android 9 Pie. This custom recovery build also includes improved manageability of Android supported filesystem standards, better protection against data loss and corruption, added functions, and improved theming support. Likewise, I've made several bug fixes and cleaned up the codebase. To read a more in-depth list on the changeling of TWRP 3.6.0, visit this link the official TeamWin site here: TWRP 3.6.0 Release Notes
REQUIREMENTS
First and foremost, you need an unlocked bootloader. There are a plethora of guides hosted here on XDA that provide detailed instructions for standard bootloader unlocking. If your tablet is not yet unlocked, go ahead and complete that task and return here once finished. Secondly, you will need a Windows PC or laptop with the SDK platform tools installed or, alternatively, the Minimal ADB & Fastboot tools (link provided below). Note that a Linux or Mac machine may also be used; for purposes of this guide, however, I will be focusing solely on a Windows setup. Next, you will need an internet connection to download the files provided in the links below. Lastly, you will need the factory supplied or a quality equivalent USB-A to micro USB data syncing/charging cable.
COMPATIBILITY
This TWRP custom recovery is compatible with both hardware variants (80 & 81) of the TB3-850F model, as well as the TB3-850M 4G-LTE supported model.
DISCLAIMER
Installing a custom recovery on an Android mobile device is an invasive procedure in terms of the modifications made to the stock partition index. Flashing the partitions of your device is a task that encompasses the inherent risk of bricking or otherwise rendering your device inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your tablet. Follow the instructions carefully, employ some patience, and things should go smoothly. I would encourage inexperienced members to read this guide in full prior to starting the instructions.
INSTRUCTIONS:​
Download the Minimal ADB & Fastboot tools from the below link and install the program on your Windows PC & laptop. Next, open your Windows File Explorer, open your C: drive, then open Program Files x86. Copy the Minimal ADB & Fastboot folder and paste it to your desktop. (Copying the directory to the desktop isn't required, but does configure the ADB & Fastboot path to a more convenient directory from which to work);​
Download TWRP 3.6.0_9-0 from the below link and save the image file in your ADB & Fastboot folder on your computer;​
Boot your tablet into fastboot mode as follows: with your tablet booted into the Android OS, ensure ADB Debugging is enabled in the Developer Options menu. Connect the tablet to your PC using a sufficient USB-A to micro USB syncing/charging cable;​
Open the ADB & Fastboot folder on your computer. Double click cmd-here.exe to open a command window, and execute the following command:
Code:
adb reboot bootloader
Your tablet may prompt you to authorize the ADB connection;​
If properly connected your Tab3 8 will boot into fastboot mode, which will be indicated by the status displayed on the tablet. To verify proper fastboot communication between your computer and tablet, execute this command:
Code:
fastboot devices
If everything is set up properly, the command window will return an alphanumeric string consistent with your tablet S/N;​
If your S/N isn't displayed, or if your are given a WAITING... notification, your tablet is not being recognized correctly. Change USB ports, try a different data syncing cable, and/or update your fastboot drivers;​
Once a solid connection has been verified, execute the following command to flash TWRP to your tablet:
Code:
fastboot flash recovery twrp.img
(The TWRP file you downloaded below is named twrp.img. The above flashing command assumes that you have left the filename unchanged.);​
You may now boot your tablet into TWRP recovery mode by executing:
Code:
fastboot boot twrp.img
​
Task complete. You should now running TWRP 3.6.0_9-0 on your Lenovo Tab3 8 device. ​
DOWNLOADS:
• TWRP 3.6.9_9-0 Lenovo Tab3 8
• Minimal ADB & Fastboot Tools v1.4.3
THANKS & MENTIONS:
First and foremost, thanks to TeamWin Recovery Project for providing the base build, and for their many years of hard work and contributions to the custom Android community. Thanks to the XDA members who remain dedicated to the Lenovo Tab3 8 and its continuing development projects. Although I'm slow, I have two more projects in the works for our beloved tablets. Thank you for your patience my friends.​BUGS:​Please leave a comment detailing any bugs or instabilities you may encounter. I will diligently try to patch and fix any reported bugs.​

Hi,
I flashed TWRP v3.4.1-0 from your link but I end up in a boot loop where I fail to mount any of the partitions.
The DL Link for TWRP v3.6.0_9-0 seems to be broken. Do you have an alternate for that?
Note: I'm working on a TB3-850F.
Thanks!

Okay I think dm-veriry is to blame. If you mounted /system after installing TWRP, dm-veriry will be triggered and the device will boot loop.
You need to flash a dm-verity disabler. I'll get you a link .

Any chance you might also have a link to the updated twrp you had linked above? It's a dead link now.

Diznatch52 said:
Any chance you might also have a link to the updated twrp you had linked above? It's a dead link now.
Click to expand...
Click to collapse
Sure. I'll fix the link

Ok link is fixed. Follow these steps.
Warning: This will wipe all data from your device.
Download the no-veriry_opt encrypt file linked below and save it to an external micro SD card. Insert the micro SD in your TB3-850F;
Install TWRP v3.6.0_9-0 and reboot recovery;
Select Wipe, Format Data, and swipe to commence.
Select Install and navigate to the saved location of the no-verity zip you downloaded in Step 1. Select the zip and swipe to commence installation.
Reboot system
no-verity_opt-encrypt_v6.1.zip
If you want root access of the Android OS, install a Magisk systemless root script after Step 4.

Awesome! I'll give it a shot.

Diznatch52 said:
Awesome! I'll give it a shot.
Click to expand...
Click to collapse
Download Magisk v24.3 from this link https://mega.nz/file/4c43FbwS#Qd-pKoupa8LZ-EI9qe5Zsr3L4rSz8NDv2Ojknrd8sCk
Install it after Step 4 if you want root. After you are booted, you can update Magisk to the latest v25.2 using the Direct Install option.

For some reason, after this process, running `adb reboot recovery` brings me to an android crash screen. Any idea why?

To confirm, this procedure did work and you were able to boot into the OS? Once you confirm I'll try to resolve your ADB issue.

Yes.

Diznatch52 said:
Yes.
Click to expand...
Click to collapse
Ok download the official TWRP App, grant it root permission, and flash the TWRP v3.6.0_9-0 to the recovery partition. Reboot your tablet and then try the adb reboot recovery command again.
When you flashed the original TWRP with fastboot, did you immediately boot into recovery and flash TWRP again using the Install>Image option?

As soon as I unbrick this again, I'll give it a shot
Edit: booting into recovery now gives me twrp! Thanks so much!
Now time to see if I have better luck flashing lineageOS

IT WORKED!
Thank you so much!

Anytime friend. Glad it worked out.

Update: December 13, 2022.
I am presently working on bumping TWRP up to v3.7.0_9-0.
The v3.7.0 base build includes Python support for Android Oreo & newer versions.; keymaster API V1 fixes; fixes on copying sepolicy on devices with no /vendor partition; several fixes on custom theme support as well as perfected ROM multiboot functionality. Also, I am updating my implementation of PIGZ compression for data transfer speed improvements and enhanced protection against data corruption. Stability improvements and minor bug fixes also included.
I will keep the OP updated with an ETA.

Diznatch52 said:
IT WORKED!
Thank you so much!
Click to expand...
Click to collapse
I have a build of LineageOS 14.1 that I optimized, fixed some bugs and removed settings entries on SIM cards & mobile networks. Open source libraries have been updated and the security patch level bumped up to June, 2022. GApps have been removed and several performance enhancements have been added. I'm without a working 850F at this time, but I should have a working device soon. I will post the LOS 14.1 build as soon as I can fully test it.

Diznatch52 said:
IT WORKED!
Thank you so much!
Click to expand...
Click to collapse
I have a build of LineageOS 14.1 that I optimized, fixed some bugs and removed settings entries on SIM cards & mobile networks. Open source libraries have been updated and the security patch level bumped up to June, 2022. GApps have been removed and several performance enhancements have been added. I'm without a working 850F at this time, but I should have a working device soon. I will post the LOS 14.1 build as soon as I can fully test it.
Oh, I nearly forgot, would you care to list your stock firmware build number please. Thanks

That would be incredible. I don't know if I still have access to my stock firmware build. I've already got a version of LOS 14.1 (could admittedly be snappier) installed. If you tell me how to find it, happy to send it over.

I just meant on your 850F, go to device settings, about tablet, and let me know your build number. Thx

[oneplus3/t][Official] Droidian (Debian Bookworm) for OnePlus 3/T

Code:
/*
* 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.
*/
{
"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"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones.​This is accomplished by using well-known technologies such as libhybris and Halium.​​## What works​
WIFI
Audio
Video Playback
USB-OTG
Cellular Data
Calls/SMS
Bluetooth
Wireguard
Flashlight
GPU (Works well in WayDroid, partially in Droidian)
See full list here
## What doesn't work​
Camera
VoWifi
You tell us
Old UNOFFICIAL installation steps
Spoiler
This steps and UNOFFICIAL build of droidian have been abandonned and is deprecated, you're on your own there ! We recommand to follow official steps below​
## Required Files​
ADB commands and stuff
TWPR Treble : https://mega.nz/folder/UgdQRYSD#8s-_u2HJQZDEqNnFOnejxQ
You'll find it in : Recovery_(System-As-Root_Compatible) > twrp-op3treble-3.3.1-1.img
Latest firmware for your phone (at the writing time: 9.0.6) : https://github.com/nvertigo/firmware-3t/tree/master/archive (like version oxygenos-9.0.6-no-alipay-firmware-3.zip or oxygenos-9.0.6-firmware-3.zip if using a OP3)
WARNING ! Firmware are device-specific, be careful to take a OP3 or OP3T depending on your device !
LineageOS Treble: https://drive.google.com/drive/folders/1vnJEKkhO3xqH-fWWG55-yxwx5K1EeKq7
You only need the file LineageOS Treble
droidian-api28-arm64.zip : https://github.com/droidian-images/droidian/releases
NOTE: As we are flashing LineageOS 16 (android 9), pay attention to use and flash Droidian API28 (which is the version for Android 9)
Please do not use generic halium anymore, @Bettehem made a special version combining both files for OnePlus 3/T here : https://gitlab.com/Bettehem/op3-halium-waydroid Please prefer this version
Below, generic halium files that this tutorial does not recommend
halium-boot.img : https://mirrors.lolinet.com/firmware/halium/oneplus3/halium-boot.img
halium-ramdisk.zip : https://mirrors.lolinet.com/firmware/halium/GSI/tools/halium-ramdisk.zip
GSI patch by @Bettehem : https://gitlab.com/Bettehem/op3-gsi-fix-droidian
You can have alpha version from CI/CD artifact : https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
## Installation​
First treblize your phone with the instructions from here: https://github.com/OP3-Halium/Documentation#treblelizing-your-op3t--firmware--twrp
Basically, all you have to do is :
Flash the special TWRP Treble previously downloaded
Boot it up and go to "Advanced" -> "Terminal", Type treblize and run
Reboot to recovery
Click to expand...
Click to collapse
Then follow the instructions here: https://github.com/OP3-Halium/Documentation#installing-using-erfan-gsi
Basically after you've treblized your device and installed the latest firmware, the install steps are as follows:
Flash the custom LineageOS Treble,so you get the /vendor partition populated.
Reboot to check that everything works. If so, reboot back in to recovery.
Go to advanced wipe and wipe everything except /vendor.
Reboot back into recovery.
Flash the droidian .zip (adb sideload droidian-api28.zip)
Deprecated steps
Flash halium-boot.img
⚠ This shouldn't be done with adb sideload, instead use those two lines :
adb push ./halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Flash halium-ramdisk.zip.
Now just flash @Bettehem's halium-boot.img
Flash @Bettehem's op3-gsi-fix-droidian.zip
⚠ Do NOT flash the regular op3-gsi-fix.zip which is for ubports and not this project ⚠
### Out of storage​A note from @Bettehem 's GSI fix :
It was made possible to move the user's home dir to the phone's userdata partition, so you can utilize the full 64/128GB storage on the device. By default when you install Droidian, the user's home dir is on the 8GB system image, and that's not very much space for both the OS and your home dir
So after installing and booting the device, you can perform the first time setup if you want or skip it for now. Then open a terminal and run the command move-home
Click to expand...
Click to collapse
OnePlus3 is officially supported by Droidian now, here's the updated step by step install :
## Required Files​
Download the latest recovery flashable zip droidian-OFFICIAL-phosh-phone-oneplus_oneplus3-api28-arm64_XXXX.zip: https://github.com/droidian-images/droidian/releases
## Installation​The step-by-step installation comes from this guide : https://github.com/Droidian-oneplus3/device-page#requirements
Treblize your device:
Instructions here: https://forum.xda-developers.com/t/treble-unofficial-lineageos-16-0-treble-for-oneplus-3-3t.3830455/
After you have installed the custom twrp and you have a /vendor partition, install the custom LineageOS 16 build from the guide.
With LineageOS 16 installed, reboot and verify that everything works. Then reboot back into TWRP.
In TWRP, go Wipe -> Advanced Wipe -> Select everything except Vendor and USB-OTG, then Swipe to Wipe.
Reboot into recovery
Flash the droidian .zip using the recovery's install menu or adb sideload
Reboot
Congrats, you're all done, just restart your phone and enjoy using Droidian
## Troubleshoots​
It had been reported some failing with the sideload function to flash parts of this tutorial.
If you enconter those problems, we recommend you to push the files to the device using adb push /path/to/your/file /tmp/ and then use TWRP's own install method
## Notes:​
### First boot​The first boot can take up to 30 seconds. If you see the green droidian's logo on boot, don't worry for the following black screen, just your phone doing its stuff. Once you're os finally booted and ready to use, you'll have the screen showing time and icons.
### Default password​The default password is 1234.
### Wrong UI scale​Some applications aren't designed to fit well on to tiny mobile screens, so if you encounter a problem where buttons/text doesn't properly fit on the screen, do the following:
1. Open the application which doesn't fit well on your screen
2. Open the Mobile Settings application and navigate to the Compositor menu
3. Turn on the toggle for the application which doesn't scale well
Now every time you open the application, it should get scaled down to fit your screen.
### Status
Droidian GSIs are experimental! Bugs and missing features are expected.
OnePlus 3 isn't officially supported by Droidian
OnePlus3 is offically supported since 19/06/2023
@Bettehem's patch is a WIP
### SSH access​Connect your phone to your computer and type ssh [email protected]<OP3-WIFI-IP>, the password is 1234
### Applications​You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
# Credits​
Thanks the Droidian team and the Mobian team for bringing Debian on mobile https://droidian.org | https://mobian-project.org
Thanks to the HaliumProject for all the hard work they do making this whole possible https://halium.org
Thanks to everyone contributing on https://github.com/OP3-Halium for those comprehensive tutorials
Thanks to simonsmh, dianlujitao, chenxingyu, for working and building the LOS Treble (Source Code: https://github.com/OP3Treble )
A huge and special thanks to @Bettehem (Telegram, Gitlab, XDA) for developing the patch and did help me to have it up and running on my phone
Thanks to you for giving a try to this and following this tutorial

# Troubleshooting​## WiFi not connecting​Droidian detects two wifi cards, and only one seems to work at a time.
If Droidian is trying to connect using the wrong card, you can easily change it by running the command nmtui, then select "Activate a connection" and then select the WiFi network you want to connect to.
## Mobile data not working​In settings go to mobile network and press the "Unlock" button. Then close the settings app and open again, because the UI doesn't get updated automatically.
You should now be able to manage your mobile connection from here. To get correct Acces Point Name (APN) settings for your carrier, look here: https://apn.how
After you have set up the APN settings, then just toggle the "Mobile Data" setting off and back on again. If mobile data still doesn't work, you may want to restart the ofono service by running this command: sudo systemctl restart ofono.service. Then reopen settings and toggle the "Mobile Data" setting off and on again.
## Changing audio device​There's a known issue with changing the audio device inside the Settings app. You can use something like pavucontrol, ncpamixer or even just run pactl/pacmd commands directly.
You need to change the sinks port from the primary_output sink for it to work. Changing the port from the deep_buffer sink doesn't work.
# Random screenshots​

I'm working on getting this installed. Can't seem to get past bootloader (oneplus icon).
Attempting to build on my system and see if that helps.

@undrwater Are you on OP3 or OP3T ? And did you exactly follow each step for the tutorial ? 'cause it all worked fine for me ^^"

RoiArthurB said:
@undrwater Are you on OP3 or OP3T ? And did you exactly follow each step for the tutorial ? 'cause it all worked fine for me ^^"
Click to expand...
Click to collapse
I'm on 3t. And while I have some confidence that I followed the directions exactly, there's room for doubt.
I'll try again when I can look at it without distractions.

undrwater said:
I'm on 3t. And while I have some confidence that I followed the directions exactly, there's room for doubt.
I'll try again when I can look at it without distractions.
Click to expand...
Click to collapse
The problem may come from the firmware link I did put before. It wasn't for 3T, so I just updated it and it would prevent similar errors
Please tell me when you'll retry and if now it works well

Actually, looking somewhat closer, I think the issue is finding the correct droidian zip to sideload. several are available, and the few I've tried fail with:
E: No hybris-mobian image found
Click to expand...
Click to collapse
/vendor is populated, lineage is flashed and booted halium boot image dd'ed.

undrwater said:
Actually, looking somewhat closer, I think the issue is finding the correct droidian zip to sideload. several are available
Click to expand...
Click to collapse
Hey, the good version is Droidian API 28 ('cause you're using a base Android 9) ARM64 (which is the Snapdragon in OP3/T)

My OP3 seems to boot into droidian but I have no display, I can tell booting finished because I get sounds when I adjust the volume or connect a charger. Does anyone have an idea why this might be?
Steps I took:
- Flashed latest firmware
- Installed treble TWRP
- ran treblize in TWRP console
- wiped all partitions with advanced wipe (including vendor)
- sideloaded / installed lineage 16 zip and rebooted to test
- wiped all partitions other than vendor in TWRP
- sideloaded / installed "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip"
- installed hallium-boot in bootloader using "fastboot flash boot hallium-boot.img"
- rebooted

the-blind-bandit said:
My OP3 seems to boot into droidian but I have no display, I can tell booting finished because I get sounds when I adjust the volume or connect a charger. Does anyone have an idea why this might be?
Steps I took:
- Flashed latest firmware
- Installed treble TWRP
- ran treblize in TWRP console
- wiped all partitions with advanced wipe (including vendor)
- sideloaded / installed lineage 16 zip and rebooted to test
- wiped all partitions other than vendor in TWRP
- sideloaded / installed "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip"
- installed hallium-boot in bootloader using "fastboot flash boot hallium-boot.img"
- rebooted
Click to expand...
Click to collapse
Hi, you need to install op3-gsi-fix-droidian.zip to get it working on the OnePlus 3.
You can download it from here: https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
So after flashing the droidian-api28-arm64.zip, just flash op3-gsi-fix-droidian.zip and you should be good to go.
Also remember to run the move-home command in terminal after booting for the first time. It will allow you to use all of the storage on the device

Bettehem said:
Hi, you need to install op3-gsi-fix-droidian.zip to get it working on the OnePlus 3.
You can download it from here: https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
So after flashing the droidian-api28-arm64.zip, just flash op3-gsi-fix-droidian.zip and you should be good to go.
Also remember to run the move-home command in terminal after booting for the first time. It will allow you to use all of the storage on the device
Click to expand...
Click to collapse
Thank you. I'm not sure how I missed that in the OP, I saw the bit in red for step 7 and just stopped there I guess
Anyway it's working now and OMG it's actually kinda good. Last time I tried a linux distro for an android phone, which wasn't that long ago, it froze almost all of the time. This seems quite responsive and actually has quite a good keyboard too. My hope for linux on phones (other that android) has been restored

the-blind-bandit said:
Thank you. I'm not sure how I missed that in the OP, I saw the bit in red for step 7 and just stopped there I guess
Anyway it's working now and OMG it's actually kinda good. Last time I tried a linux distro for an android phone, which wasn't that long ago, it froze almost all of the time. This seems quite responsive and actually has quite a good keyboard too. My hope for linux on phones (other that android) has been restored
Click to expand...
Click to collapse
Yeah I like Droidian quite a lot. I have been using it as my daily driver for some time now. Only camera doesn't work but hopefully I'll solve that issue at some point in the near future

I'm having problems with installing.
I followed the steps as instructed, treblized the phone (3T) and installed Linage 16. Lineage is booting fine. I checked the vendor partition which is populated.
After the wiping step (vendor left untouched) I installed droidian (tried droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip and droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20221003.zip) and halium-boot.img. I also installed the patch "op3-gsi-fix-droidian.zip".
Droidian isn't loading. When using the halium-boot.img (15.41 mb) linked in this thread, the phone shows the bootscreen (1+) and reboots after some time. Using the halium-boot from this instruction: https://github.com/OP3-Halium/Documentation (15.8 mb) the phone just shows the 1+ logo without rebooting ...
what am i missing?

prosch said:
I'm having problems with installing.
I followed the steps as instructed, treblized the phone (3T) and installed Linage 16. Lineage is booting fine. I checked the vendor partition which is populated.
After the wiping step (vendor left untouched) I installed droidian (tried droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip and droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20221003.zip) and halium-boot.img. I also installed the patch "op3-gsi-fix-droidian.zip".
Droidian isn't loading. When using the halium-boot.img (15.41 mb) linked in this thread, the phone shows the bootscreen (1+) and reboots after some time. Using the halium-boot from this instruction: https://github.com/OP3-Halium/Documentation (15.8 mb) the phone just shows the 1+ logo without rebooting ...
what am i missing?
Click to expand...
Click to collapse
Hi, this tutorial recommand using Bettehem's halium-boot file.
If you did checked the Github's documentation, you should have saw a note part for flashing the halium-boot.zip ( https://github.com/OP3-Halium/Documentation#note ) describing 3 differents methods to do it. Did you follow them all or how did you do it ? It may be recommended to use the old technic :
Flash halium-boot.img ⚠ This shouldn't be done with adb sideload, instead use those two lines :
Code:
adb push ./halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Click to expand...
Click to collapse

I used fastboot and the TWRP push method, no difference. I used all the files linked in this tutorial and all of those in the github documentation. After flashing, when rebootIng, TWRP complains that there is noch OS installed... Lineage Installation is no problem. I just tried the ubports installer to install Ubuntu Touch. This stops while pushing the files... Installing OxygenOS works... kinda strange
Update: It's working now. I also had to do "format data / factory reset" after step 2 and repair the fs of cache, system and data to ext4 after rebooting. Using the files from the OP3-Halium-Documentation Droidian is now loading.

I'm installing Droidian, but for some reason I'm getting a booting Ubuntu Touch. I flash in the following order:
* wipe everything but /vendor
* `ubports_GSI_installer_v10.zip`
* `droidian-devtools-api28-arm64_20220804.zip`
* `op3-gsi-fix-droidian.zip`
If I try to wipe `/system` before flashing `droidian-devtools-api28-arm64_20220804.zip`, I'm getting an error: `No hybris-mobian image found`
What am I doing wrong?

marmistrz said:
I'm installing Droidian, but for some reason I'm getting a booting Ubuntu Touch. I flash in the following order:
* wipe everything but /vendor
* `ubports_GSI_installer_v10.zip`
* `droidian-devtools-api28-arm64_20220804.zip`
* `op3-gsi-fix-droidian.zip`
If I try to wipe `/system` before flashing `droidian-devtools-api28-arm64_20220804.zip`, I'm getting an error: `No hybris-mobian image found`
What am I doing wrong?
Click to expand...
Click to collapse
You shouldn't be installing ubports_GSI_installer if you want Droidian. UBports is Ubuntu Touch.
To get Droidian running, follow the instructions on this page or https://github.com/OP3-Halium/Documentation#installing-droidian
For Droidian, you shouldn't be using ubports or droidian-devtools, as neither of those are used in this installation.
droidian-devtools is optionally used with very old droidian images and is not at all needed in the newer ones so don't use it.

Hi, I installed droidian on op3t as described, it works from beginning. I used "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip" an made an "apt-get (update, upgrade, dist-upgrade) to get the latest bookworm version.
The only problem atm: the phone cannot suspend. The blue LED blinks and if it ends the screen with the PIN login turns on (that does happen in a loop). Any hints?

sfoslino said:
Hi, I installed droidian on op3t as described, it works from beginning. I used "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip" an made an "apt-get (update, upgrade, dist-upgrade) to get the latest bookworm version.
The only problem atm: the phone cannot suspend. The blue LED blinks and if it ends the screen with the PIN login turns on (that does happen in a loop). Any hints?
Click to expand...
Click to collapse
Hi, I'm not sure why it does that but I'll try to investigate

Bettehem said:
Hi, I'm not sure why it does that but I'll try to investigate
Click to expand...
Click to collapse
If I remember right it could sleep if I disable wifi. I tried to work around with a script running 'onsuspend' but had no luck, always a probleme because the wifi adapter was shown twice in phosh settings.

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

{
"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 here.
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. 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 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 2201123G (cupid)"
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.
All kernel related source code can be found here.
Device trees for LineageOS can be found here.
Donate to support development:
Donate via PayPal to ArianK16a
Donate via PayPal to LineageOS

MiuiCamera for LineageOS on Xiaomi 12
I have created a Magisk Module to get the MIUI camera app on LineageOS 20. It's extracted from MIUI V14.0.2.0.TLCMICM.

For "new" users you could also give a step by step instruction how to update. Because format data is not always necessary.

i get " low resource device detected" error when trying to install Gapps

Will go official?

McFlypants said:
For "new" users you could also give a step by step instruction how to update. Because format data is not always necessary.
Click to expand...
Click to collapse
I will add that soon
quardier said:
i get " low resource device detected" error when trying to install Gapps
Click to expand...
Click to collapse
That's because the system partitions use erofs, a read only file system without reserved space. You can use the GMS variants if you want to use Google services or install Google apps that use overlay over the partitions.
vyvy said:
Will go official?
Click to expand...
Click to collapse
I aim to get this official one day in future, but this is not really close yet because of a different builds process due to GKI compliance which isn't supported officially in lineage.

outstanding work from the ROMs developer. thank you for bringing stable Lineage to our device

Xiaomi 12 currently no Lineage ROM bug?

Kkjin said:
Xiaomi 12 currently no Lineage ROM bug?
Click to expand...
Click to collapse
It has an error - cannot install Gapps, in TWRP it throws error 1

funciona no redmi note 12 4g?
Mod translation: it works not redmi note 12 4g?

Jadson note12 4g said:
Mod translation: it works not redmi note 12 4g?
Click to expand...
Click to collapse
Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50

Volte und voWifi calls sometimes show a strange number format.
Sometimes it's the caller number and my own number after each other, sometimes it's both numbers with a & or a + inbetween.
Even if the contact is known, the number in wrong format is shown.
Any help? I'm still on the 20230316 build. Is it fixed on the newest one?

NeoArian said:
MiuiCamera for LineageOS on Xiaomi 12
I have created a Magisk Module to get the MIUI camera app on LineageOS 20. It's extracted from MIUI V14.0.2.0.TLCMICM.
Click to expand...
Click to collapse
Is it possible to make the Xiaomi Leica camera inbuilt? Or a Magisk Module of the Xiaomi Leica Camera App?

Someone tried NFC payment and banking apps with this ROM ? Thank you