yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] zurchpet:
Coud you check if your kernel runs in 32-bit or in 64-bit mode? Activity Monitor -> kernel_task -> Type (Intel or Intel (64-bit))
[Galaxy S I9000 Android Development] toansta:
i think it's 64 bit. all other programs are 64 bit but i don't see kernel_task

will it pop up if i had the phone plugged in?
[Galaxy S I9000 Android Development] gehzumteufel:
Just go to about this Mac, click more info, then software. It will say 64 bit extensions and have a value of yes or no.
[Galaxy S I9000 Android Development] cornholio_rules:
Thanks Benjamin, it seems as you say that for some unknown reason the Sbl.bin file just don´t want to let go. Maybe this is because my SGS was branded, it was also very difficult to unlock, maybe it got special bootloaders. Anyway I don´t wanna mess around with it because I don´t wanna lose my 3 button combo and you should´t either!

Well it´s a pity that you can't do the rev. engineering, hope someone does someday or maybe it's not worth it. Nevermind, it's not the end of the world, I'll wait for a good GB release for the I9000T. :)
[Galaxy S I9000 Android Development] gehzumteufel:
The only way you will lose the 3button combo, is if you flash a very specific PBL (Primary BootLoader). Otherwise, it is impossible to lose the 3 button combo. The SBLs out there, whether it be for the very small number of i9k's or the very large number of Vibrants that were locked, you MUST have the PBL that has it locked. Otherwise, the combo is not locked. And I will add, that the only PBL that has it locked, is a PBL in which you can't find anymore.

Also, I've found that ODIN seems to flash the SBL fine, but Heimdall seems finicky. So I suggest flashing the SBL through ODIN if possible.
[Galaxy S I9000 Android Development] Benjamin Dobell:
If you're able to ascertain a usb packet log of flashing the SBL in Odin and e-mail it to me that would be fantastic. If it's too much hassle don't worry though.

EDIT: e-mail is service [_at_] glassechidna.com.au
[Galaxy S I9000 Android Development] gehzumteufel:
I can attempt to do that. I do need to flash my current device with a Mac compatible SBL. Since I've never done this before, do you have a recommended software that can do this on Win7?
[Galaxy S I9000 Android Development] zacharias.maladroit:
awesome program !

it just saved me from booting into Windows ! :D

Thanks a lot !
[Galaxy S I9000 Android Development] Benjamin Dobell:
I haven't tried this myself as I only updated my dev machine to Windows 7 last weekend. Although apparently Windows 7 has in-built USB logging functionality.

I only need a capture of Odin flashing a Sbl.bin where Heimdall would otherwise fail. So if Heimdall is able to flash a Sbl.bin fine with your device at the moment then don't worry about it.

Thanks
[Galaxy S I9000 Android Development] gehzumteufel:
I haven't tried to flash an SBL with this specific unit yet. So I haven't a clue whether or not it will fail. I just know on the one before the last one, it was flaky when flashing an SBL. I could flash modems and everything else fine though. Maybe it was just that unit. Not sure.
[Galaxy S I9000 Android Development] cornholio_rules:
That's very interesting gehzumteufel, but I'm really tired of this ....! Besides, I don't wanna brick my phone, I read a case about someone who bricked flashing Sbl.bin.

Thanks anyway!

P.S. hehe, why so rude nick? :)
[Galaxy S I9000 Android Development] gehzumteufel:
It's possible to brick it, yes. Anytime you mess with bootloaders, you can brick your phone. This is why it is usually highly advised not to bother, unless you have a really serious need to.
[Galaxy S I9000 Android Development] toansta:
ok so i don't have 64 bit extensions,

where do i go from here?
[Galaxy S I9000 Android Development] froysm:
Hello, i'm having the exact same problem! Also, it happens the same when i try to flash a modem.bin with heimdall.

I have a I9000T too.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Hmm, I'm going to need someone to get a USB packet log of both failed flashing with Heimdall and working flashing with Odin in order for me to resolve this. Either that or I'll need to get my hands on a I9000T, but I think the former is substantially more likely.
[Galaxy S I9000 Android Development] lilstevie:
did you ever figure out flashing moviNAND?
[Galaxy S I9000 Android Development] froysm:
I can get you the log of the failed flashing. Btw its just the Mexican I9000T.
[Galaxy S I9000 Android Development] froysm:
Hey! I just got the packet dump of the failed flash using wireshark, do you need a pcap file? Csv? Txt? Or what format?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Any file I can read should be fine, if you want you can send it in multiple formats just to be safe. However I have a feeling a capture of a working flash with Odin (on a device that fails with Heimdall) is going to be a lot more useful than a failed flash.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Was it you that contacted me about that via PM or e-mail? I remember someone asked but I think I forgot to respond.

