They simply don’t admit that it is a bug, as you can read here.
Because they either don’t care, don’t know how to fix it or are unwilling to admit the fault exists at all since that would open them up to lawsuits.
This is a launch bug, so it’s been around for almost 2 years. If they wanted to fix this, they would have done so by now.
Hello @all !
It looks like i have to dig out my retired FP2 since my FP4 is biten by this. I do not remember locking my boot loader, but i guess it was still locked. It fails to boot to recovery or anything useful and no changes can be made to it. Any attempts to flash anything result in
FAILED (remote: 'Flashing Unlock is not allowed
Installed ROM is iodé 4.x which ran and updated fine for several months now
The point of failure was yesterday’s attempt to install Magisk via a modified ramdisk.
The most important lines from fastboot getvar all seem to be
slot-unbootable:b:yes
slot-unbootable:a:yes
As far as i read here, i’ll have to send it in. I only write this reply in order to be counted or noted somewhere.
Cheers,
tim
When your FP4 is rooted, your bootloader cant be locked…
It failed to be rooted, resulting in this. I guess it failed because of the lock.
I think you’re unfortunately right. AFAIK in case the bootloader is locked then the boot integrity is checked - and it probably failed as you’d tempered with that.
I just wonder how you could change the boot image while the bootloader was locked…
I have indeed been tampering with lots of things, but the last bigger operations have been a few months back. I might have disabled OEM unlocking after one of them. It booted fine ever since, until yesterday.
Anyone tried to flash the frp partition with a locked bootloader ?
fastboot flash frp frp_for_factory.img
Does it work and reset the FRP ?
You can’t use fastboot flash
while the bootloader is locked, you’d need something like edl and there’s still no edl-loader available for the FP4 (there is for the FP3).
I’m not aware of someone having released firehose files anywhere else, so there’s still no way to recover from that state (unless you have access to Qualcomm’s tooling probably).
On the FP3 the devinfo
partition could be flashed with
fastboot flash devinfo devinfo-unlocked.gpx
also with a locked bootloader. That’s the reason I’m asking.
Just to have it linked here
I don’t know, if this edl works for the FP4, but it has one remarkable option:
edl modules oemunlock enable
If this command succeed, you can unlock
an unlock_critical
with fastboot
and proceed with the flash_FP4_factory.sh
script.
It would if we had a matching edl-loader (firehose files whatever you want to call it) for the FP4, we don’t.
As I’ve mentioned before in this thread, that mode is also probably called sahara for a reason, without anyone leaking the necessary files you are just stranded in a desert with not a lot you can do
The Right to repair won’t apply in this case ?
- Access to spare parts, tools and repair information for consumers
From my point of view this information should be available to public domain.
Yes, it IMHO applies.
The linked article says
Manufacturer has to repair a product for a reasonable price and within a reasonable timeframe after the legal guarantee period
I think you can have your device repaired under these conditions when your phone has reached the mentioned state.
While I value your point of view there are also good reasons to not make this available to the public.
The major reason I see is that e.g. a stolen device can not be unlocked (and sold/be reused) without contacting FP (so they can check against a list of stolen devices).
Where to check warranty- and/or legal status on the fairphone website ? I have a defective FP4 (known display issue) and the only thing I know for sure, that the phone boots (it’s reachable via USB). I cannot see, if it have a screen lock etc.
The seller claimed he also purchased it as defective. This seems to be believable, because you cannot reset a defective phone.
Turn the phone off, plug one side of a USB cable into a PC, hold Vol. Down while plugging the other end into the phone.
Run fastboot oem device-info
on the PC, that should tell you everything you need to know (at least as far as locked bootloader etc. goes).
If it’s locked and the previous owner didn’t enable oem unlocking (unlikely) or added a Google account, your journey ends there.
That’s well known, but have nothing to do warranty- and/or legal status of the phone.
$ fastboot getvar serialno
serialno: 49cdXXXX
Finished. Total time: 0.003s
$ fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.003s
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.001s]
If the phone is locked with a PIN - what I currently don’t know, beacuse of the defective display -I’m literaly in the desert. If this is the case all other parts can be reused as spare parts.
Shure, but that’s information only FP can provide contactsupport, this is a thread about getting out of the bootloader, hence my suggestion.
If the previous owner didn’t add a Google account there’s a way to trigger a factory reset from recovery via command line IIRC.
If they did or the system is otherwise unbootable you’re out of luck.
Not only that, since the ROMs are signed with test keys the moment that loader becomes available someone could theoratically just include malicious code in one of the partitions, sign it themselves, and switch those out on the phone (still needs physical access though).
Significant parts of the security model (at least for FPOS) rely on EDL to never become accessible, they’ll never release this officially (and there’s probably a bunch of Qualcomm NDAs involved that wouldn’t make it possible anyway).
If its just a matter of a broken display
All this has nothing really to do with warranty or at least why discussing here, get in contact with Fairphone to check your repair options with or without warranty