Despite any rooting, any options selected in developer settings (they do nothing regarding this)... I still need to enable adb wifi by restarting in tcpip mode by tethering to pc usb adb (adb tcpip 5555). Then I can use wifi adb fine, and tools like scrcpy that this phone works excellent with (seriously a league above Samsung streaming, and Samsung had it integrated into phone link). With every other device I ever had, and currently have like Fire Sticks, tablets... Selecting the dev option is enough and I dont need to tether to my pc every phone reboot. I can adb into them fine.
Is there anyone out there that knows whats up? Do roms other than Lineage (or stock) enable this functionality?
Related
Hi all,
someone bought me a damaged (screen cracked and not usable) phone, and they want to get their photos off the device. But in order for me to even interact with the phone via terminal, or use any recovery app on computer, the adb option must be enabled! now this is where the problem is, cuase how can i enable the adb option when i am flying blind with no screen?!
SO my question is this. Is there a way to connect the phone via the cable and push a command to the phone to enable adb option?
The other problem when connecting the phone is that all that comes up when you connects to the computer is the drive to install the drivers, and not the other drives for the system. SO maybe even a way to send a commnad to the phone to enable data connection so can get access to phone internal memory?
Hello, I have been struggling with this one for a few days...
I have a Linux ADB installation and I can use it to connect to my devices, except for one - a Galaxy S3 running Resurrection Remix 5.8.3.
When I do `adb devices` the repsonse is an empty list. The phone does show the `USB debugging connected` alert. It also shows `USB charging for this device`.
I've read that latter one should be changed to `Transfer Phots (PTP)` but doing so makes no difference, and unplugging and reconnecting the USB resets this option to the charging setting.
I've tried everything that I can think of.... disabling and reenabling USB debggging and developer mode.
I don't think it's the ADB because it works fine with any other device that I try.
What else can I try?
ogpog said:
What else can I try?
Click to expand...
Click to collapse
Do you have the specific drivers installed for your phone? If you do not, install them and then try
If you do, uninstall and install again.
I am not sure what "specific drivers" I need. I am running `adb` from `android-tools 8.0.0_r17-1` on Arch Linux. I am pretty sure that the client side is fine because it does work sometimes, as I explain below.
I did a firmware update as an attempt to fix this. I now have "RR-N-v5.8.5-20171217-i9300-Final". I have since been able to get it to work but it is hit-and-miss.
First I note that the usb connection resets to charge-only whenever it is disconncted/reconnected. This requires that the appropriate mode needs to be selected each time the USB is plugged into the device.
I connect the phone via USB to the computer and try `adb`. It doesn't work (`adb shell` reports `error: no devices/emulators found`).
I open the "Developer Options" of the settings screen. I "Revoke USB debugging authorisations" so that I get the authorisation pop-up when the adb connection works as a visual cue that the connection is working. An alternative way to get feedback is to use `adb wait-for-device` on the computer - this blocks until the connection is made and, when it exits `adb shell` works immediately afterwards.
I then go to the "Networking" selection, choose "Select USB Configration" and then change the setting from "Charging" to "PTP (Photo Transfer Protocol)". Perhaps adb will work, but unlikely. If it doesn't work I keep selecting between the various usb options and, eventually, adb starts working. It only ever seems to work on the PTP mode.
I find doing this a few times may get adb working or it may cause the device to fall over and reboot. In fact, the latter scenario is the most likely!
(edit, I think the reboot may be a result of selecting the 'audio source' option and not relevant. Selecting between charging and ptp a good few times (30-ish - I lose count) eventually gets adb working).
My work-around to this problem is to connect ADB over the network which works reliably but requires opening a terminal on the device to configure and start the service.
Hi everyone,
Yesterday I broke my Galaxy S7 screen in the building's stairs while leaving home.
I want to save all the stuff I have on it, but recently I installed a new stock rom and forgot to tick in the developer menu "usb debug".
I tried an adb connection but the phone is unauthorized...
I read on some french board that I could flash a special kernel (with debug usb ON) to be able to get an adb connection. but that I will be blocked because I never accept any adb connection while having my screen working....
Is there any solution ?
I need help to hopefully resolve my issue.
Have a nice end of day.
You can connect an USB keyboard/mouse. Maybe an USB-hub works too so you can connect a PC and keyboard at the same time.
I was able to unlock my screen but I can’t access to my storage because I have to enable the sharing storage...
It seems there is no solution.
The amazon fire devices are a little weird. I currently have them integrated with home assistant through ADB. The problem I am running into is that if the ADB connection is lost from my computer to the firetv, then either the ADB debugging needs to be toggled in developer options, or I can restart the firetv itself. If the ADB connection is lost then some of my automations and controls do not work on home assistant.
Couple things:
I am willing to root the device
If I cannot toggle adb debugging, I could just reboot the device. I have considered using a smart plug to do this, but I would rather let the fire handle it.
Would tasker or termux be an option? I've considered moving ADB from the computer server to termux with https://github.com/MasterDevX/Termux-ADB, but I am not sure that would be more reliable.
Basically I want to toggle ADB debugging or a reboot on a set schedule (eg. every night @ 4am).
Hi Moosefist
Parhaps this might help you toggling the ADB based on a schedule:
App: Automate playstore link
The app Automate let you create a schema flow where you can specify what your device should do. For example, turn off bluetooth when connected to wifi network XYZ if time is greater than 10pm.
I think even that it doesn't require root, but I am not sure since mine it rooted anyway...
Just as a FYI, ive been playing with GMS + Icebox to play around and see if i can get notifications working.
Whilst i have had limited sucess with notifications - even though the push notification tester says all is well, what i have found is that the app Tasker allows you to issue adb commands over wifi.
This means that if you set up ADB via a pc initially to listen on tcp port 5555 (or whatever provided you update tasker adb wifi settings) you can start icebox on the local phone while you are on the go without having to connect to your pc.
This means that you can start and stop gsf on the go without having to be tied to a pc.
It adb does need restarting every device reboot however, so you will need your laptop for that, but if like me you rarely restart your handset, this is loads easier than having to connec to the laptop to update apps via the app store, if you are so inclined.
Let me know what you think!