1.3.0.64 TEMS on XperiaFirm? - Xperia Z2 Q&A, Help & Troubleshooting

Have anybody noticed 1.3.0.64 firmware for D6503 on XperiaFirm? Since the last app update, I could see it.
Anybody tried this? Looks like it's an internal test firmware.

Just downloaded it. It's an 4.4.2 firmware with build number 17.1.2.A.0.251
I have attached build.prop if anybody wants to have a look!
EDIT: It has Ascom TEMS software in the /system. I have not installed this fw.

AlanDS said:
Have anybody noticed 1.3.0.64 firmware for D6503 on XperiaFirm? Since the last app update, I could see it.
Anybody tried this? Looks like it's an internal test firmware.
Click to expand...
Click to collapse
i have done download and instal firmware using flashtool 0.9.19.10 last update with windows 10 x64 but this is happen :
09/055/2016 10:55:38 - INFO - Flashtool Version 0.9.19.10 built on 04-10-2015 21:00:00
09/055/2016 10:55:38 - INFO - Executing search strategies to find proxy selector
09/055/2016 10:55:39 - INFO - No proxy found for IE. Trying next one
09/055/2016 10:55:39 - INFO - No proxy found for firefox. Trying next one
09/055/2016 10:55:39 - INFO - No proxy found for java. Trying next one
09/055/2016 10:55:40 - INFO - Syncing devices from github
09/055/2016 10:55:41 - INFO - Scanning devices folder for changes.
09/056/2016 10:56:05 - INFO - Pulling changes from github.
09/056/2016 10:56:07 - INFO - Devices sync finished.
09/056/2016 10:56:15 - INFO - Device connected with USB debugging off
09/056/2016 10:56:15 - INFO - For 2011 devices line, be sure you are not in MTP mode
09/058/2016 10:58:29 - INFO - Device disconnected
09/058/2016 10:58:40 - INFO - Device connected with USB debugging off
09/058/2016 10:58:40 - INFO - For 2011 devices line, be sure you are not in MTP mode
09/004/2016 11:04:37 - INFO - Device disconnected
09/004/2016 11:04:48 - INFO - Device connected with USB debugging off
09/004/2016 11:04:48 - INFO - For 2011 devices line, be sure you are not in MTP mode
09/007/2016 11:07:27 - INFO - Selected Bundle for Sony Xperia Z2 (D6503). FW release : 1.3.0.64. Customization : TEMS
09/007/2016 11:07:27 - INFO - Preparing files for flashing
09/008/2016 11:08:33 - INFO - Please connect your device into flashmode.
09/008/2016 11:08:37 - INFO - Device disconnected
09/008/2016 11:08:48 - INFO - Device connected in flash mode
09/008/2016 11:08:49 - INFO - Opening device for R/W
09/008/2016 11:08:49 - INFO - Reading device information
09/008/2016 11:08:49 - INFO - Phone ready for flashmode operations.
09/008/2016 11:08:49 - INFO - Opening TA partition 2
09/008/2016 11:08:50 - INFO - Current device : D6503 - BH9048Q716 - 1281-1985_R5A - 1278-4770_17.1.A.2.55 - GLOBAL-LTE_17.1.A.2.55
09/008/2016 11:08:50 - INFO - Closing TA partition
09/008/2016 11:08:50 - INFO - Start Flashing
09/008/2016 11:08:50 - INFO - Processing loader.sin
09/008/2016 11:08:50 - INFO - Checking header
09/008/2016 11:08:50 - INFO - Flashing data
09/008/2016 11:08:50 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AB_LA2.0.1_23_generic_5 / Bootloader status : ROOTABLE
09/008/2016 11:08:50 - INFO - Max packet size set to 512K
09/009/2016 11:09:00 - INFO - Making a TA backup
09/009/2016 11:09:00 - INFO - Opening TA partition 1
09/009/2016 11:09:00 - INFO - Start Dumping TA partition 1
09/009/2016 11:09:01 - INFO - Finished Dumping TA partition 1
09/009/2016 11:09:01 - INFO - TA partition 1 saved to C:\Users\Rachmat\.flashTool\registeredDevices\BH9048Q716\s1ta\2016-01-08_11-09-00\1.ta
09/009/2016 11:09:01 - INFO - Closing TA partition
09/009/2016 11:09:01 - INFO - Opening TA partition 2
09/009/2016 11:09:01 - INFO - Start Dumping TA partition 2
09/009/2016 11:09:02 - INFO - Finished Dumping TA partition 2
09/009/2016 11:09:02 - INFO - TA partition 2 saved to C:\Users\Rachmat\.flashTool\registeredDevices\BH9048Q716\s1ta\2016-01-08_11-09-00\2.ta
09/009/2016 11:09:02 - INFO - Closing TA partition
09/009/2016 11:09:02 - INFO - Parsing boot delivery
09/009/2016 11:09:02 - INFO - Ending flash session
09/009/2016 11:09:02 - ERROR - Found no matching config. Skipping boot delivery
09/009/2016 11:09:02 - ERROR - Error flashing. Aborted
09/009/2016 11:09:02 - INFO - Device connected in flash mode
09/009/2016 11:09:03 - INFO - Device disconnected
09/009/2016 11:09:05 - INFO - Device connected in flash mode
can you tell me how to fix this problem

Looks like a problem with bootloader. It doesn't matches with our device.

AlanDS said:
Looks like a problem with bootloader. It doesn't matches with our device.
Click to expand...
Click to collapse
i'm try to flash any version on my sirius and all done only this firmware can't be flashing, please tell me how this firmware work on my sirius.

jabrickjhi said:
i'm try to flash any version on my sirius and all done only this firmware can't be flashing, please tell me how this firmware work on my sirius.
Click to expand...
Click to collapse
Don't use it, avoid it because you don't need it. Stay with the 314 for rooting purposes on locked bootloader.

I need this firmware for my another sirius, cause this firmware noticed on xperiafirm via flashtool
Sent from my D6503 using Tapatalk

