Database Develop

[Q] Razr xt890i

Hi there
That's my first post, so please be understanding. Bought a Motorola phone as it is (no water damage) which comes to booting logo and after few minutes keep restarting and trying to booting with no results. I've started red some posts, already but i'm stuck. Reset doesn't work (Power button+volume control down), but when i press power button +camera button and plug in with computer, it shows black screen and green led. Already installed MEDFIELD drivers, RSD Lite and xFSTK-DLDR. tried already RSD Lite with no luck (i've downloaded CFC_signed_customer_8.7.1I-110_IFW-DE-31_RTEU.xml and CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml)
Can get to AP Fastboot Flash Mode, but when i tried to do Factory or Recovery gets:
Failed to enter Factory/Recovery mode. error code -18
No more error code, only some kind of "GETVAR" failed

Read here
http://forum.xda-developers.com/showthread.php?t=2166646
CWMR or TWRP install easy 19-Sep-13
Install and try again
Enviado desde mi GT-I8190L

jacbarahona72 said:
Read here
http://forum.xda-developers.com/showthread.php?t=2166646
CWMR or TWRP install easy 19-Sep-13
Install and try again
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
I'll give it go and let U know.
Thanks
Got such a message:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder and fastboot file(s) created.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
How can i connect with Motorola, at the minute is on AP FASTBOOT
This time i paste .img files into Fastboot Commander folder nad gets:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0x2025.
Radio version: failed.
Main software version: failed.
cid: 7.
cpld: failed.
product: smi.
getvar:mid failed (remote failure).
getvar:security failed (remote failure).
getvar:build-mode failed (remote failure).
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?
On phone i got Getvar build-mode
Fastboot command failed

If you came down those 2 firmware must know that one is ICS (8.7), the other JB (9.8) and if you wanted to install the ICS tending JB you've done a hardbrick, so I recommend you search for the thread "Unbrick for downgrading"
Sorry for my bad English
Enviado desde mi GT-I8190L
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
asgaard76 said:
I'll give it go and let U know.
Thanks
Click to expand...
Click to collapse
You bootloader is locked?
Only make if you have unlocked
Enviado desde mi GT-I8190L
---------- Post added at 08:31 AM ---------- Previous post was at 08:25 AM ----------
Read here for getvar problem
http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company
Enviado desde mi GT-I8190L

jacbarahona72 said:
If you came down those 2 firmware must know that one is ICS (8.7), the other JB (9.8) and if you wanted to install the ICS tending JB you've done a hardbrick, so I recommend you search for the thread "Unbrick for downgrading"
Sorry for my bad English
Enviado desde mi GT-I8190L
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
You bootloader is locked?
Only make if you have unlocked
Enviado desde mi GT-I8190L
---------- Post added at 08:31 AM ---------- Previous post was at 08:25 AM ----------
Read here forma getvar problem
http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
I don't know if it's unlocked as i bought when it won't pass booting screen
Quick update:
When i tried using Recovery.img through Fastboot commander got such a message (picture)
and on phone mostly gets Fastboot command failed
Invalid image size for partition recovery

asgaard76 said:
I don't know if it's unlocked as i bought when it won't pass booting screen
Quick update:
When i tried using Recovery.img through Fastboot commander got such a message (picture)
and on phone mostly gets Fastboot command failed
Invalid image size for partition recovery
Click to expand...
Click to collapse
SURELY NOT HAVE THE BOOTLOADER UNLOCKED
IMPORTANT
AS YOU AND I flashed HAS MARKED ERROR, YOU MUST CORRECTLY FASTBOOT FLASH FOR SOMETHING AS BOOT IMAGE ( LOGO_SIGNED ) , EXTRACT OF THE SAME FIRMWARE (ZIP )
1 - . DOWNLOAD ONE FASBOOT.EXE OF THE THREADS XDA
2 - . PLACE THE IMAGE FILE ( LOGO_SIGNED ) WITH THE FASTBOOT EXE FILE IN ONE FOLDER IN THE ROOT FOR EXAMPLE C:\ANDROID\ <---- YOU CREATE
3. - OPEN COMMAND WINDOW IN THE FOLDER FILES YOU HAVE MENTIONED IN THE PREVIOUS ITEM
4 - . RAZR I CONNECTED TO PC BY USB CABLE AND BE IN FASTBOOT MODE SCREEN
5 - . INDICATE THE FOLLOWING COMMAND " FASTBOOT FLASH LOGO LOGO_SIGNED "
IF YOU ARE FLASHING OK FOLLOW YOU'VE INDICATED BELOW
CASE 1
1 - . USE A FIRMWARE JB (9.8 )
2 - . DECOMPRESS , EDIT THE FILE WITH EXTENSION XML, and eliminate GETVAR LINES INDICATED IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company)
3 - . USE RSD LITE VERSION 6.14 MINIMUM TO FLASH THE STOCK XML EDITED ( WHICH YOU HAVE CLEARED THE LINES GETVAR )
CASE 2
1 - . UNLOCK YOUR BOOTLOADER
2 - . INSTALLING A CUSTOM RECOVERY VIA FASTBOOT COMMANDER
3. - INSTALL AN " AS CUSTOM ROM OF OMAR AVELAR " IN THE RECOVERY
FOLLOW THE INSTRUCTIONS IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company) IN THIS THREAD AS INDICATED UNLOCK BOOTLOADER ,
ALSO, THE RECOVERY IS TO INSTALL A CUSTOM ROM FOR EXAMPLE OF OMAR AVELAR AND YOU SHOULD HAVE UNLOCKED BOOTLOADER FOR THAT

