Develop Bugs

ADB: "no permissions" (Linux Mint 9) [SOLVED]

SOLVED
Big thanks once again to vladthedog!
vladthedog said:
HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.
Click to expand...
Click to collapse
/SOLVED - note, tried again to make sure and got "adb not recognized command" or something simlar, so i just did
Code:
sudo su
./adb kill-server
./adb start-server
than i could exit root and it worked still. had to be in the sdk/tools folder for it to work. seems i still haven't gotten ADB into the proper setting to run w/out being in the directory.
[email protected] ~/sdk/tools $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~/sdk/tools $ adb get-state
unknown
[email protected] ~/sdk/tools $ adb remount
error: insufficient permissions for device
Click to expand...
Click to collapse
i have USB debugging enabled.
it does this on every rom i try. currently using latest cyanogen.
not sure how to go about getting 'permission' so i can run ADB commands to my phone.
OS is Linux Mint 9, tried it as SU/ROOT also, get the same thing.

Try another os/computer with your phone and see if you still get the error

http://forum.xda-developers.com/showthread.php?t=722854
there's a thread on someone having java issues with linux mint, but there are multiple posts (prior to figuring out it was java) on other things about getting adb running in linux. look for my post (the long one) because it sounds like you just need to get the device running as root.

vladthedog said:
http://forum.xda-developers.com/showthread.php?t=722854
there's a thread on someone having java issues with linux mint, but there are multiple posts (prior to figuring out it was java) on other things about getting adb running in linux. look for my post (the long one) because it sounds like you just need to get the device running as root.
Click to expand...
Click to collapse
yeah that was my thread =P
ADB worked on this phone fine for a while than just recently started saying No Permissions. I didn't delete anything, didn't adjust anything, all I've done is flash different roms on the phone.
S'pose i'll steal the wifes laptop and load ADB onto it and give it a go later tonight.

HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.

yeah thats what i just did to see and it indeed worked, than came here to post i found it and read yours so now i feel fantastic =D
slowly still learning linux. i might switch from Mint to Ubuntu since it seems to have more made for it and more support out there for a newbie such as myself.
i should also add, i unplugged my usb wireless mouse thinking it may of interfered with it, but seeing that you posted what i tried i'll go that it wasn't it. just a note to anyone else.

Nrre said:
yeah thats what i just did to see and it indeed worked, than came here to post i found it and read yours so now i feel fantastic =D
slowly still learning linux. i might switch from Mint to Ubuntu since it seems to have more made for it and more support out there for a newbie such as myself.
i should also add, i unplugged my usb wireless mouse thinking it may of interfered with it, but seeing that you posted what i tried i'll go that it wasn't it. just a note to anyone else.
Click to expand...
Click to collapse
I'd recommend Ubuntu as well. Over the years I've goofed around with linux, but about 6 months ago I ended up taking the plunge and removing my windows partition and going full-on linux. I've found that ubuntu seems to have the most support out there for us newbies.
Now that I'm more confortable, i've installed a few different flavors of linux on my laptop, but always find myself coming back to ubuntu. again, its primarily because of the support issue when I screw something up

Yeah I am right now switching to Ubuntu since there is a ton more support out there. Loading up the flash drive with it right now.
Once again thanks for all the help.

vladthedog
Thanks that saved my life

Works on Pardus-Linux 2011.2-CONFIRMED
vladthedog said:
HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.
Click to expand...
Click to collapse
Thanks for the post...I was racking my brain trying to get ADB working on Pardus-Linux. I used to be an Ubuntu guy and recently saw the light...LOL.
Thanks for the help.

thanks
thanks i got it WHOO hoo View attachment 1282945 srry i had to re-edit it for my device id

Thank you man ! This procedure also worked for me on Linux Mint !
I was about to try on windows, what a shame...

[Q] Cyanogenmod 7 and Linux

