i am going to be buying a new smartphone.
i just stumbeled onto divestos.
i would like to try it.
i looked in faq for recommended devices.
the recommended pixel devices including
the new 4 series are very minimalistic.
i would like say a 12g 256g oneplus 7 pro.
are devices in this range doable. I dont mean
currently supported necessarily.
comments suggestions?
snd, is there a proper divestos forum?
If you are buying a new phone and have the budget, get a Pixel 3 or a 4 and put GrapheneOS on it.
DivestOS has more of a goal to provide support to older devices in order to increase their lifespan.
LineageOS has good support for OnePlus devices, I will look into adding them to DivestOS.
Samsung Galaxy S5 (klte)
I tried three 9-pie ROMs and three Recovery on the S5 (klte): LineageOS 16.0 - divested-16.0 - /e/OS e-0.9-pie as well as TWRP Recovery 3.3.1-0 / 3.4.0-0 and divested-16.0-recovery
Except for the DivestOS Mobile files TWRP’s and ROM’s could be installed and operated without complications.
I tried to install DivestOS Mobile Recovery with TWRP (.img) and after conversion with ODIN 3 (.img.tar). After an immediate reboot into the recovery no Divest Recovery started, but the S5 (klte) showed in the boot loop only for a moment the Samsung S5 logo but no Divest Recovery.
I tried to install the DivestOS Mobile ROM divested-16.0-20200724-dos-klte.zip with TWRP 3.3.1-0 and 3.4.0-0. In vain. The S5 (klte) showed the Samsung S5 logo but no DivestOS ROM in the boot loop only for a moment.
Yes, I read it (in red color) Broken. But this hint was already on the website since end of May 2020.
Now, two months later it was updated - with the identical error as mentioned here.
divested-16.0-20200510-dos-klte-recovery.img
divested-16.0-20200510-dos-klte.zip
divested-16.0-20200724-dos-klte-recovery.img
divested-16.0-20200724-dos-klte.zip
What is the point of a new DivestOS build if the old one, and a serious bug, hasn’t been fixed?
i plan on purchasing a larger phone
than any of the phones listed as
supported. 12gb ram 256 or 512gb
storage. Will that work?
Pixel 3
When tempted by used Pixels, I remember supporting the used hardware market indirectly supports the new market. I want more devices with replaceable battery and sd card, so Pixels are out.
12gb ram
At least that takes advantage of 64 bit OS capability, but seems excessive for a tracking device. 
@fossys
Can you test something for me?
Extract the boot.img from a recent LineageOS 16.0 for klte.
Flash DivestOS to your klte.
Then flash the LineageOS boot.img.
Tell me if that boots.
Thanks.
also of note, there are many different klte variants.
This one is only for the following as detailed on the LineageOS wiki:
SM-G900AZ
SM-G900F
SM-G900M
SM-G900R4
SM-G900R7
SM-G900T
SM-G900V
SM-G900W8
SM-S902L
did you send this to the right persion?
@fossys
When recently installing an incremental update on my device, while plugged in, it restarted (vendor logo) several times before eventually starting properly. After 2-3 restarts I unplugged it. I don’t recall seeing this during first install, but I also usually go for coffee during first boots. Maybe these are something to try - disconnect from power, and coffee. (no logcats saved)
I know that LineageOS and /e/OS do not support other models than this “klte”: G900AZ/F/M/R4/R7/T/V/W8 + S902L.
That’s my device informations:
adb shell getprop ro.product.device
klte
adb shell getprop ro.product.model
SM-G900F
adb shell getprop ro.product.name
lineage_klte
Yes, my SM-G900F “klte” boots now, but - divested-16.0-20200724-dos-klte-recovery is not working.
Divested-Recovery. I have tried six different variations of the installation. Starting point was TWRP 3.3.1-0.
the file “divested-16.0-20200724-dos-klte-recovery.img” was installed via TWRP and immediately booted into the recovery again.
ditto, - but battery removed, then tried to start the recovery by key combination.
the file “divested-16.0-20200724-dos-klte-recovery.img” was installed via TWRP and immediately booted into the system.
ditto, - - but battery removed, then tried to start the system by pressing the POWER key.
odin 3 (with uncheck auto-reboot) flashed the converted file “divested-16.0-20200724-dos-klte-recovery.img.tar”, removed the battery, then started the “klte” into the recovery.
the converted file “divested-16.0-20200724-dos-klte-recovery.img.tar” was flashed via Odin 3 (incl. auto-reboot), the battery was removed, and the “klte” rebooted into the system immediately.
1.-6. each time the identical result: Divested-Recovery was not installed. DivestOS Mobile did not start any more, i.e. in an endless boot loop the following order was displayed:
RECOVERY BOTTING… (blue font color)
Set Warranty Bit : recovery (yellow font color)
Samsung GALAXY S5 (white font color on black background)
With the installation of Divested-Recovery the DivestOS was paralyzed at the same time. As soon as I flashed TWRP 3.3.1-0.img.tar with Odin 3, no matter if with no battery removal, TWRP Rocovery started properly and also(!) DivestOS divested-16.0-20200510-dos-klte booted correctly.
The very first boot process showed a text based error message for less than two seconds in the lower left corner. It went too fast, on the other hand I was surprised and could only read: “A error has occurred … javascrpt”
This error message became fully visible twice more with the first homescreen. Again it went too fast to hold on to. But it must have been at least six to eight test lines. Any reproduction was not possible. I couldn’t take a picture until now. although I turned the S5 on and off several times.
DivestOS Mobile build divested-14.1-20200723-dos-herolte could not be tested with my SM-G930F
The DivestOS installed with TWRG 3.3.1-0 did not start, which means that the device booted and stopped immediately after the Samsung Galaxy S7 logo was visible. No boot loop, nothing. Just standstill.
I did not even try the DOS-herolte-recovery, nor do I remember my experiences with the S5 SM-G900F.
Hej @SkewedZeppelin,
since November 2019 Google has not released any security patches for Android 7.1.2. How do the latest Android security patches get into the build divested-14.1-20200723-dos-herolte?
FYI, I have 3 problems with the latest update/version on shamu. (1) When powered off for shutdown, it immediately powers back on (another reason for removable battery). (2) It takes 2 “boot cycles” (from Google logo to Pin entry screen) to start up. (3) People on calls still cannot “hear me now.” #1 freaks me out.
Hello, Divest Computing Group representative!
I’m somewhat frilled to see the new custom ROM on the scene, whose authors reasonably recommend rather neat app collection (like, Loop Habit Tracker), refer to some advanced projects (like, GrapheneOS), and overall deliver an integral message (like, “choose your computing and networking environment wisely”).
Okay, here’s a humble request and a couple of user feedback messages:
–
SkewedZeppelin, can you, please recommend some simple Android smartphone to use as a daily driver, that is already used by any of the core development team.
–
And there’re some issues with
–
Samsung S3 recovery from
divested-14.1-20200723-dos-i9300-recovery.img
a) can’t mount data partition when formatting /data
b) can’t install the divested-14.1-20200723-dos-i9300.zip
as it complains that it “failed to map file” note,
although twrp 3.0.2 can do the trick.
–
Samsung S3 experience is the most fluid I’ve ever got with other S3 ROMs, though these browsers
won’t work:
they’ll just crash after briefly loading a blank screen,
though
are working just fine.
–
As for the Nexus 10, the
divested-14.1-20200723-dos-manta.zip
can be installed and booted (tried via twrp),
though it persistently crashes at the greetings screen after a couple of seconds.
It’s not a big deal, if the problems are too tedious to correct, as I’ll just use some other ROMs, but nevertheless be glad if it can be helped.
Respectfully,
m1k.
several times before eventually starting properly
That is concerning
takes 2 “boot cycles”
Can you clarify this? Like step by step.
When powered off for shutdown, it immediately powers back on
I’ve seen this with thor, I know it was likely related to the defconfig hardener but my thor broke last month.
Yes, my SM-G900F “klte” boots now
I will make some testing kernels when I can that have different things disabled to see if we can narrow down what breaks boot.
Google has not released any security patches for Android 7.1.2
LineageOS team manually merges in applicable security patches to all of their branches from the Android Security Bulletin.
The limitations of this is that they cannot update vendor blobs and in most cases do not apply kernel patches.
They also do not implement patches from the Qualcomm Security Bulletin or the Google Pixel Security Bulletin.
So when possible it is best to have a device with a recent kernel and having the latest version of LineageOS (currently 17.1).
DivestOS partially migtigates the blobs by removing as many as possible and partially mitigates the kernel patches by patching many known CVEs. But it is only a patch.
Divest Computing Group representative!
It is just me 
refer to some advanced projects (like, GrapheneOS)
I wouldn’t be here if it wasn’t for Micay.
although twrp 3.0.2 can do the trick.
Did you ever use a partition resizer script?
they’ll just crash after briefly loading a blank screen
So no browsers work? That is very concerning. And strange, can you get a trace from logcat?
though it persistently crashes at the greetings screen after a couple of seconds.
I suspect there might be some selinux denial causing a service to crash.
I’ll have to make a testing build.
2 “boot cycles” (from Google logo to Pin entry screen) to start up.
clarify this? Like step by step.
Hit power button, select power off. Watch it shutdown. Wait a few seconds.
Google logo appears, DivestOS logo appears, Pin entry screen appears.
Enter pin.
Watch previous step repeat (G logo, D logo, pin screen).
Enter pin.
See normal/launcher screen.
@SkewedZeppelin,
you have marked the Samsung Galaxy S7 SM-G930F (herolte) as “broken” on their website.
It’s a pity that you don’t have more to say about it.
Well, today I started a second attempt, and - even if only with your trick³ - got my “herolte” to start. This time I was also able to document the error message “A error has occurred” in a screenshot.
³As boot.img, I used a lineage-14.1-20200725-UNOFFICIAL ROM with kernel version 3.18.14x by exodusnick, which in turn gets its source code from the highly regarded developer Ivan Meler.
Hello, Divest Group,
Only one lad(y) - whoa!
Impressed++
Although a bit scared and unsure of resizing partitions on an Android device (without a spare device on hand that is).
As for the i9300 logs, here they are:
Mull - i9300_mull.log.zip (26.0 KB)
Bromite - i9300_bromite.log.zip (9.9 KB)
(used pidcat to get logcat for a selected app)
Respectfully,
m1k
We have two repos for F-Droid, one for apps we created/maintain and another for unofficial builds of other FOSS applications that aren’t available elsewhere. These are already included in DivestOS, and are only here for other F-Droid users.
No! Since I got to know DivestOS Mobile here two months ago, the two “F-Droid Repos DivestOS Official & DivestOS Unofficial” are not available to me.
I think its actually normal for repos to return 403 forbidden if you attempt to access them with an ordinary browser. Those URLs are intended for the F-Droid client.
There is no directory listing or a start page. You can see that it works if you put the URL in the F-Droid client. You can also check in your browser if the index-v1.jar is available:
https://divestos.org/fdroid/official/index-v1.jar
for older indexes there is the index.xml
Often there is also an index-v1.json which you can directly search in the browser:
https://divestos.org/fdroid/official/index-v1.json
Well, I know I don’t know anything, and I know I’m not flawless.Nevertheless I assume from normal user, if I am offered Links on the DivestOS website, that I should click on them with my PC Browser and my FOSS browser to be able to see the content.
As shown above and here the screenshot of the Phone FOSS Browser. The FOSS browser shows the identical error message.
The How to Add a Repo to F-Droid I could work from. I noticed two hints (once at the top, once at the bottom of the picture with a red border).
Thanks @marzzzello,
but can you please show me how to enter the URL into the F-Droid client anyway. Right now my brain cells are blocked.
In the end I still don’t know what is behind the link “DivestOS Official”.