jacbarahona72 said:
SURELY NOT HAVE THE BOOTLOADER UNLOCKED
IMPORTANT
AS YOU AND I flashed HAS MARKED DEFECTIVE, YOU MUST CORRECTLY FASTBOOT FLASH FOR SOMETHING AS BOOT IMAGE ( LOGO_SIGNED ) , extract SAME FIRMWARE (ZIP )
1 - . DOWNLOAD ONE OF THE THREADS FASBOOT.EXE XDA
2 - . PLACE THE IMAGE FILE ( LOGO_SIGNED ) FASTBOOT WITH THE EXE FILE
3. - OPEN COMMAND WINDOW IN THE FOLDER archvos YOU HAVE MENTIONED IN THE PREVIOUS ITEM
4 - . RAZR I CONNECTED TO PC BY USB CABLE AND BE IN FASTBOOT MODE SCREEN
5 - . INDICATE THE FOLLOWING COMMAND " FASTBOOT FLASH LOGO LOGO_SIGNED "
IF YOU ARE FLASHING OK FOLLOW YOU'VE INDICATED BELOW
CASE 1
1 - . USE A FIRMWARE JB (9.8 )
2 - . DECOMPRESS , EDIT THE FILE WITH EXTENSION XML, and eliminate GETVAR LINES INDICATED IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company)
3 - . USE RSD LITE VERSION 6.14 MINIMUM TO FLASH THE STOCK XML EDITED ( WHICH YOU HAVE CLEARED THE LINES GETVAR )
CASE 2
1 - . UNLOCK YOUR BOOTLOADER
2 - . INSTALLING A CUSTOM RECOVERY VIA FASTBOOT COMMANDER
3. - INSTALL AN " AS CUSTOM ROM OF OMAR AVELAR " FOR RECOVERY
FOLLOW THE INSTRUCTIONS IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company) IN THIS THREAD AS INDICATED UNLOCK BOOTLOADER ,
ALSO, THE RECOVERY IS TO INSTALL A CUSTOM ROM AVELAR AS OF OMAR AND YOU SHOULD HAVE UNLOCKED BOOTLOADER
Click to expand...
Click to collapse
Will give it go and keep U inform. Thanks
Once again:
1. I have to download Fastboot.exe (is it fasboot commander?)
2. Image file (do i have it?? which one is it?)
3. command window?? I'm lost
4.

