Database Users

Where's sqlite3?

I have a Nexus One (unlocked, Superboot, amon-ra recovery 1.6) and am trying to issue a sqlite3 command but sqlite3 is unable to be found. I tried whereis but that command can't be found either. Can someone point me to where it is on the Nexus One or maybe it just isn't there in which case, how do I get it on my N1.
Thanks in advance,
Doug

douglasjboehme said:
I have a Nexus One (unlocked, Superboot, amon-ra recovery 1.6) and am trying to issue a sqlite3 command but sqlite3 is unable to be found. I tried whereis but that command can't be found either. Can someone point me to where it is on the Nexus One or maybe it just isn't there in which case, how do I get it on my N1.
Thanks in advance,
Doug
Click to expand...
Click to collapse
Ditto this

douglasjboehme said:
I have a Nexus One (unlocked, Superboot, amon-ra recovery 1.6) and am trying to issue a sqlite3 command but sqlite3 is unable to be found. I tried whereis but that command can't be found either. Can someone point me to where it is on the Nexus One or maybe it just isn't there in which case, how do I get it on my N1.
Thanks in advance,
Doug
Click to expand...
Click to collapse
http://bit.ly/csGw5A
?

Paul22000 said:
http://bit.ly/csGw5A
?
Click to expand...
Click to collapse
We're not stupid lol I'm pretty sure its missing from the superboot package
EDIT: Or the ROM itself

Okay I got around this by grabbing the binary from TheOfficial Nexus1 ROM. Its in the zip file under system/xbin
Then all you have to do is adb remount, adb push sqlite3 /system/xbin/. Then adb shell, chmod 777 /system/xbin/sqlite3

Would you please provide the download for Android version sqlite3
I gained the root access, but I could not find the sqlite3 in production Motorola Droid. would you please give me a download link to download sqlite3 for android? Thanks

[Q] s-on/s-off

hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root

bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..

bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
Not yet till Alpharev v2 realesed
Sent from my HTC Legend

gyroing said:
Not yet till Alpharev v2 realesed
Sent from my HTC Legend
Click to expand...
Click to collapse
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App

niksakl said:
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..
Click to expand...
Click to collapse
As far as I can tell its a new security thing HTC have added to the hboot, basically makes the system folder read only even with root (think that's correct??)
Sent from my HTC Wildfire using XDA App

bassmonkey said:
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.

You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.

thanks for the response guys
71baker said:
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
how do you do it through recovery? im guessing thatd be with adb?
Tetractys said:
You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.
Click to expand...
Click to collapse
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??

bassmonkey said:
thanks for the response guys
how do you do it through recovery? im guessing thatd be with adb?
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??
Click to expand...
Click to collapse
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.

Tetractys said:
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.
Click to expand...
Click to collapse
lol.'not concerned' very diplomatic yeah, kind of a windoze boy n therefore not really up on linux.
i did root with 3.21 and i tried the chmod command with all the spaces and terminal just gave me 'bad mode' (it also gave me bad mode when i tried adb) so i tried as i posted. bummer but nevermind, come on alpharev 2

71baker said:
Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
You can enable AUFS in Jacob's latest kernel by typing "aufs --enable" in a terminal emulator app in android, and then reboot the phone.

[Help] ADB for the Epic

Ok. I had the android sdk installed before and was able to easily "adb shell" "su"
but a few months ago my phone stopped being recognized by the pc (stock cable) so i uninstalled it since i couldnt use adb nor odin (i thought it was my phone though)
but now i got a BB cable and the drivers all installed wonderfully and there was no headaches so now i believe the hype with getting a new usb cable because the stock one sucks.
So i followed the "Setting up Android SDK for beginners" by bthomas and i ollowed it to a t because i couldnt remember how to set up the sdk, and after setting it up, when i type in adb shell, it gives me a "~#" (which never happened before) and then when i type "su" it gives me a "sh-3.2#"
Im not sure what couldve went wrong except for the fact that before i would install everything (1.5sdk, 1.6, etc.etc) because i didnt know any better, but the guide showed me that all we needed to get adb to wrok was the platform tools one, but its not working.
I need advice because i dont wanna mess up anything in my phone since ive never seen those prompts
TL;DR
ADB gives me a "~#" when i adb shell, and i dont know why
Also, im running urban regeneration with genocide 2.0

The '~' means you are in your home directory. The '#' means you already have root so the 'su' command is not necessary. Sounds like your rom has a non-stock shell installed and is kernel rooted?

machx0r said:
The '~' means you are in your home directory. The '#' means you already have root so the 'su' command is not necessary. Sounds like your rom has a non-stock shell installed and is kernel rooted?
Click to expand...
Click to collapse
but i cd to the sdk directory (Cd:/ android/sdk/platform-tools) so idk why it would think im still in the home directory (that would be cd: users/etc, right?)
and yes the kerna is rooted. its Genocide v2.0 and im undervolted.
im also ext4 if that makes a difference...as for the rom idk its Urban Regeneration
im such a noob now i never had problems before i was forced to stop using my phone with my pc

A_Flying_Fox said:
but i cd to the sdk directory (Cd:/ android/sdk/platform-tools) so idk why it would think im still in the home directory (that would be cd: users/etc, right?)
and yes the kerna is rooted. its Genocide v2.0 and im undervolted.
im also ext4 if that makes a difference...as for the rom idk its Urban Regeneration
im such a noob now i never had problems before i was forced to stop using my phone with my pc
Click to expand...
Click to collapse
After you 'adb shell' it's showing you the filesystem on the phone, not your computer. I assume the the cd platform-tools command you are mentioning is what you are doing in a Windows command prompt to get to where your adb.exe is located.
Edit: Do this, it's safe, 'pwd' shows your current directory (in Linux/Android)
adb shell
pwd
cd /
pwd
Chances are it will show your home directory and then /
http://en.wikipedia.org/wiki/Pwd

machx0r said:
After you 'adb shell' it's showing you the filesystem on the phone, not your computer. I assume the the cd platform-tools command you are mentioning is what you are doing in a Windows command prompt to get to where your adb.exe is located.
Edit: Do this, it's safe, 'pwd' shows your current directory (in Linux/Android)
adb shell
pwd
cd /
pwd
Chances are it will show your home directory and then /
http://en.wikipedia.org/wiki/Pwd
Click to expand...
Click to collapse
yeah adb.exe is in platformtools
but anyways, this is what happened
adb shell
~# pwd
pwd
~ # cd /
cd /
~ # pwd
pwd
/
and then i exited lol
could it be a problem with my computer? like the place i saved it or something?

A_Flying_Fox said:
could it be a problem with my computer? like the place i saved it or something?
Click to expand...
Click to collapse
I don't think you have a problem it's just different than what you remember. Probably because of a difference in your mod. The prompt itself can be modified with environment variables (it's the PS# variables, you can look with 'set') so I wouldn't worry about that. My pwd output on stock looked very similar to what you pasted.
My PS# variables on stock:
# set
set
.
.
.
PS1='# '
PS2='> '
PS4='+ '

machx0r said:
I don't think you have a problem it's just different than what you remember. Probably because of a difference in your mod. The prompt itself can be modified with environment variables (it's the PS# variables, you can look with 'set') so I wouldn't worry about that. My pwd output on stock looked very similar to what you pasted.
My PS# variables on stock:
# set
set
.
.
.
PS1='# '
PS2='> '
PS4='+ '
Click to expand...
Click to collapse
i typed that in and i got a whole list of things and under them PS1='\w \$ '
PS2='> '
PS4='+ '
PWD=' '
TMPDIR= '/data/local/tmp
how would i get it back to #? Im willing to go back to stock odin if i have to, but im getting more intrigued by this as you help...

A_Flying_Fox said:
i typed that in and i got a whole list of things and under them PS1='\w \$ '
PS2='> '
PS4='+ '
PWD=' '
TMPDIR= '/data/local/tmp
how would i get it back to #? Im willing to go back to stock odin if i have to, but im getting more intrigued by this as you help...
Click to expand...
Click to collapse
Ok so you can see how your PS1 environment variable is different than mine. Depending on the shell you are using it might support escape characters such as \w which should display the current directory and \$ which should show # if you are root or $ if not. Here's some non-Android specific info on the subject http://www.cyberciti.biz/tips/howto-linux-unix-bash-shell-setup-prompt.html (stop at the colors part, no clue about which if any character are supported in the stock android shell, just using to give the basic idea)
To temporarily change the command prompt you could do:
PS1="# "
But most likely your shell has a settings file that sets the default prompt when you login. Unfortunately I do not know where this is located. Going back to stock would certainly undo any custom shells or settings your current rom has set if you don't like it.

i think that directory might be sbin/sh. because it calls to it whenever i enter something like ADB REBOOT it says sbin/sh.: adb not found
but when i type in adb shell
and then reboot recovery, etc it works
i dont think i need to go to stock, i just need to not type certain things before commands i guess...
but thanks alot! youve enlightened me quite a bit hahah i wish i had more thanks to give

get the inode of a file

i'm new here so first of all hello to everyone.
heres my problem. hopefully somebody can help me.
how can i get an inode of a file. that meens to read a
particular part in the data partition. of course that
could only be possible with su, thats clear.

You've got to use the command line for every root thing.
You can get the inode as described here: http://www.cyberciti.biz/faq/howto-print-inode-data-structure/
How to use root commands: http://forum.xda-developers.com/showthread.php?t=2226664

nikwen said:
You've got to use the command line for every root thing.
You can get the inode as described here: http://www.cyberciti.biz/faq/howto-print-inode-data-structure/
How to use root commands: http://forum.xda-developers.com/showthread.php?t=2226664
Click to expand...
Click to collapse
thanks for the quick response.

i find out that ls has no option -i on android to show inodes.
does anybody know another way to get them

xiyuo said:
i find out that ls has no option -i on android to show inodes.
does anybody know another way to get them
Click to expand...
Click to collapse
Compile or use a version of busybox which has it and use that one. Add it to your apps assets and copy it to the data directory of your app. Then use that binary for the ls command.
That part is very difficult on Android. On one device you have got the ls command but the output might look completely different on another phone. (Some time ago someone reported that he noticed "ls" being linked to "ls -l" on one phone. On another phone the option "-l" might be missing.
So it is recommended to use busybox for every root command.

..

nikwen said:
Compile or use a version of busybox which has it and use that one. Add it to your apps assets and copy it to the data directory of your app. Then use that binary for the ls command.
So it is recommended to use busybox for every root command.
Click to expand...
Click to collapse
i did that.
but with
./busybox ls -i
i get
cant execute permission denied.
even if i use su. how could that be?
does anybody know how i get the permission?

xiyuo said:
i did that.
but with
./busybox ls -i
i get
cant execute permission denied.
even if i use su. how could that be?
does anybody know how i get the permission?
Click to expand...
Click to collapse
In Linux you have to add the right to execute it first:
Code:
su
chmod 775 <filename>

Root attempt #1, anyone want to try it..

Can someone post a current kernel version screenshot off of their phone please..
Update: (11/08/2014)
Instructions:
Grab file at --> https://drive.google.com/file/d/0B31X8bH_5Gl-NmExWmhlbzJ5T3c/view?usp=sharing
adb push root /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 root
./root
If you get # symbol for prompt, you have root.
Let me know the results please.. I am trying to do this without actually having a phone, I might as well go get one today though, because this might end up being to painful this way..
Update (11/15/2014):
Well, at this point I have been able to establish a remote shell to my PC. This might not sound like much, but if your on the phone and run my binary it will establish a remote shell to anywhere that you specify where a valid listener is listening on an IP and port that is specified. Malware people would go nuts with this. Why? Because with this essentially I could grab all personal information from your SDcard and other areas without your permission. Pretty much run any command that you can do now locally, I could do on your phone remotely. So, I am seeing now what leverage points I might be able to make with this..

Gl

AngelsPunishment said:
Gl
Click to expand...
Click to collapse
Ohhh. yummy....

Is this root already available??
SM-N910V
http://download.chainfire.eu/590/CF-Root/CF-Auto-Root/CF-Auto-Root-trltevzw-trltevzw-smn910v.zip
Am I missing something or has chainfire already accomplished this.. ?

gatesjunior said:
SM-N910V
http://download.chainfire.eu/590/CF-Root/CF-Auto-Root/CF-Auto-Root-trltevzw-trltevzw-smn910v.zip
Am I missing something or has chainfire already accomplished this.. ?
Click to expand...
Click to collapse
I thought that was for the DE (Developer Edition).

Nooter said:
I thought that was for the DE (Developer Edition).
Click to expand...
Click to collapse
I don't think so. Look at your model, the developer edition I believe would be a different model..
Well, hold on, maybe.. It might have an identical model number. That would be strange...

gatesjunior said:
I don't think so. Look at your model, the developer edition I believe would be a different model..
Well, hold on, maybe.. It might have an identical model number. That would be strange...
Click to expand...
Click to collapse
It's for the Dev edition. It was listed as the retail version model number but it is indeed for the dev version.

Someone want to try this
Instructions:
Grab file at --> https://drive.google.com/file/d/0B31X8bH_5Gl-NmExWmhlbzJ5T3c/view?usp=sharing
adb push root /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 root
./root
Let me know the results please..

Can you tell us how this method achieves root?

ronaldheld said:
Can you tell us how this method achieves root?
Click to expand...
Click to collapse
Well, it is essentially overflowing to try and gain root, it will not in any way cause any permanent change to your phone or flag anything.

gatesjunior said:
Instructions:
Grab file at --> https://drive.google.com/file/d/0B31X8bH_5Gl-NmExWmhlbzJ5T3c/view?usp=sharing
adb push root /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 root
./root
Let me know the results please..
Click to expand...
Click to collapse
did you fo this? what did it achieve?

mrnick81 said:
did you fo this? what did it achieve?
Click to expand...
Click to collapse
No, I do not have the phone yet.. Probably go out tonight and get it. But I wanted to start work and get things moving..

Thank you for the attempt!

Has anyone tried it yet? If not I am will give it a whirl.

Chuckleb0ne said:
Has anyone tried it yet? If not I am will give it a whirl.
Click to expand...
Click to collapse
exactly, not going to adb an unproven method

I'll give it a try in a second.
---------- Post added at 03:52 PM ---------- Previous post was at 03:37 PM ----------
Where do i place the root file on my computer? It stops me at (cannot stat root, No such file or directory).
I have a windows computer with adb installed and everything.

gatesjunior said:
No, I do not have the phone yet.. Probably go out tonight and get it. But I wanted to start work and get things moving..
Click to expand...
Click to collapse
Ok, so here is the results.

NM. same results as above.

mrlaigle said:
NM. same results as above.
Click to expand...
Click to collapse
O.k. guys, well that was shot one with no phone. Now I have phone in hand All mine, precious...

Let me know if you need restore tar.