[Q] xperia z bricked

brianmullen8

Member
Oct 21, 2010
8
1
0
Hi, I flashed my phone with beanstalk 4.4 all looked ok but it lost imei and serial number.

I then did a restore to official 4.3 but it didn't restore the imei or serial.

I backed up the TA partition (i know it's too late now) I found where the serial number was located in a hex editor I changed only one of the digits to see if it changed on the phone, I sent the TA.img back to the phone and restarted.

Now it won't turn on. I loaded up flash tools and connected the phone, it goes into flashmode but drops back out after about 2 mins. It gets to the point where it tries to read the phone info but always stops with a header error.

Is there any way to flash the TA.img using flash tools or force flash the phone.

I have tried all combination of buttons to try get flashboot but nothing.

Thanks
 

kingvortex

Senior Member
Mar 25, 2010
5,042
3,967
0
If you pushed an edited TA image to your phone, then you have almost certainly hard bricked it.
The bootloader checks the signature of the TA and refuses to boot/enter flashmode or fastboot if it has been tampered with.
If this is what has happened, then there is no way to repair it.

Sent from my C6603 using Tapatalk
 

shabbypenguin

Inactive Recognized Developer
May 30, 2010
4,896
5,362
263
33
dont suppose you have a microsd card 16gb around do ya? seems like youd be a good candidate to test sdcard booting on this device :)
 

shabbypenguin

Inactive Recognized Developer
May 30, 2010
4,896
5,362
263
33
im new to sony and gsm devices, is TA where your imei or personal info for your device is secured? if so then this isnt gunna work out well since if anyone dumps the bootloader files from mmcblk0 for you it would include their TA.img.
 

kingvortex

Senior Member
Mar 25, 2010
5,042
3,967
0
im new to sony and gsm devices, is TA where your imei or personal info for your device is secured? if so then this isnt gunna work out well since if anyone dumps the bootloader files from mmcblk0 for you it would include their TA.img.
Yes, the DRM keys for the device, the IMEI and other device specific items are stored in the TA partition.
There's some discussion in the development section on it. I'll see if I can find it for you.

Sent from my Hudl HT7S3 using Tapatalk 4
 

shabbypenguin

Inactive Recognized Developer
May 30, 2010
4,896
5,362
263
33
Yes, the DRM keys for the device, the IMEI and other device specific items are stored in the TA partition.
There's some discussion in the development section on it. I'll see if I can find it for you.

Sent from my Hudl HT7S3 using Tapatalk 4
ah ok, well then that severely limits sdcard booting on this device. basically everyone would need to dump their own "backup" image in case crap goes wrong then :/. with samsung and lg they put the efs and other personal partitions further down so the first 150 or so MB's are just pure bootloaders.
 

shabbypenguin

Inactive Recognized Developer
May 30, 2010
4,896
5,362
263
33
I'm only an interested amateur, so a lot of the discussion goes over my head, but there's a lot of information that you may find useful/interesting in this thread from around page 21 onwards - http://forum.xda-developers.com/showthread.php?t=2234627

Sent from my Hudl HT7S3 using Tapatalk 4
thanks for teh link, it rearrims what I feared. so long as everyone dumps their own sdcard backup then they should be fine, but it makes using a universal one like samsung/lg impossible :/
 

brianmullen8

Member
Oct 21, 2010
8
1
0
I do have a working ta.img if it's any good, I have no idea how to flash it back on the phone. The phone does go into flashmode but gets an error. I will get a log from flastool and post it here.

Thanks

thanks for teh link, it rearrims what I feared. so long as everyone dumps their own sdcard backup then they should be fine, but it makes using a universal one like samsung/lg impossible :/
 

TraxXrAt

Member
May 15, 2013
36
4
0
I do have a working ta.img if it's any good, I have no idea how to flash it back on the phone. The phone does go into flashmode but gets an error. I will get a log from flastool and post it here.

Thanks
You can get it back with SAmanager or with the soft given by an XDA member but I don't remember who, I can upload it if you want
 

kingvortex

Senior Member
Mar 25, 2010
5,042
3,967
0
You can get it back with SAmanager or with the soft given by an XDA member but I don't remember who, I can upload it if you want
I just had a quick look at SA Manager. Unless I'm mistaken, it runs on the phone itself, therefore it won't help if the phone will not boot.

Sent from my C6603 using Tapatalk
 

TraxXrAt

Member
May 15, 2013
36
4
0
I just had a quick look at SA Manager. Unless I'm mistaken, it runs on the phone itself, therefore it won't help if the phone will not boot.

Sent from my C6603 using Tapatalk
Oh yeah you're right, I forgot he cannot boot anymore. There should be a solution, I'll try to find out and come later
 

kingvortex

Senior Member
Mar 25, 2010
5,042
3,967
0
There is definitely nothing that can be done if the TA has been tampered with.
It was apparently possible to unbrick some older Sony devices, but the methods used do not work on our device.

Sent from my C6603 using Tapatalk
 

kingvortex

Senior Member
Mar 25, 2010
5,042
3,967
0
Hard brick means hard brick.
The TA is part of the chain of trust. The first thing that happens when powering on the device in any mode is the bootloader checks signatures and stops boot if anything has been tampered with. The only way to fix this would be to push the correct TA image to the phone, but it's not possible to get the phone into a state where it's possible to do this.
I haven't been in this situation, but I will be very very surprised if SUS is able to repair his phone.

Sent from my C6603 using Tapatalk
 

TraxXrAt

Member
May 15, 2013
36
4
0
There is definitely nothing that can be done if the TA has been tampered with.
It was apparently possible to unbrick some older Sony devices, but the methods used do not work on our device.

Sent from my C6603 using Tapatalk
Yes, may be in the future someone will find a way to restore it, it would be nice, I hope so.
 

shabbypenguin

Inactive Recognized Developer
May 30, 2010
4,896
5,362
263
33
it may be possible, youd have to run some VERY specific commands. youd basically be writing the ta.img to the sdcard then skipping the amount of blocks the ta.img is and going from there for the rest of it. if that were to work and it would sdcard boot then it would boot the older ta.img you backed up and may boot long enough to get to flash mode then so you could then flash a full tft and be back to booting, or even just dd ta.img back on and restore the backup you do have.
 

brianmullen8

Member
Oct 21, 2010
8
1
0
Thanks for all your input guys

Here's the log from flashtool

