Database Info

unable to install twrp over 3.1.1.1 on mi4c (trying to go from android 7.1 to 8 or 9)

Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys

Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.

I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...

makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!

if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199

makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:（Translation is not easy to use）

celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip

OFFICIAL LINEAGE OS 16 was released but was taken down?

They made a wiki on Beryllium (https://wiki.lineageos.org/devices/beryllium) and some other links to the official build (https://download.lineageos.org/beryllium) but they removed it.
I don't know what was the reason.
They rolling out the Lineage 16 PIE on couple devices like Oneplus 5/5T, Huawei P20 Pro, Xiaomi Mi Note 3, etc. (https://www.androidpolice.com/2019/...1-oneplus-phones-galaxy-s5-and-other-devices/)

wasn't released it failed but it is expected to succeed soon.

bower1994 said:
wasn't released it failed but it is expected to succeed soon.
Click to expand...
Click to collapse
Thank you for the response, out of curiosity, what was failed in the latest official build?

https://gitlab.com/LineageOS/builder/android/pipelines/49950700/builds
Yesterday all builds failed on that user/server

#### build completed successfully (01:34:25 (hh:mm:ss)) #### Guess we can expect a build in a few hours?

The nightly is available now

The inital nightly build seems to be broken, at least for me. Can't boot into system.

Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.

tiantnait said:
Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.
Click to expand...
Click to collapse
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!

no problems here.. clean flash, flashed firmware 9.2.25, los official nightly, pico gapps and magisk 18.2, wipe cache/dalvik and reboot. it runs awesome

Strel0ka said:
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!
Click to expand...
Click to collapse
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...

tiantnait said:
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...
Click to expand...
Click to collapse
So you performed a dirty flash of official LOS over unofficial LOS? That's like dirty flashing NOS over LOS. If you want to switch over to the official branch, I highly recommend starting from scratch.
My current setup is official LOS with microg + magisk and Encryption, no issues so far.

Yep.. Official build is on!

LineageOS 17.1 BETA TESTING

Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
EDIT: Join telegram group @clarkdev for beta testing or see development

Hi, i'm in!

DarkDroidDev said:
Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
Click to expand...
Click to collapse
Link?

i 'm in too..

Link?

@DarkDroidDev already sent the DM from telegram

Выложите пожалуйста √17

Development resumed, who want to see progress or help with testing, feel free to join telegram group
@clarkdev

Any chance you could provide links without telegram?
Not looking to add another messenger that I'll forget I have in 6 months lol

Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .

I'd also be interested but don't use Telegram

ac2323 said:
I'd also be interested but don't use Telegram
Click to expand...
Click to collapse
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.

Nice.

Wheels564 said:
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.
Click to expand...
Click to collapse
Yes, working nice.

@DarkDroidDev Hey, how did you extract the proprietary blobs? The instruction says that one needs to have an installable zip of LineageOS for clark, or already have the device runnning the LOS. I tried to extract it just from my stock Moto X Style with the script and it did something, but I'm not sure if it's going to work.
Edit: I'm also interested in testing the 17.1 build, since the one I'm trying to build following the instruction is 14.1 and actually it fails because of lack of some vendor files :/ But I'm also not interested in joining Telegram
Edit: Oh, I missed the @chrmhoffmann post!

hi, chrmhoffmann. thank you for your work.
chrmhoffmann said:
Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .
Click to expand...
Click to collapse
Hi, chrmhoffmann. Thank you for your work. I previously tested your 20200718 upgrade. I have installed the same date recovery and the latest magisk20.4. Unfortunately the system will not start. I also tried wipe system wipe cache wipe data and reinstalled it again, but it still didn't work.

I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.

kb8no said:
I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.
Click to expand...
Click to collapse
From what I've seed Darkdroiddev removed Clark from his Github so I assume he is no longer working on this phone and this thread is probably dead. Randomblame hasn't posted since February. chrmhoffmann's thread https://forum.xda-developers.com/mo...opment/unofficial-lineage-17-1-clark-t4123077 actually has a link to official Lineage gerrit which means we are well on our way to becoming official Lineage again. Meanwhile I'll keep posting LOS 14.1 for MMBL until we get there.

Question What Custom ROMS are available for this device ?

My device is Redmi note 11 pro 5G are there any custom roms available for it ? and is it lineage OS?

Derp,pe,raven os,ricedroid,evo,elixir and more ...

I have been using LineageOS 19.1 Unofficial A12.1 on the Veux (Redmi Note 11 Pro 5g 2201116SG) for a week now.
Recovery Twrp 3.6.2_12-0.
No major issues to report.

albatro9 said:
I have been using LineageOS 19.1 Unofficial A12.1 on the Veux (Redmi Note 11 Pro 5g 2201116SG) for a week now.
Recovery Twrp 3.6.2_12-0.
No major issues to report.
Click to expand...
Click to collapse
What about battery life ?

I haven't noticed any abnormal consumption.
I don't have any apps working in the background, and I haven't installed Gapps.
But the phone is new, the battery is 5Ah, with normal use I get to the evening with 30-40%.
Perhaps it consumes a bit more than MurenaOS (formerly /e/OS, which I used for years on several Xiaomis, with great satisfaction for my privacy needs).
I don't care much about battery consumption, my goal is privacy, and there is some work to be done on this Lineage.
I hope some Murena expert will work on it, I don't have the skills to do so.
I accept indications on other "privacy-friendly roms" or settings for Lineage 19.1...

albatro9 said:
I have been using LineageOS 19.1 Unofficial A12.1 on the Veux (Redmi Note 11 Pro 5g 2201116SG) for a week now.
Recovery Twrp 3.6.2_12-0.
No major issues to report.
Click to expand...
Click to collapse
Could you provide me links for the lineageOS 19.1 And the recovery I could not seems to find them.
Also i tried to install TWRP after i unlocked bootloader but it seems to failing.

meliodas_100 said:
Could you provide me links for the lineageOS 19.1 And the recovery I could not seems to find them.
Also i tried to install TWRP after i unlocked bootloader but it seems to failing.
Click to expand...
Click to collapse
Release September: Release · xiaomi-sm6375-devs/LineageOS_veux
Fix touch in recovery. Update to September security patch!
github.com

dom_mnml said:
Release September: Release · xiaomi-sm6375-devs/LineageOS_veux
Fix touch in recovery. Update to September security patch!
github.com
Click to expand...
Click to collapse
I also have problem with touch in recovery, Could it be solved with this ?
[Edit] - I used this link and tried to install the boot.img from this lineage os but i cannot seem to boot into the twrp after installing and the device is stuck at MI logo.
[Edit] - I fixed the MI logo issue by using the vendor boot.img
[Edit] - Tried again and the device is stuck at fastboot.

dom_mnml said:
Release September: Release · xiaomi-sm6375-devs/LineageOS_veux
Fix touch in recovery. Update to September security patch!
github.com
Click to expand...
Click to collapse
Device is now stuck at fastboot How to revert back?
Can anybody give me instructions on how to flash custom recovery.

albatro9 said:
I have been using LineageOS 19.1 Unofficial A12.1 on the Veux (Redmi Note 11 Pro 5g 2201116SG) for a week now.
Recovery Twrp 3.6.2_12-0.
No major issues to report.
Click to expand...
Click to collapse
Could you give me precise instructions how to install the twrp in my device mine is 2201116SI. I keep either getting stuck at a bootloader or getting the touch not working in twrp error.

meliodas_100 said:
Could you provide me links for the lineageOS 19.1 And the recovery I could not seems to find them.
Also i tried to install TWRP after i unlocked bootloader but it seems to failing.
Click to expand...
Click to collapse
I confirm the answers you have already received.
I followed the directions in "Installing a custom recovery, and disabling encryption in the system," in this forum.
There you will find Twrp 3.6.2_12-0.
Rom is "lineage-19.1-20221003-UNOFFICIAL-veux-signed.zip" (1,170,242,002 bytes).
Now I don't remember where it came from, I think from this forum.
Try to look for it, if you don't find it we will see what to do.
I am a newbie, I don't know the forum rules.
I had also tried the directions of "TWRP 3.7.0_12 for VEUX/PEUX", but I had problems.

meliodas_100 said:
Could you give me precise instructions how to install the twrp in my device mine is 2201116SI. I keep either getting stuck at a bootloader or getting the touch not working in twrp error.
Click to expand...
Click to collapse
I am not sure, but I think yours is a different phone than mine (2201116SG).
Please check it carefully.
That would explain your problems.

meliodas_100 said:
I also have problem with touch in recovery, Could it be solved with this ?
[Edit] - I used this link and tried to install the boot.img from this lineage os but i cannot seem to boot into the twrp after installing and the device is stuck at MI logo.
[Edit] - I fixed the MI logo issue by using the vendor boot.img
[Edit] - Tried again and the device is stuck at fastboot.
Click to expand...
Click to collapse
Twrp 3.6.2_12-0 is not official, small difficulties are normal, I thank who developed it!
-------------------------------
I thought it seemed to freeze, instead it unlocked after a few minutes.
I spotted a little trick: press the power button on the phone and you can access recovery right away.

niteone said:
Derp,pe,raven os,ricedroid,evo,elixir and more ...
Click to expand...
Click to collapse
Which of these roms is the most privacy friendly?
Do you have the link to download it?
Thanks in advance

albatro9 said:
Which of these roms is the most privacy friendly?
Do you have the link to download it?
Thanks in advance
Click to expand...
Click to collapse
I think lineage, I have the lineage installed. so far so good but it has some lag problems.

meliodas_100 said:
I think lineage, I have the lineage installed. so far so good but it has some lag problems.
Click to expand...
Click to collapse
I also installed Lineage 19.1 on the veux, I have no lag problem.
Now I need to install MicroG, but can't solve "signature spoofing"...

?

niteone said:
Derp,pe,raven os,ricedroid,evo,elixir and more ...
Click to expand...
Click to collapse
Any link ?

You can find them in the official telegram group for the device

niteone said:
You can find them in the official telegram group for the device
Click to expand...
Click to collapse
No, publicly please.
I will not create account on each social networks for each projects.

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