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.28k stars 813 forks source link

UAD not finding my device #649

Closed bodeaner closed 1 year ago

bodeaner commented 1 year ago

I am trying to debloat my Samsung Galaxy Tab A (2021) tablet, but it is not being recognized by the UAD program. The tablet is recognized with the 'adb devices' command and I have USB debugging on.

2023-03-10 12:02:13 INFO [src\gui\mod.rs:458] ANDROID_SDK: 0 | PHONE: fetching devices... 2023-03-10 12:02:13 ERROR [src\core\sync.rs:75] ADB: program not found 2023-03-10 12:02:13 ERROR [src\core\sync.rs:75] ADB: program not found 2023-03-10 12:02:13 ERROR [src\core\sync.rs:75] ADB: program not found 2023-03-10 12:02:13 WARN [src\gui\views\list.rs:142] No custom selection imported: The system cannot find the file specified. (os error 2) 2023-03-10 12:02:28 DEBUG [src\core\update.rs:178] Checking for UAD update 2023-03-10 12:02:41 DEBUG [src\core\update.rs:178] Checking for UAD update 2023-03-10 12:02:44 ERROR [src\core\utils.rs:162] Can't open the following URL: 2023-03-10 12:02:45 ERROR [src\core\utils.rs:162] Can't open the following URL: 2023-03-10 12:09:01 DEBUG [src\core\update.rs:178] Checking for UAD update 2023-03-10 12:09:02 ERROR [src\core\utils.rs:162] Can't open the following URL:

AnonymousWP commented 1 year ago

Post the entire logfile. Also, are you sure you followed the steps?

bodeaner commented 1 year ago

Yes, I followed the steps. Logged out of the OEM account, developer options enabled, USB debugging on and allowed for the connected computer, and I have tried with both the standard version for Windows as well as the opengl version. Also tried with a previous version. I hope I've attached the log files properly this time. Thank you for your help.

UAD_20230310.log UAD_20230315.log

zweack commented 1 year ago

Had the same issue, turns out adding platform tools to path does not work. Copying the exe to platform tools folder and starting UAD from there worked for me.

notyan commented 1 year ago

moving the UAD to adb folder works for me (windows system)

bodeaner commented 1 year ago

moving the UAD to adb folder works for me (windows system)

This worked, thank you!

AnonymousWP commented 1 year ago

It's weird how I didn't have to do this at all to get it working on both desktop and laptop. Probably PEBKAC.

Rafee-M commented 1 year ago

@bodeaner You could close the issue if your problem has been solved.

8julie commented 10 months ago

moving the UAD to adb folder works for me (windows system)

This worked, thank you!

Hey, if you don't mind, could you give me the file path for it? I'm not sure if I have the right location and I want to make sure

notyan commented 10 months ago

moving the UAD to adb folder works for me (windows system)

This worked, thank you!

Hey, if you don't mind, could you give me the file path for it? I'm not sure if I have the right location and I want to make sure

It depend on where you put your adb folder , simply it is located on where you can run ./adb if you are using windows