It's okay. We're all busy people. That's cool that it was easier than expected! Probably something you were quite happy about I bet.
Woh, sorry about not getting back to you guys, I didn't see the posts :S
Yeah Heimdall supports repartitioning since version 1.1. It was actually quite a bit easier to implement than I expected, the phone itself seems to automate it when you flash a new PIT file.
I could have sworn I edited my post and included an answer to that.
The reason is that when you repartition several partitions are being wiped, including the primary and secondary bootloaders. I don't know if the device is smart enough to back-up the bootloaders prior to the wipe and restore them afterwards. However I'm not particularly keen to find out either. If the device doesn't back-up and restore the bootloaders when you repartition then your device will be unable to boot at all i.e. hard bricked.
Maybe someone with the ability to do a JTAG restore would be willing to test this for you. This guy,
connexion2005 offers that JTAG service on his website and is pretty involved in the XDA community.
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
Does this program only work with 64 bit architecture? I am running 32 bit linux system is there a way to get this to work?
git clone git://github.com/Benjamin-Dobell/Heimdall.git
It's been a while since I cross compiled, but you don't need to be using the environment you want to compile for. Back in the day, I used to compile for all kinds of different architectures (ppc, 64bit, etc.) from my 32bit amd processor.A lot of you will be happy to know that I grabbed a 32-bit version of Ubuntu 10.10 today. So I'll compile and publish official 32-bit debian binaries soon. If I get a chance I'll try finish off 1.2 as well.
Thanks for the advice, I have cross-compiled in the past (to ARM usually) however this works out to be slightly easier for me. Otherwise I'd have to setup a proper cross-compiling environment with 32-bit libraries as well as an environment to build the debian package (which is unfortunately the hard part).It's been a while since I cross compiled, but you don't need to be using the environment you want to compile for. Back in the day, I used to compile for all kinds of different architectures (ppc, 64bit, etc.) from my 32bit amd processor.
I believe the command to gcc should be something like -m32 and -m64.
Sounds interesting.. Certainly something to watch in the future..
[Name Redacted],
Am *I* kidding...? Really?
Instead of whinging to developers who volunteer their free-time to provide the community with free and open-source software, perhaps you could get of your arse and contribute.
Firstly, did you actually read the README? It includes extremely detailed steps that explain precisely how to use both Heimdall and Heimdall Frontend? Did you even bother to look for official documentation? Considering you intend to flash a device I'd say 8 hours of reading isn't at all unreasonable. You should actually have some comprehension of what it is you're trying to achieve, unless you'd like world's most expensive paperweight sitting on your desk. The process is only a disarray if you take no logical steps to understand it, the obvious first step being; read the README!
Secondly, how in all honesty do you expect me to support every variation of Samsung device ever released? I can assure, there's a lot. I live in Australia, we don't even operate archaic CDMA networks here! The software was originally written for the international Galaxy S (GT-I9000). The fact that it works with any of Samsung's other of devices is little more than a coincidence. *If* you would like support for the Galaxy CDMA tablet, aside from implementing it yourself (it's open-source after all), then perhaps you should consider donating towards the cost of purchasing such a device. Alternatively, perhaps you would consider mailing your tablet to me and paying the postage for me to return it to you when I'm done. Then I'll volunteer *my free-time* to add support for yet another device. Because believe it or not I can't afford to spend tens of thousands of dollars purchasing every variation of every device under the sun in exchange for the occasional donation, which mind you, don't even cover my bandwidth costs!
I strongly suggest next time you give some thought to what you write before contacting someone who gives up their free-time to help people just like you.
- Ben
i.e.
Walah! You now have a complete list of all the files your device supports.
I've used GUI only, and there I've needed PIT file for partition to be recognized.