[Solved]Touch screen not workiMoto G Powerng after rooting Moto G Power

Search This thread

nero075

Member
Sep 1, 2020
14
2
Apologies if I should have searched harder. My understanding is that touch screen issues like this happen when the firmware you flash isn't quite compatible with your device. I've triple checked the stuff I downloaded, and I'm not seeing how it could be that. Maybe I did something else stupid? This is my first time rooting anything.

Product/Variant (as seen in bootloader): sofia XT2041-4 64GB PVT
The boot.img I downloaded: lolinet's firmware/moto/sofia/official/RETUS/ (the august 31 one. Currently trying with the earlier one, but the download is taking forever)
Magisk version: 7.5.1

I only have a linux laptop, so the rescue and smart assistant appears to be off the table

Here's what I did:
  • Downloaded the boot.img from lolinet
  • patched it using magisk
  • flashed it using fastboot

How I flashed it:
Code:
~/Downloads$ fastboot flash boot magisk_patched.img 
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [  0.376s]
writing 'boot_b'...
OKAY [  0.069s]
finished. total time: 0.446s
I booted up after this, and I couldn't use the touchscreen. Then I noticed the boot_b thing, so I did the following to do both partitions (although I have no idea if this is what you're supposed to do):
Code:
~/Downloads$ fastboot flash boot_a magisk_patched.img 
target reported max download size of 805261312 bytes
sending 'boot_a' (12136 KB)...
OKAY [  0.350s]
writing 'boot_a'...
OKAY [  0.076s]
finished. total time: 0.425s
~/Downloads$ fastboot flash boot_b magisk_patched.img 
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [  0.370s]
writing 'boot_b'...
OKAY [  0.214s]
finished. total time: 0.584s
No dice..
Next, I tried to just use the unpatched boot.img to restore things.
Code:
~/Downloads$ fastboot flash boot_a XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img 
target reported max download size of 805259264 bytes
sending 'boot_a' (65536 KB)...
OKAY [  1.908s]
writing 'boot_a'...
OKAY [  0.696s]
finished. total time: 2.604s
~/Downloads$ fastboot flash boot_b XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img 
target reported max download size of 805259264 bytes
sending 'boot_b' (65536 KB)...
OKAY [  1.949s]
writing 'boot_b'...
OKAY [  0.525s]
finished. total time: 2.474s

once again, no dice..this time I didn't even get to the lockscreen. Just stuck on the moto logo

Any idea what I've done wrong? Would really appreciate some help with this.

Update: I tried with the other boot.img from lolinet, doesn't get to lockscreen. Then I tried a factory reset with twrp, and flashing the earlier boot.img and I got to the setup screen, but still no touch.

Update 2: I managed to get omnirom flashed, and that's working so far! I am still curious to know why the touch screen issues popped up..will be useful next time I want to flash stock
 
Last edited:
  • Like
Reactions: bleezydocta17

nero075

Member
Sep 1, 2020
14
2
Got a link by any chance? The ones I've seen are twrp related or because of the wrong firmware.

Any idea how to figure out which set is right for my phone?
 

mingkee

Senior Member
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
 

cnoevl21

Senior Member
Feb 26, 2010
529
22
OnePlus 8T
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)

Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
 

nero075

Member
Sep 1, 2020
14
2
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
 

mingkee

Senior Member
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.

Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
 

cnoevl21

Senior Member
Feb 26, 2010
529
22
OnePlus 8T
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped

when you say flash everything. is it just flashing the .img files? or literally everything?
Sorry, ive never had to manually flash before.

---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------

If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd

ill have to try this. thanks. Ive tried to just boot the boot.img and it hasnt done anything. so ill do this to try and get into fastbootd.
 

cnoevl21

Senior Member
Feb 26, 2010
529
22
OnePlus 8T
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd

Ok. ive gotten into fastbootd but have no idea what to do now. I assumed it was like flashing with regular fastboot. but when i type commands like fastboot flash boot boot.img i get a failed result no such file or directory
 