Hi all,
I have just received my Defy and I'd like to flash Cyanogenmod 7, I've flashed numerous roms to numerous phones in the past but I was always using Windows. I now use Linux (latest ubuntu derivative).
Is there a guide anywhere for flashing from a linux machine? My google-fu is pretty much pulling up a blank on the subject!
Thanks very much

Follow steps from FAQ for CM7, and just use this : http://forum.xda-developers.com/showthread.php?t=1076138 for flashing SBF and rooting,
It's my second post for the same question today

There's just two things to know:
1) You don't use RSD Lite to flash sbf files, you use this instead: http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html
2) To root the phone you don't use SuperOneClick. Instead, get this DefyRoot pack: http://forum.xda-developers.com/showthread.php?t=1076138. Extract the pack, run the script using sudo.
And that's that. With the above differences in mind, you can follow the usual instructions: http://forum.xda-developers.com/showthread.php?t=1065798
Edit: Damn, bikerabhinav was faster

Thank you guys for the quick replies! time to give it a go
Sorry but you don't happen to know the link for installing adb on linux do you? presumably I need it hehe

I got the SDK and extracted to a directory of my choice, how on earth do I use it though, executing android in a terminal does not work, the rest is simple, can't believe I'm stuck on this part lol
I sorted that, I ran android and downloaded the development tools, I now have adb. I need to research more now, ran adb via terminal, then tried to run the rootdefy.sh but it told me adb wasn't started! see this is going to be a learning curve in Linux

You don't need the SDK, the RootDefy pack has everything necessary. I never installed the SDK.
ADB starts automatically if it isn't running yet. Did you run the script as sudo, like I told you? If not, there can be various problems. It's not necessary to run it with sudo if there's an udev rule for the phone. The script attempts to write one, but I'm not sure if it still works with the latest udev versions.
So let's do it manually:
- unplug the phone
- create a /etc/udev/rules.d/51-android.rules file containing this:
Code:
ATTRS{idVendor}=="22b8", MODE="0666"
- now reload udev:
Code:
sudo udevadm control --reload-rules
- just to be sure, kill all previous adb instances:
Code:
sudo pkill adb
- now plug the phone in and run the script again; with or without sudo, it shouldn't make a difference anymore

Thanks very much, all done and dusted now

[Q] Heimdall - "Claiming Interface Failed!"

I am trying to use Heimdall to flash a kernel to my ET4G, but running into a problem. It is able to detect my device, but when I use the flash command I get the following message:
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
This is Heimdall 1.3.0, OSX 10.7.1
Anyone know how to fix this? Thanks in advance!

Just to cover the obvious, you've enabled USB debugging, right?

Kn0wBuddy said:
Just to cover the obvious, you've enabled USB debugging, right?
Click to expand...
Click to collapse
Yes, it is enabled. I've tried every combination of USB settings and running the command with SU privs. I've installed Heimdall twice, to make sure it wasn't a bad install, and I've repaired permissions, and multiple reboots of both devices.

Solved!
It was my Mac. I'd been having issues ever since installing Lion, especially with WiFi and beach balls. So, I did a complete erase and install, and the first thing I did was install Heimdall and ran it, worked perfectly!

Is there any way around this? I would like to avoid reinstalling my OS. I believe that I have the same exact set-up (with Lion). This is my very first time Rooting, coming from the HTC Touch Pro 2. Forgive my noobness...

Kn0wBuddy said:
Just to cover the obvious, you've enabled USB debugging, right?
Click to expand...
Click to collapse
100% irrelevant to Heimdall.
There's a Heimdall update in testing that is supposed to fix a lot of OSX issues.

same error message here also using lion..
any suggestions?
thanks

Did anyone find a solution to this ?

I'm having the same problems. Tried a few different things to get it to work, to no avail... Anyone else? Tried using ODIN in Wine as well, but no dice there.

For what it is worth, heimdall and heimdall-frontend from 64bit Linux, using the official packages off the website yields this:
Code:
# heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
ERROR: Setting up interface failed!
I will keep digging around for solutions but I am fresh out of ideas. It detects the device, claims the interface and errors out in the setting up from what the output says.

im getting this error too! anyone find a fix?

nate633 said:
I am trying to use Heimdall to flash a kernel to my ET4G, but running into a problem. It is able to detect my device, but when I use the flash command I get the following message:
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
This is Heimdall 1.3.0, OSX 10.7.1
Anyone know how to fix this? Thanks in advance!
Click to expand...
Click to collapse
Hi - I had the same issue with OSX 10.6.8 and odin 1.3.1.
I got it to work - without having to reinstall everything on my mac (what kind of fix is that?). Anyway - the fix. I just reinstalled odin - restarted - and tried again - and it worked!
Good-luck.

...
I'm getting the same error as well. the funny thing is that i used zedomaxs method found here: xda-developers.com/showthread.php?t=1277000
and was able to root the first time around, kernel, cwm recover, su installed etc..
but every time i went to flash a new kernel or rom, clockwork (cwm) would not recognize the .zip on my sd card. i tried switching out multiple cards to no avail. not sure if it was an issue with the version of cwm or not but i decided to go back to stock and start the process over again. now i get this same error u guys are in terminal.

Me too With At&t Galaxy s2
I am having the same problem, any known fixes?

I was having the same "claiming interface error" and so I tried reinstalling as suggested in one of the posts. When I reinstalled, I noticed a message saying /System/Library/Extensions/Heimdall.kext wasn't properly installed, so after the installation completed, I restarted and deleted the kext file then reinstalled. After that, everything worked correctly.

everkleer said:
I was having the same "claiming interface error" and so I tried reinstalling as suggested in one of the posts. When I reinstalled, I noticed a message saying /System/Library/Extensions/Heimdall.kext wasn't properly installed, so after the installation completed, I restarted and deleted the kext file then reinstalled. After that, everything worked correctly.
Click to expand...
Click to collapse
How did you uninstall and reinstall the kext file?
Sent from my SAMSUNG-SGH-I777 using XDA App

I had the same problem. I reinstalled heimdall 1.3.1 and rebooted. Worked like a charm.

I'm getting this error on OS X 10.6.8 and can't resolve it. I've reinstalled heimdall multiple times, both from the .dmg and from source. Nothing seems to help.
Regarding the error about /System/Library/Extensions/heimdall.kext, I've noticed that the installer apparently installs it owned by your current user and group. You can verify this causes the error by attempting to load it manually with the command:
Code:
sudo kextload /System/Library/Extensions/heimdall.kext
It will give the dialog that people have been seeing, plus an error on the command line about permissions. Running the following commands fixes it, allowing the previous command to work succesfully:
Code:
sudo chown -R root:wheel /System/Library/Extensions/heimdall.kext
I still have no idea what is causing my errors, though. My only idea is that maybe it is yet another permissions issue that I haven't tracked down, possibly with libusb.
If anyone has any advice, please let me know. Otherwise, I will keep poking and if I by some chance figure it out, I will post here.

i had so many issues with heimdall that i just pulled out my old vista laptop and got her done in no time! heimdall is a cluster if you ask me

Fixed Heimdall "Claiming Interface Failed!" error!
Ok, I have a solution for the interface error. After considering the fact that the one step had permissions issues, it eventually occurred to me that, maybe, just maybe the rest of the issues are all permissions related as well. That said, if you install the heimdall-1.3.1-mac.dmg as root, it works flawlessly.
Open an OS X terminal, then (assuming you downloaded the .dmg to Downloads) type the following commands:
Code:
$ cd ~/Downloads
$ sudo open heimdall-1.3.1-mac.dmg
Enter your password then go through the setup normally. You should not see any errors, including the one about heimdall.kext, it will reboot, and it should work.
NB: If you have your phone plugged in in download mode and restart your computer, you may need to restart your phone and re-enter download mode for heimdall to detect it.
Hope this helps!

[Q] Building CM9, help!

hello xda-developers
I am having problems building from source, I've been trying to get his to work for over a week or so with the help from the lovely people here:
https://github.com/EpicCM/d710tools/issues/10
I think this forum is probably a better place, I will organize my thoughts better on this forum for all to read!
i've tried to install this on different systems, a 12.04 ubuntu, 12.04 and a clean 10.04 vm. in my next post i show all logs for the 10.04 attempt. the build results are also for 10.04
WHAT'S WRONG:
The problem is (depending on the guide i follow) cm9 either does not build (complains about libump.so not existing, despite having the proprietary repo in my localmanifest), or when i install the .zip, my phone goes into an eternal black screen after the "samsung galaxy s2" screen
There are two different basic setups i've been doing (i've tried these two setups in ubuntu 12.04,12.10,10.04LTS)
And i cannot figure out why the [email protected]#$ing [email protected]#$ why!!!!!!!! /rant
(log)Build instructions 1:
this is the build instructions that lead to a build error, these instructions were taken from here:
https://github.com/EpicCM/d710tools/wiki
commands: http://pastebin.com/WbXgKmZp
results:http://pastebin.com/Lq5iLt8L
Note: between each build i do make clobber and make installclean.
(log)Build instructions 2 (after i do make clobber and make install clean, repo sync, and the vendor and d710 tools again):
taken from the readme here
https://github.com/EpicCM/d710tools
commands: . build/envsetup.sh && brunch cm_d710-userdebug
built results:http://pastebin.com/8FWtqkRf
and if you feel the need to download the file, here is a direct download link
buildresults.txt : pastebin.com/download.php?i=8FWtqkRf
NOTE: you'll notice i had to sudo apt-get install schedtool. Also, i've done this from scratch before so i know if i dont at the end up the build it tells me to get pngcrush, so i do that too
WHAT I KNOW:
I've done my homework on the error for the build instructions 1:
-I know libUmp.so is a proprietary file, and the file does no exist in that directory, however it exists in another directory.
-Looking at the proprietary, that is where it should be, is there a script to move these directories? it's not a simple one line cp.
WHAT I DONT KNOW:
-builds but black screens? wtf?
-even if i managed to make something to do the cp to the appropriate directories, I dont even know if i'll end up with the same problem
-perhaps there is more not stated in the tutorial? if so I cannot find it
help? i've lost some hair over this, i hope you all can help buy me time to grow it back
i'll try anything.... i'll start over from an 11.10 if somebody even hints it might work...
what i want from this post
--well of course i would love a solution
--but really what i need is help to debug this, i have no idea where to start, i've done all i believe google and my brain can handle

