Database Info

[FAQ][Discussion]LineageOS 15.1 by abhishek987 [ask your questions HERE]

Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1:
!NEW AND THE ONLY RECOMMENDED METHOD!​
You must be on Oreo. Before flashing delete all your saved fingerprints and screen locks.
1. Reboot to bootloader (Bootloader must be unlocked)
2. fastboot boot recovery-xx.img (in ADB)
-> Grab official recovery from here: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
3. Wipe System/Data/Cache/Dalvik
4. Flash Lineage & TWRP Installer zip
-> Grab TWRP installer from the link above
5. Reboot to recovery using TWRP Recovery (In TWRP go to Reboot -> recovery)
6. Flash Gapps/MicroG (opengapps.org -> platform ARM64 -> Android 8.1 + Variant [IMO pico is your best pick])
7. Flash Magisk [latest] if you want ROOT (I bet you want!)
-> Grab Magisk from here: http://tiny.cc/latestmagisk
8. Reboot to System
How to update from previous build:
If you don't have permament TWRP, just follow the method above.
If you have permament TWRP:
Delete all your previous fingerprints (just for safety)
Boot to TWRP
Wipe Data/Cache/Dalvik (wiping is optional - but clean flash is always encouraged)
Flash Lineage ROM zip file
Flash Magisk
Flash Gapps/MicroG
Reboot
KNOWN BUGS:​* No bugs right now! Enjoy bug-free rom!
If you have signal stability issues, try this:
Dial *#*#4636#*#*
Go to Phone information
Set Preferred Network Type from Unknown to LTE or WCDMA only
WHAT IS WORKING:​* Everything else
LINEAGE BUILD CHANGELOG:
Code:
[FONT="Arial"]
[B]Most recent build (24.03.2018):[/B]
Fixed portrait mode
Enabled hal3 camera by default
Added doze
Lineage upstream
[B](22.03.2018): [/B]
Fixed double tap to wake (should only work for focaltech panel)
Rebased kernel to latest oreo source drop
Enabled cpusets
Lineage upstreams
[B](13.03.2018): [/B]
Fixed verity issue (builds now can be flashed without magisk)
Fixed Live Display
Fixed Substratum
Fixed ril issues
Lineage Upstream changes
[B](08.03.2018): [/B]
Fixed notification light (should work in call cases now)
Fixed slow charging
Fixed deep sleep issue
Added navbar toggle
Fixed goodix fingerprint issue (should work for all and all 5 fingerprint should be registered now)
Lineage Upstream changes
[B](06.03.2018): [/B]
Fixed led light
Added fingerprint gestures
Fixed Bluetooth name
Fixed battery capacity
Lineage upstream changes[/FONT]
Have fun with LOS!

Q&A
What does NIGHTLY mean?
Nightlies are automatical builds (every few days), so it mean you will have frequent updates, recent Lineage changes will be present in a rom. Also fixes and new stuff will come faster!
How I can go back to stock?
Grab Mi A1 tool from here: https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857.
Install it in your PC, enable USB Debugging on your phone, plug phone to PC
Click Flash Stock ROM button
Click Download ROM and wait
Click FlashAll. Your phone will reboot to fastboot and it will start to flash stock
[You will loose all your data, so backup is encouraged]
Do I need to downgrade to Nougat before flashing?
Not anymore It's advised to flash from Oreo
After update my FP don't work, wat to do?!
Make a clean flash using method from OP. If clean flash won't help, try: https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
Is Dolby working on Lineage 15.1? How to install it?
Just download Magisk module and enjoy!
My mobile signal is unstable. Is there a way to fix it?
Yes, see a workaround from OP
Why Selinux is permissive, not enforcing?
In unofficial builds Selinux is permissive. If the build goes official, it will have Selinux set to enforcing. Don't worry, just wait for official version!
Is this rom stable enough to be a daily driver?
Depends what you need. Check buglist - if these bugs don't bother you - it can surely be a daily driver
When new build will be avaible?
Don't ask for ETAs. Developers are working hard (in their free time!) to fix a bugs - we just need to wait patiently.

Some users are experiencing wifi issues (myself included). How can i fetch the log?
Steps to reproduce: Turn off bluetooth. wait a moment... wifi will start dropping connection a lot. To fix, just turn on BT again.

Headphones do not work.

Headphones are working!
By the way. I found a bug. The equalizer don't work correct. Everytime when you skip a song you must tap the bass regulator again in the equalizer app. When you don't do it, it plays without bass.

konradit said:
Headphones do not work.
Click to expand...
Click to collapse
Everything fine here, try to reflash

Installed and used for 24 hrs with no apparent problems. No fingerprint bug.
All the other bugs reported in OP exists.
Returned to Stock since I found it a bit smoother.
I will wait for a more stable official build
Good work so far

still

rasputine said:
still
Click to expand...
Click to collapse
Are you using the deadman twrp? I got that using other TWRP versions.

goofball2k said:
Are you using the deadman twrp? I got that using other TWRP versions.
Click to expand...
Click to collapse
Yes I'm using deadman's twrp

rasputine said:
Yes I'm using deadman's twrp
Click to expand...
Click to collapse
Did you reboot after doing the data wipe?

Can I install LOS 15.1 without flashing magisk? I have tried this and had bootloop before any lineageos bootlogo

radogost said:
Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1: ​There's a few working methods. First, most popular one:
....
Third, last one:
Boot to the recovery (same recovery as method above)
Wipe system and cache ( data is optional if your are on Oreo)
Check which partition you are on (A or on partiton B)
Flash the rom on one of the partitions
Flash the twrp installer zip
link: http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
Reboot back to the recovery
Switch to the second partition
Flash GAPPS/MicroG and Magisk
Reboot
Click to expand...
Click to collapse
Sorry to pick this up again but the last method implies that TWRP will be installed permanently as default recovery, right? I was successfull only with the first method however I always end up in LOS recovery when try to enter recovery with Vol-up+Power after everything is installed.
I'm sure we all agree that this whole recovery mess needs to be sorted out quickly. Even experienced users are hitting snags and flood the board with questions .

goofball2k said:
Did you reboot after doing the data wipe?
Click to expand...
Click to collapse
Yes sir

i face the same issue with any methond i am using.
in some cases i am unable to install all the zips and in another case i am unable to install only magisk(error 1)
i followed exactly the steps.
any suggestions?

I'm not sure why the issues. I followed the steps in the OP, except I didn't flash TWRP, I just boot to it temporarily.
I did the following:
Flashed 7.11.18 ROM using MiFlash.
Booted into the ROM, set it up minimally.
Rebooted to fastboot, unlocked bootloader
booted temporarily to deadman TWRP, wiped system/cache/dalvik/data (just to be sure it is completely clean)
rebooted and then booted back into deadman TWRP
flashed LOS.
rebooted and then booted back into deadman TWRP
Flashed gapps and magisk.
rebooted to OS.

hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!

Flashed from 8.1.10 without any problems...

ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?
---------- Post added at 01:47 PM ---------- Previous post was at 01:47 PM ----------
ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?

t0per666 said:
hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!
Click to expand...
Click to collapse
Tornado95 said:
Flashed from 8.1.10 without any problems...
Click to expand...
Click to collapse
Hmm so which one is telling the truth? ??
Sent from my Xiaomi Mi A1 using XDA Labs

android oreo 8.1 firmware leak for alldocube power m3

android oreo 8.1 firmware leak for alldocube power m3 ,guys who own the pad have a try!and give a bug reply post.
alldocube power me oreo 8.1 firmware(0621)
a offical oreo 8.1 firmware with google play for power m3:http://www.mediafire.com/file/qev79...2B32.Neutral.8.1.V01.01.20190118user.zip/file

The firmware is working. One problem: after installation in TWRP package OpenGapps the system crashes. I couldn't find the replacement option (arm64, 8.1). Energy saving is good. Root access - Magisk.
P.S.: Build OpenGapps UNOFFICIAL is suitable for installation and works after components are updated (for example, with Yalp Store or Aurora App Store, F-Droid & etc.)
P.P.S.: If someone decides to install the firmware - must first make a backup of the NVRAM!!! Because the firmware will have to be installed with formatting and the nvram section will die. After flashing the firmware, it must be restored from the saved backup.

For me I got Problems with the display.. Its kinda over saturated.
If someone can explain the rights step to flash this rom would be nice. I cant install twrp over the Flash tool i used this for flashing twrp:
https://forum.xda-developers.com/android/general/cube-power-m3-tablet-twrp-img-t3772179

Hai_Duong said:
For me I got Problems with the display.. Its kinda over saturated.
If someone can explain the rights step to flash this rom would be nice. I cant install twrp over the Flash tool i used this for flashing twrp:
https://forum.xda-developers.com/android/general/cube-power-m3-tablet-twrp-img-t3772179
Click to expand...
Click to collapse
Take my version TWRP specifically for Oreo (the same in Russian how to install and patched Magisk boot.img to obtain root-rights): hire.
The saturation of the screen is comfortable for me, Occasionally settings of installed programs fly off.
TWRP Oreo
patched boot

config.gz in /proc fs
wangyiling said:
android oreo 8.1 firmware leak for alldocube power m3 ,guys who own the pad have a try!and give a bug reply post.
alldocube power me oreo 8.1 firmware(0621)
Click to expand...
Click to collapse
running linux kernel was configured to have /proc/config.gz. The configuration for this is found in
General setup
[*] Kernel .config support
[*] Enable access to .config through /proc/config.gz

with oreo 8.1...
treble checker reports device to be supported by Project - only with A-partition.
did anyone tried out to switch to GSI image?

cmarxmeier said:
tried out to switch to GSI image
Click to expand...
Click to collapse
Theoretically, should be suitable all the firmware from this theme and some of this. But we need TWRP support Treble, if I understand correctly (I tried the project on another device, everything was already done).
Treble works. As an experiment, I launched Omni 8.1. Started, but gives error 'com.android.phone has stopped'. The system image installed through fastboot (my TWRP isn't able to install to the system partition). The bootloader must be unlocked.
AOSiP Pizza Alpha [EXPERIMENTAL] - wi-fi, sound work, phone don't.
[9.0.0] ArrowOS (Android 9) - very quite good, but again the phone module. Need a system.img way to rebuild, or looking for a fix. In the firmware theme this is the main question. And in general, I liked the firmware, fast response and fast touch interface.

https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .

wangyiling said:
also some one can try this new power m3 8.1 firmware
Click to expand...
Click to collapse
I already have this version installed. The work of the Treble Project checked on it. Firmware international, Google applications available, fixed some bugs. The installation also requires restoring the nvram partition.
Here's an updated TWRP 3.2.1-0 x64 for Oreo with support for the Treble Project (my port from Infinix X571): AFH

ViAlexSt said:
Theoretically, should be suitable all the firmware from this theme and some of this. But we need TWRP support Treble, if I understand correctly (I tried the project on another device, everything was already done).
Treble works. As an experiment, I launched Omni 8.1. Started, but gives error 'com.android.phone has stopped'. The system image installed through fastboot (my TWRP isn't able to install to the system partition). The bootloader must be unlocked.
AOSiP Pizza Alpha [EXPERIMENTAL] - wi-fi, sound work, phone don't.
[9.0.0] ArrowOS (Android 9) - very quite good, but again the phone module. Need a system.img way to rebuild, or looking for a fix. In the firmware theme this is the main question. And in general, I liked the firmware, fast response and fast touch interface.
Click to expand...
Click to collapse
ViAlexSt said:
I already have this version installed. The work of the Treble Project checked on it. Firmware international, Google applications available, fixed some bugs. The installation also requires restoring the nvram partition.
Here's an updated TWRP 3.2.1-0 x64 for Oreo with support for the Treble Project (my port from Infinix X571): AFH
Click to expand...
Click to collapse
nice

wangyiling said:
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
Click to expand...
Click to collapse
Firmware brings up DualWifi again - 5GHz stopped working in former version.
EngineerMode.apk seems to be removed from priv-app's in this release - restoring manually from old image did not help - app crashes.
No easy way to set IMEI on device without MTK EngineeringMode.

cmarxmeier said:
Firmware brings up DualWifi again - 5GHz stopped working in former version.
EngineerMode.apk seems to be removed from priv-app's in this release - restoring manually from old image did not help - app crashes.
No easy way to set IMEI on device without MTK EngineeringMode.
Click to expand...
Click to collapse
for imei restore ,i think mtk sn write tool will do some help

wangyiling said:
for imei restore ,i think mtk sn write tool will do some help
Click to expand...
Click to collapse
mtk sn write tool did the job. - shows up with correct IMEI and VoLTE 4G.
patched boot.img with magisk
- works like a charm so far.
Looking forward to check USB-C Port with Icy Box to get Ethernet/HDMI device listed on USB-Bus.

wangyiling said:
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
Click to expand...
Click to collapse
Someone does have TWRP recovery for this one? Trying to port old one, but getting buggy rotated recovery...

fraddy91 said:
Someone does have TWRP recovery for this one? Trying to port old one, but getting buggy rotated recovery...
Click to expand...
Click to collapse
Compile yourself by adding the lines:
# TWRP
......
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
Or Phils recovery.

Development Random Builds - A11 (PE+, Havoc OS, MSM Xtended, Project Sakura, dotOS)

So im kinda lazy, and don't want to make a new thread for each of my builds, so i will share them here if they are decent enough.
INSTALLATION:
You MUST have an unlocked bootloader
TINY FASTBOOT SCRIPT - First Time Install / Clean Flash
1. Download the ROM zip and TinyFastbootScript
2. Extract both zip files into the same folder on your PC
3. Run flash.bat and install latest Motorola drivers
4. Reboot device to bootloader mode and connect to PC
5. Select Flash Custom Firmware (option r)
6. Wait for the program to flash all images
7. After flashing, in the tinyfastboot main menu, press n, then press 3, then type fastboot -w and enter
8. Once finished, Reboot to System
Update / Dirty Flash
1. Download the ROM zip
2. Extract the ROM files into the same folder as previous update
3. Reboot device to bootloader mode and connect to PC
4. Select Flash Custom Firmware (option r)
5. Wait for the device to flash all images
6. Once finished, Reboot to System
All my builds will be GAPPS INCLUDED, and no, i WONT make you a vanilla version.
HAVOC-OS 4.16 (April security patch)
https://drive.google.com/file/d/16QLxXqCxdz_5socjV4sVGbHPOBbai-eG/view?usp=sharing
MSM Xtended (november security patch)
https://drive.google.com/file/d/1Irz9eExiix4o9u16AI7j6HDRziSkLnMN/view
Pixel Experience Plus (december security patch)
https://drive.google.com/file/d/1R10N9qay1Ku3TEErWxNIlifkNFET6NIk/view?usp=sharing
Project Sakura 5.2 - (january security patch)
https://drive.google.com/file/d/15v18B0z6m2lf1LyaL9MQJpvubtUiS5C1/view?usp=sharing
dotOS 5.2.1 (november security patch)
https://drive.google.com/file/d/1g9GL6H5dixe62DbEzcQRD95ljgZ5W_B7/view?usp=sharing
Kernel Source Code: https://github.com/moto-sm8250/android_kernel_motorola_sm8250
Device Source Code: https://github.com/moto-sm8250/android_device_motorola_nio
Device-Common Source Code: https://github.com/moto-sm8250/android_device_motorola_sm8250-common
Vendor-Common Source Code: https://github.com/moto-sm8250/android_vendor_motorola_sm8250-common
Vendor Source Code: https://github.com/moto-sm8250/android_vendor_motorola_nio
Special thanks to @Electimon for all his help!

18-11-21 - Havoc OS and MSM Xtended added
20-11-21 - Pixel Experience plus added (not fully tested, but all major things working)
22-12-21 - Havoc OS 4.12 added
02-01-22 - Pixel Experience Plus added (december patch)
21-1-22 - dotOS 5.2.1 added
29-1-22 - Project Sakura and Havoc updated to january security patch
18-3-22 - Havoc OS 4.14 added (feb patch)

Thank you will test these

Tested MSM Xtended dont boot on moto g100 just restarts on boot.

Pixel Experience plus is well dont boot on my g100 do i missing something to do ? did all instruction how to flash same just restarts to bootloader.

Any help how get running these all not working on g100

rackis18 said:
Any help how get running these all not working on g100
Click to expand...
Click to collapse
Try formatting data (fastboot -w) in the bootloader

rackis18 said:
Tested MSM Xtended dont boot on moto g100 just restarts on boot.
Click to expand...
Click to collapse
This one has been tested by a g100 user and i was told it boots up

Beetle84 said:
This one has been tested by a g100 user and i was told it boots up
Click to expand...
Click to collapse
That's interesting because on my g100 it won't boot just reboot into bootloader. I did format data etc in tiny script.

@rackis18 Open tiny fastboot script, press n and then 3 and type fastboot -w, enter and reboot

rackis18 said:
That's interesting because on my g100 it won't boot just reboot into bootloader. I did format data etc in tiny script.
Click to expand...
Click to collapse
Hey mate, just heard back from a guy on telegram with a g100, it boots up fine for him.

Beetle84 said:
Hey mate, just heard back from a guy on telegram with a g100, it boots up fine for him.
Click to expand...
Click to collapse
Which one you own, g100 or Edge S?

Windoors said:
Which one you own, g100 or Edge S?
Click to expand...
Click to collapse
I have the edge S mate

I can boot any other rom from here and they boots and works no problems but these 3 have issues on g100 i think needs to look at these mate. Thanks

rackis18 said:
I can boot any other room from here and they boots and works no problems but these 3 have issues on g100 i think needs to look at these mate. Thanks
Click to expand...
Click to collapse
The latest evo x (november build) is working?

Beetle84 said:
Could you try flashing a vbmeta
The latest evo x (november build) is working?
Click to expand...
Click to collapse
Yes works no problems I'm using it now. Anyway, nice build mate.

Beetle84 said:
@rackis18 Open tiny fastboot script, press n and then 3 and type fastboot -w, enter and reboot
Click to expand...
Click to collapse
This worked mate thanks for help.

rackis18 said:
This worked mate thanks for help.
Click to expand...
Click to collapse
So all good now?

Beetle84 said:
So all good now?
Click to expand...
Click to collapse
Yup. All good. I don't know if that's made any difference before I tried install from stock rom now from evo so just let you know because maybe a reason.

rackis18 said:
Yup. All good. I don't know if that's made any difference before I tried install from stock rom now from evo so just let you know because maybe a reason.
Click to expand...
Click to collapse
Definitely the data format was the problem i think. I changed the instructions to include that instead of the tinyfastboot reset

[ROM][T320][T325][Android 13] Unofficial LineageOS 20.0 Nightlies Tab Pro 8.4 Wifi/LTE (mondrianwifi/lte)

I'm not responsible for any damage to your device of any sort.
By flashing this, you take responsibility of anything that happens.
Process at your own risk!
If you want to check - please make backup. Better to store all partitions.
What works
audio
bluetooth
brightness
call/LTE (mondrianlte)
camera
DRM
OTA
video
wifi
wifi display
What doesn't work
Back camera preview : wrong rotation on preview in default app Fixed build 20221204
SELinux Fixed build 20221130
Instructions:
0. Patched TWRP for FOTA : mondrianwifi / mondrianlte
1. Factory reset if coming from another ROM.
2. Install ROM
3. Install GApps (optionally) [Recommended BiTGApps ARM 13]
4. Install Magisk 25.2 (optionally)
Sources & Changes:
Device tree mondrianwifi
Device tree mondrianlte
Kernel tree
Vendor tree mondrianwifi
Vendor tree mondrianlte
TWRP tree mondrianwifi
TWRP tree mondrianlte
Download:
Downloads: mondrianwifi / mondrianlte
Note to users: I'm not responsible if you brick your tablet. See the disclaimer above.
Contributors
LineageOS team for source code.
@retiredtab for helping make mondrianwifi to work on Android12
@khalvat for its work on porting msm8974 to Android12 (https://github.com/LineageOS-UL)
@pocketrule, @bierma32, @Yxo 6o6uka for willing to test WIFI builds and leaving feedback
@bmwdroid for willing to test LTE builds and leaving feedback
ROM OS Version: 13.0
Version Information
Status: Nightlies
Created 2022-11-27
Last Updated 2023-01-05

THX @phoval for the New LOS 20 Version.
Installed this as update over the Version 20221010 without issue's.

FOTA update notification works .

New build: SeLinux is enforcing

Perfect !!!
Amazing !!
Thank you @phoval !!!

Hello, good job.
Thank you @phoval

Installed and runs smooth. Sound, video & wifi works. Excelled work.

Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers

@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204

cwokel said:
Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers
Click to expand...
Click to collapse
bierma32 said:
@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204
Click to expand...
Click to collapse
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz

@chkdsk90
Charge your battery to 100% and try another clean install, format also system and data .

chkdsk90 said:
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz
Click to expand...
Click to collapse
Provide logcat.
zram boot img was alpha kernel for test.
The changes are includes since 2nd december build.

how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar

chkdsk90 said:
how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar
Click to expand...
Click to collapse
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.

pocketrule said:
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.
Click to expand...
Click to collapse
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file

chkdsk90 said:
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file
Click to expand...
Click to collapse
It's patched for FOTA. A simple internet search reveals, that fota stands for "Firmware Over-the-Air" 😉️ I.e. you can download and update the rom directly from the rom itself. If you (always) download and flash the rom manually / separately, you don't need the patched rom.

One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?

If I get a app not responding message and I hit wait it will repeatedly pop up despite the app responding again (dirty flash). Otherwise first impressions of this rom are good.

Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today

cwokel said:
One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?
Click to expand...
Click to collapse
Just disable it in system > buttons. It's customization during first setup.
You can enable gesture navigation too.
jacomail95 said:
Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today
Click to expand...
Click to collapse
If someone can find me one to buy?

Development OP9-LEMONADE-A13-ROM-WATCHDOGS-JUNE 25, 2023

I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.

Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.

I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!

Telegram group please

lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.

I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with

lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!

I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.

incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.

TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro

TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.

lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.

incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.

I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?

Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.

screenshots?

pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it

MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip

Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img

You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.