[TOOL] Newflasher (xperia command line flasher)

[churchner420]

With Xperia Companion it is only possible to upgrade but i want to downgrade from android 11 to 10. I am not happy with Android 11

That is true but at least you would have got a working device again. I hate A11 as well but your security level will get severely outdated if you don't update

 

[munjeni]

With Xperia Companion it is only possible to upgrade but i want to downgrade from android 11 to 10. I am not happy with Android 11

I have allready mentioned ten pages back about rollback protection, I will not repeat so try read it first. Here you can read about rollback protection https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84077083 . So no back to android 10 after upgrading to 11 because of rollback protection! Only a way to bypass rollback protection is -> https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84378969 (solution not confirmed!!! If you going to do that let us know the result!). In short bootloader need to be unlocked, than relocked (to reset roolback index, than reflash 10, and this need confirmation since nobody tried it and nobody confirmed solution. And ofcourse I will not repeat whats happening with device unique key after unlocking bootloader, my hope you read something about it.

 

[OR7]

I have allready mentioned ten pages back about rollback protection, I will not repeat so try read it first. Here you can read about rollback protection https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84077083 . So no back to android 10 after upgrading to 11 because of rollback protection! Only a way to bypass rollback protection is -> https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84378969 (solution not confirmed!!! If you going to do that let us know the result!). In short bootloader need to be unlocked, than relocked (to reset roolback index, than reflash 10, and this need confirmation since nobody tried it and nobody confirmed solution. And ofcourse I will not repeat whats happening with device unique key after unlocking bootloader, my hope you read something about it.

This is stated on the Sony website:
Unlock Bootloader
What is this?
By unlocking the bootloader, it’s possible to

Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys. For devices running recent software versions, for instance Xperia Z3, the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected. The secure user data partition may also become inaccessible, and you will not be able to get any more official software upgrades if you unlock the bootloader.


I'm not going to do this

 

[munjeni]

This is stated on the Sony website:
Unlock Bootloader
What is this?
By unlocking the bootloader, it’s possible to

Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys. For devices running recent software versions, for instance Xperia Z3, the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected. The secure user data partition may also become inaccessible, and you will not be able to get any more official software upgrades if you unlock the bootloader.


I'm not going to do this

Yes it was a case for old models, new models like mark 2 devices have "oem lock" possibility, with that all drm functionality is back except device unique key is forever deleted from booth trim area & rpmb which probably afect some functionality but I think not that dramatic like in old phone models, in most case it just voids waranty.

 

[Pandemic]

Yes it was a case for old models, new models like mark 2 devices have "oem lock" possibility, with that all drm functionality is back except device unique key is forever deleted from booth trim area & rpmb which probably afect some functionality but I think not that dramatic like in old phone models, in most case it just voids waranty.

Since the xperia 1/5 and up ^^

 

[munjeni]

Since the xperia 1/5 and up ^^

Excluding xperia 10. I remembered my unlocked xperia 10 and I learned a leason to not hurry to unlock bootloader before few peoples confirm it realy work.

 

[creezy57]

Since the xperia 1/5 and up ^^

how about Xperia 10 II? did somebody check?

 

[Pandemic]

how about Xperia 10 II? did somebody check?

Dunno i have xperia 1

 

[churchner420]

I tried flashing my 5 II with flashtool now but that is not working at all... Soooooo, back to newflasher but that is not working either for debranding or changing the region. Any solutions for that yet?

 

[munjeni]

We are in a circle? Is there anything not explained allready for example this -> https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84453313 (firmware bug). There is no solution because vbmeta signature will bootloop your phone if you modify oem partition e.g. you change string. Do not expect anything in newflasher in relation to bug fix, its not newflasher isue and newflasher will stay as a flashing tool only, newflasher now and in futue will not be a tool for fixing firmare bugs, only a tool for flashing as simple as possible.

One question for everybody, does unlocking bootloader disable vbmeta protection?

And one more thing to tell you guys, I'm not in android hobby, and I do not test things frequently anymore, I'm not flashing anything for about two years, and I have less time for xda, but I have some time for newflasher, so please do not reguest a things from me to test something, you need to test and tell me! You need to figure out what is need, not me. Only thing I can do is to implement that what you figure out into newflasher. I not going to figure things buyself! And I don't own mark 2 device! So I can't test anything on mark 2 device, you need to test and figure. If you figure something important let me know and I will try to implement that into newflasher.

 

[MrMmmkay]

One question for everybody, does unlocking bootloader disable vbmeta protection?

With unlocked bootloader you can do this: " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img "

 

[munjeni]

With unlocked bootloader you can do this: " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img "

Thats good to know! So solution to reset vbmeta index (bypass rollback protection) is to unlock bootloader than relock bootloader (relocking bootloader vbmeta index gets zeroed -> more info -> https://forum.xda-developers.com/t/...-locking-the-bootloader.4079715/post-83035119 -> currently unconfirmed solution. Than probably we can flash old rom without getting bootloop. All this getting sense for me, e.g. when phone is fully locked (never unlocked) its under full security, rollback protected, vbmeta protected... etc, so to bypass all this only a way is to unlock bootloader. But unlocking bootloader and device unique key is bye bye forewer. Relocking bootloader and widevine and all keys getting back except device unique key which is forever deleted. I don't know whats going on when device is under waranty, probably waranty bye bye too.

 

[suogreen]

can u help me?

signature:0000053c
Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms

 

[munjeni]

can u help me?

signature:0000053c
Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms

Full log?

 

[swooc]

recently flashed my xperia 1 j9110 with newflasher. stock 55.2.A.0.630 nordic. no root. everything flashed ok, no errors iirc. not sure if its a rom , hardware or flash problem, but my phone had randomly factory resetted after a couple of days. i've flashed many xperias with flashtool and have never experienced such a thing.

 

[munjeni]

And probably you skiped to flash userdata and some ta files?

 

[swooc]

^i N'd every prompt on the command line and only removed simlock.ta in the firmware. i've always skipped .ta files in flashtool. but i read that they were no longer a problem anymore (and encouraged to add them in) so had included them except for simlock in the firmware dir for newflasher. i always flash userdata for a complete wipe when i do a firmware flash.

i'll be doing another flash sometime this week since there's a new firmware out. will keep a lookout this time for any errors during the flashing.

 

[noahhhh]

Hi @munjeni my phone is xperia 5 II XQ-AS72.I bought it from China and flash it into sw ver: 58.0.A.28.51,customised SEA,as newflasher processing dsp_X-FLASH-ALL-2389.sin,it shows ERROR WRITE
when I move the dsp.sin file out of the folder it completed the flash,all things were fine and I thought no big deal so I didn't report it but I can't get the OTA.
so I download the 58.1.A.1.178 SEA through xperifirm and use newflasher v40,it happened again.
What caused the issue? thank u for help
this is the full log

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

Determining available free space by GetDiskFreeSpaceEx:

  Available space to caller    = 10898 MB
  Total space on current drive = 141795 MB
  Free space on drive          = 10898 MB

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 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#8&3a6eeffa&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: SOMC Flash Device
Device Instance Id: USB\VID_0FCE&PID_B00B\8&3A6EEFFA&0&1


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: XQ-AS72
Version: 0.4
Bootloader version: 1320-2827_X_Boot_SM8250_LA1.0.1_Q_51
Baseband version: 58.0.A.28.51
Serialno: QV7208752
Secure: yes
Loader version: XFL-EDO-SM8250-16
Phone ID: 0000:3XXXX,0000:3XXXX
Device ID: CXXXX
Platform ID: 200C30E1
Max download size: 104857600
Sector size: 4096
Rooting status: ROOTABLE
Ufs info: SAMSUNG,KLUEG8UHDB-C2D1,1000
Emmc info: FAILEmmc-info not supported
Default security: ON
Keystore counter: 2
Security state: 9hVHs82HDVbmXdpJ3fHpaod1NV4/GQSuzrwwyrEcD9s=
Sake root: 19408654C25217EDC7BEF2FED8FB
S1 root:
Root key hash: 502D5117AE7B00D9F89E4EAE078EE07D347F313333898EB57EB909BDA341D53D477719408654C25217EDC7BEF2FED8FB
Slot count: 2
Current slot: a

Device is put now in flash mode.

Repartitioning...
Found partition_delivery.xml in partition folder.
Determining LUN0 size...
UFS raw data[0xA9]:

  00000000  40 00 00 00 00 00 03 04 01 00 01 7F 00 01 04 00  @...............
  00000010  03 00 08 20 00 01 02 03 01 CE 10 10 02 00 00 81  ... ............
  00000020  01 20 00 00 20 00 00 00 00 00 04 00 00 00 00 00  . .. ...........
  00000030  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00000040  23 02 00 01 00 00 00 00 00 00 0C 00 00 00 00 03  #...............
  00000050  B9 48 00 00 00 00 01 03 00 00 00 00 03 B9 48 00  .H............H.
  00000060  00 00 00 23 02 01 01 01 01 00 00 03 00 0C 00 00  ...#............
  00000070  00 00 00 00 08 00 00 00 00 01 03 00 00 00 00 00  ................
  00000080  00 08 00 00 00 00 23 02 02 01 02 01 00 00 03 00  ......#.........
  00000090  0C 00 00 00 00 00 00 08 00 00 00 00 01 03 00 00  ................
  000000A0  00 00 00 00 08 00 00 00 00                       .........

LUN0 size = 249896960

Processing partition-image-LUN0_124936192_X-FLASH-ALL-2389.sin
Skipping partition-image-LUN0_124936192_X-FLASH-ALL-2389.sin

Processing partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin
- Extracting from partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin
- Extracting signature partitionimage_0.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\partition\partitionimage_0.cms
      signature:0000089c
      OKAY.
- Extracting sparse chunk partitionimage_0.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\partition\partitionimage_0.000
      download:00006000
      OKAY.
      Repartition:0
      OKAY.
- End of partition-image-LUN0_249896960_X-FLASH-ALL-2389.sin

Processing partition-image-LUN1_8192_X-FLASH-ALL-2389.sin
- Extracting from partition-image-LUN1_8192_X-FLASH-ALL-2389.sin
- Extracting signature partitionimage_1.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\partition\partitionimage_1.cms
      signature:0000089c
      OKAY.
- Extracting sparse chunk partitionimage_1.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\partition\partitionimage_1.000
      download:00006000
      OKAY.
      Repartition:1
      OKAY.
- End of partition-image-LUN1_8192_X-FLASH-ALL-2389.sin

Processing partition-image-LUN2_8192_X-FLASH-ALL-2389.sin
- Extracting from partition-image-LUN2_8192_X-FLASH-ALL-2389.sin
- Extracting signature partitionimage_2.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\partition\partitionimage_2.cms
      signature:0000089c
      OKAY.
- Extracting sparse chunk partitionimage_2.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\partition\partitionimage_2.000
      download:00006000
      OKAY.
      Repartition:2
      OKAY.
- End of partition-image-LUN2_8192_X-FLASH-ALL-2389.sin

Processing .sin files...
Created ouput folder flash_session

Processing appslog_X-FLASH-ALL-2389.sin
- Extracting from appslog_X-FLASH-ALL-2389.sin
- Extracting signature appslog.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\appslog.cms
      signature:00000893
      OKAY.
- Extracting sparse chunk appslog.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\appslog.000
      download:00002000
      OKAY.
      erase:appslog
      OKAY.
      flash:appslog
      OKAY.
- End of appslog_X-FLASH-ALL-2389.sin

Processing bluetooth_X-FLASH-ALL-2389.sin
- Extracting from bluetooth_X-FLASH-ALL-2389.sin
- Extracting signature bluetooth.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\bluetooth.cms
      signature:00000895
      OKAY.
- Extracting sparse chunk bluetooth.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\bluetooth.000
      download:000a3000
      OKAY.
      Partition: bluetooth have slot: yes
      erase:bluetooth_a
      OKAY.
      flash:bluetooth_a
      OKAY.
- End of bluetooth_X-FLASH-ALL-2389.sin
- Extracting from bluetooth_X-FLASH-ALL-2389.sin
- Extracting signature bluetooth.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\bluetooth.cms
      signature:00000895
      OKAY.
- Extracting sparse chunk bluetooth.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\bluetooth.000
      download:000a3000
      OKAY.
      Partition: bluetooth have slot: yes
      erase:bluetooth_a
      OKAY.
      flash:bluetooth_a
      OKAY.
- End of bluetooth_X-FLASH-ALL-2389.sin

Processing boot_X-FLASH-ALL-2389.sin
- Extracting from boot_X-FLASH-ALL-2389.sin
- Extracting signature boot.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\boot.cms
      signature:00000890
      OKAY.
- Extracting sparse chunk boot.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\boot.000
      download:06000000
      OKAY.
      Partition: boot have slot: yes
      erase:boot_a
      OKAY.
      flash:boot_a
      OKAY.
- End of boot_X-FLASH-ALL-2389.sin

Processing diag_X-FLASH-ALL-2389.sin
- Extracting from diag_X-FLASH-ALL-2389.sin
- Extracting signature diag.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\diag.cms
      signature:00000890
      OKAY.
- Extracting sparse chunk diag.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\diag.000
      download:00002000
      OKAY.
      erase:diag
      OKAY.
      flash:diag
      OKAY.
- End of diag_X-FLASH-ALL-2389.sin

Processing dsp_X-FLASH-ALL-2389.sin
- Extracting from dsp_X-FLASH-ALL-2389.sin
- Extracting signature dsp.cms
- Uploading signature D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\dsp.cms
      signature:0000088f
      OKAY.
- Extracting sparse chunk dsp.000
- Uploading sparse chunk D:\Software\Xperia 5 II\XQ-AS72_Customized SEA_58.1.A.1.178\flash_session\dsp.000
      download:04000000
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 7!

ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
- Error, no set_active:a OKAY reply!
Sent command: Sync
Waiting sync to finish...
........................... error, no sync response!
Closing device.
Press any key to continue . . .

I meet same error.

 

[munjeni]

We have found some bugs recently in firmwares, see some this page and some bages back! Probably in most case there is more bugs in firmwares, I don't know, if you flashed all and didn't got any newflasher error it mean no newlfahser related.

 

[swooc]

^fingers crossed.

thanks for making this flasher. i intially started off with flashtool but it wasn't working. found out new phones like the xperia 1 aren't supported. so off to google and ended up here.