John tried restarting his device, restarting his computer, and even reinstalling the ADB drivers. Still, nothing worked. He began to suspect that the issue was related to the version of LADB he was using.
Armed with this new information, John used the adb devices command with the -l option to list all devices and their interfaces. He then used the adb -s <device_id> shell command to connect to his device specifically, which allowed him to bypass the issue. ladb 1.3.1
With the connection established, John was able to push his changes to the device and test his custom ROM. The new features in LADB 1.3.1 had initially seemed like a minor update, but they ended up being crucial in resolving the issue. John tried restarting his device, restarting his computer,