search

0x192 / universal-android-debloater

Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device.
GNU General Public License v3.0
15.37k stars 815 forks source link

Cannot find the connected device #732

Closed CapoFantasma97 closed 1 year ago

CapoFantasma97 commented 1 year ago

Describe the bug The program fails to detect the connected devices. Tested on OnePlus 7 Pro and Samsung Galaxy Tab S7+.

The devices are correctly detected on other ADB tools (e.g. "Tool All In One" by Mauronofrio has no problem detecting them immediately and uninstalling APKs remotely).

UAD log UAD_20230510.log

immagine

CrafterNova commented 1 year ago

Same issue on windows 10 64 bit, connecting with Redmi 9 Power, Android 12

plexxman commented 1 year ago

I had the same issue and inspecting the log file (mine was identical to yours) it's complaining because UAD couldn't find an ADB executable. So I downloaded Minimal ADB portable, extracted in one folder, copy/pasted UAD executable to the same folder where I extracted ADB and Voilà! It worked.

Minimal ADB: https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/

Attached screenshot of minimal ADB and UAD in the same folder. image

oMaikeru commented 1 year ago

i still have the same issue even with portable adb

Reinified commented 1 year ago

I had the same issue and inspecting the log file (mine was identical to yours) it's complaining because UAD couldn't find an ADB executable. So I downloaded Minimal ADB portable, extracted in one folder, copy/pasted UAD executable to the same folder where I extracted ADB and Voilà! It worked.

Minimal ADB: https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/

Attached screenshot of minimal ADB and UAD in the same folder. image

THANK YOU SO MUCH, sorry for the caps, but this made uad finally work for me.

CapoFantasma97 commented 1 year ago

I solved it the day after I posted this issue by re-adding ADB to the PATH environment variables. I'm not sure why it wasn't there anymore. Other programs that run off ADB have their own portable ADB files so they didn't have the issue.