Flashtool "Processing of partition-image.sin finished with errors" - Xperia Z3v General

I tried updating my Sony Xperia Z3v with Flashtool
Flashtool 9.19.10 is installed. Download firmware 23.0.A.2.93 and 23.4.A.1.264 (tried both)
I get the error "Processing of partition-image.sin finished with errors" and, of course, my phone can't boot anymore.
Code:
18/058/2016 17:58:07 - INFO - Please connect your device into flashmode.
18/058/2016 17:58:30 - INFO - Device connected in flash mode
18/058/2016 17:58:30 - INFO - Opening device for R/W
18/058/2016 17:58:30 - INFO - Reading device information
18/058/2016 17:58:30 - INFO - Phone ready for flashmode operations.
18/058/2016 17:58:30 - INFO - Opening TA partition 2
18/058/2016 17:58:30 - INFO - Current device : D6708 - BH9011T61N - 1288-1477_R19B - 1278-4381_23.0.E.1.44 - VERIZON-LTE_23.0.E.1.44
18/058/2016 17:58:30 - INFO - Closing TA partition
18/058/2016 17:58:30 - INFO - Start Flashing
18/058/2016 17:58:30 - INFO - Processing loader.sin
18/058/2016 17:58:30 - INFO - Checking header
18/058/2016 17:58:30 - INFO - Flashing data
18/058/2016 17:58:31 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_22 / Boot version : S1_Boot_MSM8974AC_LA3.0_59_VZW / Bootloader status : NOT_ROOTABLE
18/058/2016 17:58:31 - INFO - Max packet size set to 512K
18/058/2016 17:58:31 - INFO - Making a TA backup
18/058/2016 17:58:31 - INFO - Opening TA partition 1
18/058/2016 17:58:31 - INFO - Start Dumping TA partition 1
18/058/2016 17:58:32 - INFO - Finished Dumping TA partition 1
18/058/2016 17:58:32 - INFO - TA partition 1 saved to C:\Flashtool\registeredDevices\BH9011T61N\s1ta\2016-03-18_05-58-31\1.ta
18/058/2016 17:58:32 - INFO - Closing TA partition
18/058/2016 17:58:32 - INFO - Opening TA partition 2
18/058/2016 17:58:32 - INFO - Start Dumping TA partition 2
18/058/2016 17:58:32 - INFO - Finished Dumping TA partition 2
18/058/2016 17:58:32 - INFO - TA partition 2 saved to C:\Flashtool\registeredDevices\BH9011T61N\s1ta\2016-03-18_05-58-31\2.ta
18/058/2016 17:58:32 - INFO - Closing TA partition
18/058/2016 17:58:32 - INFO - Parsing boot delivery
18/058/2016 17:58:32 - INFO - No flash script found. Using 0.9.18 flash engine
18/058/2016 17:58:32 - INFO - Opening TA partition 2
18/058/2016 17:58:33 - INFO - Writing TA unit 00002774. Value : [01]
18/058/2016 17:58:33 - INFO - Closing TA partition
18/058/2016 17:58:33 - INFO - Processing partition-image.sin
18/058/2016 17:58:33 - INFO - Checking header
18/058/2016 17:58:33 - ERROR - Processing of partition-image.sin finished with errors.
18/058/2016 17:58:33 - INFO - Ending flash session
18/058/2016 17:58:33 - ERROR -
18/058/2016 17:58:33 - ERROR - Error flashing. Aborted
18/058/2016 17:58:33 - INFO - Flashing finished.
18/058/2016 17:58:33 - INFO - Please unplug and start your phone
18/058/2016 17:58:33 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
18/058/2016 17:58:33 - INFO - Device connected in flash mode
18/058/2016 17:58:33 - INFO - Device disconnected
How can I get my phone to work again? And ideally updated to the latest version. Thanks!
I'm using Windows 10 and since I use it outside of USA and don't have Verizon, automatic update doesn't work so I believe flashing is the only way to get an update. It is a stock Z3v phone with all the Verizon crap.
Edit:
Here's the error part of the log with Debug output, in case it can give something useful
Code:
18/026/2016 19:26:14 - INFO - Processing partition.sin
18/026/2016 19:26:14 - INFO - Checking header
18/026/2016 19:26:14 - DEBUG - Writing packet to phone
18/026/2016 19:26:14 - DEBUG - OUT : CommandID : 5 / Flags : false,true,false / Data length : 1032 / Data CRC32 : [AC, 28, 7A, AB]
18/026/2016 19:26:14 - DEBUG - Reading packet from phone
18/026/2016 19:26:14 - DEBUG - IN : CommandID : 5 / Flags : true,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
18/026/2016 19:26:14 - DEBUG - Writing packet to phone
18/026/2016 19:26:14 - DEBUG - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
18/026/2016 19:26:14 - DEBUG - Reading packet from phone
18/026/2016 19:26:14 - DEBUG - IN : CommandID : 7 / Flags : false,false,false / Data length : 61 / Data CRC32 : [BC, 39, C4, 26]
18/026/2016 19:26:14 - ERROR - Processing of partition.sin finished with errors.

