yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] paranoid android85:
posted in the wrong thread ealier, i did everything but when i try to flash kernel i get this error:

Initialising connection...

Detecting device...

libusb couldn't open USB device /dev/bus/usb/002/015: Permission denied.

libusb requires write access to USB device nodes.

ERROR: Failed to access device. libusb error: -3

what am i doing wrong?
[Samsung Epic 4G Touch] silversx80:
Stupid question:

Is your device in download mode? Also, what's your OS and computer?

Put it in DL mode, then connect the USB cable. Type "heimdall detect" to see if your device is connected and detected. Try a different USB port as well.
[Samsung Epic 4G Touch] paranoid android85:
Yes it's in dl mode. I'm using a dell studio laptop running linux mint 11. I typed heimdall detect and it said device detected. But when I try to flash I still get that message. I'll try a different usb port when I get home
[Samsung Epic 4G Touch] Entropy512:
If you haven't set up your udev permissions to allow mortals access to that USB device, you need to run heimdall as root.

Create a file in /etc/udev/rules.d/ called android.rules and add a line like this to it:

SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="685d", MODE="0666"

To figure out the proper values for idVendor and idProduct, put the phone in download mode and then run:

lsusb

Most GSIIs are 685d though. Vendor should always be 04e8 for Samsung.
[Samsung Epic 4G Touch] paranoid android85:
Thank you, I'm going to give that a shot
[Samsung Epic 4G Touch] paranoid android85:
im still kinda new to linux, i found the file /etc/udev/rules.d/ , but it wont let me create a file called android.rules. im also not sure how to add the line

SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="685d", MODE="0666"

to the file once i make it. sorry for my n00bness
[Samsung Epic 4G Touch] zedomax:
Might want to run as root, yes, for Linux Ubuntu do:

sudo -i

in terminal to run as root.
[Samsung Epic 4G Touch] paranoid android85:
awesome! thats all i needed. im rooted now. thank you!
[Samsung Epic 4G Touch] Alex1x:
I used this root method on my iMac. Everything went okay (super user and kernel). QUESTIONS: when I reboot the phone, there is a "yellow exclamation" mark under the "Samsung Galaxy S2 I-9100". Is this normal? Any way to get rid of it?

=)
[Samsung Epic 4G Touch] EeZeEpEe:
Yeah. Install the stock kernel. You'll still keep root and superuser.
[Samsung Epic 4G Touch] zedomax:
Really? Thats awesome to hear, i learned that code two weeks ago also for ubuntu change ur root password to ur liking by typing:

