Database Info

[GUIDE] [XT1575] Return to stock and relock bootloader

*** This process can relock your bootloader if you chose, but it does NOT restore your warranty in any way, so don't ask ***
Be aware you do NOT have to lock the bootloader, have Status Code of 0, or have it show "Official" status to successfully accept and apply an OTA update, it will happily apply with an unlocked bootloader and unofficial software status, as long as you have a 100% pure stock ROM installed the update script doesn't care what the bootloader reports.
Preflash validation error? See notes at the bottom of this post.
Prerequisites:
1) Fastboot installed and working. I used Linux Mint 18, but the OS is not relevant. There are are various threads discussing how to get this working, I am not covering it.
2) You need a factory firmware image that is the same version or newer than what you have installed (see below for more info), for me with a Moto X Pure Edition (XT1575) and wanting the latest MPH24.49-18-4 firmware, I used the image from this thread and extracted it into it's own directory. In Windows it is best to place this in the same folder as fastboot (probably the platform-tools folder)
XT1572 Factory Images: http://dl.prazaar.de/?dir=Android/XT1572/Factory courtesy of @Prazaar
XT1575 Factory Images: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 - UPDATE: Direct link to XT1575 for 24.49-18-8 (Sept 1, 2016 security update) uploaded on 1/27/2017 courtesy of Motorola Firmware Team. The December 2016 security update image is NOT available as of yet!
Alternate firmware source for Pure and Style: https://firmware.center/firmware/Motorola/
XT1575 OTA ZIP file to go from 18-8 to 18-16 ONLY is available in this post for sideloading thanks to @annoyingduck
NOUGAT FIRMWARE (XT1575 ONLY): https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
OPTIONAL: 2a) Because when doing this procedure when you are done the logo when booting will still say your bootloader is unlocked, we can fix this by downloading the logo from this thread and extracting the bin file to the same folder as above.
Now, open a terminal or command window into the directory that contains the firmware files you extracted above, on Linux or Mac this could be anywhere, in my example I will use /home/acejavelin/Downloads/MXPE/18-4 as the directory, in Windows this will likely be the same as where your fastboot binary or platform-tools directory is, and follow these commands entering them ONE AT A TIME, do not just copy and paste the entire section. If you are using Linux, I recommend executing "sudo su" prior to beginning to prevent permission errors (this is shown in my sample attachment).
Code:
fastboot oem lock begin (see notes below if not wanting to lock)
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot
Note that in place of "fastboot flash logo logo.bin" you can substitute "fastboot flash logo XT1575-logo-new-9-14-15.bin" and it will work and validate at the end, and you will NOT get the bootloader unlocked screen any longer... I tested this and verified it to work.
This will return your bootloader status to LOCKED, although STATUS will still show 2, and your software status to OFFICIAL... It will pass SafetyNet for Android Pay, Pokemon GO, and banking/financial apps.
Remember that you will get checked for FRP even with this procedure, so either remove your Google account prior to this or know your credentials. This procedure will not bypass Factory Reset Protection in any way.
If you are interested in returning to stock WITHOUT locking the bootloader, then follow the above commands, but the following commands in place of the "lock" commands in the list above:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
The procedure for other XT157x device like the Style would be identical, except substitute your appropriate factory image. Note that different firmwares may contain a different number of system.img_sparsechunk.X files, you must flash the number you have in your firmware image in order. From what I have seen, most 5.1.1 firmwares have ten (0-9), 6.0 has nine (0-8), 6.0.1 has twelve (0-11), and 7.0 has ten (0-9) sparsechunks, but always verify with the XML flash file contained within the firmware archive to verify if you are in question.
If you lock with this process, you can unlock the bootloader again and even use the same unlock token... subsequent unlocking will wipe data as well. Doing this procedure will set OEM Locking option in Developer options to disabled, although it is perfectly safe to leave it like this, I suggest turning it on immediately since your warranty is gone and if something does go wrong you have the ability to unlock again to fix it.
NOTE: You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin). At this point you can either continue the flash and NOT lock the bootloader at the end, or stop until you can find the most current image. Moto used to be quite willing to hand these out when they were requested, so if you have a very new firmware installed you may not find one that you can use to relock with on the Internet. Part of the requirements to lock the bootloader is you must successfully flash the partition table (gpt.bin) in order to complete the lock process, if you can't then the bootloader lock process cannot be finished.
Also, some users have noted that after completing this process the software status does NOT go back to "Official", if it does not, upon accepting the OTA it should go back to official after the OTA is successful. The Status Code will always show 2 (relocked) or 3 (unlocked), and it can never go back to 0 (locked).
A proper flash log is attached to this guide.
Just a blurb on Marshmallow software versions... To determine what you need look at version/build numbers, here is the Security update dates and release dates (actual, not tests) of all known public OTA releases of Marshmallow for the Moto X Pure (Style varies somewhat). The initial release was MPH24.49-18 (sometimes MPH24.49-18_18, we don't know why, but it is the SAME versions), and all others after that are MPHS24.49-XX-XX as shown below.
18 or 18_18 - The initial (shipped) Marshmallow release for Moto X Pure, November 2015 (release via OTA in late-December 2015, incorrectly dated on Moto's official website as 01-SEP-16 in the "official" recovery images section, it is NOT the newest or recommended image to use)
18-3 - February 2016 (released for OTA in mid-March 2016)
18-4 - May 2016 (released for OTA in late-June 2016)
18-8 - September 2016 (released for OTA in early-November 2016)
18-16 - December 2016 (release for OTA in mid-February 2017) *** Not available as a factory image***
Nougat:
NPH25.200-22 - September 2017 (released for OTA September~November 2017) Factory image available as of 11/12/2017
NPH25.200-23 - Little is know about this version, it appears to be slowing rolling out to Verizon users only as of mid-November 2017 (no firmware available as of yet)
To see what version your bootloader is now, go into fastboot and perform a "fastboot getvar ro.build.fingerprint" and look at the output, it should be pretty clear.
NOTE: I no longer own this device, but will help where I can and will keep this thread open to assist users where ever possible, but I no longer have a device to test/verify things with.

acejavelin said:
*** This will relock your bootloader, but it does NOT restore your warranty in any way, so don't ask ***
So with Nougat coming, several people have asked how to return to stock to get the update... well, I just did this so here is a quick guide.
Prerequisites:
1) Fastboot installed and working. I used Linux Mint 18, but the OS is not relevant. There are are various threads discussing how to get this working, I am not covering it.
2) You need a factory firmware image, for me with a Moto X Pure Edition (XT1575) and wanting the latest MPH24.49-18-4 firmware, I used the image from this thread and extracted it into it's own directory. In Windows it is best to place this in the same folder as fastboot (probably the platform-tools folder)
OPTIONAL: 2a) Because when doing this procedure when you are done the logo when booting will still say your bootloader is unlocked, we can fix this by downloading the logo from this thread and extracting the bin file to the same folder as above.
Now, open a terminal or command window into the directory that contains the firmware files you extracted above, on Linux or Mac this could be anywhere, in my example I will use /home/acejavelin/Downloads/MXPE/18-4 as the directory, in Windows this will likely be the same as where your fastboot binary or platform-tools directory is, and follow these commands entering them ONE AT A TIME, do not just copy and paste the entire section. If you are using Linux, I recommend executing "sudo su" prior to beginning to prevent permission errors (this is shown in my sample attachment).
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Note that in place of "fastboot flash logo logo.bin" you can substitute "fastboot flash logo XT1575-logo-new-9-14-15.bin" and it will work and validate at the end, and you will NOT get the bootloader unlocked screen any longer... I tested this and verified it to work.
This will return your bootloader status to LOCKED, although STATUS will still show 2, and your software status to OFFICIAL... It will pass SafetyNet for Android Pay and Pokemon GO as well.
Remember that you will get checked for FRP even with this procedure, so either remove your Google account prior to this or know your credentials. This procedure will not bypass Factory Reset Protection in any way.
The procedure for other XT157x device like the Style would be identical, except substitute your appropriate factory image.
A proper flash log is attached to this guide.
Click to expand...
Click to collapse
So, flash command for partition gpt.bin does work? I've never been able to lock bootloader due to failure to execute this command. But, I've always thought of downgrading, rather than flashing the same stock build!