Code:
02/057/2014 15:57:43 - DEBUG - (MyLogger.java:100) - <- This level is successfully initialized
02/057/2014 15:57:43 - INFO  - (MainSWT.java:829) - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
02/057/2014 15:57:48 - INFO  - (MainSWT.java:125) - Device disconnected
02/057/2014 15:57:52 - DEBUG - (Bundle.java:75) - Creating bundle from ftf file : C:\Flashtool\firmwares\C6603_10.4.B.0.569_Commercial_And_Journalists.ftf
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : loader.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : kernel.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : system.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : fotakernel.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : amss_fs_3.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : boot_delivery.xml
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : amss_fs_2.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : elabel-c6603-prototype_201305081233_10.4.B.0.569.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : amss_fs_1.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : rpm.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : partition-image.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : apps_log.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : userdata.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : cache.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:75) - Creating bundle from ftf file : C:\Flashtool\firmwares\X10_V1_BLRelock.ftf
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : kernel.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : loader.sin
02/057/2014 15:57:52 - DEBUG - (Bundle.java:91) - Added this entry to the bundle list : s1boot.sin
02/057/2014 15:57:57 - INFO  - (MainSWT.java:1061) - Selected C6603 / 10.4.B.0.569 / Commercial_And_Journalists
02/057/2014 15:57:58 - INFO  - (Bundle.java:405) - Preparing files for flashing
02/057/2014 15:57:58 - DEBUG - (Bundle.java:415) - Created the prepared folder
02/057/2014 15:57:58 - DEBUG - (Bundle.java:324) - Saving entry system.sin to disk
02/057/2014 15:57:58 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : system.sin
02/057/2014 15:57:58 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\system.sin
02/058/2014 15:58:58 - DEBUG - (Bundle.java:324) - Saving entry userdata.sin to disk
02/058/2014 15:58:58 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : userdata.sin
02/058/2014 15:58:58 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\userdata.sin
02/058/2014 15:58:58 - DEBUG - (Bundle.java:324) - Saving entry kernel.sin to disk
02/058/2014 15:58:58 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : kernel.sin
02/058/2014 15:58:58 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\kernel.sin
02/059/2014 15:59:07 - DEBUG - (Bundle.java:324) - Saving entry rpm.sin to disk
02/059/2014 15:59:07 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : rpm.sin
02/059/2014 15:59:07 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\rpm.sin
02/059/2014 15:59:07 - DEBUG - (Bundle.java:324) - Saving entry elabel-c6603-prototype_201305081233_10.4.B.0.569.sin to disk
02/059/2014 15:59:07 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : elabel-c6603-prototype_201305081233_10.4.B.0.569.sin
02/059/2014 15:59:07 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\elabel-c6603-prototype_201305081233_10.4.B.0.569.sin
02/059/2014 15:59:07 - DEBUG - (Bundle.java:324) - Saving entry boot_delivery.xml to disk
02/059/2014 15:59:07 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot_delivery.xml
02/059/2014 15:59:07 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot_delivery.xml
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/tz_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/tz_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/tz_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/emmc_appsboot_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/emmc_appsboot_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/emmc_appsboot_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/sbl3_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/sbl3_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/sbl3_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/sbl1_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/sbl1_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/sbl1_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/tz_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/tz_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/tz_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/s1sbl2_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/s1sbl2_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/s1sbl2_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/sbl3_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/sbl3_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/sbl3_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/sbl2_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/sbl2_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/sbl2_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/sbl1_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/sbl1_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/sbl1_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/s1sbl2_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/s1sbl2_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/s1sbl2_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/sbl2_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/sbl2_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/sbl2_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sinb
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry boot/Yuga_S1BootConfig_MiscTA_121203_1222.ta to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : boot/Yuga_S1BootConfig_MiscTA_121203_1222.tab
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\boot/Yuga_S1BootConfig_MiscTA_121203_1222.ta
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry amss_fs_3.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : amss_fs_3.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\amss_fs_3.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry amss_fs_2.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : amss_fs_2.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\amss_fs_2.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry amss_fs_1.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : amss_fs_1.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\amss_fs_1.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry cache.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : cache.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\cache.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry loader.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : loader.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\loader.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:324) - Saving entry fotakernel.sin to disk
02/059/2014 15:59:08 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : fotakernel.sin
02/059/2014 15:59:08 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\fotakernel.sin
02/059/2014 15:59:09 - DEBUG - (Bundle.java:324) - Saving entry partition-image.sin to disk
02/059/2014 15:59:09 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : partition-image.sin
02/059/2014 15:59:09 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\partition-image.sin
02/059/2014 15:59:10 - DEBUG - (Bundle.java:324) - Saving entry apps_log.sin to disk
02/059/2014 15:59:10 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : apps_log.sin
02/059/2014 15:59:10 - DEBUG - (Bundle.java:328) - Writing Entry to .\firmwares\prepared\apps_log.sin
02/059/2014 15:59:10 - INFO  - (FlashJob.java:33) - Please connect your device into flashmode.
02/059/2014 15:59:15 - INFO  - (MainSWT.java:129) - Device connected in flash mode
02/059/2014 15:59:16 - DEBUG - (SinFile.java:271) - Header size : 1024
02/059/2014 15:59:16 - DEBUG - (SinFile.java:271) - Header size : 1024
02/059/2014 15:59:16 - INFO  - (USBFlashWin32.java:16) - Opening device for R/W
02/059/2014 15:59:16 - INFO  - (X10flash.java:600) - Reading device information
02/059/2014 15:59:16 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
02/000/2014 16:00:15 - INFO  - (X10flash.java:612) - Unable to read from phone after having opened it.
02/000/2014 16:00:15 - INFO  - (X10flash.java:613) - trying to continue anyway
02/000/2014 16:00:15 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
02/000/2014 16:00:15 - INFO  - (X10flash.java:490) - Start Flashing
02/000/2014 16:00:15 - DEBUG - (X10flash.java:306) - Sending loaderC:\Flashtool\.\firmwares\prepared\loader.sin
02/000/2014 16:00:15 - DEBUG - (SinFile.java:271) - Header size : 1024
02/000/2014 16:00:15 - INFO  - (X10flash.java:237) - Processing loader.sin
02/000/2014 16:00:15 - INFO  - (X10flash.java:216) -     Checking header
02/000/2014 16:00:15 - DEBUG - (X10flash.java:220) - Sending part 1 of 1
02/000/2014 16:00:15 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
02/000/2014 16:00:15 - INFO  - (X10flash.java:550) - Ending flash session
02/000/2014 16:00:15 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
02/000/2014 16:00:15 - ERROR - (X10flash.java:523) - Error in processHeader : 22 : The device does not recognize the command. 
02/000/2014 16:00:15 - ERROR - (X10flash.java:524) - Error flashing. Aborted
02/000/2014 16:00:15 - INFO  - (MainSWT.java:125) - Device disconnected
02/000/2014 16:00:18 - INFO  - (MainSWT.java:129) - Device connected in flash mode
@shabbypenguin i have a 2gb sd card to hand if there is anything you want me to try. If i cant get it to work i will donate it for you to experiment with.

cheers
 
Last edited: