Sailfish OS (officially) on Sony Xperia devices - Page 189 - maemo.org

clovis86 | # 1881 | 2017-10-18, 12:26 | Report

skills ?

The Following User Says Thank You to clovis86 For This Useful Post:
juiceme

KylliOrvokki | # 1882 | 2017-10-18, 12:32 | Report

Originally Posted by rfa View Post

Now, after finally getting windows to run an unsigned driver I get the error message (from the command line, to enter the unlock code):

FAILED (remote: Command did not succeed)
Finished. total time: 0.052s

What am I still missing?

Did you check that your phone is possible to unlock?
https://www.youtube.com/watch?v=jWPY...youtu.be&t=34s

I had this same error message and I solved this buy enabling "allow OEM unlock"(= something like that - I can't remember exact name) from settings. After this I was able to unlock boot loader.

Of course you need your own unique unlock code but I guess that has been used.

The Following 6 Users Say Thank You to KylliOrvokki For This Useful Post:
Feathers McGraw, jakibaki, Jordi, juiceme, maximilian1st, mosen

DrYak | # 1883 | 2017-10-18, 12:39 | Report

Originally Posted by rfa View Post

Now, after finally getting windows to run an unsigned driver I get the error message (from the command line, to enter the unlock code):

FAILED (remote: Command did not succeed)
Finished. total time: 0.052s

What am I still missing?

Just to make a check list :

The Jolla phone is updated to the latest 34.3.A.0.228 or .238 firmware (Important to do first because after unlocking the boot loader, OTA won't work as easily)
Developer menu is activated
USB debugging is on
3rd party application are authorizsed
OEM unlocking is authorized
You have registered your IMEI on Sony's website
You've obtained a long hexadecimal code in return from Sony
Your phone was first shutdown
Afterwards (wait 10 seconds at least), your phone was turned on in Fastboot mode (hold "volume up" while plugging the USB cable)
the Xperia is in Fastboot mode (no message on the screen, the LED is blue instead of green

At that moment you should run the fastboot command in your command shell (in cmd.exe) :
fastboot.exe oem unlock 0x<hexadecimal code>

Note that depending on how windows works, this might require admin rights (I have no idea, I use Linux. Maybe you'll get a UAC security prompt ? Or you need to "Run as..." cmd.exe to start the shell in admin mode ?)

The Following 12 Users Say Thank You to DrYak For This Useful Post:
Drekkie, Fellfrosch, Jordi, juiceme, lal, lancewex, llv95dno, maximilian1st, mosen, mrsellout, rogger888, Sthocs

DrYak | # 1884 | 2017-10-18, 12:51 | Report

Originally Posted by jenix View Post

That info is actually relevant. It clearly states, that Jolla / SFOS only supports SDHC cards up to 32 GB, but almaviva tries to use a 128 GB (probably SDXC) card. I always thought that the official limitation to 32 GB was because Jolla wants to mitigate to Microsoft for the exFAT licences (which you are obliged to do for cards >32 GB), but maybe there is more to it?

there is no physical different between SDXC and SDHC card, they absolutely speak the same protocol (MMC).
the only difference is a logical/marketing one :
- SDHC are <= 32 GB and are sold pre-formatted with FAT32.
- SDXC are > 32 GB and are sold pre-formatted with exFAT (which is patented and cannot be provided by Jolla).

(that's different from plain SD cards which use a slightly older version of the protocol, that can only address card up to 1GB, or up to 4GB with a few hacks. the difference betwen SD and SDHC/SDXC is a bit similar to the introduction of LBA and LBA48 in harddisks).

this current situation is an entirely different problem : the card and the chipset are negociating a clock frequency to talk to each other (MMC uses a separate clock trace) - at least that's what it seems given the differences in dmesg between my card and the problematic card.

It currently seems that if the kernel is 3.10.84, this step fails (bug seems to be known in Ubuntu communities).
if the kernel is more recently (probably like the one packaged in Android 7.1.1 Nougat by Sony), this bug seems patched.
At least, that's what looks the most likely given the problems (card always works in stock android system and fails after Sailfish X flashing).

It just randomly happened the this card happens to be a 128GB one and also happens to have the frequency error.

But other people on TJC have successfully used a different models (the 256 Evo+ from Samsung).

The Following 4 Users Say Thank You to DrYak For This Useful Post:
alfmar, jenix, juiceme, maximilian1st

Fellfrosch | # 1885 | 2017-10-18, 13:21 | Report

Have you made this step described on Sony's "How to unlock bootloader" site?:

Originally Posted by

"To be able to unlock your Xperia X, prepare it by following these steps:
Go into Settings > About phone and tap seven times on Build number to enable developer options.
From Settings, go into Developer options and enable OEM unlocking."

If not have you read this on Jolla's instruction site:

Originally Posted by

Please make sure you read the whole page of instructions before starting.

Reading instructions is mandatory to be successful!

The Following 2 Users Say Thank You to Fellfrosch For This Useful Post:
juiceme, Merienth

pexi | # 1886 | 2017-10-18, 13:40 | Report

Originally Posted by clovis86 View Post

skills ?

social skills?

The Following 3 Users Say Thank You to pexi For This Useful Post:
juiceme, mosen, rogger888

clovis86 | # 1887 | 2017-10-18, 14:08 | Report

Sorry, too easy xD
But anyway, all they gotta do is to rtfm, nop ?
( especially with windows procedure )

The Following User Says Thank You to clovis86 For This Useful Post:
juiceme

lantern | # 1888 | 2017-10-18, 14:09 | Report

I don't get "Delivered" status message after sending SMS. SIM is in the 2nd slot in F5122.
Do F5121 get this status or it's broken for everybody?

The Following User Says Thank You to lantern For This Useful Post:
juiceme

clovis86 | # 1889 | 2017-10-18, 14:13 | Report

I met this issue ( on F5121, not F5122 ) after each reboot, network settings where lost ( roaming and "delivered" status settings where always disabled )
Got to use the trick for ofono config file to get them persistent between reboot. ( file owner and group radio:radio AFAIR )
Maybe it could help you

https://together.jolla.com/question/...-after-reboot/

Originally Posted by

devel-su
systemctl stop ofono.service
cd /var/lib
mv ofono ofono.backup
mkdir ofono
chown radio:radio ofono
systemctl start ofono.service

OR :

Originally Posted by

chown radio:radio /var/lib/ofono systemctl restart ofono.service

Last edited by clovis86; 2017-10-18 at 14:19. Reason: add 2nd command

The Following User Says Thank You to clovis86 For This Useful Post:
juiceme

jenix | # 1890 | 2017-10-18, 16:22 | Report

Originally Posted by lantern View Post

I don't get "Delivered" status message after sending SMS. SIM is in the 2nd slot in F5122.
Do F5121 get this status or it's broken for everybody?

Have you configured the Messages app to request a delivery report?

The Following 2 Users Say Thank You to jenix For This Useful Post:
juiceme, lantern