[TOOL] Xflasher (xperia command line flasher for pre 2017 devices)

[munjeni]

Tool is designed for s1 protocol only! For edl mode tool is not ready since my tool uses s1 protocol and specific commands related to s1 protocol only! I allredy have made edl downloader but it was for xperia z1c only and it sucesfully uploads preloader tot the device and that's all. For preloader command I have no analyse so can't tell how it is working. But that uncomplete tool is based on s1tool (based on raw usb packets transformed into c code ), only which I can help you is you need preloader binary signed with sony certificate, without signed binary you ca do nothing, don't waste your time if you have no preloader. Another thing, I have decided 6 months ago to close all my work from public, reason was my temp ban which I not deserved here, so definitely all my future projects will stay closed source, that's final. Whats your phone model?

 

[munjeni]

Have made v22 for windows because of this https://forum.xda-developers.com/showpost.php?p=72616885&postcount=19 so if somebody had problem with v21 and timeouts or overlaped io problems please try v22 and let me know please! Booth versions is identic, only diferencie is windows version and this:

/* check on the results of the asynchronous read and update the nBytesRead... */
bResult = GetOverlappedResult(dev, &gOverLapped_out, &nBytesRead, TRUE);

its now set to TRUE (wait completes).

 

[munjeni]

Reuploaded v22 since found this:

Based on this info https://msdn.microsoft.com/en-us/library/windows/desktop/aa365467(v=vs.85).aspx parameter lpNumberOfBytesRead is only used in synchronous read/write which was case in my tool, now that parameter is NULL since we using asynchronous read/write

 

[ch3mn3y]

Didn't want to write it in Flashtool folder, as it's not about Flashtool.
After changing (or not, depends where I got firmware) .sinbs to .sins, to flash boot folder I need to change third 0 to 1, right?
Than all .sins and .tas from this folder will be flashed as long are their names don't have this additional "b"?

How it is with newflasher? There is no script to edit, so boot folder is flashed as long as the files exist and their names are correct?

 

[munjeni]

Didn't want to write it in Flashtool folder, as it's not about Flashtool.
After changing (or not, depends where I got firmware) .sinbs to .sins, to flash boot folder I need to change third 0 to 1, right?
Than all .sins and .tas from this folder will be flashed as long are their names don't have this additional "b"?

How it is with newflasher? There is no script to edit, so boot folder is flashed as long as the files exist and their names are correct?

Yes! All that things which I told you is ONLY if you extracting FTF!! If you have firmware made my xperifirm (not FTF) than you no need to rename files in boot folder since only flashtool from an unknown reason renames that files in boot folder by changing extension. Booth xflasher and newflasher can't see renamed files!

 

[ch3mn3y]

