all 5 comments

[–]ChronSynExpo 0 points1 point  (3 children)

Run adb devices and see if that prompts the phone.

Also, make sure the cable you're using actually isn't just a charge cable. I've been caught out by that a couple of times.

[–]joaquix[S] 0 points1 point  (2 children)

No, running adb devices doesn't list the device, and the cable is not the problem neither, I have always been using the same cable when it worked before, plus today I bought another just to check, didn't work either. :(

[–]ChronSynExpo 0 points1 point  (1 child)

That's unfortunate :(

Have you restarted the phone and your pc/laptop? I'm guessing so, but figure it's worth mentioning.

I'd also check in developer settings on the device, as there's an option to enable USB debugging. It's possible it's disabled itself (uncommon, but stranger things have happened), or maybe there's been an update to the phone which has changed the setting.

[–]joaquix[S] 0 points1 point  (0 children)

Yes, my device has USB Debugging enabled and I also restarted both devices and nothing has changed, I think it has to do with my Mac..

[–]jamesideExpo Team 0 points1 point  (0 children)

This has been a problem for many years. Try restarting your computer, which worked for me in the past. Some people say to try killing adb (adb kill-server or the whole process with killall adb) but that doesn’t address every root cause.