Hi,
I have enabled root access to my phone and installed "Android Terminal Emulator". But "dig" and "nslookup" commands are not working.
Can you please guide me to how I can make DNS commands running via my smartphone.
thank you.
taqi
Related
Hi,
I have install bash in my Android phone. I am trying to send the command history to a file. At the file is successfully written any command that I send from both terminal applications that I have in the phone. Also is successfully written any command that I send from my PC using the adb.
But, I am not here to present you my success!
Although, as I said, I successfully send all commands from terminal, I cannot send any commands that any application is using. I have developed an application to test the commands. Although I get root access and successfully run the commands, these commands are not sent to the history file!
Does anyone has any idea about how to solve this problem?
This was answered a little bit in the S-Off thread and I would like to post it for everyone that has the PJ8310000 device and they are running into device "offline" when using adb devices. This is for Windows 8 only. I had the same problem in OSX, but I believe the solution is the same. I cannot post in the thread in the developer section yet, that is why this is here.
First, if you can't see your device in your device manager, make sure you have the latest HTC Device drivers installed or install the latest version of HTC Sync. This is very important for Windows 8.
Second, you will need to download and install the latest Android SDK. Just "Download From Other Platforms" and choose the appropriate SDK installation. You will need to run the SDK Manager.exe to install the latest tools. Note: ADB and Fastboot have been moved from the "tools" folder to "platform-tools".
Make sure your phone is in debugging mode by going into the Developer Options and choosing "Android debugging."
Find your SDK installation and make sure you are under "platform-tools" folder. You can ctrl-shift-right click on that folder to open a command prompt at that folder location. Saves you time.
Type in the command prompt:
Code:
adb devices
Your device should be listed and probably says Offline. This is normal. Take a look at your phone, you should get a prompt on your phone asking you if you trust the device that is trying to connect to it (this should be your computer). Allow it.
Type in the command prompt:
Code:
adb devices
This time, your device should be listed with the word "device" instead of offline.
To restart the daemon, type the following separately:
Code:
adb kill-server
adb start-server
This is the best I can do for everyone and it solved my problems with no further issues. I am not an expert and this is the only solution that has worked for me.
Thanks, this worked for me.
I did this in Windows 7 SP1 no problem. All I had to so was get the latest Android SDK and replace all the adb/fastboot files I already had and it worked no problems.
If you get permission denied when doing the last "adb shell" command, get adbd insecure from the forums here and run debugging mode insecurely from there.
Sent from my One X using xda app-developers app
Desertman123 said:
If you get permission denied when doing the last "adb shell" command, get adbd insecure from the forums here and run debugging mode insecurely from there.
Click to expand...
Click to collapse
I had this problem because SU was only allowing apps in CM10.1 (4.2.1). I found the solution by enabling the Dev Options via multiple clicks on the Build number until dev options was enabled, then changed Root access to Apps adn ADB.
FYI for anyone else that gets lost like I was.
ok so i can s-off now?
yes get some, 9 steps to s0ff
Ponarona said:
ok so i can s-off now?
Click to expand...
Click to collapse
Yes, you can use the HTC One XL link in the S-Off thread with no issues. I made this to help people with Win8 and trying to get their phones to appear properly in their device manager and to list it under adb devices.
If you get device offline, my issue, I was running android 4.2.2 but had an outdated adb. Just update adb if you still have problems
I know this is exceedingly random, but if you run a mac and can't see your device in adb, and in the past you tried sharing your phone internet with your mac via usb try running this:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
./adb kill-server
I need to do that before every adb session.
I'd be amazed someone actually has those conditions, but hey, it might help someone.
Sent from my HTC One X using xda app-developers app
Hi.
I'm trying to control the access to ADB on Android 4.1.1. I already have root access to the device and now I'm trying to execute some access control code at the start of an ADB connection.
Are there any scripts that are executed with the "adb shell" access?
Thank you!
I have seen discussions online such as this:
https://stackoverflow.com/questions/12634280/what-is-a-adb-daemon
If I understand the answers give there correctly, whenever I use an adb command on my computer connected to a smartphone, the reason it does anything is because there is a background process adbd, the adb daemon, running on the smartphone. Everything I see on the computer screen when I issue an adb command is the result returned by the adbd daemon.
a) Is this correct? Is this how adb is supposed to work?
b) If it is correct, is there any way to programmatically enable/disable/re-enable the adbd process? Can I programmatically interact with adbd at all (either through Java or NDK)? Can I use adbd from the android phone itself and perform actions performed using adb, without using a computer?
I am hoping to do this on a non rooted device, but if not, any kind of device will do.
mahaju said:
I have seen discussions online such as this:
https://stackoverflow.com/questions/12634280/what-is-a-adb-daemon
If I understand the answers give there correctly, whenever I use an adb command on my computer connected to a smartphone, the reason it does anything is because there is a background process adbd, the adb daemon, running on the smartphone. Everything I see on the computer screen when I issue an adb command is the result returned by the adbd daemon.
a) Is this correct? Is this how adb is supposed to work?
b) If it is correct, is there any way to programmatically enable/disable/re-enable the adbd process? Can I programmatically interact with adbd at all (either through Java or NDK)? Can I use adbd from the android phone itself and perform actions performed using adb, without using a computer?
I am hoping to do this on a non rooted device, but if not, any kind of device will do.
Click to expand...
Click to collapse
Yes, but it requires having a rooted device and the terminal emulator app. Or you can install TWRP and use the terminal emulator that is built into TWRP.
Sent from my SM-S767VL using Tapatalk
reply to answer
Droidriven said:
Yes, but it requires having a rooted device and the terminal emulator app. Or you can install TWRP and use the terminal emulator that is built into TWRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I have an old rooted samsung phone with android 4.2.2
Is there any sample code on how I can interact with the adbd daemon? In the terminal emulator if I type "adb shell" it says starting daemon but then it says device not found. how would I do some basic stuff (like take a screen shot using "adb shell screencap" for example? Can I interact with it programmatically from java or ndk?
mahaju said:
I have an old rooted samsung phone with android 4.2.2
Is there any sample code on how I can interact with the adbd daemon? In the terminal emulator if I type "adb shell" it says starting daemon but then it says device not found. how would I do some basic stuff (like take a screen shot using "adb shell screencap" for example? Can I interact with it programmatically from java or ndk?
Click to expand...
Click to collapse
When using terminal emulator, it uses the same commands as adb shell(not the standard adb), but you remove "adb shell" from the commands. For example, in terminal emulator, it is:
reboot recovery
Instead of:
adb reboot recovery
Or
adb shell reboot recovery
Also, before running your commands in terminal emulator, you need to use the su command by typing:
su (then press enter, grant the app superuser/root permissions)
Then you can run the rest of your commands.
Sent from my SM-S767VL using Tapatalk
For some reason ADB Shell is not working, is there a work around for it? If so what is the command prompts? I'm trying to root and push to a device...
Is Bash a option if so where do I start??
Help a beginner hacker please
USB Debugging isn't properly set up on mentioned Android device, especially the RSA-keys what are necessary to pair PC and Android device didn't get created and stored.