Database Develop

[HELP] Flashmode Freeze My PC

Hi guys, my EN is poor, SORRY
when i connect my xperia tx to my pc through flashmood (voloume down then connect), the pc freeze and i should restart windows, drivers installed
but the problem not exists with my friend laptop with same flashmode & phone drivers instillation
plz help me friends, its make me so sad

1) No need to change the font in your posts
2) Download flashtool from the first thread in the development section
3) Install it
4) Goto the installation directory (C:\flashtool) and open the driver folder
5) Run driver.exe
6) Tick boxes for flashmode, fastboot and TX
7) Try again.
8) Report back here if it works or not.
9) If not, then run flashtool and attach the phone in flashmode to the PC. Report back the log from flashtool

gregbradley said:
1) No need to change the font in your posts
2) Download flashtool from the first thread in the development section
3) Install it
4) Goto the installation directory (C:\flashtool) and open the driver folder
5) Run driver.exe
6) Tick boxes for flashmode, fastboot and TX
7) Try again.
8) Report back here if it works or not.
9) If not, then run flashtool and attach the phone in flashmode to the PC. Report back the log from flashtool
Click to expand...
Click to collapse
i do all steps before, but problem not solved (just on my pc no on my friend laptop)
the problem is just when i try go to flashmode (first post edited)
i searched on google and i see many ppls have same problem and cant find any solution's
this is the log:
Code:
19/059/2013 11:59:05 - INFO - <- This level is successfully initialized
19/059/2013 11:59:06 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/059/2013 11:59:06 - INFO - You can drag and drop ftf files here to start flashing them
19/059/2013 11:59:19 - INFO - Device disconnected
19/059/2013 11:59:52 - INFO - Device connected with USB debugging on
19/059/2013 11:59:52 - INFO - Connected device : LT30
19/059/2013 11:59:52 - INFO - Installed version of busybox : BusyBox v1.20.0 (2012-08-22 21:36:24 CDT) multi-call binary.
19/059/2013 11:59:52 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-17382J-g2f4f874-00856-gaa0cc9c / Build number : 9.1.B.0.411
19/059/2013 11:59:54 - INFO - Root Access Allowed

Uninstall all android software. (Flashtool, pccompanion etc) and reboot and reinstall it.
Then try again.
Have you tried flashing something in flashmode yet?

I do all that u say
yes i flashed former tx jb with flash tool by my friend laptop

smfazel said:
I do all that u say
yes i flashed former tx jb with flash tool by my friend laptop
Click to expand...
Click to collapse
can you try it on your machine please and then post the output from flashtool...
I need to know what your machine is doing. It very much seems like a problem with your computer

gregbradley said:
can you try it on your machine please and then post the output from flashtool...
I need to know what your machine is doing. It very much seems like a problem with your computer
Click to expand...
Click to collapse
Are u aware??? !!!!!!!!
I say my pc freeze and can't get flashmode
Now I'm tryin inistall win 7 with xp
Sent from my LT29i using Tapatalk 2

Yes I am aware, but thanks for not telling me the information I wanted.
I will now just guess what flashtool says when your pc freezes....
Sent whilst sat on the toilet.

gregbradley said:
Yes I am aware, but thanks for not telling me the information I wanted.
I will now just guess what flashtool says when your pc freezes....
Sent whilst sat on the toilet.
Click to expand...
Click to collapse
Ha ha ha
Bro, when pc hangs or freezes, the pc & flashtool (& me) can't say anything's, just shold restart pc manually
Problem solved with win7
Sent from my LT29i using Tapatalk 2

[ROOT] How to Root Build 10.3.1.E.0.191 [GUIDE]

