rooting ( after unlocking bootloader)

[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

 

[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.

 

[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

 

[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

 

[flroots]

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

Thanks

 

[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.

 

[pjottrr]

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.

hmm, nicely spotted, i'll change that in the OP.

The other thing is that my patched file was named: magisk_patched_IuSnj.img

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.

 

[Leroy_Sparks]

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.

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.

 

[halliessed]

So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware

I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums

1 ) Download the latest Android 10 factory image for your device ("see this guide on where to find it.

2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.



3 ) Download latest Magisk Manager application on your phone and install it :
Link

4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update

5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).

7 ) Reboot your phone to fastboot by typing adb reboot bootloader

8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"

9 ) When i'ts done, reboot by typing fastboot reboot

10 ) Open your Magisk Manager app and check if everything is good, and it should be

extra info:

I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.

good luck to you all

Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.

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.

 

[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)

...the file's name is magisk_patched.img edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img...

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)

...flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"...

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...)

...I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12 but i went with it, and it was fine...

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.

 

[pjottrr]

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)

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.

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)

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.

pjottrr said:
...flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"...

That's it?

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....)

 

[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!

 

[KalenJr]

Hello, This method can be used on Android 11 Stock rom?

 

[Onoitsu2]

8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"

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.

 

[pjottrr]

Hello, This method can be used on Android 11 Stock rom?

you allready have android 11?
i'm still waiting for that update

 

[pjottrr]

Hello, This method can be used on Android 11 Stock rom?

according to what i found on rooting android 11 this method should work .
the process is exactly the same

 

[KalenJr]

you allready have android 11?
i'm still waiting for that update

Yes, I had already upgraded to 11. The method works very well Guys. Thanks.

 

[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 ...

 

[Jb122894]

Moto G Power 2020 users on android 10 UPDATED INSTRUCTIONS
0. backup your phone. seriously.
1. download minimal "adb & fastboot", extract and install.
2. unlock bootloader on Motorolas website. very simple with their online instructions.
3. download Rescue and Smart Assistant from the internet for your PC
4. Click rescue and it will save your exact correct firmware (don't try to find your firmware online or you will get an inactive screen!) - clicking rescue will simply download your software and will not affect the phone.
5. extract the Zip file with your firmware and put ALL those files into your adb folder (it saved to my program files) yes boot.img and fastboot.exe are going to be in the same folder
6. drag and drop boot.img onto your phone.
7. go to your phones internet browser and google magisk manager, and download the most up to date version (very important, do not use an outdated one as suggested on this video - our phone is slightly different.) Allow unknown sources to install - it will prompt you during the download
8. open the app, click install on the top right. select the boot.img you transfered to the phone on step 6
9. it will save a new patched version of the boot.img on your phone. It will be named Magisk_patched-XXXXX-XXXXXXXXX.img
10. move that file from your phones internal storage and transfer it into your adb folder on your PC.
11. delete boot.img from that folder (didnt work with boot.img and masgisk_patched-XXXXX-XXXX files both saved in the folder for me)
12. connect phone to PC
13. inside of your adb folder in your file explorer, type cmd into the search bar and hit enter
14. put your phone into the correct mode by powering phone off. then holding vol down and power until you see the android robot with his stomach open. you can release the buttons now
15. type into cmd fastboot flash boot magisk_patched-XXXXX-XXXXXX.img and hit enter wait for it to say finished
16. hit the power button on your phone and let it boot. If it gets stuck on the blue/yellow M screen (bootloop) simply hold the vol down and power button until you get to the robot screen. plug into PC. open rescue and smart assistant and click rescue. It will fix it.

Sincerely - someone who bootlooped and made touch screen inactive 10 times. Learn from my mistakes.

[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3

15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...

xdaforums.com

https://xdaforums.com/t/unlocking-bootloader.4062795/

https://xdaforums.com/t/rooting-after-unlocking-bootloader.4062873/

 

[chancerlane]

(Pasting from a less active fourm) I have an unlocked (US) moto g power (2021) with the model number XT2117-4 What firmware should I use? None of the ones in https://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/ match my model number? Should I just use it regardless or is there a place where I can get my model number's firmware