Problem on flashing stock firmware using flashtool by androxyde. - Sony Xperia XA1 Questions & Answers

My phone sony xperia XA1 was working normally. At some day it powered off itself the device unexpectedly and when I try to power it on it doesn't turn on the device. When I try to charge it the red light glows but doesn't turn on the screen. So I tried to flash stock firmware using flashtool by androxyde. But the flash tool ends flashing after writing TA unit 2774 : 01 and skips rest of the flashing process. The detailed log is given below for your reference. Please help me to fix it. Also the phone is bootloader unlocked device. If you need further details please reply me. Sorry for the bad English.
INFO - Flashtool 0.9.34.0
INFO - Searching for a web proxy
INFO - No proxy found, using direct connection
INFO - Syncing devices from github
INFO - Opening devices repository.
INFO - Scanning devices folder for changes.
INFO - Pulling changes from github.
INFO - Devices sync finished.
INFO - Loading devices database
INFO - Loaded 131 devices
INFO - Starting phone detection
INFO - Device disconnected
INFO - Selected Bundle for Sony Xperia XA1(G3116). FW release : 40.0.A.3.7. Customization : Customized MY
INFO - Preparing files for flashing
INFO - Please connect your device into flashmode.
INFO - Using Gordon gate drivers version 3.1.0.0
INFO - Opening device for R/W
INFO - Device ready for R/W.
INFO - Reading device information
INFO - Phone ready for flashmode operations.
INFO - Opening TA partition 2
INFO - Current device : G3116 - RQ300534QJ - 1307-5208_R1B - 1306-2969_48.1.A.2.112 - GENERIC_48.1.A.2.112
INFO - Closing TA partition
INFO - Start Flashing
INFO - No loader in the bundle. Searching for one
INFO - No matching loader found
WARN - No loader found or set manually. Skipping loader
INFO - Loader : S1_Root_4a6c - Version : S1_Boot_MT6757_O0.MP103_207 / Boot version : S1_Boot_MT6757_O0.MP103_207 / Bootloader status : ROOTED
INFO - Max packet size set to 8M
INFO - USB buffer size set to 512K
INFO - Parsing boot delivery
INFO - Found a template session. Using it : C:\Users\santh\.flashTool\devices\G31XX\40.0.fsc
INFO - Set loader configuration : [00 01 00 00 00 0C]
INFO - Opening TA partition 2
INFO - Writing TA unit 00002774. Value : 01
INFO - Closing TA partition
INFO - Flashing finished.
INFO - Please unplug and start your phone
INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
INFO - Device disconnected
INFO - Device connected in flash mode

Related

Can't relock Bootloader!

