Database Develop

[Q] Nexus 6 Factory Images

I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.

GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.

gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.

GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.

gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.

GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.

@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.

rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.

Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?

Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.

Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.

Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.

Noob difficulty in flashing stock marshmallow

I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
Code:
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 4.620s
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.

spudbynight said:
I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.
Click to expand...
Click to collapse
Looks like your fastboot binary is out of date. Did you get it from the latest sdk?

I've downloaded the SDK, but (yes, noob alert) I can't figure out how to actually install it.
I've downloaded fastboot from the terminal and it says I have the latest version.

OK - I installed the SDK. I followed the instructions here
When attempting to flash it seems to go a little bit further but is still failing.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.394s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.693s]
finished. total time: 1.087s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.084s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.555s]
finished. total time: 5.639s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.15
Baseband Version.....: D4.01-9625-05.27+FSG-9625-02.104
Serial Number........: ZX1G425T8L
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8197 KB)...
OKAY [ 0.269s]
writing 'boot'...
OKAY [ 0.125s]
sending 'recovery' (8915 KB)...
OKAY [ 0.300s]
writing 'recovery'...
OKAY [ 0.133s]
sending 'system' (2043261 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.841s
From there I went into the "long way" and flashed the files individually from system.img
I selected recovery and rebooted. I got an Android with a red triangle but held power and volume up. The phone rebooted without me being asked to wipe data/factory reset.
Currently booted up and restoring. How do I check this is stable? I want to make sure I get OTA updates...

So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.

KnifeSkills said:
So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.
Click to expand...
Click to collapse
Sorry, I edited my post with an update...

This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?

spudbynight said:
This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?
Click to expand...
Click to collapse
Nope. Just stay 100% stock. No root, no mods.

Cheers

i cant lock the bootloader of my nexus 6

hello i can't lock the bootloader of my nexus 6 since i received it from the technical service of motorola. before i send it to them it was closed and when i received it it was unlock and another no padlock its apear when is booting. ive traid every thing but nothing work
i can flash factory images but i cant relock it. fastboot oem lock works on my nexus 7 but not on my nexus 6

You should use the correct command, as google documents it.
But locking your bootloader is a pretty bad idea, and will prevent you from having any ability to fix anything if it fails to boot. If you cannot boot into android, you cannot enable unlock, and will be locked out for good with no recourse other then to send it in.
See this page
https://source.android.com/security/verifiedboot/verified-boot.html
Scroll down to "changing the device state" and use the given fastboot command.

i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem

alex482 said:
i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem
Click to expand...
Click to collapse
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.

istperson said:
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.
Click to expand...
Click to collapse
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly

alex482 said:
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly
Click to expand...
Click to collapse
Do other adb/fastboot commands work?

What does
Code:
fastboot devices
say?

yes its work adb devices , adb reboot, adb reboot bootloader, fastboot flash...., fastboot devices , fastboot reboot and fastboot reboot-bootloader

istperson said:
What does
Code:
fastboot devices
say?
Click to expand...
Click to collapse
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot

C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.077s
that it what it say when i tried to lock it but i also tried to flash the factory image its work but then when i try to lock it the same massage appear again

Please paste here the output of flashing the factory image.

istperson said:
Please paste here the output of flashing the factory image.
Click to expand...
Click to collapse
yes when its finish i copy and past everything here

I'd be curious what specific error it gives with the fastboot flashing lock says, as that should be the command now assuming your on MM and using up to date SDK.

C:\Program Files (x86)\platform-tools>adb devices
List of devices attached
ZX1G423BMR device
C:\Program Files (x86)\platform-tools>adb reboot bootloader
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot
C:\Program Files (x86)\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Program Files (x86)\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\Program Files (x86)\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.617s]
finished. total time: 0.617s
C:\Program Files (x86)\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.409s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.685s]
finished. total time: 1.102s
C:\Program Files (x86)\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
C:\Program Files (x86)\platform-tools>fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.283s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.522s]
finished. total time: 5.808s
C:\Program Files (x86)\platform-tools>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\platform-tools>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 20.071s]
writing 'system'...
OKAY [ 6.964s]
sending sparse 'system' (515137 KB)...
OKAY [ 20.267s]
writing 'system'...
OKAY [ 7.088s]
sending sparse 'system' (518219 KB)...
OKAY [ 20.493s]
writing 'system'...
OKAY [ 7.188s]
sending sparse 'system' (492726 KB)...
OKAY [ 19.042s]
writing 'system'...
OKAY [ 6.804s]
finished. total time: 107.938s
C:\Program Files (x86)\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8197 KB)...
OKAY [ 0.316s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.431s
C:\Program Files (x86)\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8915 KB)...
OKAY [ 0.334s]
writing 'recovery'...
OKAY [ 0.126s]
finished. total time: 0.463s
C:\Program Files (x86)\platform-tools>fasboot flash cache cache.img
"fasboot" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
C:\Program Files (x86)\platform-tools>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.057s]
sending 'cache' (6248 KB)...
OKAY [ 0.237s]
writing 'cache'...
OKAY [ 0.137s]
finished. total time: 0.446s
C:\Program Files (x86)\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.349s]
finished. total time: 1.349s
C:\Program Files (x86)\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.165s]
sending 'userdata' (138868 KB)...
OKAY [ 5.070s]
writing 'userdata'...
OKAY [ 3.001s]
finished. total time: 9.236s
C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.070s
C:\Program Files (x86)\platform-tools>fastboot reboot
rebooting...
finished. total time: -0.000s

