Database Info

i ****ed up a big time

I rooted mobile a while ago so suddenly one day it went in bootloop. So i tried to factory reset it after that still it didn't work out. After that i decided to just go for other rom so i unlocked my bootloader and tried to install cm 12.1. But wifi doesn't work on it also also it doesn't detect sim card.
Can anyone tell me how to set it to old device. I don't want any fashionable thing no root no recovery nothing i just want a phone back with wifi working and not rebooting like hell. I tried to download the original .ftf file but that also not flashing showing session ending error and please don't tell me to reinstall drivers i tried it already. my xperia L model is c2014. I also tried emma and those how don't know emma doesn't support some models and sadly one of which is my device. Plz anyone can tell me a easy process or something hopefull that i can try to get my phone back.And is sony service center will be able to help me if i give them my phone to service?

nisarg007 said:
I rooted mobile a while ago so suddenly one day it went in bootloop. So i tried to factory reset it after that still it didn't work out. After that i decided to just go for other rom so i unlocked my bootloader and tried to install cm 12.1. But wifi doesn't work on it also also it doesn't detect sim card.
Can anyone tell me how to set it to old device. I don't want any fashionable thing no root no recovery nothing i just want a phone back with wifi working and not rebooting like hell. I tried to download the original .ftf file but that also not flashing showing session ending error and please don't tell me to reinstall drivers i tried it already. my xperia L model is c2014. I also tried emma and those how don't know emma doesn't support some models and sadly one of which is my device. Plz anyone can tell me a easy process or something hopefull that i can try to get my phone back.And is sony service center will be able to help me if i give them my phone to service?
Click to expand...
Click to collapse
It is indeed a driver issue. If WiFi isn't working, you can flash stock ftf and then install whichever rom you were installing. Firstly, to get back to stock and relock your bootloader you need your TA. If you didn't backup your TA before unlocking your bootloader, You'll have to live with some functions of the stock rom lost. Restoring the TA locks your bootloader.
Okay so, if you have the stock ftf, head over to your flashtool folder, navigate to drivers and open Flashtool-drivers.exe.
For Xperia L, the drivers you need - "Flashmode Drivers", "Fastboot drivers", "Common drivers for Taoshan".
If install fails, you may need to disable driver signature check. Just google that, it's pretty simple.
If you don't see such a file, just get it from here - [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318]
Then connect your phone in FLASHmode. Not Fastboot. Fastboot has a blue LED and Flashmode has no LED (You'll see red and green flash before the no LED). Your device should be listed under Universal Serial Bus Controllers as SEMC Flash Device or Generic Flash device. If it says S1 Service or something similar, right click and update Driver Software, "Browse my computer for driver software", and let me pick from a list. Uncheck Show compatible Hardware, scroll to Sony Ericsson Mobile Communications, and select SEMC Flash device. Reconnect your device to check if it detects it as SEMC or Generic Flash Device. If yes, try to install your ftf.
If you were already on this driver, try switching to the S1 Service. (Not sure where to find that but it never worked for me. Your mileage may vary. Give it a search).
Also, if you take it to a service center, they'll probably charge you some money and probably replace the whole board. Thus, Hakuna Matata. Keep calm, your phone is absolutely fine. Never tried Emma though. Flashtool ftw!

Agent_fabulous said:
It is indeed a driver issue. If WiFi isn't working, you can flash stock ftf and then install whichever rom you were installing. Firstly, to get back to stock and relock your bootloader you need your TA. If you didn't backup your TA before unlocking your bootloader, You'll have to live with some lost functions of the stock rom lost. Restoring the TA locks your bootloader.
Okay so, if you have the stock ftf, head over to your flashtool folder, navigate to drivers and open Flashtool-drivers.exe.
For Xperia L, the drivers you need - "Flashmode Drivers", "Fastboot drivers", "Common drivers for Taoshan".
If install fails, you may need to disable driver signature check. Just google that, it's pretty simple.
If you don't see such a file, just get it from here - [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318]
Then connect your phone in FLASHmode. Not Fastboot. Fastboot has a blue LED and Flashmode has no LED (You'll see red and green flash before the no LED). Your device should be listed under Universal Serial Bus Controllers as SEMC Flash Device or Generic Flash device. If it says S1 Service or something similar, right click and update Driver Software, "Browse my computer for driver software", and let me pick from a list. Uncheck Show compatible Hardware, scroll to Sony Ericsson Mobile Communications, and select SEMC Flash device. Reconnect your device to check if it detects it as SEMC or Generic Flash Device. If yes, try to install your ftf.
If you were already on this driver, try switching to the S1 Service. (Not sure where to find that but it never worked for me. Your mileage may vary. Give it a search).
Also, if you take it to a service center, they'll probably charge you some money and probably replace the whole board. Thus, Hakuna Matata. Keep calm, your phone is absolutely fine. Never tried Emma though. Flashtool ftw!
Click to expand...
Click to collapse
Thanks will try. Changing board costs like 4-5 k and my phone is 2 year old so not replacing board rather i will go for a new device. I will surely try what u suggested. Thanks for help bro thanks a lot

[SOLVED] Soft bricked Z5 - Require Assistant

So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni

Use PC Companion repair option (marked with a red box on my screenshot).

LitoNi said:
So, i havent been modding Android phones in a long time and when I wanted to flash MM on my Z5, i forgot that i dont have the Z5 drivers. Now, based on what i know, i did have SONY PC COMPANION installed prior to soft bricking my device, so i would assume the drivers are installed. My current situation is as follows:
-Device wont turn on, switches between RED/GREEN led with error message of "update failed, please connect to PC etc..."
-Sony pc companion doesnt seem to recognize the phone as i cant repair it
-Cannot flash FTF through as it keeps failing to flash at different points, do not know if not having the Z5 drivers play a factor here. I got the drivers from there but i do not know what to do with it as it is not .exe file, i also have the latest flashtool installed.
-I backed up my files prior to this, so i am willing to wipe everything.
Thank you, i would appreciate if i can get some assistant on this. Stupid me for making this mistake in the first place.
Regards,
Litoni
Click to expand...
Click to collapse
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")

Install the drivers that are inside flashtool.

Mr_Bartek said:
Use PC Companion repair option (marked with a red box on my screenshot).
Click to expand...
Click to collapse
As mentioned, SPCC doesn't recognize my phone. It somewhat does but doesn't give me the option to repair. There are these other screens which i think are prior to the repair page (hopefully) but i was stuck at the page when it asks me to remove the battery or skip if built in. It asks me to press ok to skip but hitting the ok button didn't do anything.
zacharias.maladroit said:
What Windows version ?
Follow
# STEP 1 - GENERAL GUIDE
INSTALL / CHECK DRIVERS
of
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
and (re-)boot into (newer) Windows by disabling the driver signature verification.
Log in with administrator rights,
Extract the zip-file,
there you have inf files
https://en.wikipedia.org/wiki/INF_file
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549520(v=vs.85).aspx
right-click on those and choose install - so that the device drivers are installed.
Reboot (of Windows) shouldn't be necessary.
Entering Fastboot mode should still be possible, check whether it's being recognized now (via Minimal ADB and Fastboot).
Remember: in case the device goes crazy because it's not being detected upon connection - you can still turn it off via
Emergency off
(listed under "#FASTBOOT / FLASHMODE / RECOVERY / etc.")
Click to expand...
Click to collapse
Thanks my desktop is running windows 10 and i know theres so many issues with it.
gm007 said:
Install the drivers that are inside flashtool.
Click to expand...
Click to collapse
The drivers from flashtool does not include any xperia Z5 series.
Thank you guys for the quick responses, I managed to reflash the .200 through flashtool without any hiccups. which is weird that it didn't work for .163 earlier. I didn't wipe anything, so after flashing .200 i updated the SDK stuff from Google SDK.exe which i think it solved some, from there I flashed .163 (MM) again and it worked. Kept all data intact, even my encrypted Class 10 SD card worked without any issues. So far so good, haven't really encountered any errors, fingers crossed :fingers-crossed: once again thank you for the quick responses.

XZ Root/TWRP/ROM Help

Hi XDA,
It's been a while since I've done any work on any phones, I've previously used roms on Galaxy S and SIII. But those are a while ago as you can see. I've got an Xperia XZ, the bootloader is currently unlocked. But I cannot, for the life of me, get any further despite following several guides and programs. So I'm at a loss.
At this exact moment, I have my XZ connected to my pc with the blue light on. CMD in ADB/Fastboot cannot detect the device. My understanding is I need to flash the kernal and recovery first, then I can consider flashing a custom rom.
Would anybody be able to assist me? I dropped this project a few months ago, so I'll need to check what rom I was going to use and update the img files I have.
Thanks

Installed fastboot abd on pc?

Yep, that's been installed. I do have an issue which I thought/think is driver related as the daemon doesn't always start, and doesn't detect the phone correctly either.

What OS is on your computer?

Windows 10, I also tried Linux Mint but didn't get much further.

Have you disable the drivers vetification?

Yep!

Can flashtool detect your device? Sorry for all the questions but got to start somewhere and have you tried changing USB ports and cables?

No, the questions are good. There will be something wrong that I can't find, so we need to work it out somehow.
Flashtool doesn't consistently detect the device. The computer does, flashtool doesn't. I have changed the cables with some success, but that hasn't helped me progress much further.

Hmm, have you install the drivers from Sony developer site? Also try it on another computer..i wonder if you have a bad connection port on your phone thus the reason I asked about another computer.. Try reinstalling fastboot and adb, drivers etc. with your anti-virus disable.. And does Sony companion work? USB debugging turned on?
Sounds silly but sometimes we forget, like redoing doing your phone from scratch and you can't delete some stuff and only to remember later that you forgot to install busybox or mount your system partition.. lol

Thanks Lilbrat,
I'll be doing a fresh install, hopefully this weekend. And will cover what you have mentioned and report back. Thanks!

since this is your first Xperia device, you must first familiarize yourself with the ENVIRONMENT and TOOLS in which SONY Xperias can be played with !
some basics I wrote for X, but applies for XZ also , please read as it will be helpful!
https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7
now
since your boot is already unlocked so I can safely assume that you don't have TA.img file at all!
this leaves you with only two solutions
1. install 3rd part ROMS
2. flash sony STOCKROM and flash MODDED kernel (most of us do this)
your XZ has project name by SONY called KAGURA, your device on xperifirm is recognized by this name, dual/single you have to specify
from flashtool, xperifirm, download latest firmware 41.3.A.2.157 under KAGURA, close xperifirm and FLASHTOOL will start creating FTF file AUTOMATICALLY, click OK to any script question. and let it create ftf for u
flash it on your XZ,
send me kernel for 41.3.A.2.157, i will patch it for u! (patching guide is given in this forum but at this point i think it will be too much for you, so i will fix the kernel for u)
KAGURA twrp can be found at https://dl.twrp.me/kagura/ ( unlike SAMSUNGS, sony Xperias don't have inbuilt RECOVERY )
flashing recovery is MUST!
when device is switched off, connecting USB CABLE to PC and MObile while
1. HOLDING VOLUME UP KEY (blue LED) is FASTBOOT MODE (used mainly for sending twrp and kernels )
2. HODLING VOLUME down KEY (GREEN LED) is FLASHMODE (used mainly to FLASH stock roms using FLASHTOOL
you must install
1. Xperia Companion
2. flashtool ( www.flashtool.net) (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ)
3. install minimal adb and fastboot 1.4x from XDA (google it)
4. using these TOOLS you can
a-flash firmwere
b flash recovery
c flash modded kernel
d boot in to recovery (twrp) and flash MAGISK 16.x .zip from twrp + drm patch files! ( i will give you later with modded kernel)
e reboot and your device will wakeup ROOTED having DRM FIX! ---- switch off the SOFTWARE updater using any ROOT APP FREEZE app from playstore!

Currently working through a reinstall of flashtool etc, I can detect the phone using the Sony Companion tool, so thats positive. I haven't seen any notification that drivers have installed, but I do have the XZ drivers unzipped here.
Edit1: It doesn't detect or anything when the blue or green lights are on phone either. Not sure about them at this point.
Edit2: Just going through your guide as well Yasu, I cannot locate "sony Xperia X motherboard drivers (sa0107)" or anything similar to my device. Just throwing that out there. Installing the two common results in Sony Mobile Communications (ggsomc( USB (11/10/14 3.1.0.0) installing, but Google. Inc (WinUSB) AndroidUsbDeviceClass (12/06/10 4.0.0...) failing.
Will continue. Derp, just noticed I have a completely different flash tool. Sony Mobile Flaster by Androxyde, v0.9.25.0 but atleast it detects the connected device more than previously.
21/004/2018 13:04:44 - INFO - List of connected devices (Device Id) :
21/004/2018 13:04:44 - INFO - - USB\VID_0FCE&PID_0DDE\CB512CK84Q Driver installed : false
21/004/2018 13:04:44 - INFO - List of ADB devices :
21/004/2018 13:04:48 - INFO - - none
21/004/2018 13:04:48 - INFO - List of fastboot devices :
21/004/2018 13:04:50 - INFO - - none
Edit 3: Right, forgot to disable Win10's driver signature. Fixed that part again.

Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.

AVeers said:
Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.
Click to expand...
Click to collapse
1. as i mentioned " (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ) "
2. once these drivers are installed, you will get SOMC notification when very first time you connect your XZ in any MODE (volume up / and /or / volume down)
3. while flashing firmware, if you didnt tick WIPE areas, you will get encryption error , you must perform CLEAN FLASHING
4. before booting in to twrp, you must flash MODIFIED KERNEL - you can take modded kernel from my post in this forum
5, boot into twrp, flash drm fix files, flash magisk and wipe delvik cache/ cache and Reboot!

Yep, I see what you mean now. I missed the options on the flash screen, I thought it was odd that the time it took didn't match anything close to the times you described.

That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.

AVeers said:
That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.
Click to expand...
Click to collapse
did you flash the modded kernel?
if you simply flash magisk on original kernel!
you will be stuck on SONY LOGO

OK, I still following this with some interest, as a bit of clarification seems to be needed.. Now granted for some reason Flashtool doesn't have the XZ drivers even the newest version but there are mb drivers on Sony Developer site.. https://developer.sony.com/develop/drivers/ . (see pic)
@AVeers, more computer questions reason being you said Flashtool is seeing your phone a bit better, which leads me to believe you're still having driver issues.. Are you on a laptop or a desktop? If it's a desktop have you tried plugging your USB into the rear panel, straight into the mb also have you tried disabling your anti-virus when installing your drivers? Oh, and where are you located as your firmware is for the middle east, if I remember correctly..

Hi Mate,
I won't be able to work on this further until the weekend. But I do have those drivers from Sony here. And have been using firmware as per Australia (generic). Which is correct for my location.
The phone is plugged into the mobo via rear panel, and this is a desktop running Win10. I'm in test mode to eliminate the driver signing issue. I have not disabled the anti-virus, but I haven't had issues before.
When I run the flash for the firmware, boot.img or twrp.img, it takes seconds to complete, generally less.

XZ Premium (G8141) [Bootloop] [Bootloader Lock]

Hello, I need your help. I mention my problem: I have a XZ Premium (G8141) in the state of (BOOTLOOP) after updating the Android. I did the following: Try to repair the firmware with Xperia Companion, also flash with Newflasher and none of this worked for me. I would like to try to unlock the boot manager since I have it blocked but I can not because I do not have the USB debugging active. Any way to unlock the boot loader? Thank you very much and excuse me for my precarious English. Regards!

RickyGrizu said:
Hello, I need your help. I mention my problem: I have a XZ Premium (G8141) in the state of (BOOTLOOP) after updating the Android. I did the following: Try to repair the firmware with Xperia Companion, also flash with Newflasher and none of this worked for me. I would like to try to unlock the boot manager since I have it blocked but I can not because I do not have the USB debugging active. Any way to unlock the boot loader? Thank you very much and excuse me for my precarious English. Regards!
Click to expand...
Click to collapse
Can you describe what didn't work for you with Xperia Companion?
If you can't effect a repair with the Sony tool, the chances of you negotiating your way round finding and installing the drivers required and flashing the files required to root the phone, in the correct order seems pretty slim. The fact that the phone boots means that it's not bricked and the boot partition is ok.
There is no way to activate USB degug without getting into the OS, so repair or flash is the only option.
Have you installed the Sony drivers ? If you are using Windows 10 you will need to install these drivers with 'driver signing disabled' via safe mode.
You need to have the phone turned off comepletely before trying to connect it to Xperia companion repair, something that's easy to overlook. Hold the volume up(+) and the power button until the phone vibrates three times, then follow the instuctions on the compaion repair. Holding the volume down(-) when connecting the USB lead when asked to do so.

Didgesteve said:
Can you describe what didn't work for you with Xperia Companion?
If you can't effect a repair with the Sony tool, the chances of you negotiating your way round finding and installing the drivers required and flashing the files required to root the phone, in the correct order seems pretty slim. The fact that the phone boots means that it's not bricked and the boot partition is ok.
There is no way to activate USB degug without getting into the OS, so repair or flash is the only option.
Have you installed the Sony drivers ? If you are using Windows 10 you will need to install these drivers with 'driver signing disabled' via safe mode.
You need to have the phone turned off comepletely before trying to connect it to Xperia companion repair, something that's easy to overlook. Hold the volume up(+) and the power button until the phone vibrates three times, then follow the instuctions on the compaion repair. Holding the volume down(-) when connecting the USB lead when asked to do so.
Click to expand...
Click to collapse
I tried installing the drivers that you gave me with the signatures of desperate drivers and now the Xperia Companion does not proceed to flash
Hello, the Xperia Companion tells me that it was restored perfectly. As for the drivers, they do not show me any errors in the device manager. Although I do not remember having installed them by deactivating the drivers' signature. I'll try that, although I doubt it works. Thanks for answering!

Trying to flash H3223

Hi! So I'm new in this forum and I'm trying to flash Xperia xa2 Ultra H3223 but had two problems, first I try flashing with Flashtool but no matter what it said "no partition delivery" or something "yes to continue", found some forum and said something about copying file 50.2.fsc and manually sync but again, clicked and nothing happened. Then I installed Emma but the only firmware was from the US (I'm from Mexico) and was a custom old version 50.1 with no other option. Finally, I just installed Newflasher, follow the instructions and nothing, just this:
"ERROR: TIMEOUT: failed with error code 997 as follows:
Se estß ejecutando la operaci¾n de E/S superpuesta.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
End. You can disconnect your device when you close newflasher.exe"
I've done everything, followed every tutorial and nothing seems to work.
By the way, I'm trying to flash firmware 50.2A.3.22, last year my phone bricked and the only thing I found was firmware Commercial and Journalists wich worked well but now I want to try other version and then LineageOs but guess I'll have to wait.
Don't know what I'm doing wrong, if I turn on my phone works perfect and nothing been erased.
My device is bootloader unlocked and no root.
Please let me know if you need to know something else, I'm not desperate but was kind of excited to try Lineage
Thanks!

I had the same problem with my H3113.
While I had installed flashtool and the drivers that come with it, it seems like they are too old for the XA2. They are from 2014.
What I had to do was get flashtool from the Sony website and open up the .exe with 7-Zip:
https://developer.sony.com/develop/open-devices/get-started/flash-tool
Inside of that is the file Sony_Mobile_Software_Update_Drivers_x64_Setup.exe - this one installs a driver from 2017.
After a reboot, flashing with Newflasher worked. What a damn pain!

I had the same problem and can confirm it works. I wish I saw this comment earlier.

If you flash with flashtool will it relock bootloader?

I am running Windows 10 Pro v. 21H1 and also have a Sony H3223.
I am trying to install the latest plain LineageOS on the phone for which is still supported. The H3223 is unlocked so there are a variety of guides for different flashing projects.
LineageOS wiki suggests installing a universal ADB driver which sadly does not apply for this phone. So I then took a peek at SailfishOS and their flashing guide... incidentally, they specify the use of Sony's Xperia X driver. This forum has a thread suggesting the use of Sony's Xperia XZ2 driver.
SailfishOS was specifying the XZ2 driver as well until they updated their guide for Windows 21H1.
I have tried to install both drivers in alteration—both times I uninstalled everything Android via safe mode—and both drivers will not properly install. I get the icon with the yellow triangle badge in my Device Manager list for 5 seconds but then it changes immediately to the questions mark badge and is only visible after showing hidden devices. This is true even while the phone is plugged in.
The phone is being connected via the included USB cable and is being plugged into a USB 2.0 port on my PC.
The phone when connected does get picked up by Windows and I get listings in other places under Device Manager. ADB sees my phone when I run any adb commands but booting into fastboot mode makes the above happen every time.
In other words, when I connect the phone to my PC, Windows installs some driver from who knows where. At this point, adb commands work but fastboot commands don't work. After this, I uninstall the stuff Windows sets up and I boot the phone into fastboot mode only. When this happens, Windows only shows an Android listing under Device Manager for hidden devices. This is the same device that is designated for the driver update in any guide I find... so at this point I have tried updating this object with the Xperia X and Xperia XZ2 drivers. The Sony object that's supposed to get added to the device tree is never added an instead it's as if nothing happened.
I have followed both the LineageOS guide and SailfishOS guide and I have no clue why Windows will not update the driver. There is nothing complicated about either guides... as I said, adb commands work but that is without me installing any driver and Windows does stuff. The only time I see what I'm supposed to see is when all drivers are uninstalled and I connect the phone to my PC while it's going into fastboot mode. However, Windows will not properly see the phone in fastboot mode due to the driver not being applied.