[TOOL] Newflasher (xperia command line flasher)

[Rindel]

Figured out, thanks!

 

[linhshadoa]

i am having error with Newflasher software , when i load to boot_delivery.xml the error , the machine hangs on logo , can someone help me , thanks

 

[gelomon]

Hello @munjeni, I am new here in newflasher, I am currently using Xperia Ace III (japan only model -- ntt docomo). I have successfully flashed the latest android 13 without any issues. The next thing I want is to try to cross-flash other variant -- same xperia ace iii but from other network (au or ymobile) but I encounter and issue that it about match hash, is there a way to overcome this?

Why I want to crossflash: I want to test the modem files from other variant & other variant is more updated on security patch

 

[munjeni]

i am having error with Newflasher software , when i load to boot_delivery.xml the error , the machine hangs on logo , can someone help me , thanks
View attachment 5884823

Interesting! Can you post here boot_delivery.xml file?

 

[munjeni]

I am seeking assistance with using Newflasher on my mac M2 chip and would appreciate any guidance or advice that you can provide. Thank you in advance for your time and help.

Can you please walk me through the steps of using Newflasher on my Mac? I am new to this tool and would like to ensure that I am using it correctly. Any additional tips or precautions that I should be aware of would be greatly appreciated.

Just search google there is ton of tutorials related to newflasher

 

[linhshadoa]

Interesting! Can you post here boot_delivery.xml file?

I loaded for sony L3 dual I4312 , I tried other software but got error in boot_delivery.xml file. Thank

 

[munjeni]

Hello @munjeni, I am new here in newflasher, I am currently using Xperia Ace III (japan only model -- ntt docomo). I have successfully flashed the latest android 13 without any issues. The next thing I want is to try to cross-flash other variant -- same xperia ace iii but from other network (au or ymobile) but I encounter and issue that it about match hash, is there a way to overcome this?

Why I want to crossflash: I want to test the modem files from other variant & other variant is more updated on security patch

Every rom for an specific model or provider is signed by special platform key for example if your device is SOG08, you should not flash firmware from for example A203SO because those rom is signed with diferent platform key and your phone will reject any rom during flash with newflasher, you must use excatly the same rom for your model e.g. SOG08, just find what is your phone model and download right rom for your phone model trought xperifirm

 

[munjeni]

I loaded for sony L3 dual I4312 , I tried other software but got error in boot_delivery.xml file. Thank

Is your phone development version? In case yes you should try to manualy modify xml file, replace:

<ATTRIBUTES VALUE="PLF_ROOT_HASH=&quot;0000000000000000000000000000000000000000000000000000000000000000&quot;"/>

modify it to:

<ATTRIBUTES VALUE="DEFAULT_SECURITY=&quot;OFF&quot;"/>

See how newflasher work in relation to bootdelivery search https://github.com/munjeni/newflasher/blob/master/newflasher.c#L4788

 

[linhshadoa]

Is your phone development version? In case yes you should try to manualy modify xml file, replace:

<ATTRIBUTES VALUE="PLF_ROOT_HASH=&quot;0000000000000000000000000000000000000000000000000000000000000000&quot;"/>

modify it to:

<ATTRIBUTES VALUE="DEFAULT_SECURITY=&quot;OFF&quot;"/>

See how newflasher work in relation to bootdelivery search https://github.com/munjeni/newflasher/blob/master/newflasher.c#L4788

my phone is international version , stuck with password and i run the software again , i have fixed boot_delivery.xml file but flashed again error still . Should i keep the file Dragon_XBootConfig_MiscTA.ta ?

 

[linhshadoa]

@munjeni
I keep the file Dragon_XBootConfig_MiscTA.ta then proceed to run it, the phone is on, thank you, maybe should pay attention so that others get the same error

 

[ripppani]

Solved! The device is back alive! I downloaded and flashed the Customized HK firmware back. Now the device has no problem booting, and all my personal data are intact. Thanks!

Original question:

Hello @munjeni .

The device is Sony Xperia 10 II XQ-AU52 Customized HK. I downloaded Customized SEA firmware (59.2.A.0.463) with XperiFirm. I deleted the three files starting with "appslog", "diag", and "userdata", and kept everything else. I put newflasher.exe in the firmware folder, and ran newflasher.exe to flash it into the phone. Now the phone will not boot, showing "Your device is corrupt. It can't be trusted and will not boot. You device will be powered off in 5 seconds."

My guess is that flashing the file starting with "persist" caused this. Newflasher did not ask me whether to flash persist. (Edit: The author of Newflasher pointed out that persist is skipped by default and no longer prompted starting from version 47. I was using version 55.)

Is there a way to recover the data inside the device?

I have a basic understanding in adb and fastboot.

Please help. Thank you.

 

[munjeni]

Hello @munjeni .

The device is Sony Xperia 10 II XQ-AU52 Customized HK. I downloaded Customized SEA firmware. I deleted the three files starting with "appslog", "diag", and "userdata", and kept everything else. I put newflasher.exe in the firmware folder, and ran newflasher.exe to flash it into the phone. Now the phone will not boot, showing "Your device is corrupt. It can't be trusted and will not boot. You device will be powered off in 5 seconds."

My guess is that flashing the file starting with "persist" caused this. Newflasher did not ask me whether to flash persist. Is there a way to recover the data inside the device?

I have a basic understanding in adb and fastboot.

Please help. Thank you.

1000-th times the same question here.... google for word "rolback protection" on Sony phones and how to deal with them! You simply can't easy backup your personal data after your device is unable to boot, but there is a chance to backup them for example you should unlock bootloader and temporary boot an cwm recovery and trought cwm recovery you probably should access those important personal data. Number one thing before dealing with firmwares is: backup personal data, pictures and everything important before flashing any firmware otherwise you might end up losing all personal data, and I hope everybody here is learned that hard way as like me. So first thing to do before flashing anything is data backup first, move it to pc, hard disk, usb stick... etc thats the last thing to do before flashing phone. Any later help is too late.

 

[ripppani]

1000-th times the same question here.... google for word "rolback protection" on Sony phones and how to deal with them! You simply can't easy backup your personal data after your device is unable to boot, but there is a chance to backup them for example you should unlock bootloader and temporary boot an cwm recovery and trought cwm recovery you probably should access those important personal data. Number one thing before dealing with firmwares is: backup personal data, pictures and everything important before flashing any firmware otherwise you might end up losing all personal data, and I hope everybody here is learned that hard way as like me. So first thing to do before flashing anything is data backup first, move it to pc, hard disk, usb stick... etc thats the last thing to do before flashing phone. Any later help is too late.

I'm so sorry for asking the same question again. But I do wish you could guide me on following questions or tell me where I can find answers myself. Thank you very much.

1. Is it necessary for the bootloader to be unlocked before I can boot a custom recovery?
2. How do I unlock the bootloader? Should I use the fastboot flashing unlock command?
3. How can I trigger rollback protection if I am not flashing an older version? My device was 59.2.A.0.463, and what I flashed was also 59.2.A.0.463.

I did learn the importance of backup the hard way.

 

[munjeni]

I'm so sorry for asking the same question again. But I do wish you could guide me on following questions or tell me where I can find answers myself. Thank you very much.

1. Is it necessary for the bootloader to be unlocked before I can boot a custom recovery?
2. How do I unlock the bootloader? Should I use the fastboot flashing unlock command?
3. How can I trigger rollback protection if I am not flashing an older version? My device was 59.2.A.0.463, and what I flashed was also 59.2.A.0.463.

I did learn the importance of backup the hard way.

1. yes. Without unlocking you need Sony signed stufs otherwise you need to unlock bootloader to be able to boot/flash custom roms
2. https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/
3. I realy don't know, you probably need excatly the same rom and probably to flash whole rom including user data and the rest of things, that mean your private data from userdata partition will be erased

The same thing, if you unlock bootloader bootloader unlocking procedure will erase your userdata! You simply have less options for backing up userdata, I can sugest try to download excatly the same rom you have or newer one, that way you have chance to boot your device keeping userdata intact. Also when newflasher promt you for keeping userdata confirm with yes. Download firmware by firmware and try every one maybe one going to boot your device. If you still can't get device to boot than you do not have many options left and probably you will need to unlock bootloader and that way your userdata will be erased. Hope you know that when bootloader is unlocked your DK key (device unique key) will be forewer deleted and your phone will void waranty. See what they say https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/ and also read post 4 about unlocking and relocking bootloader to reset rollback protecton index to zero, and ask in your device forum about possibility for relocking bootloader on your device model thats a first thing before unlocking bootloader! For example I was in hury to unlock bootloader on xperia 10 thinking it can be later relocked as like on xperia 1 and 5 but it was not possible on xperia 10 since Sony disabled relocking on xperia 10, so ask somebody first before you unlock bootloader!

As of version 47 persist partition is no more flashed, its skipped by default!

- version 47 (15.07.2021)
Removed prompt for persist.sin flashing, now its by default skip. Implemented bootloader log retrieval at the end of flashing for better understanding when something goes wrong. Implemented firmware log history retrieval for those who want to know history of the flashed firmwares

hope this help

 

[ripppani]

1. yes. Without unlocking you need Sony signed stufs otherwise you need to unlock bootloader to be able to boot/flash custom roms
2. https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/
3. I realy don't know, you probably need excatly the same rom and probably to flash whole rom including user data and the rest of things, that mean your private data from userdata partition will be erased

The same thing, if you unlock bootloader bootloader unlocking procedure will erase your userdata! You simply have less options for backing up userdata, I can sugest try to download excatly the same rom you have or newer one, that way you have chance to boot your device keeping userdata intact. Also when newflasher promt you for keeping userdata confirm with yes. Download firmware by firmware and try every one maybe one going to boot your device. If you still can't get device to boot than you do not have many options left and probably you will need to unlock bootloader and that way your userdata will be erased. Hope you know that when bootloader is unlocked your DK key (device unique key) will be forewer deleted and your phone will void waranty. See what they say https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/ and also read post 4 about unlocking and relocking bootloader to reset rollback protecton index to zero, and ask in your device forum about possibility for relocking bootloader on your device model thats a first thing before unlocking bootloader! For example I was in hury to unlock bootloader on xperia 10 thinking it can be later relocked as like on xperia 1 and 5 but it was not possible on xperia 10 since Sony disabled relocking on xperia 10, so ask somebody first before you unlock bootloader!

As of version 47 persist partition is no more flashed, its skipped by default!

- version 47 (15.07.2021)
Removed prompt for persist.sin flashing, now its by default skip. Implemented bootloader log retrieval at the end of flashing for better understanding when something goes wrong. Implemented firmware log history retrieval for those who want to know history of the flashed firmwares

hope this help

Thank you for trying to help! Particularly thank you for pointing out the changes in version 47 of Newflasher. I was using version 55.

I will keep in mind that unlocking bootloader erases userdata.

I really don't want to bother you with my questions, but I hope it's okay if I came back with more questions...

Again, thanks!

 

[Avengement]

Figured out, thanks!

What was there to "figure out"?

It's a one step drag and drop clearly stated in the first post of the thread.

 

[ripppani]

1. yes. Without unlocking you need Sony signed stufs otherwise you need to unlock bootloader to be able to boot/flash custom roms
2. https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/
3. I realy don't know, you probably need excatly the same rom and probably to flash whole rom including user data and the rest of things, that mean your private data from userdata partition will be erased

The same thing, if you unlock bootloader bootloader unlocking procedure will erase your userdata! You simply have less options for backing up userdata, I can sugest try to download excatly the same rom you have or newer one, that way you have chance to boot your device keeping userdata intact. Also when newflasher promt you for keeping userdata confirm with yes. Download firmware by firmware and try every one maybe one going to boot your device. If you still can't get device to boot than you do not have many options left and probably you will need to unlock bootloader and that way your userdata will be erased. Hope you know that when bootloader is unlocked your DK key (device unique key) will be forewer deleted and your phone will void waranty. See what they say https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/ and also read post 4 about unlocking and relocking bootloader to reset rollback protecton index to zero, and ask in your device forum about possibility for relocking bootloader on your device model thats a first thing before unlocking bootloader! For example I was in hury to unlock bootloader on xperia 10 thinking it can be later relocked as like on xperia 1 and 5 but it was not possible on xperia 10 since Sony disabled relocking on xperia 10, so ask somebody first before you unlock bootloader!

As of version 47 persist partition is no more flashed, its skipped by default!

- version 47 (15.07.2021)
Removed prompt for persist.sin flashing, now its by default skip. Implemented bootloader log retrieval at the end of flashing for better understanding when something goes wrong. Implemented firmware log history retrieval for those who want to know history of the flashed firmwares

hope this help

Hi!

Newflasher output "Set slot 'b' active" at the end of flashing.

What I believe is that in devices with A/B system updates, while one slot is being flashed, the other slot remains intact. Does that mean I can just switch to the other slot and boot normally?

 

[munjeni]

Hi!

Newflasher output "Set slot 'b' active" at the end of flashing.

What I believe is that in devices with A/B system updates, while one slot is being flashed, the other slot remains intact. Does that mean I can just switch to the other slot and boot normally?

As a rule, it should be like that, but it is not! The is sin files with name _other_.sin which is always flashed to the diferent slot and thats a problem

 

[ripppani]

As a rule, it should be like that, but it is not! The is sin files with name _other_.sin which is always flashed to the diferent slot and thats a problem

Thank you for the reply!

1. Are all the "sin" files always flashed to both slots? Or, are they flashed into somewhere that are not duplicated in two slots?

2. If Newflasher output "Set slot 'b' active" at the end of flashing, does that mean those files that are only flashed into one slot flashed into slot 'b'?

Sorry for all these questions!

 

[munjeni]

Things from boot folder is flashed to booth slots. Other files is flashed to current slot. Files contain in name "_other" is flashed to diferent slot e.g. you are on slot B its flashed to slot A, Sony design. That "_other" cause problem to have independent slots.