Simply try flash only userdata sin file for example, delete all the rest of files, so if it work the rest will work too. Do in mind flashing userdata will probably factory reset your device or delete all your personal files on that partition. Another problem would be roll back protection and you will not be abble to downgrade or install the same rom and you will get infinite boot loop! I will not repeat rollback story, simple read what cause roolback protection and how to deal them! Unlock bootloader will probably be needed in that case! In short, before you decide to try anything read twice xda posts!
Managed to reflash it successfully using a shorter high speed external SSD cable. I have tried the original USB c to c cables and many other cables which turned out failure. Thank you so much for letting me know it's the cable issue.
I don't know, you should ask in xz3 forum
Unlocked bootloader? If not unlocked and you attempt to unlock bootloader factory reset will be performed and you will lose your userdata! In case bootloader is unlocked allready, simple temporary boot an twrp recovery and dump all your data!Hello there! I have a XA2 Ultra that out-of-the-blue got stuck in the infamous bootloop (reboots after Xperia logo), and desperately need to recover files from internal memory.
I dl'd with XperiFirm EXACTLY the same FW it has now (variant, region etc). Newflasher flashed the phone correctly and I chose to keep userdata, believing it would boot a-fresh. But it's still stuck in the same bootloop seems the problem is in the user partition itself?
I know the thread is NOT for this, but still... Anyone know how to "extract" the userdata partition from a bootloop-stuck Xperia phone? Doesn't matter if it's corrupt, that I could deal with later... I'm now positive that doing a full flash w/Newflasher will recover my phone, but I need to take out my files first
Tried only userdata.sin at first and it works. Later managed to flash the whole FW (except deleting .ta and persist.sin) which works successfully too.Simply try flash only userdata sin file for example, delete all the rest of files, so if it work the rest will work too. Do in mind flashing userdata will probably factory reset your device or delete all your personal files on that partition. Another problem would be roll back protection and you will not be abble to downgrade or install the same rom and you will get infinite boot loop! I will not repeat rollback story, simple read what cause roolback protection and how to deal them! Unlock bootloader will probably be needed in that case! In short, before you decide to try anything read twice xda posts!
How do you think someone can help you when there is no newflasher log? If it is at the end after "sync" ignore it since its allready known problem on some devices
No usb device with vid:0x0fce pid:0xb00b !
Product ID: 0x0dde Vendor ID: 0x0fce (Sony Ericsson Mobile Communications AB) Version: 1.00 Speed: Up to 480 Mb/sec Manufacturer: Google Location ID: 0xfa120000 / 3
Flash the correct fw and no not needed to unlock the bootloader so far i know.Thanks for this wonderful tool! Now I'm suffering flashing my 1 IV. It's firmware is CN (which version is higher) and I want to flash it the Hongkong (which version is lower) one. After I flash my phone bricks. v52 flasher, XperiFirm's firmware, I have no idea about the failure. Do I need to unlock the bootloader?
Just put your phone in "green" and double click newflasher.exe, than folow on screen messages & prompts carefully and you are done. If you need usb driver put newflasher in an empty folder, double click them and folow on screen driver extraction prompt, newflasher will extract driver which you need to install, install them. Than go back to "green" and install rom you needHi, I recently bought an xa2 (h4113) dual and somehow bricked it (old fastboot version initially?). Meaning, the device reboots 5 times and then show the meessage "[..] corrupt [..] not boot [..]". I can get a connection in emma, can activate green (recovery?) and blue (fastboot?) modes, but i do not know how to proceed. Actually I'm a little bit scared to completely brick it.
I have newflasher and a directory H4113_Customized DACHBLX_50.2.A.3.77-R5B retrieved by XperiFirm.
I am used to classic moto phones and I am somehow lost with all this new (to me) a/b stuff, no visual stock recovery and so on. Any help very much appreciated.
03.07.2022 21:51 <DIR> .
03.07.2022 21:51 <DIR> ..
11.08.2020 08:22 2.363 appslog_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 appslog_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 354 auto-boot.ta
11.08.2020 08:22 289.620 bluetooth_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 bluetooth_X-FLASH-ALL-18AE_0x00.ha
03.07.2022 21:51 <DIR> boot
11.08.2020 08:23 22.822.938 boot_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 boot_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 243 cust-reset.ta
11.08.2020 08:22 2.935 diag_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 diag_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:22 3.727.124 dsp_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 dsp_X-FLASH-ALL-18AE_0x00.hash
10.09.2018 06:36 1.374.038 elabel-H4113-row-row_2018091006121
11.08.2020 08:28 36.147 fsconfig.xml
11.08.2020 08:23 49.833 fsg_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 fsg_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.369 fsmetadata_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 fsmetadata_X-FLASH-ALL-18AE_0x00.h
03.07.2022 21:51 311 fwinfo.xml
11.08.2020 08:22 1.386 misc_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 misc_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.361 modemst1_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modemst1_X-FLASH-ALL-18AE_0x00.has
11.08.2020 08:23 1.363 modemst2_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modemst2_X-FLASH-ALL-18AE_0x00.has
11.08.2020 08:22 51.886.575 modem_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 modem_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 4.611 oem_other_X-FLASH-CUST-18AE.sin
21.08.2020 09:36 17.002.050 oem_X-FLASH-CUST-18AE.sin
21.08.2020 09:36 278 osv-restriction.ta
11.08.2020 08:22 4.935 partition-image_X-FLASH-ALL-18AE.s
11.08.2020 08:23 148.557 persist_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 persist_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 2.375 Qnovo_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 Qnovo_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 1.363 rdimage_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 rdimage_X-FLASH-ALL-18AE_0x00.hash
21.08.2020 09:36 286 reset-wipe-reason.ta
21.08.2020 09:36 1.313 simlock.ta
11.08.2020 08:22 1.351 ssd_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 ssd_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:23 76.405.066 system_other_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 system_other_X-FLASH-ALL-18AE_0x00
11.08.2020 08:28 32 system_other_X-FLASH-ALL-9B8D_0x00
11.08.2020 08:23 1.541.089.157 system_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 system_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:28 32 system_X-FLASH-ALL-9B8D_0x00.hash
03.07.2022 21:51 593 update.xml
21.08.2020 09:36 61.590 userdata_X-FLASH-CUST-18AE.sin
11.08.2020 08:23 220.532.627 vendor_X-FLASH-ALL-18AE.sin
11.08.2020 08:28 32 vendor_X-FLASH-ALL-18AE_0x00.hash
11.08.2020 08:28 32 vendor_X-FLASH-ALL-9B8D_0x00.hash
supposedly the motherboard was completely dead as the Sony Service Center states that it was completely swapped for a new one
It heave another meaning too, for example it might be power supply problem on your PC for example it didn't deliver max 5.2V over usb instead maybe a bit more e.g. 5.4V , check that first before you kill your next phone!