yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] gnac:
Petro_spina:

I used linux. I successfully flashed the cognition beta 5 rom.

I had originally (pre Heimdall) screwed the upgrade process from beta 3 and was left with a phone that stopped at the AT&T logo. All the instructions to fix were using odin.

At first I wasn't sure which files out out of the heimdall usage list were actually needed.

$heimdall
Usage:
heimdall --pit <file> [--factoryfs <file>] [--cache <file>] [--dbdata <file>]
[--boot <file>] [--secondary <file>] [--param <file>] [--kernel <file>]
[--modem <file>] [--delay <milliseconds>] [--verbose]

Then I found the flash.bat file in the heimdall/bin/windows folder which simply called heimdall with a specific list of files:

$cat bin/windows/flash.bat
Heimdall --verbose --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --boot boot.bin --secondary Sbl.bin --param param.lfs --kernel zImage --modem modem.bin

The breakthrough was discovering the cognition rom zip file and its sub .tar files included all of the files that heimdall flash.bat listed. Other Roms (including my own backups) did not.

Cognitionv2.2BETA5_ODIN $ ls
CSC.tar Install_Guide.png Odin.exe PDA.tar PHONE.tar PIT.pit

Cognitionv2.2BETA5_ODIN $ tar -tf CSC.tar && tar -tf PDA.tar && tar -tf PHONE.tar
cache.rfs
dbdata.rfs
boot.bin
cache.rfs
factoryfs.rfs
param.lfs
Sbl.bin
zImage
modem.bin

Confusingly, there were two separate copies of cache.rfs in the CSC and PDA tar files. I forget which I used.

Conversely, my backup roms only contained:

cache.img datadata.img data.img nandroid.md5 system.img

Perhaps all of the files in the cognition rom/ heimdall usage list are not necessary, but it was comforting to have them all there. So I finally ran:

$heimdall --pit PIT.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --secondary Sbl.bin --param param.lfs --kernel zImage --modem modem.bin

and after a short period where the phone informed me it was uploading files, it rebooted into my brand new ROM.

Perhaps someone could tell us parameters/files for the factoryfs.rfs, dbdata.rfs, boot.bin param.lfs options are required, or if there is a default. Otherwise, where do we get them if they aren't in our rom backups?
[Galaxy S I9000 Android Development] Benjamin Dobell:
I've just made the first official (i.e. non-beta) release which can be downloaded here.

I've added support for dumping files from the phone however the Galaxy S itself doesn't seem to support this properly. Both Heimdall and Odin yield the same results when trying to dump firmware, the phone eventually stops responding, it also doesn't seem to dump the requested information.

Unfortunately I wasn't able to include support for repartitioning. After looking into things more closely this functionality isn't handled by the Loke protocol but instead seems to be handled by adb when the phone is in the recovery menu. I might get around to including adb with Heimdall releases at some stage once I work out exactly what the required commands are.

A very big thanks goes out to the handful of people who have donated to me thus far!

The format has changed slightly in the 1.0.0 release. However, you're free to select exactly which files you wish to upload, the only parameter you must specify is the pit file. Selecting just a few files won't result in the non-specified files being deleted. Although you're free to select any combination of files I strongly recommended doing a full flash with files from the same firmware when possible. That way you're ensuring the files you're flashing are compatible with each other.

In regards to using nandroid's backups, I'm not actually sure what format they're stored in the correct rfs format as expected by the phone. If they are correct or can be converted then I can't see why it wouldn't work. I use nandroid as well myself to restore to previous versions of firmware, you can always flash a firmware with Heimdall and then use nandroid to restore an older version (although it doesn't restore certain files; zImage, boot.bin, SBl.bin and params.lfs).
[Galaxy S I9000 Android Development] ethanfel:
Hi, nice work, i'm actually trying to compile it from source under Ubuntu 10.10.

but when i try ./configure

i have :
[Galaxy S I9000 Android Development] Benjamin Dobell:
Agh, stupid me. Rename the "Heimdall Source" folder to "Heimdall-Source", spaces break configure for some reason. I'll upload a new zip with that fixed.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Okay, I've uploaded new version which should work now.

Thanks for letting me know.
[Galaxy S I9000 Android Development] ethanfel:
Thx for the quick reply.

But i have exactly the same issue when i rename my folder
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry yeah I've uploaded a new version.

However you should be able to run:

./autogen.sh

