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.

(Athene) Security Patch April Brazil - OTA

I've just received the April security patch. Just it. No Oreo.
OTA:https://drive.google.com/file/d/1nHOiasjpMbVQVP0gqMC_T_YSjBo-YEC-/view?usp=drivesdk

asks for permission to download the file, you can upload to another server the ota please

tazlooney89 said:
asks for permission to download the file, you can upload to another server the ota please
Click to expand...
Click to collapse
Try again, please. I think I've fixed the permission.

This Zip will work in...RETIN channel ...XT1643??

Thanks, it works correctly on model XT1641

preetvardhan said:
This Zip will work in...RETIN channel ...XT1643??
Click to expand...
Click to collapse
probably yes

Any improvements or fixes?

hello in twrp???
because I did via ota in an xt1626 and it only rebooted in recovery mode. I had to reinstall the rom stock from February 2018 with Original Recovery. deacupe for being lay in the matter I have the device 2 months ago had a reason i. thank you guys:good:

junin_BsB said:
hello in twrp???
because I did via ota in an xt1626 and it only rebooted in recovery mode. I had to reinstall the rom stock from February 2018 with Original Recovery. deacupe for being lay in the matter I have the device 2 months ago had a reason i. thank you guys:good:
Click to expand...
Click to collapse
Stock OTA updates are not usually flashable in TWRP - you must revert back to full stock to use OTA updates anyway (no root, no TWRP, fully unmodified device) as you found out. Unlocked bootloader status does not matter.

you officially received it from Motorola?

The OTA update installed successfully on XT1644 using the manual Recovery Install from SD Card procedure.
Sent from my Moto G (4) using Tapatalk

SnoopDoge said:
you officially received it from Motorola?
Click to expand...
Click to collapse
Yes, sometimes i get checking for updates and then...

alexandreantunez said:
Yes, sometimes i get checking for updates and then...
Click to expand...
Click to collapse
Yeah, Brazil and India appear to be the territories that get the updates first, then are steadily rolled out globally I still don't quite understand why thus far the US seem to get a different patch to everyone else though...
Here's some notes about the update and my experience of updating from a rooted NPJS25.93-14-15 device:
a) File name is Blur_Version.25.231.5.athene.retail.en.US. md5 checksum is: 25eacb6f2ddffe92c438465d068b6bad with a filesize of 40.8 MB.
b)From the OTA updater script, requires NPJS25.93-14-15 (Feb 2018) or NPJS25.93-14-18 (April 2018)
Code:
Package expects build thumbprint of 7.0/NPJS25.93-14-18/3:user/release-keys or 7.0/NPJS25.93-14-15/5:user/release-keys
c)Brings your device up to date with the 1 April 2018 security patch with build NPJS25.93-14-18. Looking at the OTA script, also updates boot/kernel, system, OEM.
d)Bootloader version still maintained at B1:07 (appears to be same version as Dec 2017/Feb 2018), and modem version ends in 62.02R (same as Feb 2018). I do not know if the bootloaders are exactly the same or if they have different signatures (with the same version). So our blankflash may still work or you may have some issues, I have no desire to test the blankflash...
Flashing this onto a rooted NPJS25.93-14-15 XT1642 retgb device was the same as previous OTA updates: unroot by re-flashing stock firmware, copying the OTA update to internal storage, then apply the OTA update.
I re-flashed the NPJS25.93-14-15 firmware from here https://forum.xda-developers.com/showpost.php?p=76337066&postcount=769 with the flashing commands further down. As my device was already on NPJS25.93-14-15, and I had not downgraded my device firmware at any point, I was comfortable skipping GPT/bootloader/modem (since they should not change except from firmware flashes), you could always flash them for peace of mind. If you ever downgraded, I would recommend a full flash. Also, I've backed up in TWRP and omitted the 'fastboot erase userdata' to preserve my data, but you may have to consider a factory reset should your device become unstable. You may also wish to consider flashing each command manually (via copy pasting to your ADB terminal) rather than using a script.
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 erase cache
fastboot reboot
This restored my device to a stock NPJS25.93-14-15 firmware without TWRP/root, but preserving my data. As normal with an unlocked bootloader, you will see 'Image signed with bad key' messages during flashing and the 'bad key' on the unlocked bootloader screen. After downloading the Blur_Version OTA update to my device's internal storage, I then booted to bootloader (with 'adb reboot bootloader' in the ADB terminal, without quotes), then selected to boot to recovery with the volume keys and then pressing the power key to select.
As before, in the 'no command' and fallen Android screen of the stock recovery, I pressed the power key first and then pressed the volume up key, holding both keys together for about a second before getting to the recovery menu (might take a few tries).
Once in the recovery menu, as before I tried to select 'Apply update from SD card', but my device complained of 'Internal and external memory cannot be mounted'. Selecting 'Mount /system' then using the 'Apply update via SD card' worked.
Using the volume and power keys to navigate to the OTA update in the Download folder, the installation then took about 5-10 minutes to install. I chose to wipe cache afterwards and then selected 'Reboot system now' to reboot.
One thing I noted, as with the previous NPJS25.93-14-15 OTA update, is that on the first boot after the update, my device showed the unlocked bootloader screen then got stuck on a black screen during the boot. I left it for about 1-2 min, afterwards holding the power button down to force a reboot then caused the device to reboot without issue and has been stable since then. You may encounter this or not, just something to be aware of.
The April 2018 stock update seems to feel quicker, at least compared to the Feb 2018 update, though early days yet. I still have my fingerprint sensor and IMEI are still present. It's also the April 2018 security patch, so whilst no Oreo, at least we're on a recent patch

