yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] MrFrem82:
It passes some time since my last request, so in case that there are some news I ask again: Does anybody test heimdall with Galaxy 5 (I5500)?
[Galaxy S I9000 Android Development] vamp6x6x6x:
Hopefully this works for me bc odin all the sudden doesnt reconize my vibrant.
[Galaxy S I9000 Android Development] TA123:
Where could I find the documentation for Heimdall? I'd like to flash Lite'ning ROM but I do not know what I should do.
[Galaxy S I9000 Android Development] Benjamin Dobell:
READMEs

Windows

OS X

Linux

If you're running Heimdall from command line then typing:

will give you information about each of the available commands.
[Galaxy S I9000 Android Development] serhan86:
@Benjamin Dobell: Do you have plans to release 1.2.0 frontend for linux 64 bit?

And to run, heimdall frontend 1.1.1, i have installed command line binary before installation. however, I have to run it from terminal not from menu or press alt+f2 and run heimdall-frontend. Why doesn't it add the program icon to menu by itself?

I suggest you it would be better for us to flash our firmwares if there is a basic and an advanced flash tab. for 4 files which are .pit, pda, phone and csc there can be simple tab. but for more advanced flashing there can be a advanced tab.

I know you are a developer, and you have to focus on windows and mac rather than linux coz you get donations better than linux. but as a end-user, please do not ignore linux.

I really appreciate all your efforts in making this software better day-by-day.
[Galaxy S I9000 Android Development] Benjamin Dobell:
I won't be releasing a Heimdall Frontend 1.2.0, however when I get a chance I'll be releasing a 1.2.1 version which includes an updated command line tool and a new frontend.

I'll look into adding an icon to the Linux start-menu with the 1.2.1 release.

I don't have any plans to allow flashing via PDA, phone and CSC archives (although the Frontend is organised into sections). I find that flashing with archives is quite convoluted as it's not at all clear what files are actually being changed on your phone. I also think it's very important that users flashing their phone have some idea of what each file actually does.

Using archives might seem more convenient, however that's only the case because firmware tends to be distributed this way for Odin. The firmware itself on the device isn't divided into groups, nor does the flashing protocol take any notices of these groups (Odin just extracts the archives and flashing the files contained within). Normally when you download an archive and extract it, you don't expect to find more archives, that's somewhat redundant. Firmware is only distributed this way due to Odin's poor user interface.

Given that Heimdall is more reliable than Odin (for supported devices), and it supports more platforms, I see no reason why anyone would bother distributing firmware in Odin's format. I'm not saying people shouldn't ever use Odin. However it's Odin's interface that imposes unusual requirements. As such it would make more sense if in order to use Odin you have to archive files. Rather than having to extract archives in order to use Heimdall.

This way all users will be fully aware of what files they're actually flashing to their device (whether they use Odin or Heimdall) and hopefully they'll gain an understanding of what those files are. Theoretically this would mean less bricked devices.

It certainly would be nice to be able to make a living releasing open-source software to communities such as this. However, monetarily speaking, after factoring in the donations, the hours invested and the value of my time then I'm most certainly at a loss. But, I'm not doing this for the money.

Donations are a mostly just a great incentive for me as it shows me that people value my work. Well that, and donations make the "overall monetary loss" slightly less. That way my girlfriend doesn't get quite as angry when I spend my time working on Heimdall instead of performing paid work :p

Also, I think you'd probably find that in general Linux users are more likely to donate than Windows and perhaps also more likely than OS X users.
[Galaxy S I9000 Android Development] hlaube:
Hi Ben,

