I am not really a deveoper and not really that good with Linux or Android terminal commands, but I can do them when I need to. There are so many android apps that I rarely use terminal commands. Gear 2 on the other hand has recovery modes or custom ROMs that I am aware of. It uses the propritary app "Gear Manger", doesn't offer a whole lot of choices in customization. I am wondering what are the most minimal developer's tools that I would need enter Tizen commands to the kernel. I am hoping its possible to just use a terminal window on Ubuntu 12.4 perform it OTA. is it possible to use the terminal window to enter Tizen commands to my Samsung Gear2?
Related
Hi folks,
I have a few question here.
1) I love to have a look inside Android internals (lets say v2.3).
For eg, I may want to change the way lock screen looks or works.
or change the way menu works/see (icons).
As of now, i dont have an android phone. I love to test that in an emulator.
How can i do that?
2) I have an apk file. How will work/run that in an emulator?
Thanks a lot.
There are instructions for the Android emulator here:
http://www.androidguys.com/2010/12/15/android-emulator/
Once that's running, you should just need to open a cmd prompt, and type
adb install nameofmy.apk
(if you get an 'adb' is not a recognised command, you'll need to CD to the 'platform-tools' folder from the sdk first)
Hi,
I have a Samsung Galaxy Note 2 with Android 4.3 (XXUEMJ9) rooted using Dr Ketan Multitool software. I have tried to use terminal emulators but they won' t open in window. The program launches, I briefly see the keyboard and the top status bar indicates Terminal session is running. In the task list, I have a Terminal session but I cannot use the terminal. I have this behaviour with Android Terminal Emulator and JS_Terminal. Privilege Terminal emulator shows up but I cannot type anything in it (It is written In mgmain JNI_OnLoad). I installed Bash X which gets root access but when I click to launch a shell I have the same behaviour than for JS_Terminal and Android Terminal Emulator. I use SuperSU to grant root access to applications. It seems something is wrong in my installation. What would you recommend ?
Best regards,
JF
I downloaded nexmon from the play store and I can't seem to enable monitor mode, I have the utils and framework installed. I'm using dirty unicorns ROM with Kali on top. I have been looking all over on how to use it. The github says to use adb shell and then enter a command but I'm trying to do mobile pen testing and don't want to be tangled to a PC. Can anyone tell me how its done ?
Have you tried using terminal emulator to run the commands?
wangdaning said:
Have you tried using terminal emulator to run the commands?
Click to expand...
Click to collapse
The correct command is nexutil -m1 right ? I tried both the kali terminal and the android terminal.
Hopefully someone else can come give some advice, I have no clue as I have never ran that set up. I was just thinking the only way to get adb commands without a pc is to use terminal emulator app.
Anyone ?
I too need help with this. From the reading I've done nexmon is supposed to work as a standalone for things like airodump-ng but it doesn't exactly define handshakes and what is happening. It uses the terms becons and frame, I don't understand how these translate and would prefer to enable monitoring on the CMD in Kali.
It seems the problem is that nexmon stores the files in Android bins and Kali CMD doesn't see these as it is a separate machine. How do you merge the files so Kali can recognize that nexmon has a way to monitor the wlan0.
Furthermore how do you get Kali CMD to kill the P2P0 network, it seems as though this might cause a problem once you get it to monitor and try to run airo commands
Personally, after Windows 8, followed by Windows 10, I started to seriously look into Linux (which is free) as my primary desktop. Today LibreOffice (which is free) has more features than Microsoft Office and can open, edit, and save all of Microsoft Office's documents. Thanks to Steam's new deployment, I can even now run my Windows-only games on Linux too. The one thing I found very hard to swallow was trying to get my Andriod device (which is technically Unix too) to actually connect to my computer and I imagine that is because the documentation (even via a Google search) to using ADB or Fast Boot with Linux seems to be hidden among pages upon pages of Windows users.
For simple ease of reference as I couldn't even find this here on XDA, allow me to correct the matter.
Type out (or copy and paste) the following commands to install ADB and Fastboot.
Code:
sudo apt-get install adb
sudo apt-get install fastboot
Now you have both adb and fastboot installed. Next, you'll need to enable adb.
Code:
sudo adb
Now boot your phone to your bootloader screen (you get there by pressing both your power and lower volume keys at the same time). Once there load TWRP with the following command.
Code:
sudo fastboot boot '/your_path_here/twrp-3.2.3-0-payton.img'
Your path will be wherever you happen to have downloaded your copy of TWRP. From there I was able to successfully mount my device within TWRP and upload my ROM zip file as needed.
You will upload files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push lineage-16.0-20180921-UNOFFICIAL-payton.zip /sdcard/
I hope this was helpful.
Note: Because you're doing this in Linux, the files you upload to your phone may not have the correct permission settings (chmod settings) after they are uploaded. This is very unlikely, but still technically possible.
Thankfully, the folks at TWRP have thought of this and in the 'Advanced' menu, you will find a file manager. From there select the file of your choice and click the chmod button that reads "chmod 0777". Don't forget to mount the DATA partition (before using the file manager) else you may not see the file you are looking for.
or just download the package from here
https://developer.android.com/studio/releases/platform-tools
unzip and have fun
munchy_cool said:
or just download the package from here
https://developer.android.com/studio/releases/platform-tools
unzip and have fun
Click to expand...
Click to collapse
This is helpful, but most newbies to Linux wouldn't even know how to execute those base files. lol But Windows users coming to Linux do know how to run command prompts (good old Microsoft kept the command prompt around long enough that folks moving to Linux just associate the terminal in the same light). Which is why I thought to have them install a preconfigured program would be easier.
But thanks for the source. It is still useful.
MotoX4 said:
This is helpful, but most newbies to Linux wouldn't even know how to execute those base files. lol But Windows users coming to Linux do know how to run command prompts (good old Microsoft kept the command prompt around long enough that folks moving to Linux just associate the terminal in the same light). Which is why I thought to have them install a preconfigured program would be easier.
But thanks for the source. It is still useful.
Click to expand...
Click to collapse
lol..i thought the first thing a Linux newbie would learn is command prompt.
you need to read about terminal before you decide using a Linux box.
munchy_cool said:
lol.. I thought the first thing a Linux newbie would learn is the command prompt.
you need to read about terminal before you decide using a Linux box.
Click to expand...
Click to collapse
:laugh: I agree. But there are a lot of folks who feel intimidated whenever learning something new. If I had started this thread with a full introduction to manually configuring and executing everything, most folks would have easily been discouraged. Especially the younger or older generations who fall somewhere between the line of "I don't got time for that" or "why so difficult". lol :laugh: Inoculating folks into using Linux I feel works best. Keep it simple and suggest that there are more in-depth ways of doing things to peak curiosity. -- Which is why I'm glad you pointed that out and why I'm loving writing this reply at the moment. :angel:
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