asgaard76 said:
Will give it go and keep U inform. Thanks
Once again:
1. I have to download Fastboot.exe (is it fasboot commander?)
2. Image file (do i have it?? which one is it?)
3. command window?? I'm lost
4.
Click to expand...
Click to collapse
1. - Fastboot.exe
2. - logo_signed (must be obtained from the firmware, exploring the zip file) NO DOWNLOAD, draw your own "firmware ZIP (CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip <-- for example)"
sorry for my bad English
Donwload files
http://db.tt/tak1LsuU
note: NO DOWNLOAD logo_signed file is of the firmware: Brasil.en.BR (IS "ICS" NO WORK, YOU DAMAGED YOUR PHONE)
Procedure
1. - Put the downloaded files in a folder in the root "C" on your pc, (I call this folder "Android" for example)
2.- Put the phone in fastboot mode (power button and Vol - squeezing them a few seconds until the screen fastboot mode) and connect with USB the phone to pc
3.- Opening a cmd screen, we stand there, I'm in cmd C:\Android\
4. - cheking with command fastboot devices
5. - Performed the command fastboot flash logo logo_signed
6. - Conducted after ending command fastboot reboot and that's it
7.- enjoy
Warning: only share what I see written on a forum and I served, so I do not take responsibility for any damage this may cause to your phone
---------- Post added at 05:14 PM ---------- Previous post was at 04:56 PM ----------
AND YOU CAN NOT COME TO RECOVERY BECAUSE ERASED PARTITION,
AS YOUR PICTURE
WHERE RECEIVED INSTRUCTIONS TO CLEAR YOUR RECOVERY?
NO YOU ACCESS IT, TO RECOVERY BECAUSE YOU HAVE NO
AND YOU MUST FLASH THE STOCK RECOVERY FIRST TO SEE IF YOU ACCESS TO RECOVERY.
ALSO THAT WHAT TO DO WITH FASTBOOT COMMANDER

what was your firmware that you had installed before this happened to you?

As per picture
It looks like image was installed, what next steps should be done?
Yes, that's my fault. I've tried program and thought that it won't make any effects, because i got messages failed, so unfortunately i erase Recovery partition. Is there anything else what we can do?
Thanks
How can i flash stock Recovery and would it help?

jacbarahona72 said:
what was your firmware that you had installed before this happened to you?
Click to expand...
Click to collapse
I don't know as i bought that phone from someone who sell it cheap (already not working) and probably that person have no clue what version/name of Android was it there?

Ok, try this, it has nothing to do with the logo u just flashed
i dunno if u already done this. But we are gonna install the stock recovery again and see what happens. Installing a recovery cant kill your device
If by this methode u cant install the recovery, fastboot gives an error, your bootloader is locked.
1. In this thread, download the 1.6 zip version of the recovery flasher. (the flasher is an automated proces, but we do it manually)
2. Open de zip file and extract the "stock.img" to the folder with the fastboot.exe
3. now, reboot the device in fastboot mode (power and volume down) and linked with usb to your pc obviously
4. use the command "fastboot devices" and u get a list of attached devices. If ur device is one of them we are good.
5. use the command "fastboot flash recovery stock.img" to flash the stock recovery. If it works, your device has an unlocked bootlaoder. If it doesn't its locked.
If it is locked, we go through the next step with rsd lite and install the latest JB 4.1.2 image to your device.
Hazou

