there were no additional accounts set up - “multiple users” was deactivated and the OS was nearly on stock.
nevertheless i made a factory reset which helped (a little) - i could set the device-owner. installing the extension after factory reset is also suggested on the developers git page.
the privilged extension isn’t working anyway. description see here
@SkewedZeppelin: i’m still wondering, would you care to share your thoughts on this please?
Thank you for your great work on the rom and making privacy a little bit easier to achieve!
1 Like
The FDroidPrivExt has been dropped due to breakage caused by the per-app sensors permission patchset.
Source:
1 Like
Thank’s for the feedback. Indeed “now” the camera works again (did a update meanwhile)… not sure if it was my stupidity or there was really a release that had a non working camera… any way’s - doesn’t matter, I’m up2date and the thing is flying 
Thank’s a million for your ongoing great work @SkewedZeppelin 
1 Like
OnePlus 8T (kebab)
OnePlus 9 (emonade)
OnePlus 9 Pro (lemonadep)
Relockable: Yes, Untested
OnePlus Android 12 firmware - relocking no longer works :: COS News
@SkewedZeppelin
Could this finding also mean negative consequences for DivestOS in terms of bootloader relock?
@fossys
Yep, as it stands it is not good.
Hopefully a workaround will be found or OPlus will add it back.
on an oneplus6/enchilada i get the following, trying to do the AVB-parts (i followed the instructions each step and it worked on a fp3 perfectly):
$ sudo fastboot erase avb_custom_key
Erasing ‘avb_custom_key’ FAILED (remote: ‘Partition doesn’t exist’)
fastboot: error: Command failed
the system runs smooth, though.
is it safe to lock the bootloader again?
–
update: after understanding, that the fastboot that can be started from recovery is a different one that can be started by volup+power & using the second one i could run the erase-command successfully.
(thanks to this reddit)
anyhow this is just hanging afterwards:
$ sudo fastboot flash avb_custom_key ~/Downloads/avb_pkmd-enchilada.bin
do you have any thoughts on this? is there a way to check whether the command was succesful?
You need to use fastboot not fastbootd.
fastbootd is entered from the recovery and is purple and has touch support.
fastboot is the volume buttons only menu that prints out device information.
If it is hanging, it likely did not complete. Try another cable or try a USB 2.0 port/hub.
cool, thanks! with your hint about an usb-2.0-hub it worked!
I have worked recently on better documenting known issues.
See now the:
any suggestions/additions welcome!
2 Likes
The new pages look good. One small tweak on the broken (known issues) page would be to group together on the System notes section, the things that are not supported by DOS (changing IMEI, Gapps, micro g, sandboxed gplay, alternate webview, remote desktop and signature spoofing) to lessen a little bit the wall of text. You might also want to include root support as a bullet point, with a link to the FAQ page explanation.
1 Like
Good suggestion, did and done!
Hello,
firstly: I really appreciate the project and all the work that has gone into it, as well as the helpful community.
I installed the latest build of DivestOS 18.1 on my FP3 today following the instructions on the DivestOS- website after having run LineageOS for microg for almost two years. As I`m not very experienced in installing custom ROMs I stuck with 18.1 as opposed to the still untested 19.1.
During installation I encountered some (hopefully minor) problems:
Initially, updating fastboot using fastboot update divested-18.1-20220711-dos-FP3-fastboot.zip did not work stating fastboot: error: boot partition is smaller than boot image. I couldn’t find helpful advice on the internet, so I went ahead and sideloaded copy-partitions and DivestOS using the already-in-place LineageOS-Recovery (as there was no specific DivestOS Recovery available for FP3). As (probably) expected, the update package signature couldn`t be verified.
After sideloading, I went back to bootloader and followed the instructions about flashing the custom AVB-keys.
DivestOS now boots without a problem an is working flawlessly so far.
Now I`m wondering if the two problems I encountered (not being able to update fastboot; not being able to verify the build signature probably due to using the LOS-Recovery) might cause any problems when trying to re-lock the bootloader. I really want to avoid bricking the device, yet being able to re-lock was one of the main reasons to switch ROMs.
Any advice is appreciated. If you need more detailed info or logs I can provide those, but please tell me how to obtain them as this is the first Custom ROM I installed by myself.
While the fastboot update method is recommended for initial installation, it doesn’t actually seem to work on all devices it is supposed to.
So the way you installed is fine.
Alright, thanks a lot for the support! Just a couple more questions that arose in the meantime:
- Will there be further updates for the 18.1 branch, or do i have to upgrade to 19.1 early on in order to check update functionality before relocking?
- The DOS-Website states under “Installation → Fastboot → Locking” that I should “verify the ability to factory reset”. Is this a must, given that I’ve already put some work into post-installation setup?
- Under “Post installation → Advanced” in the section about locking the bootloader it says “Be sure to flash our recovery first” - seems not to be a problem given that for FP3 the re-lock is “reported working”, or might that be different using the above mentioned recovery?
Best regards
- a cycle or two after 19.1 is reported working I’ll stop building 18.1 for it.
- locking should work fine, and others have already tested it, however do note that locking will wipe again
- you must always use the DivestOS recovery when locked. however for fp3 there is no recovery to flash as it is integrated with the boot partition.
Great, thanks again and props for the timely support. Guess I’ll wait for the next 18.1-update to check, and then as soon as I can bring up the time relock, upgrade to 19.1 and report back here.
@SkewedZeppelin
I upgraded to 19.1 (divested-19.1-20220713-dos-FP3.zip) without encountering any issues so far. Display, charging, voice calling, networking, bluetooth, camera and location seem to work. Is there anything else I should check out for device testing?
Do you know of anything comparable to the above mentioned firmware issues on OnePlus-devices that might make an FP3-relock more risky running Android 12 as compared to 11?
Is unofficial build supported? If so, I would love if you can add my device General - [CLOSED] DELETED | XDA Forums
@doktorbrausefrosch
Does the fingerprint reader work? I’ve had inconsistent reports that it does and doesn’t.
And, FP3 relock should be fine.
That wasn’t an issue with OnePlus as much as it was a deliberate choice from what is known so far due to the Oppo and OnePlus merger.
@nix
Unlikely