yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] skuffy:
Hello @SkewedZeppelin I have installed DivestOS on dumpling and would like to re-lock the device for security. I read through your instructions but I have a few questions, I hope you might be happy to answer (or indeed anybody else who can advise).

By instructions I mean the steps under 'Locking' in https://divestos.org/index.php?page=bootloader

Under step 1, what exactly do you mean by 'verify boot'? That the device boots as expected after DivestOS install? I thought a reason to re-lock was to enable verified boot. Do you mean two different things by verify boot and verified boot?

I have used the device for a few days with desired functionality, I have been able to update and also been able to factory reset, so I presume that fulfills the other requirements of step 1

Is dumpling an AVB device? How can I check this? I migrated from LineageOS, I certainly didn't flash the custom keys before

How will I know that verified boot is enabled after relocking?

Many thanks for all your work on this ROM.
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
1. yes, I mean make sure the device boots

2. sounds like it is working, should be safe to lock

3. dumpling/cheeseburger is a verified boot 1.0 device, not 2.0/AVB, no key flashing possible. it just trusts the keys from the system when locked

4. you'll see a yellow screen instead of an orange screen on boot

of note: this device performs a wipe when locking, so backup all your stuff first if necessary.

If anything, even locked this device is easy to unbrick thanks to EDL being available.
[OnePlus 5 & 5T Cross Device Development] skuffy:
Thank you! I have relocked and everything is working as expected.
[OnePlus 5 & 5T Cross Device Development] enzo2001:
I have few questions:

1) Do i need to use recovery from the divestos website or any recovery works fine?

2) After installing the ROM, can i flash camera patch zip in recovery for gcam?
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
1. you do not need to, but it is the only one I will support

2. you cannot flash anything else when using the DivestOS recovery. and if you do flash such modifications via another recovery there is a likely chance it will not boot

3rd party modifications and recoveries are not supported in DivestOS.
[OnePlus 5 & 5T Cross Device Development] the_Nizo:
I just tried Magisk and it works fine from what I can see. What do you mean exactly by this? I'd guess that you just didn't test it, but that wording results in something like this for some people:
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
Please read this:

Faq - DivestOS Mobile

divestos.org
[OnePlus 5 & 5T Cross Device Development] enzo2001:
Can u add the camera patch in the ROM instead because im sure many of us use gcam. And one more is it possible to replicate the google play sandbox like from GrapheneOS?
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
no.

This ROM has a focus on FOSS, I don't care to support such proprietary apps.
[OnePlus 5 & 5T Cross Device Development] hafsblau:
So DivestOS 19.1 is broken for Oneplus 5?
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
Be patient, there is no official LineageOS for the op5 yet.

The issues that it is broken are already pending merge: https://review.lineageos.org/q/proj...sm8998-common+status:open+branch:lineage-19.1
[OnePlus 5 & 5T Cross Device Development] hafsblau:
Great, was just asking because I saw 19.1 in the OTA updater.

Separate question, I use an app called "Swish" that almost everybody in Sweden uses for payment. It works great EXCEPT the QR scanning functionality - the camera is just completely black. The regular camera app works fine. I haven't encountered this before - do you know what might be the cause?

This one: https://play.google.com/store/apps/details?id=se.bankgirot.swish
[OnePlus 5 & 5T Cross Device Development] skuffy:
I noticed it has been 6 months since I started using DivestOS on my Oneplus 5T.

Since then I have been very happy with the OS. So I just wanted to stop by and say to the developer of this project: Thank you!

All of the information on the https://divestos.org/ website is great too.
[OnePlus 5 & 5T Cross Device Development] Rpbht:
Does this ROM supports work profile ?

Can we use work related apps. Here ?

Looking forward to flash but Work profile is my priority
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
Yes.

Apps like Shelter will work fine.

Actual enterprise MDM apps may or may not work.
[OnePlus 5 & 5T Cross Device Development] altromass:
Hi.

I'd like to install Divestos on my OP5 where I already have Lineageos 19.1.

As I'm not starting with the latest stock rom on my phone, as suggested, should I take extra steps before flashing Divestos?

Thankyou.
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
Since you are already on Lineage, just follow steps 7, 9, 10, and 12: https://divestos.org/index.php?page=bootloader#fastbootUnlocking
[OnePlus 5 & 5T Cross Device Development] altromass:
Great, thankyou :)
[OnePlus 5 & 5T Cross Device Development] bonswouar:
I really love the idea behind DivestOS, but I can't switch because of those limitations.

Basically the ONE root feature I don't want to loose is being able to manage my charging cycles, with https://github.com/VR-25/acc

IMO that should be pretty much mandatory on any custom OS, specially older phones, batteries don't last forever! :)

But I totally understand the reasons of not wanting root, and 100% agree on the other principles!

That's unfortunate, I guess I'll stick with LineageOS + microG..
[OnePlus 5 & 5T Cross Device Development] loparaan:
Hello, I just discovered this rom, and sorry, some issues are not clear to me:

1.- When it says that it does not support Google Apps (OpenGAPPS), does it mean that there is no way to install google services, for example to make use of apps from the Google store? I have purchased quite a few applications that I would like to continue using. If not, I don't understand doing so much emphasis on security, when it doesn't let you use the Google app store.

2.- Backup system, what system are you using? If you don't have the possibility to use google services, I understand that I won't be able to restore my phone, or use the contacts I have stored, or use the calendar for events, tasks or birthdays, right?
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
1. Apps that have a hard dependency on Play Services will not work. eg. mandatory Safetynet, in-app purchases, Play License checks, or mandatory GCM

Apps that have a fallback or work without those will usually work, and you can install them from Aurora Store.

2. Seedvault is included and lets you backup system/apps/contacts/messages to a folder, to a flash drive, or to select cloud providers

You can use EteSync or DavDroid or DecSyncCC as contact/calender/tasks provider
[OnePlus 5 & 5T Cross Device Development] cmonty14:
Hi,

I have migrated successfully from LIneageOS to DivestOS 20.

Everything is working fine.

However I cannot start banking app ING after installing it from Aurora store.

Are there known issues with banking apps not running on DivestOS?

THX
[OnePlus 5 & 5T Cross Device Development] cmonty14:
After installing DivestOS 20.0 on my device and installing all previously used apps I have identified this issue:

I cannot pair my Garmin watch with app "Garmin connect".

The issue is that "Garmin connect" crashed when it starts pairing after watch has been identified. Here's the relevant crash information:

type: crash
osVersion: OnePlus/OnePlus5T/OnePlus5T:13/TQ2A.230305.008.C1/eng.emy.20230321.233403:user/release-keys
package: com.garmin.android.apps.connectmobile:7558
process: com.garmin.android.apps.connectmobile

android.content.ActivityNotFoundException: No Activity found to handle null
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2200)
at android.app.Activity.startIntentSenderForResultInner(Activity.java:5895)
at android.app.Activity.startIntentSenderForResult(Activity.java:5858)
at androidx.activity.ComponentActivity.startIntentSenderForResult(SourceFile:2)
at android.app.Activity.startIntentSenderForResult(Activity.java:5813)
at androidx.activity.ComponentActivity.startIntentSenderForResult(SourceFile:1)
at com.garmin.android.apps.connectmobile.bic.SetupWizardActivity$q.onDeviceFound(SourceFile:41)
at android.companion.CompanionDeviceManager$Callback.onAssociationPending(CompanionDeviceManager.java:252)
at android.companion.CompanionDeviceManager$AssociationRequestCallbackProxy$$ExternalSyntheticLambda0.accept(Unknown Source:4)
at android.companion.CompanionDeviceManager$AssociationRequestCallbackProxy.lambda$execute$1(CompanionDeviceManager.java:924)
at android.companion.CompanionDeviceManager$AssociationRequestCallbackProxy$$ExternalSyntheticLambda4.run(Unknown Source:4)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7884)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ExecInit.main(ExecInit.java:48)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:355)

I could pair the watch in > Settings > Bluetooth, but then the watch is not identified by "Garmin connect" either.

Could you please advise how to fix this issue?
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
Interesting!

That is CompanionDeviceManager which DivestOS removes.