Hazou said:
Ok, try this, it has nothing to do with the logo u just flashed
i dunno if u already done this. But we are gonna install the stock recovery again and see what happens. Installing a recovery cant kill your device
If by this methode u cant install the recovery, fastboot gives an error, your bootloader is locked.
1. In this thread, download the 1.6 zip version of the recovery flasher. (the flasher is an automated proces, but we do it manually)
2. Open de zip file and extract the "stock.img" to the folder with the fastboot.exe
3. now, reboot the device in fastboot mode (power and volume down) and linked with usb to your pc obviously
4. use the command "fastboot devices" and u get a list of attached devices. If ur device is one of them we are good.
5. use the command "fastboot flash recovery stock.img" to flash the stock recovery. If it works, your device has an unlocked bootlaoder. If it doesn't its locked.
If it is locked, we go through the next step with rsd lite and install the latest JB 4.1.2 image to your device.
Hazou
Click to expand...
Click to collapse
had to make a correct flash because if you stay with an "incorrect flash", RSD LITE not work, and in many cases say error, reading the context, "directed to make a flash of SOMETHING" and that would be correct, then with RSD LITE flash the firmware and must not indicated error like before.
to the stock recovery you can flash with the same program that he used wrong
I do not have much that I left the Razr I but I've explained what ... . somewhere in all that I have written must match with you Master.
Sorry for my bad English
Enviado desde mi GT-I8190L

jacbarahona72 said:
had to make a correct flash because if you stay with an "incorrect flash", RSD LITE not work, and in many cases say error, reading the context, "directed to make a flash of SOMETHING" and that would be correct, then with RSD LITE flash the firmware and must not indicated error like before.
to the stock recovery you can flash with the same program that he used wrong
I do not have much that I left the Razr I but I've explained what ... . somewhere in all that I have written must match with you Master.
Sorry for my bad English
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
Don't get me wrong, if I gave you that idea, wasn't my purpose
U did great in presenting a solution for the problem, the only problem is that in my opinion your post wasn't very easy to read for a new guy with a problem. With all the lines/codes that were produces and not set in a container (/code) and with the big red lines that were in the post it wasn't very understandable.
Your English is fine, it is understandable, just the formatting of the post was in my opinion not very good. The solution is good though, maybe with a small sideway, but good.
Just keep it up and help those guys when ever u can. We need those folks like u that help others out!! :thumbsup:
Hazou
Verstuurd van mijn GT-P5110

Hazou said:
Don't get me wrong, if I gave you that idea, wasn't my purpose
U did great in presenting a solution for the problem, the only problem is that in my opinion your post wasn't very easy to read for a new guy with a problem. With all the lines/codes that were produces and not set in a container (/code) and with the big red lines that were in the post it wasn't very understandable.
Your English is fine, it is understandable, just the formatting of the post was in my opinion not very good. The solution is good though, maybe with a small sideway, but good.
Just keep it up and help those guys when ever u can. We need those folks like u that help others out!! :thumbsup:
Hazou
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
Will post any update 2night.

OK. Folks short update
Friend of mine who's also on xda forum gave me few tips which i tried, but no luck. Will post them here:
1. CMD: fastboot oem get_unlock_data
fastboot oem get_unlock_data
...
(bootloader) 3A25150915586129#54413233373034
(bootloader) 48354100000000000000000000#1ACF
(bootloader) 4FDA6DCEE30F10CACA1F7FC1CBD39CB
(bootloader) 08BBF#DFF3ABAE76852954D805ED6EF
(bootloader) 3FA0000
OKAY [ 0.290s]
finished. total time: 0.290s
2. fastboot oem unlock PJYERHAJMZMPVYSRKIXN
fastboot oem unlock PJYERHAJMZMPVYSRKIXN
...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.390s
In Motorola phone it says
Unlock
Fastboot command failed
He said that partition table is faulty. It can be done only in Linux or JTAG.
Any advice on this?
We tried this as well:
CMD: fastboot format data
(bootloader) Variable not supported!
formatting 'data' partition...
(bootloader) Variable not supported!
FAILED (remote failure)
FAILED (remote failure)
finished. total time: 0.342s
He said that emmc is faulty that's why fastboot won't work.

