yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] munjeni:
Its something realy strange, for example this one:

Error writing command 'set_active:b'! Looks like slot B partitions is damaged.

Your phone is slot A active allready, You should try next steps:

I can sugest start from flashing partition since in most case your partitions is somehow messed up, since the newflasher got an error on the bluetooth and it didn't reach the flashing partition.sin, but it is important, so create an empty folder and put newflasher to it, than create "partition" folder in the same folder and put partition.sin file to partition folder, try flash! if everything went ok, reboot your device. Than flash bootdelivery, if succed try one by one sin file and see which one cause problem, start from bigest one for example system.sin and system_other.sin . I'm believing if you flash partition.sin sucesfully the rest will be easy (in case there is no hardware isue for example damaged emmc where partitions is stored).
[Sony Cross-Device General] AbibPirates_79:
Sir can i ask? why always try to Flash Xperi 5 II Dual Sim - XQ-AS72

here says " Your Device is Error/Corrupt and cannot be trusted? "

i use newflasher_v55

any how to fix it sir? thank your sir ^_^
[Sony Cross-Device General] kodein:
Newflasher doesn't work for me either. After successfully flashing bootlop... Sony xperia 10IV. I had to fix the FW using sony companion
[Sony Cross-Device General] billycar11:
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...

xdaforums.com

try this method it works on my 1 IV
[Sony Cross-Device General] kodein:
OK, I'll try. I just want to ask if I should delete the files with the extension *.TA from the FW folder? In some instructions for using newflasher, I read that they should be removed... And it was not in the instructions that I should use the command via cmd: newflasher set_active:a
[Sony Cross-Device General] billycar11:
No don't delete them

Yes follow that guide exactly
[Sony Cross-Device General] munjeni:
New version, newflasher now can be run on Linux and Android!
[Sony Cross-Device General] Ambroos:
Flashed XZ Premium successfully! Thanks a ton for this tool!

Also wiped user data accidentally by forgetting to exclude userdata... ? My fault!
[Sony Cross-Device General] mario_jr:
Well, Im really noob on Xperia world.

Nah.. nevermind! Worked flawlessly

Regards!
[Sony Cross-Device General] tanipat:
yes if i know how to :)
[Sony Cross-Device General] munjeni:
Just simple do the same like you flashing, but this time do not flash anything, run test from an empty folder :)
[Sony Cross-Device General] Ladduro:
First time sony user, looking into flashing process. So, if I am going to flash only, I dont need to backup TA right? I will not loos DRM things unless I unlock bootloader. Please confirm.
[Sony Cross-Device General] munjeni:
Yes! :)
[Sony Cross-Device General] tanipat:
The log is here mate :)

--------------------------------------------------------
newflasher.exe by Munjeni @ 2017
--------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_b00b#6&3a757eec&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_B00B\6&3A757EEC&0&1

Trying to dump DRM key
- Read-TA:2:66667 sent.
DRMKEY[0x1D]:

00000000 46 41 49 4C 43 6F 6D 6D 61 6E 64 20 6E 6F 74 20 FAILCommand not
00000010 61 75 74 68 65 6E 74 69 63 61 74 65 64 authenticated

Product: G8142
Version: 0.4-SONY-0.1
Bootloader version: 1306-5035_X_Boot_MSM8998_LA1.1_N_59-A
Baseband version: 1306-8501_45.0.A.5.1
Serialno: CB512E66JV
Secure: yes
Loader version: XFL-MSM8998-N-35
Phone ID: 0000:35700808021756,0000:35700808021757
Device ID: BC5D534D
Platform ID: 2005E0E1
Max download size: 104857600
Sector size: 4096
Rooting status: ROOTABLE
Ufs info: TOSHIBA,THGAF4G9N4LBAIRB,0100
Emmc info: FAILEmmc-info not supported
Default security: ON
Keystore counter: 1
Security state: BA1894F07A55612C78DAADBA68D953CB4B3D2133
Sake root: D159
S1 root: S1_Root_e69c
Root key hash: C30DEC2471CEA311E6918657367B51068A39583BBF89FD68B379BCD5A709AB1B

Device is put now in flash mode.

No .sin files in partition dir...
You must extract partition.zip into 'partition' folder if you want flash partition image!

Processing .sin files...
Created ouput folder flash_session
No .sin files in current dir.

Processing .ta files...
No .ta files in current dir.

Processing boot delivery...

boot_delivery.xml not exist in boot folder or no boot folder.

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

End.
Press any key to continue . . .
[Sony Cross-Device General] munjeni:
Thank you mate a lot! Sadly but no way for dumping drm key :( I thinked that drm security is somehow forgoten in new flash protocol but seems Sony didn't forgot to secure that drm key, he secured it as like on all xperias :):) Thinked to make tool for dumping and on the fly converting trim area dump to .img but have no sense without drm key :(
[Sony Cross-Device General] tanipat:
i hope in you post your tools in XZ premium or even XZS forum. so that you will get more feedback :) i do want you to continue your good work, as some devs nowadays has less time and time. just this tools is life saver for so many people i am sure about it mate
[Sony Cross-Device General] yselimk:
Thanks for job...
[Sony Cross-Device General] munjeni:
Unit 8B2 which is expected to be created after unlocking (unit which keep unlock key) no more exist on newer models like xzp! So unlocking bootloader by writing unlock key to non existant unit 8b2 is no more case for 2017 models! In worst case seems sony patched mechanism for unlocking bootloader! Maybe nobody will be able to restore locked trim area since unit 8B2 is out of trim area!??! If this is true than this https://www.xda-developers.com/easily-backup-the-ta-partition-on-your-sony-xperia-device/ is seems useless for in case!
[Sony Cross-Device General] celtique:
Hi

Can we use your tool with 2016 devices?

Original XA Ultra here
[Sony Cross-Device General] munjeni:
Hi, for pre 2017 models you can use xflasher https://xdaforums.com/crossdevice-dev/sony/dev-xflasher-command-line-flasher-t2986634
[Sony Cross-Device General] munjeni:
New version is out, removed feature for unlocking bootloader.
[Sony Cross-Device General] munjeni:
How can we dump loader, anybody have idea? Need to get list of available commands :) [MENTION=4351315]tanipat[/MENTION], can you help me? Please test version from attachment, run it the same like you done with last test.rar version if you can please :)

Edit:

Is your device unlocked?
[Sony Cross-Device General] tanipat:
[MENTION=4120742]munjeni[/MENTION] yes my phone is unlocked hongkong unbranded. will test it for you tonight
[Sony Cross-Device General] munjeni:
Thanks! Oh this https://xdaforums.com/showpost.php?p=72717079&postcount=229 is seems a reason because you allready unlocked... waiting current test anyway :fingers-crossed:
[Sony Cross-Device General] Aripex:
Thanks for the tool munjeni. So for those that have successfully flashed using this method, can I just confirm what files should be excluded? I was looking at the following:

userdata.sin

fota_reset.ta

Should I be removing any others?
[Sony Cross-Device General] Xperia_Xavier:
Any guys have try it on Xperia 1 V? Does it work with HK firmware on China edition?
[Sony Cross-Device General] elukyan:
Yes. I'd successfully flashed SEA firmware on CN version of Xperia 1 V by v55.

Log attached.
[Sony Cross-Device General] 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 !
[Sony Cross-Device General] Jayram2000:
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.
[Sony Cross-Device General] AJHutchinson:
I always have that issue i have to reinstall the sony drivers anytime I want to flash
[Sony Cross-Device General] munjeni:
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!
[Sony Cross-Device General] Hurt Copain:
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.
[Sony Cross-Device General] 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
[Sony Cross-Device General] Hurt Copain:
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.
[Sony Cross-Device General] AJHutchinson:
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 👀😴😂
[Sony Cross-Device General] AJHutchinson:
worked like a charm thanks for letting us know about this bug much appreciated buddy
[Sony Cross-Device General] munjeni:
Can you post here bootdelivery.xml file?
[Sony Cross-Device General] 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)
[Sony Cross-Device General] Hurt Copain:
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.
[Sony Cross-Device General] 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!
[Sony Cross-Device General] Hurt Copain:
Thank you so much will try after work and confirm!!
[Sony Cross-Device General] Hurt Copain:
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.
[Sony Cross-Device General] munjeni:
Yes, it works now, thanks!
[Sony Cross-Device General] 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
[Sony Cross-Device General] 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
[Sony Cross-Device General] Hurt Copain:
Ok thank you, I was thinking that.
[Sony Cross-Device General] Laclevuinhon:
friend, OTA update work???
[Sony Cross-Device General] Hurt Copain:
Hi, only if your bootloader is locked. You can use newflasher with it locked as well. So, if I was you and wanted OTA, I would be sure to relock my bootloader. It's faster to update manually though. I check xperifrm daily and if there is an update copy newflasher to the unpacked contents, sent perms and flash
[Sony Cross-Device General] Laclevuinhon:
Thank you so much 😁
[Sony Cross-Device General] nemster:
normal stock upgrade somhow killed my modem/baseband and its not working. is it possible to only flash modem firmware without affecting installed system?

which files would i need to keep in the directory?
[Sony Cross-Device General] elukyan:
Hmm... Trying to flash update fw to Xperia 1 V. Same region - SEA.

--------------------------------------------------------

newflasher.exe v57 by Munjeni @ 2017/2023

--------------------------------------------------------

Determining available free space by GetDiskFreeSpaceEx:

Available space to caller = 833489 MB

Total space on current drive = 999257 MB

Free space on drive = 833489 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#5&158e3aec&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}

Class Description: SOMC Flash Device

Device Instance Id: USB\VID_0FCE&PID_B00B\5&158E3AEC&0&1

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

y

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.

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

ERROR: GetOverlapped_in_Result: failed with error code 31 as follows:

A device attached to the system is not functioning.

ERROR: IO_OTHER: failed with error code 22 as follows:

The device does not recognize the command.

- Error write! Need nBytes: 0x8 but done: 0x0

nBytes[0x0]:

- Error writing command continue!

Closing device.

Press any key to continue . . .
[Sony Cross-Device General] munjeni:
Close Sony PC COmpanion software first!
[Sony Cross-Device General] elukyan:
Oh, thanks!

Tried on another PC, all flashed fine.
[Sony Cross-Device General] elukyan:
I have bootloader unlocked, so I don't receive OTA updates. Only manual updates with XperiFirm and Newflasher.
[Sony Cross-Device General] SonyZFan:
Not sure if it's the new July update or Newflasher V57 but Google Play System Update is finally working on my 1 III. Previously both OTA and Google Play updates were not working even with a locked bootloader. Hopefully this means that OTA will work now but I'll need to wait for the next update to confirm. If not maybe the only way is to flash persist.
[Sony Cross-Device General] UniquePhillip:
Edit: For some reason my phone needed to be restarted a few times, after a couple restarts it started working again. 🤷

I flashed my 1 V DQ54 with stock 67.0.A.4.51 downloaded with xperifirm and now my phone is stuck in a bootloop. The flash indicates a success

...
- 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.4.22
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.51

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

Set slot 'b' active.

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

Done.
Closing device.
Press any key to continue . . .

When I put my phone in flash mode and run `newflasher Read-TA:2:2050` it just asks me if I want to keep userdata, then does nothing, regardless of what I pick. I searched my entire hard drive for dump.bin and there are no files. Do you have any ideas what to do?

XQ-DQ54_Customized EU-UK_67.0.A.4.51>newflasher.exe Read-TA:2:2050
--------------------------------------------------------
newflasher.exe v57 by Munjeni @ 2017/2023
--------------------------------------------------------

Determining available free space by GetDiskFreeSpaceEx:

Available space to caller = 125133 MB
Total space on current drive = 589739 MB
Free space on drive = 125133 MB
Device path: \\?\usb#vid_0fce&pid_b00b#5&2108ad5d&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: SOMC Flash Device
Device Instance Id: USB\VID_0FCE&PID_B00B\5&2108AD5D&0&3

Do you want to keep userdata? Type 'y' and press ENTER to confirm, or type 'n' to erase userdata.
y
[Sony Cross-Device General] UniquePhillip:
Oh, good news. Seems like my phone just needed to be restarted a couple times. When rebooting into flash mode again, everything works. I wish I could delete old posts.

Now I am wondering if you can help me with this. This is the bootloader log from dump.bin

[ERROR @ ta_interface.c:343]:
Unable to delete TA unit 2334
Make Decisions
PBA ID: V5052671A (1)
Vendor(0x00000000)->Sony(0x00000000)
Setting existing handle
Startup flags: [ONKEY PRESSED]
Warmboot reason: [COLDBOOT]
[ERROR @ sony_boot_config_parser.c:837]:
None or incorrect vbus_pulse configuration!
SW service triggering key detected
VBUS not detected
Recovery service trigger detected
Service mode detected: [RECOVERY]

What does this mean? I can't find anything about it. I don't even know which is the problem, although I'm guessing the 2nd (sony_boot_config_parser), based on its proximity to Recovery service trigger detected
[Sony Cross-Device General] UniquePhillip:
Once again I post too soon. Using the xperia companion tool I was able to recover the phone and re-flash, everything works now. Thank you for creating this tool, I am so excited to have a rootable version with 5G 🙏
[Sony Cross-Device General] Laclevuinhon:
after flash rom SEA for China mainland, it's defferent from th mark ii that i flashed, i dont know other mark V version looks like enything. Sorry my english!
[Sony Cross-Device General] xhermitdashx:
Has anyone tried this with the Xperia 1 V?

a root guide is missing for the new device, only loose information spread all over.

Cheers!
[Sony Cross-Device General] UniquePhillip:
Steps are same as 1 IV except you flash init_boot.img instead of boot.img
[Sony Cross-Device General] guhvanoh:
Have you actually checked the XDA 1V forum? I suggest you do so first.
[Sony Cross-Device General] xhermitdashx:
Yes I have, that's why I ended up here.

1V forum is mostly filled with questions, not much info. (for now)
[Sony Cross-Device General] guhvanoh:
See this for details. So long as you don't have the US version. That can't be rooted or so the story goes...
[Sony Cross-Device General] xhermitdashx:
yeb, saw this yesterday, was posted just after I asked also xD

Unfortunately i do have the US model, but i think theres still ways around it.

going to end conversation on 1 V here since its bit off topic for this thread. Thanks all
[Sony Cross-Device General] oopps24:
Hello guys,

i have a problem. I hanged every time on chunk system.006 on my H3213 XA2 Ultra. I tried many fws. I crashed every time on chunk system.006. xperia flash tool too. companion and emma say phone is locked. can not restore. can you help? Only bootloop, it restart after sony logo. only fastboot and flash mode works. What can i do?.

i flashed XA2 Plus and XA2 and it works perfect. Only on XA2 Ultra H3213 i have the problem.

Thx for your help