yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] munjeni:
This is not done by newlfasher, newflasher skips all that units by default. And you can't revive that simlock using it from another phone, every phone have it unique! Also those simlock unit is proteced by simlock signature from unit 0x851. If you continue to edit your trim area your phone will die with only red led and without a way to repair! Go to their center for repair
[Sony Cross-Device General] munjeni:
Unlocking bootloader trought newflasher is not a confirmed thing! It might not work at all. Unlock your bootloader by oficial way -> https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader

Read post #4 for idea
[Sony Cross-Device General] munjeni:
I not going to support things unrelated to newflasher, please ask in your device model subforum for things related to your device model problems. Unlock your bootloaders as its a only way to bypas rollback protection. There is a trick to reset rolback index to zero, just read post 4 for idea. Things, problems, questions...etc they go in circle about 40 pages allready, the same problems, the same questions...etc. I can't help you, it was five years ago when I played with sony phones, even I was not an expert in that time, now I forgot 90% of things and I can't help, ask somebody if you are unsure. Don't ask in this thread.
[Sony Cross-Device General] munjeni:
Remember, if you want your phone to use for experiments unlock your bootloader first! Thats a first thing to do! Than you can flash whatever you want. Locked bootloader is for security and integrity, today rollback protection and many other protections and newflasher is simply not enought for it. Think twice, read twice, next time!
[Sony Cross-Device General] zdob:
Hi Yf6,

I have tried to flash different versions but i always getting same version in Firmware history log.

=========== FIRMWARES HISTORY LOG =============
NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1322-1669_X_Boot_SM8350_LA1.0_R_31, cdf_version:Unknown: Nov 5 2021/04:40:34, fs_version:Unknown: Nov 5 2021/04:40:34, sw_version:61.0.A.20.13
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1322-1669_X_Boot_SM8350_LA1.0_R_31, cdf_version:Unknown: Nov 27 2021/04:44:01, fs_version:Unknown: Nov 27 2021/04:44:01, sw_version:61.0.A.20.50
NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1322-1669_X_Boot_SM8350_LA1.0_R_31, cdf_version:Unknown: Dec 22 2021/14:39:17, fs_version:Unknown: Dec 22 2021/14:39:17, sw_version:61.0.A.25.7

=================================================

And we both have similar chipset QC888 in our smartphones. I was thinking that my Pro-I have hardware issue. From the other hand you have similar issue and it seems that something wrong in software.

Actually, I have tried qUnlockTool(paid tool for sim lock remove). In some cases(other users used it for bootloader unlocking ) this tool was helping to unlock bootloader but not helped me.

I went through unlocking SIM, removing FRP(remove reset protection lock) and remove MLR lock( remove firmware downgrade lock).

But smartphone still is not able to unlock bootloader and upgrade firmware even Xperia Companion right after unlocking did't help.

Need to find other way how to unlock bootloader.

munjeni can i get some extra logs from TA to get more clear picture about what is going on inside my smartphone( not only TA2050)?​
[Sony Cross-Device General] munjeni:
There is some more trim area parts which keep logs but I didn't remember. Just dump trim area and look into HEX lines with bigger size, convert those hex to bin and see

Here you can see some units and their desciption https://github.com/munjeni/trimarea_tool/blob/master/trimarea_tool.c

https://github.com/munjeni/trimarea_tool/blob/master/include/miscta_units.h

Try dump unit 2010 (0x7da) it will show you if your bootloader is unlock allowed! If it show "ROTING_ALLOWED=0" you can't unlock bootlader.

#define TA_UNIT_2_SENS_DATA 0x7DA //simlock / bootloader unlock allowed, etc.

Units higher than 65535 (0x10000) can't be read trought bootloader protocol, reguire sake authentification key which only sony tehnicians have. So google lock, drm key and things is in those higher region and can't be read/write.

#define TA_UNIT_2_GOOGLE_LOCK 0x1046F	//google lock ( allow bootloader unlock in dev settings )

I'm unsure if those google lock affect bootloader unlocking! Don't try to modify unit 0x7da any way! Its protected by signature from unit 0x851 !
[Sony Cross-Device General] Pukysxd:
Hello . I have problems with my Sony Xperia 1 IV . I every time get bootloop and device corrupted messages. I change slot to a , but phone not boot . i can see newsflasher skip reset_non_secure_adb.ta
[Sony Cross-Device General] zdob:
Hi, have you tried Xperia Companion to recover it?
[Sony Cross-Device General] Pukysxd:
Yes , but same problem i get bootloop and later corrupted message
[Sony Cross-Device General] zdob:
It seems that you are at least the third person with similar issue in smartphone. How did you get it?
[Sony Cross-Device General] Pukysxd:
After update my phone not turning on and latter i trying reinstall firmware with newflasher V57 . I tried all the ways but nothing helped. My phone remains with the same problem
[Sony Cross-Device General] zdob:
What was original version and which one you have used for the update?
[Sony Cross-Device General] Pukysxd:
was 64.1.A.0.977 to 64.1.A.0.990 i upload newflasher procces
[Sony Cross-Device General] munjeni:
Reading your log I can see it was not skiped

Processing reset-non-secure-adb.ta
- Partition: 2
- Unit: 9B6 (2486)
- Found specific unit which don't contain data.
download:00000000
OKAY.
Write-TA:2:2486
OKAY.

What say sony pc companion software, what they do? To be honest I forgot when I used those software recently, the thing which I remeber there was two options, repair and fresh install? Do you have using repair or fresh install? Sory if I am wrong, I realy not used those software for a long time! Other thing, I can see allso you have "keep userdata", why not you try not to keep it?

Rooting status: ROOTABLE , consider unlocking bootloader if nothing help!
[Sony Cross-Device General] Pukysxd:
Xperia companion repair firmware done ,but phone gets bootloop all the same . I try keep set keep users data , but newflasher show this error.
[Sony Cross-Device General] munjeni:
Where you see error? Its ok "unit contain no data" ! It jusr errases unit 0x9b6!

Can you list me all patition sin files from partition folder?

Try not to keep user data while fresh installing, sometimes keeping userdata cause bootloop!
[Sony Cross-Device General] zdob:
it seems that userdata is not flashed:

Processing userdata_X-FLASH-ALL-6348.sin

<NOERASE>userdata_X-FLASH-ALL-6348.sin</NOERASE>

- Skipping userdata_X-FLASH-ALL-6348.sin
[Sony Cross-Device General] Pukysxd:
I wonder what the problem is, because my phone recovery factory reset is not working
[Sony Cross-Device General] munjeni:
Yes because he confirmed with Y for "keep user data" and newflasher skiped flashing userdata and many other files from xml with tag <NOERASE> I told him to try to confim keep userdata with N when newflasher ask for keeping userdata.
[Sony Cross-Device General] munjeni:
Can you show me the list of files with partition-image-LUN in the name ?
[Sony Cross-Device General] Pukysxd:
I am every time press N because i don't want keep user data .
[Sony Cross-Device General] Pukysxd:
Yes but please wait
[Sony Cross-Device General] munjeni:
your log show that you confirmed newflasher to keep userdata, so files like userdata, metadata and some other is not flashed in that case

Processing metadata_X-FLASH-ALL-6348.sin
<NOERASE>metadata_X-FLASH-ALL-6348.sin</NOERASE>
- Skipping metadata_X-FLASH-ALL-6348.sin

picture on your phone shows something in relation to medatata which is probably in relation to your keep userdata confirmation = Y, Try reflash again but this time confirm with N
[Sony Cross-Device General] munjeni:
This is your log? I can see that confirmation is Y
[Sony Cross-Device General] Pukysxd:
Yes , but when I get home I will try again only with N selected and send the whole process
[Sony Cross-Device General] munjeni:
Ok, let us know! Files skiped during flashing in your case because of confirmation Y was:

appslog_X-FLASH-ALL-6348.sin

diag_X-FLASH-ALL-6348.sin

metadata_X-FLASH-ALL-6348.sin

userdata_X-FLASH-ALL-6348.sin

at least what I can see in log. Your phone screen shows that something with metadata is wrong, probably because of skiped metadata_X-FLASH-ALL-6348.sin flash! If you doing the same "keep userdata" while using sony pc companion software, result is the same : )

Hope somebody share here list of sin files contain in the name LUN, what I need to know is how many files is with LUN0, how many with LUN1 and how many with LUN2
[Sony Cross-Device General] Pukysxd:
Same problem .. bootloop
[Sony Cross-Device General] munjeni:
What now your recovery says? Do you see metadata error?

How many sin files with name LUN0, how many with LUN1, how many with LUN2, thanks for that info!
[Sony Cross-Device General] Pukysxd:
Now my recovery done factory reset

Here all LUN file
[Sony Cross-Device General] munjeni:
Thank you, so your phone boot normaly now after factory reset?
[Sony Cross-Device General] Pukysxd:
No . Same problem. Bootloop
[Sony Cross-Device General] munjeni:
Interesting! Try now pc companion, now you have all the partition seems correct and probably pc companion is able to fix problem if not I have no idea whats going on
[Sony Cross-Device General] meeotch1:
Anyone know what the newflasher prompt "Save user data?" in newer versions actually does? Does it ignore a predefined set of *.ta files or something? And is it safe to answer "no" if you've already deleted the *.ta and other files you want to ignore?

