• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[TOOL] Newflasher (xperia command line flasher)

Search This thread

churchner420

Senior Member
Mar 25, 2015
353
28
Hey man, does that bug still persist on the latest Mark III devices? Would be interesting if Sony has changed that since the 5 II for the future. I fear we will need to flash another firmware like thing which noone has developed a tool to download it for, yet... A tool that downloads the necessary firmware parts for region Customisation changes
 

jemcik

Member
Mar 19, 2014
39
12
37
Kyiv
I was able to downgrade my Xperia 5 mark 2 (XQ-AS72 version) from android 11 (58.1.A.5.159) to android 10 (58.0.A.28.51, XQ-AS52 version) using Newflasher only with UNLOCKED bootloader.
Method with unlocking and relocking bootloader described here DOES NOT work :(
I tried three times always resulting in a message that firmware is corrupted and device cannot boot, turning off in 5 seconds bla-bla-bla.
After flashing XQ-AS52_Customized EEA_58.0.A.28.51 I relocked bootloader and everything works perfectly.
 
  • Like
Reactions: munjeni

munjeni

Senior Member
Jun 2, 2011
9,363
21,961
I was able to downgrade my Xperia 5 mark 2 (XQ-AS72 version) from android 11 (58.1.A.5.159) to android 10 (58.0.A.28.51, XQ-AS52 version) using Newflasher only with UNLOCKED bootloader.
Method with unlocking and relocking bootloader described here DOES NOT work :(
I tried three times always resulting in a message that firmware is corrupted and device cannot boot, turning off in 5 seconds bla-bla-bla.
After flashing XQ-AS52_Customized EEA_58.0.A.28.51 I relocked bootloader and everything works perfectly.
I can't tell for sure how it work since I don't owning phone with possibility to relock bootloader, but what I found is described and its close. So steps is: unlock, flash old rom, relock, right?
 

Kombre212

Member
Mar 31, 2021
7
1
Newbie question.. I found some people excluded the .ta file before they do flashing. I'm curious, what .ta file is, exactly?

Is there any harm to include them when do flashing, like the 'persist' file, for example?

Thank you
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,363
21,961

wybymz

New member
Jun 26, 2021
4
0
For help, my XZ2P (H8166 52.1.A.3.49) has been rebooted automatically at the Sony LOGO after the kernel has been flashed. Now the Fastboot mode and Flashmode cannot be accessed. Press and hold the volume - , connect to PC, it will automatically start up, display SONY, then shut down and start up again, the USB cable and PC (Win10) have been changed, how to repair, thank you.

Kernel link
 

munjeni

Senior Member
Jun 2, 2011
9,363
21,961
For help, my XZ2P (H8166 52.1.A.3.49) has been rebooted automatically at the Sony LOGO after the kernel has been flashed. Now the Fastboot mode and Flashmode cannot be accessed. Press and hold the volume - , connect to PC, it will automatically start up, display SONY, then shut down and start up again, the USB cable and PC (Win10) have been changed, how to repair, thank you.

Kernel link
Hold down all buttons (volume up, volume down, power) until device fully shutdown, than connect usb cable while holding volume down. In the same time watch your PC device mannager, look for yellow triangle if you see them you have missing flash driver. I can suggest you run newflasher and confirm 'y' when it ask you to install gordon gate, install them, reboot your pc, try again
 
Last edited:

wybymz

New member
Jun 26, 2021
4
0
Hold down all buttons (volume up, volume down, power) until device fully shutdown, than connect usb cable while holding volume down. In the same time watch your PC device mannager, look for yellow triangle if you see them you have missing flash driver. I can suggest you run newflasher and confirm 'y' when it ask you to install gordon gate, install them, reboot your pc, try again
Thank you, I tried to install the driver according to your method, it will prompt me whether to uninstall, I uninstalled and restarted and installed again, the PC still cannot connect to the phone. There is a yellow triangle in the device manager: Unknow USB Device (Device Descriptor Request Failed)
 

munjeni

Senior Member
Jun 2, 2011
9,363
21,961
Windows drivers mess? Try to install Sony PC Companion software and do "repair phone", it will install drivers automaticaly and repair windows mess with drivers. Also try diferent usb port one from back of the pc for example. Also try diferent usb cable it might be broken. Also check for dust inside phone usb port. If you installed gordon gate I see no reason why you see yellow triangle other than bad cable or usb port
 
Last edited:

wybymz

New member
Jun 26, 2021
4
0
You mean Xperia Companion? No, press and hold the volume- step in the "Xperia Software Repair" option, unable to proceed to the next step. I used all the USB ports on the laptop😭
Windows drivers mess? Try to install Sony PC Companion software and do "repair phone", it will install drivers automaticaly and repair windows mess with drivers. Also try diferent usb port one from back of the pc for example. Also try diferent usb cable it might be broken. Also check for dust inside phone usb port. If you installed gordon gate I see no reason why you see yellow triangle other than bad cable or usb port
 

munjeni

Senior Member
Jun 2, 2011
9,363
21,961
You mean Xperia Companion? No, press and hold the volume- step in the "Xperia Software Repair" option, unable to proceed to the next step. I used all the USB ports on the laptop😭
Xperia companion, yes. Than drivers is not a problem definitelly. You have tried all usb ports so it looks like only problem is phone usb port defect or defect in cable, I have no other idea. What is a VID and PID in device mannager of the usb device which have yellow triangle? You sdhould go to friend and try his cable+pc to be sure, we can't gues
 

Hichem2006

Senior Member
Jan 8, 2021
65
14
Hello, I tried flashing Android 9 stock ROM on my Xperia XZ2 Dual SIM H8266, and it ends in a bootloop then shows a message saying "Your device is corrupt and can't be trusted and will not boot Your device will be powered off in 5 seconds"
PS: I didn't downgrade, I had Oreo 8.1
 

Top Liked Posts

  • 1
    Hi!

    I successfully flashed my XQ-BC72 with TW firmware two days ago.
    I used the latest version of your tool (v48). FW was downloaded by XperiFirm.

    Only one thing - I have unlocked bootloader.

    1627205370874.png



    Thanks for the tool!)

    Regards, Eugene

    P.S. My Xp1-III was originally a CN version with the appropriate firmware.
  • 5
    New version is out!

    - 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
    3
    Thanks! New version is out

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

    I successfully flashed my XQ-BC72 with TW firmware two days ago.
    I used the latest version of your tool (v48). FW was downloaded by XperiFirm.

    Only one thing - I have unlocked bootloader.

    1627205370874.png



    Thanks for the tool!)

    Regards, Eugene

    P.S. My Xp1-III was originally a CN version with the appropriate firmware.
    1
    New version is out.

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

    Please try and let me know! Also please give me newflasher log just to confirm if I have fixed that, thanks!
  • 305
    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

    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.