PamelaGirl

Senior Member
Jul 10, 2011
853
100
Hello friend,
Did you ever resolve your issue with the touchscreen?

I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what. :(

Please let me know of your solution.
Thank you kindly.
 

klninja

Member
Feb 3, 2021
10
0
Hello friend,
Did you ever resolve your issue with the touchscreen?

I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what. :(

Please let me know of your solution.
Thank you kindly.
hey did you fix it or something? i got the same problem, and idk what to do, can you help?
 

PamelaGirl

Senior Member
Jul 10, 2011
853
100
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
 

PamelaGirl

Senior Member
Jul 10, 2011
853
100
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
 

klninja

Member
Feb 3, 2021
10
0

PamelaGirl

Senior Member
Jul 10, 2011
853
100

PamelaGirl

Senior Member
Jul 10, 2011
853
100
Sorry I honestly cannot recall. I was so frustrated at that time, blinded to get the root to work that I did not notice.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Apologies if I should have searched harder. My understanding is that touch screen issues like this happen when the firmware you flash isn't quite compatible with your device. I've triple checked the stuff I downloaded, and I'm not seeing how it could be that. Maybe I did something else stupid? This is my first time rooting anything.

    Product/Variant (as seen in bootloader): sofia XT2041-4 64GB PVT
    The boot.img I downloaded: lolinet's firmware/moto/sofia/official/RETUS/ (the august 31 one. Currently trying with the earlier one, but the download is taking forever)
    Magisk version: 7.5.1

    I only have a linux laptop, so the rescue and smart assistant appears to be off the table

    Here's what I did:
    • Downloaded the boot.img from lolinet
    • patched it using magisk
    • flashed it using fastboot

    How I flashed it:
    Code:
    ~/Downloads$ fastboot flash boot magisk_patched.img 
    target reported max download size of 805261312 bytes
    sending 'boot_b' (12136 KB)...
    OKAY [  0.376s]
    writing 'boot_b'...
    OKAY [  0.069s]
    finished. total time: 0.446s
    I booted up after this, and I couldn't use the touchscreen. Then I noticed the boot_b thing, so I did the following to do both partitions (although I have no idea if this is what you're supposed to do):
    Code:
    ~/Downloads$ fastboot flash boot_a magisk_patched.img 
    target reported max download size of 805261312 bytes
    sending 'boot_a' (12136 KB)...
    OKAY [  0.350s]
    writing 'boot_a'...
    OKAY [  0.076s]
    finished. total time: 0.425s
    ~/Downloads$ fastboot flash boot_b magisk_patched.img 
    target reported max download size of 805261312 bytes
    sending 'boot_b' (12136 KB)...
    OKAY [  0.370s]
    writing 'boot_b'...
    OKAY [  0.214s]
    finished. total time: 0.584s
    No dice..
    Next, I tried to just use the unpatched boot.img to restore things.
    Code:
    ~/Downloads$ fastboot flash boot_a XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img 
    target reported max download size of 805259264 bytes
    sending 'boot_a' (65536 KB)...
    OKAY [  1.908s]
    writing 'boot_a'...
    OKAY [  0.696s]
    finished. total time: 2.604s
    ~/Downloads$ fastboot flash boot_b XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img 
    target reported max download size of 805259264 bytes
    sending 'boot_b' (65536 KB)...
    OKAY [  1.949s]
    writing 'boot_b'...
    OKAY [  0.525s]
    finished. total time: 2.474s

    once again, no dice..this time I didn't even get to the lockscreen. Just stuck on the moto logo

    Any idea what I've done wrong? Would really appreciate some help with this.

    Update: I tried with the other boot.img from lolinet, doesn't get to lockscreen. Then I tried a factory reset with twrp, and flashing the earlier boot.img and I got to the setup screen, but still no touch.

    Update 2: I managed to get omnirom flashed, and that's working so far! I am still curious to know why the touch screen issues popped up..will be useful next time I want to flash stock