[TOOL] Newflasher (xperia command line flasher)

Search This thread

munjeni

Senior Member
Jun 2, 2011
9,582
22,215
Anyone tried v52 on 1 IV? or any method to test it before actual flashing?
Simply try flash only userdata sin file for example, delete all the rest of files, so if it work the rest will work too. Do in mind flashing userdata will probably factory reset your device or delete all your personal files on that partition. Another problem would be roll back protection and you will not be abble to downgrade or install the same rom and you will get infinite boot loop! I will not repeat rollback story, simple read what cause roolback protection and how to deal them! Unlock bootloader will probably be needed in that case! In short, before you decide to try anything read twice xda posts! :)
 
Last edited:

lucyoreo

New member
Mar 6, 2022
3
1
Looks like you have moved usb cable, cable have not a good contact, usb isue....etc, so flashing got interupted!
Managed to reflash it successfully using a shorter high speed external SSD cable. I have tried the original USB c to c cables and many other cables which turned out failure. Thank you so much for letting me know it's the cable issue.
 
  • Like
Reactions: munjeni

xz3user

New member
Jun 23, 2022
3
1
How do I flash the firmware to the latest version using this tool without modifying the oem folder on the XZ3? Also, is there anyway to flash the latest OEM partition without overwriting the launcher that I installed using temp root method?
 

sndestroy

Member
Jun 8, 2012
20
10
Santiago
Sony XA2 Ultra
Hello there! I have a XA2 Ultra that out-of-the-blue got stuck in the infamous bootloop (reboots after Xperia logo), and desperately need to recover files from internal memory.

I dl'd with XperiFirm EXACTLY the same FW it has now (variant, region etc). Newflasher flashed the phone correctly and I chose to keep userdata, believing it would boot a-fresh. But it's still stuck in the same bootloop :( seems the problem is in the user partition itself?

I know the thread is NOT for this, but still... Anyone know how to "extract" the userdata partition from a bootloop-stuck Xperia phone? Doesn't matter if it's corrupt, that I could deal with later... I'm now positive that doing a full flash w/Newflasher will recover my phone, but I need to take out my files first :cry:
 

munjeni

Senior Member
Jun 2, 2011
9,582
22,215
Hello there! I have a XA2 Ultra that out-of-the-blue got stuck in the infamous bootloop (reboots after Xperia logo), and desperately need to recover files from internal memory.

I dl'd with XperiFirm EXACTLY the same FW it has now (variant, region etc). Newflasher flashed the phone correctly and I chose to keep userdata, believing it would boot a-fresh. But it's still stuck in the same bootloop :( seems the problem is in the user partition itself?

I know the thread is NOT for this, but still... Anyone know how to "extract" the userdata partition from a bootloop-stuck Xperia phone? Doesn't matter if it's corrupt, that I could deal with later... I'm now positive that doing a full flash w/Newflasher will recover my phone, but I need to take out my files first :cry:
Unlocked bootloader? If not unlocked and you attempt to unlock bootloader factory reset will be performed and you will lose your userdata! In case bootloader is unlocked allready, simple temporary boot an twrp recovery and dump all your data!
 
  • Like
Reactions: sieghartRM

Nimda01

Senior Member
Jun 15, 2012
74
25
24
Nonthaburi
Xperia XZ2
Sony Xperia 1 II
Simply try flash only userdata sin file for example, delete all the rest of files, so if it work the rest will work too. Do in mind flashing userdata will probably factory reset your device or delete all your personal files on that partition. Another problem would be roll back protection and you will not be abble to downgrade or install the same rom and you will get infinite boot loop! I will not repeat rollback story, simple read what cause roolback protection and how to deal them! Unlock bootloader will probably be needed in that case! In short, before you decide to try anything read twice xda posts! :)
Tried only userdata.sin at first and it works. Later managed to flash the whole FW (except deleting .ta and persist.sin) which works successfully too.

Seems like Sony didn't change anything (or didn't change that much) in Mark IV's bootloader compared to III's

QNUjFjR.png

83DsOdF.png


Anyway, Thanks for your answer and contribution to this tool!
 
  • Like
Reactions: Aqq123 and munjeni

munjeni

Senior Member
Jun 2, 2011
9,582
22,215
Its seems the same with no modification between mark 3 and mark 4, thanks for testing on mark 4 and comfirming! :)
 
  • Like
Reactions: sieghartRM

pranavrr

New member
Jun 28, 2022
1
0
I need help,
tried to flash xperia 5 sov41 with UK firmware but ended up having it corrupt.
I used newflasher and got Error, didn't got flash OKAY reply! Got reply: FAILWrite fail at the end.
I am all new to this please help.
 

munjeni

Senior Member
Jun 2, 2011
9,582
22,215
I need help,
tried to flash xperia 5 sov41 with UK firmware but ended up having it corrupt.
I used newflasher and got Error, didn't got flash OKAY reply! Got reply: FAILWrite fail at the end.
I am all new to this please help.
How do you think someone can help you when there is no newflasher log? :) If it is at the end after "sync" ignore it since its allready known problem on some devices
 
Last edited:

aboiledtiger

Member
Jun 16, 2022
11
0
Hi @munjeni ! I'll appreciate your advice. trying to flash a 2018 XA2 (H3123) newflasher fails:

Code:
No usb device with vid:0x0fce pid:0xb00b !

and indeed:


Code:
Product ID:    0x0dde


  Vendor ID:    0x0fce  (Sony Ericsson Mobile Communications AB)


  Version:    1.00


  Speed:    Up to 480 Mb/sec


  Manufacturer:    Google


  Location ID:    0xfa120000 / 3


what am I missing?
thx...

nevermind... I found this:

regards...
dx
 

wednesyao

Member
Aug 11, 2017
21
2
Thanks for this wonderful tool! Now I'm suffering flashing my 1 IV. It's firmware is CN (which version is higher) and I want to flash it the Hongkong (which version is lower) one. After I flash my phone bricks. v52 flasher, XperiFirm's firmware, I have no idea about the failure. Do I need to unlock the bootloader?
 

Pandemic

Senior Member
Aug 30, 2010
24,062
23,188
Meppel
talk.sonymobile.com
Xperia XZ2
Sony Xperia 1
Thanks for this wonderful tool! Now I'm suffering flashing my 1 IV. It's firmware is CN (which version is higher) and I want to flash it the Hongkong (which version is lower) one. After I flash my phone bricks. v52 flasher, XperiFirm's firmware, I have no idea about the failure. Do I need to unlock the bootloader?
Flash the correct fw and no not needed to unlock the bootloader so far i know.
 

Guttergorm

Member
Jun 9, 2016
48
9
Moto G
Sony Xperia XA2
Hi, I recently bought an xa2 (h4113) dual and somehow bricked it (old fastboot version initially?). Meaning, the device reboots 5 times and then show the meessage "[..] corrupt [..] not boot [..]". I can get a connection in emma, can activate green (recovery?) and blue (fastboot?) modes, but i do not know how to proceed. Actually I'm a little bit scared to completely brick it.
I have newflasher and a directory H4113_Customized DACHBLX_50.2.A.3.77-R5B retrieved by XperiFirm.
I am used to classic moto phones and I am somehow lost with all this new (to me) a/b stuff, no visual stock recovery and so on. Any help very much appreciated.

D:\adb\newflasher\H4113_Customized DACHBLX_50.2.A.3.7

03.07.2022 21:51 <DIR> .
03.07.2022 21:51 <DIR> ..
11.08.2020 08:22 2.363 appslog_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 appslog_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 354 auto-boot.ta
11.08.2020 08:22 289.620 bluetooth_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 bluetooth_X-FLASH-ALL-18AE_0x00.ha
03.07.2022 21:51 <DIR> boot
11.08.2020 08:23 22.822.938 boot_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 boot_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 243 cust-reset.ta
11.08.2020 08:22 2.935 diag_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 diag_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:22 3.727.124 dsp_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 dsp_X-FLASH-ALL-18AE_0x00.hash
10.09.2018 06:36 1.374.038 elabel-H4113-row-row_2018091006121
A.10.51_X-FLASH-LTALABEL-18AE.sin
11.08.2020 08:28 36.147 fsconfig.xml
11.08.2020 08:23 49.833 fsg_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 fsg_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.369 fsmetadata_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 fsmetadata_X-FLASH-ALL-18AE_0x00.h
03.07.2022 21:51 311 fwinfo.xml
11.08.2020 08:22 1.386 misc_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 misc_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.361 modemst1_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modemst1_X-FLASH-ALL-18AE_0x00.has
11.08.2020 08:23 1.363 modemst2_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modemst2_X-FLASH-ALL-18AE_0x00.has
11.08.2020 08:22 51.886.575 modem_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modem_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 4.611 oem_other_X-FLASH-CUST-18AE.sin
21.08.2020 09:36 17.002.050 oem_X-FLASH-CUST-18AE.sin
21.08.2020 09:36 278 osv-restriction.ta
11.08.2020 08:22 4.935 partition-image_X-FLASH-ALL-18AE.s
11.08.2020 08:23 148.557 persist_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 persist_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 2.375 Qnovo_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 Qnovo_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.363 rdimage_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 rdimage_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 286 reset-wipe-reason.ta
21.08.2020 09:36 1.313 simlock.ta
11.08.2020 08:22 1.351 ssd_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 ssd_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 76.405.066 system_other_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 system_other_X-FLASH-ALL-18AE_0x00
11.08.2020 08:28 32 system_other_X-FLASH-ALL-9B8D_0x00
11.08.2020 08:23 1.541.089.157 system_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 system_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:28 32 system_X-FLASH-ALL-9B8D_0x00.hash
03.07.2022 21:51 593 update.xml
21.08.2020 09:36 61.590 userdata_X-FLASH-CUST-18AE.sin
11.08.2020 08:23 220.532.627 vendor_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 vendor_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:28 32 vendor_X-FLASH-ALL-9B8D_0x00.hash
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,582
22,215
Hi, I recently bought an xa2 (h4113) dual and somehow bricked it (old fastboot version initially?). Meaning, the device reboots 5 times and then show the meessage "[..] corrupt [..] not boot [..]". I can get a connection in emma, can activate green (recovery?) and blue (fastboot?) modes, but i do not know how to proceed. Actually I'm a little bit scared to completely brick it.
I have newflasher and a directory H4113_Customized DACHBLX_50.2.A.3.77-R5B retrieved by XperiFirm.
I am used to classic moto phones and I am somehow lost with all this new (to me) a/b stuff, no visual stock recovery and so on. Any help very much appreciated.

D:\adb\newflasher\H4113_Customized DACHBLX_50.2.A.3.7

03.07.2022 21:51 <DIR> .
03.07.2022 21:51 <DIR> ..
11.08.2020 08:22 2.363 appslog_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 appslog_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 354 auto-boot.ta
11.08.2020 08:22 289.620 bluetooth_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 bluetooth_X-FLASH-ALL-18AE_0x00.ha
03.07.2022 21:51 <DIR> boot
11.08.2020 08:23 22.822.938 boot_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 boot_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 243 cust-reset.ta
11.08.2020 08:22 2.935 diag_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 diag_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:22 3.727.124 dsp_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 dsp_X-FLASH-ALL-18AE_0x00.hash
10.09.2018 06:36 1.374.038 elabel-H4113-row-row_2018091006121
A.10.51_X-FLASH-LTALABEL-18AE.sin
11.08.2020 08:28 36.147 fsconfig.xml
11.08.2020 08:23 49.833 fsg_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 fsg_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.369 fsmetadata_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 fsmetadata_X-FLASH-ALL-18AE_0x00.h
03.07.2022 21:51 311 fwinfo.xml
11.08.2020 08:22 1.386 misc_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 misc_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.361 modemst1_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modemst1_X-FLASH-ALL-18AE_0x00.has
11.08.2020 08:23 1.363 modemst2_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modemst2_X-FLASH-ALL-18AE_0x00.has
11.08.2020 08:22 51.886.575 modem_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modem_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 4.611 oem_other_X-FLASH-CUST-18AE.sin
21.08.2020 09:36 17.002.050 oem_X-FLASH-CUST-18AE.sin
21.08.2020 09:36 278 osv-restriction.ta
11.08.2020 08:22 4.935 partition-image_X-FLASH-ALL-18AE.s
11.08.2020 08:23 148.557 persist_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 persist_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 2.375 Qnovo_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 Qnovo_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.363 rdimage_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 rdimage_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 286 reset-wipe-reason.ta
21.08.2020 09:36 1.313 simlock.ta
11.08.2020 08:22 1.351 ssd_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 ssd_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 76.405.066 system_other_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 system_other_X-FLASH-ALL-18AE_0x00
11.08.2020 08:28 32 system_other_X-FLASH-ALL-9B8D_0x00
11.08.2020 08:23 1.541.089.157 system_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 system_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:28 32 system_X-FLASH-ALL-9B8D_0x00.hash
03.07.2022 21:51 593 update.xml
21.08.2020 09:36 61.590 userdata_X-FLASH-CUST-18AE.sin
11.08.2020 08:23 220.532.627 vendor_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 vendor_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:28 32 vendor_X-FLASH-ALL-9B8D_0x00.hash
Just put your phone in "green" and double click newflasher.exe, than folow on screen messages & prompts carefully and you are done. If you need usb driver put newflasher in an empty folder, double click them and folow on screen driver extraction prompt, newflasher will extract driver which you need to install, install them. Than go back to "green" and install rom you need
 

Anon1337

Member
Feb 15, 2020
21
1
There must be at least red light when you connect usb cable! It looks like hardware isue! Maybe usb port on phone side? Check for dust! I had that problem some month ago, the cable simple could not fully enter the port, so after removing dust everything went ok
supposedly the motherboard was completely dead as the Sony Service Center states that it was completely swapped for a new one
I will post more once I get my hands on the phone. It's still on its way to me.
 

munjeni

Senior Member
Jun 2, 2011
9,582
22,215
supposedly the motherboard was completely dead as the Sony Service Center states that it was completely swapped for a new one
I will post more once I get my hands on the phone. It's still on its way to me.
It heave another meaning too, for example it might be power supply problem on your PC for example it didn't deliver max 5.2V over usb instead maybe a bit more e.g. 5.4V , check that first before you kill your next phone!
 
  • Like
Reactions: sieghartRM

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi, didn't see you edited your message.

    I tried again today and the device appeared differently, with the triangle you describe, and the right pid (yesterday it only appeared as a generic usb device called XQ-BT52). After installing the drivers, etc, I was able to flash the stock rom without any issue !
    I'm not sure what triggered it to work this time so I'm afraid I cannot help other people with a similar issue ... To be sure it wasn't on the computer's side, I connected it to my other computer and it was recognized as well. I guess I was in the wrong mode yesterday then, but I had the green light so I'm surprised this was not flash mode...

    Anyway, thanks a lot for the help, and for maintaining that wonderful tool !
  • 332
    Disclaimer:

    newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick your device or anything else!


    How to use:

    OPTIONAL STEP 1:
    - if you have missing flash driver just double click exe and confirm driver extraction, an exe will become available, run it and install driver.

    OPTIONAL STEP 2:
    - this step is optional, this step dump trim area, you can do this and keep those file somewhere on your pc in case you hard brick your device so give it to servicians to repair your phone.

    STEP 1:
    - Download right firmware for your device using XperiFirm tool, put newflasher.exe into firmware dir created by XperiFirm tool. Before you double click newflasher.exe do in mind something, newflasher tool is programed to flash everything found in the same dir!!! So tool flash all .ta files, all .sin files, boot delivery (whole boot folder), partition.zip, in short all files found in dir! If you no want to flash something just move file which you no want to flash OUT OF FOLDER! Partition.zip .sin files can be flashed only if you extract partition.zip into newly created folder called partition!

    STEP 2:
    - To start flashing phone put your phone into flash mode, double click newflasher.exe and wait wait wait until your device gets flashed, thats it. Look into log to see if something goes wrong! If all right you are done. If not post your log so I can look!

    SOME MORE THINGS:
    "You do not need to unlock bootloader or to root the phone if you want to flash a stock firmware from XperiFirm.
    There are no files in the stock firmware that need to be deleted. Prompts will ask you to skip some files.
    Feel free to press N to every prompt since:
    - TA dumping it's not related with DRM keys.
    - Flash persist_* files only if you know what you are doing, since you will lose your attest keys. Backup persist partition.
    If you need the firmware on both A and B slot use fastboot commands to choose the inactive partion and re-flash."

    Happy flashing!


    Supported platforms:

    - Newflasher is working on Windows, Linux, Android and Darwin, just chose right newflasher binary. With Android version you can flash phone by using another phone!


    Changelog:

    - version 1: Sorry a lot of work is done in pre pre alpha version and I can't count every changes, just folow development process about version 1, a lot of work is done before it started working. One esential change was done to tool improvement and it is described in one of the my posts related to moving function "erase:" to the section before function "flash:", it is realy improvement and more safer than in time when it was at the start of flashing routine.

    - version v2 (15.Aug.2017)
    Implemented free disk space safety check, it was missing and danger in case flashing process gets interupted because of the lack of the free disk space needed for sin extractions and temporary files. I have also include GordonGate flash driver prompt so in case somebody have missing flash drivers, simple need to double click exe and folow drivers archive extraction procedure, later need to install these drivers trought Windos device mannager. Also I have implemented an realy pre pre alpha version of the maybe non working trim (why maybe? Because I don't own xzp so can't test) area dump routine, in case it is working we can dump some esentials trim area units from device (probably not a full dump as like it was on every oldest xperia models - no permissions for dumping drm key unit)

    - version v3 (23.09.2017)
    Some more security checks, it's now a bit safer than v2

    - version v4 (21.10.2017)
    Updated trim area dumper, now it stores log to the trimarea.log but dump is now in .ta format and writen to the 01.ta and 02.ta

    - version v5 (22.10.2017)
    Updated trim area dumper, add progress meter, fix y-n prompt (thanks @pbarrette)

    - version v6 (22.10.2017)
    Updated trim area dumper

    - version v7 (23.10.2017)
    Updated trim area dumper, newflasher redesigned a bit, fix new partitioning for Oreo

    - version v8 (24.10.2017)
    Fix trim area dumper

    - version v9 & v10 (25.10.2017)
    Workaorunds on trim area dumper

    - version v11 (07.04.2018)
    Support for 2018 devices

    - version v12 (29.04.2018)
    Try fix doublefree bug/crash (most noticed on Linux 64 bit binary)

    - version v13 (01.05.2018)
    Fix doublefree bug/crash by removing dynamic allocation from function get_reply

    - version v14 & v15 (12.06.2019)
    Sony XPeria 1 support added.

    - version v16 (16.06.2019)
    LUN0 detection optimized.

    - version v17 (24.06.2019)
    LUN0 detection bug fixed.

    - version v18 (10.08.2019)
    Untested fix for https://forum.xda-developers.com/cr...wflasher-xperia-command-line-t3619426/page105
    Using builtin mkdir instead of calling it trought system call

    - version v19 (08.10.2019)
    Implemented prompt for flashing persist partition; print skipped .sin files

    - version v20 (13.12.2019)
    implemented prompt for flashing bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots

    - version v21 (29.06.2020)
    implemented battery level status check before flashing, flashing bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots is mandatory now and is flashed by default right now, more info, try fix previously reported isue on sync and powerdown command reported 2-3 years ago so I have disabled it and now enabled for test, implemented Macos support (curently need to be tested! If you have plan to test please flash only cache.sin DO NOT flash the rest because of safety for your device!)

    - version v22 (30.06.2020)
    trying to fix battery capacity retrieval

    - version v23 (04.07.2020)
    removed battery capacity retrieval (not going to work that way), fix trim area dump file name, new gordongate drivers

    - version v24 (04.07.2020)
    new feature - now you can run newflasher from script or console with your own command, e.g. newflasher getvar:Emmc-info , I didn't tested all the list of commands, if you do it share them with us!

    - version v25 (09.07.2020)
    New trim area dump tool, with this change trim area dump is created in 3 secconds. Do in mind this not dump protected units like drm key...etc! Some changes in scripting feature from v24

    - version v26 (10.07.2020)
    Added 4 diferent reboot modes, reboot to android, reboot to fastboot, reboot to bootloader, power off

    - version v27 (11.07.2020) (not yet released)
    Workaround in mac libusb

    - version v28 (12.07.2020)
    Workaround to sync response bug; Fully implemented support for Mac. I'm tested myself on mac 10.14 but confirmed working on mac 10.15 too

    - version v29 (12.07.2020)
    Mac proper libusb deinitialisation

    - version v30 (13.07.2020)
    Preparation for Debian packaging; I'm noticed that hex modified arm64 fake pie binary is not working so its now compiled with ndk and its true pie binary now

    - version v31 (14.07.2020)
    Fix cosmetic bug https://forum.xda-developers.com/showpost.php?p=83056693&postcount=1212 which might confuse somebody

    - version 32, not yet released

    - version 33 (30.07.2020)
    Allow bootloader unlocking with newflasher; Try fix sync response bug for win and darwin too

    - version 34 (08.08.2020)
    Added support for 32bit sized trim area units (as trim area api changed in xperia mark 2 line) (not yet released because of bug)

    - version 35 (08.08.2020)
    Updated support for 32bit sized trim area units (as trim area api changed in xperia mark 2 line); Move trim area dumps out of root folder so it not get acidentaly flashed, dumps is now inside folder tadump

    - version 36 (27.08.2020)
    Some improvements and and possible bug fixes

    - version 37 (09.12.2020)
    Added support for Xperia 5 II with emmc instead of ufs (not working)

    - version 38 (10.12.2020)
    Fixed impropper implementation from v37

    - version 39 (13.12.2020)
    Since mark 2 devices protocol is changed a bit and on some devices OKAY reply is not in separated usb poacket, instead it is merged with data packet, added support for it

    - version 40 (03.01.2021)
    Temporary solution for determining partition 0 sin file caused by two diferent emmc csd info we found recently on mark 2 devices

    - version 41 (03.01.2021)
    Removed temporary solution from version 41 so right lun0 sin file get flashed and seccond lun0 get skipped or booth skipped if lun0 sin file do not match device storage size

    - version 42 (11.03.2021)
    Fix bug in flashing booth slots when current slot is A, thanks to @chrisrg for discovering bug!

    - version 43 (12.06.2021)
    Support for Mark 3 devices

    - version 44 (19.06.2021)
    Fully Mark III device implementation

    - version 45 (20.06.2021)
    Implemented battery level check and prompt user to take a risk and continue flashing or stop flasing if battery level is less than 15 percent

    - version 46 (08.07.2021)
    Fix problem with filenames which contain "_other", it need to be always flashed to the diferent slot

    - version 47 (15.07.2021)
    Removed prompt for persist.sin flashing, now its by default skip. Implemented bootloader log retrieval at the end of flashing for better understanding when something goes wrong. Implemented firmware log history retrieval for those who want to know history of the flashed firmwares

    - version 48 (19.07.2021)
    Flash bootloader,bluetooth,dsp,modem,rdimage to booth slots only on a,b devices

    - version 49 (31.07.2021)
    Support for XQ-BT41

    - version 50 (12.08.2021)
    Workin progress on asynchronous usb to make it more like synchronous, added progress bar during send-receive usb packets and more logging. Increased usb timeout to 2 minute. Trying fix sync command at the end of flashing as reported here -> https://github.com/munjeni/newflasher/issues/42

    - version 51 (12.08.2021)
    Fix empry line printed while receiving usb packets, thanks @elukyan

    - version 52 (01.10.2021)
    Implemented userprompt for keeping userdata, thanks @OhayouBaka for figuring out! Removed bootloader log retrieval

    Credits:

    - without @tanipat and his pc companion debug logs this tool will never be possible! Thank you a lot for your time providing me logs! (by the influence of others, He was disappointed me with last post, but I still appreciate his help and can't forget it)
    - without @thrash001 who helped testing our tool I never be continue building our tool since I don't have device for testing, thanks mate!
    - didn't forgot @beenoliu, thanks mate for testing!
    - thanks to @porphyry for testing linux version!
    - thanks to @Snow_Basinger for providing sniff log from 2018 device and for testing on his 2018 device
    - thanks to @frantisheq for testing newflasher on his 2018 device and for notify about doublefree bug
    - thanks to @serajr for providing me some logs which helped me to figure out some things related to 2018 devices
    - thanks to @noelex for helping in Xperia 1 implementation
    - thanks to @Meloferz for testing on his xperia 1 mark II
    - thanks to github contributors, testers and reporters: vog, noelex, TheSaltedFish, solarxraft, pbarrette, MartinX3, kholk
    - thanks to Chirayu Desai for tracking addition to Debian and thanks to vog for initiating all that
    - thanks to @elukyan for testing and providing me usb sniff logs for mark 3 devices imlementation, thank you so much

    Common errors and how to solve:
    https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-72610228

    Source code:

    https://github.com/munjeni/newflasher
    20
    Please remember something, I made newflasher for all you, I didn't made it for me remember that, I dodn't ask for money for my work, all is for free, all is done in my spare time and for free, I have made everything just to make all you happy, remember that! I must say something more, some xda members, including some moerators, don't appreciate my effort, thats shame. I lost my recognised developer / recognised contributor title because ot that guys, I allways must remind all you that.

    Enjoy flashing! Cheers! ;)
    14
    V14 is out, added Xperia 1 support (curently untested!)

    If you flash partitions please give me newflasher log, need to know if I implemented things right!
    12
    New version is out!
    11
    New version is out! Changelog:
    - implemented flash driver, just double click exe and folow procedure (optional step)
    - trim area dump (optional step and maybe not a functional! Need confirmation.)

    Do not use any old newflasher, its soo old and definitelly not a better than latest one! Folow my instructions and put a trust on me, I am developer of the newflasher and nobody know that better than me, if you have a questions just ask here! I have removed my posts because virus tolal found a malware on all my exe files. Later I found what was going on. UPX (any version) contain the same malware, but since my exe was packed with upx all my exe contain the same malware, reason was UPX! Have no idea why virustotal see upx as a malware but I need now to recompile all my exe without using upx just because I no want to risk with it, don't know if that upx is false warining or not but definitelly better idea omiting upx.