[TOOL] Newflasher (xperia command line flasher)

[shenhenghtml]

Try this one https://forum.xda-developers.com/t/...-apple-unpack-any-sony-firmware-file.3530077/

report，lack some things in the super_x.sin package, only unpack out the system file . i think it shoud contain system ,product,system_ext ,because there is not big file can contain these file unless the super_x.sin
it is exceptional ,the new format
thank you

 

[munjeni]

report，lack some things in the super_x.sin package, only unpack out the system file . i think it shoud contain system ,product,system_ext ,because there is not big file can contain these file unless the super_x.sin
it is exceptional ,the new format
thank you

Can you upload it... ? or maybe beter idea, open it with an hex editor and give me first 20 lines

 

[munjeni]

You probably need this -> https://forum.xda-developers.com/t/...ake-partitions-rw-in-super-partition.4120963/

 

[shenhenghtml]

You probably need this -> https://forum.xda-developers.com/t/...ake-partitions-rw-in-super-partition.4120963/

yes ,it is the key
thinks

 

[invincible12]

Hello guys and @munjeni , I had been a peer here a long time. Now I got a problem so posting it.
I bought my Xperia 5 ii (XG-AS72) from Singapore. And I tried to flash the AS52 UK version with newflasher. But I ended up now in a bootloop. (Then I tried US,SEA and every other versions. Seems firmware is not the problem.) The thing I suspected is that my active slot is set to b. I hadn't enabled USB debugging so I couldn't switch my active slot with ADB. ( I tried "newflasher set_active:a" but it didn't change the slot neither). I'm also not that much of an expert in android programs. So I think I might have something not tried. Help required please and please break it down a little if any complicated methods to be done. Thanks in advance. I have attached the newflasher log file here for reference.

 

[munjeni]

Hello guys and @munjeni , I had been a peer here a long time. Now I got a problem so posting it.
I bought my Xperia 5 ii (XG-AS72) from Singapore. And I tried to flash the AS52 UK version with newflasher. But I ended up now in a bootloop. (Then I tried US,SEA and every other versions. Seems firmware is not the problem.) The thing I suspected is that my active slot is set to b. I hadn't enabled USB debugging so I couldn't switch my active slot with ADB. ( I tried "newflasher set_active:a" but it didn't change the slot neither). I'm also not that much of an expert in android programs. So I think I might have something not tried. Help required please and please break it down a little if any complicated methods to be done. Thanks in advance. I have attached the newflasher log file here for reference.

It must be changed by command:

newflasher set_active:a

probably you failed on path to the newflasher trought command line. Do it this way trought full path to the newflasher, for example:

C:\users\yourusernameonpc\Desktop\folderwhereisyournewflasherexe\newflasher.exe set_active:a

 

[invincible12]

It must be changed by command:

newflasher set_active:a

probably you failed on path to the newflasher trought command line. Do it this way trought full path to the newflasher, for example:

C:\users\yourusernameonpc\Desktop\folderwhereisyournewflasherexe\newflasher.exe set_active:a

Yeah I tried that too.. even I added the path to the environment variables and tried it. And also tried to open a powershell from the directory to run the command. But it didn't seem like switching the partition. Don't know why.
Then I tried and created a .ftf file from the downloaded xperifirm firmware and used the Sony Mobile flasher tool to flash it. Anyhow I got my phone worked.
Besides, i just had a doubt. I tried using the adb command "fastboot --set-active=a" but it didn't work as my phone was disabled with USB debugging. So does the command "newflasher set_active:a" also works when the USB debugging is enabled or it has nothing to do with it?
(P.S. Still this whole thread and your tool was very helpful though. Thanks a lot)

 

[munjeni]

No need to "allow usb debuging" as newflasher do not use fastboot protocol. It must be done in flash mode

 

[invincible12]

No need to "allow usb debuging" as newflasher do not use fastboot protocol. It must be done in flash mode

Ok... Thanks for the info. I'll try it next time i use and post a log if anything goes wrong.

 

[shirakoshi]

Hello @munjeni
I have flashed the file for SOG02 downloaded on Xperifirm on my Japanese Xperia 5 ii (SOG02) with newflasher. (At that time there was a log like 0000_b)
And when it reboots, it says

your device is corrupt It can't be trusted and will not bootYour device will be powered off in 5 seconds

and cannot boot.
No adb or fastboot recognition. I tried turning off the power and then connecting it to the cable while holding down volume down to put it in flash mode, but all I get is "your device is corrupt".
Your tool is great but I would like a little explanation, please.

 

[mj673687]

Hi,
i flashed xperia 5iii with newFlasher. after flashing I got msg "your device is corrupt It can't be trusted and will not bootYour device will be powered off in 5 seconds"

reading post on this thread I tried doing set active to b. After setting and rebooting device is not booting up. Even am not able to get to fast boot mode as well.

plz help me with this

 

[munjeni]

Hi,
i flashed xperia 5iii with newFlasher. after flashing I got msg "your device is corrupt It can't be trusted and will not bootYour device will be powered off in 5 seconds"

reading post on this thread I tried doing set active to b. After setting and rebooting device is not booting up. Even am not able to get to fast boot mode as well.

plz help me with this

Hello @munjeni
I have flashed the file for SOG02 downloaded on Xperifirm on my Japanese Xperia 5 ii (SOG02) with newflasher. (At that time there was a log like 0000_b)
And when it reboots, it says

your device is corrupt It can't be trusted and will not bootYour device will be powered off in 5 seconds

and cannot boot.
No adb or fastboot recognition. I tried turning off the power and then connecting it to the cable while holding down volume down to put it in flash mode, but all I get is "your device is corrupt".
Your tool is great but I would like a little explanation, please.

This is explained I don't know how many times in this tread! Thats nothing related to newflasher but to ROLLBACK PROTECTION, you just need to flash newer rom than actual one on your phones, or simply unlock bootloader, flash any rom designed for your model than simply relock bootloader to reset rollback index to zero, in that case your device going to boot. If you flashed allready with newflasher, all critical components like bootloader...etc is always flashed to booth slots so your device will definitelly boot to flash mode if you getting "your device is corupt", you just need to put your device to flash mode by right combination on volume buttons + connecting usb slot to PC, just put your device in flash mode and flash right firmware, or unlock bootloader and flash any older or newer rom you want. I realy dislike that rollback protection, thats crazy and not what I want on my phone, including all new features like dynamic partitions. Until all gone back to single mode partitions and without rollback protection I have no plan to buy any new phone.

 

[shirakoshi]

Thank you for your reply. I solved the problem by fixing something like boot _ a.
It was certainly not the problem of newflasher, sorry.

 

[RIKEY0324]

Since My sony xperia XA2 Plus (H4493) occurs booting error (keep showing SONY when i boot)
then i got a problem like below when i want to flashing sony xperia XA2 Plus (H4493) by Newflasher v52
thanks fotr ur help (sorry for my bad English....)

newflasher.exe v52 by Munjeni @ 2017/2020
--------------------------------------------------------

Determining available free space by GetDiskFreeSpaceEx:

Available space to caller = 407898 MB
Total space on current drive = 476936 MB
Free space on drive = 407898 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!
n
Device path: \\?\usb#vid_0fce&pid_b00b#6&12e3c9ed&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: SOMC Flash Device
Device Instance Id: USB\VID_0FCE&PID_B00B\6&12E3C9ED&0&1


Do you want to keep userdata? Type 'y' and press ENTER to confirm, or type 'n' to erase userdata.
n

Reboot mode at the end of flashing:
typa '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.
a

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! But it is recommend to have dump in case hard brick!
n
Product: H4493
Version: 0.4
Bootloader version: 1310-0301_X_Boot_SDM630_LA3.0_P_38
Baseband version: 1315-1739_50.2.A.3.65
Serialno: CQ30014QA7
Secure: yes
Loader version: XFL-SDM630-204
Phone ID: 0000:35908509024628,0000:35908509024629
Device ID: 365EE3A0
Platform ID: 000AC0E1
Max download size: 104857600
Sector size: 512
Rooting status: ROOTABLE
Ufs info: FAILUfs-info not supported
Emmc info: HYNIX,0x014a,0x0
Default security: ON
Keystore counter: 2
Security state: TvF2l+0Or40aQudMdC8LLMt1auy6bg2DtGVLnpGqPyk=
Sake root: A672
S1 root: S1_Root_70f0
Root key hash: 5F01088791F1DDAD20DB0DF59453943E4D275929A01705C83502AD5403F9010F
Slot count: 2
Current slot: b
Battery level: 70

Error, didn't got TA write 'go into flashmode' OKAY reply! Got reply: FAILUnable to write to TA unit 10100
Sent command: continue.

Done.
Closing device.
請按任意鍵繼續 . . .

 

[munjeni]

Since My sony xperia XA2 Plus (H4493) occurs booting error (keep showing SONY when i boot)
then i got a problem like below when i want to flashing sony xperia XA2 Plus (H4493) by Newflasher v52
thanks fotr ur help (sorry for my bad English....)

You are first one who getting that error, please try again

 

[RIKEY0324]

You are first one who getting that error, please try again

I have tried several times and it returns the same message....
Can you know what could be the reason?

 

[munjeni]

I have tried several times and it returns the same message....
Can you know what could be the reason?

Did you touch the trim area partition and corrupt?? I realy don't know, I see that for the first time. Might be usb cable isue? You should try another cable, also USB3.0 and 3.1 is reported sometimes that cause some isues, so I changed asynchorous usb transfer to synchronous usb transfer in newflasher source code, after that there was no isues with usb3.x, at least nobody reported, so if you can you should try usb2.0 port on your pc! Did you tried Sony PC Companion software, what they say?

 

[ruchan]

Hi!

Device path: \\?\usb#vid_0fce&pid_b00b#5&2108ad5d&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: SOMC Flash Device
Device Instance Id: USB\VID_0FCE&PID_B00B\5&2108AD5D&0&2

ERROR: Error CreateFile! failed with error code 5 as follows:
Access is denied.

I am getting this error after repairing thru Xperia Companion.. How do I fix this?

 

[munjeni]

Hi!

Device path: \\?\usb#vid_0fce&pid_b00b#5&2108ad5d&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: SOMC Flash Device
Device Instance Id: USB\VID_0FCE&PID_B00B\5&2108AD5D&0&2

ERROR: Error CreateFile! failed with error code 5 as follows:
Access is denied.

I am getting this error after repairing thru Xperia Companion.. How do I fix this?

You must close any instance of the xperia companion

 

[sufu.7]

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

- 版本 48 （19.07.2021）
闪存引导加载程序，蓝牙，dsp，调制解调器，仅在a，b设备上的展位插槽中显示图像

- 版本 49 （31.07.2021）
支持 XQ-BT41

- 版本 50 （12.08.2021）
在异步 usb 上继续工作，使其更像同步，在发送-接收 USB 数据包和更多日志记录期间添加了进度条。将 USB 超时增加到 2 分钟。尝试修复同步命令在闪烁结束时，如此处所述 -> https://github.com/munjeni/newflasher/issues/42

- 版本 51 （12.08.2021）
修复了在接收 USB 数据包时打印的空行，感谢 @elukyan

- 版本 52 （01.10.2021）
实现了用于保留用户数据的 userprompt，感谢 @OhayouBaka 的发现！删除了引导加载程序日志检索

学分：

- 没有@tanipat和他的电脑同伴调试日志，这个工具将永远不可能！非常感谢您抽出宝贵时间向我提供日志！（受他人影响，他对上一篇文章感到失望，但我仍然感谢他的帮助，无法忘记）
- 没有@thrash001谁帮助测试我们的工具，我从来没有继续构建我们的工具，因为我没有设备进行测试，谢谢伙计！
- 没有忘记@beenoliu，感谢队友的测试！
- 感谢 @porphyry 测试 linux 版本！
- 感谢@Snow_Basinger提供2018年设备的嗅探日志，并在其2018年设备上进行测试
- 感谢@frantisheq在他的2018年设备上测试newflasher，并通知有关doublefree错误的信息
- 感谢@serajr为我提供了一些日志，帮助我弄清楚了与2018年设备相关的一些事情
- 感谢 @noelex 帮助 Xperia 1 实现
- 感谢@Meloferz在他的xperia 1 mark II上进行测试
- 感谢github的贡献者，测试人员和记者：vog，noelex，TheSaltedFish，solarxraft，pbarrette，MartinX3，kholk
- 感谢 Chirayu Desai 对 Debian 的跟踪，感谢 vog 发起的所有这些
- 感谢@elukyan进行测试，并为我提供了用于标记3设备immlementation的USB嗅探日志，非常感谢

常见错误和如何解决：
https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-72610228

源代码：

https://github.com/munjeni/newflasher

下载后找不到压缩包中的 EXE
文件