-
Notifications
You must be signed in to change notification settings - Fork 678
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Root access #342
Comments
Same problem here too. plz fix thanks |
Same here Galaxy s3 android 4.3 |
See #224 |
I already readed that issue. Problem is that my phone doesn't have neither SELinux Activated or Samsung Knox... |
I found the solution to the sudo problem. You need to enable root login through ssh and then you will be able to ssh in as root and wont have any weird permission problems. Follow crazy's instructions from above: -->Start your linux after install and open Terminal Emulator then type: install nano if necessary with apt-get install nano ------------start of guide for ssh changes----------- Enable root login over SSH: Add a line in the Authentication section of the file that says PermitRootLogin yes. This line may already exist and be commented out with a "#". In this case, remove the "#" Authentication: #LoginGraceTime 2m Save the updated /etc/ssh/sshd_config file. NOTE: I NOTICED THAT ON ANDROID LINUX THE RESTART SERVICE SSHD COMMAND DOES NOT WORK. JUST STOP LINUX IN LINUX DEPLOY APP AND RESTART INSTEAD. NOW I AM SSHed FROM WINDOWS 10 INTO MY OLD NOTE 3. THINKING ABOUT ADDING IT TO A BEOWULF CLUSTER. XD !!! guide for adding root to ssh credit: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/V2V_Guide/Preperation_Before_the_P2V_Migration-Enable_Root_Login_over_SSH.html |
Hello. Meefik, could You help me?
I've installed Linux Deploy, I did all good, Kali Linux is working, everything is perfect. But when in the Terminal i write:
sudo apt-apk update
I have access denied. I've SuperSU, Linux Deploy have it, and nothing...
What i do bad? Please help me.
The text was updated successfully, but these errors were encountered: