Database Develop

[q] flashing error help needed

cant able to flash kernel in my pc (xp) as my laptop is not working.using the latest version of flashtool installed all the drivers including gg and i may have done something to the drivers as i wanted tethering in winxp which i was not able to .any help on this matter would be good.my mobile is being recognized by pc
04/033/2013 19:33:39 - INFO - Opening device for R/W
04/033/2013 19:33:39 - INFO - Start Flashing
04/033/2013 19:33:39 - INFO - Processing loader
04/033/2013 19:33:39 - INFO - Checking header
04/033/2013 19:33:39 - INFO - Ending flash session
04/033/2013 19:33:39 - ERROR -
04/033/2013 19:33:39 - ERROR - Error flashing. Aborted
04/033/2013 19:33:40 - ERROR - Drivers need to be installed for connected device.
04/033/2013 19:33:40 - ERROR - You can find them in the drivers folder of Flashtool.
04/033/2013 19:33:41 - INFO - Device disconnected

Make sure the drivers are all installed, and that your USB cable is not jerky or anything.

Yea you need x8 driver.
Sent from my E15i using xda app-developers app

everthing is good and i installed the drivers from the folder and also gordons gate

reinstall flashtool and at the same time reinstall the drivers from the folder directory, that should solve it

@op pcc installed? just reinstall gg and keep trying. that often happens to me too.

reinstalled everything but still the same error ......pcc is not installed

nanda_123 said:
reinstalled everything but still the same error ......pcc is not installed
Click to expand...
Click to collapse
install pcc. there are drivers there that are needed. then reinstall gg and try a few times. hope it works.

cascabel said:
install pcc. there are drivers there that are needed. then reinstall gg and try a few times. hope it works.
Click to expand...
Click to collapse
yes it helped..first had to install pcc companion and then reinstall it for installing the drivers and after that it was detected by flashtool but was not able to flash and then a pop up of semc flash connected came win installed the drivers and i am done..thank u for u help

Bell C6906 - Flashtool fails with error

Hello,
I am trying to flash my Bell Mobile C6906 Xperia Z1 which is currently on 4.2 - 14.1.G.1.534 to C6906 14.1.G.2.257 Generic CA 1276-7484_R7A with a md5sum of 'eb6570c22572a9c0151a768b05ce9f54' which is available from the thread titled '[FTF] C6902 & C6903 & C6906 & C6943 FTF Mega Collection' in the General section using Flashtool 0.9.13.0.
I have attempted this on a Windows 8, Windows 7 and a OpenSUSE install and all have failed with the exact same error. I have installed the drivers, loaded the rom in flashboot mode, connected the Xperia Z1 and held down the volume button and had it flash green/red (I believe, I am colourblind) and it has prepared the file and attempted to flash but fails with the following error which was created on a Windows 7 Starter - 32bit machine.
Code:
21/016/2013 11:16:23 - INFO - <- This level is successfully initialized
21/016/2013 11:16:23 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
21/016/2013 11:16:29 - INFO - Device connected with USB debugging on
21/016/2013 11:16:30 - INFO - Connected device : Sony Xperia Z1
21/016/2013 11:16:31 - INFO - Installed version of busybox : N/A
21/016/2013 11:16:31 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-perf-gde8296d-02200-g6e85970 / Build number : 14.1.G.1.534
21/016/2013 11:16:31 - INFO - Checking root access
21/016/2013 11:16:31 - INFO - Root Access Allowed
21/016/2013 11:16:32 - INFO - Stopping ric service
21/016/2013 11:16:32 - INFO - ric service stopped successfully
21/016/2013 11:16:35 - INFO - List of connected devices (Device Id) :
21/016/2013 11:16:35 - INFO - - USB\VID_0FCE&PID_519E\BH900Z1B08 Driver installed : true
21/016/2013 11:16:35 - INFO - - USB\VID_0FCE&PID_519E&MI_01\6&1487FCA0&0&0001 Driver installed : true
21/016/2013 11:16:35 - INFO - - USB\VID_0FCE&PID_519E&MI_00\6&1487FCA0&0&0000 Driver installed : true
21/016/2013 11:16:35 - INFO - List of ADB devices :
21/016/2013 11:16:35 - INFO - - BH900Z1B08
21/016/2013 11:16:35 - INFO - List of fastboot devices :
21/016/2013 11:16:35 - INFO - - none
21/016/2013 11:16:51 - INFO - Selected C6906 / 14.1.G.2.257 / Generic CA
21/016/2013 11:16:52 - INFO - Preparing files for flashing
21/019/2013 11:19:04 - INFO - Please connect your device into flashmode.
21/021/2013 11:21:04 - INFO - Device disconnected
21/021/2013 11:21:48 - INFO - Opening device for R/W
21/021/2013 11:21:49 - INFO - Device disconnected
21/021/2013 11:21:49 - INFO - Start Flashing
21/021/2013 11:21:49 - INFO - Processing loader.sin
21/021/2013 11:21:49 - INFO - Checking header
21/021/2013 11:21:49 - INFO - Ending flash session
21/021/2013 11:21:49 - ERROR -
21/021/2013 11:21:49 - ERROR - Error flashing. Aborted
I have ran this with Administrative privileges on Windows and as root under Linux, I am currently at a loss as to how to fix this. I would really like to get off the Bell branded version and have an unbranded generic that I can keep updated to the newest version. (Which is the best I can do since sadly my bootloader cannot be unlocked)

