G1 (Modded RC30) will not telnet to PC? Help - G1 Q&A, Help & Troubleshooting

Now the thing is when I am at the home screen on my G1 i push "Enter" on the keyboard and then type "telnetd" and then push enter again it doesnt do anything. When I open up telnet client on my PC it wont connect with wifi on.
So I go to Terminal Emulator on G1 and plug in"
cd system
cd bin
telnetd
And then try and connect to telnet on PC and nothing happens.
So I then go to Telnet client on my G1 and go to connect to "localhost:23" and it says "Error while connecting to server: localhost/127.0.0.1:23 - Connection refused" the thing is that my local host for my wifi is not 127.0.0.1:23
And when I "netstat" from inside Terminal Emulator there is no address with port "23"
Any help would be greatly appreciated.

Download the app called Terminal Emulator from the market and use that instead of pterminal.
use the "su" command before trying to start telnetd.
Also make sure your wifi is up before your start telned.

mrboyd said:
Download the app called Terminal Emulator from the market and use that instead of pterminal.
use the "su" command before trying to start telnetd.
Also make sure your wifi is up before your start telned.
Click to expand...
Click to collapse
Thats what I have been using is Terminal Emulator but I dont think I can install Debian through Terminal Emulator. I would rather do it through the PC anyways.
I geta syntax error when using "su" in Term. Emu. because I believe I have installed the "su" mod to always allow.

adb shell
Presuming you're already running the proper modded RC30, you should be able to run 'adb shell' with USB debugging enabled on the phone and it connected to your machine. This should just drop you to a root shell.

SplasPood said:
Presuming you're already running the proper modded RC30, you should be able to run 'adb shell' with USB debugging enabled on the phone and it connected to your machine. This should just drop you to a root shell.
Click to expand...
Click to collapse
adb being a utility included in the android sdk (in tools/)

SplasPood said:
Presuming you're already running the proper modded RC30, you should be able to run 'adb shell' with USB debugging enabled on the phone and it connected to your machine. This should just drop you to a root shell.
Click to expand...
Click to collapse
SplasPood said:
adb being a utility included in the android sdk (in tools/)
Click to expand...
Click to collapse
I got all that but how do I actually use it (adb)? Every time I click on it a command window pops up and then goes away.

Ok I got adb shell to work now thanks guys

Related

Trying to learn ADB functions! Need some help!

I am trying to learn how to use ADB, so I can find the cause of a problem I am having on every 2.xx Rom I have tried, and I have tried them all!
So take a look at the screen shot, and you can see it finds my phone. For some reason thats as far as I have gotten, been screwing with it for 2 days but alas I have to ask!
Thanks for any help you can be!
Roman
OK, at a quick glance....
Instead of just typing "logcat", try "adb logcat". I think you'll have better luck.
Still looking through the rest, will edit in a few minutes.
EDIT 1: Don't actually put the "#" or the "$" on your command line. Those are prompts that the shell presents to you, not something you're supposed to type.
EDIT 2: Add the sdk\tools directory to your path. It will make your life much easier. You can get away with just doing a "cd" to that directory, but in the long run things will be much easier if you just put it in your path.
EDIT 3: "Operation not permitted"????? That command should have worked. Have you rooted your phone yet?
do adb "insert command here" logcat push pull install etc...
Cool thanks for the help subliminalurge, I think I got it now!
Now to start my bluetooth headphones with 1.5 and grab a log, then load up 2.1 and grab a log and see what the HELL is wrong!
Thanks again!
One last question, is it possible to save a whole string from CMD!
Also how do you do a dalvik wipe?
These are the 2 commands I have! Not sure if either one work or not!
DALVIK WIPE:
adb remount
adb shell
# cd /system/sd/dalvik-cache
# rm *
adb reboot recovery
adb shell mount /data
adb shell rm -r /data/dalvik-cache
I havent used adb since rooting my g1, since the release of the flashrec method.
Heres my noob question
Can terminal emulator do the same things as adb?
The only thing id ever use adb for is to push/pull, and i just use root explorer for that.
Jesus, youd think i became a senior just by spamming...
Terminal Emulator can not do the same thing as ADB. ADB is Android Developer Bridge (bridge as in computer to phone connection). Terminal Emulator, if you know Linux terms, emulates a Linux terminal on the phone... so, if you do "adb shell", you'll have the same commands as you would in terminal emulator... sorry I'm confusing
mrinehart93 said:
Terminal Emulator can not do the same thing as ADB. ADB is Android Developer Bridge (bridge as in computer to phone connection). Terminal Emulator, if you know Linux terms, emulates a Linux terminal on the phone... so, if you do "adb shell", you'll have the same commands as you would in terminal emulator... sorry I'm confusing
Click to expand...
Click to collapse
Lol i see what you mean.
You need adb to theme, dont you?
Windows man, through and through
(oh the irony, of being such an android patron...)

Terminal Emulator??? Access "adb shell"???

how do i use the terminal emulator app to access adb shell?
adb shell is only used when you're on a computer, like when using android sdk tools. When you use the terminal emulator you use different commands try This Link for some help using the terminal emulator, they're basically the same as linux commands.
also this should be in the Q&A section
lol the terminal is the 'shell'
if you're running a terminal right on the phone, then consider yourself already @root when you're typing in commands.
foil said:
lol the terminal is the 'shell'
if you're running a terminal right on the phone, then consider yourself already @root when you're typing in commands.
Click to expand...
Click to collapse
Sort of. You are a user, but not "root". To become superuser you have to use the SU command.
/ $ su
~ # |
Click to expand...
Click to collapse
I'm sorry if I'm nitpicking here. Your original point remains true. You don't have to use ADB at that point to run commands. You run the command without ADB right in the terminal.
subcypher said:
Sort of. You are a user, but not "root". To become superuser you have to use the SU command.
I'm sorry if I'm nitpicking here. Your original point remains true. You don't have to use ADB at that point to run commands. You run the command without ADB right in the terminal.
Click to expand...
Click to collapse
No, you're fine. I was just assuming that he was already rooted, but you're right - it's a regular user account unless you change to superuser.
in order to do what you probably want you will have to type su. It should then ask for SU permission and then you should gey
Code:
#
.
hello everyone, idk if im in the wrong place, but im trying to connect my non rooted phone to my rooted tablet with terminal emulator.Is there a way for me to use adb because it worked with my previous phone...its not working and isn't showing any device when i input "adb devices"...Can anyone help me please, help would be greatly appreciated ?(btw usb debugging is enabled on my phone)

[Q] Don't know how to connect D3 using ADB

When i open ADB all it does is it has a lot of white writing that scrolls along and then closes, does anyone know if i set it up wrong, or if they could post step by step instructions? it would be much appreciated, Thanks.
what operating system are you using
smoshism said:
what operating system are you using
Click to expand...
Click to collapse
I am using windows 7
um, is there a way to remount adb? im on ubuntu so i cant help out a whole lot. but maybe i can bounce some ideas that could work
smoshism said:
um, is there a way to remount adb? im on ubuntu so i cant help out a whole lot. but maybe i can bounce some ideas that could work
Click to expand...
Click to collapse
im not sure, im not very familiar with ADB
I'm pretty new to this, but seems to me you are trying to open the adb that psouza includes with his tools. (If not, then just ignore me)
that's not gonna work for what you are trying to do. i think you need to download the android sdk to get adb working.
SrulDog said:
I'm pretty new to this, but seems to me you are trying to open the adb that psouza includes with his tools. (If not, then just ignore me)
that's not gonna work for what you are trying to do. i think you need to download the android sdk to get adb working.
Click to expand...
Click to collapse
i am using the one in the SDK, i have it on my c drive in the correct spot but it still closes itslef
Are you clicking it like an icon or running it from a DOS prompt? It is to be run from the command line as it is a dos/command line program..
Ie.. at the c:\android-sdk-x86\platform_tools\ prompt you type adb and what you want to do.
Adb push or adb pull or adb shell, etc. Just adb will give some command options
Sent from my Xoom
d7benjamin said:
When i open ADB all it does is it has a lot of white writing that scrolls along and then closes, does anyone know if i set it up wrong, or if they could post step by step instructions? it would be much appreciated, Thanks.
Click to expand...
Click to collapse
First you have to open an elevated command prompt. Do this by clicking the start icon, then typing in "cmd" (without the quotes of course) and then right clicking the only thing that pops up and choosing Run As Administrator. After doing this, you need to know where you folder that contains ADB is at. To find this easily, click Start and then click Computer and in the explorer window that just popped up, type in "adb.exe". That will show you where your adb files are at.
Continuing on, for an example, my adb stuff is in C:\root stuffz. So in the command prompt I would type in "cd c:\root stuffz" and then hit enter. After that, I can then do my adb commands, such as "adb shell", "adb push", "adb pull", etc...
Edit: Make sure you have your drivers installed for the phone. Also, make sure the phone is in debug mode and charge only. This should just about cover most of the absolute basics of getting your phone recognized by adb. I'm not too sure if I missed anything, and one of the other more experienced peeps on here can prob give you more detailed information lol.

ADB Not Working

MY ADB has stopped Working
It happened after Installing the CWM And TWCR
Well What happened it was saying ADB was outdated while installing but it installed CWM and TWCR
Now if i enable ADB in the phone the windows doesnt read that there is a mobile nor anything detected not even charging
When i disable ADB I can see my phone charging and i can transfer files
I don't know what to do and I am very worried ...
Hope If any1 could help...
Tried installing ADB drivers and the Android SDK .. No luck
I think the problem is in the phone as it doesnt allow me to connect to the PC with ADB on
I read this http://forum.xda-developers.com/showthread.php?t=1917741
and found that ro.debuggable=0 in the Deafult.prob While it is enabled ...
And there is a question too how can i backup it so if i eddit it and get a bootloop I want to be able to restore using CWM or TWCR
John98Zakaria said:
MY ADB has stopped Working
It happened after Installing the CWM And TWCR
Well What happened it was saying ADB was outdated while installing but it installed CWM and TWCR
Now if i enable ADB in the phone the windows doesnt read that there is a mobile nor anything detected not even charging
When i disable ADB I can see my phone charging and i can transfer files
I don't know what to do and I am very worried ...
Hope If any1 could help...
Tried installing ADB drivers and the Android SDK .. No luck
I think the problem is in the phone as it doesnt allow me to connect to the PC with ADB on
I read this http://forum.xda-developers.com/showthread.php?t=1917741
and found that ro.debuggable=0 in the Deafult.prob While it is enabled ...
And there is a question too how can i backup it so if i eddit it and get a bootloop I want to be able to restore using CWM or TWCR
Click to expand...
Click to collapse
Can you use adb over other computers?
Also, try ADB over network. Goto Settings > Developer Options and turn "ADB over network" on. If prompted with a warning, press OK. Then you will see an ip address with a port number under ADB over Network setting. Now open cmd (or Terminal in Linux) and cd to the directory where the ADB files are present. Then type
Code:
adb connect <ipaddress>
Of course, replace <ipaddress> with the ip that you see in the Developer Options under ADB over network. It should be something like "192.168.1.2:5555", enter the whole thing. Then see if you are successfully connected by typing
Code:
adb devices
.
If you are using windows go to control panel and look for "hardware" or more specifically "drivers". It is somewhere there, just look around and you will find it. Then enable adb and connect phone. Then Select your device name from the list and right-click and select appt. drivers.
ayushag96 said:
Can you use adb over other computers?
Also, try ADB over network. Goto Settings > Developer Options and turn "ADB over network" on. If prompted with a warning, press OK. Then you will see an ip address with a port number under ADB over Network setting. Now open cmd (or Terminal in Linux) and cd to the directory where the ADB files are present. Then type
Code:
adb connect <ipaddress>
Of course, replace <ipaddress> with the ip that you see in the Developer Options under ADB over network. It should be something like "192.168.1.2:5555", enter the whole thing. Then see if you are successfully connected by typing
Code:
adb devices
.
If you are using windows go to control panel and look for "hardware" or more specifically "drivers". It is somewhere there, just look around and you will find it. Then enable adb and connect phone. Then Select your device name from the list and right-click and select appt. drivers.
Click to expand...
Click to collapse
Thanks for the reply I can't use ADB anywere ..
The phone doesn't even appear in the PC with ADB debuging enabled not even a connected sound or anything ..
I tried Wifi Kontect on the playstore as I didnt find "ADB over Network" But ADB wont connect....
Any Other solutions ... I dont mind if i have ADB over wifi the important thing is to have any ADB connection
www .mediafire .com/convkey/fb15/db3ykaaldgkqsd66g.jpg?size_id=5
www .mediafire .com/convkey/93e0/49f47ps6s9nbeyj6g.jpg
Remove spaces so you can see the images I cant post links yet
Fixed
I have fixed my probem thanks to @sijav !
Installing
http://forum.xda-developers.com/showthread.php?t=1687590
Fixed everything ! even after un-installing the app

[Q] failed to run "adb" command on the "Terminal emulator"

I have a moto x without root, and I just follow the instruction of wakelock detector. But when I try to run adb command on the Terminal emulator, it just shows "/system/bin/sh: adb: not found". How can I run the command successfully?
lurenja said:
I have a moto x without root, and I just follow the instruction of wakelock detector. But when I try to run adb command on the Terminal emulator, it just shows "/system/bin/sh: adb: not found". How can I run the command successfully?
Click to expand...
Click to collapse
You can't use adb from a terminal on the phone... Only a convected PC. That is the problem. No way around it. Adb is for PC/Mac only.
samwathegreat said:
You can't use adb from a terminal on the phone... Only a convected PC. That is the problem. No way around it. Adb is for PC/Mac only.
Click to expand...
Click to collapse
Quote:
Originally Posted by ahikmat View Post
Wakelock detector 1.5.7, supports KitKat (rooted, also for non-rooted phones with few steps)
New permission added:
[INTERNET] - WLD does not consume any traffic, this permission is needed for adb self connection purpose
([BOOT] - this permission will be added for calculating screen on time for non-rooted kitkat phones)
Starting from kitkat we retrieve wakelock stats from "dumpsys", that is why your phone either needs to be ROOTED or you need to have adb access to your phone itself.
KitKat owners with ROOTED phones
Run WLD, allow ROOT at first run. It is preferred to check "remember it" option
KitKat owners with NON-ROOTED phones
This option takes few steps to accomplish, but this is the only way to see wakelock stats for non-rooted kitkat phones.
In android phones, by default adbd listens to USB port, we need to change it to listen tcpip for establishing adb connection.
for that we need to run "adb tcpip 5555" from PC. For Windows OS, usb drivers need to be installed. http://developer.android.com/sdk/win-usb.html
Install one of these light adb on your PC:
Windows: http://forum.xda-developers.com/show...php?p=42407269
Mac/Linux: https://code.google.com/p/adb-fastboot-install/
Enable "developer option" on your phone (it is in settings window , if you don't see it click "Build version" 7 times on "About" section)
Run "adb tcpip 5555" from command line.
Then install "Terminal emulator" on your phone and run "adb kill-server" , "adb devices" and confirm self-connection.
You can follow these slides for details: https://docs.google.com/presentation...it?usp=sharing
We are working to make single-click PC app.
If you could have better idea to optimize these steps, share it with us! Thank you!
[updated apk]
Big thanks to Sordna for helping to improve WLD and RootTools performance!
Here's the guide, I am just confused with the bold part, can anyone please explain?
lurenja said:
Quote:
Originally Posted by ahikmat View Post
Wakelock detector 1.5.7, supports KitKat (rooted, also for non-rooted phones with few steps)
New permission added:
[INTERNET] - WLD does not consume any traffic, this permission is needed for adb self connection purpose
([BOOT] - this permission will be added for calculating screen on time for non-rooted kitkat phones)
Starting from kitkat we retrieve wakelock stats from "dumpsys", that is why your phone either needs to be ROOTED or you need to have adb access to your phone itself.
KitKat owners with ROOTED phones
Run WLD, allow ROOT at first run. It is preferred to check "remember it" option
KitKat owners with NON-ROOTED phones
This option takes few steps to accomplish, but this is the only way to see wakelock stats for non-rooted kitkat phones.
In android phones, by default adbd listens to USB port, we need to change it to listen tcpip for establishing adb connection.
for that we need to run "adb tcpip 5555" from PC. For Windows OS, usb drivers need to be installed. http://developer.android.com/sdk/win-usb.html
Install one of these light adb on your PC:
Windows: http://forum.xda-developers.com/show...php?p=42407269
Mac/Linux: https://code.google.com/p/adb-fastboot-install/
Enable "developer option" on your phone (it is in settings window , if you don't see it click "Build version" 7 times on "About" section)
Run "adb tcpip 5555" from command line.
Then install "Terminal emulator" on your phone and run "adb kill-server" , "adb devices" and confirm self-connection.
You can follow these slides for details: https://docs.google.com/presentation...it?usp=sharing
We are working to make single-click PC app.
If you could have better idea to optimize these steps, share it with us! Thank you!
[updated apk]
Big thanks to Sordna for helping to improve WLD and RootTools performance!
Here's the guide, I am just confused with the bold part, can anyone please explain?
Click to expand...
Click to collapse
Yeah....did you install adbd? That is the android adb daemon.....
BEFORE you can use adb on an android device (It was never meant to be run from anything but a PC), you must FIRST *install adbd*, AND *run "adb tcpip 5555" from a ***PC****
This enables you to use the adbd daemon. Don't have access to a PC? No can do...
6719
samwathegreat said:
Yeah....did you install adbd? That is the android adb daemon.....
BEFORE you can use adb on an android device (It was never meant to be run from anything but a PC), you must FIRST *install adbd*, AND *run "adb tcpip 5555" from a ***PC****
This enables you to use the adbd daemon. Don't have access to a PC? No can do...
Click to expand...
Click to collapse
Really thanks for the reply, I didn't install the *adbd*, and I find someone said to run "adb remount" from a PC to install the *adbd*, but when I run the command, it shows "remount failed: Permission denied". Is this the right way? or how can I install the *adbd*?
lurenja said:
Really thanks for the reply, I didn't install the *adbd*, and I find someone said to run "adb remount" from a PC to install the *adbd*, but when I run the command, it shows "remount failed: Permission denied". Is this the right way? or how can I install the *adbd*?
Click to expand...
Click to collapse
I suggest asking the person who wrote the guide that you quoted. Good Luck!
Remember to always hit the thanks button under any post where someone helped you, or that provided useful information. :good:

Categories

Resources