[Please help] Motorola Kansas (MT6835) TWRP Development - Device Tree Request
[Please help] Motorola Kansas (MT6835) TWRP Development - Device Tree Request
18-07-2026, 03:38 AM
Hello Hovatek Team,
First, thank you for providing the Online TWRP Builder.
I recently used the builder to create a TWRP-based `vendor_boot.img` for my Motorola Kansas (MT6835) running Android 16. The recovery successfully boots into TWRP, which was a great starting point for development.
Since then, I have been continuing development on my own. I have been unpacking and analyzing the stock and generated images, comparing ramdisks, investigating touchscreen and display issues, documenting findings, and maintaining a GitHub repository for the project.
### Current Status
* TWRP boots successfully
* Recovery environment loads
* Touchscreen is not working yet
* Display rendering is distorted/fuzzy
* Development and testing are ongoing
I understand the Online TWRP Builder generates the files needed to build the recovery. I was wondering if it would be possible to obtain the generated device tree, or any portion of it, that was used during the build process.
My goal is not simply to obtain a working image, but to continue improving the recovery from source, create a proper device tree for the Kansas platform, and contribute to further development for this device.
If sharing the complete device tree is not possible, any guidance, recommendations, or partial files that could help with continued development would be greatly appreciated.
Thank you for your time and for providing the tools that made this project possible.
GitHub: OGDR
Project Repository:
https://github.com/OGDR/TWRP-VENDOR-IMG
Best regards,
Erickk
19-07-2026, 05:15 PM
(18-07-2026, 03:38 AM)Erickk .. I was wondering if it would be possible to obtain the generated device tree, or any portion of it, that was used during the build process.
...
Hey Erickk,
Thanks for trying our tool.
Unfortunately, we don't share the device tree. The only exceptions are:
1. During a Private Support session, if releasing the device tree would aid the client's work
2. Selected community projects we choose to support
Fixing the touch issue shouldn't be difficult.
If you're using our builder, then you need to add the touch driver file(s) to the device tree via a patch.zip (they're usually .ko files), then insert the names (separated by spaces) in the touch driver(s) part of the builder.
If you wish to patch the generated TWRP manually, then you could edit the init.rc, other .rc files or a shell script and add the insmod command to load the touch drivers. This can also be done using
Code:
adb shell insmod /path_to_module/module_name.koThe ADB shell method a quick way to test touch drivers. You should also keep your eyes on the TWRP logs for hints on missing touch drivers/modules.
Speaking of the display issue, look between the TARGET_RECOVERY_PIXEL_FORMAT flag and swapping the graphics_drm.cpp in /bootable/recovery/minuitwrp
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
20-07-2026, 04:35 AM
(19-07-2026, 05:15 PM)hovatekHello,(18-07-2026, 03:38 AM)Erickk .. I was wondering if it would be possible to obtain the generated device tree, or any portion of it, that was used during the build process.
...
Hey Erickk,
Thanks for trying our tool.
Unfortunately, we don't share the device tree. The only exceptions are:
1. During a Private Support session, if releasing the device tree would aid the client's work
2. Selected community projects we choose to support
Fixing the touch issue shouldn't be difficult.
If you're using our builder, then you need to add the touch driver file(s) to the device tree via a patch.zip (they're usually .ko files), then insert the names (separated by spaces) in the touch driver(s) part of the builder.
If you wish to patch the generated TWRP manually, then you could edit the init.rc, other .rc files or a shell script and add the insmod command to load the touch drivers. This can also be done using
Code:adb shell insmod /path_to_module/module_name.ko
The ADB shell method a quick way to test touch drivers. You should also keep your eyes on the TWRP logs for hints on missing touch drivers/modules.
Speaking of the display issue, look between the TARGET_RECOVERY_PIXEL_FORMAT flag and swapping the graphics_drm.cpp in /bootable/recovery/minuitwrp
Thank you for the suggestions and guidance.
I have continued investigating the touchscreen issue and identified the touchscreen as NVTCapacitiveTouchScreen. The corresponding kernel module appears to be nova_0flash_mmi_v3.ko, with references to novatek,NVT-ts-spi in the device tree.
At the moment, I am rebuilding my test environment. As soon as I have more time available, I plan to follow your suggestions regarding loading the touchscreen driver module in recovery and investigating the display configuration for the fuzzy/distorted rendering issue.
You also mentioned private support in relation to the project. I am not familiar with the private support process, so could you please explain how I would go about requesting it if needed?
Thank you again for your assistance and for taking the time to review the project.
Best regards,
Erick
20-07-2026, 08:04 AM
(20-07-2026, 04:35 AM)Erickk ...
You also mentioned private support in relation to the project. I am not familiar with the private support process, so could you please explain how I would go about requesting it if needed?
..
Private Support is our paid consultancy service (https://www.hovatek.com/remote)
You can send us an email requesting Private Support. It's billed hourly (minimum of 1 hour) or on a project basis; client's choice.
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)