Thank you … this was the odd thing in my mind. If I am right to assume that this was a transitional build to help users who had missed updates due to the outage I would have expected this to have arisen earlier for you.
In that case to my mind the natural Upgrade path would be to e-2.4.1-t-20241008439851-official-FP3. This is an
- older build 2024-10-08
- newer /e/OS version
e-2.4.1 - Android Upgrade to AOSP 13 (T)
Next to consider, do you have a backup of essentials?
One should not attempt an intervention like this without a backup of essentials and realising the risk that it might not work.
Warning risk of possible failure
These are the links to the OTA_PACKAGE (1.1G) and sha256sum
- https://images.ecloud.global/official/FP3/e-2.4.1-t-20241008439851-official-FP3.zip
- https://images.ecloud.global/official/FP3/e-2.4.1-t-20241008439851-official-FP3.zip.sha256sum
Do you have a PC available to apply the update by adb sideload ?
This post demonstrated the method under different circumstances to apply the OTA update on certain “broken phones”. Can you sift though that method to see what is required in your case? Feedback for v3.0 - #203 by nicofonk. Please ask if anything is unclear.
There is always the possibility that the Updater will deliver eventually; all my suggestions about restart were simply to bump the Updater following Clear storage in the Updater.