yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] sunseaker:
OK, I discovered that if I run Heimdall as root I don't get the libusb error. Seems like there is a permission issue somewhere which I'll look into later. Anyway it lead me to discover another issue which I'm not sure if it's a Heimdall or Rom issue.

I tried to flash the CPW version of the KI4 rom from Intratech (with the old bootloader added to allow the jig to work) (GT-I9100_CPW_I9100XWKI4_I9100CPWKH1_I9100XXKI1). It appeared to flash fine but afterwards I was stuck in a boot loop. I deleted the user data as described in the boot loop thread following all the instructions to the letter but every time I flashed the KI4 rom it resulted in a boot loop. Flashing back to my previous KE7 rom each time worked fine.

I was using the PIT file I got from my KE7 rom when flashing the KI4 rom. Is that the right thing to do or should I find a PIT for the KI4 rom?

In the end I resorted to flashing the KI4 rom using Odin on a friend's PC which worked flawlessly. So the rom from Intratech appears to be fine.

So what may be causing Heimdall to not perform the flash properly with the KI4 rom?
[Galaxy S II Original Android Development] cad_2011:
downloaded 1.3.0, installed on OSX Lion

put my SGS2 into download mode

start console and run "heimdall detect"

and have this error:

"Failed to detect compatible download-mode device"

any ideas?
[Galaxy S II Original Android Development] almorsol:
I am trying to flash an update using Heimdall.

Let me ask you one problem I have with it.

It is not recognizing the phone when I click on start. To start the flash.

It says: Unable to find compatible device.

I try Lusbs and it finds the android device.

I use Ubuntu. So cannot go Odin.

I know that with Odin, when you are going to flash, you set the phone in download mode, then plug it, and wait for the Odin to recognize it.

What about heimdall? I see nothing that tells me that it has been recognized by heimdall.

Any idea is well appreciated.
[Galaxy S II Original Android Development] sunseaker:
OK a few questions. Are you using the frontend to flash? If so, after you've put your phone into download mode and connected the usb cable have you clicked on the utilities tab and detect device? Did it find the device? If yes then try print the pit file. What is the error message if it fails?

Have you tried running heimdall-frontend as root? You may have a permission problem like I did. Did you compile heimdall yourself or install from the package?

Make sure that your device is infact listed in the rules file (mine is 60-heimdall-galaxy-s.rules located in /lib/udev/rules.d/ (I use openSUSE so your path may be different). My rules file didn't have my device listed which gave me the permissions problem. You can find out what your phone's usb device id is by running lsusb from the console with your phone plugged in.
[Galaxy S II Original Android Development] almorsol:
Thank you man!

I didn't know I had to do that. I will try it tonight.

I am using Front end. But didn't go to utilities and detect device.

I will try it and let you know.

Thank you!
[Galaxy S II Original Android Development] almorsol:
Hi again, I was able to flash KI8 on the phone now.

But how can I root it?

I flashed only the insecured kernel using heimdall, and now I have the yellow triangle at start. But no root. What to do?

Also, it didn't installed Superuser or CWM.

Any ideas?

Thank you!
[Galaxy S II Original Android Development] sunseaker:
OK, first.

How exactly did you flash KI8?

Did you use the rom from Intratech's ROM thread and was it one with the old bootloaders?

Did you extract the rom file and flash all the files contained inside? There are normally around eight files inside.

You should have no yellow triangle at this stage.

Second

How did you root?

Did you flash the zImage file from the insecure KI8 Kernel found here.

That should have installed CWM and Superuser. If not then I'm not sure what went wrong.

With regards to the yellow triangle, you need a usb jig to remove that (cheaply available on ebay) but this will only work if you flashed the old bootloader with KI8 (which it should have if you got the rom from Intratech). I'm not sure if there is another way to remove the triangle without a jig as I have always used a jig.
[Galaxy S II Original Android Development] almorsol:
Hi, and thank you for your reply.

I did flash the KI8 firmware from Intratech's ROM thread. Not the Frankestain. The stock one.

I then flashed an insecured kernell, but not from the thread you just mentioned.

I got it somewhere else. So the yellow triangle was there. But not the root, so what I did was to replace it with the stock kernel to make the triangle dissapear.

Tonight I will try the root kernel from the site you mentioned.

Thank you again.

PD: Heimdall is not that hard to use once you get the hang of it! :D
[Galaxy S II Original Android Development] sunseaker:
Good. See how it goes with the kernel from the link I sent. It should work - well those kernels from that site always worked for me.

And yes, Heimdall is pretty easy to use once you get the hang of it.
[Galaxy S II Original Android Development] almorsol:
It worked. I am rooted now.

However, the yellow triangle will not disappear. It is not something that bothers me a lot.

But out of curiosity, why is that? I flashed the KI8 that was on the thread above.

Thank you
[Galaxy S II Original Android Development] sunseaker:
Yes of course the triangle is being displayed. You flashed a non stock kernel. There are two ways to get rid of it.

1) Buy or make a reset jig. This will remove the triangle and reset the flash counter.

2) Use the method described here. This will remove the triangle but will not reset the flash counter.

EDIT: Just to be clear, the rest jig only works if you use roms from Intratech with the old bootloader added. I don't know how to remove the triangle or even if it's possible for the new bootloaders as I haven't studied that yet.
[Galaxy S II Original Android Development] almorsol:
Thanks again man!

I will try that later on. It is not an urgency to me. But it is good to know it can still be removed when this triangle starts anoying me.

Regards and thanks again!
[Galaxy S II Original Android Development] wgery:
Hello!

I want to flash a stock rom for my GSII on linux.I've insalled heimdall 1.3.1 and the frontend version of HEIMDALL.

My problem is that if I browse the xxxx.tar file (the rom file contains everything) it starts to extract and decompress it and then...

It says it doesn't finds the frimware.xml

My question is how to get a correct firmware.xml or how to make easily a firmware.xml and where to put in the .tar file?

---------- Post added at 04:49 PM ---------- Previous post was at 03:57 PM ----------

...fixed it...:)

Now my problem is that is dropping libusb error: 4 (cannot acces devie) any ideas?
[Galaxy S II Original Android Development] Benjamin Dobell:
If you've had trouble flashing certain partitions on your SGS2 in the past then that should no longer be the case! Have fun.
[Galaxy S II Original Android Development] intronauta:
Hi benjamin!

Thanks for the update, works flawlessly!
[Galaxy S II Original Android Development] lownoise:
Benjamin,

Thanks for the upgrade from your great tool!

However it looks like there is a little bug in the newest version

If you do heimdall print-pit on linux 32bit you end with a segmentation fault, after restarting your phone you get the computer phone screen. With the heimdall close-pc-screen your phone will boot normaly.

Tested on a sgs-i9000

I'll paste here the log files from version v1.3.1 and v1.3.2

Version v1.3.1 http://pastebin.com/tSZGA3KZ

Version v1.3.2 http://pastebin.com/MQs798i8
[Galaxy S II Original Android Development] Benjamin Dobell:
Hmm, I'll definitely take a look. However, I do all my testing on GT-I9000 and GT-I9100 (because they're the only devices I own) and I didn't encounter this.

Has anyone else encountered this?
[Galaxy S II Original Android Development] intronauta:
Without problems with Ubuntu 11.10 64bits, heimdall 1.3.2 and my i9100.

PIT is printed fine and without segment fault error->pc-screen.
[Galaxy S II Original Android Development] mai77:
error: -12

same here. In my case it is because I plugged in a Sam Galaxy Y, which is not supported.

I then switched back to the old driver instead of libUSB, and ODIN recognized the phone again. :)

To flash new kernels (boot.img), we usually just dd them to /dev/bml7 after bmlunlock, which can be done while mobile.

it would be very interesting to see a valid PIT file printout. can s.o.please post one ?
[Galaxy S II Original Android Development] Bayint Naung:
samsung GT-I9100 device,

Version 1.3.2 on fedora, I compiled from the source. libpit & heimdall

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

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

Uploading KERNEL
100%
KERNEL upload successful
Uploading FACTORYFS
42%
ERROR: Failed to confirm end of file transfer sequence!
FACTORYFS upload failed!
Ending session...
Rebooting device...
Re-attaching kernel driver...

It always stuck at 42%! :confused: 1.3.0 has no problem.

I'm encountering boot loop for certain official ROMs. not sure it's because of heimdall or ...
[Galaxy S II Original Android Development] intronauta:
I've problems with Heimdall in Ubuntu Precise 12.04 64bits.

Compiled without problems -libpit and heimdall/frontend binaries-, device is "detected" with heimdall detect, but always get the same error:

Heimdall v1.3.2, Copyright (c) 2010-2012, 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/

Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: 0

Any ideas?

** I've the ICS bootloader suggested and provided by teamhacksung for cyanogenmod roms in this thread:

http://xdaforums.com/showthread.php?t=1419102
[Galaxy S II Original Android Development] compuguy1088:
Not sure....if you packaged them by chance could you post the debs up?
[Galaxy S II Original Android Development] intronauta:
here you are, recompiled and packaged right now.

edit: wrong heimdall-frontend .deb, sorry. Reuploaded!
[Galaxy S II Original Android Development] milomak:
where would ubuntu typically look to find the libs for 64-bit packages?

i have installed these on a debian system

on it i get the below when i run heimdall

heimdall: error while loading shared libraries: libusb-1.0.so.0: wrong ELF class: ELFCLASS64

so i have libusb-1.0-0 installed. i do a locate for the so file

# locate libusb-1.0.so.0
/data/ext/live-helper/chroot/lib/x86_64-linux-gnu/libusb-1.0.so.0
/data/ext/live-helper/chroot/lib/x86_64-linux-gnu/libusb-1.0.so.0.0.0
/data/ext/live-helper/chroot/usr/lib/x86_64-linux-gnu/libusb-1.0.so.0
/lib/x86_64-linux-gnu/libusb-1.0.so.0
/lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0

in /usr/lib/ i then did a symlink

ln -s /lib/x86_64-linux-gnu/libusb-1.0.so.0 libusb-1.0.so.0
[Galaxy S II Original Android Development] Mevordel:
It is looking for the 32-bit library, but finding the 64-bit one. You would need to install the 'lib32usb' package, but because Debian does not have one, you will have to compile from source.
[Galaxy S II Original Android Development] drraptor:
How can I run the front end in Linxmint 10. Both frondnd and command line have been installed.
[Galaxy S II Original Android Development] whoosename:
There is no starter

Open a terminal and type: heimdall-frontend then hit enter.

here is the linux readme: https://github.com/Benjamin-Dobell/Heimdall
[Galaxy S II Original Android Development] notmyepic:
I am having trouble using heimdall on my Mac running Lion 10.7.4 trying to root Sprint Samsung Galaxy S3 (I also got the same error on my Epic also).

The error I get is FRONTEND ERROR: Heimdall crashed!

This has happened with both 1.3.1 and 1.3.2, I have run the kext removal commands (not there anyways). I have also tried multiple cables and USB ports on my Mac

Anyone have any suggestions?
[Galaxy S II Original Android Development] ChavitoArg:
I readed from page 9 - to 17 so no problem i guess, just one question. Why is the projects page DOWN? this is really usefull
[Galaxy S II Original Android Development] appagom:
I am getting large amounts of data corruption, some bits in nearly every file, using heimdall in linux to flash factoryfs.img to SGSII (SHW-M250K).. probably this bug:

https://github.com/Benjamin-Dobell/Heimdall/issues/37

and I did then pull the latest version from git (which does claim to be 1.4RC1 when executed) and I still get corruption.

This is bad. Most people don't diff the binaries on their phone against the ROM when things are acting weird (since most don't even know how to access the files on their ROM from a PC). Bad flashing wasn't my first guess either so it took me quite awhile to track this down. I hope nobody else needs to. The worst part is the ROMS usually boot, just very buggy. If it was bad enough to completely fail, most people would assume a bad flash I think, but it's not.

Of course I did then test with Odin. It was a linux machine so to test identical hardware I actually installed odin in a windows vm, maybe a little bold, but it actually worked with no corruption for the same ROM.

I've used heimdall to flash many kernels, but it (or my build of it running on my system at least) is certainly not suitable for flashing full ROMS on this phone. This needs to be a big red warning
[Galaxy S II Original Android Development] supertomi:
Don't use the frontend. You won't find a package. Use the CLI command. Start it with heimdall -- help. Then extract the firmware. It's self explaining.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] pinsb:
Could someone please point me at just 1 heimdall package for the i9100 that includes a working pit file that I can download.

No I can't use Odin as I only have access to 'nix where I am, and I'm trying to take a i9100 back from the stock JB leak to an earlier build so want to clean the modem, csc, bootloader etc......therefore I just want 1 working heimdall package for the i9100 .

Thanks in advance.
[Galaxy S II Original Android Development] swapnilraj:
Follow this link, scroll down to old releases and download the right version ie. either 32bit or 64bit depending on your computer, there are 2 downloads one is the Command Line Binary and the other is a GUI frontend, for it.

So if you want to use it with a GUI, you'll need to download both.
[Galaxy S II Original Android Development] pinsb:
I don't need the app thanks, I need a heimdall packaged firmware for an i9100. That's why I said it needed a pit file and the modem etc....thanks for your thoughts though.

Sent from GT
[Galaxy S II Original Android Development] AdamOutler:
Has anyone been able to compile 1.4 RC1 from source? I can't seem to get it working. Anyone have a binary?
[Galaxy S II Original Android Development] intronauta:
This one was compiled a few minutes ago over ubuntu 12.10 64bits, but when I try to flash anything, I always get "ERROR: Failed to access device. libusb error: -3"
[Fascinate General] mkarps:
Reserved. Lol. Always wanted to do that.....
[Fascinate General] dnoyeb:
:)

I have high hopes for it and am looking forward to it. the last alpha builds were great, but this whole new tree is going to be a major step forward in functionality when it hits.
[Fascinate General] AlexDeGruven:
I'd also suggest that JT post a new thread when the beta drops, keeping that one cleaner than the alpha thread that's gone haywire.
[Fascinate General] kidserious:
I'm thinking that if BT in call, camera, camcorder and hw/sw codecs all work then mms will as well. In the alpha builds the bugs were not specific to any one area (i.e. ril or just the camera area) Can't wait for the radio to reveal the moment of truth. I still can't figure how they have determined that sms/mms works without the radio. Thoughts?
[Fascinate General] landshark68:
I should have written that down when I saw it. Times_infinity said in irc how they were able to test those, but I can't remember. Sorry.

I did flash the new build on my second Fassy trying to help nemesis with something. Unfortunately I couldn't find any drivers that allowed my phone to be recognized by adb and I wasn't able to help. But the ROM itself is pretty sweet. No clutter, just bare bones Android goodness. Can't wait for this to drop so we can play with it.
[Fascinate General] landshark68:
Banned. LOL :p
[Fascinate General] dnoyeb:
the true beauty of CM when fully merged as JTs trying to do.. are the nightlies.

I would literally install a new rom every day when I was on my droid incredible... after I figured out what was causing the random reboots and fixed it on the AOSP roms like CM for the incredible, that thing became unreal.

I cannot wait to get back to nightly builds and all the awesome features that come with them.
[Fascinate General] landshark68:
So then would all the nightlies be available in a database so you could flash an older one you liked better? Or once you flashed a new nightly was the previous one gone for good?
[Fascinate General] Terror_1:
I personally just want the camera to work.... don't care about the radio's... LOL... just the camera.
[Fascinate General] kidserious:
Yea, I was in irc when you and Bryan were testing that. So it has been confirmed that mms works?
[Fascinate General] cpark_12:
As for the nightlies, are the phone specific? Or when everything gets merged for the fassy, cm7 is cm7 regardless of the phone?

Swyped via Tapatalk
[Fascinate General] landshark68:
I'm pretty sure I remember seeing that mentioned in irc, but with trying to retain info from work, personal life, AC, XDA, and irc I may be at full capacity and starting to not retain stuff :p

Basically I'm pretty sure I saw mms was working, just not 100% positive.
[Fascinate General] kidserious:
Ok thanks man.
[Fascinate General] Headcase8911:
Hey shark, thanks for putting this together. I think it's a great idea and should be fun!
[Fascinate General] landshark68:
Welcome. It will be great once CM7 gets finished. I can wait as I'm doing just fine on KangBang, so jt and crew can take their time and make it awesome. And anytime they get it finished will be a hell of a lot sooner than when we will even get a whiff of GB from verizon.
[Fascinate General] kidserious:
And this is going to GB the way it's supposed to be with the. 35 kernel. I'm running cm7 and loving it but I do miss the mms, camera and camcorder and you tube.
[Fascinate General] Terror_1:
+1 to that, I wonder how many people got their Fascinates within the last few months and what there feeling is though. I got mine on 9/13 and was initially pretty impressed, as time move on though the software side started to make the phone feel like it had been outgrown.
[Fascinate General] Squeaky192:
I just picked up a DINC, what waiting? :D

Definitely holding onto my Fascinate though. Although Sense 3.0 might have me hooked on HTC once it's stable.
[Fascinate General] adambobbyburgers:
Wait, so sms and mms are working? I thought a working RIL was needed for sms/mms to function.

Edit: so I read that wiki, and I'm assuming ril affects phone calls only?
[Fascinate General] eibbed0001:
OMG!! The Fascinate makes phone calls, too????
[Fascinate General] sageDieu:
Is this thread going to give everybody crabs? That sounds painful... probably worth it for cm7 though. Definitely not using Bluetooth though, I don't want none 'a that aids cancer.

