[TOOL] Newflasher (xperia command line flasher)

Search This thread

louisbloomm

New member
May 15, 2022
2
0
hi,
i have a xperia 1 mark 3 xq-bc72, after recent android 12 update my phone started to bootloop and got the 'your device is corrupt...' message.
i read this whole forum and tried sony companion first but no success. so i tried with newflasher many times with fw for xq-bc72 (i tried all different regions) but no matter what i do its not working for me and phone keeps bootlooping until the corrupt message appears, can anyone help i dont know what im doing wrong.
 

Attachments

  • logg.txt
    35.4 KB · Views: 12

munjeni

Senior Member
Jun 2, 2011
9,524
22,174
hi,
i have a xperia 1 mark 3 xq-bc72, after recent android 12 update my phone started to bootloop and got the 'your device is corrupt...' message.
i read this whole forum and tried sony companion first but no success. so i tried with newflasher many times with fw for xq-bc72 (i tried all different regions) but no matter what i do its not working for me and phone keeps bootlooping until the corrupt message appears, can anyone help i dont know what im doing wrong.
I don't want to repeat about "rollback protection" just read whole page 105!! In your log I have found

NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1322-1669_X_Boot_SM8350_LA2.0_S_104, cdf_version:Unknown: Mar 23 2022/17:47:07, fs_version:Unknown: Mar 23 2022/17:47:07, sw_version:61.1.A.7.35

try download excatly the same firmware, also try the same firmware but for diferent regions one will probably boot. If nothing help read post 4 -> https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-72610228
 
Last edited:

louisbloomm

New member
May 15, 2022
2
0
I don't want to repeat about "rollback protection" just read whole page 105!! In your log I have found

NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1322-1669_X_Boot_SM8350_LA2.0_S_104, cdf_version:Unknown: Mar 23 2022/17:47:07, fs_version:Unknown: Mar 23 2022/17:47:07, sw_version:61.1.A.7.35

try download excatly the same firmware, also try the same firmware but for diferent regions one will probably boot. If nothing help read post 4 -> https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-72610228
Thanks for the reply, that is what I did exactly though. the day my phone started to bootloop i was ota updated to 61.1.A.7.35 a few hours earlier.
So i literally tried every fw region version of that build with no success even tried the set active a with command but still just bootloops. I don't mind unlocking bootloader and going that route but I don't know how to unlock
 

john615

New member
May 18, 2022
3
0
How do I flash an FTF file? I have an FTF file for Xperia Pro. I've already unlocked bootloader. Can I do this with newflasher?
 

munjeni

Senior Member
Jun 2, 2011
9,524
22,174
Thanks for the reply, that is what I did exactly though. the day my phone started to bootloop i was ota updated to 61.1.A.7.35 a few hours earlier.
So i literally tried every fw region version of that build with no success even tried the set active a with command but still just bootloops. I don't mind unlocking bootloader and going that route but I don't know how to unlock
Try switch to slot B! If you mind to unlock here is step by step https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader
 
  • Like
Reactions: sieghartRM
May 19, 2022
5
0
Hi guys
Recently i updated my Xperia 10 ii (xq-au52) from Android 11 (59.1.A.2.232) to Android 12 (59.2.A.0.422).
I want to go back to 11.
I downloaded newflasher and a firmware from xperifirm.
The firmware i downloaded is XQ-AU42_MVNO JP_59.1.A.4.177-R4B.
I think it's the closest to the version i had before updating. (It was the SEA version btw)
I know it'll probably sound dumb but i have no clue what to do now.
Idk if that's the right firmware.
Idk how to put phone in flash mode.
Please may someone help me.
Thanks in advance.
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,524
22,174
Hi guys
Recently i updated my Xperia 10 ii (xq-au52) from Android 11 (59.1.A.2.232) to Android 12 (59.2.A.0.422).
I want to go back to 11.
I downloaded newflasher and a firmware from xperifirm.
The firmware i downloaded is XQ-AU42_MVNO JP_59.1.A.4.177-R4B.
I think it's the closest to the version i had before updating. (It was the SEA version btw)
I know it'll probably sound dumb but i have no clue what to do now.
Idk if that's the right firmware.
Idk how to put phone in flash mode.
Please may someone help me.
Thanks in advance.
You want to restore the firmware to an older version? Don't do that! Rolback protection not allow downgrade, and your phone will not boot! We have already spent 3 pages on it, feel free to read before you decide on the next step! I really don’t want to repeat myself.