before running configure and that will hopefully take care of everything.

EDIT: Running autogen.sh requires you to have libtool installed, so if you don't you should just be able to download heimdall's source package again and hopefully it will work.
[Galaxy S I9000 Android Development] Riseofdead:
What Galaxy S devices has Heimdall been tested with?

We’ve tested Heimdall with a Galaxy S GT-I9000 (8 GB) from the United Kingdom and Galaxy S GT-I9000 (16 GB) from Australia. We personally don’t have access to any other devices to test with, however users have confirmed Heimdall functions correctly with the all rebranded variants of the Captivate, Vibrant, Fascinate, Mesmerize, Epic 4G, Galaxy S 4G, Infuse 4G, GT-I9000T, Galaxy Tab (7 and 10.1 inches), Galaxy S II (GT-I9100), Galaxy S III (GT-I9505) and of course the international GT-I9000.

really?

Edit:

ERROR Partition "primary-boot" does not exist in the specified PIT

Ending Session...

Rebooting device...

Releasing device interface...

Re-attaching kernel driver...

Ok, i tried with several options with command line. No one works. Heimdall 1.4.0 definitly does not work. Back to 1.3.1. my device is a Samsung Galaxy S2 I9100 (International Version with 16 GB)
[Galaxy S I9000 Android Development] kcrudup:
So try using "heimdall print-pit" to dump your PIT and see what the "Partition Name" is; for example, my GT-N8000 (Galaxy Note 10.1 3G) doesn't have a partition that works with the option "--modem", but if I use "--RADIO", it works (as that's name the modem firmware partition is called in the PIT).
[Galaxy S I9000 Android Development] RoryB:
It's been a long time since I read Heimdall stuff, but I think it is case sensitive. Try:

heimdall flash --[COLOR="Red"]RADIO [/COLOR]modem.bin
[Galaxy S I9000 Android Development] groksteady:
Just to be sure, do you have the right path to the file?
[Galaxy S I9000 Android Development] moviedrome:
I'll try that thanks

Yep, I've navigated to the directory in terminal before I run heimdall that contains modem.bin

Does anyone know if it's okay to just flash the modem? I'm not going to break it doing that am I? If that is successful then I may move on to rooting etc but I don't have access to Odin as I'm on a mac so it just seems to make things more difficult
[Galaxy S I9000 Android Development] dk75:
Dunno, but maybe try adding PIT to it:

heimdall flash --pit partitions.pit --RADIO modem.bin
[Galaxy S I9000 Android Development] moviedrome:
what does that do though? I haven't got a partitions.pit file?
[Galaxy S I9000 Android Development] dk75:
I've used GUI only, and there I've needed PIT file for partition to be recognized.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Well, the statement you've quoted is wrong, but only because the GT-I9505 is a SGS4, not an SGS3. But both the SGS3 (GT-I9300) and SGS4 (GT-I9505) have been tested and are supported.

Heimdall 1.4.0 does work, the trick is to read the README, or if you're an existing user, at least the release notes ;)

Support for legacy-style partition identifications such as --primary-boot has been removed from 1.4.0 because not all devices have the same partitions and as such the legacy partition identification was at best confusing, but mostly just wrong. From Heimdall 1.4.0 onwards you must use exact partition names, or partition IDs, which both can be obtained by printing the PIT.

This is correct, the partition names are case sensitive.

You don't need to provide a PIT file, if one is not provided Heimdall grabs the information from the device. Providing the PIT file is a counter-measure of sorts. If you provide a PIT file Heimdall will verify that it matches the PIT file on the device. If they don't match Heimdall will refuse to continue with the flash.
[Galaxy S I9000 Android Development] Benjamin Dobell:
This is correct, Heimdall Frontend does require a PIT file in order to provide you with a list of possible partitions to flash. However, as mentioned in my previous comment, a PIT file is not required from command line.

In any case, the current PIT can be downloaded from your device and saved to your computer using the "download-pit" command from command line, or from the Utilities tab in Heimdall Frontend.
[Galaxy S I9000 Android Development] moviedrome:
okay i've flased the modem and I got the following:

heimdall flash --RADIO modem.bin
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna

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:

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

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

Uploading RADIO
100%
RADIO upload successful

Ending session...
Rebooting device...
Releasing device interface...

So it says it's successful but now it is telling me I have no signal and to insert the sim? What do I do now? please help me

---------- Post added at 10:52 PM ---------- Previous post was at 10:28 PM ----------

