yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] Andrew Lin:
Hi does anyone know where the optional step 2 dump trim area files are stored? What do they look like? I hard bricked my xperia 1 iii(phone vibrates once, green led flashes once without anything on the screen when trying to turn on, but doesn't turn on). I wanna backup those files I think I created last time I flashed the phone before trying to flash again to unbrick. Is this the right way to go to unbrick it?Any advice would be really appreciated. Thanks in advance!
[Sony Cross-Device General] NBinhouse:
I have a SO-04J,but I don't have the newest Japanese Rom. Once I flashed the G8141 Rom, it said Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms, Can I just force flash it?
[Sony Cross-Device General] gelomon:
Hello @munjeni, I have been using this flashtool for my xperia ace iii. From updating from A12 -> A13 and 3 more security updates. But this last security update, my ace iii is now bricked. I remember that I do the same thing as always, flash without data cleanup. Now it just shows up as QDUSB****. One thing I recall on the last output of the newflasher terminal is that somehow it switched to B? somewhat like that, I have searched the thread about like that and found out about the A/B partition. I have tried recompiling the source to match the PID/VID of the device and try the command to switch active from B to a but to no avail.

my device is bricked now, no lights, no vibrations, just QDUSB device when plugged in. Any suggestions is really appreciated. Thank you!
[Sony Cross-Device General] munjeni:
No! Those error mean that firmware is not compatible with your phone model!
[Sony Cross-Device General] munjeni:
Newflasher flashes bootdelivery to booth A and B slots, thats to prevent brick in case slot B is empty and somebody switch slot to B. In your case I realy have no idea what happened, do you have log from newflasher?
[Sony Cross-Device General] gelomon:
Where can I see the logs? I cannot find them on the firmware folder where I extract and run newflasher
[Sony Cross-Device General] munjeni:
Log of the newflasher is inside main window of the newflasher
[Sony Cross-Device General] gelomon:
Oh that one, I happen to close the window already, the only thing I remember is that the flashing was done successfully and the active was set to B at the end of the log, somehow like this below (I copied this on some other logs, but I am really sure that this is the exact end of logs too)

Set slot 'b' active.

Device is put now out of flash mode.
Sent command: Sync
Sent command: continue.

Done.
Closing device.
Press any key to continue . . .

after this, my phone was already detected as QUSB_*** and nothing I do make it blink led / vibrate or give me any response aside from that detection on windows.

What I have done is tried to recompile newflasher and force set the newly detected PID/VID for newflasher to look at but it wont set the active to 'a' partition. the result was connection timeout
[Sony Cross-Device General] munjeni:
If you flashed your phone recently bootdelivery is flashed to booth slot A+B, thats definitelly nothing in relation to newflasher if you had at the end of log all done. So even switching to slot B migh not cause hard brick since booth slots have their things already flashed. You probably faced an hw isue. Ok, switching slot to B with no reason might be in relation to isue with storage (hw isue) so it is very possible that bootloader switched to slot B because something is wrong with the storage. This case of yours is very rare, I don't remember anyone having such a thing recently! Even I'm prety surre you will not have a chance to unbrick it, it need special qcom bootloader which not exist for Sony as I know, the only option is oficial service or new mainboard as I done some times. Did you had any isue with phone recently? My xperia 10 had some touchscreen isues and some day in month-two died completely with no reason, I didn't get to replace the screen I ordered! : ) Simply bough used one with broken display and just replaced booth display and case, looks like new : )
[Sony Cross-Device General] gelomon:
Thanks for having time to explain, nope, no issues persists on the phone.

The only thing unusual I have is a 64gb memory card that has a linux system I use for my SBC, I temporarily stored it on the sdcard slot so I won't lose it.

That is the only thing I see might cause the issue.

Thanks again, Good thing I bought this device on sale ($80) brand new
[Sony Cross-Device General] kentottxxzz:
Any update to your phone? I have the same issue, and sane procedure also..
[Sony Cross-Device General] ayu_c:
After changing the CPU I can use 9008 EDL
[Sony Cross-Device General] ayu_c:
I have a dump of the device ufs
[Sony Cross-Device General] ryshd296:
v57

this error

No usb device with vid:0x0fce pid:0xb00b !

I would like to know the solution
[Sony Cross-Device General] wnijiko:
Just flashed Xperia 5 V (XQ-DE72) to TW fw successfully with Newflasher v57!

Everything works fine, maybe someone wants to know this.
[Sony Cross-Device General] Kai3004:
Hello brother

How to update oTA when flash china veréion to Sea firmwear ? vietnam sony group- They can fix but don't touch me about that :(
[Sony Cross-Device General] kentottxxzz:
Bro do you have firehose loader for 5iv?

Where did you get cpu?
[Sony Cross-Device General] kentottxxzz:
Can you please send pictures of test point?
[Sony Cross-Device General] ayu_c:
It is easy to buy CPU in China. The reason why I can use firehose is because I replaced the CPU with no fuse.
[Sony Cross-Device General] kentottxxzz:
where did you buy it? aliexpress?
[Sony Cross-Device General] Wasabi Ice Cream:
I'm still seeing this, even using my USB 2 ports...
[Sony Cross-Device General] munjeni:
Try another cable
[Sony Cross-Device General] dmilz:
Successfully flashed Xperia 5 S0-01M USING V57. Thank you
[Sony Cross-Device General] A1eksys:
How did you do that? What points in the program did you choose? My phone displays the image for an hour - Sony
[Sony Cross-Device General] wnijiko:
Just followed the instructions, no specific actions needed, make sure you are using the newest version and the right fw
[Sony Cross-Device General] bart388:
@munjeni Could you please add support for the Sony Xperia 5 III?

There is a LineageOS version for the Sony Xperia 5 III, and I would love to install it. But not without backing up my original. TA partition and DRM keys, and backing up the original Factory Recovery rom.

I've heard your tool can backup this before flashing the device. Is that correct? And there's also a restore I assume ☺️
[Sony Cross-Device General] munjeni:
It backup esential trim area unit but NOT ALL! Drm key and things is NOT backed up trought newflasher, simply not possible! Xperia 5 III is supported allready!
[Sony Cross-Device General] tomo100brt:
How to flash firmware and not to delete all data? Can we do that? I just want to update XPERIA 1 V not to reset and delete everything.
[Sony Cross-Device General] Haldi4803:
Somehow you can yes... but if you do it the wrong way you end up with a device stuck at Sony Boot Logo and end up having to use PC companion to reset your device.

Speaking from experience...
[Sony Cross-Device General] tomo100brt:
I know that, that is why I am asking for help how to do that and to not delete all data. Because last time i had to repair it with PC Companion.
[Sony Cross-Device General] NewTheLife:
Hi

Error flash XQ-DQ72 TW_67.1.A.2.112 version

--------------------------------------------------------

newflasher.exe v57 by Munjeni @ 2017/2023

--------------------------------------------------------

Device path: \\?\usb#vid_0fce&pid_b00b#8&384b90af&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}

Class Description: SOMC Flash Device

Device Instance Id: USB\VID_0FCE&PID_B00B\8&384B90AF&0&4

ERROR: Error CreateFile! failed with error code 5 as follows:

Access is denied.

Press any key to continue . . .
[Sony Cross-Device General] munjeni:
Right click -> run as administrator!
[Sony Cross-Device General] NewTheLife:
Thank for your help ;D

Why me phone not reboot ;( ? My phone sony xperia 1 v dq-qx72 tw (bootloader unlock)

:eek:😭

flash > off more reboot > 30 seconds reboot recovery
[Sony Cross-Device General] munjeni:
Try diferent firmware! Also erase userdata in case nothing helped. Also if even nothing helped try Sony PC Copmanion software,
[Sony Cross-Device General] pp03:
confirmed - android 14 on my unsupported xperia 10 V
[Sony Cross-Device General] munjeni:
Congrats, your post used the whole page : ) Consider using code tag next time please.

You no need fastboot at all for changing slot, you can do it using newflasher

newflasher set_active:a

newflasher set_active:b
[Sony Cross-Device General] King081:
Uhm upon checking factory Xperia 1v (BL has never been unlocked) TA dump it seems that Device Key no longer exists unless sony changed the offset
[Sony Cross-Device General] NewTheLife:
why flash b partition for me, not a ? b not reboot, a reboot ? Error system ?
[Sony Cross-Device General] munjeni:
Newflasher si not abble to dump whole trim area! The only non protected units is dumped! Sake authentification is need but nobody have sake auth key so forget it.
[Sony Cross-Device General] munjeni:
Sony design! For me only A is working on my xperia 10
[Sony Cross-Device General] munjeni:
Slot _a is unbootable, trying alternate slot

Err: line:1700 FindBootableSlot() status: Load Error

Err: line:1788 LoadImageAndAuth() status: Load Error

Just switch to slot A first than reflash your rom!, Or try slot B in case A is not work.

newflasher set_active:a

or

neflasher set_active:b
[Sony Cross-Device General] MD.SAFIN:
Please can you tell me how to unlock this so-03k phone bootloader? Without s1 unlock tool... it's very expensive to me ...

Unlock bootloader allowed: no
[Sony Cross-Device General] munjeni:
Bootloader unlock allowed = NO, I don't know! Newflasher can't do that.
[Sony Cross-Device General] munjeni:
Sorry I'm not in development for a long time! What I have faced similar is on my xperia 10 which I have bought used, it had user patern lock, I had hard time to figure out why I can't remove it, android was bootable but user patern lock still enabled and I had hard time to remove them trought some hacks I found on net trought html help pages I sucesfully opened some settings app inside phone to reset it, I forgot how I done that. Only know that it was realy hard time to remove lock. Even reflasing whole fw and wiping user data didn't removed user patern lock. On your phone, I realy have no idea whats going on! See this maybe it help https://xdaforums.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-84077083 . Its very possible what you say about FPS! Also very possible that you facing rollback protection but somehow its not shown inside boot log! Maybe sony updated their bootloader and rollback info is no more inside boot log, I realy have no idea. All the things in relation to the fact that our phones is not under our control anymore is a shame and disapointment in the same time! I still have old xperia 10, apsolutly have no plan to buy modern phone under not in my full control. I'm not in development for almost five years by that reason. Hope you figure out
[Sony Cross-Device General] zdob:
Even I can not use fastboot for reflash:

c:\Sony\sw\sin\UnSIN 1.13 (Win x64)>fastboot flash super super_pro-i.img
Sending sparse 'super' 1/6 (763169 KB) OKAY [ 17.142s]
Writing 'super' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed

c:\Sony\sw\sin\UnSIN 1.13 (Win x64)>fastboot -w
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
fastboot: error: Command failed
[Sony Cross-Device General] munjeni:
Thats interesting! Similar to this

: ) I don't have idea how that can be dealt off on sony phone probably not much diferent, but try consult google search, solution might exist! If you find a solution please tell us! If nothing help try find excatly the same fw as one which was sucesfully booting before you had bootlop in hope it boot again, I don't have free time right now for research even because don't have phone with simlar problem, my xperia 10 do not have rollback protection or something similar to what you have so I can't test anything... in worst case you will need to unlock bootloader.
[Sony Cross-Device General] zdob:
This won't work in my case. On that video issue was fixed by unlocking bootloader( first step is activate OEM unlock in dev menu) but I can not boot smartphone to go to the Dev menu for checking OEM unlock for the bootloader unlocking using fastboot. There is an option in FlashTool to erase userdata, apps during sw upgrade( it can be select without kernel update).

Is any possibility to erase userdata only using newflasher?
[Sony Cross-Device General] munjeni:
For bootloader unlocking you no need anything, just folow this https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader

To erase userdata just flash an fw and confirm in newflasher on prompt to erase userdata
[Sony Cross-Device General] zdob:
tricky thing. I can not unlock bootlooader until OEM UNLOCK menu is checked in Developer options menu of Android. To get this done i need to boot the device but it is in boot loop:

c:\Sony\sw\>fastboot oem unlock 0xCFF39E54C84615RD

FAILED (remote: 'Command not allowed')

fastboot: error: Command failed

Is any options to wipe CACHE and DATA using Newflasher, like on this video?
[Sony Cross-Device General] munjeni:
You need cche sin file and also userdata sin file, take a look into update.xml file which comming with wf! Files which contain tag <NOERASE> is files which you no want to flash while you need to keep userdata. So to erase userdata and all the things you need to flash those files. You can do it easy just with confirming in newflasher "keep userdata" with "n", newflasher will erase your userdata. I don't know if things is changed in new devices and that thing no more work while oem_unlock=no, you should try!

I didn't tried this https://github.com/munjeni/trimarea_tool/blob/master/trimarea_tool.c#L86 trim area contain those lock and probably if you can read those trim area unit 0x1046F you probably can also write to them. Don't write to trim area if you not know what you have doing, otherwise phone total dead is guaranted without a way for repair! Try this using newflasher:

newflasher.exe Read-TA:2:66671

it will be probably not allowed as those unit is close to drm key unit, probably you will get reply from bootloader like "not allowed! But you should try and let me know.

If nothing of this is work your option left is to flash excatly the same rom as one you have working, try many roms, hope one get boot! If not I am not able to help, go to Sony center and ask for unlock. What say sony pc companion software? Does it work?

Edit: hey I think its possible to unlock trought newflasher trught ta unit 0x8b2 ! You unlock code seems wrong!! CFF39E54C84615RD

, RD is not hexadecimal. If you give me the right unlock key I can create an .ta file for you for test if you want? Just give me the right unlock key

.ta file should be like this:

//uint8_t partition

//uint32_t trimarea_unit_num uint16_t sizeof(in hex representation! hex_codes) unt8_t hex_codes[16]

02

000008b2 0010 43 46 46 33 39 45 35 34 43 38 34 36 31 35 31 44

see picture you can create yourself just change 43 46 46 33 39 45 35 34 43 38 34 36 31 35 31 44 with your unlock key which you can type into the right part of the window inside "decoded text", you will get get 16 hex values fron the left, those left values you get you need to use and replace one I gaved as an example: 43 46 46 33 39 45 35 34 43 38 34 36 31 35 31 44 , when you type all right put your context I quoted above into an emty file caled unlock.ta and just flash with newflasher. If you don't know or you are not sure how to do this, give me your unlock code and I will create .ta file for you! Don't type something wrong, writing to trim area is dangerous for phone, one wrong and your phone is dead!