could not fix my phone with a jig. Have a new one now. :(

I flashed it already under XP (bootcamp) but I have a problem to access it in OS X (10.5.8)

herbert$ heimdall close-pc-screen --verbose

Heimdall v1.2.0, 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/

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... Failed!

Do you have any idea what is wrong? I already reinstalled libusb and heimdall 1.2 from source but that does not solve the issue.
[Galaxy S I9000 Android Development] hlaube:
Solved it. kext was somehow not korrekt. Re-installed it, works now. My phone gets now recocniced in download-mode.

xxx$ heimdall close-pc-screen --verbose

Heimdall v1.2.0, 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/

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...

Rebooting device...

Attempt complete
[Galaxy S I9000 Android Development] urbanomad:
Can you tell us how you solved this problem? Maybe it will work for 10.6.7 as well...
[Galaxy S I9000 Android Development] hlaube:
From the instructions I did

5. If you haven't installed the driver before, enter the following:

cd OSX

sudo ./install-kext.sh

Since the script created a problem, I did it by hand:

sudo chmod 755 /usr/local/bin/heimdall

sudo cp -R heimdall.kext /System/Library/Extensions

sudo chmod -R 755 /System/Library/Extensions/heimdall.kext

sudo chown -R root:wheel /System/Library/Extensions/heimdall.kext

sudo kextload /System/Library/Extensions/heimdall.kext

a reboot, and it worked.
[Galaxy S I9000 Android Development] urbanomad:
Thank you for taking the time to tell me what you did but it didn't work with my configuration.
[Galaxy S I9000 Android Development] urbanomad:
Does anyone have any suggestions what to do in my case? The differences between me and hlaube's systems are: I am on Mac OS 10.6.7 and he is 10.5.8, my phone is I9100 and his I9000...
[Galaxy S I9000 Android Development] lindsaytheflint:
"Heimdall, after the Norse god, and guardian of the Bifrost Bridge"...

Sounds like someone's getting their interpretation of "Norse mythology" from Marvel Comics... ;-)
[Galaxy S I9000 Android Development] pixbuf:
Still can't find 1.2 source packages

Ben, I run Gentoo Linux so I compile everything from source. I did 1.1 like that, but I've had it crash my computer when flashing from the command line occasionally. The phone flashes fine, but the host computer crashes. (when I use heimdall-frontend it works fine.) Very strange. So, I thought I'd try 1.2, but I can't find the source package. I looked on https://github.com/Benjamin-Dobell/Heimdall/downloads, but only found binary packages for 1.2.

The command line I'm using that crashes the computer is

heimdall flash --kernel zImage
[Galaxy S I9000 Android Development] BronzedDroid:
I was curious and checked the Norwegian and English wiki. They both say that he guarded the Bifrost Bridge. :P
[Galaxy S I9000 Android Development] Tarlabgab:
Well after multiple trying...

It seems that OSX just cant see the phone while in download mode!!

At first I was just wondered if I did something wrong. But when I check with adb it cant see the download mode,too! So that explain why command never work here.

Is there any fix or driver to install??
[Galaxy S I9000 Android Development] BronzedDroid:
On the windows version there is a readme which explains how to install the appropriate drivers. You should check if the same is true for mac.
[Galaxy S I9000 Android Development] skeepon:
im running os x 10.6.7, and i have installed over 4 times, and even after several reboots, i still dont see the app in my applications folder. how can i fix this? oh im trying to install 1.2.0 btw

EDIT: i just realized there is no GUI -_-

hmm anyone wanna run me thru on how to flash via command line? pleaseeeee
[Galaxy S I9000 Android Development] skeepon:
double post
[Galaxy S I9000 Android Development] Thiện Ngộ:
Can I flash with it on Samsung galaxy 3 (i5800) on Ubuntu?

Thanks in advance.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Unfortunately, no. Heimdall only supports Galaxy S devices. Other devices still seem to be using an older version of the flashing protocol, which is quite different.
[Galaxy S I9000 Android Development] Benjamin Dobell:
I'm working on a 1.3.0 update to both Heimdall and Heimdall Frontend. The frontend in particular is receiving a large make-over. I'm hoping to have the release ready some time in the next 7 days.

The release should include a fix for the OS X / Qt issue. I'm also looking into the kext issues some users have reported with 10.6.5+.

This is going to be a pretty major release. I've already incorporated quite a few features that were requested. However the main thing I'm doing is adding support for a tarball firmware distribution format that should make flashing simpler and less prone to human errors. Users will only need to select the tarball and Heimdall Frontend will take care of the rest. I'll go into the exact details when I get a bit closer to making the release.

You may also be interested to know that Adam Outler is developing a light-weight Java interface for Heimdall, Heimdall One-Click.
[Galaxy S I9000 Android Development] hlaube:
I like to hear that. :)

My last human error is on its way to Samsung. And I know it was my mistake!!:mad:
[Galaxy S I9000 Android Development] Sine.:
Hello Benjamin,

Does Heimdall may work for Samsung Galaxy SL? (i9003)

It would be great! :D

About Heimdall One-Click, I've heard of that (more infos here), it will be great too :)
[Galaxy S I9000 Android Development] branalvere:
Look forward to a new heimdall release, frontend was broken for me after Ubuntu 10.04 though the command line works well with maverick. Natty I haven't tried since I can't bear unity
[Galaxy S I9000 Android Development] TA123:
Do you think that the S2 support will improve in 1.3.0?

Oh, you can always use the classic desktop, which is pretty much an old Gnome interface. It is what I set up for my wife who cannot bear any changes :)

Sorry for off-topic, could not resist :)
[Galaxy S I9000 Android Development] Benjamin Dobell:
Heimdall Frontend 1.3 is much more generic and does not contain anything device specific. As a result the interface is probably a little bit more complex if you're looking to flash just a few files at a time. However the added support for "Heimdall firmware packages" makes flashing complete firmware much more straight-forward. Plus the package format includes information about supported devices, firmware version and so forth. It will be up to ROM developers to maintain this information, however it should help prevent situations in which users flash incompatible firmware.

Basically the Heimdall Frontend 1.3 interface no longer resembles the Odin process in any way, which is a good thing!

In general flashing with the SGS2 should be working perfectly at the moment. However, I'm still trying to work out ways to improve SGS2 support for things like Heimdall command line's print-pit and close-pc-screen actions. I still don't own a SGS2 so development in that respect is a bit difficult.
[Galaxy S I9000 Android Development] apacheo:
Hi Ben,

If you'd like a beta tester for 1.3 (as I am a user affected by the Kext issues on 10.6.7) I'd love to help out, because I'm sick of booting into windows to flash with Odin :)

Cheers

C
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sounds good, I'll send you a PM when 1.3 gets a bit closer to release state.
[Galaxy S I9000 Android Development] urbanomad:
I would also like to try the 1.3 beta :)
[Galaxy S I9000 Android Development] ashwinds:
I boot into 32 bit mode and it works fine. Do you have issues in 32 bit mode too?
[Galaxy S I9000 Android Development] apacheo:
Mac 10.6 only boots into 32 bit mode (by default) - you have to specifically enable 64 (which I haven't) ... as opposed to 10.7, which is 64 by default and causes crazy things to happen... ;)

But in brief, yes, it doesn't work for me in 32 or 64 bit modes. Just gives the no compatible device found error, and kextstat shows the kext isn't loaded :(
[Galaxy S I9000 Android Development] apacheo:
Thanks Ben, or an email would be great - I'll send you my email in a PM.
[Galaxy S I9000 Android Development] yhbrandon:
Extract the tar or md5 and using terminal navigate to the folder that you extract it to. Now depending on which files are included in what you flashing, youll type in a chain of commands for each file type. So for example, I have a ROM that i want to flash that includes a factory.rfs, cache.rfs, dbdata.rfs, modem.bin, and a zImage. So my code would look something like this:

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

I hope that helps

If you get confused, in terminal type in heimdall help.
[Galaxy S I9000 Android Development] vicous707:
the link is down? where do u get this now?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry, it's back up now.
[Galaxy S I9000 Android Development] jscurtu:
Dammed!!!

I just bricked my phone using Heimdall.... I am sooo stupid :-)

I think I flashed over 1000 times, with out any problems I mostly do know what I am doing..

But on the 1001 time, I guess I just wasn't concentrated!

I accidentally flashed boot.bin on Sbl.bin, now my phone just wont turn on... :(

Its a Bug.. Heimdall should check if it is a valid file before pushing.. :confused:

Looks like no way around this... Its dead...
[Galaxy S I9000 Android Development] Sine.:
Does Heimdall supports the Galaxy SL (i9003)?

I don't want to install a Windows just to use Odin :p
[Galaxy S I9000 Android Development] lownoise:
Problem with flashing

Benjamin,

Any idea how it comes that most flash's are failed with the error Handshaking with Loke... Failed! ?? I think about 1 of 5 flash's successes on my I9000

I get this error on different computers/cables and usb ports , most of the computers are running linux. Tried Odin 1.8 to flash and that succeeded every time....

Lownoise
[Galaxy S I9000 Android Development] Benjamin Dobell:
Heimdall should support the GT-I9003, yes. I haven't tested it as I don't own a GT-I9003 but if you're worried run a command like:

This will just initiate a connection and retrieve your device's PIT file. It won't flash any new files to your device.

I've definitely heard reports of that before but never heard about it happening so frequently. Usually I'd say it has something to do with a bad cable or the device's own cruddy USB implementation.

However, if you're getting reliable flashes with Odin 1.8 then it may be timing based. Heimdall uses different timing to that of Odin. Well, the timing is obviously never exactly the same, but Heimdall's is intentionally different to allow substantially faster flashing. However it can be changed using the --delay parameter. Perhaps try use a delay of 15 or 7 and see if the problem disappears. Unfortunately these little niggles seem to come down to individual devices.
[Galaxy S I9000 Android Development] Benjamin Dobell:
I'm not sure if the bug statement is a joke. If it is then that's fine :p If not, that's impossible. Although not totally identical, this is related to the Halting Problem.

Unfortunately that's very likely the case. The only known way to fix a corrupt primary bootloader is via JTAG. There are members around these forums that might be willing to do it for you. If not you might be in for a trip to a Samsung Service Centre :(
[Galaxy S I9000 Android Development] jscurtu:
Of course it was more of a joke ;-) this happened because I was not concentrated and stupid..

I send my phone to Samsung Repair this morning, will see what they say.. :rolleyes:

Thinking about it though.. for the frontend side..

At work I program mostly in vb.net or python and some little pyQt4.. my C++ skills are not that good so I will let them by side as I am more a immediate code programmer and I don't have patients.. :D

However, if I was to check if the file is valid... I would make in the frontend a selection (dropdown) to choose a device, depending on the selection and what the user puts in I will know what the valid filenames are.. As they don't change for that device..

In my case, boot.bin and Sbl.bin are to different files or lets say "filenames", switching them will for sure kill your device, 100% brick in just a few seconds..

Switching others are no problem, just re flash and your good to go..

So on the "start" button method, event i could check before the program starts to do its magic, if those filenames the user put in are valid . If not, then exit!

The user would really have to change the filenames in order to brick its device...

Its just a thought I just had....

Thanks!
[Galaxy S I9000 Android Development] Benjamin Dobell:
I've actually gone out of my way to ensure any file name can be used. Having hundreds of zImage files floating around a developer's computer can get quite confusing. Because Heimdall allows any filename you could call the file "zImage-clockwork-v1.2" and it would work fine with Heimdall. However it would not work with Odin.

The other problem is that I would have to know the name of valid files for a particular the device. The PIT file does actually contain this information and that's how Odin knows what to do. However PIT files also tend to include certain partitions that don't have a corresponding filename. For instance the backup secondary bootloaders don't have a filename specified, hence why they can't be flashed from Odin. Or in the case of the kernel and recovery, both partitions tend to specify "zImage" as the name of the file, which is why Odin can't flash them separately. Heimdall is much more robust because it does support any filename.

However, the 1.3 release includes a major overhaul of Heimdall Frontend. The firmware packaging functionality should drastically minimise the number of bricks caused by mistakes similar to this. Firmware developers create the package, in doing so they specify which files are flashed to which partition. Heimdall Frontend then produces a compressed package with all this information along with extra information about the firmware developer, supported devices etc.

Users can then download these firmware packages, select them from Heimdall Frontend and flash the package as specified by the developer. However, more advanced users are still able to customise a flash. For instance, if a package contains a recovery kernel that the user would not like to be installed, the user can simply remove it from the list of files to be flashed.
[Galaxy S I9000 Android Development] apacheo:
How are we kooking for a 1.3 beta so I can see if I can get Heimdall working on my Mac? :-)
[Galaxy S I9000 Android Development] GuestK00150:
Do I need any drivers to get this to work under linux? using archlinux64 and pretty new to linux, so small steps would be great ;) Thanks
[Galaxy S I9000 Android Development] zsori:
Interestingly I also have issues with 'Handshaking with Loke'. It always fails with:

