Functionally similar:
From Linux, with sys admin experience, and electronics knowledge.
Fastboot apparently can not touch device.
Operating system on the end of the USB cable cannot see the wileyfox swift device.
I already had two original wileyfox swifts of new condition.
I unlocked bootloaders on both, each with different version of cyanogen fastboot mode; both now twrp + lineageos.
Enter third swift, used condition, with locked bootloader, but updated to Android 7.1.2 .
Enabled developer options; enabled USB debugging; enabled OEM unlocking (maybe should say 'checked').
Recovery mode and fastboot mode are accessible via power + volume buttons.
Even tested changing USB modes within Android 7.1.2 (MTP, PTP).
adb devices => no joy;
fastboot oem device-info => no joy;
with sudo => no joy.
Suspected damaged micro USB port, so dismantled Android phone, and dismantled Lineageos phone.
Swapped micro USB port mini boards.
Result: Both USB ports were functional.. Lineageos phone still responds to ADB, fastboot, lsusb, dmesg, (shows up to workstation) .
Back to Android 7.1.2 phone:
Tried sdcard, and sideload options.
I read a reference from a web post that ADB sideload mode from recovery resulted in the workstation being able to see the phone device, but this is FALSE in my case.
So has the Googley Android monster disabled USB access to fastboot?
Am I missing some security option within Android OS?
Is "privacy guard", or similar function, locking me out? (Often the simple omission).
I cannot transfer files from the phone to workstation (computer/server/laptop/host thing); although MTP mode is checked (xor PTP).
I feel the frustration of the people whom I suspect might think they just don't get it.
I know paranoid mode, but the idea that "Android" has hijacked those locked wiley swift devices, does not seem irrational to me.
Hack my Google brick.