I had aicp_amami_lp-10.0-RELEASE-20150707 on my phone so far, but because of some bugs and the missing sony-camera app I'd like to go back to stock sony. For that, so I can have a unmodified and completly up-to-date version of it, I wanted to use the sony companion-repair-thing which I used quite a lot of times by now. problem with it is that you need a locked bootloader for that which, so far, was no problem thanks to flashtool. but now, for absolutly no reason, my phone doesn't want to relock. I put some very old sony stock firmware on it and also have twrp, tried everything, debugging is on etc. but nope, when pressing the "relock" button, the next time I'm opening the bootloader thing on flashtool it still says "relock". no error message though, nothing. It just says
Code:
08/018/2015 02:18:30 - INFO - Device connected in flash mode
08/018/2015 02:18:33 - INFO - Please connect your device into flashmode.
08/018/2015 02:18:33 - INFO - Opening device for R/W
08/018/2015 02:18:33 - INFO - Reading device information
08/018/2015 02:18:33 - INFO - Phone ready for flashmode operations.
08/018/2015 02:18:33 - INFO - Opening TA partition 2
08/018/2015 02:18:33 - INFO - Current device : D5503 - CB5A21FFPV - 1279-4727_R5B - 1279-1792_14.2.A.1.114 - EURO-LTE_14.2.A.1.114
08/018/2015 02:18:33 - INFO - Closing TA partition
08/018/2015 02:18:33 - INFO - Processing loader.sin
08/018/2015 02:18:33 - INFO - Checking header
08/018/2015 02:18:33 - INFO - Flashing data
08/018/2015 02:18:34 - INFO - Loader : S1_Root_6732 - Version : MSM8974_23 / Boot version : S1_Boot_MSM8974_LA1.04_15 / Bootloader status : ROOTED
08/018/2015 02:18:34 - INFO - Max packet size set to 524288
08/018/2015 02:18:34 - INFO - Opening TA partition 2
08/018/2015 02:18:34 - INFO - Start Reading unit 000008B2
08/018/2015 02:18:34 - INFO - Reading TA finished.
08/018/2015 02:18:34 - INFO - Closing TA partition
08/018/2015 02:18:34 - INFO - Unlock code saved to C:\Users\Thomas\.flashTool\registeredDevices\CB5A21FFPV\ulcode.txt
08/018/2015 02:18:35 - INFO - Relocking device
08/018/2015 02:18:35 - INFO - Opening TA partition 2
08/018/2015 02:18:35 - INFO - Relock finished
08/018/2015 02:18:38 - INFO - Ending flash session
08/018/2015 02:18:38 - INFO - You can now unplug and restart your device
08/018/2015 02:18:39 - INFO - Device connected in flash mode
08/018/2015 02:18:39 - INFO - Device disconnected
after that it just says "relock" again and sony companion doesn't want to repair the device because of changed software which can't get updated (that means "lock you're bootloader or you can't repair it") but that excact thing always worked before, it just doesn't now, and I don't see why.
What's also weird about flashtool:
as you can see in the log above, I have the unlock-code saved in a "ulcode.txt" in the registered devices folder so the unlock-code is always already in the bootloader window. I wanted to try what happens when I delete that file and have to manually place the code in but when deleting the ulcode.txt it just comes back right when pressing the BLU button. How does that work and how can I get that away? It even comes back without internet connection, so it has to be saved in some different folder, right? But even reinstalling it and deleting all flashtool related folders didn't change it (could it be some kind of registry entry?).
I guess I got to stick to AICP until I have a solution for now.
Did you backup your DRM keys before unlocking? Restoring the DRM keys should also lock your bootloader.
If you haven't backed up you won't get full camera quality back:
http://forum.xda-developers.com/showthread.php?p=61501853&highlight=camera#post61501853
Yokurt815 said:
Did you backup your DRM keys before unlocking? Restoring the DRM keys should also lock your bootloader.
If you haven't backed up you won't get full camera quality back:
http://forum.xda-developers.com/showthread.php?p=61501853&highlight=camera#post61501853
Click to expand...
Click to collapse
No I didn't backup my DRM keys. But I wouldn't get how that can change the camera quality. That should only change on Hardware and on the App.
I haven't tried myself, but you read around here, that not are or were camera problems on Z1 compact if you haven't saved your TA partition.
You mentioned you have TWRP. Did you try with stock recovery?

Sony Xperia M (no sim in custom rom) cant get back to stock rom help

Hello people of xda,
Yesterday i decided to try out the world of custom ROM. I installed cm14 on my phone and everything is good except my phone doesnt recognize
my sim card. In other words, my phone is useless...
I tried to flash my phone back to my original firmware but flashtool gives this procces and aborts:
03/040/2017 12:40:32 - INFO - Flashtool Version 0.9.23.0 built on 21-12-2016 11:00:00
03/040/2017 12:40:32 - INFO - Executing search strategies to find proxy selector
03/040/2017 12:40:32 - INFO - No proxy found for IE. Trying next one
03/040/2017 12:40:32 - INFO - No proxy found for firefox. Trying next one
03/040/2017 12:40:32 - INFO - No proxy found for java. Trying next one
03/040/2017 12:40:32 - INFO - Syncing devices from github
03/040/2017 12:40:32 - INFO - Opening devices repository.
03/040/2017 12:40:32 - INFO - Scanning devices folder for changes.
03/040/2017 12:40:39 - INFO - Pulling changes from github.
03/040/2017 12:40:40 - INFO - Quietly closing devices repository.
03/040/2017 12:40:40 - INFO - Devices sync finished.
03/040/2017 12:40:40 - INFO - Loading devices database
03/040/2017 12:40:40 - INFO - Loaded 94 devices
03/040/2017 12:40:40 - INFO - Starting phone detection
03/040/2017 12:40:44 - INFO - Device disconnected
03/040/2017 12:40:59 - INFO - Selected Bundle for Sony Xperia M(C1904). FW release : 15.4.A.1.9. Customization : WORLD
03/040/2017 12:40:59 - INFO - Preparing files for flashing
03/041/2017 12:41:10 - INFO - Please connect your device into flashmode.
03/041/2017 12:41:34 - INFO - Device connected in flash mode
03/041/2017 12:41:34 - INFO - Opening device for R/W
03/041/2017 12:41:34 - INFO - Reading device information
03/041/2017 12:41:34 - INFO - Phone ready for flashmode operations.
03/041/2017 12:41:34 - INFO - Opening TA partition 2
03/041/2017 12:41:34 - INFO - Current device : Unknown: May 9 2014/12:58:25 - YT910TNW20 - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25
03/041/2017 12:41:34 - INFO - Closing TA partition
03/041/2017 12:41:34 - INFO - Start Flashing
03/041/2017 12:41:34 - INFO - Processing loader.sin
03/041/2017 12:41:34 - INFO - Checking header
03/041/2017 12:41:34 - INFO - Flashing data
03/041/2017 12:41:34 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
03/041/2017 12:41:34 - INFO - Max packet size set to 512K
03/041/2017 12:41:34 - INFO - USB buffer size set to 512K
03/041/2017 12:41:35 - INFO - Parsing boot delivery
03/041/2017 12:41:35 - INFO - Ending flash session
03/041/2017 12:41:35 - ERROR - null
03/041/2017 12:41:35 - ERROR - Error flashing. Aborted
03/041/2017 12:41:36 - INFO - Device connected in flash mode
03/041/2017 12:41:36 - INFO - Device disconnected
03/041/2017 12:41:39 - INFO - Device connected in flash mode
03/042/2017 12:42:39 - INFO - Device disconnected
03/042/2017 12:42:53 - INFO - Device connected with USB debugging off
03/042/2017 12:42:53 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/047/2017 12:47:42 - INFO - Device disconnected
03/058/2017 12:58:27 - INFO - Device connected with USB debugging off
03/058/2017 12:58:27 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/000/2017 13:00:19 - INFO - Device disconnected
I want to be able to go back to stock. Or if this is not possible atleast be able to use my simcard
Please help me
Hello welcome.
Did you try it more than 1 time? (no I'm not mocking you)
Do you have any other USB-Cables to try out with?
Could you try another USB-Port on the computer?
Did you install the Flashtool drivers for your Device?
Maybe you should try out the newest Build 0.9.23.2
@matthias.smet
Welcome to XDA!
Try again with v0.9.18.6, it is more stable but however you should not use the computer for any other purposes when flashtool is preparing the bundles for flasfing.
Hello there.
Im having the exact same problem and am getting crazy searching for a solution.
What i have done so far:
reinstalled flashtool
downgraded to 0.9.23.0
downgraded to 0.9.18.6
redownloaded the .ftf
downloaded another .ftf
tried different packet sizes
tried every usb cable i could find
yes i also rebooted several times, both phone and laptop
right now the device is unusable as i managed to install Resurrection Remix but it failed the gApps (for which i tried everything to fix too) and wifi/data isnt functional , which makes it more or less a brick. And its not even my phone :crying:
at the time of writing i am again reinstalling 0.9.18.6. Hopes are small but who knows.
any other suggestions? every help is highly appreciated.
greetings, enaecore
EDIT: unexpectedly the reinstall of 0.9.18.6 finally worked for me! device is up and running again. i dont understand this, because 0.9.23.1 worked several times before i messed up with RR but well, im lucky i can hand back the phone in a working state, even if its crap stock its better than a custom brick. going back to my reliable bacon and maku now. praised be the pure android experience^^

Stuck with Flashtool ( Sony Xperira T3 )

I was flashing my phone and i got stuck, this is the log.
16/037/2017 15:37:35 - INFO - <- This level is successfully initialized
16/037/2017 15:37:35 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
16/037/2017 15:37:35 - INFO - You can drag and drop ftf files here to start flashing them
16/037/2017 15:37:40 - INFO - Device disconnected
16/037/2017 15:37:43 - INFO - Selected D5103_18.1.A.2.25_RU.ftf
16/037/2017 15:37:43 - INFO - Preparing files for flashing
16/037/2017 15:37:52 - INFO - Please connect your device into flashmode.
16/037/2017 15:37:59 - INFO - Device connected in flash mode
16/037/2017 15:37:59 - INFO - Opening device for R/W
16/037/2017 15:37:59 - INFO - Reading device information
16/038/2017 15:38:00 - INFO - Phone ready for flashmode operations.
16/038/2017 15:38:00 - INFO - Current device : D5103 - YT9111EKE6 - 1285-3447_R7B - 1280-7649_18.1.A.2.25 - GLOBAL-LTE_18.1.A.2.25
16/038/2017 15:38:00 - INFO - Start Flashing
16/038/2017 15:38:00 - INFO - Processing loader
16/038/2017 15:38:00 - INFO - Checking header
16/038/2017 15:38:00 - INFO - Flashing data
And more info what i tried to do to fix it. I've changed cabel, reinstalled drivers, restarted pc (i cant restart phone cuz it will stuck at provider logo than i need to wait for battery to die),i tried with excluding kernel and not wiping data nor cache. I tried with 32 bit version and 64 bit version.
there is a reset button near the sim card on this device to restart

xa1 ultra bootlooped After i opened bootloader

I am pretty devastated by this. TLDR at bottom if you dont want story. I was using just fine for over a year and i finally wanted to root my phone with magisk. to do that i need to open bootloader so i went to sony page and do what they said. Eventualy i managed to succesfully open bootloader but my phone screen was black (with blue light its fastboot screen) so i couldn't flash magisk. I opened phone regularly and it opened as it was brand new(factor) after that i went to settings and opened usb debugging and i saw oem bootloader was open(checked with grey) on developer settings and i closed phone. After that Phone went Bootloop. I could only close it by Power + Vol Up ( after 2 vibrations it closes) And if i restart it again its on bootlooped again.. Power + Vol Down also goes for bootloop
I am pretty upset waiting for firmware to download so i can "try" to flash that to phone. Hope that works but if it doesnt ?
any idea why it went bootloop after opening bootloader?
tldr: after opening bootloader phone went bootloop. just like title
Flashing didn't work.
15/020/2019 01:20:59 - INFO - Selected Bundle for Sony Xperia XA1 Ultra(G3221). FW release : 42.0.A.3.30. Customization : Customized UK
15/020/2019 01:20:59 - INFO - Preparing files for flashing
15/022/2019 01:22:06 - INFO - Device connected in flash mode
15/022/2019 01:22:54 - INFO - Please connect your device into flashmode.
15/022/2019 01:22:55 - INFO - Using Gordon gate drivers version 3.2.0.0
15/022/2019 01:22:55 - INFO - Opening device for R/W
15/022/2019 01:22:55 - INFO - Device ready for R/W.
15/022/2019 01:22:55 - INFO - Reading device information
15/022/2019 01:22:55 - INFO - Phone ready for flashmode operations.
15/022/2019 01:22:55 - INFO - Opening TA partition 2
15/022/2019 01:22:55 - INFO - Current device : G3221 - RQ3006UD3V - 1309-2083_R1B - 1306-6285_48.1.A.2.109 - GENERIC_48.1.A.2.109
15/022/2019 01:22:55 - INFO - Closing TA partition
15/022/2019 01:22:55 - INFO - Start Flashing
15/022/2019 01:22:55 - INFO - No loader in the bundle. Searching for one
15/022/2019 01:22:55 - INFO - No matching loader found
15/022/2019 01:22:55 - WARN - No loader found or set manually. Skipping loader
15/022/2019 01:22:55 - INFO - Loader : S1_Root_4a6c - Version : S1_Boot_MT6757_O0.MP103_207 / Boot version : S1_Boot_MT6757_O0.MP103_207 / Bootloader status : ROOTED
15/022/2019 01:22:55 - INFO - Max packet size set to 8M
15/022/2019 01:22:55 - INFO - USB buffer size set to 512K
15/023/2019 01:23:00 - INFO - Parsing boot delivery
15/023/2019 01:23:00 - INFO - No flash script found.
15/023/2019 01:23:00 - INFO - Flash script is mandatory. Closing session
15/023/2019 01:23:00 - INFO - Ending flash session
15/023/2019 01:23:00 - INFO - Flashing finished.
15/023/2019 01:23:00 - INFO - Please unplug and start your phone
15/023/2019 01:23:00 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
15/023/2019 01:23:01 - INFO - Device connected in flash mode
15/023/2019 01:23:14 - INFO - Device disconnected
it takes like 2 min max and its over. I tried to open phone but it same
After i used Sony's Emma it's fixed. I could open my phone regularly And Bootloader still open

HELP Stuck at Opening device for R/W

So I have my old Sony Xperia S lying around and I was thinking that I wanna still have a custom ROM, a custom recovery, and root. But my phone is pretty much bricked from the other attempts so I'm trying to flash the firmware again. But when I did the flashmode button it started flashing with my downloaded firmware for the LT26i. This is what it shows:
30/052/2022 09:52:44 - INFO - Flashtool 0.9.34.0
30/052/2022 09:52:44 - INFO - Searching for a web proxy
30/052/2022 09:52:45 - INFO - A proxy has been found. Using it as default
30/052/2022 09:52:45 - INFO - Syncing devices from github
30/052/2022 09:52:45 - INFO - Opening devices repository.
30/052/2022 09:52:45 - INFO - Scanning devices folder for changes.
30/052/2022 09:52:53 - INFO - Pulling changes from github.
30/052/2022 09:52:55 - INFO - Devices sync finished.
30/052/2022 09:52:57 - INFO - Loading devices database
30/052/2022 09:52:57 - INFO - Loaded 131 devices
30/052/2022 09:52:57 - INFO - Starting phone detection
30/053/2022 09:53:01 - INFO - Device connected in flash mode
30/053/2022 09:53:14 - INFO - Flash canceled
30/053/2022 09:53:16 - INFO - Please connect your device into flashmode.
30/053/2022 09:53:17 - INFO - Using Gordon gate drivers version 3.2.0.0
30/053/2022 09:53:17 - INFO - Opening device for R/W
30/053/2022 09:53:17 - INFO - Device ready for R/W.
30/053/2022 09:53:17 - INFO - Reading device information
30/053/2022 09:53:22 - INFO - Flash canceled
30/053/2022 09:53:36 - INFO - Selected Bundle for Sony Xperia S(LT26i). FW release : 6.2.B.0.211.1257-8080. Customization : LIB
30/053/2022 09:53:36 - INFO - Preparing files for flashing
30/053/2022 09:53:43 - INFO - Please connect your device into flashmode.
30/053/2022 09:53:44 - INFO - Using Gordon gate drivers version 3.2.0.0
30/053/2022 09:53:44 - INFO - Opening device for R/W
30/053/2022 09:53:45 - INFO - Device connected in flash mode
EDIT: got it fixed by turning off the verification on misc.
please how i can solve it i have the same problem

Categories

Resources