[URGENT/CRITICAL] OnePlus 6T (fajita) Aftermarket Display: Touch & USB Fails Across All Builds (Request for Single Pre-Patched Boot.img)

[yottabytesystem]

Hello NetHunter Pro Team, and specifically @Shubhamvis98 (Lead Contributor),
​I am reaching out regarding a CRITICAL and persistent hardware-related issue on my OnePlus 6T (fajita) device that has an aftermarket display replacement.
​The Problem (Universal and Deeply Rooted):
Despite successful NetHunter installation and boot, the touchscreen is completely unresponsive upon reaching the login screen. I want to emphasize that, based on my research, this issue is universal and has affected every user with a replaced display since the very first NetHunter Pro builds for the OnePlus 6T.
​Exhaustive Troubleshooting Performed:
I have dedicated significant time to completely wipe and re-flash the system, including various base Android versions. I have performed the following rigorous steps:
​I have clean-flashed NetHunter Pro after preparing the device with base OxygenOS versions of Android 9, 10, and 11. The touch failure is consistent on every single NetHunter installation.
​I meticulously installed different custom kernels (like Franco Kernel and Radioactive Kernel) specifically verified to be compatible with OnePlus 6T (fajita) / Android 11 (LOS 18.1). None of these custom kernels resolved the touch issue.
​Critically, not only does the touch fail, but external input devices (USB keyboard/mouse via OTG) also fail to function. This prevents any form of terminal access for manual fixes.
​The Underlying Cause and Final Request for Easiest Solution:
It is clear that the solution lies in resolving a missing firmware issue (files like a630.mdt, modem.mdt etc., needed for touch/USB initialization) within the boot image.
​Given that I have exhausted all standard flashing and kernel methods, my PRIMARY AND URGENT REQUEST is for the simplest possible fix:
​I request a single, pre-patched boot_fajita.img file. This file should be specifically configured to load the necessary aftermarket display and USB firmwares. I need to be able to flash this single file in Fastboot mode (fastboot flash boot file.img) to immediately resolve both the touchscreen and USB input issues.
​I believe this single-file solution, similar to the specialized boot files provided for the beryllium aftermarket displays, is the only practical way forward.
​Thank you for your invaluable work and for considering this request for a ready-to-flash patch.
​Best regards,

[Shubhamvis98]

Hi @yottabytesystem,
Thanks for the detailed report. I need to clarify a few points.

This is a community project. I cannot buy or test every device or hardware variant. All builds are tested only on OEM/original hardware.
Aftermarket display panels are not supported. There are many third-party panels in the market, and vendors do not provide drivers or technical details, making proper support impossible.
The comparison with beryllium is incorrect. Beryllium has two OEM display variants (EBBG and Tianma). The fix there was only switching between existing OEM touch drivers.
I cannot confirm that this is a “missing firmware in boot” issue. If a third-party panel needs different drivers/firmware, those must come from the panel vendor.

NetHunter Pro or any other Linux distribution targets OEM hardware only. If someone can provide proper kernel drivers or documented changes for a specific panel, patches can be reviewed.

And to use usb gadgets, you should try with externally powered usb hubs.

[Shubhamvis98]

forget to mention, did you try to place the firmware files manually in the rootfs before first boot?

[yottabytesystem]

Hello @Shubhamvis98,
​Thank you again for your patience and for confirming the limitations regarding aftermarket hardware. I understand that OEM hardware is the priority.
​I have compiled the answers to your follow-up questions and found a potential solution that might expedite the fix:
​1. Response Regarding Manual Firmware Placement
​Regarding your question about placing files before first boot:
​"No, I did not attempt to place the firmware files manually in the rootfs before the first boot."
​My intention was to try this, but I could not confirm two crucial pieces of information:
​The specific touch firmware files needed (their names and source).
​The precise target path inside the NetHunter rootfs (e.g., /vendor/firmware/).
​If you can confirm the exact folder path, I will immediately attempt to locate the files and test this method while in recovery mode and report back. This would rule out the simple "missing file" theory.
​2. Evidence Suggesting a Kernel/Driver Patch is Possible
​While you stated that a simple switch like the Beryllium fix might not apply, I found community evidence suggesting that a specific kernel patch does exist for third-party panels. This confirms that the fix might be code/driver-related, not just firmware sourcing.
​Please review this XDA thread for the ImageBreaker Kernel, where users reported success with aftermarket displays:
XDA Link:

https://xdaforums.com/t/kernel-january-1-imagebreaker-kernel-for-oneplus-6t.3885167/

​Request: Could you please analyze the source code of this kernel (if available) to identify the specific patch/commit that addresses the aftermarket touch panel initialization for the OnePlus 6T (fajita)?
​If the required driver patch can be extracted and integrated into the NetHunter Pro kernel, it would solve the problem that has plagued aftermarket display users since the first build.
​3. The Need for USB Fix
​Finally, please remember that even if the touch issue is fixed, the external USB input (OTG) remains unresponsive, which complicates remote access. Integrating the necessary USB gadget drivers is also essential for a functional system.
​Thank you again for your time and assistance. I believe the XDA kernel link provides a promising path forward.
​Best regards.

[Shubhamvis98]

@yottabytesystem
You can check this message #118 (comment) to manually extract and place firmware files.

And regarding usb fix, I've already mentioned in multiple threads that you have to modify the dtb and use externally powered OTG cable. You can find the wiki as well on kali docs to make it work.