@FishHead: In your case, I think it’s dead. If you don’t have the ‘Try again’ option, and the system boots directly into the fastboot menu, it’s not a good thing. I think the ‘Factory reset’ option is the only solution for you (of course if this option is available), otherwise, return the device to the manufacturer. But hey, let’s wait for the E/OS team’s response. In my case, I had more luck, because even if I get the recovery screen, I can use my device. I prefer to wait for an update, because if I try to make changes, the device could freeze permanently.
Unlocking the lockscreen is where the phone decides to give up. At the moment I’m using my hotspot (enabled before unlocking) and no issues whatsoever. Same goes for any other functionalities that doesn’t require unlocking.
Yeah, I think your absolutely right. I dont even have the factory reset option left haha. So sending it in will probably be the only choice.
I’m glad your in luck though! Atleast a couple of you will be saved. Yeah, definitely. Its nice to see the team working on this already, so hopefully this will be fixed for you soon.
Vendor Name: Fairphone
Device name: Fairphone 5 official Android 13
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: 2.9 e/os
Is the device: Not rooted
Till now everythings works fine as before.
I just hope, that the next security patch will be current and not 2 months old.
I don’t want to block my device with bad manipulations. I have already used the tools (adb, fastboot) to replace the Fairphone ROM with the E/OS one, but that was a long time ago. Can I use adb without unlocking the OEM and unlocking the bootloader? If so, I can try to recover the log file.
Thanks to those who have been sharing details on the issue. The development team has been assigned to work on this and are in the process of finding a resolution to the problem. Will share updates when there is any progress on this.
Some users mentioned they were able to reboot to 2.9 on the other slot. Wanted to check how this was achieved. Pl share details if possible.
Thanks for the feedback. I hope you find out where the problem is coming from, and that a solution will be found. I think my system is installed on slot A, but I don’t understand why it boots on slot B (that’s what I see on the recovery screen) and I don’t know why, in my case, when I choose the ‘Try again’ option, it boots normally, and I am on version 3.0, not 2.9. I’m happy that my device is not full blocked like some others.
Thanks.
Regards.
Note: Can I have access to /data/system/ with usb transfer option and my cable ? Do I really need adb software to access to /data/system ?
Vendor Name: OnePlus
Device name: 7T Pro - Mod. HD1911
Device CodeName: hotdog
Version of CustomROM which existed previously: /e/OS 2.9-t
The device is: Not rooted
Upgraded to /e/OS 3.0-t-20250601497058-community-hotdog
Would it be possible to share a bug report generate on your phone. You can share it with me in a DM …pl check there is no personal information in the log before sending
Version of /e/OS or Stock which existed previously 2.9-t
Is the device Rooted / Not rooted
Almost everything works well
Thanks to the community for a job well done.
There’s still a problem that’s been there since the switch to Android T: the native camera app can’t take videos: the image freezes and the recording generates an error. It’s a shame to have to install another app for this.
Other problem with AppLounge: install or update application always failed with a retry button (sameafter clearing cache and data). I’m using Aurora & Droid-ify to bypass this.
I would like to share further details… but either I mis-tapped or it was triggered automatically… and now my phone has factory-reset itself.
The positive: it seems to work now. The negative: I think I have lost some of my most recent contacts that weren’t backed up yet.
Suggestion: maybe the update process should remind the user to back up their data before starting? I work only on my PC, so I don’t know about the good practices regarding smartphone data backups…
I check if maybe I did something wrong, so i wiped out everything and fresh installation of v3.0 did nothing to me, so it’s problem with the ROM, everybody who calls me, hears themselves. Similar to echo, but they hear themselves with delay. They can obviously hear me as well.
For me the reboot on slot B is ok, I have a phone like before update. No data losts, every thing ok.
Just I didn’t reboot my phone since I boot on this slot. I don’t really know what there are on the slot A, the os is probably installed, but problem on boot. My phone is unlocked.
As I previously mentioned here yesterday, everything works pretty well on my FP4 on 3.0 (and also for my wife).
So I guess that the challenge for the developers will now be to reproduce the errors. Maybe all those users who can not boot anymore have some common points (special config, specific apps, another active launcher, etc…). So, in order to help, here’s my working config:
Are all these FP4 devices bootloader locked : My bootloader is locked
Are any of the users on premium accounts. That is with additional storage on the Murena cloud. I 'm using the free Murena services.
Were Parental Controls activated on the device. Not activated
Do you have multiple users on the system : No, only one user.
What is the default language on the phone : French
Is Hide my IP activated : No, not activated
What’s the launcher in use: Bliss
Type of Sim card services: Standard Sim Card (No e-Sim)
Does Android Auto has been added: No
Does the device contain a SD card: Yes (Micro-SD 256 GB)
I dont even have the factory reset option left haha. So sending it in will probably be the only choice.
