How to unlock bootloader - Sony xperia X

[rfa]

https://developer.sonymobile.com/unlockbootloader/

I'm sure as we approach Jolla releasing the firmware we're all waiting for we'll need this link.


For my own curiosity, there's no need for me to use this until I get an OS image, is there?

[jurop88]

This link can be useful as well.
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
The TA partition is where the DRM key is stored. When the bootloader is unlocked, the DRM keys are being wiped and therefore are lost forever. With the procedure mentioned above we can safely have a backup of the DRM keys, therefore being able to restore the Xperia to its 'like new' conditions in case of warranty repairs.

It is therefore important to backup the TA partition and DRM keys BEFORE unlocking bootloader first time.

The above procedure is based on an exploit present on Android < 7.0, corrected with the Nougat version. Therefore, if your device is shipped with Nougat pre-installed it takes a bit more time since you need to downgrade the phone first to a previous Android version.
I already did it with mine and I can confirm the procedure works.

[pexi]

What about this one: https://www.reddit.com/r/SonyXperia/comments/6huyxm/xperia_x_root_guide_with_working_drm_on_stock_rom/

Is it possible to have DRM with multirom?

[explit]

MultiROM would probably not support SailfishOS on Xperia.
DRM (TA-Backup) can be restored back with XperiaFlashtool. don't know if it will be needed after Sailfish is installed

[rob_kouw]

I can't get this working. Of course I'm not experienced with stuff like this. The phone came with Android 7.0.

In Windows I installed the Flash Tool (Emma), which did not connect automatically. On the Sony pages I found the X was not mentioned with a key to connect to Emma!? (https://developer.sonymobile.com/open-devices/flash-tool/supported_phones/)
(Edit: After connecting holding the volume up key some extra drivers were installed. Then Emma did connect when plugging the USB in while holding the volume down key. Need to unlock first.)

Then I found that the bootloader needs to be unlocked first. (OK, why not, never mind backing up the TA partition an DRM keys now.)

I decided to get my unlock key anyway. The description says to install the Android SDK, but only the command tools at the bottom. Fine, but this is only a zip file. The Extras folder where I should update a driver is not there, it's probably necessary to install the entire SDK...

I rest my case for now, I'll just wait for a more convenient tool from SailfishOS...

[meloferz]

I can't get this working. Of course I'm not experienced with stuff like this. The phone came with Android 7.0.

In Windows I installed the Flash Tool (Emma), which did not connect automatically. On the Sony pages I found the X was not mentioned with a key to connect to Emma!? (https://developer.sonymobile.com/open-devices/flash-tool/supported_phones/)

Then I found that the bootloader needs to be unlocked first. (OK, why not, never mind backing up the TA partition an DRM keys now.)

I decided to get my unlock key anyway. The description says to install the Android SDK, but only the command tools at the bottom. Fine, but this is only a zip file. The Extras folder where I should update a driver is not there, it's probably necessary to install the entire SDK...

I rest my case for now, I'll just wait for a more convenient tool from SailfishOS...Don't unlock your bootloader before you make the DRM key backup! That's why you have to downgrade and execute the script to backup it, before you unlock... Because if you unlock your bootloader, you will lose your DRM key

Enviado desde mi F5121 mediante Tapatalk

[meloferz]

I recommend you to download flashtool from www.flashtool.net, that's has a more friendly UI and is good for start

Enviado desde mi F5121 mediante Tapatalk

[meloferz]

Also this link will help you a lot https://forum.xda-developers.com/showthread.php?t=3590476

Enviado desde mi F5121 mediante Tapatalk

[explit]

https://talk.maemo.org/showpost.php?p=1532677&postcount=785

[Drekkie]

Also this link will help you a lot https://forum.xda-developers.com/showthread.php?t=3590476

Enviado desde mi F5121 mediante Tapatalk

Just wanted to reiterate if you are wanting to backup DRM partition and unlock the xperia x, the post above (and the dirty cow post it links to) are pretty good, and worked for someone like me who is still novice in these areas. The DRM image was successfully created.

My curent noob question is now that i have my DRM img successfully backed up, i'm not sure from those threads how to actually restore it back to stock if i wanted to (i have only unlocked, not rooted).

Do you just copy the TA/DRM backup img file to phone and use twrp to flash it, or are you supposed to connect the phone to computer and boot into fastboot mode where you run adb commands from the pc? Have been searching but not found any explicit examples, just mentions of 'flash with the drm img back to stock'.

[meloferz]

Just wanted to reiterate if you are wanting to backup DRM partition and unlock the xperia x, the post above (and the dirty cow post it links to) are pretty good, and worked for someone like me who is still novice in these areas. The DRM image was successfully created.

My curent noob question is now that i have my DRM img successfully backed up, i'm not sure from those threads how to actually restore it back to stock if i wanted to (i have only unlocked, not rooted).

Do you just copy the TA/DRM backup img file to phone and use twrp to flash it, or are you supposed to connect the phone to computer and boot into fastboot mode where you run adb commands from the pc? Have been searching but not found any explicit examples, just mentions of 'flash with the drm img back to stock'.In the thread of the backup tool, there is a command that you can use to restore DRM keys, some people do with TWRP in the terminal, or connected to the pc with adb

Enviado desde mi F5121 mediante Tapatalk

[meloferz]

After restore DRM keys, you have to flash stock rom to boot

Enviado desde mi F5121 mediante Tapatalk

[explit]

After restore DRM keys, you have to flash stock rom to boot

Enviado desde mi F5121 mediante Tapatalk

Thats good to know. So as long as bootloader is unlocked and we use unsigned ROM (AOSP, SailfishOS etc.) we don't need (and don't can) restore the DRM-Keys ?

[rob_kouw]

I tried to flash it with the Androxyde Flasher you suggested. It took me a while to get the right driver, indeed. The Device Manager is happy in Windows 10, no unknown devices any more.

But it won't flash yet.
16/023/2017 00:23:33 - INFO - Device connected in flash mode
16/024/2017 00:24:12 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 34.0.A.2.301_R8A. Customization : Nordic Generic_1302-3140
16/024/2017 00:24:12 - INFO - Preparing files for flashing
16/025/2017 00:25:12 - INFO - Please connect your device into flashmode.
16/025/2017 00:25:13 - INFO - Opening device for R/W
16/025/2017 00:25:13 - INFO - Start Flashing
16/025/2017 00:25:13 - INFO - No loader in the bundle. Searching for one
16/025/2017 00:25:26 - INFO - No matching loader found
16/025/2017 00:25:26 - WARN - No loader found or set manually. Skipping loader
16/025/2017 00:25:27 - INFO - Ending flash session
16/025/2017 00:25:27 - ERROR - null
16/025/2017 00:25:27 - ERROR - Error flashing. Aborted
16/025/2017 00:25:27 - INFO - Device connected in flash mode
16/025/2017 00:25:35 - INFO - List of connected devices (Device Id) :
16/025/2017 00:25:35 - INFO - - USB\VID_0FCE&PID_ADDE\5&365BD757&0&1 Driver installed : true
16/025/2017 00:25:35 - INFO - List of ADB devices :
16/025/2017 00:25:35 - INFO - - none
16/025/2017 00:25:35 - INFO - List of fastboot devices :
16/025/2017 00:25:36 - INFO - - none

[meloferz]

Thats good to know. So as long as bootloader is unlocked and we use unsigned ROM (AOSP, SailfishOS etc.) we don't need (and don't can) restore the DRM-Keys ?That's right, or custom roms based on stock, so... You will restore DRM keys and flash stock rom just to let your phone as it was never unlocked

Enviado desde mi F5121 mediante Tapatalk

[meloferz]

I tried to flash it with the Androxyde Flasher you suggested. It took me a while to get the right driver, indeed. The Device Manager is happy in Windows 10, no unknown devices any more.

But it won't flash yet.
16/023/2017 00:23:33 - INFO - Device connected in flash mode
16/024/2017 00:24:12 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 34.0.A.2.301_R8A. Customization : Nordic Generic_1302-3140
16/024/2017 00:24:12 - INFO - Preparing files for flashing
16/025/2017 00:25:12 - INFO - Please connect your device into flashmode.
16/025/2017 00:25:13 - INFO - Opening device for R/W
16/025/2017 00:25:13 - INFO - Start Flashing
16/025/2017 00:25:13 - INFO - No loader in the bundle. Searching for one
16/025/2017 00:25:26 - INFO - No matching loader found
16/025/2017 00:25:26 - WARN - No loader found or set manually. Skipping loader
16/025/2017 00:25:27 - INFO - Ending flash session
16/025/2017 00:25:27 - ERROR - null
16/025/2017 00:25:27 - ERROR - Error flashing. Aborted
16/025/2017 00:25:27 - INFO - Device connected in flash mode
16/025/2017 00:25:35 - INFO - List of connected devices (Device Id) :
16/025/2017 00:25:35 - INFO - - USB\VID_0FCE&PID_ADDE\5&365BD757&0&1Driver installed : true
16/025/2017 00:25:35 - INFO - List of ADB devices :
16/025/2017 00:25:35 - INFO - - none
16/025/2017 00:25:35 - INFO - List of fastboot devices :
16/025/2017 00:25:36 - INFO - - noneDid pop up a message that told you to use a fsc script? If so... Click yes and try to flash again

Enviado desde mi F5121 mediante Tapatalk

[explit]

Did pop up a message that told you to use a fsc script? If so... Click yes and try to flash again

Enviado desde mi F5121 mediante Tapatalk
Yes thats normal. It tells you this message every time you load a new Firmware for flashing.

I flashed mine with XPeriaFlashTool under Linux

[rob_kouw]

I found this question on GitHub: https://github.com/Androxyde/devices/issues/53 in which someone asks why he cannot flash the F5121 with Androxyde. He states he did manage with an earlier version: "I only flash successfully with an older version F5121_34.0.A.2.301 using 34.0.fsc script."
So it seems I had the wrong ftf to flash with. I will have another go with this version: https://easy-firmware.com/index.php?a=browse&b=category&id=18692, at the bottom.