I assume that you can root your Z1 as you are still on the 534 firmware.
Root your device and then follow this great GUIDE by Apollo89 (and be sure to hit him a thanks) to change the customization number to 1276-7484 then use SUS to get the latest firmware.
So basically what I'm telling you to do is to change the customization number to the one that you tried flashing it's ftf (1276-7484_R7A) and then get it on your device using SUS.
I can't confirm that it will work but hopefully it will.
Regards,
~J2C

I downloaded Build Props and allowed it root then changed my 'ro.semc.version.cust' to '1276-7484' and ro.semc.version.cus_revision to 'R1A' (from R11A) and then rebooted, on reboot it reset it back to 1276-3533 and R11A, tried again without changing cus_revision and still it reverted back.
It is most likely some issue with /system being read/writable, however I have set it so in root explorer and have multiple applications reporting that it is r/o (chmod 777) and do not appear to be having any errors with editing the build props, but they continue to revert when rebooting.

I found this C6906 Android 4.3 ftf
And I found this .257 firmware, but you need to send SMS or something to be able to download.
And I found this. it has 3 ftf's for C6906
Hope you find a working ftf.
Regards,
~J2C

Just2Cause said:
I found this C6906 Android 4.3 ftf
And I found this .257 firmware, but you need to send SMS or something to be able to download.
And I found this. it has 3 ftf's for C6906
Hope you find a working ftf.
Regards,
~J2C
Click to expand...
Click to collapse
Thanks, but according to this thread I can't update directly to 4.3 by using the ftf, it'll brick I don't use the 4.2 upgrade and then use PC Companion or similar to upgrade.

Well, flash the 257 from the other links...

Just2Cause said:
Well, flash the 257 from the other links...
Click to expand...
Click to collapse
The .257 from your links are identical to the one I was trying before, the exact same md5sum as before.

magwart said:
Thanks, but according to this thread I can't update directly to 4.3 by using the ftf, it'll brick I don't use the 4.2 upgrade and then use PC Companion or similar to upgrade.
Click to expand...
Click to collapse
I had the Bell branded 4.2 firmware installed on my 6906 and flashed the generic 4.3 firmware and have had no issues. Not sure if that post is 100% accurate. I also wiped my phone when I upgraded just so I could make sure I wouldn't run into any compatibility issues when I moved over.
After looking at your logs, it looks like the phone is not in flashboot. The flashtool is recognizing the phone in USB debug mode. Make sure you put the phone in flashboot before connecting to flashtool.
Here is a sample of my log.
Code:
16/047/2013 17:47:34 - INFO - <- This level is successfully initialized
16/047/2013 17:47:34 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
16/047/2013 17:47:39 - INFO - Device connected in flash mode
16/047/2013 17:47:48 - INFO - Selected C6906 / 14.2.A.0.290 / Generic CA
16/047/2013 17:47:49 - INFO - Preparing files for flashing
16/048/2013 17:48:01 - INFO - Please connect your device into flashmode.
16/048/2013 17:48:02 - INFO - Opening device for R/W
16/048/2013 17:48:03 - INFO - Reading device information
16/048/2013 17:48:03 - INFO - Phone ready for flashmode operations.
16/048/2013 17:48:03 - INFO - Current device : C6906 - BH90062B08 - 1276-3533_R11A - 1272-6084_14.1.G.1.534 - BELL-LTE_14.1.G.1.534
16/048/2013 17:48:03 - INFO - Start Flashing

mfreema said:
I had the Bell branded 4.2 firmware installed on my 6906 and flashed the generic 4.3 firmware and have had no issues. Not sure if that post is 100% accurate. I also wiped my phone when I upgraded just so I could make sure I wouldn't run into any compatibility issues when I moved over.
Also, when flashing, which version of the flashtool are you running? 32bit or 64bit?
Click to expand...
Click to collapse
I have ran 32bit on Windows 7 and 64bit on Windows 8. Both have had the same problem, and I can't figure out what the error is since it is blank. I suppose it has something to do with even a rooted system the /system partition remains not fully r/w on a locked bootloader.

magwart said:
I have ran 32bit on Windows 7 and 64bit on Windows 8. Both have had the same problem, and I can't figure out what the error is since it is blank. I suppose it has something to do with even a rooted system the /system partition remains not fully r/w on a locked bootloader.
Click to expand...
Click to collapse
Please see my updated post above.

magwart said:
I have ran 32bit on Windows 7 and 64bit on Windows 8. Both have had the same problem, and I can't figure out what the error is since it is blank. I suppose it has something to do with even a rooted system the /system partition remains not fully r/w on a locked bootloader.
Click to expand...
Click to collapse
Just try to flash the Android 4.3! I have done it many times on my phone from 534 to 290 and had 0 problems!
Regards,
~J2C

mfreema said:
Please see my updated post above.
Click to expand...
Click to collapse
I noticed that and got it to work in Flashmode, seems there was a driver issue - still causing an error:
Code:
21/029/2013 22:29:02 - INFO - Device connected in flash mode
21/029/2013 22:29:03 - INFO - Opening device for R/W
21/029/2013 22:29:03 - INFO - Reading device information
21/029/2013 22:29:03 - INFO - Unable to read from phone after having opened it.
21/029/2013 22:29:03 - INFO - trying to continue anyway
21/029/2013 22:29:03 - INFO - Start Flashing
21/029/2013 22:29:03 - INFO - Processing loader.sin
21/029/2013 22:29:03 - INFO - Checking header
21/029/2013 22:29:03 - INFO - Ending flash session
21/029/2013 22:29:03 - ERROR - Error in processHeader : 22 : The device does not recognize the command.
21/029/2013 22:29:03 - ERROR - Error flashing. Aborted
21/029/2013 22:29:03 - INFO - Device disconnected
Is the updated error.

maybe you are doing wrong steps?
Open flashtool > click on the flashing icon > select flashmode > navigate to where you have saved the ftf > Select the ftf you want to flash > then click on ok (or something like that, im in school right now so I cant tell) > wait till it finish preparing files > power off the phone, hold the VOL down and connect it to PC then wait till it finishes.
Regards,
~J2C

Just2Cause said:
maybe you are doing wrong steps?
Open flashtool > click on the flashing icon > select flashmode > navigate to where you have saved the ftf > Select the ftf you want to flash > then click on ok (or something like that, im in school right now so I cant tell) > wait till it finish preparing files > power off the phone, hold the VOL down and connect it to PC then wait till it finishes.
Regards,
~J2C
Click to expand...
Click to collapse
Thanks, I got it working! Currently using the Sony Update Service to .90 and 4.3. Now that I know that its possible to do this, I need to find a ROM that is compatible with working root.
Thanks again!

