yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] kalpik:
My driver installation on Windows went well, but I'm getting "Failed to access device. Error: -12"

Any help? Also, Odin does not see my phone!
[Galaxy S II Original Android Development] Boal:
I have the same problem as urbanomad without ever having had a 2nd extension folder. So that's probably not the reason.
[Galaxy S II Original Android Development] urbanomad:
Yes, it was

/System/Library/Extensions/Content/Info.plist
[Galaxy S II Original Android Development] Boal:
That doesn't look like a second Extensions folder, more like the contents of the .kext "file" (it's actually just a folder) moved up one level.
[Galaxy S II Original Android Development] insty:
$ heimdall

dyld: Library not loaded: /usr/local/lib/libusb-1.0.0.dylib

Referenced from: /usr/bin/heimdall

Reason: Incompatible library version: heimdall requires version 2.0.0 or later, but libusb-1.0.0.dylib provides version 1.0.0

Trace/BPT trap

Any idea?
[Galaxy S II Original Android Development] Boal:
Install libusb 2.0.0 or later?

edit: Ok, maybe you can try this and post the ouput: otool -L /usr/bin/heimdall

It gives me:

$ otool -L /usr/bin/heimdall
/usr/bin/heimdall:
/usr/local/lib/libusb-1.0.0.dylib (compatibility version 2.0.0, current version 2.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 103.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
[Galaxy S II Original Android Development] TA123:
Tried to flash a custom ROM to my SGS2. It failed but also wiped out my internal SD card :( Nothing important there apart from a few photos though.
[Galaxy S II Original Android Development] urbanomad:
I had the same problem and followed the instructions here http://point-cloud-library-pcl-mailing-list.967500.n3.nabble.com/Why-does-pcd-viewer-try-to-load-libusb-2-0-0-td2959838.html
[Galaxy S II Original Android Development] AkkerDK:
Fail flashing Lite'ning v1.4

I have before flashed Lite'ning v1.3 with Heimdall without any problems, så I didn't hesitate to flash v1.4 also ... But this time it was no good, I got caught on the "Samsung Galaxy S II GTI9100" screen, tried to wipe cache and dalvik-cache in Recovery mode, but that didn't help.

I could reflash v1.3 without any problems though, but why do it fail with v1.4?

Heimdall says the flash went okay, but I get stuck anyway.

Could it be, that v1.4 has a new modem, and I off course placed modem.bin in the modem field ... No other versions of Lite'ning has had a modem with the flash, could modem.bin be the problem? And if, how to solve that?

Or could it be anything else?

UPDATE: Have noticed that the new modem was indeed flashed, so flash was successful as Heimdall stated... Just "funny" that I get stuck on reboot then?
[Galaxy S II Original Android Development] Xero Xenith:
Boot loop thread:

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

Basically, you may just need to wipe :)

I'm trying that one now - here's hoping!

EDIT: I got the exact same problem as you. Even the screen I got stuck at was exactly the same. I solved it by just flashing my old firmware :)
[Galaxy S II Original Android Development] Hooolm:
I installed Heimdall 1.2.0 on MacOS X 10.6.7

heimdall print-pit gives me

Failed to detect compatible device

Any ideas?
[Galaxy S II Original Android Development] Boal:
Have you read the thread and checked for the other reported symptoms?
[Galaxy S II Original Android Development] jzuijlek:
I to was stuck on the boot screen after flashing lr 1.4. Extracted the factoryfs, modem.bin and zImage and flashed via command line, all status messages where normal.

After that I flashed the rom via odin and it booted fine.
[Galaxy S II Original Android Development] Hooolm:
Yeah, although I didn't think I had to state that explicitly :)
[Galaxy S II Original Android Development] apacheo:
You aren't alone; Heimdall doesn't work on my Mac either. Just gives the device not found, and the Heimdall kext doesn't seem to be enabled, even though its installed. Trying to enable it by hand doesn't work either.

