That’s normal behaviour for phones with unlocked bootloader from what I learned. If you search the forum you find discussions and explanations…for quite some phone models it is simply not possible to relock the bootloader on a custom-rom.
It says " Bootloader relocking support - Data unavailable" for pixel 5
You might dig into that in the device specific section of the forum.
1 Like
hi, GS-users,
On a GS290, e/os-2.2-s, the update verification cannot complete ?
Even if the internet connexion is good.
Is there a server or an e/os-2.3 question for the GS290 ?
thanks for your attention, Brieucs.
hi, verification of upgrade to 2.3 impossible on :
GS290 Android 12
e/os 2.2-s-20240715 417774-stable-GS290
build : e_GS290-user-12 SQ3A.220705.004
eng.root.20240715.221536
if asked, it answers : “verify your internet connexion, and try again”,
but the connexion is good.
thanks for your attention; brieucs.
download works from server (disclaimer: I tried only with PC as I have no GS290 and I only started the download but then aborted it)
https://images.ecloud.global/stable/GS290/
https://images.ecloud.global/dev/GS290/
Hi,
Thanks for replying.
Previously on my GS290 on reboot I hadn’t the screen that I receive on Pixel 5, but that’s not a problem.
1 Like
Maybe your GS290 had a locker bootloader?
No any bootloader locker
Vendor Name: Fairphone
Device name : fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: 2.2 T
Is the device Rooted/not rooted: not rooted
Update went well except one thing: Since the update App Lounge is no longer able to connect. It always says anonymous account is not available. It says trying to refresh but this does not work and clearing cache and app data did work work as well.
Was mentioned by others as well. So I hope a ticket is open at /e/ side
many thanks.
I can access and download the stable image you suggest. As I don’t feel easy with the recovery-mode, I will take some precautions (savings), Where the Image has to be placed for recovery to use it (can I access the cache-partition ? I prefer to avoid ADB or extra-sd-card if possible),
brieucs.
By giving the links I only meant to show that the server has the files available and should work for OTA-update as well.
I don’t know where to put the files on the phone in avoidance of adb and sd-card, maybe others know.
You may just try the download-folder (?)
If OTA does not work I’d go with an sd-card if one is available, that should be a very simple process.
But I’d be interested anyways why OTA does not work and fix it if possible - so I don’t need the workaround next time…
I presume you cleared cache of the updater-app and rebooted your phone minimum once ?
You should use the lineageos-update folder located in the system section. But before that, clean the updater cache and data as @obacht said. To do so go in Apps > … > show system app > updater
1 Like
Vendor Name: Xiaomi
Device name: Mi 9 Lite
Device CodeName: pyxis
Version of /e/OS or Stock which existed previously: Stock latest
Is the device Rooted / Not rooted: not rooted
Everything OK. SaftyNet works so I have switched from Redmi Note9 Pro to Mi 9 Lite for this reason.
Yesterday account manager started to report credential errors and drain battery. It worked few days fine before so it is not due to upgrade but something else.
Have tried removing it and then adding it back ?
Gigaset
GS290
2.3-s-20240816426374-stable-GS290
Not rooted
OTA installation went fine. Phone is working fine since installed 2.3-s more than a week ago - and maybe feels a tad faster. Thank you for the team!
Vendor Name : Murena
Device name : Fairphone 5
Device Code Name : FP5
Version of /e/OS : 2.3-t - stable
Previous version of /e/OS: 2.1 => 2.2 - stable
Is the device Rooted / Not rooted : not rooted
After OTA Problems upgrading from 2.1 to 2.2 to 2.3 FP5
I’m finally at 2.3 no problems at 1st sight 
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 2.2-t-20240717417775-dev-FP3
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 2.3-t-20240820427106-dev-FP3.
The following things work for me:
- Call / be called
- Send SMS / receive SMS
- Notification LED
- Alarm
- Internet via Wi-Fi
- Internet via mobile network
- Wi-Fi hotspot
- Location
- Settings - System - microG - Self-Check: all ok, including location permissions
- Settings - System - microG - Location - Wi-Fi location - Request from Mozilla: enabled
- Settings - System - microG - Location - Wi-Fi location - Request from Hotspot: enabled
- Settings - System - microG - Location - Wi-Fi location - Remember from GPS: enabled
- Settings - System - microG - Location - Mobile network location - Request from Mozilla: enabled
- Settings - System - microG - Location - Mobile network location - Remember from GPS: enabled
- Settings - System - microG - Location - Location server - Use /e/OS’s location system: enabled
- Settings - Advanced Privacy - Geolocation: Exposed
- Settings - Advanced Privacy - Geolocation - Use my real location
- Settings - Location - Use assisted GPS: enabled
- Settings - Location - Location Services - Wi-Fi scanning: enabled
- Settings - Location - Location Services - Bluetooth scanning: disabled
- Settings - Location - App location permissions - “Allowed only while in use”: Apps are listed
- Compass
- Screenshot
- Main camera (original FP3 Camera module, not +) photo + video
- Selfie camera (original FP3 Top module, not +) photo + video
- USB connection to PC / MTP
- MyPhoneExplorer 2.1
- Bluetooth (music playback, data connection)
3 Likes
Fairphone 3+
FP3
Update from v2.2-t-stable to v2.3-t-stable
Not rooted
Update completed within 40 minutes with no issues seen.
Initial testing of basic functions & apps shows these appearing to be working fine: wi-fi, mobile data, bluetooth, GPS, phone, message, mail, browser, camera, app lounge and various other apps.
All looks good, thanks for all the good work.
1 Like
Fairphone
Fairphone 5
FP5
Update from v2.2-t-stable to v2.3-t-stable
Not rooted
The first time I tried to update it seemd to work but when I did the restart to finish it went into a loop. With volume DOWN and POWER I was able to get into fastboot mode and was able to turn it of.
After some minutes I turned it on again and it went back to 2.2
Next time I had the same issue but when I turned it after some minutes it showed that I’m on 2.3. But now I have the issue, that the phone crashes about once a day and goes into bootloop. I’m always able to turn it of via fastboot mode and wait some minutes, but its realy annoying
Any news? Because is increasing the number of app with no notifications even if notifications are active and there is no battery limitation. I want to specify that the audio problem for hands-free calls is only with calls with landline telephone
- Samsung
- Galaxy S9
- SM-G960F
- All STABLE versions for 2 years
- Not rooted
hello, the update went well. But since v2 in fact, the screen option “increase sensitivity” seems not working. I have a protective glass which has no problem untill the v2. Very boring…