ERROR: libusb error -7 whilst receiving bulk transfer #414
Comments
|
Can you try again and post the complete log including the command that you entered. The fact that you are getting the PIT is a good sign. Have you tried actually flashing the recovery image? I would try with a USB2 port. |
|
Did this actually work??? |
|
Very strange. It does indeed look like it completed the transfer as it managed to get to 100% but whether the phone accepted it is uncertain because it showed that the upload failed. It smells of a usb setup problem, I recommend building libusb from source, get it from https://sourceforge.net/projects/libusb/files/ Also, if you are using --no-reboot then remember to use --resume on the next command otherwise you will experience problems. |
|
PS: I notice that you are trying to install an hlte file on an hltevzw device, if your original post is correct, download the correct image from https://twrp.me/devices/samsunggalaxynote3verizon.html |
|
Whilst I am waiting for the dist-upgrade to get deps for libusb... Less joy than the first time. Thanks fo rhte heads up. I was looking at lineageos and they seemed to think that was the twrp to get.. hope I havn't bricked it 8) I guess it may be because I didnt o a |
|
If you did not use --resume then you must reboot the phone before trying again. I never use --no-reboot as it always seems to cause me problems but I guess that you have no choice if you are working remotely. Get someone local to the device to reboot it back into bootloader mode. |
|
aaah crap. TO make life easy for me, can you please instruct as to how to build an isolated version of libusb and use this with Heimdall. Ubuntu has too many dependencies on |
|
Before trying that, did you reboot the phone and try flashing without --no-reboot? I shall be back after sleep zzzzz.... |
|
Yes. Cheers for the help @JonnyTech |
|
I cheated and just ripped libusb-1.0-0 out with dpkg --force-all... still the same errors and less progress than before again... |
|
Recompile Heimdall after replacing libusb. Keep the command line simple. Reboot both phone and computer then try: If that does not work can you explain what you did here:
Heimdall should work as a normal user without any system modification. |
|
I tried all I could With libusb as directed and rebooting every combination.... My friend gave up... maybe he will be back with the phone in a week or so... By changing permissions i mean Where the device is what heimdall reports that it does not have permission to write to. |
|
Thanks for replying - hopefully you can try the device locally next time too... |
|
I'm having exactly the same issue in Parabola GNU/Linux-libre (Arch-based, the heimdall pkg comes from Arch). |
|
I ran into this error using Heimdall 4.1.2 with an I9105P device # heimdall print-pit --verbose --no-reboot --resume [...] Beginning session... ERROR: libusb error -7 whilst receiving bulk transfer. Retrying... Without # heimdall print-pit --verbose --no-reboot
[...]
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
PIT file download successful.
[...]
Note that with the Initialising protocol... ERROR: Failed to receive handshake response. Result: -7 ERROR: Protocol initialisation failed! |
|
Hi, For example herolte (Galaxy S7) need this command to install twrp : Problem is identical when you pass 2 commands without reboot : first pass, second fails. Context :LINUX : I Attach files from 2 print-pit commands, and their equivalents including debug messages first_print-pit.log Command used are : Thx, |
|
I duplicated this same issue on two separate Samsung Galaxy Note 4 phones. Compiled 1.4.2 on Ubuntu 16.04 today. Just trying to print the PIT results in: The boot sequence following this shows: I'm willing to test potential code fixes. |
|
I'll have same problem ERROR: libusb error -7 whilst receiving bulk transfer. Retrying... on my Tab S5e. [ |
|
Hi,
As I can remember, debian package didn't work and I compiled heimdall from github sources. I had to unplug usb, reboot in download mode and re-plug usb cable, before launching another heimdall command. And after flashing recovery, you have to boot in recovery mode before a normal boot. |
Only unplug and replug usb cable works fine with --resume. |
|
I test that with --resume and with replug cable with no other result. I can't see any difference between first or following commands. I would assume something's wrong with my device, but adb sideload (when in TWRP) seems to work. (Linux Mint/CInnamon) |
|
I had this problem with a Galaxy Note 4 (SM-N910F) on Ubuntu 22.04 on a USB 3 port (USB-C to MicroUSB cable, no USB 2 ports available). I could download the PIT but any firmware download failed with this error and the debug log had failures with "urb status -2". I got it to work with:
The full command: |
Compiled from source on Ubuntu 22.04 I get the same error with the distro package. And also if I use the five year old build from https://hub.docker.com/r/groupsky/heimdall Samsung S22 |
|
Hey all, had a big problem flashing a Samsung Galaxy A52s 5G with the exact same error: but solved it by compiling a 2.1.0 version from https://git.sr.ht/~grimler/Heimdall |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am having a similar issue to #413 trying to install TWRP on a Samsung Galaxy Note 3, SM-N900V (Verizon version)
The USB device is USB 3.
I have USB2 devices if this will help.
Original log of trying to flash is gone, but here are the snippets of trying to get the PIT file:
Note: I have changed the permissions fo the USB device so I can perform this as my normal user as I have heard that doing this as root can be problematic.
And my
libusbHeimdall built from git (pulled yesterday), ubuntu 17.04.
The text was updated successfully, but these errors were encountered: