Motorola Moto G Pure flash Magisk issue - Moto G Q&A, Help & Troubleshooting

Motorola Moto G Pure flash Magisk issue - Moto G Q&A, Help & Troubleshooting

I've got a Motorola Moto G 5G that I've successfully rooted. Thanks to the threads I've read here at XDA. But now I've got a Motorola Moto G Pure (bootloader unlocked) and I can't seem to get Magisk flashed through platform tools. Could it be that I'm flashing the wrong boot image through Magisk manager? Or is it because I'm typing the wrong commands in platform tools?? Can someone please help??

Hey I've got a Motorola G Pure and I had trouble flashing it too. I think there's something with them that makes it a bit more difficult. I flashed a Moto G Power back a few years ago with ease.
Have you already got the OEM unlocked by emailing them? Once you got the bootloader unlocked
If so the commands
sudo fastboot boot_a boot.img
sudo fastboot boot_b boot.img
(on linux only do you need the command sudo before it otherwise just run the fastboot command(
should work if you renamed your magisk boot.img and put it in the same folder as the original with all the other ROM files.
If that doesn't work that confirms that Moto G Pure takes a little more effort to flash. Please let me know if that works for you. You may want to check google or another form before trying that but I'm pretty sure that is correct.

Related

Root Moto G on Lollipop 5.0.2

Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked

n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
Click to expand...
Click to collapse
can i use with stock recovery?
thanks.

vbnoob said:
can i use with stock recovery?
thanks.
Click to expand...
Click to collapse
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta

n1c00_ said:
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta
Click to expand...
Click to collapse
My phone is unlocked bootloader with stock recovery.
Thanks.

vbnoob said:
My phone is unlocked bootloader with stock recovery.
Thanks.
Click to expand...
Click to collapse
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...

n1c00_ said:
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...
Click to expand...
Click to collapse
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.

I think I screwed phone. Being a noob I didn't realise fastboot and Bootloader screens are different. I went and use chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions link
in fastboot. After error failed now it ADB doesn't detect my phone.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>
Any advise to help me? Tried hard method going to bootload still nothing either or at least I think its nothing since this is first attempt I ever tried root my phone. Everytime I plugin in fastboot or even in normal mode the pc does detect it. But it just won't show up in adb.
Decided to try again using leocuervo1983 method for fastboot it stated as fail as well but somehow I got root even though adb still no longer detect my phone.
Edit:
Just found out fastboot doesn't use adb commands or do they? I feel stupid. I Guess there are no issues then even if failed still got root. Fastboot commands works adb doesn't work.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
TAXXXXXXXX fastboot

The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.

pfufle said:
The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.
Click to expand...
Click to collapse
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?

Xicor Yagami said:
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?
Click to expand...
Click to collapse
Yes since the recovery isn't entirely compatible with the new kernel.

pfufle said:
Yes since the recovery isn't entirely compatible with the new kernel.
Click to expand...
Click to collapse
Tried latest TWRP? same results?

Xicor Yagami said:
Tried latest TWRP? same results?
Click to expand...
Click to collapse
yep.

n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked
Click to expand...
Click to collapse
Thanks a lot! Worked like a charm using mfastboot command.

Works fine
My bootloader was however unlocked...I tried this on CM12....extract the img file from the CF-Auto root File and then flash on the bootloader mode...with mfastboot boot filename.img

The method same as that of kitkat works for lollipop too...you could made some mistake unknowingly somewhere in the middle while following the original procedure
Sent from my Moto G using XDA Free mobile app

is there any method to root moto g?
Any side effects of chainfire method?

leocuervo1983 said:
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.
Click to expand...
Click to collapse
It did'n work for me .... I ran the bat file , and when I pressed a key, it was waiting for the phone and nothing happened.
Edited:
Sorry... I forgot to unlock bootloader first.... worked fine!!! Thanks a lot!!!

[MOTO G6+] Root guide from start (pro users)

Hi,
This guide is based on my experience with a Moto G6+ RETEU XT1926-3.
And it supersedes the explanations on this thread: https://forum.xda-developers.com/moto-g6/help/root-g6-t3786379
In any case is only for experienced users! If you like to create a more user friendly guide, then contribute to it!
GUIDE:
Boot for first time (don't use your gmail user, just skip all!). Enable "developer options". Set "OEM Unlocking". Set "USB debugging".
Get your Bootloader Unlock Key from Motorola: https://forum.xda-developers.com/moto-g6/how-to/guide-unlock-bootloader-t3791238
Connect to PC with USB and Accept the connection. In the PC Shell:
"adb reboot bootloader"; "fastboot oem unlock UNIQUE_KEY" (2 times); "fastboot reboot bootloader". Afer end check that all is OK!
Insert SD-Card, and check it works!
In the PC Shell:
"adb reboot bootloader"; "fastboot boot twrp-3.2.1-0-evert.img".
When the TWRP boots --> READ-ONLY mode! Inside "Mount" select "Micro SD card" and push button "Disable MTP". Open ADB shell.
WARNING: This TWRP is an unofficial version for Moto X4! Don't flash it!
Inside the ANDROID (ADB) shell:
"dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/boot of=/external_sd/boot.img"
"dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/logo of=/external_sd/logo.bin"
Power off, extract the SD-Card and secure copy your backup!
Power on in fastboot mode. Then flash patched logo.bin (for disable unlock warning), and flash boot patched kernel:
"fastboot flash logo logo.bin"
"fastboot boot patched_boot-MotoG6+-OPW27.113-45.img"
Reboot and make the initial setup with your regular user. Check that all is OK!
Before any reboot install MagiskManager:
https://github.com/topjohnwu/MagiskManager/releases
Upgrade to lasted Magisk Beta:
- Inside the Magisk Manager "Settings", change "Update Channel" to "Beta".
- Then in the Main Magisk select "install" and "Install" the last version (v16.7) with "Direct Install".
- Reboot.
That's all! Your phone is rooted with MagiskSU, and you can install Magisk Modules! :good:
If you boot with the patched boot kernel and install Magisk with the direct mode then you will have a backup of the stock boot.img inside Magisk. Useful for OTA updates and to uninstall it. In this case points 4-7 is not required (but recomended). The backup is stored in "/data/stock_boot_XXXXXXXXX.img.gz".
PENDING: Disable dm-verity (/data encryption) for TWRP backups!
GREETINGS:
@jekyll86 for Magisk patched kernel image https://forum.xda-developers.com/moto-g6/development/guide-magisk-patched-boot-image-opw27-t3794977
@luiz_neto for patched logo https://forum.xda-developers.com/moto-g6/development/bootlogo-remove-message-unlocked-t3789155
@luiz_neto for unofficial TWRP for Moto X4 https://forum.xda-developers.com/showpost.php?p=76501832&postcount=3
@lohanbarth for Unlock Bootloader guide https://forum.xda-developers.com/moto-g6/how-to/guide-unlock-bootloader-t3791238

root for the normal g6, still nothing? I would also like to know how the tea is decrypted, Thank you
Enviado desde mi moto g(6) mediante Tapatalk

stifmaster81 said:
root for the normal g6, still nothing? I would also like to know how the tea is decrypted, Thank you
Click to expand...
Click to collapse
No at time! I don't have any G6, only G6+ that it's a very different device.
Here an idea for any that have sufficient skills and one Moto G6:
- Search for a similar device with a custom recovery (TWRP).
- Try to boot this TWRP image (fastboot boot twrp.img).
- If it works, extract the kernel to boot.img using the shell of the TWRP.
- Use some Magisk Manager tool for repack/patch the extracted boot.img.
- Try to boot this kernel (fastboot boot patch_boot.img).
- If it works, then install the Magisk Manager and patch the flash kernel.
After that, you have rooted your device! Then extract then the patched kernel and share with others. The rest of the guide will be the same with this custom kernel.

manos78 said:
No at time! I don't have any G6, only G6+ that it's a very different device.
Here an idea for any that have sufficient skills and one Moto G6:
- Search for a similar device with a custom recovery (TWRP).
- Try to boot this TWRP image (fastboot boot twrp.img).
- If it works, extract the kernel to boot.img using the shell of the TWRP.
- Use some Magisk Manager tool for repack/patch the extracted boot.img.
- Try to boot this kernel (fastboot boot patch_boot.img).
- If it works, then install the Magisk Manager and patch the flash kernel.
After that, you have rooted your device! Then extract then the patched kernel and share with others. The rest of the guide will be the same with this custom kernel.
Click to expand...
Click to collapse
Very complicated for me, I'll wait to see if someone gets something out
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 02:40 PM ---------- Previous post was at 02:35 PM ----------
To decrypt the mobile, can something be done? By command line Nexus type or something?
Enviado desde mi moto g(6) mediante Tapatalk

What is this for? i rooted my g6+ just booting this twrp and normally flash magisk zip in recovery and that was it.

CreasingMass Dev said:
What is this for? i rooted my g6+ just booting this twrp and normally flash magisk zip in recovery and that was it.
Click to expand...
Click to collapse
Well, I do in this way because:
1) This TWRP isn't for Moto G6+, instead is for Moto X4. So, if it's something wrong in the partition mapping (fstab) then you can end with a bricked device. I'm satisfied if you can do it... but you be in risk.
2) If you review my guide, you will see how to obtain a BACKUP of the "boot.img". With your method, you'll lose it. And then, how you will apply the next OTA when it comes?
In any case, it's good to discover and test more rooting methods.
Perhaps for users with the Moto G6 or Moto G6 play, this other method can help them.
Regards.

manos78 said:
Well, I do in this way because:
1) This TWRP isn't for Moto G6+, instead is for Moto X4. So, if it's something wrong in the partition mapping (fstab) then you can end with a bricked device. I'm satisfied if you can do it... but you be in risk.
2) If you review my guide, you will see how to obtain a BACKUP of the "boot.img". With your method, you'll lose it. And then, how you will apply the next OTA when it comes?
In any case, it's good to discover and test more rooting methods.
Perhaps for users with the Moto G6 or Moto G6 play, this other method can help them.
Regards.
Click to expand...
Click to collapse
ye i don't care about OTAs, rooted my device just 30mins after getting it wishing there was some treble stuff but nah, anyway i don't care about losing that, i still use my g5 plus instead of this one because of the roms, can't use moto stock Sh!t it's just useless and full of bs

CreasingMass Dev said:
i still use my g5 plus instead of this one because of the roms, can't use moto stock Sh!t it's just useless and full of bs
Click to expand...
Click to collapse
Wooh! I really hate my Moto G5+ ... 3GB or RAM is a joke from Motorola. The 4GB of RAM of the Moto G6+ is a glory! And I prefer Oreo than Nougat, in Stock with a lot of Magisk modules.

FYI,
If you rooted your Moto G6+ with this guide, and now you like to apply the June's OTA over the April firmware... then, you need to wait!
The OTA refuses to install, even if you uninstall Magisk, or boot with the stock kernel, or reflash the stock kernel.

Have same issue....
I have a Moto G6.
When submitting the string on Motorola's site, I get this;
Your device does not qualify for bootloader unlocking
Any ideas how to get around this roadblock?

worried_G6 said:
I have a Moto G6.
When submitting the string on Motorola's site, I get this;
Your device does not qualify for bootloader unlocking
Any ideas how to get around this roadblock?
Click to expand...
Click to collapse
There is no way around it. if your device is branded from Verizon or probably AT&t the bootloader is not unlockable.

Help with Installing TWRP for Moto E6

Greetings All,
I recently purchased a Motorola E6 (Model XT2005-5).
Expecting to be able to install the TWRP recovery, I unlocked the bootloader.
Based on the TWRP site, there appears to be a recovery image for just about every phone on the planet, EXCEPT the E6 :-(
After scouring the net, I found about 4 or 5 possible recovery images, as well as a LOT of dead links.
None of these images appear to work.
They either just boot the phone to the existing system, or bring up a message about 'corrupt data'.
As per recommendations ,these images were booted using the Linux command:
'fastboot boot '
rather than flashed.
I HAVE managed to flash a stock ROM image. Although it boots OK, I get a 'bad key' message when it starts.
Donno if this is significant or not.
There also seems to be some data that was NOT cleared by the stock rom installation commands.
The phone was packaged for US Cellular, and I still get the US Cellular splash screen when the phone starts.
The source for updates also seems to be from US Cellular...
There is no problem using the SIM from my phone provider.
Does anyone have a valid link to a functional TWRP for this phone?
Are there additional commands needed (other than 'boot') to possibly get the images that I have found to work?
Is there some additional ROM that needs to be erased to clear out the US Cellular data/logo?
Any other advice or suggestions are GREATLY appreciated.
Thanx.
Richard Rosa

richardrosa said:
Greetings All,
I recently purchased a Motorola E6 (Model XT2005-5).
Expecting to be able to install the TWRP recovery, I unlocked the bootloader.
Based on the TWRP site, there appears to be a recovery image for just about every phone on the planet, EXCEPT the E6 :-(
After scouring the net, I found about 4 or 5 possible recovery images, as well as a LOT of dead links.
None of these images appear to work.
They either just boot the phone to the existing system, or bring up a message about 'corrupt data'.
As per recommendations ,these images were booted using the Linux command:
'fastboot boot '
rather than flashed.
I HAVE managed to flash a stock ROM image. Although it boots OK, I get a 'bad key' message when it starts.
Donno if this is significant or not.
There also seems to be some data that was NOT cleared by the stock rom installation commands.
The phone was packaged for US Cellular, and I still get the US Cellular splash screen when the phone starts.
The source for updates also seems to be from US Cellular...
There is no problem using the SIM from my phone provider.
Does anyone have a valid link to a functional TWRP for this phone?
Are there additional commands needed (other than 'boot') to possibly get the images that I have found to work?
Is there some additional ROM that needs to be erased to clear out the US Cellular data/logo?
Any other advice or suggestions are GREATLY appreciated.
Thanx.
Richard Rosa
Click to expand...
Click to collapse
There doesn't seem to be a working custom recovery for this device.
Moto devices are often referred to by development name or codename.
Your device should be SURFNA, look for that name on the bootloader screen
or
Code:
fastboot getvar product
I suggest following this thread for twrp
[ABANDONED] TWRP Dirty Port for Moto E6
https://www.getdroidtips.com/twrp-recovery-motorola-moto-e6/ None of my recoveries have worked for the E6, but I'm being linked as a developer for a working TWRP recovery. if you came from this link, DO NOT use my builds. I've deleted the...
forum.xda-developers.com
The bad key warning is pretty common with Moto devices after the bootloader is unlocked.
I have a general moto stock firmware thread here
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
There doesn't seem to be a working custom recovery for this device.
Moto devices are often referred to by development name or codename.
Your device should be SURFNA, look for that name on the bootloader screen
or
Code:
fastboot getvar product
I suggest following this thread for twrp
[ABANDONED] TWRP Dirty Port for Moto E6
https://www.getdroidtips.com/twrp-recovery-motorola-moto-e6/ None of my recoveries have worked for the E6, but I'm being linked as a developer for a working TWRP recovery. if you came from this link, DO NOT use my builds. I've deleted the...
forum.xda-developers.com
The bad key warning is pretty common with Moto devices after the bootloader is unlocked.
I have a general moto stock firmware thread here
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
I was afraid that was the answer.
Of all the cellphones in all the world, I had to buy this one :-(
I HAVE managed to get root access by flashing a Magisk modified recovery. However, this method is good for one boot per flash. It appears that once the boot completes, the modified recovery is gone from memory.
I DO get an error on flash about the image not signed or corrupt, and a similar message on the phone when booting, but once powered this way, I can 'su' in a shell.
How many times can the ROM be flashed before it starts to wear out?
And I STILL cannot find where USC hides it's bootanimation file. I removed the one in /system/media and a couple in /vendor, and that #$%^* 'Hello Moto' greeting and the USC logo screen still appear...
Thanx again for your help
Richard Rosa

richardrosa said:
I was afraid that was the answer.
Of all the cellphones in all the world, I had to buy this one :-(
I HAVE managed to get root access by flashing a Magisk modified recovery. However, this method is good for one boot per flash. It appears that once the boot completes, the modified recovery is gone from memory.
I DO get an error on flash about the image not signed or corrupt, and a similar message on the phone when booting, but once powered this way, I can 'su' in a shell.
How many times can the ROM be flashed before it starts to wear out?
And I STILL cannot find where USC hides it's bootanimation file. I removed the one in /system/media and a couple in /vendor, and that #$%^* 'Hello Moto' greeting and the USC logo screen still appear...
Thanx again for your help
Richard Rosa
Click to expand...
Click to collapse
Try patching both the recovery.img and the boot.img
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

sd_shadow said:
Try patching both the recovery.img and the boot.img
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you! That was the magic. It even got rid of the 'bad key' message on a normal boot!
Now if I can only find where that bootanimation file is hidden....
Thanx again.
Richard Rosa

[CLOSED] Delete Thread

Due to the disrespect of certain members here I will no longer share the tutorials.

Hi Articul8Madness,
Seems very cool. I'm new with XDA, and just got this moto one 5G ace from Metro as well. Are you recommending to flash it with the US retail ROM? Will it actually unlock the phone?
Tkx,
MH

huayixin said:
Hi Articul8Madness,
Seems very cool. I'm new with XDA, and just got this moto one 5G ace from Metro as well. Are you recommending to flash it with the US retail ROM? Will it actually unlock the phone?
Tkx,
MH
Click to expand...
Click to collapse
I actually have the RETBRAZIL rom currently flashed to it, lol. But I've tried the RETUS, RETEU roms. The TMO and Sprint ROM will get you a MetroPCS load screen as its the same.
And no, it will not unlock the phone. MetroPCS ties the IMEI to the Sim Card. They will not unlock this phone even if you pay in full like I did for three consecutive months of service. This is why no one Sim Unlocks Metro phones.

This way I was able to clean flash without any problems.
Is there a dirty flash that doesn't erase user data?

Articul8Madness said:
I actually have the RETBRAZIL rom currently flashed to it, lol. But I've tried the RETUS, RETEU roms. The TMO and Sprint ROM will get you a MetroPCS load screen as its the same.
And no, it will not unlock the phone. MetroPCS ties the IMEI to the Sim Card. They will not unlock this phone even if you pay in full like I did for three consecutive months of service. This is why no one Sim Unlocks Metro phones.
Click to expand...
Click to collapse
Thanks, really appreciate the insightful reply.

PEACH-PIT said:
This way I was able to clean flash without any problems.
Is there a dirty flash that doesn't erase user data?
Click to expand...
Click to collapse
There is no dirty flash for stock since this isn't a ROM but firmware. I suggest you backup your texts, phone logs, pictures, and anything else before you flash.

PEACH-PIT said:
...Is there a dirty flash that doesn't erase user data?
Click to expand...
Click to collapse
Yes, but it's not really advisable, it could cause apps to not work as expected.
Skip data wipe post #6

sd_shadow said:
Yes, but it's not really advisable, it could cause apps to not work as expected.
Skip data wipe post #6
Click to expand...
Click to collapse
Thank you.
I'll give it a try.

Articul8Madness said:
This tutorial is for people like me than ran into problems rooting the Moto One 5G Ace XT2113 (MetroPCS Qualcomm Variant) running on stock Android 10. I got this today after my beloved Moto G7Power's usb/charging port melted and fell out the phone after two and a half years and MetroPCS would NOT honor my insurance and replace the phone. Long story there. So far, this phone's been a good replacement but I'm still early in the game.
Follow the following at your own risk! I am not responsible for any mishaps with your devices. I also don't know if this will work on other variants, as I only have these for MetroPCS, and from my understanding this will NOT obviously work for Verizon, AT&T, and Cricket phones because you have to have the bootloader unlocked.
I want to thank @sd_shadow for pointing the way for me. This phone is a bit different being a new OS and a different updated Moto, and sd_shadow helped me get through the curious WTF now moments. This guide is solely for people like me that jumped head first into this phone with our variant trying to root and ran into some problems.
Introduction/Preparation
First, go and prepare by READING EVERYTHING OF THE FOLLOWING. Very important. Don't even jump into this without reading this thread here all the way to the last page: Motorola Guide To Flashing (this is so you know start to finish the differences between this model and maybe your previous models, plus the differences now between flashing Android 9 to 10, having an A/B system versus the new fastbootd mode).
Second, unlock the bootloader. The MetroPCS variant can be unlocked by Motorola; follow their instructions, it's easy peasy. Use their data tool to get the code formatted correctly or you may have problems. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). I did it in Waterfox this go round and it sent the codes immediately . When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
***NOTES SO YOU DON'T FREAK OUT***
1. Every time you power up the phone after you unlock the bootloader Moto will try and make you feel like crap with a bad throwing shade with a message that your phone is not to be trusted and the bootloader is unlocked. :laugh: This is normal. Give it a minute, you havent broke it.
2. There is no custom recovery/TWRP for this variant as of yet, so flashing the stock roms via fastboot is the only way to reset.
3. OEM Unlocking toggle switch is interesting. On my first phone it was activated once the bootloader is unlocked and greyed out to where it couldn't be accessed anymore. Same thing happened with my Moto G7Power so I'm assuming that's the new normal.
Files
If you tried to root like me and lost ALL touchscreen usability, then this is what you're going to have to do to come back from the paperweight abyss. First, pull out your Sim Card flashing. Yes, pull it out and flash without it. Flashing with the sim card/SD card in can cause problems flashing.
1. Get Minimal ADB and Fastboot (it's easier to use than Android SDK and smaller). Or you can use the Fastboot software of your choice. I used Minimal ADB and Fastboot.
2. Download the Motorola Drivers from their site (if you run into problems you will have to uninstall and reinstall them through their utility.
3. Cpu-Z.apk (This is a good thing to have to know your hardware responsibly).
4. Stock Firmware. I used XT2113_KIEV_RETUS_10_QZK30.Q4-40-55_subsidy-DEFAULT_regulatory-DEFAULT_CFC_R1_CFC.xml which is the US Retail software instead of MetroPCS's firmware because I hate any branded US carrier bloatware and such and like that factory unlocked from the manufacturer feel. Both of my phones flashed fine with it and you can find it here: Moto One 5G Ace ALL Firmwares. It doesn't matter what your carrier is, they have them all there. Try them at your discretion and risk.
****Notes on Flashing The Stock Firmware****
The best way to find out what your codes are is to go to the flashfile.xml that is located in the rom you downloaded. Once you get that the best way to use it since it won't be legibile for flashing is to put it in the online flash converter here: Online FlashFile Converter And don't worry - flashing another stock won't relock the bootloader.
Also, just so you know, once you flash and boot the phone back up you MUST put the sim card back in or a message about the phone being locked once you begin to set it up will come up. Just pop it in enough to get past that screen then remove it. Last thing you want is your data updating the phone without your permission and you turning it off.
1. Extract the firmware to the folder where Minimal ADB & Fastboot are at on your computer.
2. Turn the phone completely OFF and back ON if you haven't done so yet. Make sure there is no Sim Card of SD card in it.
3. Press Volume Up and Power to boot into fastboot mode if you have no touchscreen access. If you do just reboot or turn the phone off and turn it back on the regular way.
4. Plug your phone via USB cable into the computer.
5. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure all your firmware files have been extracted in the Minimal ADB directory or it won't work.
7. Cut, Copy, and Paste in Fastboot All Together everything from the Online Flash File Converter. In my case since I used the RETUS version mine looked like this:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
echo -----------------------------------------------------------------------------------------------
echo English - Process concluded!
echo Português - Processo concluído!
echo English - Press any key to restart the phone!
echo Português - Pressione qualquer tecla para reiniciar o celular!
echo -----------------------------------------------------------------------------------------------
pause
fastboot reboot
exit
8. When it is done it will stop. Hitting enter did not reboot my phone so I did it manually by hitting the Power button on START while still in flashboot.
9. That's it! You should have your phone officially flashed to firmware of your choice.
Hope this helps my fellow MetroPCSers. I lost ALL functionality of my touchscreen trying to root and with a little help from my XDA friends brought them back with this method. Old girl is working and now I'm working on a proper root with a proper matching boot.img.
And please, tinker with the little tyke responsibly. ;-P
Click to expand...
Click to collapse
Nice walkthru . Does this phone support monitor mode? I dont wanna root this Beauty unless i can put this gear to work.
THANKS

majored said:
Nice walkthru . Does this phone support monitor mode? I dont wanna root this Beauty unless i can put this gear to work.
THANKS
Click to expand...
Click to collapse
Thanks. I don't know if it supports monitor mode or not as I haven't installed Kali Nethunter on it.

If I put the retailus firmware on my metro phone will it still recieve over the air security updates?

retrov said:
If I put the retailus firmware on my metro phone will it still recieve over the air security updates?
Click to expand...
Click to collapse
Most likely no, you may need to flash firmware manually.

sd_shadow said:
Most likely no, you may need to flash firmware manually.
Click to expand...
Click to collapse
Thank you, I was able to flash worked great. I flashed the latest retail us rom has security update for march. Any recomendations on relocking the boatloader without bricking it if I need to send in for repair or something?

retrov said:
Thank you, I was able to flash worked great. I flashed the latest retail us rom has security update for march. Any recomendations on relocking the boatloader without bricking it if I need to send in for repair or something?
Click to expand...
Click to collapse
If you need to relock your bootloader, you must flash back to the original stock firmware for your variant or you will find yourself stuck in EDL mode.

can someone tell me why i cant mount my moto 5g ace is rooted with magisk but adb mount not in /proc/mounts

seriously you should know that you are a good person. when i attempted to flash a custom rom which ive done many times before but failed this time and ended up with no touch capabilities i got really depressed. coming across your forum and seeing you had the same issue really made my day. keep it up man.

Articul8Madness said:
I actually have the RETBRAZIL rom currently flashed to it, lol. But I've tried the RETUS, RETEU roms. The TMO and Sprint ROM will get you a MetroPCS load screen as its the same.
And no, it will not unlock the phone. MetroPCS ties the IMEI to the Sim Card. They will not unlock this phone even if you pay in full like I did for three consecutive months of service. This is why no one Sim Unlocks Metro phones.
Click to expand...
Click to collapse
Not true, I paid an unlocking service and got my MeotroPCS Motorola One 5G Ace SIM unlocked. I can and do use other SIM cards from other carriers.

mewcatchew said:
Not true, I paid an unlocking service and got my MeotroPCS Motorola One 5G Ace SIM unlocked. I can and do use other SIM cards from other carriers.
Click to expand...
Click to collapse
Consider yourself lucky as it does not work for all branded Metro phones. Also, why pay when you could have waited 3 months of continuous service and got it unlocked by them for FREE.

Articul8Madness said:
Consider yourself lucky as it does not work for all branded Metro phones. Also, why pay when you could have waited 3 months of continuous service and got it unlocked by them for FREE.
Click to expand...
Click to collapse
Because it's 6 months, not 3.

Fastboot issues when rooting Moto G Pure

Device is a Moto G Pure (codename Ellis), I've found little to no support for this device on the Internet, and a friendly redditor informed me due to the nature of the processor's manufacturers (MediaTek), there never will be much support for this model of device. I have managed to unlock the bootloader, and I'm all ready to go with drivers and fastboot and ADB, and I also have a twrp recovery image. My issue is I'm unsure if this is the correct TWRP img as I downloaded one for a similar Moto model (Moto G Stylus 2020, TWRP 3.5.0-0) and fastboot keeps throwing errors when I try to flash or boot this image. First error was 'command is not support' as I was using flashboot boot boot.img, did some research and instead tried flashboot flash boot boot.img which wasn't liked either, threw the error 'image size exceeds file limit'. I changed active partition from a to b and tried both commands, both of which presented the same issue. I even tried compressing the file down to 35mb and it still threw a fit. The TWRP file is only 48mb, what do I do? Further researching the issue is not bringing me much luck

there is no TWRP for Moto G Pure (yet) don't do stupid things

aIecxs said:
there is no TWRP for Moto G Pure (yet) don't do stupid things
Click to expand...
Click to collapse
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom

MisterMilo said:
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom
Click to expand...
Click to collapse
The stock rim is available at lollinet. I actually have a copy of it and have a magisk patched boot img. I think where your reaching the error is ( and I'm very new so feel free to correct me) the fastboot command. I think it's an a b partition. So it would be fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
MisterMilo said:
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom
Click to expand...
Click to collapse

I rooted mine through magisk by just boot image didn't disable dm verity or vb meta I do have root but you can't flash twrp from any other moto g because the moto g pure has a mediatek Helios g25 chip (I think,definitely mediatek tho)and all the others have quallcom snapdragon chips that's why you can't flash twrp in fastboot mode it's crazy no one's compiled twrp yet for this device seeing how easy it is to root. If you need help rooting yours lmk.

bayjones742 said:
I rooted mine through magisk by just boot image didn't disable dm verity or vb meta I do have root but you can't flash twrp from any other moto g because the moto g pure has a mediatek Helios g25 chip (I think,definitely mediatek tho)and all the others have quallcom snapdragon chips that's why you can't flash twrp in fastboot mode it's crazy no one's compiled twrp yet for this device seeing how easy it is to root. If you need help rooting yours lmk.
Click to expand...
Click to collapse
I Wanna Root Mine, Can You Teach Me How???

ROBOOTO said:
I Wanna Root Mine, Can You Teach Me How???
Click to expand...
Click to collapse
Easy all you gotta do is download your rom/firmware you can easily do this through the Lenovo rescue tool once you download your rom/firmware just extract into a folder somewhere you can easily access oh that rescue tool will download the firmware into crogramData\RSA\Download\RomFiles I think even though it says it's in downloads folder at first I couldn't find it for like an hour but anyways once you find the rom just extract it into a folder somewhere you can easily access & take the boot.img and send it or a copy of it into your phone's internal storage after you do that just download magisk 25.2 you know the latest one from johnwu's GitHub page and install that on your phone and you know how the rest goes just go to install magisk select img to patch choose the boot.img you transferred onto your phone let magisk do it's thing once it's done you have to transfer it back into the rom files you extracted remember to rename it back to boot.img because magisk names it something else but once you put it back in it's folder with the rest of the roms files I can't remember if I zipped em back up or not but anyways take that whole file back to the folder where the rescue tool downloaded it CrogramData\RSA\Download\RomFile and just go and adb reboot your phone into bootloader mode and let the rescue tool flash your moto g pure but with the patched boot image and hahahahaha you done oh but you have to have an unlocked bootloader otherwise you can't flash ... boi! Oh btw you'll have root but I can't uninstall system apps can't mount mount system to rw and as far as I know there's no TWRP but use fox's magisk module manager and flash bootloop protector it save my butt couple times already don't flash Sony Bravia engine will cause bootloop idk if I could compile TWRP I would almost 10 years I been doing this ... and still haven't learned to do that...lol
{Mod edit: Inappropriate language iaw. rule no. 2 removed. Oswald Boelcke}

Hi I'm feeling your pain from not having rw with your root. Have you checked out lebigmac's make sysRW script? I had to do it to get RW on my Moto G Stylus 5G cuz Android 11. Looks like I'll have to do it again for this model. Any luck on getting TWRP?

Database Info

welcome