magwart said:
Thanks, I got it working! Currently using the Sony Update Service to .90 and 4.3. Now that I know that its possible to do this, I need to find a ROM that is compatible with working root.
Thanks again!
Click to expand...
Click to collapse
Finally :fingers-crossed:
EDIT: any .534 ftf is rootable, but you have to find one that has OTA update to .257 firmware. but it is not possible to root android 4.3 without unlocking bootloader (currently) so if you want root you should stick to 14.2.G.2.257 Android 4.2 till there is a way to root android 4.3.
Regards,
~J2C

Trying to flash a stock rom, but having an issue with flashmode.

The instant I enter flashmode the flash fails. Here is my log:
Code:
29/032/2014 09:32:24 - INFO - <- This level is successfully initialized
29/032/2014 09:32:24 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
29/032/2014 09:32:28 - INFO - Device connected with USB debugging on
29/032/2014 09:32:29 - INFO - Connected device : Sony Xperia T
29/032/2014 09:32:29 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
29/032/2014 09:32:29 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-g5b052b2-00814-g976ab37 / Build number : 9.1.A.1.141
29/032/2014 09:32:29 - INFO - Checking root access
29/032/2014 09:32:30 - INFO - Root Access Allowed
29/033/2014 09:33:49 - INFO - Selected Bundle for LT30p. FW release : 9.2.A.1.199. Customization : Generic UK
29/033/2014 09:33:49 - INFO - Preparing files for flashing
29/033/2014 09:33:54 - INFO - Please connect your device into flashmode.
29/034/2014 09:34:03 - INFO - Device disconnected
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:04 - INFO - Opening device for R/W
29/035/2014 09:35:04 - INFO - Start Flashing
29/035/2014 09:35:04 - INFO - Processing loader.sin
29/035/2014 09:35:04 - INFO - Checking header
29/035/2014 09:35:04 - INFO - Ending flash session
29/035/2014 09:35:04 - ERROR -
29/035/2014 09:35:04 - ERROR - Error flashing. Aborted
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:15 - INFO - Device disconnected
Any ideas what could be wrong or what I can do?
Thanks
Edit: I tried uninstalling the phone from Device Manager, but that had no effect. When the flash fails I see a popup in the corner saying this device malfunctioned/is not recognized.

Astralogic said:
The instant I enter flashmode the flash fails. Here is my log:
Code:
29/032/2014 09:32:24 - INFO - <- This level is successfully initialized
29/032/2014 09:32:24 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
29/032/2014 09:32:28 - INFO - Device connected with USB debugging on
29/032/2014 09:32:29 - INFO - Connected device : Sony Xperia T
29/032/2014 09:32:29 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
29/032/2014 09:32:29 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-g5b052b2-00814-g976ab37 / Build number : 9.1.A.1.141
29/032/2014 09:32:29 - INFO - Checking root access
29/032/2014 09:32:30 - INFO - Root Access Allowed
29/033/2014 09:33:49 - INFO - Selected Bundle for LT30p. FW release : 9.2.A.1.199. Customization : Generic UK
29/033/2014 09:33:49 - INFO - Preparing files for flashing
29/033/2014 09:33:54 - INFO - Please connect your device into flashmode.
29/034/2014 09:34:03 - INFO - Device disconnected
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:04 - INFO - Opening device for R/W
29/035/2014 09:35:04 - INFO - Start Flashing
29/035/2014 09:35:04 - INFO - Processing loader.sin
29/035/2014 09:35:04 - INFO - Checking header
29/035/2014 09:35:04 - INFO - Ending flash session
29/035/2014 09:35:04 - ERROR -
29/035/2014 09:35:04 - ERROR - Error flashing. Aborted
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:15 - INFO - Device disconnected
Any ideas what could be wrong or what I can do?
Thanks
Edit: I tried uninstalling the phone from Device Manager, but that had no effect. When the flash fails I see a popup in the corner saying this device malfunctioned/is not recognized.
Click to expand...
Click to collapse
1.- Are you sure you have the right FTF for your phone model?
2.- Are you sure the FTF file isn't corrupted? (download again)
3.- Are you sure the proper drivers are installed (install them from the "drivers" folder in the Flashtool folder).
4.- Are you sure your USB cable isn't damaged and is disconnecting while flashing (try a different cable).
I think I've read that excluding the TA partition and/or BASEBAND might help. Don't take my word for it, Google it first.

Antiga Prime said:
1.- Are you sure you have the right FTF for your phone model?
2.- Are you sure the FTF file isn't corrupted? (download again)
3.- Are you sure the proper drivers are installed (install them from the "drivers" folder in the Flashtool folder).
4.- Are you sure your USB cable isn't damaged and is disconnecting while flashing (try a different cable).
I think I've read that excluding the TA partition and/or BASEBAND might help. Don't take my word for it, Google it first.
Click to expand...
Click to collapse
1 - I have an Xperia T and this is the FTF I 'm trying to flash.
2 - Yes, I have re-downloaded from a mirror.
3 - That installer doesn't include drivers in it's list for Xperia T, the Xperia TX drivers failed to install, I tried them to see if they would work.
Edit: In flashtool, exclude baseband is clearly labelled, but exclude TA partition is not. I can exclude "partition", is that it? Or could it be the "FOTA" option?
4 - The cable isn't causing the problem. Tried another.
I have no idea how excluding the TA partition and/or the baseband. I'll read up about it and see if it helps.
I even used the full unroot option in SuperSU, just so I could try to update the official way but it still didn't work.

Astralogic said:
3 - That installer doesn't include drivers in it's list for Xperia T, the Xperia TX drivers failed to install, I tried them to see if they would work.
Edit: In flashtool, exclude baseband is clearly labelled, but exclude TA partition is not. I can exclude "partition", is that it? Or could it be the "FOTA" option?
4 - The cable isn't causing the problem. Tried another.
Click to expand...
Click to collapse
No, if you don't see the exclude TA, then the FTF doesn't have the "simlock.ta" file in it.
You should use the TX drivers. If you haven't installed drivers at all, then that is clearly an issue. You could try with this driver pack, but the drivers that come with Flashtool should work.
What error do you get when installing the drivers?

Antiga Prime said:
No, if you don't see the exclude TA, then the FTF doesn't have the "simlock.ta" file in it.
You should use the TX drivers. If you haven't installed drivers at all, then that is clearly an issue. You could try with this driver pack, but the drivers that come with Flashtool should work.
What error do you get when installing the drivers?
Click to expand...
Click to collapse
Here's a screenshot of the error.
But when I attempt to install the drivers you linked to above, the top driver (Sony(WinUSB), above Sony Net) in the Device Driver Installation Wizard window has a green tick next to it. The bottom one, Sony Net, still has a red X next to it.

Astralogic said:
Here's a screenshot of the error.
But when I attempt to install the drivers you linked to above, the top driver (Sony(WinUSB), above Sony Net) in the Device Driver Installation Wizard window has a green tick next to it. The bottom one, Sony Net, still has a red X next to it.
Click to expand...
Click to collapse
Correct me if I'm wrong, but it seems like you're using Windows 8. You need to disable driver signature enforcement, either by doing this, or Googling another method (there are several).
Notice that drivers have been extracted to the temp folder (check your screenshot); I'd copy that driver folder to somewhere else, just to have it on hand, and that way it's easier to install the drivers manually through the Windows Device Manager, something you'd need to do after disabling the driver signing, and something I'd do anyways regardless if you're on Windows 8 or not; if drivers don't come with a specific software (such as Nvidia or ATI drivers) then it's always possible and in some cases easier to just add the driver manually through the Device Manager.

Antiga Prime said:
Correct me if I'm wrong, but it seems like you're using Windows 8. You need to disable driver signature enforcement, either by doing this, or Googling another method (there are several).
Notice that drivers have been extracted to the temp folder (check your screenshot); I'd copy that driver folder to somewhere else, just to have it on hand, and that way it's easier to install the drivers manually through the Windows Device Manager, something you'd need to do after disabling the driver signing, and something I'd do anyways regardless if you're on Windows 8 or not; if drivers don't come with a specific software (such as Nvidia or ATI drivers) then it's always possible and in some cases easier to just add the driver manually through the Device Manager.
Click to expand...
Click to collapse
I got the drivers installed succesfully by disabling driver signature verification and running the installer, but I still get the same error in flashtool. I really thought that was going to fix it.

Astralogic said:
I got the drivers installed succesfully by disabling driver signature verification and running the installer, but I still get the same error in flashtool. I really thought that was going to fix it.
Click to expand...
Click to collapse
Open the Device Manager and check if you have any devices with a yellow exclamation mark/warning. Aside from that, try a computer with Windows 7, maybe?
If not, and considering that you get a "this device has malfunctioned" error in Windows, and it's not your USB cable, then your USB port on either your phone or computer might not be working properly.

Antiga Prime said:
Open the Device Manager and check if you have any devices with a yellow exclamation mark/warning. Aside from that, try a computer with Windows 7, maybe?
If not, and considering that you get a "this device has malfunctioned" error in Windows, and it's not your USB cable, then your USB port on either your phone or computer might not be working properly.
Click to expand...
Click to collapse
The bad news is it didn't work
The good news is I got more info this time
Take a look at this screenshot, it's definitely some time of driver issue, something called S1boot fails to install: Screenshot.
That is AFTER the successful installation of the TX drivers in the drivers folder, these errors occur the instant my phone enters flashmode.
Edit: Forgot to mention this was on another PC, running Windows 7.
Edit 2: Just to clarify, the instant my phone entered flashmode, the computer tried to install those drivers.
Edit 3: I found this, I'm about to try it. Fingers crossed.
Edit 4: Those drivers didn't work. In Windows 8, I right click the INF and it installs, but no success on the flash. In Windows 7 I get a message that this INF does not support this method of installation. There are no devices with a yellow exclamation in device manager on either computer ;(

OK I managed to update the firmware using Sony Update Server program, now I constantly get the message android.process.media has stopped working. I tried to use an app called Rescan Media Root to disable the media scanner but it didn't work. The message is relentless, the phone is unusable because of this damn message
Maybe it's occurring because I disabled some system app or something?

Astralogic said:
OK I managed to update the firmware using Sony Update Server program, now I constantly get the message android.process.media has stopped working. I tried to use an app called Rescan Media Root to disable the media scanner but it didn't work. The message is relentless, the phone is unusable because of this damn message
Maybe it's occurring because I disabled some system app or something?
Click to expand...
Click to collapse
Most likely you didn't wipe data, A.K.A. Factory Reset.

Antiga Prime said:
Most likely you didn't wipe data, A.K.A. Factory Reset.
Click to expand...
Click to collapse
You're right. But I fixed it by clearing the data for Download Manager and Media Manager (or something like that).

flashtool doesn't recognise phone is connected

hello, i want to use the flashtool but it keep asking to plug in the phone. i turned it off, and press volume down while connecting already.

avila188 said:
hello, i want to use the flashtool but it keep asking to plug in the phone. i turned it off, and press volume down while connecting already.
Click to expand...
Click to collapse
Sounds like you may need to install the flashtool-specific drivers. In your flashtool directory, there should be a "drivers" folder where you can install the flashtool (and fastboot)-specific drivers. I don't know if you need to have the latest version of flashtool (since this phone is still kind of new) to get a more appropriate driver set.
Also if you are installing these drivers in Windows 8 & up, you will likely have to install them while Driver Signature Enforcement (or whatever its called) is disabled. That method can be found easily via google search.

ok i installed the driver from the drivers folder. plugged the phone, recoqnised, but write up the following error:
20/030/2015 07:30:31 - ERROR - Processing of loader.sin finished with errors.
20/030/2015 07:30:31 - INFO - Ending flash session
20/030/2015 07:30:31 - ERROR -
20/030/2015 07:30:31 - ERROR - Error flashing. Aborted
20/030/2015 07:30:31 - INFO - Device connected in flash mode

