Page 142 of 309 « First 132140141 142 143144152 Last »
Reply
Thread Tools
juiceme is offline juiceme
2017-10-07 , 13:12
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#1411
Originally Posted by r0kk3rz View Post
We've had a successful flash, so if you want to remain windows free during the install of Sailfish X make sure you update via OTA to 34.3.A.0.228 (check Settings | About phone | Build number) before unlocking your bootloader.

Once you do that, Sailfish X will flash just fine.
I have not unlocked the bootloader yet, so I might also try that.
However, do I need an Android account or whatever to receive OTA updates?
 

The Following 4 Users Say Thank You to juiceme For This Useful Post:
mosen's Avatar
mosen is offline mosen
2017-10-07 , 16:19
Community Council | Posts: 1,669 | Thanked: 10,225 times | Joined on Nov 2014 @ Lower Rhine
#1412
Originally Posted by juiceme View Post
I have not unlocked the bootloader yet, so I might also try that.
However, do I need an Android account or whatever to receive OTA updates?
EDIT: As corrected by jakibaki, below link is no flashable image.
sorry for misleading, i should have invested more time.

Original wrong suggestion:
No need for OTA as you should be able to DL this image of 34.3.A.0.228 from sony open source archvie and flash.
Right?
__________________
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
Last edited by mosen; 2017-10-08 at 01:31.
 

The Following 4 Users Say Thank You to mosen For This Useful Post:
jakibaki is offline jakibaki
2017-10-07 , 16:53
Posts: 120 | Thanked: 843 times | Joined on Jul 2015 @ Berlin, Germany
#1413
Originally Posted by mosen View Post
No need for OTA as you should be able to DL this image of 34.3.A.0.228 from sony open source archvie and flash.
Right?
The download you linked is just the source code of the open-source-stuff of that update afaik. At the very least it's not a flashable image.

That has nothing to do with the bootloader-update that the ota/emma/flashtool applies.

The ota is just an additional way of getting the update that's needed to flash sailfish x. The official way is to use emma but unofficially updating via ota or the open source flashtool works too.
 

The Following 8 Users Say Thank You to jakibaki For This Useful Post:
explit's Avatar
explit is offline explit
2017-10-07 , 20:15
Posts: 592 | Thanked: 1,603 times | Joined on Apr 2010 @ Berlin / Germany
#1414
Originally Posted by jakibaki View Post
I didn't have to update any script, the community-build I flashed doesn't even require the blob-partition yet (that requirement will only come in the next build). I just confirmed that the blob-partition is now properly writable from fastboot mode.

I don't think the sailfish-x build will ship with the flash.sh but simply using this one which is in the same folder as the flash.bat in the repo should most likely work with no/only minor modification
Hi Jakibaki.

Can you explain me, if i need to flash the new community-image or i still can use the old one from 1.10.2017 (with replaced flash.sh) ?

Thanks
 

The Following 3 Users Say Thank You to explit For This Useful Post:
mousse04 is offline mousse04
2017-10-07 , 20:21
Posts: 443 | Thanked: 282 times | Joined on Oct 2011 @ Grenoble, France
#1415
Originally Posted by explit View Post
Hi Jakibaki.

Can you explain me, if i need to flash the new community-image or i still can use the old one from 1.10.2017 (with replaced flash.sh) ?

Thanks
What is thos "new community-image" are you talking about ?
 

The Following 2 Users Say Thank You to mousse04 For This Useful Post:
jakibaki is offline jakibaki
2017-10-07 , 20:34
Posts: 120 | Thanked: 843 times | Joined on Jul 2015 @ Berlin, Germany
#1416
Originally Posted by explit View Post
Hi Jakibaki.

Can you explain me, if i need to flash the new community-image or i still can use the old one from 1.10.2017 (with replaced flash.sh) ?

Thanks
You don't need to do anything different from the instructions of whatever community-build you want to use after updating, the update only unlocks the oem partition, it doesn't force you to use it. The flash.sh is specific for the build you want to use and changing it to write the blobs to the oem-partition would only break the community-build because it still expects them to be in the old position.

The only place where you'll have to replace a script is the official release because that one will (most likely) only ship with the windows-script.
 