Had that problem too... it was due to bad Emmc. Sorry for your loss bro.

It could be indeed an emmc problem, in that case a repair at motorola can only fix it, or u will need to replace the motherboard, that will set u back another 150 dollars.
But, u successfully flashed the logo, so a part of the emmc is still working correctly i assume. btw, my knowledge about emmc problems stops here..
The next steps i should take is the following, we will reformat/partition your device, as far as it goes. But I never done this, didn't need to i only know it is possible. Everything that happens now is on your own responsibility!!
1. Download your correct firmware, must be jellybean 4.1.2 from here(firmware)
2. Extract it content in a folder like "STOCKROM"
3. Download new fastboot files from here (mfastboot,xda)
4. Extract the new mfastboot files in the folder "STOCKROM" if u named it like that.
5. Connect your device with your pc, make sure all drivers are correctly installed, and boot in fastboot mode (power + volume down)
6. Flash each of the partitions in sequence using mfastboot (is like fastboot, but can install files larger then 100mb), you need to enter the following commands one-by-one checking that each one returns an [OKAY]. If it doesnt work, i am out of ideas. sry, but report anyway what happend
7.
Code:
mfastboot flash gpt gpt_signed
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck with it, i will hear from you.
Hazou
btw, erasing 'data' is impossible, fastboot doesn't know 'data', only 'userdata'

Hazou said:
It could be indeed an emmc problem, in that case a repair at motorola can only fix it, or u will need to replace the motherboard, that will set u back another 150 dollars.
But, u successfully flashed the logo, so a part of the emmc is still working correctly i assume. btw, my knowledge about emmc problems stops here..
The next steps i should take is the following, we will reformat/partition your device, as far as it goes. But I never done this, didn't need to i only know it is possible. Everything that happens now is on your own responsibility!!
1. Download your correct firmware, must be jellybean 4.1.2 from here(firmware)
2. Extract it content in a folder like "STOCKROM"
3. Download new fastboot files from here (mfastboot,xda)
4. Extract the new mfastboot files in the folder "STOCKROM" if u named it like that.
5. Connect your device with your pc, make sure all drivers are correctly installed, and boot in fastboot mode (power + volume down)
6. Flash each of the partitions in sequence using mfastboot (is like fastboot, but can install files larger then 100mb), you need to enter the following commands one-by-one checking that each one returns an [OKAY]. If it doesnt work, i am out of ideas. sry, but report anyway what happend
7.
Code:
mfastboot flash gpt gpt_signed
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck with it, i will hear from you.
Hazou
btw, erasing 'data' is impossible, fastboot doesn't know 'data', only 'userdata'
Click to expand...
Click to collapse
None of them are working. Anyway i was in few repair shops in Dublin and none of them can fixed as they stated Motorola isn't popular in Ireland. Mostly i heard "i have no clue" or "You have to send to manufacturer". One of them tried fixed (it takes roughly 3 hours), but also gave up. He said that it's nearly same story with chip which Samsung S3 had. Don't ask me what does it mean, cuz have no idea. Friend of mine who's also user on that forum will fix it as he stated, but don't know if i gonna send it to Poland. At this stage i have to stop any more tests with Motorola as i don't know what i have to do.
Thanks for all support and will keep You inform if something turn up.
Btw. one of Chinese "call him tech-e" broked back cover of Motorola (beside camera, cracked glass), but i noticed it when i left his repair centre.
Thanks

Okey, best of luck!
Hazou
Verstuurd van mijn XT890

[Q] Moto G Relock Problems

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!

[Q] MOTO X Bricked