heart attack over, i reflashed XXEMG4 and it has come back to life :)

That'll teach me to read properly before I flash, in the modems thread it clearly says you can't use older modems once you've gone to xxemg4.
[Galaxy S I9000 Android Development] mg2195:
Wondering if you plan on adding support to the Galaxy S4...more specifically the ATT variant (SGH-I337)

it appears to work with everything flashing wise...except the system partition...everything else goes through except system...i get this error:

Uploading SYSTEM
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!

Anything i can do to help with this? or is it something that I am doing wrong or am missing?

Again everything else appears to flash successfully
[Galaxy S I9000 Android Development] ushiyama:
Flash ext[n] image files

Instead of make an .rfs image i thinking in make an .ext2 or .ext4 image an try to use it to flash. I will work on factory.rfs and dbdata.rfs and make and modified factory.ext2 and dbdata.ext2 of them.

Can i use Heimdall 1.4.0 to flash it from linux to an I9000B device?
[Galaxy S I9000 Android Development] hakanbilir:
Crazy dll error. I insattled uninstalled restarted again again. Silly DLL...
[Galaxy S I9000 Android Development] jaythenut:
just found this well cool no more using my kids pc for odin

ive got a gs4 i9505 ,and heimdall cant download pit, anyone got any ideas , i am going into download mode:

DInitialising connection...

Detecting device...

Claiming interface...

ERROR: Claiming interface failed!
[Galaxy S I9000 Android Development] Ms. K:
Error using Heimdall on a MAC

HI,

I am unable to get my S4 into recovery mode no matter what form I try. I can get into the " downloading target screen".

When I used Heimdall. It detected my device. But when I tried to create my "PIT", I received this message.

Initializing connection

Detecting Device

Claiming Interface

Setting up Interface

Checking if protocol is initialized

Protocol is not initializing

Initializing protocol

ERROR:Failed to initialize protocol.

What should I do? I have the ROM, VirginRom on my phone. Everything works. But I saw that I had the incorrect Kernel.

I would appreciate anyone's help.

Ms. K
[Galaxy S I9000 Android Development] iXNyNe:
There two ways to look at your situation;

1) backups of EVERYTHING are always good to have. Making and maintaining backups is the safe and responsible thing to do whenever you start making your way through various device mods. They can really save you in case of an accident or major failure.

2) backing up your PIT is almost useless. PIT is the partition table and its rarely modified on modern android devices since 4.0 (ice cream sandwich) pretty much requires mtp partitioning. Back in the days of android 2.x (all the various flavors) many who wanted to switch from their manufacturers ROM to an aosp based ROM would need to repartition their device.

My honest advice to you is find a compatible kernel (make absolutely sure it is compatible with your ROM) and flash it using mobile Odin (there are plenty of instructions in the first few posts of the mobile Odin thread about how to safely do this). A proper kernel should include a working recovery, but if not look into clockworkmod (cwm) or team win (twrp) which you should be able to install as long as you can get adb (if heimdall detected your device then adb should be working)

Heimdall is an awesome tool but sounds like overkill for what your currently doing (which sounds like you just need a working kernel/ROM/recovery combination). Once you have a working recovery, do a nandroid backup (backup from within the recovery).

If anything I've said above is incorrect, I'm sorry for being a bit out of date, I haven't needed heimdall or Odin in quite some time personally.
[Galaxy S I9000 Android Development] Ms. K:
Incorrect situation

Hi,

Thank you so much for your time. I actually had the right kernel but for some reason the Loki zip must not have went through. I actually got my recovery back by taking back to where I purchased it from. I"m looking at the ROM, Graviton now.

http://xdaforums.com/showthread.php?t=2372742

I love how helpful everyone here is. Thank you so much for your time.

Ms. K

Samsung s4

Model Number

Samsung SGH-1337

Android Version

4.2.2

Baseband Version

1337UCUAMDL

Kernel Version

3.4.0-453947

se.infra@SEI-46 #1

Sat Apr 27 17:06 KST 2013

Build Version

JDQ391337UCUAMDL
[Galaxy S I9000 Android Development] Zen Arcade:
I'm seeing a similar error message with the US AT&T i317 Note 2 when attempting to flash the modem. The modem flashes to 100% (correctly -compared a dd dump with original) then ends with:

ERROR: RADIO upload failed!

Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...

(Then below the status window left of the progress bar, "Failed to confirm end of file transfer sequence!")

UPDATE (face palm) - This error is a result of attempting to flash a modem pulled from the phone after an OTA update using "dd" and not stripping the trailing zeros off the file. On the i317, Samsung is signing the modem.bin with a CA cert and the bootloader is erroring out if the file is not the correct length. (After editing the modem.bin to the correct length, the Heimdall flash worked flawlessly).

To recover from the bad flash was easy enough - flash a known working package in download mode.

Benjamin - Both mg2195 and I arrived here independently, but both were long time Samsung Infuse users, and have benefited from your work and that of Adam Outler. Heimdall and Heimdall-One-Click roms and kernel packages were provided by qkster and have been used extensively by many on the xda Infuse forum. Thank you for making that possible.
[Galaxy S I9000 Android Development] perosredo:
Note 3 (N900W8) Support

Does Heimdall have support for the Galaxy Note 3?

I personally have the N900W8 Rogers/Canada LTE Variant and am using Ubuntu 13.10.

EDIT:

Got it to work eventually: http://xdaforums.com/showpost.php?p=46237129&postcount=221
[Galaxy S I9000 Android Development] svs57:
i need help. heidmall can't open large files for example my system.img (2367450528 byte)

I recompile heidmail with -D_FILE_OFFSET_BITS=64

now it can open my system.img

but i got new error:

ERROR: Failed to confirm end of file transfer sequence!

I know that there is patch for this error.

do anybody have this patch?

I downloaded latest sources but still have this error

I don't have 64 bit pc to flash...

please help me
[Galaxy S I9000 Android Development] fastguy:
I'm trying to flash a Samsung HomeSync GT-B9150 with a modified boot.img that I packed, trying to root it.

heimdall 1.4.0 is flashing the stock one perfectly, but when it comes to flashing mine, it states:

ERROR: Failed to confirm end of file transfer sequence!

Same thing happens on Odin 3.07 and Odin 3.09. Is it possible that there's some kind of bootloader lock etc that does not let me flash firmware? I could unpack the boot.img in the stock firmware file and re-pack it without issues. But I just can't flash it.
[Galaxy S I9000 Android Development] Dijinn:
I've been trying to flash the TZ partition on Galaxy S4 Mini Duos for 3 days now and no success...

I flashed the original kernel via Heimdall, all of it, all partitions, but after doing it, wi-fi was gone... As far as ppl noticed already, this seems to be a problem with this TZ partition... No matter how many times I flash it via Heimdall, it seems Heimdall flashes it in, but when the system comes up, nothing... I got no clue on how to solve this...

help? xD anyone? please? xD
[Galaxy S I9000 Android Development] yermandu:
ClockworkMod

CWM works fine with heimdall?

Before to install Cwm (Download Mode) i was goting

ERROR: Setting up interface failed!

Now, i got (Recovery Mode)

ERROR: Failed to detect compatible download-mode device.

Its a i9000 based, i see in the heimdall dev page some bugs related, waiting for some news :fingers-crossed:
[Galaxy S I9000 Android Development] hardik190:
i want to extract pit file from my bros mega 5.8 but when i try to run it in windows 8 its giving me error MSVCPR100.DLL not found what is the solution .. ??
[Galaxy S I9000 Android Development] :
reading partitions

Sorry for what is probably a FAQ.

Clearly, heimdall can read partition layout and write image files to partitions (and even repartition).

But, I wonder, can it (or, better stated does Loke also support) also read any partition and save the content to image files.

For example, before I flash (write) a recovery.img with heimdall, I would first like to (read) save existing (stock) one, so that, if flashed one is bad, I can revert back to previous saved one.

Thanks for heimdall and happy 2014
[Galaxy S I9000 Android Development] JulioQc:
I hope this is not a repeat...

When trying to lauch the frontend (ore Heimdall), all I get is a "heimdall-frontend.exe is not a valid win32 application" error message.

Im using WinXP x86 with admin rights, latest .NET SDK and followied instructions for driver install in readme.txt
[Galaxy S I9000 Android Development] dk75:
But do you have this?

