yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] gehzumteufel:
Just IGNORE that post. The fix is to install the QT Framework. Nothing more, nothing less. This makes it extremely easy. No modification of anything. Just install and it's fixed.
[Galaxy S I9000 Android Development] HeisRisen:
Perhaps you can make a youtube video on how to do just that.
[Galaxy S I9000 Android Development] titooo7:
thanks mate but... where can i download qt framework? :D
[Galaxy S I9000 Android Development] gehzumteufel:
I'm mobile so I don't have the link handy, but I did link to it a few pages back.
[Galaxy S I9000 Android Development] fotoflo:
Hemidall force quits on launch, mac version

Hi,

Just downloaded the newest version of hemidall yesterday (first time install) and after running the installer and rebooting hemidall front end wont launch.

Helow is the information provided by the problem report. let me know if i can be of any more help/how we can fix this.

Looks like it's not loading QtGui.framework/Versions/4/QtGui - is it just my system that doesnt have this? where should i get it?

Process: heimdall-frontend [11994]

Path: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend

Identifier: com.yourcompany.heimdall-frontend

Version: ??? (???)

Code Type: X86 (Native)

Parent Process: launchd [203]

Date/Time: 2011-03-15 08:00:54.824 +0800

OS Version: Mac OS X 10.6.6 (10J567)

Report Version: 6

Interval Since Last Report: 159090 sec

Crashes Since Last Report: 7

Per-App Crashes Since Last Report: 7

Anonymous UUID: A244B10F-CFB1-45E3-A124-C52EB321712A

Exception Type: EXC_BREAKPOINT (SIGTRAP)

Exception Codes: 0x0000000000000002, 0x0000000000000000

Crashed Thread: 0

Dyld Error Message:

Library not loaded: QtGui.framework/Versions/4/QtGui

Referenced from: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend

Reason: image not found

Binary Images:

0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <A4F6ADCC-6448-37B4-ED6C-ABB2CD06F448> /usr/lib/dyld
[Galaxy S I9000 Android Development] skorianez:
Hi developer,

How about create a Personal Package Archives(ppa) for Ubuntu?

https://help.launchpad.net/Packaging/PPA
[Galaxy S I9000 Android Development] Benjamin Dobell:
I'll look into it.

Qt can be downloaded here. There is also a work-around detailed a few pages back within this thread.
[Galaxy S I9000 Android Development] fotoflo:
QT

Thank you.

But you might want to check if the user has QT and then ask them to download it if they dont, instead of crashing.

best,

fotoflo
[Galaxy S I9000 Android Development] fotoflo:
QT

it looks like QT is a development framework & sdk. There are no binaries available for consumers - or at least i didnt see anything like like that in my quick perusal of the qt site.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Haha, yeah it's not meant to crash. In fact Qt is already included (as a private framework) when you download Heimdall Frontend. However there is some weird issue whereby OS X is not able to find private frameworks (and hence Qt).

That is correct, go with the library only release. If you want to avoid downloading Qt then take a look at the fix a few pages back, it's simply a work-around that allows OS X to find the private framework Qt at run-time, so no need to download anything.
[Galaxy S I9000 Android Development] thecrucible:
Hi guys, I tried flashing with Heimdall on my Macbook Pro however when I click the start button I get the following error message, dyld: unknown required load command 0x80000022

I followed the instructions in the OP and extracted the individual files from the .tar and slotted them into the appropriate place in the front end app.
[Galaxy S I9000 Android Development] Benjamin Dobell:
You're running OS X on your Macbook Pro? I'm not entirely sure what that error is given that the user interface displayed correctly, perhaps Heimdall Frontend is unable to find the heimdall binary. Are you able to run Heimdall from terminal?
[Galaxy S I9000 Android Development] thecrucible:
Yes, currently running OS X 10.5.8. I just tried launching Heimdall from terminal and was successful but the issue still persists. Actually I was always able to open the application but it was just that each attempt to initiate the flashing process resulted in that error message.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Are you able to run heimdall command line tool from the terminal? Have a look at the README for basic documentation.
[Galaxy S I9000 Android Development] agsded:
I really dig how granular this tool is than flashing my galaxy s with Odin.