However yes I have worked it out. I haven't tried it though cause I have a GT-I9000. It's simply a matter of getting the correct partition ID, which is stored in the PIT file.

In fact I've actually got some code for the next release of Heimdall that reads PIT files from the phone the same way as Odin does. The only problem with using PIT files is that is that files being flashed are matched to partition IDs by their name. However I want to continue allowing users to manually select any partition ID and flash files with any name. As a result I'm going to have to come up with some sort of hybrid approach that is partially hard-coded but also allows users to manually select any partition that isn't already supported/hard-coded. This way people won't have to wait for me to make a new release if a new partition pops up or if users want to make their own PIT files.
[Galaxy S I9000 Android Development] lilstevie:
yeah I PM'ed you on github, the soft method sounds great, as I actually create an extra partition, being able to generate a pit that includes the new partition data to flash would be so much easier than the current method of rooting around in recovery making and formatting the partition
[Galaxy S I9000 Android Development] froysm:
I think that will be impossible... You see, I can't flash the Sbl.bin file even with Odin!
[Galaxy S I9000 Android Development] CTown:
Ubuntu Natty Packages

I hope you don't mind if post two packages for Ubuntu Natty (which will be officially released on the 28th). Sorry, if someone already made packages for Natty. I used checkinstall to create these packages, which the Readme recommends. Just extract the archive and install heimdall first and then install heimdall-frontend.

I tried to depend on the least number of packages as possible. Please tell me if I forgot to require something:

heimdall only depends on libusb-1.0-0.

heimdall-frontend depends on heimdall & libqtgui4 (which depends on libqttcore4).
[Galaxy S I9000 Android Development] Benjamin Dobell:
I don't mind at all :)

Although I should probably check... Are there problems with Natty and the Heimdall packages linked to on the official Heimdall page?

EDIT: Those dependencies seem correct to me.
[Galaxy S I9000 Android Development] nedooo:
How to revert drivers so I can use Odin again? Thanx
[Galaxy S I9000 Android Development] Benjamin Dobell:
Detailed instructions are included in the README. Alternatively you might just be able to use a different USB port on your PC.
[Galaxy S I9000 Android Development] Razer(x):
Is there any precompiled package for archlinux?

Sent from my Galaxy S
[Galaxy S I9000 Android Development] Benjamin Dobell:
Official ones, no. However there are definitely user-compiled copies floating around:

https://aur.archlinux.org/packages.php?ID=42632
[Galaxy S I9000 Android Development] Razer(x):
Thanks, is it normal to have no gui?

EDIT: Fixed launching heimdall-frontend
[Galaxy S I9000 Android Development] CTown:
Sorry, I guess I missed those. Also, how does one add a .desktop file in a package created by checkinstall? I releaized one is not included. Other packages I installed through checkinstall include one. Sorry for not being on topic.
[Galaxy S I9000 Android Development] umohost:
To developers:

just wanted to thank you for such a great tool. I'm running Linux and it's working fine. And it's open source. You guys definitely rock ;)
[Galaxy S I9000 Android Development] cygnae:
Hi, I was trying to Flash darky's resurrection ROM so I can get Gingerbread, but now I'm stuck only in Download mode, and Heimdall will do this:

Uploading primary bootloader

0%File Part #0... Response: 0 0 0 0 0 0 0

File Part #1... Response: 0 0 0 0 1 0 0

Primary bootloader upload successful

Uploading secondary bootloader

0%File Part #0... Response: 0 0 0 0 0 0 0

File Part #1... Response: 0 0 0 0 1 0 0

File Part #2... Response: 0 0 0 0 2 0 0

File Part #3... Response: 0 0 0 0 3 0 0

File Part #4... Response: 0 0 0 0 4 0 0

File Part #5... Response: 0 0 0 0 5 0 0

File Part #6... Response: 0 0 0 0 6 0 0

File Part #7... Response: 0 0 0 0 7 0 0

File Part #8... Response: 0 0 0 0 8 0 0

File Part #9... Response: 0 0 0 0 9 0 0

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet. Retrying

Error -7 whilst receiving packet.

Failed to confirm end of file transfer sequence

Secondary bootloader upload failed!

am I doing something wrong?
[Galaxy S I9000 Android Development] gehzumteufel:
Just out of curiosity, why are you flashing PBL and SBL? This is EXTREMELY dangerous. If the PBL ever borks, you are done. There is no recovering.
[Galaxy S I9000 Android Development] cygnae:
Following instructions to be able to flash Gingerbread, or anything at this point. Download mode is the only thing working right now.

Followed Darky's Resurrection Edition tutorial (can't post links it seems)
[Galaxy S I9000 Android Development] gehzumteufel:
Now you can. You have 5 posts. Can you link to this?
[Galaxy S I9000 Android Development] cygnae:
Let's see...

http://goo.gl/gTBB7

EDIT: It seems no matter what are the options I choose for flashing, the LAST ONE always fails with Error -7.

This time I tried without primary and secondary boot, and it's giving me Error -7 on MODEM.

Any clues?
[Galaxy S I9000 Android Development] gehzumteufel:
What OS are you using?
[Galaxy S I9000 Android Development] cygnae:
Windows 7 x64.

It seems that without flashing boot/sbl/modem I got it to work. Funny thing now, I have a working I9000T with 2.2.1, speedmod and JVK baseband.
[Galaxy S I9000 Android Development] gehzumteufel:
You can flash modems via CWM anyway. So that's not a big deal. This also goes to show that Heimdall, when it comes to bootloaders, that it is really finnicky.
[Galaxy S I9000 Android Development] cygnae:
Well since you guys told me flashing boot.bin and Sbl.bin was dangerous, and my Sbl.bin ALWAYS fails, I tried flashing several different Sbl.bin and nothing, they will all give Error -7 whilst receiving packet. Good thing is I'm at JVB and I can upgrade to JVK without problems. The only thing is that I will be missing Recovery (CWM)

Any toughts? :)
[Galaxy S I9000 Android Development] gehzumteufel:
For the most part, the new 3e recovery (that breaks the ability to use CWM) is remedied by rooting and then pushing the fixed 3e recovery.
[Galaxy S I9000 Android Development] Kyonz:
Not sure if someone can help but I'm having issues getting heimdall to detect my device - odin works correctly, have replaced drivers using zadig and tried both libusb and WinUSB.

Trying to flash galaxy tab.

USB\Vid_04e8&Pid_6877&MI_02

(6601 in download mode)

have been trying for what must be hours now to get this going but no luck - anyone able to prod me in the right direction?
[Galaxy S I9000 Android Development] Dr Hotdog:
Heimdall will not build from source on either Fedora 14 x86_64 or Fedora 13 i686, the 'make install' fails to complete on both systems. It's bit where the script tries to restart udev that fails.

Fedora 14 x86_64 gives:

sudo service udev reload
Redirecting to /bin/systemctl reload udev.service
Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/sytemd1/private: Connection refused

Fedora 13 i686 gives:

sudo service udev reload
udev: unrecognized service

