Notices


Reply
Thread Tools
Posts: 84 | Thanked: 606 times | Joined on Jul 2015 @ Berlin, Germany
#21
Originally Posted by acrux View Post
Hmm, but what about the blobs itself?
When flashing the community build I used SW_binaries_for_Xperia_AOSP_M_MR1_3.10_v12_loire.z ip, but now the recommended one is: SW_binaries_for_Xperia_AOSP_M_MR1_3.10_v13_loire.z ip?
v12 vs v13?
Use the normal blob img file (the one I linked in the guide) in combination with these instructions.
 

The Following 2 Users Say Thank You to jakibaki For This Useful Post:
Posts: 428 | Thanked: 256 times | Joined on Oct 2011 @ Grenoble, France
#22
Originally Posted by m4r0v3r View Post
i flashed that then flashed sfos but network isnt working :/ guessing something didnt flash?
You need to boot onto Android once. That's very important. I had same problem than you
 

The Following 3 Users Say Thank You to mousse04 For This Useful Post:
Posts: 20 | Thanked: 38 times | Joined on May 2015
#23
Currently in the final step: sudo ./flash.sh
Detected Linux
Searching device to flash..
Found device with vendor id '0fce': Bus 001 Device 023: ID 0fce:adde Sony Ericsson Mobile Communications AB C2005 (Xperia M dual) in service mode
Fastboot command: fastboot -i 0x0fce

How long is it supposed to be? (15 minutes so far)

