Galaxy S9+ ‘star2lte’
- /e/OS ‘Q’ build 2021.04.15 : dev (Android 10)
- /e/OS ‘Q’ Version 0.16 eRecovery
1 Like
Hi Manoj & everybody
I have a Samsung Galaxy S4 Mini (International LTE) running “serranoltexx” 0.13
No update since [e-0.13-n-2020121089402-dev-serranoltexx.zip]
I have just seen an recent opened issue : “Build in failure for serranoltexx” on gitlab:
I wonder if I can help solve this issue ?
I am quite a newbie, but I can help if I am well managed. I rooted and installed my ROM by myself 2 years ago.
Thanks and Bye
I’m writing this message from my Yoga Tab 3 (YT-X703F), freshly updated to 0.16 Pie 
Thanks to /e/ team ! 
@mcmd I have TWRP too on an S9 and was able to update without any extra/manual steps. I’d just try it and see what happens for you.
I’m going to check later if the stock calendar app still has the bug of too many notifications.
1 Like
Upgrade failed for me on Sony z5c currently on 0.15 Q. This is my first time attempting an upgrade, so it’s possibly something I’m doing wrong.
Two things I didn’t understand, the update was for 0.16 but the “Apply update” screen said “you are about to upgrade to 0.15”. And the other thing was " this feature requires a compatible recovery or updates will have to be installed manually" - I don’t know what this means or how to go about ensuring I have a compatible recovery.
Hi @mike_from_ireland
I’ve just raised an issue in gitlab about this #3014 OTA Update fails to install. The workaround is as follows:
- Manually reboot into TWRP
- Choose ‘Install’
- Navigate to the directory `/data/lineageos-updates/
- Select the downloaded zip file in that directory
- Proceed with the installation
Hope that helps!
3 Likes
@cornfarmer Indeed it worked, thanks! Just as a FYI for anyone else reading this, if your S9 is encrypted and has TWRP loaded, when TWRP loads it will ask for a password- just hit “cancel” and the update will proceed.
4 Likes
Confirmation on my part that the Samsung A3 update to the e-0.19 version went well using a TWRP recovery to flash the new zip file. No problems apart from the Android error message that existed before.
However, the update on my main device - a OnePlus 6 - was much longer than expected. After the initial download there was a progress bar indicating the installation was taking place, but after a second message about “preparing packages” or something to that effect a further progress bar advanced at a snail’s pace and took well over an hour to complete. As there was no reboot to recovery and this is an A/B device I assume that the installation as to the alternative slot and then I was finally able to reboot successfully to the updated version.
However, as I have related separately, this new installation replaces my TWRP recovery with /e/'s own version and unroots the phone. This made a reinstallation of Magisk a major undertaking. See my post.
I installed 0.16-q-20210415110667-dev-star2lte OTA on my Galaxy S9+
First thing I noticed was (like others) root was gone, reinstalled via SIDELOAD Magisk again since DATA is encrypted.
Any way to decrypt DATA? I don’t have a password or a way to get password?
Another observation is that the phone app now has more options like Call Waiting disable which I can disable notification and it doesn’t put call on hold, but I prefer having working call waiting. It also has Call Forwarding menu which was missing. What it doesn’t do is follow the theme (DARK) so it’s white and very obnoxious when everything else is black/dark on my phone.
Hi @petefoth I have seen this issue being raised in a few devices after a OTA release. Any idea why this happens…were you able to check on the z3c …are we missing some files in our build system.
CONFIRMING this same deal on my S9+ with TWRP, I hit cancel re the password and it proceeded perfectly 
I was on A10/eOS0.13… now on A10/eOS0.16 All the apps seem smooth and some nice visual improvements, but as stated by others, the phone and contacts apps are now white on my DARK theme. Over all still a great OS Thanks to the eOS team!!!
Regards
IT VAULT
I’ve had a quick look in the log file, and the install seems to fail with the exception: java.io.IOException: Setup BCB failed. A quick Google internet search reveals the following post on reddit, which seems to indicate this is something to do with file encryption.
https://www.reddit.com/r/LineageOS/comments/7i16cg/ota_update_with_full_disk_encryption/
My phone is protected with a screen pattern. This may be the problem
(I have updated the issue with this information https://gitlab.e.foundation/e/backlog/-/issues/3014#note_91503)
I have created an MR in the local manifests project which may fix the problem BUT I don’t understand why the build stared to fail when previous builds have succeeded without the need for a manifest. I have spent a long time digging into LineageOS and nothing seems to have changed with either LOS or the code in the z3c device and kernel trees.
My guess is that something has changed in the /e/ gitlab repos and/or the /e/ build infrastructure which has caused some of the files needed on the build to no longer be visible. I know for example that the some repos in the e / devices group have been made private and this is a possible cause. @rhunault may have more information, but I am unable to investigate since I don’t have access to the /e/ build infrastructure or some of the repos which were previously public and are now hidden. This really needs to be investigated by someone from the development team who do have the necessary access. This is a device officially supported by LOS, and until recently, /e/ would build for such devices - locally using Docker, and via the /e/ CI/CD - with no problems. LOS hasn’t changed, so the problem must be with /e/
I will continue to investigate when I have time, by trying to build locally, but investigating takes a lot of time, especially because the recent changes in repo visibility have broken my local and Docker builds: builds which used to work with no problem are now failing during the repo sync operation.
But, even if I can fix my local build, perhaps with more manifests linking to more repos, that doesn’t help explain why or how /e/ have managed to break the build. Over to you guys I am afraid 
Great news to see /e/ will be ported on Teracube device.
1 Like
I have created issue #3019 to track this problem
[Later] There is a v0.16 release available at https://images.ecloud.global/dev/z3c/ so maybe the failure was a one-off. OTA install over the v0.15 z3c build works with no obvious problems
Thanks Pete that would be helpful
@mike_from_ireland Do you have any form of encryption or screen lock enabled on your phone? Screen pattern or PIN?
@petefoth I use a pin for the screen lock. I have not knowingly encrypted the phone, so my encryption settings are whatever /e/ does as default.
Thanks
I really must try and find out what that is 