donrojo said:
So, flash command for partition gpt.bin does work? I've never been able to lock bootloader due to failure to execute this command. But, I've always thought of downgrading, rather than flashing the same stock build!
Click to expand...
Click to collapse
Yes, of course it does... You can clearly see in the log I attached from my flashing the device.
The key is you cannot downgrade to a lower gpt.bin, you can only flash the same or newer version of firmware. After having several Moto devices, I can attest that downgrading successfully while locking is almost impossible. I will update my guide to make it clearer.
And please do not quote the entire first post and embed your comments in it, on mobile I had a very difficult time trying to determine what you were asking. EDIT: Sorry, your previous post looked very different in the XDA app, looks fine on computer... weird.

What is the purpose of relocking your bootloader? The unlocked bootloader has never interfered with me taking an OTA.

Thank you for this guide.
I have a question.
I'm currently on a relatively recent nightly of CM13, which I believe is based on 6.0.1.
I don't think the XT1575 ever got 6.0.1, only 6.0.
Is there a way around this issue other than waiting for 7.0 to hit officially?

quakeaz said:
What is the purpose of relocking your bootloader? The unlocked bootloader has never interfered with me taking an OTA.
Click to expand...
Click to collapse
You are correct, and this as nothing to do with accepting OTA (that is just how this discussion came up), but the lock/unlock state of the bootloader has two distinct issues I can think of although there maybe more I am forgetting.
1. Security - If your bootloader is unlocked, anyone who gets access to your device can just fire up fastboot and boot TWRP and access any information on your device, even if it is encrypted since TWRP can read the encryption password.
2. SafetyNet API - Do to recent changes by Google, SafetyNet API checks to fail just because the bootloader is unlocked, even if everything else is perfectly stock... SafetyNet is a mandatory part of Play Services that auto-updates itself regardless of your settings, and it is used to see if your device has been modified (rooted) or tampered with in anyway, and applications can use SafetyNet to check the status of your device... Sounds harmless enough, but for example this means that even an unlocked bootloader will make it so you can't use Android Pay or many other financial apps or even play Pokemon Go. Until recently, SafetyNet could be fooled with apps like RootCloak or Suhide, but Google has updated it to detect these things and look far beyond simple rooting. UPDATE: This only seems to be enforced on devices that shipped with Nougat or newer, and does seem to effect any device upgraded to Nougat so far. Lollipop and Marshmallow devices are not effected.

