DivestOS: long term device support with enhanced privacy and security

Originally I changed to DivestOS via TWRP. It was no problem, cause I ereased deeply.

The update I used the normal function of the Updater.

Thanks

@taragate

so it is just stuck at the Samsung logo?
I’d suggest you boot to the recovery and adb sideload the latest image again.
TWRP is not supported, use the DivestOS recovery.
Don’t wipe.
It should boot.

I test on klte before every release and have no issues on my end.

No, the Samsung goes sometimes further. For a very short moment I can see my start-screen and than it shuts down, sometimes two or even three times one after another. But it is not a loop, afterwards it stays turned off.

I’d suggest you boot to the recovery and adb sideload the latest image again.” That means, not taking the zip-file but the image-file (divested-18.1-20230122-dos-klte-recovery.img) instead?

Until now I am only used to Odin and TWRP for installing lineageOS.
So please, give me some explanations going further. My platform is Linux / Ubuntu.

Thank you very much !!!

@taragate

No, the Samsung goes sometimes further. For a very short moment I can see my start-screen and than it shuts down, sometimes two or even three times one after another.

That sounds like your battery is just low, leave it on the charger.

No, it is not the battary. I tried with adb sideload but not consequent and with real knowlidge what I’m doing. But anyway now DivestOS runs normal BUT the update from 16.04,23 failed again but not with the mistake before. It just failed and I’m not udated yet.

And now I come back to my further question:
“Until now I am only used to Odin and TWRP for installing lineageOS.
So please, give me some explanations or links going further with ADB or Heimdall going further (now added). My platform is Linux / Ubuntu.”

@taragate
do note that the latest update is always shown as an option to “update” to

if you try installing the latest update via the Updater while already running it you will get that “Update failed” notification afterwards, because it saw no change, which is expected if you already had it installed.

Right, the actual update (06.05.23) is fine now. Irritating, that this update still offers the “Installing”. In LineageOS you can erase the file. So I didn’t realize this behavour early enough.

Please, give me links of explanations “Heimdall” & ADB, Plattform Linux. Because you told me, TWRP doesn’t work anymore.

Thank you very much.

TWRP is not supported, that doesn’t necessarily mean it won’t work. But the Divest Recovery is recommended.
Please search the internet to learn to work with Heimdall.
The command for flashing the recovery is:
heimdall flash --RECOVERY <name-of-recovery.img>
Please be careful!

Thanks for the answer !!!

“TWRP is not supported, that doesn’t necessarily mean it won’t work”.

In case it works with TWRP, is DivestOS still safe and secure and an unchanged ROM?

On [ROM] DivestOS 20.0 for mata | XDA Forums it means:

"DivestOS does not support the following:

  • Google Apps (OpenGAPPS)
  • DRM (Widevine)
  • alternative recoveries (TWRP)
  • root (Magisk)
  • runtime modification frameworks (Xposed or theme engines)"

OR: " It is not recommended to use TWRP with DivestOS, …"

So there must be a reason, why not ???

Thank you

@taragate
TWRP is NOT supported: Faq - DivestOS Mobile

  • TWRP may work on select older devices
  • TWRP is actually recommended on a very small selection of devices on Motorola msm8916 series or apollo/thor due to limitations
  • TWRP will not work on file-based encryption devices due to the stronger encryption changes
  • TWRP prompts the user to install MALWARE: https://twrp.me/app/privacypolicy.pdf
    • Location information (e. g. longitude / latitude)
    • Usage information (e. g. transferred amount of data, call logs)
    • App usage (e. g. of all installed apps, their usage time, duration, volume and location)
  • TWRP is often based on outdated and insecure kernel/device trees
2 Likes

@SkewedZeppelin

I’ve successfully installed the latest DOS build on an LG G6 (H870). Everything except the camera seems to work. Even encryption works well. The camera not working seems to be an upstream problem, probably fixed in the next release or two.

1 Like

Kuketz did a writeup of DivestOS as part of their Android OS series:

1 Like

Xiaomi Mi A2 ‘jasmine_sprout’

divested-18.1-20230510-dos-jasmine_sprout-fastboot.zip
avb_pkmd-jasmine_sprout.bin

mia2-dos-brick

I was able to lock the bootloader again on my Mi A2 with DOS 18.1 like I did back in the CalxyOS days.

Mi A2 re-locked bootloader

Xiaomi Mi A2 + DOS 18.1 20230510

Relockable: Tested Working

@fossys I think it is still permissive, I can maybe set it enforcing.

edit:
Verified boot is permissive: DivestOS-Build/Enable_Verity.sh at master · Divested-Mobile/DivestOS-Build · GitHub

DivestOS is always SELinux enforcing.

(post deleted by author)

Xiaomi Poco F1 (beryllium)

divested-20.0-20230505-dos-beryllium.zip
default Lineageos ‘aperture’ vers. 13 Camera-App

After opening, the entire system is blocked, shortly after which the system crashes and reboots.

The identical process is repeated with the GrapheneOS camera apps ‘Secure Camera’ vers. 62 and ‘Simple Camera’ vers. 5.6.3 from SimpleMobileTools.