yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Benjamin Dobell:
Also, as promised, here is a release of the Heimdall Suite for Windows that has been statically linked with the Microsoft Visual C++ 2010 runtimes.

NOTE: Generally you should download the dynamically linked version from the Glass Echidna website and install the MSVC2010 runtimes separately. The above download is only required if you're experiencing problems with the version from my website.
[Galaxy S I9000 Android Development] Matrixxlx:
Forgive my English, I thank you for the work they share, I wanted to better understand the issue of the bootloader, use Mac OS X and then putting RSJP5 ITV official before using Heimdall I should not have problems in subsequent flash ?????

Thanks to all
[Galaxy S I9000 Android Development] Benjamin Dobell:
I'm not sure of exactly which firmware version you will need. However I've started a thread that aims to list all firmware versions that include the fixed Sbl.bin.

If you find a firmware version that includes a fixed secondary bootloader please post in this thread.
[Galaxy S I9000 Android Development] luismanson:
i got auth problem after flashing a too big kernel and trying to flash again

the partition size is on the XDA wiki, im not sure if this is a standar, but a warning wont hatm

your idea of not doing to many checks seems good, but i guess it wont harm some basic stuff

or maybe:

zImage is XX big

systemfs is...

are you sure?

just an idea, i love you app!
[Galaxy S I9000 Android Development] Matrixxlx:
The Journal does not contain I9000RSJP5 Sbl.bin, but it's located in I9000XXJPU ....... so I wanted to know if I have to first put the JPU or Odin or by Kies, Sbl.bin to fix the bootloader, then flash to the next rom with Heimdall .........?????

Now I do a search to see where the bootloader is contained Sbl.bin ....

For now, thanks
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry I don't quite understand what you're asking.

If you're using Windows or Linux then you don't have to worry about the fixed secondary bootloader. If you're using OS X then you will need to install a fixed secondary bootloader (Sbl.bin).

If you do want to use OS X then you have to get the fixed secondary bootloader on your device. You can flash the fixed secondary bootloader onto your device using Heimdall on either Windows or Linux. However just because a firmware includes a file called Sbl.bin doesn't necessarily mean that it is the "fixed version".
[Galaxy S I9000 Android Development] Grsmto:
Mac osX Qt fix included in 1.1.1 doesn't work. We can't run the app.

Edit : The Qt fix can't be unzipped on my macbook ("operation not allowed", first time I get that error on an archive). Heimdall definitely doesn't want me !
[Galaxy S I9000 Android Development] Benjamin Dobell:
You shouldn't need a Qt fix with 1.1.1. The Qt libraries are included as private frameworks, as per Nokia's recommendation. However as I have the Qt SDK installed on my Macbook I'm unable to test if the private frameworks are in fact working.

If Heimdall 1.1.1 isn't working with the private frameworks then you should be able to download the Qt fix for 1.1.0. On the Heimdall product page just scroll down a little way to "Old Releases" and grab the fix from there. Let me know how you go.

Would other OS X users who don't already have Qt installed as shared binaries be able to try out Heimdall Suite 1.1.1 and let me know how you go. It's a bit difficult to diagnose the problem myself, I'll have to try get my hands on a "virgin" Mac.
[Galaxy S I9000 Android Development] [Ramad]:
Moved to the right thread : http://xdaforums.com/showthread.php?p=10262104&posted=1#post10262104
[Galaxy S I9000 Android Development] Grsmto:
yes, It's what I did. I didn't have Qt installed, and the 1.1.1 didn't launch (it's what I tried to explain on my last post lol, but my english is bad).

Now, I downloaded Qt from Nokia website (from here : qt.nokia.com/downloads/qt-for-open-source-cpp-development-on-mac-os-x ) and Heimdall 1.1.1 launch !

So, your "included Qt version" in the 1.1.1 doesn't work.

Note that your Qt fix for 1.1.0 on your website is not working. The archive is undecompressable on my mac.
[Galaxy S I9000 Android Development] oquinones:
Ok so I have a T-Mobile Vibrant that I'm looking to flash the corrected Sbl.bin on Windows so I can access it on the Mac. Is it safe to just extract the corrected Sbl.bin from the official Froyo for I9000 and flash that to my Vibrant or is that a no-no?
[Galaxy S I9000 Android Development] MrFrem82:
Does it had been tested with samsung galaxy 5 (i5500)?
[Galaxy S I9000 Android Development] PAulyhoffman:
I installed on 32bit ubuntu using source and when i open heimdall-front end i get

Xlib: extension "RANDR" missing on display ":0.0".

i can load all the files but the start function doesn't ever show ready?

