[TOOL] Newflasher (xperia command line flasher)

[churchner420]

I created a bug report on the Github site for the XQ-AS52 issue. I hope that's ok

 

[munjeni]

Very interesting. Trying a differrent cable right now as well. What exaclty did you exclude? And did you say 'no' to all the questions newflasher asked during the flash?
I always exclude partition and userdata. Btw you can't use flashtool cause flashtool doesn't even know the Xperia 5 II yet. I created an ftf file with it and changed the device name in the Meta inf folder to XQ-AS52 but then flashtool doesn't even show the firmware anymore...
This is definitely a newflasher issue and not depending on the cable or the usb port... @munjeni

Edit: tried a different cable but that does not change anything... Still looping on the Sony logo. Can't even get to the bootanimation.

You need to flash everything except persist.sin, that mean you need to flash partition and userdata too! Only file which you can remove from firmware is persist.sin, simlock do not need to be removed since newflasher will skip it by default, the rest of files please flash all including partitions and userdata, in that case it will boot. Bootloop you have is because of not flashed userdata and partition, in most case because incopatibility between new firmware and your userdata partition, there is many reasons for example selinux labels... so please flash all! All xperias mark 2 is cofirmed working with newflasher and apsolutly problem is not newflasher. If nothing help read this post https://xdaforums.com/t/tool-newflasher-xperia-command-line-flasher.3619426/page-68#post-83883385 , so set slot A active, than reboot device again to flash mode and than try again to reflash all. Hope this help.

 

[churchner420]

You need to flash everything except persist.sin, that mean you need to flash partition and userdata too! Only file which you can remove from firmware is persist.sin, simlock do not need to be removed since newflasher will skip it by default, the rest of files please flash all including partitions and userdata, in that case it will boot. Bootloop you have because of not flashed userdata and partitions in most case because incopatibility between new firmware and your userdata partition, there is many reasons for example selinux labels... please flash all! All xperias mark 2 is cofirmed working with newflasher and apsolutly problem is not newflasher. If nothing help read this post https://xdaforums.com/t/tool-newflasher-xperia-command-line-flasher.3619426/page-68#post-83883385 , so set slot A active, than reboot device again to flash mode and than try again to reflash all. Hope this help.

Ok thank you man. I will try flashing my device shortly.

Btw what about the qestions newflasher asks during the flash process. I usually answer everything with 'no', is that correct?
If it is still not working I will post another reply. Stay safe

 

[munjeni]

You ansvering with 'n' not with 'no' ! I can sugest you, start newflasher and confirm with 'y' when it ask you for gordon gate driver, it will extract driver exe in the same folder with newflasher, install new driver, reboot pc (important), than do steps above this post. Waiting your reply...

 

[churchner420]

You ansvering with 'n' not with 'no' ! I can sugest you, start newflasher and confirm with 'y' when it ask you for gordon gate driver, it will extract driver exe in the same folder with newflasher, install new driver, reboot pc (important), than do steps above this post. Waiting your reply...

i reinstalled the flash drivers and then flashed the device skipping persist.sin. Well, that worked, sort of... Iwas on customized EEA and wanted to switch to customized UK but after I flashed UK it still said GLOBALEEA in the service menu PLUS I could not repair the device with Xperia Companion anymore which I usually do after changing the firmware customisation. It seems to me that the device is stuck somewhere between EEA and UK...
Now I tried to flash back EEA and now the device doesn't boot because of corruption... I really don't know wha to do anymore...

 

[frozenwaffles]

Hi, i am getting this error. Can you help please?

Repartitioning...
Found partition_delivery.xml in partition folder.
Determining LUN0 size...
- Error, no DATA reply!

 

[munjeni]

Hi, i am getting this error. Can you help please?

Repartitioning...
Found partition_delivery.xml in partition folder.
Determining LUN0 size...
- Error, no DATA reply!

Double click newflasher and confirm with 'y' whien it ask you for gordon gate driver, install gordon gate, reboot your pc, try again

 

[munjeni]

