[Q] Heimdall "Handshaking with Loke... Failed" - Galaxy S II Q&A, Help & Troubleshooting

Hey all, sorry I'm not posting this in the Heimdall thread but I don't have enough posts so making a thread here. I've been getting the error "Handshaking with Loke... Failed ERROR: Failed to receive response!"
I'm trying to follow the instructions on the Cyanogenmod wiki for Galaxy S2 but I just cannot flash the kernel. I have flashed an insecure stock kernel to get root in the past using Odin but Heimdall just doesn't want to work.
Any help will really be appreciated, thanks in advance.

---

What OS do you run?
It's necessary to tell, because Heimdall runs on Linux, Windows & OSX.
Sent from my GT-I9100 using XDA App

---

Sorry I forgot to mention, using Windows 7 Ultimate 64-Bit.

---

Did you update the usb drivers using zadig.exe before trying to use Heimdall?

---

yup, updated the usb drivers for both ports I used and checked they were updated even when switching cables etc.

---

So you installed the drivers that come with Heimdall?
Did you make sure that KIES and such our closed?
Did you run as administrator?
A side note:
I can only do one operation at a time. That means that after I downloaded the pit-file I can't flash directly. I have to reboot the phone into download-mode again.
Sent from my GT-I9100 using XDA App

---

willypiggy said:
Hey all, sorry I'm not posting this in the Heimdall thread but I don't have enough posts so making a thread here. I've been getting the error "Handshaking with Loke... Failed ERROR: Failed to receive response!"
I'm trying to follow the instructions on the Cyanogenmod wiki for Galaxy S2 but I just cannot flash the kernel. I have flashed an insecure stock kernel to get root in the past using Odin but Heimdall just doesn't want to work.
Any help will really be appreciated, thanks in advance.
Click to expand...
Click to collapse
I'm using a Mac so i dont know if this will work for you but the CM update guide links to Heimdall 1.3.1 and ive never been able to make it work... what i had to do was install the Heimdall 1.2.0 command line binaries and flash the CM kernel through the Terminal/Command. heres the link for the windows version https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-1.2.0-win32.zip

---

I did install the drivers it came with, Kies was not running, I did run as admin.
I tried 1.2 and it just gives me the error "Failed to open file "zImage""

---

Are you using the Heimdall frontend (like ODIN) or just Heimdall (command line)?
I find the frontend is easy to use if you aren't familiar with using the shell applications... You simply pick the files you need and insert them into the section you want to flash....
Much easier....

---

I'm using the command line as it says in the guide, I'll give it a go using the frontend and see if that comes up with anything different.
EDIT: Trying to use Odin to flash the kernel seems to have worked, my current kernel is now [email protected] #4 but nothing appears to have changed especially that I still can't seem to see a new version of CWM. Should I proceed wit the second part of the tutorial?
EDIT2: Followed the instructions and now have (what seems to be) fully working cyanogen mod. Not sure why on earth the command line method of flashing wasn't working but odin sure did the trick.

---

willypiggy said:
I did install the drivers it came with, Kies was not running, I did run as admin.
I tried 1.2 and it just gives me the error "Failed to open file "zImage""
Click to expand...
Click to collapse
Although you've managed to do the job with ODIN, I think I better tell you what you did wrong with Heimdall.
(On Windows) Heimdall comes with its own drivers. You need to install them. To do so, you use the "zadig.exe" file insode the "..\Heimdall\drivers" folder. You install the driver for "Samsung USB Composite device" or "Gadget Serial". Then it works.

---

TheSniperFan said:
Although you've managed to do the job with ODIN, I think I better tell you what you did wrong with Heimdall.
(On Windows) Heimdall comes with its own drivers. You need to install them. To do so, you use the "zadig.exe" file insode the "..\Heimdall\drivers" folder. You install the driver for "Samsung USB Composite device" or "Gadget Serial". Then it works.
Click to expand...
Click to collapse
Glad Odin did get the job done but I was installing the USB Drivers and I checked and reinstalled them multiple times so it can't be that

---

You need to rollback the usb drivers to successfully use ODIN. If you didn't need to then you didn't successfully install the Heimdall usb drivers...

---