*edit

I was trying to use a PIT file which would be a repartition and it needs the boot and sbl

i just flashed back to stock via heimdall. Thanks!

now back to perception.
[Galaxy S I9000 Android Development] Benjamin Dobell:
That's a no-no. It might work, however it's a lot more likely to brick your device.

Heimdall is designed for Galaxy S devices, it will not run with older devices as they use an older protocol.

I'm not sure what that warning is all about, probably something Qt related, but I'm glad you got it working.
[Galaxy S I9000 Android Development] .Slane.:
Hi, I've tried Heimdall to flash Speedmod Kernel K12 some days ago and it failed, and the famous "Bricked Screen of Death" appeared. My setup is Windows 7 64bits, international GT-I9000 with Download/Recovery with USB debugging enabled, I've flawlessly flashed 2/3 Samsung ROM and many Speedmod Kernel via Odin3 1.3 without any problem, but as I prefer Open Source Project, I've tried this project. The documentation about flashing in Heimdall is ROM based flash so it need always a PIT file for that, in case of kernel only flash, I've never use a PIT file with Odin, and so I didn't use one with Heimdall (I guess it must be the root of my "Brick state"). As I've forget which PIT I use at last and don't have a good way to see which is used now (perhaps with "df"), if Heimdall need a PIT for kernel, I can't use it before a full flash with repartition. Thankfully, the documentation in Readme are good enough to revert the USB driver, because I was much worried then I see that Odin didn't see my SGS with Heimdall drivers.
[Galaxy S I9000 Android Development] PAulyhoffman:
and it works great. Thank you for an awesome open source tool.

Using the command line and help function is great. i figured it out by reading outcomes with commands.

It is also great that you continue to offer support on this forum. THANKS
[Galaxy S I9000 Android Development] Benjamin Dobell:
What command did you use to flash the kernel? Also what version of Heimdall did you run? Version 1.1.0 onwards does not require you to specify a PIT file in order to flash, except when repartitioning. A PIT file is only required for version 1.0.0, but it should not allow you to flash without one.

A couple of days ago I wrote a simple command line program to extract data from PIT files. Now that I know exactly what a PIT file contains the next release of Heimdall will take proper notice of PIT files. This should solve any problems non-GT-I9000 users may have been experiencing as a result of different partition IDs.
[Galaxy S I9000 Android Development] .Slane.:
Sorry, I've missed the Heimdall version : it's the 1.1.1
[Galaxy S I9000 Android Development] jamoosy:
just installed it with the mac osx install pkg.

when i try to run the frontend it just crash with an error that goes something like

"heimdall cant open because of a problem"

"please check with developer for further information"

my mac is latest mbp 13" running updated osx 10.6.5

also im afraid just throwing it to the trash wont actually remove all of it out of my mac.

any ideas?
[Galaxy S I9000 Android Development] beaner94:
''bricked'' epic

So I have an epic that i rooted thru the 1 click root method. i attempted to go into recovery. Clockwork was not installed properly (my bad), and ever since I get a black screen after galaxy S boot screen. Ive tried using odin which did nothing for me. While I can get heimdall to flash DG27-8 successfully. I still get the black screen. Ive read I might need to use seperate database data .rfs but havent been able to find one. Ive gone thru the many forums trying to find it. this my las resort. Any help would be greatly appreciated.

thanks in advance guys
[Galaxy S I9000 Android Development] .Slane.:
Perhaps a stupid question but have you revert to Samsung USB driver to use Odin ? With Heimdall USB driver, Odin isn't able to see my SGS, re-installing driver with the method explain in the Readme helped me to de-brick (Phone <-> ! <-> PC) my SGS with a Odin flash.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Wow in trying to find out what files to delete I just found out that the current OS X 1.1.1 package is actually missing the heimdall command line binary (which is required to use the frontend). I don't know if that's the cause of the crash, probably not, but I'll release a new package with it included soon.

Anyway, for some reason OS X doesn't provide a method to uninstall packages. Well it does actually but it is hidden away and there isn't a user interface. It's apparently the "Mac way" to only remove the applications themselves. Personally I would only worry about removing Heimdall Frontend (i.e. drag it to the trash) and I wouldn't bother removing libusb or the kext. However if you really want to delete everything then you need to remove the following:

/usr/local/lib/libusb-1.0.0

/System/Library/Extensions/heimdall.kext

