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

suicidal_orange | # 1871 | 2017-10-17, 23:27 | Report

Originally Posted by DrYak View Post

Originally Posted by suicidal_orange

but with the SD connected (no tape) the second sim gets disabled. Thus the problem seems to be in software...

Or a PCB traces problem ?

Hence this question

Originally Posted by suicidal_orange

anyone willing take one apart and look for joined traces?

It's probably a multi layer PCB so nothing to see, but you never know!

Had a look at the dmesg logs, lots of error looking things but can't isolate anything that looks like a working second sim. I give up for today.

The Following 2 Users Say Thank You to suicidal_orange For This Useful Post:
juiceme, maximilian1st

deprecated | # 1872 | 2017-10-18, 02:07 | Report

Originally Posted by suicidal_orange View Post

Hence this question

It's probably a multi layer PCB so nothing to see, but you never know!

Had a look at the dmesg logs, lots of error looking things but can't isolate anything that looks like a working second sim. I give up for today.

I took at a look at the SIM carriage for F5122, and it appears there are only 17 pins total on the package. 9 on one side, 8 on another.

SIMs are 6 pins, SD cards are 8, so that's a total of 20 pins. Looks to me like one of the SIM sockets physically share pins with the SD socket.

Of course, I could be wrong. This is just based on a cursory inspection of the repair part.

The Following 5 Users Say Thank You to deprecated For This Useful Post:
alfmar, hhbbap, imaginaryenemy, juiceme, suicidal_orange

rfa | # 1873 | 2017-10-18, 03:15 | Report

Originally Posted by rogger888 View Post

I am at a complete loss, could someone point me in the right direction please. I have enabled oem, usb debugging, my bootloader can be unlocked and I am running 34.3.A.0.238, yet when I use EMMA it says phone locked. Where have I gone wrong please. Thank you

I'm having this exact problem.

I think it;s because I'm using Windows 8(.1) & it has issues with unsigned drivers - the Fastboot "extra" driver

Any suggestion or help would be much appreciated

Edit: New post above with more information / new questions

Originally Posted by DrYak View Post

Exactly. You have reached the point where the bootloader can be unlocked.
Now you need to actually unlock.
(Warning: actually unlocking it will fry the DRM keys. Have you backed these up before ? *)

On the website you need to register your e-mail (or a single use e-mail)
Then give the IMEI of your Xperia X
then it will give you the code to unlock the phone.

It will look something like 'fastboot oem unlock 0x<key>' where the key is a long hexadecimal string specific to your phone.

Only the 'fastboot' executable.
If you've reached that point, you should normally already have it installed.
(There is a Windows copy packed inside Jolla's Sailfish X installer).

-----

* - the most user-friendly and cross-platform is to use http://www.flashtool.net/ :

- downgrade the firmware to Android 6.0.1 Mashmallow (34.0.A... firmwares)
- activate again developers mode, debug mode, untrusted sources
- menu File -> turn on "Advanced mode".
- menu Advanced -> TrimArea -> Raw -> Backup (this gives a .fta file)
- this gives you a "registeredDevices_<serialnumber>_rawta_<date>.fta" file, keep it preciously
- upgrade the firmware to Android 7.1.1 Nougat (34.3.A.0.228 or 238).
- now you can safely unlock your phone ("fastboot oem unlock 0x<key>")

I have no intention of downgrading to Marshmallow

I've bought an Xperia X purely for SailfishOS & have no intention of selling it (I've still got my N900 & two N9's)

I can't find a fastboot.exe anywhere...

What have I missed?

Last edited by rfa; 2017-10-18 at 03:25. Reason: New info / questions

The Following 2 Users Say Thank You to rfa For This Useful Post:
juiceme, rogger888

Fellfrosch | # 1874 | 2017-10-18, 05:08 | Report

you have to go to the folder where you have unzipped the sailfish image package. There is the fastboot.exe and the flashing script.

For unlocking the bootloader you have to go to https://developer.sonymobile.com/unl...urboot-loader/
there you will get a code which is necessary to unlock your phone. Just follow the instructions step by step...

Last edited by Fellfrosch; 2017-10-18 at 05:13.

The Following 5 Users Say Thank You to Fellfrosch For This Useful Post:
hhbbap, jakibaki, juiceme, rfa, rogger888

anig | # 1875 | 2017-10-18, 05:14 | Report

There is a fastboot.exe in the sailfish X zip that you download from Jolla. I used that. Read it somewhere on TJC but can't find the link now.

The Following 2 Users Say Thank You to anig For This Useful Post:
juiceme, rogger888

rfa | # 1876 | 2017-10-18, 06:35 | Report

The step I haven't undertaken is the (buying &) downloading the sailfish zip

I was trying to unlock the bootloader first.

I'll reply again after this step

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

suicidal_orange | # 1877 | 2017-10-18, 07:16 | Report

Originally Posted by deprecated View Post

I took at a look at the SIM carriage for F5122, and it appears there are only 17 pins total on the package. 9 on one side, 8 on another.

SIMs are 6 pins, SD cards are 8, so that's a total of 20 pins. Looks to me like one of the SIM sockets physically share pins with the SD socket.

Of course, I could be wrong. This is just based on a cursory inspection of the repair part.

Sounds like a great idea but the tray looks to be plastic and I see no pins so I guess you're looking at the PCB (or I've found a generic pic not the actual one)? Shared GND would make sense by that's only two pins saved... Wherever these contacts are someone can continuity test between them and see what's connected to what.

The Following 2 Users Say Thank You to suicidal_orange For This Useful Post:
hhbbap, juiceme

jenix | # 1878 | 2017-10-18, 07:38 | Report

Originally Posted by DrYak View Post

After reading this info :
- they totally failed to understand that the current kernel doesn't even detect the presence of an SD card.
It has nothing to do with the format of the partition, it doesn't even reach the point where the partition content matters.
This info isn't relevant (yet) to your case.

But, well, as said above : community members are trying to build a new kernel. If that solves your problem, it's something that will be much easier for Jolla to integrate into the next update of Sailfish X

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? Missing support for specific card types (a seems to be what we have found out here) could be an additional thing..

I'll try to ask about the sdcard issues in the upcoming community meeting today, if there is a chance for it.

The Following 3 Users Say Thank You to jenix For This Useful Post:
juiceme, maximilian1st, suicidal_orange

rfa | # 1879 | 2017-10-18, 09:29 | Report

Originally Posted by rfa View Post

The step I haven't undertaken is the (buying &) downloading the sailfish zip

I was trying to unlock the bootloader first.

I'll reply again after this step

Now I get :

Originally Posted by

Invalid Request

Unfortunately we were unable to process this request

on the Jolla payment page - after getting to: https://shop.jolla.com/payment/purchase/

Last edited by rfa; 2017-10-18 at 09:32. Reason: details

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

rfa | # 1880 | 2017-10-18, 11:23 | Report

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?

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