thats the reason for the s in Sailfish_OS-Jolla-5.0.0.43-s19mps-1.0.0.30.zip
The Reeder S19 Max Pro look a bit different like the S19 Max Pro S, so the Hardware is also different i guess and that could be the reason the S-Software don´t work on the non-s-Modell.
As a last resort, I will send the phone to the technical service, but I am still researching to see if I can do something myself. I am still open to all suggestions
Yep, I live in İstanbul / Türkiye. It can be easily purchased almost everywhere here.
Today I will try to create a PAC from the archive file I downloaded yesterday which has many IMG files in it. If I succeed, I’ll try get the device working with Android again and try again with the commands mentioned by affe_null which I missed earlier.
If I succeed, great. If not, I will send the device to technical service. I also emailed Reeder to ask if they can provide me a PAC file for this device, but I don’t have much hope that they will.
The spd_dump command line tool (see the flashing thread I linked above) doesn’t need a PAC file. It can replace Unisoc’s flash tool and lets you flash images to partitions directly. In fact, you will not be able to make a working PAC file without a signed FDL1 image, which is not provided in the gsmturkey archive. The spd_dump tool lets you bypass this.
To restore the partitions you’ve changed, you can just use the following command (assuming you have followed the setup instructions from the flashing thread and the gsmturkey archive is unpacked to images/):
./spd_dump \
exec_addr 0x65015f08 \
fdl fdl1-dl.bin 0x65000800 \
fdl images/uboot_a.bin 0x9efffe00 exec \
w boot_a images/boot_a.bin \
w boot_b images/boot_b.bin \
# ... same for other partitions
To get SailfishOS working, you will probably only need this (instead of the command above) with lk.bin taken from the SailfishOS archive:
Of course it might be that Jolla has modified something else, in which case I can share dumps of some additional partitions from my C2. Since the flashing interface is provided by the boot ROM, it should always be possible to restore the phone even if the bootloader is not working.
It took me a while to figure out how to do it. I thought I had to enter fastboot mode to do the operations mentioned here, but that’s not the case.
I had to turn on the phone by pressing the volume up button and the power button. This puts the phone in a special mode where it can communicate with the program mentioned here. I’m so happy to finally make some progress after breaking my phone
However, the above parameters either don’t work for me or I didn’t manage to enter them correctly.
spd_dump.exe
branch:main, sha1:86fa3e31bc6ab9bd92eeaf48aa63bbfc7e065485
Successfully connected to port: 4
CHECK_BAUD bootrom
BSL_REP_VER: "SPRD3\0"
CMD_CONNECT bootrom
BROM >exec_addr 0x65015f08
custom_exec_no_verify_65015f08.bin does not exist
current exec_addr is 0x0
BROM >fdl fdl1-dl.bin 0x65000800
File does not exist.
BROM >fdl lk.bin 0x9efffe00 exec
unexpected response (0x008a)
timeout reached
Press any key to continue . . .
I’m open to your suggestions for what to do next, because I’m going to go very slowly on my own because I’ve been using iOS for about two years and I’m quite rusty for this kind of work.
I get timeout or sending error for lk.bin part:
spd_dump.exe exec w uboot_a lk.bin w uboot_b lk.bin
branch:main, sha1:86fa3e31bc6ab9bd92eeaf48aa63bbfc7e065485
Successfully connected to port: 5
CHECK_BAUD bootrom
BSL_REP_VER: "SPRD3\0"
CMD_CONNECT bootrom
timeout reached
Press any key to continue . . .
spd_dump.exe exec w uboot_a lk.bin w uboot_b lk.bin
branch:main, sha1:86fa3e31bc6ab9bd92eeaf48aa63bbfc7e065485
Successfully connected to port: 5
usb_send failed (0 / 1)
And an unexpected response when I adjusted timeout setting:
You are invoking the command correctly, but it seems that you have not placed the files you are referring to in the correct folder. Have you unpacked ums9230_universal_unlock.zip?
After a command fails, you usually need to restart the flashing mode by holding the volume up and power keys.
I usually read the documents carefully from beginning to end, but I think I missed quite a few things because of my excitement. I didn’t download the archive you mentioned
I had very little time before going to work and I gave it a try right away. I can say that it was a new progress for me
signature verification of "uboot_a" failed or timeout reached
I hope we can overcome this situation too
By the way, I am not sure if the above is an error message or just an information message. I mean, I don’t know if I was able to write to uboot_a or not because signature verification failed. As a result, the phone still doesn’t turn on in any way and I don’t have a working Sailfish.
Thank you so much to you and the whole Sailfish community.