A friend brought a HTC One Mini in a very unusual situation to me. The phone bootloader is "Locked" and "S-ON". It only boots to fastboot usb mode only. The battery is still ok because I checked with a script that is used to charge in that mode when the battery is low; at least it still has about 3870mV, and the minimum is around 3680mV. The problem is that:
1. When I try to unlock so I can flash a custom TWRP recovery the unlock spalsh screen does not appear, although the unlock command says sucessful.
C:\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s
Click to expand...
Click to collapse
2. I downloaded this stock file OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip because it matches the OS version showing on the fastboot screen on the phone. When I try to flash it from fastboot I get this error:
C:\fastboot-win>fastboot flash zip OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip
sending 'zip' (346477 KB)...
OKAY [ 16.826s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 49.466s
Click to expand...
Click to collapse
Can anyone please render any help? I can follow any instructions to the letter, just that I have never come across this kind of issue before.
Thanks in advance.
My HTC One Mini has developed a problem where it will not turn on, it just keeps loading up the Fastboot screen. If I power down or restart the device many times, I can get lucky and it will boot the OS. Right now, that seems to not be working.
If I select the Bootloader option and go to Recovery, it just flashes up the 3 Android guys on skateboards and goes back to Fastboot. Reboot and Reboot Bootloader both reboot the phone, but I end up at the Fastboot menu again. Also, if I power down, it doesn't show the charge animation, it just jumps back into the Fastboot menu, unless I have removed power/USB from the device and then it will power off.
I've read quite a few forum posts, too many I think, and I'm not stuck on what to do/try. Any help would be great, I currently have no phone!
ScottHelme said:
My HTC One Mini has developed a problem where it will not turn on, it just keeps loading up the Fastboot screen. If I power down or restart the device many times, I can get lucky and it will boot the OS. Right now, that seems to not be working.
If I select the Bootloader option and go to Recovery, it just flashes up the 3 Android guys on skateboards and goes back to Fastboot. Reboot and Reboot Bootloader both reboot the phone, but I end up at the Fastboot menu again. Also, if I power down, it doesn't show the charge animation, it just jumps back into the Fastboot menu, unless I have removed power/USB from the device and then it will power off.
I've read quite a few forum posts, too many I think, and I'm not stuck on what to do/try. Any help would be great, I currently have no phone!
Click to expand...
Click to collapse
While at fastboot, connect the USB to pc and flash a new recovery again using the command ( fastboot flash recovery recoveryfile.img )
htc_one_mini_m4 said:
While at fastboot, connect the USB to pc and flash a new recovery again using the command ( fastboot flash recovery recoveryfile.img )
Click to expand...
Click to collapse
I get this:
C:\Users\Scott\Downloads\Android\Android>fastboot flash recovery TWRP-2.6.3.0.img
target reported max download size of 800227328 bytes
sending 'recovery' (8572 KB)...
OKAY [ 1.267s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.161s
ScottHelme said:
I get this:
C:\Users\Scott\Downloads\Android\Android>fastboot flash recovery TWRP-2.6.3.0.img
target reported max download size of 800227328 bytes
sending 'recovery' (8572 KB)...
OKAY [ 1.267s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.161s
Click to expand...
Click to collapse
Are you bootloader unlocked & s-off ?
htc_one_mini_m4 said:
Are you bootloader unlocked & s-off ?
Click to expand...
Click to collapse
I followed a guide to unlock the bootloader and got the following:
C:\Users\Scott\Downloads\unlock>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.013s]
finished. total time: 0.171s
I don't get a prompt on the device and when I reboot, it still says ***LOCKED *** at the top.
ScottHelme said:
I followed a guide to unlock the bootloader and got the following:
C:\Users\Scott\Downloads\unlock>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.013s]
finished. total time: 0.171s
I don't get a prompt on the device and when I reboot, it still says ***LOCKED *** at the top.
Click to expand...
Click to collapse
You followed the steps from the HTCdev.com site ?
http://www.htcdev.com/bootloader/
Geniuses of the internet!
I am in desperate need of help.
Basically yesterday morning I was greeted with an update notification and being none the wiser I just accepted and thought everything would be ok. Silly me.
Since then my phone has done nothing but boot loop. First to the black screen with Google and the unlocked pad lock, but after some playing I now have a white Warning Bootloader Unlocked message.
I have tried flashing a stock ROM or two with Fastboot and some tools but I cant get the sodding thing to boot up.
Whenever I try to Fastboot files to my phone, the first few files always fail with the same warning
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.140s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.447s
It might be worth mentioning that this was a Virgin Mobile phone which I flashed to GPe.
So now all I want is to flash my phone to a stock GPe ROM and get the bloody thing working again.
PLEASE HELP!
Ross
Update #1
I flashed Philz to the phone but when trying to sideload the rom, I get a error: device not found message. Fastboot picks up the phone find, I am using minimal ADB and Fastboot install and I have all the latest USB drivers from Motorola.
Also the two files that fail from Fastboot leave a message on the phone
version downgraded for primary_gpt and version downgraded for tz
Still wont boot though.
Update #2
I installed the SDK and tried sideloading and still no dice
Update #3
I found a gpt.bin file in these forums that now does flash, but the motoboot.img still fails
Hi, I have been testing the SafetyNet api and I made a serious mistake, I decided to close the bootloader of my Moto Maxx, but I did not take into consideration that although I had the last published rom of my region installed, I did install an update via OTA, which I understand prevents me from installing the rom I have, since it seeks to install the rom + update, even worse, forget to click on the option "allow oem unlock" so I can not reopen the bootloader, the last rom published for my region is the XT1225_QUARK_RETLA_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml, but it does not let me flash it, I have tried all published so far, but I have only been partially lucky with the rom QUARK_VERIZON_6.0.1_MCG24 .251-5-5_cid2_subsidy-DEFAULT_CFC.xml, which I believe already comes with the security OTA update and lets me flash gpt.bin, but since it is from another region it does not let me flash recovery or system.img, will there be someone who have the last Latin American rom or at least the recovery.img to try to revive my smartphone?, sorry for my clumsy English and thanks in advance.
Well, I finally found a ROM that fix my error, if someone else goes through the same thing you can download it in
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
terenos said:
Well, I finally found a ROM that fix my error, if someone else goes through the same thing you can download it in
QUARK_RETBR_6.0.1_MPGS24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
I could have pointed you to this version by @bhb27 here:
XT1225_QUARK_RETBR_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml.zip
https://www.androidfilehost.com/?fid=385035244224403573
Fast download. But I thought you wanted RETLA version.
Looking again, the one you found may be slightly newer than what @bhb27 has posted? @bhb27, is that one he found newer?
70.2-7 (his) vs 70.2-2. (yours)
See the difference?
BUILD REQUEST INFO:
SW Version: quark_retbr-user 6.0.1 MPGS24.107-70.2-7 7 release-keysMDM9625_104438.245.02.85R
MBM Version: 70.96
Modem Version: MDM9625_104438.245.02.85R
FSG Version: UNKNOWN
Build Fingerprint: motorola/quark_retbr/quark_umts:6.0.1/MPGS24.107-70.2-7/7:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.211.7.quark_retbr.retbr.en.BR
Model number: Moto Maxx
Android Version: 6.0.1
Baseband Version: MDM9625_104438.245.02.85R
Build Number: MPGS24.107-70.2-7
Build Date: Tue Jan 17 04:30:18 CST 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_b_default_v1.0.nvm
Regulatory Info (eLabel): None
Blur Version: Blur_Version.24.211.7.quark_retbr.retbr.en.BR
Version when read from CPV: quark_retbr-user 6.0.1 MPGS24.107-70.2-7 7 release-keys
Click to expand...
Click to collapse
ChazzMatt said:
I could have pointed you to this version by @bhb27 here:
XT1225_QUARK_RETBR_6.0.1_MPGS24.107-70.2-2_cid12_subsidy-DEFAULT_CFC.xml.zip
https://www.androidfilehost.com/?fid=385035244224403573
Fast download. But I thought you wanted RETLA version.
Looking again, the one you found may be slightly newer than what @bhb27 has posted? @bhb27, is that one he found newer?
70.2-7 (his) vs 70.2-2. (yours)
See the difference?
Click to expand...
Click to collapse
Sorry for that, I thought I needed the specific ROM of my region, but finally it was not like that, anyway thank you very much.
On the other hand, it seems that the version I found is a bit newer.
terenos said:
Well, I finally found a ROM that fix my error, if someone else goes through the same thing you can download it in
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Thanks. Same Here. Flash with RSD Lite and all OK. Thanks!!!
I flashed the full stock rom with RSD Lite and relock the bootloader, but the message warning bootloader unlocked already shows... Please, How to remove this message?
MelquiXDA said:
I flashed the full stock rom with RSD Lite and relock the bootloader, but the message warning bootloader unlocked already shows... Please, How to remove this message?
Click to expand...
Click to collapse
Not sure why you relocked your bootloader when you can use Magisk to hide that.
But it's easy to replace the unlocked bootloader warning. How do you want to do it -- via ADB (fastboot) or TWRP? Besides which method, choose which boot logo below you wish to replace the warning? The warning is just a graphic, and you will replace it with another graphic -- like one of the Motorola logos below.
Here's some custom boot logos from my Moto Maxx/Moto Turbo guide. Works on all Quarks -- Droid Turbo/Moto Turbo/Moto Maxx. Your choice of colors of the Motorola M logo. Very classy.
Install either via ADB (fastboot) or TWRP. Both choices are offered.
____________
BOOT LOGOS
You can just reflash your choice of boot logo to replace the unlocked warning screen. It's just a static image Motorola insists on showing you that your bootloader is unlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know, I UNLOCKED it on purpose!
Here's boot logos (not to be confused with boot animation -- the boot logo is what you see before the boot animation starts) you can flash with ADB. Various colors of the Motorola M logo.
Remove annoying bootloader unlocked warning
* ADB FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68538894&postcount=2
And here's the same boot logos you can flash with TWRP:
* TWRP FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68579272&postcount=5
Works for all Quarks (XT1254/XT1250/XT1225).
* Black and White
* Black and Teal
*White and Teal
* Black and Red
(The last three with color are custom graphics made by @fenix3nk0r3 .
* added another boot logo to my Quark guide... posts #2 (ABD) and post #5 (TWRP flashable) to include Dark Google ATAP:
Thanks to @XDleader555 for the splash logo I found in Moto X Pure forum -- but I adapted it for our Quarks so it would not be upside down. The other bundled elements are taken from the Black & Teal boot logo file ("recovery", "bootloader", etc) but the splash screen is this black artistic Motorola logo. For the TWRP flashable file I utilized @bhb27's excellent logo flasher app. Post #3 is ADB, post #5 is TWRP flashable.
ChazzMatt said:
Not sure why you relocked your bootloader when you can use Magisk to hide that.
But it's easy to replace the unlocked bootloader warning. How do you want to do it -- via ADB (fastboot) or TWRP? Besides which method, choose which boot logo below you wish to replace the warning? The warning is just a graphic, and you will replace it with another graphic -- like one of the Motorola logos below.
Here's some custom boot logos from my Moto Maxx/Moto Turbo guide. Works on all Quarks -- Droid Turbo/Moto Turbo/Moto Maxx. Your choice of colors of the Motorola M logo. Very classy.
Install either via ADB (fastboot) or TWRP. Both choices are offered.
____________
BOOT LOGOS
You can just reflash your choice of boot logo to replace the unlocked warning screen. It's just a static image Motorola insists on showing you that your bootloader is unlocked.
I know, I UNLOCKED it on purpose!
Here's boot logos (not to be confused with boot animation -- the boot logo is what you see before the boot animation starts) you can flash with ADB. Various colors of the Motorola M logo.
Remove annoying bootloader unlocked warning
* ADB FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68538894&postcount=2
And here's the same boot logos you can flash with TWRP:
* TWRP FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68579272&postcount=5
Works for all Quarks (XT1254/XT1250/XT1225).
* Black and White
* Black and Teal
*White and Teal
* Black and Red
(The last three with color are custom graphics made by @fenix3nk0r3 .
* added another boot logo to my Quark guide... posts #2 (ABD) and post #5 (TWRP flashable) to include Dark Google ATAP:
Thanks to @XDleader555 for the splash logo I found in Moto X Pure forum -- but I adapted it for our Quarks so it would not be upside down. The other bundled elements are taken from the Black & Teal boot logo file ("recovery", "bootloader", etc) but the splash screen is this black artistic Motorola logo. For the TWRP flashable file I utilized @bhb27's excellent logo flasher app. Post #3 is ADB, post #5 is TWRP flashable.
Click to expand...
Click to collapse
Thanks. I flashed the logo.bin with locked bootloader sussessfully.
I used the 01 file of this site:
https://maxximizar.wordpress.com/2016/06/24/logos-moto-maxx-droid-turbo-moto-x-style/
MelquiXDA said:
Thanks. I flashed the logo.bin with locked bootloader sussessfully.
I used the 01 file of this site:
https://maxximizar.wordpress.com/2016/06/24/logos-moto-maxx-droid-turbo-moto-x-style/
Click to expand...
Click to collapse
OK. That's very close to the White/Teal above - just a lighter shade of teal.
terenos said:
Well, I finally found a ROM that fix my error, if someone else goes through the same thing you can download it in
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Sorry to bump the thread. Someone have a mirror to this version?
I made the same mistake and now I need a 23.107-70.2-7 image.
Regards
I have Indian moto turbo xt1225. Till now I am using different Rom after boot loader unlocked lastyear. Last week I have planned to sell my phone. so I decided to relock boot loader. So I put command OEM lock in fast boot and bootloader got locked. The sad thing that I have forgotten to tick allow OEM unlock in developer option before doing this. Now my phone is bricked and bootloader is in locked condition. I can't push any Rom or recovery via adb or fast boot because of locked bootloader. I googled how to unlock bootloader in fast boot mode, but no solution is seen. Sombody says flashing factory firmfare via rsd lite solve the problems as it doesn't need uncloked bootloader. But when I flashing mtoturbo lollipop Indian factory version given in this forum, flashing failed message came in rds lite .flashing failed boot.img like errors. Kindly help
sreenash said:
I have Indian moto turbo xt1225. Till now I am using different Rom after boot loader unlocked lastyear. Last week I have planned to sell my phone. so I decided to relock boot loader. So I put command OEM lock in fast boot and bootloader got locked. The sad thing that I have forgotten to tick allow OEM unlock in developer option before doing this. Now my phone is bricked and bootloader is in locked condition. I can't push any Rom or recovery via adb or fast boot because of locked bootloader. I googled how to unlock bootloader in fast boot mode, but no solution is seen. Sombody says flashing factory firmfare via rsd lite solve the problems as it doesn't need uncloked bootloader. But when I flashing mtoturbo lollipop Indian factory version given in this forum, flashing failed message came in rds lite .flashing failed boot.img like errors. Kindly help
Click to expand...
Click to collapse
Searching in the web i found the latest firmware for xt1225 (is retbr, but its ok for india and other LA moto):
https://drive.google.com/file/d/1slulWTBMw833L30PMbVEFKf6XRoJuLQK/view?usp=sharing
if you need the mfastboot and "automated" flash, here is the folder i used:
https://drive.google.com/file/d/1-KrMlXplGWzMx7BWutXePNxqRmOQip50/view?usp=sharing
I hope it helps you.
Pls see the flash screen. It didnt work for me
C:\ADB>echo off max-sparse-size: 268435456 finished. total time: 0.000s target max-sparse-size: 256MB sending 'partition' (32 KB)... OKAY [ 0.016s] writing 'partition'... (bootloader) This may take a few seconds, if a (bootloader) different partition table is being (bootloader) flashed since we need to backup (bootloader) and restore a few partitions (bootloader) Flashing primary GPT image... (bootloader) Flashing backup GPT image... OKAY [ 0.172s] finished. total time: 0.187s target max-sparse-size: 256MB sending 'motoboot' (2163 KB)... OKAY [ 0.078s] writing 'motoboot'... (bootloader) flashing sbl1 ... (bootloader) flashing aboot ... (bootloader) flashing tz ... (bootloader) flashing sdi ... (bootloader) flashing rpm ... OKAY [ 0.452s] finished. total time: 0.530s target max-sparse-size: 256MB sending 'radio' (85620 KB)... OKAY [ 2.777s] writing 'radio'... (bootloader) flashing modem ... (bootloader) flashing mdm1m9kefs1 ... (bootloader) flashing mdm1m9kefs2 ... (bootloader) flashing mdm1m9kefs3 ... OKAY [ 1.420s] finished. total time: 4.196s target max-sparse-size: 256MB sending 'logo' (2712 KB)... OKAY [ 0.094s] writing 'logo'... OKAY [ 0.062s] finished. total time: 0.156s target max-sparse-size: 256MB sending 'boot' (16384 KB)... OKAY [ 0.515s] writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.811s target max-sparse-size: 256MB sending 'recovery' (16400 KB)... OKAY [ 0.515s] writing 'recovery'... (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.811s target max-sparse-size: 256MB sending 'system' (262143 KB)... OKAY [ 8.315s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 8.424s target max-sparse-size: 256MB sending 'system' (239764 KB)... OKAY [ 7.628s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 7.644s target max-sparse-size: 256MB sending 'system' (250695 KB)... OKAY [ 7.940s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 7.956s target max-sparse-size: 256MB sending 'system' (255001 KB)... OKAY [ 8.081s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 8.096s target max-sparse-size: 256MB sending 'system' (257746 KB)... OKAY [ 8.174s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 8.190s target max-sparse-size: 256MB sending 'system' (261982 KB)... OKAY [ 8.284s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 8.284s target max-sparse-size: 256MB sending 'system' (262140 KB)... OKAY [ 8.299s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 8.315s target max-sparse-size: 256MB sending 'system' (247037 KB)... OKAY [ 7.784s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 7.800s target max-sparse-size: 256MB sending 'system' (262140 KB)... OKAY [ 8.284s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 8.299s target max-sparse-size: 256MB sending 'system' (219553 KB)... OKAY [ 6.942s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 6.942s erasing 'cache'... OKAY [ 0.031s] finished. total time: 0.031s erasing 'userdata'... OKAY [ 0.203s] finished. total time: 0.203s erasing 'clogo'... OKAY [ 0.031s] finished. total time: 0.031s ... OKAY [ 0.016s] finished. total time: 0.016s ... OKAY [ -0.000s] finished. total time: -0.000s ------------------------------------------------------------------------- please scroll up and check your flash for any errors ------------------------------------------------------------------------- Press any key to continue . . .
---------- Post added at 10:11 AM ---------- Previous post was at 09:48 AM ----------
Is this because of invalid signed image
sreenash said:
I have Indian moto turbo xt1225. Till now I am using different Rom after boot loader unlocked lastyear. Last week I have planned to sell my phone. so I decided to relock boot loader. So I put command OEM lock in fast boot and bootloader got locked. The sad thing that I have forgotten to tick allow OEM unlock in developer option before doing this. Now my phone is bricked and bootloader is in locked condition. I can't push any Rom or recovery via adb or fast boot because of locked bootloader. I googled how to unlock bootloader in fast boot mode, but no solution is seen. Sombody says flashing factory firmfare via rsd lite solve the problems as it doesn't need uncloked bootloader. But when I flashing mtoturbo lollipop Indian factory version given in this forum, flashing failed message came in rds lite .flashing failed boot.img like errors. Kindly help
Click to expand...
Click to collapse
With locked bootloader you have to flash the same or newer firmware for your region than what you had. Every firmware release, no matter how minor, has a new bootloader version.
With an UNLOCKED bootloader you can fastboot all the way back to other region Kitkat 4.4.4 if you wish. Moto Turbo XT1224 launched with Lollipop but Latin America countries had Kitkat for their XT1225. You can flash any region, any version of XT1225 firmware -- IF the bootloader is unlocked, as long as you exclude GPT.bin from your flash commands.
With locked bootloader, you can only flash the region for your XT1225 (India) and only the latest date firmware ever installed or you can update to even newer.
The problem is in India, the "most recent" firmware which was delivered via OTA was NEVER released as full image file. Most are looking for this file: The problem is Motorola apparently never publicly released the India (RETEU) "GS" region full image version of this firmware. They only released the partial image OTA.
XT1225_QUARK_RETEU_6.0.1_MPGS24.107-70.2_cid7_subsidy-DEFAULT_CFC.xml
So, you have to go to a Motorola Service Center for them to install it for you. See here for more information.
https://forum.xda-developers.com/showpost.php?p=77072321&postcount=5
ChazzMatt said:
With locked bootloader you have to flash the same or newer firmware for your region than what you had.
Click to expand...
Click to collapse
Can I flash it in fastboot with twrp stock image backup taken earlier
sreenash said:
Can I flash it in fastboot with twrp stock image backup taken earlier
Click to expand...
Click to collapse
No, not in fastboot you cannot flash TWRP images.