yes im on 6.0 marshmallow and the sdk with the latest update

Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?

istperson said:
Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?
Click to expand...
Click to collapse
yes its all turn on i send to it to change the rear camera because it was factory failure

Then it too must be a hardware problem.

do you think so?

alex482 said:
do you think so?
Click to expand...
Click to collapse
It seems, you did everything right. The line "(bootloader) Please flash valid signed images firstly!" is returned by the bootloader, and the bootloader is, opposite to adb and fastboot, closed source. So no help from the source.
I googled it, and it appeared on the Moto G 2014 device.

VZN XT1254 Droid Turbo All stock. bootloader locked. software:eek:fficial, bricked help!

VZN XT1254 Droid Turbo All stock. bootloader locked. softwarefficial, bricked help!
I rooted with KingRoot yesterday, and then ran SunShine installer, and somewhere between that its soft bricked my device. I was using a kinda faulty usb cable, to go back and forth between command prompts for adb and fastboot, but this issue didnt arise till my first Kingroot experience, which I must add is pretty lame, but then sunshine forced closed during the process and forced a device reboot. It rebooted in bootloader , fastboot is still working, device is charging, but the bootloader log reads : Failed to validate boot image. Cant access recovery or nothing, just fastboot, my baseband is MDM9625_104651.11.05.16.02R Quark_Custom, VZN XT1254, my locked bootloader status is keeping me from getting any of my files flashed successfully, Ive got copies of RSDlite 6.2.4 , my drivers installed, adb fastboot, and my stock image of VZN_/SU4TL-44, no success on flashing, plz help.

Just wondering, why did you use kingroot? It is not needed anymore.
https://youtu.be/6avEPGWB8E0
Sent from my XT1254 using Tapatalk

Sunshine shouldn't have bricked your device. But I believe in the moto maxx forum you'll find images to flash in fastboot.
http://forum.xda-developers.com/showthread.php?p=59659400

I'm not necessarily saying sunshine did brick my device I'm saying sunshine and kingroot together did cause some issue due to sunshine just wanting to constantly force close, so I rebooted the device, and it's got stuck in a soft brick boot loader loop, recovery including all other options but fastboot will respond, I am new with motorolla devices, especially on the 5.1 os, I picked up this phone as a trial and error device to do whatever with, I did follow rootjunkies video on using kingroot, I know now the method was outdated, lesson learned, but I can't get no fastboot flash commands to stick due to the original secured state of the bootloader, I've always steered away from motorolla and vzn due to the locking methods of the boatloader , phone was free hope I can get out of this state now lol

Thanks for the two post , I am attempting now I will update with results

Keep getting failed remote failure, I'm on a stock locked Boatloader, should I be trying rsdlite

lwilliz87 said:
Keep getting failed remote failure, I'm on a stock locked Boatloader, should I be trying rsdlite
Click to expand...
Click to collapse
RSDlite does nothing more than automate fastboot. If fastboot won't work, RSDlite won't work. What commands, exactly, are you trying to use to flash the images that you're trying to flash? If you're using that link to the Moto Maxx forum that mrkhigh provided, that won't help you, since the SU4TL-44 Droid Turbo firmware is not listed there. This is the one that you want: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip. I'm pretty sure that "remote failure" is what fastboot says when you attempt to flash an image that is not meant for the device, or an image that is an older version of the image that is on there (which is the case if you're trying to flash any of the firmwares listed on the Moto Maxx page).

Didn't note it stopped at .38

Remote failure
You are correct. yes I get remote failure, but I have already went thru rootjunk several times and downloaded that exxact VRZ_XT1254_SU4TL-44_44_CFC.xml.zip , I have the adb and fastboot both installed, and needed files, I have also mfastboot in there too. Ive ran the BAT.exe thru command prompt, Ive tried this with the same file mentioned above from rootjunkysdl, and from moto-firmware : Following out tonight
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>VRZ_XT1254
_SU4TL-44_44_CFC.bat
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>SET fastbo
ot=fastboot.exe
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.155s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 5.709s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.736s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2860 KB)...
OKAY [ 0.170s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.201s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.097s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.386s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.292s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (235017 KB)...
OKAY [ 13.362s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 17.003s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (250150 KB)...
OKAY [ 14.529s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.634s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (261098 KB)...
OKAY [ 9.887s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.120s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk4
target reported max download size of 536870912 bytes
sending 'system' (246901 KB)...
OKAY [ 9.053s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.100s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk5
target reported max download size of 536870912 bytes
sending 'system' (247563 KB)...
OKAY [ 9.430s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.515s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk6
target reported max download size of 536870912 bytes
sending 'system' (246206 KB)...
OKAY [ 9.523s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.608s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk7
target reported max download size of 536870912 bytes
sending 'system' (258024 KB)...
OKAY [ 9.215s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.405s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk8
target reported max download size of 536870912 bytes
sending 'system' (260155 KB)...
OKAY [ 9.700s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.923s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk9
target reported max download size of 536870912 bytes
sending 'system' (254924 KB)...
OKAY [ 9.498s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 23.768s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk10
target reported max download size of 536870912 bytes
sending 'system' (174885 KB)...
OKAY [ 7.398s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.558s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase ddr
erasing 'ddr'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.010s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>pause
Press any key to continue . . .

lwilliz87 said:
You are correct. yes I get remote failure, but I have already went thru rootjunk several times and downloaded that exxact VRZ_XT1254_SU4TL-44_44_CFC.xml.zip , I have the adb and fastboot both installed, and needed files, I have also mfastboot in there too. Ive ran the BAT.exe thru command prompt, Ive tried this with the same file mentioned above from rootjunkysdl, and from moto-firmware : Following out tonight
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>VRZ_XT1254
_SU4TL-44_44_CFC.bat
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>SET fastbo
ot=fastboot.exe
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.155s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 5.709s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.736s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2860 KB)...
OKAY [ 0.170s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.201s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.097s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.386s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.292s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (235017 KB)...
OKAY [ 13.362s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 17.003s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (250150 KB)...
OKAY [ 14.529s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.634s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (261098 KB)...
OKAY [ 9.887s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.120s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk4
target reported max download size of 536870912 bytes
sending 'system' (246901 KB)...
OKAY [ 9.053s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.100s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk5
target reported max download size of 536870912 bytes
sending 'system' (247563 KB)...
OKAY [ 9.430s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.515s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk6
target reported max download size of 536870912 bytes
sending 'system' (246206 KB)...
OKAY [ 9.523s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.608s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk7
target reported max download size of 536870912 bytes
sending 'system' (258024 KB)...
OKAY [ 9.215s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.405s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk8
target reported max download size of 536870912 bytes
sending 'system' (260155 KB)...
OKAY [ 9.700s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.923s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk9
target reported max download size of 536870912 bytes
sending 'system' (254924 KB)...
OKAY [ 9.498s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 23.768s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk10
target reported max download size of 536870912 bytes
sending 'system' (174885 KB)...
OKAY [ 7.398s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.558s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase ddr
erasing 'ddr'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.010s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Hmmmm. Interesting. Did you try entering the commands manually in a command prompt without using the batch file?

TheSt33v said:
Hmmmm. Interesting. Did you try entering the commands manually in a command prompt without using the batch file?
Click to expand...
Click to collapse
Yes I have tried entering the commands indiviually. only one that will come back with ok clear status most of the time without any failure is the fastboot flash boot boot.img , thats when i do it by itself, and today I downloaded the verizon wireless software assistant, it detected the phone needed repair, downloaded it downloads the correct software as it says, I have been selecting keep data, and then after numerous failed attempts and redownloads I been selecting erase devices data, and when it goes to flash it fails before even the first go, Im pretty sure my drivers are right, I dont know what to do . I hoping that maybe if this keeps on and with fingers crossed the new 6.0 update will hit my device soon and the software assistant will be able to update it for me with no problems, or I can flash it with no problems, right now I am uninstalling everything Motorola and gonna retry the VZW upgrade/repair again.

Sunshine did cause this unusual soft-hard brick. (Well, more like a faulty usb cable) I'll explain:
Fastboot is unable to run ANY commands that read or write to the device, EXCEPT for getvar all.
No flashing, erasing, get_unlock_data, ect.
Can't flash gpt,boot, bootloader ect.
Since I was unable to intentionally hardbrick his phone by flashing the turbo prototype engineering edition boot loader, he can't get into a hardbrick where he could use qh_loader.
To sum it up: Fastboot is broken, can't force a true hardbrick, kingroot doesn't touch any of this. Sunshine does.
This is a TRUE hardbrick, as we can unbrick hardbricks, but this is fubar'd royally.
Jtag will be the only solution

SaschaElble you just need to lay back on this stuff, you are going to do far more harm than good.
A) no sunshine didnt cause this, please backup this statement, its pretty obvious what is going on here
B) you need to stop advising people on these things, especially trying to get people to flash things that will hardbrick phones
C) example of B, motorola hasnt enabled jtag in ages
D) jtag doesnt fix emmc problems, jtag doesnt fix a hardware issue.
SunShine "doesnt touch any of that" either, again you are going off on things you don't understand. We even published a disclosure of what sunshine does touch, wish you had read it prior to throwing blame at us : http://theroot.ninja/disclosures/TRUSTNONE_1.0-11282015.pdf
This looks like some emmc issue imo.
SaschaElble said:
Sunshine did cause this unusual soft-hard brick. (Well, more like a faulty usb cable) I'll explain:
Fastboot is unable to run ANY commands that read or write to the device, EXCEPT for getvar all.
No flashing, erasing, get_unlock_data, ect.
Can't flash gpt,boot, bootloader ect.
Since I was unable to intentionally hardbrick his phone by flashing the turbo prototype engineering edition boot loader, he can't get into a hardbrick where he could use qh_loader.
To sum it up: Fastboot is broken, can't force a true hardbrick, kingroot doesn't touch any of this. Sunshine does.
This is a TRUE hardbrick, as we can unbrick hardbricks, but this is fubar'd royally.
...It's almost as if a totally different, and incompatible bootloader was flashed, but the conversion process was not completed by sunshines app. The entire partition table is messed up, and trying to flash gpt.bin to correct this fails as well. So a deeper rooted problem is present.
Jtag will be the only solution
Click to expand...
Click to collapse

A) Kingroot by itself sure didn't do it. User observed your app foreclosing and then device restarting, while this may be the intended sequence of events, the end result was a bricked turbo
B) Hardbricking via eng edition bootloader its a tested and unbrickable situtation.
C) Jtaging in this case had nothing to to with my intentional hardbrick, as hardbricks can be unbricked without jtag
D) How does this appear to be a emmc hardware problem? Device would boot into qh_loader mode if this was the case, as aboot would be unreachable.
E) Another user reported sending device out for jtag repair services, without further research I would assume such exist. In the most extreme cases, removing the emmc chip and flashing can be done.
SunShine "doesnt touch any of that" - This is assuming defined behavior, we are talking about undefined behavior = You can't prove it did, or didn't. But you can logically deduce that only sunshine modify's the way the turbo boots at the bootloader level. It may VERY well be that your app worked 100% as intended, but user's device had unexpected consequences. Still faulting sunshine.
This looks like some emmc issue imo. Again, a faulty emmc would cause the SoC to boot in to QH_Loader (unbrick mode) - This is not a faulty emmc. Even IF it was, this was directly after your app force closed and the device restarted.

SaschaElble said:
A) Kingroot by itself sure didn't do it. User observed your app foreclosing and then device restarting, while this may be the intended sequence of events, the end result was a bricked turbo
B) Hardbricking via eng edition bootloader its a tested and unbrickable situtation.
C) Jtaging in this case had nothing to to with my intentional hardbrick, as hardbricks can be unbricked without jtag
D) How does this appear to be a emmc hardware problem? Device would boot into qh_loader mode if this was the case, as aboot would be unreachable.
E) Another user reported sending device out for jtag repair services, without further research I would assume such exist. In the most extreme cases, removing the emmc chip and flashing can be done.
SunShine "doesnt touch any of that" - This is assuming defined behavior, we are talking about undefined behavior = You can't prove it did, or didn't. But you can logically deduce that only sunshine modify's the way the turbo boots at the bootloader level. It may VERY well be that your app worked 100% as intended, but user's device had unexpected consequences. Still faulting sunshine.
This looks like some emmc issue imo. Again, a faulty emmc would cause the SoC to boot in to QH_Loader (unbrick mode) - This is not a faulty emmc. Even IF it was, this was directly after your app force closed and the device restarted.
Click to expand...
Click to collapse
1.) Sunshine did not do this, period. Nothing in the sunshine apps gets anywhere near anything like this
2.) eMMC very frequently fail such that they can be read but not written. It's not uncommon at all
3.) JTAG is disabled on Motorola devices. Don't make assumptions.
By your logic, if I fill up my gas tank tomorrow and get a flat tire right afterwards, the bad gas caused it? Nice logic there.
--beaups

beaups said:
1.) Sunshine did not do this, period. Nothing in the sunshine apps gets anywhere near anything like this
2.) eMMC very frequently fail such that they can be read but not written. It's not uncommon at all
3.) JTAG is disabled on Motorola devices. Don't make assumptions.
By your logic, if I fill up my gas tank tomorrow and get a flat tire right afterwards, the bad gas caused it? Nice logic there.
--beaups
Click to expand...
Click to collapse
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?

SaschaElble said:
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
Click to expand...
Click to collapse
It is pointless indeed. We have the code, we know exactly what it is capable of, and its not capable of what's happened here. Argue all you want, you just continue to reinforce you have no clue how these devices work.
--beaups
Sent from my XT1254 using Tapatalk

Fine, I'm done.

SaschaElble said:
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
Click to expand...
Click to collapse
1) this isnt a bootloader issue, its an emmc issue, pretty dang obvious, i can see it from 30k feet up
2) I found his device ID, he never purchased sunshine (ask him), SunShine never actually ran on the device, because he never purchased it, SunShine never touched his device, just the purchasing framework (Which tests for root, basic compatibility etc) ran, and it doesnt touch anything.

