shift6mq bricked / stuck in boot fastboot mode screen.

Send in your smartphone. I think EDL is the only and correct way here after all you have tried. However, the problem here is that I am not (yet) aware of any published compatible firmware package. However, according to other forum participants, a new flash should not be that expensive. I think I remember €26, correct me if I'm wrong...

Greetz
 
  • Like
Reaktionen: NoG....eFan
Could you please fastboot --set-active=a and try if it boots now?
Done. Still brings me back to this 'fastboot mode boot' screen.

Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
 
The weird thing about this is also, that your fastboot version claims it is: version-bootloader:5.0.20221224, whereas after flashing ShiftOS 7 it should be 20250528.

So it seems that flashing does not really flash anything at all.

Without EDL/QFIL this seems to be a bit hard to work on but maybe what you could try is booting the recovery image directly and see if that boots up, via fastboot boot recovery.img and then install the system via OTA.

If that does not work, you could also boot into fastbootd from within that recovery (it will not reboot but start fastbootd, which is included in the recovery) and flash there again.

Otherwise if all fails, maybe trying to live boot into pmOS and manually flash partitions there via dd.
 
you could try is booting the recovery image directly and see if that boots up, via fastboot boot recovery.img and then install the system via OTA.

This also fails.
Code:
$ fastboot boot recovery.img
Sending 'boot.img' (98304 KB)                      OKAY [  2.379s]
Booting                                            FAILED (remote: 'Failed to load/authenticate boot image: Device Error')
fastboot: error: Command failed

I really appreciate your help. Thanks!
Maybe it's time to think about plan B and just send in my shift6mq to fix it...