yashsingh1/xdaforums huggingface dataset:
[Moto G Power Guides, News, & Discussion] pjottrr:
Well, first of all, it looks like you somehow used the wrong boot.img to patch it. i think you used one that didn't match your exact firmware, and thus, you lost touch functionality. ( you are not the first to loose touch with the wrong boot image) .... but of course i could be wrong....

So the best course of action is figure out ( or try a few) from the lolinet mirrors ( see this tread for links and help finding the firmware)

if you have no clue which firmware you are using the best course of action is get an otg cable so you can at least connect a keyboard/ mouse and look at the firmware currently installed.

when yuou found the proper version, download it from lolinet, and try that boot image and you should be fine :)
[Moto G Power Guides, News, & Discussion] cnoevl21:
I dont see how i could have used the wrong firmware. I connected phone to lmsa and downloaded it. thats what i used to do everything.

This is the file name: SOFIA_RETAIL_QPMS30.80_51_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml

and i used the boot.img from this folder
[Moto G Power Guides, News, & Discussion] Drift3r:
I encountered the same issue when I first tried to unlock the bootloader and root my phone.

IMHO, get your image directly from Motorola through the LSMA app. This app can rescue your phone and it downloads the correct uncompressed oem image for you.

https://www.motorola.com/us/rescue-and-smart-assistant/p
[Moto G Power Guides, News, & Discussion] cnoevl21:
Is used the lsma app to get it this time around. That'd why I'm so confused.

And now lsma won't connect to my phone anymore.
[Moto G Power Guides, News, & Discussion] cnoevl21:
How were you able to connect to LMSA after screwing up the rooting process? Because I can't seem to. I think the usb debugging is set to transfer file mode and that may be why its not connecting to LMSA. But since I have no touch screen, I have no way of changing it.
[Moto G Power Guides, News, & Discussion] Drift3r:
It was a new phone so I rescued it because I did not have anything of value on it. After that I used the boot.img that was downloaded through the LSMA app to root my phone.

Recently, if you saw my post, I needed to unrooted my phone to do a android update. I used the original stock boot.img to unroot it. I then downloaded the updated version of the oem stock image using LSMA and I used that image's newer boot.img to root my phone again.
[Moto G Power Guides, News, & Discussion] cnoevl21:
Wish it was that easy for me. I can't get rescue on LMSA to work. Get an error message about firmware. So can't go thru the rescue process
[Moto G Power Guides, News, & Discussion] pjottrr:
Have you verified on your phone that that is indeed the correct rom? maybe somewhere a bug in lmsa caused it to give you the wrong rom? i wouldn't know any other reason that your boot.img doesn't have touch , there is , somehow something wrong. i am curious to know what the solution / cause of this is

what i do see is that if i google this image i see an update on 2020-06-09, came out as QPMS30.80-51-3

and what you got from lmsa is ....51-8 , so maybe lmsa just downloaded the latest available image , but since you only used the boot.img .... maybe your current installed rom is below the 51-8 ?

edit: 2020-10-30 was the date .8 was released
[Moto G Power Guides, News, & Discussion] rafe83:
I tried to flash the stock boot image via fastboot to unroot, but I keep getting an "cannot determine image filename" error. Did I do something wrong?
[Moto G Power Guides, News, & Discussion] pjottrr:
without knowing what you did, we can only wild guess what went wrong, but i'll try anyway :)

it should be as simple as:

1 put the boot.img in the fastboot directory ( i have it on c:\fastboot )

2 Open command promt and go to directory c:\fastboot

3 type command: fastboot flash boot boot.img ( or fot testing , 1 time boot: fastboot boot boot.img )

if that is what you did... .and take note, if you are in fastbootD mode i'm not sure the procedure is the same, but normal fastboot should work

if this wild guess of mine corresponds to what you did, i have no clue on what went wrong, maybe then share a few images....

edit: made an assumption about fastbootd. Corrected
[Moto G Power Guides, News, & Discussion] pjottrr:
i f=ound a post someone trying to do the recovery in the same way, he figured out:

solved it! i was missing the command fastboot flash "recovery" keyword before the recovery name!
[Moto G Power Guides, News, & Discussion] rafe83:
Ok thanks. I will give it a try when I get home. I apologize. This fastbootD is kind of new to me and that's coming from someone that has been rooting phones since my samsung S3 lol.
[Moto G Power Guides, News, & Discussion] haanjamin:
Did you end up figuring this out?

I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.

Oh and LMSA can't rescue... key information cannot be read from device.

I'd appreciate any help. Thanks.

UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.

UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.

UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
[Moto G Power Guides, News, & Discussion] pjottrr:
I'm assuming here:

So a decent solution would be to update the phone first ( touch or no touch) , if no touch and auto update, just use an otg cable, and manually update the phone ( over OTA?) . After that the patching should work normally again....

Did you see a change in LMSA between your update 1 and 2 ? ( not erroring out anymore )
[Moto G Power Guides, News, & Discussion] pjottrr:
same goes for me , the fastbootD thing is still something i'm not using , since it is confusing.

we have both, but the whole rooting and patching could be done without fastbootD on this phone, so i haven't found any use for it. ( yet)
[Moto G Power Guides, News, & Discussion] haanjamin:
LMSA still gave me the same error until the phone had updated and I had -8 boot loaded. Yes, I think an OTG would work until the update is installed, or the correct boot (-5). This was on a brand new phone and I actually did check for system updates before I started trying to root. It notified me an updated security patch was installed but said nothing about downloading new firmware so I figured I was good to go with what LMSA downloaded.
[Moto G Power Guides, News, & Discussion] cnoevl21:
unfortunately, when i tried to manually flash stock firmware, i am now stuck in a bootloop. goes from the moto splash screen to the bootloader unlocked message and loops from there.

ive tried going into recovery and doing a factory reset. ive tried manually flashing 3 different firmwares. cant get out of the bootloop.
[Moto G Power Guides, News, & Discussion] mingkee:
Did you try LMSA rescue?
[Moto G Power Guides, News, & Discussion] cnoevl21:
I cant connect to it. when i try i get a message saying my firmware doesnt match.
[Moto G Power Guides, News, & Discussion] cnoevl21:
To those who have been following along this past week with all my downfalls. I have finally fixed everything. To help anyone else the fell down the same rabbit hole as me. This is what i did to fix things:

UPDATE: ive gotten everything sorted. no more bootloop. touchscreen working. connecting to lmsa. and rooted. Thank you for all the responses.

I think what happened is that when i started all this i was not using the latest adb. That seemed to not be an issue for unlocking bootloader, but a major issue for rooting. When i tried to root,i got the no touchscreen. So I followed directions and went to manually flash the stock firmware. I didnt know how to do this and couldnt find instructions for the g power. but did find instructions for the g8 power and assumed it would be the same...its almost the same, but not, so i got the bootloop.

These are the instructions:

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash vbmeta vbmeta.img

fastboot flash radio radio.img

fastboot flash bluetooth BTFM.bin

fastboot flash dsp dspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash recovery recovery.img

fastboot flash super super.img_sparsechunk.0

fastboot flash super super.img_sparsechunk.1

fastboot flash super super.img_sparsechunk.2

fastboot flash super super.img_sparsechunk.3

fastboot flash super super.img_sparsechunk.4

fastboot flash super super.img_sparsechunk.5

fastboot flash super super.img_sparsechunk.6

fastboot flash super super.img_sparsechunk.7

fastboot flash super super.img_sparsechunk.8

fastboot flash super super.img_sparsechunk.9

fastboot flash super super.img_sparsechunk.10

fastboot flash super super.img_sparsechunk.11

fastboot flash super super.img_sparsechunk.12

fastboot flash super super.img_sparsechunk.13

