Xpeia XA Dual 3112 Soft-Brick after flashing 33.2.B.3.74 via Flashtool - Sony Xperia XA Questions & Answers
I was trying to update my Xperia XA Dual 3112 to the last 33.2.B.3.74 via Flashtool. After the flashing finished "successfully" (according to the Flashtool) I got a bricked phone!!! No Flashboot, no battery charging icon, no Sony logo, no response to any button combination, no vibrations, nothing. Only red led when it is plugged into the PC USB or wall charger, and that's it!!! Any ideas how to fix it??? =( When connected to Flashtool it keeps saying "Device connected with USB debugging off / For 2011 devices line, be sure you are not in MTP mode". If I leave it alone connected to the PC, after 30 sec Flashtool says "Device disconnected". If I keep pressing the Vol Down or Power button, it keeps disconnecting and reconnecting every 15-20 sec.
Here is the Flashtool log after Flashing the fw:
21/011/2016 20:11:18 - INFO - <- This level is successfully initialized
21/011/2016 20:11:20 - INFO - Flashtool Version 0.9.22.3 built on 08-06-2016 22:30:00
21/011/2016 20:11:20 - INFO - Executing search strategies to find proxy selector
21/011/2016 20:11:20 - INFO - No proxy found for IE. Trying next one
21/011/2016 20:11:20 - INFO - Strategy firefox failed trying next one : No Firefox installation found
21/011/2016 20:11:20 - INFO - No proxy found for java. Trying next one
21/011/2016 20:11:20 - INFO - Syncing devices from github
21/011/2016 20:11:20 - INFO - Opening devices repository.
21/011/2016 20:11:21 - INFO - Scanning devices folder for changes.
21/011/2016 20:11:36 - INFO - Pulling changes from github.
21/011/2016 20:11:36 - INFO - Quietly closing devices repository.
21/011/2016 20:11:36 - INFO - Devices sync finished.
21/011/2016 20:11:36 - INFO - Loading devices database
21/011/2016 20:11:36 - INFO - Loaded 94 devices
21/011/2016 20:11:36 - INFO - Starting phone detection
21/011/2016 20:11:44 - INFO - Device connected with USB debugging off
21/011/2016 20:11:44 - INFO - For 2011 devices line, be sure you are not in MTP mode
21/015/2016 20:15:01 - INFO - Device disconnected
21/017/2016 20:17:44 - INFO - Selected Bundle for Sony Xperia XA(F3112). FW release : 33.2.B.3.74. Customization : CIS RU/UA/KZ/BY
21/017/2016 20:17:44 - INFO - Preparing files for flashing
21/019/2016 20:19:02 - INFO - Please connect your device into flashmode.
21/019/2016 20:19:20 - INFO - Device connected in flash mode
21/019/2016 20:19:20 - INFO - Opening device for R/W
21/019/2016 20:19:21 - INFO - Reading device information
21/019/2016 20:19:21 - INFO - Phone ready for flashmode operations.
21/019/2016 20:19:21 - INFO - Opening TA partition 2
21/019/2016 20:19:21 - INFO - Current device : F3112 - RQ3000YZSZ - 1302-4379_R5A - 1300-9504_33.2.B.2.35 - GENERIC_33.2.B.2.35
21/019/2016 20:19:21 - INFO - Closing TA partition
21/019/2016 20:19:21 - INFO - Start Flashing
21/019/2016 20:19:21 - INFO - Processing loader.sin
21/019/2016 20:19:21 - INFO - Checking header
21/019/2016 20:19:21 - INFO - Flashing data
21/019/2016 20:19:21 - INFO - Loader : S1_Root_cf2a - Version : MT6755_13 / Boot version : S1_Boot_MT6755_M0.MP6_13 / Bootloader status : ROOTABLE
21/019/2016 20:19:21 - INFO - Max packet size set to 8M
21/019/2016 20:19:21 - INFO - USB buffer size set to 512K
21/019/2016 20:19:23 - INFO - Parsing boot delivery
21/019/2016 20:19:26 - INFO - No flash script found. Using 0.9.18 flash engine
21/019/2016 20:19:26 - INFO - Opening TA partition 2
21/019/2016 20:19:26 - INFO - Writing TA unit 00002774. Value : 01
21/019/2016 20:19:26 - INFO - Closing TA partition
21/019/2016 20:19:26 - INFO - Processing partitions.sin
21/019/2016 20:19:26 - INFO - Checking header
21/019/2016 20:19:26 - INFO - Flashing data
21/019/2016 20:19:26 - INFO - Phone boot version : S1_Boot_MT6755_M0.MP6_13. Boot delivery version : S1_Boot_MT6755_M0.MP6_16
21/019/2016 20:19:26 - INFO - Going to flash boot delivery
21/019/2016 20:19:26 - INFO - Opening TA partition 2
21/019/2016 20:19:26 - INFO - Flashing Tuba_S1BootConfig_MiscTA.ta to partition 2
21/019/2016 20:19:26 - INFO - Writing TA unit 0000084F. Value : 1A CE 2C 00 01 00 07 05 00 02 02 10 00 10 05 00 01 02 68 00 10 04 00 03 01 01 00 04 00 04 81 01 00 02 00 04 85 05 00 05 82 68 00 10 02 00 05 85 12 00 02 00 A9 09 BE BA A9 09 00 00 00 FA BE BA 00 FA 00 00 04 00 03 00 02 00 04 00 04 00 B8 0B 0E 00 06 00 58 1B 01 4B 00 00 00 03 96 00 96 00 07 00 07 00 00 00 00 40 00 03 00 09 00 01 05 00 08 00 01 96 00
21/019/2016 20:19:26 - INFO - Writing TA unit 000008FD. Value : 00
21/019/2016 20:19:26 - INFO - Closing TA partition
21/019/2016 20:19:26 - INFO - Opening TA partition 2
21/019/2016 20:19:26 - INFO - Processing lk_S1-BOOT-LIVE-CF2A-0004-MMC.sin
21/019/2016 20:19:26 - INFO - Checking header
21/019/2016 20:19:26 - INFO - Flashing data
21/019/2016 20:19:27 - INFO - Processing lk2_S1-BOOT-LIVE-CF2A-0004-MMC.sin
21/019/2016 20:19:27 - INFO - Checking header
21/019/2016 20:19:27 - INFO - Flashing data
21/019/2016 20:19:27 - INFO - Processing logo_S1-BOOT-LIVE-CF2A-0004-MMC.sin
21/019/2016 20:19:27 - INFO - Checking header
21/019/2016 20:19:27 - INFO - Flashing data
21/019/2016 20:19:27 - INFO - Processing preloader_s1sbl_S1-BOOT-LIVE-CF2A-0004-MMC.sin
21/019/2016 20:19:27 - INFO - Checking header
21/019/2016 20:19:27 - INFO - Flashing data
21/019/2016 20:19:27 - INFO - Processing tee1_S1-BOOT-LIVE-CF2A-0004-MMC.sin
21/019/2016 20:19:27 - INFO - Checking header
21/019/2016 20:19:27 - INFO - Flashing data
21/019/2016 20:19:27 - INFO - Processing tee2_S1-BOOT-LIVE-CF2A-0004-MMC.sin
21/019/2016 20:19:27 - INFO - Checking header
21/019/2016 20:19:27 - INFO - Flashing data
21/019/2016 20:19:27 - INFO - Closing TA partition
21/019/2016 20:19:27 - INFO - Opening TA partition 2
21/019/2016 20:19:28 - INFO - Processing boot.sin
21/019/2016 20:19:28 - INFO - Checking header
21/019/2016 20:19:28 - INFO - Flashing data
21/019/2016 20:19:30 - INFO - Closing TA partition
21/019/2016 20:19:30 - INFO - Opening TA partition 2
21/019/2016 20:19:30 - INFO - Processing cache.sin
21/019/2016 20:19:30 - INFO - Checking header
21/019/2016 20:19:30 - INFO - Flashing data
21/019/2016 20:19:31 - INFO - Processing fotakernel.sin
21/019/2016 20:19:31 - INFO - Checking header
21/019/2016 20:19:31 - INFO - Flashing data
21/019/2016 20:19:33 - INFO - Processing md1arm7.sin
21/019/2016 20:19:33 - INFO - Checking header
21/019/2016 20:19:33 - INFO - Flashing data
21/019/2016 20:19:34 - INFO - Processing md1dsp.sin
21/019/2016 20:19:34 - INFO - Checking header
21/019/2016 20:19:34 - INFO - Flashing data
21/019/2016 20:19:34 - INFO - Processing md1img.sin
21/019/2016 20:19:34 - INFO - Checking header
21/019/2016 20:19:34 - INFO - Flashing data
21/019/2016 20:19:36 - INFO - Closing TA partition
21/019/2016 20:19:36 - INFO - Opening TA partition 2
21/019/2016 20:19:36 - INFO - Processing oem.sin
21/019/2016 20:19:36 - INFO - Checking header
21/019/2016 20:19:36 - INFO - Flashing data
21/019/2016 20:19:38 - INFO - Processing system.sin
21/019/2016 20:19:38 - INFO - Checking header
21/019/2016 20:19:38 - INFO - Flashing data
21/023/2016 20:23:26 - INFO - Closing TA partition
21/023/2016 20:23:26 - INFO - Opening TA partition 2
21/023/2016 20:23:26 - INFO - Closing TA partition
21/023/2016 20:23:26 - INFO - Opening TA partition 2
21/023/2016 20:23:26 - INFO - Processing elabel.sin
21/023/2016 20:23:26 - INFO - Checking header
21/023/2016 20:23:27 - INFO - Flashing data
21/023/2016 20:23:28 - INFO - Closing TA partition
21/023/2016 20:23:28 - INFO - Opening TA partition 2
21/023/2016 20:23:29 - INFO - Writing TA unit 00002725. Value : 32 30 31 36 2D 30 39 2D 32 31 20 32 30 3A 32 33 3A 32 38 00
21/023/2016 20:23:29 - INFO - Writing TA unit 00002774. Value : 00
21/023/2016 20:23:29 - INFO - Closing TA partition
21/023/2016 20:23:29 - INFO - Ending flash session
21/023/2016 20:23:29 - INFO - Flashing finished.
21/023/2016 20:23:29 - INFO - Please unplug and start your phone
21/023/2016 20:23:29 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
21/023/2016 20:23:29 - INFO - Device connected in flash mode
21/023/2016 20:23:47 - INFO - Device disconnected
Any suggestions would be highly appreciated, as the device is only few hours old.
I see here that flashtool says that phone is connected with USB debugging off, that needs to be turned on also unknown sources. Maybe that can be problem... Is bootloader unlocked?
Sent from my Sony Xperia XA using XDA Labs
---------- Post added at 11:07 PM ---------- Previous post was at 10:48 PM ----------
http://xperiahealthcentre.weebly.com/fix-a-brick.html try also this site, maybe can help.
Sent from my Sony Xperia XA using XDA Labs
gms91 said:
I see here that flashtool says that phone is connected with USB debugging off, that needs to be turned on also unknown sources. Maybe that can be problem... Is bootloader unlocked?
Sent from my Sony Xperia XA using XDA Labs
---------- Post added at 11:07 PM ---------- Previous post was at 10:48 PM ----------
Sent from my Sony Xperia XA using XDA Labs
Click to expand...
Click to collapse
In order to turn on the USB Debugging and the Unknown Sources, the phone must be working. My phone is dead: no response to any actions. The only thing I get is the red led when I plug in the phone to the PS USB or to the wall charger. The battery was about 100% when I flashed the new fw, so still should be almost full.
The bootloader is not unlocked as I bought the phone only a few hours ago, and I just wanted to update it to the last fw version.
gms91 said:
I see here that flashtool says that phone is connected with USB debugging off, that needs to be turned on also unknown sources. Maybe that can be problem... Is bootloader unlocked?
Sent from my Sony Xperia XA using XDA Labs
---------- Post added at 11:07 PM ---------- Previous post was at 10:48 PM ----------
Sent from my Sony Xperia XA using XDA Labs
Click to expand...
Click to collapse
The link to the website that you suggested me is not working for me, as the only offer solutions for the devices which can enter Flashmode. As I mentioned in my previous posts, I can not enter Flashmode. The phone gives no reaction to any button combinations. Thanks for the suggestion anyway.
My big concern is that the phone does not enter any mode, nor Flashmode neither Fastboot (my bootloader is not unlocked anyway, but I still have to get the vibrations, no?). It does not make any vibration or any sign of life when trying any button combination. Should that mean it's totally dead? Please help. Any suggestion?
I have read in the Thread : [Guide to recover 2012 and older Xperia phones] that people get to connect the device in Flashmode (in order to flash a stock ftf) in between the bootloops. I have no idea if my device is in bootloops or not, because I can not get any display sign, no Sony logo, or even a black screen on. Even though, if I connect it to the computer, I can hear each 5-10 sec that the device connects and disconnects from to computer. Shoul that mean it is a boot loop? How to identify if it is or not?
Also, according to the same [Guide], it may help if the battery drains completely, and in this case you can just charge the battery with a wall charger, then to try to enter Flashmode. But how can you get your battery drained it the phone doesn't respont to anything, no bootloop or screen on? Xperia XA has a built in battery, so taking off the battery is not a solution, especially for a phone which you bought a few hours ago
I am not a noobie in flashing and recovering android devices from different stages of brickness. And I am pretty sure I didn't miss anything or did something wrong during the flashing instalation. And yes, I have all the drivers installed on the PC (Win 10) as I flashed another version of fw 2.73 before that and everything went smooth. And yes, I did check the checkboxes for the TA.
I have already read hundreds of messages and tens of pages from the Xperia Recovery Guide, and nobody seemed to have a similar problem with similar sindroms. Shoul that mean that my new XA is totally dead? Reminder: the bootloader is not unlocked, so I still have a hope.
More experienced guys, please, give me some hints...
Vector Edge said:
I am not a noobie in flashing and recovering android devices from different stages of brickness. And I am pretty sure I didn't miss anything or did something wrong during the flashing instalation. And yes, I have all the drivers installed on the PC (Win 10) as I flashed another version of fw 2.73 before that and everything went smooth. And yes, I did check the checkboxes for the TA.
I have already read hundreds of messages and tens of pages from the Xperia Recovery Guide, and nobody seemed to have a similar problem with similar sindroms. Shoul that mean that my new XA is totally dead? Reminder: the bootloader is not unlocked, so I still have a hope.
More experienced guys, please, give me some hints...
Click to expand...
Click to collapse
Did you use the latest version of flashtool?(the bootloader does NOT need to be unlocked for this)
Use latest version of flashtool in simple mode only and select YES if asked for a fsc script
If you use flashtool in Pro mode all the lower check boxes for the ftf parts mean the opposite
Did you include the simlock.ta part(big no no pretty sure only Sony service can ressurect it)
From my experience with xperia devices if there's no response when connecting to the USB and a red led Only Sony service can restore it especially if the simlock.ta part of the ftf was included. Sorry to hear about your problem but I'd take it to Sony and say it died doing the latest software update(don't mention anything about flashtool you should be fine)
Someone please correct me if I'm wrong
I used flashtool 0.9.22.3 myself just last week to update to 33.2.A.2.93 no problem at all(I know this doesn't help you) but it confirms that flashtool works fine on the xa only used it in simple mode with yes to the fsc script with only the simlock.ta part excluded
To force the xa to turn off hold vol up and the power button till it vibrates 3 times.
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Did you use the latest version of flashtool?(the bootloader does NOT need to be unlocked for this)
Use latest version of flashtool in simple mode only and select YES if asked for a fsc script
If you use flashtool in Pro mode all the lower check boxes for the ftf parts mean the opposite
Did you include the simlock.ta part(big no no pretty sure only Sony service can ressurect it)
From my experience with xperia devices if there's no response when connecting to the USB and a red led Only Sony service can restore it especially if the simlock.ta part of the ftf was included. Sorry to hear about your problem but I'd take it to Sony and say it died doing the latest software update(don't mention anything about flashtool you should be fine)
Someone please correct me if I'm wrong
I used flashtool 0.9.22.3 myself just last week to update to 33.2.A.2.93 no problem at all(I know this doesn't help you) but it confirms that flashtool works fine on the xa only used it in simple mode with yes to the fsc script with only the simlock.ta part excluded
To force the xa to turn off hold vol up and the power button till it vibrates 3 times.
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
- Yes, I have used the very last version of the Flashtool available on their website;
- I mentioned about the locked bootloader for the purpose of mentioning to not being able to use Fastboot;
- I used the SIMPLE mode of the Flashtool;
- I chose NO for the FSC script. Would THIS be the party pooper???
- I did not include the simlock.ta, as I using the SIMPLE Mode in the Flashtool, and as far as I know, it is excluded by default in the last version of the Flashtool.
- Right before this happened, I updated the same phone with the same PC and Flashtool to the xx.x.x.2.73 and everything went fine. And I also chose NO for the FSC script. But it flashed properly. BTW, what does this FSC do after all?
-The phone is not reacting to the button combinations, therefore i can not use the vol up + power, it never vibrates.
Thanks for your response anyway.
BTW, an important think is that I excluded all the TA checkbox options in the flashtool (there were three or four I think). So that should not be concern. After reading hundreds of posts I found out this can be a big issue.
I have seen here on XDA, in the [Guide] Recover 2012 Xperias and newer, that guys are suggesting two totally different (at the first sight) options in order to unbrick a Xperia.
1. Drain battery completely.
2. Plug the phone in the wall charger and wait for days.
As far as I understand, plugging in a phone with a bad kernel will not charge the battery, the battery will drain, after that it will start to recharge. But this works in case when you don't get a red light when plugging in the phone. In my case I get the red led right away, once I plug it in USB or charger, but nothing more than that, no bootloops which would drain my battery, no charging battery icon, no black screen on, nothing...
Vector Edge said:
I have seen here on XDA, in the [Guide] Recover 2012 Xperias and newer, that guys are suggesting two totally different (at the first sight) options in order to unbrick a Xperia.
1. Drain battery completely.
2. Plug the phone in the wall charger and wait for days.
As far as I understand, plugging in a phone with a bad kernel will not charge the battery, the battery will drain, after that it will start to recharge. But this works in case when you don't get a red light when plugging in the phone. In my case I get the red led right away, once I plug it in USB or charger, but nothing more than that, no bootloops which would drain my battery, no charging battery icon, no black screen on, nothing...
Click to expand...
Click to collapse
I can confirm, if phone have only red led and you can listen plug/unplug sound when the phone is connected on the PC, the phone is in bootloop on kernel/ramdisk init, you have same result as flashing a bad boot.img
If you are lucky the preloader is not corrupted.
Try to plug phone to PC, put Flashtool in "waiting for device in flashmode" state, hold vol- until the phone "reboot" (next time you listen the plug sound). The flashing process may start.
On the very begin of the init, the phone will start with flashmode mode for 2sec, if a command is send at this moment, it will stay in that mode. It's like an emergency access, thank you MTK
XA and Ultra are not Qualcomm, if you want guides, tuto, dev tools, you have to think MTK. Look at Elephone M3 or P9000 to understand
rrvuhpg said:
I can confirm, if phone have only red led and you can listen plug/unplug sound when the phone is connected on the PC, the phone is in bootloop on kernel/ramdisk init, you have same result as flashing a bad boot.img
If you are lucky the preloader is not corrupted.
Try to plug phone to PC, put Flashtool in "waiting for device in flashmode" state, hold vol- until the phone "reboot" (next time you listen the plug sound). The flashing process may start.
On the very begin of the init, the phone will start with flashmode mode for 2sec, if a command is send at this moment, it will stay in that mode. It's like an emergency access, thank you MTK
XA and Ultra are not Qualcomm, if you want guides, tuto, dev tools, you have to think MTK. Look at Elephone M3 or P9000 to understand
Click to expand...
Click to collapse
I understand that MTK is not Qualcomm, and there is a different approach when in comes to unbricking the phone. Could you, PLEASE, suggest me a source where I could find different methods to enter Flashmode on a MTK? I have had the rubber band on the volume down which was kept pressed for a whole night, with the Flashtool asking to connect the device in Flashmode, but nothing good happened. And the phone was connecting and disconnecting continuously (kind of bootloop, but without any obvious sign on the phone). Bootloop continues only if I have the rubber band on the volume down or on the power button. Otherwise, without a rubber band pressing the buttons, the phone just disconnects (even if it stays connected by USB).
I'm really lost: Should I keep charging the battery until it gives me any sign of life? Or should I leave it alone until it fully discharges??
Have you tried to repair it through Xperia Companion on PC?
Vector Edge said:
I understand that MTK is not Qualcomm, and there is a different approach when in comes to unbricking the phone. Could you, PLEASE, suggest me a source where I could find different methods to enter Flashmode on a MTK? I have had the rubber band on the volume down which was kept pressed for a whole night, with the Flashtool asking to connect the device in Flashmode, but nothing good happened. And the phone was connecting and disconnecting continuously (kind of bootloop, but without any obvious sign on the phone). Bootloop continues only if I have the rubber band on the volume down or on the power button. Otherwise, without a rubber band pressing the buttons, the phone just disconnects (even if it stays connected by USB).
I'm really lost: Should I keep charging the battery until it gives me any sign of life? Or should I leave it alone until it fully discharges??
Click to expand...
Click to collapse
If you tried all over a night your battery is probably full now.
Try an other way: unplug, hold vol+ vol- and power for 8-10sec (force shutdown), release all, hold vol- again and plug.
You can find guides all over the web, generally for other phones you can remove the battery...
NEVER USE MTK SP FLASHTOOL
Your phone can really have a hardware problem and need to be replaced/repaired, do this if you can. That's very strange if your bootloader is locked and you have this problem.
LuiGi_MM said:
Have you tried to repair it through Xperia Companion on PC?
Click to expand...
Click to collapse
I can not use the Xperia Companion method as I can not get into the Flashmode
rrvuhpg said:
If you tried all over a night your battery is probably full now.
Try an other way: unplug, hold vol+ vol- and power for 8-10sec (force shutdown), release all, hold vol- again and plug.
You can find guides all over the web, generally for other phones you can remove the battery...
NEVER USE MTK SP FLASHTOOL
Your phone can really have a hardware problem and need to be replaced/repaired, do this if you can. That's very strange if your bootloader is locked and you have this problem.
Click to expand...
Click to collapse
- Vol+ and Vol - did not force the shutdown.
- I literally read already thousands of post on xda, and I can not find what it takes to quit this bootloop
- Why should I never use MTK SP SLASHTOOL? Isn't it specialised for MediaTek ?
Vector Edge said:
- Yes, I have used the very last version of the Flashtool available on their website;
- I mentioned about the locked bootloader for the purpose of mentioning to not being able to use Fastboot;
- I used the SIMPLE mode of the Flashtool;
- I chose NO for the FSC script. Would THIS be the party pooper???
- I did not include the simlock.ta, as I using the SIMPLE Mode in the Flashtool, and as far as I know, it is excluded by default in the last version of the Flashtool.
- Right before this happened, I updated the same phone with the same PC and Flashtool to the xx.x.x.2.73 and everything went fine. And I also chose NO for the FSC script. But it flashed properly. BTW, what does this FSC do after all?
-The phone is not reacting to the button combinations, therefore i can not use the vol up + power, it never vibrates.
Thanks for your response anyway.
Click to expand...
Click to collapse
Something must of been done differently, I know if it asks for a fsc script you should choose yes(pretty sure this was part of the reason m5+c5 were hardbricking), I'm also pretty sure that only Sony service centre can ressurect it if it's not responding to anything. Best advice would be to take it to them.
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Something must of been done differently, I know if it asks for a fsc script you should choose yes(pretty sure this was part of the reason m5+c5 were hardbricking), I'm also pretty sure that only Sony service centre can ressurect it if it's not responding to anything. Best advice would be to take it to them.
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
When I installed the previous version of the firmware xxx.2.93 (just one hour before the fatal flash, when I wanted to flash the vershion xxx.3.74) on the same phone, on the same PC and with the same Flashtool, then I choose NO for the FSC file as well, and everything went good, and the phone booted afterwords with no problem!
Related
Xperia J Flash problem
First of all, if there's other threads that described my issue, forgive me because I probably didn't use the proper term. Anyway, I'm trying to get http://forum.xda-developers.com/xpe...y-bean-11-2-0-31-11-2-0-21-t2333078?nocache=1 to work, but my phone simply refuse to stay flashing. It detects the phone, execute the flash, and then nothing. Code: 13/049/2014 03:49:58 - INFO - Connected device : Sony Xperia J 13/049/2014 03:49:58 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary. 13/049/2014 03:49:59 - INFO - Android version : 4.1.2 / kernel version : 3.4.0 / Build number : 11.2.A.0.31 13/049/2014 03:49:59 - INFO - Checking root access 13/050/2014 03:50:00 - INFO - Root Access Allowed 13/050/2014 03:50:09 - INFO - Selected Bundle for ST26i. FW release : null. Customization : Aby uzywac CWM sflasuj to 13/050/2014 03:50:09 - INFO - Preparing files for flashing 13/050/2014 03:50:09 - INFO - Please connect your device into flashmode. 13/050/2014 03:50:13 - INFO - Device disconnected 13/050/2014 03:50:46 - INFO - Device connected in flash mode 13/050/2014 03:50:47 - INFO - Opening device for R/W 13/050/2014 03:50:47 - INFO - Reading device information 13/050/2014 03:50:47 - INFO - Phone ready for flashmode operations. 13/050/2014 03:50:47 - INFO - Current device : ST26i - YT910E9CU2 - 1266-7873_R2E - 1263-8752_11.2.A.0.31 - WORLD-i_11.2.A.0.31 13/050/2014 03:50:47 - INFO - Start Flashing 13/050/2014 03:50:47 - INFO - Processing loader.sin 13/050/2014 03:50:47 - INFO - Checking header 13/050/2014 03:50:47 - INFO - Flashing data 13/050/2014 03:50:47 - INFO - Processing of loader.sin finished. No error, no nothing. It just stops there. The green light on the phone lights up when I first connect it in flash mode, but it goes off when it flashtool starts flashing, thus ending everything there. Anybody know what's wrong and how to fix it? I've tried factory reset, changing usb ports and other menial troubleshooting, but at 4:43 A.M. I'm not sure how much more of troubleshooting I can do. *Update* If I were to unplug after the led died off, and plug it again (without pressing any buttons down), it automatically connected into flash mode instead of recharging.
First, is your bootloader locked? I ask this so i can sure your bootloader is locked. Second, if you flash anything using flashtool, always in the same result? :fingers-crossed:
I had a similar problem. All I had to do was to remove the micro SD card while flashing. Once you're done with flashing you can insert it again.
Vroyaloko said: First, is your bootloader locked? I ask this so i can sure your bootloader is locked. Second, if you flash anything using flashtool, always in the same result? :fingers-crossed: Click to expand... Click to collapse Yeah Bootloader is locked, and trying to flash anything will end with the same result. :c Pthn said: I had a similar problem. All I had to do was to remove the micro SD card while flashing. Once you're done with flashing you can insert it again. Click to expand... Click to collapse Oh, I will try that will post result after. *Update* It worked! Thanks. Sorry that took so long, was fiddling with it :l
[Q] Help, Stuck - Flashing Data (Flashtool)
13/032/2014 13:32:14 - INFO - Selected ST21i / 11.0.A.4.27 / Indian 13/032/2014 13:32:14 - INFO - Preparing files for flashing 13/032/2014 13:32:17 - INFO - Please connect your device into flashmode. 13/036/2014 13:36:49 - INFO - Device connected in flash mode 13/036/2014 13:36:50 - INFO - Opening device for R/W 13/036/2014 13:36:50 - INFO - Reading device information 13/036/2014 13:36:50 - INFO - Phone ready for flashmode operations. 13/036/2014 13:36:51 - INFO - Current device : Unknown: Jun 20 2012/22:39:46 - YT90033ZLS - Unknown: Jun 20 2012/22:39:46 - Unknown: Jun 20 2012/22:39:46 - Unknown: Jun 20 2012/22:39:46 13/036/2014 13:36:51 - INFO - Start Flashing 13/036/2014 13:36:51 - INFO - Processing loader 13/036/2014 13:36:51 - INFO - Checking header 13/036/2014 13:36:51 - INFO - Flashing data Everything goes fine till this step, then Green LED on phone indicationg Flashmode goes off, and the process is stuck. Any solution?
anirudhabrv said: 13/032/2014 13:32:14 - INFO - Selected ST21i / 11.0.A.4.27 / Indian 13/032/2014 13:32:14 - INFO - Preparing files for flashing 13/032/2014 13:32:17 - INFO - Please connect your device into flashmode. 13/036/2014 13:36:49 - INFO - Device connected in flash mode 13/036/2014 13:36:50 - INFO - Opening device for R/W 13/036/2014 13:36:50 - INFO - Reading device information 13/036/2014 13:36:50 - INFO - Phone ready for flashmode operations. 13/036/2014 13:36:51 - INFO - Current device : Unknown: Jun 20 2012/22:39:46 - YT90033ZLS - Unknown: Jun 20 2012/22:39:46 - Unknown: Jun 20 2012/22:39:46 - Unknown: Jun 20 2012/22:39:46 13/036/2014 13:36:51 - INFO - Start Flashing 13/036/2014 13:36:51 - INFO - Processing loader 13/036/2014 13:36:51 - INFO - Checking header 13/036/2014 13:36:51 - INFO - Flashing data Everything goes fine till this step, then Green LED on phone indicationg Flashmode goes off, and the process is stuck. Any solution? Click to expand... Click to collapse My suggestions: Reinstall required drivers on your PC with Sony PC companion. It is available on Sony 's official site approx size 27 mb. Are you able to boot the phone after incomplete flashing???
Anupam_Dey said: My suggestions: Reinstall required drivers on your PC with Sony PC companion. It is available on Sony 's official site approx size 27 mb. Are you able to boot the phone after incomplete flashing??? Click to expand... Click to collapse i am also stuck trying to reverse to stock from [LP][30-11-2014] Android 5.0 LolliPop for Xperia Z (KMA). The flashtool s stuck at checing header
aa.jazzz said: i am also stuck trying to reverse to stock from [LP][30-11-2014] Android 5.0 LolliPop for Xperia Z (KMA). The flashtool s stuck at checing header Click to expand... Click to collapse post log of flashtool as you did before
It is due to drivers If you are using Win 8 you need to install an update which supports Flashmode and fastboot drivers otherwise just restart your pc/laptop by using "Advance Reboot" option in settings And choose Disable Signature verification when pc/laptop boots into advance menu. This solved my problem. Hope yours is also solved. Use USB 2.0 port to flash. U cannot flash if you connect to USB 3.0.
still i am having the same problem help me it stucks at the flashing data some times it wont read my phone sometimes phone wont detect in flashmode
[Q] Xperia E microSD class 10?
Hi, I am going to buy a new microSD class 10 with 16gb, and I was wondering if our Xperia E is compatible with the class 10 feature. Thanks Regards ajesushn Sent from my C1505 using XDA Free mobile app
Yes.Mine is 8gb class 10.
ajesushn said: Hi, I am going to buy a new microSD class 10 with 16gb, and I was wondering if our Xperia E is compatible with the class 10 feature. Thanks Regards ajesushn Sent from my C1505 using XDA Free mobile app Click to expand... Click to collapse Yes, its better for the phone, Sent from my ST26i using XDA Free mobile app
bootloader problem hi my sony model : sony v 26/053/2018 15:53:03 - INFO - Max packet size set to 64K 26/053/2018 15:53:03 - INFO - Opening TA partition 2 26/053/2018 15:53:03 - INFO - Start Reading unit 00 00 08 B2 26/053/2018 15:53:03 - INFO - Reading TA finished. 26/053/2018 15:53:03 - INFO - Closing TA partition 26/053/2018 15:53:03 - INFO - Ending flash session 26/053/2018 15:53:04 - INFO - Your phone bootloader cannot be officially unlocked 26/053/2018 15:53:04 - INFO - You can now unplug and restart your phone 26/053/2018 15:53:04 - INFO - Device connected in flash mode 26/053/2018 15:53:05 - INFO - Device disconnected 26/053/2018 15:53:08 - INFO - Device connected in flash mode 26/053/2018 15:53:19 - INFO - Device disconnected 26/053/2018 15:53:24 - INFO - Device connected with USB debugging off 26/053/2018 15:53:24 - INFO - For 2011 devices line, be sure you are not in MTP mode i checked bootloader unlocked allowed : yes but > flash tool 26/053/2018 15:53:04 - INFO - Your phone bootloader cannot be officially unlocked
Xperia XA Bootloader open.
Hello Everybody! First thing, sorry my bad english.. I have a XA, but can't open bootloader, service info say: not allowed. I try kingoroot can't root, try SONY unlocker key, but ADB say: command not allowed. But OEM unlock enabled.. Have a method to open it? I love this phone, but i need root access.. Thanks in advance, have nice day!
EndlessGOD said: Hello Everybody! First thing, sorry my bad english.. I have a XA, but can't open bootloader, service info say: not allowed. I try kingoroot can't root, try SONY unlocker key, but ADB say: command not allowed. But OEM unlock enabled.. Have a method to open it? I love this phone, but i need root access.. Thanks in advance, have nice day! Click to expand... Click to collapse Here you are https://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3638727 You can unlock very easily your bootloader via Flashtool by cliking BLU icon
pa7taloha said: Here you are https://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3638727 You can unlock very easily your bootloader via Flashtool by cliking BLU icon Click to expand... Click to collapse Dude, i tell, DON'T WORKING SONY UNLOCK CODE, OEM unlock won't working .. COMMAND NOT ALLOWED .. You send a link, with first step: oem unlock .. how .. ?
EndlessGOD said: Dude, i tell, DON'T WORKING SONY UNLOCK CODE, OEM unlock won't working .. COMMAND NOT ALLOWED .. You send a link, with first step: oem unlock .. how .. ? Click to expand... Click to collapse 23/016/2017 18:16:37 - INFO - Flashtool Version 0.9.23.1 built on 11-01-2017 15:12:00 23/016/2017 18:16:37 - INFO - Executing search strategies to find proxy selector 23/016/2017 18:16:38 - INFO - No proxy found for IE. Trying next one 23/016/2017 18:16:38 - INFO - Strategy firefox failed trying next one : No Firefox installation found 23/016/2017 18:16:38 - INFO - No proxy found for java. Trying next one 23/016/2017 18:16:38 - INFO - Syncing devices from github 23/016/2017 18:16:39 - INFO - Opening devices repository. 23/016/2017 18:16:39 - INFO - Scanning devices folder for changes. 23/016/2017 18:16:57 - INFO - Pulling changes from github. 23/016/2017 18:16:58 - INFO - Quietly closing devices repository. 23/016/2017 18:16:58 - INFO - Devices sync finished. 23/016/2017 18:16:58 - INFO - Loading devices database 23/016/2017 18:16:58 - INFO - Loaded 98 devices 23/016/2017 18:16:58 - INFO - Starting phone detection 23/016/2017 18:16:59 - INFO - Device disconnected 23/017/2017 18:17:04 - INFO - Device connected with USB debugging off 23/017/2017 18:17:04 - INFO - For 2011 devices line, be sure you are not in MTP mode 23/017/2017 18:17:05 - INFO - Device disconnected 23/017/2017 18:17:08 - INFO - Device connected with USB debugging off 23/017/2017 18:17:08 - INFO - For 2011 devices line, be sure you are not in MTP mode 23/017/2017 18:17:58 - INFO - Device connected with USB debugging on 23/017/2017 18:17:58 - INFO - Connected device : Sony Xperia XA 23/017/2017 18:17:58 - INFO - Installed version of busybox : N/A 23/017/2017 18:17:58 - INFO - Android version : 6.0 / kernel version : 3.18.22+ / Platform : 64bits / Build number : 33.2.A.4.70 23/017/2017 18:17:58 - INFO - Root access denied 23/018/2017 18:18:02 - INFO - Please connect your device into flashmode. 23/018/2017 18:18:12 - INFO - Device disconnected 23/018/2017 18:18:49 - INFO - Device connected in flash mode 23/018/2017 18:18:49 - INFO - Opening device for R/W 23/018/2017 18:18:50 - INFO - Reading device information 23/018/2017 18:18:50 - INFO - Phone ready for flashmode operations. 23/018/2017 18:18:50 - INFO - Opening TA partition 2 23/018/2017 18:18:50 - INFO - Current device : F3111 - RQ3002V3XD - 1302-8031_R5A - 1300-9502_33.2.A.4.70 - GENERIC_33.2.A.4.70 23/018/2017 18:18:50 - INFO - Closing TA partition 23/018/2017 18:18:50 - INFO - No loader in the bundle. Searching for one 23/018/2017 18:18:50 - INFO - Processing loader.sin 23/018/2017 18:18:50 - INFO - Checking header 23/018/2017 18:18:50 - INFO - Flashing data 23/018/2017 18:18:50 - INFO - Loader : S1_Root_cf2a - Version : MT6755_12 / Boot version : S1_Boot_MT6755_M0.MP6_16 / Bootloader status : NOT_ROOTABLE 23/018/2017 18:18:50 - INFO - Max packet size set to 8M 23/018/2017 18:18:50 - INFO - Opening TA partition 2 23/018/2017 18:18:50 - INFO - Start Reading unit 00 00 08 B2 23/018/2017 18:18:50 - INFO - Reading TA finished. 23/018/2017 18:18:50 - INFO - Closing TA partition 23/018/2017 18:18:50 - INFO - Ending flash session 23/018/2017 18:18:51 - INFO - Your phone bootloader cannot be officially unlocked 23/018/2017 18:18:51 - INFO - You can now unplug and restart your phone 23/018/2017 18:18:51 - INFO - Device connected in flash mode 23/018/2017 18:18:51 - INFO - Device disconnected 23/018/2017 18:18:53 - INFO - Device connected in flash mode 23/019/2017 18:19:53 - INFO - Device disconnected 23/020/2017 18:20:04 - INFO - Device connected with USB debugging off 23/020/2017 18:20:04 - INFO - For 2011 devices line, be sure you are not in MTP mode 23/020/2017 18:20:07 - INFO - Device disconnected
Check whether you can unlock your bootloader or not by dialing *#*#7378423#*#* ->service info --> Configuration, check rooting status if it says bootloader unlock allowed: Yes, then you can unlock it. But you have mentioned that you are using XA, fortunately it should be Yes. Try to use flashtool 0.9.23.2, to pass from 0.9.23.1 to 0.9.23.2 you have to download x10flasher.jar and put this file in the folder named Flashtool. To unlock your bootloader, go to devellopper mod in your phone, tick USB debugging , and Oem unlock too. In lock screen and security tick unknown source. Then unlock it via flashtool.
EndlessGOD said: Dude, i tell, DON'T WORKING SONY UNLOCK CODE, OEM unlock won't working .. COMMAND NOT ALLOWED .. You send a link, with first step: oem unlock .. how .. ? Click to expand... Click to collapse pa7taloha said: Check whether you can unlock your bootloader or not by dialing *#*#7378423#*#* ->service info --> Configuration, check rooting status if it says bootloader unlock allowed: Yes, then you can unlock it. But you have mentioned that you are using XA, fortunately it should be Yes. Try to use flashtool 0.9.23.2, to pass from 0.9.23.1 to 0.9.23.2 you have to download x10flasher.jar and put this file in the folder named Flashtool. To unlock your bootloader, go to devellopper mod in your phone, tick USB debugging , and Oem unlock too. In lock screen and security tick unknown source. Then unlock it via flashtool. Click to expand... Click to collapse Bootloader unlock allowed: NO
EndlessGOD said: Bootloader unlock allowed: NO Click to expand... Click to collapse Try checking in developer mode. OEM unlocking -if it is in off mode turn it on.
Z3(D6633) In Bootloop, Don't Work Flash with Flashtool
Hello guys, I have an inconvenient problem, I was in Lineage OS15, but until unlock my bootloader I maked the TA Backup. Well, yersterday I restored my TA Backup and go back to the stock, my phone worked, Checked in service the keys menu, all is OK, so the restore worked ... The problem started when I started to install some applications and when I started the pokemon GO, my phone simply restarted, now is stuck in Black Sony Logo and restart and restart, and restart.... I Tryed flash the stock again but don't worked, I get the same result. Someone have an Idea? I still have Flashmode and FastRecovery Working Fine, PC Companion detect my phone tool, but the recovery proccess don't work too, when the flash finish I have the same result, reboot. The Flashtool Log is... 2/050/2018 21:50:03 - INFO - Selected Bundle for Sony Xperia Z3(D6633). FW release : 23.5.A.1.291_R5D. Customization : 1288-7359 12/050/2018 21:50:03 - INFO - Preparing files for flashing 12/050/2018 21:50:26 - INFO - Please connect your device into flashmode. 12/050/2018 21:50:30 - INFO - Opening device for R/W 12/050/2018 21:50:30 - INFO - Reading device information 12/050/2018 21:50:30 - INFO - Phone ready for flashmode operations. 12/050/2018 21:50:30 - INFO - Opening TA partition 2 12/050/2018 21:50:30 - INFO - Current device : D6633 - BY900F54UB - 1288-7359_R5D - 1286-4838_23.5.A.1.291 - GLOBAL-LTE_23.5.A.1.291 12/050/2018 21:50:30 - INFO - Closing TA partition 12/050/2018 21:50:30 - INFO - Start Flashing 12/050/2018 21:50:30 - INFO - Processing loader.sin 12/050/2018 21:50:30 - INFO - Checking header 12/050/2018 21:50:30 - INFO - Flashing data 12/050/2018 21:50:31 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AC_LA3.0_M_3 / Bootloader status : ROOTABLE 12/050/2018 21:50:31 - INFO - Max packet size set to 512K 12/050/2018 21:50:31 - INFO - USB buffer size set to 512K 12/050/2018 21:50:31 - INFO - Parsing boot delivery 12/050/2018 21:50:31 - INFO - No flash script found. Using 0.9.18 flash engine 12/050/2018 21:50:31 - INFO - Opening TA partition 2 12/050/2018 21:50:31 - INFO - Writing TA unit 00002774. Value : 01 12/050/2018 21:50:31 - INFO - Closing TA partition 12/050/2018 21:50:31 - INFO - Processing partition.sin 12/050/2018 21:50:31 - INFO - Checking header 12/050/2018 21:50:31 - INFO - Flashing data 12/050/2018 21:50:31 - INFO - Phone boot version : S1_Boot_MSM8974AC_LA3.0_M_3. Boot delivery version : S1_Boot_MSM8974AC_LA3.0-M-3 12/050/2018 21:50:31 - INFO - Going to flash boot delivery 12/050/2018 21:50:31 - INFO - Opening TA partition 2 12/050/2018 21:50:32 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin 12/050/2018 21:50:32 - INFO - Checking header 12/050/2018 21:50:32 - INFO - Flashing data 12/050/2018 21:50:32 - INFO - Closing TA partition 12/050/2018 21:50:32 - INFO - Opening TA partition 2 12/050/2018 21:50:32 - INFO - Flashing Leo-DSDS_S1BootConfig_MiscTA.ta to partition 2 12/050/2018 21:50:32 - INFO - Writing TA unit 0000084F. Value : 1A CE 1D 00 01 00 04 05 00 02 02 08 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 12 00 02 00 A9 09 BE BA A9 09 00 00 B3 08 BE BA B3 08 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01 03 00 09 00 01 12/050/2018 21:50:32 - INFO - Writing TA unit 000008FD. Value : 00 12/050/2018 21:50:32 - INFO - Closing TA partition 12/050/2018 21:50:32 - INFO - Opening TA partition 2 12/050/2018 21:50:32 - INFO - Processing rpm_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin 12/050/2018 21:50:32 - INFO - Checking header 12/050/2018 21:50:32 - INFO - Flashing data 12/050/2018 21:50:32 - INFO - Processing s1sbl_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin 12/050/2018 21:50:32 - INFO - Checking header 12/050/2018 21:50:32 - INFO - Flashing data 12/050/2018 21:50:33 - INFO - Processing sbl1_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin 12/050/2018 21:50:33 - INFO - Checking header 12/050/2018 21:50:33 - INFO - Flashing data 12/050/2018 21:50:33 - INFO - Processing tz_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin 12/050/2018 21:50:33 - INFO - Checking header 12/050/2018 21:50:33 - INFO - Flashing data 12/050/2018 21:50:33 - INFO - Processing dbi_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin 12/050/2018 21:50:33 - INFO - Checking header 12/050/2018 21:50:33 - INFO - Flashing data 12/050/2018 21:50:33 - INFO - Closing TA partition 12/050/2018 21:50:33 - INFO - Opening TA partition 2 12/050/2018 21:50:33 - INFO - Closing TA partition 12/050/2018 21:50:33 - INFO - Opening TA partition 2 12/050/2018 21:50:34 - INFO - Processing amss_fsg.sin 12/050/2018 21:50:34 - INFO - Checking header 12/050/2018 21:50:34 - INFO - Flashing data 12/050/2018 21:50:34 - INFO - Processing amss_fs_1.sin 12/050/2018 21:50:34 - INFO - Checking header 12/050/2018 21:50:34 - INFO - Flashing data 12/050/2018 21:50:34 - INFO - Processing amss_fs_2.sin 12/050/2018 21:50:34 - INFO - Checking header 12/050/2018 21:50:34 - INFO - Flashing data 12/050/2018 21:50:34 - INFO - Processing apps_log.sin 12/050/2018 21:50:34 - INFO - Checking header 12/050/2018 21:50:34 - INFO - Flashing data 12/050/2018 21:50:34 - INFO - Processing cache.sin 12/050/2018 21:50:34 - INFO - Checking header 12/050/2018 21:50:34 - INFO - Flashing data 12/050/2018 21:50:35 - INFO - Processing fotakernel.sin 12/050/2018 21:50:35 - INFO - Checking header 12/050/2018 21:50:35 - INFO - Flashing data 12/050/2018 21:50:37 - INFO - Processing kernel.sin 12/050/2018 21:50:37 - INFO - Checking header 12/050/2018 21:50:37 - INFO - Flashing data 12/050/2018 21:50:39 - INFO - Closing TA partition 12/050/2018 21:50:39 - INFO - Opening TA partition 2 12/050/2018 21:50:40 - INFO - Processing system.sin 12/050/2018 21:50:40 - INFO - Checking header 12/050/2018 21:50:40 - INFO - Flashing data 12/056/2018 21:56:14 - INFO - Processing userdata.sin 12/056/2018 21:56:14 - INFO - Checking header 12/056/2018 21:56:14 - INFO - Flashing data 12/056/2018 21:56:49 - INFO - Closing TA partition 12/056/2018 21:56:49 - INFO - Opening TA partition 2 12/056/2018 21:56:49 - INFO - Flashing auto-boot.ta to partition 2 12/056/2018 21:56:49 - INFO - Writing TA unit 00000907. Value : 00 12/056/2018 21:56:49 - INFO - Flashing fota-reset.ta to partition 2 12/056/2018 21:56:49 - INFO - Writing TA unit 00000964. Value : 00 12/056/2018 21:56:49 - INFO - Flashing osv-restriction.ta to partition 2 12/056/2018 21:56:49 - INFO - Writing TA unit 0000091A. Value : 00 12/056/2018 21:56:49 - INFO - Closing TA partition 12/056/2018 21:56:49 - INFO - Opening TA partition 2 12/056/2018 21:56:49 - INFO - Processing elabel.sin 12/056/2018 21:56:49 - INFO - Checking header 12/056/2018 21:56:50 - INFO - Flashing data 12/056/2018 21:56:52 - INFO - Closing TA partition 12/056/2018 21:56:52 - INFO - Opening TA partition 2 12/056/2018 21:56:52 - INFO - Writing TA unit 00002725. Value : 32 30 31 38 2D 30 31 2D 31 32 20 32 31 3A 35 36 3A 35 32 00 12/056/2018 21:56:52 - INFO - Writing TA unit 00002774. Value : 00 12/056/2018 21:56:52 - INFO - Closing TA partition 12/056/2018 21:56:52 - INFO - Ending flash session 12/056/2018 21:56:52 - INFO - Flashing finished. 12/056/2018 21:56:52 - INFO - Please unplug and start your phone 12/056/2018 21:56:52 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings 12/056/2018 21:56:54 - INFO - Device disconnected 12/056/2018 21:56:55 - INFO - Device connected in flash mode 12/057/2018 21:57:04 - INFO - Device disconnected 12/057/2018 21:57:12 - INFO - Device connected in flash mode 12/057/2018 21:57:23 - INFO - Device disconnected
Someone have an Idea about it? Flash work, but I stuck in the black sony logo with a Stock and Custom, I Try unlock my bootloader again same stuck in black logo, The unlock was reported with success in Fastboot but don't show the android screen after this. But the flash still working. I don't have no more Idea to recover my phone.
FallenSp said: Someone have an Idea about it? Flash work, but I stuck in the black sony logo with a Stock and Custom, I Try unlock my bootloader again same stuck in black logo, The unlock was reported with success in Fastboot but don't show the android screen after this. But the flash still working. I don't have no more Idea to recover my phone. Click to expand... Click to collapse Have you tryied with EMMA software from Sony? Restore it completely with that and should work.
Tux111 said: Have you tryied with EMMA software from Sony? Restore it completely with that and should work. Click to expand... Click to collapse I tryied with Flashtool and don't worked, my phone was with Lineage 15, I recovered my TA Backup, flashed a Stock and all was worked fine, but I don't restarted my phone. I was installing the applications when I test the Pokemon Go and my phone reset, after this entered in Bootloop, I can flash with flash tool normaly but don't work, still in Bootloop. I tryied unlock my Bootloader to go back to Lineage but don't worked too, success in ADB unlocking, but when I restart the phone not show the android flash after unlock bootloader. I used the Xperia Companion to restore my phone but don't worked, so I tryied unlock the bootloader, this is really strange. Have a way to I recovery my TA backup in Flashtool or Fastboot? If I Restore, I can lock my Bootloader again and try send to Sony to Repair, it will have a cost but is a solution...
FallenSp said: I tryied with Flashtool and don't worked, my phone was with Lineage 15, I recovered my TA Backup, flashed a Stock and all was worked fine, but I don't restarted my phone. I was installing the applications when I test the Pokemon Go and my phone reset, after this entered in Bootloop, I can flash with flash tool normaly but don't work, still in Bootloop. I tryied unlock my Bootloader to go back to Lineage but don't worked too, success in ADB unlocking, but when I restart the phone not show the android flash after unlock bootloader. I used the Xperia Companion to restore my phone but don't worked, so I tryied unlock the bootloader, this is really strange. Have a way to I recovery my TA backup in Flashtool or Fastboot? If I Restore, I can lock my Bootloader again and try send to Sony to Repair, it will have a cost but is a solution... Click to expand... Click to collapse Just try with EMMA software, don't need to send to Sony to repair.
Tux111 said: Just try with EMMA software, don't need to send to Sony to repair. Click to expand... Click to collapse It work with an Unlocked Bootloader? I unlocked to try recovery my phone. I have a Stock FTF, just flash normaly?
FallenSp said: It work with an Unlocked Bootloader? I unlocked to try recovery my phone. I have a Stock FTF, just flash normaly? Click to expand... Click to collapse Flash a Stock ROM to block bootloader (doesn't matter if it boot or not) and after use EMMA to restore stock firmware.
Tux111 said: Flash a Stock ROM to block bootloader (doesn't matter if it boot or not) and after use EMMA to restore stock firmware. Click to expand... Click to collapse Ok I ll try it, but... I tryied restore my phone with Xperia Companion Repair, It flash the stock again, but not worked with me, I ll try use EMMA to restore. But is very Strange, the flash work, only problem is this bootloop, In my old xperia, flash a stock rom solve the problem, but not is this case now.
Not so strange as you think. When you switch from stock to a modded Nougat or Oreo ROM , i think a part of the system is being upgraded and need some component not present in a common flashtool firmware to work again. Only EMMA for me fixed the problem everytime i want to come back to stock again.
I Tryied the Emma Tool, but don't work in a Dual Device, I receive the message No Available services matched the connected device It's strange, don't matter, I Flash, and Re-Flash and don't boot, I try a downgrade, the same stock rom, and nothing ._. A strange thing is, I Flashed the FTF 23.0.F.1.74 but always show me in Emma or other tool 23.5.A.1.291, The flash occur with success but not work.
Up... Someone have an Idea? I tryied downgrade, Xperia Companion Fix and other things, but don't boot, Reboot in the Sony Black Logo. If I put the cable with the phone Off, don't charge too, enter in bootloop, the charger proccess start after bootloader boot, how my phone have this problem, it enter in bootloop.
FallenSp said: Up... Someone have an Idea? I tryied downgrade, Xperia Companion Fix and other things, but don't boot, Reboot in the Sony Black Logo. If I put the cable with the phone Off, don't charge too, enter in bootloop, the charger proccess start after bootloader boot, how my phone have this problem, it enter in bootloop. Click to expand... Click to collapse Did you try flashing the stock rom using Flashtool? Sent from my Sony D6633 Dual using XDA Labs
thelegacy2010 said: Did you try flashing the stock rom using Flashtool? Sent from my Sony D6633 Dual using XDA Labs Click to expand... Click to collapse Yes, I was in Lineage OS 15, I restored my TA Backup and flashed a Stock rom, It worked fine but for an unknow reason my phone restarted alone and don't boot anymore, I try flash a Stock again but don't boot. I have Fastboot, Flashmode access normaly but if I flash, don't revive my phone, it is very strange.
Up. Phone yet is dead, I don't have more idea to try revive my phone.
up
Did you try flashing different firmware versions? The one you flashed might be corrupted. Try downloading a new fresh copy of the firmware and use flashtool to flash it. Don't connect the phone into flash mode before flashing. Once you select your firmware it's going to get built and then it will prompt to connect your phone.(Holding Volume Down + Power)
got same problem no fix yet, stuck on boot logo and andless bootloop cant boot to twrp but somehow can boot to fastboot
Dont work flash other version of Stock Rom, I tried flash other variant, Ukraine, Brazil, etc and don't worked, I stuck in the boot logo, but I have access to Fastboot, I can run commands, Flash work, but if I Flash a Stock, stay in the same version, it is like I don't make any flash, it's very strange. The Flash proccess end normaly, but don't change the variant, version, etc.
Friend happened to me the same as you, my Xperia D6633 also got stuck in the Sony logo. Try flashing with Flashtool 0.9.24.4 of Windows 7 several original TFTs and nothing did not Flash TFT and still had the same problem (stuck in the Sony logo stuck). Until you test with Flashtool 0.9.18.5 Windows 7 Flashee TFT original and the TLF revived, try Flashtool 0.9.18.5 Windows. Sorry for my English, I'm Spanish.: o:RE ---------- Post added at 01:20 AM ---------- Previous post was at 12:55 AM ---------- Try with Flashtool 0.9.18.5 Windows to me I fix my Xperia Z3 D6633 Friend happened to me the same as you, I also had the TLF stuck in the Sony logo. Try flashing several original TFTs with Flashtool 0.9.24.4 from Windows 7 and nothing did not Flash TFT and it was still locked into the Sony logo. Until I test with Flashtool 0.9.18.5 of Windows 7, I flashed the original TFT and the TLF revived. Uninstall Flashtool 0.9.24.4 from Windows, delete all your files, Flashtool folders from the C disk and Flashtool user folders. Install Flashtool version 0.9.18.5 and try installing a TFT. Sorry for my English, I'm Spanish.
No problem dude it's clear to me, well, I tryed, I receive an error in the flash process and my phone is dead, no more flash mode or fast boot, but your tip is correctly in my opnion, I tryed other things between this time and this maybe corrupted my phone, With the version mentioned appear worked a true flash process, thanks for your help, I think that the new version not work normaly, so if someone have the same problem, I recomend try the mentioned version of flashtool. EDITED​I access the flash mode again, flashed a old stock and finaly apear worked, Charging the phone, thanks a lot dude. EDITED​Bootloop, thanks dude, I try charging the phone but still in bootloop, I think that the phone is dead, bootloader corrupted, it's the only explanation.