I’ll hope you’ll get an answer here as well, but maybe you should cross-reference your post in the >130 messages thread on the 1.8.5 update to increase visibility.
yes.
I think the problem may be the storage-mode.
which have you enabled?
If you have MTP-Mode enabled please switch to storage-mode and try adb again.
Let me know if it works.
Which OS do you use with adb?
I usually start the adb daemon as root which is probably bad practise, but I was always too lazy to properly set everything up. I think I originally started doing
sudo adb start-server
because
adb devices
gave me this exact
???????????? no permissions
output when not executed as root.
Now when I tried starting the daemon with my normal user account and version 1.8.5 on my phone, adb devices correctly listed my phone - as long as it’s in MTP mode
So, in some way, I can reproduce @infos’ problem. sudo adb start-server still works with both storage modes though. Oh well.
Yes, I mean this will possibly solve the problem such as @haffenloher solution.
But I wonder why before the upgrade adb worked without this workarounds.
I my opinion it must be a user right management problem on this Android version using usb in storage mode.
While using mtp mode it works as desired.
As far as I know mtp depends also on udev rules.
I wonder: Have you done the Storage Upgrade? Then you will notice that your internal storage is not exposed anymore in storage mode (only in MTP mode!). In this case, it is not a bug, but a side effect of the Unified Storage Partition.