Database Develop

Help me pls. adb not found

The first, I'm beginner coding android for android studio or eclipse but my device has not adb (or eclipse and android studio didn't see) although I install driver from pc companion, use cmd [adb devices] is show unauthorized including i try install adb.bat that show killing-server, daemon successfull and gone
Help me pleashttp://dl.xda-developers.com/attachdl/cb9471a26af0816560a1f998f0fffeb1/53345aac/2/6/5/3/6/7/6/device_manager.png
http://dl.xda-developers.com/attachdl/292092d7ea82c6eef2cac9b35d14e4fd/53345ac1/2/6/5/3/6/7/7/10151209_10201661776966300_1517802886_n.jpg

Monkun said:
The first, I'm beginner coding android for android studio or eclipse but my device has not adb (or eclipse and android studio didn't see) although I install driver from pc companion, use cmd [adb devices] is show unauthorized including i try install adb.bat that show killing-server, daemon successfull and gone
Help me pleashttp://dl.xda-developers.com/attachdl/cb9471a26af0816560a1f998f0fffeb1/53345aac/2/6/5/3/6/7/6/device_manager.png
http://dl.xda-developers.com/attachdl/292092d7ea82c6eef2cac9b35d14e4fd/53345ac1/2/6/5/3/6/7/7/10151209_10201661776966300_1517802886_n.jpg
Click to expand...
Click to collapse
Is USB debugging turned on in developer options?

I assume you have the Android SDK installed, along with ADB and the path has been set for ADB?
Edit - I see you have from your screenshots. Ignore this. Sorry.
Sent from my C6603 using Tapatalk

I found a problem that a happen the rom on eXistenZ and now I re-install this rom(fresh install)

