heimdall can flash samsung galaxy S phones in "download" mode, it can be used as a substitute to the official leaked odin tool. I have tested it on a Galaxy-S GT-I9000 and it works like a charm. Reproducible: Always Steps to Reproduce: 1. emerge heimdall Actual Results: emerge exits with: emerge: there are no ebuilds to satisfy "heimdall" Expected Results: emerge heimdall installs the heimdall library and frontends The ebuild is not complete because I can't get the qt app to build. I'll leave that for someone more versed in QT to do (the build works fine, i have a feeling the receipe of heimdall-frontend is ignoring the PREFIX).
Created attachment 261061 [details] ebuild for http://www.glassechidna.com.au/products/heimdall frontend installation doesn't work because it ignores PREFIX and thus gets a sandbox violation
Minor nitpick - that pkg_postint should probably be more along the lines of net-wireless/bluez.
Created attachment 261093 [details] heimdall-9999.ebuild with proposed modifications
done.
Created attachment 263497 [details] heimdall-9999.ebuild Install frontend now works and is enabled by default. Some minor syntax cleanup. Fresh ebuild is always in my repo @ http://gitorious.org/flow-s-ebuilds/flow-s-ebuilds/blobs/master/app-mobilephone/heimdall/heimdall-9999.ebuild
Created attachment 271127 [details] heimdall-9999.ebuild Slightly reworked ebuild: - added an ebuild header - replaced "frontend" USE flag with "qt4" - fixed quoting in several places - fixed tab spaces - added "|| die" in several places - added sed-line to fix deprecated udev-rules syntax
Quick question: which portage category this ebuild may have ?
(In reply to comment #8) > Quick question: which portage category this ebuild may have ? I reply to myself since i browse portage to choose one for my overlay and i have notive the existence of the "app-mobilephone" category that i never saw before. PS: sorry for the double comment but bugzilla tell me that a collision have occurs when i posted.
Created attachment 276812 [details] heimdall-9999.ebuild Small change for the ebuild from Lars Wendler (Polynomial-C). The Makefile has slightly changed: reload -> restart See also: https://gitorious.org/flow-s-ebuilds/flow-s-ebuilds/commit/c5385be1afaedc3aa13d67428b2da4834d05c5c7
When trying to install heimdall from the poly-c overlay at some moment I get: make install-data-hook make[2]: Entering directory `/var/tmp/portage/app-mobilephone/heimdall-9999/work/heimdall-9999/heimdall' sudo service udev restart libtool: install: /usr/bin/install -c heimdall /var/tmp/portage/app-mobilephone/heimdall-9999/image//usr/bin/heimdall sudo: service: command not found I could install it fine before. Any ideas what is going on? Simon
Simon: Thats what my previous comment is about.
Thanks Florian, it works now. I downloaded your ebuild instead of using poly-c. Simon
The ebuild does not work for me. Any suggestions what I need to change? >>> Compiling source in /var/tmp/portage/app-mobilephone/heimdall-9999/work/heimdall-9999 ... make -j9 DESTDIR=/var/tmp/portage/app-mobilephone/heimdall-9999/image/ make all-am make[1]: Entering directory `/var/tmp/portage/app-mobilephone/heimdall-9999/work/heimdall-9999/heimdall' make[1]: *** No rule to make target `../libpit/libpit-1.3.a', needed by `heimdall'. Stop. make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/var/tmp/portage/app-mobilephone/heimdall-9999/work/heimdall-9999/heimdall' make: *** [all] Error 2
Created attachment 288675 [details] updated ebuild with proposed fixes from here plus build of libpit
the ebuild should be updated to use the new git-2 eclass.
Created attachment 289557 [details] Ebuild updated to use git-2 eclass, some modifications from zugaina overlay The ebuild now uses the git-2 and qt4-r2 eclasses instead of their older counterparts, there are also some other minor modifications to the ebuild.
Created attachment 322663 [details] heimdall-9999.ebuild Update: - using virtual/libusb:1 insted of >dev-libs/libusb-1 - added sys-libs/zlib to DEPEND - deleted --prefix and others from econf (econf has --prefix defined) - more userfriendly output - added desktop entry for heimdall-fronend (without icon)
heimdall-frontend doesn't seem to be getting installed correctly with the current HEAD, it's getting built, but doesn't end up in the resulting package.
* * Configuring heimdall-frontend... * * Running qmake ... RCC: Warning: No resources in 'mainwindow.qrc'. WARNING: target.path is not defined: install target not created ... * * Installing heimdall-frontend... * make -j4 OUTPUTDIR=/mnt/datapool/tmp/portage/app-mobilephone/heimdall-9999/image/ install make: Nothing to be done for `install'.
Fix is here: https://github.com/korneliuszo/Heimdall/commit/f47f47ca45523a0c92e59d81da29ed6cad3c53ee
Created attachment 337328 [details] Heimdall 1.3.1 ebuild Since v1.3.2 has problems with certain devices, this ebuild pulls a v1.3.1 tarball from GitHub and builds that.
AFAIK current 1.4.0-rc1 has those problems fixed. I would target that version first and foremost. I have first hand success on complete reflashing both P1000 and P7300 with 1.4.0-rc1.
Created attachment 355508 [details] heimdall-1.4.0.ebuild Tried to clean up the ebuild a bit. Dunno if the pushd/popd combination is really useful in this case but that can be changed easily.
I've been maintaining an ebuild in my overlay for a while, so I figured I would add it to the tree. +# ChangeLog for app-mobilephone/heimdall +# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*heimdall-1.4.0 (18 Aug 2013) +*heimdall-9999 (18 Aug 2013) + + 18 Aug 2013; Mike Gilbert <floppym@gentoo.org> +heimdall-1.4.0.ebuild, + +heimdall-9999.ebuild, +metadata.xml: + New ebuild, resolves bug 353180.
Scott's ebuild works fine with minor fixes for me in amd64. Current ebuild (heimdall-1.4.0) in Portage needs big ~amd64, like udev and openrc.
(In reply to Jaime Martin from comment #26) > Scott's ebuild works fine with minor fixes for me in amd64. Current ebuild > (heimdall-1.4.0) in Portage needs big ~amd64, like udev and openrc. I have no idea what that means. If there is a problem with the current ebuild, file a new bug.
