TWRP Builder For Moto XT2215-4

dwp
Newbie

4

26-07-2024, 08:31 PM

#1

Hello and thanks for the idea of an automated builder for TWRP for my device. Most of this is above my pay grade, so using an automated mechanism is perfect!

My device (Moto XT2215-4, 2022 Stylus 5G) uses a Qualcomm Snapdragon 6375. The Device Info HW app from Play Store reports that the touchscreen is NVT-ts and it would appear from here that the name of its .ko file might be novatek-nvt-ts.ko and the screen resolution is reported as 1080x2460.

I have tried 2 builds from your system using the attached boot.img file (actually, it is not attached as it is too large and is rejected - even if zipped): the first did not specify touchscreen info, in the the second I entered novatek-nvt-ts.ko. After downloading the file, I put my device into bootloader mode and, from my desktop PC, issued fastboot boot c:twrp-boot. In both cases, the device rebooted and I saw the main TWRP screen. Holy cow, that is great!

However, in both cases, there was no response to the touchscreen at all. So I could not try to go any further and had to force-reboot the system using the power/volume-down keys.

If you have any suggestions, I would love to hear them.

BTW - I did the same thing with the TWRP supposedly for this phone found here. In that case, the touchscreen was responsive and some things "worked" kind-of. But most everything did not.

Thanks again for this brilliant and helpful idea!

hovatek
Administrator

49,774

27-07-2024, 10:37 AM

#2

(26-07-2024, 08:31 PM)dwp Hello and thanks for the idea of an automated builder for TWRP for my device. Most of this is above my pay grade, so using an automated mechanism is perfect!
...

There are two ways to fix touch issues
1. Specify touch driver names
2. Use patch.zip to copy over touch drivers from vendor > firmware directory.

You could do both just to be sure.

The first thing to do is identify the touch drivers.
If your phone is rooted then navigate to vendor folder using a root file manager and copy out all its contents to your PC. I suspect your touch driver would have the name "novatek" in it since the blanket name is "NVT-ts".

If your phone isn't rooted then you have to extract the vendor.img or super.img (to get the vendor.img) and locate the drivers accordingly.

Fixing Touch
Search for "novatek". Once you identify the files with novatek in the names, you list out the names separated by space if more than one e.g

Code:

novatek_ts_1.ko novatek_ts_2.ko

The above is just an example.

You would specify the above under Touch drivers in our tool

Next, you create a folder named vendor and another folder inside the vendor folder named firmware. You copy the files with novatek in the name located in stock vendor > firmware into the firmware folder so you have something like:

Code:

vendor > firmware > touch driver files

As a fall back (for those using GSI or have system > vendor > firmware) you create another folder named system (at the same level as vendor) and copy the vendor folder into the system so you have something like:

Code:

vendor > firmware > touch driver file 

system > vendor > firmware > touch driver file

You then select both the system and vendor folder, right-click and choose Send to > Compressed and name the file patch

When uploading your boot image, you also select the patch.zip i.e you select both files at the same time.

Hope that helped.

This post was last modified: 31-07-2024, 09:45 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

hovatek
Administrator

49,774

27-07-2024, 10:38 AM

#3

(26-07-2024, 08:31 PM)dwp things "worked" kind-of. But most everything did not.

According to the tree they used, for touch drivers, you would input

Code:

csot_novatek_ts_fw.bin csot_novatek_ts_mp.bin tianma_novatek_ts_fw.bin tianma_novatek_ts_mp.bin tm_novatek_ts_fw.bin tm_novatek_ts_mp.bin

For patch.zip, you would use [ Login to download]

This post was last modified: 27-07-2024, 12:05 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

dwp
Newbie

4

27-07-2024, 04:08 PM

#4

Hello again. I cannot thank you enough for this tool and your help with it.

I checked in /vendor/firmware on my device and found all of these files: csot_novatek_ts_fw.bin csot_novatek_ts_mp.bin tianma_novatek_ts_fw.bin tianma_novatek_ts_mp.bin tm_novatek_ts_fw.bin tm_novatek_ts_mp.bin

I then used your tool to re-build a TWRP boot image and pasted-in all the above file names. Sadly, the result was no more useful as the touchscreen was again not at all responsive. I will try again after zipping up the various files as mentioned above.

This is so great! Thanks

dwp
Newbie

4

27-07-2024, 04:28 PM

#5

Well adding the supplied patch file to the uploaded boot.img in the automated build (rPW1Q3obvdR9z0q9282A) along with the list of file names still does not result in a responsive touchscreen. I guess I am just stuck! That's too bad, really. Thanks again.

hovatek
Administrator

49,774

27-07-2024, 04:33 PM

#6

(27-07-2024, 04:08 PM)dwp Hello again. I cannot thank you enough for this tool and your help with it.

I checked in /vendor/firmware on my device and found all of these files: csot_novatek_ts_fw.bin csot_novatek_ts_mp.bin tianma_novatek_ts_fw.bin tianma_novatek_ts_mp.bin tm_novatek_ts_fw.bin tm_novatek_ts_mp.bin

I then used your tool to re-build a TWRP boot image and pasted-in all the above file names. Sadly, the result was no more useful as the touchscreen was again not at all responsive. I will try again after zipping up the various files as mentioned above.

This is so great! Thanks

Please provide your Work ID so I can also check the changes.
by the way, are you using a GSI?
Edit seen rPW1Q3obvdR9z0q9282A
Are you using a GSI?

This post was last modified: 27-07-2024, 04:34 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

hovatek
Administrator

49,774

27-07-2024, 04:43 PM

#7

I've triggered a rebuild for rPW1Q3obvdR9z0q9282A so re-download and try.
If still no touch then there's another Mod we could try

dwp
Newbie

4

27-07-2024, 06:05 PM

#8

Thanks so much once again. Sadly, the rebuild gets no further.

I had to look up what is GSI. I think it means that I am using a standard, AOSP Android OS. If that is the case, I do not think so. The ROM, other than being rooted with Magisk and with LsPosed installed, is stock that came with the phone - Android 12. As such, I believe the kernel code and info (if one were going to try and build TWRP themselves - perhaps above my pay grade) might be one of the two seen here:

https://github.com/MotorolaMobilityLLC/k...issues/420

My guess, since I am on Android 12, not 12.1 would be the R1 version. But I am not sure. As you can see in the thread, I have asked. But so far, no response to my query.

Thanks very much indeed!

hovatek
Administrator

49,774

27-07-2024, 06:51 PM

#9

(27-07-2024, 06:05 PM)dwp Thanks so much once again. Sadly, the rebuild gets no further.

I had to look up what is GSI. I think it means that I am using a standard, AOSP Android OS. If that is the case, I do not think so. The ROM, other than being rooted with Magisk and with LsPosed installed, is stock that came with the phone - Android 12. As such, I believe the kernel code and info (if one were going to try and build TWRP themselves - perhaps above my pay grade) might be one of the two seen here:

https://github.com/MotorolaMobilityLLC/k...issues/420

My guess, since I am on Android 12, not 12.1 would be the R1 version. But I am not sure. As you can see in the thread, I have asked. But so far, no response to my query.

Thanks very much indeed!

I've sent you a PM for a private chat

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

View a Printable Version

Users browsing this thread:
1 Guest(s)

Find us

Call us

Mail us

Useful Links

Actions