Ok, solved.
I'm trying using EMMA now. It doesn't seem to recognize my XA2 is fastboot mode right now. Any tips?
I disconnected the phone from the PC and shut it down. After 30 seconds I held the volume down key and and kept it pressed while connecting the phone to the pc. And EMMA recnognized the phone without problem
That's exactly what happened to me. I never could get Emma to work. It seems like there's an issue between emma and the h3123
so it flashed part of the file. might aswell flash the modem.img and run the fastboot getvar all and see if you're on the latest bootloader. which bootloader.sin did you make an img from?
Devices supported by the sony open device program, and "maybe" emma too (source):
Flashtool does need fsc script indeed, also its dev stated that he will release a compatible version soon.
Flashtool doesn't support the HXXXX series of devices yet.
I would try a older flash tool the newer flash tool did work when I had my Sony xa ultra so used older one and it worked.I'd be really surprised if a new version of Flashtool doesn't come out in the next week, that supports 2018 devices. It's ****ty the original firmware isn't available on Xperifirm - only the march update. I guess we'll have to wait. It's also upsetting to me Emma doesn't support this device
I'm in contact with Newflasher's developer ( @munjeni friend of mine ) and he's already aware of new A/B partitioning platform (Seamless update) in which all 2018 sony devices have.
Sony changed protocol a bit, to be precise he done some more hash files per some sin files (e.g. system.sin have two hash files)... I will need URB output from the Device Monitoring Studio usb sniff log durind Sony PC Companion software flashing, hope somebody have skills for do that! You need to sniff usb packets while you use Sony PC Companion software (repair - flash your phone), and usb in DMS must be set to URB view, when flashing stops save URB view to your PC and give me it. Without usb sniff log (URB mode) from DMS I can't update newflasher since I have no idea what sony changed in protocol. If you provide me that I can update newflasher easy!
The problem I have is the PC companion won't flash anything because the bootloader is unlocked (it tells me this whenever attempting a 'software repair'
I don't know how you will deal with this but here it's, let me know if I did something wrong, looks like some ancient language.
Thanks but your log is not enought since its too short! To be precise I need session where I can see whats going on with Sony last update to flashing protocol, e.g. SIN files which now have two hash files like system.sin ...
No need to export as html, just save session which can be load later! And you are right file is big. If you understand what I need maybe you can extract only that part of it where we can see that two hashes processed? It can be seen at a start of system.sin and maybe at the and of system.sin! Newflasher worki g good for all si. files, ta files ...etc but stop working on sin files which bave two hasher, thats new things implemented in flash protocol and I need to see whats going on with it to be abble implement tbat changes
