Hello,
Having issues with heimdall on Ubuntu 12.04.
I was trying to flash ClockworkMODs recovery but i just hit this issue:
Code:
sudo heimdall flash --RECOVERY recovery-clockwork-touch-6.0.3.6-jfltexx.img --no-reboot
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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
Its been a while since i have done this, but i'm sure i have no issues before on this system.
Anyone know what the issue is?
I don't know what the issue is, but version 1.3.2 of Heimdall worked. I think the issue is in the latest version of heimdall somehow. The error thrown by libusb seems to be of the "not supported" type.
[/COLOR]
-=nezero=- said:
Hello,
Having issues with heimdall on Ubuntu 12.04.
I was trying to flash ClockworkMODs recovery but i just hit this issue:
Code:
sudo heimdall flash --RECOVERY recovery-clockwork-touch-6.0.3.6-jfltexx.img --no-reboot
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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
Its been a while since i have done this, but i'm sure i have no issues before on this system.
Anyone know what the issue is?
Click to expand...
Click to collapse
memstick said:
I don't know what the issue is, but version 1.3.2 of Heimdall worked. I think the issue is in the latest version of heimdall somehow. The error thrown by libusb seems to be of the "not supported" type.
Click to expand...
Click to collapse
Hey, I know this thread is somewhat old... But I am running ubuntu 12.04 x64 as well. I only saw 1.3.2 in i386 at the github downloads for heimdall. Did you just install libusb-1.0 i386 as well to get heimdall 1.3.2 to work?
evarInward said:
Hey, I know this thread is somewhat old... But I am running ubuntu 12.04 x64 as well. I only saw 1.3.2 in i386 at the github downloads for heimdall. Did you just install libusb-1.0 i386 as well to get heimdall 1.3.2 to work?
Click to expand...
Click to collapse
Hey guys! Just wanted to let you know that if you are still having this issue, you need to update your kernel. If you are unsure how to do this, just drop me a line and I'll give you some links and info. Just remember to rebuild heimdall and libpit.
similar issue
I think i have a similar problem
i am using heimdall 1.4 on ubuntu 12.04, when i try to flash cwm recovery the program stops at detaching driver and does not even proceed to "Initialising protocol..." in the above image.
using samsung i9082
could someone help please.
yogneo said:
I think i have a similar problem
i am using heimdall 1.4 on ubuntu 12.04, when i try to flash cwm recovery the program stops at detaching driver and does not even proceed to "Initialising protocol..." in the above image.
using samsung i9082
could someone help please.
Click to expand...
Click to collapse
same, same device
sorry but... heimdall, works on i9500?
Related
Hi,
I updated my galaxy note 3 from 4.3 to 4.4.2 (both stock) using heimdall and that went without a hitch, I forgot to wipe all my data so ended up flashing 4.4.2 on top of 4.3 but it works fine with the only difference I see is that my battery leak problem got worse.
I then wanted to install CWM in order to eventually install a custom rom but that got cut short when heimdall (both GUI and on terminal) failed to read my PIT file.
Please note that the phone works and I can go into download mode without a problem and heimdall detects the device but once it starts downloading the PIT i get this:
[email protected]$ heimdall download-pit --output pit4.4.pit
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I am not sure how to proceed, my device is unusable with the horrible battery leak right now.
Thanks
I tried to flash a new Rom but when the installation was over I got stuck in recover, and now Every rom I try to install I get this message:
Skipping MD5 check: no MD5 file found
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error executing updater binary in zip ' /sdcard/Download/cm-11........zip'
Error flashing zip
Please help!!!
I dont know what to do
JJPP35 said:
I tried to flash a new Rom but when the installation was over I got stuck in recover, and now Every rom I try to install I get this message:
Skipping MD5 check: no MD5 file found
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error executing updater binary in zip ' /sdcard/Download/cm-11........zip'
Error flashing zip
Please help!!!
I dont know what to do
Click to expand...
Click to collapse
Had the same problems. I had to flash a man then reroot:good:
verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
getting this error trying to install cm12
any help??
irishboy1234 said:
verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
getting this error trying to install cm12
any help??
Click to expand...
Click to collapse
Redownload the zip. I think it may be corrupted or it did not download entirely.
verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
GALAXY S4 I9500
any help ?
can any onetell me for the error message Error Executing updater binary in zip when i instal any rom
Unable to flash Lumia 920 QHSUSB_DLOAD - Getting "Failed to get response to HELLO_REQ
Hello... So I tried all available HEX/MBN files on my Lumia...
I used the short R3209 resistor method and my computer recognized it as QHSUSB_DLOAD.
Every time I try to flash it, here is what is going on.
Logs:
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode emergency -hexfile "C:\dump\HEX2.hex" -mbnfile "C:\dump\MSIMAGE.mbn" -orig_gpt
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile C:\dump\HEX2.hex -mbnfile C:\dump\MSIMAGE.mbn -orig_gpt
Process started Fri Mar 27 15:55:44 2020
Logging to file C:\Users\gmirz\AppData\Local\Temp\thor2_win_202003 27155544_ThreadId-13272.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Connection to DLOAD mode succeeded
Get Dload parameters
Sending HEX flasher to the device
Sending GO command if HEX flasher successfully uploaded.
Emergency Programmer V1 version 2014.10.31.001
Mbn download selected
Waiting for connection to flash programmer
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 7 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 8 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 9 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 10 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 11 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 12 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 13 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 14 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 15 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 16 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 17 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 18 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 19 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 20 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 21 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 22 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 23 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 24 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 25 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 26 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 27 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 28 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 29 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 30 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 31 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 32 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 33 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 34 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 35 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 36 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 37 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 38 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 39 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 40 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 41 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 42 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 43 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 44 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 45 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 46 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 47 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 48 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 49 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
and so on... and so on....
Help me please.
I don't think the eMMC is blown.