Anyone got a work around to get the make install script to work? Or better yet, a Fedora compatible rpm? I be really grateful for any help as I have a semi-bricked Galaxy Tab (CWM recovery and download mode OK, but won't boot) that I need to sort out, but until I can get Heimdall running there's nothing I can do.

Edit: I figured out a workaround that enabled me to get it installed and running on Fedora. I'm sure there are much better ways of doing it, but it worked and enabled me to fix my dead phone :-) The problem lies with the 'sudo service udev reload' commands, which after running configure appear in the Makefile, Makefile.am, Makefile.in, postinstall-pak and postremove-pak. What I did was simply replace each instance of 'sudo service udev reload' with a Fedora friendly equivalent, 'sudo udevadm control --reload-rules', after which 'make install' worked fine.
[Galaxy S I9000 Android Development] Benjamin Dobell:
What error do you receive?
[Galaxy S I9000 Android Development] Dani897:
im kinda a newb with linux. i downloaded the debian packages and installed them in the package manager. is there anything else i need and what comand do i type to start it?
[Galaxy S I9000 Android Development] Kyonz:
Sorry thought I put that in, I get the error that says it can't find a known device.

Have done what I'd consider the obvious things (restarts after installing device drivers, run above UAC etc).

Platform is Win7 ent x64.
[Galaxy S I9000 Android Development] Benjamin Dobell:
If you install both .deb packages then you should be good to go. The GUI can be run by typing the following in a terminal:

You'll want to use the WinUSB drivers and if you see the device in Device Manager (with product ID 6601) then it should work fine. However if it's not working it might be worth trying a different USB port or different cable.
[Galaxy S I9000 Android Development] smokestack76:
With natty the deb packages still work? Havent really had time to mess with it much. But need my heimdall fix lol. Had it going on 10.10 before. But have not tried it again yet :(

Edit: Guess not. Said i am missing heimdall and its installed command line already.... Hmmm

Double edit: Had to reboot. All working again now :rolleyes:
[Galaxy S I9000 Android Development] TheSneakerWhore:
Just throwing this out there:

Heimdall 1.1.1 on Mac OS X 10.6.xx does not recognize any compatible devices...no matter the situation (t959).
[Galaxy S I9000 Android Development] domin0311:
hi.

I cant install heimdall in ubuntu natty...its says Dependency is not satisfiable: heimdall

edit: never mind i got it
[Galaxy S I9000 Android Development] gehzumteufel:
Which bootloader do you have?
[Galaxy S I9000 Android Development] Benjamin Dobell:
10.6.x does detect devices assuming the correct bootloader is available.
[Galaxy S I9000 Android Development] pixbuf:
Flashing back to stock with heimdall

I love this program. I've used it on Gentoo Linux (1.1.1 built from source) to flash kernels several times, and it works great. Much faster and easier than Odin (and I don't have to reboot into Windows).

I did use Odin in Windows to flash back to stock to install Continuum v.5, but next time I'd like to use Heimdall. Is this possible? To do this in Odin you flash JF6_secure.zip in pda. JF6_secure.zip contains these files:

-rwxrwxrwx Cezar/None 251490304 2010-12-22 08:46 factoryfs.rfs
-rwxrwxrwx Cezar/None 1429504 2010-06-19 09:04 cache.rfs
-rwxrwxrwx Cezar/None 1376256 2010-06-19 09:04 dbdata.rfs
-rwxrwxrwx Cezar/None 6226652 2010-06-19 09:04 zImage
-rwxrwxrwx Cezar/None 12582912 2010-06-18 18:17 modem.bin

Can I just do

heimdall --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --kernel zImage --modem modem.bin

The second task is to flash the primary and secondary bootloaders. I guess I do

heimdall --primary-boot boot.bin --secondary-boot sbl.bin

In principle, I guess this would work, but I definitely don't want to brick my phone. Has anyone done this? Does it work? Is it safe?
[Galaxy S I9000 Android Development] marjoejoejoe:
im gonna try this with the xxjpu firmware from samfirmware...

is there anyway on OSX to see if heimdall recognizes the device? like a prompt or in ODIN's case the Com box highlights to yellow..
[Galaxy S I9000 Android Development] zurchpet:
HardwareGrowler an App you get with the Growl install .dmg shows you every detected device while running. The SGS shows up as Gadget Serial when connected while in Download Mode and Hardware Growler running.

Also open the Console.app and look at the All Messages view. If the bootloaders are defective you see an error message related to an USB specification there.

Hope that helps :)
[Galaxy S I9000 Android Development] marjoejoejoe:
thanks, growler works...console displays error

5/12/11 3:09:49 PM	kernel	0 1 AppleUSBCDCACMData: start - Find CDC driver for data interface failed

meaning bootloaders defective?

how to resolve?

thanks
[Galaxy S I9000 Android Development] zurchpet:
flash a ROM from Windows with Odin/heimdall or Linux with heimdall from this list: http://xdaforums.com/showthread.php?t=891518
[Galaxy S I9000 Android Development] marjoejoejoe:
i hope i get this correctly

meaning if i flash those roms i will have correct bootloaders from then..

so if i flash other rom's such as CM7 or other customized rom , i will lose the bootloaders?

earlier in the thread i read thet xxjpu had the correct bootloaders...i used the jpu rom to flash back to stock froyo, i'm assuming it wont retain the bootloaders because i am now in GB, on CM7..and console gives that error..

for your clarification please..

i once soft bricked my phone with heimdall...so i always end up loggin to windows for odin...

i leaning to just using odin instead of having to go windows...or i got go parallels and just ubuntu,,
[Galaxy S I9000 Android Development] zurchpet:
Yes, if the ROM contains in the PDA parts tar a boot.bin and/or Sbl.bin the bootloders are overwritten... but AFAIK all bootloaders in the wild are good... meaning they FIX the OS X issue rather than bringing it back.

Some stock bootloader from factory seem to be buggered...

I also use heimdall for Windows on Parallels Desktop on my Mac... had issues with heimdall, and never cared to look why it fails... :)
[Galaxy S I9000 Android Development] marjoejoejoe:
thanks, will try this out
[Galaxy S I9000 Android Development] Benjamin Dobell:
That should work fine, lots of people have flashed this way. However keep in mind if you were previously using a kernel that converted your partitions to something other than RFS, and you intend to flash the stock kernel, then you will need to repartition (and therefore provide a PIT file). In order to repartition you will need to flash all the files in one go (including the primary and secondary bootloader).
[Galaxy S I9000 Android Development] pixbuf:
I see. Thanks for the info. So to avoid this (I must, since there is no PIT file included) I have to convert back to rfs before flashing using the ext4 app.
[Galaxy S I9000 Android Development] TheSneakerWhore:
KB1

