Topics

Very optimistic. Android 16 comes with additional eBPF feature requirements to the kernel, which the 4.4 version the Pro1 is stuck on doesn't fulfill, but the Pro1X's 4.19 kernel version does. Or rather, those have been backported down to that version, but nobody has done this for 4.4 yet. See the LineageOS announcement for some details: https://lineageos.org/Changelog-30/ It may happen, but not within a few days if it does.

As LOS 23.0 is now available for the Pro1X (see this), we can expect it for the Pro1 as well in a few days. Will try it ASAP and report back, if it is as useful as 22.1 or as useless as 22.2.

Yeah, I strictly use Linux to do any of this. I never try it with my Windows 11 machine.  

I just dealt with this issue on a new Windows 11 PC, mentioned in the LOS 23 thread. Same symptoms as the OP here, trying to use fastboot. If you look at the devices attached to the PC once the phone is connected to it in fastboot mode, I expect you would see a driver error on the PC. The solution for me was to install a dedicated Andriod phone fastboot interface driver in the PC operating system.  I can't advise how to do that with Linux, but I'm sure the OP can figure it out. 

I went ahead and did this, too. No issues as yet. The one hiccup was that I had recently "upgraded" the OS on my PC to Windows 11, and it didn't have a fastboot driver for an Android device, to use with installing the Magisk img file. The phone shows as an unknown device on the PC when the phone was rebooted into fastboot mode, and when trying to update the driver manually, the default driver list does not show Android Phone. The default driver list did show "Samsung Android Bootloader Interface" though, and I installed driver version 2.21.0.0 of that. It worked just fine for me. I figured this was likely a more stable solution for a new W11 PC than trying to force a 2016 era driver into it. God knows my W10 PC was chock full of driver conflicts after 8 years of hard grinding.