Nice explanation there @echo92 .
BTW I have the April 2018 firmware ready for testing if anyone is willing to, on the retail variants. However it is better if you take modem/persist/fsg backup in TWRP if possible.
I will be updating my firmware thread once people test this on their models with the backup above mentioned. Please mention the device model and the channel you flashed it onto. Disclaimer as per the standard firmware pages: Take backup and proceed with caution, I don't own this file.
https://sourceforge.net/projects/st...FAULT_regulatory-DEFAULT_CFC.xml.zip/download

thanks @rajatgupta1998.....................bdw is there any possibility for us to an RevivorOS update

punchytoe said:
thanks @rajatgupta1998.....................bdw is there any possibility for us to an RevivorOS update
Click to expand...
Click to collapse
Soon [emoji769]
Sent from my Moto G (4) using Tapatalk

The April patch update has been released in India?

CMKdaGreatest said:
The April patch update has been released in India?
Click to expand...
Click to collapse
no, it seems like VERY few "lucky" (?) users received it like OP here

removed
---edit, flashed no issues

rajatgupta1998 said:
Nice explanation there @echo92 .
BTW I have the April 2018 firmware ready for testing if anyone is willing to, on the retail variants. However it is better if you take modem/persist/fsg backup in TWRP if possible.
I will be updating my firmware thread once people test this on their models with the backup above mentioned. Please mention the device model and the channel you flashed it onto. Disclaimer as per the standard firmware pages: Take backup and proceed with caution, I don't own this file.
https://sourceforge.net/projects/st...FAULT_regulatory-DEFAULT_CFC.xml.zip/download
Click to expand...
Click to collapse
running on xt1640 channel retbr

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?

[STOCK FIRMWARE][WINDOWS][OUTDATED] How to upgrade and clean wipe from Stock Android 10 to Stock Android 11 without OTA [Retail USA Channel]

NOTICE : As of June 15, 2022 you no longer NEED this method as the OTA for Android 11 has been released. This is here for those who don't get the OTA or need an upgrade from a clean reset manually using only the RSA tool.
Credits to : morpheus092511 over on the Lenovo Forums for tricking the Moto Tool into installing the stock firmware, and Chepr29 from the Lenovo Forums for the fastboot method that doesn't require the tool.
In fastboot on your PC after your extract the Android 11 firmware and have your device in recovery mode enter the following commands (back up your data this will clean wipe it!) :
Code:
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 recovery recovery.img
fastboot flash dtbo dtbo.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 flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot erase userdata
fastboot erase carrier
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
1. BACK UP ANY IMPORTANT FILES OR INFORMATION! DON'T FORGET TO BACK UP YOUR TWO FACTOR AUTHENTICATION CODES AS WELL! This method can be done with other firmwares, but I have only tested a clean wipe upgrade from stock Android 10 to 11 RETUS on the Motorola One Ace 5G (Unlocked from Amazon) and can't comment on other firmwares.
2. Windows ONLY! DOWNLOAD THE RSA software from Motorola that allows you to recover, backup, or flash stock firmware to your device.
https://download.lenovo.com/lsa/Releases/Rescue_and_Smart_Assistant_v6.1.1.9_signed_setup.exe
3. DOWNLOAD the retail Android 11 firmware for the Motorola One Ace 5G (Kiev) Retail USA / Unlocked from here :
https://mirrors.lolinet.com/firmware/moto/kiev/official/RETUS/XT2113-2_KIEV_RETUS_11_RZK31.Q3-45-16_subsidy-DEFAULT_regulatory-DEFAULT_R8_CFC.xml.zip
4. Go to C:\ProgramData\RSA\Download\RomFiles and extract the .zip folder here. You may need 7Zip, or WinRAR to do so. I recommend 7Zip as it's open source and free without nag popups.
https://www.7-zip.org/a/7z2107-x64.exe
5. Connect your phone to the PC via USB-C and shut it off. Hold volume down, and power on at the same time until the recovery screen shows.
6. The RSA software will detect your proper "latest" firmware automatically in fastboot mode, allow it time to download and wait until it's done, give it some time after it hits 100.00% because the program will begin decompressing and unzipping the stock firmware, but it will NOT tell you this, keep that in mind!
7. Under the same directory in Step 4, you should now have two folders. One that says 10 and 11 with almost the same naming convention, delete ALL of the files in the folder that RSA downloaded (the 10 folder), and copy and paste all of the files from (the 11 folder), but LEAVE the name of the folder the same as what it was when RSA downloaded it, don't change the name or you'll either have to re-name it back, or re-download the firmware once more and let it extract.
8. Go back to the RSA program and hit the yellow "Rescue" button. Don't touch your phone and leave it alone! All data will be erased and it will begin flashing the firmware from Android 11 without a single issue. If you have PIN or password locked your phone previously, upon first boot up Android will ask you for your previous device PIN before you can begin setting up the device initially.
NOTE : This should preserve your warranty, mine expired a few months ago and I haven't been able to confirm this 100% because of this. (we waited a LONG time for this update!) Since the process does NOT require your bootloader to be unlocked or modified in anyway whatsoever, I do NOT see how you could possibly void the warranty. As of this writing, I have NEVER attempted to even unlock my bootloader for stability purposes, and because rooting isn't a concern to me on this device. In fact, to my knowledge you are NO LONGER able to unlock the bootloader on Android 11, so proceed with caution if this is something you require! There may be a 3-day wait of being connected to the Internet before you are allowed to use the OEM Unlock function, please keep that in mind if this is an issue.
Since it is stock firmware, there are no functionality issues to be concerned with. Calling, 5G, camera, Bluetooth, NFC and other basic sensors and extra functionality work 100% to my knowledge after testing most functions myself for the better duration of a day, even my Fossil Gen 6 Android Wear 2.0 (updating to 3.0 soon) watch is functioning flawlessly over WiFI and Bluetooth with the new update.

Please note this method is now outdated, as the OTA has been released for Android 11.

TheLastSidekick said:
Please note this method is now outdated, as the OTA has been released for Android 11.
Click to expand...
Click to collapse
It does work though, for anybody needing (or just wanting) to recover from a blown system without having to wait for a Rescue download.
Also it's a bit irritating that 95-9 for RETUS never got uploaded to lolinet. And now since 11 is released, that's all you can get through RSA, because it INSISTS on upgrading the phone to the latest version.
(Edit/Add) I would just like to have 95-9 handy for emergency reflashing if ever needed, but now I can't get my hands on it anywhere . . . except on that "easy" website and I don't really trust it 100%.
NOTE: I just flashed an 11 upgrade (manually via fastboot) and there was only 0-9 sparsechunk files. No super.img_sparsechunk.10 to be found, either the file or in the servicefile.xml . . . ? This was specifically the KIEV_RETAIL_RZK31.Q3_45_16_subsidy_DEFAULT_regulatory_DEFAULT_R8_CFC.xml firmware . . .

Moondroid said:
It does work though, for anybody needing (or just wanting) to recover from a blown system without having to wait for a Rescue download.
Also it's a bit irritating that 95-9 for RETUS never got uploaded to lolinet. And now since 11 is released, that's all you can get through RSA, because it INSISTS on upgrading the phone to the latest version.
(Edit/Add) I would just like to have 95-9 handy for emergency reflashing if ever needed, but now I can't get my hands on it anywhere . . . except on that "easy" website and I don't really trust it 100%.
NOTE: I just flashed an 11 upgrade (manually via fastboot) and there was only 0-9 sparsechunk files. No super.img_sparsechunk.10 to be found, either the file or in the servicefile.xml . . . ? This was specifically the KIEV_RETAIL_RZK31.Q3_45_16_subsidy_DEFAULT_regulatory_DEFAULT_R8_CFC.xml firmware . . .
Click to expand...
Click to collapse
Yeah the whole thing is strange the way the way each firmware is slightly a different size between what is evidently the same Retail build.

