Database Develop

Looking for 24.11.18.victara_retca.retca.en.ca recovery ROM

I seem to have lost my recovery image backup that I made before installing TWRP. I currently have 24.11.18.victara_retca.retca.en.ca installed on my phone, but can't get the most recent OTA because of this. I'm on WIND Mobile in Canada, though I don't know if there's any difference between that and standard retail.
Does anyone have a lead on the 24.11.18 stock recovery (or full ROM)?

egerlach said:
I seem to have lost my recovery image backup that I made before installing TWRP. I currently have 24.11.18.victara_retca.retca.en.ca installed on my phone, but can't get the most recent OTA because of this. I'm on WIND Mobile in Canada, though I don't know if there's any difference between that and standard retail.
Does anyone have a lead on the 24.11.18 stock recovery (or full ROM)?
Click to expand...
Click to collapse
Download the full firmware, and keep it:
VICTARA_RETCA_XT1097_6.0_MPE24.49-18_cid14_CFC.xml.zip
https://firmware.center:8081/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
EDIT: Extract the zip, if you're still on 5.1 then flash the full firmware:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
I doubt there will be a full firmware with the May 2016 patch.
(I have the XT1097 from Wind)

Gus Ghanem said:
Download the full firmware, and keep it:
VICTARA_RETCA_XT1097_6.0_MPE24.49-18_cid14_CFC.xml.zip
EDIT: Extract the zip, if you're still on 5.1 then flash the full firmware:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
I doubt there will be a full firmware with the May 2016 patch.
(I have the XT1097 from Wind)
Click to expand...
Click to collapse
Hi Gus (or anyone else who reads this),
Will this process reset my phone? I flashed the recovery ROM, as that's all I thought I needed, but now I think the "pre-flight checks" on the OTA are failing, i.e. some OS file on my device isn't correct. Is there a way to flash just the OS without resetting the whole device?
Cheers,
Eric

egerlach said:
Hi Gus (or anyone else who reads this),
Will this process reset my phone? I flashed the recovery ROM, as that's all I thought I needed, but now I think the "pre-flight checks" on the OTA are failing, i.e. some OS file on my device isn't correct. Is there a way to flash just the OS without resetting the whole device?
Cheers,
Eric
Click to expand...
Click to collapse
Did you flash stock recovery from the same firmware version that you already had on your phone?
In order to get OTA's, the OS must be pure stock; ALL files have to be stock. If you've never flashed 6.0 before, you will need to upgrade the Bootloader and Partition Table, which probably wipes all partitions.
Are you trying to preserve data/files/apps? I think you should back up your files before attempting anything.
The May 2016 patch is probably the last OTA this device will ever receive, that's why I'm running CM13, and soon we will get CM14 Nougat.
I don't think there's a way around it, if you want a pure factory stock device, you'll have to reset it (flash ALL the firmware files).
---------- Post added at 11:17 AM ---------- Previous post was at 11:03 AM ----------
You can try flashing the exact firmware version you have on your phone now, like this:
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

Thanks. Flashing everything and not erasing userdata worked.

System status back to Official

I have tried to flash Stock rom and relock bootloader already but System Status still : Modified
Anyone can help me?

When I had a Moto G4 Plus, when I upgraded via OTA (from 6.0 to 7.0) the status changes, I do not know if the Moto X4 will do the same
How do you block the bootloader? can you teach me? I already want to block it and I can not without mentioning that at the beginning I get the message of this one and I have to press the power button to advance :/

You need official signed stock images to flash which have not been released by Lenovo. There's no return from unlocking the bootloader currently.

Neffy27 said:
You need official signed stock images to flash which have not been released by Lenovo. There's no return from unlocking the bootloader currently.
Click to expand...
Click to collapse
That means i need to blink it to Lenovo shop to flash back to original signed rom right?

lol right

Signed ROMs: https://androidfilehost.com/?w=files&flid=229118
Payton_ = Retail
Payton_Fi = Android ONE
Payton_AMZ = AMAZON
THIS WILL WIPE ALL YOUR DATA AND THE SECURITY PATCH MUST TO BE THE SAME AS YOU HAVE NOW OR ABOVE for example Retail 8.1 - 1 April Security Patch.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase clogo
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
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 flash boot boot.img
fastboot oem lock
If your bootloader is already block you can skip this commands:
fastboot oem lock
fastboot oem lock
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 flash boot boot.img
fastboot oem lock
instand of they you can use:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase clogo
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fasboot reboot

lucasbitencourt said:
Signed ROMs:
Payton_ = Retail
Payton_Fi = Android ONE
Payton_AMZ = AMAZON
THIS WILL WIPE ALL YOUR DATA AND THE SECURITY PATCH MUST TO BE THE SAME AS YOU HAVE NOW OR ABOVE for example Retail 8.1 - 1 April Security Patch.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase clogo
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
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 flash boot boot.img
fastboot oem lock
If your bootloader is already block you can skip this commands:
fastboot oem lock
fastboot oem lock
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 flash boot boot.img
fastboot oem lock
instand of they you can use:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase clogo
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fasboot reboot
Click to expand...
Click to collapse
Hi! I have Moto X4 XT1900-7 4/64 (Europe)
I have downloaded Retail ROM version, and did everything like you describe for devices with unlocked bootloader. And I have a problem. During the start i see "Your device has loaded a different operating system. Visit this link on another device: motorola [dot] com [slash] unlockbootloader…". Then device starts, but I can't connect it to my laptop via USB (I have also tried with another PC). It's charging, but there is no notification to choose connection mode. In settings the option "USB Not connected" is grey. Do you have any ideas?

MNelaer said:
Hi! I have Moto X4 XT1900-7 4/64 (Europe)
I have downloaded Retail ROM version, and did everything like you describe for devices with unlocked bootloader. And I have a problem. During the start i see "Your device has loaded a different operating system. Visit this link on another device: motorola [dot] com [slash] unlockbootloader…". Then device starts, but I can't connect it to my laptop via USB (I have also tried with another PC). It's charging, but there is no notification to choose connection mode. In settings the option "USB Not connected" is grey. Do you have any ideas?
Click to expand...
Click to collapse
On 8.1 there's a bug in April Security Patch the USB only works with de lockscreen security disabled. See if the June update is available for you, then update, if not, go to developer's options and check the option OEM Unlocker then flash this:
fastboot oem lock
fastboot oem lock
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 flash boot boot.img
fastboot oem lock
if oem lock doesn't works change to: fastboot flashing lock or oem relock
Some phones only clears the massage after a update.

It works properly only via mfastboot for me, don't really know why. Before you answered I have boot-looped my device (with no possibility to run adb/fastboot commands, ya). But mfastboot helped me to boot 8.0 Retail ROM from the link you mentioned before and then to lock Moto X OEM.

lucasbitencourt said:
Signed ROMs: https://androidfilehost.com/?w=files&flid=229118
Click to expand...
Click to collapse
Those are not signed or he wouldn't get that message. You can flash all the available copied payton ROMs all day manually to get the phone working.
@MNelaer - Go here to get your phone working again.

Neffy27 said:
Those are not signed or he wouldn't get that message. You can flash all the available copied payton ROMs all day manually to get the phone working.
@MNelaer - Go here to get your phone working again.
Click to expand...
Click to collapse
This ROMs are signed, and we can flash without unlock de bootloader.

Downgrade Pie To Oreo ?

I regret my English but I need your help update my X4 Oreo 8.1 Patch November to Pie 9.0, I have a da Fiio Q1 mark II which worked perfectly in Oreo 8.1 through OTG, after updating this stopped working normally , it connects and disconnects only until the smartphone restarts, is there a way to go back to oreo? It is not Fi project

Yes, the way is:
1. unlock bootloader (this erase all user data / internal storage)
2. flash Oreo full fastboot package

Comby_sk said:
2. flash Oreo full fastboot package
Click to expand...
Click to collapse
Someone might need to correct me, but I don't think you want to attempt to "downgrade" either of partition - gpt.bin or bootloader - bootloader.img (possibly others) so one doesn't potentially brick the device.
This is how it was on older Moto devices I owned.

jbaumert said:
Someone might need to correct me, but I don't think you want to attempt to "downgrade" either of partition - gpt.bin or bootloader - bootloader.img (possibly others) so one doesn't potentially brick the device.
This is how it was on older Moto devices I owned.
Click to expand...
Click to collapse
Flashing full fastboot package with correct script and unlocked bootloader doing this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
I downgraded many times my X4 from Pie to Nougat or from Pie to Oreo.

Comby_sk can I do it with this scribt?!
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot flash modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.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_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
PAUSE
fastboot reboot
RAW Paste Data

@tomtom_38 yes, you do.

many thanks

Touchscreen not working after flash, Ali Moto G6

Hello,
I followed the steps to install TWRP correctly, and then flashed ALI_RETAIL_9.0_PPSS29.55-24-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC that i got from https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ and the process worked correctly. However, I foolishly thought I had flashed the wrong build and then flashed ALI_OPS27.82-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC that I got from https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292
Now my phone boots fine, but the touchscreen does not work at all, neither in TWRP nor when booted into the firmware. Is there any hope?
Model is ali XT1925-6
If I burnt out a part, what parts are they and how difficult will it be to replace them?
Edit: I now realize that my carrier channel is retus, and I installed retail. However, the touchscreen did not fail on that rom

II firmware that you flashed you only linked to the whole thread, you didn't show the exact firmware that you tried to flash.
Why not just try the one for your firmware and your carrier from mirrors.lolinet.com
The firmware used first time should be fine if it works

madbat99 said:
II firmware that you flashed you only linked to the whole thread, you didn't show the exact firmware that you tried to flash.
Why not just try the one for your firmware and your carrier from mirrors.lolinet.com
The firmware used first time should be fine if it works
Click to expand...
Click to collapse
Thanks for your response,
I installed androidfilehost.com/?fid=818222786056029922 from the second thread.
I tried reflashing the first rom, but the touchscreen does not work there either. I've just downloaded and installed the correct rom, still no dice
Is it possible that the second rom burnt my digitizer?
Edit: the fingerprint sensor doesn't respond on the setup screen either, although I'm not sure if thats because it isn't working or it doesnt do anything on the setup screen

I think part of the problem may be that I cannot wipe system when installing a new rom; using adb shell twrp wipe system returns Error with wipe command value 'system', and I cannot access the touchscreen to do it via the UI. Are there any other ways to wipe system? fastboot erase system -w fails with Permission denied
Edit: I was able to erase system as well as data, cache, and dalvik before flashing. Still no change
The script I'm using to flash roms is
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.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 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 system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 userdata
fastboot erase DDR
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot

fisher_1 said:
I think part of the problem may be that I cannot wipe system when installing a new rom; using adb shell twrp wipe system returns Error with wipe command value 'system', and I cannot access the touchscreen to do it via the UI. Are there any other ways to wipe system? fastboot erase system -w fails with Permission denied
Edit: I was able to erase system as well as data, cache, and dalvik before flashing. Still no change
The script I'm using to flash roms is
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.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 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 system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
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 userdata
fastboot erase DDR
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Download the "newest" firmware for your device with matching SKU and software channel. Don't use someone else's script. The commands for flashing the firmware are in the flashfile.xml in the firmware zip. Extract it and check the commands. You can use XML to batch program to create your own batch script if you must use a script.
It's unlikely that flashing a firmware broke your hardware.
If it's software related, flashing the correct firmware should fix it.
If it's a hardware problem, then it won't. But official firmware isn't likely to cause hardware failure
The firmware package in the first post of that thread is pretty old.

Unfortunately it still is not working. I used the commands from flashfile.xml and flashed XT1925-6_ALI_RETUS_9.0_PPSS29.55-24-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC, the correct firmware, but nothing has changed.
On a side note, when I flash a file, I get the message (bootloader) is-logical: (partitionName) not found, althought I get an OKAY response so I'm assuming it flashes correctly.

I'm having the same issue, got the phone on July 12 and immediately started the unlocking/rooting process (that's what I bought the device for) following dejello's guide. Everything went perfect, phone was working all right for 2 days then on Monday morning after using the device for a while, I placed it in an upper pocket of my backpack drove home and next thing I know the touch screen isn't working, not even on TWRP . Hardware damage seems very unlikely on my case. I did a factory reset using a mouse, but I haven't been able to flash stock back. I'll try that later today and see what happens.
UPDATE: It was a hardware issue. Came home and flashed back to stock, still had no touch response. Since my software troubleshoot had no success I decided to give hardware a shot. I followed this video to disassemble the phone. I started tweaking the digitizer connector. With the phone still disassembled I turned it on and still no touch. Disconnected it again and blew some air with a hair dryer to it trying to remove any debris, connected it again and still no touch. Repeated the process a couple times and eventually the screen was responsive again. I think this specific device came with something loose or some dirt on it.

Can you relock the bootloader?

Title. Alternatively, can you still receive OTAs with an unlocked bootloader if the firmware is stock?
Currently the issue is that the firmware files you can find online throw a bad key error on the boot and recovery images, so it's not possible to lock the bootloader that way. Motorola also doesn't provide proper OTA packages to download (I asked the support) and an emergency recovery tool like Samsung Kies doesn't seem to exist for Moto.
What are my options here? I want to give the device to a relative and need everything to work.

I did it with this code on fastboot folder (Minimal ADB & Fastboot Portable 1.4.3) with the last firmware RETAIL PPSS29.55-37-4 and then use RSD Lite to re-flash the firmware, it worked for me. Do it under your own risk.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot oem lock
fastboot oem lock
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 flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash boot boot.img
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot oem lock
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin

Thank you, that worked perfectly!

HeavyHDx said:
Thank you, that worked perfectly!
Click to expand...
Click to collapse
@HeavyHDx I highly recommend to re-flash the firmware on RSD Lite (if you haven't did it) because it could be some errors with the NON-HLOS.bin, like no sound when calling, at least that happened with me.

How could it worked perfectly since some commands are non-sense??
The Moto g6 is a A-only device... So all commands for XXX_other.img or "_b.img" won't be executed.
The second thing is that this device has a "adspso.bin" file for partition "dsp". But the command here will flash a "dspso.bin" file.
What about /recovery???