acejavelin said:
Sounds harmless enough, but for example this means that even an unlocked bootloader will make it so you can't use Android Pay or many other financial apps or even play Pokemon Go. Until recently, SafetyNet could be fooled with apps like RootCloak or Suhide, but Google has updated it to detect these things and look far beyond simple rooting.
Click to expand...
Click to collapse
Interesting, I've used Android Pay with my bootloader unlocked on the MXPE (otherwise stock, no root).
If you decide to unlock the bootloader again, I assume the original code supplied by Motorola is required? I've never relocked/unlocked.
Also, just an observation, I assume once we do get the Nougat (or any other) OTA, the unlocked bootloader warning screen will return, since the unlocked flag has already been tripped and the OTA will write a new logo.bin.
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
Mejilan said:
Thank you for this guide.
I have a question.
I'm currently on a relatively recent nightly of CM13, which I believe is based on 6.0.1.
I don't think the XT1575 ever got 6.0.1, only 6.0.
Is there a way around this issue other than waiting for 7.0 to hit officially?
Click to expand...
Click to collapse
You're fine to downgrade to the latest stock firmware you were running.

quakeaz said:
Interesting, I've used Android Pay with my bootloader unlocked on the MXPE (otherwise stock, no root).
If you decide to unlock the bootloader again, I assume the original code supplied by Motorola is required? I've never relocked/unlocked.
Click to expand...
Click to collapse
Have you used Android Pay since October 16-18, such as to add a payment method/card? Because that is when Google made the changes to the SafetyNet API, and has committed to aggressively maintaining it to detect and report all "tamper" situations.
Yes, the original code works... Tested it myself, locked, unlocked, and locked again, works perfectly, and if you wish you can request the code again from Motorola if you lost the email or something, but it will still be the same code.

quakeaz said:
You're fine to downgrade to the latest stock firmware you were running.
Click to expand...
Click to collapse
Ah hah! Good to know.
Thank you.

acejavelin said:
Have you used Android Pay since October 16-18, such as to add a payment method/card? Because that is when Google made the changes to the SafetyNet API, and has committed to aggressively maintaining it to detect and report all "tamper" situations.
Yes, the original code works... Tested it myself, locked, unlocked, and locked again, works perfectly, and if you wish you can request the code again from Motorola if you lost the email or something.
Click to expand...
Click to collapse
Thanks for confirming about the unlock/relock/unlock.
I just added a CC to check if it'd work. No issues here. Maybe it's only certain devices? Google Play Services 9.8.77.

Mejilan said:
Thank you for this guide.
I have a question.
I'm currently on a relatively recent nightly of CM13, which I believe is based on 6.0.1.
I don't think the XT1575 ever got 6.0.1, only 6.0.
Is there a way around this issue other than waiting for 7.0 to hit officially?
Click to expand...
Click to collapse
The issue isn't the aftermarket firmware or it's version, it could be Android 29 Gamma for all we care... You need to use an official Moto firmware that is at least the same version or newer than your bootloader and partition table (gpt.bin), if you are not a stock firmware you will need to do some investigating via the baseband version what actual version you have (unless you can remember the last official firmware version).
Safest bet is just use the current release, if you can't find it online you can always request it from Moto service but this may take several days (weeks in some areas I have heard). Be aware that the firmware posted on Moto's official is NOT the most current and is likely a downgrade if you have ever accepted an OTA since the device was released.

