[TOOL] [UPDATE 04/09/2015] Flashtool version 0.9.19.10 - Windows / Linux / Mac

munjeni

Senior Member
Jun 2, 2011
9,019
21,774
263
Some people are noticing on the Xperia 1 II that immediately after flashing with this setup the phone shows up with 128GB of storage instead of 256GB (I did not notice this, but apparently it can be fixed with Xperia Companion repair). We also notice that the flashing process goes remarkably quickly. Would any of the FlashTool developers be able to look at these issues to see what is going on and if it is a problem?

Thanks
You need to chose right sin for Repartition:0 , e.g. partition-image-LUN0_124936192_X-FLASH-ALL-2389.sin is for 128 gb or partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin for 256 gb. If you flashed partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin and you have 128 gb instead of 256 gb its in most case sony bug.
 

brocnical

Senior Member
Oct 9, 2011
242
108
73
Ulster
You need to chose right sin for Repartition:0 , e.g. partition-image-LUN0_124936192_X-FLASH-ALL-2389.sin is for 128 gb or partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin for 256 gb. If you flashed partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin and you have 128 gb instead of 256 gb its in most case sony bug.
Yes, well the .fsc file I generated has:
Code:
Repartition:0:partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin
so it is correctly saying to use a 256 GB partition then. Then there must be a bug somewhere else.
 

munjeni

Senior Member
Jun 2, 2011
9,019
21,774
263
Yes, well the .fsc file I generated has:
Code:
Repartition:0:partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin
so it is correctly saying to use a 256 GB partition then. Then there must be a bug somewhere else.
You didn't had bug? If no than I'm believing those users who reported bug have flashed 128 version on their 256 device. One thing about 58.0.fsc , I think better idea is having two, one for 128 device and one for 256 device e.g. 58.0.256.fsc & 58.0.128.fsc , I didn't analysed flashtool and can't say if flashtool have implemented autodetection for right partition image and also can't say what will happen if somebody flash their 128 device with 256 partition0, will it brick their device?
 
Last edited:

brocnical

Senior Member
Oct 9, 2011
242
108
73
Ulster
You didn't had bug? If no than I'm believing those users who reported bug have flashed 128 version on their 256 device. One thing about 58.0.fsc , I think better idea is having two, one for 128 device and one for 256 device e.g. 58.0.256.fsc & 58.0.128.fsc , I didn't analysed flashtool and can't say if flashtool have implemented autodetection for right partition image and also can't say what will happen if somebody flash their 128 device with 256 partition0, will it brick their device?
No, I didn't have the bug, though I never checked the storage at first. My phone did crash on first boot but after hat it has been running fine without a software repair. When I checked it has the 256Gb storage as expected.

The .fsc and .properties I posted will work only for the XQ-AT51 which is 256GB storage only. Users with the other variants should create their own .fsc and .properties.
 

brocnical

Senior Member
Oct 9, 2011
242
108
73
Ulster
I note that the Torrent links for FlashTool at flashtool.net are showing only for version 0.9.26.0 instead of the latest 0.9.28.0. The links for the uploaded.to download for Linux are also broken. Please could you fix.
 

Raskaipika

Member
May 12, 2016
26
0
0
Hi mates:

I've downgrade my cousin's SONY XPERIA X (F5121) to Android 6.0.1 Marshmallow from 8.0.0 Oreo to be able to make a backup of the TA partition, but I've a few questions:

I used to the process, a German customized version because is the only one that I've found to this purpose, but We're from Spain, is there any problem with this? I don't know if in these countrys, the frequencies used for 2G/3G/4G are the same or are different, because after the downgrade, the coverage is worse than before using the Oreo stock rom.

Other question, when I used the program, at the WIPE section, I didin't select the PERSIST and NOQ(I don't remember well the name of thist last option), the "problems" with the coverage can be related with this??

Thank you so much for your time and help, regards.
 
Last edited:

levone1

