The Complete Noob Guide To Getting Read/Write Access On The Moto One 5G Ace XT2113 [Qualcomm Variant]

Search This thread

devasure

Senior Member
May 18, 2015
83
14
my device is redmi 9i sports android 10.
this is what I got.
can anybody help me out
 

boltjuice

Member
Apr 8, 2018
13
0
Moto G 5G
everything went smooth till i reboot phone and now is stuck on moto logo =(
Same here. Followed steps and used file in post 5 and now I am in vibrating boot loop on motorola logo.

Have Motorola One 5G Ace Model # XT2113-2 Build # RZK31.Q3-45-16-3
My phone performed system update to Android 11 while setting up phone.
I unlocked bootloader, installed TWRP v3.6.0, rooted with Magisk v24.3, and this was a fail.

If you are on Android 11 is there a way to get R/W access?
 
Last edited:

RETIEF

Senior Member
Sep 28, 2007
311
66
67
Moto G 5G
Same here. Followed steps and used file in post 5 and now I am in vibrating boot loop on motorola logo.

Have Motorola One 5G Ace Model # XT2113-2 Build # RZK31.Q3-45-16-3
My phone performed system update to Android 11 while setting up phone.
I unlocked bootloader, installed TWRP v3.6.0, rooted with Magisk v24.3, and this was a fail.

If you are on Android 11 is there a way to get R/W access?
Use the same method as for 10.
 

RETIEF

Senior Member
Sep 28, 2007
311
66
67
Moto G 5G
Go to the guide, but then follow the link to the Mun... (I don't remember his handle) post. Download the new supperrepack. Run it only once! That is what I did and it worked.
 
  • Like
Reactions: boltjuice

boltjuice

Member
Apr 8, 2018
13
0
Moto G 5G
Go to the guide, but then follow the link to the Mun... (I don't remember his handle) post. Download the new supperrepack. Run it only once! That is what I did and it worked.
So to clarify you downloaded superrepack v15 from munjeni in first post here

Then use that file and follow the steps in this guide?
 

RETIEF

Senior Member
Sep 28, 2007
311
66
67
Moto G 5G
So to clarify you downloaded superrepack v15 from munjeni in first post here

Then use that file and follow the steps in this guide?
Yes. But I let the script only run once.
 
  • Like
Reactions: Moondroid

Moondroid

Senior Member
Feb 12, 2015
304
110
Worked fine using v15 (and Minimal ADB and Fastboot from 2018). Windows 7 Pro 64 laptop. No hiccups, no problems at all. Good clear instructions. As is typical, the many steps probably make it look harder than it really is.

FYI, I've done this successfully on a TWRP-&-Magisk-rooted XT2113-2 and also on a Magisk-only root via patched boot.img (both on Android 10).
 
Worked fine using v15 (and Minimal ADB and Fastboot from 2018). Windows 7 Pro 64 laptop. No hiccups, no problems at all. Good clear instructions. As is typical, the many steps probably make it look harder than it really is.

FYI, I've done this successfully on a TWRP-&-Magisk-rooted XT2113-2 and also on a Magisk-only root via patched boot.img (both on Android 10).
Depends on your phone. The reason I listed so many steps is because I worked closely with a dev that was trying to get us r/w access and on my variant it was necessary.
 

daktah

Senior Member
Jun 17, 2010
275
108
trying to use superrepack, both the steps here and on the original thread result in a bootloop. well not exactly a bootloop, but it just sits on the splash screen. easily fixed by a twrp restore.
also tried to use the universal r/w, cant run it because im on slot a. tried to use the lineage copy slot zip, output says it didnt copy loop17 through 20 (not sure what these actually are, but it does not list data or super or anything being copied so probably these) and subsequently trying to boot slot b results in infinite vibration on the splash screen.

does anyone have any idea how to fix this? im on a11 rzk31.q3-45-16 (retus i believe) xt2113-2, bootloader unlocked with magisk root.

update:
this morning it's come to my attention that I have no sound in some places (in calls even while on Bluetooth and the sample sounds that play when you adjust the volume) and no camera. this is after a twrp restore of every single partition right before attempting system RW so apparently something has been altered or damaged to disable this functionality. since now I have to restore my phone, is there a stock ROM available that is pre-rooted and RWd way to do it myself? also I'm trying to access mirrors.loli.net to get the firmware but it just keeps closing the connection, is this happening anyone else or is it just me on my phone? I have no problems with any other websites. what a pita this has become.

update to the update:
luckily managed to return everything to normal without wiping anything by downloading the rom from home (i guess its just phone IPs the site rejects? idk never had a problem with loli.net until now on my phones) and fastboot flashing all of the images except for super, boot and bootloader and no erase commands. still would like to know how to preRW these images files so i dont have to deal with this buggy risky crap next time.
 
Last edited:
trying to use superrepack, both the steps here and on the original thread result in a bootloop. well not exactly a bootloop, but it just sits on the splash screen. easily fixed by a twrp restore.
also tried to use the universal r/w, cant run it because im on slot a. tried to use the lineage copy slot zip, output says it didnt copy loop17 through 20 (not sure what these actually are, but it does not list data or super or anything being copied so probably these) and subsequently trying to boot slot b results in infinite vibration on the splash screen.

does anyone have any idea how to fix this? im on a11 rzk31.q3-45-16 (retus i believe) xt2113-2, bootloader unlocked with magisk root.

update:
this morning it's come to my attention that I have no sound in some places (in calls even while on Bluetooth and the sample sounds that play when you adjust the volume) and no camera. this is after a twrp restore of every single partition right before attempting system RW so apparently something has been altered or damaged to disable this functionality. since now I have to restore my phone, is there a stock ROM available that is pre-rooted and RWd way to do it myself? also I'm trying to access mirrors.loli.net to get the firmware but it just keeps closing the connection, is this happening anyone else or is it just me on my phone? I have no problems with any other websites. what a pita this has become.

update to the update:
luckily managed to return everything to normal without wiping anything by downloading the rom from home (i guess its just phone IPs the site rejects? idk never had a problem with loli.net until now on my phones) and fastboot flashing all of the images except for super, boot and bootloader and no erase commands. still would like to know how to preRW these images files so i dont have to deal with this buggy risky crap next time.
I only use V2. Any other version of Superpack causes issues, esp. the last version, it deletes settings icon for me. Also use the earliest stock roms, not later ones. Can't commit on changes to those and possible patching.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    Update: I used Version 2 with no problems. According to @munjeni there are BIG DANGEROUS ISSUES with Version and newer. Starting at V7 there are clone issues. I have tried Version 9 and had those issues.

    Using the V2 method you will be able to delete and remove files. The ability to resize the partitions has not been achieved, so you will be at the mercy of the space limitations in the partition.





    This tutorial is for people like me that after rooting the Moto One 5G Ace XT-2113 (MetroPCS Qualcomm Variant) running on stock Android 10 discovered that their root did not grant them Write Access to system files. Starting with Android 10, a new System As Root protocol prohibits users from access all of their files due to Dynamic Partitions and being formatted to EXT4_FEATURE_RO_COMPAT_SHARED_BLOCKS, effectively making root useless. You can read about that here:
    Rest not, a method has been made!

    Follow the following at your own risk! I am not responsible for any mishaps with your devices and neither is @munjeni. I also don't know if this will work on other variants, as I only have tried this method on the RETUS and RETEU stock firmware. Also, this will NOT obviously work for Verizon, AT&T, and Cricket phones or other mobile carriers that lock their bootloaders.

    I want to thank a couple of people for their big beautiful brains and hard work in figuring this out. First, all the love in the world goes out to @lebigmac. This beautiful soul and I have been back and forth a week trying to get something going on the Moto. I thank him for his patience, his genius, and his tenacity to hang in there with my device even after I threatened a bunch of times to go to Apple and be done with this new cumbersome lockdown AndroidOS. He gave the hope as his method has worked on Asus and Xiaomi variants. It has been an honor to be on his beta test team.

    Last, but not least, I want to thank @munjeni whose method finally broke on through to the other side. If it were not for his big beautiful brain I’d be ordering me an iPhone and calling it quits. It is due to his and @lebigmac’s hard work researching and testing that gives us the ability to finally have full root access. Thank you guys. I love you both!

    And please visit both of their threads and help them continue support and development on this project for ALL of your Android 10 phones (especially this one).
    @lebigmac Method: [SCRIPT][Android 10+] Universal Mount System read write R/W
    @munjeni Method: [TOOL][WIN,LIN,AND,DARW] Super image unpack-repack tools

    Introduction/Preparation
    First, go and prepare by READING EVERYTHING I’M WRITING IN THIS POST BEFORE YOU START. Very important. Don't even jump into this without reading this thread here all the way to the end. This isn’t exactly child’s play if you are not comfortable with the ADB Shell or Linux, and if you type the wrong commands you could do serious, irreparable damage to your device. It also doesn’t hurt to read the original thread for this all the way through, and you can find that here: Munjeni's Superpack Repack Tool

    Second, make sure your bootloader is unlocked and you have Magisk root on your device. You can check the forum for tutorials on how to do that. This method will ABSOLUTELY NOT WORK if you are not bootloader unlocked, and rooted with your boot.img patched by Magisk. If you can’t figure out that part of it then you definitely aren’t prepared for this.

    ***NOTES SO YOU DON'T FREAK OUT***
    1. While it hasn’t happened to me, there is the possibility that you can brick your phone doing this. As such, make sure you have your firmware already downloaded and available to flash should something go wrong. This is just a precaution, a break glass in case of emergency situation. It’s better to have the files already ready to go with the flashfile commands converted and not need it than need it and frustrated because you didn’t prepare.

    2. There is no custom recovery/TWRP for this variant yet (and trust me I’m trying very hard to work on that), so you will have to use ADB Shell to run the commands we need for this exercise. If you are not familiar with that, please do some research on ADB Shell so you’re comfortable and familiar. Google for once is a friend for that!

    Files
    Here is a list of things you will need going into it.

    1. Windows 7. I did it in Windows 7 and Kali Linux so I can’t speak on whether or not this will work smoothly in other versions. This method is exclusively for Windows 7. Go to the original thread on info on how to use it on other platforms.

    2. Get Tiny ADB and Fastboot (it's easier to use than Android SDK and smaller) or whatever fastboot you’re comfortable with.

    3. Make sure the drivers for your Moto One 5G Ace are already downloaded and installed on your computer.

    4. @munjeni’s Super Unpack Repack Tool. Can’t get anywhere with the method without it. You can download it here from the first post: https://forum.xda-developers.com/t/tool-win-lin-and-darw-super-image-unpack-repack-tools.4120963/

    5. Root Explorer (or whatever your favorite type of system explorer is). There’s no getting into the system files without it.

    6. Busybox. I used Busybox Pro 70 that I had from my MotoG7Power and that worked flawlessly. A newer version of Busybox did not install on my device because I didn’t have Write access going into it but that version I can attest works.

    7. Stock Firmware (Just in case, remember?) I used XT2113_KIEV_RETUS_10_QZK30.Q4-40-55_subsidy-DEFAULT_regulatory-DEFAULT_CFC_R1_CFC.xml which is the US Retail software and the XT2113-3_KIEV_RETEU_10_QZKS30.Q4-40-62-2_subsidy-DEFAULT_regulatory-XT2113-3-EU-SAR_CFC.xml 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.

    8. The stock charging cable that comes with your phone.

    The Process
    1. Make sure the phone is at least halfway charged. Last thing you want is the phone to die in the middle of any of this and cause a system error that you might can’t get out of.

    2. Make sure your have installed your Root Explorer and Busybox beforehand.

    3. Extract @munjeni’s Super Unpack Repack Tool. Copy the file “superrepack.arm64_pie” to your phone.

    4. Rename “superrepack.arm64_pie” on your phone to “superrepack” (obviously without quotations).

    5. Move “superrepack” file on your phone to /data/local/tmp folder. If you have root and using a root explorer you can’t miss it (obviously without quotations).

    6. Connect your phone to your PC via the charging cable.

    7. Open TinyADB and Fastboot. Do not open it as an administrator or it will not function correctly getting root access on your device.

    8. Type: “adb shell” and press enter. This will change C:/TheNameOfYourDirectory to kiev:/ $

    9. Type: “su” and press enter. This will change the dollar sign “$” to a sharp symbol “#” and will look like kiev:/ # Make sure you allow permissions if Magisk asks for it or it will give you a permission denied message.

    10. Type: “ls -Alg /dev/block/by-name | grep "super"” and press enter since you need to know where your block device is. It should return a result that looks like “lrwxrwxrwx 1 root 16 1970-01-01 08:07 super -> /dev/block/NameOfYourBlock” (obviously without quotations except the quotations in "super" - keep those)

    11. Copy and paste somewhere “/dev/block/NameOfYourBlock” (obviously without quotations). You’re going to need that later.

    12. Close TinyADB and Fastboot. Now open a fresh instance of it in a new window.

    13. Type: “adb shell” (obviously without quotations) and press enter. This will change C:/TheNameOfYourDirectory to kiev:/ $

    14. Type: “su” (obviously without quotations) and press enter. This will change the dollar sign “$” to a sharp symbol “#” and will look like kiev:/ #

    15. Type: “chmod 755 /data/local/tmp/superrepack” (obviously without quotations) and press enter as the chmod command will give us root permissions to run the script. This is VERY IMPORTANT. Don’t worry if it goes to a blank next line that’s normal.

    16. Type: “setenforce 0” (obviously without quotations) and press enter as we need to disable selinux. Again, don’t worry if it goes to a blank next line as that’s normal.

    17. Type: “/data/local/tmp/superrepack /dev/block/NameOfYourBlock” (obviously without quotations) and press enter. Let the script run to the end.

    18. Reboot your phone. Close Tiny ADB and Fastboot.

    19. When your phone is rebooted go to Root Explorer (or your explorer).

    20. Mount the system in your file explorer! You should have R/W Access in ALL of your partitions.

    If Something Goes Wrong And You Have To Reflash Your Phone…
    Please refer to the guides in the forum on how to get your phone back to stock. There’s one for flashing, one for root, and a subsequent one for debloat.
    If you come up with an error, please go to the original thread https://forum.xda-developers.com/t/tool-win-lin-and-darw-super-image-unpack-repack-tools.4120963/ and let @munjeni know what the issue is so he can help.

    Hope this brings some love to the Moto One 5G Ace users. We definitely need a boost to lift development spirits.

    I will try and answer questions if I can or point you in the right direction.
    3
    https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/

    "moto g 5g" can use makeSystemRW v1.31.
    It must be used in conjunction with makesysrw_repair.
    makesysrw_repair requires linux.

    The size option will not work if it is too large or too small.
    You need to specify an appropriate size.
    Please adjust it by yourself.
    I got the right result with 20mb.

    adb shell
    su
    chmod +x /data/local/tmp/makesysrw_1.31/makesysrw.sh
    setenforce 0
    ./data/local/tmp/makesysrw_1.31/makesysrw.sh size=20
    2
    You have it correct. Follow the guides exactly. I tried shortcuts and they all failed. As a result, I have none this process three times. Don't be me.
    2
    https://forum.xda-developers.com/t/...t-system-read-write-r-w.4247311/post-84914345

    Perhaps this will eliminate the need for makesysrw_repair.
    However, you will need an sd card.

    adb shell
    su
    chmod +x /data/local/tmp/makesysrw_1.31/makesysrw.sh
    setenforce 0
    cd /data/local/tmp/makesysrw_1.31
    ./makesysrw.sh size=20 out=/external_sd/super.img
    2
    First of all, thank you for replying to my post. I read what you wrote twice because I wanted to make sure I got everything correct. Yes, I felt the same about using your guide. However, I saw two started posts from you regarding rooting so I wanted to make sure I was following the correct one if that makes sense. Also, one of my concerns was in fact the R/O attribute of all this. I wanted to know if it was even worth going through all this just to be limited by the R/O crap this started. I was very much looking forward to R/W access as that is a major benefit of rooting ones phone. I also have the MetroPCS variant but I do have an unlocked device.

    So, in conclusion, I guess my real question is... is it worth it since we cannot achieve R/W access?

    Edit: Also, another big reason for wanting to fully root my device is that I would like to start using Titanium Backup for backing up my device which as I am sure you are aware, can only be used with a fully rooted device with superuser permissions. Now, with the issue of R/O, is it still possible for me to start using Titanium Backup by following your guide but not having R/W access? Thanks for your time.
    You need to follow this guide. Then follow the guide on how to get r/w access. Then follow the guide on how to debloat if you wish to remove anything. I root for the purpose of using Titanium backup. It is only useful on this phone if you use the first two guides.