passwd
[Samsung Epic 4G Touch] zedomax:
Sure nice to hear a mac user rooted their phone FINALLY.
[Samsung Epic 4G Touch] silversx80:
Hey now :(
[Samsung Epic 4G Touch] zedomax:
I swear 90% of XDA use Windows or Ubuntu, lol. What do u use?
[Samsung Epic 4G Touch] silversx80:
OSX on three computers at home, with one running Ubuntu on VM. Windows at work. Will be taking the old Macbook (1st gen) and making a dedicated Linux machine.
[Samsung Epic 4G Touch] Entropy512:
This will start a root shell.

It's somewhat safer to just run individual commands as root, using

sudo <command>

So for editing the file in rules.d it would be

sudo nano -w /etc/udev/rules.d/android.rules

To run heimdall without doing the udev tweaks I mentioned:

sudo heimdall <whatever options you want to pass to heimdall here>

But for me it's easier to fix the rules once and not have to sudo again when flashing stuff. :)
[Samsung Epic 4G Touch] g4me0v3r:
I am on a Mac running Lion and I get "ERROR: Claiming interface failed!" Forgive me for being such a uber noob, but this is my very first Android device, coming from the HTC Touch Pro 2.

:confused::confused::confused:
[Samsung Epic 4G Touch] EeZeEpEe:
What step are you on when this happens?
[Samsung Epic 4G Touch] g4me0v3r:
That error pops up when I am on the step to flash the kernel. Oh and I am also using SPH-D710_Zedomax_EpicTouchKernel-v3. Thanks for the speedy reply, I am new to the world of Android.

=/
[Samsung Epic 4G Touch] StormCell:
Sorry for the dumb question:

When I go to the Heimdall website I don't see anything for Binaries or Heimdall 1.2.0 or actually to download anything. Granted I am a little borked from my root canal but still...
[Samsung Epic 4G Touch] zedomax:
Try scrolling down.
[Samsung Epic 4G Touch] silversx80:
Install Heimdall 1.2.0 (here) for command line binary and make sure you download the one for OSX.

Install. Also, decompress the kernel by double clicking it (will automatically extract the file).

Then, put your phone into download mode. After it's in DL mode, plug it into the USB port. Don't plug it in first.

Open Terminal in Applications>Utilities and navigate to directory where the kernel is.

Type "heimdall detect" exactly like it is in the quotes and hit return. If it can read your phone, it'll tell you "device detected". Then it's OK to flash. Exactly like Zedo had posted: heimdall flash --kernel zImage. It is case sensitive, so make sure that "I" is capitalized. Several moments and it'll be flashed.
[Samsung Epic 4G Touch] g4me0v3r:
I had previously DL'd the 1.3.0 version already, is there anyway to go back a version?

Also, I tried this method just now. Still says "Claiming interface... Failed!"
[Samsung Epic 4G Touch] thedeadletters:
Installing Heimdall?

Thanks for the guide and kernel.

I'm on Mac OSX and I can't get the command line in Terminal working. When I open Terminal and type "Heimdall" I get:

dyld: unknown required load command 0x80000022

Trace/BPT trap

Computer Name:~ username$

I installed 1.3 and it didn't work. So I uninstalled (dragged and dropped into Recycle Bin/Deleted) and installed 1.2 command line. Ended up getting the same exact result. Am I supposed to go to a different directory? How can I check to see if Heimdall 1.2 Command Line is even installed?

Thanks in advance!
[Samsung Epic 4G Touch] g4me0v3r:
Spent hours upon hours trying to figure out how to flash with OSX, gave me a headache, decided to switch over to Windows and flash using Odin. Took maybe 15 mins, even with dl'ing all the proper files.
[Samsung Epic 4G Touch] zedomax:
Try 1.2 binaries, 1.3 front-end for mac has known to have problems.
[Samsung Epic 4G Touch] silversx80:
I have 1.3.0 and 1.2.0. Just install 1.2.0, no need to do anything with 1.3.0. You actually need 1.2.0 to use the command prompt, and it's different than 1.3.0. 1.3.0 is the GUI and doesn't give you access to the command line prompts.

Stupid question

When you type "heimdall detect", does it return "device detected"?

Everything is case sensitive, so heimdall should be all lowercase. If you just type hiemdall (in all lowercase), I think it tells you that you need to give it a command... or tells you something about its version. I can't remember, but I can check when I get home. Also, double check that you installed the 1.2.0 Command Line binaries for OS X (Universal). It should have mounted a .dmg and had a pkg installation on that disk image.
[Samsung Epic 4G Touch] thedeadletters:
Thanks for the replies. I mistyped "Heimdall" in the post; I used all lowercase when I was in Terminal.

In any case, I did some research on this error and it seems like the problem is that I'm using Leopard and not Snow Leopard. Thanks, though.
[Samsung Epic 4G Touch] zedomax:
Make sure you are using 1.2 binaries for Mac, I haven't heard of one person who got 1.3 Heimdall working including myself.
[Samsung Epic 4G Touch] Benjamin Dobell:
Hmm, that's not good. Theoretically Heimdall should work on any OS X version all the way back to Tiger and even run on PowerPC machines. I finally solved the OS X issues that delayed the 1.3.1 release by several weeks so I'm going to make a new release some time in the next 24 hours. If you could test the 1.3.1 release on your Leopard machine and then let me know if it works that would be fantastic.

I'm not sure why but the error you're getting suggests there was a problem finding libusb-1.0 at run time.
[Samsung Epic 4G Touch] zedomax:
I get that libusb error on Windows and Mac, is there a certain library I have to install to get the GUI working??? Thanks for the software btw, it ROCKS!
[Samsung Epic 4G Touch] adorkablejuliep:
Thanks! Rooted on my mac :)
[Samsung Epic 4G Touch] zedomax:
nice bud, congrats, it's like having a child! :)
[Samsung Epic 4G Touch] thedeadletters:
Wow! Talk about excellent customer service! I will most definitely try it once it's released and let you know how it works.

Thanks!!!

BTW - I'm using an iMac running 10.4.11 and a Macbook Pro running 10.5.8.
[Samsung Epic 4G Touch] zedomax:
Right, excellent customer service is the best thing in the world. GO HEIMDALL, I've been using heimdall over ODIN for all my development, makes my job so much easier and faster, recommended over Sammy's crappy ODIN crap.
[Samsung Epic 4G Touch] Benjamin Dobell:
I think you might have gotten the errors slightly mixed up as the following error is OS X specific:

However, if you're able to copy and paste the exact errors you're getting then I'll see if I can find out what is going on.
[Samsung Epic 4G Touch] TheDudeAbides:
SUCCESS!!!!!!

Zedo....think I got a man crush goin' on. Keep on rockin' my brotha!

On my MacBook Air.
[Samsung Epic 4G Touch] zedomax:
Man crush!
[Samsung Epic 4G Touch] wase4711:
should debug mode be on or off?

I tried to flash twice, and got the "claiming interface failed" message both times..

heimdall 1.2 installed properly, and, I have the image file in the right spot..

thanks
[Samsung Epic 4G Touch] wase4711:
Well, it was OSX lion that gave me the problem; once i flashed it on a computer running snow leopard, it worked perfectly.

one quick questing when the phone reboots, I have the yellow exclamation mark on my screen; how do I get rid of that?

thanks!
[Samsung Epic 4G Touch] skorch:
thought I'd throw my weight in here with my fellow OSXers, since I'm stuck on my work macbook. I'm able to get my device detected by heimdall, just am unable to claim the interface successfully. Maybe I'm doing something dumb, and I'm overlooking it. My device is in download mode, and I connected the usb after getting it into dl mode. I then run the commands, but no dice:

http://i.imgur.com/eEmRh.png

edit: Macbook pro 6,2 running OSX 10.6.8

edit2: I decided, after remembering that I had it, to boot into my ubuntu partition on this macbook and try it from there. It went smoothly! Big thanks to the devs!
[Samsung Epic 4G Touch] krazyflipj:
Can't get this to work. I'm getting claim interface error. I had 1.3 installed but installed 1.2 afterwards. When I type in heimdall detect, i get unknown detect. Any suggestions? FYI running snow leopard.
[Samsung Epic 4G Touch] wase4711:
that was happening to me using Lion, but it worked on SL

Did you try to uninstall both 1.3, and 1.2, then reboot your computer, then re install 1.2?

it took me a few tries, but ended up working

EDIT:

Well, got a new phone today, and, once again I am getting the claim interface error"

tried version 1.2, 1.3.1, and on lion osx and snow leopard computers...

Oh well, try again tomorrow
[Samsung Epic 4G Touch] EeZeEpEe:
Weird. I did it with my iMac running Lion and 1.3 in Terminal.
[Samsung Epic 4G Touch] wase4711:
here's what I get trying to run it on lion..tried the latest command line version, 1.3.1

"Initialising connection...

Detecting device...

Claiming interface...

ERROR: Claiming interface failed!"
[Samsung Epic 4G Touch] EeZeEpEe:
What command or step are you getting that at? This is exactly what I did to get the kernel installed:

1. Download the .tar file and double click to untar it. Keep it in your downloads folder.

2. Open Terminal and type:

cd /Users/myusername/Downloads (I think username is cap sensitive)

3. Followed by:

heimdall flash --kernel zImage
[Samsung Epic 4G Touch] wase4711:
yes, that is EXACTLY the same thing that I have been doing, but getting the error message after "heimdall flash --kernel zImage"
[Samsung Epic 4G Touch] EeZeEpEe:
Damn. Other than making your Epic 4G Touch is in download mode and plugged in, I have no clue as to what could be going wrong. It could possibly be the Mac. If anything I would try using Odin if you can use someone's Windows computer. I rooted a coworker's phone and it was even easier since you have no commands to worry about having typos.
[Samsung Epic 4G Touch] wase4711:
well, on my first e4gt it took several tried to get it to root, so I will keep trying, until another way comes out, or, I get my hands on a windows pc...

thanks
[Samsung Epic 4G Touch] urinsane:
This was the same error I was getting with Heimdall 1.3 on Snow Leopard last week. I'm waiting on a replacement phone right now (long story, charging port related.. my fault, not a phone defect) and already am back to stock, so not really wanting to try 1.31 right now, but I'll report back as to whether I get the same error on my new phone.
[Samsung Epic 4G Touch] cinematree:
I had no problems installing (OSX 10.6.8), but have been having problems with my phone since rooting it. I don't know if it's from rooting it, but I didn't have any issues in the 3 weeks I used the phone before rooting it. Sometimes texts won't send (I keep hitting resend and it keeps getting a sending error), my antenna seems to not work that solidly (I won't get reception in places i usually do or it's very inconsistent), and sometimes my phone won't hang up a phone call no matter what i do unless I turn it off. And the battery seems to die more quickly. The wifi tethering works fine. Any idea if these issues sound like they're from the root?

Model Number: SPH-D710

Android Version 2.3.4

Baseband Version: S:D710.10 S.EG30

Kernel: 2.6.35.7_ZedomaxEpicTouchKernelv3-g165267b-dirty

Build Number: Gingerbread.EG30

Hardware Version: D710.10
[Samsung Epic 4G Touch] wase4711:
you have a better chance of getting help if you post this in Q&A, instead of this thread...
[Samsung Epic 4G Touch] EeZeEpEe:
I went back to stock kernel immediately after and I've been fine.
[Samsung Epic 4G Touch] CoolWheelChair:
Initialising connection...

Detecting device...

Claiming interface...

Setting up interface...

Checking if protocol is initialised...

Protocol is not initialised.

Initialising protocol...

Handshaking with Loke...

ERROR: Failed to receive response!

why does this keep happening??:confused:
[Samsung Epic 4G Touch] Gub40897:
Ibid

This keeps happening to me too? Any way to fix this?
[Samsung Epic 4G Touch] springsyeti:
You followed all the commands to ensure you have heimdall installed and are in the correct directory for the z image. And you are in download mode on the phone and it is connected to the machine when typing heimdall.
[Samsung Epic 4G Touch] CoolWheelChair:
definitely did, like I'm not really a.noob i just haven't had a phone in 7 months lol i had a rooted g1 & g2
[Samsung Epic 4G Touch] LPChris:
I was able to root and put this kernel on however after I did my battery life went to **** (maybe 30% what it was when it was stock/unrooted) and I experienced my first LoS issue. Going back to stock fast!

---------- Post added at 12:13 AM ---------- Previous post was at 12:12 AM ----------

This is because of the root and this kernel. Go back to stock, this thread should really suggest a different kernel or close up shop until a decent one comes around.
[Samsung Epic 4G Touch] tersoth:
+2 I'm getting this as well. Any help would be appreciated
[Samsung Epic 4G Touch] tersoth:
I was having the same problem till I installed v 1.2.0 after I installed that I had no problems. Just make sure to uninstall v 1.3.x
[Samsung Epic 4G Touch] CoolWheelChair:
ok

i finally got it,

u have to be in root

sudo -i

make sure android debugging is on and try it again. i think for me it was a combo of not having the debugging on and not being in root.

thanks guys for the help, the answers were all there i just had to look for em.
[Samsung Epic 4G Touch] todivefor:
I have Samsung Galaxy SII Epic 4G Touch and am running Mac OSX Lion. Anyone successfully root in this environment with Heimdall?
[Samsung Epic 4G Touch] wase4711:
yep, more than once
[Samsung Epic 4G Touch] EeZeEpEe:
Yup. Rooted my Epic 4G Touch with Lion and had no problems.
[Samsung Epic 4G Touch] mikegoldnj:
Claiming interface......failed