I noticed that the froyo roms, however, have an extra file, movinand.bin. at least the Samsung fascinate ones do. Any ideas what it is, and/or it would create a problem as heimdall has no box for that file.
[Galaxy S I9000 Android Development] steelechamp:
I am using a Samsung Captivate running on Firefly 2.6 and for some reason it says my device is undetectable. WHats the fix for this? I dont have access to Odin(on a mac) and I really would like to use this to install the MIUI Captivate (Gingerbread) Build.
[Galaxy S I9000 Android Development] alex6999:
Is it safe to flush bootloader with odin if I install heimdall driver?

I don't want to play, post instruction says flush tar with odin.

I going to change boot logo
[Galaxy S I9000 Android Development] agsded:
If you extract the tar, out comes all the bin files for heimdall to use. The advantage you have with heimdall is you can extract the red cwm recovery tar and use that recovery.bin..... and once you have your hacked param flashed and logo uploaded....any time you need to fix a brick where you'd go to Odin, you can instead use heimdall and flash just the elements you need....ie, skipping the param file to keep from loosing your custom logo, and skip the recovery.bin to keep from overwriting your custom recovery. Heimdall param more granular.....Odin is a big all in one lump....heimdall is elegant....lets you fix what's broken without the need to totally wipe to bone stock unless that is how far you NEED to go....

Just my 2 cents worth
[Galaxy S I9000 Android Development] v1nsai:
I hate asking because I know it's probably been mentioned somewhere, but where the hell can I download the Captivate JF6 firmware (which is what Odin flashes). I've tried extracting it from Odin and Bay_Wolf's AIO captivate toolbox, but the bay_wolf toolbox is missing sbl.bin and I can't crack Odin open with any of the tools I've used. I've been all over the forums and www.samfirmwares.com and Google and just.....dammit I'm stumped. Would really like to help try this software out it looks great, seems like I'm the only one that can't find this though it's probably somewhere really obvious -_-
[Galaxy S I9000 Android Development] agsded:
I've had good success at least on PC with extracting tar files using winrar....
[Galaxy S I9000 Android Development] v1nsai:
As long as its a valid tar file, you should always have "good success" with winrar. But I'm asking where to actually get the firmware file for captivate JF6.
[Galaxy S I9000 Android Development] JamalWallace:
Hi! Trying to flash a new kernel on my Galaxy S but getting this error:

unknown required load command 0x80000022

Tried also (looks like that other people got the same error):

heimdall close-pc-screen

dyld: unknown required load command 0x80000022

Trace/BPT trap

Running OSX Leopard 10.5.8

Thank's.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Hmm, that's not good. Are you booted in 64-bit mode or just standard 32-bit?
[Galaxy S I9000 Android Development] JamalWallace:
I would say 32bit as I didn't touch anything... Is there anything that I can do to confirm that?
[Galaxy S I9000 Android Development] zurchpet:
Question. heimdall for Mac does not work on 64-bit kernel, right?

It works fine on my MB white (kernel in 32-bit mode) but on the MBP (kernel in 64-bit mode) it fails on handshaking with Loke.
[Galaxy S I9000 Android Development] Benjamin Dobell:
If you didn't touch anything then it will be 32-bit. I'm really not sure what the problem is. That error is a linking error which makes me think Heimdall can't find libusb-1.0, however I can't see why that would be the case.

The only two things I can think of are:

1. Try download and install libusb-1.0 from somewhere else (you'll need version 1.0.8 or later).

2. Try download and compile Heimdall. The README includes instructions but you must have XCode installed. Heimdall Frontend also won't compile without the Qt SDK, however if you're happy to use the command line tool then there's no need to compile it.

It should actually work fine on all versions of OS X, however I haven't tested it on 64-bit OS X. The binaries distributed are universal and should work on x86, AMD64 and PPC architectures.

If it's failing on your 64-bit machine would you be able to run the command line tool with the --verbose parameter and e-mail the output to service [_at_] glassechidna.com.au?
[Galaxy S I9000 Android Development] prokla:
Whi I can't see download link ?
[Galaxy S I9000 Android Development] nai3660:
thank you :)
[Galaxy S I9000 Android Development] Manadar:
Hi I'm looking for any update that would help me see my I9000 in Heimdall when connecting it in DL mode. I don't have windows at home so I would love being able to use your soft :)

I'm running osX 10.6.6 atm.
[Galaxy S I9000 Android Development] gehzumteufel:
You need to make sure you have the right bootloader. Otherwise, it won't work.
[Galaxy S I9000 Android Development] Manadar:
Allright, I tried to understand what you said by searching this thread.

Therefore I must find primary and secondary bootloaders from a "good" rom and add them in heimdall so as to see my phone when I connect it?
[Galaxy S I9000 Android Development] gehzumteufel:
You shouldn't need the PBL. Just the SBL. The PBL is the most rarely updated bootloader for these devices, and you should avoid mucking with it, unless absolutely necessary. It's possible to break the SBL, and still be able to recover, however it is impossible (for us anyway) to fix the device without JTAG if you break the PBL.
[Galaxy S I9000 Android Development] ashwinds:
On 64 bit, while loading the kext, I get the error below:

sh-3.2# kextutil /System/Library/Extensions/heimdall.kext

/System/Library/Extensions/heimdall.kext has problems:

Warnings:

Personality CFBundleIdentifier differs from containing kext's (not necessarily a mistake, but rarely done):

GalaxyS

Dependency Resolution Failures:

64-bit kexts must use com.apple.kpi.* libraries, not com.apple.kernel* libraries.
[Galaxy S I9000 Android Development] AlexandreT:
Has anybody with JVK (2.3.3) been able to correctly flash anything with heimdall? Are the new bootloaders recognized?

I'm running osx and I installed everything right, including qt, but it just failed flashing a kernel. Inclusively it made the phone loose recovery access (download mode was still available) and had to go back to Odin in my windows laptop. I'm guessing these new bootloaders are not well recognized by heimdall.
[Galaxy S I9000 Android Development] zurchpet:
They work flawlessly for me... Used Heimdall on Windows 7 64-Bit via Parallels Desktop.
[Galaxy S I9000 Android Development] gehzumteufel:
He is referring to the native Mac port. Big difference.
[Galaxy S I9000 Android Development] Xacky:
The website is down?

Also the PPA: doesn´t seem to work?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Hmm someone else reported it went down also. I didn't even notice :P Either way it's up again now.

I haven't made a PPA release myself, if you're using a PPA then that's done by a third party, that's fine but I can't really help you out there.
[Galaxy S I9000 Android Development] AlexandreT:
So, has nobody else used Heimdall with JVK (2.3.3) bootloaders in OSX? To the Dev., a previous user claimed that JVK bootloaders were well recognized in the Windows version. Should windows and OSX versions be expected to behave the same?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Unfortunately no. Perhaps the new bootloader fixes the problem, however the issue in the past is that the secondary bootloader is not USB standard complaint.

It just so happens that Windows performs the exact same process every time you connect a USB device. This process is simply one possible way to interact with USB devices and the USB specification allows this to be varied slightly. As a result Samsung just ignore the data sent to the Galaxy S' USB port because they assume it will always be the same. On Linux the process just so happens to be done the same way as in Windows so it works. However OS X actually tries to be slightly more economic in its communication, as a result the Galaxy S starts sending incorrect information and OS X tries to recover by asking for the data in a different way but instead the Galaxy S just responds with more junk data so OS X gives up :P
[Galaxy S I9000 Android Development] AlexandreT:
So, does this mean that probably JVK new bootloaders really aren't working with Heimdall in OSX? Anybody else care to try?

Is there anyway we can circumvent this problem in OSX?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Well, it is possible they do work. Samsung have sporadically released working secondary bootloaders for OS X in the past, take a look at the link in my signature for details. I just meant that because the phone is well recognised in Windows doesn't necessarily hold true for OS X.

There actually theoretically is a way around this. The apple IOUSBFamily drivers are open-source. Someone could theoretically release a customised version that makes OS X operate in the same fashion as Windows. In fact the IOUSBFamily source does contain certain hacks for particularly note-worthy devices that Apple obviously wanted working. However I chose not to take this route as it's far more trouble than it's worth trying to compile and distribute various compilations for different versions of OS X. The correct way to make devices function with OS X is traditionally to provide a kext file not modify the way the USB stack functions.

Perhaps if enough of you are to report it as a bug to Apple (even though it's not Apple's fault) then Apple would make changes available as a service pack. Although I wouldn't count on it.
[Galaxy S I9000 Android Development] imkr1:
Hi there,

Can you give me any file link which i could get 2e recovery by using Heimdall?

Thanks
[Galaxy S I9000 Android Development] gehzumteufel:
The type of recovery has no relation nor anything to do with Heimdall. This tool is nothing more than an Odin replacement.
[Galaxy S I9000 Android Development] spiritssight:
Tab Fail

Hello Folks,

I am wondering what I can do, when I put my Galaxy Tab (AT&T) into download mode then connect to Heidall (Ubuntu) it says it fails at handshake with Loke, what could be the cause of this? I just got done doing this with my Cappy and it worked perfect.

Is there something I can do to see more information that would help with resolving this issue?

Thanks in Advance.

God Bless,

Christopher
[Galaxy S I9000 Android Development] imkr1:
Yes i know, but since Odin didn't recognize my phone I can't root my device to install Custom ROM, so can you please tell me how to root my SGS XXJPY 2.2.1 using Heimdall?

Thanks
[Galaxy S I9000 Android Development] imkr1:
When i try to flash new ROM through Heimdall, after i pressed "Start"

It said " Failed to access device. Error:-12

So what does it mean??? Please help!!
[Galaxy S I9000 Android Development] Benjamin Dobell:
Windows I presume? If so this error probably means you've not installed the drivers correctly.
[Galaxy S I9000 Android Development] LiberatorUSA:
DK28 USB trouble

Hi,

I have USB trouble on my phone,.. its dead as dead can be.

Now I read about your tool and figured I could do the following:

Use the Zadig tool to install a different USB driver using my wife's Epic which still has a working USB

1) try if Zadig can see my Epic4G somehow (DK28),.. Failed

2) try if Zadig can see my wife's Epic4G (EC05),.. It sees an unknown device with vendor ID 0000 and product ID 0000.

3) Tried installing in Zadig with my wife's epic attached,.. failed

4) Tried altering name unknown to the string posted... made no difference,.. failed.

Any tips on how to get this Zadig tool to work?

Based on discussion here:

http://xdaforums.com/showthread.php?p=12772632#post12772632
[Galaxy S I9000 Android Development] ravi84m:
Cool. I just added the ppa and now I enjoy flashing via my ubuntu terminal.
[Galaxy S I9000 Android Development] EasyAndy:
The page where haimdall is located is not a valid web site and I cant find the program any where else on the internet. Please help me get the latest copy of haimdall as my verizon galaxy tab is bricked and I think this is the only method I can use to recover form my brick.

Thanks,

Andy
[Galaxy S I9000 Android Development] zurchpet:
http://nobrain.ch/files/heimdall-suite-1.1.1-win32.zip

:)
[Galaxy S I9000 Android Development] Xerfas:
So what does this mean?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Umm, it means what it says :P

Please explain what you don't understand so I can elaborate on anything that isn't clear.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Doh! Someone could have told me my donate link both here and on the Glass Echidna website was broken :( I thought it was weird that Heimdall has been downloaded over 30,000 times (from official mirrors alone) in the last couple of months but we haven't received a single donation.

The problem is PayPal, being the idiots they are, have suspended my PayPal account. I was aware of this and have been attempting to get it resolved for months now. However I was under the impression I simply couldn't withdraw from the account, I didn't realise no-one could donate.

The reason PayPal suspended my account is because they wanted me to provide evidence that I'm registered as a Non-Profit company. Which I'm not, nor does my account say anywhere that I am. They still haven't really acknowledged this fact but they are insistent that you must be a registered non-profit company to take donations, despite the fact they tried this exact same stunt with TortoiseSVN and in the end admitted their mistake. Anyway according to PayPal's staff (but not their Terms of Service) every single one of the "Donate to me" links on this website is invalid. So if you'd all like to chime in by sending PayPal a bunch of abusive e-mails that would be great, spread the word too.

Anyway, as a temporary work-around I've linked the donate buttons to my personal PayPal account, until they suspend that too. If you'd attempted to donate in the last couple of months and it didn't work, then please feel free to try again ;)

EDIT: For those of you in Australia the e-mail address you should use to contact PayPal is aucr@paypal.com.

EDIT 2: I started a thread in general about this.
[Galaxy S I9000 Android Development] toansta:
@Benjamin, hey ben nice program.

can you help me, i've finally got the front end to work on my mac after i installed QT but thats as far as i can go.

when i plug my phone in (download mode) and click start with everything that i want to flash it just comes up as failed.

i'm sure it's something stupid that i've missed but i have no idea how to fix this.

sorry man i've been using odin for too long this is so new to me

thanks in advance,

toansta
[Galaxy S I9000 Android Development] Benjamin Dobell:
Does it say "failed to detect compatible device"? If so this is likely a result of a faulty secondary bootloader, see the link in my signature about OS X secondary bootloaders.

If that's not the error, could you please try entering the following in a terminal (with your device connected in download mode) and let me know what the output is:
[Galaxy S I9000 Android Development] Xerfas:
Sorry I didn't read the answer as I should have done the first time. Now I understand a bit more I think.
[Galaxy S I9000 Android Development] cornholio_rules:
Error -7 ?

Hi Benjamin, congrats for your excellent program.

Do you know why I can't complete uploading Sbl.bin with Heimdall? It seems everything goes ok except for the secondary bootloader. Odin also fails. I use Windows 7 64. SGS I9000T.

Here's the verbose:

Product: "Gadget Serial"

Serial No: "?"

length: 18

device class: 2

S/N: 0

VID:PID: 04E8:6601

bcdDevice: 021B

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: 83

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: 02

max packet size: 0200

polling interval: 00

Claiming interface... Success

Setting up interface... Success

Beginning session...

Handshaking with Loke... Success

Uploading primary bootloader

0%File Part #0... Response: 0 0 0 0 0 0 0 0

File Part #1... Response: 0 0 0 0 1 0 0 0

Primary bootloader upload successful

Uploading secondary bootloader

0%File Part #0... Response: 0 0 0 0 0 0 0 0

File Part #1... Response: 0 0 0 0 1 0 0 0

File Part #2... Response: 0 0 0 0 2 0 0 0

File Part #3... Response: 0 0 0 0 3 0 0 0

File Part #4... Response: 0 0 0 0 4 0 0 0

File Part #5... Response: 0 0 0 0 5 0 0 0

File Part #6... Response: 0 0 0 0 6 0 0 0

File Part #7... Response: 0 0 0 0 7 0 0 0

File Part #8... Response: 0 0 0 0 8 0 0 0

File Part #9... Response: 0 0 0 0 9 0 0 0

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet.

Failed to confirm end of file transfer sequence!

Secondary bootloader upload failed!
[Galaxy S I9000 Android Development] Benjamin Dobell:
I'm unsure exactly why your device doesn't respond when confirming the end of the secondary bootloader file transfer sequence. However users have had similar problems before with other devices, in particular Galaxy Tabs. In the end users seem to be able to get it to work by messing around, repartitioning etc. until it finally works. I don't necessarily recommend this, especially if you want to keep your data. However as far as a I can tell the problem is caused by certain secondary bootloaders running on devices. These secondary bootloaders seem to not want to be replaced!

Other than this being some obscure feature of certain secondary bootloaders. All I can really think of is that perhaps Samsung have slightly changed the way in which a secondary bootloader is flashed, when your current secondary bootloader is installed on the device. The only way I'd really be able to find out is by trial and error (not necessarily good for the livelihood of my device), or if I had a LOT of free time, reverse engineering Sbl.bin itself.

Personally I'd absolutely love to reverse-engineer Sbl.bin. Unfortunately, monetarily speaking, I can't afford to take any more time away from my professional free-lance jobs at the moment.
[Galaxy S I9000 Android Development] toansta:
i typed what you said into terminal and this is what i got

Manufacturer: "SAMSUNG"

Product: "Gadget Serial"

Serial No: "?"

length: 18

device class: 2

S/N: 0

VID:PID: 04E8:6601

bcdDevice: 021B

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: 83

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: 02

max packet size: 0200

polling interval: 00

Claiming interface... Success

Setting up interface... Success

Beginning session...

Handshaking with Loke... Success

Attempting to close connect to pc screen...

Ending session...

Failed to receive session end confirmation!

i guess the problem is the wrong bootloader? i'm trying to use it with JVB by the way

but yesterday i was trying to flash JP5 to restore everything fresh again.

possibly it may work if i had started with a proper FW first?

thanks for the help though