[TOOL] Newflasher (xperia command line flasher)

[Xperia_Xavier]

Any guys have try it on Xperia 1 V? Does it work with HK firmware on China edition?

 

[elukyan]

Yes. I'd successfully flashed SEA firmware on CN version of Xperia 1 V by v55.
Log attached.

 

[dmam27]

Hi all!! Let me ask you please: I'm not sure that i'm using proper drivers for my Xperia 5ii and my Windows 11 PC. On device manager the device is recognised as SONY sa0111 ADB Interface Driver. Is this right ? Because Newflasher doesn't find the phone Error: No usb device with vid:0c0fce pid:0xb00b !

 

[Jayram2000]

Flashing a Xperia 1 iii without unlocking

Things needed: 1. An Xperia 1 iii (of corse) 2. A Windows PC (I don't know if there's a Mac or Linux version, but I didn't find it) 3. A reliable USB-C cable 4. NewFlasher Download: [TOOL] Newflasher (xperia command line flasher) 5. XperiFirm...

forum.xda-developers.com

try this method it works on my 1 IV

This worked to solve my bootloop on my X5II XQ-AS72. I was on Slot B for some reason and changing back let me flash the 58.2.a.10.126 with no issue.

 

[AJHutchinson]

Hi all!! Let me ask you please: I'm not sure that i'm using proper drivers for my Xperia 5ii and my Windows 11 PC. On device manager the device is recognised as SONY sa0111 ADB Interface Driver. Is this right ? Because Newflasher doesn't find the phone Error: No usb device with vid:0c0fce pid:0xb00b !

I always have that issue i have to reinstall the sony drivers anytime I want to flash

 

[munjeni]

Hi all!! Let me ask you please: I'm not sure that i'm using proper drivers for my Xperia 5ii and my Windows 11 PC. On device manager the device is recognised as SONY sa0111 ADB Interface Driver. Is this right ? Because Newflasher doesn't find the phone Error: No usb device with vid:0c0fce pid:0xb00b !

Volume up+power button is for flash mode and volume+ down + power button is for fastboot mode, your device need to be in flash mode!

 

[Hurt Copain]

Yes. I'd successfully flashed SEA firmware on CN version of Xperia 1 V by v55.
Log attached.

hi, i have 1 V also, your log indicates the same issue i am having,

Processing boot delivery...

Found boot_delivery.xml in boot folder.
- Boot delivery version: 8550-0001
- Verifying if boot delivery match with device...
searching for: PLATFORM_ID="001CA0E1";PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"
Didn't found bootdelivery that match your device!


This means it didn't flash everything, it did all partitions but bootloader and a few others. Trying to figure out why the sha/hash check is failing, all the files are the same.

 

[AJHutchinson]

I had no issues flashing and then rooting my Xperia 1 V (XQ-DQ54) so most likely not a newflasher issue but not I can't setup a lockscreen pin, pattern or password I put my pattern twice as requested then it goes back to start over eventually crashing the settings app, probably a build issue tried both O2 UK firmware and the generic UK

 

[Hurt Copain]

I had no issues flashing and then rooting my Xperia 1 V (XQ-DQ54) so most likely not a newflasher issue but not I can't setup a lockscreen pin, pattern or password I put my pattern twice as requested then it goes back to start over eventually crashing the settings app, probably a build issue tried both O2 UK firmware and the generic UK

yea it was an issue we talking about a few weeks ago. wipe and relock. Then after booting up, skip to home screen after setup. Renable oem lock- so it now shows off, a reboot is required. Then, once booted up again, do not set lock screen. Enable oem unlock, then unlock bootloader again. after it boots up again, try to set lock stuff and fp. If it works you are good. If not your firmware has the keystore issue i talked about previously in another thread and the only thing i could do to fix it was flash the sea firmware then unlock. Same thing though, don't set lock stuff beforehand. Let us know what happens. Good luck.

 

[AJHutchinson]

yea it was an issue we talking about a few weeks ago. wipe and relock. Then after booting up, skip to home screen after setup. Renable oem lock- so it now shows off, a reboot is required. Then, once booted up again, do not set lock screen. Enable oem unlock, then unlock bootloader again. after it boots up again, try to set lock stuff and fp. If it works you are good. If not your firmware has the keystore issue i talked about previously in another thread and the only thing i could do to fix it was flash the sea firmware then unlock. Same thing though, don't set lock stuff beforehand. Let us know what happens. Good luck.

Thanks for replying buddy I'm gonna have a try tomorrow as it sounds like I'm going to have loads of fun and I'm tired right now

 

[AJHutchinson]

yea it was an issue we talking about a few weeks ago. wipe and relock. Then after booting up, skip to home screen after setup. Renable oem lock- so it now shows off, a reboot is required. Then, once booted up again, do not set lock screen. Enable oem unlock, then unlock bootloader again. after it boots up again, try to set lock stuff and fp. If it works you are good. If not your firmware has the keystore issue i talked about previously in another thread and the only thing i could do to fix it was flash the sea firmware then unlock. Same thing though, don't set lock stuff beforehand. Let us know what happens. Good luck.

worked like a charm thanks for letting us know about this bug much appreciated buddy

 

[munjeni]

hi, i have 1 V also, your log indicates the same issue i am having,

Processing boot delivery...

Found boot_delivery.xml in boot folder.
- Boot delivery version: 8550-0001
- Verifying if boot delivery match with device...
searching for: PLATFORM_ID="001CA0E1";PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"
Didn't found bootdelivery that match your device!


This means it didn't flash everything, it did all partitions but bootloader and a few others. Trying to figure out why the sha/hash check is failing, all the files are the same.

Can you post here bootdelivery.xml file?

 

[SonyZFan]

Flashed with Newflasher but now unable to get both OTA updates and Google Play System updates. Hope it will be fixed.

Edit: Newflasher V57 and July patch fixed Google Play system updates but fix for OTA updates remains to be seen (need to wait for the next update)

 

[Hurt Copain]

Can you post here bootdelivery.xml file?

so here is the boot delivery from Xperia 1 V HK_dq72 and EU_dq54 this same error is at the end of any firmware other than CN and HK. The others flash but the bootloader files are omitted, so the firmware is updated, with the exception of those files.

The error in the flash log states:

searching for: PLATFORM_ID="001CA0E1";PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B" Didn't found bootdelivery that match your device!

full log:https://katb.in/oromihiyasu

I search 001CA0E1 all in the firmware and it is present in all versions across the firmware versions, Including hk and cn. Whether it be cn,hk,sea,eu, etc. I am guessing a different sku is hardcoded in the boot delivery files present on the devices in cn and hk so it claims it is a different bootloader, but the only firmware that is actually noticeably different when compared is Japan's.

Also, tried deleting .ta files as well, doesn't work. All in all it doesn't matter, once you activate the 5g bands while rewriting mbn files, its fine nonetheless what version we flash if you omit modem files. The boot delivery part that fails is no modem files at all, just bootloader it seems. Comparing hash of the bootloader versions across the firmwares show no diff but with Japanese.

 

[munjeni]

Thank you! I can see generation 5 of the xperia bootdelivery format is changed, now it look like this:

PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"

instead of:
PLATFORM_ID="001CA0E1";PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"

I'm added support for that and verzion 57 is out, hope problem with bootdelivery is gone!

- version v56, v57 (07.07.2023)
Add suport for Xperia 1 generation 5, changed bootdelivery xml atributes

Let me know!

 

[Hurt Copain]

Thank you! I can see generation 5 of the xperia bootdelivery format is changed, now it look like this:

PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"

instead of:
PLATFORM_ID="001CA0E1";PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"

I'm added support for that and verzion 57 is out, hope problem with bootdelivery is gone!

- version v56, v57 (07.07.2023)
Add suport for Xperia 1 generation 5, changed bootdelivery xml atributes

Let me know!

Thank you so much will try after work and confirm!!

 

[Hurt Copain]

Thank you! I can see generation 5 of the xperia bootdelivery format is changed, now it look like this:

PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"

instead of:
PLATFORM_ID="001CA0E1";PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"

I'm added support for that and verzion 57 is out, hope problem with bootdelivery is gone!

- version v56, v57 (07.07.2023)
Add suport for Xperia 1 generation 5, changed bootdelivery xml atributes

Let me know!

Confirmed working! Successful, complete flash, here is the output after the flash showing the problem areas no longer failing to flash. Thank you again.

Found boot_delivery.xml in boot folder.
- Boot delivery version: 8550-0001
- Verifying if boot delivery match with device...
searching for: PLATFORM_ID="001CA0E1";PLF_ROOT_HASH="20CF0F0CD33CA51E062BD90C60DB3CF6C1FB759790D578163C8D211A47319BD99E8025D63737831DCB7F37D30B9B711B"
Found bootdelivery match: COMMERCIAL_001CA0E1
TA file: PDX234_XBootConfig_MiscTA.ta

Processing ./boot/PDX234_XBootConfig_MiscTA.ta
- Partition: 2
- Unit: 84F (2127)
- Unit size: 0x59
download:00000059
OKAY.
Write-TA:2:2127
OKAY.
- Unit: 8FD (2301)
- Unit size: 0x1
download:00000001
OKAY.
Write-TA:2:2301
OKAY.
SIN file: bootloader_X_BOOT_SM8550_LA1_1_T_23_X-FLASH-ALL-25B1.sin

Processing bootloader_X_BOOT_SM8550_LA1_1_T_23_X-FLASH-ALL-25B1.sin
- setting up inflate...
- infflating, please wait...
.
- inflate returned: 0
- gzpipe: ok.
- gunziped ok.
- Extracting from bootloader_X_BOOT_SM8550_LA1_1_T_23_X-FLASH-ALL-25B1.sin
- Extracting signature bootloader.cms
- Uploading signature ./boot/bootloader.cms
download:00000896
OKAY.
signature
OKAY.
- Extracting sparse chunk bootloader.000
- Uploading sparse chunk ./boot/bootloader.000
download:00c02000
OKAY.
Partition: bootloader have slot: yes
erase:bootloader_a
OKAY.
flash:bootloader_a
OKAY.
- End of bootloader_X_BOOT_SM8550_LA1_1_T_23_X-FLASH-ALL-25B1.sin

=========== FIRMWARES HISTORY LOG =============
NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:8550-0001_X_Boot_SM8550_LA1.1_T_23, sw_version:67.0.A.1.127
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:8550-0001_X_Boot_SM8550_LA1.1_T_23, sw_version:67.0.A.4.22
NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:8550-0001_X_Boot_SM8550_LA1.1_T_23, sw_version:67.0.F.1.135
NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:8550-0001_X_Boot_SM8550_LA1.1_T_23, sw_version:67.0.A.4.22

=================================================

Set slot 'a' active.

Device is put now out of flash mode.
Sent command: Sync
Sent command: continue.

 

[munjeni]

Yes, it works now, thanks!

 

[Hurt Copain]

Hi @munjeni I am not sure if this is a potential newflasher issue or just me being too experimental. I have the following error trying to flash a Japanese firmware. I more or less wanted to see what would happen. "Fails to verify cms while writing the first lun." Is this just to prevent different hardware versions from a potential hard brick?

Thank you!

Katbin

hurtcopain@pop-os:~/Desktop/Xperia 1 V/SO-51D_NTT DoCoMo JP_67.0.B.4.23$ sudo ./newflasher.x64 -------------------------------------------------------- newflasher.x64 v57 by Munjeni @ 2017/2023 -------------------------------------------------------- Determining available...

katb.in

 

[munjeni]

FAILFAILFailed to verify cms is message from phone, that mean FW you tried to flash is signed with certificate not compatible with your phone and you can't flash that FW