I have:

FactoryFS filled

zImage filled

Cache filled

Modem filled

Secondary Bootloader filled (KB1)

Will not recognize my device.
[Galaxy S I9000 Android Development] bilboa1:
any plan to bring I9100 compat?
[Galaxy S I9000 Android Development] hlaube:
You can download the pit-files from samfirmware.com. To each firmware there is an information which is the correct pit-file.

I just rembered, in the package of Odin, I downloaded, there have been pit-files as well.
[Galaxy S I9000 Android Development] hlaube:
SBL.bin

Hi,

I flashed this versions from samfirmware.com succesfull a couple of times, had no problem on my OS X laptop (10.5.8, Intel Core Duo)

I9000_XWJS7_XXJPY_XEEJS1

I9000_XWJVB_XXJVK_NEEJV3_Sbl
[Galaxy S I9000 Android Development] moonzbabysh:
for the life of me i cant get this to work on my mac. how do i put in the script that would allow for it to open? im new to mac so i need things in laments terms please.
[Galaxy S I9000 Android Development] jackiechan8:
+1

Has anybody tried Heimdall with the SGSII yet (maybe it works)?
[Galaxy S I9000 Android Development] peadarog:
I just tried using it with the SGS2. Nothing radical, since I have zero experience with heimdall and Galaxy phones.

1) I put the phone into download mode, following instructions I got here.

2) I connected the phone to my fedora 11 install (yes, I'm way behind the times!)

3) I ran lsusb and got:

Bus 001 Device 002: ID 04e8:685d Samsung Electronics Co., Ltd

It doesn't mention the words "mobile phone" as I think it does for the S1, but I may be wrong about that.

4) I ran:

heimdall close-pc-screen --verbose

according to instructions earlier in this thread (page 26).

5) I got:

Failed to detect compatible device

Any ideas would be welcome :)
[Galaxy S I9000 Android Development] AmbientNoise:
trying to get this to work on my mac osx 10.6.7. I got heimdall to launch using a terminal workaround, because it wouldn't even open before that. I am in download mode on my epic 4g and the phone is connected to the computer, but nothing I have ever done, be it in terminal or heimdall frontend has resulted in the computer recognizing that my phone is connected. All my files to reflash froyo eb13 are in place in heimdall ready to click start and hopefully restore my bricked phone, but it says "Failed to detect compatible device". it also says that in terminal when i type in

heimdall close-pc-screen

How the heck can I make my mac recognize my phone, since osx doesnt need any drivers??? Please help!
[Galaxy S I9000 Android Development] hlaube:
Do you have installed libusb-1.0 on your Mac?
[Galaxy S I9000 Android Development] AmbientNoise:
I didn't before..I just installed it, but heimdall still wont recognize my phone..

Also, I find it really weird that my phone doesnt pick up in download mode because it picked it up everytime when i enabled usb storage and debugging in the phone. the only problem is i cant get the phone to boot into the system
[Galaxy S I9000 Android Development] nzroman:
Looking to flash JVH (stock) and have couple of questions for those who have done it with Heimdall.

I have used this software to flash bootloaders in the past, as my Galaxy S didn't have recovery or download mode enabled. But I never flashed any firmware, because all the flashing was done through CWM. I'm currently running a 2.2.1 custom JP5 Rom.

There are a lot of stock JVH roms around on xda. I obviously want a rooted one, if possible. So I reckon stock JVH in Ramad's thread should do me nicely. It comes as a one 168mb file. The instructions given in the Ramad's thread for Odin packages however.

My question is, what should be the steps if I wanted to flash JVH over existing JP5 using Heimdall? I will obviously disable lagfix on my current kernel (hardcore's). Do I flash that 168mb file as a PDA? And do I need to choose bootloaders? Or what to do about repartition?

Thanks in advance. :>
[Galaxy S I9000 Android Development] hlaube:
And with libusb in terminal

heimdall close-pc-screen

did not work?

Oh, and have you tested to put a sudo in front of the command? I have on my mac the issue, that my daily user is not priviliged, so I use heimdall with a user, that can use sudo.
[Galaxy S I9000 Android Development] gehzumteufel:
libusb isn't needed at all btw. Nor is sudo.
[Galaxy S I9000 Android Development] katsuru:
Just installed Heimdall under ubuntu, how do i run the GUI now? My ubuntu does not seem to show me any trace of Heimdall on my machine.. :confused:

Ok got it, no GUI for Ubuntu, i can live with that xD