[meloferz]

I found this question on GitHub: https://github.com/Androxyde/devices/issues/53 in which someone asks why he cannot flash the F5121 with Androxyde. He states he did manage with an earlier version: "I only flash successfully with an older version F5121_34.0.A.2.301 using 34.0.fsc script."
So it seems I had the wrong ftf to flash with. I will have another go with this version: https://easy-firmware.com/index.php?a=browse&b=category&id=18692, at the bottom.I suggest you to use Xperifirm from Flashtool, there it create the ftf after download is completed, that's how I flashed my Xperia X

Enviado desde mi F5121 mediante Tapatalk

[rob_kouw]

OK, I will. Did you use a flash script? Androxyde Flashtool keeps saying:
No flash script found.
Flash script is mandatory. Closing session

(Which is weird as in ...\.flashtool\devices\F51XX there are 3 .fsc files)

[meloferz]

OK, I will. Did you use a flash script? Androxyde Flashtool keeps saying:
No flash script found.
Flash script is mandatory. Closing session

(Which is weird as in ...\.flashtool\devices\F51XX there are 3 .fsc files)It have to be included in the ftf I think, don't remember well because when I downloaded from Xperifirm, flashtool asked me to include in the ftf file, and choose yes, and flashed using fsc script when flashtool asked me

Enviado desde mi F5121 mediante Tapatalk

[rob_kouw]

In the meantime I found this explanation of the setup on Windows 10, with temporary disabling of Driver Signature Enforcement, allowing you to install the right drivers.
http://www.droidviews.com/setup-androxyde-flashtool-sony-xperia-devices-windows/

He also gives a step-by-step guide for XperiFirm and FlashTool.
http://www.droidviews.com/install-stock-firmware-on-sony-xperia-devices-using-xperifirm-and-flashtool/

Edit: I finally flashed the phone. Thanks guys!
The trick for me was the installation of the drivers. Everything seemed to be OK, but apparently wasn't. The part of disabling of Driver Signature Enforcement before starting Flashtool-drivers.exe was crucial. I only installed the upper two drivers. All the others are meant for specific models, and the X is not among them.

Further newbie tips: on the phone, Settings, About phone, click "Build number" until you are a Developer. With Developer Options allow "USB Debugging". I disabled "Verify apps over USB", not sure whether needed. For later use, enable "OEM unlocking" here too.

Before flashing: hold key Volume Down when plugging in the USB cable. For backupTA connect normally with MTP.

[explit]

Guys! Make it better with Xperia Flashtool. Its much easier

[rob_kouw]

Guys! Make it better with Xperia Flashtool. Its much easier

Sorry, I have no Linux pc available for that. :eek:

[juiceme]

I could not wait a week but powered on my shiny new F5121 for the first time now :p
(OK I did manage to hold and wait more than a week before doing so!)

But now I have few questions;
1.) my device seems to come with Nougat 7.1.1 preinstalled.
Now, to save the TA partition it is apparent that I need to downgrade this to 6.x in order to be able to use the tad-daemon workaround.
The question is; where to get a known-good Marshmallow image for my device? When I search the net I find numerous sites that allow download but how to know which are genuine? 2.) I am unsure how the downgrade is supposed to help; I understand that unlocking the bootloader destroys the DRM keys but how can I flash the downgrade image without unlocking the bootloader?
Or is there something special about "sony-signed" images that allow them to be flashed without bootloader unlocking? 3.) If the above is true, does the flashing process guarantee that I can only flash a real-sony-signed-image with locked bootloader?
If that is true, then I don't need to worry about where I download the image, right?

[carmenluci]

I could not wait a week but powered on my shiny new F5121 for the first time now :p
(OK I did manage to hold and wait more than a week before doing so!)

But now I have few questions;
1.) my device seems to come with Nougat 7.1.1 preinstalled.
Now, to save the TA partition it is apparent that I need to downgrade this to 6.x in order to be able to use the tad-daemon workaround.
The question is; where to get a known-good Marshmallow image for my device? When I search the net I find numerous sites that allow download but how to know which are genuine? 2.) I am unsure how the downgrade is supposed to help; I understand that unlocking the bootloader destroys the DRM keys but how can I flash the downgrade image without unlocking the bootloader?
Or is there something special about "sony-signed" images that allow them to be flashed without bootloader unlocking? 3.) If the above is true, does the flashing process guarantee that I can only flash a real-sony-signed-image with locked bootloader?
If that is true, then I don't need to worry about where I download the image, right?


1) You can download Android 6 using Xperifirm, the answer is here: https://talk.maemo.org/showpost.php?p=1532677&postcount=785, and you can download Xperifirm from XDA Forum: https://forum.xda-developers.com/crossdevice-dev/sony/pc-xperifirm-xperia-firmware-downloader-t2834142

2) You don't need unlock the bootloader to flash the downgrade image

3) Yes, you can only flash sony image without bootloader unlocking

[juiceme]

1) You can download Android 6 using Xperifirm, the answer is here: https://talk.maemo.org/showpost.php?p=1532677&postcount=785, and you can download Xperifirm from XDA Forum: https://forum.xda-developers.com/crossdevice-dev/sony/pc-xperifirm-xperia-firmware-downloader-t2834142

2) You don't need unlock the bootloader to flash the downgrade image

3) Yes, you can only flash sony image without bootloader unlocking

Thanks!

This is good to know, especially 3.) since it means I cannot accidentally flash a buggy/compromised package :D

Can one do this from Linux, as I have no access to windows machines and frankly would not want to install a VM just for this purpose?

[aspergerguy]

Can one do this from Linux, as I have no access to windows machines and frankly would not want to install a VM just for this purpose?

You should get Linux version from here:https://www.installandroidrom.co.uk/2017/03/download-sony-mobile-flasher-for.html

I am sure that you have already found ExplIT's resource:http://sailfishmods.de/2017/07/howto-sony-xperia-x-teil-1-cda-drm-keys-bootloader/

[juiceme]

You should get Linux version from here:https://www.installandroidrom.co.uk/2017/03/download-sony-mobile-flasher-for.html

Lovely!
I actually already found https://github.com/Androxyde/Flashtool when I started looking with correct keywords :D

[aspergerguy]

Back to orange triangle (brings back memories) and this device will Boot in 5secs.:D

[HtheB]

You can actually just download the images from Sony itself using the Flashtool..... Even all the countries and carrier options are available.

[juiceme]

You can actually just download the images from Sony itself using the Flashtool..... Even all the countries and carrier options are available.

