yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] chris_j26:
I have flashed my xperia 5 ii using latest firmware and am having a couple of issues. I accidentally flashed the persist partition first time around and the device got into a boot loop.

I then flashed without persist and my device is still stuck in a boot loop on Sony logo.

Does '. ta' files need to be flashed? Anyone have any ideas to get device booting successfully again?
[Sony Cross-Device General] Jbrimb:
deleted
[Sony Cross-Device General] fumbles22:
Hello,

I just flashed my XZ premium using Newflasher. It worked first time without any problems at all WHICH IS AMAZING given that I spent a couple of days messing around with Flashtool.

I followed this guide:

https://teamandroid.com/download-newflasher-xperia-flash-tool/

but I downloaded Newsflasher from the post in this forum (since it was newer) and I downloaded the firmware I needed from Xperifirm (ie. not through flashtool since the Xperiafirm button wasn't working).

I didn't remove any ta files and the phone seems to be working just fine.

Overall, it was a hassle free flashing. 10/10.
[Sony Cross-Device General] Jbrimb:
Trying to write allow oem unlocking/unlock bootloader on 5II demo device :

Processing oem-unlock.ta
- Partition: 2
- Unit: 1046F (66671)
- Found specific unit which don't contain data.
download:00000000
OKAY.
Write-TA:2:66671
Error, didn't got OKAY reply! Got reply: FAILCommand not authenticated

Is this even possible ? service menu says rooting status : unlocking allowed yes, but it doesn't seem very true

Device has greyed out oem unlock setting.

reading 66671 isn't allowed either

writting to 0x8b2:

02
000008b2 0010 33 33 38 35 30 46 41 33 45 34 38 44 37 33 39 43

says ok, but bootloader doesn't get unlocked
[Sony Cross-Device General] tuha.juku:
Btw, I just succeeded to flash XQ-DE54 A14 upgrade from 67.1.A.2.182 to 67.1.A.2.208.

Did'nt erase userdata.

Flashtool can handle new devides!
[Sony Cross-Device General] munjeni:
Writing to trim area units higher than 0xffff is not allowed and reguire sake authentification. thats with reason, higher units is authentification protected, otherwise it will be easy to buypass stolen devices protected by pattern...etc.

Is this 33850FA3E48D739C your unlock key you received from Sony site? If not than try with your key! If yes I have no idea.
[Sony Cross-Device General] Jbrimb:
It is indeed the key I received, although I believe it to be useless since my demo model that wasn't supposed to have ever been sold to the public doesn't allow for oem unlocking in settings...

It would be interesting if there was a way to enable the option regardless, let me know what you feel about that situation

basically the phone says unlocking allowed, but the option is greyed out in settings. It has an app in which you enter your store's opening hours even after being flashed with regular Xperia software
[Sony Cross-Device General] munjeni:
Try unlock by oficial way using fastboot

fastboot oem unlock 33850FA3E48D739C
[Sony Cross-Device General] i7778:
Hi, first of all thank you for the tool! Unfortunately I did not work for my case - could you please help?

Phone: Xperia XZ2 Compact dual sim H8324

Android 10

Software: 1311-5320_52.1A.3.49 GLOBAL-A2 - user

File System Version GENERIC_52.1.A.3.49

Customization Version 1313-5469-R6C

The goal is to try installing couple files oem_X-FLASH-CUST From IN Firmware - hope it allows VoLTE to work in Australia.

GordonGate driver from the newflasher (Sony_Mobile_Software_Update_Drivers_x64_Setup.msi) installed.

Newflasher version v57

Attempt to flash gives an Access Denied error:

Phone has been restarted, factory resetted several times..... No difference.

Also run new flasher as administrator - No difference

Also got to Developer Option - Allow USB debugging - No difference

I DID NOT unlock boot loader - should I? .

Could you please advise on the next steps ?

Regards, i778
[Sony Cross-Device General] Kiyoshi15:
Hello.

I have trouble flashing Android 11 onto my Xperia 1 III (XQ-BC72, 512gb). Long story short - it was updated to A12 against my will (don't ask, it's too absurd) and I cannot stand this (or A13, for that matter) design. I spent more than 20 hours trying to understand this whole "flashing" thing, I never did anything with my phone that required this level of command options etc.

So - the thing is, my phone ends up with a bootloop every time I flash it with Android 11 files. I can switch back and forth between Android 12 and Android 13 and it works flawlessly, but Android 11 fails to start. I have original XperiFirm files of Android 11. I tried every version and region (Customized HK, SEA, CN, TW, UK, US; ver. 61.0.A.23.20,

61.0.A.15.35 or 61.0.A.11.23) - nothing works.

Yes, I have the bootloader unlocked. Yes, I tried these methods:

Flash Android 12 or 13 > unlock the bootloader > flash Android 11

Flash Android 12 or 13 > unlock the bootloader > flash Android 11 > lock the bootloader

Flash Android 12 or 13 > unlock the bootloader > lock the bootloader > flash Android 11

Flash Android 11 (while in a bootloop) > flash newer patch of A11

Ends with bootloop every single time. I don't get any errors in Newflasher. Yes, I use the "set_active:a" command.

I'm determined to rollback to Android 11, no matter the way I'll have to use. Will rooting make it possible? I've never rooted my phone, I have no knowledge whether it might help or not.

TL;DR

Could you please give me any hints or possible solution on how to flash Android 11 onto the Xperia 1 III when it was already updated to Android 12?

\\ bootloader unlocked & locked after flashing, I have original files, tried every version and region, nothing works
[Sony Cross-Device General] munjeni:
Try unlock bootloader and stay unlocked
[Sony Cross-Device General] munjeni:
You need to close Sony Xperia Companion Software, it make usb busy when not closed! : )
[Sony Cross-Device General] munjeni:
I'm regular member as like you without permissions to delete anybody account, you need to tell moderators for that.
[Sony Cross-Device General] Kiyoshi15:
This was the first thing I've tried. It stays in a bootloop for about 5 times, then displays a message "Your device is corrupt".
[Sony Cross-Device General] i7778:
Thank you, that worked! It was not actually Sony Xperia Companion Software, it was some ADB soft for old Mediatec phones that I have on my machine installed ages ago. Somehow it activates when Xperia XZ2 is connected and yes, it does block USB. Once the soft removed , the flasher works fine - thank you!

