We have moved to a new Sailfish OS Forum. Please start new discussions there.
3

[Xperia X] Android OTA Updates - Why such small increments? [answered]

asked 2017-11-11 18:12:38 +0300

jimjamz gravatar image

I've turned on my brand new and sealed Sony Xperia X F5121 today. The F5121's stock OS was on Android 6.0. As soon as I connected to Wi-Fi, a couple of large (1Gb+) updates were first installed to bring me up to 34.2.nnn (Android 7.0) but since the first couple of updates, all subsequent updates have been gradually less and less in size, now averaging around 100Mb. So far, all the installs, restarts and updates have taken about 4 hours. I've gone through about 9 or 10 updates, installs and restarts. I'm currently on 34.2.A.2.47 (Android 7.0) and I know that I need to get up to 34.3.A.0.228 before I can unlock the bootloader and then start flashing. The problem is, I have no idea how far away I am from getting to the latest update. With all the small incremental updates, there could be 10, 100 or 1000. I have no idea.

Why couldn't the updates be more smarter and be a more up-to-date, combined package? Rather than having to step through every incremental update, all the recent updates could have been slipstreamed into one current update, which simply contains the latest packages to take me straight to the latest available version. Why does it have to follow this incremental approach? Having never used Android before, I don't really know how this works or what they (Sony/Android) were thinking.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2017-11-12 01:45:10.645099

Comments

1

Why ? Simply to show to all people that were complaining about all the intermediate updates that we have to do when doing a factory reset on Sailfish that's it's far worse on Android :)

Sthocs ( 2017-11-12 02:28:17 +0300 )edit

2 Answers

Sort by » oldest newest most voted
6

answered 2017-11-11 18:30:24 +0300

Gatze gravatar image

updated 2017-11-12 22:32:02 +0300

DrYak gravatar image

I don't think Jolla can't do something about your problem. Maybe the use of the Emma tool is the solution ?


For Linux users :

  • Flashtool is a cross platform (java) tool similar to Emma, that can handle the flashing of firmware (even on unlocked bootloader).
  • XperiFirm (also included packaged inside flashtool) is a cross platform (Mono) tool to search for firmware versions (useful for finding the latest 34.3 before flashing Sailfish X, or to downgrade to 34.0 before backing up the DRM keys inside TA)
  • backupTA - optional only mentioned for completeness (and also packed with Flashtools) used to backup the DRM keys in the TA.
edit flag offensive delete publish link more

Comments

My underlying question was, "is there one single update available that can take me straight to the latest version or must i have to install every single update released, incrementally?"

Apologies if that was not clear. Answers would probably come from sailors who have had to follow the same official installation instructions with a fresh, stock Sony Xperia X on Android 6.0. I'm also a Linux user so the Emma tool is not an option.

As of writing, there have been 3 more updates to my F5121 since my original post. I'm currently on 34.2.A.2.69. This is taking forever.

jimjamz ( 2017-11-11 18:40:46 +0300 )edit

Emma tool flash to most recent Android Version is the solution only one update required.

DarkTuring ( 2017-11-11 19:36:42 +0300 )edit

Androxyde Flashtool linked with Xperifirm would also obtain latest version.

aspergerguy ( 2017-11-11 20:25:40 +0300 )edit
1

I can confirm this answer as well - Sony's Emma tool for Windows is the only fast solution. Unfortunately that's how Android works, there's nothing to do about it and Jolla can't change that. I recently set up an other brand new Android device (non-Sony one) and it also took forever until I could update to the most recent version.

molan ( 2017-11-12 01:44:42 +0300 )edit
0

answered 2017-11-11 21:35:02 +0300

jimjamz gravatar image

After many hours of incremental updates, I eventually got to 34.3.A.0.238, which is the current and latest update available. This was enough to start the unlocking of the bootloader and the subsequent flashing process.

edit flag offensive delete publish link more

Comments

Yes, it's a pain and the most annoying part of the flashing.

lispy ( 2017-11-11 21:42:41 +0300 )edit

Question tools

Follow
2 followers

Stats

Asked: 2017-11-11 18:12:38 +0300

Seen: 668 times

Last updated: Nov 12 '17