yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] jscurtu:
You have to switch the USB driver back to Samsung driver than odin should work.. you should be able to do that in the device Manager ..

If you unpack cf root (the .tar) than you can root with heimdall too! Just flash the zimage! Thats all....

You will need something like peazip to unpack the .tar file.
[Galaxy S I9000 Android Development] CaracalSef:
I used heimdall to flash first bootloader and second bootloader (to make the 3 buttons combo work) and was just fine. With the drivers installed by this program. Used it to flash cf-root too. It's a nice program :)
[Galaxy S I9000 Android Development] tkienzle:
Hello is there a way to repartition with out using a primary-boot boot.bin i can't seem to locate it for my Samsung Captivate it messed up when i was removing lagfix phone just sat there on boot screen now it says it can't find E: thanks for any and all suggtions...
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry Heimdall does not allow you to repartition without specifying all the files required to boot your phone. Have you tried flashing without repartitioning?

jscurtu is totally correct, for some reason I assumed you were talking about two different systems. README.txt includes instructions to uninstall the driver.
[Galaxy S I9000 Android Development] [Ramad]:
There is no need to uninstall the driver, I use two USB ports, one for Heimdall and one for Odin, you just have to remember which port has libusb for Windows installed.

Windows will keep the libusb driver installed and ready only for the particular USB port that you have chosen to use with Heimdall, all other ports are Odin ready, this is on Windows 7 x64.
[Galaxy S I9000 Android Development] jamesey10:
I'm on Ubuntu 10.10

I downloaded the backend and frontend.

When I try installing on my AMD64 laptop this happens:

james@james-laptop:~/Desktop$ sudo dpkg -i heimdall.deb
dpkg: error processing heimdall.deb (--install):
package architecture (amd64) does not match system (i386)
Errors were encountered while processing:
heimdall.deb

and when I try installing it on my Intel Desktop, this happens:

james@james-desktop:~/Desktop$ sudo dpkg -i heimdall.deb
dpkg: error processing heimdall.deb (--install):
package architecture (i386) does not match system (amd64)
Errors were encountered while processing:
heimdall.deb

It mixes up the amd64 and i386 architectures. the same thing happens when i use the ubuntu software center
[Galaxy S I9000 Android Development] Benjamin Dobell:
As far as I can tell that's a problem with Ubuntu 10.10. I saw something similar myself on my Ubuntu 10.10 machine when I installed but managed to continue anyway.
[Galaxy S I9000 Android Development] tkienzle:
Happy Panda here thanks worked awesome!!!
[Galaxy S I9000 Android Development] MrZeroo00:
Heimdall not compatible with Mac OS X 10.6.6 ?

Process: heimdall-frontend [1456]
Path: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend
Identifier: com.yourcompany.heimdall-frontend
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [285]

Date/Time: 2011-01-26 12:37:14.312 +0000
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6

Interval Since Last Report: 183014 sec
Crashes Since Last Report: 3
Per-App Crashes Since Last Report: 2
Anonymous UUID: CD6E6E5D-FC98-4D41-9BD5-C3274BE5208B

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 (???) <39AC3185-E633-68AA-7CD6-1230E7F1CEF4> /usr/lib/dyld

Model: MacBookPro4,1, BootROM MBP41.0073.B00, 2 processors, Intel Core 2 Duo, 2.19 GHz, 4 GB, SMC 1.30f3
Graphics: GeForce G310M, GeForce G310M, PCIe, 512 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0xE025), Atheros 9285: 2.1.14.5
Network Service: AirPort, AirPort, en1
PCI Card: GeForce G310M, Display, Slot-1
Serial ATA Device: WDC WD5000BEVT-35ZAT0, 465,76 GB
Serial ATA Device: TSSTcorp CDDVDW TS-L633C
USB Device: USB 2.0 PC Camera, 0x1210, 0x25f4, 0xfa400000
[Galaxy S I9000 Android Development] Benjamin Dobell:
Take a look at this post.
[Galaxy S I9000 Android Development] doudou1408:
Any packages for debian / Ubuntu 32 bits ?
[Galaxy S I9000 Android Development] Dlev7:
I have a mac and I keep getting this message when I downloaded Heimdall on my Mac:

"heimdall-frontend cannot be opened because of a problem.

Check with the developer to make sure heimdall works with this version of Mac OS X. You may need to reinstall the application. Be sure to install any available updates for the application and Mac OS X"