I was trying to flash a single file (cust-reset.ta) today, and I noticed that when I answered "yes" to Save User Data, it output indicated that cust-reset.ta was being ignored.
[Sony Cross-Device General] PavelBronco:
I've had a similar bootloop problem after attempting to upgrade my Xperia 10 V (XQ-DC54) from 68.1.A.2.93 to the fresh 68.1.A.2.170 update from Xperifirm. In my case eventually some combination of repeatedly flashing both slots (the last regular OTA before rooting had left the phone in slot B), giving up and wiping the user data, too [1], locking and re-unlocking the bootloader and switching to booting from slot A finally fixed the problem. Unfortunately I can't say which of the above things exactly got things unstuck again.

[1] My phone had got itself into some weird state where most files on the internal storage had become inaccessible, so I had just wiped and started re-installing it anyway, so one more wipe wasn't that big a tragedy.
[Sony Cross-Device General] munjeni:
"Do you want to keep userdata?" is a feature to keep your private userdata like pictures and etc intact! But better idea is to backup them first before any attempt to flash an rom!!! Because as you can see many peoples have isue with boot loop after flashing an fw, so if you do not created backup of your userdata you will lost them forever in case you get boot loop caused by unsucesfull flash and you will need to erase userdata!

cust-reset.ta is part of <NOERASE> , you can see that in one of xml files comming with rom, for idea! "Do you want to keep userdata?" confirmed with N skips all that files marked with <NOERASE>
[Sony Cross-Device General] munjeni:
Yes, trick here is to reset rollback protection index to zero, in that case you can downgrade rom to a lover version. Trick here is unlocking bootloader and relocking it, when relock happen index is zero! : ) Do in mind, not all models have relock feature, so before atempting to unlock bootloader double think about that, read forums and ask somebody about your device model if you are unsure about relock feature posibilities! Also check if you device model is good enough new model with rollback protection. And also, allow bootloader unlock inside settings menu must be enabled, otherwise you will end up in lock state as somebody here faced that problem and is not able to unlock bootloader but have boot loop without a way to enter that settings meny to enable option. Double think and be carefull, don't hurry!

Unlocking bootloader is a recomended option for those who need phone for experimenting with firmwares. And locked bootloader is for those who need phone for everything else. Paying 1k euro for an phone and using that phone for experiments you must agree is not an option, so unlock your bootloader first! Better idea? : )

Trim area? Never ever touch it!! Otherwise you will need new motherboard!

"Do you want to keep userdata?" is a feature to keep your private userdata like pictures and etc intact! But better idea is to backup them first before any attempt to flash an rom!!! Because as you can see many peoples have isue with boot loop after flashing an fw, so if you do not created backup of your userdata you will lost them forever in case you get boot loop caused by unsucesfull flash and you will need to erase userdata!

I linked this post to post no #4 for those who didn't read and for me to not repeat the same things.
[Sony Cross-Device General] meeotch1:
Thanks for the reply. I assume you mean that confirming "Do you want to keep userdata?" with "y(es)" will skip the NOERASE files. (As you would normally delete *.ta files in order to avoid a full wipe of user data.) Correct?

It's interesting that the update.xml file doesn't include all the *.ta files... here's update.xml:

<?xml version="1.0" encoding="utf-8"?>
<UPDATE>
<SYSTEMPARTITIONIMAGE>partition.zip</SYSTEMPARTITIONIMAGE>
<BOOT>boot.zip</BOOT>
<NOERASE>appslog_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>diag_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>ssd_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>Qnovo_X-FLASH-ALL-C93B.sin</NOERASE>
<FACTORY_ONLY>persist_X-FLASH-ALL-C93B.sin</FACTORY_ONLY>
<NOERASE>userdata_X-FLASH-CUST-C93B.sin</NOERASE>
<NOERASE>cust-reset.ta</NOERASE>
<NOERASE>master-reset.ta</NOERASE>
<RESETNONSECUREADB>reset-non-secure-adb.ta</RESETNONSECUREADB>
<NOERASE>reset-wipe-reason.ta</NOERASE>
<SIMLOCK>simlock.ta</SIMLOCK>
</UPDATE>

And here are the *.ta files from that firmware:

auto-boot.ta
cust-reset.ta
fota-reset.ta
master-reset.ta
osv-restriction.ta
reset-kernel-cmd-debug.ta
reset-non-secure-adb.ta
reset-wipe-reason.ta
simlock.ta

Looks like fota-reset.ta, osv-restriction.ta, and reset-kernel-cmd-debug.ta are not set to NOERASE. (And presumably not skipped by newflasher in "Keep User Data" mode.
[Sony Cross-Device General] munjeni:
yes

yes, I have no idea why it is excluded from xml, let us know if you find something interesting! Normaly all the files is flashed when "keep userdata" is set to N, thats a clean way for installing an rom, and for years it was no problem at all, whats going on with recent devices I have no idea. Simlock and persist is by default skiped by newflasher. And also some trim area units is skiped by default (never ever touch them!):

memcmp(unit, "000007D3", 8) == 0 || /* hardware config */

memcmp(unit, "000007DA", 8) == 0 || /* simlock */

memcmp(unit, "00000851", 8) == 0 || /* simlock signature */

memcmp(unit, "000008A2", 8) == 0 || /* device name */

memcmp(unit, "00001324", 8) == 0 || /* device id */

memcmp(unit, "0001046B", 8) == 0) { /* drm key */
[Sony Cross-Device General] lusterW:
Hi guys,

My phone is xperia 5 V, has been posted here before, but it didn't solve the problem.

XQ-DE72 “your device is corrupt” is displayed after the HK_67.1.A.2.182 is updated

My phone none Root none unlock the Bootloader. The original version is CN_67.0.F.3.57, then newflasher was successfully updated to HK_67.0.A.6.99. I tried to update to HK_67.1.A.2.182 but failed. After the phone was restarted, the message "your...

xdaforums.com

The phone none Root none unlock the Bootloader. original version is CN_67.0.F.3.57, then newflasher was successfully updated to HK_67.0.A.6.99.

I tried to update to HK_67.1.A.2.182 but failed. After the phone was restarted, the message "your device is corrupt" was displayed. I switched to slot A and slot B and then flash the firmware, but the fault was the same.

I upload log file, please help.

Thanks guys.
[Sony Cross-Device General] Asshwin@2002:
Processing oem_other_X-FLASH-CUST-A2CD.sin

- Extracting from oem_other_X-FLASH-CUST-A2CD.sin

- Extracting signature oem.cms

- Uploading signature C:\Users\Asshwin\Desktop\Custom rom Sony 5 II\Sony unlock\SO-52A_NTT DoCoMo JP_58.2.B.0.560\flash_session\oem.cms

signature:000008b5

Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms

Set slot 'b' active.

Device is put now out of flash mode.

Sent command: Sync

End. You can disconnect your device when you close newflasher.exe

Press any key to continue . . .
[Sony Cross-Device General] Asshwin@2002:
still same problem
[Sony Cross-Device General] munjeni:
The situations is described in last 2-3 pages, read it! I'm unsubscribed until something new.
[Sony Cross-Device General] tuha.juku:
Hi.

Same here. Device is Xperia 5 V XQ-DE54, rooted with Magisk, trying to flash XQ-DE54 Customized EU-UK 67.1.A.2.182 (Android 14).

Phone was restarted and message "Press power key to continue" is shown. When I press it, it stays in the Sony boot logo.

The process goes normally when i flash XQ-DE54 Customized EU-UK 67.0.A.6.99 (Android 13) firmware.

What could be wrong?
[Sony Cross-Device General] lusterW:
My device is XQ-DE72, but no root.

I'm confused.
[Sony Cross-Device General] munjeni:
Your choice was:

Do you want to keep userdata? Type 'y' and press ENTER to confirm, or type 'n' to erase userdata.

y

try next time with N ! If nothing help see https://xdaforums.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-89236275
[Sony Cross-Device General] lusterW:
In fact, I've tried not keeping userdata, and the result is still the same, confusing
[Sony Cross-Device General] munjeni:
Ok, see page-two in back, even pc companion didn't help, I'm believing its a bug in recent devices. Also somebody is able to enter into recovery menu and wipe things. You can enter into recovery?
[Sony Cross-Device General] flyingfishfinger:
Hi,

I accidentally (hard?)-bricked my XZ1C G8441 by doing something silly, I tried to take a full block device backup from my previous G8441 and put it on this new one - now it doesn't boot of course. I can't even enter fastboot or ADB, the LED never turns blue with I use the VOL- & PWR key.

The previous state was LOS20, rooted w/ Magisk and bootloader unlocked of course. I tried recovering with Xperia Companion, when I plug in normally it says "Unlock your device" - of course I can't because it does not boot. I also tried the option where the device does not show up, but then it ends in the message "Xperia Companion cannot update this device since the boot loader has been unlocked." - and I don't want to (nor do I know how, in this state) to relock the bootloader.

Now, trying to recover with newflasher. I downloaded one of the G8441 firmware versions using XperiFIrm (does it matter which?) and did NOT delete any of the files in it; then I get the following output:

I also took the boot log using the TA read command suggested by you, it is attached.

Any suggestions on how to recover this?

Cheers,

R
[Sony Cross-Device General] tonsofquestions:
I'm sorry to break it to you, but there's not much you can do here - at least to my knowledge. Maybe if you had additional (private) Sony tools, but not with it in the current state.

I'm honestly surprised it boots into flashmode at all, but I'm pretty sure it's broken in some way that's irreparable.

The phone contains some info (particularly in the trim area) that's custom to the phone - device keys, etc. that would not work if you flash to another device. That's why you're not supposed to flash the TA partition from one phone to another to try and relock it or restore DRM keys - they won't work and will likely break the device - which is probably at least part of what happened to you here. :(

The "correct" way to do what you're trying to do is via the TWRP recovery backup/restore tools, which create a full disk image - but just of the appropriate partitions. It doesn't help you now, but perhaps for next time. On the plus side, at least you still have your old phone, even if the new one isn't usable?

As far as relocking the bootloader goes, it's not possible on the XZ1c, full stop.

Not in your current state, not on a freshly rooted device with the right backups, there's no command to do it, and no one's ever figured out how.

It's again theoretically possible that with the right Sony tools you could, but they're not available for public use.
[Sony Cross-Device General] tuha.juku:
It's really annoying to erase userdata...

Anyway, I closed the bootloader and used Xperia Companion to upgrade to A14. Then opened again and Magisk etc.

I'm just wondering if it will now be like that every time I want to flash new firmware?

Could it be a bug in device when (like I wrote) Newflasher is flashing previous firmwares (A13) correctly?

Same with linux and windows.

Yes, I can enter into recovery as well. No problem.

Sorry, stupid question: can Newflasher handle large files?

super_X-FLASH-ALL-25B1.sin is 4GB (part of XQ-DE54 Customized EU-UK 67.1.A.2.182 firmware).
[Sony Cross-Device General] munjeni:
Yes sure it handle large files! It handle lerge files in chunks, see source code for idea. newflasher working for years with large files with no problem at all.

Its no need, but sometimes is need for example when device no want to boot and clean install including userdata erase is need.

See post 4 about rollback protection for idea!
[Sony Cross-Device General] munjeni:
I newer ever see that somebody done this, OMG! Every Sony phone have unique heart called trim area partition, every device have that partition unique, you can NOT use it from another phone! So, if you do not have original trim area partition backup you can say good bye to your phone! If you have trim area backup than you are lucky one, convert your trim area backup to .ta file using trimarea tool from my github page, convert backup to .ta and simply flash .ta file using newlfasher. I see your log, you messed up whole trim area by trim are from another phone, and to be honest you are lucky one since you have flash mode working, realy lucky! The most common thing while messing up trim area is total brick! If you don't have original trim area backup the only way for you is new mainboard, don't waste your time if you don't have backup!

you have messed trim area and most inportant things like hwconfig, sim unit, sim signature unit... etc, thats all unique per device and you can do nothing without trim area backup. Option two is go to Sony center for repair.
[Sony Cross-Device General] flyingfishfinger:
Yeeaahh I definitely screwed that one up, ha. I do not have a working backup from this phone, it was "new" (used) and I was attempting to install the backup image from my current device. Guess I learned something - let's see what the Sony Repair will quote :) Thanks for confirming my suspicions at any rate!
[Sony Cross-Device General] lusterW:
Add some information about #2,544, I did not use the phone DE-72 after I bought it back and immediately flash version 67.1.A.2.182 to clear the user data, but it boot failed.
[Sony Cross-Device General] munjeni:
128 pages of informations! Read at least 2-3 pages in back to understand whats hoing on with recent devices, to be honest I have no idea whats going on!
[Sony Cross-Device General] mak6021:
Hello, how will you transfer ftf firmware for your flasher?
[Sony Cross-Device General] munjeni:
Extract it by 7z first than it will become .sin which you can flash by newflasher.
[Sony Cross-Device General] quanghuy290699:
I need help after flashing with newflasher v57, it hangs on the "sony" logo and keeps rebooting. After a few times it will say corrupt
[Sony Cross-Device General] munjeni:
I'm unsubscribed from here until something new sorry, ten pages and the same questions i realy not going to repet the same thing, simply read our thread at least the last 3 pages for idea.