I originally removed it years ago because it was only used by Android Wear (which depends on Google Play Services which isn't included).

But it seems to be commonly used these days as you demonstrate.

I'll add it back in the next update.
[OnePlus 5 & 5T Cross Device Development] cmonty14:
Could you please share this fix with me so I can test it?

And should I report this issue in Git to make this official?
[OnePlus 5 & 5T Cross Device Development] androidtel:
Thank you for making this ROM available!

Up to date and with the possibility to lock the bootloader.

Thank you!
[OnePlus 5 & 5T Cross Device Development] androidtel:
Update to April 16 2023 DOS version with Android security update of April 5 did work perfectly.

Thank you for your work.
[OnePlus 5 & 5T Cross Device Development] androidtel:
Update to October 4th 2023 DOS version with Android security update of October 1st (!!!!) did work perfectly.

THANK YOU!
[OnePlus 5 & 5T Cross Device Development] hafsblau:
Same here :)
[OnePlus 5 & 5T Cross Device Development] fraenzken:
I'm running LineagoOS20/microG on my Oneplus5T but would like to change to DivesOS. Do I have to return to stock firmware first? Or do I have to downgrade frome LineageOS20 to 17? The device page of DivesOS directs me to the installation information on the LineageOS page, which reads:
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
You need to follow the DivestOS steps not the LineageOS steps.

Please follow the steps here: https://divestos.org/builds/LineageOS/dumpling/install.html
[OnePlus 5 & 5T Cross Device Development] fraenzken:
Thanks, I'll try that.
[OnePlus 5 & 5T Cross Device Development] fraenzken:
Is there already an ETA for DivestOS 21? LineageOS 21 has been available for a while already, that's why I ask.
[OnePlus 5 & 5T Cross Device Development] androidtel:
Update to May 12, 2024 DOS version with Android security update of May 5 did work perfectly.

Thank you for your work.

I see from your webpage that the financial support for DOS is quite limited.

Did you consider applying for a FUTO Legendary Grant?

It seems to me that DOS would qualify.
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
You're welcome :)

FUTO already generously awarded me a legendary grant!

It is noted in the special donation history section here: https://divested.dev/donate

and was noted in the March changelog: https://divestos.org/pages/news#2024-03
[OnePlus 5 & 5T Cross Device Development] androidtel:
Sorry I didn't look into to special donation section lately.

Excellent and congratulation!

What about support from the sidn fonds?
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
Interesting, this is the first I've heard of them. But I don't think I can qualify as an American.

I'll keep them on my list though, especially for some others in this area.

Thanks.
[OnePlus 5 & 5T Cross Device Development] cmonty14:
I'm running lates DivestOS divested-20.0-20240512 on my mobile device OnePlus 5T (dumpling).

From Aurora I installed Google Maps.

I can start this app, but the map is not showing any details, it is grey.

Can you please advise how to fix it?
[OnePlus 5 & 5T Cross Device Development] SkewedZeppelin:
Please do not repeat questions across multiple mediums

https://www.reddit.com/r/DivestOS/comments/1d451mq

edit:

Just tested, latest Google Maps appears to really want Play Services now.

Please follow the steps to install microG here: https://divestos.org/pages/faq#microgEnable

You don't need to enable any other options.
[OnePlus 5 & 5T Cross Device Development] cmonty14:
THX.

Google Maps is now displaying the map correctly.

However routing between 2 locations is not working after revoking Network permission from the microG app.

Can you confirm this?
[OnePlus 3 & 3T Cross Device Development] :
With relocking support based on the right signing, this would be a nice upgrade to a more secured and hardened LOS variant!

Is DivestOS recovery a 'rebranded' LOS recovery and/or does it give functionality like command line and file browser like TWRP?
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
The signing bit is a predicament.

DivestOS is signed with release-keys, including for verity.

But the oneplus3 bootloader appears to only accept test-keys, and won't lock.

It is likely possible to simply not perform the verity signing, leaving the default test-keys for verity and release-keys for system, but I do not have a device to personally test it with.

As for the recovery, it is indeed rebranded LineageOS recovery with a few minor tweaks.

