Open UniversalSuperBox opened 3 years ago
I was stuck on fastboot and your comment about "Optional Updates" on Windows Update was enough to get it installed. Thanks!
Why is this even a question? of course it should download needed drivers as soon as a device is selected!
The question isn't, "should we?"
The question is, "how?"
Only one person who works on Ubuntu Touch or the Installer is a Windows software engineer, and they're pretty busy elsewhere in the project. We'd love your help to make the installer work better on Windows.
The issue wasn't a driver problem, it's a root permission / twrp issue. I had to reinstall and root for this to work
On Tue, 13 Jul 2021, 22:53 Dalton Durst, @.***> wrote:
The question isn't, "should we?"
The question is, "how?"
Only one person who works on Ubuntu Touch or the Installer is a Windows software engineer, and they're pretty busy elsewhere in the project. We'd love your help to make the installer work better on Windows.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ubports/ubports-installer/issues/1922#issuecomment-879427590, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANK2OF2ISVQE5ZODTSDCFP3TXSYUZANCNFSM43PGMLIA .
I suggested an enhancment to include some of the required drivers for the fastboot to work in MS Windows, see issue #2272
I needed a fastboot driver to install Ubports on Xiaomi Mi A2 / jasmine_sprout, as explained here #2330 But I didn't manage to install Ubports with Linux (Debian 11): another driver missing?
It should be also added that some drivers might require Device Driver Signing
to be disabled to be installed successfully (eg Xiaomi driver.
If the Device Driver Signing
is not disabled the following error might occur:
Windows encountered a problem installing the driver software for your device. Windows found driver software for your device but encountered an error while attempting to install it. The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
Select the “Start” button.
Type “startup”.
Select “Change advanced startup settings“.
Select “Restart now” under the “Advanced startup” area.
Select “Troubleshoot“.
Select “Advanced Options“.
Select “Startup Options“.
Select “Restart“.
A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
The UBports Installer used to warn users that they should install some adb drivers from the ClockWorkMod website. This good-intentioned warning seems to have worked at some point in the past, but it did more harm than good lately: the installer worked better before installing the drivers than after.
However, the saga doesn't end there. It turns out, more drivers are required to use the UBports Installer on Windows! The driver included with Windows works for most
adb
devices in my library, but the vendor-specific fastboot drivers are required forfastboot
sessions.Google's drivers can be found on their website Other vendors' drivers, along with installation instructions, can be found in the Android documentation.
There is also a driver which is offered in Windows Update that seems basically "universal" for the devices I tested -- the OnePlus One, Nexus 5, Volla Phone, Xperia X... I can't remember its name, but it appears in "Optional Updates" after Windows sees a fastboot device the first time.
This report serves two purposes:
Please post here if you know either.