[TOOL] Newflasher (xperia command line flasher)

Search This thread

dima_vy

Senior Member
Aug 13, 2009
108
5
Hi!
I'm not sure, that this the right thread to ask, but, I will try my luck here also😊
I have xperia 5iii from UK. I live in Israel. The phone can't turn on volte. I know that xperia 1IV works in Israel fine. So the question is - can I replace modem files in firmware folder of my phone with the files from xperia 1 IV and flash it with newflasher?
Thank you
 

munjeni

Senior Member
Jun 2, 2011
9,652
22,323
Determining available free space by GetDiskFreeSpaceEx:

Available space to caller

= 110717 MB Total space on current drive 190775 MB

Free space on drive

- 110717 MB

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

Device path: \\?\usb#vid_efce&pid_beeb#5&3b19be35&0&2#{a5dcbf18-6530-11d2-901f-80c84fb951ed} Class Description: libusb-win32 devices

Device Instance ID: USB\VID_OFCE&PID_B00B\5&38198E35&0&2

Optional step! Type 'y' and press ENTER if you want dump trim area, or type 'n' and press ENTER to skip. Do in mind this doesn't dump drm key since sake authentifiction is need for that! n

Optional step! Type 'y' and press ENTER if you need to flash bootloader, bluetooth, dsp,modem, rdimage to booth a,b slots, or type 'n' to skip. By default it is NOT flashed to booth slots, do on your own risk!

y - Error write! Need nBytes: 9x18 but done: exe nBytes [exe]:

- Error writing command getvar:max-download-size!

End. You can disconnect your device when you close newflasher.exe Press any key to continue
You need to install gordongate usb drivers which you can install by folowing newflasher window text! In case you have compiled newflasher by yourself do in mind newflasher not use libusb!
 

munjeni

Senior Member
Jun 2, 2011
9,652
22,323
Hi!
I'm not sure, that this the right thread to ask, but, I will try my luck here also😊
I have xperia 5iii from UK. I live in Israel. The phone can't turn on volte. I know that xperia 1IV works in Israel fine. So the question is - can I replace modem files in firmware folder of my phone with the files from xperia 1 IV and flash it with newflasher?
Thank you
You can't! Every model have its own signed fw which you can't use from another model, it simply will not flash at all, in worst case you might hard brick your device!
 

john615

New member
May 18, 2022
4
0
Is it possible to relock bootloader? I want my Xperia Pro 5g to be completely stock again. Is this possible once the bootloader was unlocked?

Can someone please guide me step by step on how to relock bootloader? I unlocked it a few months back and installed an older firmware. Now I just want to lock the bootloader and get the latest firmware and ota updates, and just have the phone back to stock. I completely forgot the process.

I'm willing to pay someone to help me out if possible. It shouldn't take too long. I will lock bootloader, then repair with xperia companion to get DRM back. I just dont know where to begin.
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,652
22,323
Is it possible to relock bootloader? I want my Xperia Pro 5g to be completely stock again. Is this possible once the bootloader was unlocked?

Can someone please guide me step by step on how to relock bootloader? I unlocked it a few months back and installed an older firmware. Now I just want to lock the bootloader and get the latest firmware and ota updates, and just have the phone back to stock. I completely forgot the process.

I'm willing to pay someone to help me out if possible. It shouldn't take too long. I will lock bootloader, then repair with xperia companion to get DRM back. I just dont know where to begin.
Man use Google and search for that, there is a ton of sites shares that info, diferencie is only "does my devices can be relocked", thats what you need to know first! For example I have Xperia 10 and I have unlocked bootloader but until I figured that I can't relock my bootloader it was too late since I was in hurry to unlock bootloader and later figured out that I can't relock bootloader. Just search about that thing first! Procedure for relocking bootloader is the same for all Xperia devices, main diferencie is not all device have feature "relock bootloader". So just search for example "how to rellock bootloader on Xperia" trought Google and you will get info for sure for step by step guide.
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,652
22,323
SOMC Flash device has CODE 10 error in device manager even after installing gordongate from newflasher. Spent the last 2 days looking it up but found nothing. Enters flash mode but isnt recognised by the system.
Looks like usb cable isue? Usb post isue pc side or phone side? Dust inside usb port phone side? OS isue? Many more things to check!
 

mirhl

Senior Member
Oct 15, 2012
3,109
1,168
Procedure for relocking bootloader is the same for all Xperia devices, main difference is not all device have feature "relock bootloader".
Not really?
Relocking through reflashing the original TA was always possible until XZP/XZ1.
Then somehow it didn't work anymore (alas I don't remember the details, again)
Last but not least, since ~X1 (as you know?) not only TA restoring is good, but oem lock should also be a thing.
 

munjeni

Senior Member
Jun 2, 2011
9,652
22,323
Not really?
Relocking through reflashing the original TA was always possible until XZP/XZ1.
Then somehow it didn't work anymore (alas I don't remember the details, again)
Last but not least, since ~X1 (as you know?) not only TA restoring is good, but oem lock should also be a thing.
J4nn and me analysed that things detaily, there is some keys inside rpmb which we sucesfully dumped, and we found that if you restore TA it didn't restore key in rpmb! If I remembered right key from rpmb when XOR with key from some ta unit (didn't rebember) match key from unit 66667. What is used for key from rpmb I realy didn't remembered. In general device is not the same like when device was factory locked, and what problems can we get because of missing key from rpmb I don't know. To be honest I don't care anymore, its not my hobby for a long time.
 

Nhshop

New member
Jan 6, 2023
2
2
hello, mr. munjeni. I really thank you for the project you created. Sorry, I also read the thread discussing bootloader unlock: no and your comment was in there. Maybe this file can help you. This file contains ".dll" which can hack username and password of s1 networktool. It worked 2 years ago for my sony xperia and changed bootloader to yes. Now unusable. Maybe you can update or create a new ".dll" so it can be reused. Thank you.

Sorry for the bad english.
 

Attachments

  • qUnlockTool.rar
    7.4 MB · Views: 58

munjeni

Senior Member
Jun 2, 2011
9,652
22,323
Hi guys, I put newflasher and its files with the extracted tft files in the same directory, my phone is detected but I get this error.

Code:
update.xml not exist in current folder!

update.xml not exist in current folder!

Reboot mode at the end of flashing:
type 'a' for reboot to android, type 'f' for reboot to fastboot, type 's' for reboot to same mode, type 'p' for poweroff, and press ENTER.
Thats not error but warning! Without update.xml you wouldn't be abble to keep userdata, instead an clean installation. Clean installation is always prefered!
 
Last edited:
  • Like
Reactions: sieghartRM

munjeni

Senior Member
Jun 2, 2011
9,652
22,323
hello, mr. munjeni. I really thank you for the project you created. Sorry, I also read the thread discussing bootloader unlock: no and your comment was in there. Maybe this file can help you. This file contains ".dll" which can hack username and password of s1 networktool. It worked 2 years ago for my sony xperia and changed bootloader to yes. Now unusable. Maybe you can update or create a new ".dll" so it can be reused. Thank you.

Sorry for the bad english.
That not working for free, and that can't be cracked, these app reguire paid credits to get unlock code from the remote server.
 
  • Like
Reactions: sieghartRM

kfrin

Member
Jan 5, 2012
35
3
Hi munjeni!
I want to thank you very much for your tool because it just saved my G8341 which was stuck in a bootloop. Impossible to flash it with Flashtool so thanks again!
FYI, I unlocked the bootloader on my XZ1 years ago and I want to relock it but I still didn't succeed to do it.
I'll keep you updated guys if I have any chance with doing the thing.
Sorry for my bad english
 

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

Senior Member
Jun 2, 2011
9,652
22,323
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

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    If i change all file sin by sony_dump what should be i rename the extension
    I don't have time for this, if you don't know I can't help sorry thats not easy and extremely danger for your phone, easily might brick your phone! My sugestion, don't play with it if you have no idea what you have need or what you have doing, otherwise big chance that you will need to buy new phone!
    2
    Just open it with an hex editor and look, it might be ext4, fat, binary...etc, tool allready produce extension at the end if it detect it as an ext4 for example. I don't want to participate further because I haven't worked on it for a long time, today's phones are much more secure than before, so it's very possible that their protection is much more complicated and that it's very possible that if you flash something manually, you'll kill the phone, and I won't say anything further. You have to fend for yourself! I just made tool, the rest is "do it yourself".
    1
    Your phone model is SO-51C . You can't flash an fw if it is not SO-51C using newflasher , every firmware have signature verifiction and if fw is not designed for your phone model bootloader will reject flashing it because of wrong signature. The only way is botloader unlocking and some tools like https://forum.xda-developers.com/t/...-apple-unpack-any-sony-firmware-file.3530077/ so convert sin files to raw format and flash it jurself manualy trought command line. Don't ask how I do't know, not an easy task.
  • 340
    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
    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.