Files are not expected to be edited from recovery, as no modifications are officially supported to /system.
[OnePlus 3 & 3T Cross Device Development] sinkoo1979:
Running smooth on my Oneplus 3. Thanks for the rom
[OnePlus 3 & 3T Cross Device Development] :
Locked BL or not?
[OnePlus 3 & 3T Cross Device Development] sinkoo1979:
not
[OnePlus 3 & 3T Cross Device Development] Antsu:
Hey @SkewedZeppelin

Question about kernel patches. Even though the version of the kernel isn't upstreamed, from 3.18.124 to 3.18.140, could it be considered that there are the same patches than in actual upstreamed 3.18.140 kernel has?
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
That is a hard question to answer.

Does the shipping kernel include some of the 3.18.124-140 patches? Likely. All of them? No.

Does it include patches that aren't in those? Yes

Would it be helpful to be updated to 3.18.140? Yes, but that takes a non-trivial amount of effort, and moreso to bringup all the other devices too.

Patches welcome.

Of extra note, 3.18 is still maintained jointly by Google/Linaro and receives monthly updates, hence why there are so many 3.18 patches in my CVE repo. I use the CIP scripts to automatically identify the corresponding patches in the Google repo, and pull into my patch repo.

For example, 3.18.140 was released 798 days ago, but through my patcher the oneplus3 kernel is mitigated against CVE-2021-33909 despite only being published 2 days ago.
[OnePlus 3 & 3T Cross Device Development] :
Hi @SkewedZeppelin, thanks for your work. Are you planning a degoogled version (without connections to Google) for this amazing Rom?
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
What do you think DivestOS does to disqualify it from being degoogled?

The captive portal check is the only periodic connection to Google and that has a toggle in the Settings app.
[OnePlus 3 & 3T Cross Device Development] :
I was talking about connectivity check and fallback dns. These things, obviously, don't disqualify your work.
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
Fallback DNS is Quad9, not Google.

Network Connections - DivestOS Mobile

divestos.org

Privacy Policy - DivestOS Mobile

divestos.org
[OnePlus 3 & 3T Cross Device Development] :
I did a mistake, sorry
[OnePlus 3 & 3T Cross Device Development] :
Next week will be a nice moment to install Divest ;-)

As I understand from the website, locking BL still not supported on OP3t?
[OnePlus 3 & 3T Cross Device Development] :
I do not want to end up with a brick so I would like to ask for some clarification what "Relockable: Yes, test-keys only?" means? Some downloads are provided with avb key to flash before relocking. What do test keys mean and how do I flash them?
[OnePlus 3 & 3T Cross Device Development] :
At this moment I think it is not possible to relock for the OP3T as I understand:

https://xdaforums.com/t/rom-divestos-18-1-for-oneplus3-t.4285915/post-85114089

Some info about the test keys can be found doing a simple Google search, but not 100 percent sure if this is what you ment:

Sign builds for release | Android Open Source Project

source.android.com

mjg59 | Self-signing custom Android ROMs

mjg59.dreamwidth.org

For me this issue is the reason I did not try DivestOS already but kept my LOS installation.
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
The issue with op3, is that when locked it seems it will only boot a test-keys signed image.

But locking with a test-keys signed image largely defeats the purpose of locking.

Because anyone can just sign their malware with test-keys and flash it over no issue.

You should note however that locking is one of many security features DivestOS offers over other ROMS. op3 for example has well over 400 kernel security patches, far fewer proprietary blobs, out of box ad/tracker blocking, along with a hardened and rapidly updated WebView among many other features as documented on the website.
[OnePlus 3 & 3T Cross Device Development] :
Good explanation, thanks.

It would be nice though if, even when it is not for the purpose of safety, it could be locked again to remove the ugly warning at boot. But you are right, it is not giving an extra layer of security, in fact for the OP3T I think it is only cosmetic, so not a reason not to switch... ;-)
[OnePlus 3 & 3T Cross Device Development] :
When you want me to test something without the risc of bricking, please let me know ;-)
[OnePlus 3 & 3T Cross Device Development] Dimon76:
Can you put a magisk for root? And for hiding banking applications
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
DivestOS does not support root or any such system modifications.

DivestOS is largely secure out of the box and making such changes throws that security out the window.
[OnePlus 3 & 3T Cross Device Development] smartpr1v4t3:
Hi,