i reinstalled the flash drivers and then flashed the device skipping persist.sin. Well, that worked, sort of... Iwas on customized EEA and wanted to switch to customized UK but after I flashed UK it still said GLOBALEEA in the service menu PLUS I could not repair the device with Xperia Companion anymore which I usually do after changing the firmware customisation. It seems to me that the device is stuck somewhere between EEA and UK...
Now I tried to flash back EEA and now the device doesn't boot because of corruption... I really don't know wha to do anymore...

Did you try diferent UK firmware? What I'm believing your device might have hardware fault, why I think that because even sony pc companion is unable to repair your phone, thats not possible otherwise. Is your bootloader unlocked? See "RIsk" section here -> https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ I realy have no other ideas what might be problem because two-three devices mark 2 reported problem but tousens of other devices have no problem with newflasher

 

[churchner420]

Did you try diferent UK firmware? What I'm believing your device might have hardware fault, why I think that because even sony pc companion is unable to repair your phone, thats not possible otherwise. Is your bootloader unlocked? See "RIsk" section here -> https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ I realy have no other ideas what might be problem because two-three devices mark 2 reported problem but tousens of other devices have no problem with newflasher

Nope the device is not unlocked hence Xperia companion should work. I think I know what the problem is. The firmware is still somehow stuck at Customized EEA which is what I can see in the service menu. But I am using the latest build number from Customized UK which is not yet available for Custimozed EEA but only for the UK and some other regions. Therefore I can't download, flash or repair the firmware with Xperia Companion cause the new build number doesn't even exist for the region the device is stuck on yet. I will see what happens when Sony releases the new firmware for EEA.
That sounds like a plausible explanation to me.
And that should also be the reason for my device's software corruption issue when reflashing the old EEA firmware cause that is a downgrade. That also sounds like newflasher isn't flashing every file from the firmware folder or is skipping a random step. That would explain why the device is still on customized EEA although I flashed UK successfully. Btw my phone runs on the UK firmware now but is still shown as EEA haha... Meaning, I am running a firmware that doesn't even exist yet... The problem should definitely lie within the flashing process of newflasher cause otherwise the downgrade should work es well... Hope you can work out what the problem is there cause I reinstalled all the drivers and Xperia Companion but everything I tried did not work.

 

[munjeni]

Nope the device is not unlocked hence Xperia companion should work. I think I know what the problem is. The firmware is still somehow stuck at Customized EEA which is what I can see in the service menu. But I am using the latest build number from Customized UK which is not yet available for Custimozed EEA but only for the UK and some other regions. Therefore I can't download, flash or repair the firmware with Xperia Companion cause the new build number doesn't even exist for the region the device is stuck on yet. I will see what happens when Sony releases the new firmware for EEA.
That sounds like a plausible explanation to me.
And that should also be the reason for my device's software corruption issue when reflashing the old EEA firmware cause that is a downgrade.

If sony companion see your phone corupt, that definitely mean you got something from UK firmware, e.g. modified some partitions which normaly didn't exist/get flashed trought UEE fw. If you do not have backup its non reversible changes. One partition modification and fota-ua is no more working, thats at least what we have found (for refernce https://xdaforums.com/t/xz1c-xz1-xz...eys-implemented.3795510/page-67#post-80599561 start read from that page)

That also sounds like newflasher isn't flashing every file from the firmware folder or is skipping a random step. That would explain why the device is still on customized EEA although I flashed UK successfully.

Nope. Newflasher design is to flash everything from inside a folder, every single .sin file, every single .ta file, partition folder and boot folder. You should provide newflasher log so we try analyse it!

Btw my phone runs on the UK firmware now but is still shown as EEA haha... Meaning, I am running a firmware that doesn't even exist yet... The problem should definitely lie within the flashing process of newflasher cause otherwise the downgrade should work es well... Hope you can work out what the problem is there cause I reinstalled all the drivers and Xperia Companion but everything I tried did not work.

