[TOOL] Newflasher (xperia command line flasher)

Search This thread
By:
Advanced…
Traace

Traace

Senior Member
Mar 13, 2010
440
115
Newflasher is refusing to flash anything to my phone at all... while Flashtool can. What is going on?

Steps I followed:

Optional Step 1: Installed the drivers

Step 1: Downloaded the right firmware and placed newflasher.exe into the Firmware Directory next to .ta , .sin, boot, partition

Step 2: Put phone in Flash Mode, connected it to the pc and start newflasher.exe

Wait Wait Wait but nothing happens at all. Not after 2 min, not after 5 min, not after 20 min, never...


Logs:
--------------------------------------------------------
newflasher.exe v55 by Munjeni @ 2017/2020
--------------------------------------------------------

Determining available free space by GetDiskFreeSpaceEx:

Available space to caller = 112755 MB
Total space on current drive = 299239 MB
Free space on drive = 112755 MB

Optional step! Type 'y' and press ENTER if you need GordonGate flash driver, or type 'n' to skip.
This creates GordonGate driver installer in the same dir with newflasher.exe!
 
munjeni

munjeni

Senior Member
Jun 2, 2011
9,622
22,306
The rest of log? Phone model? Next to it, driver installed? Checked in device mannager correctness of the driver? Usb cable ok? Phone usb port ok? Sony pc companion software shut down? And also checked task bar if it is realy shut down? Etc...
 
Last edited:
  • Like
Reactions: sieghartRM
J

janolucero

Senior Member
Oct 11, 2009
141
29
Santiago
Sony Xperia XZ2 Compact
Xperia XZ2
hi @munjeni please guide me.
I have an Xperia 5 II XQ-AS52 (europe) firmware 58.2.A.10.126
Sadly I flashed japanese firmware XQ-AS42 v58.2.A.10.163 thinking it was a better one than the older europe release.
The problem is I can't go back to the euro firmware because if I flash it my phone go in a loop and says " your device is corrupt it cant be trusted and will not boot"
If I boot the japanese firmware my phone reads both sim cards but none of them have signal. I have tried flashing older firmwares but the problem persist and tried to fix it with xperia companion but it says "temporary device incompatibility" and shows me my phone info. Even if I flashed an older android version it stills shows the japanese one.
This is what Companion says:

Temporary device incompatibility detected​

Could not perform the selected operation at this time. Please try again later.
UEGetPhoneInfoARBHigh
XQ-AS52 3530 43040143 58.2.A.10.163
2.18.6.0 / Windows 10 Home 64 bit / Win64 / US / /

Please help me.
 
munjeni

munjeni

Senior Member
Jun 2, 2011
9,622
22,306
Sorry I have old xperia 10 and I can't help, what I know about "your device is corrupt..." mean rolback protection cause that. The only way to bypass that is see post 4 !
 
  • Like
Reactions: sieghartRM and janolucero
smudgy636

smudgy636

New member
Mar 13, 2022
3
0
hey, i have an xperia 5 iv, if i flash the latest firmware without the user data file is there a way of keeping root or will i have to root again?
 
RyTekk

RyTekk

Senior Member
Aug 17, 2012
1,142
573
Nha Trang
janolucero said:
hi @munjeni please guide me.
I have an Xperia 5 II XQ-AS52 (europe) firmware 58.2.A.10.126
Sadly I flashed japanese firmware XQ-AS42 v58.2.A.10.163 thinking it was a better one than the older europe release.
The problem is I can't go back to the euro firmware because if I flash it my phone go in a loop and says " your device is corrupt it cant be trusted and will not boot"
If I boot the japanese firmware my phone reads both sim cards but none of them have signal. I have tried flashing older firmwares but the problem persist and tried to fix it with xperia companion but it says "temporary device incompatibility" and shows me my phone info. Even if I flashed an older android version it stills shows the japanese one.
This is what Companion says:

Temporary device incompatibility detected​

Could not perform the selected operation at this time. Please try again later.
UEGetPhoneInfoARBHigh
XQ-AS52 3530 43040143 58.2.A.10.163
2.18.6.0 / Windows 10 Home 64 bit / Win64 / US / /

