Conversation

Escaping from Google, I installed on a ; installed and , and everything was running smoothly (except my bank app crashing at startup). Great ! 🤩

3
1
0

After some tests on running on my SD card, I tried to switch back to using root command `qbootctl -s a`, then `reboot`. It simply shut down actually. Oh wait, not booting when pressing power. Uh oh. Neither fastboot nor recovery booting working. Oh no. After so much hope, I believe I bricked my . Fortunately, still under warranty. Conclusion : when running root commands related to booting, be dragons.

1
0
0

@jovial Does the screen at least light up when you connect the FP5 to charge? If YES, this might be worth a try ➡️ https://forum.fairphone.com/t/how-to-boot-my-fp4/117761/2?u=wearefairphone Other than that, such bricking is certainly outside of warranty (although I would expect Fairphone would not regard your warranty regarding hardware as voided). But their repair contractor Cordon in France might unbrick it for a survivable fee. /u
(Not the company writing here)

2
0
0

@WeAreFairphone Epilogue of my Fair brick 5 : assistance offered to fix the hard brick for 50€, I accepted, I sent it to Cordon electronics and got it back ... and it's bootable again ! 🥳 Unfortunately I had no choice for the system, so I'm overwhelmed again with Google. I would give a try to /e/OS, but won't try the dual boot again. Happy hacking everybody !

1
0
0

@jovial Was that 50€ everything (shipping, labour) included?

1
0
0

@WeAreFairphone Everything was included, I paid after the diagnostic and before repair :
29€ labour + 13.7€ administrative fees + 8.54€ VAT = 51.24€

If I wanted my phone back without repair, it would have cost me 38.04€.

1
0
0

@jovial Thank you, helpful to know when others are running into this problem. /u

1
0
0
@WeAreFairphone @jovial Just FYI, LineageOS in this case was not the cause of the brick. The cause seems to be that qbootctl now bricks devices instead of switching slots: https://github.com/linux-msm/qbootctl/issues/4

Honestly, thank you all for warning about this .. I would be very angry if I had to return my FP5 *again* (mine got EDL bricked, but because of a half-done LineageOS upgrade..).
1
2
1

@WeAreFairphone Hello, thanks for the tip ! Unfortunately, no light at all, not a single life-sign, event when plugging a charger. 😔🔌📴 That's really a fair-brick 5 right now. I opened a ticket to support, we'll see how much that lesson will cost to me ... 💸

1
0
0

@jovial The problem might be related to the much-feared "anti-rollback protection" that Google injected into Android to make Custom ROM life harder and riskier ... 🙄 /u

0
0
0

@jovial
Very interesting news.
Is the banking app ok now?
This is the main barrier for me.

1
0
0

@CharlesShould Not yet. I plan to complain to my bank to ask them to make the app independent from Google. But might be coming from elsewhere, like device integrity. Hard to say, I haven't checked the logs. If missing Google Services is the root cause, could be worth tinkering with microG : https://github.com/microg/GmsCore/wiki

0
0
0

system being in internal memory, I installed in dual boot, using a/b boot partition and putting system inside the sd card (well explained in wiki page of pmOS). It finally works out, being able to send SMS, haptic feedback, playing , updating system and rebooting. Nice ! 🤩📱🐧

0
0
0

@fun @WeAreFairphone Very-well spotted, this issue 4 on qbootctl is very likely to be related to my brick. From now on, I would consider any superuser command affecting low levels of a too risky to attempt on a daily driver. However, there is an interesting tip mentioned in the issue : having a pi nano with fastboot installed and automated, allowing to switch A/B starting slot safely on the go. I might try this at some point.

1
0
0
@jovial @WeAreFairphone yes, switching manually by entering fastboot does still work just fine. Just don't use qbootctl for that.
0
0
0