Carlos-Anso yes, and I'm sure you didn't read why I'm there.. In fastbootd (entered through recovery) device get's recognized, in fastboot (first screen) not. So, please explain how a damaged cable can be used for this 100% reproducible error (yes, not even once detected there, not even once not detected on the wrong screen).
Can someone with knowledge please shime in and direct us in right direction, please? Setup seems fine, but when is a stock device behaving like this? Beeing undetectable in fastboot, while proofing it generally has no problem connecting + the installer works
How would one produce this on purpose?