What do I do?
[Galaxy S I9000 Android Development] BJNK:
Ubuntu 10.10 Cant see device..

First off, very nice program, thanks for the development efforts.

Question.. I am running Ubuntu 10.10 64 bit and Heimdall seems to have installed fine, but when I boot my phone into download mode, connect it and then try and upload a zImage, Heimdall never seems to see my phone.

I can ADB my phone when turned on etc, but for some reason Heimdall never lets me click Start.

Any thoughts?

Phone is an I9000M, stock UGJL2 build.
[Galaxy S I9000 Android Development] jscurtu:
Are you using a .pit file?
[Galaxy S I9000 Android Development] Benjamin Dobell:
If the Start button is greyed out that doesn't mean that Heimdall can't communicate with your phone. Instead it means that you're trying to perform an incomplete action, which in most cases is choosing repartition but not specifying all the necessary files.

If you just want to flash a zImage then don't select repartition (i.e. don't chose a PIT file).
[Galaxy S I9000 Android Development] Benjamin Dobell:
It could be a few things, you'll probably want to take a look at my response to a similar question a few posts back.
[Galaxy S I9000 Android Development] BJNK:
I just want to comment and say I am idiot. I dl the file I wanted, but was trying to flash the .zip instead of the actual zImage like I was using CWM. Woops.

Thanks for your help!
[Galaxy S I9000 Android Development] NEBBIT:
Need to Flash Captivate back to stock using Linux...Help

I just am not getting how to use this pgm.

1. where do I get the ROM files that are in the Heimdall frontend display?

2. Do I need adb?

3. Is there a tutorial/idiots guide to this.

Any help is greatly appreciated.

Nebbit
[Galaxy S I9000 Android Development] Router:
Hi, mcord.

Did you manage to run Heimdall 0n 10.5.8?
[Galaxy S I9000 Android Development] gehzumteufel:
Ben,

I'd just like to report, so that if you get any questions about the T-Mobile US Galaxy S (T-Mobile Samsung Vibrant officially) CAN use Heimdall as long as the SBL from KB1 is used. They finally fixed a US released device.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Thanks, I've added it here.
[Galaxy S I9000 Android Development] TubeShaped:
Benjamin, why can't we rapartition the device without reflashing the bootloaders? Odin allows it...
[Galaxy S I9000 Android Development] Bxsteez:
I'm having a huge issue with this SW. I followed the readme and now my device just has a phone two dots a yellow exclamation two dots and a computer. I can't get into download mode and I can't boot up. Is there anything I can do? And why didn't this work?
[Galaxy S I9000 Android Development] TubeShaped:
What the... The same thing just happened to me! I can still get into download mode but can't boot up anymore. The device also appears in IORegistry (OS X) with the ProductID Ox6601 but Heimdall is either stuck at

Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success

Failed to receive device info response!

or at

Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Failed!

Help! Is it bricked?
[Galaxy S I9000 Android Development] Benjamin Dobell:
What files did you try to flash and what error are you getting?

No you're not bricked, use the following command to boot your phone:

Given that it's failing at two different places my guess is that your USB port/hub is failing. Either that or the cable itself is a bit dodgy. You probably wouldn't notice it with other devices but the Galaxy S seems to be particularly sensitive.

Odin lets you do a lot of things that don't make sense. i.e. Repartitioning but providing no files. I'm yet to verify that it actually is safe to repartition without the bootloaders, and I'm not particularly keen to find out.
[Galaxy S I9000 Android Development] TubeShaped:
Thank you very much for your help. I connected the USB cable directly to the motherboard at the back of my pc. Heimdall still failed either at "handshaking with loke" or, if i freshly re-entered download mode at "receiving info". The same thing when i tried the "heimdall close-pc-screen" command. I tried it many times and was about to go nuts but somehow my phone rebooted. I felt like being blessed. Heimdall still said "failed". Now I don't dare trying to flash again. What's going wrong?
[Galaxy S I9000 Android Development] gehzumteufel:
I have the T-Mobile version and when I use heimdall I have to do the flash twice. Its weird, but it works.
[Galaxy S I9000 Android Development] TubeShaped:
I flashed like 20 times...
[Galaxy S I9000 Android Development] Bxsteez:
I used that command and it booted up fine. I was trying to flash a kernel on my sprint galaxy tab.
[Galaxy S I9000 Android Development] gehzumteufel:
Wasn't saying that it would fix your problem, just that some of us have to do it multiple times. When I tested this on the Mac (since we only JUST got a leaked working bootloader), it soft-bricked the first time, then I did it again, and it was fine. Don't exactly understand the reasoning, but it works. It seems to only have this problem when it's the very first time flashing. For my device anyway.
[Galaxy S I9000 Android Development] TubeShaped:
Ok I tried it again but this time in verbose mode:

