Twitter refuses to even show the mystery Vista back button. It's too cursed
Conversation
This is the last thing you see before you die
1
2
39
Just hovering in the woods and glowing. Right before the grays appear and you are incinerated by beams of light
5
19
OK, I got a LITTLE further! I told the device manager I wanted a "Legacy Device" of type "Show All Devices". I was then able to Have Disk the .inf and… OMG, "Android Bootloader Interface"! That's exactly what I want!
It failed because it couldn't find "the file".
…What file?
3
1
13
So here's what I've figured out.
- .inf files are just part of a windows driver; they're a text file that describes what things the kernel should map to what things in the .cat or the .dll or whatever.
- Sony gave me only a .inf. They expected you'd supply the rest of the driver.
1
1
17
- If I had the driver installed, Windows might be able to patch the new .inf into it.
- However, it fails with "cannot find the file specified" because although I have *a* Android driver, I don't have whatever specific 2010 driver Sony's inf was written *against*.
1
1
10
- So what I need to make the inf work is to either locate Sony's old 2010 driver (by GUID?) or, more likely, figure out what lines in Sony's inf are the important ones and graft them into the driver I *do* have. That sounds... doable.
But then I get to the Even More Cursed part.
2
8
I have *two* android_winusb drivers installed. 4d7eed is for my Oculus Quest; it's Android, but it's probably not the one Android phones are using, so I can ignore that.
7036ed8 is the one I *think* the phone is using. It's...
"LeMobile"?!
2
9
The Android driver is *supposed* to list Android's manufacturer as Google. Instead, the manufacturer is "LeMobile". I cannot figure out what "LeMobile" is. I assumed it's some French cell provider, but I find no evidence such a company has ever existed in any country.
6
10
Googling "lemobile android", I find multitudes trying to figure out where this "le mobile" driver came from, and claims of it breaking their phone/bootloader. I guess at some point this became the "newest" Android driver in Windows Update, and Microsoft installs it for everything
2
3
12
Replying to
They left the Nexus and Pixel vendor ids in their driver when they forked the code so if you ever plugged in one of those and installed optional updates from Windows Update it would have given you this. It works fine but it's an older version of the proper adb/fastboot driver.
Replying to
Thanks. Is this the source for the newest/normalest driver?
1
Replying to
Yes, but it's a trivial driver and the one Windows Update gives you should work fine anyway. I think there are other drivers with the same vendor ids but for some reason Windows Update almost always prefers to find the LeMobile one. I don't know why Windows drivers are like this.
1
Show replies
On macOS and Linux there isn't a specific driver for adb/fastboot since they just use generic USB support. It doesn't work that way on Windows though. Each device needs this driver with their vendor ids but several vendors left the Nexus/Pixel vendor ids in the code like this.