P.S. It would be worthwhile to put this scenario in the NewFlasher FAQ.
[Sony Cross-Device General] RyTekk:
Hi @munjeni, recently we can't cross flash Xperia due to this issue, and I have had an idea. Can we extract cms from correct firmware files, copy somewhere and put it at the process when newflasher extract, so that we can overwrite the cms and newflasher can flash the incorrect firmware files from another variant? Could you please write an option for newflasher so that we can flash some single files and have a delay to copy and overwrite the cms, so we can bypass the verification (I just need to flash oem.sin to get VoLTE so it wouldn't take a lot of time to manually copy cms file). Thanks for consider my idea.
[Sony Cross-Device General] munjeni:
No! Newflasher is just flasher, one who check files for integrity and signature is bootloader!
[Sony Cross-Device General] RyTekk:
I know newflasher is, and should be just a flasher. I mean can I copy cms from correct fw file of my phone, then flashing sin files from fw of other variant (global for example), stop at extracting cms from sin file, then overwrite it with the cms file I copied above from correct fw, and continue flashing process, so I can get the sin file flash complete from other fw variant. Is it possible since at the moment, newflasher process is too fast to I can do that bypass method.
[Sony Cross-Device General] munjeni:
You first need to learn what digital signatures is!! Than you will iunderstand how things work. YOu must understand that every sin file contain digital signature of the main file, for example lets do an example, manufactures doing things this way: system image is signed by rsa256, hash (signature, cms whatever you call them) is attached at the end of file or at the separated file, so when you modify (one bit is enought!) to system image than signature is no more valid and your system file become invalid!!! The same if you modify signature!!! So when you send system file to bootloader bootloader will check booth files and if it is invalid your file will become invalid too and auto rejected, thats how things work. So your idea is apsolutly bad idea! : ) Please don't write ideas here, I am apsolutly not interested, I don't have free time for this.
[Sony Cross-Device General] leungalv:
Just used Newflasher to update Xperia 5 IV to latest stock firmware. Easy and painless, thank you :)
[Sony Cross-Device General] Equinocs:
I would like to update my ACE III to the newest security patch level while keeping my settings&userdata. As I understand it I need to delete all the files marked as NOERASE in the update.xml - is this correct? Just to be safe, should I also delete persist* ?
[Sony Cross-Device General] munjeni:
Its always recommend to flash whole firmware, but if you realy no want to lose userdata see this post https://xdaforums.com/showpost.php?p=72692665&postcount=220 :)
[Sony Cross-Device General] tanipat:
It is unlocked but i did not mean it is unlocked bootloader. I am not consider to unlock bootloader now as i did not know the effect like losing Bravia engine or some sort is still present in this versio. will test for you soon mate
[Sony Cross-Device General] munjeni:
Yes sure! Can you try test.rar?
[Sony Cross-Device General] tanipat:
[MENTION=4120742]munjeni[/MENTION] Here it is Bro :)

--------------------------------------------------------
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

Trying to get list of all commands...
- help sent.
HELP[0x19]:

00000000 46 41 49 4C 43 6F 6D 6D 61 6E 64 20 6E 6F 74 20 FAILCommand not
00000010 73 75 70 70 6F 72 74 65 64 supported

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:
Many thanks! Booth commands failed :( Thats it, tool is a stable, seems I will no more experiment with it, enjoy all! :)
[Sony Cross-Device General] sev7en:
Good morning,

the download link for the newest version doesn't work anymore... can you please check it?

Thanks,
[Sony Cross-Device General] munjeni:
Hello! I'm checked it, it works :)
[Sony Cross-Device General] oneheart:
sorry，the log lost :mad:
[Sony Cross-Device General] munjeni:
Can I get log from this version -> https://xdaforums.com/showpost.php?p=72749556&postcount=246 , anybody?? That didn't help only me, but you too and everybody who have plan to use future much safer version!! Fill free...
[Sony Cross-Device General] perutz:
thanks:):):):):):):)
[Sony Cross-Device General] san.13:
:D. thank you very much :D
[Sony Cross-Device General] tanipat:
i would trying to help here again mate, but i am quite busy these day i think i am able to sit down and work for you this week end. if still nobody involve in the meantime. say again your work is very appreciated me and i am sure you already make alot of people happy as still no other dev work on our device yet, yes included even long contributor like flashtool's dev. keeps it up man
[Sony Cross-Device General] san.13:
Download link does not work.

Regards
[Sony Cross-Device General] munjeni:
It work, just folow!
[Sony Cross-Device General] san.13:
The download link is still not working.

regards
[Sony Cross-Device General] munjeni:
Can you give screenshoot?
[Sony Cross-Device General] san.13:
I do not have an screenshoot.

The problem is that the page returns practically to the starting point.

I have thanked you.

After login with my nick the page always returns to the login point without putting the download link

regards
[Sony Cross-Device General] munjeni:
It working perfectly! You just need to type san.13 excatly the same like your nick here, than click submit, download will show
[Sony Cross-Device General] san.13:
Ok downloaded, thanks.
[Sony Cross-Device General] gschpasti:
Hello,

I've tried to flash a Xperia XA2 (H3113) which had Lineage installed but does not start anymore, it cannot enter bootloader or recovery, device is just buzzing when power it on.

But flashing does not work:

Product: H3113
Version: 0.4
Bootloader version: 1310-0301_X_Boot_SDM630_LA3.0_P_38
Baseband version: 1311-5291_50.2.A.0.400
Serialno: xxx
Secure: no
Loader version: XFL-SDM630-204
Phone ID: FAILPhone-id not supported
Device ID: E1A90C07
Platform ID: 000AC0E1
Max download size: 104857600
Sector size: 512
Rooting status: ROOTED
Ufs info: FAILUfs-info not supported
Emmc info: MICRON,0x014e,0x0
Default security: ON
Keystore counter: 2
Security state: FAILSecurity-state not supported
Sake root: A672
S1 root: S1_Root_70f0
Root key hash: 5F01088791F1DDAD20DB0DF59453943E4D275929A01705C83502AD5403F9010F
Slot count: 2
Current slot: a
Battery level: 72

Device is put now in flash mode.

Repartitioning...
partition_delivery.xml not exist in partition folder or no partition folder.

Processing partition-image_X-FLASH-ALL-18AE.sin
- setting up inflate...
- infflating, please wait...

- inflate returned: 0
- gzpipe: ok.
- gunziped ok.
- Extracting from partition-image_X-FLASH-ALL-18AE.sin
- Extracting signature partitionimage_0.cms
- Uploading signature ./partition/partitionimage_0.cms
signature:0000053c
Error, didn't got signature OKAY reply! Got reply: FAILFailed to init keystore

any idea how what can be done to get it alive again?
[Sony Cross-Device General] k_basara:
My phone is Xperia 5 IV (CQ72). I've flashed it several times before, and there are always difficulties, but eventually it will work and I can finish flashing my phone.

Not this time. I can set active slot but can't flash the phone. I can't figure out why.

I need help. Command line output is in the spoiler. Thanks.

Spoiler content hidden.
[Sony Cross-Device General] Cuonglla117:
Check your driver and connection between pc and phone. I can see in the log that the PCs not really recognize the phone, like the drivers got messed up
[Sony Cross-Device General] munjeni:
Probably you killed your trim area partition during flashing Lineage, after reboot your phone is hardbricked so you now have missing kaystore which is part of the trim area. I'm in doupt you can do anything right now.
[Sony Cross-Device General] munjeni:
Thats known problem, simply close xperia companion completely since companion software make usb port busy!
[Sony Cross-Device General] k_basara:
Hi, thanks for your work on this tool and your reply for help, the problem here is I didn't even install Xperia Companion.

I also flashed several other Xperia phones on this PC, namely G8441, G8142, G8342, SO-02K, without any problem.
[Sony Cross-Device General] 2769a:
I don't know what problem I encountered, can anyone tell me how to solve it?
[Sony Cross-Device General] munjeni:
You can't flash J9210_Customized HK_55.2.A.4.332-R9C since your device model is SO-01M
[Sony Cross-Device General] Chemikill:
Not working for me on an Xperia 1 II

https://i.postimg.cc/YSg7FRMt/Error.jpg

Any ideas?
[Sony Cross-Device General] Chemikill:
So I finally got this to work after updating the sony mobile driver on the PC. Now the problem is that the phone is stuck in a bootloop and will not boot into the stock rom failing after the sony logo.

Why?
[Sony Cross-Device General] munjeni:
Rolback protection -> https://xdaforums.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-72610228
[Sony Cross-Device General] Chemikill:
Thank you.

The only problem is that I don't see any instructions or a guide on how to fix this. Both the stock rom and the custom rom are android 12. What do I need to do to relock the bootloader to reset rollback protection?
[Sony Cross-Device General] munjeni:
Google it! A lot of tutorials you can see on google search, for example this is how to unlock bootloader, similar thing is for relock bootloader, just search xda

Unlock bootloader | Developer World

developer.sony.com
[Sony Cross-Device General] Chemikill:
The commands to relock the bootloader are not working...

https://i.imghippo.com/files/HyyWr1716371350.jpg
[Sony Cross-Device General] munjeni:
Read this detaily! https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader
[Sony Cross-Device General] Chemikill:
Those are the instructions I used to unlock the device. It mentions nothing about how to RELOCK the device to reset rollback protection. I also tried the same commands with the unlock code at the end and the same error is returned.
[Sony Cross-Device General] munjeni:
Your device model is? If you checked the link above, Sony explained how to check for "device is allowed to unlock", make sure your device is allowed for bootloader unlock, thats a first thing to check. Seccond thing to check, search on xda, is is your device allow for relocking! Unlocking bootloader as you can see on Sony site explain that if you unlock your bootloader you will void waranty! If you relock bootloader even you woid waranty since you can't hide unlocking status from Sony. If your device is not allowed for unlock bootloader you can't unlock them! If your phone is allowed for unlock read carefully instructions from link above. Before you unlock bootloader search xda and check if your model have features for relock bootloader, in case no than double think about do you realy need to unlock bootloader! Unlocking bootloader and you lost some device functionality. Relocking bootloader and you get back those functionality. So double check things before you attempt to unlock bootloader! If your bootloader is unlock allowed and your device have not implemented relocking feature probably your device also do not have implemented rollback protection. Rollback protection have only device which have relock allowed feature. If nothing help try Sony PC Companion software, it will repair your device in case you can't get it to work with newflasher. If neither help I'm sorry thats all I can help. I am not even active here and to be honest I do not have free time for this, everything you need to know ask in your device model subforum in hope you get better help there. Hope this help.
[Sony Cross-Device General] Chemikill:
XQ-AT51

The same model mentioned in the link you provided mentioning the possibility to relock.

Newflasher caused the bootloop after flashing so that is why I am posting in this thread.
[Sony Cross-Device General] munjeni:
Newlasher is not responsible for bootloop you have. Rollback protection is in most case isue you have -> https://emteria.com/blog/android-security#:~:text=Anti-rollback protection is an,upgraded to a newer one. Whats your option, is to flash excatly the same rom your had working or to flash newer one. Option two is, unlock bootloader, flash an rom. Option 3, unlock bootlader, relock bootloader to reset rollback index to zero, flash an rom. If you ask here about your device I don't know, I have old xperia 10, so in relation for your model the best thing is to contact somebody with xperia 1 II model or ask in xda sony xperia 1 II subforum since many of users with xperia 1 II know what to do and might help you if you post in the right subforum. My old xperia 10 do not have rollback protection feature, don't have relock feature and I have no idea how it work, androids simply not interest me for a long time. When I get an new phone, probsbly not very soon, I will try investigate something, right now I have no idea. Just gaved you some links in hope it help and give you some idea.
[Sony Cross-Device General] Chemikill:
I'm currently trying to flash the same stock rom with newflasher. This is what's causing the bootloop.

If I flash a custom rom to get out of the bootloop the device has no EMEI number and will not read from the sim card so therefore no calls or data access.

Sony companion software complains the device has an unlocked bootloader and to relock it before it can do a repair.

So the only option I have is to relock the bootloader to reset rollback protection as you claim but none of the relock commands are working which leaves me stuck in a bootloop of the stock rom or stuck with a broken custom rom that can't make/receive calls or access the internet.
[Sony Cross-Device General] sieghartRM:
Have you tried Sony Emma flash tool?

Download the flash tool | Developer World

developerworld.wpp.developer.sony.com

How to use Sony Emma flash tool:

How to flash your device | Developer World

developerworld.wpp.developer.sony.com
[Sony Cross-Device General] munjeni:
I would need to see your flash log from newflasher. Its strange that your device is unlocked and your device can't boot, it must boot! Might be that you have skipping some files when flash for example .ta files? Procedure is, download an rom by XperiFirm, than do not delete any single file from folder, than siply start flashing rom and confirm userdata erase. And also if neither help try another stock rom, one might work for you.