Actually, there's an easier method using RSA rescue.
You can grab boot.img for rooting.

mingkee said:
Actually, there's an easier method using RSA rescue.
You can grab boot.img for rooting.
Click to expand...
Click to collapse
I was using Rescue tool for this, may I please ask you how you were able to grab the boot.img? Thank you in advance!
Also, for those wondering if using the method above if OTAs will continue to update the answer is 100% YES confirmed.

TheLastSidekick said:
I was using Rescue tool for this, may I please ask you how you were able to grab the boot.img? Thank you in advance!
Also, for those wondering if using the method above if OTAs will continue to update the answer is 100% YES confirmed.
Click to expand...
Click to collapse
After rescue, check C:\Program Data\RSA\Download\romfiles\
Check Kiev folder

Question Some new installation experiences

Hi there,
I don't know how first installation of Lineage (and probably other Android tastes) went, though I had some issues I would like to share for people trying to install another OS then factory setup in the future.
I bought a new fresh G100 four days ago and set it up with only wifi, no sim, just to enlock and install LOS.
As I read on the forums, it normally is taking 2-3 days before the button in developer settings is active and not greyed out anymore, though for me nothing changed. After three days I did a full reset and set it up with only wifi, no sim, and the button in developer settings was active.
I used the following drivers and SDK:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Drivers | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I used the following guides for unlocking:
Sign in to Motorola - Motorola Mobility LLC
Sign in to Motorola
motorola-global-portal.custhelp.com
Info about nio variants | LineageOS Wiki
wiki.lineageos.org
After unlocking in fastboot I did not reboot, though emmediately flashed the Lineage recovery.
The recovery from the LOS website was not booting so I installed TWRP:
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2-for-moto-edge-s.4303199/
This recovery was booting and there I flashed the copy-partitions-xxxx.zip and emmediately after I installed LOS.
The procedure above was not working for me as I ended up with a phone only booting in fastboot.
So what I did afterwards was the following:
Phone was already unlocked, so installed the latest firmware following the procedure here:
https://www.getdroidtips.com/firmware-moto-g100-xt2125-4/
So, downloading latest firmware flash files, extracting to a folder with fastboot etc.. in it, and entering the commands to flash the firmware.
After that I head all my partitions back.
Then I installed latest LOSrecovery.img from:
index - powered by h5ai v0.29.2 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.29.2 (https://larsjung.de/h5ai/)
build.lolinet.com
To be sure to have it in boot_a and boot_b I did:
fastboot flash boot_a <recovery.img>
fastboot flash boot_b <recovery.img>
This was working, so using adb sideload I now installed:
adb sideload copy-partitions-20220613-signed.zip
and the latest LOS:
adb sideload lineage-19.1-20220903-nightly-nio-signed.zip
(To use adb sideload you can go to "apply update" in LOS recovery and then "apply from ADB")
A working system, yes!
My questions at the moment;
- Is the official LOS recovery indeed not working, or am I doing something wrong?
When the above is true:
- I can not use the LOS update functionality as it is not possible to switch off updating recovery in settings?
- I have to disable LOS update and use adb sideload for updating?
In general:
- Is it possible to lock the bootloader again after the setup above, or do I have to keep it unlocked? Coming from Oneplus and there I could lock it again.
Hope it helps and am curious if the experiences from other people are the same.

For your last question, no, you can't relock the bootloader while on a custom rom for this device.

Today I tried again to install the LOS recovery from the official download page https://download.lineageos.org/nio
So in fastboot I did:
fastboot flash boot_a lineage-19.1-20220903-recovery-nio.img
fastboot flash boot_b lineage-19.1-20220903-recovery-nio.img
For your information; installation went without any issues. Recovery working fine, LOS booting fine, no issues.
So what went wrong the first time I do not exactly know, though I think the trouble came because of not rebooting after installation of LOS recovery and doing a full reset from within recovery to remove encryption.
Someone who can answer that?
That's it for now; a new happy G100 user!