[Xiaomi Mi Pad 4 ROMs, Kernels, Recoveries, & Other] limited_imagination:
Great work arter97, thank you very much.

I had trouble connecting my Windows PC to the Mi Pad 4 to use adb and fastboot commands after flashing the arter97 kernel.

Obviously, the device does not identify as a Mi Pad 4 any more at this point, so the Windows drivers get confused.

But I figured out the trick, so will post it here.

Initially after flashing arter97's new OS, I could only connect to the PC with a Ubuntu virtual machine that I had running on the PC. The Mi Pad 4 didn't show up in the Ubuntu file manager, but I could instantly connect via adb running in a Ubuntu terminal. So score 1 for Linux, I guess.

But not so for the Windows PC host, which didn't see the Mi Pad 4 at all: not in the file manager and not with adb running in a command terminal window, either.

The solution starts with downloading and installing Mi PC Suite. This will put all kinds of rubbish on the PC that you will want to delete afterwards, but it does install a folder with driver .INF files that you need.

Open Device Manager, and you will see the Mi Pad 4 sticking out in the tree, with some new odd new name like SDM660-QRD_SNXXXX, and with a little yellow exclamation mark. Right click it to check the properties, click the details tab, select Hardware IDs under the Property list, and make note of the VID and PID numbers. On mine, it was VID of 2717, and PID of FF08. (Interestingly, that translates as the RedMi Note 3 if you Google it.)

Next, search your PC's drive to find the file called "android_winusb.inf", which will be in one of the Xiaomi folders that gets installed with Mi PC Suite. It may be somewhere in the hidden AppData folders, Local or Roaming, depending on which version of Windows you're using, but the Windows search function should find that file.

Open android_winusb.inf with Notepad++ or similar, and scroll to the line that says, "%CompositeAdbInterface% = USB_Install, USB\VID_2717&PID_ff08&MI_00".

Edit that line and change it to whatever you noted from Hardware IDs. In my case, I deleted the "&MI_00" at the end of the line, so that it just read "%CompositeAdbInterface% = USB_Install, USB\VID_2717&PID_ff08", and then saved the edited file as android_winusb.inf, in the same Xiaomi install folder.

Then go back to the Device Manager, right click the SDM660-QRD_SNXXXX, and select update driver software. Point the Browse button to the Xiaomi folder with your edited android_winusb.inf file in it, and click next. Windows won't like the unsigned driver and will give you a warning, but force feed it anyway.

Boom, the driver should install more or less automatically at that point, and your Device Manager will show a new device folder at the top of the tree, "Android Devices", and within that, "Android Composite ADB Interface".

Now if you've already installed Minimal ADB & Fastboot, when you type "adb devices", your arter97 Mi Pad 4 should show up without any trouble.

It would be great if the device showed up in the Windows or Ubuntu file managers, but I suspect that problem follows from the mandatory f2fs file system with the new kernel. I can get around that issue with adb push & pull commands, although it's a little more clunky.