yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] janolucero:
Don't worry, the drm keys arent back after the bootloader lock but image processing is working fine.

So I did all the procedure and my phone is back. Thank You <3
[Sony Cross-Device General] smudgy636:
hey, i have an xperia 5 iv, if i flash the latest firmware without the user data file is there a way of keeping root or will i have to root again?
[Sony Cross-Device General] Pandemic:
You need to patch your boot.img with magisk and fastboot it then you have root again.
[Sony Cross-Device General] kfrin:
Thank you for the info, I will not waste my time thanks to you! BTW I sold the phone.
[Sony Cross-Device General] RyTekk:
Try to copy partition folder from japanese firmware to the europe one and do flashing again. I met this issue on Xperia 5 and solved it by this way (but just on android 10, it doesn't seem to work on android 11).
[Sony Cross-Device General] munjeni:
@Pandemic Is there any temp root exploit for Kirin ??
[Sony Cross-Device General] Pandemic:
Dunno bro, i just patch my boot.img with magisk 25.2 and fastboot it and then i have root on my Xperia 1 iii with A13.
[Sony Cross-Device General] munjeni:
What about this https://xdaforums.com/t/xperia-1-5-...cve-2020-0041-including-magisk-setup.4146103/ is it working ? My xperia 10 dieid and I bought used one and on my surprise its locked, bootloader never unlocked, and now I'm searching for temp root exploit it order to continue my work on figuring out how DK key is working on device
[Sony Cross-Device General] Pandemic:
Dunno bro never tried it and i have xperia 1 mark 3 and that is for Xperia 1 and with your xperia 10 ? No bro dont do that, its jnly for Xperia 1 and 5, better patch your boot.img like i always do to avoid that., Just a tip 🫶💪
[Sony Cross-Device General] munjeni:
Log is incomplete and I have no idea about what is at the start of log! You should try USB2.0 port insted of USB3.X, also check for dust inside your phone usb port, also check usb cable, also try another usb cable... etc
[Sony Cross-Device General] Avengement:
Tried this tool to flash a stock ROM to an Xperia 10 Plus I4293 and it doesn't do anything. I put the exe into the same folder as the firmware files I downloaded with xperifirm, installed the flash driver, put the device in flash mode, started the program and then answered all the questions in the command prompt. In literally 2 seconds it claims the flash is complete and when I reboot the phone, nothing has changed and the custom ROM is still installed.

Any idea what's going on?
[Sony Cross-Device General] Pandemic:
Also type Y when ask wipe usedata ? And tell us more info please what you did and which options you choose in Newflasher.
[Sony Cross-Device General] Avengement:
Thanks for the quick reply. I tried it again using another machine with the folder containing the stock rom files directly on the desktop and it worked great. Not sure if the directory had anything to do with the issue but that resolved it for me since the Sony Mobile Flasher kept getting stuck at "device connected in flashmode"

Cheers.
[Sony Cross-Device General] IbrahimAnjum:
New version does support 5 ii A002SO? because its not working on my device as it starts looping on sony logo screen
[Sony Cross-Device General] munjeni:
Your device is supported but search about rollback protection to get idea!
[Sony Cross-Device General] Rindel:
Figured out, thanks!
[Sony Cross-Device General] 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
[Sony Cross-Device General] 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
[Sony Cross-Device General] munjeni:
Interesting! Can you post here boot_delivery.xml file?
[Sony Cross-Device General] munjeni:
Just search google there is ton of tutorials related to newflasher
[Sony Cross-Device General] linhshadoa:
I loaded for sony L3 dual I4312 , I tried other software but got error in boot_delivery.xml file. Thank
[Sony Cross-Device General] munjeni:
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
[Sony Cross-Device General] munjeni:
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
[Sony Cross-Device General] linhshadoa:
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 ?
[Sony Cross-Device General] 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
[Sony Cross-Device General] 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:
[Sony Cross-Device General] munjeni:
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.
[Sony Cross-Device General] ripppani:
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.
[Sony Cross-Device General] munjeni:
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
[Sony Cross-Device General] ripppani:
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!
[Sony Cross-Device General] Avengement:
What was there to "figure out"?

It's a one step drag and drop clearly stated in the first post of the thread.
[Sony Cross-Device General] ripppani:
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?
[Sony Cross-Device General] munjeni:
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
[Sony Cross-Device General] ripppani:
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!
[Sony Cross-Device General] 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.
[Sony Cross-Device General] ripppani:
Thank you for replying!

1. Is there some kind of log that I can read from the phone, so I can learn what exactly happened? (I did not save the complete output of Newflasher, but only the last few lines of it. I learned the importance of saving log the hard way...)

2. If I was to flash the Customized HK firmware back (the phone was Customized HK before), could it do more damage?
[Sony Cross-Device General] munjeni:
You can't damage it further mean userdata in case you not flasher userdata or some .ta files which respond to factory reset. Experiment yourself! Never ever touch trim area otherwise hard brick is guaranted! You must find which part of the rom cause bootloop and I can't tell you that since my phone is old xperia 10 and I do not have any rollback protection nor to test anything in relation to it! So if you ask me how it work I can tell you I don't know, I have not dealt with such a problem. You should read log and try to figure it out, log is stored inside trim area and you should read them by runnig newflasher from command line with this command:

newflasher Read-TA:2:2050

it will create dump.bin file, open it with an text editor and read.

You will read something like this https://xdaforums.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84077083 about vbmeta error in case rollback protection caused boot loop
[Sony Cross-Device General] ripppani:
Thank you very much! I will try that and let you know how it goes.
[Sony Cross-Device General] 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. Thank you so much for your suggestions!

But reading the log, I did not find any error about vbmeta, nor did I find load_and_verify_vbmeta:657: ERROR: vbmeta_a: Image rollback index is less than the stored rollback index.. The word rollback did not show up in the log at all. I think that means the problem was not caused by rollback protection. The log was dumped before I flashed the Customized HK firmware back.

I can provide the log so you can look into it, but could you first tell me, is there any sensitive information I need to redact before posting?
[Sony Cross-Device General] munjeni:
No need log! Did you figured out what was the problem?
[Sony Cross-Device General] ripppani:
I'm not familiar with the Android booting process so I can't be sure, but I found this in the log:

Unable to get Panel Config, Not Found
VB: RWDeviceState: read_req err ! status: 0 read status: -15
VBRwDevice failed with: 00000050
Unable to read display cmdline: 00000050

Do you know what that means?
[Sony Cross-Device General] munjeni:
Sorry don't know, here is some info in relation to VBRwDevice function https://o0xmuhe.github.io/2022/11/01/Qual-Android方案Unlock学习-以Oneplus7Pro为例/ its something in relation to verified boot chain, probably you have missed something last time when it failed to boot and that log is stored there... realy don't know, I'm not active here for almost 5 years and doing nothing on android for 5 years and forgot almost all. Things have changed a lot in 5 years, I'm not up to date! I'm just maintain newflasher and thats all, I am not interested in android hacking nor am I interested in android for 5 years : ) If you need any info please consult google search
[Sony Cross-Device General] ripppani:
I see. You've done a great job. Thanks!
[Sony Cross-Device General] FighterZ007:
Hello guys i want some help.

So i wanted to convert my japanese sony xz3 to global rom but i always get this error
[Sony Cross-Device General] munjeni:
Verify cms error mean that firmware is not compatible with your device
[Sony Cross-Device General] Garech:
I need some help with my Sony Xperia Pro-I. I want to root. The bootloader is unlocked. I tried to flash firmware with Newflasher and it looked like everything was going as expected. Many files flashed. Then it got to the end and my phone bricked. When I try again I get the following: "No usb device with vid:0x0fce pid:0xb00b !" Do you have any ideas? EDIT-I tried again and got the following:
[Sony Cross-Device General] munjeni:
error on powerdown is not critical if the rest is flashed without error, its well known that some devices sometimes respond with error to commands sync and powerdown and thats not problem. If your device can't boot and you have unlocked bootloader thats in most case isue with rom or you have not flashed everything, its always recommend to flash whole rom including all .ta files and all .sin files, bootdelivery & partition files including userdata, than if device not booting you should than care. Also dust inside phone usb port, bad cable, shaky usb port ...etc might cause errors durring flashing.
[Sony Cross-Device General] Garech:
Thanks
[Sony Cross-Device General] Garech:
One thing though, the error I showed happens once I accept the newflasher prompts, it doesn't actually move into the flashing stage yet. Is that still normal?
[Sony Cross-Device General] munjeni:
I must see log from the start to the end otherwise I have no idea
[Sony Cross-Device General] Garech:
Is that a Newflasher text logged as I used it, or a phone logcat or something else? I will look for it.
[Sony Cross-Device General] munjeni:
Are you sure you are in flash mode? Looks like you are in fastboot mode, it have diferent vid and pid! Fasboot mode is volumeup+power it give blue led, and flashmode is volumedown+power, green led light, newflasher work only with flash mode
[Sony Cross-Device General] Garech:
It was in recovery/flash mode, green light. Could this be due to drivers?
[Sony Cross-Device General] FighterZ007:
Thanks you
[Sony Cross-Device General] munjeni:
Migh be! Also make sure xperia companion is fully closed otherwise usb is busy and newflasher can't see usb device
[Sony Cross-Device General] Garech:
Thanks for your helpful responses. I am pleased to report that my Xperia Pro-I US model (XQ-BE62) is rooted!
[Sony Cross-Device General] Mohammed Ajeena:
Guys, need your help and support to flash my 1 iv docomo version (SO-51C) to global version, I've tried to flash to (XQ-CT54) version, but it didn't work out knowing that I unlocked the bootloader and when trying to flash, it gives the below error.

signature:0000089c

device from 2021 and up?

download:0000089c

OKAY.

signature

Error, signature OKAY reply, got reply: FAILFAILFailed to verify cms!
[Sony Cross-Device General] munjeni:
Your phone model is SO-51C . You can't flash an fw if it is not SO-51C using newflasher , every firmware have signature verifiction and if fw is not designed for your phone model bootloader will reject flashing it because of wrong signature. The only way is botloader unlocking and some tools like https://xdaforums.com/t/tool-windows-linux-android-apple-unpack-any-sony-firmware-file.3530077/ so convert sin files to raw format and flash it jurself manualy trought command line. Don't ask how I do't know, not an easy task.
[Sony Cross-Device General] Mohammed Ajeena:
Thanks for your help … so currently there is no way to flash a global ROM into my SO-51C easily like other versions
[Sony Cross-Device General] munjeni:
You should try one more time, if you getting "Failed to verify cms" thats mean rom is not compatible with your device.
[Sony Cross-Device General] Mohammed Ajeena:
Well, i've tried many times and got the same error and below are the steps used:

1- Unblock the bootloader through official Sony website to get the code and then used ABD method to unlock and its unlocked.

2- Downloaded the official ROM for customized UK through Xperia Firm software.

3- Used Newflasher v.55

4- Deleted all .ta files include the one in the boot folder.

5- Follow the steps to flash untill get the error which i was explained earlier.
[Sony Cross-Device General] FirasMM:
I try to convert the rom from japanese to global rom my phone is xperia 1 iv So-51c and i used newflasher v56 and rom XQ-CT54 but get this error
[Sony Cross-Device General] FirasMM:
If i change all file sin by sony_dump what should be i rename the extension
[Sony Cross-Device General] munjeni:
I don't have time for this, if you don't know I can't help sorry thats not easy and extremely danger for your phone, easily might brick your phone! My sugestion, don't play with it if you have no idea what you have need or what you have doing, otherwise big chance that you will need to buy new phone!
[Sony Cross-Device General] FirasMM:
Sorry, I have some information, but I need additional information from you. Now I am converting all sin files or only partition folder files, and do I change the extension to ext4 or what? Thank you very much for your generosity.
[Sony Cross-Device General] munjeni:
Just open it with an hex editor and look, it might be ext4, fat, binary...etc, tool allready produce extension at the end if it detect it as an ext4 for example. I don't want to participate further because I haven't worked on it for a long time, today's phones are much more secure than before, so it's very possible that their protection is much more complicated and that it's very possible that if you flash something manually, you'll kill the phone, and I won't say anything further. You have to fend for yourself! I just made tool, the rest is "do it yourself".
[Sony Cross-Device General] mantonio.lglez:
I also have this problem.

My Xperia XA2 Ultra displays "Your device is corrupt. It can't be trusted and will not boot." when trying to boot into flash mode, but after several tries it boots to flash mode. This issue started after a few months stored without use. If I try too boot it normally (to Android), it hangs in the Sony logo.

I have the correct driver installed (SOMC Flash Device), the phone is charged, tried different USB cables, used USB 2.0 ports. Also, I tried Flash Tool and got error "Unit 10021 does not exist ( Hex unit value 00002725 )", Xperia Companion threw me error "UEUpdateFailed UE_2005" and trying to update with newflasher resulted in "Error, didn't got TA write 'go into flashmode' OKAY reply! Got reply: FAILUnable to write to TA unit 10100".

I'm trying to flash Customized US and the phone hasn't had the bootloader unlocked nor has never been rooted.

Searched everywhere but couldn't find anything else, and already ran out of ideas. I have no technical knowledge aside from reading tutorials and flashing some other phones.

Any help would be much appreciated.
[Sony Cross-Device General] munjeni:
What you have done before your device died? Looks like you have corupted trim area partition. Did you done something to it, did you wrote something to partitions? Do you have trim area backup?

In relation to FlashTool seems your firmware boot delivery xml file have some error, did you downloaded firmware trought XperiFirm? If yes make sure you not delete anything from it, just keep everything including all ta files, all .sin files, boot folder and all the rest unchanged. I will download 50.2.A.3.77-R2B and let you know if something is wrong with it! Edit, I'm checked your firmware its ok!

Edit:

I have made test version for XA2 devices, let me know if it work! Before you flash make sure you have downloaded firmware using XperiFirm and you didn't deleted or modified something inside firmware folder! Let me know!
[Sony Cross-Device General] Noobie911:
I'm new with this stuff, and I wanna flash Japanese Global ROM for Xperia 5 II (Softbank A002SO to XQ-AS42), but I don't have any pc to work on atm. Can someone teach how to use newflash on android to android (via adb, or I guess termux or something)
[Sony Cross-Device General] mantonio.lglez:
Hi.

Thank you very much for spending some of your time with my problem.

The device was dead before I tried to flash it. I don't think I did anything to the trim area partition, given that I flashed the firmware I downloaded from XperiFirm, but no, I don't have a trim area backup. I didn't delete any files from the firmware folder, the only thing I changed after the first failed attempt was the partition.sin file that I moved to the "partition" folder I created.

The test version of Newflasher did give me a different output, which I will attach. It said something about error code 997, but I was using a USB 2.0 port, since I already had this error before. I also noticed every flashing software I tried failed at rebooting the phone to every mode, I don't know what's with that.

I'm starting to believe it's a hardware issue from being stored so long without use (I don't know a thing about hardware). Maybe it's the battery, even though the phones charges and stays on. I will try to get a new one and try to flash it again.

Thank you very much again.