quakeaz said:
Thanks for confirming about the unlock/relock/unlock.
I just added a CC to check if it'd work. No issues here. Maybe it's only certain devices? Google Play Services 9.8.77.
Click to expand...
Click to collapse
All I know is it didn't work for me on BrokenOS anymore, neither did Pokemon Go (not that big deal though), so I figured go all in...
There are multiple articles on this online, here are just a few...
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
http://www.androidpolice.com/2016/1...unlocked-android-phones-android-pay-affected/
http://www.androidcentral.com/andro...u-unlock-your-bootloader-and-thats-good-thing

acejavelin said:
The issue isn't the aftermarket firmware or it's version, it could be Android 29 Gamma for all we care... You need to use an official Moto firmware that is at least the same version or newer than your bootloader and partition table (gpt.bin), if you are not a stock firmware you will need to do some investigating via the baseband version what actual version you have (unless you can remember the last official firmware version).
Safest bet is just use the current release, if you can't find it online you can always request it from Moto service but this may take several days (weeks in some areas I have heard). Be aware that the firmware posted on Moto's official is NOT the most current and is likely a downgrade if you have ever accepted an OTA since the device was released.
Click to expand...
Click to collapse
Understood, thank you.
I haven't been on stock since the first half of the year.
I honestly don't remember if my last stock build was 5.1.1 or 6.0, but regardless, I should be good to go if I just download the newest stock and attempt your tutorial.
Again, many thanks.

Does the relocking procedure wipe userdata like unlocking does? I am considering relocking as most of the Android Pay issues with unlocked bootloader seem to be with N. I'm already running stock so I was thinking I could just begin lock process, reflash same stock images, complete lock, skipping the erase userdata command.

quakeaz said:
Does the relocking procedure wipe userdata like unlocking does? I am considering relocking as most of the Android Pay issues with unlocked bootloader seem to be with N. I'm already running stock so I was thinking I could just begin lock process, reflash same stock images, complete lock, skipping the erase userdata command.
Click to expand...
Click to collapse
Probably, my assumption is you can't complete the process without erasing cache and userdata, as 'fastboot oem lock' will likely fail, but to be honest I did not test it. Basically to get it complete you must follow all steps of the flashing XML file in the firmware file.

acejavelin said:
Probably, my assumption is you can't complete the process without erasing cache and userdata, as 'fastboot oem lock' will likely fail, but to be honest I did not test it. Basically to get it complete you must follow all steps of the flashing XML file in the firmware file.
Click to expand...
Click to collapse
Interesting. I may give it a shot, if I do I'll report back here. The erase userdata and cache commands are optional according to Motorola.com factory image download page instructions. I've done normal stock reflash without them.

quakeaz said:
Interesting. I may give it a shot, if I do I'll report back here. The erase userdata and cache commands are optional according to Motorola.com factory image download page instructions. I've done normal stock reflash without them.
Click to expand...
Click to collapse
Good luck... Let me know how it goes, but I think that only works for developer models, on "normal" models you have to do oem lock begin before oem lock though, not the same process.

delete wrong thread

Can't seem to boot up
Hi, so I flashed using this guide, I'm using the XT1572 model in the UK and used the appropriate firmware etc, my issue is that after everything had finished and I rebooted, it was stuck booting for an hour, I know this phone can sometimes take a while to boot after a factory reset but I haven't experienced it this badly before, also, I flashed the moto splash screen image but the boot animation is still the one from AICP :/ any help would be appreciated guys

JIMMMEHHHH said:
Hi, so I flashed using this guide, I'm using the XT1572 model in the UK and used the appropriate firmware etc, my issue is that after everything had finished and I rebooted, it was stuck booting for an hour, I know this phone can sometimes take a while to boot after a factory reset but I haven't experienced it this badly before, also, I flashed the moto splash screen image but the boot animation is still the one from AICP :/ any help would be appreciated guys
Click to expand...
Click to collapse
Your flash didn't take... Do you have a log of flash attempt from the terminal?
Also, sometimes the firmware has different numbers of system sparse chunks, it's not always 8, and sometimes it only has "system.img" as a single file, you have to flash what it shows in the XML file contained within the firmware archive.

Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)

Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)
Firmwares
the latest firmware as of time of writing is February's 2020 OTA (BECKHAM_RETAIL_9.0_PPWS29.131-27-1-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC) = https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
previous OTAs RETAIL variant can be found here = https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
future OTAs possibly here = https://androidfilehost.com/?w=search&s=beckham
other variants = https://mirrors.lolinet.com/firmware/moto/beckham/official/
Unlock Bootloader
first you need to install Motorola Drivers = https://support.motorola.com/us/en/solution/MS88481
- ATTENTION - use the most up-to-date ADB Drivers otherwise will brick if older version is used; instead of downloading ADB elsewhere which is often old version, get it directly from GOOGLE, here = https://dl.google.com/android/repository/platform-tools-latest-windows.zip
now you can proceed to unlock bootloader = https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
TWRP
get the official TWRP here = https://dl.twrp.me/beckham/
- ATTENTION - if you just want root access, then there's no need to install TWRP, just boot from the .img once using the latest version
use TWRP to make a backup of EFS partition before installing anything, store the backup files outside of the device
if you want custom ROMs or GSI, then you will need to install TWRP installer .zip into the recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the latest .zip version in the recovery partition. Unfortunately the only official installable version of TWRP that exists is bugged, and the TWRP developers haven't fixed it yet, go talk to them ask for some love, be respectful = https://github.com/TeamWin/android_device_motorola_beckham/issues
Magisk
install Magisk using the new&correct method AKA "Boot Image Patching Method" to be able to install OTA later = https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
when OTA arrives, you may manually install it whilst retaining Magisk by carefully following these instructions = https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
- ATTENTION - you won't be able to install stock OTAs if you use older method or if system partition is modified, be really careful to not alter the hash of the partitions

Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45

@heynando, what is the difference between "retail" and "retus"? Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?

ritchea said:
@heynando, what is the difference between "retail" and "retus"?
Click to expand...
Click to collapse
RETUS is short for Retail + US.
The difference between RETUS and RETAIL is, I imagine, cannot confirm, the same RETAIL firmware with some US regional modifications such as bloatware or CSC thing
you can check which model is yours in SETTINGS > SYSTEM > ABOUT PHONE > SOFTWARE CHANNEL. Or in the bootloader by running the command
Code:
fastboot getvar product
you can find the entire list of product codes here = https://mirrors.lolinet.com/firmware/moto/readme-en.html#listone
XT1929-4(Canada, SS, 4+32GB) XT1929-3(NA/Sprint, SS, 4+32GB)
XT1929-4(NA/AMZ/BWACA/RETCA/RETUS/USC, SS, 4+64GB)
XT1929-5(BRAZIL/RETBR/TIMBR/TEFBR, DS, 4+64GB / 6+128GB)
XT1929-6(LATAM/AMXLA/NIIPE/ATTMX//TEFCL/TEFPE/RETLA/RETAR/RETMX/RETCL/AMXMX, DS, 4+64GB)
XT1929-6(LATAM/RETLA/TEFCO/TIGCO, DS, 6+128GB)
XT1929-8(EMEA_APAC/RETEU/DTEU, DS, 4+32GB / 4+64GB)
ritchea said:
Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
Click to expand...
Click to collapse
I believe that's the internal version of the software. If the number changes that emphasizes there has been software changes and/or tweaks in the system and/or firmware. If the number doesn't change, then it's just a regular security patch with no further modifications in system and/or firmware.

Thanks for that info. Yeah, I know mine has the retus software channel. I just couldn't find or figure out if Retail was actually one word or if it was a combo of ret+ail. That version has a LOT of software posted.

I flashed retail on an EU model. And after it the software channel say Reteu just like the original. Also the model number is as it should be. In my opinion you can flash retail firmware on us and EU models.

confirmed that this firmware is working on XT1929-4
these are the steps I took:
downloads and setup
install moto drivers (in windows, not needed for linux)
install android tools (adb and fastboot)
downloaded official TWRP
downlaoded and extracted the firmware
backup of partitions (including efs)
Code:
adb reboot bootloader
fastboot boot twrp_recovery.img
backed up lots of partitions
rebooted system
copied the TWRP backup files to my pc for safe keeping
set the fastboot slot (i did this because many of teh fastboot commands below were failing)
Code:
adb reboot bootloader
fastboot --set-active=a
rebooted back into bootloader
installed the firmware
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
installed magisk the new good way
did the initial device setup
installed magisk manager
copied the boot.img from the extracted firmware above to the phone.
followed these steps for boot img patching and install of magisk https://topjohnwu.github.io/Magisk/install.html#boot-image-patching

sirkuttin,
Thanks for the detail how to. That worked perfectly for me, and my moto z3 play, same model as yours. I could not get the ota or even lenovo smart assistant to work on my phone. It basically had it locked up, stuck on the boot logo. I'm assuming its the old way of install magisk that caused that. This got me on the latest firmware release, and then installed magisk the new way. Lenovo smart assistant was useful in downloading the firmware.
Thanks.

Hi I tried the new magisk install way. I'm on XT1929-4_BECKHAM_RETUS_9.0_PPW29.183-29-1, copy boot.img and patched it to magisk_patched.img. Then after fastboot flash boot /path/to/magisk_patched.img and a reboot, i'm not stuck on the motorola powered by android screen. Verity mode is set to disabled.
I tried holding down the power button to simulate a battery pull but no luck, the screen just stays on. Can anybody give me any advise? I think now I have to just wait till the device is out of juice. Never experience this before.
---------- Post added at 02:16 PM ---------- Previous post was at 01:31 PM ----------
So the battery pull is "Power + Vol Down". I was able to flash the PPW29.183-29-1 firmware and get it going again. I noticed it tried to upgrade me to PPW29.183-29-1-2 so I must have been on newer firmware. I flashed the magisk_patched and am rooted now.

It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).

ch3mn3y said:
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
Click to expand...
Click to collapse
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.

heynando said:
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
Click to expand...
Click to collapse
It, unfortunately, does... However I csnnot update (continous update unsuccesful) :f Have to check if Xposed module is not a reason.
And You probably could use Installer to flash stock recovery? If not TWTP itself however I've never checked if one for Play has access to recovery partiotion to flash images. It should gave if it can be done using the installer...
Sent from my Moto Z3 Play using Tapatalk

ch3mn3y said:
However I csnnot update (continous update unsuccesful)
Click to expand...
Click to collapse
Me too and it drove me nuts, I did patch the /boot partition with the original file, but the OTA app still failed to install, even after reboot. And there's no useful data in the logcat to debug the app. So I gave up and had to use Titanium to freeze the OTA app otherwise it would keep trying to download and install infinitely.
ch3mn3y said:
:f Have to check if Xposed module is not a reason.
Click to expand...
Click to collapse
It's probably not because I don't use it and the OTA method didn't work me either
ch3mn3y said:
And You probably could use Installer to flash stock recovery?
Click to expand...
Click to collapse
Yes you're right, I agree there..

heynando said:
Yes you're right, I agree there..
Click to expand...
Click to collapse
Just checked the inside of the installer zip file and it won't work. Still once every 3 months it wouldn't be a problem to connect device to PC and flash recovery.img with fastboot.
Is there a list with a commands and order how to flash Z3 Play images of official firmware? I want July patches and have some problems, so clean reflash is what I need.
Additional question is if I have to use "-u" when flashing second and other system images? Remember I had to do it with my X Play coz of unlocked bootloader and here I have one in the same state as well. If yes than could someone tell me where to put it, coz I'm not sure...

tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?

tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?

Ramble2k said:
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Click to expand...
Click to collapse
This one, make sure to get the latest. https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/

Hi, I'm trying to unlock my Moto Z3 Play bootloader, but I don't get the code on CMD, but only a few numbers ... The version of my device is PPW29.131-27-1-11, channel RETBR software.
Someone went through this, can you tell how to reverse this situation?

I couldn't get the bootloader unlocked for xt1929-4. I tried different computers, Linux and win. Have latest adb and fastboot. When fastboot OEM get_unlock_data is given, I says counttas slot not found etc., can someone help?

It may seem obvious, but you
checked OEM unlocking and USB Debugging?

[Guide] Restoring Black Shark 1 Global to Stock