cachanilla86 said:
Don't use it, avoid it because you don't need it. Stay with the 314 for rooting purposes on locked bootloader.
Click to expand...
Click to collapse
I was initially interested on this firmware because it has TEMS software which is used for Mobile Network testing by the Engineers.
But now it looks like we need a different variant.

Related

[Q] Trouble with Flashtool 0.9.18.5 and Z2 23.1.A.1.28

Hello,
I am having some trouble flashing my Z2, I hope you can help me...
As you can see in the log below somethings get updated (confirmed in the service menu, Phone software V=1278-4770_23.1.A.28, file system V=global-lte_23.1.A.0.726). I have tried Sony's USB drivers and Flashtool drivers, 32/64 versions of flashtool itself (computer is 64 tho), also tried VodaUK and genericUK ftf (later is the one I want, both downloaded twice with Xperifirm), USB2 and USB3 ports... It always fails at the same point. After that the phone reboots into normal operating mode while still plugged (that's what you can see in the last entries).
I am uncheking all wipe options as i don't want to loose anything..
Code:
14/057/2015 09:57:32 - INFO - Flashtool Version 0.9.18.5 built on 14-02-2015 15:30:00
14/057/2015 09:57:32 - INFO - Executing search strategies to find proxy selector
14/057/2015 09:57:33 - INFO - No proxy found for IE. Trying next one
14/057/2015 09:57:33 - INFO - No proxy found for firefox. Trying next one
14/057/2015 09:57:33 - INFO - No proxy found for java. Trying next one
14/057/2015 09:57:43 - INFO - Syncing devices from github
14/057/2015 09:57:43 - INFO - Scanning devices folder for changes.
14/057/2015 09:57:54 - INFO - Pulling changes from github.
14/057/2015 09:57:57 - INFO - Devices sync finished.
14/058/2015 09:58:01 - INFO - Device disconnected
14/058/2015 09:58:16 - INFO - Selected Bundle for Sony Xperia Z2 (D6503). FW release : 23.1.A.1.28. Customization : Customized UK
14/058/2015 09:58:16 - INFO - Preparing files for flashing
14/059/2015 09:59:08 - INFO - Please connect your device into flashmode.
14/059/2015 09:59:23 - INFO - Device connected in flash mode
14/059/2015 09:59:23 - INFO - Opening device for R/W
14/059/2015 09:59:23 - INFO - Reading device information
14/059/2015 09:59:23 - INFO - Phone ready for flashmode operations.
14/059/2015 09:59:23 - INFO - Current device : D6503 - BH908DB616 - 1281-2651_R8C - 1278-4770_23.1.A.1.28 - GLOBAL-LTE_23.1.A.0.726
14/059/2015 09:59:23 - INFO - Start Flashing
14/059/2015 09:59:23 - INFO - Processing loader.sin
14/059/2015 09:59:23 - INFO - Checking header
14/059/2015 09:59:23 - INFO - Flashing data
14/059/2015 09:59:24 - INFO - Processing of loader.sin finished.
14/059/2015 09:59:24 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AB_LA3.0_L_15.4 / Bootloader status : NOT_ROOTABLE
14/059/2015 09:59:25 - INFO - Processing partition-image.sin
14/059/2015 09:59:25 - INFO - Checking header
14/059/2015 09:59:25 - INFO - Flashing data
14/059/2015 09:59:25 - INFO - Processing of partition-image.sin finished.
14/059/2015 09:59:25 - INFO - Parsing boot delivery
14/059/2015 09:59:25 - INFO - Phone boot version : S1_Boot_MSM8974AB_LA3.0_L_15.4. Boot delivery version : S1_Boot_MSM8974AB_LA3.0_L_15.4
14/059/2015 09:59:25 - INFO - Boot delivery up to date. Nothing to do
14/059/2015 09:59:25 - INFO - Processing kernel.sin
14/059/2015 09:59:25 - INFO - Checking header
14/059/2015 09:59:25 - INFO - Flashing data
14/059/2015 09:59:27 - INFO - Processing of kernel.sin finished.
14/059/2015 09:59:27 - INFO - Processing fotakernel.sin
14/059/2015 09:59:27 - INFO - Checking header
14/059/2015 09:59:27 - INFO - Flashing data
14/059/2015 09:59:29 - INFO - Processing of fotakernel.sin finished.
14/059/2015 09:59:29 - INFO - Processing amss_fs_2.sin
14/059/2015 09:59:29 - INFO - Checking header
14/059/2015 09:59:29 - INFO - Flashing data
14/059/2015 09:59:29 - INFO - Processing of amss_fs_2.sin finished.
14/059/2015 09:59:29 - INFO - Processing amss_fs_1.sin
14/059/2015 09:59:29 - INFO - Checking header
14/059/2015 09:59:29 - INFO - Flashing data
14/059/2015 09:59:29 - INFO - Processing of amss_fs_1.sin finished.
14/059/2015 09:59:29 - INFO - Processing amss_fsg.sin
14/059/2015 09:59:29 - INFO - Checking header
14/059/2015 09:59:29 - INFO - Flashing data
14/059/2015 09:59:29 - INFO - Processing of amss_fsg.sin finished.
14/059/2015 09:59:29 - INFO - Ending flash session
14/059/2015 09:59:29 - ERROR -
14/059/2015 09:59:29 - ERROR - Error flashing. Aborted
14/059/2015 09:59:29 - INFO - Device connected in flash mode
14/059/2015 09:59:35 - INFO - Device disconnected
14/059/2015 09:59:35 - INFO - Device connected in flash mode
14/000/2015 10:00:41 - INFO - Device disconnected
14/000/2015 10:00:50 - INFO - Device connected with USB debugging off
14/000/2015 10:00:50 - INFO - For 2011 devices line, be sure you are not in MTP mode
14/019/2015 10:19:26 - INFO - Device disconnected
I have to be doing something wrong, can you point out what is it?
Thanks guys!!
On what version of windows you are? if on win8 or 8.1 try reinstalling drivers after disabling driver signing also try run flashtool as administrator
ravijokhun said:
On what version of windows you are? if on win8 or 8.1 try reinstalling drivers after disabling driver signing also try run flashtool as administrator
Click to expand...
Click to collapse
THanks for the quick reply! I am on Win7 x64.
Forgot to add as part of troubleshooting: ran flashtool as user and as admin, install drivers both as user and admin too..
poiko said:
THanks for the quick reply! I am on Win7 x64.
Forgot to add as part of troubleshooting: ran flashtool as user and as admin, install drivers both as user and admin too..
Click to expand...
Click to collapse
You try using a different image? I can't imagine that'd be the problem, but for troubleshooting.
I'd also try a different cable and a different version of Flashtool.
King Cole said:
You try using a different image? I can't imagine that'd be the problem, but for troubleshooting.
I'd also try a different cable and a different version of Flashtool.
Click to expand...
Click to collapse
nah! Same thing... :crying:
This time tried with different cable, same
Also tried .726, same.. however now system info shows .726 everywhere which I guess is a good thing.
As for previous Flashtool version I could only find .13 which did not appear to do anything. Is there a another version between .13 and .18?
Thanks for your help..
poiko said:
nah! Same thing... :crying:
This time tried with different cable, same
Also tried .726, same.. however now system info shows .726 everywhere which I guess is a good thing.
As for previous Flashtool version I could only find .13 which did not appear to do anything. Is there a another version between .13 and .18?
Thanks for your help..
Click to expand...
Click to collapse
I don't know of .13, the only ones I know are .10, .11, .16, and .18, but you shouldn't need to worry about that too much I wouldn't think. I'd try flashing it on a different computer with a fresh install of the drivers. And be sure you're wiping all the right things too.
...erm
"wipe the right things"? I am certainly not wiping data, should I wipe others?
Try an earlier version of xperifirm, one that doesn't make xml files for flashtool.
Hi,
I've followed your suggestion, but in a slightly different way. Instead of using a previous version of Xperifirm, I did download the firmware directly from Flashtool and let it build the bundle. It worked!
Thanks for the help!
As pointed out, there must be something going on with the xml files done by Xperifirm.
Uncheck "Unknown" under partition list before you start flashing the stock ROM. The unknown partition includes a file named fwinfo.xml which isn't supposed to be there in the firmware bundle. Delete fwinfo.xml from the source folder before you build the ftf or uncheck unknown partition before flashing
tejaswi.rohit said:
Uncheck "Unknown" under partition list before you start flashing the stock ROM. The unknown partition includes a file named fwinfo.xml which isn't supposed to be there in the firmware bundle. Delete fwinfo.xml from the source folder before you build the ftf or uncheck unknown partition before flashing
Click to expand...
Click to collapse
I'll try this as I'm having problems using flashtool
Sent from my D6603 using Tapatalk 2
tejaswi.rohit said:
Uncheck "Unknown" under partition list before you start flashing the stock ROM. The unknown partition includes a file named fwinfo.xml which isn't supposed to be there in the firmware bundle. Delete fwinfo.xml from the source folder before you build the ftf or uncheck unknown partition before flashing
Click to expand...
Click to collapse
That certainly did the trick! I am now a happy owner of a carrier-debloated device!!
Thanks!:victory:
poiko said:
That certainly did the trick! I am now a happy owner of a carrier-debloated device!!
Thanks!:victory:
Click to expand...
Click to collapse
How do I do this
Sent from my D6603 using Tapatalk 2
bodomfan said:
How do I do this
Click to expand...
Click to collapse
Well... I've followed the guide below and the suggested previously
http://www.gizmobolt.com/2015/04/09...z3-23-1-a-0-690-ftf-using-flashtool-manually/

Sony LT26i bricked?

Hello i have the above device and after a failed attempt to put a lollipop version it (it worked at first) i tried to install the old OS back.After failing to do this properly(see the pattern here?.... ) the phone booted,but nothing worked.I restarted and it stuck on Sony logo.Back then i though it was bricked but i read somewhere that it is possible to restore it(i hope?).I think i am stuck at the following loop.
1.The only way for the phone to start is to plug the USB. (battery depleted?)
2.After a while(~10mins) the Sony Logo appears on its own. (here i think i get some juice in the battery).
3.While stuck there it takes ~30min to turn off again. (stops charging after Sony logo?)
So what i did is after i see the logo,I remove the battery,put it back in and plug the USB.Did this 3 times and step 2. speeds up which probably means i charged the battery a bit more). Then i am moving a step ahead trying to flash the .ftf OS file i downloaded through FlashTool64 using the rubber-band trick.Problem is it asks for the device drivers.I have downloaded these but there is not executable(just plain files).
How do i proceed?
Thanks in advance for any and every help you provide and sorry for any mistake in my English.
Update:managed to install drivers (i think) and now i am stuck here
13/056/2015 17:56:39 - INFO - Flashtool Version 0.9.19.8 built on 24-09-2015 22:00:00
13/056/2015 17:56:39 - INFO - Executing search strategies to find proxy selector
13/056/2015 17:56:39 - INFO - No proxy found for IE. Trying next one
13/056/2015 17:56:39 - INFO - No proxy found for firefox. Trying next one
13/056/2015 17:56:39 - INFO - No proxy found for java. Trying next one
13/056/2015 17:56:39 - INFO - Syncing devices from github
13/056/2015 17:56:39 - INFO - Scanning devices folder for changes.
13/056/2015 17:56:45 - INFO - Pulling changes from github.
13/056/2015 17:56:45 - INFO - Devices sync finished.
13/056/2015 17:56:50 - INFO - Device disconnected
13/057/2015 17:57:26 - INFO - Selected Bundle for LT26. FW release : 6.1.A.0.452. Customization : Generic CH(1257-3740)
13/057/2015 17:57:26 - INFO - Preparing files for flashing
13/057/2015 17:57:34 - INFO - Please connect your device into flashmode.
13/058/2015 17:58:10 - INFO - Device connected in flash mode
13/058/2015 17:58:11 - INFO - Opening device for R/W
13/058/2015 17:58:11 - INFO - Reading device information
13/058/2015 17:58:11 - INFO - Phone ready for flashmode operations.
13/058/2015 17:58:11 - INFO - Opening TA partition 2
13/058/2015 17:58:11 - INFO - Current device : Unknown: Jul 25 2013/14:37:45 - BX903AZHS2 - Unknown: Jul 25 2013/14:37:45 - Unknown: Jul 25 2013/14:37:45 - Unknown: Jul 25 2013/14:37:45
13/058/2015 17:58:11 - INFO - Closing TA partition
13/058/2015 17:58:11 - INFO - Start Flashing
13/058/2015 17:58:11 - INFO - Processing loader.sin
13/058/2015 17:58:11 - INFO - Checking header
13/058/2015 17:58:11 - INFO - Flashing data
13/058/2015 17:58:13 - INFO - Loader : S1_Root_de72 - Version : R5C004 / Boot version : R10C008 / Bootloader status : ROOTED
13/058/2015 17:58:13 - INFO - Max packet size set to 63K
13/058/2015 17:58:13 - INFO - Making a TA backup
13/058/2015 17:58:13 - INFO - Opening TA partition 1
13/058/2015 17:58:13 - INFO - Start Dumping TA partition 1
13/058/2015 17:58:14 - INFO - Finished Dumping TA partition 1
13/058/2015 17:58:14 - INFO - TA partition 1 saved to C:\Users\Jack\.flashTool\registeredDevices\BX903AZHS2\s1ta\2015-10-13_05-58-13\1.ta
13/058/2015 17:58:14 - INFO - Closing TA partition
13/058/2015 17:58:14 - INFO - Opening TA partition 2
13/058/2015 17:58:14 - INFO - Start Dumping TA partition 2
13/058/2015 17:58:15 - INFO - Finished Dumping TA partition 2
13/058/2015 17:58:15 - INFO - TA partition 2 saved to C:\Users\Jack\.flashTool\registeredDevices\BX903AZHS2\s1ta\2015-10-13_05-58-13\2.ta
13/058/2015 17:58:15 - INFO - Closing TA partition
13/058/2015 17:58:15 - INFO - Ending flash session
13/058/2015 17:58:15 - ERROR -
13/058/2015 17:58:15 - ERROR - Error flashing. Aborted
13/058/2015 17:58:15 - INFO - Device connected in flash mode
13/058/2015 17:58:16 - INFO - Device disconnected
13/058/2015 17:58:18 - INFO - Device connected in flash mode
13/059/2015 17:59:02 - INFO - Device disconnected
After that Sony logo appears and stays there.
Sorry for long post I cant post image link.
All I can suggest is to visit here http://forum.xda-developers.com/showthread.php?t=1849170 and read, read, and read some more.
es0tericcha0s said:
All I can suggest is to visit here http://forum.xda-developers.com/showthread.php?t=1849170 and read, read, and read some more.
Click to expand...
Click to collapse
I have seen the said thread and its very detailed,the problem is I cant identify in which state my phone is,aka which guide(trick) to follow.
If you don't have the bootloader unlocked, you must use flashtool = green light. You might try another version of flashtool or another download. http://forum.xda-developers.com/showthread.php?t=1723610
I managed to enter TWRP v2.8.0.1 (its bootloader right?).It is saying that no OS is installed.Also my pc can see the device but i can not install the drivers whatever i do.I have windows 10 but tried to Windows 7 too.Is there any other way to copy the ftf file i got on the SD card so i can install it from TWRP?
If you have TWRP (which you hadn't mentioned earlier...) then you can just download a rom zip and use that to install. ftf files do not work through TWRP. Only custom stuff.
es0tericcha0s said:
If you have TWRP (which you hadn't mentioned earlier...) then you can just download a rom zip and use that to install. ftf files do not work through TWRP. Only custom stuff.
Click to expand...
Click to collapse
Thanks i didn't know that.So custom stuff it is.Anything to recommend for the said device?
Also mt question still stands:How will i transfer the ROM on the phone since i cant install the drivers?
SD card...
Update:I finally found the reason why Flash tool failed to flash the stock android.I changed it to the older version instead and pulled the rubber band trick over the night.Woke up to a stock 4.0.4 android.
Now i am trying to update to 4.1.2 but PC companion says my phone has custom software(???) and the phone it self restarts to update and after 1 second with the update icon it restarts and says Update Failed.
Any thoughs?

M4 in bootloop

I messed around with my build.prop file (changed vendor and model to fool samsung Gear Fit) and I ended up with phone stuck in bootloop.
It turns on, SONY logo is displayed, then screen goes black and again SONY logo, and again...
Phone is rooted, with unlocked bootloader and with recovery. I have downloaded STOCK firmwares, I wanted to flash them using flashtool. Here's the output:
Code:
07/059/2015 20:59:29 - INFO - Selected Bundle for Sony Xperia M4 Aqua (E2303). FW release : 26.1.A.2.167. Customization : Customized CE1
07/059/2015 20:59:29 - INFO - Preparing files for flashing
07/000/2015 21:00:00 - INFO - Please connect your device into flashmode.
07/000/2015 21:00:01 - INFO - Opening device for R/W
07/000/2015 21:00:01 - INFO - Reading device information
07/000/2015 21:00:01 - INFO - Phone ready for flashmode operations.
07/000/2015 21:00:01 - INFO - Opening TA partition 2
07/000/2015 21:00:01 - INFO - Current device : Unknown: Feb 27 2015/10:41:51 - YT9113XHE7 - Unknown: Feb 27 2015/10:41:51 - 1291-5963_26.1.A.2.99 - Unknown: Feb 27 2015/10:41:51
07/000/2015 21:00:01 - INFO - Closing TA partition
07/000/2015 21:00:01 - INFO - Start Flashing
07/000/2015 21:00:01 - INFO - Processing loader.sin
07/000/2015 21:00:01 - INFO - Checking header
07/000/2015 21:00:01 - INFO - Flashing data
07/000/2015 21:00:01 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8936_LA2.0_33 / Bootloader status : ROOTABLE
07/000/2015 21:00:01 - INFO - Max packet size set to 512K
07/000/2015 21:00:02 - INFO - Making a TA backup
07/000/2015 21:00:02 - INFO - Opening TA partition 1
07/000/2015 21:00:02 - INFO - Start Dumping TA partition 1
07/000/2015 21:00:02 - INFO - Finished Dumping TA partition 1
07/000/2015 21:00:03 - INFO - TA partition 1 saved to C:\Users\Tomasz\.flashTool\registeredDevices\YT9113XHE7\s1ta\2015-11-07_09-00-02\1.ta
07/000/2015 21:00:03 - INFO - Closing TA partition
07/000/2015 21:00:03 - INFO - Opening TA partition 2
07/000/2015 21:00:03 - INFO - Start Dumping TA partition 2
07/000/2015 21:00:03 - INFO - Finished Dumping TA partition 2
07/000/2015 21:00:03 - INFO - TA partition 2 saved to C:\Users\Tomasz\.flashTool\registeredDevices\YT9113XHE7\s1ta\2015-11-07_09-00-02\2.ta
07/000/2015 21:00:03 - INFO - Closing TA partition
07/000/2015 21:00:03 - INFO - Parsing boot delivery
07/000/2015 21:00:04 - INFO - Ending flash session
[COLOR="Red"]07/000/2015 21:00:04 - ERROR -
07/000/2015 21:00:04 - ERROR - Error flashing. Aborted[/COLOR]
07/000/2015 21:00:04 - INFO - Device connected in flash mode
07/000/2015 21:00:04 - INFO - Device disconnected
Phone enetrs in fastboot and flashmode - I was able to flash recovery in this mode, but I can't flash stock using flashtool. PC-Comapnion recognizes some SONY device but to flash it devicu must be fully started EMMA crashes on my PC
Does anyone has .img files which I can flash in fastbootmode? (boot, system and data i think will be enough), or maybe there's something wrong with phone?
[EDIT]: problem solved. WHat I did:
- downloaded AOSP 5.1.1 beta and flashed in fastboot.
- now flashtool was able to flas latest stock rom.

SK17i - Can't flash ICS 4.0.4 Stock via flashtool with locked bootloader?!

Hey together,
i installed android 4.4.4 on my Xperia Mini Pro (SK17i) from Legacy & everything worked fine until suddenly the touch broke without any reason... The internet knew the problem and told me to go back to stock.
I relocked the bootloader in order to use Sony PC Companion, but "Companion" (it's not really what it's posing to be) told me there is no new software due to the fact that Sony disabled the support for our devices
Trying to flash several ICS Stock version found here in the forum didnt help either because the flashing process is always aborted... See the flash log:
16/048/2016 14:48:11 - INFO - Selected Bundle for SonyEricson Xperia Mini Pro(SK17i). FW release : 4.1.B.0.431. Customization : ME & North Africa
16/048/2016 14:48:11 - INFO - Preparing files for flashing
16/048/2016 14:48:20 - INFO - Please connect your device into flashmode.
16/048/2016 14:48:24 - INFO - Device connected in flash mode
16/048/2016 14:48:24 - INFO - Opening device for R/W
16/048/2016 14:48:24 - INFO - Reading device information
16/048/2016 14:48:24 - INFO - Phone ready for flashmode operations.
16/048/2016 14:48:24 - INFO - Opening TA partition 2
16/048/2016 14:48:24 - INFO - Current device : SK17i - BX902J08UP - 1249-7380_R1I - 1244-7088_4.1.B.0.431 - WORLD-i_4.1.B.0.431
16/048/2016 14:48:24 - INFO - Closing TA partition
16/048/2016 14:48:25 - INFO - Start Flashing
16/048/2016 14:48:25 - INFO - Processing loader.sin
16/048/2016 14:48:25 - INFO - Checking header
16/048/2016 14:48:25 - INFO - Flashing data
16/048/2016 14:48:27 - INFO - Loader : S1_Loader_Root_773f - Version : R4A069 / Boot version : R9B031 / Bootloader status : ROOTABLE
16/048/2016 14:48:27 - INFO - Max packet size set to 65536K
16/048/2016 14:48:27 - INFO - USB buffer size set to 65536K
16/048/2016 14:48:28 - INFO - No flash script found. Using 0.9.18 flash engine
16/048/2016 14:48:28 - INFO - Opening TA partition 2
16/048/2016 14:48:28 - INFO - Writing TA unit 00002774. Value : 01
16/048/2016 14:48:28 - INFO - Closing TA partition
16/048/2016 14:48:28 - INFO - Opening TA partition 2
16/048/2016 14:48:28 - INFO - Closing TA partition
16/048/2016 14:48:28 - INFO - Opening TA partition 2
16/048/2016 14:48:28 - INFO - Processing adsp.sin
16/048/2016 14:48:28 - INFO - Checking header
16/048/2016 14:48:28 - INFO - Flashing data
16/048/2016 14:48:31 - INFO - Processing amss.sin
16/048/2016 14:48:31 - INFO - Checking header
16/048/2016 14:48:31 - INFO - Flashing data
16/048/2016 14:48:39 - INFO - Processing amss_fs_mango.sin
16/048/2016 14:48:39 - INFO - Checking header
16/048/2016 14:48:39 - INFO - Flashing data
16/048/2016 14:48:39 - INFO - Processing cache.sin
16/048/2016 14:48:39 - INFO - Checking header
16/048/2016 14:48:39 - INFO - Flashing data
16/048/2016 14:48:39 - INFO - Processing fota0.sin
16/048/2016 14:48:39 - INFO - Checking header
16/048/2016 14:48:39 - INFO - Flashing data
16/048/2016 14:48:40 - INFO - Processing fota1.sin
16/048/2016 14:48:40 - INFO - Checking header
16/048/2016 14:48:40 - INFO - Flashing data
16/048/2016 14:48:41 - INFO - Processing kernel.sin
16/048/2016 14:48:41 - INFO - Checking header
16/048/2016 14:48:41 - INFO - Flashing data
16/048/2016 14:48:43 - INFO - Closing TA partition
16/048/2016 14:48:43 - INFO - Opening TA partition 2
16/048/2016 14:48:43 - INFO - Processing system.sin
16/048/2016 14:48:43 - INFO - Checking header
16/048/2016 14:48:44 - ERROR - Processing of system.sin finished with errors.
16/048/2016 14:48:44 - INFO - Ending flash session
16/048/2016 14:48:44 - ERROR -
16/048/2016 14:48:44 - ERROR - Error flashing. Aborted
16/048/2016 14:48:44 - INFO - Flashing finished.
16/048/2016 14:48:44 - INFO - Please unplug and start your phone
16/048/2016 14:48:44 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
16/048/2016 14:48:44 - INFO - Device connected in flash mode
16/048/2016 14:48:45 - INFO - Device disconnected
16/048/2016 14:48:46 - INFO - Device connected in flash mode
16/049/2016 14:49:27 - INFO - Device disconnected
Click to expand...
Click to collapse
What the hell is going wrong?! I would like to see my good old friend/phone working again :crying:
The Problem is that I cant use my phone at the moment, so "unknwon sources and debugging" are impossible to check for me!
Can anybody help me with this problem?
Greeting
alki
I have some problem, too
Try an older version Flashtool. I think that will do the trick if memory serves me right. And with older I mean around 0.9.4. Nope sorry, don't have it for you. Again, pretty sure you will succeed with an older version. But not exactly sure how far back you will have to go.
Try searching topics from when it was released to find out which versions where used back then.
Hiya thought id try and help
just fixed my phone (soft bricked phone... all i wanted was ICS on a locked bootloader... one nameless rom....and a bit of bad judgment my part....)
BUT spent 3 days searching/researching for all files needed to restore!
if you are running windows 10 can confirm that flashtool-0.9.18.1-windows works. Also search youtube for running on windows 10 have to disable signature.... easy as pie though!
also there is a tutorial on here for rolling back to stock gingerbread then to android 4.04 ICS + Root ( file working, a little bit complicated)- TUT....Xperia.4.0.4 ROM.....
i just flashed 4.0.4 (build 4.1.B.0.431) straight and prayed i wanted my phone back and ICS so bad!
this flash guide for bricked phone was really helpful androidgadgematic.... How to fix bricked....android unbrick. (has Stock rom firmware)
It has clear pictures for flashing
Note: Xperia mini pro Hold down volume down then connect to PC....
hope you get your phone back
4.0.4 was almost worth the bricking...lol, really smart
have all files if needed...
only problem is no Google Play, (says Play Shop yet lets me add account lol)
and no timer widget (NEXT mission)
hope this may be of some use to you / anyone as definitely not an expert. just found many dead links and soooo much info but not really that helpful (IMO)
UPDATE: TIMER WIDGET FIXED!
an XDA thread just search for xperia mini pro widgets loads of apks some better than original ( timer widget v3! )
APK INSTALL PROBLEM
install slideME (had to use phone internet, installs no problem) then AndExplorer installs APKS no problem
GOOGLE PLAY FIXED!
apkmirror... google play version 3.10.9 (2014-page 3) installed no problems
happy bunni

Unable to Update to Customized IN 34.2.A.0.333 [Solved]

I just got a Xperia X 5122 in India,
It is running stock MM and I want to upgrade to Nougat.
So I unlocked boot loader using fastboot.
I downloaded Customized IN 34.2.A.0.333 using xperiafirm and created ftf using flashtools. while flashing Im getting the below error.
29/003/2017 19:03:41 - INFO - Start Flashing
29/003/2017 19:03:41 - INFO - No loader in the bundle. Searching for one
29/003/2017 19:03:41 - INFO - No matching loader found
29/003/2017 19:03:41 - WARN - No loader found or set manually. Skipping loader
29/003/2017 19:03:41 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Bootloader status : ROOTED
29/003/2017 19:03:41 - INFO - Max packet size set to 4M
29/003/2017 19:03:41 - INFO - USB buffer size set to 512K
29/003/2017 19:03:44 - INFO - Parsing boot delivery
29/003/2017 19:03:44 - INFO - No flash script found.
29/003/2017 19:03:44 - INFO - Flash script is mandatory. Closing session
29/003/2017 19:03:44 - INFO - Ending flash session
29/003/2017 19:03:44 - INFO - Flashing finished.
29/003/2017 19:03:44 - INFO - Please unplug and start your phone
29/003/2017 19:03:44 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
29/003/2017 19:03:44 - INFO - Device connected in flash mode
Can anyone help? or suggest what is going on?
Solution: Flashtool 0.9.23.2 doesn't contain flash script for F5122 Model, go to \.flashTool\devices\F51XX make a copy of F5121_34.2.A.0.266.fsc and rename it to F5121_34.2.A.0.333.fsc and you will be able flash the ftf with some warnigs
you dont have a flash script for that firmware. You need to re-download the firmware with xperifirm(within flashtool) when it's done downloading and when you exit xperifirm flashtool will build a ftf for flashing, it will promt you with a question if you want to add a flash script.
kistigun said:
you dont have a flash script for that firmware. You need to re-download the firmware with xperifirm(within flashtool) when it's done downloading and when you exit xperifirm flashtool will build a ftf for flashing, it will promt you with a question if you want to add a flash script.
Click to expand...
Click to collapse
Hey, totally irrelevant question - are you running stock 7.0 as your desc says? why is that?
FoxTheLegend said:
Hey, totally irrelevant question - are you running stock 7.0 as your desc says? why is that?
Click to expand...
Click to collapse
not any more, was on stock 311 to see if battery drain was any less but it's the same. Currently on poison 2.01 311
kistigun said:
not any more, was on stock 311 to see if battery drain was any less but it's the same. Currently on poison 2.01 311
Click to expand...
Click to collapse
I downloaded posion. 333 I guess its worth the time flashing?
FoxTheLegend said:
I downloaded posion. 333 I guess its worth the time flashing?
Click to expand...
Click to collapse
You wont fix battery drain with it but it's always good to flash latest update
Thanks for the response,
current firmware s 34.0.A.2.292 which is MM, I'm trying to update to Nougat.
I also downloaded Customized MY .333 but flashtoll threw the same error.
I will try kistigun suggestion.
P.S. good to see someone from Weert
I cleaned the /download and *.ftf files in flash tools folder. The I downloaded the firmware using flashtools>xperiafirm>firmware download> firmware build.
It didn't prompt me for flash script. it builder the firmware and it try to flash it and the same error as the above popped.
can anyone share the flash script so I can integrate or copy it to flashtool's scripts folder?
hakdrg said:
I cleaned the /download and *.ftf files in flash tools folder. The I downloaded the firmware using flashtools>xperiafirm>firmware download> firmware build.
It didn't prompt me for flash script. it builder the firmware and it try to flash it and the same error as the above popped.
can anyone share the flash script so I can integrate or copy it to flashtool's scripts folder?
Click to expand...
Click to collapse
Weird, will share my flash script when i get home
kistigun said:
Weird, will share my flash script when i get home
Click to expand...
Click to collapse
Thanks Man!
Update 1 I tried to flash to Bundle for Sony Xperia X(F5122). FW release : 34.2.A.0.311. Customization : Customized CE1
and same error see the log below
30/006/2017 19:06:35 - INFO - Loaded 94 devices
30/006/2017 19:06:35 - INFO - Starting phone detection
30/006/2017 19:06:39 - INFO - Device disconnected
30/006/2017 19:06:55 - INFO - Selected Bundle for Sony Xperia X(F5122). FW release : 34.2.A.0.311. Customization : Customized CE1
30/006/2017 19:06:55 - INFO - Preparing files for flashing
30/007/2017 19:07:39 - INFO - Please connect your device into flashmode.
30/007/2017 19:07:50 - INFO - Device connected in flash mode
30/007/2017 19:07:50 - INFO - Opening device for R/W
30/007/2017 19:07:51 - INFO - Reading device information
30/007/2017 19:07:51 - INFO - Phone ready for flashmode operations.
30/007/2017 19:07:51 - INFO - Opening TA partition 2
30/007/2017 19:07:51 - INFO - Current device : F5122 - BH902DN65L - 1302-4789_R8A - 1300-4897_34.0.A.2.292 - GENERIC_34.0.A.2.292
30/007/2017 19:07:51 - INFO - Closing TA partition
30/007/2017 19:07:51 - INFO - Start Flashing
30/007/2017 19:07:51 - INFO - No loader in the bundle. Searching for one
30/007/2017 19:07:51 - INFO - No matching loader found
30/007/2017 19:07:51 - WARN - No loader found or set manually. Skipping loader
30/007/2017 19:07:51 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Bootloader status : ROOTED
30/007/2017 19:07:51 - INFO - Max packet size set to 4M
30/007/2017 19:07:51 - INFO - USB buffer size set to 512K
30/007/2017 19:07:53 - INFO - Parsing boot delivery
30/007/2017 19:07:53 - INFO - No flash script found.
30/007/2017 19:07:53 - INFO - Flash script is mandatory. Closing session
30/007/2017 19:07:53 - INFO - Ending flash session
30/007/2017 19:07:53 - INFO - Flashing finished.
30/007/2017 19:07:53 - INFO - Please unplug and start your phone
30/007/2017 19:07:53 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
30/007/2017 19:07:53 - INFO - Device connected in flash mode
30/008/2017 19:08:31 - INFO - Device disconnected
P.S.
Unknown sources and Debugging is Enabled inside my phone setting
Update 2 : I read on some thread there might be issue with flash mode drivers,I rechecked the driver and updated it, FLash tool is recognizing the driver and phone , I dont think this is an issue with the driver
I have to update/copy the flash script to \.flashTool\devices\F51XX right?
Latest verion in there is F5121_34.2.A.0.266.fs
hakdrg said:
Thanks Man!
Update 1 I tried to flash to Bundle for Sony Xperia X(F5122). FW release : 34.2.A.0.311. Customization : Customized CE1
and same error see the log below
30/006/2017 19:06:35 - INFO - Loaded 94 devices
30/006/2017 19:06:35 - INFO - Starting phone detection
30/006/2017 19:06:39 - INFO - Device disconnected
30/006/2017 19:06:55 - INFO - Selected Bundle for Sony Xperia X(F5122). FW release : 34.2.A.0.311. Customization : Customized CE1
30/006/2017 19:06:55 - INFO - Preparing files for flashing
30/007/2017 19:07:39 - INFO - Please connect your device into flashmode.
30/007/2017 19:07:50 - INFO - Device connected in flash mode
30/007/2017 19:07:50 - INFO - Opening device for R/W
30/007/2017 19:07:51 - INFO - Reading device information
30/007/2017 19:07:51 - INFO - Phone ready for flashmode operations.
30/007/2017 19:07:51 - INFO - Opening TA partition 2
30/007/2017 19:07:51 - INFO - Current device : F5122 - BH902DN65L - 1302-4789_R8A - 1300-4897_34.0.A.2.292 - GENERIC_34.0.A.2.292
30/007/2017 19:07:51 - INFO - Closing TA partition
30/007/2017 19:07:51 - INFO - Start Flashing
30/007/2017 19:07:51 - INFO - No loader in the bundle. Searching for one
30/007/2017 19:07:51 - INFO - No matching loader found
30/007/2017 19:07:51 - WARN - No loader found or set manually. Skipping loader
30/007/2017 19:07:51 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Bootloader status : ROOTED
30/007/2017 19:07:51 - INFO - Max packet size set to 4M
30/007/2017 19:07:51 - INFO - USB buffer size set to 512K
30/007/2017 19:07:53 - INFO - Parsing boot delivery
30/007/2017 19:07:53 - INFO - No flash script found.
30/007/2017 19:07:53 - INFO - Flash script is mandatory. Closing session
30/007/2017 19:07:53 - INFO - Ending flash session
30/007/2017 19:07:53 - INFO - Flashing finished.
30/007/2017 19:07:53 - INFO - Please unplug and start your phone
30/007/2017 19:07:53 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
30/007/2017 19:07:53 - INFO - Device connected in flash mode
30/008/2017 19:08:31 - INFO - Device disconnected
P.S.
Unknown sources and Debugging is Enabled inside my phone setting
Update 2 : I read on some thread there might be issue with flash mode drivers,I rechecked the driver and updated it, FLash tool is recognizing the driver and phone , I dont think this is an issue with the driver
I have to update/copy the flash script to \.flashTool\devices\F51XX right?
Latest verion in there is F5121_34.2.A.0.266.fs
Click to expand...
Click to collapse
Here is the flash script for f5121 34.2 firmware:
https://1drv.ms/u/s!AlGc5S9rgkBTt12-LTTknYr5CdR1
indeed, place it in the folder \.flashTool\devices\F51XX
kistigun said:
Weird, will share my flash script when i get home
Click to expand...
Click to collapse
kistigun said:
Here is the flash script for f5121 34.2 firmware:
https://1drv.ms/u/s!AlGc5S9rgkBTt12-LTTknYr5CdR1
indeed, place it in the folder \.flashTool\devices\F51XX
Click to expand...
Click to collapse
Thanks a lot for sharing the script file.
This file has same contents(text/script) as the F5121_34.2.A.0.266.fsc on my flash tools folder \devices\F51XX
Soulution So I renamed the file to F5122_34.2.A.0.333.fsc
And I tried flashing my phone and it started flashing with the below warning
30/042/2017 19:42:28 - WARN - Unit 2212 not found in bundle
30/042/2017 19:42:30 - WARN - Unit 2550 not found in bundle
30/042/2017 19:42:30 - WARN - Unit 2553 not found in bundle
Phone took usual times to restart but it booted to Nougat!!!
now I flashed Poison 2.1 to the phone using TWRP and everything is working fine!!!!
Calls, fingerprint,wifi,speakers and...I dont have ant issues so far!!
Thanks a lot for your support!! Fijn Weekend!
hakdrg said:
I just got a Xperia X 5122 in India,
It is running stock MM and I want to upgrade to Nougat.
So I unlocked boot loader using fastboot.
I downloaded Customized IN 34.2.A.0.333 using xperiafirm and created ftf using flashtools. while flashing Im getting the below error.
29/003/2017 19:03:41 - INFO - Start Flashing
29/003/2017 19:03:41 - INFO - No loader in the bundle. Searching for one
29/003/2017 19:03:41 - INFO - No matching loader found
29/003/2017 19:03:41 - WARN - No loader found or set manually. Skipping loader
29/003/2017 19:03:41 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_73 / Bootloader status : ROOTED
29/003/2017 19:03:41 - INFO - Max packet size set to 4M
29/003/2017 19:03:41 - INFO - USB buffer size set to 512K
29/003/2017 19:03:44 - INFO - Parsing boot delivery
29/003/2017 19:03:44 - INFO - No flash script found.
29/003/2017 19:03:44 - INFO - Flash script is mandatory. Closing session
29/003/2017 19:03:44 - INFO - Ending flash session
29/003/2017 19:03:44 - INFO - Flashing finished.
29/003/2017 19:03:44 - INFO - Please unplug and start your phone
29/003/2017 19:03:44 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
29/003/2017 19:03:44 - INFO - Device connected in flash mode
Can anyone help? or suggest what is going on?
Solution: Flashtool 0.9.23.2 doesn't contain flash script for F5122 Model, go to \.flashTool\devices\F51XX make a copy of F5121_34.2.A.0.266.fsc and rename it to F5121_34.2.A.0.333.fsc and you will be able flash the ftf with some warnigs
Click to expand...
Click to collapse
I'm trying to downgrade to MM from N in order to perform the dirtycow DRM exploit so as to be able to install PoisonRom (Android Nougat). This is all just to have roon on N, by the way... Anyways, the problem is, after solving the scripts issue, now I'm stuck at "Reading Device Information". This is the log:
09/051/2017 16:51:40 - INFO - Quietly closing devices repository.
09/051/2017 16:51:40 - WARN - close() called when useCnt is already zero
09/051/2017 16:51:40 - INFO - Devices sync finished.
09/051/2017 16:51:40 - INFO - Loading devices database
09/051/2017 16:51:40 - INFO - Loaded 94 devices
09/051/2017 16:51:40 - INFO - Starting phone detection
09/051/2017 16:51:44 - INFO - Device connected in flash mode
09/053/2017 16:53:11 - INFO - Selected Bundle for Sony Xperia X(F5121). FW release : 4.0.A.2.301_R8A. Customization : Customized TW
09/053/2017 16:53:11 - INFO - Preparing files for flashing
09/053/2017 16:53:59 - INFO - Please connect your device into flashmode.
09/054/2017 16:54:00 - INFO - Opening device for R/W
09/054/2017 16:54:00 - INFO - Reading device information
It's flashtool 0.9.23.1, running in windows 10, drivers installed, and Xperia X with .266 Nougat firmware
Any ideas?
I have same problem so my solution is changing the driver to android adb before flash room, I also backuped DRM with dirtycow after flash taiwan rom.

Categories

Resources