I just instaled this:
Release: Heimdall Suite 1.3.2 (Binaries)
Platforms: OS X 10.4+ (Universal – x86/AMD64/Intel 64)
License: MIT License
Includes:
Heimdall command line tool.
Heimdall Frontend.
Codeless kext (aka driver).
And still getting: "Handshaking with Loke... Failed ERROR: Failed to receive response!".

---

gepardek said:
I just instaled this:
Release: Heimdall Suite 1.3.2 (Binaries)
Platforms: OS X 10.4+ (Universal – x86/AMD64/Intel 64)
License: MIT License
Includes:
Heimdall command line tool.
Heimdall Frontend.
Codeless kext (aka driver).
And still getting: "Handshaking with Loke... Failed ERROR: Failed to receive response!".
Click to expand...
Click to collapse
I know i'm digging up this thread, but i have an answer and a question (relative of course)
ANSWER
I had the same problem. I solved it when i realized that i have had installed Heimdall Suite 1.3.2 (Binaries) (as you did) and also copied (following the directions of a tutorial) the [email protected]/opt/local/lib/.
ALSO after every change, its a MUST to remove the battery (my i9000-international- right now is softbricked thnks to the "swiftness" of my actions ) and reopen the "Download Mode".
QUESTION
As i said i'm using -also- the "Heimdall Suite"; at the "Flash tab" i'm not sure which partitions to associate with which files. I tried to follow the association from the post below, but i couldn't find most of the files the kind dude is proposing.
I'm trying to flash the cm-10.2-20131006-NIGHTLY-galaxysmtd. My phone is a galaxy s1 i9000 international 2.3.6 Android not rooted.
Thank you in advance for any suggestion/advice/curse/direction/documentation
ps: sorry forgot to post the links:
https://gurde.com/2012/08/how-to-install-android-jelly-bean-on-galaxy-s-i9000/#comment-42
http://forum.xda-developers.com/showthread.php?t=2244251

---

Sorry for the second post but great news!!!!
heimdall's (frontend) function "Print PIT" restored my phone from "softbrickness"!!!
Also found what the partition's acronyms at the "Flash" tab of heimdall means:
IBL+PBL is the boot loader, be extra careful with it;
PIT is the partition table;
EFS contains some important data like IEMEI, be extra careful with it;
SBL is the second boot loader;
SBL2 is the backup of the second boot loader;
PARAM contains some images used as various stage of the boot process;
KERNEL is the kernel;
RECOVERY is the backup of the kernel;
FACTORYFS contains /system file system which is some kind of root file system;
DBDATA contains /data file system which is the database to store application parameters;
CACHE contains /cache file system which contains the Dalvik cache;
MODEM contains the firmware for the modem.
Click to expand...
Click to collapse
the relative bin files i've found at the cm-10.2-20131006-NIGHTLY-galaxysmtd rom are:
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/modem.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/de-DE_gl0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/de-DE_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/en-GB_kh0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/en-GB_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/en-US_lh0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/en-US_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/es-ES_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/es-ES_zl0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/fr-FR_nk0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/fr-FR_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/it-IT_cm0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/it-IT_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/vendor/firmware/cypress-touchkey.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/vendor/firmware/fw_bcmdhd.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/vendor/firmware/fw_bcmdhd_apsta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/vendor/firmware/samsung_mfc_fw.bin
Click to expand...
Click to collapse
Also this is my PIT file (in case anyone can give me an insight):
Code:
Entry Count: 13
Unknown 1: 1
Unknown 2: 0
Unknown 3: 7508
Unknown 4: 65
Unknown 5: 64224
Unknown 6: 18
Unknown 7: 55304
Unknown 8: 67
--- Entry #0 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 6684783
Unknown 3: 2097268
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename:
--- Entry #2 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 20
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.rfs
--- Entry #3 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: sbl.bin
--- Entry #4 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 4
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename: sbl.bin
--- Entry #5 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 21
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 22
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1146
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 23
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 0
Unknown 3: 0
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 24
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 140
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 11
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 50
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #12 ---
Unused: Yes
Chip Identifier: 1 ((null))
Partition Identifier: 11
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...

---

reposting just in case somebody knows how to make the file-to-choice association i ask above with the new information i provided.
thank you for your comprehension and sorry for the inconvenience