reserved
more debug information, non build logs. These are the instructions as i followed
LOGS:
With the goal of being very thoughrough, i will start from a clean ubuntu 10.04 VM (network is using bridged), and I will post the result of each command to setup the environment for building.
If i saw an error with these i would google, but i dont see a problem, so i'm here.
Here we go (using this guide to setup env for 10.04 https://github.com/EpicCM/d710tools/wiki)
NOTE: for this step i had to change 0.2.4 to 0.2.6 because 0.2.4 was not building, 0.2.6 appears to work with no problem.
Setup local java repo and java commands: http://pastebin.com/RGhD1Shb
Results: http://pastebin.com/iEnNzSh3
(log)Installing required packages (Ubuntu 10.04)
commands: http://pastebin.com/eCZXkNvV
results: http://pastebin.com/vwzxfVsq
(log)Iidk what this is but guide said to do it for ubuntu 10.04:
command: sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
result: [sudo] password for tryagain: [email protected]:~$
(log)IMKDIRS, DOWNLOAD REPO, INIT REPO:
commands:http://pastebin.com/58aunVxB
results:http://pastebin.com/kKq9vyf5
(log)IThen i LOCAL MANFIFEST saved as local_manifest.xml inside ~/android/system/.repo/local_manifest.xml, here's what my localmanifest looks like:
http://pastebin.com/SCPAV8Ne
(log)IREPO SYNC THE FILES:
you may notice in the script file i had to repo sync -j1 more than once, because sometimes it would fail... in the end had no errors
commands : repo sync -j1
results: http://pastebin.com/a5Pa3sbL
results2: http://pastebin.com/VGPcPrE6
(the reason why there are two results is that i apparently forgot to save the local_manifest.xml the first time, results2 shows with the syncing of the files i have in my local manifest)
(log)IPREBUILTS, APPLY.SH:
commands: http://pastebin.com/VVx84ujN
results: http://pastebin.com/w9Wij28c
NOTE: i had to gedit the vendor to get the term.apk since
https://github.com/downloads/jackpal/Android-Terminal-Emulator/Term.apk isnt working
i replaced https://github.com/downloads/jackpal/Android-Terminal-Emulator/Term.apk with http://dl.dropbox.com/u/11103217/Term.apk to get things going.

reserved
reserved just in case, i got a lot of text

I've tried different jdks different tutorials and refine this from scratch on 3 different Linux versions
Sent from my SPH-D710 using xda app-developers app

updated!!!!

bump
1/24hour bump

1/24 bump

Nigel here, try running running: adb lolcat ; while you're on the blackscreen so we can get some insight into what's wrong with the rom.

so adb logcat doesnt work, it doesnt recognize my device as connected to my computer on the black screen.
The computer says it's an unknown device, or the device errored.
but that didnt stop me from trying anyway, i went into recovery to try and find what i wanted. As adb works in recovery for some reason.
when i execute it in recovery i get this
C:\Users\dfreelan\Downloads>adb logcat
/sbin/sh: exec: line 1: logcat: not found
so I went into adb shell while in recovery and executed /system/bin/logcat and got this
http://pastebin.com/8hnAa3iK
I went into /dev/log and executed "cat main" and tried to cat all the other things there, but i didnt get more information than what you see there.
Here is the recovery.log from installing the .zip, in case that is good for some debugging:
http://pastebin.com/gVC1TYyy

dfreelan said:
so adb logcat doesnt work, it doesnt recognize my device as connected to my computer on the black screen.
The computer says it's an unknown device, or the device errored.
but that didnt stop me from trying anyway, i went into recovery to try and find what i wanted. As adb works in recovery for some reason.
when i execute it in recovery i get this
C:\Users\dfreelan\Downloads>adb logcat
/sbin/sh: exec: line 1: logcat: not found
so I went into adb shell while in recovery and executed /system/bin/logcat and got this
http://pastebin.com/8hnAa3iK
I went into /dev/log and executed "cat main" and tried to cat all the other things there, but i didnt get more information than what you see there.
Here is the recovery.log from installing the .zip, in case that is good for some debugging:
http://pastebin.com/gVC1TYyy
Click to expand...
Click to collapse
adb logcat doesnt work in recovery.
While in recovery, adb shell and pull a last_kmsg, also try editing your local_manifest to build with the ics device tree not the smdk tree and see if that helps.
ie: "<project name="EpicCM/android_device_samsung_d710" path="device/samsung/d710" remote="github" revision="smdk" />" change that to "ics", i think smdk had some issues with cm9.
also if you want, hit up #jb-dev-e4gt on freenode, you may get some help there, our main dev chris41g is MIA so the progress on this device is at a stand-still. Though i do see sbrissen and PhantomPhreak53 are working on cm10.1

hrubak said:
adb logcat doesnt work in recovery.
While in recovery, adb shell and pull a last_kmsg, also try editing your local_manifest to build with the ics device tree not the smdk tree and see if that helps.
ie: "<project name="EpicCM/android_device_samsung_d710" path="device/samsung/d710" remote="github" revision="smdk" />" change that to "ics", i think smdk had some issues with cm9.
also if you want, hit up #jb-dev-e4gt on freenode, you may get some help there, our main dev chris41g is MIA so the progress on this device is at a stand-still. Though i do see sbrissen and PhantomPhreak53 are working on cm10.1
Click to expand...
Click to collapse
well apparently it never writes to /proc/last_kmsg
I figured for kicks and giggles i'd show you kmsg i got freshly booting into recovery, but my guess is that it's no good.
http://pastebin.com/jJC6ZJsZ
here's the brunch std err, they error out as there is no target for d710 (maybe i should use the old kernel? new one is smdk)
http://pastebin.com/jP0mTkZS
brunch stdout
http://pastebin.com/X571EkmR
here's what happens when i use make -j4, you'll notice it still errors out on libUMP.so
http://pastebin.com/eXEcTRPK
here's the new local_manifest.xml, you know to make sure i didnt [email protected]#$ up
http://pastebin.com/zXLCWDAP

when i use the _old kernel (android_kernel_samsung_epic4gtouch_old) i get this build error:
http://pastebin.com/09hDh8Nh
when i use the control kernel (android_kernel_samsung_epic4gtouch) It compiles!!!!!
however, still does the same infinite black screen (and i was so optimistic too)
here's my new local_manifest.xml
http://pastebin.com/FgARtF77
and of course, there is still no last_kmsg :-/

You might take a look at this:
http://aosp.chris41g.org/chris41g_o...How-To-Compile-CyanogenMod-9-from-Source.aspx
I followed this guide, generally, with changes to compile CM10 and got it to work. I did it on ubuntu 12.04. I did have to make some changes for 12.04. I didn't/don't know what I am doing, but got it to compile and flash and work.

todivefor said:
You might take a look at this:
http://aosp.chris41g.org/chris41g_o...How-To-Compile-CyanogenMod-9-from-Source.aspx
I followed this guide, generally, with changes to compile CM10 and got it to work. I did it on ubuntu 12.04. I did have to make some changes for 12.04. I didn't/don't know what I am doing, but got it to compile and flash and work.
Click to expand...
Click to collapse
i was actually doing exactly that to try and get cm9 to work my very first time. i talked to hrubak on the irc channel. He looked at the ICS kernel and noticed chris41g changed some stuff and ssuspected that that's why CM9 wasnt working for me.
He suggested i just do CM10.
i'll post with my success or failure
Thanks for the reply!

[GUIDE] How to ROOT your T-Mobile Galaxy S4 on a Mac / Linux PC using Heimdall

How to ROOT your T-Mobile Galaxy S4 on a Mac / Linux PC using Heimdall​
Before you do ANYTHING, start here:
Download and install Heimdall: http://www.glassechidna.com.au/products/heimdall/
And Install libusbx: http://libusbx.org/
What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung Galaxy S devices.
What is libusbx?
libusbx is a library that provides generic access to USB devices. As a library, it is meant to be used by developers, to facilitate the production of applications that communicate with USB hardware.
Click to expand...
Click to collapse
Onto the magic..
1. Download CF-Root by Chainfire here: http://forum.xda-developers.com/showthread.php?t=2294005
2. Unzip the file: CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
3. Unzip the file called "CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5" that is inside the original zip file.
4. You should end up with "recovery.img" and "cache.img.ext4" (Put them on your desktop or somewhere easy to navigate to!)
5. Put your phone into download mode. (Hold Volume down + Power + Home button)
6. Connect your phone to your computer.
6. Open your favorite Terminal program on your computer. (I use the stock Mac Terminal)
7. Run the following command:
sudo heimdall flash --RECOVERY *RECOVERY DIRECTORY* --CACHE *CACHE DIRECTORY*
NOTE: Replace *RECOVERY DIRECTORY* and *CACHE DIRECTORY* to the full path of where the file is on your computer!
NOTE: --RECOVERY and --CACHE are CASE SENSITIVE!
For example: heimdall flash --recovery C:\Users\user\Desktop\recovery.img --cache C:\Users\user\Desktop\cache.img.ext4
8. Your phone should reboot.
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
9. Done!
Note: This does not install a custom recovery, but you can download ROM Manager from the Play Store and install ClockworkMod Recovery using that. Alternatively, you can flash a recovery.img using the same way you flashed these two files. (heimdall flash --recovery *RECOVERY DIRECTORY*)
Click to expand...
Click to collapse
Getting an error?
If you receive this error message:
Initialising connection…
Detecting device…
Claiming interface…
ERROR: Claiming interface failed!
it’s because you have used the Samsung Kies software, which you should uninstall at once, but as it adds some kernel extensions, run this as well:
A. Launch Terminal
B. Get Root and run these:
sudo sh
kextunload -b com.devguru.driver.SamsungComposite
kextunload -b com.devguru.driver.SamsungACMData
kextunload -b com.devguru.driver.SamsungACMControl
C. Try again!
Click to expand...
Click to collapse

thanks, But a couple of qns.
1. USB debugging should be turned on or off?
2. when I put the device in download mode, it asks up to cancel and down continue in download mode. What to press?
If i put down, it says - downloading do not turn off. At this time, I've not run the heimdall command yet on terminal. (Ubuntu).
The error thats spit out is:
Initialising connection...
Detecting device...
libusbx: error [op_open] libusbx couldn't open USB device /dev/bus/usb/001/007: Permission denied.
libusbx: error [op_open] libusbx requires write access to USB device nodes.
ERROR: Failed to access device. libusb error: -3

didadi said:
thanks, But a couple of qns.
1. USB debugging should be turned on or off?
2. when I put the device in download mode, it asks up to cancel and down continue in download mode. What to press?
If i put down, it says - downloading do not turn off. At this time, I've not run the heimdall command yet on terminal. (Ubuntu).
The error thats spit out is:
Initialising connection...
Detecting device...
libusbx: error [op_open] libusbx couldn't open USB device /dev/bus/usb/001/007: Permission denied.
libusbx: error [op_open] libusbx requires write access to USB device nodes.
ERROR: Failed to access device. libusb error: -3
Click to expand...
Click to collapse
1. It does not matter.
2. Yes, you press volume down to continue.
As for that error, try installing this on your Linux setup: http://libusbx.org/
It should have been bundled with Heimdall for Linux but maybe it isn't.

theexel said:
1. It does not matter.
2. Yes, you press volume down to continue.
As for that error, try installing this on your Linux setup: http://libusbx.org/
It should have been bundled with Heimdall for Linux but maybe it isn't.
Click to expand...
Click to collapse
Hmm,still the same err,but I guess I was able to detect S4.
I did install libusbx from source, by
./configure && make && make install && sudo ldconfig - blah.
Then tried to use heimdall flash command/action.

Try using sudo before the heimdall command.
sudo heimdall flash ....

theexel said:
Try using sudo before the heimdall command.
sudo heimdall flash ....
Click to expand...
Click to collapse
hmm,sudo is able to write,but stil one error, "recovery" not found in specified PIT as below. One last step?
--------
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "recovery" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
heimdall flash --RECOVERY ./clockworkmod_6.0.3.2_jfltespr.img --no-reboot - May be like this?
---------- Post added at 11:13 PM ---------- Previous post was at 11:07 PM ----------
Alright,thank you very much!. I am rooted. Exact command to run is:
sudo heimdall flash --RECOVERY /path_to_recovery/recovery.img --CACHE /path_to_cache/cache.img.ext4
Fantastic! thanks

Glad you got it sorted!
Sent from my SGH-M919 using Tapatalk 4

theexel said:
Glad you got it sorted!
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
Would this also work if say...I bricked my phone?
I run windows virtualized on OpenSUSE, but the USB drivers for windows won't work in a virtual environ. I can never be too sure if I can get my hands on a windows PC.

nyloxy said:
Would this also work if say...I bricked my phone?
I run windows virtualized on OpenSUSE, but the USB drivers for windows won't work in a virtual environ. I can never be too sure if I can get my hands on a windows PC.
Click to expand...
Click to collapse
You'd probably need to flash the whole Samsung Stock firmware not just the files I listed above, but yes, it should be possible, bud. :good:
If you want me to check it out for you and write a tutorial, I'll be more than happy to me.

theexel said:
You'd probably need to flash the whole Samsung Stock firmware not just the files I listed above, but yes, it should be possible, bud. :good:
If you want me to check it out for you and write a tutorial, I'll be more than happy to me.
Click to expand...
Click to collapse
Thanks for the info! Quick tutorial would be the bomb! I just got into rooting and flashing a few weeks ago and I never want to go back! :victory:
Started using the Infamous Alpha. Currently on 8.6, and it's rock solid. I just worry that there may be a time in the near future that I brick my S4 and I'm no longer a fan of windozzz!

Just 3 big steps.
1.Download and install Heimdall: http://www.glassechidna.com.au/products/heimdall/
2. Install libusbx. You need to download the sources and compile them. Usual ./configure, make , make install.
Use sudo su and then compile.
you may have to do , sudo apt-get install libudev-dev before compiling the libusbx libs.
3.Onto the magic..
..as said in post 1....
Make sure to use sudo for the heimdall flash ...Needless to say use the caps.!
Then install cwm from the Google Play and then you are Golden.
Thank you again to theexel for quick replies thru my earlier posts.:good:

Added a fix for a possible error:
If you receive this error message:
Initialising connection…
Detecting device…
Claiming interface…
ERROR: Claiming interface failed!

Can somebody make a video on how to do this?
This sounds confusing and I don't wanna brick my phone lol
I'm willing to donate to whoever does a video!

So will this wipe my phone?

[email protected] said:
So will this wipe my phone?
Click to expand...
Click to collapse
No. It will only root your phone.
flemingg said:
There is nothing can be done without the libraries files.
Click to expand...
Click to collapse
Library files?

Noob help with installing libusbx?
Hi Guys,
First off kudos and many thanks Exel for posting this. Also, sorry to bug you all with such a noob question but may I bother someone to post the exact commands/syntax for installing libusbx on/in mac os x 10.8.x? I've tried looking online and may not be using the right keywords to get the information I need.
Thanks loads for all the help you guys,
nv_gck

Re: Noob help with installing libusbx?
NV_GCK said:
Hi Guys,
First off kudos and many thanks Exel for posting this. Also, sorry to bug you all with such a noob question but may I bother someone to post the exact commands/syntax for installing libusbx on/in mac os x 10.8.x? I've tried looking online and may not be using the right keywords to get the information I need.
Thanks loads for all the help you guys,
nv_gck
Click to expand...
Click to collapse
Hi Guys,
Please ignore my last request. I figured it out from the INSTALL file in the libusbx source code. Also, I did it without installing the full Xcode IDE on my Mac, just the Xcode terminal tools. Have successfully rooted.
Thanks again Exel

NV_GCK said:
Hi Guys,
Please ignore my last request. I figured it out from the INSTALL file in the libusbx source code. Also, I did it without installing the full Xcode IDE on my Mac, just the Xcode terminal tools. Have successfully rooted.
Thanks again Exel
Click to expand...
Click to collapse
Glad you got it working!

It would really be worth it to mention that you actually have to compile libusbx from source. I spent a half hour Googling before coming to this realization.

Hey there fellas, spent the last couple hours trying to get this to work and keep getting hung up in terminal here,
Code:
Invalid argument: folder/recovery.img
Any help?