My moto X has a problem , let me show you the log file first
-Unlocked using motorola's website
-Flashed TWRP recovery
-Created a backup
-[MISTAKE 1]Wiped using advanced wipe
-Everything including the backup I created got wiped ,with no OS
-Mounted and tried to install CyanogenMod 11
-[ERROR 1]This rom is supported by ghost xt1053(my model number) ,and your device is . (like just a dot) //Cannot install the zip file
-[BRICKED]
-Then I searched what to do ,downloaded "TMO_213.44.1.ghost_row.Retail.en.US" firmware
-Using fastboot ,I flashed the firmware using the following commands
After downloading the image for your device:
Unzip the image.
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ 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
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock​
-It showed an error During locking the device
-The phone finally started working [UNBRICKED?]
-My sim card wasnt detecting
-So I searched more ,and checked my IMEI
-Dialed *#06# and got "IMEI 0"
-For confirmation ,I went again to settings->about->Status
-Everything was fine except "IMEI 0",and "IMEI SV 00"
-I couldnt find anything online except changing my IMEI ,which is ,one: illegal and two: not possible since I do not have Engineering mode app in my phone
-Headed over to the service center and they told me that my motherboard is gone ,you have to pay 291.050 US Dollars to change it
-But if the motherboard is gone ,how can my phone work ?
Here is my question to you guys ,what should I do ? Can I do anything to get my phone working again ? Please help me as I am not using a phone ,and I really need to use this one .
Thanks in advanced
Sorry for my bad English

I think there was a step you missed there when flashing:
fastboot flash modem NON-HLOS.bin
and it's better to use Motorola fastboot aka mfastboot instead of regular old fastboot. if you don't have it just Google for it.
for a more complete guide see option 5 on this site: http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Also there is absolutely no need for that last step you tried, fastboot oem lock... that will relock your bootloader which is totally unnecessary. you don't need it for otas or anything else, and as for warranty your phone is already flagged as unlocked and relocking it won't change that.

dtg7 said:
I think there was a step you missed there when flashing:
fastboot flash modem NON-HLOS.bin
and it's better to use Motorola fastboot aka mfastboot instead of regular old fastboot. if you don't have it just Google for it.
for a more complete guide see option 5 on this site: http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Also there is absolutely no need for that last step you tried, fastboot oem lock... that will relock your bootloader which is totally unnecessary. you don't need it for otas or anything else, and as for warranty your phone is already flagged as unlocked and relocking it won't change that.
Click to expand...
Click to collapse
Okay so I tried the whole process with "fastboot flash modem NON-HLOS.bin" ,and restarted ,but my IMEI is still showing 0 .
I was using mfastboot from the start. Any help ?

Guys please help me ,I know its torturous for you'll ,but I'm helpless right now

dkaushik95 said:
Guys please help me ,I know its torturous for you'll ,but I'm helpless right now
Click to expand...
Click to collapse
It's OK dude first step is to relax and realize that losing imei is not a new thing, it's happened to countless others. what that means is there should be a huge amount of info on what people have tried and what worked and didn't work. You'll find all the info by using Google search and changing keywords.
some keywords to try:
fastboot imei
Motorola recover imei
Restore imei
imei 0
recover imei
efs imei
and so on. if you read through them and feel you're not up to it, or if you try everything and nothing works, you have another option maybe:
Take it in / send it in for repair to Motorola or other (certified) repair shop
good luck.
BTW: The original box the phone comes in has your imei written on it. otherwise you can try the fastboot getvar method but that might or might not work.

Can you try to falsh using RSD lite it Completly safe and esay process . Try it once
MAhesh

Mahesh8348 said:
Can you try to falsh using RSD lite it Completly safe and esay process . Try it once
MAhesh
Click to expand...
Click to collapse
I tried everything including RSD Lite and several other methods ,and I've given it to Motorola . I hope they fix it

[UPDATE]
I sent my phone to the service center ,and they replaced the phone with a new one !
Everything is back to normal ,thanks for the support guys ,really appreciate it

Bricked Moto X 2014? Fastboot flashing, ADB Sideloading, Nothing Seems To Work

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.

Soft bricked XT1052

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.