the terminal was working fine i install kali linux then use the terminal to install wireshark used it to addit user permition worked fine the wireshark ,after a day tryed to install another orogram got the error cant open the terminal.any more sugestion it seams the only way to get root acses to install programes
Related
Hello ther
I am running ubuntu on my transofrmer quiet a time for now , having lxde deksktop installe
now i tried to install lazarus on my linux distro , i tried terminal installation, synaptic package manager method , and i tried to compile it mysel
after installation a quick unreadable error flashes up when starting lazarus , and then it terminates
self compiling quits ith error 2 ,
can anyone help me to get lazarus running ??
As with any linux software..
1. start it from the console, you may have more output
2. check if you can start with --debug or some other options for more output
3. check software logs and messages
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 tried to install kali linux through linux deploy. everything was right when i started the download but after the download is finished and i reconfigure than all things fail like l (dns...fail,mtab....fail,motd....fail,hosts...fail,hostname...fail,timezone..fail,su...fail,chroot:cant execute apt_get no such file
sudo....fail,groups...fail and etc than when i start vnc viewer it shows some error what should i do please help
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
For a while I had to keep running ADB commands from my Windows desktop because I couldn't get the USB authorization prompt to pop up on my Linux laptop running Ubuntu 18.04.
I noticed OnePlus included .exe files for Windows and I saw a .sh Linux/OSX file which I know is a script file.
Couldn't do anything with sudo which I though was odd. Opened the directory where the script is with my device connected, entered root user with "su"
Ran the script as su rather than just sudo
AND IT WORKED now I'm authorized with my Linux laptop and can resume under regular user. That was a weird problem.
That was a frustrating problem that had such a simple solution. Must not have had sudo access to adb.
Just sharing what worked for me! Linux > Windows for terminal use and adb stuff