Hey,
Having problems for entering ADB codes. How do you enter something like $ fastboot oem lock. Thanks
try
"adb shell" press enter
"su" press enter
now you have the "$" at start of the command
Sent from my GT-P3100 using XDA Free mobile app
You type that command in a command line on your computer if you have adb and fastboot installed and your phone is plugged via usb.
$ is basically a sign for command line in linux, your line starts with $ for a normal user and # for root.
To sum up, if you see something starting with $, that means it is a command.
Search the forums for more info about installing adb and fastboot if you didn't already.
Related
Is there an adb command to launch an apk from your phone or pc
Sent from my SCH-I500 using XDA App
Take a look here: http://forum.xda-developers.com/showthread.php?t=580291
NOTE: that is for the phones terminal in an app such as Terminal Emulator. From the computer just type "adb shell" then you are in the phones terminal and can run those commands.
So basicly im trying to follow a tutorial to get my screen working in ubuntu touch, which involves using adb shell, nano to modify a file.
the little tutorial goes like this:
thecosmicfrog said:
Sure thing. Boot up your device, then plug in a USB cable. Open a terminal and run "adb devices". Make sure that a device shows up. If not, unplug and plug in again. I find that it never works the first time for me.
Next, run "adb shell". This will connect you to your phone and open a shell session on it. Open the /etc/rc.local file in a text editor using the following command:
"nano /etc/rc.local"
Scroll down to the bottom using your keyboard's arrow keys and on the line before "exit 0", insert the following:
./system/bin/sensorservice &
Save and exit the file using Ctrl+X then reboot your phone by running the command "reboot".
This should fix the black screen problems.
Click to expand...
Click to collapse
well when im in adb shell, and type nano /etc/rc.local my adb (or cmd window) screws up completely (see attachement)
what is going on and how do i fix it?
this isn't normal i think!
j
My "adb push" command is not working. When I type it in, the command prompt seems to run "adb help". No error message, just the list of possible commands. See the attached screenshot.
Does anybody know what's happening?
Computer: Windows 7
Device: Verizon Galaxy Nexus (toro)
Version: 4.2.2Kernel Version: 3.0.85-franco.Kernel-nightlyBuild: JDQ39
The "adb push" command is used to push files to your device.
Typing "adb push" won't do anything besides displaying all the adb functions.
To push something, your command must be something like "adb push whateverthefileis system/bin" the "system/bin" is the destination where it is to be pushed, for example if you want to push an app you do, "adb push android.apk system/app"
Make sure your drivers for phone is installed properly.
IF I HELPED HIT THANKS
Click to expand...
Click to collapse
Sent from my Nexus F...Fi...Fii...Ahem...*clears throat*... Five.
solution???
Did you put your phone in recovery mode first?
krishneelg3 said:
The "adb push" command is used to push files to your device.
Typing "adb push" won't do anything besides displaying all the adb functions.
To push something, your command must be something like "adb push whateverthefileis system/bin" the "system/bin" is the destination where it is to be pushed, for example if you want to push an app you do, "adb push android.apk system/app"
Make sure your drivers for phone is installed properly.
Sent from my Nexus F...Fi...Fii...Ahem...*clears throat*... Five.
Click to expand...
Click to collapse
I had typed in the correct syntax for the command, but will try updating drivers. Thanks!
ADB push just scrolls commands
I am trying to use ADB with telnet to root my Droid Maxx. I have been desperately trying to use Jcase's method. All my commands work, except the push command. I can telnet, my drivers are all up to date, my phone is on debug, install unknown sources etc...Everything seems to be in order, but the su and RockMyMoto.jar will not push, just a scrolling of commands. Any help would be most appreciated.
Thank you
I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows
MrTooPhone said:
I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows
Click to expand...
Click to collapse
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.
In addition to the above, by not prepending './' to your command, you were calling a(n apparently available) system-wide installation that might have been too old to detect the device. It would also help if you would post an lspci so we could see if the device is at least in the correct mode.
acejavelin said:
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.
Click to expand...
Click to collapse
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.
MrTooPhone said:
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.
Click to expand...
Click to collapse
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Tried again with Linux. SU did the trick. Thanks.
I was using the minimal ADB and fastboot and when I started to enter in commands. I put in the command "adb shell". The next line that came up was "[email protected]:/ $" I do not know how to carry on from there.
roboownsall said:
I was using the minimal ADB and fastboot and when I started to enter in commands. I put in the command "adb shell". The next line that came up was "[email protected]:/ $" I do not know how to carry on from there.
Click to expand...
Click to collapse
Hello,
Can you tell us what exactly are you trying to do with the tool?
-Vatsal