I am following the below post to root my Xperia E Dual. > [How To Root Xperia E! Latest Update! (Locked Bootloader)\*LINKS > UPDATED* NOOB > GUIDE!](http://forum.xda-developers.com/xperia-j-e/general/how-to-root-xperia-e-update-locked-t2409525) In step 4 to install Framaroot APK we need to Check the option "Unknown sources" and "Usb dubugging" (in Developer options) But when I am turning on the Developer option Flashtool is showing an message like below: 08/048/2014 01:48:38 - INFO - Device connected with USB debugging off 08/048/2014 01:48:38 - INFO - For 2011 devices line, be sure you are not in MTP mode I have tried changing the Usb connection mode but problem is not resolved. Could you please help? **Some info:** Operating System Used to flash: Windows 8.1

Is it possible to use USB debugging on an app that is not yours, and was downloaded from the Google Play Store? I don't really need any in-depth information, I just want to be able to see general errors that may be occurring. I'm basically trying to debug a scrolling issue in my US Bank app on my own because their response is terrible, slow, and I've done redundant "troubleshooting" steps. The phone I have is a Google Nexus 5 running Android 6.0.1, which is not rooted.

**Context**, in case anyone believes I'm trying to do this for nefarious purposes. I have a Samsung Galaxy A12 running Android 11. Long story short, two years ago I shattered my phone's screen, I was already planning to change up the phone so, yes I was a little bummed out. Recently, I fixed the screen. I wanted to access some old files that I had in there, but I can't remember the password. It's a fairly long password, so it wouldn't be easy to remember after 2 years. I decided that maybe I can try to recover some videos and pictures, but apparently I didn't have USB debugging on in the past, or maybe it disabled on its own. It should have Dev options on though. I went to recovery mode and tried to mount /system, but it also gives me

failed to open /dev/block/dm-0 no such file or directory
mounted /system

and even after spamming it to the point it just says **mounted /system**. When I type adb pull /data/property/persist.sys.usb.config ~/ it just says adb: error: failed to get feature set: no devices/emulators found I have also tried to switch USB ports, but nothing. Overall, I'm confused, don't know what I'm doing anymore, much less how to fix things.

I've got an Asus ZenPad 300C that is crashing constantly. Things I have tried: - Clearing cache. I am unable to access Settings to clear the cache but was able to run a clean-up app, which I think did some of that. No effect. - Factory Reset. If I use Power+Volume Up to access recovery mode I can see the options - FASTBOOT MODE and POWER OFF, but the power button doesn't work so there's no way to actually select FASTBOOT MODE. I tried connecting via USB to run ADB and do it that way but USB Debug mode is not enabled and I cannot get into Settings on the phone to allow it because Settings crashes. - Battery. I have removed the back and temporarily disconnected the battery but that made no difference. Is there any other way to perform a hard reset or troubleshoot and fix this issue or is it done for?

My phone screen broke. I can't see anything, and the touch screen doesn't work. I can't buy a new phone, so I'm not looking into backing up my data. I want to be able to use it from my pc. I have a Motorola Moto G2 running LineageOS 14.1 and TWRP custom recovery. Until now, I have been able to use my phone from my PC using [Vysor](https://vysor.io) , because I previously had USB debugging activated. However, **I accidentally deactivated it and now I'm stuck out**. I can access via ADB through recovery and **already have investigated how to activate USB debugging** again from the shell using these sources: - https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock - https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb - https://android.stackexchange.com/questions/12834/broken-screen-while-debug-mode-was-disabled-how-can-i-re-enable-adb - [Enable USB debugging through Clockworkmod with adb ](https://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb/13332721#13332721) - https://android.stackexchange.com/questions/55674/how-can-i-enable-adbd-during-boot-on-cyanogenmod - [Manually enable adb debugging from recovery](https://forum.xda-developers.com/showthread.php?t=2335799) - [How to authorize adb service from boot](https://groups.google.com/forum/#!topic/mozilla.dev.b2g/epQ6qhIFZ50) But **none of these solutions have worked for me.** Here's a brief summary of everything I've tried: - I've set the content of /data/property/persist.sys.usb.config to mtp,adb - I've edited /data/system/users/0/settings_global.xml, setting adb_enabled, verifier_verify_adb_installs and development_settings_enabled to 1 - I've added these lines to /system/build.prop: `persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb` - I've used the following setprop commands: `setprop persist.service.adb.enable 1 setprop persist.service.debuggable 1 setprop persist.sys.usb.config mtp,adb` But when I reboot, I still can't see my device when I run adb devices Not only that, but then **everytime I reboot to TWRP recovery again, I notice that some changes are reversed:** - /data/property/persist.sys.usb.config content only says adb - /data/system/users/0/settings_global.xml remains almost intact but adb_enabled is back to 0 again - When I run getprop to all of the properties I've set before using setprop, it returns an empty string (which makes me suspect that the changes I've been making to /system/build.prop are being completely ignored) **It's as if everytime the phone boots, the system loads some default configuration and reverses some of the changes I've made and USB debugging remains deactivated**. Am I missing something? I really not know what else to do.

Just a few hours ago it was working. This is for an Honor X6B phone connecting to a windows laptop. Sometimes when I connect the phone via USB I get a popup asking permission for USB debugging but rarely and it doesn't make any difference. It's appearing in Device Manager > Portable devices, but... Now, when I run adb devices , either: - my phone is not being listed at all, or - it's listed but says 'unauthorized' So I can't run cordova run android without errors/failure. What am I doing wrong? I've tried: - Disconnecting and reconnecting the phone - 2 cables I know to be good with data connections, and 2 different ports on my laptop - 'adb kill-server' and 'adb start-server' - disabling and re-enabling 'USB Debugging' in developer options - Revoked USB Debugging authorisations in developer options - Switched between MTP and PTP USB modes - Deleted possibly stale ADB Keys in C:\Users\Me\\.android\ - Restarted phone and laptop - Tried updating the driver, it's already using the optimal one apparently - Disabling and re-enabling Developer options I can't find any other ideas for how to get this working again, please help!

Specifically, how does my Android adb fail to detect devices attached by USB data cable, on Windows or Linux (with Developer options and USB debugging enabled), except rarely (~1 out of 17-20 sessions)? $ ./adb kill-server && ./adb start-server && ./adb devices * daemon not running; starting now at tcp:5037 * daemon started successfully List of devices attached What is occurring under the hood? --- After lengthy efforts and research, my hunch is: it's likely an update bug, and SDK 33 or older would still work, like in this example: https://stackoverflow.com/questions/43131020/adb-cannot-connect-to-daemon-at-tcp5037 How can I obtain SDK 33 or older to get the corresponding platform-tools? Please explain the actual working mechanism to solve this issue.

How to modify the files in subfolders of android/data on android 14, I tried shizuku + ZArchiver or FV file explorer and it doesn't work, i connected my phone to my computer and tried to edit files from there also using adb and it doesn't work, I tried the files app by Marc and used splitscreen but even that doesn't work. Is there a way to modify (specifically push files into android/data) **not just read** the files, as even before trying shizuku or all these I could already view the files and copy them out of android/data, but I couldn't copy anything in, or edit or delete anything. To clarify I am talking about the /sdcard/android/data folder not /data/data and I need a way push files in, I could already view and pull files out from before

This is a follow-up question to https://android.stackexchange.com/q/230996/202005 . Basically, I intend to somehow use this command to remove the lock screen: adb sideload customROM.zip But, the customROM.zip should be something like described [here](https://www.isrgrajan.com/how-to-enable-usb-debugging-in-android-using-recovery-mode.html) to enable USB debugging. The problem is, those steps are incomplete: > **Steps to Enable USB Debugging Using Recovery Mode** > > * Unzip the stock ROM. > * Within the extracted folder, you will find the **system.img** well extract it too using Ext4 Unpacker > * Also, extract the **Update-SuperSU.v1.65.zip** file. > * Now open the folder where you have extracted the **system.img** files > * Grab any **.apk** file from this folder and change the extension from **.apk** to **.zip** > * And Copy the **RSA Certificated** to the **Update-SuperSU.v1.65** folder (delete previous files if exist) > * Also, copy the **build.prop** to the system folder located within **Update-SuperSU.v1.65** folder > * Locate the **update-script** file within this folder and edit it using **Notepad++** > * You need to update the **build.prop** file after adding the following line at the bottom > persist.service.adb.enable=1 > > * Next step is updating **SQLite** Database > * Which can be done by adding the following code to the update-script file > sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'" > > Cheers! You have Enabled USB Debugging > Now you can install your custom or stock ROM using ADB – USB Debugging Although the above steps seem **incomplete**, they look convincing that there might be a way to modify a stock ROM to enable USB debugging by: adb sideload modified-stock-ROM-which-just-enables-USB-debugging-and-does-nothing-else.zip Is there any better explanation than [those steps](https://www.isrgrajan.com/how-to-enable-usb-debugging-in-android-using-recovery-mode.html) ?

Running adb shell dumpsys | sed -n '/^Packages:/,/^[[:space:]]*$/p' yields a lot of information about installed packages. For example: Packages: Package [com.android.fmradio] (2af5b15): ... Following each package name com.android.fmradio there is a hex number, here 2af5b15, in brackets - what does this mean? Where do I find comprehensive documentation about dumpsys output? So far, I couldn't find anything on https://developer.android.com/tools/dumpsys about this, unfortunately.

I have two TCL TVs (one with Android TV and one with Google TV installed). In both cases, the USB drive becomes invisible to the TV software if I enable USB debugging. What could be the reason? Can I fix it somehow from my side? For example, by sending some adb command?

I have phone with not working SIM slots because misfunction. I enabled USB debugging by sign-in into Xiaomi account, but for "Install via USB" - I need SIM. MIUI 12.5 based on Android 10. What I tried: Disabling MIUI optimization - not help.

When I try to enable USB debugging on my Android device, I am prompted with this message: > The computer's RSA key fingerprint is:
> FE:35:23:34:... I see the public key in ~/.android/adbkey.pub How can I verify that this RSA key fingerprint is correct on the computer's commandline? Can I use adb?

I'm trying to use adb on Windows 11 and it's not picking up any of my devices. I've tried both a Samsung Galaxy S24 Ultra and a Google Pixel 6a. I've downloaded the platform tools on Windows 11 and added adb to my path so there's no problem there, adb is working just fine. I've enabled developer options on both phones and enabled USB debugging as well, my default USB configuration is set to file transfer even though I've tried every USB configuration available and I'm using the appropriate USB-C cable. I have even tried different usb ports on my computer as I have 3 of them. However, when I enable usb debugging I'm not getting the normal popup for the computer's RSA fingerprint asking me to allow access to the phones so what could I be doing wrong? I've never had this problem before, normally I do all that I listed above and adb works just fine. I've scoured the internet for solutions but they are all the same and no matter what I try I cannot get adb to recognize the devices. I've even gone as far as downloading specific USB drivers for each phone with no success. I'm at a loss, could windows defender somehow be blocking the adb connection? Would my firewall somehow be contributing to the problem? I only have the stock Windows Defender options enabled and have not messed with the firewall in any way.

I have an old Nexus 7 2013 tablet. It had virtually stopped working, so I did a factory reset. When I boot up it now goes into the Google startup screen and then to setting up a new account. It connects to WiFi but then at the next stage says Google play services has failed. I can't get past this stage. So I thought I would install Lineage OS. **How can I enable Developer mode and USB debugging without a working Android system?** When I connect with a USB cable to a PC, the PC doesn't recognize it. It charges but it doesn't show up on the PC as being attached. When I run adb devices on the PC it runs but shows no devices attached. I've checked the cable using another device and that shows up on my PC. **Is there a way to get my original Android system working or turn on Developers mode and USB debug so I can install LineageOS or some other OS?**

I have an Android device with Android 5.0. I turned on USB debugging and connected it to one laptop. The android device displayed a pop-up for USB debugging authorization, I allowed it. After a few days, I accidentally broke the Android device screen, it's not sensing any touch input and the screen display is quite broken. I have another laptop, and now I want, connect to that Android device to USB debugging. - How do I do it? - Is it possible to force "USB Debug authorization" from the laptop side? - Are USB Debugging Permission given to one laptop stored/saved in that laptop, like a file in the android-sdk folder or platform-tools folder, so that I can copy that file to another laptop and make it works, OR transfer RSA fingerprint, or any other ideas?

I have a Samsung Galaxy J5 2017 with a broken screen, the screen is black and unresponsive. I found an app that I can use to mirror my phone screen to my PC so I can recover my Google Authenticator codes for my accounts which requires USB debugging to be enabled. Unfortunately I don't have USB debugging enabled on this phone, I found a few ways to enable USB debugging but none of them work for me. I can't use an external keyboard / mouse or go into recovery mode because the screen is black. I also can't use the screenshotting method because the screen is unresponsive. Is there a way to enable USB debugging using my PC?

ADB cannot recognize my device in recovery mode. USB debugging is disabled and I think that's the reason why. Also, how can I enable USB debugging via fastboot (if that's even possible)?

I want to find out the directory where the native libraries of an app have been extracted to. The path structure will depend on the Android version. On Android 14 it will be something links this: /data/app/~~7BZ-8zEDb3gzGGndbbDhg9==/com.some.app-GQePpzWb2GhdgZ8qftAnrH==/lib On a rooted phone, this would be an easy task. It's also possible via ADB and USB debugging: adb shell dumpsys package com.some.app | grep legacyNativeLibraryDir However, I want to know if there's a way to find out without rooting or activating USB debugging.

I just bought a new Samsung Galaxy M11. I'm trying to transfer my files from my old phone to the new phone connected to a PC but it won't copy. I get the pop-up that says the internal storage is write protected. I have tried the developer options too by switching on and off the USB Debugging but it still doesn't work. I have searched the web but all I get is related to external storage or SD card. Is there anyway to remove the write protection on the internal storage?