I am going to downgrade my X Perf from N to MM to do a TA backup and then upgrade again, but I have reached a rather annoying snag and I don't know if I'm doing something wrong. I am using Flashtool version 0.9.23.0, so it should work with the phone, but I still have to choose the phone every time, it doesn't read it from the bundle. And every attempt on the 4-5 ROMs I've tried so far gives me the error messages:
Code:
26/022/2016 09:22:46 - INFO - No loader in the bundle. Searching for one
26/022/2016 09:22:53 - INFO - No matching loader found
26/022/2016 09:22:53 - WARN - No loader found or set manually. Skipping loader
26/022/2016 09:22:53 - INFO - Ending flash session
26/022/2016 09:22:53 - ERROR - null
26/022/2016 09:22:53 - ERROR - Error flashing. Aborted
From what I can find out the problem is that there is no loader.sin in the firmwares I download. So far there hasn't been one in any of them! I have tried downloading on two different computers, and the same result all the time. Can anybody please tell me what I am doing wrong here? Or if the loader.sin is supposed to be taken from somewhere else. I haven't found anything about that in any of the "how to" threads I've seen.
same problem here..
First of all ensure Flashtool's drivers are properly installed on your system (windows 8/8.1/10 video guide)!
Also, you can try using an older version of Flashtool (0.9.18.6) to flash MM ftf. And ofc the new one for N.
The loader.sin is not part of ftf anymore, see MM and N ftf contents I've created and flashed successfully:
Serajr, thanks! I will make another attempt. And I have read your posts too, but didn't find a solution to this. Does this mean that Flashtool has to read the loader from the phone it's flashing, then?
Mastiff said:
Serajr, thanks! I will make another attempt. And I have read your posts too, but didn't find a solution to this. Does this mean that Flashtool has to read the loader from the phone it's flashing, then?
Click to expand...
Click to collapse
Exactly, that's why drivers must be properly installed!
And just in case...
If you want a recovery too, go for this one (multirom-20161218-recovery-fota-dora.zip). It is weird, but official twrp for dora does not work!!
To flash it, unpack the zip and flash its image with this fastboot command (just after you unlock your device's bootloader):
fastboot flash recovery twrp.img (after OK messages, unplug usb cable to turn device off).
Now you must enter on recovery (mandatory, otherwise you will need to flash twrp again), to do that: press Power and Volume Down buttons simultaneously, and release only the Power buttom when sony logo appears.
While on recovery ignore/disable any multirom function (unless you want it).
Well, I got one step further! I had misunderstood about the drivers, I thought it refered to the same driver as the ADB driver... But now I got to this:
26/033/2016 14:33:16 - WARN - No loader found or set manually. Skipping loader
26/033/2016 14:33:16 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : ROOTABLE
26/033/2016 14:33:16 - INFO - Max packet size set to 4M
26/033/2016 14:33:16 - INFO - USB buffer size set to 512K
26/033/2016 14:33:17 - INFO - Parsing boot delivery
26/033/2016 14:33:30 - INFO - No flash script found.
26/033/2016 14:33:30 - INFO - Flash script is mandatory. Closing session
26/033/2016 14:33:30 - INFO - Ending flash session
26/033/2016 14:33:30 - INFO - Flashing finished.
26/033/2016 14:33:30 - INFO - Please unplug and start your phone
26/033/2016 14:33:30 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
26/033/2016 14:33:30 - INFO - Device connected in flash mode
26/033/2016 14:33:48 - INFO - Device disconnected
Click to expand...
Click to collapse
I did choose not to use an FSC script as you said, but does that have anything to do with the reason for this failure, or is there something else going on here?
Edit: I'm still trying to downgrade to MM so I can backup the TA. I selected to wipe everything except the TA, and I excluded the TA, which I understood that I should do. Is there something I should have done while converting the file?
Mastiff said:
Well, I got one step further! I had misunderstood about the drivers, I thought it refered to the same driver as the ADB driver... But now I got to this:
I did choose not to use an FSC script as you said, but does that have anything to do with the reason for this failure, or is there something else going on here?
Edit: I'm still trying to downgrade to MM so I can backup the TA. I selected to wipe everything except the TA, and I excluded the TA, which I understood that I should do. Is there something I should have done while converting the file?
Click to expand...
Click to collapse
Did you do this?
Code:
26/033/2016 14:33:30 - INFO - For flashtool, [B][U]Unknown Sources[/U][/B] and [U][B]Debugging[/B][/U] must be checked in phone settings
Yep. I started the phone and checked that it was done after that fail, and both were set to on. Some of the first things I do on a phone, Titanium backup needs those settings to work. Of course it also needs root, which I do not yet have...
Edit: It is USB debugging that it means, right? Under Developer options?
I tried to start the phone again and authorize the pc for USB debugging (never had to do that before on any phone), but it didn't change anything.
Yep, it is!
Well buddy, things are starting to become tough. Try this:
- Turn your device off and keep it disconnected from usb
- Open Flashtool and start the MM flash process (choose firmware, etc...)
- Click on flash button. The message to connect your device in flash mode will pop up
- Now connect your phone to the usb while pressing Volume Down button (and do release it after flash process begins)
Ofc I can also being forgetting something, so please, anybody else reading to this thread, comment on!
Edit: On ftf creation I've also ignored FSC script! Did you?
Edit 2: Let windows recognizes your device into flashmode. With Flashtool closed (and others windows apps too), also with your device turned off, connect it to the usb with Volume Down (flashmode) button pressed. Is everything ok, did windows recognize it?
Do the same after you unlock the bootloader, with Volume Up (fastboot), and type in a windows command prompt: fastboot devices
Well, I installed the drivers again, just to test. But one thing: I only found the common drivers, and not a driver that worked specifically for the X Performance. Can that be the problem? I thought it would be in this version of Sony Mobile Flasher. Also I see a few errors in device manager. It's named "SOMC Flash Device", but under the Information part I see:
Device USB\VID_0FCE&PID_ADDE\5&2c705bfe&0&1 could not be migrated.
Click to expand...
Click to collapse
So is this still a driver issue? I looked through the list in the drivers installation program, but didn't see any driver for this phone. So I only get two drivers, the Google Inc. Win USB and Sony Mobile Communications ggsomc. I am probably missing something, right?
Edit: Not sure if I skipped the FSC script, but I'm making a new bundle now and will try with that to see if I may have forgotten to skip it on creation this last time.
Nope, new bundle didn't help. Also I found an old howto that said;
NOTE: If your list of files includes “fwinfo.xml” as highlighted below then manually delete it before continuing to the FlashTool steps. You MUST delete this file otherwise your FTF firmware file will corrupt.
Click to expand...
Click to collapse
But that was from 2014, so I do assume that this has been fixed.
And to continue the stream of info, this is not the firmware, it seems. I tried with a different firmware (Nougat for Nordic Countries) and it went just like with the Polish Marshmallow.
I have an idea for a last attempt: I will reset the phone to factory, do a very quick setup to where I get USB debugging and unknown sources and then try again.
Ok, download this one from sony and unpack it.
Now add hardware manually and point to the *.inf file (there should be at least 3 options to install).
Edit: "Device USB\VID_0FCE&PID_ADDE\5&2c705bfe&0&1 could not be migrated." << I have this too, and everything works!
Thanks! But I get a message that there are no drivers compatible with Windows 64 in that file. Weird, because it actually says that it does on that page. Maybe it just isn't compatible with Windows 10, I will try it on a Windows 7 computer I have here.
Nope, same error from both flash attempts and the driver file when using Windows 7. I do not have a Windows 7 32 bit device anywhere near, I'm afraid.
Mastiff said:
Thanks! But I get a message that there are no drivers compatible with Windows 64 in that file. Weird, because it actually says that it does on that page. Maybe it just isn't compatible with Windows 10, I will try it on a Windows 7 computer I have here.
Click to expand...
Click to collapse
This is the inf file and all x64 (and 32) contents from my android sdk folder. Try pointing to this one!
This is very strange, if those drivers worked on your system. Still the same thing, no compatible driver, check that any drivers in the directory are made for Windows 64 bit systems (roughly translated from Norwegian). But it is the SOMC Flash Device that I should use this driver on, right? In that case I have no idea why that's happening here.
Mastiff said:
This is very strange, if those drivers worked on your system. Still the same thing, no compatible driver, check that any drivers in the directory are made for Windows 64 bit systems (roughly translated from Norwegian). But it is the SOMC Flash Device that I should use this driver on, right? In that case I have no idea why that's happening here.
Click to expand...
Click to collapse
It is weird indeed! I think so, and I really don't remenber the right one, maybe Android Composite ADB interface.
Windows 7 things are much easier, but it must work on 10 as well! Hope you succeed!!
Edit: For further info to unlock device's bootloader > https://www.youtube.com/watch?v=iIdJg7KNH3A
Related
The instant I enter flashmode the flash fails. Here is my log:
Code:
29/032/2014 09:32:24 - INFO - <- This level is successfully initialized
29/032/2014 09:32:24 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
29/032/2014 09:32:28 - INFO - Device connected with USB debugging on
29/032/2014 09:32:29 - INFO - Connected device : Sony Xperia T
29/032/2014 09:32:29 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
29/032/2014 09:32:29 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-g5b052b2-00814-g976ab37 / Build number : 9.1.A.1.141
29/032/2014 09:32:29 - INFO - Checking root access
29/032/2014 09:32:30 - INFO - Root Access Allowed
29/033/2014 09:33:49 - INFO - Selected Bundle for LT30p. FW release : 9.2.A.1.199. Customization : Generic UK
29/033/2014 09:33:49 - INFO - Preparing files for flashing
29/033/2014 09:33:54 - INFO - Please connect your device into flashmode.
29/034/2014 09:34:03 - INFO - Device disconnected
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:04 - INFO - Opening device for R/W
29/035/2014 09:35:04 - INFO - Start Flashing
29/035/2014 09:35:04 - INFO - Processing loader.sin
29/035/2014 09:35:04 - INFO - Checking header
29/035/2014 09:35:04 - INFO - Ending flash session
29/035/2014 09:35:04 - ERROR -
29/035/2014 09:35:04 - ERROR - Error flashing. Aborted
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:15 - INFO - Device disconnected
Any ideas what could be wrong or what I can do?
Thanks
Edit: I tried uninstalling the phone from Device Manager, but that had no effect. When the flash fails I see a popup in the corner saying this device malfunctioned/is not recognized.
Astralogic said:
The instant I enter flashmode the flash fails. Here is my log:
Code:
29/032/2014 09:32:24 - INFO - <- This level is successfully initialized
29/032/2014 09:32:24 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
29/032/2014 09:32:28 - INFO - Device connected with USB debugging on
29/032/2014 09:32:29 - INFO - Connected device : Sony Xperia T
29/032/2014 09:32:29 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
29/032/2014 09:32:29 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-g5b052b2-00814-g976ab37 / Build number : 9.1.A.1.141
29/032/2014 09:32:29 - INFO - Checking root access
29/032/2014 09:32:30 - INFO - Root Access Allowed
29/033/2014 09:33:49 - INFO - Selected Bundle for LT30p. FW release : 9.2.A.1.199. Customization : Generic UK
29/033/2014 09:33:49 - INFO - Preparing files for flashing
29/033/2014 09:33:54 - INFO - Please connect your device into flashmode.
29/034/2014 09:34:03 - INFO - Device disconnected
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:04 - INFO - Opening device for R/W
29/035/2014 09:35:04 - INFO - Start Flashing
29/035/2014 09:35:04 - INFO - Processing loader.sin
29/035/2014 09:35:04 - INFO - Checking header
29/035/2014 09:35:04 - INFO - Ending flash session
29/035/2014 09:35:04 - ERROR -
29/035/2014 09:35:04 - ERROR - Error flashing. Aborted
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:15 - INFO - Device disconnected
Any ideas what could be wrong or what I can do?
Thanks
Edit: I tried uninstalling the phone from Device Manager, but that had no effect. When the flash fails I see a popup in the corner saying this device malfunctioned/is not recognized.
Click to expand...
Click to collapse
1.- Are you sure you have the right FTF for your phone model?
2.- Are you sure the FTF file isn't corrupted? (download again)
3.- Are you sure the proper drivers are installed (install them from the "drivers" folder in the Flashtool folder).
4.- Are you sure your USB cable isn't damaged and is disconnecting while flashing (try a different cable).
I think I've read that excluding the TA partition and/or BASEBAND might help. Don't take my word for it, Google it first.
Antiga Prime said:
1.- Are you sure you have the right FTF for your phone model?
2.- Are you sure the FTF file isn't corrupted? (download again)
3.- Are you sure the proper drivers are installed (install them from the "drivers" folder in the Flashtool folder).
4.- Are you sure your USB cable isn't damaged and is disconnecting while flashing (try a different cable).
I think I've read that excluding the TA partition and/or BASEBAND might help. Don't take my word for it, Google it first.
Click to expand...
Click to collapse
1 - I have an Xperia T and this is the FTF I 'm trying to flash.
2 - Yes, I have re-downloaded from a mirror.
3 - That installer doesn't include drivers in it's list for Xperia T, the Xperia TX drivers failed to install, I tried them to see if they would work.
Edit: In flashtool, exclude baseband is clearly labelled, but exclude TA partition is not. I can exclude "partition", is that it? Or could it be the "FOTA" option?
4 - The cable isn't causing the problem. Tried another.
I have no idea how excluding the TA partition and/or the baseband. I'll read up about it and see if it helps.
I even used the full unroot option in SuperSU, just so I could try to update the official way but it still didn't work.
Astralogic said:
3 - That installer doesn't include drivers in it's list for Xperia T, the Xperia TX drivers failed to install, I tried them to see if they would work.
Edit: In flashtool, exclude baseband is clearly labelled, but exclude TA partition is not. I can exclude "partition", is that it? Or could it be the "FOTA" option?
4 - The cable isn't causing the problem. Tried another.
Click to expand...
Click to collapse
No, if you don't see the exclude TA, then the FTF doesn't have the "simlock.ta" file in it.
You should use the TX drivers. If you haven't installed drivers at all, then that is clearly an issue. You could try with this driver pack, but the drivers that come with Flashtool should work.
What error do you get when installing the drivers?
Antiga Prime said:
No, if you don't see the exclude TA, then the FTF doesn't have the "simlock.ta" file in it.
You should use the TX drivers. If you haven't installed drivers at all, then that is clearly an issue. You could try with this driver pack, but the drivers that come with Flashtool should work.
What error do you get when installing the drivers?
Click to expand...
Click to collapse
Here's a screenshot of the error.
But when I attempt to install the drivers you linked to above, the top driver (Sony(WinUSB), above Sony Net) in the Device Driver Installation Wizard window has a green tick next to it. The bottom one, Sony Net, still has a red X next to it.
Astralogic said:
Here's a screenshot of the error.
But when I attempt to install the drivers you linked to above, the top driver (Sony(WinUSB), above Sony Net) in the Device Driver Installation Wizard window has a green tick next to it. The bottom one, Sony Net, still has a red X next to it.
Click to expand...
Click to collapse
Correct me if I'm wrong, but it seems like you're using Windows 8. You need to disable driver signature enforcement, either by doing this, or Googling another method (there are several).
Notice that drivers have been extracted to the temp folder (check your screenshot); I'd copy that driver folder to somewhere else, just to have it on hand, and that way it's easier to install the drivers manually through the Windows Device Manager, something you'd need to do after disabling the driver signing, and something I'd do anyways regardless if you're on Windows 8 or not; if drivers don't come with a specific software (such as Nvidia or ATI drivers) then it's always possible and in some cases easier to just add the driver manually through the Device Manager.
Antiga Prime said:
Correct me if I'm wrong, but it seems like you're using Windows 8. You need to disable driver signature enforcement, either by doing this, or Googling another method (there are several).
Notice that drivers have been extracted to the temp folder (check your screenshot); I'd copy that driver folder to somewhere else, just to have it on hand, and that way it's easier to install the drivers manually through the Windows Device Manager, something you'd need to do after disabling the driver signing, and something I'd do anyways regardless if you're on Windows 8 or not; if drivers don't come with a specific software (such as Nvidia or ATI drivers) then it's always possible and in some cases easier to just add the driver manually through the Device Manager.
Click to expand...
Click to collapse
I got the drivers installed succesfully by disabling driver signature verification and running the installer, but I still get the same error in flashtool. I really thought that was going to fix it.
Astralogic said:
I got the drivers installed succesfully by disabling driver signature verification and running the installer, but I still get the same error in flashtool. I really thought that was going to fix it.
Click to expand...
Click to collapse
Open the Device Manager and check if you have any devices with a yellow exclamation mark/warning. Aside from that, try a computer with Windows 7, maybe?
If not, and considering that you get a "this device has malfunctioned" error in Windows, and it's not your USB cable, then your USB port on either your phone or computer might not be working properly.
Antiga Prime said:
Open the Device Manager and check if you have any devices with a yellow exclamation mark/warning. Aside from that, try a computer with Windows 7, maybe?
If not, and considering that you get a "this device has malfunctioned" error in Windows, and it's not your USB cable, then your USB port on either your phone or computer might not be working properly.
Click to expand...
Click to collapse
The bad news is it didn't work
The good news is I got more info this time
Take a look at this screenshot, it's definitely some time of driver issue, something called S1boot fails to install: Screenshot.
That is AFTER the successful installation of the TX drivers in the drivers folder, these errors occur the instant my phone enters flashmode.
Edit: Forgot to mention this was on another PC, running Windows 7.
Edit 2: Just to clarify, the instant my phone entered flashmode, the computer tried to install those drivers.
Edit 3: I found this, I'm about to try it. Fingers crossed.
Edit 4: Those drivers didn't work. In Windows 8, I right click the INF and it installs, but no success on the flash. In Windows 7 I get a message that this INF does not support this method of installation. There are no devices with a yellow exclamation in device manager on either computer ;(
OK I managed to update the firmware using Sony Update Server program, now I constantly get the message android.process.media has stopped working. I tried to use an app called Rescan Media Root to disable the media scanner but it didn't work. The message is relentless, the phone is unusable because of this damn message
Maybe it's occurring because I disabled some system app or something?
Astralogic said:
OK I managed to update the firmware using Sony Update Server program, now I constantly get the message android.process.media has stopped working. I tried to use an app called Rescan Media Root to disable the media scanner but it didn't work. The message is relentless, the phone is unusable because of this damn message
Maybe it's occurring because I disabled some system app or something?
Click to expand...
Click to collapse
Most likely you didn't wipe data, A.K.A. Factory Reset.
Antiga Prime said:
Most likely you didn't wipe data, A.K.A. Factory Reset.
Click to expand...
Click to collapse
You're right. But I fixed it by clearing the data for Download Manager and Media Manager (or something like that).
hello, i want to use the flashtool but it keep asking to plug in the phone. i turned it off, and press volume down while connecting already.
avila188 said:
hello, i want to use the flashtool but it keep asking to plug in the phone. i turned it off, and press volume down while connecting already.
Click to expand...
Click to collapse
Sounds like you may need to install the flashtool-specific drivers. In your flashtool directory, there should be a "drivers" folder where you can install the flashtool (and fastboot)-specific drivers. I don't know if you need to have the latest version of flashtool (since this phone is still kind of new) to get a more appropriate driver set.
Also if you are installing these drivers in Windows 8 & up, you will likely have to install them while Driver Signature Enforcement (or whatever its called) is disabled. That method can be found easily via google search.
ok i installed the driver from the drivers folder. plugged the phone, recoqnised, but write up the following error:
20/030/2015 07:30:31 - ERROR - Processing of loader.sin finished with errors.
20/030/2015 07:30:31 - INFO - Ending flash session
20/030/2015 07:30:31 - ERROR -
20/030/2015 07:30:31 - ERROR - Error flashing. Aborted
20/030/2015 07:30:31 - INFO - Device connected in flash mode
avila188 said:
ok i installed the driver from the drivers folder. plugged the phone, recoqnised, but write up the following error:
20/030/2015 07:30:31 - ERROR - Processing of loader.sin finished with errors.
20/030/2015 07:30:31 - INFO - Ending flash session
20/030/2015 07:30:31 - ERROR -
20/030/2015 07:30:31 - ERROR - Error flashing. Aborted
20/030/2015 07:30:31 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
ok i installed all drivers, and it works.
now i flashed already and got the latest build, and my telstra apps are all gone! woohoo! i suppose now my phone is like unlocked and sony version ( no carrier)?
thanks to the uploader at
[FTF] STOCK FIRMWARES for D5803 & D5833
one thing tho, when i want to delete app shortcut, the x location is now at the top, not at the bottom on the apps shortcut. is this what you all have?
Processing step by step the official Unlock your boot loader fpr sony xperia z3 compact D5803_ 23.5.A.0.570 developer.sonymobile.com/unlockbootloader
1. Installation of SDK, Studio, Eclipse. Downloaded the Google USB Driver Package und replaced the original android_winusb.inf by the sony fastboot driver android_winusb.inf like required in C:\Users\AppData\Local\Android\sdk\extras\google\usb_driver
2. Connected z3c offline to pc and press up button
3. Device manager starts and shows S1 Fastboot
4. Update driver by path C:\Users\AppData\Local\Android\sdk\extras\google\usb_driver
5. Installation of the official fastboot driver fails because missing hash value in the driver android_winusb.inf .
Do you have same experience or advice ?
This procedure looks a bit strange and unneeded..
To keep it bit more simple just use "Flashtool" http://www.flashtool.net/downloads.php
And use its integrated driver installation feature to install Fastboot and Flashmode Drivers AND your Device Drivers (Note that you need to pick Z3C for sure)..
http://www.android-hilfe.de/attachm...a-driver-pack-v1-8-20141101-setup-png.419663/
http://www.android-hilfe.de/attachm...a-driver-pack-v1-8-20141101-setup-png.419664/
But before you start... Save your TA Partition!!!!
fluffi444 said:
But before you start... Save your TA Partition!!!!
Click to expand...
Click to collapse
+1
The threads are full of people saying they don't have the DRM keys to make their camera and extra functions work again.
Follow the guide here
Hi all i tried to flash my XZ2 with flashtool and i downloaded the latest ROM from Xperifirm. I created FTF file from the ROM i downloaded by unchecking .TA files. I have unlocked bootloader with cmd (which means all the drivers must be installed properly). But it didnt show neither errors nor succeeding in flashing the ROM. When i exited flash boot mode, my phone still can be turned on normally.
In before, i softbricked my phone but managed to reflash it with EMMA, but not satisfied because it's android 8. Anyone please help me, what steps i missed here? Im super noob in this kind of stuff, so please explain it easily for me. Thank u!
14/037/2020 00:37:07 - INFO - Flashtool 0.9.31.0
14/037/2020 00:37:07 - INFO - Searching for a web proxy
14/037/2020 00:37:09 - INFO - No proxy found, using direct connection
14/037/2020 00:37:09 - INFO - Syncing devices from github
14/037/2020 00:37:09 - INFO - Opening devices repository.
14/037/2020 00:37:09 - INFO - Scanning devices folder for changes.
14/037/2020 00:37:23 - INFO - Changes have been found. Doing a hard reset (removing user modifications).
14/037/2020 00:37:25 - INFO - Quietly closing devices repository.
14/037/2020 00:37:25 - INFO - Devices sync finished.
14/037/2020 00:37:27 - INFO - Loading devices database
14/037/2020 00:37:27 - INFO - Loaded 129 devices
14/037/2020 00:37:27 - INFO - Starting phone detection
14/037/2020 00:37:31 - INFO - Device connected in flash mode
14/038/2020 00:38:36 - INFO - Selected Bundle for Sony Xperia XZ2(H8296). FW release : 52.1.A.3.49-R4C. Customization : Custom TW
14/038/2020 00:38:36 - INFO - Preparing files for flashing
14/041/2020 00:41:26 - INFO - Please connect your device into flashmode.
14/041/2020 00:41:27 - INFO - Using Gordon gate drivers version 3.1.0.0
14/041/2020 00:41:28 - INFO - USB buffer size set to 512K
14/041/2020 00:41:28 - INFO - Opening device for R/W
14/041/2020 00:41:29 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
evermore05 said:
Hi all i tried to flash my XZ2 with flashtool and i downloaded the latest ROM from Xperifirm. I created FTF file from the ROM i downloaded by unchecking .TA files. I have unlocked bootloader with cmd (which means all the drivers must be installed properly). But it didnt show neither errors nor succeeding in flashing the ROM. When i exited flash boot mode, my phone still can be turned on normally.
In before, i softbricked my phone but managed to reflash it with EMMA, but not satisfied because it's android 8. Anyone please help me, what steps i missed here? Im super noob in this kind of stuff, so please explain it easily for me. Thank u!
Click to expand...
Click to collapse
I have solved the problem. So i need to install the driver from C:\Flashtool\drivers, ticked the flash boot and fast boot, include .TA files in the FTF file, and not plugging my phone in USB 3.0 slot. Hope this would be useful for anyone having the same problem as mine.
Oke so i finally got araund to do my daily driver sony xz1 compact and when i tried to unlock the bootloader using flashtool also know as sony mobile flasher by androyxde.
I get the following error
ERROR - Cannot invoke “String.split(String)” because the return value of “java.util.Properties.getProperty(String)” is null
Now i looked everywhere on the internet literally and i could not find a awnser to my problem but i did find multiple people with this problem but no defenitive awnser…
but i kept looking and i found that my computer can not find my phone exactlly because when i use command and try adb devices it cant see it but fastboot mode it can.
So i looked for an awnser and said probally need to update your drivers so i downloaded drivers from the sony site installed them then got the message that i have to restart computer before it can go into effect and i do that and then nothing stil does not work i see no adb devices in the list.
oh and i selected the allow unknow drivers from the security option in windos 10 so that should be oke.
I think this might be the problem that adb devices cant be read seeing as it has to be in that mode when trying to unlock the bootloader in flashtool.
This is what it shows in the program
01/048/2021 22:48:26 - INFO - Flashtool 0.9.33.0
01/048/2021 22:48:26 - INFO - Searching for a web proxy
01/048/2021 22:48:26 - INFO - No proxy found, using direct connection
01/048/2021 22:48:27 - INFO - Syncing devices from github
01/048/2021 22:48:27 - INFO - Opening devices repository.
01/048/2021 22:48:28 - INFO - Scanning devices folder for changes.
01/048/2021 22:48:36 - INFO - Pulling changes from github.
01/048/2021 22:48:37 - INFO - Devices sync finished.
01/048/2021 22:48:39 - INFO - Loading devices database
01/048/2021 22:48:39 - INFO - Loaded 131 devices
01/048/2021 22:48:39 - INFO - Starting phone detection
01/048/2021 22:48:58 - INFO - Device connected with USB debugging on
01/049/2021 22:49:01 - INFO - Connected device : Sony Xperia XZ1 Compact
01/049/2021 22:49:01 - INFO - Installed version of busybox : N/A
01/049/2021 22:49:01 - INFO - Android version : 9 / kernel version : 4.4.148-perf+ / Platform : 64bits / Build number : 47.2.A.11.228
01/049/2021 22:49:01 - INFO - Root access denied
After that i try ubl option
01/051/2021 22:51:20 - INFO - Please connect your device into flashmode.
01/051/2021 22:51:57 - INFO - Using Gordon gate drivers version 3.2.0.0
01/051/2021 22:51:58 - INFO - Opening device for R/W
01/051/2021 22:51:58 - INFO - Device ready for R/W.
01/051/2021 22:51:58 - INFO - Reading device information
01/051/2021 22:51:58 - INFO - Reading phone properties
01/051/2021 22:51:58 - INFO - Sending getvarroduct
01/051/2021 22:51:58 - INFO - getvar status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:2202
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:2205
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:2210
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:4900
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Read-TA:2:10021
01/051/2021 22:51:58 - INFO - Read-TA status : OKAY
01/051/2021 22:51:58 - INFO - Sending Get-root-key-hash
01/051/2021 22:51:58 - INFO - Get-root-key-hash status : OKAY
01/051/2021 22:51:59 - INFO - Connected device : G8441 / SW release 1307-7511_47.2.A.11.228 / Customization 1310-8075_R4C
01/051/2021 22:51:59 - INFO - Last flash date : 2018-11-19 23:19:03
01/051/2021 22:51:59 - INFO - Phone ready for flashmode operations.
01/051/2021 22:51:59 - ERROR - Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null
C:\Users\n>adb devices
List of devices attached
adb server is out of date. killing…
daemon started successfully *
C:\Users\n>adb reboot bootloader
error: device ‘(null)’ not found
C:\Users\n>
It's been a while since I've done it but I think you need the Google USB drivers and the 15sec ADB driver. If I remember, the Sony driver doesn't work for ADB/Fastboot. You'll need to update/assign one driver while it's connected in normal mode and do the other while it's in fastboot mode.
Thank you for your fast reply
I already had 15 sec adbdriver and for the assigning driver i dont quite understand but i tried it in difrent modes and it tells it already has the most up to date drivers.
stil doesnt work
what am i missing ?
mstrnemo said:
Thank you for your fast reply
I already had 15 sec adbdriver and for the assigning driver i dont quite understand but i tried it in difrent modes and it tells it already has the most up to date drivers.
stil doesnt work
what am i missing ?
Click to expand...
Click to collapse
Did you assign the drivers manually? Windows will almost always tell you that you have the most up-to-date drivers and leave it at that. You need to go to device manager, right click update driver and then select browse my computer for drivers. It'll give you the option to search a location on your computer but you want the 2nd option that says Let Me Pick from a List of Available Drivers on my Computer.
I also reread your OP and saw you're using sony mobile flasher by androyxde. I don't remember ever using that. It was several years ago but I only used newflasher, renoroot and adb/fastboot. I used newflasher to downgrade to Oreo, renoroot to back up TA and adb/fastboot to unlock the bootloader. Then I did the process in reverse to have an unlocked BL and the latest Pie version.
AlexKarimov said:
Did you assign the drivers manually? Windows will almost always tell you that you have the most up-to-date drivers and leave it at that. You need to go to device manager, right click update driver and then select browse my computer for drivers. It'll give you the option to search a location on your computer but you want the 2nd option that says Let Me Pick from a List of Available Drivers on my Computer.
I also reread your OP and saw you're using sony mobile flasher by androyxde. I don't remember ever using that. It was several years ago but I only used newflasher, renoroot and adb/fastboot. I used newflasher to downgrade to Oreo, renoroot to back up TA and adb/fastboot to unlock the bootloader. Then I did the process in reverse to have an unlocked BL and the latest Pie version.
Click to expand...
Click to collapse
Newflasher ? is just to flash firmware i dont need to i already have latest firmware.
I did that first manuelly install drivers i downloaded from the sony site but i do not know about the adb driver ? is that the 15 sec adb driver installer
I cant unlock bootloader using adb/fastboot because when using command adb devices it cant see my phone?
so wether it is flashtool or adb/fastboot it doesnt work theres gotta be something i am missing?
see below what it says in command
(c) Microsoft Corporation. All rights reserved.
C:\Users\n>adb devices
List of devices attached
C:\Users\n>adb reboot bootloader
error: no devices/emulators found
C:\Users\n>
mstrnemo said:
Newflasher ? is just to flash firmware i dont need to i already have latest firmware.
I did that first manuelly install drivers i downloaded from the sony site but i do not know about the adb driver ? is that the 15 sec adb driver installer
I cant unlock bootloader using adb/fastboot because when using command adb devices it cant see my phone?
so wether it is flashtool or adb/fastboot it doesnt work theres gotta be something i am missing?
see below what it says in command
(c) Microsoft Corporation. All rights reserved.
C:\Users\n>adb devices
List of devices attached
C:\Users\n>adb reboot bootloader
error: no devices/emulators found
C:\Users\n>
Click to expand...
Click to collapse
You need newflasher to downgrade to oreo so you can unlock bootloader.
If you have the ADB driver, then you need the Google USB driver.
If none of this helps, I'm sorry but I can't offer any more.
i need to downgrade to oreo so i can unlock bootloader ?
i didnt know that what is the reason for this ?
hmmm is there a how to on the site or somewhere that i may have missed somehowe ? seems weird to me there isnt alot of info about this doesnt have everyone had the same problem at some point?
Anyway thank you for your help
when on my computer can see it so it works
when in fastboot mode it can be seen so it has the right driver (can also be seen in command)
however android adb interface has a ! mark and gives me a code 10 error ?
Edit: i deleted the one with the ! so no more code 10 error but i then tried literally every single one in the list but noone works ? with that i mean it shows the device works but i can not use command adb devices and adb reboot bootloader does stil not work
I ****ed up i had it ... it worked i dont know what i did but it worked so i go back to flashtool thinking to get this over with now suddenlly i get error missing driver? and that i should go to the driver folder and i go there and install al of them just in case i then try it again but now i get the same error i had in the beginning ? adb doesnt work anymore and now i try to install adb driver but it wont work ??? damn 2 steps front 3 steps back
Anyone willing to help me install drivers i just cant seem to get it to work?
I ended up reinstalling windows 10 and then tried again and then it worked.
/Closed/