How to put phone in flash mode? Simply power off phone first, than connect usb cable to the phone, than while keeping volume down button connect another side of the cable to the PC, you will notice green light on phone, thats indication for flash mode, now release volume buton and you are in flash mode. You must have right driver on your pc for flash mode so before putting phone in flash mode install driver first! How to install driver? Simply run newflasher, it will ask you for "extract gordon gate driver", simply confirm with "y" and press enter, driver will be extracted to the same folder with newflasher. Install driver and thats it. About flashing phone with newflasher google it! Have a ton of tutorials on the net about how to flash phone with newflasher, simply read.
 
Last edited:
May 19, 2022
5
0
You want to restore the firmware to an older version? Don't do that! Rolback protection not allow downgrade, and your phone will not boot! We have already spent 3 pages on it, feel free to read before you decide on the next step! I really don’t want to repeat myself.

How to put phone in flash mode? Simply power off phone first, than connect usb cable to the phone, than while keeping volume down button connect another side of the cable to the PC, you will notice green light on phone, thats indication for flash mode, now release volume buton and you are in flash mode. You must have right driver on your pc for flash mode so before putting phone in flash mode install driver first! How to install driver? Simply run newflasher, it will ask you for "extract gordon gate driver", simply confirm with "y" and press enter, driver will be extracted to the same folder with newflasher. Install driver and thats it. About flashing phone with newflasher google it! Have a ton of tutorials on the net about how to flash phone with newflasher, simply read.
Thank you very much for your help. So there's no way to get back to Android 11? That's sad :(
My phone came from factory running Android 10. I guess there's no way to go back to that also, right? I'm stuck on Android 12?
Feels bad man. I really didn't like this new update. Anyways. Thank you for warning me. Thanks for helping me.
 

munjeni

Senior Member
Jun 2, 2011
9,524
22,174
Thank you very much for your help. So there's no way to get back to Android 11? That's sad :(
My phone came from factory running Android 10. I guess there's no way to go back to that also, right? I'm stuck on Android 12?
Feels bad man. I really didn't like this new update. Anyways. Thank you for warning me. Thanks for helping me.
There is a way! Unlock bootloader, flash, relock bootloader. Relocknig bootloader after flashing reset roolback protection index to zero so you can boot for example old firmware. Before you decide to unlock bootloader do in mind every device have unique device key hidden under phone, when you unlock bootloader those key get forewer deleted so even relocking bootloader those key is no back! Some device models can't relock bootloader like my xperia 10 without mark, so before everyhing read twice xda treads or ask someone in proper forum to get idea what you lost or what you benefit. In you need info about if your device can be relocked also ask in proper forum. Hope this help
 
May 19, 2022
5
0
There is a way! Unlock bootloader, flash, relock bootloader. Relocknig bootloader after flashing reset roolback protection index to zero so you can boot for example old firmware. Before you decide to unlock bootloader do in mind every device have unique device key hidden under phone, when you unlock bootloader those key get forewer deleted so even relocking bootloader those key is no back! Some device models can't relock bootloader like my xperia 10 without mark, so before everyhing read twice xda treads or ask someone in proper forum to get idea what you lost or what you benefit. In you need info about if your device can be relocked also ask in proper forum. Hope this help
Wait, that's great news. :) I'm definitely going to try. I'm aware of the risks, thanks for warning me.
On Sony Developer World website there's a tutorial on how to unlock the bootloader. After doing that i can flash the phone normally, is that what you meant?
If yes,then my only concern is if the firmware version i mentioned before.
Should I worry about that?
Idk if it has a region or carrier block or something like that.
Excuse my English btw, I'm still learning.
And thanks again for being so helpful.
 

munjeni

Senior Member
Jun 2, 2011
9,524
22,174
Wait, that's great news. :) I'm definitely going to try. I'm aware of the risks, thanks for warning me.
On Sony Developer World website there's a tutorial on how to unlock the bootloader. After doing that i can flash the phone normally, is that what you meant?
If yes,then my only concern is if the firmware version i mentioned before.
Should I worry about that?
Idk if it has a region or carrier block or something like that.
Excuse my English btw, I'm still learning.
And thanks again for being so helpful.
Yes you can flash any rom for your phone model! Procedure is a bit diferent since rollback protection need to be bypassed in order to flash older rom, procedure is: unlock bootloader, probably your device will boot after that, if not booting try to relock bootloader first, when bootloader is relocked rolback index is reset to zero and rollback protection is bypassed so your device probably will boot with your current rom. But before you unlock bootloader search on xda look for what you gain and what you lose when bootloader is unlocked. In my opinion if your bootloader is relockable I see no reason for keeping bootloader locked. For example my xperia 10 no mark do not have bootloader relock feature, what I was lost after unlocking bootloader is I can't connect anymore my phone to smart tv trought wifi since secure protocol is missing. Whats going on after relocking bootloader I don't know, so search xda before anything!
 
Last edited:
May 19, 2022
5
0
Yes, I'll search. I've been reading a lot lately. There's so much things i still don't understand. One thing I learned is that it's irreversible and side effects are unpredictable.
The general idea of the process i have is this:
Unlock bootloader
Phone will be wiped clean and then restart still with Android 12
Flash firmware
Phone will restart with Android 11
Lock bootloader
Phone will restart again with Android 11 and locked bootloader.
That's if everything goes well. Is that correct?
I really don't want to mess up anything. I really love my device, also it was very expensive. I'm going to try only after I feel confident enough. All that aside, thank you for your time, patience and help. I really appreciate that.
 

munjeni

Senior Member
Jun 2, 2011
9,524
22,174
Yes, I'll search. I've been reading a lot lately. There's so much things i still don't understand. One thing I learned is that it's irreversible and side effects are unpredictable.
The general idea of the process i have is this:
Unlock bootloader
Phone will be wiped clean and then restart still with Android 12
Flash firmware
Phone will restart with Android 11
Lock bootloader
Phone will restart again with Android 11 and locked bootloader.
That's if everything goes well. Is that correct?
I really don't want to mess up anything. I really love my device, also it was very expensive. I'm going to try only after I feel confident enough. All that aside, thank you for your time, patience and help. I really appreciate that.
I can't tell you for sure since I'm owning Xperia 10, but thats confirmed on another models see https://forum.xda-developers.com/t/...-xq-at51-with-flashtool.4119707/post-84509417 and might be the same for the rest of devices which have relock bootloader feature activated inside bootloader, first off all things take a look in your device subforum and check for if your device is relockable! My xperia 10 was not relockable and I was hurried to unlock bootloader and it cost me that my wifi connection to the smart tv doesn't work anymore because my bootloader is unlocked
 
May 19, 2022
5
0
I can't tell you for sure since I'm owning Xperia 10, but thats confirmed on another models see https://forum.xda-developers.com/t/...-xq-at51-with-flashtool.4119707/post-84509417 and might be the same for the rest of devices which have relock bootloader feature activated inside bootloader, first off all things take a look in your device subforum and check for if your device is relockable! My xperia 10 was not relockable and I was hurried to unlock bootloader and it cost me that my wifi connection to the smart tv doesn't work anymore because my bootloader is unlocked
Thanks for pointing me to the right direction.
Very interesting reading.
As I learn more about this procedure, I'm starting to rethink my decision. I was so worried if i could or not, that i didn't really think if i should or not. Yes, it's possible. But there's a price. And also all the risks.
This new Android 12 is ugly.
But maybe it's better have a fully functional ugly phone than having a beautiful mess. Idk if that makes sense. I'll report back if I change my mind someday.
In any case, I'm more than thankful for your help and support. Thank you thank you thank you.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Anyone tried this on a Chromebook ? Just asking for a friend :)
    Is it android variant? If not you shoul compile newflasher using cross compiler for that os
    2
    Than one of the arm binaries should work, probably arm64 but also if it is android variant maybe pie binary should work too
    2
    Where i can find it bro or someone can make it for me and share it :( ?
    Inside newflasher_v52.zip from the first post! There is arm32, arm64 and arm64_pie, so 3 diferent binaries for arm platform, one of those 3 should work
    1
    The same as you doing on windows, diferencie is only platform! So as like you doing with any native binary on linux/android, chmod first, than the rest of steps is the same as windows version, put fw in an folder, put binary in the same folder, chmod binary, than trought adb shell or trought terminal emulator just execute binary and it will start the same like it start on windows platform. You need to become root first otherwise binary will not have enought permission to comunicate trought usb.
    1
    Hi,
    I messed up my XZ2. it was on Stock ROM, rooted with Magisk and I wanted to pass the SafetyNet checks and used MagiskHide Props config to spoof the fingerprint, result was a non booting device .-(
    I managed to boot into TWRP, but can't restore a backup from TWRP. Trying to flash the FW again is not successful, attached is a newflasher dump file.
    The error is probably this line:
    ERROR: boot_a: Hash of data does not match digest in descriptor.
    but I don't know what to do now.
    Any idea?
    Thanks

    Forgot to attach the dump file​

    Hm, I can't attach a file ?​

    from the file:​

    VB: RWDeviceState: Succeed using rpmb!
    Boot counter is 926
    XBoot Init
    Init XBootPALAPILib
    Init TA API Lib
    XBOOT (1310-7079_X_Boot_SDM845_LA2.0.1_Q_207)
    [WARNING @ ta_interface.c:109]:
    Unable to read TA unit 66667, error=4
    [ERROR @ xboot_glue.c:107]:
    read_ta returned err=-22
    [ERROR @ xboot_glue.c:526]:
    get_dk returned err=-22
    Reading 321 bytes from RPMB, OK
    Reading 321 bytes from RPMB, OK
    XDeviceTreeAddrExtract start
    no check attributes (Mode 3)
    LoadImageAndAuth: 1615: CurrentSlot.Suffix=_a
    Not updating rollbackindex as current slot is unbootable
    Invalid vm-linux partition
    load_and_verify_vbmeta:481: DEBUG: Loading vbmeta struct from partition 'vbmeta_a'.
    load_and_verify_hash_partition:181: DEBUG: boot_a: Loading entire partition.
    load_and_verify_hash_partition:236: ERROR: boot_a: Hash of data does not match digest in descriptor.
    load_and_verify_hash_partition:181: DEBUG: dtbo_a: Loading entire partition.
    load_and_verify_hash_partition:240: DEBUG: dtbo_a: success: Image verification completed
    Loading Image Start : 2805 ms
    Loading Image Done : 2805 ms
    Total Image Read size : 4096 Bytes
    Loading Image Start : 2806 ms
    Loading Image Done : 2836 ms
    Total Image Read size : 16080896 Bytes

    Upload as zip file works
    Not updating rollbackindex as current slot is unbootable
    Invalid vm-linux partition
    load_and_verify_vbmeta:481: DEBUG: Loading vbmeta struct from partition 'vbmeta_a'.
    load_and_verify_hash_partition:181: DEBUG: boot_a: Loading entire partition.
    load_and_verify_hash_partition:236: ERROR: boot_a: Hash of data does not match digest in descriptor.

    Looks like magisk messed your boot partition! You just need to reflash boot partition, but looks like whole slot is messed up so you will need to flash partition.sin too! If that not help reflash whole firmware including all .ta. all .sin, partition, bootdelivery. Never mix sin files trought two-few firmwares, always use one firmware and don't modify/delete anything. If you can't get it to work, post newflasher log
  • 330
    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.