http://www.microsoft.com/en-au/download/details.aspx?id=30679
[Galaxy S I9000 Android Development] anly11:
is the new version 1.4.0 intended to flash also galaxy i9000 or is it for other models? because i have tried flash firmware on my i9000 with 1.4.0 but i got error and program did not make flash. then i have tried 1.3.1 and everything went right. i am working in linux system.
[Galaxy S I9000 Android Development] microMXL:
I'm using v1.4 RC2 on archlinux and no problems flashing i9000
[Galaxy S I9000 Android Development] jtl999:
MSVCP100.DLL is missing but have Visual Studio 2010 Ultimate SP1.

Hi.

When I try and launch Hemidall I get the error MSVCP110.DLL is missing. I tried repair installing the redistributes but that did not help. I'll try installing the latest Windows Updates. Even though that is most likely not going to help. I already have Visual Studio 2010 Ultimate SP1 installed though. Any help?:confused:
[Galaxy S I9000 Android Development] AdamOutler:
Put this: https://android-casual.googlecode.c...icationstools/heimdall/resources/msvcp110.dll

And this:https://android-casual.googlecode.c...icationstools/heimdall/resources/msvcr110.dll

Into the same folder with Heimdall.exe. that's all the MSVCRedist is used for.
[Galaxy S I9000 Android Development] jtl999:
Works. Thanks
[Galaxy S I9000 Android Development] ngoonee:
Wanna maintain the AUR package for it? I uploaded it and maintain it but haven't bothered in a while since I've not been actively using heimdall. PM me =)
[Galaxy S I9000 Android Development] universed:
Flashing TWRP?

I am trying to flash TWRP via heimdall to my unrooted SM-N900T Note 3 from T-Mobile. I want to then flash SuperuserSU to root the device.

I tried to run the following command from the command prompt in Windows 7 in the Heimdall directory:

heimdall flash --RECOVERY openrecovery-twrp-2.6.3.1-hltetmo.img and I get a "Failed to access device. libusb error: 12". My Note 3 is connected in download mode and the drive is showing up as "Samsung Mobile USB Modem".

I am able access my device from the Heimdall front end. Can I simply add the TWRP IMG into a recovery partition via the Heimdall frontend or is there more to this?
[Galaxy S I9000 Android Development] universed:
I am rooted, I flashed TWRP through Odin and that did the trick.....
[Galaxy S I9000 Android Development] devrieshh:
does heimdalll support the samsung galaxy gio already?
[Galaxy S I9000 Android Development] devrieshh:
Whell you can flash everything by sideloading, so no need to use heimdall as far as i know.

(as far as your recovery modus is accesseble...)
[Galaxy S I9000 Android Development] ice.modding:
works on i9500?
[Galaxy S I9000 Android Development] ErikMunoz:
Heimdaill on xubuntu

Hello guys

im trying to use the tool in Xubuntu 13.10 x64 and i've got this messge:

(heimdall-frontend:2149): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed

that message appear when i clicked on "detect"

Have you seen it before?

i hope you can help me to get it run.

Edit:

I succefully flashed a galaxy s3 ( I747 ATT ) :D :D :D

question: is there a way to only perform a wipe like a fatory reset?
[Galaxy S I9000 Android Development] myanogencod:
First big thanks to the developer.

He's one of the very few people helping Linux users use their open-source environment to deal with Android - Linux desktop issues. (and shame on you samsung and others!)

Now, I've been tasked to "cure" a recently released samsung (yes...) Galaxy Grand 2 dual-sim (SM-G7102) and wonder if the flashing process using the Odin protocols is generic enough to try and use Heimdall? Point being that is something goes awry I'm in a pickle with no access to that proprietary OS. :fingers-crossed:

The phone itself is actually quite pleasant to use. Similar to Moto G but with removable storage *and* large removable battery.

Edit: There's a cross-platform (Java) frontend/add-on to Heimdall, built by the developer's mate, that uses Samsung's own "odin" data for flashing without the need to package that model's specifics for Heimdall: jOdin3 . How did I miss it... :^)
[Galaxy S I9000 Android Development] DF5JT:
Restore EFS Backup

I'd like to use Heimdall to flash a nandroid backup of my EFS partition, a file called 'efs.ext4.tar'. This tarball contains files and directories, i.e. it is not an image of a block device. How can I convert this file into a heimdall compatible 'efs.img.ext4'?
[Galaxy S I9000 Android Development] rjh1:
Can someone please help me, I downloaded this program as well as vcredist_x64 and when I try to run heimdall it gives me a error "MSVCP110.dll is missing from your computer." I have uninstalled and re installed many times as well as rebooted the computer and tried again .... still same error. what am I doing wrong?

Rick