The system updater should not behave like this. I have found the updater fully automated just like the images in Post #1.
If your “previous” version is running correctly, perhaps it will download the update again if you refresh the Updater … perhaps after a reboot.
great to hear it should not behave like this. Now just finding why it does with me and what the solution is.
e OS seems to be running just fine, phone has rebooted several times, update has been downloaded several times. But problem is still the same.
I assume the bootloader being unlocked is not the problem (i’m not very experienced with this, and i have read i should not re-lock the bootloader when e OS is flashed on it, but just checking, since that is the only thing i currently can think of what might be causing this update-problem).
I’ve for now followed the ‘adb sideload’ route, which enabled me to get the update stick on the phone (i did get a ‘signature failed’ message at 47%, but i downloaded the zip from /e/OS community beyond1lte download). Same for both the 2.7 and 2.8 update/file. Thank you.
Correct, the rule of thumb is “if the install instructions do not mention to lock Bootloader do not attempt it”.
There have been reports on the forum that e-Recovery fails for certain builds [2] – at Gitlab: [1].
I think it is worth noting your experience in the build-feedback threads:
[1] I find one Gitlab backlog issue for beyond1lte
This sounds close (??) to your issue. You might comment there.
I think it is worth recording your exact build_version_string and please can you check the version which currently displays when booted into e-Recovery, perhaps an image just in case anything else is revealed.
[2] A fix is proposed here Feedback for v2.8 - #4 by WillemR
It is a flaw in the update process but if you use my trick , the update will succeed.
It seems to work on all S10, S10e, S10+ and more, even on a tab.
With the message of signature fail, just continue.
When it rebooted into recovery with that error.
I did choose,
Advanced
Enter fastboot
Then back again with,
Enter recovery
After that, the OTA update continued and updated recovery and /e/OS/ to 2.8-u.
So for now everything went fine afterall.
The signature fail message is due to the name changing from
stable to official and dev to community