Database Info

Can't use Flashtool.

Hello. I'm new at this great forum. Excuse my english, I'm from Spain. Several days trying to solve my problem, reading at google, forums, etc. This is the matter:
I bought recently an Xperia ray, bootloader blocked, updated to 4............62 Then, I realised that this firmware cannot be rooted. So I`ve downloaded previous firmwares, 042 and 058 and tried to flash via flashtool so as to revert my 062 firmware to those 042 or 058. but there is no way to flash. I start flashing with the phone switched off and ge this message:
05/009/2012 14:09:30 - INFO - <- This level is successfully initialized
05/009/2012 14:09:31 - INFO - Flashtool Version 0.6.6 built on 2012-01-08 19:34:23
05/009/2012 14:09:42 - INFO - Selected Xperia Ray (ST18i)_4.0.2.A.0.42_CE.ftf
05/009/2012 14:09:42 - INFO - Preparing files for flashing
05/009/2012 14:09:49 - INFO - Device disconnected
05/010/2012 14:10:18 - INFO - Please connect your device into flashmode.
05/011/2012 14:11:04 - INFO - Device connected with USB debugging off
05/011/2012 14:11:04 - INFO - For 2011 devices line, be sure you are not in MTP mode
However, I previously put USB debugging on, for sure.
Then, I tried conecting USB cable with the phone switched on, and get this message:
05/045/2012 13:45:03 - INFO - <- This level is successfully initialized
05/045/2012 13:45:03 - INFO - Flashtool Version 0.6.6 built on 2012-01-08 19:34:23
05/045/2012 13:45:11 - INFO - Device disconnected
05/045/2012 13:45:14 - INFO - Selected X10_V1_BLRelock.ftf
05/045/2012 13:45:14 - INFO - Preparing files for flashing
05/045/2012 13:45:14 - INFO - Please connect your device into flashmode.
05/046/2012 13:46:23 - INFO - Device connected with USB debugging on
05/046/2012 13:46:27 - INFO - Connected device : ST18
05/046/2012 13:46:27 - INFO - Installed version of busybox : N/A
05/046/2012 13:46:27 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
After that, no further actions, and no flash done. I dont know what else i can do. Help, please. I also tried using different usb ports, with no result.
Thanks in advance.

Problem solved.
Thanks.

dude i'm facing the same issue.. what did you do to resolve it????

katuss said:
dude i'm facing the same issue.. what did you do to resolve it????
Click to expand...
Click to collapse
well, you have to put your phone in download mode don't start flashing with phone off/on
look here on your phone should be the same procedure just search before to post

[SOLVED] (Urgent Help needed !!!) Xperia M2 shown as Z3

So as the title says, when i connect my M2 to my PC it's shown as Z3. I can't flash any M2 ftf via Flashtool.It always failed saying :
07/013/2015 17:13:00 - INFO - Start Flashing
07/013/2015 17:13:00 - INFO - Ending flash session
07/013/2015 17:13:00 - ERROR - Can't read a byte value
07/013/2015 17:13:00 - ERROR - Error flashing. Aborted
07/013/2015 17:13:00 - INFO - Device connected in flash mode
07/013/2015 17:13:01 - INFO - Device disconnected
I can flash only CM13 from a russian site like xda :/
Any help will be appreciated...
Thanks in advance :/
Edit : I found out that..when it's in recovery and i connect to PC it says Z3 but when i turn on the system and connect the phone to PC it says M2 or D2303.

If you had searched up a bit on Google, you'd have come up with this... Which clearly says that you need to clean everything up (the .flashTool folder), uninstall Flashtools and install it again. I always recommend using the 0.9.18.6 version to avoid compatibility issues with this device.

linuxct said:
If you had searched up a bit on Google, you'd have come up with this... Which clearly says that you need to clean everything up (the .flashTool folder), uninstall Flashtools and install it again. I always recommend using the 0.9.18.6 version to avoid compatibility issues with this device.
Click to expand...
Click to collapse
Actually i've searched before makin the thread. Done it few times...at the beginning it was not makin any difference.. but after that somehow it worked...anyway thanks :highfive:

Xperia L - problems entering flash mode

Hello,
I've flashed my Xperia L once or twice some time ago, now I just wanted to try out some of the new goodies, not just stay on the cursed 4.2.2. I have it all set up correctly software-wise, yet whenever I run Flashtool (version 9.19.8( and try to Volume-Down connect my phone, it get's problematic. Yeah, the phone does connect in flash mode, yet after a couple dozen seconds it simply disconnects as if I had manually unplugged it. Phone restarts and gets connected to PC the standard-way.
Now, is it that Flashtool automatically cuts off the connection after some time, or my cable or socket(s) are faulty? I thought it had something to do with having moved cable a tiny bit and connection being lost but now, I have tried again, ensuring no movement will be involved and it just disconnected again. I did also check all my laptop's USB ports, also bought a USB HUB and checked it. Did check two different cables, one for some Nokia, I think, no results.
Here's flashtool log.
Code:
18/043/2017 15:43:31 - INFO - Device connected in flash mode
18/044/2017 15:44:32 - INFO - Device disconnected
18/045/2017 15:45:22 - INFO - Device connected with USB debugging on
18/045/2017 15:45:22 - ERROR - root : this bundle is not valid
18/045/2017 15:45:23 - INFO - Connected device : Sony Xperia L
18/045/2017 15:45:23 - INFO - Installed version of busybox : BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
18/045/2017 15:45:23 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-g74b701b-00054-gde56c65-dirty / Build number : 15.3.A.1.17
18/045/2017 15:45:23 - INFO - Checking root access
18/046/2017 15:46:04 - INFO - Root Access Allowed
18/046/2017 15:46:04 - INFO - Stopping ric service
18/046/2017 15:46:20 - INFO - ric service stopped successfully
Any ideas?
Renagrds,
Greg

Gregoric said:
Hello,
I've flashed my Xperia L once or twice some time ago, now I just wanted to try out some of the new goodies, not just stay on the cursed 4.2.2. I have it all set up correctly software-wise, yet whenever I run Flashtool (version 9.19.8( and try to Volume-Down connect my phone, it get's problematic. Yeah, the phone does connect in flash mode, yet after a couple dozen seconds it simply disconnects as if I had manually unplugged it. Phone restarts and gets connected to PC the standard-way.
Now, is it that Flashtool automatically cuts off the connection after some time, or my cable or socket(s) are faulty? I thought it had something to do with having moved cable a tiny bit and connection being lost but now, I have tried again, ensuring no movement will be involved and it just disconnected again. I did also check all my laptop's USB ports, also bought a USB HUB and checked it. Did check two different cables, one for some Nokia, I think, no results.
Here's flashtool log.
Code:
18/043/2017 15:43:31 - INFO - Device connected in flash mode
18/044/2017 15:44:32 - INFO - Device disconnected
18/045/2017 15:45:22 - INFO - Device connected with USB debugging on
18/045/2017 15:45:22 - ERROR - root : this bundle is not valid
18/045/2017 15:45:23 - INFO - Connected device : Sony Xperia L
18/045/2017 15:45:23 - INFO - Installed version of busybox : BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
18/045/2017 15:45:23 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-g74b701b-00054-gde56c65-dirty / Build number : 15.3.A.1.17
18/045/2017 15:45:23 - INFO - Checking root access
18/046/2017 15:46:04 - INFO - Root Access Allowed
18/046/2017 15:46:04 - INFO - Stopping ric service
18/046/2017 15:46:20 - INFO - ric service stopped successfully
Any ideas?
Renagrds,
Greg
Click to expand...
Click to collapse
First of all, you should check this thread:
https://forum.xda-developers.com/showpost.php?p=70833785&postcount=304
There, I've said that you should just use older versions of flashtool for XL, like v0.9.18.4 !
If it doesn't solve your problem, then you should flash the ROM , right after you connect the phone to pc, as fast as you can!
And note that if it disconnects again, do nothing, just unplug the phone and wait untill the progress bar is completed and rom is prepared for flashing, then it again asks to connect the phone, and you connect it and wait untill it Finnishes
It happened for me too, and with this method, I've flashed the ROM successfully!

Soft Brick After Trying to Flash Latest Stock Nougat Firmware via Flashtool

Hello XDA, longtime reader, first time poster.
I tried flashing a custom ROM the other day, but something went wrong, and I now have a device that bootloops (unlocked screen, SONY logo, followed by a "the software update failed" message). I think the cause of all of this came from a few missing drivers that Flashtool/Windows 7 didn't install properly. I'm not sure if this matters, but this happened after trying to update to the latest stock nougat firmware (downloaded via Xperifirm) from a custom 6.0.1 ROM.
I went through as many solution threads as possible, but I'm still having trouble. The last thing I did just before this post was create an ftf via Flashtool, added "41.fsc" script when asked, prepared flash with full wipe/no exclusions, connected phone to USB via Flash Mode, selected F83XX when prompted for device, and this was the log I received...
29/021/2017 00:21:58 - INFO - Device connected in flash mode
29/021/2017 00:21:59 - INFO - Opening device for R/W
29/022/2017 00:22:00 - INFO - Reading device information
29/022/2017 00:22:00 - INFO - Phone ready for flashmode operations.
29/022/2017 00:22:00 - INFO - Opening TA partition 2
29/022/2017 00:22:00 - INFO - Start Flashing
29/022/2017 00:22:00 - INFO - No loader in the bundle. Searching for one
29/022/2017 00:22:44 - INFO - No matching loader found
29/022/2017 00:22:44 - WARN - No loader found or set manually. Skipping loader
29/022/2017 00:22:44 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_40 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_40 / Bootloader status : ROOTED
29/022/2017 00:22:44 - INFO - Max packet size set to 4M
29/022/2017 00:22:44 - INFO - USB buffer size set to 512K
29/022/2017 00:22:54 - INFO - Parsing boot delivery
29/022/2017 00:22:54 - INFO - Found a template session. Using it : C:\Users\[name]\.flashTool\firmwares\prepared\41.fsc
29/022/2017 00:22:54 - INFO - Set loader configuration : [00 01 00 00 00 0C]
29/022/2017 00:22:54 - INFO - Flashing finished.
29/022/2017 00:22:54 - INFO - Please unplug and start your phone
29/022/2017 00:22:54 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Extra information...
PC
- Windows 7 64-bit
- Flashtool 0.9.23.2 installed
- As far as I know, every driver I need has been downloaded and installed (Sony's website, Flashtool-drivers.exe)
(↑ "Sony sa0115 ADB Interface Driver" under Device Manager reads "This device cannot start. (Code 10)", if that makes any difference)
- Xperia Companion doesn't detect my phone, so I can't use their "software repair" option
Phone
- F8332
- Bootloader unlocked
- *Backup TA missing*
- Device rooted
- TWRP 3.1.1-0 installed
- Android 6.0.1 (firmware unknown)
Files
- Latest Nougat firmware (F8332_Customized FR_1305-9679_41.2.A.7.76_R1D) -- folder only (ftf can be created anytime, just need to know what to keep/exclude. I've been seeing different answers regarding when to add "41.fsc" to ftf (before/after flashing, or adding at all), and excluding .sin files before flashing, so if anyone has a definite answer to these, I'd really appreciate it.)
Otherwise, if none of that matters and the problem lies somewhere else, I'm all ears.
Thank you in advance.

@simpleflips
wow - your post should stand out as a prototype for HOW TO ASK FOR HELP!
I had the same problem recently when trying to flash my F8331 under Windows 10. Did not try Linux on the same machine since there are some issues with Mono here.
My drivers where not giving me any clues (PC-Manager, logging under Windows?).
So I dug out my spare laptop (Win 7 bitness?): installed the XZ-driver and it worked there after a full wipe in TWRP (I had encrypted the device and TWRP did not take the key properly).
You can try the drivers I link in my Guide.
Under both Windows installations I had no problems with adb and fastboot.
So I can only guess that my "solution" was the full wipe or some unkwon differences in driver magic between the notebooks used.

@DHGE
Apologies for the delay, thank you for the words and response. I should've noted that before my OP and bootloop, I tried to flash the custom Nougat ROM via TWRP, but got an error. (Zip file is corrupt! Error installing zip file '/sdcard1/[rom].zip') (Tested after transferring the file via AirDroid, don't remember if I even downloaded directly from my phone.) Now if I run a full wipe through TWRP and re-flash the original 6.0.1 ROM that's in my microSD, it *does* install, but bootloop still exists. I tried wiping/flashing the custom ROM via fastboot out of curiosity, and received the following:
wipe (entered bootloader mode from my Downloads folder, where the ROM is found)
C:\Users\[name]\Downloads>fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (status read failed (Too many open files in system))
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command failed (Invalid argument))
erasing 'userdata'...
FAILED (command write failed (No such device or address))
finished. total time: 0.020s
(Afterward, I get a message saying fastboot.exe has stopped working. Not on Minimal ADB, though.)
flash
C:\Users\[name]\Downloads>fastboot update [rom].zip
'archive does not contain 'android-info.txt' ,
error: update package '[rom].zip' has no android-info.txt
Do these errors relate with each other? Was my file just not downloaded properly?
Regarding the drivers, I downloaded the official Xperia XZ ADB interface driver (Sony sa0115) from SONY's website, and installed via Device Manager, but get the Code 10 Error mentioned in OP. According to some user posts, the solution was changing their phone's USB configuration to MIDI, afterward Windows would properly detect and install the Sony sa0115 driver. (I reckon that's not possible on a soft bricked device, is it...?) No devices are found after entering adb devices in command prompt, so I'm going to presume installing/flashing anything via ADB is out of the question. Right now, Device Manager shows 2 devices-- One of them being the actual XZ when connected in fastboot mode (labeled "Android Phone"), the other being the Sony sa0115 driver I downloaded/installed. The trick now is mounting the two together.
At this point, fastboot/TWRP seem to be the only way out of this. The custom ROM notes that no kernel flashing is necessary, but your guide includes a link to the AndroPlus kernels (for stock, and other roms, I take it). Unfortunately, until I figure out how to properly flash the firmware via Flashtool, AndroPlus will have to wait. (Unless there's a way to find out what firmware my phone is using right now.) The next option is to directly send the custom 7.1.1 ROM from my PC to the microSD card, but I can't find my SD card adapter right now, so I'll update later this week.

simpleflips said:
@DHGE
At this point, fastboot/TWRP seem to be the only way out of this
Click to expand...
Click to collapse
Unfortunately this is not a way out. And what you wrote above sounds rather weird for me...
The only way out is to flash a SONY ROM properly. THE tool for this is flashtool.
There are some mentions of SONY's recovery tool(s?) but last time I tried one I could not get it to work. Flashtool to my rescue.
Maybe you can take your phone to a qualified repair shop and they flash you a SONY ROM.

The bundle does not match the connected device

Hi,
I'm restore my last backup on twrp. Restore success but my phone enter loop on boot.
Than i want flash stock rom via xperifirm but i failed, error message; The bundle does not match the connected device
How can i fix this? || Current device : Unknown: Jul 24 2016/19:28:59 - BH90A7YR1L
14/004/2018 00:04:08 - INFO - Selected Bundle for Sony Xperia Z3(D6603). FW release : BH90A7YR1L. Customization : BH90A7YR1L
14/004/2018 00:04:08 - INFO - Preparing files for flashing
14/006/2018 00:06:10 - INFO - Please connect your device into flashmode.
14/006/2018 00:06:26 - INFO - Using Gordon gate drivers version 3.1.0.0
14/006/2018 00:06:26 - INFO - Opening device for R/W
14/006/2018 00:06:26 - INFO - Device ready for R/W.
14/006/2018 00:06:26 - INFO - Reading device information
14/006/2018 00:06:26 - INFO - Phone ready for flashmode operations.
14/006/2018 00:06:26 - INFO - Opening TA partition 2
14/006/2018 00:06:27 - INFO - Current device : Unknown: Jul 24 2016/19:28:59 - BH90A7YR1L - Unknown: Jul 24 2016/19:28:59 - 23.5.A.1.291_23.5.A.1.291 - GENERIC_23.5.A.1.291
14/006/2018 00:06:27 - INFO - Closing TA partition
14/006/2018 00:06:27 - ERROR - The bundle does not match the connected device
14/006/2018 00:06:27 - INFO - Ending flash session
14/006/2018 00:06:28 - INFO - Device disconnected
14/006/2018 00:06:32 - INFO - Device connected in flash mode
14/006/2018 00:06:39 - INFO - Device disconnected

Help

Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it click
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
At least this worked for me. If it doesn't work for you, you could try to use Sonys official developer Xperia Flashtool ("Emma"). This application saved me once or twice already from severe situations.
BUT WARNING: I'm not entirely sure anymore, but I think it erases your entire internal storage (incl. pictures, music, documents, some appdata, etc)
So if you can still get into TWRP, make a full backup of your personal data (with adb or simply drag'n'drop or whatever you like).
Usage is very simple and self-explanatory: Download -> install -> connect Phone -> install Firmware (downloads it automatically)
PS: I don't know why you're experiencing a bootloop and what ROM you're using, but this little idea came to my mind what you could try:
Wipe dalvik/cache and flash your boot.img again with fastboot
I used this little trick several times with success, but only with Custom ROMs (Ressurrection Remix, Lineage, Carbon). So I can't tell anything about Stock-ROMs.
I hope I could help you

castrum_doloris said:
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it click
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
At least this worked for me. If it doesn't work for you, you could try to use Sonys official developer Xperia Flashtool ("Emma"). This application saved me once or twice already from severe situations.
BUT WARNING: I'm not entirely sure anymore, but I think it erases your entire internal storage (incl. pictures, music, documents, some appdata, etc)
So if you can still get into TWRP, make a full backup of your personal data (with adb or simply drag'n'drop or whatever you like).
Usage is very simple and self-explanatory: Download -> install -> connect Phone -> install Firmware (downloads it automatically)
PS: I don't know why you're experiencing a bootloop and what ROM you're using, but this little idea came to my mind what you could try:
Wipe dalvik/cache and flash your boot.img again with fastboot
I used this little trick several times with success, but only with Custom ROMs (Ressurrection Remix, Lineage, Carbon). So I can't tell anything about Stock-ROMs.
I hope I could help you
Click to expand...
Click to collapse
Hi,
Emma works perfectly! Thank you

Yummy!
21/028/2018 21:28:17 - INFO - Reading device information
21/028/2018 21:28:17 - INFO - Phone ready for flashmode operations.
21/028/2018 21:28:17 - INFO - Opening TA partition 2
21/028/2018 21:28:17 - INFO - Current device : D6603 - BH90A7YR1L - 1288-5531_R9D - 1282-2729_23.5.A.0.575 - GLOBAL-LTE_23.5.A.0.575
21/028/2018 21:28:17 - INFO - Closing TA partition
21/028/2018 21:28:17 - INFO - Start Flashing
21/028/2018 21:28:17 - INFO - Processing loader.sin
21/028/2018 21:28:17 - INFO - Checking header
21/028/2018 21:28:17 - INFO - Flashing data
21/028/2018 21:28:18 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AC_LA3.0_M_2 / Bootloader status : ROOTED
21/028/2018 21:28:18 - INFO - Max packet size set to 512K
21/028/2018 21:28:18 - INFO - USB buffer size set to 512K
21/028/2018 21:28:19 - INFO - No flash script found. Using 0.9.18 flash engine
21/028/2018 21:28:19 - INFO - Opening TA partition 2

castrum_doloris said:
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
I hope I could help you
Click to expand...
Click to collapse
thank you
my phone z5p e6833
but my different rom install "xz2 thema rom", "xz3 thema rom" vb. different most rom install my phone device name e6883 change
flashtool-0.9.25.0-windows install and flashing E6833_32.4.A.1.54_1298-2968_R2E and error Bundle does not match device yor phone device e6883
uninstall flashtool-0.9.25.0-windows
install flashtool-0.9.23.1-windows
not redownload E6833_32.4.A.1.54_1298-2968_R2E old time download E6833_32.4.A.1.54_1298-2968_R2E
flashing ok
re thankyou

castrum_doloris said:
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it click
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
. . .
I hope I could help you
Click to expand...
Click to collapse
Thank you so much for that answer. I spent hours trying to find a solution, but using an older version of the software would never have occurred to me. Thank you so much for that answer. I spent hours trying to find a solution, but using an older version of the software would never have occurred to me.
Now my Z2 Tablet runs with Android 9; great:good::highfive:

emad
it work for me thanxs:good::good:

我的Z5P Dual E6883 閃光成 E6853之後無法復原 終於在0.9.18.6得到解決的方法 無法表達如此感謝

I can confirm that it works by using the older version of FlashTool, with an Xperia ZR :good: I also disabled the "verification" part as this posed some problems with reading from the device. I was able to install two different types of .ftf files (one at a time), and then reinstall recovery and LineageOS. My original problem was a bootloop, only showing the TWRP or Sony splash screen beforing screen going black again and rebooting.

castrum_doloris said:
Hello there
I had the same problem with my Xperia Z2, so I found your thread while searching for a solution. First "Bundle does not match device" and then "root: This bundle is not valid" .
I could just solve this (strange) issue, so here are some tips how I managed it:
I assume that you installed the newest version of flashtool (0.9.24.4)
- uninstall/remove flashtool (0.9.24.4)
- Download the previous release of flashtool (0.9.18.6) and install it click
- Install the drivers of your phone (directory of flashtool -> drivers)
- Launch flashtool -> Xperifirm -> Download the correct Firmware (again). Make sure that your home-directory of flashtool (default: C:\Users\xyz\.flashTool) is empty (at least no .ftf file may exist)
- Let flashtool create the .ftf File
- Flash the .ftf
At least this worked for me. If it doesn't work for you, you could try to use Sonys official developer Xperia Flashtool ("Emma"). This application saved me once or twice already from severe situations.
BUT WARNING: I'm not entirely sure anymore, but I think it erases your entire internal storage (incl. pictures, music, documents, some appdata, etc)
So if you can still get into TWRP, make a full backup of your personal data (with adb or simply drag'n'drop or whatever you like).
Usage is very simple and self-explanatory: Download -> install -> connect Phone -> install Firmware (downloads it automatically)
PS: I don't know why you're experiencing a bootloop and what ROM you're using, but this little idea came to my mind what you could try:
Wipe dalvik/cache and flash your boot.img again with fastboot
I used this little trick several times with success, but only with Custom ROMs (Ressurrection Remix, Lineage, Carbon). So I can't tell anything about Stock-ROMs.
I hope I could help you
Click to expand...
Click to collapse
Thank Youuu !!!! You made my day . I was stuck here for around an year . It never occurred to me to try an older release of flashtool. :good::good:

LOL! Newer is not always better haha. I just ran into this issue while trying to flash my Xperia Z2 back to stock. It was showing "Unknown" and complaining with "The bundle does not match the connected device" then refusing to flash. I thought it had to do with the LineageOS kernel it was running at the time, but no, flashing a stock-based kernel didn't fix that either.
Thanks for saving me from a headache!