Ok...I have Heimdall 1.20, in root in terminal, usb debugging enabled on phone, in download mode, plugged in usb, gave flash command, keep getting "Claiming interface... failed."

Any suggestions?
[Samsung Epic 4G Touch] hotspace:
@mike I installed the Heimdall front end and then installed via the terminal.

Try this

1 put phone in download

2 plug phone into usb

3 from the terminal window Heimdall detect

You should see something like "Device Attached" if not start troubleshooting. I'd start by unuinstalling/restarting/reinstalling/restarting and then reconnecting the phone and attempting number 1-3 again.

Then follow the instructions just like in the OP.
[Samsung Epic 4G Touch] mikegoldnj:
Thanks...I get the device detected but still get the claiming interface failed message.
[Samsung Epic 4G Touch] hotspace:
Try a different cable. I think you might be surprised.
[Samsung Epic 4G Touch] mikegoldnj:
I tried two different cables, tried with them plugged in to a USB Hub and plugged in directly to the Mac.

Same failed result.
[Samsung Epic 4G Touch] hotspace:
Was there a computer restart each time too? A no **** pwr dwn restart?

HAve you tried extracting a pit from the phone?

download-pit --output <filename>

We need to troubleshoot to see if this is a phone thing or a Mac thing
[Samsung Epic 4G Touch] mikegoldnj:
Yes, full restart/power down done.

Just tried downloading pit. Detects device. Same error claiming interface failed.

On phone's Odin screen "Custom Binary Download" = No Is this normal or is there a way to change this?
[Samsung Epic 4G Touch] sc00basteve:
I'm having the same "claiming interface failed" errors.

Tried same fixes and no luck even though heimdall detect says my ET4G is connected.

Sent from my Epic Touch 4G.
[Samsung Epic 4G Touch] hotspace:
Do you mean the Download screen?

Also, do you have ADB working on your Mac?
[Samsung Epic 4G Touch] mikegoldnj:
Yes, that is the screen.
[Samsung Epic 4G Touch] hotspace:
How about the ADB?

---------- Post added at 02:20 PM ---------- Previous post was at 02:18 PM ----------

I should probably add...I'm by no means an expert. I'm just trying to help you troubleshoot.

Have you tried anything that is not in this thread? If yes....what? I want to get this thing done for ya.
[Samsung Epic 4G Touch] mikegoldnj:
ADB is working.

I appreciate your efforts! I rooted my EVO no problem.

This one seems quite different.
[Samsung Epic 4G Touch] wase4711:
for mac users having the "claiming interface" issue, try a different cable, try rebooting the computer, try fixing permissions, and rebooting, and try uninstaling heimdall and reinstalling it

version 1.2 works the best..

It took me a number of attempts and fixes to do it, but it worked...eventually..

or, find a friend with a win doze machine, and do it through Odin
[Samsung Epic 4G Touch] hotspace:
@mike what version of OS X are you running?

Also, the input Wase has provided is exactly what I would do. If you've tried all of Wase's suggestions, there might be other Software on your machine conflicting with Heimdall.
[Samsung Epic 4G Touch] mikegoldnj:
I'm on Lion (10.7.2)

I'm repairing permissions now. Already tried two different cables attached via powered usb hub and attached directly to usb port on mac.

ADB definitely finds device connected. Is there a way to root the Samsung via ADB or is it only through Heimdall?
[Samsung Epic 4G Touch] wase4711:
I was never able to do it on Lion; I used my sons machine and he has snow leopard...
[Samsung Epic 4G Touch] hotspace:
I was reading before rooting mine and I recall reading something that said no one had been able root on Lion. I might be wrong....Also, I'm not sure of flashing kernel via ADB on a Samsung device. Ultimately, that is what would need to happen.
[Samsung Epic 4G Touch] mikegoldnj:
Unfortunately, all the Macs in the house are on Lion. The only pc I have is a work laptop but it's locked down for any outside programs.
[Samsung Epic 4G Touch] wase4711:
thats a drag, because I was never able to get it to install on lion 10.7.2
[Samsung Epic 4G Touch] todivefor:
I asked that question earlier in this thread, and someone responded they had gotten it to work on lion.
[Samsung Epic 4G Touch] mikegoldnj:
I also noticed that when I'm using the Heimdall front end, and try to choose the zImage file, I get a message that it can't find the firmware xml.