i tried today the Rom and it is running fine.

Will report if i find something
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
Did you have the "sensors off" toggle enabled?

It blocks mic/camera/sensors.
[OnePlus 3 & 3T Cross Device Development] smartpr1v4t3:
Haha, yeah i edited already my post :D

I find it some minutes after posting. Had the "sensors off" toggle enabled.

Didnt know it was also for camera ;)
[OnePlus 3 & 3T Cross Device Development] Dimon76:
┤Mod Edit├┤Adding automated English translation├

Spoiler content hidden.

Spoiler content hidden.
[OnePlus 3 & 3T Cross Device Development] lapirado:
How's that?
[OnePlus 3 & 3T Cross Device Development] TempAccount10001:
@SkewedZeppelin Could you please check if you can enable an option to disable notification panel ( tiles) in lock screen.
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
Some tiles are already restricted from use on lockscreen, I might make more restricted in the future.

But I have no intent on adding a toggle to disable the quick tiles menu all together.
[OnePlus 3 & 3T Cross Device Development] TempAccount10001:
@SkewedZeppelin

I have another question.

What happens if I use a custom kernel?

Does the hardening stuff you implemented in divestos still works.

Thanks you for the rom :-)
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
You would lose all kernel hardening and CVE patching (a few hundred security fixes).

I do not recommend it.
[OnePlus 3 & 3T Cross Device Development] jiraianam:
How can I relock the bootloader, please someone share the file for re-lock the bootloader
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
You cannot relock the bootloader of this device.
[OnePlus 3 & 3T Cross Device Development] jiraianam:
This is not truth look this NLOS they create a file for relock bootloader an in this ROM the dev write "October 2022: a user recently reported bootloader locking this device without issue"

[ROM][SDCLANG-6][microg ready][OMS exPosures]NLOS-16.0] - 20220430

NLOS is an unofficial unified LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build. Thanks to @UnbracedTundra NLOS...

xdaforums.com

I want relock the bootloader of this device, please someone help us. THIS OS IS THE LATEST SECURITY UPDATES OF 05, MAY.

Please someone too can create a file for relock bootloader of https://doc.e.foundation/devices/oneplus3

DivestOS and /e/OS is the most updated rom of the op3 and come with a lot features for privacy ready. Please someone made for us the file for relock bootloader in this two OS
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
You cannot relock this device with official DivestOS as the bootloader wrongly only trusts test-keys.

You would have to resign DivestOS with insecure public test-keys to be able to relock it.

Relocking with test-keys is useless.

Goal of relocking is to ensure updates are all signed before installing.

Relocked with test-keys means anyone can sign whatever with test-keys and install it regardless.

Relocked with test-keys == not-locked.

There is no special file that will let you relock it. op3 is not an AVB device.
[OnePlus 3 & 3T Cross Device Development] unnilinux:
Hi any guide or steps to go back to lineage os ?

flash twrp via fastboot and flashing lineage from recovery is failing with error 1
[OnePlus 3 & 3T Cross Device Development] SkewedZeppelin:
Just flash TWRP or Lineage recovery via fastboot.

The DivestOS recovery won't allow flashing non-DivestOS files.

And go back to what? Lineage dropped support for oneplus3t.

Is there a particular issue you are encountering that could perhaps be fixed?
[General Questions and Answers] tze_vitamin:
I won Mi community, Redmi note 9 pro 5g, I am from Serbia. We don't have this phone here , because it's only for Chinese market.

I have Redmi note S2, my first phone, Redmi note 7, Redmi note 8 pro , Poco f2 pro, and this ..

I try all this phone to use without mask but very fast I got micro scratches,and little bigger..

On this phone ,I use it without mask and after almost there weeks ,no single scratch,not even little micro scratch on back.. the phone is good and safe like now.

Is it possible that material for Chinese market is better than frome Europe?

Is possible, that make some big changes in quality?

Redmi note 7 after week of wearing without mask was terrific on back... So scratch at back that I barely sold him...

Why they so make so big difference..

I understand that this Xiaomi is Chinese brand, but it about e the same for all ..this is not far for customers..