Hi, on mobile i enter to download mode and on pc in terminal i run following command
Code:
sudo heimdall flash --recovery recovery.img --no-reboot
but error occurred:
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, 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...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
Related
I would like install Cyanogenmod 10.1 on my i9000. I installed on my Ubuntu 12.04 heimdall 1.4 deb (for Ubuntu 12.10).
The guide is tho official guide on wiki's Cyanogenmod: wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
1. Download Semaphore's ClockworkMod Recovery, and the Heimdall Suite:
2.Power off the Galaxy S and connect the USB adapter to the computer but not to the Galaxy S.
3.Now boot the Galaxy S into download mode by holding down Home & Volume Down. Accept the disclaimer. After this insert the USB cable into the device.
4.Place Semaphore's ClockworkMod Recovery file into the Heimdall directory.
5.On the computer, open a terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage --no-reboot
When I try to apply the kernel, this is the answer:
Code:
[email protected]:~$ sudo heimdall flash --kernel zImage --no-reboot
[sudo] password for domenico:
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...
PIT file download successful.
ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
Releasing device interface...
[email protected]:~$
What's up? Where I'm wrong?
Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot
whetu said:
Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot
Click to expand...
Click to collapse
THANKS!!!
How to open a terminal??
Hi
Please help! On the computer; How to open a terminal and run command...??
Thanks in advance
whetu said:
Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot
Click to expand...
Click to collapse
Yes it worked
Thanks mutch
[Q] ERROR: Partition "factoryfs" does not exist in the specified PIT. [SOLVED]
Code:
K:\GT-19000\HEIMDALL\Heimdall Suite 1>heimdall flash --repartition --pit m110s.p
it --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boo
t boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem mo
dem.bin
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...
libusbx: error [cache_config_descriptors] unexpected configuration descriptor si
ze (actual) for '\\.\USB#VID_0000&PID_0538#5&ED9EEE6&1&1'.
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.
ERROR: Partition "factoryfs" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
I tried this method to flash eclair back on my m110s. I am currently running cm7. But it gives above error. The flashing works fine using Odin but causing my baseband/imei missing. Any idea why?
EDIT: LOL, I guess Uppercase matters in windows compared to linux.
I am attempting to use Heimdall (with the S5 patch) with my Note 4 in Xubuntu 14.10, but I keep getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
In a clean install of Xubuntu 14.10 I did the following:
Code:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-uprade -y
sudo apt-get install android-tools-adb build-essential git libudev-dev pkg-config zlib1g-dev
sudo wget https://raw.githubusercontent.com/snowdream/51-android/master/51-android.rules -O /etc/udev/rules.d/51-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo service udev restart
mkdir ~/.source
cd ~/.source
wget 'http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.19/libusb-1.0.19.tar.bz2'
tar -vxjf libusb-1.0.19.tar.bz2
rm libusb-1.0.19.tar.bz2
cd libusb-1.0.19
./configure
make
sudo make install
cd ~/.source
git clone https://github.com/sshimko/Heimdall.git --branch gs5 --single-branch heimdall-gs5
cd heimdall-gs5/libpit
./configure
make
cd ../heimdall
./configure
make
sudo make install
sudo udevadm control --reload-rules
adb reboot download
heimdall print-pit --verbose
Here is the result of "heimdall print-pit --verbose":
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Does anyone who has been able to use Heimdall with the Note 4 in Linux have any suggestions as to how I can get this setup correctly?
Thanks.
I had the same results with https://github.com/karabijavad/Heimdall/tree/issue-197 and https://github.com/Benjamin-Dobell/Heimdall/issues/232.
Did you ever figure this out? I'm getting the same "Failed to send request to end PIT file transfer!" error.
As far as i I know, there's only so much heimdall can do. I've only had success on windows for flashing the full firmware. I'm on Linux mint and I'm still not sure. You could try jodin on this site. It's a web based Odin.
Jodin uses Heimdall, so it doesn't fix the problem. On windows I couldn't get the stupid Samsung drivers to work.
Sent from my SM-N910T using XDA Free mobile app
DieHappy said:
I am attempting to use Heimdall (with the S5 patch) with my Note 4 in Xubuntu 14.10, but I keep getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
In a clean install of Xubuntu 14.10 I did the following:
Code:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-uprade -y
sudo apt-get install android-tools-adb build-essential git libudev-dev pkg-config zlib1g-dev
sudo wget https://raw.githubusercontent.com/snowdream/51-android/master/51-android.rules -O /etc/udev/rules.d/51-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo service udev restart
mkdir ~/.source
cd ~/.source
wget 'http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.19/libusb-1.0.19.tar.bz2'
tar -vxjf libusb-1.0.19.tar.bz2
rm libusb-1.0.19.tar.bz2
cd libusb-1.0.19
./configure
make
sudo make install
cd ~/.source
git clone https://github.com/sshimko/Heimdall.git --branch gs5 --single-branch heimdall-gs5
cd heimdall-gs5/libpit
./configure
make
cd ../heimdall
./configure
make
sudo make install
sudo udevadm control --reload-rules
adb reboot download
heimdall print-pit --verbose
Here is the result of "heimdall print-pit --verbose":
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Does anyone who has been able to use Heimdall with the Note 4 in Linux have any suggestions as to how I can get this setup correctly?
Thanks.
Click to expand...
Click to collapse
Did you put it to work?
BR
I have not been able to get it to work with my Note 4.
Sent from my SM-N910T using XDA Free mobile app
I am currently running into the same problems as well
Nobody has a fix yet.
[Q&A] [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Avai
Q&A for [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Flashing ROM from Mac OS X
Hi,
I tried to flash a ROM (recovery.img) using heimdall command line, I tried with the following command
Code:
sudo heimdall flash --recovery filename.img --no-reboot
The device in download mode got detected, then it says Initializing Protocal. after that I got "Error: failed to send data, releasing device interface"
Any solutions or help, regarding this.
jvigneshcs said:
Hi,
I tried to flash a ROM (recovery.img) using heimdall command line, I tried with the following command
Code:
sudo heimdall flash --recovery filename.img --no-reboot
The device in download mode got detected, then it says Initializing Protocal. after that I got "Error: failed to send data, releasing device interface"
Any solutions or help, regarding this.
Click to expand...
Click to collapse
You didn't mention the device details, i9000? Heimdall 1.4.0 worked with my newer Samsung devices, but there I had to type --RECOVERY instead of --recovery.
It hasn't worked for my i9000 (Ubuntu 12.04 32-bit)
For my old Samsung i9000 (S1) I had to uninstall Heimdall 1.4.0 and install Heimdall 1.3.1
Your typing style would perfectly fit there.
tetakpatalked from Nexus 7 flo
tetakpatak said:
You didn't mention the device details, i9000? Heimdall 1.4.0 worked with my newer Samsung devices, but there I had to type --RECOVERY instead of --recovery.
It hasn't worked for my i9000 (Ubuntu 12.04 32-bit)
For my old Samsung i9000 (S1) I had to uninstall Heimdall 1.4.0 and install Heimdall 1.3.1
Your typing style would perfectly fit there.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thanks for you response. I tried with my Samsung Galaxy Grand Duos GT-I9082 with suitable recovery.img.
Later I installed using Odin from Windows machine.
Successfully tested on Samsung Galaxy S4 Active (GT-I9295)
The frontend sucks But after some research I understood the logic and managed to (re-)flash my phone with I9295XXUCNH2 . I didn't need to repartition and had a valid .pit file on the phone, so it is pretty straightforward:
Code:
sudo heimdall flash --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img --HIDDEN hidden.img.ext4
Cannot load PIT from S3 Neo
Hi,
I want to root my i9301. This requires odin... Since I am on linux, I tried Heimdall. But I fail already downloading the PIT file.
Looks like usb problems, any idea?
Code:
Heimdall v1.4.1
...
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
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...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
tried i8730 using same cable at motherboard usb port.
worked fine with "WARNING: Empty bulk transfer after sending packet failed. Continuing anyway..."
Ubuntu 16.04 Kernel 4.4.0-34-generic
thanks
Edit: solved, used odin on windows instead.
Hello to all ,
i am trying to get lineageOS on my galaxy s5 active, SM G870-A phone but i stuck on the very beginning with heimdall. Here what i see on terminal console(Ubuntu 18.04.2 LTS) Can anyone help?
[email protected]:~$ heimdall print-pit
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
[email protected]:~$