[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:

[Root] Doze Settings Editor (Android Marshmallow Only)

Just to inform you all with Marshmallow there is an app to edit the default doze settings and get better battery life
Thanks to @p0isonra1n
p0isonra1n said:
[Root] Doze Settings Editor (Android Marshmallow Only)
Requires Root
This app is a simple editor of the settings or parameters which affect the operation of Doze.
If no root is available then it will offer an ADB command that will modify the doze settings.
Because there is no root on open it will always load the default settings.
Click to expand...
Click to collapse

I had problem activating Doze new settings via app so I had to use the adb (even though my device is rooted)
here is how :
1- enable usb debugging from settings> developer options
2- There are plenty guides on how to install and run adb, you can google it or use this or this or ...
3- connect your device
4 - in terminal run
Code:
adb start-server
adb shell dumpsys deviceidle
if the values shown are same as default , then you have my problem, go to step 5. if values are what you set in the app profiles ... then you dont need to proceed
5- revoke "Doze Settings" su permissions from super su app
6- run the app , su permission will be denied and it give u a command to copy, copy it to a text file and send the file to your pc
7- open the file in your pc and copy the text
8- paste the copied line in the adb terminal and hit enter
reboot device and run the "adb shell dumpsys deviceidle" from terminal again, it should show new values.

It helps! Thanks!

Question one UI 3.1

so i was using adb to uninstall some system apps and when finished my home screen would not load. found out one UI 3.1 was gone>.any way to reinstall with out having to use odin again? thanks oh s21 ultra

You mean you have removed system apps using ADB root? If so, you'll have to reinstall the system (or at least push back the apps you removed).
Be careful on which apps you remove. It's recommended to have TWRP, so that you don't have to go through trouble of Odin and stuff ...

Factory reset

Why do you people do this without knowing the basics? Why?
Factory reset, then use this tool to debloat. Select safe level.
[TOOL] ADB AppControl 1.8.0 🚀 Ultimate App Manager & Debloat Tool + Tweaks
ADB AppControl 🚀 Root is not required. Works with any Android device. Can do almost everything you dreamed about with applications. ADB AppControl - the desktop program, that will allow you to easily manage applications on your android device...
forum.xda-developers.com

I was Trying to Avoid Factory reset, I know That would work. And my phone is not rooted.1 And to the guy hating, you didnt know what -you were doing at one point. im learning I go, so save it.

And thanks everyone, I appriciate it, im gonna Check out the Adb tool...

Unless I had very valuable data a Factory Reset would be my first option. The good news is your OS Android 11 is likely still intact. The bad news is you have no User Interface which is the platform used to communicate and accommodate your OS. Throw in the problem with no Home Screen which compounds the problem. If you've deleted UI 3.1 it may be other vital utilities are missing as well which you're not aware of which only a factor reset will install and replace.

I just re flashed firmware, but it kinda werd, the screen is big and easy mode is off and font is small..

How To Guide How to debloat Galaxy Tab S8 ♻️

In this guide we will see step by step how to debloat the Galaxy Tab S8​
First of all we have to enable: Developer Options
Settings->About tablet->Software information->(tap 7 times)Build number
After that we will enable: OEM Unlocking & USB Debbuging
Settings->Developer Options->OEM Unlocking(ON) & USB Debbuging(ON)
On the next step we need to download & install : ADB & Fastboot tools
Once you install the tools, connect your {Tablet} - {PC}
Select: USB Debbuging & Open your: Terminal
We are almost there
Now i will make a short explanation in order to understand what are we doing exactly & how we will do it.
What is ADB?
ADB provides us with commands that can be used to debug Android devices,
installing or uninstalling apps and getting information about a connected device.
adb shell
This command activates the remote shell command console on the connected Android smartphone or tablet.
adb shell pm uninstall -k --user 0
Using this, you can easily uninstall the unwanted system apps. To be able to execute it, you must issue 'adb shell' command first.
You can then use 'pm uninstall -k --user 0' followed by the Android app package name as shown below.
pm uninstall -k --user 0 com.whatsapp_2.20.apk
This command can help you if you want to remove all the bloatware from your phone.
Please note that most system apps don't have the 'Uninstall' option on the device but this command works magically.
If you don't know the app package name for the apps you want to remove, you can use adb shell pm list packages to find it out.
adb shell pm list packages
Using the above ADB Shell command, you can print the list of the app package names for all apps installed on your Android device.
You can use this command with different parameters to get a more specific list of app packages.
For instance, if you want to list the system apps only, use
adb shell pm list packages -s
In order to list all third-party apps installed on your Android phone or tablet, you issue the following command.
adb shell pm list packages -3
Do you want ADB Shell to show the list of all enabled or disabled apps on your device,
try the command with '-d' (disabled apps) and '-e' (for enabled apps) parameter.
adb shell pm list packages -d
adb shell pm list packages -e
Now, if pm list command troubles you or you are unsure that you are making the right choice you should stop right there
(uninstalling the wrong app might harm your tablet's operating system) and use another method for identifying which app you want to uninstall.
(GUI method - Graphical User Interface) For example: APK Inspector will provide you with a detailed list of installed packages (plus their icon) on your device, once you select an app, extra details will be shown to you & that's how you will get the correct name.of.the.app
Thanks for your time ❤​

Reserved

I really appreciate this write-up it has been a big help..
I use my OnePlus 9 pro with ADB and fastboot for Android NDK to debloat..
and that application inspector is a God send so again. thank you
I don't know if it was just a fluke or what but when I rebooted after successfully deleting digital well-being my tablet booted up super fast...
either way I'm good.

Awesome thanks for the tip. Is using "install" put the app back if I screw up something?

So it really doesn't uninstall just uninstalls from your app draw?

striker59 said:
So it really doesn't uninstall just uninstalls from your app draw?
Click to expand...
Click to collapse
For the os, it is like it has been uninstalled. But you don't free disk space, as the data of the app are still there. They just been hidden from os. That's why you can have back the app again just with an adb command again.

Man I used this to shut down numerous apps on all of my Android devices. Samsung and Verizon apps. Thanks!

Went back in to uninstall more apps. Device is recognized but adb shell won't load. The last time I used adb it was for my phone.

Figured it out, had to revoke USB debugging on my tablet. Delete on the computer c:user.android and restart (actual path on the computer could be different than what I stated).

Hi there.
Can anyone confirm, if it is save to remove the phone app from the device since it is connected to this samsung feature "calls/ messages on other Galaxy devices"? Actually i fully wanne get rid of this feature and app since i don´t use a galaxy phone.
Can someone share experiences/ideas according this topic?

Stogie87 said:
Hi there.
Can anyone confirm, if it is save to remove the phone app from the device since it is connected to this samsung feature "calls/ messages on other Galaxy devices"? Actually i fully wanne get rid of this feature and app since i don´t use a galaxy phone.
Can someone share experiences/ideas according this topic?
Click to expand...
Click to collapse
I have Debloated it (adb frozen) months ago. Didn't have any problem. You can always enable it again.

Am I right? If i debloat I don't clean up the system space used from the os ?

nofear5888 said:
Am I right? If i debloat I don't clean up the system space used from the os ?
Click to expand...
Click to collapse
You won't earn more free space. Apps are still there after Debloating.

sosimple said:
For the os, it is like it has been uninstalled. But you don't free disk space, as the data of the app are still there. They just been hidden from os. That's why you can have back the app again just with an adb command again.
Click to expand...
Click to collapse
@striker59
You remove the app for the current user but its still inside system's root directory.
You don't gain storage.
What you can achieve tho if you remove/disable the unnecessary services without causing softbrik or error spamming 'service has stop working' is a lightweight $user who uses less ram, your phone's overall performance is better and the battery reduction is slower.