If you see nothing in newflasher log it mean there is no failure on newflasher side! There is .ta file something like reset-customisations.ta if I'm not wrong, if those file is flashed customisation string from trim area is removed so on next boot it get filed with new customiation. But it looks like your phone got "mixed": things e.g. bootloader and some things from UK custom fw and some things from EEA. You should provide folder list from EEA and folder list from UK so we try compare. Also newflasher log from booth flashings so we try analyse and compare what is flashed and what is not. Without it we can't gues, to be honest I no want to continue further without logs / folder lists since I'm sure newflasher is ok here.

 

[jdilla1987]

Hello,

I recently flashed my firmware to the EE UK 58.0.A.28.25 from XperiFirm and everything went smoothly.
I wanted to try different ones so I attempted to flash others (as well as trying to go back to stock 58.0.A.22.21) but this ended up giving me the dreaded 'Your device is corrupt' bootloop.
I thought I had bricked my phone but I can flash the initial EE UK 58.0.A.28.25 and everything works fine again.

Am I missing something? It's been a while since I dabbled in flashing phones but the process seems pretty straight forward.
I always dumped the TA files and never touched the backup persist partition.

My phone is currently working but now I'm a bit weary to proceed with future flashes as I don't know what exactly the issue is. Is it not good practice to flash previous firmware versions?
Any help would be greatly appreciated!

• Sony Xperia 5 ii
• XQ-AS52

 

[munjeni]

Hi, you must flash whole rom including userdata, partition, boot delivery, all ta files, only file to delete is persist.sin, if that not help I realy have no idea without newflasher log. Here is allready discusion on this page related to UK firmware and xperia 5 II, I'm unsure right now whats going on

 

[churchner420]

Hello,

I recently flashed my firmware to the EE UK 58.0.A.28.25 from XperiFirm and everything went smoothly.
I wanted to try different ones so I attempted to flash others (as well as trying to go back to stock 58.0.A.22.21) but this ended up giving me the dreaded 'Your device is corrupt' bootloop.
I thought I had bricked my phone but I can flash the initial EE UK 58.0.A.28.25 and everything works fine again.

Am I missing something? It's been a while since I dabbled in flashing phones but the process seems pretty straight forward.
I always dumped the TA files and never touched the backup persist partition.

My phone is currently working but now I'm a bit weary to proceed with future flashes as I don't know what exactly the issue is. Is it not good practice to flash previous firmware versions?
Any help would be greatly appreciated!

• Sony Xperia 5 ii
• XQ-AS52

Yep that is the exact issue I am running into... If you try repairing your phone with Xperia Companion it will say that your device is temporairly incompatible during tthe flash process.

 

[churchner420]

Hi, you must flash whole rom including userdata, partition, boot delivery, all ta files, only file to delete is persist.sin, if that not help I realy have no idea without newflasher log. Here is allready discusion on this page related to UK firmware and xperia 5 II, I'm unsure right now whats going on

That is not a user related problem here. That definitely has to do something with newflasher cause that is the exact same issue I am having when I try to flash back to Customized EEA.

 

[churchner420]

If sony companion see your phone corupt, that definitely mean you got something from UK firmware, e.g. modified some partitions which normaly didn't exist/get flashed trought UEE fw. If you do not have backup its non reversible changes. One partition modification and fota-ua is no more working, thats at least what we have found (for refernce https://xdaforums.com/t/xz1c-xz1-xz...eys-implemented.3795510/page-67#post-80599561 start read from that page)

Nope. Newflasher design is to flash everything from inside a folder, every single .sin file, every single .ta file, partition folder and boot folder. You should provide newflasher log so we try analyse it!

If you see nothing in newflasher log it mean there is no failure on newflasher side! There is .ta file something like reset-customisations.ta if I'm not wrong, if those file is flashed customisation string from trim area is removed so on next boot it get filed with new customiation. But it looks like your phone got "mixed": things e.g. bootloader and some things from UK custom fw and some things from EEA. You should provide folder list from EEA and folder list from UK so we try compare. Also newflasher log from booth flashings so we try analyse and compare what is flashed and what is not. Without it we can't gues, to be honest I no want to continue further without logs / folder lists since I'm sure newflasher is ok here.

The files were all provided by XperiFirm. Just download the latest UK and EEA firmware. I didn't delete, modify or change anything in any way. I just took the folder XperiFirm created and flashed everything inside (skipping persist.sin). Maybe you can download both firmwares and have a look at the files in both folders maybe al well at the customisation files. Cause indeed there seems to be a problem with the customisation files.
I'm sorry that I can't deliver any log files cause really need my phone now and I will only reset it once more to get everything running properly.
There is another problem because of that mixed firmware I am running now: the Play Store security update is from May which is very old.

 

[munjeni]

That is not a user related problem here. That definitely has to do something with newflasher cause that is the exact same issue I am having when I try to flash back to Customized EEA.

You can't blame newflasher for 100 percent sure, might be firmware isue?? If you do not see any error in newflasher session it mean no problem with newflasher. Every single step in newflasher is with fully debug window, there is no chance for something to happen without displaying it inside main window. One more thing, maybe Sony tampered bootloader e.g. not allowing to install old bootloader over new bootloader I don't know, e.g.while you try to go back to UEE fw bootloader remain from UK fw. Remember one thing, last commandin newflasher is 'sync', when sync happen changes is aplied but we do not know whats happening on phone side, thats a question for bootloader notfor newflasher, newflasher just doing flash & handle every single step, whats going on after sync I don't care, thing which I care is to have no errors during flashing, the rest of things is question for developers. Even Sony pc companion fail to repair phone, so we can't blame booth, its question for fw developers why booth fail.

 

[churchner420]

You can't blame newflasher for 100 percent sure, might be firmware isue?? If you do not see any error in newflasher session it mean no problem with newflasher. Every single step in newflasher is with fully debug window, there is no chance for something to happen without displaying it inside main window. One more thing, maybe Sony tampered bootloader e.g. not allowing to install old bootloader over new bootloader I don't know, e.g.while you try to go back to UEE fw bootloader remain from UK fw. Remember one thing, last commandin newflasher is 'sync', when sync happen changes is aplied but we do not know whats happening on phone side, thats a question for bootloader notfor newflasher, newflasher just doing flash & handle every single step, whats going on after sync I don't care, thing which I care is to have no errors during flashing, the rest of things is question for developers. Even Sony pc companion fail to repair phone, so we can't blame booth.

Ok thanks for your replies. I was just trying to go back to EEA cause Xperia Companion doesn't work and on the old fw is was. But now when I go back to the old EEA version Xperia Companion is still showing the new UK build number when it says that the device is temporarily incompatible when the flashing procedure starts.
Can you please have a look at the fw files? I really don't know what to do cause if the phone really is somewhere in between the two customisations OTA updates might not work anymore and I don't want to see that happen hence I switched to the UK fw cause that one gets updates quicker

 

[munjeni]

Ok thanks for your replies. I was just trying to go back to EEA cause Xperia Companion doesn't work and on the old fw is was. But now when I go back to the old EEA version Xperia Companion is still showing the new UK build number when it says that the device is temporairly incompatible when the flashing procedure starts.
Can you please have a look at the fw files? I really don't know what to do cause if the phone really is somewhere in between the two customisations OTA updates might not work anymore and I don't want to see that happen hence I switched to the UK fw cause that one gets updates quicker

Compare folder from UK and UEE fw and let me know if you find some extra/missing files

 

[churchner420]

Compare folder from UK and UEE fw and let me know if you find some extra/missing files

I did that. Both folders look exactly identical. I really don't know what else to do...

 

[munjeni]

Can you give me output of those commandline newflasher commands?

newflasher Read-TA:2:2202
newflasher Read-TA:2:2205
newflasher Read-TA:2:2206
newflasher Read-TA:2:2207
newflasher Read-TA:2:2475
newflasher Read-TA:2:2498

Or if you have no idea how to do it please give me trim area dump via pm