Heimdall v1.2.0, 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/

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... Failed!
ERROR: Failed to receive response

This happens every time I try to run print-pit.

Since Heimdall worked for me before (I have flashed one ROM and one kernel without issues) I tried to revert to the Heimdall version I have used earlier (which is 47faaf0) and tried to reflash the kernel and it failed with the same error.

I'm not sure what changed since my last successful flash. I guess one obvious answer is flashing that kernel (which is speedmod k13e).

I have tried to use --delay 15 and 7 as suggested in your earlier post.

I don't have other ideas. Do you?
[Galaxy S I9000 Android Development] hlaube:
Hmmm did something similar. Owe now a new phone. But make contact to Samsung Service. Mine is there right now. May be, they fix it. I wrote them ahead and got the answer they will do it.
[Galaxy S I9000 Android Development] hlaube:
Ups you did it already.
[Galaxy S I9000 Android Development] Bec07:
So, cross-platform you say?

Will there be honeycomb support? I have a neat acer iconia A500 with a full size usb port and flashing my galaxy S off it... man that would make my day!

I'll try to boot up linux in the meantime ;)
[Galaxy S I9000 Android Development] squealernet:
I made some alienized RPMs for i368:

1.2.0 CMD Tool - http://www.multiupload.com/WI6QA7OPW7

1.1.1 Suite - http://www.multiupload.com/O5K7RQVSRR

no additional tweaks, straight from the original .deb. You may need some tweaks for usb rights

Create "/etc/udev/rules.d/90-android.rules" if you can't flash as user with:

SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"

Additionally: a big "Thank You" for making this software, works great.
[Galaxy S I9000 Android Development] lownoise:
Some Info

zsori,

Heimdall used to work for me also, here is a quick history of my flashing history.

I've used heimdall for the last half year without any problem till i flashed cyanogenmod

I've reverted back to stock 2.2.1 with Odin 1.83 and repartion (512 pit file)

After that the heimdall was failing most of the time 1/5 succeeded.

Then when the official GB update was released I've flashed it through Kies

My GB version is JVH and i am sure the bootloaders are updated also.

From then heimdall is always failing!!

Tried different computers, usb cables, and OS (Windows/Linux)

The Delay option doesn't work either for me.

Odin 1.83 is working for me..

So can someone confirm that heimdall is working with the JVH bootloaders:confused: