Related
Hi Guys,
I am a noob and tried to ulock bootloader and flash new rom, I now have an issue, please advise
I successfully flashed bootloader, I then rooted using RAZRI_Root_Windows. I then installed RSD 5.7, downloaded Retail GB rom from (http://sbf.droid-developers.org/smi/list.php), as I am currently on Orange branded and want unbranded. During the flash process I got an error when RSD was installing system_signed, stating it had failed. I then tried to reboot and now my phone can only go into fastboot and I cannot use any of the menus in fastboot. This is what I see in fastboot:
AP fastboot flash moide (secure boot)
20.00 (sha - oba4DF3)
IFWI info
eMMC info
battery (okay)
connect USB data Cable
ROM-key : motorola -key
Boot mode selection menu:
- normale powerup
- recovery
- factory
- BP tools
- switch console [default: null]
- power of "
And, it's written in yellow :
" fastboot reason : flash failure
fastboot : max download size: 100MB "
I think the problem is the max download size as when I try to manually flash the system_signed file in command I get the following error message. Sending system (795017)
(bootloader) data too large
failed remote failure
Can I resize the repartition manually??
Any help would be welcome
http://forum.xda-developers.com/showthread.php?p=36612151
Sent from my XT910
HSD-Pilot said:
http://forum.xda-developers.com/showthread.php?p=36612151
Sent from my XT910
Click to expand...
Click to collapse
Yeah thanks. I downloaded RSD 6.4.1 and i flashed a rom no problem :good::good:
ETA
grampsharry said:
Yeah thanks. I downloaded RSD 6.4.1 and i flashed a rom no problem :good::good:
Click to expand...
Click to collapse
hi guys, with RSD lite 6.1.4 and rom FW for XT890 from Argentina what is the time of the process, because stack in Flashing radio...
Thanks!
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!
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.
Hi guys,
Hoping you lovely people can help.
I think I may have bricked my device.
It's stuck in a fastboot bootloop with the error code "failed to validate system image"
Now my (amateur) thinking of this is it's possibly due to the device now being OEM locked? Status 2. As I accidentally locked it like a fool.
I can't get into developer options to enable OEM unlock as it wont boot to system.
I've been going through all the forums and can't find any help.
Thank you all in advance
nickkk93 said:
Hi guys,
Hoping you lovely people can help.
I think I may have bricked my device.
It's stuck in a fastboot bootloop with the error code "failed to validate system image"
Now my (amateur) thinking of this is it's possibly due to the device now being OEM locked? Status 2. As I accidentally locked it like a fool.
I can't get into developer options to enable OEM unlock as it wont boot to system.
I've been going through all the forums and can't find any help.
Thank you all in advance
Click to expand...
Click to collapse
You are on stock ?
RolanDroid said:
You are on stock ?
Click to expand...
Click to collapse
I am now, I was using CM13
nickkk93 said:
Hi guys,
Hoping you lovely people can help.
I think I may have bricked my device.
It's stuck in a fastboot bootloop with the error code "failed to validate system image"
Now my (amateur) thinking of this is it's possibly due to the device now being OEM locked? Status 2. As I accidentally locked it like a fool.
I can't get into developer options to enable OEM unlock as it wont boot to system.
I've been going through all the forums and can't find any help.
Thank you all in advance
Click to expand...
Click to collapse
I had the same problem when flashed back the stock recovery, flashed UK or DE over EU stock+twrp
Those are the latest XT1072 stocks, get the one you prefer and flash it.
GB->http://www.filefactory.com/file/42o...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
ES->http://www.filefactory.com/file/2aj...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
DE->http://www.filefactory.com/file/1hr...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
EU->http://www.filefactory.com/file/57j...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
Get fastboot + mfastbootv2(http://forum.xda-developers.com/attachment.php?attachmentid=2427667) and flash the fw like this
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
Click to expand...
Click to collapse
If you want also to restory factory/delete data
mfastboot erase cache
mfastboot erase userdata
Click to expand...
Click to collapse
and then
mfastboot reboot
Click to expand...
Click to collapse
You should be ok now, no need to lock/unlock if you get the right region fw for your phone.
dr.nic said:
I had the same problem when flashed back the stock recovery, flashed UK or DE over EU stock+twrp
Those are the latest XT1072 stocks, get the one you prefer and flash it.
GB->http://www.filefactory.com/file/42o...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
ES->http://www.filefactory.com/file/2aj...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
DE->http://www.filefactory.com/file/1hr...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
EU->http://www.filefactory.com/file/57j...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
Get fastboot + mfastbootv2(http://forum.xda-developers.com/attachment.php?attachmentid=2427667) and flash the fw like this
If you want also to restory factory/delete data
and then
masftboot flash partition gpt.bin
You should be ok now, no need to lock/unlock if you get the right region fw for your phone.
Click to expand...
Click to collapse
When running the first command:
mfastboot flash partition gpt.bin
I'm getting the error:
(bootloader) Preflash validation failed
also getting
(bootloader) Invalid signed image
(bootloader) preflash validation failed
Merge whit thread http://forum.xda-developers.com/moto-g-lte/help/xt1072-stuck-fastboot-flash-screen-help-t3265735 same problem.
Check my reply in page 2 and see if that work for you.
Hi I seem to be having some major issues with my Xt1072 and cannot get it to boot!
It all started with the message popping up saying error creating mount script in second partition?
I got sick of this so I started rebooting the phone to see if I could rectify it?! and like before it just kept getting stuck in bootloop. then as the hours progressed it got worse and eventually i am at the point where my pc does not see it, then it sees it, then it doesnt see it? then I got my phone stuck in the weirdest loop Ive ever seen, it actually boots to the home screen, then 10 seconds later, screen goes black and then wakes up again and back to home screen, 10 seconds later the process gets repeated over and over again, the only thing that seems to stop it dead in its tracks is when I connect it to my pc and hold power and vol down simultaneously. now all it does sometimes is just goes straight to a white screen with huge battery charging and thats it?! i tried the commands which ive quoted below with the resulting cmd:getvar:max-sparse-size on the bootloader screen on my phone???? what does it all mean??? anyone know what the hell is going on??? I am at a loss??
If you want also to restory factory/delete data
Quote:
mfastboot erase cache
mfastboot erase userdata
and then
Quote:
mfastboot reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
< waiting for device >
target max-sparse-size: 256MB
error: cannot load 'gpt.bin': No error
Click to expand...
Click to collapse
Hi I have a problem related to this. The phone is not mine, but the owner has been doing things about rooting and that, and after touching things of the phone and reboot it, it was stuck on the motorola logo, I am able to use mfastboot, and I have followed the guides said in this post, but nothing works.
Could you help me?
Thanks.
Hello guys ! I am very happy that I found you ! I am apologize for my poor english, but you are my last hope of help. . .
My Moto X 2014 2nd was Flawless and perfect before the last OTA update in 2015.... After I installed, my phone don`t reboot anymore and freezing with the first white logo image about 20 sec and after appear a black screen with the "dead" android robot with red exclamation on it said "NO COMAND". The injured android logo just repeatedly flashes on for an instant and then disappears. Nothing happens when I hold the power button and press volume up. Anything I choose from bootloader is giving me the same result. I read all the pages from here and I am still stuck...
-I install everything: adb (it recognize the device - TA99303EV4) but every comand failed with a "REMOTE FAILURE" message. Fastboot or mfastboot - the same..... I try the CODE that i receive from Motorola ( for unlock the bootloader) but it failed again: "check Enable OEM Unlock in Developer Option". Yeah, right - but I can`t do it now with this black screen
-The RDS Lite doesn`t recognize my device (many restarts, different USB ports and computers, nothing works...)
-Motorola Device Manager said: "No updates for your phone. Current Version: 23.16.3.victara.retes.retesall.en.eu"
-In the Device manager (win 7 32bit) it appears ok: Motorola ADB Interface
My Bootloader screen looks like this:
AP Fastboot Flash Mode (S)
60.16 (sha-496ce05, 2015-04-02 10:55:00)
CPU: MSM8974AC ES1.1
eMMC: 16 Gb Sandisk RV=07 PV=01 TY=57
DRAM: 2048 MB Elpida S8 SDRAM DIE=4Gb
Battery OK (Charging)
Device is LOCKED. Status Code: 0
Software status: Official
Transfer Mode: USB Conected
Dates extracted from adb (fastboot get var all) screen:
date:11-19-2014
sku:XT1092
ro.build.fingerprint: motorola/victara_retes/victara:5.1/LPE23.32-25.3/3:user/release-keys
ro.build.version.full:Blur_Version.23.16.3.victara _retes.retesall.en.EU
sdi.git: git=MBM-NG-V60.16-0-g582b967
The firmware that I trying to flash is:
BUILD REQUEST INFO:
SW Version: victara_retes-user 5.1 LPE23.32-25.3 3, RMBM Version: 60.16
System Version: 23.16.3.victara_retes.retesall.en.EU, Model number: Moto XAndroid Version: 5.1
Baseband Version: MSM8974BP_4235210.110.09.13R, Build Number: LPE23.32-25.3
Build Date: Tue Aug 18 04:30:10 CDT 2015
Blur Version: Blur_Version.23.16.3.victara_retes.retesall.en.EU
Please, help me... In my country there is nobody who can repair my beloved phone, I went 4 times to diferent service centers and nothing... Maybe with your help, my beloved MOTO X will be back to life again. If, OMG, IF i knew before to check/enable that option in the developer option - USB debbuging......
I wish you all the best for all and thank you so much for every posible answer !
Please corect me if I am wrong:
I thing that once OTA was upgraded the partition table, then I can`t never go back. Maybe the bootloader (motoboot.img) (also system) would ONLY work with the correct partition table. Meaning that I can't mix and match at all.
I think that means that I am currently stuck with the latest GPT from the last OTA i received. Somehow maybe the bootloader was downgraded and won't work for flashing other partitions ?! ...
That means that if I flash the new bootloader version and reboot, maybe it will be back to life. So guys, what version do you thing I must try to flash ?
Please respond me, I don`t know where to ask anymore... If I only could pass that "Device is LOCKED . Status Code 0" will be so. . . blissful
I have so much expectations from the MASTERS of this forum and nobody give me a chance. . . an ideea. . . I simply don`t believe: Am I the only one who has this stupid problem ?!?!
So, because of your complete silence (and only views) I understand that I have to throw my phone on the trash because:
- nobody told me that I have to enable this stupid USB debugging option on the first day when I bought the phone.
- nobody told me that I have to unlock this bootloader on the second day when I bought this phone.
- nobody told me that I should NEVER trust the OTA updates that destroyed my phone who works flawless before. . .
I will still wait, maybe someone, SOMEONE will find a solution for this idiot situation.
With all my great respect,
Matrix.
Hi,
You should be able to flash stock images without USB debugging enabled.
Can you explain a bit more how you tried to flash the image ?
Hope we'll find a solution,
Best regards.
I use the common way like usual - mfastboot, fastboot, Android SDK Slim, the image package is in the same folder. . .
fastboot devices - returns my serial number so my phone is conected and recognized.
After I tried all this comands like usuals:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
fastboot erase userdata
fastboot erase cache
but after EVERY comand, the messages is sending...OK, writing and this stupid lines:
Preflash validation failed
FAILED (remote control)
finished. Total time .....followed by some seconds.
I tried also the mfastboot command instead of fastboot - the same result. . .
like this:
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s"
On and on, the same message . . . .
Matrix_MotoX_2nd said:
I use the common way like usual - mfastboot, fastboot, Android SDK Slim, the image package is in the same folder. . .
fastboot devices - returns my serial number so my phone is conected and recognized.
After I tried all this comands like usuals:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
fastboot erase userdata
fastboot erase cache
but after EVERY comand, the messages is sending...OK, writing and this stupid lines:
Preflash validation failed
FAILED (remote control)
finished. Total time .....followed by some seconds.
I tried also the mfastboot command instead of fastboot - the same result. . .
like this:
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s"
On and on, the same message . . . .
Click to expand...
Click to collapse
Make sure your battery is fully charged before trying to flash anything. Sometimes a low battery can be the reason for the failure messages.
My battery is fully charged. . . I even let it over night. . .
I found these on several sites:
1) "If you're flashing your variant's factory image, you can flash it without unlocking the bootloader. You would only need to unlock the bootloader if you want to flash another variant's image or a custom ROM." So I try with victara_retes-user 5.1 LPE23.32-25.3 3 (Blur_Version.23.16.3.victara_retes.retesall.en.EUVersion) and is NOT working. Same failure message. . .
2)"Google has added a check box under Developer Options that enables the OEM unlock command to work. If that box isn’t checked, then you will see an error during the bootloader unlock process. So without the option checked in Developer settings to allow OEM Unlock, users can't modify the system partition"
Which variant should I choose to be true ?. . .
Matrix_MotoX_2nd said:
My battery is fully charged. . . I even let it over night. . .
I found these on several sites:
1) "If you're flashing your variant's factory image, you can flash it without unlocking the bootloader. You would only need to unlock the bootloader if you want to flash another variant's image or a custom ROM." So I try with victara_retes-user 5.1 LPE23.32-25.3 3 (Blur_Version.23.16.3.victara_retes.retesall.en.EUVersion) and is NOT working. Same failure message. . .
2)"Google has added a check box under Developer Options that enables the OEM unlock command to work. If that box isn’t checked, then you will see an error during the bootloader unlock process. So without the option checked in Developer settings to allow OEM Unlock, users can't modify the system partition"
Which variant should I choose to be true ?. . .
Click to expand...
Click to collapse
You need the xt1092 reteu 5.1 firmware.
Sent from my XT1095 using Tapatalk
Thank you so much for your answers ! All of you !
Can you give me a correct link ? There is so many xt 1092 reteu 5.1 firmware, and I want to be 100% sure that I`ll do it like you told me.
Can I look here for the corect one ?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1092/
I will try today again with this xt1092 reteu 5.1 firmware. But if the phone blocked every attempt to flash or erase its partitions, does it matter which firmware I send it to flash ?. . .
I`ll post the result as soon as I`ll arrive at home. Hope you are right, so much !
I really don`t understand why the Motorola official site who send me the unlock bootloader code special for my phone doesn`t work . . . It was so simple if it works. . .:crying:
Youre bootloader isn,t unlocked because off status zero.
Follow this guide.
https://www.youtube.com/watch?v=nLNja2M6zc0
With all my respect sir, you didn`t read my posts. . . .
I already past this stupid step, like I said:
"I try the CODE that i receive from Motorola ( for unlock the bootloader) but it failed again: "check Enable OEM Unlock in Developer Option". . . . . . I already attach the image that proves what I am talking about and about. . .
So. . .bad news. Is the same error message, over and over again, with this firmware xt1092 reteu 5.1 . . . The phone simple don`t want to be flashed, don`t wanna accept any comand . Is there any way to flash SOMETHING on this phone ? I should try another program to flash, or something like TWRP recovery, or . . . another firmware ?
I don`t know, SOMETHING, SOMEHOW ?
I am sad. Very sad.
I attached a picture.
p.s the firmware that I tried was from here: http://forum.xda-developers.com/moto-x-2014/general/ota-t3132045.
and a little movie, trying every combination of pressing. . .
https://www.youtube.com/watch?v=vDTSncEvscM
wherever I tried to flash the RETES or RETEU 5.1 firmware, the phone respond with " invalid PIV signed system image". I am choose the wrong variants ?!?
Nobody can help me ? . . .
Matrix_MotoX_2nd said:
Nobody can help me ? . . .
Click to expand...
Click to collapse
Why dont you try flashing KITKAT Bootloader and image... It'll remove that silly option of OEM Unlocking in Developer Options... And maybe you will have luck with this... If the phone is already sort of dead, its worth a shot...
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
Also I wonder why don't you go back to MOTO Care, if your bootloader isn't yet unlocked they may help you with it..
I really wish I could help, but since I haven't posted enough, can't provide the links, so I'll do my best to give you exact google search terms to use.
I managed to softbrick my phone the day I got it. Engabling USB debugging doesn't matter in fastboot, which is where you'll be doing all the recovery/fixing at. I can't assure you that this will work for you, different problems can make for different results, however this tool was the only successful way I was able to recover my device.
Tool I used: House of Moto [4.3] SamuriHL's House of Moto - DroidRzr
It shows up as the second link in a google search for me.
The place I got the factory ROM from was: Downloads for Motorola Moto X 2014 by Motorola-Firmware-Team | AndroidFileHost | Download GApps, PA GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers
This one is a bit more difficult, any of the results will be fine, but on the page, on the right side toward the bottom, select your phone, then the exact model.
This will do a full factory flash, you don't need the bootloader unlocked to do this. Alternatively, if you have better luck than me with using RSD Lite, that tool should work, too (it's never worked for any of my phones on any of the five computers I've tried it with, so I regard that software as hopelessly useless, but everyone has different results).
@hamzaalijoiyah
"Why dont you try flashing KITKAT Bootloader and image"
I`ve tried with the same silly message - Failed (remote failure).... !!!!!
@Kayjay0x
Thank you for this new idea/trying to resurect my beloved Moto X xt1092. At first glance, there`s another adb and fastboot based programs, but I`ll give it a try again.
Kayjay0x said:
I really wish I could help, but since I haven't posted enough, can't provide the links, so I'll do my best to give you exact google search terms to use.
I managed to softbrick my phone the day I got it. Engabling USB debugging doesn't matter in fastboot, which is where you'll be doing all the recovery/fixing at. I can't assure you that this will work for you, different problems can make for different results, however this tool was the only successful way I was able to recover my device.
Tool I used: House of Moto [4.3] SamuriHL's House of Moto - DroidRzr
It shows up as the second link in a google search for me.
The place I got the factory ROM from was: Downloads for Motorola Moto X 2014 by Motorola-Firmware-Team | AndroidFileHost | Download GApps, PA GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers
This one is a bit more difficult, any of the results will be fine, but on the page, on the right side toward the bottom, select your phone, then the exact model.
This will do a full factory flash, you don't need the bootloader unlocked to do this. Alternatively, if you have better luck than me with using RSD Lite, that tool should work, too (it's never worked for any of my phones on any of the five computers I've tried it with, so I regard that software as hopelessly useless, but everyone has different results).
Click to expand...
Click to collapse
Bro you saved my day, I tried your method and it worked ! I updated the thread I started
Ufff.... the same story even with this House of Moto . . .
Please, someone can tell me what version image file do i have to download and try to flash - 100% corect ? Always I found this message: "invalid image file" from the screeen (fastboot or house of moto). . .
my getvar screen is attached on the post.
I tried till now and EVERY time said: invalid image file. . . :
VICTARA_RETES_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml
RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml
VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml
RETEUALL_XT1092_4.4.4_KXE21.187-45_cid7_CFC.xml
YassGo said:
Bro you saved my day, I tried your method and it worked ! I updated the thread I started
Click to expand...
Click to collapse
Glad to hear it worked out for you like it did for me!
Matrix_MotoX_2nd said:
Ufff.... the same story even with this House of Moto . . .
Please, someone can tell me what version image file do i have to download and try to flash - 100% corect ? Always I found this message: "invalid image file" from the screeen (fastboot or house of moto). . .
my getvar screen is attached on the post.
I tried till now and EVERY time said: invalid image file. . . :
VICTARA_RETES_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml
RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml
VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml
RETEUALL_XT1092_4.4.4_KXE21.187-45_cid7_CFC.xml
Click to expand...
Click to collapse
I don't know what to suggest other than trying your luck with a non EU rom? Can't promise that'll work though.