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

From OOS 10.0.1 trying to install LOS 16.0 as a beginner and failing completely

I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?

It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.

TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.

remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?

I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well

In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.

I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?

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.

Bootloop after installing Lineage

Recently I decided to play around with my retired xiaomi 4c which I bought in 2016/2017.
Firstly, I unlocked my phone and installed TWRP recovery. (the version I installed is twrp-3.1.1-0-libra), the link I used is here: https://dl.twrp.me/libra, the reason why I did not install version 3.1.1-1 is that It won't load in recovery mode.
Secondly, I tried to install lineage 14.1, 15.1,16.1, 17.1 (none of them worked), It gave me this error
E3004 the packge is for device 4c,libra, this device is .
After searching on google, I deleted the first line (the assert statement) in META-INF\com\google\android\updater-script.
I guess it managed to be installed (no error pop out).
the log displayed while it is installing:
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
packing system image unconditionally
However, when I click boot to system, it stuck on the mi logo.
I need some suggestions on how to make this work.
Thanks in advance!

Flash the latest available official miui (currently V10.1.1.0), via mi flash tools
Flash twrp or orangefox, via ADB. twrp official site has an old version, androidfilehost has a newer version TWRP-20190528-3.3.1.0-libra. orangefox official site has taken down libra files but sourceforge has OrangeFox -R10.0-1-Stable-libra.
Then try again

I experienced "this device is ." problem before.
From I read somewhere in XDA, sometimes a ROM may require certain recovery images to flash. So if the image is published with some recovery, you may want to try them together.
The last time I flashed my mi4c successfully, the LineageOS build and TWRP are both from this post: https://forum.xda-developers.com/t/rom-android-8-9-10-unofficial-lineageos-for-mi-4c-mi-4s.4008625/ .
Good luck

Gourcuff14 said:
Flash the latest available official miui (currently V10.1.1.0), via mi flash tools
Flash twrp or orangefox, via ADB. twrp official site has an old version, androidfilehost has a newer version TWRP-20190528-3.3.1.0-libra. orangefox official site has taken down libra files but sourceforge has OrangeFox -R10.0-1-Stable-libra.
Then try again
Click to expand...
Click to collapse
Thank you! I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird

momocraft said:
I experienced "this device is ." problem before.
From I read somewhere in XDA, sometimes a ROM may require certain recovery images to flash. So if the image is published with some recovery, you may want to try them together.
The last time I flashed my mi4c successfully, the LineageOS build and TWRP are both from this post: https://forum.xda-developers.com/t/rom-android-8-9-10-unofficial-lineageos-for-mi-4c-mi-4s.4008625/ .
Good luck
Click to expand...
Click to collapse
Thank you, I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird.
Haha but now I failed to bypass the ssl pinning through sslunpinning and frida ><, frida says Bad access due to invalid address
Any idea how to fix this?

Try the boot image included in this build package and post your findings in that thread for assistance.
[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s
DESCRIPTION Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download. FEATURE The following items may not be available for...
forum.xda-developers.com

you need orangefox for mi4c

yanzifan021 said:
Thank you! I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird
Click to expand...
Click to collapse
Hi friend, could you share the download link 14.1, thanks

timsg said:
Hi friend, could you share the download link 14.1, thanks
Click to expand...
Click to collapse
Here there are some builds https://androidfilehost.com/?w=search&s=libra&type=files&page=19

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