Hovatek Forum DEVELOPMENT Android [Please help] Made TWRP with Hotvatek Qualcomm Tool successfully but Touchscreen isn't working.
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


[Please help] Made TWRP with Hotvatek Qualcomm Tool successfully but Touchscreen isn't working.

[Please help] Made TWRP with Hotvatek Qualcomm Tool successfully but Touchscreen isn't working.

BigBlackCack
BigBlackCack
BigBlackCack
Newbie
3
04-04-2021, 05:52 AM
#1



Greetings.

I made a TWRP for my device with teh Hovatek Qualcomm Tool. It works. It boots! But the touchscreen isn't working. Can anyone point me in the right direction on what I'm doing wrong? I've tried porting some module files from a similiar build/processor that has TWRP but I've been stumped on Android 10. I'm a noobie with this so treat me with kid gloves.

Information:
Model: Moto One 5G Ace
Processor: Qualcomm 765G
Codename: Kiev
Ram: 6GB
Processing Cores: 8
Kernel Architecture armv8l
Nearest Variant: Moto One5G Plus
OS: Android 10
Read/Write Access: Yes
Firmware: Stock from RETEU
Original Firmware: MetroPCS/TMO

Links:
Firmware Repository: https://mirrors.lolinet.com/firmware/mot.../official/
Kernel Source/Device Tree: https://github.com/MotorolaMobilityLLC/k...0.Q4-40-62
Copy Of My Made TWRP and Original Files: https://www40.zippyshare.com/v/uPK30Ei8/file.html

Thanks!
X3non
X3non
X3non
Recognized Contributor
22,062
05-04-2021, 10:36 AM
#2
(04-04-2021, 05:52 AM)BigBlackCack ...

you can try the same method @ https://www.hovatek.com/forum/thread-32743.html
hovatek
hovatek
hovatek
Administrator
49,585
08-04-2021, 09:11 AM
#3
(04-04-2021, 05:52 AM)BigBlackCack Greetings.

I made a TWRP for my device with teh Hovatek Qualcomm Tool.  It works.  It boots!  But the touchscreen isn't working.  Can anyone point me in the right direction on what I'm doing wrong?  I've tried porting some module files from a similiar build/processor that has TWRP but I've been stumped on Android 10.  I'm a noobie with this so treat me with kid gloves.

Information:
Model: Moto One 5G Ace
Processor: Qualcomm 765G
Codename: Kiev
Ram: 6GB
Processing Cores: 8
Kernel Architecture armv8l
Nearest Variant: Moto One5G Plus
OS: Android 10
Read/Write Access: Yes
Firmware: Stock from RETEU
Original Firmware: MetroPCS/TMO

Links:
Firmware Repository: https://mirrors.lolinet.com/firmware/mot.../official/
Kernel Source/Device Tree: https://github.com/MotorolaMobilityLLC/k...0.Q4-40-62
Copy Of My Made TWRP and Original Files: https://www40.zippyshare.com/v/uPK30Ei8/file.html

Thanks!


This is a bug we're aware of for some devices. It stems from the process of unpacking and repacking the recovery image. Wer'e looking to find a work-around in future versions. For now, use OTG , build from source or try the Unisoc tecnique
This post was last modified: 08-04-2021, 09:20 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
BigBlackCack
BigBlackCack
BigBlackCack
Newbie
3
09-04-2021, 09:55 PM
#4
(08-04-2021, 09:11 AM)hovatek
(04-04-2021, 05:52 AM)BigBlackCack Greetings.

I made a TWRP for my device with teh Hovatek Qualcomm Tool.  It works.  It boots!  But the touchscreen isn't working.  Can anyone point me in the right direction on what I'm doing wrong?  I've tried porting some module files from a similiar build/processor that has TWRP but I've been stumped on Android 10.  I'm a noobie with this so treat me with kid gloves.

Information:
Model: Moto One 5G Ace
Processor: Qualcomm 765G
Codename: Kiev
Ram: 6GB
Processing Cores: 8
Kernel Architecture armv8l
Nearest Variant: Moto One5G Plus
OS: Android 10
Read/Write Access: Yes
Firmware: Stock from RETEU
Original Firmware: MetroPCS/TMO

Links:
Firmware Repository: https://mirrors.lolinet.com/firmware/mot.../official/
Kernel Source/Device Tree: https://github.com/MotorolaMobilityLLC/k...0.Q4-40-62
Copy Of My Made TWRP and Original Files: https://www40.zippyshare.com/v/uPK30Ei8/file.html

Thanks!


This is a bug we're aware of for some devices. It stems from the process of unpacking and repacking the recovery image. Wer'e looking to find a work-around in future versions. For now, use OTG , build from source or try the Unisoc tecnique

There are no fstab files so the Unisoc techique doens't work. Half the files mentioned in that do not exist on Android 10. I'll try building from source.
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram