In reply to @omori:tchncs.de
files that are deleted are not recoverable, see https://grapheneos.org/faq#encryption

jbnm: costco cow wholesale As I understand it, it is possible to use special recovery software/techniques to recover files in a user profile if you are able to unlock the profile. As it is flash storage the only way to reliably make files unrecoverable is to delete a secondary user profile (or factory reset for the main profile). This reliably flushes the encryption keys for all data in that user.

Alternatively you could create and keep files in an app which use the Titan security chip/strongbox to encrypt files and supports deleting the keys from strongbox (i think that, depending on app design, this may take clearing storage on the app). Would have to be careful to only use said file with other apps that dont end up creating a copy of it (eg. some gallery apps may create a thumbnail)

Although its beta/not mature this app uses strongbox and makes it possible to create files & take photos within its encrypted storage
https://github.com/Secure-File-Manager/Secure-File-Manager/wiki/Frequently-Asked-Questions/_edit#how-are-my-files-encrypted

A better app design would use Storage Access Framework. This would provide the possibility to work on encrypted files with other apps while keeping them encrypted.

In reply to @maade93791:matrix.org
if your not building with root

jbnm costco cow wholesale
Could also create and keep files in other encrypt storage apps that dont use strongbox. The possibility to recover files deleted from such storage would likely also be difficult but likely not such a strong guarantee as if the app used strongbox.

Safest/easiest way is to delete the user profile. Would then be certain that you had also deleted any copies other apps that accessed the file could have made

In reply to @candidlurker:matrix.org

Hi, do the kernel build scripts for 6th gen Pixels at some point forcefully set LTO=thin?

I'm asking because I compiled the kernel with full LTO (LTO=full BUILD_KERNEL=1 ./build_bluejay.sh) out of curiosity. Then I generated deltas and deployed the update to my P6a via my local update server. To my surprise the update went smooth and the device rebooted just fine. On the device under settings I see the build number I used for this specific build. So I assume the newly built kernel did boot... 🤔

Trying to rebuild the latest stable bluejay (pixel 6A) release here. I get an error of a missing abl.img file when running "m target-files-package".
Here's a log:
++++ radio ++++
Traceback (most recent call last):
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/internal/stdlib/runpy.py", line 196, in _run_module_as_main
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/internal/stdlib/runpy.py", line 86, in _run_code
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/main.py", line 12, in <module>
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/internal/stdlib/runpy.py", line 196, in _run_module_as_main
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/internal/stdlib/runpy.py", line 86, in _run_code
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/add_img_to_target_files.py", line 1098, in <module>
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/add_img_to_target_files.py", line 1090, in main
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/add_img_to_target_files.py", line 1006, in AddImagesToTargetFiles
File "/home/user/grapheneos-13/out/host/linux-x86/bin/add_img_to_target_files/add_img_to_target_files.py", line 628, in CheckAbOtaImages
AssertionError: Failed to find abl.img
10:24:50 ninja failed with: exit status 1

failed to build some targets (02:26 (mm:ss))

I can't find abl.img in any of the ota/factory images of bluejay. What am I doing wrong?