---

You can follow my guide for a much simpler way to upgrade to the latest and get root. Doesn't require flashtool or anything.

---

I could have before I started, but not anymore.
Now I tried flashing while unchecking "partition.sin" to see what happens. Now the phone can't turn on at all... dead. What can be done? Perhaps a hardware flash by a very competent technician with the right equipment is the only option at this point?

---

MysteryXx said:
I could have before I started, but not anymore.
Now I tried flashing while unchecking "partition.sin" to see what happens. Now the phone can't turn on at all... dead. What can be done? Perhaps a hardware flash by a very competent technician with the right equipment is the only option at this point?
Click to expand...
Click to collapse
Flashtool 9.19.10 is installed. Download firmware 23.0.A.2.93 and 23.4.A.1.264 (tried both)
Click to expand...
Click to collapse
There's your obvious problem. You used firmwares that weren't designed for the Z3v. Therefore it's time to get another Z3v.

---

GigaSPX said:
There's your obvious problem. You used firmwares that weren't designed for the Z3v. Therefore it's time to get another Z3v.
Click to expand...
Click to collapse
I followed instructions that were specifically for the Z3v...
Can it be fixed through flashing the hardware chip directly? I guess I'll see tomorrow.

---

MysteryXx said:
I followed instructions that were specifically for the Z3v...
Can it be fixed through flashing the hardware chip directly? I guess I'll see tomorrow.
Click to expand...
Click to collapse
Instructions from where? You downloaded firmwares made for other Xperia devices, which are entirely different from the Verizon Variant. And I understand you wanted to have it debloated from the Verizon crapware, but that's part of the system you can easily use root to freeze them. No technician can fix this unless you really can try to flash the firmware that are specifically branded for the Z3v.

---

If a technician is equipped to flash the hardware, where can I download the specific firmware that needs to be written on it? Having the equipment is one thing; but he might not know what to put on it to make it work.

---

OK found a Thai guy in Panthip Plaza who has the equipment to flash the chip and who can repair for $20. He hasn't succeeded after 4 hours but he told me to give him 3 more days; he just needs more time. These Thai people can repair anything. You just need to find the right guys and give them enough time.

---

Please Use Flashtool 0.9.18.6 , Flash firmware 23.4.B.0.319. OK

---

MysteryXx said:
OK found a Thai guy in Panthip Plaza who has the equipment to flash the chip and who can repair for $20. He hasn't succeeded after 4 hours but he told me to give him 3 more days; he just needs more time. These Thai people can repair anything. You just need to find the right guys and give them enough time.
Click to expand...
Click to collapse
http://forum.xda-developers.com/z3/xperia-z3v-general/stop-flash-roms-z3-section-t3252918
Just leaving this here to get some common sense grounds established. While it's great to know you're in BKK, not everyone is going to be hands on in knowing much about the Z3v since it's a US based phone, not structurally the same as the international Xperia variants. Good luck.

---

Haiboy said:
Please Use Flashtool 0.9.18.6 , Flash firmware 23.4.B.0.319. OK
Click to expand...
Click to collapse
Thanks I'll tell him to try that firmware!
GigaSPX said:
http://forum.xda-developers.com/z3/xperia-z3v-general/stop-flash-roms-z3-section-t3252918
Just leaving this here to get some common sense grounds established. While it's great to know you're in BKK, not everyone is going to be hands on in knowing much about the Z3v since it's a US based phone, not structurally the same as the international Xperia variants. Good luck.
Click to expand...
Click to collapse
Even him thought that Z3 and Z3v would be the same; so not surprised he failed on the first day.

---

Haiboy said:
Please Use Flashtool 0.9.18.6 , Flash firmware 23.4.B.0.319. OK
Click to expand...
Click to collapse
He tried that firmware and many other things and hasn't succeeded yet. He'll keep trying.
Any other ideas that could help him?

---

MysteryXx said:
He tried that firmware and many other things and hasn't succeeded yet. He'll keep trying.
Any other ideas that could help him?
Click to expand...
Click to collapse
There is nothing you can do. Your phone is done for, it's bricked. As I've said this earlier, whatever guide you followed outside of the Z3v forum, you were already heading towards a path to ruining your phone.
You're in BKK, there are plenty of Sony devices available. Just go buy yourself of Z5/Z5 Premium or at least a Z3.

---

In the computer world where I come from, you can't break the hardware with software. If the software is broken beyond repair, you re-install fresh and you're good to go.
How can you explain that the same wouldn't apply to cellphones?
If no such "fresh install" exists, can't you take the content of a chip of the same model and clone it? It's just data as far as I know.

---

MysteryXx said:
In the computer world where I come from, you can't break the hardware with software. If the software is broken beyond repair, you re-install fresh and you're good to go.
How can you explain that the same wouldn't apply to cellphones?
If no such "fresh install" exists, can't you take the content of a chip of the same model and clone it? It's just data as far as I know.
Click to expand...
Click to collapse
Try taking a computer from 1995 and install Windows 10 on it. Or take any Windows computer and install Mac OS X on it. Even take any Android phone, and try installing a ROM that's specifically made for a certain phone (Samsung Galaxy Phone with an LG ROM).
You should get my point, it's the compatibility issues. I've already explained several times, and you may as well ask for a second and third opinion, it's all the same. You're taking something and forcing it into a host that's incompatible. It's much like anatomy, transplanting an incompatible organ from one donor into the person who needs it will be all for naught because the white blood cells will attack thinking it's a threat.
Basing on what you've said so far, why can't you do it? You're spending time and money on a dead phone. It's a waste.

---

He hasn't succeeded; said maybe going to Sony Center, but might require changing the motherboard.
Installing MacOS on a PC won't start the install at all, but once my cousin accidentally installed Linux on a computer, flushed the partitions with all the important data and created new types of partitions. I was able to re-install Windows and recover most of the data (with undelete programs) without problem.

---

MysteryXx said:
He hasn't succeeded; said maybe going to Sony Center, but might require changing the motherboard.
Installing MacOS on a PC won't start the install at all, but once my cousin accidentally installed Linux on a computer, flushed the partitions with all the important data and created new types of partitions. I was able to re-install Windows and recover most of the data (with undelete programs) without problem.
Click to expand...
Click to collapse
Sony Center isn't going to help with consumer negligence and using tools outside of Sony's official programs, you also void warranty and support.
I never stated Linux since I knew very well that PCs can do Linux. And
Installing MacOS on a PC won't start the install at all...
Click to expand...
Click to collapse
There you go, you could never get the install process to fully go through, and therefore messed up your phone. Done deal.

---

MysteryXx said:
In the computer world where I come from, you can't break the hardware with software. If the software is broken beyond repair, you re-install fresh and you're good to go.
How can you explain that the same wouldn't apply to cellphones?
If no such "fresh install" exists, can't you take the content of a chip of the same model and clone it? It's just data as far as I know.
Click to expand...
Click to collapse
It is true, if you can get the EEPROM to a clean flashable state you can reflash an OS on it, getting it to that clean flashable state is another thing. People put Ubuntu Linux on phones, even Windows 98, heck one guy put Android on an iPhone. You are correct in that software doesn't always hurt the hardware.
I do a lot of work in Automotive computers, ECU, PCM, TCM, use to you had the take the EEPROM out of the com to flash, now we can flash through the OBD port, if a flash goes bad during the erase phase the EEPROM is toast, but if anything happens after that it is recoverable, only question is at what phase of the flash process did the fault happen here.
Use to you could flash BIOS on coms (probably still can), PROMs on CD/DVD drives, graphic cards all had a flashable PROM, haven't built a com in years but during the overclocking water cooling CPU gaming com days it wasn't unusual to flash new things and reload the OS cause you overclocked the CPU, Memory, or GPU too far and corrupted Winders (I dual booted and Linux would boot when Winders wouldn't).
So have flashed a few EEPROMs before.

---

GigaSPX said:
There you go, you could never get the install process to fully go through, and therefore messed up your phone. Done deal.
Click to expand...
Click to collapse
With a PC, you could make a scratch on the hard drive, fix the bad sectors (if the rest of the hard drive is still OK), recreate the partitions and re-install from scratch and you're good to go.

---

1linuxfreak said:
I do a lot of work in Automotive computers, ECU, PCM, TCM, use to you had the take the EEPROM out of the com to flash, now we can flash through the OBD port, if a flash goes bad during the erase phase the EEPROM is toast, but if anything happens after that it is recoverable, only question is at what phase of the flash process did the fault happen here.
Click to expand...
Click to collapse
You mean that you can toast the chip if something goes wrong?
At first it was giving error on "partition-image.sin" and was then rebooting on loop. Then I did the mistake of disabling partition from the flash process to see what happens... thinking that the software can never break the hardware. After that, it wasn't booting at all. And it appears that from his tests with flashing the chip directly, he wasn't able to get it to turn back on either even to that reboot loop.