[PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available)
- Thread starter Benjamin Dobell
- Start date
-
- Tags
- noad
Essentially yes. Although you can actually flash over the backup secondary bootloader if you really want to. Heimdall 1.1.1 allows you to do this via command line, the functionality is intentionally not available from Heimdall Frontend.I'm curious... so there is an always untouched backup secondary bootloader, that can be reached with the JIG and a working primary bootloader?
So the only real way to brick is to **** up the primary bootloader?
Thank you for all your efforts
There may also be a backup primary bootloader, although I am yet to find any reference to one.
I cant have Heimdall 1.1.1 working on Snow Leopard.
When I try to open it I receive a message saying that it can't be opened due to some problem, so I tried the fix mentioned in this thread:
I created a file called heimdall-frontend and wrote the follwing content inside it:
But when i click on the app nothing happens... Any other tips?
When I try to open it I receive a message saying that it can't be opened due to some problem, so I tried the fix mentioned in this thread:
I created a file called heimdall-frontend and wrote the follwing content inside it:
Then i placed it inside /Applications/heimdall-frontend.app/Contents/MacOS and changed the name of the file that was previously there from heimdall-frontend to heimdall-frontend-old
But when i click on the app nothing happens... Any other tips?
Hi all
I had problems running the heimdall-frontend on mac which was exiting with the following errors in Console:
PHP:12.01.11 14:17:03 [0x0-0x428428].com.yourcompany.heimdall-frontend[14266] dyld: Library not loaded: QtGui.framework/Versions/4/QtGui 12.01.11 14:17:03 [0x0-0x428428].com.yourcompany.heimdall-frontend[14266] Referenced from: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend 12.01.11 14:17:03 [0x0-0x428428].com.yourcompany.heimdall-frontend[14266] Reason: image not found
And to fix this I wrote a really simple bash script to start the GUI
PHP:#!/bin/bash cd '/Applications/heimdall-frontend.app/Contents/Frameworks/' ../MacOS/heimdall-frontend > /dev/null &2>1 exit 0
And now Heimdall's UI starts without problems
Edit: if you put this script inside /Applications/heimdall-frontend.app/Contents/MacOS, rename heimdall-frontend to heimdall-frontend-old, then name this script heimdall-frontend and edit the third line to replace heimdall-frontend with heimdall-frontend-old and Heimdall will start normally
Err.....with all dues respect can we have this in simple instructions please? File name, paths....etc?
Just IGNORE that post. The fix is to install the QT Framework. Nothing more, nothing less. This makes it extremely easy. No modification of anything. Just install and it's fixed.
I am happy with CLI version of Heimdall. It is very straight forward and easy to use. Learn how to use command shell.
Sent from my Nexus One using XDA App
Perhaps you can make a youtube video on how to do just that.
thanks mate but... where can i download qt framework?
I'm mobile so I don't have the link handy, but I did link to it a few pages back.
Hemidall force quits on launch, mac version
Hi,
Just downloaded the newest version of hemidall yesterday (first time install) and after running the installer and rebooting hemidall front end wont launch.
Helow is the information provided by the problem report. let me know if i can be of any more help/how we can fix this.
Looks like it's not loading QtGui.framework/Versions/4/QtGui - is it just my system that doesnt have this? where should i get it?
Process: heimdall-frontend [11994]
Path: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend
Identifier: com.yourcompany.heimdall-frontend
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [203]
Date/Time: 2011-03-15 08:00:54.824 +0800
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6
Interval Since Last Report: 159090 sec
Crashes Since Last Report: 7
Per-App Crashes Since Last Report: 7
Anonymous UUID: A244B10F-CFB1-45E3-A124-C52EB321712A
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 (???) <A4F6ADCC-6448-37B4-ED6C-ABB2CD06F448> /usr/lib/dyld
Hi,
Just downloaded the newest version of hemidall yesterday (first time install) and after running the installer and rebooting hemidall front end wont launch.
Helow is the information provided by the problem report. let me know if i can be of any more help/how we can fix this.
Looks like it's not loading QtGui.framework/Versions/4/QtGui - is it just my system that doesnt have this? where should i get it?
Process: heimdall-frontend [11994]
Path: /Applications/heimdall-frontend.app/Contents/MacOS/heimdall-frontend
Identifier: com.yourcompany.heimdall-frontend
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [203]
Date/Time: 2011-03-15 08:00:54.824 +0800
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6
Interval Since Last Report: 159090 sec
Crashes Since Last Report: 7
Per-App Crashes Since Last Report: 7
Anonymous UUID: A244B10F-CFB1-45E3-A124-C52EB321712A
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 (???) <A4F6ADCC-6448-37B4-ED6C-ABB2CD06F448> /usr/lib/dyld
Hi developer,
How about create a Personal Package Archives(ppa) for Ubuntu?
https://help.launchpad.net/Packaging/PPA
How about create a Personal Package Archives(ppa) for Ubuntu?
https://help.launchpad.net/Packaging/PPA
I'll look into it.
Qt can be downloaded here. There is also a work-around detailed a few pages back within this thread.
Haha, yeah it's not meant to crash. In fact Qt is already included (as a private framework) when you download Heimdall Frontend. However there is some weird issue whereby OS X is not able to find private frameworks (and hence Qt).
That is correct, go with the library only release. If you want to avoid downloading Qt then take a look at the fix a few pages back, it's simply a work-around that allows OS X to find the private framework Qt at run-time, so no need to download anything.
Hi guys, I tried flashing with Heimdall on my Macbook Pro however when I click the start button I get the following error message, dyld: unknown required load command 0x80000022
I followed the instructions in the OP and extracted the individual files from the .tar and slotted them into the appropriate place in the front end app.
I followed the instructions in the OP and extracted the individual files from the .tar and slotted them into the appropriate place in the front end app.
You're running OS X on your Macbook Pro? I'm not entirely sure what that error is given that the user interface displayed correctly, perhaps Heimdall Frontend is unable to find the heimdall binary. Are you able to run Heimdall from terminal?
Yes, currently running OS X 10.5.8. I just tried launching Heimdall from terminal and was successful but the issue still persists. Actually I was always able to open the application but it was just that each attempt to initiate the flashing process resulted in that error message.
Are you able to run heimdall command line tool from the terminal? Have a look at the README for basic documentation.
Similar threads
- Poll
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
254What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash ROMs onto Samsung Galaxy S devices.
How does it work?
Heimdall uses the same protocol as Odin to interact with a device in download mode. USB communication in Heimdall is handled by the popular open-source USB library, libusb-1.0.
Why “Heimdall”?
The flashing software Odin is named after the king of gods in Norse mythology. Loke, the software component on the Galaxy S that provides functionality to flash, may also to be named after an important character in Norse mythology, often translated as Loki. As such I have named my flashing software Heimdall, after the Norse god, and guardian of the Bifrost Bridge.
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Why use Heimdall when we can use Odin?
Odin is generally unreliable and only runs on Windows systems. Furthermore, Odin is leaked Samsung software that is not freely available or well understood by the community.
Is Heimdall safe?
No matter what method you chose, flashing firmware onto your phone has a lot of potential for disaster. We have tested Heimdall with a variety of phones flashing several different firmware versions resulting in a 100% success rate. As such we believe that Heimdall is generally reliable. However keep in mind, just like any flashing software, Heimdall has the potential to brick your phone if not used correctly.
How do Galaxy S phones get bricked when flashing?
Besides the inherent risks like power outs, accidental removal of the USB cable etc. The Galaxy S appears to be running extremely unreliable USB control software.
A failure to flash does not automatically equate to a bricked phone. However if you're extremely unlucky and the flash fails whilst transferring the primary boot-loader, secondary boot-loader or params.lfs (all quite small) than you've got yourself a paper weight that you're hoping Samsung will replace.
Please be extremely careful mixing files from different firmware releases. Don't do so unless you're certain it will work!
What Galaxy S variants 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 don’t personally have access to any other devices to test with, however users have confirmed Heimdall functions correctly with the AT&T Captivate, Bell Vibrant, Telstra GT-I9000T, Epic 4G and the Galaxy Tab.
Enough talk, where can we get it?
The latest release is available here. Please read the instructions and README files included in the archives.
I love you, man. Will you have my baby?
No, but I will very gladly accept donations. If you appreciate my work and would like to support future development you can make a donation here. If you think you have something else to offer, then feel free to shoot me a PM or contact me via the contact form on the Glass Echidna website.8My response to the extremely rude user whose e-mail is included in my previous post:
7Hey 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.5Source 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.4
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.
