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.

[Resolved!] OPWS27.2.1 - does not install

Hi !
So, my Moto X4 has some problem. I got a notification today that it's got a system update waiting (OPWS 27.2.1), so naturally I clicked the install button.
It downloaded whole 118MB package, but then, after 3 steps of installation it says that my Moto X4 has encountered some problems and the installation has not been finished (and no changes were made to the phone)
Now, I am not sure what to do, I've tried to factory reset the phone (no success after this, update does not install).
I think it maybe because I've flashed my phone with official software for european retail units (it was initially running T-Mobile branded software variant).
But what to do now ?

Seems that I have used incorrect script to flash official Android 8. Just one line is missing from it, it's not affecting phone functionality... but not allowing OTA update to install.
This is how the complete, working script should look like :
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 erase modemst2
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 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
In the script that I have used primarly, there was the line flashing logo.bin missing. After I added this line, and reflashed the phone, OTA installed without problems.
I suppose that the Moto Updater is calculating maybe filesystem checksum after OTA update installation, and because there was one component not updated, this failed every time. But this is just my, well, "wild guess".

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.

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???

Can't update my moto one power(p30 note), stuck on 8.1.0 oreo

Hello guy,
Ive bought Moto one power(p30 note) second hand,
Whenever i try to update it says "your device is up-to-date", I'm currently on Android 8.1.0.
before asking here I searched a lot and found incomplete solutions and tbh I don't want to brick the mobile.
that's why i decided to ask experienced people here and hopefully will be guided.
I want to update to android 10 if there is or any latest Official update.
Some info:
SKU: XT1942-2
Android: 8.1.0
Security patch level: September 1, 2018
Baseband v: M636_18.33.01.78R
If it needs more info kindly tell me.
I will be really thankful to you
you guys can direct me to related threads and videos about how to Update.
thank you

This is newest, download and unpack : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
When in folder, run in fastboot:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.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_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse

matibu06 is this going to completely wipe out the device storage? Is this Android 10?