Senior Member
Dec 28, 2014
3,741
1,451
243
The flash script very likely was created from the USB log of a 128 GB Xperia 1 II device. Doing a factory reset through the phone after it was flashed with FlashTool should fix that (at least that's how it works on the older Xperia X, where the dual SIM variant has 64 GB of storage compared to the 32 GB of the single SIM variant)...
This is not the case. I created the USB log and flash script myself on a 256 GB Xperia 1 II XQ-AT51. I did not notice the issue myself though.
Quick question - how to generate a fsc? I read from someone on another forum who has Xperia 10 (I3113), and can't use FT, because no fsc for his model...
Thanks
 

cd993

Senior Member
May 8, 2009
3,286
1,096
243
London
Does anyone know of a successful way to update to the latest firmware (I'm using an Xperia 1 II) that is bootloader unlocked & rooted.

Research seems to suggest delete all .TA files aswell as the userdata file and if that works, to flash an extracted/pactched boot.img that I've already prepped. Though some users mention that they then get a decryption error resulting in the need to fully wipe.

If I have to do a clean flash it wouldn't be the end of the world but I would love to avoid the hassle of (even with the usage of Swift Backup etc) and little things like not losing my autobrightness settings which have been learning my usage etc
 
Jul 3, 2020
43
4
0
41
Ostrava
www.cfcbazar.com
Recommendation

Good day! Thanks to the developers of this wonderful tool, for the most part it works great. After a lot of testing, I have found 1 recommendation that will help us users.

Sometimes installing custom ROMs makes the FlashTool unable to recognize the device, but the bootloader lock/unlock function works, because you can select the device manually. Please add the same check for flashing. It will be of great help to us, if we can select the device manually.
 

Forbiddendnb

Senior Member
Feb 7, 2012
143
11
0
i cant flash lates firmware for my Xperia 5 (J9210)
Flashtool Latest release (0.9.29.0)

01/003/2020 11:03:35 - INFO - Selected Bundle for Sony Xperia 5 Dual(J9210). FW release : 55.1.A.9.75. Customization : Customized RU
01/003/2020 11:03:35 - INFO - Preparing files for flashing
01/004/2020 11:04:27 - INFO - Please connect your device into flashmode.
01/004/2020 11:04:35 - INFO - Using Gordon gate drivers version 3.1.0.0
01/004/2020 11:04:35 - INFO - USB buffer size set to 512K
01/004/2020 11:04:35 - INFO - Opening device for R/W
01/004/2020 11:04:35 - INFO - Device ready for R/W.
01/004/2020 11:04:35 - INFO - Reading device information
01/004/2020 11:04:35 - INFO - Reading phone properties
01/004/2020 11:04:35 - INFO - Sending getvar:product
01/004/2020 11:04:35 - INFO - getvar status : OKAY
01/004/2020 11:04:35 - INFO - Sending Read-TA:2:2202
01/004/2020 11:04:35 - INFO - Read-TA status : OKAY
01/004/2020 11:04:35 - INFO - Sending Read-TA:2:2205
01/004/2020 11:04:35 - INFO - Read-TA status : OKAY
01/004/2020 11:04:35 - INFO - Sending Read-TA:2:2210
01/004/2020 11:04:35 - INFO - Read-TA status : OKAY
01/004/2020 11:04:35 - INFO - Sending Read-TA:2:4900
01/004/2020 11:04:35 - INFO - Read-TA status : OKAY
01/004/2020 11:04:35 - INFO - Sending Read-TA:2:10021
01/004/2020 11:04:35 - INFO - Read-TA status : FAIL
01/004/2020 11:04:35 - WARN - Unit 10021 does not exist ( Hex unit value 00002725 )
01/004/2020 11:04:35 - INFO - Connected device : J9210 / SW release 1318-9850_55.1.A.3.112 / Customization 1320-0801_R8B
01/004/2020 11:04:35 - INFO - Last flash date : null
01/004/2020 11:04:35 - INFO - Phone ready for flashmode operations.
01/004/2020 11:04:35 - INFO - Start Flashing
01/004/2020 11:04:35 - INFO - Parsing boot delivery
01/004/2020 11:04:35 - ERROR - null
01/004/2020 11:04:35 - INFO - Sending Sync
01/004/2020 11:04:35 - INFO - Sync status : OKAY
01/004/2020 11:04:35 - INFO - Sending powerdown
01/004/2020 11:04:35 - INFO - powerdown status : OKAY
01/004/2020 11:04:38 - INFO - Device disconnected
01/004/2020 11:04:39 - INFO - Device connected in flash mode
01/004/2020 11:04:52 - INFO - Device disconnected
Who can help me ?
 
Last edited:

dummytest97

Senior Member
Jul 17, 2016
127
10
28
is the this the right place to report error? i have phone Sony SOV36 and wanted to flash because password forgot but flashtool showing error and phone still normally on. Anyone can help me? 1 more i saw at flashtool log say current device is G8341 , i think maybe seller flash with G8341 firmware.
@Androxyde
 
Jul 3, 2020
43
4
0
41
Ostrava
www.cfcbazar.com
is the this the right place to report error? i have phone Sony SOV36 and wanted to flash because password forgot but flashtool showing error and phone still normally on. Anyone can help me? 1 more i saw at flashtool log say current device is G8341 , i think maybe seller flash with G8341 firmware.
@Androxyde
The problem comes from the Windows 10 driver signature enforcement. Its recommended to use Linux, an older version of lash tool if possible or to disable Windows 10 driver signature enforcement.

Tutorial for using Flash Tool on Linux Ubuntu.
 

TripodKnight

Member
Mar 24, 2013
13
3
3
Xperia 5 ii Support?

Hi, thanks for this tool. I am a new Sony xperia 5 ii owner and noticed xperia 1 ii support was recently added.

Are there plans to add Xperia 5 ii support? I'd create the fsc file per these instructions but my Xperia 5 ii will not repair using the xperia companion app. It's not bricked (Still loads android, only camera and call sound don't work) but I can't for the life of me fix it. Newflasher will not succeed when trying to flash the newest XperiFirm rom.

So I ask, is anyone able to add Xperia 5 ii XQ-AS52 support?
 

killa92

Senior Member
Jul 17, 2011
60
2
8
England
Hi, Does anybody have files to support G82XX? I can't seem to download individual files from github and when i download all device data firefox thinks there's a virus for some reason :(

Ok, So i took the time out to carry out repair function in companion whilst logging USB, I come to parse USB log with correct decrypted location and correct .tms. It has been parsing for over 30 minutes, not yet saw a sign of success. My .tms file is about 1.62GB, Is this a normal size? Having a very tough time with this device, reluctantly tried newflash which doesnt support so happy to come back to flashtool however it seems I am not getting any luck with parse function?
 
Last edited: