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

[galapagos]

An update is available for RETUS (from S2RES32.29-16-1-10-4 to S2RES32.29-16-1-10-5). Did anyone get the full firmware via RSA? Does it usually take extra time for the full image to appear on RSA? I guess I can just go back to stock boot.img to unroot then upgrade, backup the boot.img, then patch & re-root using magisk?

EDIT: All went successfully. Updated and re-rooted.

 

[maddog3030]

An update is available for RETUS (from S2RES32.29-16-1-10-4 to S2RES32.29-16-1-10-5). Did anyone get the full firmware via RSA? Does it usually take extra time for the full image to appear on RSA? I guess I can just go back to stock boot.img to unroot then upgrade, backup the boot.img, then patch & re-root using magisk?

EDIT: All went successfully. Updated and re-rooted.

I know there is a security update that take the phone to S2RES32.29-16-1-10-5
but RSA dose not show it yet, even when I use a phone that is already on S2RES32.29-16-1-10-5 it still shows S2RES32.29-16-1-10-4!!!???
and no updates on https://t.me/motoupdatestracker yet.
** its up now https://t.me/motoupdatestracker !!

 

[BLeAk11]

How did you manage to unlock an At&t variant BL? I just got one and immediately Moto says no dice with my BL code. I'm doublechecking for errors and spaces but I'm not new to that process, I know how to put the string together.


Edit: Maybe it's because I just got it. I might have to wait the 48 to 72 hours or whatever to have it allow me to unlock. I've never actually had a phone that needed that. OEM unlocking is allowable, though it ran an update and I worried that screwed up my unlock ability too. It's on RRES31.Q2-11-61-4-16 with unlocking check able to toggle. Hope that's it. I specifically bought it as a nav phone for work that I thought I could root for Viper4Android use for my BT headphones since all of the non-root EQ apps are super weak if they even ever work at all.

Yeah there is a wait

 

[FlyingPoo]

I'm still on S2RES32.29-16-1-10-4 and getting this OTA nag to update to S2RES32.29-16-1-10-5. If I already have TWRP installed as well as Magisk, can I just boot into TWRP, install S2RES32.29-16-1-10-5, then the TWRP-boot image, then the Magisk zip all in one TWRP session, reboot and still keep TWRP and root? Also, I suppose I should note that I have the 4/128 version of this phone.

 

[ragarcia87]

I'm still on S2RES32.29-16-1-10-4 and getting this OTA nag to update to S2RES32.29-16-1-10-5. If I already have TWRP installed as well as Magisk, can I just boot into TWRP, install S2RES32.29-16-1-10-5, then the TWRP-boot image, then the Magisk zip all in one TWRP session, reboot and still keep TWRP and root? Also, I suppose I should note that I have the 4/128 version of this phone.

You should be able to. As long as you install TWRP first then rename Magisk.apk to Magisk.zip and flash it after the TWRP. Then you should be fine.

 

[Camadams1179!]

Would this by chance work for the non 5G version of this phone? Ive been needing a useable TWRP but i dont want to delve into making it myself and brick my device. Any help would be welcomed, my phone is rooted through magisk as well but TWRP is useful for some stuff as well...

 

[FlyingPoo]

You should be able to. As long as you install TWRP first then rename Magisk.apk to Magisk.zip and flash it after the TWRP. Then you should be fine.

I had to go about your method to install an OTA but used a windows script. Worked well. Then fastboot boot twrp.img > flash recovery to ramdisk then install Magisk again.

Looking at changing a few other things now.

Its been a minute and I'm digging out old tools.


Camadams, If you boot your phone into fastboot, you can "test" this twrp image by connecting your phone to your PC and run the command

fastboot boot a12v2-twrp-boot.img

This isn't permanent and reverts back to original recover after a phone restart.
If it boots into this recovery and everything works, you can go to Advanced > flash recovery to ramdisk and select the a12v2-twrp-boot.img file for a more permanent solution.

 

[Camadams1179!]

This isn't permanent and reverts back to original recover after a phone restart.
If it boots into this recovery and everything works, you can go to Advanced > flash recovery to ramdisk and select the a12v2-twrp-boot.img file for a more permanent solution.

Are you aware if this works on Android 11 or does that have no factor in this process, id assume if i did it with the a12v2 twrp img it just wouldnt allow it but just being cautious

 

[FlyingPoo]

Are you aware if this works on Android 11 or does that have no factor in this process, id assume if i did it with the a12v2 twrp img it just wouldnt allow it but just being cautious

There is a v11 in the 1st post. Not sure, as I got this phone with android 12 already on it.
As this was built for the denver model, there may be other issues when doing a nandroid backup for example if this appears to work on your phone model when booted through fastboot.

 

[Camadams1179!]

There is a v11 in the 1st post. Not sure, as I got this phone with android 12 already on it.
As this was built for the denver model, there may be other issues when doing a nandroid backup for example if this appears to work on your phone model when booted through fastboot.

Well tried to boot it and it says

downloading 'boot.img'...
OKAY (2.293s)
booting. . .
(Bootloader)Command is not support
Failed (Remote Failure)
Finished. total time: 2.297s

is this my cord or usb slot or is this just a command i cannot use? And to clear up, im on android 11 and never got the update to 12.

 

[FlyingPoo]

Well tried to boot it and it says

downloading 'boot.img'...
OKAY (2.293s)
booting. . .
(Bootloader)Command is not support
Failed (Remote Failure)
Finished. total time: 2.297s

is this my cord or usb slot or is this just a command i cannot use? And to clear up, im on android 11 and never got the update to 12.

Is your bootlloader unlocked?

 

[Camadams1179!]

Is your bootlloader unlocked?

Yes, it is. My device is rooted. Unsure as to why it is having this issue.

 

[wswjw]

Well tried to boot it and it says

downloading 'boot.img'...
OKAY (2.293s)
booting. . .
(Bootloader)Command is not support
Failed (Remote Failure)
Finished. total time: 2.297s

is this my cord or usb slot or is this just a command i cannot use? And to clear up, im on android 11 and never got the update to 12.

You will get this error if, in an attempt to arrive at fastboot, the command adb reboot fastboot was used. Then instead you'll be in fastbootd, of which the fastboot boot xxx.img command will fail and produce this error. From fastbootd menu, select reboot bootloader to arrive at fastboot then try the command to boot the img.