[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.
(04-04-2021, 05:52 AM)BigBlackCack ...
(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!
(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