Topics

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.

Lineage 23.0 (Android 16) is out for the Pro1x.  This conversation continues here:  

Lineage-23.0-20251013-NIGHTLY-pro1x with October 1st security patch installed smoothly using the Lineage upgrade procedure linked in the OP. It was installed with MindtheGapps 16 and Magisk 29 installed as a zip for SU only.  all data was preserved in the upgrade. I did have to open the Magisk app to let it run an update, but root was established. All went according to plan and everything seems to be working so far.