Development [LATEST][RECOVERY][UNOFFICIAL]TWRP 3.7.0_12-v2 for Moto G Stylus 5G 2021[XT2131-1][denver]

Search This thread

androiddlifee

New member
Jun 13, 2017
3
0
Hello. I don't have a PC to root my device. However, is this thread away to download the twrp then load the magisk root?
 

miker1111769

Member
May 15, 2021
8
0
Hey all,

I've been rooting, flashing and unlocking phones for years so it seriously kills me to ask such a noob question!

How the heck do I get to the recovery menu (Not rootedat the moment)!

I've gotten there twice, and it keeps seeming luck dumb luck I'm getting there...

And I've searched for 5 days on this....

I do the volume down+power, Get to the bootloader, volume to recovery, get to the "no command" screen, and from there it either just sits forever, I've tried power+volume up from that screen which sends it back to a normal boot... and all kinds of other things! that aren't working....

So can someone please give me the exact procedure to get into recovery? lol thanks!

Mike
 

maddog3030

Senior Member
May 5, 2014
151
55
Nexus 7
Nexus 6
Hey all,

I've been rooting, flashing and unlocking phones for years so it seriously kills me to ask such a noob question!

How the heck do I get to the recovery menu (Not rootedat the moment)!

I've gotten there twice, and it keeps seeming luck dumb luck I'm getting there...

And I've searched for 5 days on this....

I do the volume down+power, Get to the bootloader, volume to recovery, get to the "no command" screen, and from there it either just sits forever, I've tried power+volume up from that screen which sends it back to a normal boot... and all kinds of other things! that aren't working....

So can someone please give me the exact procedure to get into recovery? lol thanks!

Mike
hummmm....5 days
First unlock bootloader then
Follow the instructions on the 1st page of this thread
 

miker1111769

Member
May 15, 2021
8
0
hummmm....5 days
First unlock bootloader then
Follow the instructions on the 1st page of this thread
Well gee thanks, I didn't start at the beginning I decided to start backwards.

The first thread says nothing about getting into recovery BEFORE installing TWRP.

Now if I could just get an answer to the original question that'd ve much appreciated
 

maddog3030

Senior Member
May 5, 2014
151
55
Nexus 7
Nexus 6
Well gee thanks, I didn't start at the beginning I decided to start backwards.

The first thread says nothing about getting into recovery BEFORE installing TWRP.

Now if I could just get an answer to the original question that'd ve much appreciated
Hummmm...
1) adb reboot bootloader.
2) fastboot boot a12v2-twrp-boot.img
3)
  • Once TWRP boots up, go to Advanced > Install Recovery Ramdisk
  • Then choose the a12v2-twrp-boot.img
  • Then go to Install and choose the Magisk-v25.2.zip file to re-root the device
  • Then go to Reboot > System....
Profit 😁 Doesn't get any clearer.
 

miker1111769

Member
May 15, 2021
8
0
Hummmm...
1) adb reboot bootloader.
2) fastboot boot a12v2-twrp-boot.img
3)
  • Once TWRP boots up, go to Advanced > Install Recovery Ramdisk
  • Then choose the a12v2-twrp-boot.img
  • Then go to Install and choose the Magisk-v25.2.zip file to re-root the device
  • Then go to Reboot > System....
Profit 😁 Doesn't get any clearer.
Did I say I had a computer?

Please don't treat me like I'm stupid about how to do these things, I rooted and unlocked a gs7 back when it was new through XDA...

if your not gonna help stop replying. I'm not gonna waste my time .
 

miker1111769

Member
May 15, 2021
8
0
Use the app like https://play.google.com/store/apps/details?id=eu.sisik.hackendebug and enable wifi adb in developer settings, and connect that account to the WiFi adb on your phone and use the app to send the command adb reboot recovery to get it to recovery... Best way if you don't got computer
Did you even read my original post?

I want to know how to get to the recovery of an on a unrooted moto g stylus 5G XT2131-1!
hace I confused you?
 
Did you even read my original post?

I want to know how to get to the recovery of an on a unrooted moto g stylus 5G XT2131-1!
hace I confused you?
I explained how to get to stock recovery on unrooted stylus phone. You don't have to be rooted to use wireless adb. Just enable developer options and do as I instructed. Either way.
 

MineMasterHD

Member
Sep 13, 2015
46
4
So I made the mistake of forgetting to backup the stock boot partition like I normally do before flashing the Magisk .zip. This is fine for now but I know it will become an issue when the next OTA update is released. What is the simplest way to perform the OTA update without losing data?
 
So I made the mistake of forgetting to backup the stock boot partition like I normally do before flashing the Magisk .zip. This is fine for now but I know it will become an issue when the next OTA update is released. What is the simplest way to perform the OTA update without losing data?
No worries at all, I'll explain how I do OTA without losing data...

The way I do it is using motoflash2sh or similar method to convert the flashfile.xml to fastboot format, then I remove the parts that would flash and format the userdata. Below is an example of the generated fastboot script and from the script I would remove the lines fastboot erase userdata || exit 1 fastboot erase metadata || exit 1

Those are the most important that you don't want to erase, userdata obviously is your data and the metadata is what holds the decryption key for your data so you'll need to make sure they are both intact. That should allow you to update OTA without losing data.

I think when I did it last I actually removed these lines fastboot erase carrier || exit 1 fastboot erase userdata || exit 1 fastboot erase metadata || exit 1 fastboot erase ddr || exit 1


Anyways, hope that helps. Please excuse my long post however I wanted to share the way I do it. Now, you will have to redo the sequence of fastboot boot twrp.img and then redo the process of injecting the ramdisk of TWRP back into the new boot.img that was flashed and then flash the Magisk.zip again... This is just cause of the new boot.img that is flashed during OTA...

Bash:
#!/bin/sh -x

cd ""

# <header>
#     <phone_model model="denver_global" />
#     <software_version version="denver_global-user 12 S2RES32.29-16-1-5 c4167-b6ebd release-keysM4350_HI431_41.1123.01.84R" />
#     <subsidy_lock_config MD5="e564ee6b429d585b6af57304fafaac31" name="slcf_rev_d_boost_dish_v2.2.nvm" />
#     <regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png" />
#     <cid_template_config SHA1="cfc1136c36955ba5ffe514efdf0037e95e47bef3" name="cid_template.dat" />
#     <sparsing enabled="true" max-sparse-size="536870912" />
#     <interfaces>
#       <interface name="AP" />
#     </interfaces>
#   </header>

md5sum --check <<EOF || exit 1
aa62e4245f4c04cde7de53a39afbd655 *gpt.bin
1457273247b6647e7a840263fc1c8743 *bootloader.img
a0c9d006bb33c646599d12ce64b74e87 *vbmeta.img
258334bc37dfe16b4b2df3e68a5b3168 *vbmeta_system.img
f5ad1817a5c781d485b12908b27cdcd4 *radio.img
cdb2152a024986f207ae868d03f59144 *BTFM.bin
7a2af0230c857b10759be5b87986687a *dspso.bin
69293ed09102d7440f9405ce23d0eceb *logo.bin
a374bda2d21c205a27f79a2dedc89bca *boot.img
926f938feaec4337c6cd5a00dbe458ce *vendor_boot.img
6432965406a9a99ec8ccddacd753e1f9 *dtbo.img
abb5ba9bd9770e3fcd5e198c561c6460 *super.img_sparsechunk.0
b11125a60b152af56873fa9f9efc83f5 *super.img_sparsechunk.1
73f4d822fdc372ace9363f20369499d1 *super.img_sparsechunk.2
868807fb9833e6f982d00235c1967014 *super.img_sparsechunk.3
e5783f7d2eef9c2c0ac13f2db4614d49 *super.img_sparsechunk.4
4977964a7c4fb5108d1729ba0d2781d4 *super.img_sparsechunk.5
4e3e2612ecef3d8e49bd5efa0201437e *super.img_sparsechunk.6
6916502936d47b8fd4a7299f567b6845 *super.img_sparsechunk.7
131035034b18a3f7a5153fcaf9dc1f79 *super.img_sparsechunk.8
ad6e83193863ca3c76bba5548b531ca5 *super.img_sparsechunk.9
adec4bf966b45e8ee08684acb5457bd1 *super.img_sparsechunk.10
656777ecb5968ad17474581b86e85bdf *super.img_sparsechunk.11
36239a8f794b7ce54fc63b6188a6b7e5 *super.img_sparsechunk.12
EOF

