Hey Tavi, are there any issues with the development of DOS 21? I’ve been out of the loop for a year and can’t seem to find anything on your website. Also, for upgrading from DOS19 to DOS20, i just follow the lineageos guide (Upgrade to a higher version of LineageOS (e.g. lineage-20 → lineage-21)) by sideloading the update - no format/factory reset required?
Thank you.
It is in progress.
Just sideload the update via recovery and should be good, no wipe required. Be sure to backup first!
If firmware isn’t included you may need to follow the firmware upgrade guide from Lineage.
After several months using my device with DivestOS, I have encountered several issues of which are releated to my device age. It is in fact a little old (its a Xiaomi Redmi Note 7 form 2019) and I need to install root privileges (need additional functions and other stuff). I already know that it compromises the device’s security but for my own purpose, its all right. The problem which I am facing is the fact that due to Xiaomi’s security methods, now I cannot change the DivestOS custom recovery image to the TWRP recovery image. The only method to install root, in contrast, is to adb sideload it (a feature that is present in DivestOS’s recovery images). After sideloading it, I cannot install root as the file (Magisk’s zip) is not signed by DivestOS. So, ¿what shall I do now? Thanks for all beforehand.
@Fena1
why can’t you change the recovery? TWRP or OrangeFox should work just fine.
1 Like
Basically, as I have changed the computer where I unlocked it, now when I try to flash that custom recovery images it says that there is an unknown error. In the Xiaomis app, it appears to unlock the device and when I enter in fastboot in the device, the device constantly resets. What I have managed to understand is that although I have got the previous adb keys and the necessary drivers, fastboot modifications need to be made after the app says you have unlocked the device. It is just a security measure.
@Fena1
the system where you unlocked it doesn’t matter
please try using fastboot 33.0.3: Bootloader - DivestOS Mobile
and see the USB troubleshooting steps here: Bootloader - DivestOS Mobile
@SkewedZeppelin Will Vayu no longer receive support for DivestOS 20.0? It no longer appears on the devices page in the 20.0 section. Are you unable to resolve the wifi bug?
@Zorosuro
it has been broken for 14 months now and no one else has tried to fix it
@SkewedZeppelin That’s strange, I hope that in version 21 this bug doesn’t occur. I could even help fix it, but I don’t know much about android development, and the vayu is my main device, so I don’t want to risk losing it.
@SkewedZeppelin I love Mulch but I’m not happy with two things. First and the most important:
Getting it from F-Droid. Would it not be possible to publish it in Github too without F-Droid Version? Because I don’t like the Security Issues of F-Droid. And Mulch is a secure based Browser, so it would be more accurate to publish it on Github or even Play Store or Accrescent. And the second is Content Blocker. Would it be possible to implement it? Other than that, I’m thankful for this Browser and I really hope these two things can happen!
And I would love to change my Webview to Mulch Webview. I tried it, but it don’t worked. I would appreciate it, if you could help me with that. I use LineageOS.
1 Like
What security issues apply in this context? Because there are none.
Yes, this is pending, but there are some compatibility issues.
The WebView is a privileged system component and the system only allows their usage if:
- their package ID is declared in the system manifest and the app is installed into /system
- or if their package ID and matching signing signature is declared in the system manifest and the user opted-in to it
There are some Magisk modules that let you override this to Mulch, or you can instead use a system that comes with it such as DivestOS or allows it such as CalyxOS or iodeOS.
1 Like
There is of course. Look here: F-Droid Security Issues | PrivSec - A practical approach to Privacy and Security
As a User, I need to trust you and F-Droid. Why not only you? You could publish it on Github/Gitlab as non F-Droid Version or in the Play Store. Both would be good and secure. Good of course would be Github/Gitlab. Or Accrescent would be the best.
Oh nice, when could we expect the Content Blocker? 
I tried to install Mulch Webview but I think my Phone don’t support that. I tried many methods online but it didn’t work, or I did something wrong, which I don’t guess.
No you don’t. That outdated article is primarily about F-Droid.org compiled apps, and the issues with the F-Droid client itself have largely been fixed.
Using the DivestOS.org repo to get Mulch does not have those issues and provides much more verification than GitHub would and load balances downloads across the 7 mirror servers.
And to be clear, direct downloads are available, which is no different than what GitHub would offer: Our Apps - DivestOS Mobile
1 Like
Are those direct downloads F-Droid Version? And which of them should I use? Because there are many and I don’t know which would be the best/most secure…
And why is the Website Downloads not recommended?
direct downloads F-Droid Version
they are the same exact ones you’d get from the DivestOS.org F-Droid repo: Our Apps - DivestOS Mobile
This is again another benefit of the F-Droid client, it’ll pick the correct version for your device.
I try to install the latest Lsposed or the new Lsposed forks which work supposedly up to Android 15, and none work, it crashses on Lsposed Manager opening, but I think it was working 3 months ago approx… Do you think you made a change which would explain this ?
@mohican
you might have a bad module loading
try booting in safe mode:
You can boot into safe mode by holding Volume Down the moment the ‘DivestOS’ animation starts. Release it when after it vibrates once. After booted it will say “SAFE MODE” in the bottom left.
then turn off all your modules and reboot normally and enable them one by one repeating until you narrow it down
@SkewedZeppelin Is a Xiaomi Poco X3 NFC Build possible? Since it has LineageOS 21 support with Android 14
@anon66069599
surya has been on the TODO list
2 Likes