Sanity tests can't cause harm?
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Either way the timing still sucks

[URGENT HELP NEEDED] DEVICE WON'T BOOT. please help. please, please!!!

Okay, I had a perfectly working Moto X4 (Indian Retail version), rooted and debloated. But then the idea of going back to unrooted struck me and I flashed the ROM with no problem. Then, I went back to the Bootloader (Had USB Debugging turned on and OEM Unlock "NOT" turned on in the Developer Options) and locked the bootloader by running oem lock and then, the Phone won't boot -
It gave me the message --
" Your Device is Corrupt. It can't be trusted and will not boot."
From then, I've tried reflashing the firmware - No luck.
It gives a "Permission denied" message in cmd and fails.
Unlocking the OEM worked with the get_unlock_data but then it asked me to turn on USB debugging in the developer options (and I can' boot the phone past the message).
I've tried booting into recovery, won't work - just the same message. Tried booting into the bootable TWRP - Won't work. Same message.
Fastboot erase cache erases the cache and won't do anything else.
PLEASE HELP ME. PLEASE....​
The CMD error log reads as -->
Code:
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot devices
ZY224JGPK4 fastboot
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.115s]
finished. total time: 0.123s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash bootloader bootloa
der.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.237s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.344s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash modem NON-HLOS.bin
target didn't report max-download-size
sending 'modem' (95999 KB)...
FAILED (command write failed (No error))
finished. total time: 0.010s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash fsg fsg.mbn
target didn't report max-download-size
sending 'fsg' (5508 KB)...
FAILED (command write failed (No error))
finished. total time: 0.008s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.002s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash bluetooth BTFM.bin
target didn't report max-download-size
sending 'bluetooth' (4540 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash dsp dspso.bin
target didn't report max-download-size
sending 'dsp' (16384 KB)...
FAILED (command write failed (No error))
finished. total time: 0.002s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash logo logo.bin
target didn't report max-download-size
sending 'logo' (2153 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_a' (19853 KB)...
OKAY [ 0.438s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.453s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516148 KB)...
OKAY [ 11.396s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.400s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (522692 KB)...
OKAY [ 15.666s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.671s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (521055 KB)...
OKAY [ 15.620s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.626s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523959 KB)...
OKAY [ 15.885s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.893s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (521817 KB)...
OKAY [ 16.218s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.226s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (522195 KB)...
OKAY [ 16.019s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.026s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (524276 KB)...
OKAY [ 16.235s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.242s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (167142 KB)...
OKAY [ 3.634s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.644s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system_b system_ot
her.img
target reported max download size of 536870912 bytes
sending 'system_b' (134369 KB)...
OKAY [ 2.931s]
writing 'system_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.942s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (237897 KB)...
OKAY [ 5.203s]
writing 'oem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 5.209s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase carrier
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>

At the time of posting there are only stock images available for the Retail US version of the X4. The only way to get back is to have backed up your original rom and also have "OEM Unlock" enabled in dev settings. Try contacting Lenovo and tell them your issue. They may be able to assist you by providing a stock firmware image or by having you send in your device for service.

Hi, i have just made the exact mistake you did. Did you manage to find a way to fix this?

FIX
For anyone that does get this issue i have managed to find a fix.
If you are unable to flash the official firmware (7.1.1/8.0) with locked boot loader then with fastboot enter "fastboot boot boot.img", this worked for me and i was able to get into android and enable OEM unlock to unlock the bootloader and then flash the official firmware.

I couldn't fix it. And the service center is not providing warranty since I've unlocked the bootloader and they're saying it's irreparable and asking me to change the whole motherboard of a 1 month old handset. I'll be bringing the phone back from service center tomorrow and will be trying this method

bot_rosco said:
For anyone that does get this issue i have managed to find a fix.
If you are unable to flash the official firmware (7.1.1/8.0) with locked boot loader then with fastboot enter "fastboot boot boot.img", this worked for me and i was able to get into android and enable OEM unlock to unlock the bootloader and then flash the official firmware.
Click to expand...
Click to collapse
Can you PLEASE FOR the love of God elaborate,please _/|\_

achyut said:
Can you PLEASE FOR the love of God elaborate,please _/|\_
Click to expand...
Click to collapse
First try factory reset (in recovery).
Go into bootloader, use vol buttons till it says boot recovery. It should reboot and show an android on its back. Press power and vol up. Then go down to format. Select the bottom option. It should take a few seconds and select reboot and it mite work if not just follow the above guide.
If that doesnt work,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img

bot_rosco said:
Sure,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
Click to expand...
Click to collapse
Then? Then it'll boot back normally?? Sorry,I don't have the phone with me yet (it's in service center).

achyut said:
Then? Then it'll boot back normally?? Sorry,I don't have the phone with me yet (it's in service center).
Click to expand...
Click to collapse
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck

bot_rosco said:
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
Click to expand...
Click to collapse
am gonna try it tomorrow and if it works, you're up for a token of gratitude from my side.

bot_rosco said:
First try factory reset (in recovery).
Go into bootloader, use vol buttons till it says boot recovery. It should reboot and show an android on its back. Press power and vol up. Then go down to format. Select the bottom option. It should take a few seconds and select reboot and it mite work if not just follow the above guide.
If that doesnt work,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
Click to expand...
Click to collapse
I can't boot recovery though, shows the same message

achyut said:
am gonna try it tomorrow and if it works, you're up for a token of gratitude from my side.
Click to expand...
Click to collapse
Good luck
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
achyut said:
I can't boot recovery though, shows the same message
Click to expand...
Click to collapse
i had same, worth a try tho.

bot_rosco said:
Good luck
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
i had same, worth a try tho.
Click to expand...
Click to collapse
You could try booting to the TWRP recovery, i.e. fastboot boot TWRP.img
and then wiping data from there.

jakejm79 said:
You could try booting to the TWRP recovery, i.e. fastboot boot TWRP.img
and then wiping data from there.
Click to expand...
Click to collapse
In think this depends on the firmware as oreo has encryption that does not play nice with twrp so it may not work, worth a try though.

nope. trying fastboot boot boot.img gives a <bootloader> permission denied! message and fails

achyut said:
nope. trying fastboot boot boot.img gives a <bootloader> permission denied! message and fails
Click to expand...
Click to collapse
Use mfastboot not fastboot, you'll have to add this to your tools. It's Motorola fastboot with proper permission.

bot_rosco said:
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
Click to expand...
Click to collapse
QWZR said:
Use mfastboot not fastboot, you'll have to add this to your tools. It's Motorola fastboot with proper permission.
Click to expand...
Click to collapse
my computer doesn't recognize mfastboot command. previously I've flashed the ROMs with just fastboot command

achyut said:
my computer doesn't recognize mfastboot command. previously I've flashed the ROMs with just fastboot command
Click to expand...
Click to collapse
You have to download it.
https://androidfilehost.com/?fid=95916177934532795

QWZR said:
You have to download it.
https://androidfilehost.com/?fid=95916177934532795
Click to expand...
Click to collapse
okay, set up and tried flashing, not working. even RSD Lite is giving "phone failed to switch to fastboot mode" error, even though the phone is in fastboot and is recognized as fastboot devices in cmd.
am running out of options now. damn...
any help? anyone??
please....

achyut said:
okay, set up and tried flashing, not working. even RSD Lite is giving "phone failed to switch to fastboot mode" error, even though the phone is in fastboot and is recognized as fastboot devices in cmd.
am running out of options now. damn...
any help? anyone??
please....
Click to expand...
Click to collapse
Have you tried the twrp method that someone mentioned above? Other than that i cant think of anything, sorry.