fastboot getvar max-sparse-size || exit 1
fastboot oem fb_mode_set || exit 1
fastboot flash partition gpt.bin || exit 1
fastboot flash bootloader bootloader.img || exit 1
fastboot flash vbmeta vbmeta.img || exit 1
fastboot flash vbmeta_system vbmeta_system.img || exit 1
fastboot flash radio radio.img || exit 1
fastboot flash bluetooth BTFM.bin || exit 1
fastboot flash dsp dspso.bin || exit 1
fastboot flash logo logo.bin || exit 1
fastboot flash boot boot.img || exit 1
fastboot flash vendor_boot vendor_boot.img || exit 1
fastboot flash dtbo dtbo.img || exit 1
fastboot flash super super.img_sparsechunk.0 || exit 1
fastboot flash super super.img_sparsechunk.1 || exit 1
fastboot flash super super.img_sparsechunk.2 || exit 1
fastboot flash super super.img_sparsechunk.3 || exit 1
fastboot flash super super.img_sparsechunk.4 || exit 1
fastboot flash super super.img_sparsechunk.5 || exit 1
fastboot flash super super.img_sparsechunk.6 || exit 1
fastboot flash super super.img_sparsechunk.7 || exit 1
fastboot flash super super.img_sparsechunk.8 || exit 1
fastboot flash super super.img_sparsechunk.9 || exit 1
fastboot flash super super.img_sparsechunk.10 || exit 1
fastboot flash super super.img_sparsechunk.11 || exit 1
fastboot flash super super.img_sparsechunk.12 || exit 1
fastboot erase carrier || exit 1
fastboot erase userdata || exit 1
fastboot erase metadata || exit 1
fastboot erase ddr || exit 1
fastboot oem fb_mode_clear || exit 1
 

MineMasterHD

Member
Sep 13, 2015
46
4
No worries at all, I'll explain how I do OTA without losing data...

The way I do it is using motoflash2sh or similar method to convert the flashfile.xml to fastboot format, then I remove the parts that would flash and format the userdata. Below is an example of the generated fastboot script and from the script I would remove the lines fastboot erase userdata || exit 1 fastboot erase metadata || exit 1

Those are the most important that you don't want to erase, userdata obviously is your data and the metadata is what holds the decryption key for your data so you'll need to make sure they are both intact. That should allow you to update OTA without losing data.

I think when I did it last I actually removed these lines fastboot erase carrier || exit 1 fastboot erase userdata || exit 1 fastboot erase metadata || exit 1 fastboot erase ddr || exit 1


Anyways, hope that helps. Please excuse my long post however I wanted to share the way I do it. Now, you will have to redo the sequence of fastboot boot twrp.img and then redo the process of injecting the ramdisk of TWRP back into the new boot.img that was flashed and then flash the Magisk.zip again... This is just cause of the new boot.img that is flashed during OTA...

Bash:
#!/bin/sh -x

cd ""

# <header>
#     <phone_model model="denver_global" />
#     <software_version version="denver_global-user 12 S2RES32.29-16-1-5 c4167-b6ebd release-keysM4350_HI431_41.1123.01.84R" />
#     <subsidy_lock_config MD5="e564ee6b429d585b6af57304fafaac31" name="slcf_rev_d_boost_dish_v2.2.nvm" />
#     <regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png" />
#     <cid_template_config SHA1="cfc1136c36955ba5ffe514efdf0037e95e47bef3" name="cid_template.dat" />
#     <sparsing enabled="true" max-sparse-size="536870912" />
#     <interfaces>
#       <interface name="AP" />
#     </interfaces>
#   </header>

md5sum --check <<EOF || exit 1
aa62e4245f4c04cde7de53a39afbd655 *gpt.bin
1457273247b6647e7a840263fc1c8743 *bootloader.img
a0c9d006bb33c646599d12ce64b74e87 *vbmeta.img
258334bc37dfe16b4b2df3e68a5b3168 *vbmeta_system.img
f5ad1817a5c781d485b12908b27cdcd4 *radio.img
cdb2152a024986f207ae868d03f59144 *BTFM.bin
7a2af0230c857b10759be5b87986687a *dspso.bin
69293ed09102d7440f9405ce23d0eceb *logo.bin
a374bda2d21c205a27f79a2dedc89bca *boot.img
926f938feaec4337c6cd5a00dbe458ce *vendor_boot.img
6432965406a9a99ec8ccddacd753e1f9 *dtbo.img
abb5ba9bd9770e3fcd5e198c561c6460 *super.img_sparsechunk.0
b11125a60b152af56873fa9f9efc83f5 *super.img_sparsechunk.1
73f4d822fdc372ace9363f20369499d1 *super.img_sparsechunk.2
868807fb9833e6f982d00235c1967014 *super.img_sparsechunk.3
e5783f7d2eef9c2c0ac13f2db4614d49 *super.img_sparsechunk.4
4977964a7c4fb5108d1729ba0d2781d4 *super.img_sparsechunk.5
4e3e2612ecef3d8e49bd5efa0201437e *super.img_sparsechunk.6
6916502936d47b8fd4a7299f567b6845 *super.img_sparsechunk.7
131035034b18a3f7a5153fcaf9dc1f79 *super.img_sparsechunk.8
ad6e83193863ca3c76bba5548b531ca5 *super.img_sparsechunk.9
adec4bf966b45e8ee08684acb5457bd1 *super.img_sparsechunk.10
656777ecb5968ad17474581b86e85bdf *super.img_sparsechunk.11
36239a8f794b7ce54fc63b6188a6b7e5 *super.img_sparsechunk.12
EOF

fastboot getvar max-sparse-size || exit 1
fastboot oem fb_mode_set || exit 1
fastboot flash partition gpt.bin || exit 1
fastboot flash bootloader bootloader.img || exit 1
fastboot flash vbmeta vbmeta.img || exit 1
fastboot flash vbmeta_system vbmeta_system.img || exit 1
fastboot flash radio radio.img || exit 1
fastboot flash bluetooth BTFM.bin || exit 1
fastboot flash dsp dspso.bin || exit 1
fastboot flash logo logo.bin || exit 1
fastboot flash boot boot.img || exit 1
fastboot flash vendor_boot vendor_boot.img || exit 1
fastboot flash dtbo dtbo.img || exit 1
fastboot flash super super.img_sparsechunk.0 || exit 1
fastboot flash super super.img_sparsechunk.1 || exit 1
fastboot flash super super.img_sparsechunk.2 || exit 1
fastboot flash super super.img_sparsechunk.3 || exit 1
fastboot flash super super.img_sparsechunk.4 || exit 1
fastboot flash super super.img_sparsechunk.5 || exit 1
fastboot flash super super.img_sparsechunk.6 || exit 1
fastboot flash super super.img_sparsechunk.7 || exit 1
fastboot flash super super.img_sparsechunk.8 || exit 1
fastboot flash super super.img_sparsechunk.9 || exit 1
fastboot flash super super.img_sparsechunk.10 || exit 1
fastboot flash super super.img_sparsechunk.11 || exit 1
fastboot flash super super.img_sparsechunk.12 || exit 1
fastboot erase carrier || exit 1
fastboot erase userdata || exit 1
fastboot erase metadata || exit 1
fastboot erase ddr || exit 1
fastboot oem fb_mode_clear || exit 1
Thanks. I had no idea motoflash2sh is a thing. This will be very helpful.

Where do I get the original firmware files from?

As for re-rooting, my process is a little different. In the past, on my Moto G Fast (rav), I never permanently flashed the recovery to the phone. I used fastboot to boot TWRP, create a backup of the stock boot image (to make OTAs easier next time), use Magisk to create a patched version of that boot image, go back into fastboot, and flash that boot image with fastboot for root.

Then, when OTAs came around, I would simply use fastboot to boot into TWRP again, restore the stock boot image from the backup I made previously, and then with that, I can perform OTA updates normally through the system updater. Once the update is finished, I repeat the steps of backing up the stock boot image, patching, and flashing.

Similarly, with this denver device, I did not permanently flash TWRP. I simply booted it with fastboot and then flashed the Magisk .zip.

It seems like an easier way to get the OTA update done would be to keep the boot.img from the most recent OTA update, flash that boot.img when the next OTA update comes around, update it, and then follow my usual rooting process.

Would this still work on denver?
 
Thanks. I had no idea motoflash2sh is a thing. This will be very helpful.

Where do I get the original firmware files from?

As for re-rooting, my process is a little different. In the past, on my Moto G Fast (rav), I never permanently flashed the recovery to the phone. I used fastboot to boot TWRP, create a backup of the stock boot image (to make OTAs easier next time), use Magisk to create a patched version of that boot image, go back into fastboot, and flash that boot image with fastboot for root.

Then, when OTAs came around, I would simply use fastboot to boot into TWRP again, restore the stock boot image from the backup I made previously, and then with that, I can perform OTA updates normally through the system updater. Once the update is finished, I repeat the steps of backing up the stock boot image, patching, and flashing.

Similarly, with this denver device, I did not permanently flash TWRP. I simply booted it with fastboot and then flashed the Magisk .zip.

It seems like an easier way to get the OTA update done would be to keep the boot.img from the most recent OTA update, flash that boot.img when the next OTA update comes around, update it, and then follow my usual rooting process.

Would this still work on denver?

It should still work.. Magisk has this nice little feature that if you are on stock boot.img when you flash the zip file it makes a backup of the original stock boot.img file on your phone, I think in the /data/ partition but dont quote me... and then you can go into Magisk and click uninstall (its for otas) and it will restore that backup of the original boot.img stock so you can do the ota.. then before reboot for ota... go back to magisk and pick install to other slot or something like that... so that when it reboots for ota it reinstalls magisk on the reboot


i think thats how that works... either way... you can find the files a few ways... theres a telegram to get them and also https://mirrors.lolinet.com/firmware/motorola/denver/official/
 
  • Like
Reactions: MineMasterHD

callihn

Senior Member
Oct 14, 2012
159
31
I don't see any XT numbers or code names in about phone, I bought the unlocked version currently on sale for black friday so I don't know if this is what I need? Can anyone verify?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I don't see any XT numbers or code names in about phone, I bought the unlocked version currently on sale for black friday so I don't know if this is what I need? Can anyone verify?
    1
    Did you even read my original post?

    I want to know how to get to the recovery of an on a unrooted moto g stylus 5G XT2131-1!
    hace I confused you?
    When you get to the no command screen hold power button while tapping the volume up button. It works for me.
    1
    Thanks. I had no idea motoflash2sh is a thing. This will be very helpful.

    Where do I get the original firmware files from?

    As for re-rooting, my process is a little different. In the past, on my Moto G Fast (rav), I never permanently flashed the recovery to the phone. I used fastboot to boot TWRP, create a backup of the stock boot image (to make OTAs easier next time), use Magisk to create a patched version of that boot image, go back into fastboot, and flash that boot image with fastboot for root.

    Then, when OTAs came around, I would simply use fastboot to boot into TWRP again, restore the stock boot image from the backup I made previously, and then with that, I can perform OTA updates normally through the system updater. Once the update is finished, I repeat the steps of backing up the stock boot image, patching, and flashing.

    Similarly, with this denver device, I did not permanently flash TWRP. I simply booted it with fastboot and then flashed the Magisk .zip.

    It seems like an easier way to get the OTA update done would be to keep the boot.img from the most recent OTA update, flash that boot.img when the next OTA update comes around, update it, and then follow my usual rooting process.

    Would this still work on denver?

    It should still work.. Magisk has this nice little feature that if you are on stock boot.img when you flash the zip file it makes a backup of the original stock boot.img file on your phone, I think in the /data/ partition but dont quote me... and then you can go into Magisk and click uninstall (its for otas) and it will restore that backup of the original boot.img stock so you can do the ota.. then before reboot for ota... go back to magisk and pick install to other slot or something like that... so that when it reboots for ota it reinstalls magisk on the reboot


    i think thats how that works... either way... you can find the files a few ways... theres a telegram to get them and also https://mirrors.lolinet.com/firmware/motorola/denver/official/
    1
    Oh wow, that is really buried. Thanks once again. I never would have found that.
    1
    Oh wow, that is really buried. Thanks once again. I never would have found that.
    No worries and yeah very buried... I had to search Home in settings lol and then click every option lol
  • 7
    W9JMd4u.png

    Code:
    /*
    *Disclaimer
    *
    * Your warranty is now void.
    *
    * We're not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at us for messing up your device, we will laugh at you.
    */

    Introduction

    Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.

    Android 12 Installation Instructions
    DO NOT FLASH ZIP, UNZIP FIRST
    • First unzip the ANDROID-12-UNZIP-ME-FIRST.zip file to get a12v2-twrp-boot.img and Magisk-v25.2.zip files.
    • Copy a12v2-twrp-boot.img and Magisk-v25.2.zip to either internal storage or external SD card.
    Then do:
    Code:
    adb reboot bootloader
    fastboot boot a12v2-twrp-boot.img
    • Once TWRP boots up, go to Advanced > Install Recovery Ramdisk
    • Then choose the a12v2-twrp-boot.img
    • Then go to Install and choose the Magisk-v25.2.zip file to re-root the device
    • Then go to Reboot > System
    Working
    • Everything, including touchscreen. No need to flash 3rd party kernel.

    Troubleshooting
    If you get the error createTarFork{} process ended with ERROR: 255
    Go to /data/ folder and delete the fonts folder then reboot and try backup /data again.


    Screenshot_2022-10-04-03-22-07.png Screenshot_2022-10-04-03-22-01.png


    //DISCONTINUED//
    Android 11 Installation Instructions
    DO NOT FLASH ZIP, UNZIP FIRST
    • First unzip the ANDROID-11-UNZIP-ME-FIRST.zip file to get twrp-boot.img and Magisk-v25.2.zip files.
    • Copy twrp-boot.img and Magisk-v25.2.zip to either internal storage or external SD card.
    Then do:
    Code:
    adb reboot bootloader
    fastboot boot twrp-boot.img
    • Once TWRP boots up, go to Advanced > Install Recovery Ramdisk
    • Then choose the twrp-boot.img
    • Then go to Install and choose the Magisk-v25.2.zip file to re-root the device
    • Then go to Reboot > System
    2
    Thank you for this! I will give it a shot.
    2
    Alright. touch screen works after i turn off the screen and turn it back on. umm it also wont let me backup any data.

    Ok thank you. Yeah I didnt think decryption would work. It's meant for A11... but I will work on A12 compile version of it now. Just gotta get the right modules, etc from A12. Once It's done I'll add it to this thread in addition to the A11 version.
    2
    Really ? It reboots to system instead of to a brick? What's next custom ROM? People like you restore my faith in humanity. Confirmed working
    2
    I'll give it a try :}

    Awesome! Let me know. Decryption might not work on A12. I'm compiling A12 based TWRP now. Seeing if it compiles anyways, lol.