I understand that. Only that script seems to not include .sin files form boot folder, so I wanted to ask to be sure how to include them as even when I know that they are "part" of boot delivery and Your (amazing btw, thanks for it) tool seems to not flash it (at least it didn't when I tested it with Z2) without any modifications to script.
Just wanted to be sure if changing that third 0 to 1 is how You get script to flash .sins from boot folder onto device. It's good to know it for the future flashes.
Thanks for Your answer.

 

[munjeni]

I understand that. Only that script seems to not include .sin files form boot folder, so I wanted to ask to be sure how to include them as even when I know that they are "part" of boot delivery and Your (amazing btw, thanks for it) tool seems to not flash it (at least it didn't when I tested it with Z2) without any modifications to script.
Just wanted to be sure if changing that third 0 to 1 is how You get script to flash .sins from boot folder onto device. It's good to know it for the future flashes.
Thanks for Your answer.

I told you allready! You must rename extensions (.sinb and .tab to .sin and .ta) in case it is renamed by flashtool! Than xflasher would be able to see that files in boot folder! Now xflasher can't see it because of design! Do not try to include these files from boot folder manualy by adding it to the .bat because you can get hard brick because boot delivery contain 5 configurations, every configuration have its own set of sin files, if you flash wrong sin file (from wrong configuration) you can get hard brick! Better idea rename extensions right, or maybe more better idea, use xperifirm and redownload firmware, do not pack firmware to ftf since if you pack them to ftf it will change extension to xxxB! I have no idea why Androxide rename these extensions to xxxB.

 

[munjeni]

V23 is out, final version, all optimisations and fixes related to usb packets backported from newflasher, enjoy!

 

[GreyLeshy]

Please lay out the latest version has it.

 

[munjeni]

Yes

 

[schastang]

Hi!

I'm trying to get my Xperia Z back to life.
(see posts https://forum.xda-developers.com/showpost.php?p=74066206&postcount=372
and https://forum.xda-developers.com/xperia-z/help/xperia-z-flash-failure-trying-to-flash-t3684222)

I gave a try to your tool, but it seems there is an issue with the TA partition of my phone.

When I flash firmware with xflasher, there are some errors and the phone still don't boot after the Sony logo (it turns black, I can see backlight, and then reboots).
When I try to unlock bootloader, There are some errors related to the TA partition (similar issue with flashtool : ERR_DYNAMIC= "Write TA failed")

I tried everything to save my phone but didn't succeed. Could you please help?
For information, I have unlocked my device to install custom ROMs, but I decided to get back to the original state, so I tried to restore the initial backup (made with TWRP) but it failed few seconds after start. I think some partitions (Trim Area ?) are corrupted now that's why I cannot unlock it again, or flash any other FTF.

Please find logs as attachment :
- flash firmware log
- unlock bootloader log

Thanks a lot.
Seb

 

[schastang]

Hi!

I'm trying to get my Xperia Z back to life.
(see posts https://forum.xda-developers.com/showpost.php?p=74066206&postcount=372
and https://forum.xda-developers.com/xperia-z/help/xperia-z-flash-failure-trying-to-flash-t3684222)

I gave a try to your tool, but it seems there is an issue with the TA partition of my phone.

When I flash firmware with xflasher, there are some errors and the phone still don't boot after the Sony logo (it turns black, I can see backlight, and then reboots).
When I try to unlock bootloader, There are some errors related to the TA partition (similar issue with flashtool : ERR_DYNAMIC= "Write TA failed")

I tried everything to save my phone but didn't succeed. Could you please help?
For information, I have unlocked my device to install custom ROMs, but I decided to get back to the original state, so I tried to restore the initial backup (made with TWRP) but it failed few seconds after start. I think some partitions (Trim Area ?) are corrupted now that's why I cannot unlock it again, or flash any other FTF.

Please find logs as attachment :
- flash firmware log
- unlock bootloader log

Thanks a lot.
Seb

Hi munjeni,

Lot of thanks to you. I finally succeed in resurrecting my Xperia Z phone by using this great tool !
It allowed me to flash this ROM (https://forum.xda-developers.com/xperia-z/general/stock-rom-xperia-z-c6603-10-6-0-454-t3127499) while Flashtool failed to write most of parts (TA, SYSTEM, KERNEL, ...) 1 file by 1 file

THANK YOU!

Seb

 

[xrenoix]

hello @munjeni look here TA Backup for G814x by @Macs1209 it's work i have test on my G8141
https://forum.xda-developers.com/xz-premium/how-to/ta-backup-g814x-t3691603

i can send my backup to you in private !!!

 

[greenbeans71]

The C4 E5306 Single is not compatible with the Flashtool. Is it compatible when used in conjunction with Xflasher and if so, to clarify,this tool unlocks the bootloader? Thanks

 

[bigrammy]

Testing now my side, this is error I am getting from v16:

Proccessing cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin...
File size: 0x5B0754
Sin header size: 0x624
Sin data size: 0x5B0130
ERROR: Unable to open max_p for read! failed with error code 2 as follows:
The system cannot find the file specified.


Error uploading cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin!

I know whats wrong now V17 in next 5 minutes!

I get this error also :crying:

Log:

-------------------------------------------------------
            Xperia Command Line Flasher v23            
                                                       
                 by Munjeni @ 2014,2017                     
-------------------------------------------------------
found device with vid:0x0fce pid:0xadde.
Proccessing cache_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin...
File size: 0x6475
Sin header size: 0x408
Sin data size: 0x606D
Unable to open max_p for read!
No such file or directory
Error uploading cache_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin!

EDIT: Fixed I forgot to activate noloader option

Log here:

-------------------------------------------------------
            Xperia Command Line Flasher v23            
                                                       
                 by Munjeni @ 2014,2017                     
-------------------------------------------------------
found device with vid:0x0fce pid:0xadde.
 - Successfully read 0xd bytes from handle.
Raw input [0xD]:

  00000000  00 00 00 00 00 00 00 00 00 00 00 00 00           .............

 - Successfully read 0x411 bytes from handle.
Raw input [0x411]:

  00000000  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000020  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000030  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000040  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000050  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000060  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000070  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000080  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000090  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000000A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000000B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000000C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000000D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000000E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000000F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000100  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000110  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000120  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000130  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000140  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000150  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000160  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000170  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000180  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000190  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000001A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000001B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000001C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000001D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000001E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000001F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000200  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000210  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000220  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000230  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000240  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000250  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000260  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000270  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000280  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000290  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000002A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000002B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000002C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000002D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000002E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000002F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000300  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000310  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000320  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000330  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000340  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000350  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000360  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000370  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000380  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000390  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000003A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000003B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000003C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000003D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000003E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  000003F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000400  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000410  00                                               .

 - Successfully read 0x4 bytes from handle.
Raw input [0x4]:

  00000000  5F 56 45 52                                      _VER

-------------------------------------------------------
            Xperia Command Line Flasher v23            
                                                       
                 by Munjeni @ 2014,2017                     
-------------------------------------------------------
found device with vid:0x0fce pid:0xadde.
Proccessing cache_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin...
File size: 0x6475
Sin header size: 0x408
Sin data size: 0x606D
Setting max packet size to: 0x80000
Sending command...
Raw command[0xD]:

  00000000  00 00 00 05 00 00 00 03 00 00 04 08 11           .............

 - Successfully write 0xd bytes to handle.
Writing sin header with size of 0x408 bytes
 - Successfully write 0x408 bytes to handle.
Sin header writen.
CRC32[0x4]:

  00000000  12 FB 1F E3                                      ....

Writing crc32 for sin header...
 - Successfully write 0x4 bytes to handle.
 - Successfully read 0xd bytes from handle.
Raw input [0xD]:

  00000000  00 00 00 00 00 00 00 00 00 00 00 00 00           .............

Verifying crc32...
success: device replied with 0000000500000001000000000B which mean ok.

 - Successfully read 0x4 bytes from handle.
Raw input [0x4]:

  00000000  00 00 00 01                                      ....

Sending command...
Raw command[0xD]:

  00000000  00 00 00 06 00 00 00 03 00 00 60 6D 0F           ..........`m.

 - Successfully write 0xd bytes to handle.
Writing chunk part: 1 with size of 0x606d bytes
 - Successfully write 0x606d bytes to handle.
Chunk part: 1 writen.
CRC32[0x4]:

  00000000  FF 00 18 75                                      ...u

Writing crc32 for chunk part: 1
 - Successfully write 0x4 bytes to handle.
WRITING LAST PACKET. SETTING TIMEOUT TO 600000 (ms).
 - Successfully read 0xd bytes from handle.
Raw input [0xD]:

  00000000  00 00 00 00 00 00 00 00 00 00 00 00 00           .............

Verifying crc32...
Success: device replied with 0000000600000001000000000E which mean ok.

LAST PACKET REAPLY AFTER ms: 0.101000
 - Successfully read 0x4 bytes from handle.
Raw input [0x4]:

  00000000  00 00 00 01                                      ....

Finished.


cache_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin uploaded sucessfully.

boot folder does not get loaded in the .sh should I take all the files from the boot folder and dump them in the main folder?
Boot contents.

boot_delivery.xml
logo_S1-BOOT-LIVE-A4CD-0004-MMC.sin  
preloader_s1sbl_S1-BOOT-LIVE-A4CD-0004-MMC.sin  
tee1_S1-BOOT-LIVE-A4CD-0004-MMC.sin 
tee2_S1-BOOT-LIVE-A4CD-0004-MMC.sin
lk_S1-BOOT-LIVE-A4CD-0004-MMC.sin  
Pine_S1BootConfig_MiscTA.ta          
secro_S1-BOOT-LIVE-A4CD-0004-MMC.sin

xflasher.sh

#NOTE:
#      first command must write loader to the device! Or in case newer sony device which doesn't have loader
#      first parameter must be noloader instead of loader.sin!
#      All next commands set argument 0 as a loader since loader or noloader is need only in first command!
#      Next command in this example make s1 dump to file called tadump.ta.
#
#      Remember, loader or noloader must be first parameter and no more than one time, and must be first parameter!
#      0 mean skip command from table!
#      unlock bootloader parameter is 0 for skip unlocking, or unlock bootloader KEY for unlocking!
#      dump ta parameter 0 is for skip s1 dumping, or 1 for dumping s1, dump will be stored in file caled tadump.ta
#      Enjoy tool!
#
#Table of commands with example steps for using xflasher tool:
#-----------------------------------------------------------------------------------------------------------------------------------------------------
#xflasher   | send loader?  |   dump ta?  |  unlock bootloader? KEY | USB_VID | USB_PID |  FLASH BOOT DELIVERY? | flash ta file? | write log to file
#-----------------------------------------------------------------------------------------------------------------------------------------------------

#upload loader.sin (please change this to loader.sin in case your device uses loader.sin)
#                  (please change to noloader in case your device don't use loader!     )
./xflasher.x64  noloader  0  0  0FCE  ADDE  0  0  >xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi

#flash sin files
./xflasher.x64  partitions_S1-SW-LIVE-A4CD-PID1-0005-MBR.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  system_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  elabel-G3311-row-row_201707070748817.1_43.0.A.7.55_S1-ELABEL-LIVE-A4CD-PID1-0004-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  diag_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  Qnovo_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  kernel_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  cache_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  oem_S1-CUST-LIVE-A4CD-PID1-0004-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  apps_log_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  userdata_S1-CUST-LIVE-A4CD-PID1-0004-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  fotakernel_S1-SW-LIVE-A4CD-PID1-0005-MMC.sin  0  0  0FCE  ADDE  0  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi

#flash ta files
./xflasher.x64  0  0  0  0FCE  ADDE  0  auto-boot.ta  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  0  0  0  0FCE  ADDE  0  GMSK_TX_PWR_ROLLBACK.ta  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  0  0  0  0FCE  ADDE  0  osv-restriction.ta  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  0  0  0  0FCE  ADDE  0  simlock.ta  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  0  0  0  0FCE  ADDE  0  cust-reset.ta  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  0  0  0  0FCE  ADDE  0  Wifi_MiscTA1.ta  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  0  0  0  0FCE  ADDE  0  fota-reset.ta  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi
./xflasher.x64  0  0  0  0FCE  ADDE  0  reset-wipe-reason.ta  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi

#flash boot delivery
./xflasher.x64  0  0  0  0FCE  ADDE  1  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi

 

[munjeni]

#flash boot delivery
#xflasher   | send loader?  |   dump ta?  |  unlock bootloader? KEY | USB_VID | USB_PID |  FLASH BOOT DELIVERY? | flash ta file? | write log to file
./xflasher.x64  0  0  0  0FCE  ADDE  [COLOR="Red"][B]1[/B][/COLOR]  0  >>xflasher.log ; rc=$?; if [[ $rc != 0 ]]; then exit $rc; fi

red part (1 or 0) if 1 it tells xflasher about to flash boot delivery! Bootdelivery files is not loaded to sh with one reason, xflasher need to determine it trought info from your device!

 

[CMT 1412-4444 'Fours']

Got sent here after I dumbly went over to the Newflasher thread instead. Downloaded Xflasher, put it into the Z4 Tab firmware folder, ran it, then held the volume [-] key before connecting to my laptop to get the solid green light that I'm told indicates flash mode, and ran the new .bat file in the firmware folder, only to get the following log:

-------------------------------------------------------
            Xperia Command Line Flasher v23            
                                                       
                 by Munjeni @ 2014,2017                     
-------------------------------------------------------

No usb device with vid:0x0fce pid:0xadde !
-------------------------------------------------------
            Xperia Command Line Flasher v23            
                                                       
                 by Munjeni @ 2014,2017                     
-------------------------------------------------------

No usb device with vid:0x0fce pid:0xadde !

My tablet is the SGP771 Global 4G model, not the SO-05G Japan-only 4G model, and USB debugging in dev options is on. I can't help but feel like I did something wrong with the drivers, as I have downloaded the correct drivers from Sony's website for the Z4T, but every time I go to Device Manager and try to manually update them, it tells me the default drivers from 2006 are the latest one and won't let me do anything else.

 

[Emba4]

Got sent here after I dumbly went over to the Newflasher thread instead. Downloaded Xflasher, put it into the Z4 Tab firmware folder, ran it, then held the volume [-] key before connecting to my laptop to get the solid green light that I'm told indicates flash mode, and ran the new .bat file in the firmware folder, only to get the following log:

-------------------------------------------------------
            Xperia Command Line Flasher v23            
                                                       
                 by Munjeni @ 2014,2017                     
-------------------------------------------------------

No usb device with vid:0x0fce pid:0xadde !
-------------------------------------------------------
            Xperia Command Line Flasher v23            
                                                       
                 by Munjeni @ 2014,2017                     
-------------------------------------------------------

No usb device with vid:0x0fce pid:0xadde !

My tablet is the SGP771 Global 4G model, not the SO-05G Japan-only 4G model, and USB debugging in dev options is on. I can't help but feel like I did something wrong with the drivers, as I have downloaded the correct drivers from Sony's website for the Z4T, but every time I go to Device Manager and try to manually update them, it tells me the default drivers from 2006 are the latest one and won't let me do anything else.

Those are the MTP drivers, you need to put the tab into flash mode (hold Vol down while connecting) the device manager should show something like SOMC Flash Device in device manager in the USB Controllers section rather than portable devices. if oyu open the properties of the device and then open Details tab and select Hardware Ids from the drop down menu and you should see the VID/PID for the device which should match the 0x0fce and 0xadde in the script

Now on to my own question, ive been trying to use xFlasher to flash an XA1, initially i tried newflasher as i thought it would be on the new protocol but the PID doesnt match so i tried xFlasher and it recognizes it but it fails when attempting to send the first image. is xFlasher not compatible with MTK sony devices? i have considered if it may actually be using hte new protocol but still have the old PID but i didnt want to try it in case it nukes the phone (i know MTK devices can be fragile and its not like you can revive sonys like you can a cheapo alcatel or something)

 

[Emba4]

i seem to be having an issue with boot delivery on a Z5 dual (if you want specifics on the issue ill put them at the end as its not really relavent) no matter what version of the firmware i download apparently the boot delivery doesnt match my device (all other files flash fine and the phone sort of works) i have literally downloaded every single file for the Z5D on xperifirm and non have a boot delivery that match, in a vain attempt to force it as im pretty much 100% sure my Z5 Dual is in fact a Z5 Dual (proven by the fact that the other files flash) i even modified the CDA numbers in the boot delivery xml to try and force it to match

am i missing something incredibly simple? have i found some sort of incredibly obscure prototype device that somehow has a different bootloader? (i doubt it but you never know with CEX) is there a way i can tell the flasher to ignore the check , i know its there to stop it flashing the wrong thing but there is basically zero chance that it is the wrong one

the problem with the device is that after i flashed it when i attempt to switch it on i get an empty battery icon and no boot, plug it in and itll say something like 37% and will now power on but it wont switch on if its not connected, the only thing i can think is that it needs a FULL flash to sort it out

 

[goku_0729]

i have xa1 ultra i tried to flash the latest rom on support on process of flashing failed on fotakernel. sin even if i try to flash system.sin also failed. any help for this were i went wrong flashing.