Relocking bootloader is this way (I didn't tried!!):

// [Relock bootloader, Blagus]
02

000008B2 0002 00 00
[Sony Cross-Device General] zdob:
results for command: newflasher.exe Read-TA:2:66671

c:\Sony\sw\ta read>newflasher Read-TA:2:66671
--------------------------------------------------------
newflasher v57 by Munjeni @ 2017/2023
--------------------------------------------------------

Determining available free space by GetDiskFreeSpaceEx:

Available space to caller = 69886 MB
Total space on current drive = 510975 MB
Free space on drive = 69886 MB
Device path: \\?\usb#vid_0fce&pid_b00b#5&4267132&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: SOMC Flash Device
Device Instance Id: USB\VID_0FCE&PID_B00B\5&4267132&0&1

Do you want to keep userdata? Type 'y' and press ENTER to confirm, or type 'n' to erase userdata.
n
Writing command: Read-TA:2:66671
got first reply[0x21]:

00000000 46 41 49 4C 46 41 49 4C 43 6F 6D 6D 61 6E 64 20 FAILFAILCommand
00000010 6E 6F 74 20 61 75 74 68 65 6E 74 69 63 61 74 65 not authenticate
00000020 64 d

got fail reply: FAILFAILCommand not authenticated
Closing device.

yes. right, correct unlock code for my IMEI is: CFF39E54C51AE27D

my unlock.ta:

02
000008b2 0010 43 46 46 33 39 45 35 34 43 35 31 41 45 32 37 44

result of flashing:

Processing unlock.ta
- Partition: 2
- Unit: 8B2 (2226)
- Unit size: 0x10
download:00000010
OKAY.
Write-TA:2:2226
OKAY.

c:\Sony\sw\fastboot getvar all
(bootloader) parallel-download-flash:no
(bootloader) hw-revision:20001
(bootloader) unlocked:no

Bootloader still is locked

PC Companion is flashing the phone using recovery menu without errors but phone is still not booting well.

It seems that issue is very similar to this one: https://xdaforums.com/t/xperia-1-bootloop.3959162/page-3
[Sony Cross-Device General] munjeni:
I expected thiat, those extra parts of the trim area reguire sake authentification but we don't have priv key for it so forget it. Please try again using unlock.ta and after that dump bootloader log it must say something about failed unlock operation

Also check if unit is writen by command:

newflasher.exe Read-TA:2:2226

Download the newer rom with highest sw number maybe you have facing rollback protection who know!
[Sony Cross-Device General] munjeni:
Must not reboot between commands or you did? I don't see anything in relation to writing to unit 0xb02 (or 2226). I forgot if log is imediatelly writen to the ta, maybe on next boot it become available, sorry I forgot how it work
[Sony Cross-Device General] NewTheLife:
How to Root Sony Xperia 1 V via Magisk Patched Init Boot

In this comprehensive guide, we will show you the steps to root your Sony Xperia 1 V via Magisk Patched Init_Boot.

droidwin.com

Warning: skip copying init_boot image avb footer (init_boot partition size: 8388608, init_boot image size: 100663296).

Sending 'init_boot' (98304 KB) OKAY [ 2.550s]

Writing 'init_boot' FAILED (remote: 'Flashing is not allowed for partition

')

fastboot: error: Command failed
[Sony Cross-Device General] munjeni:
@zdob are you sure your device is "bootloader unlock allow = YES" ? If it was NO while accesing *#*#7378423#*#* you can't unlock bootloader any way! In elation to boot loop I can see this line:

Load Image vendor_boot_a total time: 2 ms
Invalid boot image header
Invalid boot image header:No Media

Try this way: reboot to bootloader, switch to slot B and flash only vendor_boot sin file , than switch to slot A and reboot, If not booting switch to slot A and flash vendor_boot sin file. If nothing help try many diferent fw roms one of it must boot. See log of neflasher for idea about which rom was sucesfully boot, try flash excatly the same rom version. Make sure while booting android allow them to setup for at least 5 minutes, it can't boot imediately when you reflash whole rom! If you didn't allow them to setup fully by interupting setup time you might probably corupt it while it setting up! Anyway that was so strange that sony pc companion software is unable to fix your phone! I would go to their centre and tell him about problem with device as a the last thing if nothing help.
[Sony Cross-Device General] liangnan:
Processing dsp_X-FLASH-ALL-4BA8.sin

- Extracting from dsp_X-FLASH-ALL-4BA8.sin

- Extracting signature dsp.cms

- Uploading signature D:\BaiduNetdiskDownload\XQ-BC72_Customized HK_61.2.A.0.472A\flash_session\dsp.cms

download:0000088f

OKAY.

signature

OKAY.

- Extracting sparse chunk dsp.000

- Uploading sparse chunk D:\BaiduNetdiskDownload\XQ-BC72_Customized HK_61.2.A.0.472A\flash_session\dsp.000

download:04000000

ERROR: TIMEOUT: failed with error code 997 as follows:

重叠 I/O 操作在进行中。

- Error write! Need nBytes: 0x200000 but done: 0x0

nBytes[0x0]:

Error uploading chunk 4!

ERROR: TIMEOUT: failed with error code 997 as follows:

重叠 I/O 操作在进行中。

Error, null reply
[Sony Cross-Device General] munjeni:
See post 4
[Sony Cross-Device General] zdob:
Change slot A to B and vice versa didn't help and flashing vendor_boot sin file. I can not enter #*#7378423#*#* until it is booted well.
[Sony Cross-Device General] munjeni:
I have no idea, thats all I can help. Looks like that your phone don't have possibility for bootloader unlock, "unlock alloweed = NO". I should go to service and ask for bootloader unlock! You can do nothing until oficial service unlock bootloader unlock feature, simple go there and ask. Hope I helped
[Sony Cross-Device General] MD.SAFIN:
Can you please share this method?🙂 Device: Xperia xz2 SO-03k(NTT Docomo)(bootloader unlock allowed:no)
[Sony Cross-Device General] munjeni:
https://xdaforums.com/t/tool-newflasher-xperia-command-line-flasher.3619426/post-89201637
[Sony Cross-Device General] MD.SAFIN:
I don't understand those things.

.can you tell me what to do step by step?

And how do I backup TA partition?(everyone says it's important to backup it before unlocking bootloader) and lastly....will it work on docomo xz2 SO-03k? BL unlock allowed :no
[Sony Cross-Device General] munjeni:
Forum contain ton of posts in relation how to backup trim area and how that can be done, you need rooted phone in order to backup trim area fully, newlfasher can't dump it fully since trim area reading is protected by sake authentification so drm key and units higher than 10000 can't be read. You can't unlock bootloader any way since your bootloader unlocking is not allowed on your device, don't waste your time with it!
[Sony Cross-Device General] MD.SAFIN:
well...can I flash global rom on it at least 🙁?
[Sony Cross-Device General] munjeni:
I don't know, you can ask somebody with the same phone model, probably you can't because of two diferent models for example your is SO-03k and you will probably need fw for the same SO-03k( but you can try, in case you get "signature verification failed" that mean that you can't.
[Sony Cross-Device General] mrxnk:
Hi bros,

My phone is 1II Au SOG01.

Currently, my phone cannot detect the simcard due to re-flashing simlock.ta (I don't know why simlock.ta was re-flashed, but now it is locked, and when I try to read this area from phone's memory, it carries the default value).

If anyone, who is use the phone same mine, can read the simlock area in your phone and sent me?

The command:

newflasher.exe Read-TA:2:2010

and

newflasher.exe Read-TA:2:2011

Simlock.ta is located at the 0x7DA area (=2010),

Please help to read and send to me, just for reference with my case, hope that I can recuse my phone.
[Sony Cross-Device General] yf6:
Hi, I have been trying for more than 10 days to boot my Xperia1 III (XQ-BC72) with the exact same OEM lock and boot loop, and I've been using you as a reference, but looking at the newflasher log, I'm not sure it's the latest fw version you're writing about. I think XQ-BE72_Customized HK_61.2.F.0.256 and bootloader 1322-1669-X-BOOT-SM8350-LA2.0.1-T-207 is the latest version available for download on XperiFirm.