Such a shame that this software just doesn't work..
[Galaxy S II Original Android Development] Hooolm:
Heimdall seems to work just fine for a lot of people. It may be any weird little kink on my Mac or my SGS2 that prevents it from being detected in download mode. Having spent about as much time on the issue as I am prepared to waste, and having received nothing but one snotty reply to my polite inquiry, I've focused my efforts elsewhere.
[Galaxy S II Original Android Development] atinm:
Macs are generally quite painful - I stopped using my Mac for anything related to Android, including Heimdall. In fact, I finally went and relegated my Macbook Pro to backup computer and upgraded to a big ass Ubuntu box. Heimdall works great on Linux :-)
[Galaxy S II Original Android Development] sgstwo:
You did the right thing. ;)
[Galaxy S II Original Android Development] Boal:
Can we get back on topic? Apparently Heimdall is supposed to work on Macs but doesn't work correctly -- at least not everywhere. What can we do about that?
[Galaxy S II Original Android Development] Bond@007:
Oh it's a big problem for me because i've only a Macbook Pro and not other computer.

My Samsung Galaxy S2 and me are so sad :(
[Galaxy S II Original Android Development] Boal:
You can always use boot camp. Though it would be nice if that wasn't necessary.
[Galaxy S II Original Android Development] MicioMax:
Litening 1.5 installs well with heimdall on Ubuntu.... I guess it was some strange format in 1.4 that gave problems.

Max
[Galaxy S II Original Android Development] vorcigernix:
Can't compile this on fedora :-/
[Galaxy S II Original Android Development] sgstwo:
Since you didn't post any error messages, I have to assume you don't want any help.
[Galaxy S II Original Android Development] Bond@007:
I've a Samsung Galaxy S2 and Macbook Pro but last time i've tested this software with MacOsX, it's doesn't work ... it's ok today ?

There is a tuto for to flash SGS2 with Heimdall on Mac ?

Thanks before for your help.
[Galaxy S II Original Android Development] cputoaster:
Any news on the Mac issues? Did anybody manage?
[Galaxy S II Original Android Development] Paul2436:
Hello,

i've a realy strange problem with my GalaxyS2. [I already made a Thread about i it]

Short Version: All changes on my Phone (Configurations, App's, Files) are rejected after a reboot. E.g.:

- I delete a Picture on my internal storage, then I reboot my Phone and the Picture is back again

- I delete some System-App's, then I reboot my Phone and they are back again.

I even can't flash a new FW. Tried it many times with Odin and don't get any error...but after the Phone reboots *#1234' still shows me the old FW.

Now I tried it with Heimdall and the newest Firmware (i9100XXKG1):

C:\Users\Paul\Desktop\heimdall-1.2.0-win32>heimdall.exe flash --kernel zImage --
secondary-boot Sbl.bin --param param.lfs --modem modem.bin --hidden hidden.img -
-factoryfs factoryfs.img --cache cache.img --primary-boot boot.bin

Heimdall v1.0.2b, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au

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:
http://www.glassechidna.com.au/donate/

Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success

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

Uploading BOOT
100%
BOOT upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading PARAM
100%
PARAM upload successful
Uploading KERNEL
100%
KERNEL upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Ending session...
Rebooting device...

But *#1234# still shows me the old Firmware...

Then I tried Heimdall with Repartition, and I get always this error:

C:\Users\Paul\Desktop\heimdall-1.2.0-win32>heimdall.exe flash --repartition --pi
t u1_02_20110310_emmc_EXT4.pit --kernel zImage --secondary-boot Sbl.bin --param
param.lfs --modem modem.bin --hidden hidden.img --factoryfs factoryfs.img --cach
e cache.img --primary-boot boot.bin

Heimdall v1.0.2b, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au

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:
http://www.glassechidna.com.au/donate/

Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success

Partition corresponding to -pit argument could not be located
Uploading PARAM
100%
PARAM upload successful
Uploading KERNEL
100%
KERNEL upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading MODEM
100%
Failed to confirm end of file transfer sequence!
MODEM upload failed!
Ending session...
Rebooting device...

Two Questions:

1. What does "Partition corresponding to -pit argument could not be located" mean?

2. Any Ideas? :p
[Galaxy S II Original Android Development] AkkerDK:
The problem seems to be back with Lite'ning v2.0

At least I'm unable to make the phone boot, even though Heimdall reports a successful flash
[Galaxy S II Original Android Development] TA123:
I wonder if libusb-1.0 > 1.08 is really necessary. I've got 1.08 version on my Ubuntu system and when I tried to build a proper package of the libusb-1.0 from the Heimdall's git repository I have a conflict with my installed version from Ubuntu repos.
[Galaxy S II Original Android Development] Benjamin Dobell:
Libusb 1.0.8 is not strictly a requirement, no. Users have had success using 1.0.6 in the past. As such you'll be fine if you modify the package and/or source requirements. 1.0.8 is only specified as that's the version I use and test with, I use this version simply because it's the first version to officially support Windows.
[Galaxy S II Original Android Development] Benjamin Dobell:
Heimdall Suite 1.3 (beta 1) binaries are now available from here.

If you're a developer or in any way interested in the brand new Heimdall Firmware Package format then this thread may also be of interest. Please spread the word about the packaging format. If mass adopted I think it has the potential to save a lot of accidental bricks!

Oh, and because this is a beta release it's the perfect time for users to report issues. However if you're going to do so please provide as much information as possible and post the issues using the Github issue tracker. Unfortunately just reporting problems isn't always that useful to me. So if you're able to report particular cases in which Heimdall fails but Odin succeeds then that's particularly important. Even better are USB captures of this process taking place!
[Galaxy S II Original Android Development] TA123:
Thanks a lot, Benjamin. Just seen your post with binaries. So will keep in mind about libusb if have to build a package in future.
[Galaxy S II Original Android Development] AkkerDK:
I have an issue of kind, but don't know whether it should be in Github issue tracker or not.

It's about flashing the Lite'ning ROM, which sometimes works, sometimes don't, but no matter if it works or not, Heimdall, both 1.2 and 1.3 beta, report a successful flash.

I had no problems flashing Lite'ning ROM v1.2 and v1.3 with Heimdall, then it didn't work with v1.4 (but Heimdall states a successful flash), then it worked again with v1.5 (all of those was with Heimdall 1.2), but now again it don't work with v2.0 (tried with both Heimdall 1.2 (front-end and comman-line) and 1.3 (command-line only).

I think this is very confusing, and guess it must have someting, have no clue what, to do with Lite'ning ROM somehow, not with Heimdall ... But can I somehow find out what is happening in Heimdall flashing Lite'ning ROM v1.5 contra Lite'ning ROM v2.0 and maybe see any differences?

Another issue is, that I'm a bit confused about the new Heimdall front-end (1.3 beta).

If I understand it correctly, as a user, I am only able to use Heimdall front-end 1.3 beta to flash, if the ROM developer either has made a Heimdall firmware package or included a firmware.xml file ... and if the developer hasn't provided either, I as a user will not be able to use Heimdall front-end 1.3 beta to flash, but will have to use command-line.

Is that correct understood?

If it is, then I quite honestly don't understand why You are restricting the use of Heimdall front-end that way?

Also, as a user, I find Heimdall front-end 1.3 beta a bit confusing ... Heimdall front-end 1.1.1 was quite self-explanatory, kernel file placed here, modem file there, and so forth ... I don't think the use of heimdall front-end 1.3 beta is quite as self-explanatory from a user wievpoint.
[Galaxy S II Original Android Development] Benjamin Dobell:
I'm not really sure, you're probably better off going to Lite'ning ROM developer(s) and asking them what has changed. Perhaps you could request that they distribute Heimdall Frontend Packages in future.

You can definitely still perform a custom flash with Heimdall Frontend. The README includes detailed instructions. You just need to select a PIT file first. I'm working on some updates at the moment that should make this a bit clearer (and simpler).

I agree that the interface for Heimdall 1.3 is more complex than that of 1.1.1. This is one reason why I strongly recommend developers distribute Heimdall Firmware Packages so that inexperienced users don't run into problems.

Of course I didn't make the interface more complex simply for the sake of it. The increase in complexity was required in order to support a wider range of devices (and all the obscure partitions they might have). For instance the 1.1.1 Frontend wouldn't have allowed you to flash the SGS2's "GANG", "UMS.EN" and "HIDDEN" partitions.

Rather than trying to maintain a huge, incomplete and ever-changing list of possible selections that would clutter the interface and span multiple pages, this new user interface displays only allows you to flash partitions that are available on your particular device (based on the PIT information).

The changes will undoubtedly take some getting used to, particularly since this interface is so drastically different to Odin's. However I'm hoping that developers will release packages to largely simplify the learning curve for new users.

If you have any suggestions as to how I could make the user interface more intuitive then I'm definitely open to suggestions. It's just not that easy due to the number of devices that need to be supported.
[Galaxy S II Original Android Development] MicioMax:
Same problem here, and Litenin' works perfectly on all versions with odin.... So it should be an Heimdall problem, not Litenin' one.

I also made an heimdall package, with no changes either (which was expected, as the package is just a shortcut of manual flashing).

Max
[Galaxy S II Original Android Development] king_dani:
help is needed and appreciated

hi Ben

I have read so much about your project, and donated a very modest amount since i was superexcited that i do not need to buy a PC just to be able to use my SGSII the way i like, and i plan to compensate that modesty when i actually am able to use this program.

I have read pages upon pages of XDA and other websites with regard to how your project works. however, it seems that you have just very recently changed the way your program works in Mac OS. I have downloaded and installed Heimdall 1.3 beta2, and can see that it has a fairly user-friendly interface which i admire, but the point is, I am not able to get hold of an xml file for the latest 2.3.4 leaked ROM, KG2, so i am practically stuck. is it possible for you to give me a solution? any help is greatly appreciated, be it from Benjamin or other XDA brethren

thanks
[Galaxy S II Original Android Development] Benjamin Dobell:
Thanks for the donation, very much appreciated!

With Heimdall Frontend 1.3 you're still able flash firmware that isn't included in a Heimdall Firmware Package. This type of flash is now called a "custom flash". In order to do so you must supply a PIT file, this wasn't a requirement with Heimdall Frontend 1.1.1 but it is necessary so that the same user interface is able to support a wide variety of devices (based on info retrieved from a PIT file). Beta 1/2 doesn't include a means of downloading a device's PIT file so you have to grab the appropriate PIT file from somewhere.

However I've written code that adds the ability to download your device's PIT file. This code is available in Heimdall's Git repo but binaries have not yet been compiled. The final 1.3.0 release will be available soon and will include this functionality along with some user interface improvements and a few other minor bits of functionality.

For now you can still use a PIT file from elsewhere and follow the instructions in the README under the heading "Performing a Custom Flash with Heimdall Frontend".

Let me know if you have any difficulties.
[Galaxy S II Original Android Development] king_dani:
thanks for your reply. I did figure out that I would need pit file, but KG2 leaked release does not come with pit file, as far as I understood, pit is something that would tell Heimdall (and Odin) where to put each file inside different partitions of the device. now, do you think things have changed from KG1 leak in pit file? because I have pit file from that release. also, could you please elaborate on how to use this custom flash method? is there a guide on how to do that, i don't see the button.

sorry for being so thick
[Galaxy S II Original Android Development] TA123:
it is much easier to flash using command line and it does not require a pit file.
[Galaxy S II Original Android Development] king_dani:
is it? how do i use command line in 1.3 beta2? i mean i know before there was command line, but now i can not find it for the life of me. also, is it by using adb? could you help out a fellow SGSIIer?
[Galaxy S II Original Android Development] king_dani:
i played safe, and now i am trying to flash KG1, which has pit file as well onto the device. i open Heimdall suite, choose flash tab, browse and select the pit file, but Start button is gray. i add some files to partition section , though have no idea what is what (is there any way to decipher them? a guide perhaps?) and still the Start is gray, device is in downloading mode, nothing happens.

help is appreciated as always

EDIT:

so i have unzipped (untarred) the file that is the biggest file in update, and has CODE in its name. there are a lot of files. first, i am not confident if i have used the right unzip program, i use Keka, but could you please point me to a tested software to unzip which has zero risk of messing zipped files? i have no experience with tar files, and i am not sure if keka uses the right algorithms to retrieve files intact.

also , there are a ton of files to choose from, but i think i have read that you need to flash only a couple of files , am i correct? what about boot.bin and hidden.img? i really don't like to brick my device :D
[Galaxy S II Original Android Development] Benjamin Dobell:
The Start button remains greyed out until you've selected a PIT and added at least one partition to the flash (or if you load a Heimdall Firmware Package). Before a partition is counted as being added you must select a file to be flashed to said partition. The destination partition is set from the Partition Name drop-down and the file corresponding to that partition is set by the Browse button just below. I think you might have worked this out already judging by your edit.

As far as determining which file is for what partition. You should be able to match the name of files to certain partitions. i.e. Sbl.bin matches with SBL1 (or SBL) depending on the name of the partition in the PIT file. boot.bin is BOOT (or IBL+PBL, only one or the other will be listed), zImage is KERNEL and think the others should be reasonably straight forward.

I'm trying to avoid including the above file -> partition info in the README as it's device specific, actually it's technically PIT specific, and I want to avoid confusing people. Although it might be a good idea if I add something to the help menu that has a few examples.

The number of files that you want to flash really depends on what you want to do. If you're trying to flash a full firmware (especially if you're repartitioning) then you'll want to include every file that you have available to you, so all files included in all tar archives for the firmware you're intending to flash.

As a general rule I always recommend flashing boot.bin if you flash Sbl.bin, or vice versa. The reason for this is that it's possible to have a mismatch between these two files that results in your phone not being able to boot at all. param.lfs is also used in the boot process so is quite important as well. However whilst you obviously want to put all other files in the correct location, if you do make a mistake it won't break your device at all.

So the really important ones are:

BOOT = boot.bin

SBL1 = Sbl.bin

PARAM = param.lfs

Don't stuff these important three up. Then the others you should also be able to determine by name, i.e. HIDDEN = hidden.img. However as mentioned above if you stuff up partitions that aren't these three and your device doesn't boot you can just access download mode again (no damage will be caused).

NOTE: Don't flash EFS, err ever. It won't stop your phone booting but if you override it without an appropriate backup then the phone loses its IMEI and other important information.

As far as using an extraction program to get the files out of the TAR archive goes. I would personally use 7-zip on windows and use the terminal "tar" command on OS X or Linux. However generally speaking the TAR format is very straight forward, it's pretty hard to stuff up extracting them. So I don't think you'll have any problems using any reasonably popular tool.
[Galaxy S II Original Android Development] king_dani:
thanks for your response. however, there are just so many of these files lying in one update, and as you have pointed, some (like efs) might screw things up.

1. CODE_I9100XXKG1_CL349526_REV02_user_low_ship.tar has 8 files inside, including a cache.img

2.GT-I9100-CSC-MULTI-OXAKG1.tar gives me another cache.img, which i have no idea which one should i flash as image.

3.MODEM_I9100XXKG1_REV_02_CL1034110.tar gives me a modem.tar, which up until know, i had no idea about, i thought we already have modem from file 1, but it appears it is more difficult than it seems.

the pit file supposed to have this information available, is there anyway that you could automate this process? i know you have written a non-device specific part for Heimdall, but i think there is not even a single ROM that provides such capability, and what i'm trying is the official leaked ROM.

also, all this was about the old 2.3.4 leaked one, the KG2, does not have a pit file, but worse is all files there are tar.md5 files, which i assume is another type of zip file, but i don't have the means to unzip them. any ideas?

thanks for your continuous support, i really hate windows and i am trying my best to avoid it at all costs, but it seems like a long stretch
[Galaxy S II Original Android Development] brocabortzfield:
Can someone please do a root walkthrough for mac users?
[Galaxy S II Original Android Development] king_dani:
root shouldn't be this hard, all you have to do is to use ChainFire 4.0 rooted kernels and flash them onto your device. granted, if pit file is necessary for flashing these kernels, then it might not be that easy.

anyway, i have rooted my device on Odin using someone else's PC.

but i hate to do that everytime...
[Galaxy S II Original Android Development] Benjamin Dobell:
For rooting you only need a PIT file and the kernel. The official 1.3.0 that's going to be released soon also includes the ability to download the pit from your device so the process is much simpler.