Sent from my CM7 SCH-i500
[Fascinate General] vai1018:
It's not that bad. Outside of a little burning while you urinate, the aids and the cancer cancel each other out eventually. CM7 is totally worth THAT.
[Fascinate General] jt1134:
http://xdaforums.com/showthread.php?t=1116424
[Fascinate General] landshark68:
^^^ New test build released @ XDA by jt1134. Get it while it's hot.
[Fascinate General] beenz:
I just got an OG Droid for my mom and flashed CM7 on that to get a taste. Now I feel like a crack addict and need my fix on the Fascinate!
[Fascinate General] xain713:
Omfg this test build is awesome!!!!!!
[Fascinate General] chefthomas99:
Confirmed : Netflix works!
[Fascinate General] jpricesd:
Nice! Just a little more functionality and I will flash this for my every day ROM.
[Fascinate General] 1993cb7:
Ok so im downloading that test build right now and im going to flash it to play around!

Im interested in swype....i mentioned it in the other thread and someone said that i would just need to find the swype.apk to have it working in cm7?

Is that true?

I loved all the versions of cm7 thus far, but i need swype since i dont have a hard keyboard.
[Fascinate General] kallell:
Don't use swype. Try Swiftkey x beta (free) in the marketplace. It's hands down THE best keyboard i have used on android. Swype is/was ok, but what i made up in speed, i lost in having to correct the words i "spelled" by swypeing. The word prediction on swiftkey x beta after a few days is just INSANE. I type super fast when i text, so inevitably i miss alot. With accuracy in the 25-30%(they have stats on the app), it still correctly predicts 95% of my words or so.

Also, any other improvements besides volume up yesterday?
[Fascinate General] jptech7:
Some sensors have been fixed.
[Fascinate General] xsc0rchx:
Check out this post http://xdaforums.com/showthread.php?t=959222. I have used this process in ComRom and it works if I uninstall the existing Swype through TB and then install the apk package. I would be interested to know if it would work in CM7.
[Fascinate General] woodsjs:
If in-call bluetooth works on this, I will be a happy boy.
[Fascinate General] Terror_1:
Anyone having trouble with the cell radio not working?

EDIT: DURRRRR nevermind.... reboot required.

AWESOME WORK!!!!
[Fascinate General] Headcase8911:
Where did you find this info?
[Fascinate General] kidserious:
Uhh.....the op states it clearly. But, I can confirm it. I was in irc when Jt fixed the accelerometer and compass. Only the light sensor is still broken. So make sure auto-brightness and GPS are turned off. If not, your battery will last all of a couple of hours.
[Fascinate General] tmlhodge:
Slide it keyboard is just like swype
[Fascinate General] Bubbadogg14:
I got flex t9 wen it was free for cm7 cuz I could not get swype 2 wrk for me on jts alpha 3 at all.... At one point the closest I got was I could get the keyboard up n working except I could not swype w it do it was like a normal keyboard
[Fascinate General] gdnl:
I had swype stop working on cm7 and wiping dalvik cache fixed it for me. Seems like cache needs purging every 3 weeks or so.
[Fascinate General] cpark_12:
looks like jt fixed in-call audio!
[Fascinate General] CHANGiism:
jt just twitted he fixed the in-call audio. **** YEAHHHHHHHHH?
[Fascinate General] landshark68:
He sure did
[Fascinate General] Ianxcom:
I was just about to post that.so stoked!
[Fascinate General] cpark_12:
apparently bt audio works too
[Fascinate General] jkat797:
YES! I need mms tho. Im sure alot of people are waiting for it and would flash it in a heartbeat if it was to work
[Fascinate General] gdnl:
I think this is the night where everyone gets their .35 kernel...
[Fascinate General] xain713:
Woooooot. Awe damn third pair of underwear in the past 2 days

Sent from my cm7 fassy :)
[Fascinate General] cpark_12:
ha! i had to wash today just to have some more clean pairs for tonight!
[Fascinate General] tripacer99:
Man, SO CLOSE TO COMPLETION. OH GOD, THE EXCITEMENT IS LITERALLY KILLING M
[Fascinate General] sfobrien:
I'm looking forward to trying this when it's done but man it is going to be tough switching from ComRom 2.0.
[Fascinate General] beenz:
*****es love in call audio