yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] pixbuf:
I suggest Continuum v5 from this thread, which is JVH based GB. The instructions on the OP are very clear. You would flash back to stock 2.1, flash the bootloaders and then the kernel. Then you flash the ROM from CWM.

Unfortunately, the instructions are only for using Odin. I inquired about doing it with Heimdall in this post. Ben Dobell, the Heimdall developer, responded in post #948. That should be enough to get you going.
[Galaxy S I9000 Android Development] nzroman:
Great, thank you. Those links have enough info to go on by. :>
[Galaxy S I9000 Android Development] hlaube:
I can not confirm what you are writing. It may be that libusb is not needed, when Heimdall installs it when you load binary, but if you translate it on your mac from source, you will need it.

And if you daily user has no admin-rights, what I hope is the case, heimdall, at least the version on my mac, will not flash as an unprivileged user. Since I am to lazy to set up may daily user as a sudo-user, I start heimdall this way:

MacBook:~ xxx$ su yyy

Password:

bash-3.2$ /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend

were xxx is normally my daily user, yyy would me my privileged, while equipped with admin rights.

I may be wrong, but at least I can flash my SGS, and did it more then once.
[Galaxy S I9000 Android Development] gehzumteufel:
lol again, it's not needed. This coming from a Windows, Linux and OS X user. And I have flashed on all 3 OSes. Didn't need libusb on any of them (with windows, you just use the included driver). On OS X, most people need the right bootloader, but even this is no guarantee. Sudo is also unnecessary. You can run it without an admin prompt and without using sudo. For the most part, OS X doesn't require you to use sudo. Unless your daily user isn't part of the admin group. Which you would have had to specify it being a regular user when you were creating the user.
[Galaxy S I9000 Android Development] hlaube:
Well, I thought, that was what I wrote, but it may be, I expressed it wrong. And in all honest, none should run his mac on a daily base as a member of the admin-group.
[Galaxy S I9000 Android Development] gehzumteufel:
lol tell that to the general OS X userbase. Especially since Apple defaults to admin.
[Galaxy S I9000 Android Development] Benjamin Dobell:
There is a GUI, open terminal and type:
[Galaxy S I9000 Android Development] Tachikoma_kun:
Just soft bricked my SGS on OSX with Heimdall, it didn't even get to flashing, put the phone into download mode, picked the kernel, clicked start, it said failed to receive device info response and the phone is now bricked...

Stock VJO trying to flash cf-root kernel
[Galaxy S I9000 Android Development] gehzumteufel:
What's showing on the screen?
[Galaxy S I9000 Android Development] Tachikoma_kun:
Phone--!--Computer icon
[Galaxy S I9000 Android Development] gehzumteufel:
Try flashing again using Heimdall.
[Galaxy S I9000 Android Development] Tachikoma_kun:
I have a dozen times, gives the same fail message :(
[Galaxy S I9000 Android Development] gehzumteufel:
You're going to have to flash with ODIN then.
[Galaxy S I9000 Android Development] Tachikoma_kun:
Oh well, best pop over to my sisters house, thanks for the help.
[Galaxy S I9000 Android Development] bilboa1:
http://xdaforums.com/showpost.php?p=13995677&postcount=5

tada ;-)
[Galaxy S I9000 Android Development] Borky_16:
Sorry I don't want to read soooo much a quick answer would help me :)

I installed the binary source of heimdall and the frontend at Ubuntu 11.04, but can't find the app in the menu :(

do i have to make a link?

Where is that binary ?! :D

Thanks anyway ! :p

Edit:

Got it only a Link to /usr/bin/heimdall-frontend :)
[Galaxy S I9000 Android Development] el_Salmon:
Samsung Galaxy Ace Support

Hi guys,

anyone has tried to use it with Samsung Galaxy Ace (S5830)
[Galaxy S I9000 Android Development] tazman171:
Cough, :rolleyes: Why? Why o why o why? So no windows users on this forum care about open source? What a broad and STUPID statement. Advancing your cause are you. :(
[Galaxy S I9000 Android Development] FadeFx:
belive me, i would have tested heimdall already, if i only had my phone returned from repair...

and why? because of openness. and yes, i am a windows user........
[Galaxy S I9000 Android Development] tazman171:
I'm going to test it to, just got off a 2 day flash battle with this thing, thought I had bricked it on a few occasions, lol.
[Galaxy S I9000 Android Development] Benjamin Dobell:
It works for me now. Perhaps my server went down temporarily. If anyone else has difficulties let me know.

August 18th: Sent phone to Handtec.

August 25th: Phone arrived at Handtec.

August 27th: Handtec sent phone to Samsung

September 15th: Handtec received repaired phone from Samsung.

September 16th: Handtec sent phone to me.

September 20th: Expecting the phone to arrive.

So all in all just over a month to get my phone repaired :(
[Galaxy S I9000 Android Development] Benjamin Dobell:
To anyone interested in Heimdall progress, I'll be making a minor release sometime in the next 24 hours to add support for a new product ID. I'll also update the list of supported devices when I make the release.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Just released alpha 7 which added support for devices with product ID 681D.
[Galaxy S I9000 Android Development] Phlogiston:
where is the source code?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Read the first post. It's presently unavailable until I get someone testing the current release.
[Galaxy S I9000 Android Development] Brock Samson:
Any sort of time line to when this may come to Mac? I have been following this thread since day one and hate having to drive to my moms to use Odin. I am really looking forward to this.
[Galaxy S I9000 Android Development] Benjamin Dobell:
I'm still waiting on testers, however as soon as I can get some confirmation from testers on Windows I will then release the Mac and Linux versions. It really won't take me any longer than a couple of hours to setup the Mac and Linux releases once I know other people have had success with the Windows version.

Although I expected it yesterday I still haven't got my phone back so even I haven't even been able to test recent alphas.

Actually I have something to do for those who aren't willing to test but would like to help out. Could people please check if they have ever flashed a CODE/PHONE tar with Odin that does NOT contain a file called param.lfs?
[Galaxy S I9000 Android Development] mopodo:
I tried...

I had some dificulties installing the drivers on windows 7 64bit

You have to choose "Browse my computer for driver software" -> "Let me pick from a list of device drivers on my computer" -> "Have Disk"

On Windows XP in VirtualBox (host is Debian with Kernel 2.6.35.5) I had no problems.

I tried to flash JPH over JPH (803.pit)

I tried it with the 512.pit and the 803.pit both failed.

Sbl.bin and boot.bin were taken from JP2 or JP3 (don't knwo exactly)

Attached are some output logs (both from XP 32bit in VirtualBox, but under Win7 the same errors occured)

log1.txt (tried it connected to frontpanel USB 1.1 :D )

log2.txt (the errors trying to flash JPH)

Country: Switzerland

Carrier: Phone was Swisscom branded but used at orange network till yesterday and since today sunrise :)

HardwareIDs from Heimdall Driver...

USB\VID_04E8&PID_6601&REV_021;

USB\VID_04E8&PID_6601
[Galaxy S I9000 Android Development] Benjamin Dobell:
Thanks for testing!

I have no idea how Odin is managing to flash when the phone is so unreliable in terms of responding to messages. When I get my phone back (hopefully today) then I'll have to investigate further.

I'm not overly surprised that USB 1.1 fails as I'm attempting to transfer packets too large for USB 1.1. I was hoping that libusb-1.0 would automagically split them up somehow but that's probably not the case. Unfortunately I don't have a USB 1.1 port to test with.

I presume log2.txt is using a USB 2.0 (or newer) port? log2.txt is useful as it indicates Heimdall is failing at a similar place to where Heimdall has failed in the past, I'm not immediately sure why though.
[Galaxy S I9000 Android Development] pietro_spina:
I would love to test this on Linux. unfortunately I do not have a windows set up or I would test there also.

any chance to test a pre alpha of the linux version?

thank you for your efforts on this front.

-p
[Galaxy S I9000 Android Development] Benjamin Dobell:
I've actually got access to two working Galaxy S at the moment as I got a new one (16 GB Australian Optus Edition) and am giving my old one (8 GB UK/International Edition) to my girlfriend, although it seems to have reception issues so I might have to send it back again. Anyway now that I have access to phones again I'm expecting to have something stable very soon and therefore a linux release in the next week is definitely on the cards.

I've also worked out how Odin dumps the NAND so I'll be adding that functionality to Heimdall as well. I haven't actually been able to pull off a full dump with Odin anyway, it gets to somewhere between 100 - 300 mb before Odin itself locks up.
[Galaxy S I9000 Android Development] dirk1978:
Awesome. I await a Linux version with anticipation :)
[Galaxy S I9000 Android Development] techmik67:
Just tried to install drivers. Windows Vista 32bit. No problems with windows drivers.

I got it to recognize and tell me the Heimdal driver wasnt a regular driver provider blah, blah.... said yes, install anyway.... got the error "There is no driver selected for the device information set or element".
[Galaxy S I9000 Android Development] mopodo:
yes, USB 2.0 port direct on the motherboard
[Galaxy S I9000 Android Development] Bec07:
Loki as a name is much frendlier and easy to remember.

Some screenshots in the first post?
[Galaxy S I9000 Android Development] techmik67:
same error on win7 64bit..... "There is no driver selected for the device information set or element"
[Galaxy S I9000 Android Development] mopodo:
Take a look at my post, probably helps

Just the first paragraph

http://xdaforums.com/showpost.php?p=8254896&postcount=91
[Galaxy S I9000 Android Development] bernabap:
Benjamin,

after I tried CM7 on my I9000B and get back to a stock rom with Odin I always get "Handshaking with Loke... Failed!" cant flash anything with Heimdall anymore! :( only with Odin. This is a know problem? Is there a way to use Heimdall again?
[Galaxy S I9000 Android Development] braschlosan:
Verified that Heimdall flashes the Samsung Galaxy Indulge SCH-R910 kernel correctly.

Bricked my phone with a bad kernel written with DD and was able to fix it with Heimdall and the original kernel :)
[Galaxy S I9000 Android Development] Benjamin Dobell:
Hey everyone,

Sorry for disappearing for a little while, I've been quite busy. However the good news is that I just managed to set aside some time to work on an update to Heimdall!

The update will be command line only (for now) and adds the following functionality:

- Support for the Galaxy S II! (Hopefully, keep reading.)

- Support for SHW-M110S (Korean Galaxy S).

- Improved support for Galaxy Tab, Captivate and Vibrants (see below).

- No reboot option.

- Dump the devices PIT file and print the information in a human readable format.

- Support for more named partition parameters i.e. --hidden, --movinand.

- One more major feature (read below).

However the biggest change is probably the proper support for PIT files. This means that less things are hard-coded. Instead Heimdall will be grabbing data from your device's PIT file or the PIT file you specify when repartitioning. This may seem like it has minor impact on the usefulness of Heimdall but it actually allowed me to add a second method of specifying files to be flashed to your phone.

You can now type

i.e.

This essentially means you can flash any file your device supports as long as you know the partition identifier. Of course I don't expect you to know them off the top of your head. This is where the PIT file dumping functionality comes in.

Walah! You now have a complete list of all the files your device supports.

Another minor change is that I've removed the restriction on needing to specify bootloaders (or any files in particular) when repartitioning. However, this was in place as a safety feature. I honestly have no idea whether repartitioning without certain files is safe, and I have no immediate plans to find out, so please be careful!

Back to the Galaxy S II. I don't own a Galaxy S II, so I'm unable to test any changes at present. However I very much would like to own a Galaxy S II! I'm certainly not one to hold out on releasing open-source software until a certain amount of donations have been received. I don't particularly agree with that. However let's just say that I'd very much like to be able to develop (and test) for the Galaxy S II and your donations would be very much appreciated! Again, a very big thanks to those of you who have donated!!!

Donate Link: http://www.glassechidna.com.au/donate/

Source Code ETA: < 24 hours

Platform-specific binaries might take a little while longer to churn out.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Source for 1.2.0 (beta) Heimdall command line tool has been pushed to Github. I'm going to get some sleep, when I wake up I'll start posting binaries.

Galaxy S II users, let me know if it works.
[Galaxy S I9000 Android Development] bilboa1:
no matter how small the change is a quick thanks goes a long way :P
[Galaxy S I9000 Android Development] maedox:
Hi, thanks for this. As an avid flasher and Linux user I'm eager to try it. One question first; Is there any risk in flashing with this on Galaxy S II? I read your warnings about params etc., do they apply to S2 too? I guess the chance of something happening is always there, but it's <= than every other method anyway.
[Galaxy S I9000 Android Development] Arielo1:
is this something like EZBase ?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Heimdall 1.2.0 command line binaries are now available. Debian 32-bit, Debian 64-bit, Windows and OS X (universal) are all available.

It took me a good 5 hours to remember how I got those damn universal binaries compiling and linking with libusb-1.0. So OS X users need to be especially grateful! :P On the plus side the package should now be installable on OS X 10.4.

As you seem to know, there's always some degree of risk.

I think in general we should be good to go. Some users had made quick modifications Heimdall 1.1.1 to get the kernel flashing on the SGS2 which worked fine, so the protocol should be the same. The main difference between the SGS2 and other devices are the partition identifiers. However the new PIT file reading functionality should take care of that.

Short answer, no.
[Galaxy S I9000 Android Development] sptorrent:
Thanks ever so much for this piece of kit! No more need to exit Linux!!!

Heimdall 1.1.1-1 has been working perfectly for me (flashed quite a number of times, either kernel or total repartition).
[Galaxy S I9000 Android Development] distortedloop:
Hi Benjamin.

Posted the same info in the Droid Charge forum, but not sure how often you frequent there.

Tried 1.2.0 command line on my MacBook Pro and the Droid Charge. I get a "claiming interface....Failed!" message.

With 1.1.1 I would get a "no compatible device" type message.

I am able to do a succesful heimdall dump command on this machine and my i9000 if that provides any helpful information.

length: 18
device class: 2
S/N: 0
VID:PID: 04E8:68C3
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!
[Galaxy S I9000 Android Development] distortedloop:
tried it on XP

Tried 1.2.0 command line on WinXP box.

Can download PIT info and close-pc-screen with heimdall and the Droid Charge, but any attempt to flash either a kernal zImage or recovery file results in a failure and a soft-brick that requires close-pc-screen to be ran to get a normal boot again.

Here's the output for a kernel flash that failed; the recovery file failed with same errors:

C:\Software from Dave>heimdall flash --kernel zImage

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

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

Downloading device's PIT file...
PIT file download sucessful

Uploading KERNEL
0%
ERROR: Expected file part index: 0 Received: 1
KERNEL upload failed!
Ending session...
Failed to receive session end confirmation!

I'm kind of screwed with this phone, heimdall won't work on either of my Macs, and Odin on the WinXP machine doesn't see the phone even though heimdall does.
[Galaxy S I9000 Android Development] Benjamin Dobell:
distortedloop, ah I just realised what I did wrong with the Mac release that's preventing the interface being claimed, I'll release an update ASAP.

However the failure during flashing is odd, especially since all the other functionality is working. It seems as though Samsung have intentionally changed the flashing protocol.

I'm not sure if it's really the best idea ever. However if you're capable of compiling from source, you could try change BridgeManager.cpp line 806, from:

for (int filePartIndex = 0; filePartIndex < sequenceSize; filePartIndex++)

to

for (int filePartIndex = 1; filePartIndex <= sequenceSize; filePartIndex++)
[Galaxy S I9000 Android Development] Benjamin Dobell:
The updated OS X package is now available. The binaries are the same, the .kext has just been updated for Galaxy S II and Droid Charge phones.
[Galaxy S I9000 Android Development] TA123:
Does 1.2.0 work with the 1.1.0 frontend or has to be used as command line tool only?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Yeah the 1.2.0 command line binary works fine with the 1.1.1 Frontend, however you're obviously limited to the functionality available from the frontend.
[Galaxy S I9000 Android Development] MoxFulder_CH:
I have an issue on OSX 10.5.8

mac:~ David$ heimdall close-pc-screen

dyld: unknown required load command 0x80000022

Trace/BPT trap

I have the same dyld issue from the frontend too. Any idea ?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Damn ye, OS X. Although I'd included a universal binary for heimdall I forgot to include a universal version of the libusb-1.0 library.

Anyway, new OS X binaries are now available. You only need them if you're on a x86 or PPC architecture.
[Galaxy S I9000 Android Development] distortedloop:
Where are the new binaries? The ones at Heimdall – Glass Echidna still show as 1.2.0 and the one I downloaded just now has the exact same MD5 checksum as the one I downloaded yesterday.
[Galaxy S I9000 Android Development] Benjamin Dobell:
It's still version 1.2.0 but the checksum definitely shouldn't be the same. You'll be able to tell if it's new because the new DMG doesn't include the README where as the old one did. The installer also no longer says "(beta)" anywhere.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Github seems to give me errors when I upload files. However they do normally upload. I think last time the server freaked out because I deleted a file and uploaded a file with the same name immediately.

Regardless I've uploaded the DMG once more and this time it seems to have worked as I've downloaded and checked it.
[Galaxy S I9000 Android Development] MoxFulder_CH:
I have downloaded the new 1.2.0 version and I still have the same issue. Should I uninstall the previous version first ? If yes : how ?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Hmm, the installer should have removed the broken libusb-1.0 library for you. You can check manually though, there should no longer be /usr/local/lib/libusb-1.0.0.dylib, instead there should be /usr/lib/libusb-1.0.0.dylib. There should also be no /usr/local/bin/heimdall, but there should be a /usr/bin/heimdall. i.e. The files should be in /usr/ not /usr/local/.

If this isn't the case then either I stuffed up the post installed script or you managed to download 1.2.0 prior to me uploading the good copy (I had to upload it twice). If that's the case then try download again. You can tell you have the good copy because the DMG will not have a README file.

Assuming that /usr/lib/libusb-1.0.0.dylib does exists, what is the output from the following command:

There will be probably problems with the Frontend unless you've applied one of two fixes. Either install Qt from Nokia's website or setup the work-around script in this thread. Sorry I don't have the link on me for the script but if you search this thread you should find it.

Assuming all the files exist in the correct location then Heimdall 1.2.0 command line should be working fine.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Okay, no more linking error though, that's good.

I'm not sure why your device is not being detected in download mode though. There were reports of 64-bit OS X (i.e. users that weren't effected by the libusb-1.0 dylib problem) being able to flash fine. With other (1st generation Galaxy S) devices weren't detected it was because the secondary bootloader had a bug in it, I haven't heard any reports of that with the SGS2 though. Did you say that you're able to flash from Odin within VirtualBox? If /System/Library/Extensions/heimdall.kext/ also exists then I'm at a bit of a loss, sorry!
[Galaxy S I9000 Android Development] distortedloop:
Okay, I just downloaded again and compared. This morning's download does not have the readme. All the other 1.2.0 files I've tried do. You might consider some subversion numbering (like 1.2.0a) to differentiate the two files. I can see potential for confusion here.

I was able to finally get Odin to flash the kernel I was trying to flash to the Charge on my friend's XP laptop after running through a couple of sets of drivers. Since I've got nothing to flash, can't test this just yet, but will do when I get a chance (perhaps just reflash the same thing).

Thanks for your efforts. I'll report back once I've tried it.
[Galaxy S I9000 Android Development] hlaube:
I tested the Win32-version of 1.2 under WinXP (Bootcamp on my Mac).

That works fine, had no problem to connect to the phone.
[Galaxy S I9000 Android Development] tkienzle:
suse 11.4 install

Hello i just installed then new 1.2.0 into suse 11.4 and wanted to know if i did it right.

When it runs it tells me its Heimdall v1.0.2b, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna

But that don't seem right.

I also installed the frontend 1.1.0 it tells me in the about tab that i have:

Heimdall Frontend

Version 1.1.0

and

Heimdall

Version 1.1.0

Does it over right the other when you install the frontend?

Are the frontend and 1.2.0 compatible?

Thank you for your time and awesome coding...
[Galaxy S I9000 Android Development] Benjamin Dobell:
I've responded to your e-mail as I saw it first. However feel free to respond here so others can benefit from any information exchanged.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry, evidently I'm not the best at updating version numbers inside the software itself! the v1.0.2b is a mistake, it's actually version 1.2.0. So that's all good. As far as the version info in the Frontend goes, just ignore it altogether, it's horrendously wrong :o

When I get a chance I'll address all these little quirks in a 1.2.1 update for both Heimdall and Heimdall Frontend. On a side note the 1.0.2b version mistake has already been fixed on Github and for the current OS X binaries (but not Windows or Linux).

EDIT: Heimdall 1.2.0 (command line) is compatible with Heimdall Frontend 1.1.1.