-
-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: Setting up interface failed! #190
Comments
Hi, I'm having also trouble with heimdall ..to investigate more information you can try this: |
What is heimdall print-pit --usb-log-level debug? |
it is a terminal command that shows the pit of the device in the terminal while also debugging the procedure |
Same problem here. Debug output is: Initialising connection... [13.913469] [000074fe] libusbx: debug [libusb_close] From usb-devices command for the particular device: So there isn't any driver associated with this device and I don't get why libusbx try to release a kernel driver |
I'm afraid I'm having the same issue. Heimdall 1.4. Mac OS X 10.9.1 |
Same here. Installing USEProber and looking at what it shows, it seems to have a few oddities. However, when booted into firmware download / odin mode: If I'm reading this right, then in Odin mode it just doesn't get configured? |
I also had this error: Nothing I tried worked until I did a "Factory data reset" in the settings menu. After that I got no more errors. It could have been a coincidence but perhaps others can give that a try and report back. |
Same problem with heimdall (ubuntu 14.04) flashing. Does anybody find the solution? |
@altamira01 +1 for ubuntu |
sudo heimdall print-pit --verbose --stdout-errors --usb-log-level debug Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is If you appreciate this software and you would like to support future Initialising connection... [timestamp] [threadID] facility level [function call][ 0.002816] [00004215] libusbx: debug [libusb_get_device_list]
iMan:iProd:iSer: 2:1:3 interface[0].altsetting[0]: num endpoints = 1 interface[1].altsetting[0]: num endpoints = 2 [ 8.001228] [00004215] libusbx: debug [libusb_close] |
unfortunately i had to recover my old windows xp pc and do it with Odin. |
looks like same problem here, galaxy s iii, write(1, "Initialising protocol...\n", 25Initialising protocol... when you dig down to where it sends the handshake "LOKI" it receives a -7 error in return. ERROR: Failed to receive handshake response. Result: -7 According to LIBUSB this is a timeout error. |
I had the same issue. Changing the usb port I was using fixed it. Turns out, my some of the usb ports on my laptop are provided via a hub which causes the error. I used the one usb port that is direct, and not via a hub and my phone got flashed just right. |
I had the same problem, but moved the device from a USB 3.0 port to a USB 2.0 port and it worked after that. |
Currently, I have the same issue, any suggestion ? I'm using Ubuntu 14.04 |
acardenasnet have you tried every single one of the USB plugs in your computer? (ie to verify that they aren't viewed as hubs internally) |
Client: Lenovo ideapad S10-2 heimdall info I've read a lot that this is supposed to be a libusb error in heimdall 1.4 but I'm using 1.4.1. Am I stupid? I've tried all three usb plugs of my netbook as you can see in the lsusb output and none of them works. edit: currently re-building with patch #246 applied. |
Same issue here. |
same for me, no luck on an t520, booth patches applied ubuntu 14, libusb-0.1-4 cames installed but libusb-1.0-0 needed to compile ... |
installing from https://launchpad.net/~modycz/+archive/ubuntu/heimdall solve it :-) |
PPA resolved the error for me too on Ubuntu 14.04 👍 |
just tried using PPA on Ubuntu 14.04 64bit, but still no luck. I have tried 1.4.0 (from website) and 1.4.1 (from github source) as well.
|
same error here $ sudo heimdall download-pit --output s.pit --verbose --stdout-errors Initialising connection...
iMan:iProd:iSer: 2:1:3 interface[0].altsetting[0]: num endpoints = 1 interface[1].altsetting[0]: num endpoints = 2 |
Hi, sudo heimdall flash --verbose --recovery recovery.img Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is If you appreciate this software and you would like to support future Initialising connection...
iMan:iProd:iSer: 2:1:3 interface[0].altsetting[0]: num endpoints = 1 interface[1].altsetting[0]: num endpoints = 2 |
Thanks @sanjayankur31, moving to other USB port solved the problem for me. |
Using a different USB port worked for me too :) |
Same trouble. I tried to flash samsung galaxy s2 (i9105) and see the following message:
Tried all my USB ports. Same result. OS Gentoo GNU/Linux, version from upstream. (9999) |
@kozlov-p-v What is you run as root? |
@Benjamin-Dobell yes, sure - I tried from non-root and root user. |
That error is much lower level than Heimdall itself, 110 is a timeout error straight from the Linux kernel. What version of libusb-1.0 is running on your machine? I have seen a few odd reports (although I don't remember where) of certain libusb-1.0 versions not getting on with certain Linux kernel versions. If you're able to try compiling libusb-1.0 yourself and see if the problem persists that would be ideal. |
I have pretty much the same problem please help me ! root# heimdall print-pit --usb-log-level debug Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is If you appreciate this software and you would like to support future Initialising connection... [timestamp] [threadID] facility level [function call][ 0.006118] [000072ee] libusbx: debug [libusb_get_device_list] [ 5.008021] [000072ee] libusbx: debug [libusb_close] And this error log is from version 1.4.0 root# heimdall print-pit --usb-log-level debug Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is If you appreciate this software and you would like to support future Initialising connection... [timestamp] [threadID] facility level [function call][ 0.003373] [000018f5] libusbx: debug [libusb_get_device_list] [ 5.004050] [000018f5] libusbx: debug [libusb_close] |
This might be the same issue as #228. Try my fix with the udev rule. |
Hello. I have a major issue. I was trying to install CWM on my Galaxy Ace 2x using Odin, when something went horribly wrong. Now, my device is bricked, and gives me the following error message when I try to turn it on: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried to fix my device through Kies, but my phone wasn't connecting to it. I don't have access to a PC anymore and am now using a Mac (OS X 10.9.1). I discovered Heimdall, and how it is like a Mac alternative to Odin. I was thrilled that I was finally able to flash my stock ROM, and have my phone back to normal once more. However, whenever I try to download my device's PIT file, I get the following error message:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
ERROR: Setting up interface failed!
Releasing device interface...
Please, someone help me. I have run out of options. I desperately need assistance. :(
Thank you, Eli.
The text was updated successfully, but these errors were encountered: