Pro1/SailfishOS stucks at the security code input screen.

[Astaoth 3]

Hi fellow prawn farmers,

 

I've a Pro1 which runs under SailfishOS. As I haven't made upgrades for a very long time, I was still with the 4.0 version, I decided to upgrade it this week. I've made backups of all my data and a partition image dump on the one containing the rootfs and the homefs if case of.

 

I've made the upgrades following the Cassandra guides here, up to the 4.4 version. Upgrading to the v4.5 was removing some packages I wanted to keep. Then I made the post-install stuff described at the end, but also the screen firmware flash (I've changed it and it was a pain with the SFOS gestures). Everything was functionnal, I was able to reboot my phone and use it as expected. After the screen flash, I removed the screen firmware directory from the /usr/bin/droid/droid-load-firmware.sh script. But at the same time, I may have messed with the line defining the firmware directories in this script. I think I fixed it in the right way, however after a reboot, I'm stucked on the luks decyphering screen : after typing my unlock code, the phone stays busy indefinitely.

For fixing this, I've attempted to put my Pro1 into the recovery mode. However when I attempt to boot into it, the phone reboot into the default boot option, which is the unworking SFOS. I've attempted multiple ways to reach the recovery, with no success.

 

This leads me to multiple questions : 

• How could I reach the internal partitions, or at least the rootfs ?
• It seems that I don't have any recovery, is that possible ?
• Can anyone past the content of their /usr/bin/droid/droid-load-firmware.sh script (Pro1 only, not from a Pro1X) ?
• Does anyone has a suggestion for solving this ?

 

EDIT : now that I get better the boot process and how is installed SFOS, I've edited the topic title for being more accurate.

Edited September 9 by Astaoth

[brunoais 334]

Can you boot your phone into EDL mode? There are some guides here in these forums on how to do that.

[Astaoth 3]

I'm on linux. I can make a full reset factory with QDL, but I would instead fix the boot issue I have.

 

I've been able to reach the internal data with the droidian recovery installed on the slot B (I hope this doesn't mess more with the SFOS boot process), but there isn't really any log about the SFOS boot process, I can't get why my phone is stuck during at the initial security code input screen. What could prevent the OS to boot ?

Edited September 9 by Astaoth