When I run adb devices nothing is listed. I already have root. Everything changed with OneUI 3. I can't even find developer options or USB debugging anymore. Where have they been moved to?
Same place, enable it by tapping on build number in about phone > software information, enable USB debugging and it should work
Guess it got reset with update to android 11
Related
I can't connect adb on any 4.2.2 ROMS, i understand theres a new security feature in 4.2.2 that should prompt you to confirm your PCs RSA key, but i never get this prompt. Also, ktoonsez kernel seems to bypass the security, as it allows me to connect without ever seeing the prompt. But any other kernel, no prompt, and all adb commands show device offline.
I do have the latest version of adb (1.0.31) and the latest sdk etc.., i also can't connect to adb using the USB cable either. I've tried reinstalling drivers, rebooting... nothing seems to be working.
any suggestions?
Edit: got it working. Can't say i know exactly what i did to fix it, but i'll try to reiterate what i just did. Clean flashed a new ROM, in developer options > root access set to Apps and ADB, make sure Android debugging is enabled, make sure USB debugging notify is enabled, then turn on adb wireless. Then on my pc connect to adb using "adb connect 192.168.1.x", adb devices shows device still offline. Then connected my phone to my pc through usb and i got the prompt. FINALLY lol
I'm sure you already did this, but you didn't mention it.
In a lot of 4.2.2 ROM's, you have to go into Developer Options and change from "Root access for Apps Only" to "Root Access for Apps and ADB".
Not all 4.2.2 ROM's do this, but some of them do.
I could not ADB from my computer to my 4.2.2 until I changed that selection.
Also, some new ROM's have the built-in Superuser which includes an ADB option in its settings.
CZ Eddie said:
I'm sure you already did this, but you didn't mention it.
In a lot of 4.2.2 ROM's, you have to go into Developer Options and change from "Root access for Apps Only" to "Root Access for Apps and ADB".
Not all 4.2.2 ROM's do this, but some of them do.
I could not ADB from my computer to my 4.2.2 until I changed that selection.
Also, some new ROM's have the built-in Superuser which includes an ADB option in its settings.
Click to expand...
Click to collapse
Tried it, no luck.
Maybe try this?
https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq
CZ Eddie said:
Maybe try this?
https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq
Click to expand...
Click to collapse
I appreciate the input but all that post says is that you must be on the latest SDK version which I mentioned I already was
I have a strange issue. After installing the Shield drivers, when I type in "fastboot devices" a number comes up. But when I type in "adb devices" it's completely blank. I cannot install SuperSu without it as I learned the hard way. Does anyone know why this is happening? Is it a possibility that using the Nvidia Shield TV 2017 version causes an issue with the ADB devices not showing up?
CrescentShield said:
I have a strange issue. After installing the Shield drivers, when I type in "fastboot devices" a number comes up. But when I type in "adb devices" it's completely blank. I cannot install SuperSu without it as I learned the hard way. Does anyone know why this is happening? Is it a possibility that using the Nvidia Shield TV 2017 version causes an issue with the ADB devices not showing up?
Click to expand...
Click to collapse
Did you remember to enable the hidden Developer
Settings (System > About Device > Build (7x Tap)), and then from those new Settings actually enable the USB Debugging? Otherwise yeah you're not getting far. Also not so sure if it applies to Fastboot per-se but, in the case of ADB you'll also have to confirm via a Checkbox that you want to log into the system that way.
Ichijoe said:
Did you remember to enable the hidden Developer
Settings (System > About Device > Build (7x Tap)), and then from those new Settings actually enable the USB Debugging? Otherwise yeah you're not getting far. Also not so sure if it applies to Fastboot per-se but, in the case of ADB you'll also have to confirm via a Checkbox that you want to log into the system that way.
Click to expand...
Click to collapse
I did enable USB debugging but have since learned a few things about using that software. Your device firmware has to be functional so ADB can see it, at least in my case. Now when I connect I can see it in ADB and TWRP. And if don't see it in TWRP you can always install the root manually.
Hi,
i have rooted my Pixel 3 XL without problems.
TWRP & MAgisk is installed.
Now i wanted to disable the new gestures as described here:
https://www.xda-developers.com/disable-android-pie-gestures-google-pixel-3/
unfortunately, the USB Debugging does not stay on.
Also titanium backup always complains about this.
When i enable USB Debugging, i see for a few seconds some "le Mobile android device", but disappeared immediately after.
USB drivers are installed.
Any idea?
Thanks
Btw: adb devices shows me my device in recovery when in TWRP. So cable seems to be ok. (anyway, i installed everything with this cable).
Termi11 said:
Hi,
i have rooted my Pixel 3 XL without problems.
TWRP & MAgisk is installed.
Now i wanted to disable the new gestures as described here:
https://www.xda-developers.com/disable-android-pie-gestures-google-pixel-3/
unfortunately, the USB Debugging does not stay on.
Also titanium backup always complains about this.
When i enable USB Debugging, i see for a few seconds some "le Mobile android device", but disappeared immediately after.
USB drivers are installed. Any idea?
Thanks Btw: adb devices shows me my device in recovery when in TWRP. So cable seems to be ok. (anyway, i installed everything with this cable).
Click to expand...
Click to collapse
Assuming you have enabled USB debugging in Dev settings. You've somehow got the wrong drivers installed. Use a program called USBDeview To remove all the Google related drivers on your PC/Laptop and reinstall the Google USB drivers. There are tutorials out there for step by step, but for some reason your drivers are wrong.
I confirm, Dev options are enabled, so also USB debugging.
Unfortunately when i enable USB debugging (WITHOUT CABLE), go back, and enter again in the Dev options menu, the USB debugging is disabled again..
But nevertheless i reinstalled the drivers as you wrote -> same problem.
I think the problem is the Pixel, not windows, as everything went fine while rooting the device. (usb debugging was active).
Solved!
My fault, enabled by mistake in Cerberus App the "prevent USB Debugging" option!
Should work now
Hey guys,
I'm trying to root my Huawei watch 1 since a week but with no success. The problem is that I'm not even able to unlock the bootloader.
As stated in the title the watch is not recognized at all by the PC, when I plug it in nothing happens not even a sound. I tried with at least 5 different computers running Windows 10 and one computer running Linux (Ubuntu) and I also tried different cables. In Windows Device Manager there is no sign of the watch and in Ubuntu using "lsusb" all the usb ports are shown as empty.
The watch is working perfectly btw with the latest Wear Os update (2.23.0.238044309) and Android 7.1.1
Is there anything I can do to make the PC recognize the watch ? Or are there any workaround to root the watch / unlock the bootloader ?
Any help would be appreciated
Elixir_ said:
Hey guys,
I'm trying to root my Huawei watch 1 since a week but with no success. The problem is that I'm not even able to unlock the bootloader.
As stated in the title the watch is not recognized at all by the PC, when I plug it in nothing happens not even a sound. I tried with at least 5 different computers running Windows 10 and one computer running Linux (Ubuntu) and I also tried different cables. In Windows Device Manager there is no sign of the watch and in Ubuntu using "lsusb" all the usb ports are shown as empty.
The watch is working perfectly btw with the latest Wear Os update (2.23.0.238044309) and Android 7.1.1
Is there anything I can do to make the PC recognize the watch ? Or are there any workaround to root the watch / unlock the bootloader ?
Any help would be appreciated
Click to expand...
Click to collapse
Have you enabled Developer Options and ADB debugging on your watch? If not, here's how to do it:
Open the Settings menu on the watch.
Scroll to the bottom of the menu. If no Developer Options item is provided, tap About.
Tap the build number 7 times.
From the Settings menu, tap the Developer Options item.
Enable ADB debugging.
JimSmith94 said:
Have you enabled Developer Options and ADB debugging on your watch? If not, here's how to do it:
Open the Settings menu on the watch.
Scroll to the bottom of the menu. If no Developer Options item is provided, tap About.
Tap the build number 7 times.
From the Settings menu, tap the Developer Options item.
Enable ADB debugging.
Click to expand...
Click to collapse
Thank you for the suggestion ! I already did it before and unfortunately it didn't change anything to the fact that the watch isn't recognized by the pc.
Hello xda'ers
I have the Xiaomi Redmi Note 8, however I want to use the scrcpy github . com / Genymobile / scrcpy utility it says it cannot detect the phone.
ADB Setup and its drivers have been correctly installed.
USB debugging has been enabled in the phone.
But the ADB cannot detect the phone.
It still is not working, so I went into the phone, developer options and go to USB Debugging, Security settings, and toggle that on, but it asks for a Mi Account?, which I do not have.
Please help.
Might as well sign up for that Mi account, because you need the (security settings) toggle turned on if you want to control the device via scrcpy. What does it tell you when you enter the command adb devices ? Did you get the popup asking for confirmation on whether you want to allow the PC to access debugging when you connected the phone via USB? Also make sure MTP/PTP/whatever else isn't turned on.
It's odd, executing adb devices gave an unauthorized message on the computer console, but the security confirmation never appeared on the phone up until some hours ago. I authorized the connection and voila I can now see the phone's screen on desktop PC via scrcpy, however.....
The screen just freezes, I mean, I cannot interact with it on the computer. If I unblock the phone manually and interact with it, the screen refreshes properly on the desktop, alas this is an issue with scrcpy not with the phone or ADB. Maybe I should file a bug or search their site?
Again, you have to enable the (security settings) toggle in your developer options if you want to control your device from the computer. This is mentioned on the Readme on scrcpy GitHub already.
Found solution:
1. Enable USB debugging
2. Run any terminal as root
3. setprop persist.security.adbinput 1
. That's all, nothing else is required