I tried redownloading several times with same result.
[Samsung Epic 4G Touch] EeZeEpEe:
I rooted it with Lion and Heimdall 1.3.0.

Don't really know why it worked for me and others are having problems.
[Samsung Epic 4G Touch] mikegoldnj:
I've now tried with three different versions of Heimdall (1.20, 1.30, and 1.31) all detect the device and all come up with the error on claiming interface.

The error comes up not only on the flash command but also on download-pit and print-pit.
[Samsung Epic 4G Touch] sc00basteve:
Same here. I think it time to take one of my buddies hostage for his win doze machine. lol
[Samsung Epic 4G Touch] EeZeEpEe:
Yeah I would just do that then. I rooted a coworkers phone while at work and used odin.
[Samsung Epic 4G Touch] mikegoldnj:
I finally gave up and rooted on a windows machine. At first I thought I had bricked the phone but I was able to finally flash the rooted kernel and then flash Calkulin's ROM.

Thanks for all the help.
[Samsung Epic 4G Touch] admang:
I kept having the same issues with heimdall and even ODIN using Wine wasn't recognizing the phone for some reason. I ended up rooting successfully with these very simple command line instructions.
[Samsung Epic 4G Touch] kinesis:
how do i do this for the regular Epic 4g? I can't find information anywhere on Epic4G + EI22 + Heimdall root.. Please help.
[Samsung Epic 4G Touch] kxmas:
It worked for me. He assumes that you're a kernel with superuser bundled. I didn't want to go that quickly though. One hack at a time :) Once clockworkmod was installed, then I just flashed the superuser zip file through it and called it.

I used this stock kernel, repacked with clockworkmod.

http://chris41g.devphone.org/index.php?dir=EpicTouch%2FStock+Repack%2FEG31%2F

grab the .md5 and run

tar xvf StockCWM5-EG31.tar.md5

to get the kernel image file.
[Samsung Epic 4G Touch] berto55:
How do I figure out what my username is??
[Samsung Epic 4G Touch] EeZeEpEe:
Username for Mac is whatever your home folder name is. I believe it's cap sensitive. I think it's also the name that appears in Terminal next to the $ symbol.
[Samsung Epic 4G Touch] IIIDOUBLETAPIII:
Ive tried these steps and it came up with "can not detect compatible devices" what should I do?

My phone is in download mode and everything.
[Samsung Epic 4G Touch] musclehead84:
Use the auto root package that is stockied. This is a little old. If your device is not detected you need to install the drivers.
[Samsung Epic 4G Touch] IIIDOUBLETAPIII:
but im running mac os x lion, I dont think i can download any drivers. if so how do i get them.
[Samsung Epic 4G Touch] Jabawockee:
When u plug your phone in to Mac does the usb drive show up on your desktop? I used this method and I too am running lion worked flawlessly.

sent from the future via Nocturnal'd 3D
[Samsung Epic 4G Touch] sanchez:
Worked for me on Lion as well, first try. Installed the Heimdall binary, put phone in download mode and flashed.

Worked like a charm. Only took like 15 seconds too :D
[Samsung Epic 4G Touch] konman21:
help out a brother

any ideas? Lion 10.7.2

Initialising connection...

Detecting device...

Claiming interface...

ERROR: Claiming interface failed!
[Samsung Epic 4G Touch] lafester:
Same problem here.... Any solution to this?
[Samsung Epic 4G Touch] simply dave:
Hello,

I'm stuck on step 4.

In my terminal after typing cd /home/myownusername/Downloads

No such file or directory comes up. Been typing it over and over now for the past 20mins and it still tells me the same.

any thoughts?

Sorry I didn't you liked to be contacted whether here, facebook, or youtube.

Thanks.

Dave.