Please help me.
Click to expand...
Click to collapse
Try to copy partition folder from japanese firmware to the europe one and do flashing again. I met this issue on Xperia 5 and solved it by this way (but just on android 10, it doesn't seem to work on android 11).
 

Attachments

  • DSC_0451.JPG
    DSC_0451.JPG
    1.9 MB · Views: 31
  • 2023-02-23_8-22-11.jpg
    2023-02-23_8-22-11.jpg
    55.9 KB · Views: 30
H

heiiji

New member
Nov 11, 2019
3
0
hi, @munjeni, i encountered an issue while trying to downgrade Xperia 5 iii from A13 to A11, using newflasher.exe version 55, below is the log:
after newflasher failed ,i also tried the xperifirm + flashtool , also failed, please help me out. thanks!!

Code: 
 - Extracting sparse chunk super.010
 - Uploading sparse chunk D:\documents\Sony\xperia5iii\resource\XQ-BQ72_Customized HK_61.1.A.11.88\decrypted\flash_session\super.010
      download:06306b39
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
 - Error write! Need nBytes: 0x200000 but done: 0x0
nBytes[0x0]:


         Error uploading chunk 9!
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
 - Error write! Need nBytes: 0xe but done: 0x0
nBytes[0x0]:


Error writing commad: Read-TA:2:2475

ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
 - Error write! Need nBytes: 0xc but done: 0x0
nBytes[0x0]:


Error writing command 'set_active:a'!
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
 - Error write! Need nBytes: 0x4 but done: 0x0
nBytes[0x0]:


 - Error writing command Sync!
Closing device.
Press any key to continue . . .

this is the flashtool log:

Code: 
16/018/2023 06:18:31 - INFO  - Selected Bundle for Sony Xperia 5 III(XQ-BQ72). FW release : 61.1.A.11.88. Customization : SONY_HK
16/018/2023 06:18:31 - INFO  - Preparing files for flashing
16/019/2023 06:19:20 - INFO  - Please connect your device into flashmode.
16/019/2023 06:19:37 - INFO  - Using Gordon gate drivers version 3.1.0.0
16/019/2023 06:19:38 - INFO  - USB buffer size set to 512K
16/019/2023 06:19:38 - INFO  - Opening device for R/W
16/019/2023 06:19:38 - INFO  - Device ready for R/W.
16/019/2023 06:19:38 - INFO  - Reading device information
16/019/2023 06:19:38 - INFO  - Reading phone properties
16/019/2023 06:19:38 - INFO  - Sending getvar:product
16/019/2023 06:19:38 - INFO  -    getvar status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:2202
16/019/2023 06:19:38 - INFO  -    Read-TA status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:2205
16/019/2023 06:19:38 - INFO  -    Read-TA status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:2210
16/019/2023 06:19:38 - INFO  -    Read-TA status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:4900
16/019/2023 06:19:38 - INFO  -    Read-TA status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:10021
16/019/2023 06:19:38 - INFO  -    Read-TA status : FAIL
16/019/2023 06:19:38 - WARN  -    FAILUnit 10021 does not exist ( Hex unit value 00002725 )
16/019/2023 06:19:38 - INFO  - Connected device : XQ-BQ72 / SW release 61.2.G.0.33 / Customization Unknown
16/019/2023 06:19:38 - INFO  - Last flash date : null
16/019/2023 06:19:38 - INFO  - Phone ready for flashmode operations.
16/019/2023 06:19:38 - INFO  - Start Flashing
16/019/2023 06:19:38 - INFO  - Parsing boot delivery
16/019/2023 06:19:38 - ERROR - null
16/019/2023 06:19:38 - INFO  - Sending Sync
16/019/2023 06:19:38 - INFO  -    Sync status : OKAY
16/019/2023 06:19:38 - INFO  - Sending powerdown
16/019/2023 06:19:38 - INFO  -    powerdown status : OKAY
16/019/2023 06:19:42 - INFO  - Device disconnected
16/019/2023 06:19:43 - INFO  - Device connected in flash mode
 
Pandemic

Pandemic

Senior Member
Aug 30, 2010
24,198
23,218
Meppel
talk.sonymobile.com
Samsung Galaxy Tab A series
Xperia XZ2
  • Like
Reactions: munjeni
munjeni

munjeni

Senior Member
Jun 2, 2011
9,622
22,306
heiiji said:
hi, @munjeni, i encountered an issue while trying to downgrade Xperia 5 iii from A13 to A11, using newflasher.exe version 55, below is the log:
after newflasher failed ,i also tried the xperifirm + flashtool , also failed, please help me out. thanks!!

Code: 
 - Extracting sparse chunk super.010
 - Uploading sparse chunk D:\documents\Sony\xperia5iii\resource\XQ-BQ72_Customized HK_61.1.A.11.88\decrypted\flash_session\super.010
      download:06306b39
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
 - Error write! Need nBytes: 0x200000 but done: 0x0
nBytes[0x0]:


         Error uploading chunk 9!
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
 - Error write! Need nBytes: 0xe but done: 0x0
nBytes[0x0]:


Error writing commad: Read-TA:2:2475

ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
 - Error write! Need nBytes: 0xc but done: 0x0
nBytes[0x0]:


Error writing command 'set_active:a'!
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
 - Error write! Need nBytes: 0x4 but done: 0x0
nBytes[0x0]:


 - Error writing command Sync!
Closing device.
Press any key to continue . . .

this is the flashtool log:

Code: 
16/018/2023 06:18:31 - INFO  - Selected Bundle for Sony Xperia 5 III(XQ-BQ72). FW release : 61.1.A.11.88. Customization : SONY_HK
16/018/2023 06:18:31 - INFO  - Preparing files for flashing
16/019/2023 06:19:20 - INFO  - Please connect your device into flashmode.
16/019/2023 06:19:37 - INFO  - Using Gordon gate drivers version 3.1.0.0
16/019/2023 06:19:38 - INFO  - USB buffer size set to 512K
16/019/2023 06:19:38 - INFO  - Opening device for R/W
16/019/2023 06:19:38 - INFO  - Device ready for R/W.
16/019/2023 06:19:38 - INFO  - Reading device information
16/019/2023 06:19:38 - INFO  - Reading phone properties
16/019/2023 06:19:38 - INFO  - Sending getvar:product
16/019/2023 06:19:38 - INFO  -    getvar status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:2202
16/019/2023 06:19:38 - INFO  -    Read-TA status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:2205
16/019/2023 06:19:38 - INFO  -    Read-TA status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:2210
16/019/2023 06:19:38 - INFO  -    Read-TA status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:4900
16/019/2023 06:19:38 - INFO  -    Read-TA status : OKAY
16/019/2023 06:19:38 - INFO  - Sending Read-TA:2:10021
16/019/2023 06:19:38 - INFO  -    Read-TA status : FAIL
16/019/2023 06:19:38 - WARN  -    FAILUnit 10021 does not exist ( Hex unit value 00002725 )
16/019/2023 06:19:38 - INFO  - Connected device : XQ-BQ72 / SW release 61.2.G.0.33 / Customization Unknown
16/019/2023 06:19:38 - INFO  - Last flash date : null
16/019/2023 06:19:38 - INFO  - Phone ready for flashmode operations.
16/019/2023 06:19:38 - INFO  - Start Flashing
16/019/2023 06:19:38 - INFO  - Parsing boot delivery
16/019/2023 06:19:38 - ERROR - null
16/019/2023 06:19:38 - INFO  - Sending Sync
16/019/2023 06:19:38 - INFO  -    Sync status : OKAY
16/019/2023 06:19:38 - INFO  - Sending powerdown
16/019/2023 06:19:38 - INFO  -    powerdown status : OKAY
16/019/2023 06:19:42 - INFO  - Device disconnected
16/019/2023 06:19:43 - INFO  - Device connected in flash mode
Click to expand...
Click to collapse
Log is incomplete and I have no idea about what is at the start of log! You should try USB2.0 port insted of USB3.X, also check for dust inside your phone usb port, also check usb cable, also try another usb cable... etc
 
You must log in or register to reply here.

Similar threads

A
[TOOL] [UPDATE 04/09/2015] Flashtool version 0.9.19.10 - Windows / Linux / Mac
Replies
4K
Views
5M
M
MiniGNU
IgorEisberg
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5]
Replies
3K
Views
3M
L
lm8lm8
zxz0O0
Easy Root Tool for various Xperia devices
Replies
2K
Views
1M
L
lawrenceh
DooMLoRD
[Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318]
Replies
130
Views
969K
F
funnydoc
Toledo_JAB
  • Poll
[GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick
Replies
2K
Views
576K
E
evilhedrox

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    munjeni
    munjeni
    What about this https://forum.xda-developers.com/t/...cve-2020-0041-including-magisk-setup.4146103/ is it working ? My xperia 10 dieid and I bought used one and on my surprise its locked, bootloader never unlocked, and now I'm searching for temp root exploit it order to continue my work on figuring out how DK key is working on device
    View
    1
    Pandemic
    Pandemic
    munjeni said:
    What about this https://forum.xda-developers.com/t/...cve-2020-0041-including-magisk-setup.4146103/ is it working ?
    Click to expand...
    Click to collapse
    Dunno bro never tried it and i have xperia 1 mark 3 and that is for Xperia 1 and with your xperia 10 ? No bro dont do that, its jnly for Xperia 1 and 5, better patch your boot.img like i always do to avoid that., Just a tip 🫶💪
    View
  • 338
    munjeni
    munjeni
    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

    - version 53, 54, 55 (20.0822022)
    Fix trimarea dumper crash on big endian machines, update building makefiles

    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
    View
    20
    munjeni
    munjeni
    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! ;)
    View
    14
    munjeni
    munjeni
    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!
    View
    12
    munjeni
    munjeni
    New version is out!
    View
    11
    munjeni
    munjeni
    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.
    View

New posts