Hello, this is not a guide for noobs.
At this point, i assume your BlackShark 1 is running a custom ROM, or a modification, and not it cannot update over OTA.
This guide helps you restore your BS1 SKR-H0 to Stock ROM, hopefully you can update it when the next OTA comes out.
This guide sets one of your partitions at system update G66X1906170OS00MPX.
You agree that by performing these operation, you risk bricking your device. I will probably not be there to help you recover.
There are a few steps:
Flash the stock images
Re-encrypt storage
Re-flash the stock files
Flash the stock images
Download the full backup from here: https://mega.nz/#!IZFAEAoC!UMHJ0drlhoHyGtV-0KYrtteC1VMP8-eqFWWrMXLZikQ
Extract the backup
Enter fastboot mode on your phone
Check which slot you are on, and which slot is definitely working. Try this on a slot that is broken, or that is not 100% working (in my case, slot a)
Run the following command for every partition:
Code:
fastboot flash <partitionname>_<slotname> <filename>
example: fastboot flash boot_a boot_a (if the slot you are overwriting is slot a)
or fastboot flash boot_b boot_a (if the slot you are overwriting is slot b)
Once finished, boot twrp, flash disableforceencrypt and magisk, and reboot into the system.
Reencrypt storage
First of all, backup ALL YOUR INTERNAL STORAGE, as it WILL GET WIPED IN THIS STEP. i warned you.
Once the system boots with the new version, go into stock recovery (adb reboot recovery, or enter bootloader > select start recovery)
Then reboot into the system. once the system boots, go to settings, security, encryption, and enable encryption. The phone should encrypt now. Wait for it to start encryption, finish, and get stuck at boot animation. This is the end of step 2.
Re-flash the stock files
This is the final and easiest step. If previous steps were performed correctly, then all you have to do now it the following:
from the stuck bootanimation, reboot to bootloader.
Flash 1 more time system, boot and vendor partition. This time DO NOT flash disableforceencrypt and magisk.
reboot into stock recovery
perform a wipe 1 more time.
reboot the system.
If done correctly, your phone should go into first time setup, with the stock OS, no internal error on boot, and you should be able to accept OTAs when they come. If OTA fails, Follow step 4:
(Optional) OTA Shows up again after finishing, and keep failing
If you restored your BlackShark to stock, and OTA does not finish (keeps coming back up), do the following:
If your backup is from slot a, and you are on it right now, run the following commands:
Make sure you are on the correct slot, with the correct backup!
Code:
fastboot flash boot boot_a.img
fastboot flash system system_a.img
fastboot flash vendor vendor_a.img
fastboot flash dsp dsp_a.img
fastboot flash devcfg devcfg_a.img
fastboot flash bluetooth bluetooth_a.img
fastboot flash dtbo dtbo_a.img
fastboot flash modem modem_a.img
fastboot flash vbmeta vbmeta_a.img
For the partitions dtbo and devcfg, i'm not sure if they need reflashing, however i found out that the others might be changed indirectly, and cause OTA to fail.
So just reflash those partitions from backup (Make sure to use the correct version/slot!)
Finally, if update still fails, you can connect your phone to pc, run adb logcat, and watch the logs just after update download is finished. If it fails, you will find some lines about a failed partition, with the partition name.
Special thanks to @leipnacht who provided me with stock file, so that i could restore my phone.

Big Thanks to this! I'm glad the stock files helped restoring your phone. This will surely help xda users as well when somethings go wrong with root coz some games will ban you if your phone is detected as rooted phone. This is very useful reference for everyone.

i need this for CN version too:crying::crying:

help
How do I install and recover my black shark please?
when I have install via fastboot I get a message
FAILED remote flashing is not allowed for critical partitions.
way of doing the command on fastboot
fastboot flash partitionabl_a abl_a
fastboot flash partitionsystem_a system_a
Sorry, I do not understand much about this.

metamorfose123 said:
How do I install and recover my black shark please?
when I have install via fastboot I get a message
FAILED remote flashing is not allowed for critical partitions.
way of doing the command on fastboot
fastboot flash partitionabl_a abl_a
fastboot flash partitionsystem_a system_a
Sorry, I do not understand much about this.
Click to expand...
Click to collapse
It's fastboot flash abl_a abl_a
Etc... If you want to overwrite slot a, or
Fastboot flash abl_b abl_a
If you want to overwrite B.

needful guide for restoring black shark. Big thumb up for this post.

@gilbert32 thanks for your hard work! I'll check to see if I can find someone with a stock CN rom and see if this will work for it. I haven't had the phone until now because a family member temporarily needed one :good:

hi, i have a problem, after flash system i get only on S logo

geed301 said:
hi, i have a problem, after flash system i get only on S logo
Click to expand...
Click to collapse
What version are you on? Which black shark?

SKR-H0 in oreo 8.1, but i resolved hahaha, i was used
fastboot flash boot boot_a.img
fastboot flash system system_a.img
fastboot flash vendor vendor_a.img
Just copy and pasted hahaha , today i updated to P and its great
Thnks for the tutorial and sorry for my bad english

Hi! I do not understand. One month ago I used this tutorial and I could get the previous little OTA update. Now I tried again do the same steps, all of them, and I can't get the OTA. I tried it 5 times… I have a question, in this new update of android Pie is the camera slow motion enabled? Can someone upload the android Pie backup for flashing directly?

