bad luck there was a small time slot where a build was online without enforcing. I have mentioned that in my automation channel, always a good idea to keep an eye on it.I think yes i have thé last build. No ?
And yes i have execute the command in a terminal for the OTA but no update.
Done with succes! thxbad luck there was a small time slot where a build was online without enforcing. I have mentioned that in my automation channel, always a good idea to keep an eye on it.
Please flash the latest ROM which has the same date as yours in recovery manually.
Are there any more detailed guides to flashing this? It seems I can only manage to bootloop the phone when flashing twrp unless there's something I'm missing.
Pls see: https://code.binbash.rocks:8443/MVA...mmit/bfb5fe5ef00980739a72f50ed8376dfc12c20813News about SHRP: I understand that the recovery is expected to ask for a decrypting password at boot when /data is encrypted. Since SHRP does not ask for my PIN, I tried to force decryption via command line (https://twrp.me/faq/openrecoveryscript.html) and got the following:
SHRP's current behaviour is then expected.Code:
j5y17lte:/ # twrp decrypt ******** Attempting to decrypt data partition or user data via command line. No crypto support was compiled into this build. j5y17lte:/ #
FBE (FILE based encryption), encrypts just files not a whole partition (which is done by FDE, Full Disk Encryption). So the recovery just see files there. It does not know anything else (e.g. that these are encrypted files) as this has been disabled in my recovery builds (bc - as said this is not working and might never will).Shouldn't the recovery try to backup the whole data partition as a single
encryptedfile then? Yet the log shows a per-file approach:
788.| I:addFile '/data/misc_de/0/xnnZ+wmTPfWXkfeWumVXaD' including root: 0 789.| ==> set selinux context: u:object_r:storaged_data_file:s0 790.| I:addFile '/data/system' including root: 0 791.| ==> set selinux context: u:object_r:system_data_file:s0 792.| I:addFile '/data/system/EKRwi+BdRece6DSbSzpxxB' including root: 0 793.| ==> set selinux context: u:object_r:system_data_file:s0 794.| I:Error adding file '/data/system/EKRwi+BdRece6DSbSzpxxB' to '/external_sd/TWRP/BACKUPS/5203ac375f5ab43b/2021-04-07--18-44-04_e_j5y17lte-userdebug_10_QQ3A200805001_30_UN/data.ext4.win'
Anyhow, the problems is this: The standard Camera app from /e/OS takes photos just fine, but videos are corrupted somehow. Playback shows only a still image and video length is shown as 98 hours or something like that. Gallery app shows other videos just fine, and the corrupted videos cannot be played on laptop either, so the problem really happens when saving the video.
The workaround I discovered was to install the CameraMX app from Apps. Videos taken by it are also corrupted, *but* if its FX mode is enabled, videos are saved correctly. Even if no effects are enabled.
/* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * Please do some research if you have any concerns about features included in the products you find here before flashing it! * YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. * Your warranty will be void if you tamper with any part of your device / software. * Same statement for XDA. */