[Sony Cross-Device General] munjeni:
I found that we can improve newflasher and make them fully safe! I can make test version and move "erase" command till before command "flash", if working by that way we have newflasher more safe because chances for usb connection lost or user cancel interacion, or something goes wrong...etc booth minimize chance for hard bricks because these two hard commands is at the end of upload process so if something goes wrong these two commands will not execute which gives us chance to say "oh oh time for stop flashing"! :) If you want I can make test version again! Let me know please if somebody ready to test!

Edit:

here is test version, please flash only cache.sin and kernel.sin, give me log please! Let explain you what I mean, see this log for referencie https://xdaforums.com/showpost.php?p=72691859&postcount=217 , for example lets use this part:

Processing amss_fs_2_X.sin
- setting up infflate...
- infflating, please wait...

- infflate returned: 0
- gzpipe: ok.
- gunziped ok.
- Extracting from amss_fs_2_X.sin
- Extracting signature flash_session/modemst2.cms
- Uploading signature flash_session/modemst2.cms
signature:00000536
OKAY.
[COLOR="Red"]erase:modemst2[/COLOR]
OKAY.
- Extracting sparse chunk flash_session/modemst2.000
- Uploading sparse chunk flash_session/modemst2.000
download:00000400
OKAY.
flash:modemst2
OKAY.
- End of amss_fs_2_X.sin

Red part. By default I have used thing the same like it is done on sony pc companion. By default command "erase" erases partition before command "download", but lets say what will happen if download fail, or usb cable acidentaly disconnect, process stop somehow, sin extraction fail somehow, inflate fail somehow...etc? Bad thing will happen for sure because partition is erased by "erase" command! :) But we can improve thing a bit, for example we can move command erase to section before command flash! For example it will look like this:

Processing amss_fs_2_X.sin
- setting up infflate...
- infflating, please wait...

- infflate returned: 0
- gzpipe: ok.
- gunziped ok.
- Extracting from amss_fs_2_X.sin
- Extracting signature flash_session/modemst2.cms
- Uploading signature flash_session/modemst2.cms
signature:00000536
OKAY.
- Extracting sparse chunk flash_session/modemst2.000
- Uploading sparse chunk flash_session/modemst2.000
download:00000400
OKAY.
[COLOR="Blue"]erase:modemst2[/COLOR]
OKAY.
flash:modemst2
OKAY.
- End of amss_fs_2_X.sin

Much safer?? Hope you agree. :) By that way I think we have elimintated chance for hard brick for 99 percent because command "erase" is now before command "flash" (command "flash" is last command in proccess which is nothing than command "confirm flash", for example if something goes wrong without command "flash" whole process is abort, thats how things working in new flashing protocol) !

Problem might be only and only system.sin and cache.sin because it contain more chunks so erase command will go in chunk.000 and if e.g. chunk.001 somehow fail device will go softbricked only instead of hardbrick! System or cache can't hard brick device, everybody know that.

- infflate returned: 0
- gzpipe: ok.
- gunziped ok.
- Extracting from system_X.sin
- Extracting signature flash_session/system.cms
- Uploading signature flash_session/system.cms
signature:00000b3a
OKAY.
- Extracting sparse chunk flash_session/system.000
- Uploading sparse chunk flash_session/system.000
download:063ff034
OKAY.
[COLOR="Red"] erase:system[/COLOR]
OKAY.
flash:system
OKAY.
- Extracting sparse chunk flash_session/system.001
- Uploading sparse chunk flash_session/system.001
download:063ff7e8
OKAY.
flash:system
OKAY.
- Extracting sparse chunk flash_session/system.002
- Uploading sparse chunk flash_session/system.002
download:063ff018
OKAY.
flash:system
OKAY.
- Extracting sparse chunk flash_session/system.003
- Uploading sparse chunk flash_session/system.003
download:063ffec8
OKAY.
flash:system
OKAY.
- Extracting sparse chunk flash_session/system.004
- Uploading sparse chunk flash_session/system.004
download:063ff220
OKAY.
flash:system
OKAY.
- Extracting sparse chunk flash_session/system.005
- Uploading sparse chunk flash_session/system.005
download:063ff118
OKAY.
flash:system
OKAY.
- Extracting sparse chunk flash_session/system.006
- Uploading sparse chunk flash_session/system.006
download:063ff508
OKAY.
flash:system
OKAY.

As you can see all other files like modem, bootloader, partition, amss...etc contain only one chunk which is more than great, chances for hard brick is 1 percent only (if flashed wrong firmware, or if flashing interupted because of empty battery) :)

That thing I done now in test version, let me know please!