Related
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
So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?
bretjrodgers said:
So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?
Click to expand...
Click to collapse
When you do "Adb shell" > "su" you have to allow it on your phone. A little popup will appear.
If you can su in a terminal on the phone itself then you can be certain you have root.
Are you sure there is not a prompt on the phone when you are attempting su from ADB? It might be asking for su permissions but timing out and showing denied.
bretjrodgers said:
So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?
Click to expand...
Click to collapse
So after installing SU Terminal & Root Explorer from Android Market, when I did the following :
C:/>adb shell
$ su
su
#
I have verified that SuperUser permissions through ADB are obviously working. However when I do the following command...
C:/>adb root
adbd cannot run as root in production builds
...is displayed. It seems as though, yes, I do have SuperUser access, I don't have root access through ADB and Android Commander still does not recognize root. Is this because I am running the stock ROM, and if so, is there a general thread with all available/recommended Vibrant ROMs to install?
bretjrodgers said:
So after installing SU Terminal & Root Explorer from Android C:/>adb root
adbd cannot run as root in production builds
...is displayed. It seems as though, yes, I do have SuperUser access, I don't have root access through ADB and Android Commander still does not recognize root. Is this because I am running the stock ROM, and if so, is there a general thread with all available/recommended Vibrant ROMs to install?
Click to expand...
Click to collapse
Just to clarify, you realize adb root has nothing to do with your phone?
adb root restarts the adb daemon on the computer you are on as root (something I usually don't recommend).
When you start Android Commander make sure it has permissions on your phone when it makes the request.
d01100100 said:
Just to clarify, you realize adb root has nothing to do with your phone?
adb root restarts the adb daemon on the computer you are on as root (something I usually don't recommend).
When you start Android Commander make sure it has permissions on your phone when it makes the request.
Click to expand...
Click to collapse
Ok so I now understand the purpose of the adb root command after some additional research. I guess the issue is that when I run Android Commander, even though it does detect my device on the PC, it does not ask for/request SU permissions on my device
The FAQ thread for Android Commander:
http://forum.xda-developers.com/showthread.php?t=628138
** If you using Win7/Vista run Program as Administrator or disable UAC, otherwise this function will fail!
Click to expand...
Click to collapse
Guess I never needed for something like this since I'm comfortable with the command line.
d01100100 said:
The FAQ thread for Android Commander:
http://forum.xda-developers.com/showthread.php?t=628138
Guess I never needed for something like this since I'm comfortable with the command line.
Click to expand...
Click to collapse
I am running the program with both UAC disabled, and running as administrator and still the program does not recognize as root. I am only worried not just about Android Commander, but the possibility for functionality of other programs that require root as well.
Type adb shell
You'll see '$' as your prompt, type 'su'
$ su
You'll see '#' as your prompt, type 'id'
# id
uid=0(root) gid=0(root)
That means you have root.
Further proof you can remount /system from ro to rw.
You have root, Android Commander isn't the standard to judge whether your root is working correctly. Just a cursory glance at the app thread, it requires quite a bit of finesse to get working and it's touchy about which rom you're using. If yours doesn't work and you've actually followed the directions, send the developer your logs in the proper thread.
Why not just download the app Terminal Emulator and just type "su".... you'll either get the # or Permission Denied.
Based off everything you said, yes, you have root... ^ easiest way to test though. No need to deal with adb.
I'm trying to follow this thread (http://forum.xda-developers.com/showthread.php?t=2515141) to get IR working on my MIUI 5.5.8 ROM. I have root permissions (SuperSU) and I have adb shell granted root permissions on SuperSU.
I'm trying to run this part:
adb root
adb shell "mkdir -p /data/local/userinit.d"
But that's what I get:
C:\Users\Leandro\Downloads\platform-tools>adb devices
List of devices attached
06902d4f16cf0d35 device
C:\Users\Leandro\Downloads\platform-tools>adb root
restarting adbd as root
C:\Users\Leandro\Downloads\platform-tools>adb shell "mkdir -p /data/local/userin
it.d
mkdir failed for /data/local/userinit.d/, Permission denied
What could I do to solve this?
Thank you.
Have you tried it like this
adb devices
adb shell
su
mkdir -p /data/local/userinit.d
Art Vanderlay said:
Have you tried it like this
adb devices
adb shell
su
mkdir -p /data/local/userinit.d
Click to expand...
Click to collapse
I'm trying to push TWRP and Loki flash tool via ADB but I'm getting permission denied. Do you know what I can to gain access?
It says root access when in download mode but I don't have root while OS is running. Does this mean my phone is semi rooted? What should I do now?
y300owner said:
I'm trying to push TWRP and Loki flash tool via ADB but I'm getting permission denied. Do you know what I can to gain access?
It says root access when in download mode but I don't have root while OS is running. Does this mean my phone is semi rooted? What should I do now?
Click to expand...
Click to collapse
What android version are you on?
Art Vanderlay said:
What android version are you on?
Click to expand...
Click to collapse
Was on Stock Verizon VS980_27A 4.4.2. Tried many ways. Didn't work. Stumproot.apk fixed the problem.
If anyone is on the stock ROM not rooted, use this command (on PC) and tell me the output (it is for the fingerprint).
Code:
adb shell getprop ro.build.fingerprint
I can't right now since I am on a custom ROM and my ctsProfile is always false.
_Masked_ said:
If anyone is on the stock ROM not rooted, use this command (on PC) and tell me the output (it is for the fingerprint).
Code:
adb shell getprop ro.build.fingerprint
I can't right now since I am on a custom ROM and my ctsProfile is always false.
Click to expand...
Click to collapse
This what you are looking for?
OnePlus/OnePlus6TSingle/OnePlus6TSingle:9/PKQ1.180716.001/1812281442:user/release-keys
Jeffro64 said:
This what you are looking for?
OnePlus/OnePlus6TSingle/OnePlus6TSingle:9/PKQ1.180716.001/1812281442:user/release-keys
Click to expand...
Click to collapse
Yes, thanks.
EDIT: Finally got to 69 posts.
_Masked_ said:
Yes, thanks.
EDIT: Finally got to 69 posts.
Click to expand...
Click to collapse
No problem...Hope it helps.
Gratz on the 69 LOL.
You can type the getprop commend in terminal emulator directly in your phone, no need to have a computer
And being rooted doesn't change the fingerprint which is related to cryptography and disk image
Recently my phone got back from warranty with a retail board (don't know if it's relevant), so I had to do all the unlocking and rooting things. but all the times that I changed custom roms my phone only booted if I went to bootloader and pressed start, any other way it boots directly into rcovery mode.
actualy using Ressurection Remix (Pie) no root.
redejcr said:
Recently my phone got back from warranty with a retail board (don't know if it's relevant), so I had to do all the unlocking and rooting things. but all the times that I changed custom roms my phone only booted if I went to bootloader and pressed start, any other way it boots directly into rcovery mode.
actualy using Ressurection Remix (Pie) no root.
Click to expand...
Click to collapse
In ADB shell type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
[email protected] said:
In ADB shell type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Click to expand...
Click to collapse
Only shows permission denied even if adb interface was authorized.
redejcr said:
Only shows permission denied even if adb interface was authorized.
Click to expand...
Click to collapse
You can root it, and get permission, or.... add "sudo", or "su" command to beginning of command shell. Haven't done it without root, but that should get you root permission for bash shell. Something like this
Code:
adb shell su -c "your command here"
[email protected] said:
You can root it, and get permission, or.... add "sudo", or "su" command to beginning of command shell. Haven't done it without root, but that should get you root permission for bash shell. Something like this
Code:
adb shell su -c "your command here"
Click to expand...
Click to collapse
Yeap, that worked, thanks a lot. You saved me from this headache.
The only diference is that I had to root AND add su to the command.