search

openandroidinstaller-dev / openandroidinstaller

Makes installing alternative Android distributions nice and easy.
https://openandroidinstaller.org
GNU General Public License v3.0
420 stars 33 forks source link

Boot custom recovery may mess up USB or Graphics drivers #318

Open thanojo opened 11 months ago

thanojo commented 11 months ago

Describe the bug I attempted to install LineageOS 20 on my Samsung S8 using OpenAndroidInstaller. After entering download mode, I attempted to boot custom recovery with Heimdall, but received the following error message:

>ERROR: Failed to access device. libusb error: -12

This seems to be a known issue with no clear solution. After going through several attempts using different USB cables, different ports, different laptops, at one point I unplugged the phone (previously connected to the Laptops side USB-2.0 port) while OpenAndroidInstaller was still open at "Boot custom recovery" and the aforementioned error message was output. This caused my external monitors, which were connected to the laptop via a Dell WD15 dock, to go dark. Windows still recognizes them, but they no longer receive a signal. I fixed it eventually after reinstalling and updating all kinds of Lenovo & Dell drivers (I did not keep track due to frustration). I suspect that Heimdall or OpenAndroidInstaller may have caused some sort of conflict with my PC's USB or graphics drivers. So, I think this is more a warning to users than a bug report.: I mean clearly OpenAndroidInstaller can mess with your phone and you make sure to disclaim that, but it seems the same applies to the desktop from which the OS installation is performed.

To Reproduce Steps to reproduce the behavior:

  1. In OpenAndroidInstaller, reproduce the heimdall_flash_recovery error: >ERROR: Failed to access device. libusb error: -12 (using wrong USB cable or port, for example) at the Boot Custom Recovery stage
  2. Disconnect phone from PC with OpenAndroidInstaller still running. (This is the main cause, I do not think it has much to do with the error message in step 1. That's just how it happened to me.)

Log file

openandroidinstaller.log

Desktop:

Smartphone:

tsterbak commented 11 months ago

Thank you for reporting this issue!

Indeed, a very weird issue. I have no idea what could be going on there and how this messes with the drivers. But good to know that this can happen! :grimacing:

eadmaster commented 4 months ago

some here on windows 10 with a samsung s8, will retry on linux later...

EDIT: on linux the error does not appear indeed

tsterbak commented 4 months ago

Sometimes usb drivers or all kinds of other drivers can be an issue that affect the functioning of heimdall. It's a pretty old, in-official redevelopment of samsungs own tool that can behave weirdly sometimes... heimdall nevertheless is awesome!