Can someone please help me, or point me in the right direction on how to setup and run simple commands through adb on a MAC? Yes, I've used the search, and yes I've searched all over the internet but I still cannot figure it out. Sorry for my stupidity lol
But any help would be greatly appreciated, thank you
Perhaps you could say a few words about what you have tried already and where you are stopped.
I'm assuming you've downloaded and installed the Mac version of the SDK, yes?
On the phone, you need to turn on Settings -> Applications -> Development -> USB debugging (and may as well check "Stay awake", too).
I don't have a OS/X box, but on Linux you need to perform the *first* adb command as root... the first time an "adb" command is run (after a reboot) it starts up an adb-server process, and that needs to be priviliged enough to write to USB. (After that, you can run adb commands as any user, since those commands "talk" to the adb-server on your Mac, which in turn talks to the phone over the USB cable.)
bftb0
Go to developer. android. com/sdk/index.html (take out the spaces - I still can't post links for some reason) and download the Android SDK for Mac. That same page also includes directions on how to get started with installation. You'll be using the Terminal within Mac OS X for ADB commands, so I would recommend getting comfortable with Terminal before jumping into the SDK. Unfortunately, you'll have to look this up because I couldn't even begin to explain everything, nor do I have the time. Hope the rest helps, though.
bftb0 said:
Perhaps you could say a few words about what you have tried already and where you are stopped.
I'm assuming you've downloaded and installed the Mac version of the SDK, yes?
On the phone, you need to turn on Settings -> Applications -> Development -> USB debugging (and may as well check "Stay awake", too).
I don't have a OS/X box, but on Linux you need to perform the *first* adb command as root... the first time an "adb" command is run (after a reboot) it starts up an adb-server process, and that needs to be priviliged enough to write to USB. (After that, you can run adb commands as any user, since those commands "talk" to the adb-server on your Mac, which in turn talks to the phone over the USB cable.)
bftb0
Click to expand...
Click to collapse
Yes I've downloaded and installed the sdk, turned debugging on and now im trying to flash the recovery image onto my phone and that is where im lost at because I don't know exactly what to do
Los-O said:
Yes I've downloaded and installed the sdk, turned debugging on and now im trying to flash the recovery image onto my phone and that is where im lost at because I don't know exactly what to do
Click to expand...
Click to collapse
Note that what you are asking (now) is completely different than what you asked about in your OP - in fact, OS X is immaterial, really, in light of what you just indicated. That suggests that you are in a hurry... if that is the case, I recommend you spend a couple days reading before you rush off and do something you might regret. It is evident from your response that you really have not been reading the threads here with much diligence.
If you are trying to flash a recovery image, that implies that your phone is already rooted; either that what you are trying it isn't going to work - you have to have a rooted phone to begin with before you flash a custom recovery image. At the moment, you can root your Eris only if it has a 1.5 (1.16.605.1 or 1.17.605.1) official Verizon/HTC release on it. This has been described if not a hundred times in the threads here, at least tens of times - you need to read some more.
Nevertheless, if you want to rush into something, here is a step by step set of instructions which was current a couple of days ago. I won't vouch for it being 100% up to date with the latest and greatest images (either ROM or recovery), but it completely describes the process involved.
Stock 1.5 --> Root (2.1) install --> Custom Recovery install -> recovery to custom ROM 0.3. That's what is working at the moment.
bftb0
bftb0 said:
Note that what you are asking (now) is completely different than what you asked about in your OP - in fact, OS X is immaterial, really, in light of what you just indicated. That suggests that you are in a hurry... if that is the case, I recommend you spend a couple days reading before you rush off and do something you might regret. It is evident from your response that you really have not been reading the threads here with much diligence.
If you are trying to flash a recovery image, that implies that your phone is already rooted; either that what you are trying it isn't going to work - you have to have a rooted phone to begin with before you flash a custom recovery image. At the moment, you can root your Eris only if it has a 1.5 (1.16.605.1 or 1.17.605.1) official Verizon/HTC release on it. This has been described if not a hundred times in the threads here, at least tens of times - you need to read some more.
Stock 1.5 --> Root (2.1) install --> Custom Recovery install -> recovery to custom ROM 0.3. That's what is working at the moment.
bftb0
Click to expand...
Click to collapse
I've already rooted my phone
Los-O said:
I've already rooted my phone
Click to expand...
Click to collapse
Well, then you should be on your way; the instructions for what you are trying to attempt are in that link I provided for you in answer to your question (which you purposely redacted when you quoted my post).
I understand that it's your first post, and I should give some leeway for that reason alone, especially since you might have gotten root without ever having used "adb" or "fastboot". (PB00IMG.ZIP method).
On the other hand, I think you can see my point. Please try to avoid wasting other people's time by providing them useful & relevant details of your situation so they can give you good answers. And reading some of the links adjacent to your own post which actually give exactly the details you are asking for might be a good idea, too.
You wanted to know "What are the directions to DisneyWorld?", but instead asked "How do I put gas in my car?" - when you already knew exactly how to do that. But don't take my word for it - reread your first post for yourself - it actually says nothing about what you are trying to do.
I don't know, maybe I got this all wrong, and you still don't have your phone talking to your OS X machine correctly with adb, and that's the source of the trouble. But then, there would be no way to know one way or another - you haven't really said.
bftb0
Download the android sdk and run this automator script.
20 Questions
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Once you have the android sdk unzipped, add the full path to the android tools directory to your path.
I just added the path to my .bash_profile.
For me it looks like this:
export ANDROID-SDK=/Users/Aaron/android-sdk/
export PATH=$ANDROID-SDK/toolsATH
Then I save and close my bash_profile and run the command, from the terminal:
source .bash_profile
This reloads the bash_profile into the shell. Then cd to your android tools directory. Once you get into the tools directory type the command adb. If everything is correct you should see a help menu spit out to the console.
If you need help with your bash_profile a simple google search will help you out.
hey bftb0,
just wanted to chime in and say thanks for that step-by-step. been wrestling with the same issues as the original poster and your walk through got it going. thanks for being patient.
taocow
bftb0,
thank you so so soo much for that last post, I think i've finally figured it out. and also thank you for your patience, i wish i could buy you a coke or something lol
taocow said:
hey bftb0,
just wanted to chime in and say thanks for that step-by-step. been wrestling with the same issues as the original poster and your walk through got it going. thanks for being patient.
taocow
Click to expand...
Click to collapse
los-O said:
bftb0,
thank you so so soo much for that last post, I think i've finally figured it out. and also thank you for your patience, i wish i could buy you a coke or something lol
Click to expand...
Click to collapse
taocow / los-O
Did you need to run the first "adb" command as root with "sudo" ? Let me know - and also mention the version of OS X that you are using; maybe it will help other Mac users if they read this thread. (I got the impression from reading a little bit that different releases of OS X might handle "sudo" a little differently - or have different device permissions for regular users.)
Also, in reviewing this thread, I have to say ... I acted like an a$$. And I should know better, I did IT for a while. If there is one thing I learned about dealing with people and computers, it's that it is extremely easy for a misunderstanding to occur, and especially if you are helping someone out over the phone or via mail/forum. Please accept my apologies.
bftb0
bftb0 said:
taocow / los-O
Did you need to run the first "adb" command as root with "sudo" ? Let me know - and also mention the version of OS X that you are using; maybe it will help other Mac users if they read this thread. (I got the impression from reading a little bit that different releases of OS X might handle "sudo" a little differently - or have different device permissions for regular users.)
Also, in reviewing this thread, I have to say ... I acted like an a$$. And I should know better, I did IT for a while. If there is one thing I learned about dealing with people and computers, it's that it is extremely easy for a misunderstanding to occur, and especially if you are helping someone out over the phone or via mail/forum. Please accept my apologies.
bftb0
Click to expand...
Click to collapse
also now im able to install the recovery (thanks to you) but when i try and push the recovery and flash images i get
"cannot stat 'recovery.img': No such file or directory" same for the flash image
but i put the files in the tools folder like the guide said to do...?
also im on OS X 10.6.2, but no i didnt have to use the "sudo" thing you were talking about, the "adb devices" command worked the first try. and dont worry about it, i understand where you were coming from. but apology accepted, though
Los-O said:
also now im able to install the recovery (thanks to you) but when i try and push the recovery and flash images i get "cannot stat 'recovery.img': No such file or directory" same for the flash image but i put the files in the tools folder like the guide said to do...?
Click to expand...
Click to collapse
That sounds like you are referring to the files by name, but they are not in the current directory where you are running the fastboot command.
The "pwd" command (Print Working Directory) tells you what your current directory is.
The "cd folder-path" command (Change Directory) allows you to change the Terminal/Shell's idea of where the "current directory" is.
The idea behind the PATH variable is that it is a searchable list (separated by ':' colon characters), so that you can be in a given directory with the files you want to manipulate, but the commands you use are in other directories. When you start a command by typing its' name, the Terminal/Shell app walks through that list of folders in PATH (from left to right in order), looking for that program by name.
That means that if you want to run a program ("proggie") that opens a file ("myfile") that is in the current directory you might type the command.
$ proggie myfile
(or $ proggie ./myfile )
... and as long as "proggie" was in one of the folders listed in your PATH, it would run, and find your file "myfile".
But, there is no requirement that you be in the same directory with your files, or the program that you are running (for instance "fastboot"). In those cases, you need to explicitly specify the complete path to your files or programs, so they can be found. For instance:
$ proggie /users/los-o/mystuff/project3/myfile
or, if "proggie" was not in a folder in your PATH, but you knew that it was located in /opt/tools, you could type the command
$ /opt/tools/proggie myfile
If your current directory contains the file "myfile", or
$ /opt/tools/proggie /users/los-o/mystuff/project/myfile.
Same deal with fastboot - you give it the name of the recovery file as the 3rd argument on the "command line"
$ fastboot flash recovery name-of-my-copy-of-the-recovery-file.img
bftb0
*Whew!* Ok thanks again bftb0 for all the help, I think im finally starting to get the hang of this adb stuff
u have a knack for teaching
bftb0 said:
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Click to expand...
Click to collapse
excellent post...very helpful
Los-O said:
Can someone please help me, or point me in the right direction on how to setup and run simple commands through adb on a MAC? Yes, I've used the search, and yes I've searched all over the internet but I still cannot figure it out. Sorry for my stupidity lol
But any help would be greatly appreciated, thank you
Click to expand...
Click to collapse
I do everything on a Mac, so I would be the guy to ask. How far did you get? Have you unzipped the sdk to a folder?
Basically the difference between mac and others is that when others do a command like adb, we have to do ./adb This is true for other commands too. It's easy once you get used to it.
bftb0,
Thanks so much! Step 6 solved my problem
Thank you!!
bftb0 said:
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Click to expand...
Click to collapse
Wow what a straightforward guide to helping me get this set up!! A million thanks! I don't even have an Eris, but what model of the phone you have is irrevelant to this guide...
Thanks again!!
I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.
That's not how it works. When you use the option in SuperOneClick, it enables that option for you, even if it doesn't show up in settings>applications.
Thanks. When using SuperOneClick I was able to root, but I wan't able to allow Unknown Sources through Settings->Applications.
Now it works!
thanks, sideloading didnt work for me using aroot.
i rooted using SOC a while ago, and DLed the official PSN apk yesterday since it's not on the US market, and installed it by clicking the apk in file manager with no problem.
Thank you so much! This finally worked! Using aRoot/GladEnable/SuperOneClick , all of them SAID it was enabled but it clearly wasn't ... when I navigated to the db field it was still at '1' .. thanks for this, finally it's working
i am on gingerblur, and when clicking the menu button i don't get a dialog to do anything. Maybe a bug of the theme?
So i can't use root explorer to do this, but anyway this is useful since now i know the database name and can do it by hand...
For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done
franciscojavierleon said:
For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done
Click to expand...
Click to collapse
I tried this and it did not work just said sqlite3 not found. Type exit and type exit then type sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" it just locked up terminal. If I type sqlite3 before adb shell it finds it.
Used root explorer and copied settings.db to sdcard. Once there used as a disk drive on computer. Edited it with navcat for sqlite and saved it. Then disconnected it for computer used root explorer and copied it back to data and overwrote existing file. Rebooted and all was fine.
I did everything, but I am not able to edit the field...
"Thanks
manpreet14 said:
I did everything, but I am not able to edit the field...
"Thanks
Click to expand...
Click to collapse
thanks much
i got it
BravoMotorola said:
I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.
Click to expand...
Click to collapse
Thanx. Very useful info.
Worked for me.
Thanks
Works Great. Thank you!
is there a way to enable side loading with out rooting the phone?
aszrael1266 said:
is there a way to enable side loading with out rooting the phone?
Click to expand...
Click to collapse
sideload wonder machine. look it up. pretty easy.
BravoMotorola said:
I don't know about you, but SuperOneClick's Allow Non Market Apps feature didn't work for me. When I went to setting>applications there was no check box for Unknown sources present. I got it by using Root Explorer and SQLight Editor (both on the market)
1. Use "RootExplorer" take you to
/data/data/com.motorola.android.providers.settings/databases/settings.db/settings
2. click on the "Value" colum of "force_only_market_apps"
3. Press "menu" button and select "Edit Field"
4. Change "1" to "0", then save.
Without even doing a factory reset or just a regular reboot you should have an unknown sources box available in your settings>applications.
Click to expand...
Click to collapse
Thanks for this instruction...
Even though this thread is a little old it did help me and therefore want to add my two cents worth to possible help others who may be having issues. I have a rooted Motorola Flipside.
I purchased SQL Lite Editor from the market and was able to change the value directly in it. Here's how:
1. Download and install SQL Lite Editor from the market.
2. Start SQL Lite Editor to display a list of the applications installed on your device.
3. Look for the application titled Settings Storage (and in smaller print underneath it will display "com.motorola.android.providers.settings".
4. Select Settings.db.
5. Select Settings.
6. In the list of columns scroll down to item #70, "force_only_market_apps" and select it.
7. Click the shortcut menu on your device and select Edit Record.
8. Change the value from 1 to 0 then save and exit SQL Lite Editor.
9. Go to Settings > Applications. Unknown Sources will be visible and you will be able to check it.
Hope this helps anyone else who has issues.
Regards,
Greg
franciscojavierleon said:
For those that want to do this by hand:
-connect your phone via usb, enable usb debugging
-from a command line, go where you have adb installed (android sdk or many scripts on this forum)
-run adb shell, then su. accept the message on the phone if prompted.
-type: sqlite3 /data/data/com.motorola.android.providers.settings/databases/settings.db "UPDATE settings SET value=0 WHERE name='force_only_market_apps';" then enter, and you are done
Click to expand...
Click to collapse
You are awesome buddy.. thanx
In Blayo 0.7 rom written
kernel modules
Loading kernel modules is done by editing /data/local/modules file. If you want to enable for example ipv6 support, you have to edit this file adding "ipv6" (without absolute path and any suffixes) to it. The same goes for other modules too. Modules are added separated by spaces.
Click to expand...
Click to collapse
So how I edit this files?or how I can find their location?
Has this forum some information about editing Android system?
Using some file manager (astro, open intents, root explorer.. whatever you have installed), navigate to that modules file and open it in a text editor, then literally just type in 'ipv6' without the quotations, then save and exit. Reboot your phone and you're good to go.
If you feel intensely nerdy you could echo it in:
Code:
adb shell
echo "ipv6" >> /data/local/modules
reboot
el.dizzee said:
Using some file manager (astro, open intents, root explorer.. whatever you have installed), navigate to that modules file and open it in a text editor, then literally just type in 'ipv6' without the quotations, then save and exit. Reboot your phone and you're good to go.
Click to expand...
Click to collapse
I opened in a text editor but it doesn't show me nothing
I use root explorer
TheGrammarFreak said:
If you feel intensely nerdy you could echo it in:
Code:
adb shell
echo "ipv6" >> /data/local/modules
reboot
Click to expand...
Click to collapse
write "ipv6" quotes or not?
With quotes, I think. To check what you added to the file you'd just echo or cat the file back. If it's go quotes then you can overwrite the whole file by using a > instead of >>
TheGrammarFreak said:
With quotes, I think. To check what you added to the file you'd just echo or cat the file back. If it's go quotes then you can overwrite the whole file by using a > instead of >>
Click to expand...
Click to collapse
Sorry for this silly question but what the difference between echo or cat?
I think I will be on the first way because I don't really know how to use ADB right?
virus54 said:
Sorry for this silly question but what the difference between echo or cat?
I think I will be on the first way because I don't really know how to use ADB right?
Click to expand...
Click to collapse
Lol. Cat would be better in this case. And I did suggest this method with the preface "If you feel intensely nerdy you could ..."
ADB is easy though
Can you plz give me a guide with ADB?
I will try your way but there is may be something bad with my phone?
Download this (it's the ADB tools) to a known location. Then extract the zip to a known location. Open a command window in that location (for the sake of this guide: C:\ADB) So open CMD (start, run, type CMD, hit enter) In CMD type "cd C:\ADB". Plug your phone into the computer (make sure you're using CM). Debugging mode should be on (you'll get a notification in the status bar of your phone). Type "adb shell". You'll end up with a "#" and nothing else (if you get a "$" just type "su" and hit enter, and on the phone's screen accept the Superuser request).
Execute your comands
TheGrammarFreak said:
Download this (it's the ADB tools) to a known location. Then extract the zip to a known location. Open a command window in that location (for the sake of this guide: C:\ADB) So open CMD (start, run, type CMD, hit enter) In CMD type "cd C:\ADB". Plug your phone into the computer (make sure you're using CM). Debugging mode should be on (you'll get a notification in the status bar of your phone). Type "adb shell". You'll end up with a "#" and nothing else (if you get a "$" just type "su" and hit enter, and on the phone's screen accept the Superuser request).
Execute your comands
Click to expand...
Click to collapse
Thank you.
I succeed
what else I can do with ADB?
virus54 said:
Thank you.
I succeed
what else I can do with ADB?
Click to expand...
Click to collapse
Loads
10chars
thank you with your help i did it
virus54 said:
thank you with your help i did it
Click to expand...
Click to collapse
Sweet.
twitter.com/TheGrammarFreak
virus54 said:
I opened in a text editor but it doesn't show me nothing
I use root explorer
write "ipv6" quotes or not?
Click to expand...
Click to collapse
I guess I'm kinda late on the response, but yeah, it's supposed to be blank. And then all you have to to is add in "ipv6", WITHOUT the quotes, and then save and exit. But TGF's method works well too, didn't know to do that.
No problem I will look and learn too
better that i will enter as a 'Hex editor'?
because on "text editor" I cannot edit
Hi all!
How I can configure the pie so it takes a screenshot?
up!
There is a forum specifically for questions (Hint: This isn't it)
You shouldn't bump your own threads
You should ask in the LMT thread itself: http://forum.xda-developers.com/showthread.php?t=1330150
There's a native "screencap" binary that can be setup to execute in a shell script, that you can then assign the script to run for specific pie location.
Sample code:
Code:
#command line screen capture
sleep 1
screencap -p /sdcard/Pictures/Screenshots/screencap_$(date +"%Y-%m-%d_%H-%M-%S").png
Adjust to your needs / location where you want the captures saved.
Drop your script in a file, such as "screen.sh", push to your phone, change permissions to make executable, point PIE to the script, and you're good to go.
styckx said:
There is a forum specifically for questions (Hint: This isn't it)
You shouldn't bump your own threads
You should ask in the LMT thread itself: http://forum.xda-developers.com/showthread.php?t=1330150
Click to expand...
Click to collapse
Sorry, I didn't know it.
JsChiSurf said:
There's a native "screencap" binary that can be setup to execute in a shell script, that you can then assign the script to run for specific pie location.
Sample code:
Code:
#command line screen capture
sleep 1
screencap -p /sdcard/Pictures/Screenshots/screencap_$(date +"%Y-%m-%d_%H-%M-%S").png
Adjust to your needs / location where you want the captures saved.
Drop your script in a file, such as "screen.sh", push to your phone, change permissions to make executable, point PIE to the script, and you're good to go.
Click to expand...
Click to collapse
Thanks
Edit: How I change permissions? I don't understand : point PIE to the script
Dejotaa said:
Sorry, I didn't know it.
Thanks
Edit: How I change permissions? I don't understand : point PIE to the script
Click to expand...
Click to collapse
From adb shell you can 'chmod' the file, or if you don't use adb, use a file manager instead. In adb, "chmod 777 screen.sh" should do the trick
In LMT, once your script is in place, and tested to work from the command line and/or terminal emulator, go to the 'PIE' tab, select the piece piece, i.e. "Pie item 1 longpress', scroll to 'Advanced Commands', select 'Script', point to the location where you placed the script, such as "/system/screen.sh, profit.
JsChiSurf said:
From adb shell you can 'chmod' the file, or if you don't use adb, use a file manager instead. In adb, "chmod 777 screen.sh" should do the trick
In LMT, once your script is in place, and tested to work from the command line and/or terminal emulator, go to the 'PIE' tab, select the piece piece, i.e. "Pie item 1 longpress', scroll to 'Advanced Commands', select 'Script', point to the location where you placed the script, such as "/system/screen.sh, profit.
Click to expand...
Click to collapse
Can you do the instructions for "dummies" ?
Edit:
Where I have to put the Screenshot.sh file for use "chmod 777 screenshot.sh" in adb?