Database Info

[ROM][OFFICIAL][discovery][11] LineageOS 18.1

{
"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 :
https://wiki.lineageos.org/devices/discovery
Downloads :
https://download.lineageos.org/discovery
Reporting Bugs
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:

[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261769960 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?

banbenggengxin
Hello, I started to use this ROM for my H4233 on October 1st. At present, I mainly use the WeChat camera and there will be problems. Seeing that the download address has been updated to the 20201011 version, can I post a change log on this page after the version is updated? Thanks for the above from Google Translate
你好 我10月1日左右开始给我的H4233 使用该ROM 目前主要是使用微信相机会有问题，看到下载地址已经更新到了20201011版本能否在版本更新后在该页面 发布一个更新日志呢 ，谢谢

Hi, someone did install the rom? Any benefits compare to the 17.1

so i installed it, but it shows me LOS 17.1 and not 18.1.. whats the point??

ok, forget it, it was the problem of the internal recovery of LOS. It shows the sideload, but it has strange effects, or no effect. With TWRP it works. But now i try E os

there are no opengapps available for android 11, what gapps to get (similar to opengapps micro) please?

found nikgapps .
but theres another problem
after wiping everything from recovery, installing gapps - it boots in OS everything is okay, then I install magisk (21.00) from recovery but I cant boot anymore, I get bootloop?
Any ideas please?

maxis123 said:
found nikgapps .
but theres another problem
after wiping everything from recovery, installing gapps - it boots in OS everything is okay, then I install magisk (21.00) from recovery but I cant boot anymore, I get bootloop?
Any ideas please?
Click to expand...
Click to collapse
yeah you need a modded version for 11. Theres a modded magisk floating around the oneplus 7 pro forums somehwere

sorry for double post but heres the magisk link
[ROM][Android 12L][OP7Pro] crDroid v8.12 [19.12.2022]
Does anyone have the magisk download links from the third post? They're not showing up on the new website.
forum.xda-developers.com
should be second post

I upgraded my phone H3223 from Android 9 to this version. Using TWRP. Before update I applied Sony AOSP 11 https://developer.sony.com/file/download/software-binaries-for-aosp-android-11-0-kernel-4-14-nile/
I used NIKgapp.
NikGapps - Browse /Releases/NikGapps-R at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
I didn't wipe my data , after installing this version and NIKgapp , I rebooted and I have version lineage_discovery-userdebug 11 RQ1A.201205.008 eng.luk.20201212.191949 dev-keys
All existing apps are working after update.
Camera is working , only problem that I have is microphone . Randomly mic is so low or does not work for some applications. I have to reboot to fix this and this problem happens everyday.
Also up and down audio volume keys sometime donot work .
I noticed after upgrade to this Android version I have a program called AudioFX . I turn it off and on but the problem with microphone happens .

Hi!
I installed LOS 18.1 on my sony XA2 ultra H4213, but i have the following problems that i could not solve, even after deleting the cache:
- no sound for media (videos, music, telegram ...) the rest of the sound works well (buzzer, call ...)
- and all videos stuck.
Do somebody has an idea?
Thanks!

I reflashed android pie and the sound / videos work well again, but i can not install LOS now
no possibility to get to recovery mode and no fastboot drivers for the H4213. I even forgot how could I install it in the past... maby the recovery mode was working.

HowTo upgrade from 17.1 (make sure your computer has working "adb" (setup instructions can be found here):
1. Download the latest Lineage build and Lineage recovery from here. Optional, if you need Google apps, it can be obtained from here.
2. Run "adb reboot sideload"
3. Run "adb sideload /path/to/zip" (inserting the path to your LineageOS package).
4. If you need Google apps: Advanced -> Reboot to Recovery -> [when the device reboots] -> Apply Update -> Apply from ADB, then sideload gapps "adb sideload /path/to/zip". Reboot.
5. Start your device with new installed LineageOS, set the minimal startup settings. Open developer options (to unlock it: "Settings" -> "About phone" -> tap 7 times on "Build number") and enable ADB interface ("Settings" -> "System" -> "Developer options" -> "Android debugging").
6. Download Magisk from here, and install it "adb install Magisk.apk" (replace Magisk.apk with the appropriate filename).
7. Copy Lineage recovery file to your device (for example, to the Download folder).
8. Open Magisk app on the device and tap "Install" button in the Magisk card. Choose “Select and Patch a File” in method, and select the Lineage recovery file you copied previous step.
9. The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img
10. Copy the patched image to your PC with ADB "adb pull /sdcard/Download/magisk_patched_[random_strings].img"
11. Power off device. With the device powered off, hold "Volume Up" and connect the USB cable - the notification light should turn blue (you are in the 'fastboot mode').
12. Flash patched image "fastboot flash boot /path/to/magisk_patched.img". Reboot.
13. Open Magisk app and enable 'MagiskHide'.
14. ...
15. You have root and Google's SafetyNet passes.

What is your--
LineageOS version: lineage-18.1-20210401-nightly-discovery-
LineageOS Download url:https://download.lineageos.org/discovery/changes/#!
Gapps version: NikGapps-basic-arm64-11-20210404-signed
Did you--
wipe: fresh install
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer:no
a non-stock kernel: no
other modifications: no
Navigation with gesture is bugged, has dead touch on the edges of the screen

An other bug, my phone need to reboot to charge it, cuz otherwise it won't. In battery menu say can't be charged right now.

Just upgraded from 17.1. Looks fine, everything working to this moment. Good job man, thanks for the hard work!

LuK1337, update the #2​It's mandatory to remove simlock.ta file. Earlier, Newflasher did ignore (didn't flash) that file automatically. As for now - it doesn't. I just flashed my phone by your guide and now I have phone, which doesn't see simcards
I can't even imagine what to do now ...

Vlackrs said:
An other bug, my phone need to reboot to charge it, cuz otherwise it won't. In battery menu say can't be charged right now.
Click to expand...
Click to collapse
Hm. Exact same problem here :/

Dear developer
Does GPS navigation and positioning do not work?
Is there a way to improve it?

AndreyAleks said:
LuK1337, update the #2​It's mandatory to remove simlock.ta file. Earlier, Newflasher did ignore (didn't flash) that file automatically. As for now - it doesn't. I just flashed my phone by your guide and now I have phone, which doesn't see simcards
I can't even imagine what to do now ...
Click to expand...
Click to collapse
False alarm. The simlock.ta is ignored just as earlier (details here). I've flashed whole stock firmware and simcards are working.

[ROM][11] DarkJoker360 AOSP 11 for Huawei P8 Lite 2017

Hi,
{
"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"
}
DarkJoker360 AOSP 11 for Huawei P8 Lite 2017
*** Stable Version ***
About​
Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
Click to expand...
Click to collapse
Working​
* Touchscreen
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Mtp / Adb
* Sensors
* Wifi
* RIL
* Camera
* NFC
* FP gestures​
Click to expand...
Click to collapse
Not Working​
* You tell me
Click to expand...
Click to collapse
NOTE: The signal icon is buggy due to Huawei weird ril implementation, I am still looking to fix it over the new Android 10-11 telephony changes.
Installation​
* you must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! )
WARNING: You must be decrypted before installing it otherwise it won't boot. (Read second post.)
* go to TWRP
* format data
* reboot to TWRP again
* do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!​
Click to expand...
Click to collapse
Update​
* reboot to TWRP and do a wipe cache, dalvik/art cache
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!​
Click to expand...
Click to collapse
If you are getting Error 70 while flashing gapps just resize system from TWRP !
If gapps are giving network errors or other kind of errors install them after first boot !
Download​
AOSP 11 and NFC fix
NikGapps
OpenGapps​
Click to expand...
Click to collapse
Please support my work, it's very important! Thanks
DONATIONS
Regards !​

NOTES
* For root method read this post, for rooting with magisk read this instead.
* If you face corrupted storage issues you need to go back on emui and re-install the rom.
* I recommend NikGapps core with SetupWizard add-on.
* Use 8.0.0.360 or maximum .400 firmware for booting the rom.
* Gapps can may give "Uncertified device" error and abort the google account login, use this guide to fix it (thanks to @latviandude )
* If you want VoLTE/Wifi Calling working flash this zip
** You must be decrypted for booting this rom **
Before following the installation steps format data and flash this file via TWRP.

Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)

Hi . how can i "resize system" ?

piterconlai said:
Hi . how can i "resize system" ?
Click to expand...
Click to collapse
Go to twrp recovery, press "Wipe" Then choose "Advanced Wipe". After that select/check "System" box and then press on "Repair or Change File System" and then you will see down "Resize File System" - press on it and done ur System has been resized.

hardcorehenry said:
Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
View attachment 5194331 View attachment 5194333
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)
Click to expand...
Click to collapse
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?

Added to AOSP 11 accent, font and icon shape picker (like theme picker), now working on an aosp icon pack picker (aka styles) !

piterconlai said:
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?
Click to expand...
Click to collapse
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected again and again), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.

hardcorehenry said:
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.
Click to expand...
Click to collapse
Thanks for the reply
so can you do 8 h of screen with this rom?
Have you tried if the blutooth smartwatch works by accident?
Last question :
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it

piterconlai said:
so can you do 8 h of screen with this rom?
Click to expand...
Click to collapse
Well you have to calculate yourself from data I provided or flash rom and find out.
piterconlai said:
Have you tried if the blutooth smartwatch works by accident?
Click to expand...
Click to collapse
I don’t have such device.
piterconlai said:
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it
Click to expand...
Click to collapse
If you are more interested in comfort than struggle, testing and help DEV to perfect this rom don’t change anything. Going back means flash and install everything from scratch.

I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?

Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.

hardcorehenry said:
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.
Click to expand...
Click to collapse
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards

Friedensfurz said:
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards
Click to expand...
Click to collapse
Hi,
I’ll try exactly step by step how I did it(I’m on macOS so there might be small differences). When on stock after unlocking bootloader and flashing TWRP(took from this post), you need to copy on your external sdcard or USBOTG NFC_fix.zip, gapps(optional) and fstab.hi6250b.zip or edit your own from /vendor/etc like in this post. Boot into TWRP (backup just in case your vendor partition)and either flash fstab.hi6250b.zip(easy way) or replace fstab.hi6250 in /vendor/etc with edited one via TWRP file manager(harder way). After flashing/replacing enter in TWRP into Wipe and Format Data>yes then reboot into TWRP, wipe: cache, dalvik cache and data and reboot into system. You should reboot into ugly looking stock rom. In settings>security>more you should see Encrypt phone that means storage is decrypted. Enable debug and confirm via adb and boot into TWRP. Make backup(ramdisk, kernel, data, system) enter section Wipe>Advanced Wipe and wipe Dalvik/ART Cache, Cache, Data and System. Don’t Format Data again because most probably it'll f*up Internal Storage besides internal storage is already decryptet. Reboot into bootloader. Run in terminal(macOS) or whatever is used in Windows/Linux:
fastboot devices
fastboot flash system drag and drop aosp-11_prague_20210117.img
Reboot into TWRP, resize System if needed, flash NFC_fix.zip and gapps(optional).
Wipe Cache and Dalvik, reboot and that should be all.

Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
It is a know "issue", just ignore it and boot it.
It is most likely a warning.