Disclamer: I take absolutely NO credit for this, I was searching through the forums and found a posting by ragingMonkey that worked for rooting the 10.3.1.E.0.191 build number for the Sony Xperia Z (C6606).
Well, here it is:
you should have your phone in developer mode and have usb debugging on
- i used a flash tool from d-h.st/Kb8
- switched my kernel to d-h.st/1Vz
- rooted with download.cnet.com/Kingo-Android-Root/3000-2094_4-75996768.html
1. you do this by opening flash tool. letting it install. then selecting you device and flashmode drivers.
2. then connect your phone to computer via usb
3. then click the lighting bolt in the top right in the menu bar.
4. a window will pop up. press the flashmode radio button then ok
5. another window will pop up.
6. on the right side of the window it will ask if you wanna wipe types of info like cache, data, applogs. if you want you can click those if not leave them blank.
7. then at the top you will see a browse button to browse files (i think its a ... button)
8. use it to find the kernel
9. after you do that click the flash button and follow the instructions.
10. the instructions are "1 unplug the phone. 2 turn off phone. 3 enter flash mode by pressing and holding the down volume button (while off). 4 connect device (still off)"
11. once you plug the phone back in the flash tool will exit the window you were in and be doing its process in the terminal like window in the original window.
12. after you do that. unplug the device and reboot it. then exit flashtool (important) and then
use the kingo android root.
13. it should do some installing then ask you to connect device
then just follow those instructions in which i dont have up so i cant tell you hope i helped
NOTE: It will say "Root Failed", although it actually did NOT fail and was successful!
BIG thanks to ragingMonkey!
Bye!

There is a much easier way, no different kernals needed. I have also heard alot of negative about kingo root.
Use the tools mentioned here.
http://forum.xda-developers.com/showthread.php?t=2547714
Download both the tools. Make sure you have USB debugging is on and install from unknown sources is on. One of the folders downloaded will have ABD files while the other will not. Copy the ADB files to the one that does not. Run the ADB.exe then run the tool, the install batch file.
I did this with a C6606 on 10.3.1.E.0.191.

Tried going through your suggestion, it didnt help help on my Tmobile C6606. Attached is a screenshot. any suggestions??
Here's my info though:
Android 4.2.2
Build: 10.3.1.E.0.191
Thank you.
deerhurst said:
There is a much easier way, no different kernals needed. I have also heard alot of negative about kingo root.
Use the tools mentioned here.
http://forum.xda-developers.com/showthread.php?t=2547714
Download both the tools. Make sure you have USB debugging is on and install from unknown sources is on. One of the folders downloaded will have ABD files while the other will not. Copy the ADB files to the one that does not. Run the ADB.exe then run the tool, the install batch file.
I did this with a C6606 on 10.3.1.E.0.191.
Click to expand...
Click to collapse

for anyone looking for a solution, this post helped me root my tmo C6606
http://forum.xda-developers.com/showpost.php?p=48861859&postcount=26
Thanks everyone.

Looking to go AOSP from Stock KK [4.4.4]

Sooooooooooo,
I have a Z1 [C6903] that I picked up yesterday. It came with 14.2.A.1.136 Jellybean 4.3.
I wanted to
Unlock bootloader
Install custom recovery
Root
Install any nice AOSP ROM [preferably LP-based]
I installed the Minimal ADB-Fastboot 1.4.
I also installed the Flashtool 0.9.18.2.
I also installed the Z1 device, Fastboot, and Flashmode drivers [version 1.6.2] from the driver folder. It first failed, and then I disabled driver verification then everything went smooth!
Device manager recognized the phone in MTP and Fastboot, and Flashmode modes. Drivers installed correctly I presume.
Then the challenges arrive:
adb devices returned it as "offline"
Android studio couldn't push a project to it because it was offline
fastboot devices identified it, but fastboot -i 0x0fce getvar version returned an error [getvar:version FAILED (command write failed (Unknown error))]
Things I've tried to do to rectify the connectivity issue:
I'm using a SurfacePro 4 so I can't switch USB ports [only have one].
I've tried different cables - they yield the same result.
I've enabled and disabled USB debugging, revoked access, unplugged and replugged, rebooted, etc. Still no change in result.
Since the device had some OTA updates pending, I ran those and now i'm on 4.4.4 with 14.4.A.0.157, with some other updates currently waiting for me to accept so they can download. I've decided to post here for help and won't run those updates unless it increases my profit
PS: Even after the updates, adb and fastboot still are unchanged in their results.
Help please
Update:
It was a freaking USB cable. I had tried two of them. None had worked.
I finally unleashed my Anker USB cable and Boom! We good to go!!!
Thanks all!:highfive::highfive::highfive::highfive:

