Hi
I bought this phone off a reseller from bell (supposedly) anyways when I try to register on the virginmobile phone app there is a message that pops up saying download the mybell app to view your plans. Since I was able to unlock the bootloader I installed a different system and when I downloaded and installed the virginmobile phone app I got the same message about installing the mybell app. Could this be controlled by the radio that is installed ? And this is were things got weirder the baseband is listed as MSM86268P_1032.390.81.01P, TELUS_CUST (System version 210.12.50.falcon_umts.Telus.en.CA, android version 4.4.4) So both the baseband and system indicate something from telus, (a different canadian cell provider)...
So to summarize I got a phone that thinks it is a bell phone, but has a telus baseband and system.. When I flash the system and boot partition it still thinks it is a bell phone...
So questions
1) Could it be the baseband that is causing the phone to think it is bell ? If so what radio should I flash, I found a list here http://forum.xda-developers.com/showthread.php?t=2649763 can I use the US/Global one ?
2) I tried switch over to GPE using this thread http://forum.xda-developers.com/showthread.php?t=2646404
But kept getting errors while flashing, (like the following) is this because I am already on 4.4.4 ? Is there a different process to follow ?
...GPE_XT1032_KOT49H.M004_CFC.xml>fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.099s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.421s
thanks
Nz
Hi all,
I have been seeking for infos to solve my problems for days and so, eventually, I come to you, begging for your help.
My device is a Moto G 2014 XT1032 (Europe), unlocked and used to be on android lollipop stock (I upgraded it manually during Easter).
Following a wrong attempt to restore a backup, I have (almost) bricked my phone.
Here is what works : Fastboot but NOT adb, acess to recovery (clockwork) and that's it. The usb debugging is not activated.
Otherwise, the phone is stucks in a bootloop.
Here is what I get when I try to update the phone :
Code:
C:\>fastboot update pa_dlx.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\>
And when I simply try to flash the sip (in order to install it from cwm) :
Code:
C:\>fastboot flash zip pa_dlx.zip
target reported max download size of 536870912 bytes
sending 'zip' (205116 KB)...
OKAY [ 6.461s]
writing 'zip'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 6.508s
Voilà. I would warmly accept any help you could give me.
I thank you in advance,
M.
EDIT : Thanks to this guide : GUIDE Moto G Restore Stock Firmware, I managed to solve my problem.
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
IK1981 said:
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
Click to expand...
Click to collapse
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
bobby0724 said:
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Click to expand...
Click to collapse
Already tried this. Already fails at first command... When doing this for the first time, it takes up to one minute to get a response. When retrying, it fails immediately
Code:
~/Downloads/XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7_subsidy-DEFAULT_CFC__v2.xml# fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 55.425
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
therealduff1 said:
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
Click to expand...
Click to collapse
Thanks for your help. Tried it with your tool but as far as I could see I land in the same troubles.
Code:
OSPREY_RETEU_6.0_MPI24.65-33_cid7_subsidy
please move all of the firmware files into the moto toolkit directory (the same folder containing toolkit.py)
Please make sure usb debugging is turned on in developer settings, then type 'done' into this promptdone
error: device '(null)' not found
Has your device successfully loaded bootloader mode ? please type 'yes' if it has successfully loadedyes
Press enter to confirm you would like to upgrade to android marshmallow ;)
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 55.795s
Partition table has been flashed
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.438s
Bootloader has been flashed
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.172s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.530s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.093s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.094s
Stock marshmallow recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (238438 KB)...
OKAY [ 7.500s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 15.891s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (238552 KB)...
OKAY [ 7.492s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.608s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (256695 KB)...
One thing that confuses me is the fact that the tool tells me that I shall turn on the USB debug mode. However, since Android does not boot any longer, I have no chance to do this in the Settings. Is there any way to enable this debug mode in another way?
Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate
Hi !
I see that you have fixed your issue https://forum.xda-developers.com/showpost.php?p=71188370&postcount=1372 so I close this down
Cheers !
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.