avila188 said:
ok i installed the driver from the drivers folder. plugged the phone, recoqnised, but write up the following error:
20/030/2015 07:30:31 - ERROR - Processing of loader.sin finished with errors.
20/030/2015 07:30:31 - INFO - Ending flash session
20/030/2015 07:30:31 - ERROR -
20/030/2015 07:30:31 - ERROR - Error flashing. Aborted
20/030/2015 07:30:31 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
ok i installed all drivers, and it works.
now i flashed already and got the latest build, and my telstra apps are all gone! woohoo! i suppose now my phone is like unlocked and sony version ( no carrier)?
thanks to the uploader at
[FTF] STOCK FIRMWARES for D5803 & D5833
one thing tho, when i want to delete app shortcut, the x location is now at the top, not at the bottom on the apps shortcut. is this what you all have?

I Failed Flashing ROM with FlashTool

Hi all i tried to flash my XZ2 with flashtool and i downloaded the latest ROM from Xperifirm. I created FTF file from the ROM i downloaded by unchecking .TA files. I have unlocked bootloader with cmd (which means all the drivers must be installed properly). But it didnt show neither errors nor succeeding in flashing the ROM. When i exited flash boot mode, my phone still can be turned on normally.
In before, i softbricked my phone but managed to reflash it with EMMA, but not satisfied because it's android 8. Anyone please help me, what steps i missed here? Im super noob in this kind of stuff, so please explain it easily for me. Thank u!
14/037/2020 00:37:07 - INFO - Flashtool 0.9.31.0
14/037/2020 00:37:07 - INFO - Searching for a web proxy
14/037/2020 00:37:09 - INFO - No proxy found, using direct connection
14/037/2020 00:37:09 - INFO - Syncing devices from github
14/037/2020 00:37:09 - INFO - Opening devices repository.
14/037/2020 00:37:09 - INFO - Scanning devices folder for changes.
14/037/2020 00:37:23 - INFO - Changes have been found. Doing a hard reset (removing user modifications).
14/037/2020 00:37:25 - INFO - Quietly closing devices repository.
14/037/2020 00:37:25 - INFO - Devices sync finished.
14/037/2020 00:37:27 - INFO - Loading devices database
14/037/2020 00:37:27 - INFO - Loaded 129 devices
14/037/2020 00:37:27 - INFO - Starting phone detection
14/037/2020 00:37:31 - INFO - Device connected in flash mode
14/038/2020 00:38:36 - INFO - Selected Bundle for Sony Xperia XZ2(H8296). FW release : 52.1.A.3.49-R4C. Customization : Custom TW
14/038/2020 00:38:36 - INFO - Preparing files for flashing
14/041/2020 00:41:26 - INFO - Please connect your device into flashmode.
14/041/2020 00:41:27 - INFO - Using Gordon gate drivers version 3.1.0.0
14/041/2020 00:41:28 - INFO - USB buffer size set to 512K
14/041/2020 00:41:28 - INFO - Opening device for R/W
14/041/2020 00:41:29 - INFO - Device connected in flash mode
Click to expand...
Click to collapse

evermore05 said:
Hi all i tried to flash my XZ2 with flashtool and i downloaded the latest ROM from Xperifirm. I created FTF file from the ROM i downloaded by unchecking .TA files. I have unlocked bootloader with cmd (which means all the drivers must be installed properly). But it didnt show neither errors nor succeeding in flashing the ROM. When i exited flash boot mode, my phone still can be turned on normally.
In before, i softbricked my phone but managed to reflash it with EMMA, but not satisfied because it's android 8. Anyone please help me, what steps i missed here? Im super noob in this kind of stuff, so please explain it easily for me. Thank u!
Click to expand...
Click to collapse
I have solved the problem. So i need to install the driver from C:\Flashtool\drivers, ticked the flash boot and fast boot, include .TA files in the FTF file, and not plugging my phone in USB 3.0 slot. Hope this would be useful for anyone having the same problem as mine.