The strange thing is, everytime i go into download mode to flash, it gets past one more step for the first time:

Afterwards it fails as seen above, until I re-enter download mode again. My bootloader must be somehow messed up? I'm clueless...
[Galaxy S I9000 Android Development] gehzumteufel:
Have you tried using a different USB cable?
[Galaxy S I9000 Android Development] TubeShaped:
Just tried it, exactly the same behavior :confused: :(

Edit: Just thought back and maybe its the JPU bootloader? Before I had JPA bootloader installed and it worked just fine...
[Galaxy S I9000 Android Development] gehzumteufel:
JPU would be a later revision, but maybe it does have a bad bootloader. So, try going back to JPA's bootloader.
[Galaxy S I9000 Android Development] Dark4eons:
Working fine under ubuntu x86, thanks for the great software.
[Galaxy S I9000 Android Development] TubeShaped:
OK I was able to fix it: The JPU bootloader is indeed bugged again, Mac support broken. I booted from an ubuntu live-cd (i386), compiled heimdall from source and flashed a full ROM including the JPJPA bootloaders. Flashing from Mac now works again.*Samsung suxx. If they would really go opensource and release the bootloader and RIL, the SGS would be a much better device.
[Galaxy S I9000 Android Development] Benjamin Dobell:
I'm glad you got it sorted, if I finally get some free time again I'll get back to analysing the different bootloaders. It's ludicrously complex trying to navigate the binary files though, I wish they'd release the source!
[Galaxy S I9000 Android Development] zurchpet:
Did you get the JTAG docu and apps from Tricky on PM? Does it help?
[Galaxy S I9000 Android Development] Benjamin Dobell:
I received the links but haven't downloaded anything yet. I haven't been looking at JTAG for quite some time now actually. I returned the phone I was going to attempt to JTAG repair upon request of the owner when the jig fix was discovered. The jig seems to work in most situations so I haven't really had much need to look at JTAG recently. That and after seeing how small the pads are you have to solder to I'd need to purchase some better quality soldering equipment before I even try.
[Galaxy S I9000 Android Development] Ch4m3l30n:
GlassEchidna.com.au domain down?

Is anybody else having trouble accessing the GlassEchidna.com.au domain?

I've just discovered this software and wish to use it to flash my phone on Ubuntu 10.10.

Thx all, especially Benjamin Dobell.
[Galaxy S I9000 Android Development] afilopou:
same here.link is down
[Galaxy S I9000 Android Development] zurchpet:
Yes looks down: http://www.downforeveryoneorjustme.com/GlassEchidna.com.au
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry guys. Despite the fact we have paid to renew all our domain names, both domain resellers we use have stuffed up somehow. I'm particularly concerned as I can't even receive e-mails at the moment.

You can still download Heimdall from github:

https://github.com/Benjamin-Dobell/Heimdall
[Galaxy S I9000 Android Development] thecrucible:
This is actually the third time I have downloaded and installed Heimdall on my Mac, however in each instance the application would not start up.

I just checked the error report and it says:

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

Any ideas?
[Galaxy S I9000 Android Development] gehzumteufel:
Did you download and install QT?
[Galaxy S I9000 Android Development] thecrucible:
Didn't know I was supposed to...I guess I should have read the instructions better... ;)

Thanks!
[Galaxy S I9000 Android Development] hansmrtn:
Here is the cached version of the website.

http://webcache.googleusercontent.c...d=1&hl=en&ct=clnk&gl=us&source=www.google.com

Long link, but the downloads work
[Galaxy S I9000 Android Development] Ch4m3l30n:
Sorry for the registrar issues. I know how frustrating that can be.

Thanks for the github link.

I made Ubuntu 10.10 x86 deb packages. Would you like to include them in your github repo?
[Galaxy S I9000 Android Development] Snaydher:
Galaxy 5 x MacOS

Hi,

Heimdall works on Galaxy 5 devices?

Thanks...
[Galaxy S I9000 Android Development] Benjamin Dobell:
Thanks for that. I've actually got a bunch of RPM packages that someone else kindly donated as well. However there are two potential issues I have with distributing packages from other people. The first issue, although it's unlikely anyone would include anything malicious, I have no real means of verifying the integrity of the binaries produced. The other issue is more to do with the package itself, I'm unsure whether third-party packages install everything to the correct location and whether all dependencies are referenced correctly.

I hope neither of these two potential issues arise, so I'll put up all the third-party packages I have in the next day or so.

Unfortunately, no. The Galaxy 5 uses an older flashing protocol than that used by the Galaxy S series of devices.

EDIT: Forgot to mention the http://www.glassechidna.com.au/ domain is back up.
[Galaxy S I9000 Android Development] jRi0T68:
I'm an idiot.

I read this post, but don't understand what to do.

http://xdaforums.com/showpost.php?p=10537398&postcount=650

I'm running 10.5.8, but have no folder for Heimdall, just the application was installed. I've never had to mess with this type of thing before.
[Galaxy S I9000 Android Development] gehzumteufel:
Which version of the Galaxy S do you have? Only reason I ask, is because some of them have gotten the updates necessary to flash via the Mac, and others have not.

As for how to use it, just go into the apps and launch it. Nothing more you need to do. Unless you didn't install QT. If you did, then it should just launch.
[Galaxy S I9000 Android Development] jRi0T68:
I've got a Vibrant T959. After I posted, I saw a reference to needing QT, which I'm downloading all 900+ mb of now. Home internet is slow.

Hopefully this works, because I don't have a PC, am stuck in boot loop, can't get into recovery.

Next step is taking a sledgehammer to my phone.
[Galaxy S I9000 Android Development] gehzumteufel:
Okay, I'm just going to stop you now. QT framework is all you need.

Also, being that I know first hand, that unless you have the bootloader from KB1, you will NOT be able to use Heimdall on the Mac.

The easiest way to get to download mode that I have found, is to pull the battery so it goes totally off. Then insert battery, hold volume up/down, and plug the phone into the computer. This has worked perfectly with all 3 of the ones I have had.
[Galaxy S I9000 Android Development] pdiddyfan:
How the heck do we install the drivers for the mac??
[Galaxy S I9000 Android Development] gehzumteufel:
There are no drivers.
[Galaxy S I9000 Android Development] pdiddyfan:
I downloaded qt, but heimdall doesn't recognize my device. Something missing?
[Galaxy S I9000 Android Development] gehzumteufel:
What device do you have?
[Galaxy S I9000 Android Development] pdiddyfan:
Epic 4g. Trying to use the program to flash back to stock eclair. My pc doesn't recognize my phone anymore. I have the drivers installed on it correctly. It's something with the phone. It won't recognize it, so I'm on the mac now using heimdall...
[Galaxy S I9000 Android Development] gehzumteufel:
In that case, I unfortunately don't have much help. I am sure that the bootloader problem that has plagued all the galaxy s devices also affects the epic. Samsung ****ed up the bootloader. As a result you will have to do it with a pc until a fixed bootloader is found/leaked.
[Galaxy S I9000 Android Development] Manadar:
Hum, after installing QT and heimdall, my GT-i9000 doesn't mount in DL mode in Heimdall, i guess i'm gonna have to use crappy windows? :(
[Galaxy S I9000 Android Development] jRi0T68:
Okay, I've done a search and will continue to do so, but perhaps someone can help me here.

I've got my Vibrant connected to my Mac running OS10.5.8. Heimdall is running, I downloaded the bootloader from KB1 and put it into the Secondary Bootloader.

I also downloaded and extracted Eugene_2E_JK2_Froyo.tar and placed the 512 PIT file in the PIT file field, Boot.bin in the Primary bootloader field, and the rest of the files in there corresponding fields.

When I click start, I get the message that Heimdall Failed to Start.

What am I doing wrong?

Edit: The file I downloaded didn't have a recovery file. Where might I download that from, if it's what is needed?
[Galaxy S I9000 Android Development] gehzumteufel:
If you didn't have the bootloader from KB1 on there BEFORE this, you aren't going to be able to use the Mac. I can't stress this enough.

As for this "recovery" file? Not sure what you're referring to.

You can use the JFD ODIN tar (you have to extract it if you use Heimdall on the PC) to revert back to stock.
[Galaxy S I9000 Android Development] jRi0T68:
Thanks again. You've been most helpful. So I needed to have that sbl.bin flashed to my phone before I got a boot loop?

Once I gain access to a PC, set it up with Odin, and get myself out of this hole I've dug, do I flash that sbl.bin through Odin?
[Galaxy S I9000 Android Development] gehzumteufel:
You are correct. It has to be in place beforehand, because the problem is that the USB implementation (as per the OP) is bad, and is fixed in some bootloaders, but not all. For the T959 (original Vibrant) the only bootloader it is fixed in, is the one with KB1.

You cannot flash it as is, unless you use Heimdall (on the PC). Otherwise, you need to add the sbl.bin to a tar archive to use it with ODIN.
[Galaxy S I9000 Android Development] lownoise:
Why flash bootloaders

Benjamin,

Could you tell me why we should flash bootloaders if we want to repartition with heimdall:confused: , odin doesn't require it.

I know you don't have to repartition if you want to change stock firmwares but in the case of cyanogen mod, they use a different partition layout and if you want to go back to stock you must use repartition.

I think heimdall is a great product! It works very good on linux;) but flashing bootloaders....

Lownoise
[Galaxy S I9000 Android Development] gehzumteufel:
Heimdall doesn't have the ability to repartition. So you have to use odin for that.
[Galaxy S I9000 Android Development] intronauta:
ein??? Heimdall can repartitioning without problems (but needs boot-sbl.bin to do it)
[Galaxy S I9000 Android Development] gehzumteufel:
Unless something has changed, repartitioning has never worked. It isn't a function he was able to get out of the coding stuff.

Ben???? Can you respond about this? I know you said previously you didn't know how they did this op...
[Galaxy S I9000 Android Development] intronauta:
Maybe i'm wrong, but i think that he refers to repartitioning without boot-sbl.bin
[Galaxy S I9000 Android Development] gehzumteufel:
The problem is that (from what I was aware of and could be wrong if something changed) the repartitioning function is not part of the protocol used for flashing that he was able to find. So he wasn't able to get it working at the time. I don't know if he has revisited it since though.

Here is the post that he says that repartitioning isn't supported.
[Galaxy S I9000 Android Development] intronauta:
I think that this post is very old and is about v1.0, the repartitioning feature was included in v1.1
[Galaxy S I9000 Android Development] lownoise:
Yeah Repartitioning is included as feature of v1.1

But I don't want to take the risk to repartition with bootloaders (boot.bin, sbl.bin) , If something go's wrong you have a malfunction phone....
[Galaxy S I9000 Android Development] gehzumteufel:
Ah I stand corrected. Cheers!
[Galaxy S I9000 Android Development] Benjamin Dobell:
Woh, sorry about not getting back to you guys, I didn't see the posts :S

Yeah Heimdall supports repartitioning since version 1.1. It was actually quite a bit easier to implement than I expected, the phone itself seems to automate it when you flash a new PIT file.
[Galaxy S I9000 Android Development] gehzumteufel:
It's okay. We're all busy people. That's cool that it was easier than expected! Probably something you were quite happy about I bet.
[Galaxy S I9000 Android Development] lenrek:
Finally... I can kill off the last remnant of WindowsXP. Still keeping 1 just to Kies.

Thanks! :D
[Galaxy S I9000 Android Development] lownoise:
But why we must flash boot.bin and sbl.bin:confused:
[Galaxy S I9000 Android Development] Benjamin Dobell:
I could have sworn I edited my post and included an answer to that.

The reason is that when you repartition several partitions are being wiped, including the primary and secondary bootloaders. I don't know if the device is smart enough to back-up the bootloaders prior to the wipe and restore them afterwards. However I'm not particularly keen to find out either. If the device doesn't back-up and restore the bootloaders when you repartition then your device will be unable to boot at all i.e. hard bricked.
[Galaxy S I9000 Android Development] gehzumteufel:
I don't think that's the case. I think it only wipes the partitions that you have rfs files for at the time of repartitioning, but I don't have any way to prove this. Just my personal opinion.
[Galaxy S I9000 Android Development] pietro_spina:
Maybe someone with the ability to do a JTAG restore would be willing to test this for you. This guy,

connexion2005 offers that JTAG service on his website and is pretty involved in the XDA community.
[Galaxy S I9000 Android Development] gehzumteufel:
Or someone that has a replacement they are sending back.