FasterBit said:
Hi! I do not understand. One month ago I used this tutorial and I could get the previous little OTA update. Now I tried again do the same steps, all of them, and I can't get the OTA. I tried it 5 times… I have a question, in this new update of android Pie is the camera slow motion enabled? Can someone upload the android Pie backup for flashing directly?
Click to expand...
Click to collapse
I didn't find any slow motion option in camera. When you try OTA, open adb logcat at the same time. It should show you an error regarding which partition was modified when OTA fails.
It's probably one of: Boot, System, Modem, DSP, DTBO, Bluetooth, Vendor (maybe also other ones)

i need stock global ota package
do you have it yet?

hoangtieubao said:
i need stock global ota package
do you have it yet?
Click to expand...
Click to collapse
I have a backup of the global pie rom, i can upload it within this week.

gilbert32 said:
I have a backup of the global pie rom, i can upload it within this week.
Click to expand...
Click to collapse
i have solution to full convert rom to global
but i still dont have skr-h0 ota package full base
i need it to do

i have cn version OTA package, after flash
it can use *#1027# to fully convert to chinese version , ota works fine.
maybe you need to ask blackshark to provide a Full OTA request to your phone. just say your phone is rooted ,and cannot update anymore, need a full ota to restore it.
we use this trick to get cn version full ota package and it works

Vlin.Wang said:
i have cn version OTA package, after flash
it can use *#1027# to fully convert to chinese version , ota works fine.
maybe you need to ask blackshark to provide a Full OTA request to your phone. just say your phone is rooted ,and cannot update anymore, need a full ota to restore it.
we use this trick to get cn version full ota package and it works
Click to expand...
Click to collapse
this trick is very nice
and could you do it to get full ota for us?
i think too many people to want it

Any chance to find the global rom for black shark 2 pro.. DLT-A0
Any chance to find the global rom for black shark 2 pro.. DLT-A0
I need to make the phone supports multi language
Please help

Help Needed
Hi All,
Hope all is well.
Could anyone please help post a noob guide for this. I've flashing rooting etc thinf before but this one's really confusing for me. I would appreciate it greatly. I have a facebook group of BS1 Global user and they all wanted to restore their smartphone, I referred them to this thread but none of them seems to understand this tutorial. Pardon our ignorance. We would really appreciate it greatly.
Thanks in advance!

Hi Gilbert,
Thank you so much for posting this.
Your effort is greatly appreciated by us.
I am new to BS1 Global and I haven't done flashing rooting etc to this phone.
It would really help if there could be a step by step tutorial for users like me.
I would like to ask what files/tools are needed for this tutorial. I probably need pc? And probably need to install something on pc like drivers? What are they?
I'm guessing I need to unlock bootloader and root my bs1 global?
Also need to install twrp for bs1 global? And I don't know this disablforceencrypt and magisk thing.
Please please help post a noob tutorial for bs1 global that haven't been modified yet.
That would really be helpful, I look forward to your response. Thank you so much in advance.

[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

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
OH MY GOD YOU JUST SAVED MY LIFE!

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.

Coming from an OP3T need help regarding the new partitions

I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I would really appreciate it if anyone can explain the additional steps that would be required to do this on the 8T

It's a very different world with the 8T (I also come from a 3T).
The 8T has A/B partitions as well as virtual A/B partitions. It also supports streaming OTA and seamless OTA updates. It has fastboot and fastbootd.
There's lots of good information on all of this in:
Virtual A/B Overview | Android Open Source Project
source.android.com
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
platform/system/update_engine - Git at Google
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
And more on this at the same site.
And, if you get into serious trouble, the unbricking tool is really easy to use and works wonderfully.

pratyush28 said:
I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I wouls really appreciate it if anyone can explain the additional steps that would be required to do this on the same thing on an 8T.
Click to expand...
Click to collapse
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.

dpryor88 said:
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
Click to expand...
Click to collapse
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.

pratyush28 said:
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
Click to expand...
Click to collapse
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.

dpryor88 said:
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
Click to expand...
Click to collapse
Thanks mate, I won't hesitate to ask if I need help once I get the new device

@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?

pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
I have the other model. Unbrick tool works fine on mine.

pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.

BillGoss said:
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
Click to expand...
Click to collapse
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?

pratyush28 said:
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
Click to expand...
Click to collapse
Yes, I installed a couple of custom ROMs and they were fine.
The only place I know that matters is the xbl and xbl_config partitions. The full OOS ROMs have an extra -lp5 set of files that get flashed on lp5 phones instead of the "normal" xbl files.
But since this only applies to firmware and the xbl partitions are never touched by custom ROMs, there cannot, therefore, be incompatibilities due to lp4 vs lp5.