Make sure to enable USB debugging in Developer Options at the bottom of the Settings app

tomascus said:
Make sure to enable USB debugging in Developer Options at the bottom of the Settings app
Click to expand...
Click to collapse
Did this and more. Still to no avail.
The phone shows up in the computer, it just doesn't show as online when I run the adb devices command.
That's what I need help with.
Thanks

ahh have you tried using
Code:
adb kill-server
adb start-server
and trying again?
What should happen is the authorisation window pops up on your phone

tomascus said:
ahh have you tried using
Code:
adb kill-server
adb start-server
and trying again?
What should happen is the authorisation window pops up on your phone
Click to expand...
Click to collapse
Excellent! I did that, too. even manually closed and restarted adb.exe to no avail.
The thing is, my Z1 DOES NOT show me the authorization pop-up! Ever!
I've done this a million times on other phones, and I know the procedure. It's just that this Z1 is not showing the authorization popup
Thoughts?

boydee said:
Excellent! I did that, too. even manually closed and restarted adb.exe to no avail.
The thing is, my Z1 DOES NOT show me the authorization pop-up! Ever!
I've done this a million times on other phones, and I know the procedure. It's just that this Z1 is not showing the authorization popup
Thoughts?
Click to expand...
Click to collapse
Find a quiet corner and cry
Tried running adb as admin?

tomascus said:
Find a quiet corner and cry
Tried running adb as admin?
Click to expand...
Click to collapse
Tried this, too!
No change, anywhere.
I actually went ahead and tried adb on another PC with minimal adb-fastboot and adb drivers installed, and it returned the same "offline" response
Whoa!:angel:

@boydee
this could work with you
i assume that you rooted your phone you will do that:
1. open your favorite file explorer(suggest: ES File Manger)
2.go to /data/misc/adb/
3.delete "adb_keys" file
4.enable usb debugging
5.reinstall your drivers
6.open command and kill adb server(adb kill-server)
7.connect your device and run command (adb devices)
8.look at your device you will find text box telling you a new pc check always trust bla bla and click trust or something like that
9.you will see something like that
http://imgur.com/ReQtofb

How to upgrade to kitkat 4.4.4 India version of c6903 Sony Xperia Z1 pls help

DectonX said:
@boydee
this could work with you
i assume that you rooted your phone you will do that:
1. open your favorite file explorer(suggest: ES File Manger)
2.go to /data/misc/adb/
3.delete "adb_keys" file
4.enable usb debugging
5.reinstall your drivers
6.open command and kill adb server(adb kill-server)
7.connect your device and run command (adb devices)
8.look at your device you will find text box telling you a new pc check always trust bla bla and click trust or something like that
9.you will see something like that
http://imgur.com/ReQtofb
Click to expand...
Click to collapse
Hey, thanks for the advice!!
Finally got root [without use of PC] and when I open the /data/misc/adb/, the folder is EMPTY
A little confused there.
I did the same procedure for the PC [deleting from C:/Users/boydee/.android/] but it also was to no avail.

k9rockstar said:
How to upgrade to kitkat 4.4.4 India version of c6903 Sony Xperia Z1 pls help
Click to expand...
Click to collapse
Hey there! Please check here for a firmware file that works for you.
When you've downloaded, use the Flashtool to flash it to your phone.
If you want help flashing it to your phone, check this thread out.
Hope that helps

boydee said:
Hey, thanks for the advice!!
Finally got root [without use of PC] and when I open the /data/misc/adb/, the folder is EMPTY
A little confused there.
I did the same procedure for the PC [deleting from C:/Users/boydee/.android/] but it also was to no avail.
Click to expand...
Click to collapse
This could problem with installing drivers as PC don't detect adb in debugging mode
So disable driver verification again and install drivers from flashtool remember to check
1. Fastboot drivers
2. Flashmode drivers
3. Xperia Z1 drivers
And restart
If the problem not fixed try adb universal drivers just Google it
I was have same problem with win 8.1 but I didn't all that I just installed win 7 and do it
Remember to backup ta before unlock to backup your DRM keys

Why is there no loader.sin in the ROMs I'm downloading with Xperifirm?

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

(Closed) Strange error while trying to unlock bootloader

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/