In the current state of the smartphone, can I flash the image according to the Google instructions or do I have to do or consider anything else with regard to the actions already successfully performed: “Flashing additional partitions” and “Installing a custom recovery using fastboot” from the /e/os instructions?
Best to treat it as two jobs. Revert the phone to Google Android 14, preferably test that the phone is fully functioning. Then you will be in a good position to “fresh start” the /e/OS install.
After I entered the commands “fastboot set_active other” and “ fastboot reboot bootloade” twice and then rebooted, only a white Google still image appeared.
Is the warning significant? And if so, how do I get more space on bootloader_b or should I switch to bootloader_a?
I would find it helpful if there was additional information about this tip in the Install-/e/OS-instructions or if a link was provided showing exactly how to install the latest OS version of Android 14 on the smartphone. Is it also possible via the Android interface, for example, or do you always have to flash the smartphone with the Google image (latest stock OS version 14) via adb?
Downgrading is often quite tricky. The general rule in Android is never go back. The link I gave is a developer page and while it includes its own instructions I do understand that they may seem quite advanced.
I do recommend that you create a New Topic under support(New Topic link top right of that hashtag) then maybe someone who knows the device well can help you restore the stock ROM.
It is unfortunate that the message is only given the status Tip.
Addition:
After 3 days i noticed now an unproper behavior of the App Switch Button.
Sometimes i have to press it several times to see the overview and sometimes
it is presented at once
Vendor Name : Fairphone
Device name : Fairphone 4
Device CodeName : FP4
Version of /e/OS or Stock which existed previously : 2.6.3-u-official
Is the device Rooted / Not rooted : not rooted
The update went smoothly, but the battery consumption is extremely high with two FP4s.
In flight mode about 6% within 10 hours (that was already much worse), but in normal mode the mobile phones only lasts about 50% compared to the previous version.
Vendor Name: Xiaomi
Device name: POCO X3 NFC
Device CodeName: Surya
Version of /e/OS or Stock which existed previously: e/OS 2.6.3
Is the device Rooted / Not rooted: Not rooted
For the most part everything is working well. Two little problems which have been present at least since last version (which was my first) are that the QR scanner isn’t working and dict.cc app crashes as soon as I enter a word.
Thanks for the tip, I’ve been watching this ticket for seven months. Maybe it’s a bit naive of me to think that because of the cooperation with Fairphone and the direct sale of the devices by Murena, test devices should be available. But I’m just a user and not a programmer.
My best guess would be that AppLounge is in a struggle similar to aurora store vs. the g…that does not like the anonymous approach and keeps “sabotaging” it… (?)
Yep ran into this as well on my Samsung S10, if you reboot you’ll end up in the previous version, in my case 2.6.3 U. So skipping 2.7, too lazy to do the manual upgrade which has been reported to work.