DarkJoker360 said:
It is a know "issue", just ignore it and boot it.
It is most likely a warning.
Click to expand...
Click to collapse
Nope it's caused by new version of official firmware for this phone, system partition on newer versions is 2GB on b388 is 3GB.

That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed working firmware 8.0.0.402[service rom] or 8.0.0.400 [the same as developer's]).

hardcorehenry said:
That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed firmware 8.0.0.402[service rom]).
Click to expand...
Click to collapse
I recommend .360 firmware or .400 (the one I am using)
Newer firmwares with newer security patches may refure to boot due to some Huawei changes for avoiding modding.

Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.

Friedensfurz said:
Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.
Click to expand...
Click to collapse
No magisk at the moment, I'm sticking with A10 untill Magisk 19.3 will work on this rom (need to pass safety net)

[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.

[ROM][Huawei][13] LeaOS - Lineage 20.0 for Huawei device (EMUI 9.1 version)

Non-Official Lineage 20.0 for EMUI 9 Huawei (ANE, FIG, POT, VTR, STF)
{
"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"
}
LeaOS is a project which based on LineageOS 20.1 with Andy Yan's and TrebleDroid GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, CAST/Miracast, Media App fixes, Camera HDR, SafetyNet etc..)
Changelog :
LeaOS Maarch 2023 version
Move to Android r35 (SPL Maarch)
Add offline charging
Add spoof model to pass safetynet
LeaOS February 2023 version
First release
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download the version that corresponds to your Huawei phone model here and extract img file. You can choose with ou without GoogleApps
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage, data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
(option) Install single modem patch for multi-sim device : 11-Huawei-MonoSim-AB-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant.
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13
ROM Kernel: Linux Huawei 4.9.148
ROM Firmware Required: EMUI 9.1
Based On: Lineage 20.0 and TrebleDroid
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group
Channel update

Good news, I had just installed the 23/2/23 release and was going really good, except for the SIM card PIN request which was causing bootloop.After removed the PIN of the SIM card I was haven't any problem for the ROM which was running fine, but I could't fix a problem with mobile data which were not working even after re-set the correct APN and check with the dial number on phone info.
After all that I see the new release that I'm going to install RN.
Thanks for your work. Keep it UP!

I will try to fix this pin code and data problem. This is a problem that affects all dual sim huawei. Are you on dual sim?

AltairFR said:
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Click to expand...
Click to collapse
Is TWRP for Stanford (Honor 9) exist? Thanks

Smith Huang said:
Is TWRP for Stanford (Honor 9) exist? Thanks
Click to expand...
Click to collapse
Yes here
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net

AltairFR said:
I will try to fix this pin code and data problem. This is a problem that affects all dual sim huawei. Are you on dual sim?
Click to expand...
Click to collapse
Yes, It's a dual SIM phone. I have just one in it.Anyway I tried the no_gapps version and have not problem with data connection. I think is possibile it is a problem gapps related. Anyway I installed the new release with no gapps and installed LiteApp and works fine.

AltairFR said:
Yes here
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks again!

It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!

Is this project dead or is it in development

Not dead why ?

AltairFR said:
Not dead why ?
Click to expand...
Click to collapse
Oh ok cause I might install it

xqqy said:
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Click to expand...
Click to collapse
Good morning .
For partition size problems, it happens often, so I have developed a program to resize the system partition. He is on xda looking for Huawei partition tools.
For the battery I will look on my stf-l09. Have you tested with the aosp version of leaos?
For the USB problem, I did not see this problem.. thank you for the tests

Is this os pre-rooted? Cause I still wanna watch Netflix and stuff

uncognic said:
Is this os pre-rooted? Cause I still wanna watch Netflix and stuff
Click to expand...
Click to collapse
This OS have an option to pass safetynet, so you can use netflix

When i go to download recovery, im not sure which one to download between twrp-3.5.2-v1-figo-emui9.img, twrp-3.7.0_9-0-anne.img and twrp-3.7.0_9-0-anne.img. I have a Honor 9 STF-L09

With the last leaos, you can flash without twrp

Wait what. But the step-by-step giude asks me to flash twrp for a patch

uncognic said:
Wait what. But the step-by-step giude asks me to flash twrp for a patch
Click to expand...
Click to collapse
It is for drm and i don"t know if stf need
Use this twrp :
https://sourceforge.net/projects/altairfr-huawei/files/TWRP-Recovery/twrp-stf-ki960.img/download

xqqy said:
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Click to expand...
Click to collapse
Huawei Partition Kit - Enlarge system partition
Huawei Partition Kit This kit allows you to enlarge/reduce (2Go->5Go) the system partition on a Huawei kirin 65x, 960 or 970 phone. You can do it from a Huawei android 9 rom, a Lineage 18.1, 19.1, 20, or an AOSP 11,12 or 13. The kit reinstalls...
forum.xda-developers.com

Hi,
I gave this ROM a spin, but didn't get very far in the process documented in the FP.
First flashed TWRP from here with fastboot to recovery_ramdisk.
Code:
$ fastboot flash system LeaOS-20.0-20230304-iceows-google-stf.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/7 (460241 KB) OKAY [ 11.774s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
I also tried to flash from twrp with adb sideload, but that fails instantaneously.
And now I'm stuck with a phone that won't boot. Any suggestions how to proceed?
Btw, device is an STF-L09.

[AOSP ROM] [OFFICIAL] | Android 14 | GSI Install Instructions for Galaxy Tab S6 (SM-T860, SM-T865)

{
"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"
}
Hi everybody, I have been looking for a way to get an official version of Vanilla Android 14 on the Tab S6 for and wanted to make sure the community finally had access to a fully working and sufficiently detailed guide.
This ROM improves battery life by 200%, it's absolutely insane.
Every source, link or file referenced in this guide is 100% official and safe.
Cheers!
Download Firmware + Extract:​
Install SamFirm and download the latest firmware for the Tab S6.
(You will also need to install Visual Studio C++ 8 & 9 for this software to function properly)
SamFirm Tool
Download the latest version of SamFirm Tool, which helps you download the Samsung Stock Firmware (ROM) for free.
samfirmtool.com
Install 7Zip and extract the firmware zip.
Then open the CSC file with 7zip and extract the PIT.
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
Disconnect USB/power cables and turn your device OFF
Hold both Volume buttons (do not press Power) and plug in the USB cord connected to your PC
The download/unlock screen should come up immediately. Select the option for device unlock mode.
Download TWRP:
Download the official TWRP and vbmeta image
TWRP > https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
vbmeta > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Download Official AOSP / Android 14 Image:
The official Android 14 (or 13/12/11) GSI is available on Google's developer page and needs to be extracted via 7zip. (This will also contain a vbmeta.img but disregard it)
(GMS = Gapps | No GMS = Vanilla | FLOSS = Open Source Apps Only)
(Make sure to get a arm64 version) https://developer.android.com/about/versions/14/gsi-release-notes.html
If you prefer the consumer grade "prettier" version of AOSP, you can also download one of the arm64 images provided by phhusson on Github, who exclusively uses official sources code, as well.
https://github.com/phhusson/treble_experimentations/releases
You can also download one of the official daily builds directly from the ACI Project's master-branch (Android Continuous Integration) which represents the literal bleeding edge of AOSP straight from Android : https://ci.android.com/builds/branches/aosp-master/grid?
Flashing Firmware with Odin
Download Odin Flash Tool from a safe source.
Odin - Download
Odin: Samsung-Geräte rooten und flashen - Kostenloser Download für ✓ Windows
www.netzwelt.de
Put the Tab S6 in Download Mode by pressing both Volume Up + Volume Down, while simultaneously connecting the USB cable. (The tablet needs to be off)
Open Odin and add the Firmware Files to the appropriate slots
BL > BL , AP > AP, CSC > CSC
Then click on PIT and add the previously extracted PIT file
Lastly click options and select Nand Erase, Re-Partition, while unselecting Auto Reboot
Flashing TWRP & vbmeta with Odin
After successfully flashing hold down Power Button + Volume Down for 7 seconds but be ready to immediately hold down Volume up + Volume Down to re-enter Download Mode.
(USB Cable needs to be connected at all times)
(If you missed your chance and it's booting, hold down Power Button + Volume down to reset and try again)
Once back in Download Mode click Reset in Odin
Deselect Auto Reboot in the Options again
Then add the TWRP image in AP and vbmeta.tar in the CP slot.
Wiping Cache & Partitions
After flashing hold down Power Button + Volume for 7 seconds and immediately hold down Power Button + Volume Up the entire time until you see TWRP.
Once inside TWRP wipe Dalvik Cache and Cache in the Advanced Wipe menu. Subsequently re-enter the wipe menu, select Format Data and type yes.
After this (USB cable still connected) make sure the Internal Storage is mounted and transfer the system.img (extracted from the AOSP GSI zip) to the tablet
Finishing Up
In TWRP click Install, select the system.img and choose system image.
Flash it, Reboot to System and your DONE!
Current build - Android 14:
Date: April 12, 2023
Build: UPB1.230309.014
Build type: experimental
Security patch level: April 2023
Google Play Services: 23.09.12
Working:
Fingerprint
Hardware Buttons
SDCard
Wifi
Bluetooth
Gapps and Google Setup
Tablet is very fast!
Charging
USB File Transfer
Audio
Video out for USB-C
Auto-rotate
GPS
Official Samsung Keyboard Physically attached working fine too!
Themes
Colours
Mic
SPen
Not Working:
Top Speakers
This issue has already been fixed in the Beta Version which will soon be moved to stable.
Current build - Android 13 (Beta):
(at the time of writing this)
Date: March 29, 2023
Build: T3B2.230316.003
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
Generic System Image releases | Platform | Android Developers
developer.android.com

Many, many thanks for this.. If i understand correctly, we can choose the android 13 file which includes gaps, so to have Google services?
Also there must be an error. The pit file is in CSC file and not in AP file.
Il try it, I'll post the results when i do it.
Thanks again!

I just installed it. Working fine. It does have gaps and playstore and it is vanila android, doesn't have samsung ui.
I suppose i can install in twrp magisk to root it.
After i flashed twrp and restarted, it didn't boot in twrp, but all screen had an error message with yellow txt, something about microsd (which i didn't had). I restarted again to boot in twrp, and this time it did boot in twrp, so i did flash image.
Thanks again!

Anyone knows how to root it?
After flashing system image from android 13, twrp is deleted as i understand. Trying to boot in recovery, it boots to normal recovery, not twrp.
I flashed in odin again only twrp and vbmeta
(TWRP image in AP and vbmeta.tar in the CP slot.). Only those files i used, I'm not sure if this is correct. Anyway, i booted in twrp this time. I couldn't find download folder where i had magisk.zip to flash, trying to root, so i finally just restarted the tablet. It booted ok, but when i tryed again to boot in twrp, it booted in normal recovery again, not twrp.
---If anyone can show me the contact steps to install twrp and root..
--- Aslo in this 13 rom, there isn't fingerprint scanner. Is there any way (xposed, something) to install it?
Thanks!

Although rom is fantastic, with excellent battery life, Ulunfortunately i found a bug which is important for me. Only the 2 right speakers work. The other 2 dont. If some time in the future there is a fix to this, it would be much appreciated. Until then, i have to go to android 12 original..

sosimple said:
Although rom is fantastic, with excellent battery life, Ulunfortunately i found a bug which is important for me. Only the 2 right speakers work. The other 2 dont. If some time in the future there is a fix to this, it would be much appreciated.
Click to expand...
Click to collapse
The speaker issue has already been fixed in the Daily Beta Version of Android 13 offered on the Google Developer's page. Just flash one of those.
Versions des images système génériques | Plate-forme | Android Developers
developer.android.com

tablet_seeker said:
The speaker issue has already been fixed in the Daily Beta Version of Android 13 offered on the Google Developer's page. Just flash one of those.
Versions des images système génériques | Plate-forme | Android Developers
developer.android.com
Click to expand...
Click to collapse
Ok thanks. I'll try the beta.

sosimple said:
Ok thanks. I'll try the beta.
Click to expand...
Click to collapse
Additionally, you can also try the arm64 image from ACI's master-branch. This is literally straight from Android and built/updated hourly.
https://ci.android.com/builds/branches/aosp-master/grid?
I just flashed the one that was released this morning and all four speakers work.

tablet_seeker said:
Additionally, you can also try the arm64 image from ACI's master-branch. This is literally straight from Android and built/updated hourly.
https://ci.android.com/builds/branches/aosp-master/grid?
I just flashed the one that was released this morning and all four speakers work.
Click to expand...
Click to collapse
Which version/build did you use? Also, for updates, does the system>update function within the room work or does the full zip file need to be flashed each time?

weinbers said:
Which version/build did you use? Also, for updates, does the system>update function within the room work or does the full zip file need to be flashed each time?
Click to expand...
Click to collapse
The first column named "aosp_arm64"
Branch Grid
ci.android.com
That will lead you to this page: https://ci.android.com/builds/submitted/9909221/aosp_arm64-userdebug/latest where you'll choose "aosp_arm64-img-9909221.zip"
As for your question about updates, it depends on whether your device supports seamless system updates. The SM-T860 and SM-T865 do not support it.

AOSP GSI with Android 14 has just been released! You can flash it right now with this guide.
Android 14 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 14 preview builds.
developer.android.com

tablet_seeker said:
The first column named "aosp_arm64"
Branch Grid
ci.android.com
That will lead you to this page: https://ci.android.com/builds/submitted/9909221/aosp_arm64-userdebug/latest where you'll choose "aosp_arm64-img-9909221.zip"
As for your question about updates, it depends on whether your device supports seamless system updates. The SM-T860 and SM-T865 do not support it.
Click to expand...
Click to collapse
This one have gapps included ?
Stable ?
Thanks for your work

Amr.Bendari said:
This one have gapps included ?
Stable ?
Thanks for your work
Click to expand...
Click to collapse
GMS = Google apps included
The regular arm64 image is Vanilla Android without Gapps.
You can also grab daily gsi builds from ci.android.com
Android 14 is brand new, so it's not perfectly stable but definitely usable.

In the title you have Android 14.. though then in Post #1 you have Android 13?
I did try 14 though they brightness did not work properly? and the it kept freezing? You said "Android 14 is brand new, so it's not perfectly stable but definitely usable." which version did you use? Cause the one i tried definately wasn't

Hello ,
Thank you for sharing the info
I have checked Rom and answered my own questions .
Widevine is L3 (so only 480p on Netflix)
Performance in Hearthstone is way better .
Unfortunately for me only bottom speakers works , i have checked both 14 and 13 beta
When using spen or Samsung keyboard pointer is set to vertical orientation when tablet is in Horizontal position ,
So they are unusable .
Cannot relock boatloader since it is erroring out on the VBmeta

Hello!
Has anyone rooted now?
How about updates?
Can I just play it like that? I'm currently on Android 13...

Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI

niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
maybe with some magisk modules.. or if your lucky just by flashing the apk

Sage said:
In the title you have Android 14.. though then in Post #1 you have Android 13?
I did try 14 though they brightness did not work properly? and the it kept freezing? You said "Android 14 is brand new, so it's not perfectly stable but definitely usable." which version did you use? Cause the one i tried definately wasn't
Click to expand...
Click to collapse
Thanks, fixed.
The Preview version on Google's main GSI site is unstable. You need to get the latest build on ci.android.com
They are literally building and releasing new artifatcs every 30 minutes.
Also, do you know where to get a Disabler for force encryption on Android 13 for the tab s6? Can't find anything.
Scodera said:
Hello!
Has anyone rooted now?
How about updates?
Can I just play it like that? I'm currently on Android 13...
Click to expand...
Click to collapse
Sure. Just download the Magisk APK from Github.
Install the Magisk APK, then extract the boot.img from your firmware files. Transfer the boot.img to your tablet, patch it with Magisk and then flash this patched img in TWRP choosing the boot option. There are tons of guides for this online.
No updates bc the tab S6 does not support seamless updates. You have to flash new versions. But its super fast because you just flash system and ur good.
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
Yes. I don't trust APKMirror so what I do is install the stock ROM from the latest samfirm firmware. Root it. Install File Commander, or any other root file manager.
Then navigate to /data/app and grab the Samsung Notes APK. All other apps are stored in this directory BTW. Then just install the APK once you flashed AOSP GSI

niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
If you still want to keep using Samsung apps under a different OS like this one (AOSP, A14) install the Magisk module " Xmlpak a road to vendor apps".
After reboot, the Samsung apps you want to use again should show up in the app store for you to install. If not you can use APKMirror to download the APKs. Contrary to what a user posted above, this site is more than safe and verified.