The Following 4 Users Say Thank You to jakibaki For This Useful Post:
asa is offline asa
2017-10-08 , 10:00
Posts: 55 | Thanked: 34 times | Joined on Jun 2014
#1417
Originally Posted by jakibaki View Post
Downgrading is no problem at all

Assuming that you want to downgrade to back up your drm-keys this guide is the way to go.

EDIT: The poster of that guide has terrible google-fu. A marshmallow ftf can be found here (source)
EDIT2: Much faster mirror
I'm clearly no expert here so what I'm doing wrong:

08/039/2017 12:39:09 - INFO - Flashtool Version 0.9.23.1 built on 11-01-2017 15:12:00
08/039/2017 12:39:09 - INFO - Executing search strategies to find proxy selector
08/039/2017 12:39:10 - INFO - No proxy found for IE. Trying next one
08/039/2017 12:39:10 - INFO - Strategy firefox failed trying next one : No Firefox installation found
08/039/2017 12:39:10 - INFO - No proxy found for java. Trying next one
08/039/2017 12:39:10 - INFO - Syncing devices from github
08/039/2017 12:39:10 - INFO - Opening devices repository.
08/039/2017 12:39:10 - INFO - Scanning devices folder for changes.
08/039/2017 12:39:19 - INFO - Pulling changes from github.
08/039/2017 12:39:20 - INFO - Quietly closing devices repository.
08/039/2017 12:39:20 - INFO - Devices sync finished.
08/039/2017 12:39:20 - INFO - Loading devices database
08/039/2017 12:39:20 - INFO - Loaded 98 devices
08/039/2017 12:39:20 - INFO - Starting phone detection
08/039/2017 12:39:25 - INFO - Device disconnected
08/040/2017 12:40:02 - INFO - Device connected with USB debugging on
08/040/2017 12:40:03 - INFO - Connected device : Sony Xperia X
08/040/2017 12:40:03 - INFO - Installed version of busybox : N/A
08/040/2017 12:40:03 - INFO - Android version : 7.1.1 / kernel version : 3.10.84-perf-gcb77bab-03149-gfe8d4a8 / Platform : 64bits / Build number : 34.3.A.0.217
08/040/2017 12:40:03 - INFO - Root access denied
08/040/2017 12:40:16 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 34.0.A.2.301. Customization : NCB
08/040/2017 12:40:16 - INFO - Preparing files for flashing
08/041/2017 12:41:25 - INFO - Please connect your device into flashmode.
08/041/2017 12:41:58 - INFO - Device disconnected
08/042/2017 12:42:19 - INFO - Device connected in flash mode
08/042/2017 12:42:20 - INFO - Opening device for R/W
08/042/2017 12:42:20 - INFO - Reading device information
08/042/2017 12:42:20 - INFO - Unable to read from phone after having opened it.
08/042/2017 12:42:20 - INFO - trying to continue anyway
08/042/2017 12:42:20 - INFO - Phone ready for flashmode operations.
08/042/2017 12:42:20 - INFO - Opening TA partition 2
08/042/2017 12:42:20 - INFO - Start Flashing
08/042/2017 12:42:20 - INFO - No loader in the bundle. Searching for one
08/042/2017 12:42:34 - INFO - No matching loader found
08/042/2017 12:42:34 - WARN - No loader found or set manually. Skipping loader
08/042/2017 12:42:34 - INFO - Ending flash session
08/042/2017 12:42:34 - ERROR - null
08/042/2017 12:42:34 - ERROR - Error flashing. Aborted
08/042/2017 12:42:35 - INFO - Device connected in flash mode

 

The Following 4 Users Say Thank You to asa For This Useful Post:
jakibaki is offline jakibaki
2017-10-08 , 11:44
Posts: 120 | Thanked: 843 times | Joined on Jul 2015 @ Berlin, Germany
#1418
Originally Posted by asa View Post
I'm clearly no expert here so what I'm doing wrong:

08/039/2017 12:39:09 - INFO - Flashtool Version 0.9.23.1 built on 11-01-2017 15:12:00
08/039/2017 12:39:09 - INFO - Executing search strategies to find proxy selector
08/039/2017 12:39:10 - INFO - No proxy found for IE. Trying next one
08/039/2017 12:39:10 - INFO - Strategy firefox failed trying next one : No Firefox installation found
08/039/2017 12:39:10 - INFO - No proxy found for java. Trying next one
08/039/2017 12:39:10 - INFO - Syncing devices from github
08/039/2017 12:39:10 - INFO - Opening devices repository.
08/039/2017 12:39:10 - INFO - Scanning devices folder for changes.
08/039/2017 12:39:19 - INFO - Pulling changes from github.
08/039/2017 12:39:20 - INFO - Quietly closing devices repository.
08/039/2017 12:39:20 - INFO - Devices sync finished.
08/039/2017 12:39:20 - INFO - Loading devices database
08/039/2017 12:39:20 - INFO - Loaded 98 devices
08/039/2017 12:39:20 - INFO - Starting phone detection
08/039/2017 12:39:25 - INFO - Device disconnected
08/040/2017 12:40:02 - INFO - Device connected with USB debugging on
08/040/2017 12:40:03 - INFO - Connected device : Sony Xperia X
08/040/2017 12:40:03 - INFO - Installed version of busybox : N/A
08/040/2017 12:40:03 - INFO - Android version : 7.1.1 / kernel version : 3.10.84-perf-gcb77bab-03149-gfe8d4a8 / Platform : 64bits / Build number : 34.3.A.0.217
08/040/2017 12:40:03 - INFO - Root access denied
08/040/2017 12:40:16 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 34.0.A.2.301. Customization : NCB
08/040/2017 12:40:16 - INFO - Preparing files for flashing
08/041/2017 12:41:25 - INFO - Please connect your device into flashmode.
08/041/2017 12:41:58 - INFO - Device disconnected
08/042/2017 12:42:19 - INFO - Device connected in flash mode
08/042/2017 12:42:20 - INFO - Opening device for R/W
08/042/2017 12:42:20 - INFO - Reading device information
08/042/2017 12:42:20 - INFO - Unable to read from phone after having opened it.
08/042/2017 12:42:20 - INFO - trying to continue anyway
08/042/2017 12:42:20 - INFO - Phone ready for flashmode operations.
08/042/2017 12:42:20 - INFO - Opening TA partition 2
08/042/2017 12:42:20 - INFO - Start Flashing
08/042/2017 12:42:20 - INFO - No loader in the bundle. Searching for one
08/042/2017 12:42:34 - INFO - No matching loader found
08/042/2017 12:42:34 - WARN - No loader found or set manually. Skipping loader
08/042/2017 12:42:34 - INFO - Ending flash session
08/042/2017 12:42:34 - ERROR - null
08/042/2017 12:42:34 - ERROR - Error flashing. Aborted
08/042/2017 12:42:35 - INFO - Device connected in flash mode

That's weird :/

I think the ftf I linked may not be the correct one
 

The Following 3 Users Say Thank You to jakibaki For This Useful Post:
asa is offline asa
2017-10-08 , 14:26
Posts: 55 | Thanked: 34 times | Joined on Jun 2014
#1419
Originally Posted by jakibaki View Post
That's weird :/

I think the ftf I linked may not be the correct one
Alright, will try to find another .ftf-file.
 

The Following 2 Users Say Thank You to asa For This Useful Post:
jorm1s is offline jorm1s
2017-10-08 , 16:38
Posts: 1 | Thanked: 7 times | Joined on Oct 2017 @ Finland
#1420
Originally Posted by asa View Post
Alright, will try to find another .ftf-file.
After lurking here for several years I finally decided to make an account so I could reply to this. So, hi everyone!

Anyway, I had the same problem when flashing the linked .ftf, but the problem turned out to be that I had not enabled third party software on the phone (Settings → Lock screen & security → Unknown sources). Also make sure you are running the latest flashtool, 0.9.23.2.

Hope this helps you or anyone else with the same problem!
 

The Following 7 Users Say Thank You to jorm1s For This Useful Post:
Reply
Page 142 of 309 « First 132140141 142 143144152 Last »

Tags
sailfish os, sony xperia x

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 12:58.

Contact Us - Home - Archive - Top