/usr/local/bin/heimdall (it's actually missing in the existing package, see above)

/Applications/heimdall-frontend.app

This isn't really Heimdall related and should be in its own thread. However, have you tried booting into recovery and performing a factory reset? Does samfirmware not include dbdata.rfs? You could try use the dbdata.rfs from a GT-I9000 etc. you will be missing some functionality but you might at least be able to boot.
[Galaxy S I9000 Android Development] Epic800:
I received an error message saying the frontend couldn't open. I am running the latest OSX update and software for Heimdall.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Thanks, another user has filed a detailed bug report, so we're working on it.

A temporary work around is to install Qt from Nokia's website.
[Galaxy S I9000 Android Development] Verysafety:
configure: error: no acceptable C compiler found in $PATH
[Galaxy S I9000 Android Development] Verysafety:
when I run "./configure" in terminal

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for a thread-safe mkdir -p... ./install-sh -c -d

checking for gawk... no

checking for mawk... no

checking for nawk... no

checking for awk... awk

checking whether make sets $(MAKE)... no

checking for gcc... no

checking for cc... no

checking for cl.exe... no

configure: error: in `/Users/kenney/desktop/libusb-1.0.8':

configure: error: no acceptable C compiler found in $PATH
[Galaxy S I9000 Android Development] razze76:
It seems that you don't have the development packages installed. Which OS (and distro) are you running?
[Galaxy S I9000 Android Development] Benjamin Dobell:
razze76 is correct. You'll need to install XCode.

EDIT: That's assuming you're on OS X. If you're using linux something like:

will install gcc etc. You also need pkg-config.
[Galaxy S I9000 Android Development] appagom:
It works on korean galaxy S SHW-M110S in linux. The

handshake response is 190 and must be added to the source code.

I've only tested flashing one kernel, but it worked like a charm. Very nice. I can provide the booted idProduct code too, but it seems this is irrelevant/ in download mode(it is identical to other devices in download mode). I think I may have added it to the source code, but I don't remember and I can't see how it would have done anything, I just added it cause I didn't realize that at first.

edit: compiled from git, downloaded about 5 days ago.

update: Flashed several kernels with this. No problems. Simpler than Odin where you need to know what to tick. Just needs the handshake update for others to be able to use it. Still only tried kernels though.
[Galaxy S I9000 Android Development] ficeto:
Mac OS X frontend issues and fix

Hi all :)

I had problems running the heimdall-frontend on mac which was exiting with the following errors in Console:

12.01.11 14:17:03	[0x0-0x428428].com.yourcompany.heimdall-frontend[14266]	dyld: Library not loaded: QtGui.framework/Versions/4/QtGui
12.01.11 14:17:03	[0x0-0x428428].com.yourcompany.heimdall-frontend[14266]	Referenced from: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend
12.01.11 14:17:03	[0x0-0x428428].com.yourcompany.heimdall-frontend[14266]	Reason: image not found

And to fix this I wrote a really simple bash script to start the GUI

#!/bin/bash
cd '/Applications/heimdall-frontend.app/Contents/Frameworks/'
../MacOS/heimdall-frontend > /dev/null &2>1
exit 0

And now Heimdall's UI starts without problems :)

Edit: if you put this script inside /Applications/heimdall-frontend.app/Contents/MacOS, rename heimdall-frontend to heimdall-frontend-old, then name this script heimdall-frontend and edit the third line to replace heimdall-frontend with heimdall-frontend-old and Heimdall will start normally
[Galaxy S I9000 Android Development] scubabuddha:
I've got a captivate in download mode that Heimdall doesn't see. It's definitely in download mode, and connected over usb to Ubuntu 10.10. Running:

heimdall flash --factoryfs factoryfs.rfs --cache cache.rfs --param param.rfs --kernel zImage --modem modem.bin

returns

"Failed to detect compatible device"

Probably related, running:

./adb kill-server
sudo ./adb usb

returns:

"error: protocol fault (no status)"

Any ideas?
[Galaxy S I9000 Android Development] Benjamin Dobell:
It looks like a problem with the USB connection itself. As such I recommend trying a different port or a USB hub.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry about the delayed responses, I've been a bit busy with work.

When I get a chance I'll be releasing a new version that handles PIT files properly. When I do so I'll add 190 so that SHW-M110S devices work.

Thanks for that. I'm still at a bit of a loss as to why the private frameworks aren't being found normally. If I can't work it out then I'll include this work-around in the next release.
[Galaxy S I9000 Android Development] scubabuddha:
Unlikely... I've tried both ports my laptop and 3 ports on my desktop
[Galaxy S I9000 Android Development] Benjamin Dobell:
Then there is a problem with your particular install of Linux (unlikely) or the phone itself. You're definitely in download mode? You see a little yellow android guy with a shovel?

I'd still guess it's the USB ports on your computer. Dodgy USB ports are not uncommon at all, two of the six my PC has are not particularly reliable.

EDIT: Sorry I originally mentioned OS X instead of Linux.
[Galaxy S I9000 Android Development] appagom:
And cables.. I've had both bad. I think its not always so much broken as just can't handle these devices well. The voltage and current demands arent that low. My Sammy cable is fine.. a much thinner one I have is very marginal. Mice don't tend to have this trouble.
[Galaxy S I9000 Android Development] scubabuddha:
Definitely seeing the droid with the shovel inside a yellow triangle. It says "Downloading... Do not turn off Target!!!"

I believe it's something wrong with the phone. Any idea what specifically could be wrong to cause an error like that?
[Galaxy S I9000 Android Development] iserlohn:
Heimdall version 1.1.1 Fedora 14 SRPM and x86_64 RPM attached.

The SRPM was updated to the latest version and modified to cleanly compile (service udev was causing errors). Worked fine to flash Galaxy Tab on my system.
[Galaxy S I9000 Android Development] 9angled:
heimdall ebuild + frontend problem

+1: heimdall is great, i would havea few other things to add about packaging too:

1, in the makefile for heimdall you do a service udev reload: this only works on ubuntu, please make it optional (i patch it out in my ebuild)

2, the qt frontend doesn't like to be told where to be installed (or i suck at qt4 which is a fact too), can you please tell how to install the app into a directory other than default /usr/local/bin

the ebuild can be found on dev.9souldier.org in the overlay repo's dev-libs directory (can't post links to the forum) but it doesn't install the frontend since i don't know how to change DESTDIR

Thanks
[Galaxy S I9000 Android Development] Logseman:
Hello there, I have a slight problem, and I hope you can solve it.

I installed Heimdall as per the instructions and the CLI runs fine (I could run "heimdall help" with no problems), but I'm not being able to install the frontend. I downloaded QT 4.7 so it's not a Qt issue, I fathom, but then I get the following output when I typed the instructed commands:

$ qmake heimdall-frontend.pro
Failure to open file: /home/logseman/Documentos/Heimdall/heimdall/heimdall-frontend/Makefile
Unable to generate makefile for: heimdall-frontend.pro

I tried to see if it was a permission issue, so I entered on root and I tried again:

# qmake heimdall-frontend.pro
##Nothing appeared, no error like when I tried without root.
# make
/usr/bin/uic-qt4 mainwindow.ui -o GeneratedFiles/ui_mainwindow.h
make: /usr/bin/uic-qt4: Program not found
make: *** [GeneratedFiles/ui_mainwindow.h] Error 127

What is it that I'm doing wrong there? Is there anything I lack? I run the latest version of Heimdall, 1.1.1, and Ubuntu 10.10 Maverick btw.

Thanks in advance,

Logseman
[Galaxy S I9000 Android Development] spiritssight:
Hello Patrik Modesto,

I tryed to use your PPA and it telling me not allowed. any advice would be great. I am using Ubuntu 11.04 however I know if use 10.10 it would work also I think.

Anyhow I am also using 32 bit system.

Thanks for the wonderful work, I don't like windows and don't want to ever have to touch if I can.

God Bless,

Christopher
[Galaxy S I9000 Android Development] jscurtu:
Using 11.04 is the Problem, as it is still in alpha state.... i dont think there are any 11.04 debs yet.?

Also, my advise.. dont flash your device with a unstable OS ...you just never know, all the sudden it goes upps it crashed..

Download his package and install it manual. Not by adding his ppa .

Cheers
[Galaxy S I9000 Android Development] Benjamin Dobell:
Damaged USB port, or USB circuitry perhaps. Or as already suggested, perhaps it's just the cable.

When you say optional what exactly do you mean? How would I go about doing so?

I'm using the variable OUTPUTDIR to set the install path.

An example:

I'm not sure what is going on there. Ubuntu 10.10 and Qt 4.7 is what I use to build the official 64-bit packages available from the Glass Echidna website. Did you compile Qt 4.7 or just download it? To install/compile you should follow these instructions. Although be warned compiling takes around 6 hours!
[Galaxy S I9000 Android Development] Logseman:
I downloaded and ran the bin file which is present in Qt's website, actually this one (I forgot to mention I have a 32-bit architecture): http://qt.nokia.com/downloads/sdk-linux-x11-32bit-cpp

Is that not the installation file I should run? I see no "source file" to compile.
[Galaxy S I9000 Android Development] Benjamin Dobell:
I just downloaded the framework myself:

http://qt.nokia.com/downloads/linux-x11-cpp

However from what I can tell the files you've downloaded should work. Just in case it might be worth recompiling it anyway, the SDK includes the source I believe.
[Galaxy S I9000 Android Development] Logseman:
Compiling Qt and going to sleep. Let's see what the morning brings :D
[Galaxy S I9000 Android Development] DeiphoneaAndroid:
Hello,

i can not make the heimdal 1.1.1 work on a Mac with 10.6.6 . any idea ?
[Galaxy S I9000 Android Development] Benjamin Dobell:
ficeto provided a temporary solution. I'll need to come up with something more permanent but I've been very busy lately focusing on my game engine.
[Galaxy S I9000 Android Development] Logseman:
I couildn't bring to qmake the heimdall-frontend.pro file. Somewhere Qt gets stuck in its compilation. I guess I'll use the CLI.

Thanks for your help!
[Galaxy S I9000 Android Development] Benjamin Dobell:
If you could post the error log that would be great.
[Galaxy S I9000 Android Development] DeiphoneaAndroid:
Hello benjamin,

are you planning to release a new version for MAC 10.6.6 based ?

By now i have it working with the script from ficeto, but just wondering.
[Galaxy S I9000 Android Development] Benjamin Dobell:
When I get a chance I'll release a 1.1.2 version which includes better PIT awareness (particularly relevant for the Galaxy Tab). When I release 1.1.2 I'll try sort out the OS X issues people are seeing.
[Galaxy S I9000 Android Development] JimJam707:
This looks nice :) I'll test it for you with my Samsung Galaxy Spica i5700. I have previously used a version of odin I found in this section of XDA so this might work :D
[Galaxy S I9000 Android Development] Benjamin Dobell:
Heimdall is for the Galaxy S series of Samsung Android devices. It will not work with the Spica i5700 as it uses an older version of the flashing protocol.
[Galaxy S I9000 Android Development] DeiphoneaAndroid:
Thank you, I will look forward for a the new version.
[Galaxy S I9000 Android Development] tbrass:
cova_fe : I, for one, would love to see your ebuild, as my builds keep failing.

Benjamin Dobell -- I can't wait to try out your program. Sounds very promising!
[Galaxy S I9000 Android Development] smithisize:
Hi, I just tried to install on x32 Ubuntu 10.10

I was able to install the app itself, but not the front end. Here is my terminal output:

marcus@marcus-Dell-DV051:~/heimdall-1.1.1/heimdall-frontend$ qmake heimdall-frontend.pro
heimdall-frontend.pro:37: Unknown test function: isEqual
WARNING: Found potential symbol conflict of mainwindow.cpp (Source/mainwindow.cpp) in SOURCES
WARNING: Found potential symbol conflict of mainwindow.h (Source/mainwindow.h) in HEADERS
WARNING: Found potential symbol conflict of aboutform.cpp (Source/aboutform.cpp) in SOURCES
WARNING: Found potential symbol conflict of aboutform.h (Source/aboutform.h) in HEADERS
WARNING: target.path is not defined: install target not created

Ideas?

Regards

Smith
[Galaxy S I9000 Android Development] Logseman:
I'm going to try again today. I'll give you the error log.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Based on that log I'm guessing you're using an old version of qmake, presumably from Qt 3. You need to download the latest version from the official Qt website.
[Galaxy S I9000 Android Development] smithisize:
As in the entire like 500 MB SDK??
[Galaxy S I9000 Android Development] Benjamin Dobell:
The libraries alone will do it, although they're still pretty bloated ~200 MB.
[Galaxy S I9000 Android Development] imkr1:
Hi, I tried to flash to XXJPY with heimdall, but every time i press "Start" I always stuck in 0%.. What is the problem??

I also checked.. Repartition.... Should i uncheck it?
[Galaxy S I9000 Android Development] leventefarkas:
libusb-1.0.3

hi,

does the latest version really not working with libusb 1.0.3 or you just add 1.0.8 as a requirement since it's the latest?

thanks
[Galaxy S I9000 Android Development] imkr1:
Hi, I successfully flashing 2.2.1 XXJPY through Heimdall fronttend but now i can not

root my device with CF-root using odin.. though can i root it through Heimdall ?? and which CF-root file name suit for me? i'm having Gernamy product code, GI9000HKDDBT, PDA:I9000XXJPY, PHONE:I9000XXJP, CSC:I9000XAJPY and Build Info: 2010.12

Thanks,..
[Galaxy S I9000 Android Development] Benjamin Dobell:
I'm not sure why Odin no longer works, it could just be Odin being flaky or perhaps you've installed a protected bootloader.

If you need help about CF-root I recommend asking in a thread relating to CF-root as I don't really know anything about it.