Bricked Moto X 2014? Fastboot flashing, ADB sideloading, nothing seems to work
Hello,
I have this Moto X 2nd gen (XT1092), and I wanted to install an Android Marshmallow OS last weekend.
I did it according to this article on XDA: http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858 , where an install image plus small install description is posted.
This is the first ‘non-standard’ thing I tried with this phone. It is not rooted, nor did I make any changes in the settings for developers, apart from enabling USB debugging. The device was running an stock version of Android 5.1, which I received the normal way(just an automatic system update).
Using some 'fastboot flash....' commands via the PC, the image should be installed. However, upon trying the first command: 'fastboot flash partition gpt.bin', the terminal responded with:
-------------------------
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.102s
-------------------------
Afterwards, my phone didnt boot to android anymore. The only thing it does is put me in "AP Fastboot Flash Mode (S)"
I have tried installing different stock Motorola images/zips for my phone, in order to try to get it back to how it was, but for every fastboot flash I want to do (except for the boot logo), I get the preflash validation error.
I also tried sideloading images via ADB via the recovery mode, bit this doesn’t work either:
When I try "adb sideload <IMAGE>.zip", it starts to send the file to the phone, and the phone receives it. Very quickly after completing the transfer, though, the phone can say two things (depending on what .zip file I try):
1.
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of motorola/victara_reteu/victara:5.0/LXE22.46-19.1/1:user/release-keys or motorola/victara_reteu/victara:5.1/LPE23.32-25.1/1:user/release-keys; this device has motorola/victara_reteu/victara:4.4.4/KXE21.187-42/41:user/re
Installation aborted.
2.
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
One thing to note is that when I try 'adb devices', it gives me:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
TA99300SXJ sideload
-------------------------
It says that the device is in ADB sideload mode, which blocks me from using other ADB functions, like shell. Is there a way to get 'full' ADB acces?
I also tried using the official Motorola “RDS Lite” software, as some people say this can be used to correctly flash an image to the phone, but this program just does not see my phone.
I did install all drivers, and Windows recognizes the device correctly, in both fastboot and ADB (recovery) mode.
Another thing I wanted to do to solve this, is to unlock the bootloader, as some people on forums said that this would help. However, when I try “fastboot oem unlock UNIQUEKEY” with the key I got from the Motorola website, the bootloader responds with the message stating that I have to enable unlocking the bootloader via developer settings. And obviously, I cannot go to settings to enable this.
-------------------------
I’m very stuck here, and I would be the intensely happy if there would be someone around who can help me get my phone back to life!
I do have experience with flashing Android ROMs/Images/Zips, but not on Motorola devices.
I reckon that this:
“Package expects build fingerprint of motorola/victara_reteu/victara:5.0/LXE22.46-19.1/1:user/release-keys or motorola/victara_reteu/victara:5.1/LPE23.32-25.1/1:user/release-keys; this device has motorola/victara_reteu/victara:4.4.4/KXE21.187-42/41:user/re”
could possibly be caused by an incorrect zip file. If that is the case, is there any way to obtain the proper file?
I did read about some special micro USB cables connecting the normally unused pin 4. Could this be helpful?
Any help would be IMMENSELY appreciated. I'm not ready to give up the fight!
Kind regards,
Ostheer
This same thing happened to me today. Ive had my fair share of rooted phone issues but this one is a mystery to me. Ive rooted every other Moto device [G, G '14, X, X Pure] And now a new issue arises.
I used a .bat file from CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162 . It finished and booted into bootloader but wont go anywhere from there. I have a feeling Ive reset to a locked state with no boot file.
Device is LOCKED. Status Code:0
Software status: Modified
$ Normal Powerup
failed to validate boot img
boot up failed
fastboot oem get_unlock_data
(bootloader) could not get unlock data
boot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.040s
Just like you I tried several fixes and no luck.
1. ADB Lite: Same issue
2. mfastboot Same issue
3. RSD Lite: Does not recognize my devices (win 10 / sdk / all drivers / redownloaded 3 times)
4. any bat file I try / manual code / or adb all fail
There must be a solution to this. I want Marshmallow 6.0 just as much as the next guy to work on my phone. Thanks for the help
WhiteRaven96 said:
This same thing happened to me today. Ive had my fair share of rooted phone issues but this one is a mystery to me. Ive rooted every other Moto device [G, G '14, X, X Pure] And now a new issue arises.
I used a .bat file from CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162 . It finished and booted into bootloader but wont go anywhere from there. I have a feeling Ive reset to a locked state with no boot file.
Device is LOCKED. Status Code:0
Software status: Modified
$ Normal Powerup
failed to validate boot img
boot up failed
fastboot oem get_unlock_data
(bootloader) could not get unlock data
..... ..... .....
There must be a solution to this. I want Marshmallow 6.0 just as much as the next guy to work on my phone. Thanks for the help
Click to expand...
Click to collapse
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.
ostheer said:
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.
Click to expand...
Click to collapse
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk
AGISCI said:
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
@AGISCI,
Thank you for your reply. I am currently downloading the file you linked, and will try to flash it using mfastboot as soon as it finishes downloading.
I did indeed hear that using the OTA afterwards is not something you will want to do.
ostheer said:
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...-0-xt-1097-t3266858/post64274827#post64274827 POST #33
This I think is your delay. I just woke up today and noticed my phone now says UNLOCKED I didnt do anything else but attempt all my failed steps on another computer and a reboot [which had not been done since system failure. So it boot up like it was unlocked and didnt go further. Back to bootloader mode, let see if it works
YES! Got it to load up and boot using this 6.0 zip http://forum.xda-developers.com/moto-x-2014/development/rom-installation-rsd-t3263800
However now my SIM card isnt being recognized. Which ssems to happen all the time when using a file from another country. Isnt there a simple solution for this fix?
WhiteRaven96 said:
http://forum.xda-developers.com/mot...-0-xt-1097-t3266858/post64274827#post64274827 POST #33
This I think is your delay. I just woke up today and noticed my phone now says UNLOCKED I didnt do anything else but attempt all my failed steps on another computer and a reboot [which had not been done since system failure. So it boot up like it was unlocked and didnt go further. Back to bootloader mode, let see if it works
YES! Got it to load up and boot using this 6.0 zip http://forum.xda-developers.com/moto-x-2014/development/rom-installation-rsd-t3263800
However now my SIM card isnt being recognized. Which ssems to happen all the time when using a file from another country. Isnt there a simple solution for this fix?
Click to expand...
Click to collapse
That is great news! I am still downloading the zip AGISCI linked.
So if I'm correct, in the fastboot screen it now says "device is unlocked" for you?
What steps did you make to try to unlock the bootloader?
Also, am I correct to assume that you used fastboot/mfastboot to flash your zip in the end?
How is it possible? Your bootloader just got unlocked without root!
I will be more than happy if you explain again what you did and what happend exactly.
Thanks.
Whenever you flash a firmware meant for another region/carrier, you are also flashing the modem/radio that supports that region/carrier, so you have to find the firmware that supports your device/region/carrier and flash the modem/radio from it, in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
These are the files you need to flash "NON-HLOS.bin" and "fsg.mbn"
AGISCI said:
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The download completed, and I have tried flashing it using mfastboot:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
what I get is the following:
the gpt.bin and motoboot.img indeed failed, logo.bin, boot.img, recovery.img, NON-HLOS.bin and fsg.mbn succeeded.
the system.img_sparsechunk.X files give this:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot\VICTARA_RETEU_XT1092_5.1_LPE23.3
2-25.3_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256681 KB)...
OKAY [ 8.068s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.181s
-------------------------
while the phone responds with:
-------------------------
cmd: getvar:max-sparse-size
cmd: download:0faaa7a0
cmd: flash:system
version downgraded for system
Invalid PIV signed system image
-------------------------
Any ideas? This zip seemed to have done 'better' than other, but the phone still doesn't accept it.
ostheer said:
The download completed, and I have tried flashing it using mfastboot:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
what I get is the following:
the gpt.bin and motoboot.img indeed failed, logo.bin, boot.img, recovery.img, NON-HLOS.bin and fsg.mbn succeeded.
the system.img_sparsechunk.X files give this:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot\VICTARA_RETEU_XT1092_5.1_LPE23.3
2-25.3_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256681 KB)...
OKAY [ 8.068s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.181s
-------------------------
while the phone responds with:
-------------------------
cmd: getvar:max-sparse-size
cmd: download:0faaa7a0
cmd: flash:system
version downgraded for system
Invalid PIV signed system image
-------------------------
Any ideas? This zip seemed to have done 'better' than other, but the phone still doesn't accept it.
Click to expand...
Click to collapse
It sounds like the download of the .zip is corrupt. You will need to download the zip again. There is a list of md5 values in an xml file inside the zip. If the md5 is different it won't flash as a safety precaution.
Sent from my XT1095 using Tapatalk
ostheer said:
That is great news! I am still downloading the zip AGISCI linked.
So if I'm correct, in the fastboot screen it now says "device is unlocked" for you?
What steps did you make to try to unlock the bootloader?
Also, am I correct to assume that you used fastboot/mfastboot to flash your zip in the end?
Click to expand...
Click to collapse
You are indeed correct. I dont think using another computer helped, although I managed to get FLASH Partition gpt.bin to work first try. What I think happened was my friend [not knowing it was in bootloader] did the bootloader button sequence and failed so instead it just tried to boot up [Stopped @ unlocked bootloader screen]
SO after I got 6.0 to work the radio network wasnt the same so now my SIM isnt being recognized.
So I looked for a simple solution and found directions
The Radio uses these lines of the flash process:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
I searched for Moto X radio files but no luck, however I did find this link for Moto G which is everything I need to find the solution myself with instructions
http://forum.xda-developers.com/showthread.php?t=2649763
:highfive:
---------- Post added at 08:46 PM ---------- Previous post was at 08:27 PM ----------
OrenGazala said:
How is it possible? Your bootloader just got unlocked without root!
I will be more than happy if you explain again what you did and what happend exactly.
Thanks.
Click to expand...
Click to collapse
I believe that Root is a step that comes after bootloader
[YOUR PHONE]
1. unlock-Bootloader --> mfastboot oem get_unlock_data
This is the first step Motorola tells you to do. Go Here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. Install TWRP --> mfastboot flash recovery 'your twrp.img'
At this point your phone should turn on, if not your not finished
3. Install Root --> push SuperSU-v2.--
This zip I have CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip started this whole mess but it was made to where you can relock your phone after returning it to stock. Problem was that when I ran the .bat file it never took the files so it dumped every partition THEN locked me out, or just pretended to, Im still unsure because I think all I did was try to push a flash line by line [eg. gpt.bin,motoboot,logo...] only got to motoboot and then did a reset. :highfive:
bootloader unlock question
AGISCI said:
It sounds like the download of the .zip is corrupt. You will need to download the zip again. There is a list of md5 values in an xml file inside the zip. If the md5 is different it won't flash as a safety precaution.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I checked all MD5's and compared them to the ones I generated with a MD5 checksum tool, they all match. I am downloading the zip again, but theoretically that shouldn't help as de MD5's are good.
"Invalid signed image" stays the problem here, unfortunately...
Is there no way to unlock the bootloader if you didn't enable this via settings in Android?
ostheer said:
Thanks for the reply. I checked all MD5's and compared them to the ones I generated with a MD5 checksum tool, they all match. I am downloading the zip again, but theoretically that shouldn't help as de MD5's are good.
"Invalid signed image" stays the problem here, unfortunately...
Is there no way to unlock the bootloader if you didn't enable this via settings in Android?
Click to expand...
Click to collapse
No there is no way to unlock it if you didn't.
Question what version of android were you on before you did this? 5.1? With stagefright patch?
Sent from my XT1095 using Tapatalk
AGISCI said:
No there is no way to unlock it if you didn't.
Question what version of android were you on before you did this? 5.1? With stagefright patch?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thought so,
I was on an official 5.1 build, presumably with the patch indeed, as my phone was fully updated and the patch came out in September. For the patch I can't be 100% sure though.
I downloaded the zip for the second time, but as expected after the MD5 check, the results were the same...
ostheer said:
Thought so,
I was on an official 5.1 build, presumably with the patch indeed, as my phone was fully updated and the patch came out in September. For the patch I can't be 100% sure though.
I downloaded the zip for the second time, but as expected after the MD5 check, the results were the same...
Click to expand...
Click to collapse
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk
AGISCI said:
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am currently downloading this zip, and also some others.
Curiosity:
How is the phone actually checking the file signatures? What is it comparing them to?
I'm wondering how did I manage to make the phone unable to boot, while the bootloader doesn't allow anything to be flashed?
ostheer said:
I am currently downloading this zip, and also some others.
Curiosity:
How is the phone actually checking the file signatures? What is it comparing them to?
I'm wondering how did I manage to make the phone unable to boot, while the bootloader doesn't allow anything to be flashed?
Click to expand...
Click to collapse
The images are also signed by motorola with a special key that only they have and know. If the key does not match with your installed firmware flashing will fail.
Sent from my XT1095 using Tapatalk
AGISCI said:
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I downloaded the zip without stagefright, and flashing it using the described procedure again gave the error 'Preflash validation failed' - 'Invalid PIV signed system image'.
Strangely though, flashing motoboot.img actually did work for the first time. (!)
Also flashing the recovery.img works for most zips I tried. That's rather strange as apparently they are being checked too: flashing a twrp recovery (unsurprisingly) didn't work: "mismatched partition size (recovery)".
AGISCI said:
The images are also signed by motorola with a special key that only they have and know. If the key does not match with your installed firmware flashing will fail.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I requested a compatible stock zip from Motorola for my device, using a ticket on their site. Probably they won't be very eager to supply it though.
Related
Hey guys, I did something really stupid.
I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.
Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.
Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system
Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
DaveTheRave said:
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
Click to expand...
Click to collapse
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
audit13 said:
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
Click to expand...
Click to collapse
Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.
No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell
Using snap-fastboot:
snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?
EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.
Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Sorry I've been MIA, been busy with work.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot oem fb_mode_set
...
OKAY [ 0.006s]
finished. total time: 0.006s
fastboot oem fb_mode_clear
...
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.095s]
finished. total time: 3.095s
fastboot erase cache
erasing 'cache'...
OKAY [ 1.669s]
finished. total time: 1.669s
fastboot reboot
rebooting...
finished. total time: 0.005s
audit13 said:
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
Click to expand...
Click to collapse
That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"
Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.
Boot problem
Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.
have u solved the problem
Please explain how u have solved the problem ,my moto g4 plus in same problems
I foolishly didn't create a backup. I know. Stupid of me.
I have a Moto G 2nd Gen model XT1064 (USA, purchased at Best Buy off contract, Single SIM). I can fastboot and I have TWRP recovery installed. I cannot find a rom that works however. Of all the .zips I've downloaded only one, a dual SIM UK version, boots. But it does not recognize my SIM or wifi chip. The others fail without giving me an error as to why.
UPDATE: This thread.... http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 helped restore my wifi, though the firmware linked was a dual sim and I cannot enable my SIM card, the option is grayed out.
I have tried over the past day to try and get this to go back to its factory image with no luck at all. I have a Nexus 4, seeing as it has a toolkit and factory images readily available, its always easy to work on. This Moto G is a different story.
What do I need to get this back right? I may already have the files and not even realize it..
Thanks for any help!
canyoudig_it said:
I foolishly didn't create a backup. I know. Stupid of me.
I have a Moto G 2nd Gen model XT1064 (USA, purchased at Best Buy off contract, Single SIM). I can fastboot and I have TWRP recovery installed. I cannot find a rom that works however. Of all the .zips I've downloaded only one, a dual SIM UK version, boots. But it does not recognize my SIM or wifi chip. The others fail without giving me an error as to why.
UPDATE: This thread.... http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 helped restore my wifi, though the firmware linked was a dual sim and I cannot enable my SIM card, the option is grayed out.
I have tried over the past day to try and get this to go back to its factory image with no luck at all. I have a Nexus 4, seeing as it has a toolkit and factory images readily available, its always easy to work on. This Moto G is a different story.
What do I need to get this back right? I may already have the files and not even realize it..
Thanks for any help!
Click to expand...
Click to collapse
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site(http://sbf.droid-developers.org/phone.php?device=36)
edog11 said:
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site
Click to expand...
Click to collapse
I have tried flashing it from TWRP. I get this error message...
Code:
Package expects build fingerprint of motorola/titan_retuaws/titan_umts:4.4.4/KXB21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan-retaildsds/titan_umtsds:4.4.4/KXB21.85-14/9:user/release-keys.
E:Error executing updater binary in zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Error flashing zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Updating Partition details...
canyoudig_it said:
I have tried flashing it from TWRP. I get this error message...
Code:
Package expects build fingerprint of motorola/titan_retuaws/titan_umts:4.4.4/KXB21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan-retaildsds/titan_umtsds:4.4.4/KXB21.85-14/9:user/release-keys.
E:Error executing updater binary in zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Error flashing zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Updating Partition details...
Click to expand...
Click to collapse
You cannot use custom recovery(TWRP) to flash this.
You need to follow this and you will lose data.
Unlock the bootloader.
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
You should now be at stock Android 4.4.4 with an unlocked bootloader.
edog11 said:
You cannot use custom recovery(TWRP) to flash this.
You need to follow this and you will lose data.
Unlock the bootloader.
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
You should now be at stock Android 4.4.4 with an unlocked bootloader.
Click to expand...
Click to collapse
THANK YOU! That did it! Everything works as it did before. You were a great help!
canyoudig_it said:
THANK YOU! That did it! Everything works as it did before. You were a great help!
Click to expand...
Click to collapse
Glad you were able to get you phone working again.
Warriors, come out and plaay.
EDIT: Found a link from another XDA thread... here's the direct download from Mega: https://mega.co.nz/#!mlIz0KCQ!lVXP5PCLRV9MRxwRdhEbKesEoq9UCPs4Lv8ec1Nx0ZY
edog11 said:
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site(http://sbf.droid-developers.org/phone.php?device=36)
Click to expand...
Click to collapse
Anyone have another link/mirror? SBF Droid site is down.
While I did download it from another site, it seems a number of files are missing from the download. HEre's what I'm getting:
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US kelley$ ./fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US kelley$ cd /Users/kelley/Desktop/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US\ 01-12-18-009
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.066s]
writing 'logo'...
OKAY [ 0.108s]
finished. total time: 0.174s
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash boot boot.img
error: cannot load 'boot.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
The SBF Droid website is down... and only gives an error message stating the following:
An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
If you are the system administrator of this resource then you should check the error log for details.
Faithfully yours, nginx.
Click to expand...
Click to collapse
My phone is unusable at this point; not bricked but might as well be as I can't make/receive phone calls nor texts. Can anyone PLEASE send me a valid link to a what's noted above? I accidentally flashed the wrong file to my phone and absolutely need to get it back to stock. THANK YOU... more than you'll EVER know!
thewinelover said:
While I did download it from another site, it seems a number of files are missing from the download. HEre's what I'm getting:
The SBF Droid website is down... and only gives an error message stating the following:
My phone is unusable at this point; not bricked but might as well be as I can't make/receive phone calls nor texts. Can anyone PLEASE send me a valid link to a what's noted above? I accidentally flashed the wrong file to my phone and absolutely need to get it back to stock. THANK YOU... more than you'll EVER know!
Click to expand...
Click to collapse
Sir..if you don't find a known good download soon..let me know, I can upload to my Drive..
Sent from my:
4.4.4_23.3.24 XT1080M
Droid Maxx Developer Edition
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Oh gosh that would be SO HELPFUL!!! Would you NWKENT? You might just save my phone!
PS - I'm a girl...
NWKENT said:
Sir..if you don't find a known good download soon..let me know, I can upload to my Drive..
Sent from my:
4.4.4_23.3.24 XT1080M
Droid Maxx Developer Edition
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Click to expand...
Click to collapse
thewinelover said:
Oh gosh that would be SO HELPFUL!!! Would you NWKENT? You might just save my phone!
PS - I'm a girl...
Click to expand...
Click to collapse
Here you go young lady....
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml
Linky
EDIT: Here's the md5 checksum. ALWAYS verify these prior to installing.
b44ffe73058ebb8b85c853151f8c3e36
*RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
@fathergweedo, You sir, are the BOMB!! Thank you so much!!!!
thewinelover said:
@fathergweedo, You sir, are the BOMB!! Thank you so much!!!!
Click to expand...
Click to collapse
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
EDIT: TWRP doesn't backup PDS by default. You must select it prior to the backup. Just thought I should clarify that.
fathergweedo said:
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
Click to expand...
Click to collapse
And we're BAAAAAA-AAAAACK!!! With the right file, it's easy peasy, lemon squeezy!
You BETCHA! All of my apps are restoring now and as soon as they finish, that will be my next task!!! @fathergweedo, I cannot thank you enough. I'm thinking you're in the states, and if you are, you'll understand what I mean.... you brought new meaning to a HAPPY THANKSGIVING!!!! Cheers!!!
Thx!
fathergweedo said:
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
Click to expand...
Click to collapse
THX so much! Had the same problem as the OP
fathergweedo said:
Here you go young lady....
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml
Linky
EDIT: Here's the md5 checksum. ALWAYS verify these prior to installing.
b44ffe73058ebb8b85c853151f8c3e36
*RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
Click to expand...
Click to collapse
Thank you so much I spent the last 3 hours trying to recover from a softbrick and this did the trick. :good:
Hey,
I got my Moto G like 3 Weeks ago, unlocked it and rooted it. Now there is an OTA that my friend got. (He's not unlocked). I am not recieving this OTA Update at all and i cant relock my Bootloader.
When i flash stock Firmware with fastboot, starting with OEM Lock begin, i get an error. The first error comes when i flash something. It does flash it without problems but says <Bootloader> Preflash Validation failed. I am sure that i am using the right Firmware, i think it's not signed. So, the last command i run is OEM Lock wich gives me the error SST Lock failure. And then it flashed to stock, everything fine but it's not locked again. Also there is no recovery when i press recovery on bootloader. On my Nexus 5 i got an Recovery and not an android with a red sign laying on the ground...
How can i relock my Bootloader and where to get official signed images for XT1068 Dual SIM Version (Germany) (used theese, getting errors sbf .droid-developers. org/phone.php?device=36)
I could not find anything regarding this in search, sorry.
And sorry for that TERRIBLE english but greetings from germany
tbunlmtd said:
Hey,
I got my Moto G like 3 Weeks ago, unlocked it and rooted it. Now there is an OTA that my friend got. (He's not unlocked). I am not recieving this OTA Update at all and i cant relock my Bootloader.
When i flash stock Firmware with fastboot, starting with OEM Lock begin, i get an error. The first error comes when i flash something. It does flash it without problems but says <Bootloader> Preflash Validation failed. I am sure that i am using the right Firmware, i think it's not signed. So, the last command i run is OEM Lock wich gives me the error SST Lock failure. And then it flashed to stock, everything fine but it's not locked again. Also there is no recovery when i press recovery on bootloader. On my Nexus 5 i got an Recovery and not an android with a red sign laying on the ground...
How can i relock my Bootloader and where to get official signed images for XT1068 Dual SIM Version (Germany) (used theese, getting errors sbf .droid-developers. org/phone.php?device=36)
I could not find anything regarding this in search, sorry.
And sorry for that TERRIBLE english but greetings from germany
Click to expand...
Click to collapse
First of all: you do have a recovery. The android with the red exclamation mark laying on the ground IS your recovery. But it's not really designed for common users. To get the options in recovery (when you're in the screen with the android with the red exlamation mark), hold the VOLUME-UP for 10 to 15 seconds an then pres the POWER button. And there you have it: a recovery!
About the relock of the bootloader: the rom has to be flashed without errors to have a possible relock. Flash a rom with a higher or the same build number!
I myself had a lot of troubles with this too, but in the end I flashed the RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml.zip and after that i had a succesfull relock!
By the way I used the fastboot under Linux-Ubuntu. But it should work with mfastboot in Windows too, i suppose!
Greetings from Holland!
smitharro said:
First of all: you do have a recovery. The android with the red exclamation mark laying on the ground IS your recovery. But it's not really designed for common users. To get the optionsin recovery (when you're in the screen with the android with the red exlamation mark), hold the VOLUME-UP for 10 to 15 seconds an then pres the POWER button. And there you have it: a recovery!
About the relock of the bootloader: the rom has to be flashed without errors to have a possible relock. Flash a rom with a higher or the same build number!
I myself had a lot of troubles with this too, but in the end I flashed the RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml.zip and after that i had a succesfull relock!
By the way I used the fastboot under Linux-Ubuntu. But it should work with mfastboot in Windows too i suppose!
Greetings from Holland!
Click to expand...
Click to collapse
Thank you, i'll try this now!
Working just fine, thanks!
Cannot lock bootloader
tbunlmtd said:
Working just fine, thanks!
Click to expand...
Click to collapse
I am stuck here too. Cannot relock bootloader ...
build version KXB21.85-17; System version: Blur_Version.21.11.17.titan_retuglb.retuglb.en.US
I have downloaded the same firmware from http://sbf.droid-developers.org/phone.php?device=36
Applied flash according to :
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
Click to expand...
Click to collapse
getting downgrade error, Invalid PIV signed image error, sst lock failure error ! failed to validate system image in device display
[NB: I have changed to US version (retuaws) before and flashed back to global ]
Same Exact problem
Anonymous 360 said:
I am stuck here too. Cannot relock bootloader ...
build version KXB21.85-17; System version: Blur_Version.21.11.17.titan_retuglb.retuglb.en.US
I have downloaded the same firmware from http://sbf.droid-developers.org/phone.php?device=36
Applied flash according to :
getting downgrade error, Invalid PIV signed image error, sst lock failure error ! failed to validate system image in device display
[NB: I have changed to US version (retuaws) before and flashed back to global ]
Click to expand...
Click to collapse
I am usually quite good at following directions, but after unlocking this thing, I am trying to relock it so I can download Lollipop and I get the exact same errors. I have been on it for 5 hours and counting.
What am I doing wrong?
Damionix said:
I am usually quite good at following directions, but after unlocking this thing, I am trying to relock it so I can download Lollipop and I get the exact same errors. I have been on it for 5 hours and counting.
What am I doing wrong?
Click to expand...
Click to collapse
if you cannot fix it yet, then let me know.
Look at my post here. I don't want to make duplicate posts. Therefore a link!
Hi,
I have an XT1072 which was rooted and running CM. Since I wanted to install stock ROM, I used the Windows Tool from this forum to restore stock Android. By doing so, I was stuck with Bootloader locked screen.
Since then I am stuck on Fastboot Flash Mode screen (see pic attached).
When I try to connect my device to the same PC or any other PC and try mfastboot or fastboot or any command, it just says Waiting for device. I have all the required drivers installed in all the PCs I tested.
Using the volume buttoms, I am able to select any option, but it wont open any option (such as Normal Powerup or Recovery)
Can someone help?
Thanks
anyone?
ram11 said:
anyone?
Click to expand...
Click to collapse
Your system image is signed using incorrect key. Reflash system partition with factory image.
LuK1337 said:
Your system image is signed using incorrect key. Reflash system partition with factory image.
Click to expand...
Click to collapse
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?
ram11 said:
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?
Click to expand...
Click to collapse
You need to get fastboot drivers...
LuK1337 said:
You need to get fastboot drivers...
Click to expand...
Click to collapse
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.
ram11 said:
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.
Click to expand...
Click to collapse
Join #titandev at freenode in 20 mins, I'll try to help you out.
Sent from my Moto G 2014 LTE using Tapatalk
Any luck?
Hi Guys,
I know this is a long shot as this is an old thread but did you get anywhere with a resolution to this?
I'm in the exact same position.
Tried flashing with different factory roms and "fastboot boot" to try force it to boot a twrp image
I'm also stuck here, anyone has had any luck?
Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
This will flash the fw, factory reset and reboot the phone.
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it
dr.nic said:
Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
This will flash the fw, factory reset and reboot the phone.
Click to expand...
Click to collapse
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot reboot
Click to expand...
Click to collapse
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
Bootloader should check if boot and system images are correct otherwise it should send user back to bootloader.
dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
I gave this a shot as suggested and I'm getting this error:
C:\Users\Nick\Downloads\New folder>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259279 KB)...
OKAY [ 9.742s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.131s
Also getting the error:
version downgraded for system
Invalid PIV signed system image
Out of tricks stock flash + factory reset always worked for me sorry.
I noted my phone model/region before doing anything (xt1072-thea-reteu) got the right fw and it worked fine, maybe was another problem giving the same error "failed to validate system image" unable to boot and stuck in bootloader, weird.... :\
Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?
nickkk93 said:
Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?
Click to expand...
Click to collapse
My phone is in a drawer I'd love to be able to fix it because I really miss Android now but it there doesn't seem to be a solution... I am no giving up hope entirely though!
I tink that I have similar problem with my X1072.
After unroot with Kingroot and install AdAway and TWRP from Google Play I even noticed that I hadn't unlock bootolader.
Now I can't reboot my phone without entering in Bootloader and reseting to factory defaults. After some reboots no data has been deleted.
I have tried to reflash the entire phone but In bootloader mode the phone is not detected by the computer, so I can't flash. I'm stucked. by now
josepmanel said:
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!
Click to expand...
Click to collapse
Have you had any luck at all? My phone has been in a drawer for a couple of months now...
Guys try flashing the latest MM stock i discovered an error too in my old update script /sniff.
Run the *.bat as admin .
Stock zip for XT1072:
MEGA Mirror 1
MEGA Mirror 2
Fastboot+mfastbootv2
BAT File
MM Flash BAT said:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Also remember if you are on another model and not XT1072 you should dl the correct image for your phone from HERE Look if Android 6 is available for your country, if you have gb-de-fr-es you can use the EU stock image.
Unpack everything in the same folder and launch the *.BAT as admin
Soft bricked when trying to flash stock 5.1 back from CM13. Somehow managed to wipe the entire phone and now all I have access to are fastboot and TWRP recovery. I have no ROM ZIPs to access in TWRP since internal storage was wiped. I tried ADB sideload but says it can't mount /data/. My computer recognises the phone as a fastboot device but not as an ADB device.
Is there any coming back from this?
I've downloaded the retail GB stock image file for XT1052 but I can't flash the partition as I just get error 'update gpt_main version failed' 'preflash validation failed for GPT'
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I've downloaded the RetGB for 5.1 for XT1052 from here: https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1052/
But it seems to be missing a number of key files that are described in option 5 of the link you posted. Am I missing something? I'm also still getting errors each time I try to flash the partition except now CMD is just showing:
"target max-download-size: 768MB error: cannot load 'gpt.bin': no error. Any ideas? Thanks.
My only other thought at this point is to try and flash a ROM in recovery using USB-OTG. Could that work? For example, if I download stock ROM or even the CM 14 I had on previously before everything got wiped and put that on an external drive and flashed in TWRP?
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I just moved cmd.exe into my platform tools folder where everything else is and tried again to flash the partition. Instead this time I get:
C:\Android-SDK\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.335s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.328s
And then on the phone itself in the fastboot screen it shows:
"downgraded security version. update gpt_main version failed. preflash verification failed for GPT'. I thought this would mean the bootloader I'm trying to flash would represent a downgrade but I checked against the info.txt file in the recovery image zip and it says 30.BE which matches the 30.BE in my fastboot screen...
OK I've now got an OS. Managed to reinstall CM14 using usb-otg. Figured that was the safest bet given it was the last OS installed.
Problem I now have is that I can't get any service (I could previously on CM14 before all this happened). Is it possible that when I managed to completely wipe the phone that I would the relevant modem/radio files?
Thanks
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Sent from my XT1060 Dev Ed
varunpilankar said:
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Click to expand...
Click to collapse
That doesn't have my version - xt1052.
Would this be to return my mobile service? I've got back on CM14 but all my IMEI and sim data has wiped so I can't get service. Not sure if I need to use the 5.1 factory image I have and just flash modem files. Seen elsewhere that I could try
Fastboot flash modem NON-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Would that do the trick do you reckon?
Take a nandroid backup & try doing it!
There is also a 5.1 stock zip Rom & try that too, might be helpful.
Sent from my XT1060 Dev Ed
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
hachamacha said:
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
Click to expand...
Click to collapse
Thanks. Will give that a look as I would like to know how to easily go back to stock in the event of catastrophe - I've been trying to flash back using both fastboot and TWRP but it fails every time due to 'downgrade security' etc. even though I know I'm using the same bootloader as in the stock ROM.
I managed to get my IMEI and service back by flashing
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I've now got Resurrection Remix on as I thought I'd see if that would fix my service issues (it didn't - so still had to do the steps above). But have managed to learn a lot over the past few days to bring my phone back from death! I'm mainly used to Sony phones so this has been an experience.