bummer, not so easy :(

It seems that downloading the image is not possible from inside the Flashtool in the linux version, it requires an external windows binary "XperiFirm.exe"...

I tried flashing using the image found in @ExplIT's link (which seems to be "F5121_34.0.A.2.292_Customized DE" but either the image is noncomplete or there is something dizzy about my environment/setup, as Flasher fails for "no loader" and "no flash script" ...

root@tither:~/.flashTool# cat flashtool_2017-09-19_05-49-28.log
19/031/2017 17:31:23 - INFO - <- This level is successfully initialized
19/031/2017 17:31:28 - INFO - Flashtool Version 0.9.23.1 built on 11-01-2017 15:12:00
19/031/2017 17:31:28 - INFO - libusb version 1.0.20
19/031/2017 17:31:28 - INFO - Executing search strategies to find proxy selector
19/031/2017 17:31:28 - INFO - No proxy found for gnome. Trying next one
19/031/2017 17:31:28 - INFO - No proxy found for kde. Trying next one
19/031/2017 17:31:28 - INFO - Proxy found for firefox
19/031/2017 17:31:29 - INFO - Syncing devices from github
19/031/2017 17:31:29 - INFO - Opening devices repository.
19/031/2017 17:31:30 - INFO - Scanning devices folder for changes.
19/031/2017 17:31:41 - INFO - Pulling changes from github.
19/031/2017 17:31:42 - INFO - Quietly closing devices repository.
19/031/2017 17:31:42 - INFO - Devices sync finished.
19/031/2017 17:31:42 - INFO - Loading devices database
19/031/2017 17:31:42 - INFO - Loaded 98 devices
19/031/2017 17:31:42 - INFO - Starting phone detection
19/031/2017 17:31:45 - INFO - Device disconnected
19/032/2017 17:32:07 - INFO - Device connected in flash mode
19/032/2017 17:32:43 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 34.0.A.2.292. Customization : Customized DE
19/032/2017 17:32:43 - INFO - Preparing files for flashing
19/035/2017 17:35:10 - INFO - Please connect your device into flashmode.
19/035/2017 17:35:12 - INFO - Opening device for R/W
19/035/2017 17:35:12 - INFO - Device ready for R/W.
19/035/2017 17:35:12 - INFO - Reading device information
19/035/2017 17:35:12 - INFO - Phone ready for flashmode operations.
19/035/2017 17:35:12 - INFO - Opening TA partition 2
19/035/2017 17:35:12 - INFO - Current device : F5121 - CB512EV81U - 1302-4766_R2D - 1300-4911_34.3.A.0.194 - GENERIC_34.3.A.0.194
19/035/2017 17:35:12 - INFO - Closing TA partition
19/035/2017 17:35:12 - INFO - Start Flashing
19/035/2017 17:35:12 - INFO - No loader in the bundle. Searching for one
19/035/2017 17:35:12 - INFO - No matching loader found
19/035/2017 17:35:12 - WARN - No loader found or set manually. Skipping loader
19/035/2017 17:35:12 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_N_160 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_N_160 / Bootloader status : ROOTABLE
19/035/2017 17:35:12 - INFO - Max packet size set to 4M
19/035/2017 17:35:12 - INFO - USB buffer size set to 512K
19/035/2017 17:35:15 - INFO - Parsing boot delivery
19/035/2017 17:35:15 - INFO - No flash script found.
19/035/2017 17:35:15 - INFO - Flash script is mandatory. Closing session
19/035/2017 17:35:15 - INFO - Ending flash session
19/035/2017 17:35:15 - INFO - Flashing finished.
19/035/2017 17:35:15 - INFO - Please unplug and start your phone
19/035/2017 17:35:15 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
19/035/2017 17:35:16 - INFO - Device connected in flash mode
19/036/2017 17:36:35 - INFO - Device disconnected
root@tither:~/.flashTool#

[Heik]

In my flashing process (in Windows) I had to select USERDATA option under Wipe in Flashtool Firmware Selector.

Not sure if I got similar results as juiceme, when it was not selected. Anyway, flashing failed.

May be totally different problem, though.

[Mazoon]

bummer, not so easy :(

It seems that downloading the image is not possible from inside the Flashtool in the linux version, it requires an external windows binary "XperiFirm.exe"...

I tried flashing using the image found in @ExplIT's link (which seems to be "F5121_34.0.A.2.292_Customized DE" but either the image is noncomplete or there is something dizzy about my environment/setup, as Flasher fails for "no loader" and "no flash script" ...

root@tither:~/.flashTool# cat flashtool_2017-09-19_05-49-28.log
19/031/2017 17:31:23 - INFO - <- This level is successfully initialized
19/031/2017 17:31:28 - INFO - Flashtool Version 0.9.23.1 built on 11-01-2017 15:12:00
19/031/2017 17:31:28 - INFO - libusb version 1.0.20
19/031/2017 17:31:28 - INFO - Executing search strategies to find proxy selector
19/031/2017 17:31:28 - INFO - No proxy found for gnome. Trying next one
19/031/2017 17:31:28 - INFO - No proxy found for kde. Trying next one
19/031/2017 17:31:28 - INFO - Proxy found for firefox
19/031/2017 17:31:29 - INFO - Syncing devices from github
19/031/2017 17:31:29 - INFO - Opening devices repository.
19/031/2017 17:31:30 - INFO - Scanning devices folder for changes.
19/031/2017 17:31:41 - INFO - Pulling changes from github.
19/031/2017 17:31:42 - INFO - Quietly closing devices repository.
19/031/2017 17:31:42 - INFO - Devices sync finished.
19/031/2017 17:31:42 - INFO - Loading devices database
19/031/2017 17:31:42 - INFO - Loaded 98 devices
19/031/2017 17:31:42 - INFO - Starting phone detection
19/031/2017 17:31:45 - INFO - Device disconnected
19/032/2017 17:32:07 - INFO - Device connected in flash mode
19/032/2017 17:32:43 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 34.0.A.2.292. Customization : Customized DE
19/032/2017 17:32:43 - INFO - Preparing files for flashing
19/035/2017 17:35:10 - INFO - Please connect your device into flashmode.
19/035/2017 17:35:12 - INFO - Opening device for R/W
19/035/2017 17:35:12 - INFO - Device ready for R/W.
19/035/2017 17:35:12 - INFO - Reading device information
19/035/2017 17:35:12 - INFO - Phone ready for flashmode operations.
19/035/2017 17:35:12 - INFO - Opening TA partition 2
19/035/2017 17:35:12 - INFO - Current device : F5121 - CB512EV81U - 1302-4766_R2D - 1300-4911_34.3.A.0.194 - GENERIC_34.3.A.0.194
19/035/2017 17:35:12 - INFO - Closing TA partition
19/035/2017 17:35:12 - INFO - Start Flashing
19/035/2017 17:35:12 - INFO - No loader in the bundle. Searching for one
19/035/2017 17:35:12 - INFO - No matching loader found
19/035/2017 17:35:12 - WARN - No loader found or set manually. Skipping loader
19/035/2017 17:35:12 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_N_160 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_N_160 / Bootloader status : ROOTABLE
19/035/2017 17:35:12 - INFO - Max packet size set to 4M
19/035/2017 17:35:12 - INFO - USB buffer size set to 512K
19/035/2017 17:35:15 - INFO - Parsing boot delivery
19/035/2017 17:35:15 - INFO - No flash script found.
19/035/2017 17:35:15 - INFO - Flash script is mandatory. Closing session
19/035/2017 17:35:15 - INFO - Ending flash session
19/035/2017 17:35:15 - INFO - Flashing finished.
19/035/2017 17:35:15 - INFO - Please unplug and start your phone
19/035/2017 17:35:15 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
19/035/2017 17:35:16 - INFO - Device connected in flash mode
19/036/2017 17:36:35 - INFO - Device disconnected
root@tither:~/.flashTool#


F5121_34.0.A.2.301_R8A_Nordic Generic_1302-3140.ftf (edit: md5sum
6ea96ed801e6a8d3164f5280c84b17f4) worked for my unit from the recent Verkkokauppa.com sale, had to however allow debug, unknown sources and disable verification of stuff installed through USB ("Tarkista USBN:n kautta asennetut"), I think.
I think I downloaded the image from https://easy-firmware.com/home/browse/file-info/id/58108 (maybe a legit image? or full of malware? doesn't matter, got the TA partition with it and will overwrite with SFOS)

[jayki]

bummer, not so easy :(

It seems that downloading the image is not possible from inside the Flashtool in the linux version, it requires an external windows binary "XperiFirm.exe"...


For me it works with installed "mono (https://www.archlinux.org/packages/extra/x86_64/mono/)" Package, which can run the .exe. Don't know how to install Mono on other Distributions but in Archlinux it was just installing the mono package :)

[mrsellout]

For me it works with installed "mono (https://www.archlinux.org/packages/extra/x86_64/mono/)" Package, which can run the .exe. Don't know how to install Mono on other Distributions but in Archlinux it was just installing the mono package :)

You could also use the docker version ( https://hub.docker.com/_/mono/ ) if you don't want to keep mono on your system afterwards.

[juiceme]

F5121_34.0.A.2.301_R8A_Nordic Generic_1302-3140.ftf (edit: md5sum
6ea96ed801e6a8d3164f5280c84b17f4) worked for my unit from the recent Verkkokauppa.com sale, had to however allow debug, unknown sources and disable verification of stuff installed through USB ("Tarkista USBN:n kautta asennetut"), I think.
I think I downloaded the image from https://easy-firmware.com/home/browse/file-info/id/58108 (maybe a legit image? or full of malware? doesn't matter, got the TA partition with it and will overwrite with SFOS)

Thanks, downloaded that file but the same thing still haunts me.
Why does it say "No flash script found. / Flash script is mandatory. Closing session" ?

What's this flash script anyway, is it part of the SW package or is it something I am missing in the Flasher?

I am beginnig to think downgrading is impossible for me... probably I am going to just unlock the bootloader and care f**ck about the TA backup thingy :mad:

[jurop88]

What a 'flash script (.fsc)' is:
http://www.flashtool.net/fsccreate.php
Building one is 'close to impossible' for non-skilled person (I dug a bit about it with the USB logger with no success - I am not a skilled one :))
The downloaded image shall therefore have this .fsc file included. With XperiFirm I found a version with MM for my phone that included the flash script and flashed with no hassle back to Android 6.01 using that one (F5121_34.0.A.2.292_R4A_Customized IT)

[juiceme]

What a 'flash script (.fsc)' is:
http://www.flashtool.net/fsccreate.php
Building one is 'close to impossible' for non-skilled person (I dug a bit about it with the USB logger with no success - I am not a skilled one :))
The downloaded image shall therefore have this .fsc file included. With XperiFirm I found a version with MM for my phone that included the flash script and flashed with no hassle back to Android 6.01 using that one (F5121_34.0.A.2.292_R4A_Customized IT)

Thanks, so I'd need to pull a flashscript for my device from a git repo somewhere?
(I assume these are device type specific, and not SW release specific, right?)

Any pointers where to get it?

[nieldk]

Thanks, so I'd need to pull a flashscript for my device from a git repo somewhere?
(I assume these are device type specific, and not SW release specific, right?)

Any pointers where to get it?

I suggest using flashtool, it will create the file for you.
It may need modifications, but probably the best starting point.

[juiceme]

I suggest using flashtool, it will create the file for you.
It may need modifications, but probably the best starting point.

Heh, that error comes from the Flashtool :D

I guess I need to run xperiafrm.exe to get a proper SW package instead of downloading from random sites off da net.
I already tried that with mono but was behind the company firewall and it did not work. Have to try it from home...

[jurop88]

I guess I need to run xperiafrm.exe to get a proper SW package instead of downloading from random sites off da net.

^ this

worst case I still have the above ITA image to share, do not know if it's legal and how to do it, though

[joschobart]

For me it works with installed "mono (https://www.archlinux.org/packages/extra/x86_64/mono/)" Package, which can run the .exe. Don't know how to install Mono on other Distributions but in Archlinux it was just installing the mono package :)

In debian/ubuntu-like distros you install wine with this command:

sudo apt-get install wine

Then run the .exe by typing:

wine XperiFirm.exe

Update: In order to use the tool you need .Net 4.0 installed as well. After installing wine install .Net with the following command:

winetricks dotnet40

[nieldk]

Heh, that error comes from the Flashtool :D

I guess I need to run xperiafrm.exe to get a proper SW package instead of downloading from random sites off da net.
I already tried that with mono but was behind the company firewall and it did not work. Have to try it from home...

The ftf file that you downloaded have already been processed by flashtool (flashtool generates that file)
You will need to download a firmware with xperifirm, which flashtool will process, creating a directory in flashtool folder with all the files it uses to create the ftf file.
Among them the flash file script.
Also, you should update flashtool (it’s a single jar file that you just replace in flashtool folder).
Short: The script is used to generate the ftf file (from my Xperia team days memory when I cracked the Play boot loader)

[Heik]

When I tried to use files that I downloaded using XperiFirm and created the ftf file from the files in downloaded folder (Tools > Bundles > Create) (did not use files cust-reset.ta and fota-reset.ta) I got about the same error as juiceme. Maybe I just made some error in creating the ftf file.

21/035/2017 21:35:41 - INFO - No flash script found.
21/035/2017 21:35:41 - INFO - Flash script is mandatory. Closing session

When I used ftf file that I directly downloaded for example from http://www.gsm-file.com/
(for F5121:
F5121_34.0.A.2.301_R8A_Nordic Generic_1302-3140.ftf

for F5122:
F5122_34.0.A.2.301_R9A_Hong Kong Generic_1302-5683.ftf,
later noticed, that also
F5122_34.0.A.1.277_Central Europe_1302-5672_R3A.ftf
was available)

I managed to flash the phones without any problems, assuming that USERDATA was ticked in wipe option in flashtool Firmware Selector.

I did this all in Windows 10, however, I did not manage to follow Windows instructions to backup DRM partitions, I had to do that in Linux :-)

[juiceme]

Well, managed to run XperiFirm.exe by running it in mono.

When I select Xperia X / F5121 it gives a bunch of downloads, but seems there are only latest versions available.
How do I know which android version they are?

I tested by selecting bundled nordic version, and downloaded it; however instead of a single *.ftf file, there are tens of files of type *.sin
Can I perform a flashing with these, or do I need to somehow bundle these to a *ftf first?

[lantern]

Throw away XperiFirm.
Flash this fw (F5121/5122 - doesn't matter)
http://www.mediafire.com/file/tmovrijc3rt6hn8/F5121_4.0.A.2.301_R8A_Customized+TW_1302-4771.ftf

[nieldk]

Well, managed to run XperiFirm.exe by running it in mono.

When I select Xperia X / F5121 it gives a bunch of downloads, but seems there are only latest versions available.
How do I know which android version they are?

I tested by selecting bundled nordic version, and downloaded it; however instead of a single *.ftf file, there are tens of files of type *.sin
Can I perform a flashing with these, or do I need to somehow bundle these to a *ftf first?

flashtool will bundle them to an ftf file when you choose flash.
For Android 6.0.1, you can download 'storefront' version from Xperifirm (version 34.0.A.1.264)

[juiceme]

Throw away XperiFirm.
Flash this fw (F5121/5122 - doesn't matter)
http://www.mediafire.com/file/tmovrijc3rt6hn8/F5121_4.0.A.2.301_R8A_Customized+TW_1302-4771.ftf

Thanks, I'll try that.
(altough I am sceptical, why would one image behave differently than another...)

Oh, downloading time 1h45min...

[juiceme]

flashtool will bundle them to an ftf file when you choose flash.

Well, this is one of the reasons I hate GUI tools like this.
For a CLI tool one can give exact information how to use, a string of characters to use on a terminal.
For a GUI tool one can only give vague advice on what should be done and clicked...

For example, how to "flashtool will bundle them" for example; when I push the "flash" button and navigate to a directory where I have a *.ftf file, it will open a tree view of the SW and allow me to start flashing.
If I navigate to the directory where I have this bundle of *sin's I got no such thing and the "flash" button stays grayed out.

For the life of me I cannot understand why people would want to create utilities like these when it is bloody obvious a CLI tool would be much easier???


For Android 6.0.1, you can download 'storefront' version from Xperifirm (version 34.0.A.1.264)

OK, I'll try to download that.

[nieldk]

Well, this is one of the reasons I hate GUI tools like this.
For a CLI tool one can give exact information how to use, a string of characters to use on a terminal.
For a GUI tool one can only give vague advice on what should be done and clicked...

For example, how to "flashtool will bundle them" for example; when I push the "flash" button and navigate to a directory where I have a *.ftf file, it will open a tree view of the SW and allow me to start flashing.
If I navigate to the directory where I have this bundle of *sin's I got no such thing and the "flash" button stays grayed out.

For the life of me I cannot understand why people would want to create utilities like these when it is bloody obvious a CLI tool would be much easier???




OK, I'll try to download that.

hehe yeah, Iam CLI guy also

[pacman]

For Android 6.0.1, you can download 'storefront' version from Xperifirm (version 34.0.A.1.264)

Yes, or this detailed German guide (http://sailfishmods.de/2017/07/howto-sony-xperia-x-teil-1-cda-drm-keys-bootloader/) suggests the "Internal – Commerial and Journalists" version. Probably doesn't make much difference either way.

If you ever think that you might want to go back to stock Android, make a note of the current customisation in the phone's service menu.

[juiceme]

Up to now none of the things suggested here have worked for me :eek:

So as I said earlier...
I am beginnig to think downgrading is impossible for me... probably I am going to just unlock the bootloader and care f**ck about the TA backup thingy :mad:

As I think most probably am not going to need any of this DRM BS in any case... I was kind of thinking maybe it could be useful in SFOS at some later time too but if so, then I'll just have to learn to live without it.

In any case I was not doing this to be able to restore the "full original stock android" to the device anyway, am not interested about that and I am not afraid of (a-)voiding any warranty issues anyway...

[epninety]

Up to now none of the things suggested here have worked for me :eek:

So as I said earlier...

As I think most probably am not going to need any of this DRM BS in any case... I was kind of thinking maybe it could be useful in SFOS at some later time too but if so, then I'll just have to learn to live without it.


I had a couple of sessions of trying to make this (DRM backup) happen. All the documentation seemed to be poor, and full of links to even worse documentation. I was frustrated looking at programs whose purpose wasn't clearly stated, and instructions which say 'do xyz' but don't state what the purpose is, or what the expected result is.

Frustrating - I gave up and just unlocked without backing up DRM.

That said, even Sony seem to have it cockeyed - the instructions for how to use the unlock code were only visible before I got the code, I had to go back and request the code again to find the instructions. :confused:

[pexi]

I downloaded the MM image from xperia forum, opened it with flashtool and that's it. No need to make it more complicated.

[pexi]

Get it from here: http://www.xperiablog.net/forum/resources/categories/xperia-x.99/

After that set usb debugging and accept software from usb in Android settings. Then check from your PC that "adb devices" works and execute DRM backup to save your keys.

[juiceme]

I downloaded the MM image from xperia forum, opened it with flashtool and that's it. No need to make it more complicated.

None of the images I have downloaded and tried work for me, flashing always fails with missing flashscript.

[mousse04]

None of the images I have downloaded and tried work for me, flashing always fails with missing flashscript.

I'm uploading an image I've used for my X. Finally working.
Make sure to have fastboot recognized.

I will post the link once it is done 16mns roughly

[juiceme]

I'm uploading an image I've used for my X. Finally working.
Make sure to have fastboot recognized.

I will post the link once it is done 16mns roughly

Thanks!
However I'm a bit doubtful about the fastboot bit, doesn't that require the device to be unlocked?
I have used "Flash Mode" previously as instructed, holding <vol-> down while plugging in USB...

[mousse04]

Thanks!
However I'm a bit doubtful about the fastboot bit, doesn't that require the device to be unlocked?
I have used "Flash Mode" previously as instructed, holding <vol-> down while plugging in USB...

In this case, it is fine.

Here it is :

https://drive.google.com/open?id=0B6TlqqSsp53DaHE1Y0VkY0JEVlE


Let me know how it will work.

[ajalkane]

At least for me that image did not work under Linux. Always stucking on either reading device infromation, or that the flashscript was not found.

What horror. I think I will not have the stomach to try under Windows and experience it's little quirks just to get DRM keys backed up.

[pexi]

I used Linux and I held volume down + plugged usb. flashed in flashmode.

[pexi]

None of the images I have downloaded and tried work for me, flashing always fails with missing flashscript.

The one I referred to worked. I used Linux version of the flash tool.

[ajalkane]

Christ almighty, I managed to flash it using flashtool after installing the patch x10flasher.jar from here:

http://www.flashtool.net/downloads_linux.php

Unfortunately the result is garbage. The phone first booted and complained that some media service has stopped. And after that it boots into distorted image and reboots all over again.

Flasher showed these warnings:

apps_log is excluded from bundle
diag is excluded from bundle
ssd is excluded from bundle
Qnovo is excluded from bundle
persist is excluded from bundle
userdata is excluded from bundle
Unit 2212 not found in bundle
Unit 2550 not found in bundle
Unit 2553 not found in bundle

I'll try again to flash but this seems painful :D

[lantern]

afair you have to wipe userdata

[ajalkane]

afair you have to wipe userdata

I tried with Wipe on all options, to no avail.

I flashed 7.1.1 again on it. At least the device now boots, but it's giving me "com.android.phone has stopped" error all the time. Oh well, waiting for Sailfish.

[juiceme]

OK, now it is decided, I'll pass the hopeless DRM backup thing, request device unlock keys from Sony and I hope the SFOS image is available for purchase tomorrow. :)

What I absolutely don't understand is why the XDA forum guys who undeniably must be android hackers of some reputation put up using windoze for development environment... and the tools they create are this kind of java-crap!

What a world...

[mousse04]

OK, now it is decided, I'll pass the hopeless DRM backup thing, request device unlock keys from Sony and I hope the SFOS image is available for purchase tomorrow. :)

What I absolutely don't understand is why the XDA forum guys who undeniably must be android hackers of some reputation put up using windoze for development environment... and the tools they create are this kind of java-crap!

What a world...

So, meaning my image doesn't work :( ?

[juiceme]

So, meaning my image doesn't work :( ?

I dare not try it as it bricked @ajalkane's phone!

[mousse04]

At least for me that image did not work under Linux. Always stucking on either reading device infromation, or that the flashscript was not found.

What horror. I think I will not have the stomach to try under Windows and experience it's little quirks just to get DRM keys backed up.

Were you using the image I posted ?

[mousse04]

I dare not try it as it bricked @ajalkane's phone!

Strange, this is the one I used

[ajalkane]

Were you using the image I posted ?

Yes. Or actually I've tried so many different links that I'm not sure anymore. I'll try one final time just to make sure.

[mousse04]

Yes. Or actually I've tried so many different links that I'm not sure anymore. I'll try one final time just to make sure.

What you can try to is :

Create a folder : .flashTool/mydevices/F51XX/

in the tar file I uploaded, there is a fsc file. Extract it
and copy it here:


.flashTool/mydevices/F51XX/
.flashTool/devices/F51XX/

Then, close flashtool and launch it again and try flashing again

Good luck

[ajalkane]

What you can try to is :

Create a folder : .flashTool/mydevices/F51XX/


Unfortunately even this didn't work. Same boot loop as a result.

[mousse04]

Unfortunately even this didn't work. Same boot loop as a result.

hum .. very strange

[richie]

I had a couple of sessions of trying to make this (DRM backup) happen. All the documentation seemed to be poor, and full of links to even worse documentation. I was frustrated looking at programs whose purpose wasn't clearly stated, and instructions which say 'do xyz' but don't state what the purpose is, or what the expected result is.


I've yet to do this myself, but trying to make sense of docs. It would be good if someone could do a video of some of the steps to downgrade using official Sony image to help understand instructions.

Rich

[nieldk]

Unfortunately even this didn't work. Same boot loop as a result.

Happened to me once with one SE device. Used Xperia Companion from Sony to fix it.

[juiceme]

I wonder if whether it works correctly, fails alltogether to flash or goes to brickloop depends also on the variant existing on the device?

Using the "Xperia Companion" is a no-no since it is a windoze tool.

---------- edit ----------

I kind of thought the whole point of flashing a device that has a locked bootloader is to do it so that only official Sony-signed images can be flashed... so either it flashes or not but is impossible to brick...??

[pexi]

Hard to believe that I was just lucky so here is the process that I did with my Xperia and Opensuse PC. Hope I remember it all.

- enabled usb debugging and allowed application install from usb in Xperia original android 7
- downloaded flashtool for linux and applied the update available on the flashtool page
- downloaded Xperia scandinavia image version 6.something from the link I gave earlier
- downloaded madcows DRM backup script
- started root shell with "su - root"
- installed adb with "zypper install android-tools"
- plugged in Xperia
- tested that "adb devices" works
- unplugged Xperia
- shut off Xperia
- held volume down button and plugged in Xperia
- launched Flashtool as root
- browsed and opened the Android 6.x what I just downloaded
- used flash mode
- selected all wipes
- watched it update
- rebooted Xperia, set the new user mandatory settings
- enabled usb debugging and install apps from usb
- executed madcows DRM backup script

Never had a glitch. Did I forget something?

[ajalkane]

I wonder if whether it works correctly, fails alltogether to flash or goes to brickloop depends also on the variant existing on the device?

I've also wondered whether there are multiple versions of Xperia X with subtle differences that could explain failure. My box says revision 4, which suggests there is other revisions.

[nieldk]

I wonder if whether it works correctly, fails alltogether to flash or goes to brickloop depends also on the variant existing on the device?

Using the "Xperia Companion" is a no-no since it is a windoze tool.

---------- edit ----------

I kind of thought the whole point of flashing a device that has a locked bootloader is to do it so that only official Sony-signed images can be flashed... so either it flashes or not but is impossible to brick...??

Not impossible to brick, that’s for sure.
I see ppl mentioning setting “wipe all”, that’s usually not necessary. Not entirely sure if that’s the issue, but it very well could be.
It might, more likely, be differences in hw revisions . Slight changes in design or even different chipsets.
I think it’s important feedback for the porters, and really suggest to join IRC channel to involve the porters. And Jolla.

[mousse04]

I wonder if whether it works correctly, fails alltogether to flash or goes to brickloop depends also on the variant existing on the device?

Using the "Xperia Companion" is a no-no since it is a windoze tool.

---------- edit ----------

I kind of thought the whole point of flashing a device that has a locked bootloader is to do it so that only official Sony-signed images can be flashed... so either it flashes or not but is impossible to brick...??

Actually you cannot brick this device as we have a tool to flash in flash mode which is almost the nothing mode :)

@juicme, @ajalkane One trial (because I remember that I had same problem than you to flash stock MM (problem of flash script), but cannot remember how I fix it)

In flash mode, before launching the flashtool (so, flashtool is closed), could you do a ./adb devices in order to start daemon

So, you should get :
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Then, try to flash an image.

FYI, try again the image I provided (not the upload, the one I've uploaded) and it works fine

[mrsellout]

FWIW, I couldn't run the backup script on machines running Arch and Manjaro (an Arch based distro), but was successful on a PC running MX linux (Debian base).

The phone would keep asking what type of usb connection is required (charging, mtp, or midi), and selecting mtp would prompt it to ask again, and again.

[ajalkane]

In flash mode, before launching the flashtool (so, flashtool is closed), could you do a ./adb devices in order to start daemon


Same results, unfortunately. I'm going to bite the bullet with chagrin and try Sony's official flasher on Windows, as it seems that's what will be required anyway for flashing Sailfish.

[nieldk]

Same results, unfortunately. I'm going to bite the bullet with chagrin and try Sony's official flasher on Windows, as it seems that's what will be required anyway for flashing Sailfish.

Could you post the log from trying flashtool?

[ajalkane]

Could you post the log from trying flashtool?

Sure, here's the logs when I flashed Mousse04's image:


28/021/2017 21:21:03 - INFO - Device connected in flash mode
28/021/2017 21:21:23 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 4.0.A.2.301_R8A. Customization : Customized TW
28/021/2017 21:21:23 - INFO - Preparing files for flashing
28/021/2017 21:21:48 - INFO - Please connect your device into flashmode.
28/021/2017 21:21:49 - INFO - Opening device for R/W
28/021/2017 21:21:49 - INFO - Device ready for R/W.
28/021/2017 21:21:49 - INFO - Reading device information
28/021/2017 21:21:49 - INFO - Phone ready for flashmode operations.
28/021/2017 21:21:49 - INFO - Opening TA partition 2
28/021/2017 21:21:49 - INFO - Current device : F5121 - CB512EFM5U - 1302-4771_R8A - 1300-4911_34.0.A.2.301 - GENERIC_34.0.A.2.301
28/021/2017 21:21:49 - INFO - Closing TA partition
28/021/2017 21:21:49 - INFO - Start Flashing
28/021/2017 21:21:49 - INFO - No loader in the bundle. Searching for one
28/021/2017 21:21:49 - INFO - No matching loader found
28/021/2017 21:21:49 - WARN - No loader found or set manually. Skipping loader
28/021/2017 21:21:49 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Bootloader status : ROOTABLE
28/021/2017 21:21:49 - INFO - Max packet size set to 4M
28/021/2017 21:21:49 - INFO - USB buffer size set to 512K
28/021/2017 21:21:50 - INFO - Parsing boot delivery
28/021/2017 21:21:52 - INFO - Found a template session. Using it : /home/arto/.flashTool/firmwares/prepared/F5121_4.0.A.2.301.fsc
28/021/2017 21:21:52 - INFO - Set loader configuration : [00 01 00 00 00 0C]
28/021/2017 21:21:52 - INFO - Opening TA partition 2
28/021/2017 21:21:52 - INFO - Writing TA unit 00002774. Value : 01
28/021/2017 21:21:52 - INFO - Closing TA partition
28/021/2017 21:21:55 - INFO - Processing partition.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:55 - INFO - Opening TA partition 2
28/021/2017 21:21:55 - INFO - Processing cmnlib_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:55 - INFO - Processing emmc_appsboot_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLA TFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:55 - INFO - Processing hyp_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:55 - INFO - Processing keymaster_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFOR M-LOIRE-COM-LIVE-HWID009B00E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:56 - INFO - Processing rpm_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:56 - INFO - Checking header
28/021/2017 21:21:56 - INFO - Flashing data
28/021/2017 21:21:56 - INFO - Processing s1sbl_S1_Boot_MSM8956_LA1_0_1_73_AID_4_S1-BOOT-LIVE-D553-0004-ELF_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:56 - INFO - Checking header
28/021/2017 21:21:56 - INFO - Flashing data
28/021/2017 21:21:57 - INFO - Processing sbl1_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:57 - INFO - Checking header
28/021/2017 21:21:57 - INFO - Flashing data
28/021/2017 21:21:57 - INFO - Closing TA partition
28/021/2017 21:21:57 - INFO - Opening TA partition 2
28/021/2017 21:21:57 - INFO - Writing TA unit 0000084F. Value : 1A CE 33 00 01 00 08 03 00 02 04 02 05 00 02 02 80 00 10 05 00 01 02 71 00 00 05 00 04 82 82 00 10 02 00 04 85 05 00 03 02 82 00 10 05 00 05 82 71 00 00 02 00 05 85 12 00 02 00 A9 09 BE BA A9 09 00 00 B3 08 BE BA B3 08 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01 03 00 09 00 01
28/021/2017 21:21:57 - INFO - Writing TA unit 000008FD. Value : 00
28/021/2017 21:21:57 - INFO - Closing TA partition
28/021/2017 21:21:57 - INFO - Opening TA partition 2
28/021/2017 21:21:57 - INFO - Processing tzs1attest_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFO RM-LOIRE-COM-LIVE-HWID009B00E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:57 - INFO - Checking header
28/021/2017 21:21:57 - INFO - Flashing data
28/021/2017 21:21:57 - INFO - Processing tz_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:57 - INFO - Checking header
28/021/2017 21:21:57 - INFO - Flashing data
28/021/2017 21:21:58 - INFO - Processing tzs1sbl_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:58 - INFO - Checking header
28/021/2017 21:21:58 - INFO - Flashing data
28/021/2017 21:21:58 - INFO - Closing TA partition
28/021/2017 21:21:58 - INFO - Opening TA partition 2
28/021/2017 21:21:58 - INFO - Processing apps_log.sin
28/021/2017 21:21:58 - INFO - Checking header
28/021/2017 21:21:58 - INFO - Flashing data
28/022/2017 21:22:00 - INFO - Processing diag.sin
28/022/2017 21:22:00 - INFO - Checking header
28/022/2017 21:22:00 - INFO - Flashing data
28/022/2017 21:22:00 - WARN - ssd is excluded from bundle
28/022/2017 21:22:00 - INFO - Processing adspso.sin
28/022/2017 21:22:00 - INFO - Checking header
28/022/2017 21:22:00 - INFO - Flashing data
28/022/2017 21:22:01 - INFO - Processing cache.sin
28/022/2017 21:22:01 - INFO - Checking header
28/022/2017 21:22:01 - INFO - Flashing data
28/022/2017 21:22:01 - INFO - Processing modem.sin
28/022/2017 21:22:01 - INFO - Checking header
28/022/2017 21:22:01 - INFO - Flashing data
28/022/2017 21:22:04 - INFO - Processing Qnovo.sin
28/022/2017 21:22:04 - INFO - Checking header
28/022/2017 21:22:04 - INFO - Flashing data
28/022/2017 21:22:05 - INFO - Processing amss_fs_1.sin
28/022/2017 21:22:05 - INFO - Checking header
28/022/2017 21:22:05 - INFO - Flashing data
28/022/2017 21:22:06 - INFO - Processing amss_fs_2.sin
28/022/2017 21:22:06 - INFO - Checking header
28/022/2017 21:22:06 - INFO - Flashing data
28/022/2017 21:22:06 - INFO - Processing amss_fsg.sin
28/022/2017 21:22:06 - INFO - Checking header
28/022/2017 21:22:06 - INFO - Flashing data
28/022/2017 21:22:06 - INFO - Processing persist.sin
28/022/2017 21:22:06 - INFO - Checking header
28/022/2017 21:22:06 - INFO - Flashing data
28/022/2017 21:22:06 - INFO - Processing kernel.sin
28/022/2017 21:22:06 - INFO - Checking header
28/022/2017 21:22:06 - INFO - Flashing data
28/022/2017 21:22:09 - INFO - Processing fotakernel.sin
28/022/2017 21:22:09 - INFO - Checking header
28/022/2017 21:22:09 - INFO - Flashing data
28/022/2017 21:22:25 - INFO - Processing ramdump.sin
28/022/2017 21:22:25 - INFO - Checking header
28/022/2017 21:22:25 - INFO - Flashing data
28/022/2017 21:22:27 - INFO - Processing system.sin
28/022/2017 21:22:27 - INFO - Checking header
28/022/2017 21:22:27 - INFO - Flashing data
28/026/2017 21:26:04 - INFO - Closing TA partition
28/026/2017 21:26:04 - INFO - Opening TA partition 2
28/026/2017 21:26:04 - INFO - Processing oem.sin
28/026/2017 21:26:04 - INFO - Checking header
28/026/2017 21:26:04 - INFO - Flashing data
28/026/2017 21:26:09 - WARN - userdata is excluded from bundle
28/026/2017 21:26:09 - INFO - Closing TA partition
28/026/2017 21:26:09 - INFO - Opening TA partition 2
28/026/2017 21:26:09 - INFO - Writing TA unit 000008A4. Value : 00 00 00 00 00 00 00 00 00 00 00 00 00 00
28/026/2017 21:26:09 - INFO - Closing TA partition
28/026/2017 21:26:10 - INFO - Opening TA partition 2
28/026/2017 21:26:10 - INFO - Writing TA unit 00000964. Value : 00
28/026/2017 21:26:10 - INFO - Closing TA partition
28/026/2017 21:26:10 - INFO - Opening TA partition 2
28/026/2017 21:26:10 - INFO - Writing TA unit 00000907. Value : 00
28/026/2017 21:26:10 - INFO - Closing TA partition
28/026/2017 21:26:10 - INFO - Opening TA partition 2
28/026/2017 21:26:10 - INFO - Writing TA unit 0000091A. Value : 00
28/026/2017 21:26:10 - INFO - Closing TA partition
28/026/2017 21:26:10 - INFO - Opening TA partition 2
28/026/2017 21:26:10 - INFO - Writing TA unit 000009F6. Value : 01
28/026/2017 21:26:10 - INFO - Closing TA partition
28/026/2017 21:26:11 - INFO - Opening TA partition 2
28/026/2017 21:26:11 - INFO - Writing TA unit 000009F9. Value : 76 69 72 67 69 6E 2C 6E 6F 74 69 6D 65 73 74 61 6D 70 00
28/026/2017 21:26:11 - INFO - Closing TA partition
28/026/2017 21:26:11 - INFO - Opening TA partition 2
28/026/2017 21:26:11 - INFO - Processing elabel.sin
28/026/2017 21:26:11 - INFO - Checking header
28/026/2017 21:26:11 - INFO - Flashing data
28/026/2017 21:26:12 - INFO - Closing TA partition
28/026/2017 21:26:12 - INFO - Opening TA partition 2
28/026/2017 21:26:12 - INFO - Writing TA unit 00002725. Value : 32 30 31 37 2D 30 39 2D 32 38 20 32 31 3A 32 36 3A 31 32 00
28/026/2017 21:26:12 - INFO - Writing TA unit 00002774. Value : 00
28/026/2017 21:26:12 - INFO - Closing TA partition
28/026/2017 21:26:12 - INFO - Ending flash session
28/026/2017 21:26:12 - INFO - Flashing finished.
28/026/2017 21:26:12 - INFO - Please unplug and start your phone
28/026/2017 21:26:12 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings

[mousse04]

Sure, here's the logs when I flashed Mousse04's image:


28/021/2017 21:21:03 - INFO - Device connected in flash mode
28/021/2017 21:21:23 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 4.0.A.2.301_R8A. Customization : Customized TW
28/021/2017 21:21:23 - INFO - Preparing files for flashing
28/021/2017 21:21:48 - INFO - Please connect your device into flashmode.
28/021/2017 21:21:49 - INFO - Opening device for R/W
28/021/2017 21:21:49 - INFO - Device ready for R/W.
28/021/2017 21:21:49 - INFO - Reading device information
28/021/2017 21:21:49 - INFO - Phone ready for flashmode operations.
28/021/2017 21:21:49 - INFO - Opening TA partition 2
28/021/2017 21:21:49 - INFO - Current device : F5121 - CB512EFM5U - 1302-4771_R8A - 1300-4911_34.0.A.2.301 - GENERIC_34.0.A.2.301
28/021/2017 21:21:49 - INFO - Closing TA partition
28/021/2017 21:21:49 - INFO - Start Flashing
28/021/2017 21:21:49 - INFO - No loader in the bundle. Searching for one
28/021/2017 21:21:49 - INFO - No matching loader found
28/021/2017 21:21:49 - WARN - No loader found or set manually. Skipping loader
28/021/2017 21:21:49 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Bootloader status : ROOTABLE
28/021/2017 21:21:49 - INFO - Max packet size set to 4M
28/021/2017 21:21:49 - INFO - USB buffer size set to 512K
28/021/2017 21:21:50 - INFO - Parsing boot delivery
28/021/2017 21:21:52 - INFO - Found a template session. Using it : /home/arto/.flashTool/firmwares/prepared/F5121_4.0.A.2.301.fsc
28/021/2017 21:21:52 - INFO - Set loader configuration : [00 01 00 00 00 0C]
28/021/2017 21:21:52 - INFO - Opening TA partition 2
28/021/2017 21:21:52 - INFO - Writing TA unit 00002774. Value : 01
28/021/2017 21:21:52 - INFO - Closing TA partition
28/021/2017 21:21:55 - INFO - Processing partition.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:55 - INFO - Opening TA partition 2
28/021/2017 21:21:55 - INFO - Processing cmnlib_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:55 - INFO - Processing emmc_appsboot_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLA TFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:55 - INFO - Processing hyp_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:55 - INFO - Processing keymaster_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFOR M-LOIRE-COM-LIVE-HWID009B00E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:55 - INFO - Checking header
28/021/2017 21:21:55 - INFO - Flashing data
28/021/2017 21:21:56 - INFO - Processing rpm_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:56 - INFO - Checking header
28/021/2017 21:21:56 - INFO - Flashing data
28/021/2017 21:21:56 - INFO - Processing s1sbl_S1_Boot_MSM8956_LA1_0_1_73_AID_4_S1-BOOT-LIVE-D553-0004-ELF_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:56 - INFO - Checking header
28/021/2017 21:21:56 - INFO - Flashing data
28/021/2017 21:21:57 - INFO - Processing sbl1_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:57 - INFO - Checking header
28/021/2017 21:21:57 - INFO - Flashing data
28/021/2017 21:21:57 - INFO - Closing TA partition
28/021/2017 21:21:57 - INFO - Opening TA partition 2
28/021/2017 21:21:57 - INFO - Writing TA unit 0000084F. Value : 1A CE 33 00 01 00 08 03 00 02 04 02 05 00 02 02 80 00 10 05 00 01 02 71 00 00 05 00 04 82 82 00 10 02 00 04 85 05 00 03 02 82 00 10 05 00 05 82 71 00 00 02 00 05 85 12 00 02 00 A9 09 BE BA A9 09 00 00 B3 08 BE BA B3 08 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01 03 00 09 00 01
28/021/2017 21:21:57 - INFO - Writing TA unit 000008FD. Value : 00
28/021/2017 21:21:57 - INFO - Closing TA partition
28/021/2017 21:21:57 - INFO - Opening TA partition 2
28/021/2017 21:21:57 - INFO - Processing tzs1attest_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFO RM-LOIRE-COM-LIVE-HWID009B00E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:57 - INFO - Checking header
28/021/2017 21:21:57 - INFO - Flashing data
28/021/2017 21:21:57 - INFO - Processing tz_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:57 - INFO - Checking header
28/021/2017 21:21:57 - INFO - Flashing data
28/021/2017 21:21:58 - INFO - Processing tzs1sbl_S1_Boot_MSM8956_LA1_0_1_73_AID_4_PLATFORM-LOIRE-COM-LIVE-HWID009B00E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-D553-0004-MMC.sin
28/021/2017 21:21:58 - INFO - Checking header
28/021/2017 21:21:58 - INFO - Flashing data
28/021/2017 21:21:58 - INFO - Closing TA partition
28/021/2017 21:21:58 - INFO - Opening TA partition 2
28/021/2017 21:21:58 - INFO - Processing apps_log.sin
28/021/2017 21:21:58 - INFO - Checking header
28/021/2017 21:21:58 - INFO - Flashing data
28/022/2017 21:22:00 - INFO - Processing diag.sin
28/022/2017 21:22:00 - INFO - Checking header
28/022/2017 21:22:00 - INFO - Flashing data
28/022/2017 21:22:00 - WARN - ssd is excluded from bundle
28/022/2017 21:22:00 - INFO - Processing adspso.sin
28/022/2017 21:22:00 - INFO - Checking header
28/022/2017 21:22:00 - INFO - Flashing data
28/022/2017 21:22:01 - INFO - Processing cache.sin
28/022/2017 21:22:01 - INFO - Checking header
28/022/2017 21:22:01 - INFO - Flashing data
28/022/2017 21:22:01 - INFO - Processing modem.sin
28/022/2017 21:22:01 - INFO - Checking header
28/022/2017 21:22:01 - INFO - Flashing data
28/022/2017 21:22:04 - INFO - Processing Qnovo.sin
28/022/2017 21:22:04 - INFO - Checking header
28/022/2017 21:22:04 - INFO - Flashing data
28/022/2017 21:22:05 - INFO - Processing amss_fs_1.sin
28/022/2017 21:22:05 - INFO - Checking header
28/022/2017 21:22:05 - INFO - Flashing data
28/022/2017 21:22:06 - INFO - Processing amss_fs_2.sin
28/022/2017 21:22:06 - INFO - Checking header
28/022/2017 21:22:06 - INFO - Flashing data
28/022/2017 21:22:06 - INFO - Processing amss_fsg.sin
28/022/2017 21:22:06 - INFO - Checking header
28/022/2017 21:22:06 - INFO - Flashing data
28/022/2017 21:22:06 - INFO - Processing persist.sin
28/022/2017 21:22:06 - INFO - Checking header
28/022/2017 21:22:06 - INFO - Flashing data
28/022/2017 21:22:06 - INFO - Processing kernel.sin
28/022/2017 21:22:06 - INFO - Checking header
28/022/2017 21:22:06 - INFO - Flashing data
28/022/2017 21:22:09 - INFO - Processing fotakernel.sin
28/022/2017 21:22:09 - INFO - Checking header
28/022/2017 21:22:09 - INFO - Flashing data
28/022/2017 21:22:25 - INFO - Processing ramdump.sin
28/022/2017 21:22:25 - INFO - Checking header
28/022/2017 21:22:25 - INFO - Flashing data
28/022/2017 21:22:27 - INFO - Processing system.sin
28/022/2017 21:22:27 - INFO - Checking header
28/022/2017 21:22:27 - INFO - Flashing data
28/026/2017 21:26:04 - INFO - Closing TA partition
28/026/2017 21:26:04 - INFO - Opening TA partition 2
28/026/2017 21:26:04 - INFO - Processing oem.sin
28/026/2017 21:26:04 - INFO - Checking header
28/026/2017 21:26:04 - INFO - Flashing data
28/026/2017 21:26:09 - WARN - userdata is excluded from bundle
28/026/2017 21:26:09 - INFO - Closing TA partition
28/026/2017 21:26:09 - INFO - Opening TA partition 2
28/026/2017 21:26:09 - INFO - Writing TA unit 000008A4. Value : 00 00 00 00 00 00 00 00 00 00 00 00 00 00
28/026/2017 21:26:09 - INFO - Closing TA partition
28/026/2017 21:26:10 - INFO - Opening TA partition 2
28/026/2017 21:26:10 - INFO - Writing TA unit 00000964. Value : 00
28/026/2017 21:26:10 - INFO - Closing TA partition
28/026/2017 21:26:10 - INFO - Opening TA partition 2
28/026/2017 21:26:10 - INFO - Writing TA unit 00000907. Value : 00
28/026/2017 21:26:10 - INFO - Closing TA partition
28/026/2017 21:26:10 - INFO - Opening TA partition 2
28/026/2017 21:26:10 - INFO - Writing TA unit 0000091A. Value : 00
28/026/2017 21:26:10 - INFO - Closing TA partition
28/026/2017 21:26:10 - INFO - Opening TA partition 2
28/026/2017 21:26:10 - INFO - Writing TA unit 000009F6. Value : 01
28/026/2017 21:26:10 - INFO - Closing TA partition
28/026/2017 21:26:11 - INFO - Opening TA partition 2
28/026/2017 21:26:11 - INFO - Writing TA unit 000009F9. Value : 76 69 72 67 69 6E 2C 6E 6F 74 69 6D 65 73 74 61 6D 70 00
28/026/2017 21:26:11 - INFO - Closing TA partition
28/026/2017 21:26:11 - INFO - Opening TA partition 2
28/026/2017 21:26:11 - INFO - Processing elabel.sin
28/026/2017 21:26:11 - INFO - Checking header
28/026/2017 21:26:11 - INFO - Flashing data
28/026/2017 21:26:12 - INFO - Closing TA partition
28/026/2017 21:26:12 - INFO - Opening TA partition 2
28/026/2017 21:26:12 - INFO - Writing TA unit 00002725. Value : 32 30 31 37 2D 30 39 2D 32 38 20 32 31 3A 32 36 3A 31 32 00
28/026/2017 21:26:12 - INFO - Writing TA unit 00002774. Value : 00
28/026/2017 21:26:12 - INFO - Closing TA partition
28/026/2017 21:26:12 - INFO - Ending flash session
28/026/2017 21:26:12 - INFO - Flashing finished.
28/026/2017 21:26:12 - INFO - Please unplug and start your phone
28/026/2017 21:26:12 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings


strange, it looks to work fine ...

And at the end, your device is still with Nougat? Why are you saying it doesn't work ?

[ajalkane]

strange, it looks to work fine ...

And at the end, your device is still with Nougat? Why are you saying it doesn't work ?

No, I'm pretty sure it's with MM. It's just that it boots, gives a distorted Xperia image after about 10 seconds, and reboots again. Bootlooping forever.

[mousse04]

No, I'm pretty sure it's with MM. It's just that it boots, gives a distorted Xperia image after about 10 seconds, and reboots again. Bootlooping forever.

ok and is it the good xperia X version?

[ajalkane]

ok and is it the good xperia X version?

This is bog standard Xperia X. On the box it says F5121 Graphite Black, SI 1302-9422 Rev 4.

[ajalkane]

I just did the flashing in Windows with Mousse04 image and apparently the result is a working phone. Too bad the phone speaks now chinese or something like that which makes using it a bit problematic :D.

However, this points to my linux setup being the culprit. I'm using Ubuntu 16.04 with adb and fastboot installed from the official repositories. Maybe they're outdated and are the reason for the failure?

[Heik]

No, I'm pretty sure it's with MM. It's just that it boots, gives a distorted Xperia image after about 10 seconds, and reboots again. Bootlooping forever.

That was exactly what my Xperia X did after flashing, if USERDATA was not wiped.

[ajalkane]

That was exactly what my Xperia X did after flashing, if USERDATA was not wiped.

I did click all wipe options.

[nieldk]

I did click all wipe options.

I don't think you should wipe all,
Just wipe user data.
By wiping all, I think you delete data that SFOS Needs (drivers that it depends on from Android, like WiFi and more)

Flashing went well from your log output.

[ajalkane]

I don't think you should wipe all,
Just wipe user data.
By wiping all, I think you delete data that SFOS Needs (drivers that it depends on from Android, like WiFi and more)


But wouldn't flashing the new Android image anyway install all those drivers?

[mousse04]

I just did the flashing in Windows with Mousse04 image and apparently the result is a working phone. Too bad the phone speaks now chinese or something like that which makes using it a bit problematic :D.

However, this points to my linux setup being the culprit. I'm using Ubuntu 16.04 with adb and fastboot installed from the official repositories. Maybe they're outdated and are the reason for the failure?

strange. Mine got all languages

[mousse04]

I don't think you should wipe all,
Just wipe user data.
By wiping all, I think you delete data that SFOS Needs (drivers that it depends on from Android, like WiFi and more)

Flashing went well from your log output.

Good point. I also wiped only userdata.

I would say rather that : as the .fsc script is not perfectly up to date, ar aligned with the image, maybe by wiping everything, you wiped something which is not flashed by the script ....

[ajalkane]

I finally managed to accidentally click on some chinese scribbling that presented me with language selection. So I'm now able to use the phone and hopefully try to recover the DRM keys.

Thank you all for the help! For now it remains a mystery to me why I couldn't flash successfully with linux, but that it was at the end a success is most important. And a word of encouragement to others with my predicatement, it was much less a laborous process to do it under Windows than I was afraid of. Unlike many guides said, I did not have to install any drivers etc. Just download FlashTool and feed the image to it.

[mousse04]

I finally managed to accidentally click on some chinese scribbling that presented me with language selection. So I'm now able to use the phone and hopefully try to recover the DRM keys.

Thank you all for the help! For now it remains a mystery to me why I couldn't flash successfully with linux, but that it was at the end a success is most important. And a word of encouragement to others with my predicatement, it was much less a laborous process to do it under Windows than I was afraid of. Unlike many guides said, I did not have to install any drivers etc. Just download FlashTool and feed the image to it.

got the same problem ... but was luckier ;)

Edit: Anyway, good news. Now, let's help @juiceme :)

[ajalkane]

Edit: Anyway, good news. Now, let's help @juiceme :)

My advice to juiceme: if you have troubles with this inside linux, then despite the mental horror, boot into Windows or loan a friend's Windows machine for fifteen minutes. I spent several evenings trying these tools within Linux. Once I swallowed my pride, it was only a matter of 15 minutes until I had successfully downgraded the phone.

At least under Windows 10 I didn't have to download any drivers, just have Mousse04 image on USB stick and download Flashtool. Easy peasy. The DRM backup software seemed to work well within linux after flashing MM.

[mousse04]

My advice to juiceme: if you have troubles with this inside linux, then despite the mental horror, boot into Windows or loan a friend's Windows machine for fifteen minutes. I spent several evenings trying these tools within Linux. Once I swallowed my pride, it was only a matter of 15 minutes until I had successfully downgraded the phone.

At least under Windows 10 I didn't have to download any drivers, just have Mousse04 image on USB stick and download Flashtool. Easy peasy. The DRM backup software seemed to work well within linux after flashing MM.

Yes the DRM and SailfishOS stuffs are easy after this fu... downgrade :)

[richie]

Hi

If you used flashtool, where did you get it from?

I tried downloading from http://www.flashtool.net/downloads.php

and the md5sum doesn't match for either the Linux or Windows versions, e.g.

Windows md5 sum on website is E06829037E0F1291BC53E45B012D6FDF

but on the file downloaded it is
ceab49b14bf84eacf8ce0202e2498b5e flashtool-0.9.23.1-windows.exe

Linux md5 sum on website is
3C70AF72F9B9E45C195F9192409E0C0F

but on the file downloaded it is
a68d331f710b78f7eaf4350e70d3e693 flashtool-0.9.23.1-linux.tar.7z

md5sum's on 0.9.23.1 before patch 0.9.23.2

Has anyone got a version with the matching md5 sum?

Rich

[jenix]

bummer. So I received my Xperia X F5121 from Amazon today and of course wanted to flash the community image right away. I did the TA backup and wanted to unlock the bootloader. As described in the guide, I went to check the status in the service menu and there it says under "Confguration": "Bootloader unlock allowed: No". The way I understand it, it's not possible to unlock the bootloader and flash SFOS, right?
This really puzzles me, since it is a full priced retail version. Is there a possibility to unlock the bootloader that I'm missing (like flashing another ROM first) or do I have to return the phone?

[ljo]

bummer. So I received my Xperia X F5121 from Amazon today and of course wanted to flash the community image right away.
I did not care about any DRM stuff.
But I found it being a real lockin procedure since it was impossible to unlock the bootloader unless I
* actually started the phone (not only vol-up start),
* set up the android,
* enabled developer mode by clicking 7-8 times on the build item in the about/system in settings section, and
* then checked the then appeared "allow bootloader unlock" as the last step.

Not sure if it will help you or fit your situation, but to me this was a completely wasteful step of an hour or so. They claim it is for protecting active installations that you cannot allow direct flash of phones in use, but it was no active installation (and never used before) since I had to actually set it up and avoid installing and configuring phone-home features etc ... I only wanted to unlock and flash.
The good part of it was that it took two minutes flat to flash the image until booting SailfishOS after the bootloader unlock (which took only a fraction of a second). :)

Cheers,

[lantern]

bummer. So I received my Xperia X F5121 from Amazon today and of course wanted to flash the community image right away. I did the TA backup and wanted to unlock the bootloader. As described in the guide, I went to check the status in the service menu and there it says under "Confguration": "Bootloader unlock allowed: No".
That is not a usual retail version, for sure. Return it :(

[jenix]

I did not care about any DRM stuff.
But I found it being a real lockin procedure since it was impossible to unlock the bootloader unless I
* actually started the phone (not only vol-up start),
* set up the android,
* enabled developer mode by clicking 7-8 times on the build item in the about/system in settings section, and
* then checked the then appeared "allow bootloader unlock" as the last step.


Thanks for your reply. That's exactly what I did as well: Started up Android, skipped through the initial Android setup, enabled Developer mode and then checked the Service menu for the bootloader unlock (which states "No" in my case).
So I guess I'll have to send it back and look for another source.

[ljo]

Not sure about service menu. Sounds like you did not do the last step. I am pretty sure the allow bootloader unlock option was in the settings section. I swithed it from no to yes and then shut down the phone.

[jenix]

That is not a usual retail version, for sure. Return it :(

Sure seems like it. It also has a strange model number on the box. Most shops list the black Xperia X F5121 as Model 1302-9401 or 1302-8005, mine is "1302-5472 Rev 3".
Maybe we should start a list which model number can be unlocked and which one can't?

[lantern]

No need. You just got an operator model. Maybe it was "refurbished" by some dishonest seller.

[mariusmssj]

Got my Xperia X (F5122 dual sim) and found out it's running 7.1.1 :( tried looking for a marshmallow firmware for it but couldn't find anything :(

What are the DRM keys for? It is purely for warranty and being able to restore phone to it's previous android state?

[jakibaki]

Got my Xperia X (F5122 dual sim) and found out it's running 7.1.1 :( tried looking for a marshmallow firmware for it but couldn't find anything :(

What are the DRM keys for? It is purely for warranty and being able to restore phone to it's previous android state?

Flashing the F5121 firmware could work (at least with custom roms it only has no dual-sim support so it could be enough to backup the keys).

The drm-keys unlock some functionality on android but won't be needed at all on Sailfish OS or custom android roms (there are drm-fixed-kernels available for custom roms which restore those features).

In many places (eu afaik so you'll be fine until brexit is done :p) they aren't even needed to "restore" warranty since wiping the warranty by unlocking your bootloader is not allowed there.

So unless you're going to sell the phone or you plan on ever running stock rom on it again you don't need to backup your drm-keys (can't hurt though).

[mariusmssj]

Thanks jakibaki, I have no intention of using android or going back to it. I thought that Jolla might need the DRM keys to access some of the hardware stuff (Camera, audio DAC, etc...)

As you helped me in the other thread getting F5121 marshmallow firmware is not an issue but F5122 seems to be a right pain and I don't think I need go through it.

I guess we will know more next Wednesday. Once again thanks for helping :)

[Peccelius]

Hi folks,

so in order to install Sailfish X do I need to unlock bootloader using Sony's instructions (and install android sdk and other stuff)? Or does Jolla provide some tool for this on wednesday or can I unlock bootloader using Emma?

[mariusmssj]

Hi folks,

so in order to install Sailfish X do I need to unlock bootloader using Sony's instructions (and install android sdk and other stuff)? Or does Jolla provide some tool for this on wednesday or can I unlock bootloader using Emma?

From what I understood EMMA can't flash anything with a locked bootloader. So you will to first unlock it before using EMMA.

I haven't unlocked my bootloader yet but with doing some reading you don't need the whole SDK to unlock it. But I will wait to see Jolla's instructions first before doing anything.

Also if you have a windows PC sony has a video on how to unlock the bootloader: >>Video Here<< (https://www.youtube.com/watch?v=jWPYicb8_-Q)

[KylliOrvokki]

In this case, it is fine.
Here it is :
https://drive.google.com/open?id=0B6TlqqSsp53DaHE1Y0VkY0JEVlE
Let me know how it will work.

I am following helpers:
http://www.xperiablog.net/2016/03/12/install-xperia-marshmallow-using-flashtool-and-xperifirm-guide/
http://sailfishmods.de/2017/07/howto-sony-xperia-x-teil-1-cda-drm-keys-bootloader/

My XperiFirm -Create your FTF firmware [1302-3140] file is always failing at the end of the download with unpacking failing. I am using Mac.

@mousse04
Should your FTF version work with phone "Region: Nordic (Generic) [1302-3140]"?

[einmaleins]

My XperiFirm -Create your FTF firmware [1302-3140] file is always failing at the end of the download with unpacking failing. I am using Mac.


I had that on Linux after one successful try. I tried deleting the directory created by flashtool (something like /root/.flashtool). Next try was successful. So maybe this might help in your case as well.

[KylliOrvokki]

Aaand - boot loop with Mousse04's file above.

Edit.

But now managed to get working with Mousse04's ftf. I totally missed step "Right at Wipe , we select everything from APPS_LOG, DIAG, SSD, USERDATA"
After this I boot loops gone.

Thanks for the file!! :)

Now I can continue to DRM stuff...

[aspergerguy]

Please note that as of today you need to update Xperifirm:
https://forum.xda-developers.com/crossdevice-dev/sony/pc-xperifirm-xperia-firmware-downloader-t2834142

Have to manually amend Androxyde's Flashtool to account for this change as no longer connects to server by replacing Xperifirm.exe in Users > Name > .flashTool with version dated 16/10/2017 to restore XF icon function.

[rob_kouw]

Back in August, I struggled with this subject using a Windows 10 pc.

I ended up using flashtool-0.9.23.1-windows.exe to get the necessary drivers onto my pc. That worked well, but today Norton Security claimed there is some malware hidden in the tool, within the file flashtool-drivers.exe. So it deleted this file.
The name of the malware: Heur.AdvML.B

To whom it may concern...

[nieldk]

Back in August, I struggled with this subject using a Windows 10 pc.

I ended up using flashtool-0.9.23.1-windows.exe to get the necessary drivers onto my pc. That worked well, but today Norton Security claimed there is some malware hidden in the tool, within the file flashtool-drivers.exe. So it deleted this file.
The name of the malware: Heur.AdvML.B

To whom it may concern...

Yes. I noticed this aswell :)
But, consider this. Flastool contains exploits for many things. For Example rooting the device.
Sure, its “malware”, but its intentional ;)

Just remember to get it from the (more or less) official sources !