Hi
i try to build from vanila rootbox source,
and when i entered the following line:
Code:
~$ repo init -u git://github.com/Root-Box/platform_manifest.git -b jb-mr1
terminal:
Code:
No command 'repo' found, did you mean:
Command 'rep' from package 'rep' (universe)
Command 'repl' from package 'nmh' (universe)
Command 'repl' from package 'mailutils-mh' (universe)
repo: command not found
repo
OK, problem sloved...
but i get this eror:
Code:
curl: (22) The requested URL returned error: 404
If you need to flash ROM even using fastboot for Smartphone or Tablet in which they use Android OS! Then Ubuntu OS is needed!
This is a guide I made for ubuntu users and included a guide for windows users to setup Android SDK which contains ADB.
Android Debug Bridge (ADB) provides a terminal interface on your PC to interact with your device's file system. This can be useful for many things like installing & uninstalling apps, logcat, backup & restore, and hacking your device just to name a few.
ubuntu 12.04 & 12.10 Guide
1. Go here and download android-sdk (not the adt-bundle)....
https://hotfile.com/dl/241406263/5e6a306/android-sdk_r22.0.5-linux.tgz.html
2. Place the downloaded file in your home folder and then extract it and you should get a folder named android-sdk-linux (do not rename it).
3. If you’re on a 64bit machine run these commands in terminal to make sdk compatible with 64bit (if you’re on 32bit machine then skip this step)....
sudo apt-get update
sudo apt-get install ia32-libs-multiarch
4. Run this command in terminal to install jdk if you don’t have it already....
sudo apt-get install openjdk-6-jdk
5. Navigate to the home folder where you extracted android-sdk-linux and open the folder then open the folder named tools
6. Inside the tools folder there will be a file named android... double click it and select run then android sdk manager will open.
7. In the center pane deselect everything... Now only select the following....
Android SDK Tools
Android SDK Platform-tools
Android Support Library
8. Once selections have been made click on install packages and wait till finished.
9. Upon completion of step 8 in terminal run this command....
sudo gedit ~/.bashrc
When the file opens, go to the very bottom and copy/paste the following 3 lines (make sure they’re each on separate lines)....
# Android tools
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
10. Now reboot your computer.
11. Set your phone to usb debugging then plug it to your pc after pc is done booting
12. Open a terminal on your pc and enter....
adb devices
If all went well, you should see your phone’s serial number and you’ll be ready to go.
~~~~~Important~~~~~
You can use steps 5 & 6 to open Android SDK Manager & update your ADB/SDK installation. Only select your installed packages then update.
Also if you only need the fastboot/adbtools:
sudo add-apt-repository -y ppa: phablet-team/tools
Note: delete the space after"-y ppa:" -xda creates smileys like ppa
sudo apt-get update
sudo apt-get install -y phablet-tools
Sent from my Nexus 4 using xda app-developers app
Thank...
gazhead said:
Also if you only need the fastboot/adbtools:
sudo add-apt-repository -y ppa: phablet-team/tools
Note: delete the space after"-y ppa:" -xda creates smileys like ppa
sudo apt-get update
sudo apt-get install -y phablet-tools
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks man! It's also good way!
Followed this guide (thank you for posting) but couldn't connect. Scratched around and found I needed to create a new file in /etc/udev/rules.d with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="<4-char_verndorID>", ATTR{idProduct}=="4-char_productID", MODE="0666", OWNER="username"
Followed by:
Code:
sudo restart udev
Then plugged device in and it worked!
qtoon said:
Followed this guide (thank you for posting) but couldn't connect. Scratched around and found I needed to create a new file in /etc/udev/rules.d with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="<4-char_verndorID>", ATTR{idProduct}=="4-char_productID", MODE="0666", OWNER="username"
Followed by:
Code:
sudo restart udev
Then plugged device in and it worked!
Click to expand...
Click to collapse
What did you name the new file you created? Or did you add this string to another existing file from the rules.d directory? I'm not sure what I've done wrong, but I get
Code:
[email protected]:~$ adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'kdb' from package 'elektra-bin' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'openjdk-7-jdk' (universe)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~$
This is after following each step, adding the three lines to the end of .bashrc and rebooting.
atmu5fear said:
What did you name the new file you created? Or did you add this string to another existing file from the rules.d directory? I'm not sure what I've done wrong, but I get
Code:
[email protected]:~$ adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'kdb' from package 'elektra-bin' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'openjdk-7-jdk' (universe)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~$
This is after following each step, adding the three lines to the end of .bashrc and rebooting.
Click to expand...
Click to collapse
@atmu5fear, inferring that you're new to Linux (a common background for all), some notes:
Unlike wlth Win-d'oh-s, there is a worldwide development community that's always working toward improvement of every aspect of the system, including echoed messages and documentation. You may have to shake off the tendency to ignore Windudz messages, which are frequently unhelpful. Linux command echoes are much more on-target. Also, look for files such as README in rules.d and read it!
Now before creating a new config file (which may not be necessary on your system), see the top feedback line: "No command 'adb' found." First, see that the adb binary is present and that it has exec permission. (Since it's a small file and functions alone, I prefer to copy it to the folder I'm working from.)
If it then runs but won't connect, read on...
Directory (or "folder") names with a trailing '.d' are special: They configure, control, or provide executables for daemons (programs which run continuously, providing a service).
Within service-config.d folders, if the service steps through the files sequentially (as in this case), then it does so based on each filename. (True except for the special case of rc.d, iIRC, in which order is set by the special program rcorder).
So in this case, for example, since the existing files are named 70-whatever, your newly-created file could be 80-atmu5fears-phone to load after the others.
Should connect.
qtoon said:
@atmu5fear, inferring that you're new to Linux (a common background for all), some notes:
Unlike wlth Win-d'oh-s, there is a worldwide development community that's always working toward improvement of every aspect of the system, including echoed messages and documentation. You may have to shake off the tendency to ignore Windudz messages, which are frequently unhelpful. Linux command echoes are much more on-target. Also, look for files such as README in rules.d and read it!
Now before creating a new config file (which may not be necessary on your system), see the top feedback line: "No command 'adb' found." First, see that the adb binary is present and that it has exec permission. (Since it's a small file and functions alone, I prefer to copy it to the folder I'm working from.)
If it then runs but won't connect, read on...
Directory (or "folder") names with a trailing '.d' are special: They configure, control, or provide executables for daemons (programs which run continuously, providing a service).
Within service-config.d folders, if the service steps through the files sequentially (as in this case), then it does so based on each filename. (True except for the special case of rc.d, iIRC, in which order is set by the special program rcorder).
So in this case, for example, since the existing files are named 70-whatever, your newly-created file could be 80-atmu5fears-phone to load after the others.
Should connect.
Click to expand...
Click to collapse
Thanks @qtoon for the reply. I'm not really new to Ubuntu, albeit, it's been a while. First started using it just prior to the realease of Hardy Heron 8.04 LTS. That being said I am certainly no expert, but am somewhat familiar and comfortable with the command line. I did read the README file before posting, but since I'm not all that familiar with configuration files and the like, I figured maybe I should ask.
As per your suggestion i moved the ADB binary to my home folder, not necessarily my working folder, but to test to see if the adb command would be recognized in terminal.
Code:
mv ~/ADB/android-sdk-linux/platform-tools/adb ~/
Still got same result so I moved it back, then went on to make a new file and add the suggested string
Code:
sudo > /etc/udev/rules.d/80-atmu5fear-adb
sudo gedit /etc/udev/rules.d/80-atmu5fear-adb
After saving and restarting udev I still get the same "adb command not found" error.
I then changed the string to read OWNER"atmu5fear" instead of "username", still nothing
Any more suggestions?
Thanks
atmu5fear
Sorted it out
instead of:
adb devices
i needed to input:
./adb devices
It's listed, and in order to use the adb shell:
./adb shell
once in the shell all adb commands work
I get this error...
[email protected]:~$ sudo > /etc/udev/rules.d/80-sjy-phone
bash: /etc/udev/rules.d/80-sjy-phone: Permission denied
ok....... didn't need to add a file, changed phone usb mode to media device and all is ok.
thanks
atmu5fear said:
Sorted it out
instead of:
adb devices
i needed to input:
./adb devices
It's listed, and in order to use the adb shell:
./adb shell
once in the shell all adb commands work
Click to expand...
Click to collapse
Didn't think to mention that, apologies.
Quick 'why' on the ./ here.
Glad you got it running.
Just tried on 14.4 and worked like a charm.
Note: No need to reboot the computer, just reload the bash config with
Code:
source ~/.bashrc
Thanks
A good step by step guide
i will try it and see if it works
Thanks again
Hello, can someone help me ? - I m having problems connecting my device with adb (I ve connected several other devices before with no problems).
I ve got an Allwinner A20 tv box, it worked fine for a few months then one day, after being on (but idle) for a few hours, I noticed the screen was blank but the light on the front was blue (indicating it was on, red is standby). It would not respond to the remote control or to anything, so I unplugged it and since then it will not boot and the screen is blank, the red light will light up but that is it. I ve eliminated the remote controller not working, but I cant boot the device.
So I ve tried connecting via ADB (with Ubuntu) but I cant get the device to show up after typing "adb devices".
Using this guide:
http://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
I can get the vendor id and device id and I ve added it and the manufacturer to udev/modeswitch devices, but when I type "sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W"
I get the following error:
~/Android/sdk/platform-tools$ sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1f3a
DefaultProduct= 0xefe8
SierraMode=1
NeedResponse=0
Look for default devices ...
found USB ID 048d:1336
found USB ID 1d6b:0002
found USB ID 19a8:2036
found USB ID 1f3a:efe8
vendor ID matched
product ID matched
found USB ID 1d6b:0001
found USB ID 062a:0102
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
USB description data (for identification)
-------------------------
Manufacturer: not provided
Product: not provided
Serial No.: not provided
-------------------------
Send Sierra control message
Error: Sierra control message failed (error -7). Abort
I ve searched Google for the error code but I cannot find anything.
The device was rooted and USB debugging was on.
Any help would really be appreciated.
Thanks
Hello there,
I just tried sideloading the 5.01 update on my Nexus 5 only to find that my adb was out of date! Shocking! For some reason it cannot be simply updated by using:
sudo apt-get install android-tools-adb
So I have adapted an old package with the new ADB binary (1.0.32) which can easily update you. Worked for me on Xubuntu 14.04.
Instructions:
1. Unzip the zip
2. Either cd to the directory Android in the extracted package and run ./ADB-Install-Linux.sh or just navigate to the same directory and right click and select "Execute" if your OS so allows.
This is not my work, merely a tutorial to get you up and running on 1.0.32. All credit goes to @kalaker who made this script back in 2012.
Thanks should help me on Ubuntu 14.04
Hmm, in sid
Code:
[email protected]:~$ apt-cache policy android-tools-adb
android-tools-adb:
Installed: 4.2.2+git20130529-5.1
Candidate: 4.2.2+git20130529-5.1
piperx said:
Hmm, in sid
Code:
[email protected]:~$ apt-cache policy android-tools-adb
android-tools-adb:
Installed: 4.2.2+git20130529-5.1
Candidate: 4.2.2+git20130529-5.1
Click to expand...
Click to collapse
Sorry, I don't quite understand, help me out a little here! Was there a quicker way to update?
Is this why I cant see my device after adb devices in terminal ubuntu 14.10?
I can see my device when N5 is on but not when in botloader mode.
this is what I see after that command:
~# apt-cache policy android-tools-adb
android-tools-adb:
Installed: 4.2.2+git20130218-3ubuntu36
Candidate: 4.2.2+git20130218-3ubuntu36
Version table:
*** 4.2.2+git20130218-3ubuntu36 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
100 /var/lib/dpkg/status
Ane idea?
hormosapiens said:
I can see my device when N5 is on but not when in botloader mode. Ane idea?
Click to expand...
Click to collapse
Yep. ADB works in recovery or the OS. Fastboot works in bootloader.
hormosapiens said:
Is this why I cant see my device after adb devices in terminal ubuntu 14.10?
I can see my device when N5 is on but not when in botloader mode.
this is what I see after that command:
~# apt-cache policy android-tools-adb
android-tools-adb:
Installed: 4.2.2+git20130218-3ubuntu36
Candidate: 4.2.2+git20130218-3ubuntu36
Version table:
*** 4.2.2+git20130218-3ubuntu36 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
100 /var/lib/dpkg/status
Ane idea?
Click to expand...
Click to collapse
Yeah you need fastboot as well. If you run the script that should work for you.
Guynan said:
Hello there,
I just tried sideloading the 5.01 update on my Nexus 5 only to find that my adb was out of date! Shocking! For some reason it cannot be simply updated by using:
sudo apt-get install android-tools-adb
So I have adapted an old package with the new ADB binary (1.0.32) which can easily update you. Worked for me on Xubuntu 14.04.
Instructions:
1. Unzip the zip
2. Either cd to the directory Android in the extracted package and run ./ADB-Install-Linux.sh or just navigate to the same directory and right click and select "Execute" if your OS so allows.
This is not my work, merely a tutorial to get you up and running on 1.0.32. All credit goes to @kalaker who made this script back in 2012.
Click to expand...
Click to collapse
I unziped and run this script.
now on N5 fastbood mode connected to my ubuntu 14.10 after adb devices I get "bash: /usr/bin/adb: Permission denied"
am I missing something?
Thanks
Try running it again, that should work. Were you root? Well you have to be for the script to run to completion. Please try it again?
hormosapiens said:
I unziped and run this script.
now on N5 fastbood mode connected to my ubuntu 14.10 after adb devices I get "bash: /usr/bin/adb: Permission denied"
am I missing something?
Thanks
Click to expand...
Click to collapse
I solved this issue navigating to the folder /usr/bin and then changing the Properties of both adb and fastboot files, in Permissions, check the "Allow to run as a program" (or something like this) box.
I guess it could be set in the script sh file. :good:
Thanks.
Worked after editing permissions in the usr/adb file. Cheers.
Tested on Zorin OS.
isn't working for me.
I was also getting the "permission denied" error after typing "adv version" or "adb devices". I changed the permission of the "adb" file in /usr/bin but after this, I got the error saying "no such file or directory. I'm running Ubuntu 15.04. Any ideas? at least tell me how to revert back to the old thing as I didn't understand "run Uninstall ADB.sh" as written in the README file. thanks in advance.
You are probably on a 64bit OS.
You just need to install some 32bit library:
This should fix your issue:
Code:
sudo apt-get install libc6:i386 libstdc++6:i386
Hi, i have a Nexus 6P based on 7.1.1 with Magisk root v14.0 with Magisk manager v14.0.
With the terminal emulator app i'm trying to execute this commands:
Code:
su
pm uninstall org.telegram.messenger
But i got an error: Android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died etc..
But if i connect my Nexus 6P to my pc, and via ADB i try to push this command
Code:
adb shell pm uninstall org.telegram.messenger
It works. I don't know if it's related to Magisk, but i tried to build an app made by that execute "pm uninstall org.telegram.messenger" after "su" to get root shell but nothing, i got only an error on my android monitor: "E/Magisk: Unknow id: pm" and obviously telegram has this package name and it is installed as user app. Someone can help me ?
smartandroidtech said:
Hi, i have a Nexus 6P based on 7.1.1 with Magisk root v14.0 with Magisk manager v14.0.
With the terminal emulator app i'm trying to execute this commands:
Code:
su
pm uninstall org.telegram.messenger
But i got an error: Android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died etc..
But if i connect my Nexus 6P to my pc, and via ADB i try to push this command
Code:
adb shell pm uninstall org.telegram.messenger
It works. I don't know if it's related to Magisk, but i tried to build an app made by that execute "pm uninstall org.telegram.messenger" after "su" to get root shell but nothing, i got only an error on my android monitor: "E/Magisk: Unknow id: pm" and obviously telegram has this package name and it is installed as user app. Someone can help me ?
Click to expand...
Click to collapse
Are you able to uninstall the normal way thought settings>apps?
Sent from my H1611 using Tapatalk
Welcome to Termux!
Wiki: https://wiki.termux.com
Community forum: https://termux.com/community
Gitter chat: https://gitter.im/termux/termux
IRC channel: #termux on freenode
Working with packages:
* Search packages: pkg search <query>
* Install a package: pkg install <package>
* Upgrade packages: pkg upgrade
Subscribing to additional repositories:
* Root: pkg install root-repo
* Unstable: pkg install unstable-repo
* X11: pkg install x11-repo
Report issues at https://termux.com/issues
$ <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creativ
bash: syntax error near unexpected token `<'
$ pkg install root-rep
Err:1 https://dl.bintray.com/termux/termux-packages-24 stable InRelease
Could not resolve host: dl.bintray.com
Err:2 https://dl.bintray.com/grimler/game-packages-24 games InRelease
Could not resolve host: dl.bintray.com
Err:3 https://dl.bintray.com/grimler/science-packages-24 science InRelease
Could not resolve host: dl.bintray.com
Reading package lists... Done
Building dependency tree... Done
All packages are up to date.
W: Failed to fetch https://dl.bintray.com/termux/termux-packages-24/dists/stable/InRelease Could not resolve host: dl.bintray.com
W: Failed to fetch https://dl.bintray.com/grimler/game-packages-24/dists/games/InRelease Could not resolve host: dl.bintray.com
W: Failed to fetch https://dl.bintray.com/grimler/science-packages-24/dists/science/InRelease Could not resolve host: dl.bintray.com
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree... Done
E: Unable to locate package root-rep
$ package install unstable-tepo
No command 'package' found, did you mean:
Command 'pamedge' from package 'netpbm'
Command 'pbmpage' from package 'netpbm'
Command 'pacat' from package 'pulseaudio'
$ Command 'pamedge' from package 'netpbm'
No command 'Command' found, did you mean:
Command 'w3mman' from package 'w3m'
$ Command 'pbmpage' from package 'netpbm'
No command 'Command' found, did you mean:
Command 'w3mman' from package 'w3m'
$ Command 'pacat' from package 'pulseaudio'No command 'Command' found, did you mean:
Command 'w3mman' from package 'w3m'
$ $pkg install x11-repo
BusyBox v1.30.1 (2019-03-19 00:36:42 UTC) multi-call binary.
Usage: install [-cdDsp] [-o USER] [-g GRP] [-m MODE] [-t DIR] [SOURCE]... DEST
Copy files and set attributes
-c Just copy (default)
-d Create directories
-D Create leading target directories
-s Strip symbol table
-p Preserve date
-o USER Set ownership
-g GRP Set group ownership
-m MODE Set permissions
-t DIR Install to DIR
$ Usage: install [-cdDsp] [-o USER] [-g GRP] [-m MODE] [-t DIR] [SOURCE]... DEST
No command 'Usage:' found, did you mean:
Command 'osage' from package 'graphviz'
$ Command 'osage' from package 'graphviz'
No command 'Command' found, did you mean:
Command 'w3mman' from package 'w3m'
$ $-c Just copy (default)
bash: syntax error near unexpected token `('
$ -d Create directories
No command '-d' found, did you mean:
Command 'ld' from package 'binutils'
Command 'id' from package 'busybox'
Command 'od' from package 'busybox'
Command 'dd' from package 'busybox'
Command 'hd' from package 'busybox'
Command 'dd' from package 'coreutils'
Command 'od' from package 'coreutils'
Command 'id' from package 'coreutils'
Command 'ed' from package 'ed'
Command 'fd' from package 'fd'
$ -D Create leading target directories
No command '-D' found, did you mean:
Command 'ab' from package 'apache2'
Command 'dc' from package 'bc'
Command 'bc' from package 'bc'
Command 'ld' from package 'binutils'
Command 'nm' from package 'binutils'
Command 'ar' from package 'binutils'
Command 'as' from package 'binutils'
Command 'cp' from package 'busybox'
Command 'rm' from package 'busybox'
Command 'sv' from package 'busybox'
Command 'dc' from package 'busybox'
Command 'ln' from package 'busybox'
Command 'vi' from package 'busybox'
Command 'id' from package 'busybox'
Command 'du' from package 'busybox'
Command 'nc' from package 'busybox'
Command 'od' from package 'busybox'
Command 'ar' from package 'busybox'
Command 'wc' from package 'busybox'
Command 'ps' from package 'busybox'
Command 'dd' from package 'busybox'
Command 'rx' from package 'busybox'
Command 'tr' from package 'busybox'
Command 'hd' from package 'busybox'
Command 'xz' from package 'busybox'
Command 'ls' from package 'busybox'
Command 'mv' from package 'busybox'
Command 'cc' from package 'clang'
Command 'dd' from package 'coreutils'
Command 'cp' from package 'coreutils'
Command 'ln' from package 'coreutils'
Command 'ls' from package 'coreutils'
Command 'rm' from package 'coreutils'
Command 'od' from package 'coreutils'
Command 'wc' from package 'coreutils'
Command 'id' from package 'coreutils'
Command 'tr' from package 'coreutils'
Command 'nl' from package 'coreutils'
Command '[' from package 'coreutils'
Command 'mv' from package 'coreutils'
Command 'du' from package 'coreutils'
Command 'pr' from package 'coreutils'
Command 'sh' from package 'dash'
Command 'dx' from package 'dx'
Command 'ed' from package 'ed'
Command 'fd' from package 'fd'
Command 'gs' from package 'ghostscript'
Command 'go' from package 'golang'
Command 'gm' from package 'graphicsmagick'
Command 'gc' from package 'graphviz'
Command 'jq' from package 'jq'
Command 'k' from package 'kona'
Command 'm4' from package 'm4'
Command 'mc' from package 'mc'
Command 'mg' from package 'mg'
Command 'lz' from package 'mtools'
Command 'uz' from package 'mtools'
Command 'ne' from package 'ne'
Command 'nc' from package 'netcat'
Command '7z' from package 'p7zip'
Command 'ps' from package 'procps'
Command 'pv' from package 'pv'
Command 'r2' from package 'radare2'
Command 'co' from package 'rcs'
Command 'ci' from package 'rcs'
Command 'rg' from package 'ripgrep'
Command 'ri' from package 'ruby-ri'
Command 'ag' from package 'silversearcher-ag'
Command 'sl' from package 'sl'
Command 'am' from package 'termux-am'
Command 'pm' from package 'termux-tools'
Command 'df' from package 'termux-tools'
Command 'su' from package 'termux-tools'
Command 'ip' from package 'termux-tools'
Command 'ht' from package 'texlive-bin'
Command 'mf' from package 'texlive-bin'
Command 'ul' from package 'util-linux'
Command 'vi' from package 'vim'
Command 'vi' from package 'vim-python'
Command 'wg' from package 'wireguard-tools'
Command 'xz' from package 'xz-utils'
$ -s Strip symbol table
No command '-s' found, did you mean:
Command 'as' from package 'binutils'
Command 'ps' from package 'busybox'
Command 'ls' from package 'busybox'
Command 'ls' from package 'coreutils'
Command 'gs' from package 'ghostscript'
Command 'ps' from package 'procps'
$ -p Preserve date
No command '-p' found, did you mean:
Command 'cp' from package 'busybox'
Command 'cp' from package 'coreutils'
Command 'ip' from package 'termux-tools'
$ -o USER Set ownership
No command '-o' found, did you mean:
Command 'go' from package 'golang'
Command 'co' from package 'rcs'
$ -g GRP Set group ownership
Rooted my thinkpad 430 laptop
Cruelty will be in your memory on your deathbed, not mine.
jrummy¿ said:
Rooted my thinkpad 430 laptop
Click to expand...
Click to collapse
How 'bout G8 next?
I need to be able to afford one hahaha
The pc has 973 GB of software memory
Anybody want to buy it???
Cant find the RAM size on it but its got 4 i5s and 4 i7s
Im confused did you get root for Q710AL?