(...) Aborted :-(
Phone still running Android.

(...) Retrying after pressing volume up a bit longer than before. Blue LED instead of green. Now flashing. Phone rebooted as SFOS (Without a SIM card, as the required size is now even smaller.)

Thanks a lot, Jakibaki!

Last edited by objectifnul; 2017-10-11 at 21:34.
 

The Following User Says Thank You to objectifnul For This Useful Post:
benny1967's Avatar
Posts: 3,774 | Thanked: 5,592 times | Joined on Mar 2006 @ Vienna, Austria
#24
Originally Posted by jakibaki View Post
This is an unofficial Guide for installing the official Sailfish X image on your Xperia X (single sim-version, it might possibly work with the dual-sim version but that's untested) using Linux/MacOS.
You're my hero. Worked great! Thank you so much!
 

The Following 3 Users Say Thank You to benny1967 For This Useful Post:
Posts: 5 | Thanked: 15 times | Joined on Jun 2014
#25
Thanks jakibaki!

Flashed a F5122 from Linux and seems to working well :-)
 

The Following 5 Users Say Thank You to bruce-one For This Useful Post:
Posts: 448 | Thanked: 753 times | Joined on Jan 2010 @ France
#26
Originally Posted by jakibaki View Post
You don't need any drm keys.

If you didn't run ota while on an official sony rom in the last few days you'll need to install the update. It enables a special partition to be written to from fastboot-mode which is needed to install sailfish-x. (there is a workaround but this way is much easier)
Hi jakibaki,


What do you mean by « (there is a workaround but this way is much easier) ».

Also, I own a F5122 (double sim), I am running build n° 34.3.A.0.238, so it look like it is at the right level of build.

Is there a way to just verify the special partition exist on my device, before engaging the process to flash SFOS for X ?


Regards,

COLIN Stéphane

Last edited by colin.stephane; 2017-10-11 at 22:03. Reason: Typo's ...
 

The Following 2 Users Say Thank You to colin.stephane For This Useful Post:
Posts: 392 | Thanked: 707 times | Joined on Aug 2014
#27
Originally Posted by jakibaki View Post
Now run
Code:
./flash.sh
on MacOS to flash Sailfish OS.Finally reboot your phone and enjoy Sailfish OS on your Phone!
Just completed using Mac OSX High Sierra, many thanks.

HTML Code:
Last login: Wed Oct 11 22:24:22 on console
iMac:~ adrian$ cd //Users/adrian/Desktop/SailfishX/SailfishOS-2.1.3.5-1-f5121-0.0.1.16 
iMac:SailfishOS-2.1.3.5-1-f5121-0.0.1.16 adrian$ chmod +x flash.sh
iMac:SailfishOS-2.1.3.5-1-f5121-0.0.1.16 adrian$ ./flash.sh
Detected Mac OS X - Version: 10 13-
Searching device to flash..
Found device with vendor id '0fce': Vendor ID: 0x0fce:
Fastboot command: fastboot -i 0x0fce 
./flash.sh: line 167: md5sum: command not found
Flashing boot partition..
target reported max download size of 536870912 bytes
sending 'boot' (10842 KB)...
OKAY [  0.342s]
writing 'boot'...
OKAY [  0.077s]
finished. total time: 0.420s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [  0.228s]
sending sparse 'system' 1/2 (524284 KB)...
OKAY [ 16.455s]
writing 'system' 1/2...
OKAY [  3.677s]
sending sparse 'system' 2/2 (92428 KB)...
OKAY [  2.961s]
writing 'system' 2/2...
OKAY [  0.654s]
finished. total time: 23.974s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [  0.173s]
sending sparse 'userdata' 1/3 (524284 KB)...
OKAY [ 16.456s]
writing 'userdata' 1/3...
OKAY [  3.668s]
sending sparse 'userdata' 2/3 (524284 KB)...
OKAY [ 16.500s]
writing 'userdata' 2/3...
OKAY [  3.673s]
sending sparse 'userdata' 3/3 (252840 KB)...
OKAY [  7.986s]
writing 'userdata' 3/3...
OKAY [  1.767s]
finished. total time: 50.222s
Flashing oem partition..
target reported max download size of 536870912 bytes
sending 'oem' (163040 KB)...
OKAY [  5.140s]
writing 'oem'...
OKAY [ 22.583s]
finished. total time: 27.723s

Flashing completed.

Remove the USB cable and bootup the device by pressing powerkey.
 

The Following 2 Users Say Thank You to aspergerguy For This Useful Post:
Posts: 84 | Thanked: 606 times | Joined on Jul 2015 @ Berlin, Germany
#28
The workaround would have been booting into recovery and moving the blobs to the special partition from there (the partition is only read-only in fastboot mode) but since you're already on a new firmware you very likely won't need that.

Originally Posted by colin.stephane View Post
Is there a way to just verify the special partition exist on my device, before engaging the process to flash SFOS for X ?
Download and extract the .img file from here, enter fastboot mode and then cd to the folder where you downloaded that image and run
Code:
sudo fastboot flash oem SW_binaries_for_Xperia_AOSP_M_MR1_3.10_v13_loire.img
If it runs without an error that means that the partition is properly writable.
 

The Following 4 Users Say Thank You to jakibaki For This Useful Post:
Posts: 880 | Thanked: 2,055 times | Joined on Jan 2012 @ UK
#29
Originally Posted by jakibaki View Post
The workaround would have been booting into recovery and moving the blobs to the special partition from there (the partition is only read-only in fastboot mode) but since you're already on a new firmware you very likely won't need that.



Download and extract the .img file from here, enter fastboot mode and then cd to the folder where you downloaded that image and run
Code:
sudo fastboot flash oem SW_binaries_for_Xperia_AOSP_M_MR1_3.10_v13_loire.img
If it runs without an error that means that the partition is properly writable.
So if this works we don't need EMMA for the official build?
 

The Following User Says Thank You to mariusmssj For This Useful Post:
Posts: 84 | Thanked: 606 times | Joined on Jul 2015 @ Berlin, Germany
#30
Originally Posted by mariusmssj View Post
So if this works we don't need EMMA for the official build?
You don't need emma for the official build at all (that's the whole point of this guide).
If this works you can just skip the flashtool step of the guide.
 

The Following 6 Users Say Thank You to jakibaki For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 01:48.