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
Hey guys I basically did everything that the Cricket how to said, but with the Metropcs logins and passwords. I have flashed several phones before, but not an Android OS. The phone works with internet and picture text coming in, but the apps. like Youtube and Google maps will only work on WIFI and not on the network and MMS out will also not work.
My assumption is that it has to do with this whole autostart file thing. I am so new to this programming stuff that I am not sure what to do when it comes to this.
So I used QPST and CDMAW to program the back end so that is probably why the Internet works. APN and Proxy settings are all correct, but here is the only place I have an error.
These are the directions:
Before starting the next step make sure you have the u2nl file and autostart.sh in this folder c:/android/tools
"Now go to the command prompt on your pc and type the following commands:
cd c:\android\tools
adb remount
adb push c:\android\tools\u2nl /system/bin/u2nl
adb push c:\ android\tools\autostart.sh /data/opt/autostart.sh
Now:
adb shell
chmod 0755 /system/bin/u2nl
chmod 0755 /data/opt/autostart.sh
reboot"
My error begins when I type the adb remount.... it states unable to find device or something like that.
I plugged phone to computer not in Diag mode or any mode, just turned it off then back on and plugged it in. Is there a setting on the phone I need to check?
Then I go ahead and do those push commands just for the hell of it, it just scrolls through this whole display of things.. not sure what its doing.
The adb shell part works and so do those other commands after....
When I am done with the last line that has the autostart.sh and hit enter...
The phone doesn't reboot, I just unplug and then turn off and then back on. I would have thought there would be a script to reboot phone or something...
So what am I missing or is it not even possible to get Google maps and youtube to work on Metroweb... has to be on wifi??? I have seen people say they have done it...
Any help would be appreciated..
Hey guys! I accidentally "forgotten" access to the ADB Shell on my Super SU. I am really scared now. How do I manually re-enable it? I don't want to flash my phone and stuff if possible.
P.S. If this is the wrong topic/thread please feel free to direct me to the proper area.
zeron824 said:
Hey guys! I accidentally "forgotten" access to the ADB Shell on my Super SU. I am really scared now. How do I manually re-enable it? I don't want to flash my phone and stuff if possible.
P.S. If this is the wrong topic/thread please feel free to direct me to the proper area.
Click to expand...
Click to collapse
Regranting su access is an extremely quick and simple process. All you have to do to be able to use root from adb shell is to start and and shell on the device again, call su and grant root from the SuperSU access prompt that will appear on the device, regranting access to apps is simple too, simply open the app and when it calls for su, SuperSU will bring up the access prompt for any app/uid that it hasn't got any stored settings for already
mmonaghan34 said:
Regranting su access is an extremely quick and simple process. A you have to do to be able to use root from adb shell is to start and and shell on the device again, call su and grant root from the SuperSU access prompt that will appear on the device, regranting access to apps is simple too, simply open the app and when it calls for sure, SuperSU will bring up the access prompt for any app/uid that it hasn't got any stored settings for already
Click to expand...
Click to collapse
Thank you very much!
Hey there XDA! I'm here to show off a new Android app I've published that I think a certain audience may find useful.
Ever heard of ADB? If not, you likely won't need this app. But for those of you who have used or encountered ADB in the past, you know that you usually need a PC to shell into your phone. While yes, apps such as Termux exist, they don't have elevated privileges as ADB does.
Behold, LADB! A truly local ADB shell server. That means no root, no computer, and no hassle.
Here's how it works. LADB bundles an ADB server within the app libraries and extracts it upon runtime (W^X compliant). Normally, this server cannot connect to itself because it requires an active USB connection to be visible. However, Android's Wireless ADB Debugging feature allows the server and the client to speak to each other through localhost. LADB initializes the ADB server and asks to connect to localhost, solving this limitation.
So, what can you do with it? Well, anything that ordinarily uses "adb shell <command>" can now be done locally. That means granting apps special privileges for things like SystemUI Tuner, many logcat apps, and generally anything else that needs elevated privileges. That's not all though. You can disable system apps using pm disable-user com.android.whatever, you can enable and disable system overlays with cmd overlay, you can get a logcat with logcat -d | tail -n 20, and the possibilities go on.
Here's the link to the app. It is paid, and it's actually my first paid app in a very long time. If you just need to use the ADB server for a minute, you can buy the app, use it for a few minutes, and then refund it through the store (don't tell Google).
https://play.google.com/store/apps/details?id=com.draco.ladb
Note, this app is also open source! I'm a huge fan of FOSS so I went ahead and published the app on GitHub so that anyone can compile the app for themselves for free. Any purchases through the Google Play store can be considered as donations <3.
https://github.com/tytydraco/ladb
I'm always available for support if you encounter any issues either by direct message, by telegram (@tytydraco), or by email [email protected]. I'll also be answering questions in the comments of this post. Enjoy!
Reserved for any updates or questions
Hi! I bought this app few minutes ago. I haven't tied yet. Can I use this app on 2 phones with the same google account or I have to pay twice?
badmania98 said:
Hi! I bought this app few minutes ago. I haven't tied yet. Can I use this app on 2 phones with the same google account or I have to pay twice?
Click to expand...
Click to collapse
You only need to pay once for it to be in your library
” While we tested this and found it working on essentially every modern Android phone sold in the US in the last four years, not every device is guaranteed to have the Wireless Debugging feature. It's part of AOSP, Android's open source code base, but OEMs sometimes remove functionality from their skinned versions of Android. If your phone doesn't have this option, sadly, LADB won't work for you. ”
Unfortunately my Mate 30 Pro has not this option.
LE: I managed to work.
Anybody tried to use appops https://play.google.com/store/apps/details?id=rikka.appops using ladb?
Is there a way to automate some task, for example after reboot?
Unfortunately my galaxy note 10+ has no wireless adb so i can't try but i hope it will come with android 11...
Yes, well...
alessandro_xda said:
Anybody tried to use appops https://play.google.com/store/apps/details?id=rikka.appops using ladb?
Is there a way to automate some task, for example after reboot?
Unfortunately my galaxy note 10+ has no wireless adb so i can't try but i hope it will come with android 11...
Click to expand...
Click to collapse
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?
alessandro_xda said:
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?
Click to expand...
Click to collapse
This functionality is on it's way
alessandro_xda said:
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?
Click to expand...
Click to collapse
What do you mean by work? can you prompt an adb command?
I've the same device and it doesn't work (NO wireless ADB in devOpts) just waiting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when I press reset it gives me this message
And FC's.
Using v1.1.2 under Android 10 with rootfs.
Thanks
rypz79 said:
What do you mean by work? can you prompt an adb command?
I've the same device and it doesn't work (NO wireless ADB in devOpts) just waiting
View attachment 5170637
when I press reset it gives me this message
View attachment 5170639
And FC's.
Using v1.1.2 under Android 10 with rootfs.
Thanks
Click to expand...
Click to collapse
I've just typed ls
alessandro_xda said:
I've just typed lsView attachment 5170783
Click to expand...
Click to collapse
I've no idea why it's not working on my SM-N975F (N10+)
Say what ROM are you using? what kernel? do you have root access (magisk)?
TnXaLoT
rypz79 said:
I've no idea why it's not working on my SM-N975F (N10+)
Say what ROM are you using? what kernel? do you have root access (magisk)?
TnXaLoT
Click to expand...
Click to collapse
I'm on stock rom (unrooted)
I think you only need to start the wireless connection using the cable connected to a pc and then the wireless adb will survive until next reboot
No wireless abd option on A50
I have ladb up and running but I am having trouble getting basic advanced commands to function.
When I enter:
adb shell pwd
It returns:
system/bin/sh: <stdin>[24]: adb: inaccessible or not found
It returns this for every adb command I have tried.
what happens if I disable the system keyboard (Gboard) on my oppo? I'm using SwiftKey and it "fights" with gboard autocorrection...
Tuvor said:
I have ladb up and running but I am having trouble getting basic advanced commands to function.
When I enter:
adb shell pwd
It returns:
system/bin/sh: <stdin>[24]: adb: inaccessible or not found
It returns this for every adb command I have tried.
Click to expand...
Click to collapse
It isn't really a bug. On pc you would always type something like adb {acction} {parameters}. Adb - is the program which is going to be executed so in windows it will be adb.exe (it contains server for adb interface). Action - specifies what adb server should do, so things like devices - list adb devices, shell - open android shell. The last one contains parameters for action, so if you used shell as action it takes shell command as parameter. In this situation, when we use local shell we need to skip adb shell part because we don't have a whole adb server like adb.exe on windows with a lot more options, because we are always using just this adb shell functionality.
pawloland said:
It isn't really a bug. On pc you would always type something like adb {acction} {parameters}. Adb - is the program which is going to be executed so in windows it will be adb.exe (it contains server for adb interface). Action - specifies what adb server should do, so things like devices - list adb devices, shell - open android shell. The last one contains parameters for action, so if you used shell as action it takes shell command as parameter. In this situation, when we use local shell we need to skip adb shell part because we don't have a whole adb server like adb.exe on windows with a lot more options, because we are always using just this adb shell functionality.
Click to expand...
Click to collapse
could you please explain this like I was completely stupid?
I am trying to get running the SystemUITuner. When I enter the path with cd / /storage/emulated/0/Download/platform ecc LADB doesnt show anything. I think that should be ok. But when I then enter ./adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS it tells me "permission dinied".
What am I doing wrong?
mathias.ngr said:
could you please explain this like I was completely stupid?
I am trying to get running the SystemUITuner. When I enter the path with cd / /storage/emulated/0/Download/platform ecc LADB doesnt show anything. I think that should be ok. But when I then enter ./adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS it tells me "permission dinied".
What am I doing wrong?
Click to expand...
Click to collapse
You don't need to type " adb shell"....just type pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS
See if that works
Ryano89 said:
You don't need to type " adb shell"....just type pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS
See if that works
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That worked. Thanks a lot and have a nice sunday!