fastboot flash super super.img_sparsechunk.14

fastboot flash super super.img_sparsechunk.15

I added' fastboot flash super super.img_sparsechunk.15', because the g8 power only has 14 sparsechunks and thats why i kept getting the bootloop. very stupid mistake that was driving me nuts! Once i added that 15th line the phone booted up and touchscreen worked again.

Then i installed magisk manager. Took the boot.img file from my stock rom and put it on my phone. back in magisk i clicked on install a patch file, chose the boot.img and created a magisk_patched.img which i put back into the adb folder i previously used to flash the firmware.

Then went back to fastboot and flashed the magisk_patched.img and the phone is now working and rooted...THANK GOD
[Moto G Power Guides, News, & Discussion] pjottrr:
Glad you figured it out,

would you like to elaborate on what's different in the g8 power versus the gpower? then i'll add the info to my first post so the chances are smaller that more people run into it. Since i own the European version i have no idea what is different with the g power
[Moto G Power Guides, News, & Discussion] cnoevl21:
its seems that this 'fastboot flash super super.img_sparsechunk.15' is not in g8 power firmware. the g8 has sparsechunk 0-14 only.
[Moto G Power Guides, News, & Discussion] pjottrr:
ah ok, i misinterpreted, sorry for that.

I thought you meant the rooting process was differently, but you mean the recovery procedure is slightly different.

This would be useful for a recovery guide , if there will be one.
[Moto G Power Guides, News, & Discussion] vadimfe:
Hi! I have Mo G8 Power (europian variant=sofiar). My question is if I unlock bootloader, can I install TWRP via fastboot and then without patching boot.img simply flash latest Magisk zip in order to get rooted device!

Thanks in advance! And sorry for my English!:)

P.S. I ask 'cause I 've read this in a Telegram dedicated to Moto G8 Power.
[Moto G Power Guides, News, & Discussion] pjottrr:
I'm not sure if what you are asking is an option since this whole process is different in android 10 , also Twrp is more optional nowadays. I haven't heard of anywone just flashing mask the old way. ( but maybe it is possible)

If you are not planning on switching rom, you don't need TWRP at least,

and the patching / unpatching of the boot image is also easily done.

If you really want to install magisk via twrp, can you share some sources / info you found out via telegram so we could check it out?
[Moto G Power Guides, News, & Discussion] vadimfe:
https://t.me/MotoG8Power/5841

That is official Telegram channel for Motorola G8 Power from where I took info.

Mabe exist the way to confirm or not confirm this info?

Because is much more simple!

Thanks in advance! Sincerely yours Vadim.
[Moto G Power Guides, News, & Discussion] kuzo:
yes, on g8 power it is easy, just install twrp and then magisk flash...

I have the same one and I did it like this

commands

fastboot flash recovery twrp-3.4.0-0-sofia-test9.img

fastboot flash recovery_a twrp-3.4.0-0-sofia-test9.img

fastboot flash recovery_b twrp-3.4.0-0-sofia-test9.img

fastboot reboot fastboot

https://drive.google.com/file/d/19mqtxGAhvGfVWMu_4wvm4QK9wwlgjGUL/view?usp=sharing
[Moto G Power Guides, News, & Discussion] vadimfe:
Hi! Thanks a lot for your complete and fast answer! I have only 2 questions. First of all I need fastboot or fastbootd to execute these commands? Maybe stupid question but I noob whith this. And second one if I get OTA of I went something wrong, can I connect to LRSA(Resque Assistant Tool Lenovo) and flash full rom with stock recovery or with unlocked bootloader it is impossible?

Thanks in advance for your answer! And sorry for my bad English. Sincerely yours Vadim.

And another stupid question is last command "fastboot reboot" for rebooting into system? And without to repeat "fastboot" 2 times?
[Moto G Power Guides, News, & Discussion] kuzo:
Sorry it took me so long... I make it as easy as possible, you just have to extract the file that I leave you below, and then connect your phone in fastboot mode to the pc and double clip the file #TWRP and that's it

https://drive.google.com/file/d/11tskToYn4oAWo3DzQxEtat3ucpJb8hoA/view?usp=sharing

and yes, then you can install rom stock via fastboot whenever you want with unlocked bootloader
[Moto G Power Guides, News, & Discussion] vadimfe:
Hi! Tnanks a lot for your preparation for me ! I'll try it!
[Moto G Power Guides, News, & Discussion] SomeGuy2008:
question, I just unlocked my bootloader with no issues. I used Lenovo rescue app to download "SOFIA_RETAIL_QPM30.80_63_6_8_subsidy_DEFAULT_regulatory_DEFAULT_CFC". I extracted the boot.img and patched using magisk manager. before I actually install the new patched boot.img I wanted to test it per the first post using "fastboot boot magisk_patched.img". It booted up although a little slow. but the touch screen doesnt seem to work. I cant unlock it or anything. the buttons seem to work though. is this expected? did I maybe miss a step?

its currently running QPMS30.80-51-5

NM. I did miss a step. in first post about original version matching. my bad.

Thanks

~SG
[Moto G Power Guides, News, & Discussion] myasus:
Can anyone help to upload the original or modified boot.img for QPMS30.80-51- 8? Did not check before flashing :( Downloading from lolinet is too slow and kept failing. Thanks.

Edit: Nevermind, find another download site: https://t.me/s/motoupdatestracker?q=#sofia and got my touch back :)
[Moto G Power Guides, News, & Discussion] jim2029:
Thank You for this guide. I haven't rooted a Phone since the DroidX phone. I stumbled a little bit, but in the end, I have root! If I can do it, anyone can do this.
[Moto G Power Guides, News, & Discussion] flroots:
I have rooted my Moto G Stylus (XT2043-4) without issues. Now if I want to receive future OTA updates, must I unroot? If so, what's the best method? Can I just flash the stock (unpatched) boot.img or is it more complicated?

Also since the magisk root is systemless, does that mean I will receive OTA announcements (even if I can't install them)?

Note: I understand this is the G Power forum not the G Stylus forum, but I haven't received a reply there. Hope you can help
[Moto G Power Guides, News, & Discussion] pjottrr:
You will receive notifications, but the update will fail to install.

After you went back to the original boot.img you can install the update, download the new rom Via lmsa, repatch the new boot image and flash via fastboot
[Moto G Power Guides, News, & Discussion] flroots:
Thanks
[Moto G Power Guides, News, & Discussion] Leroy_Sparks:
I successfully performed rooting using this thread (magisk v21.4). Two minor observations:

In the original post there is mention of magisk_patched.bin I assume this is a typo as the patched file has a .img extension.

The other thing is that my patched file was named: magisk_patched_IuSnj.img I didn't change it, but tested it by booting it (not flashing it) using this filename. It worked, so I then flashed it (again using the full filename).

Two minor points, but this may give some clarification to anyone who saw this and was unsure - we always want to follow procedures EXACTLY to avoid screwing something up.
[Moto G Power Guides, News, & Discussion] pjottrr:
hmm, nicely spotted, i'll change that in the OP. :)

i think that's new in the latest magisk, i haven't seen that earlyer at least.

But i'm glad you found help in the topic with rooting, have fun with it .

edit; and thnx for pointing out the mistake i made in the OP. You are the first to notice it.
[Moto G Power Guides, News, & Discussion] Leroy_Sparks:
I hope it helps anyone else in the future who is as easily confused as I am.

I think the patched file name thing could be new. I used it to patch the OEM bootloader and also on a custom ROM (Havoc). Both had a seffix in the filename (not the same letters). It's prbably good because it distinguishes one file from another.

Again, thanks for this guide, it seems every phone has it's own unique challenges in unlocking/rooting/etc.
[Moto G Power Guides, News, & Discussion] halliessed:
When my device is in the bootloader it does not show up under ADB Devices. It does show up when the phone is turned on. Whats up with this?

Edit: My immeasurable stupidity is clear. Nevermind.
[Moto G Power Guides, News, & Discussion] culiacanazo:
Thanks for your thread. Do you know anything, pertaining to this topic here of yours, whether it is doable for the g8 power lite, codenamed blackjack, aka XT-2055-2, not to be confused for any other, since we are on a MediaTek chip?

(Android 10)

a patched image from BLACKJACK_RETBR_QOD30.163-7 produced magisk_patched_Fbrjm.img, so, other than the two BR, i find no explanation from the naming (I'm, well, the phone is Mexican but the rest after retail brasil is a match which (i think?) is what matters)

That's it? Because i remember you could reboot thru the commands in huawei, then it started having to have the button combo or it would boot where it wanted (mate 10 pro, between oreo and pie, although methinks it had to do more with the loss of the boot partition...)

That's because images acquired in that manner usually just weigh however big the partition may happen to be, whereas the patched image only weighs what the actual amount of what's being used is plus the usually tiny patch on top.

Open up said stock image and you'll see.
[Moto G Power Guides, News, & Discussion] pjottrr:
i don't think it's any difference, the cpu might be different, but the process ( i guess) is the same.

there might however be something with a/b paritions , mine doesn't have that, but i beleive some us models have an a and a b boot partition.

it might as wel be the case with the light version.

i noticed the new naming as well in the last update. i think it is just random so it is getting less confusing ( what the latest magisk patched image is...) . but if you really want the answer you could dig into it by looking trough the changelog of the magisk manager.

well the most important thing is test how the boot image behaves, especially on your device. , just boot the patched boot image, and ( of cource in your case it would be:

"fastboot boot magisk_patched_Fbrjm.img"

if all works fine, you could decide to flash it, and then it is sort of permanent... ( until you want to install the next update....)
[Moto G Power Guides, News, & Discussion] creedzeppelin:
I use minimal ADB and fastboot and had zero problems with my sofia phone getting root. I've only ever had HTC phones and I've never used Magisk before, but it was so easy. Thanks a lot everyone!
[Moto G Power Guides, News, & Discussion] KalenJr:
Hello, This method can be used on Android 11 Stock rom?
[Moto G Power Guides, News, & Discussion] Onoitsu2:
I actually found it to feel smoother doing it by booting from it, for that single boot, and opening the magisk app, and letting it, re-flash it. I have fully reverted mine to stock once and tried both methods now and I dunno, maybe an alternative route, since Magisk would have the perms to install itself again, so you know it does it with latest files since it's pretty hardcore about updating itself at that time. Might be safest in case to prevent outdated files usage.

Oh yeah, this worked on the moto g power (2021) version, just got, not even a week out of the box, but did take about 3-days before could enable the unlocking option in Dev options, was blocked till then.
[Moto G Power Guides, News, & Discussion] pjottrr:
you allready have android 11?

i'm still waiting for that update
[Moto G Power Guides, News, & Discussion] pjottrr:
according to what i found on rooting android 11 this method should work .

the process is exactly the same
[Moto G Power Guides, News, & Discussion] KalenJr:
Yes, I had already upgraded to 11. The method works very well Guys. Thanks.
[Moto G Power Guides, News, & Discussion] pjottrr:
So i finally got it as well,

However, when trying to boot the patched boot image, i get stuck on a Motorola logo.

it is booting, i get the screen flicker, yet it's stuck on the moto logo after that.

If i flash back the non-patched boot.img from fastboot it works fine.

has anyone here had the same ?

i'm using:

update channel reteu

magisk manager 22.1

build number: RPE31.Q4U-47-35

update 2:

it appeared i had a module installed not compatible with android 11

so i booted into safemode ( hold volume down as soon as the phone vibrates) , then reboot the phone ( magisk modules will be disabled after a safemode boot) , i removed all modules, and i'm back :)...