Database Users

mytouch fender stuck at "HTC Magic" splash screen.

I buddy of mine gave me this mytouch fender because he tried to root the phone and he's an idiot.
Now the phone is stuck at the "HTC Magic" splash screen and won't boot into android and won't boot into any kind of recover.
I can get into hboot though by holding down volume and power.
Where do I start? I have a Sprint Epic 4g that I rooted for my wife so I'm not a complete moron I just need a push in the right direction for this phone.

Start by post ALL fastboot info, ALL.
Plus the outcome of this command:
Code:
fastboot getvar version-main

I didn't want to get it wrong so I just took some pics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Actually, I might be a little closer to a moron than you think.
(I just meant that I can follow directions easily enough to get through a guide or tutorial)

You are in a very good shape...
Download this combo i made for you:
EDIT new link: http://rapidshare.com/files/432674806/MagicFenderCombo.zip
Download my fastboot commander, magic version. (check my signature)
Download rom: http://cyanogenmod-mirror.local.host.name/desire/cm/stable/update-cm-6.0.2-Desire-signed.zip
Download gapps: http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-tiny-20101020-signed.zip
Guide:
1) boot into fastboot mode
2) Start my tool
3) using the first tab, load hboot, radio and recovery respectively.
4) Push "flash all"
5) If all good, go to misc tab and push "reboot device". If not, post here and do not reboot the device or shutdown the tool.
6)Your fastboot info should have changed now :0)
7) Reboot into recovery
8)choose usb-toggle
9)now you have your sdcard mounted in your OS. Move the rom and gapps to the root of the sdcard.
10)Unmount the sdcard
11)Flash the rom
12)Flash the gapps
13)Reboot and enjoy :0)
I assume you know how to use the custom recovery!!!!
Good luck.

everything looked good until it tried to flash recovery. I have my system running still and I haven't rebooted yet.
From your tool log window:
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.
MagicFiles folder found.
hboot-1.33.2010.img found.
hboot-1.76.2007.img found.
radio_htc_pvt_32a_3.22.20.17.img found.
radio_htc_pvt_32a_6.35.16.19.img found.
recovery-ra-magic_6.35-v1.7.0.1.img found.
recovery-ra-sapphire-v1.7.0h.img found.
"Flash old" button enabled.
"Flash new" button enabled.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 3.22.20.17.
SPL/hboot version: 1.33.2010.
product: sapphire.
mid: sapp31000.
security: off.
build-mode: eng.
-----------------------------------.
Print of device info SUCCESSFUL.
Hboot, radio & recovery files set - FlashAll button enabled.
STARTING FLASH OF CUSTOM FILES.
Flashing "radio" - PLEASE WAIT.
"radio" flash SUCCESSFUL.
Flashing "hboot" - PLEASE WAIT.
"hboot" flash SUCCESSFUL.
Flashing "recovery" - PLEASE WAIT.
"recovery" flash FAILURE.
FLASH OF CUSTOM FILES FAILURE - RECOVERY FAILURE.

I noticed on the phone that all the other progress bars fill up and disappear but when it gets to the purple progress bar and tries to flash recovery it just sits there without filling in any color at all.
Somebody else was telling me that I needed a "gold card" because this is a Fender T-Mobile phone?
Anyway, I still have the phone in the last state it was in when the recovery failed to flash and I haven't rebooted yet. Waiting to here what to do next.

Try to flash the recovery alone!!!
Also provide the info inside the "actual tab".
Do not reboot, do not shutdown the tool....
You do not need any goldcard... you have eng spl...
Don't worry... as long the hboot and radio was ok, you are in no harm :0)

Same result when I try to flash recovery alone.
"Actual output" tab:
###Calling fastboot with: getvar version-baseband###
version-baseband: 3.22.20.17
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar version-bootloader###
version-bootloader: 1.33.2010
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar product###
product: sapphire
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar mid###
mid: SAPP31000
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar security###
security: off
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar build-mode###
build-mode: ENG
finished. total time: 0.000s
********************************
###Calling fastboot with: flash radio C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\radio.img###
sending 'radio' (21504 KB)... OKAY [ 5.938s]
writing 'radio'... OKAY [ 37.688s]
finished. total time: 43.625s
********************************
###Calling fastboot with: flash hboot C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\hboot_7201A_1.33.0013G_091021.nb0###
sending 'hboot' (512 KB)... OKAY [ 0.484s]
writing 'hboot'... OKAY [ 0.563s]
finished. total time: 1.047s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.719s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.531s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.719s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.531s
********************************

Ok... go misc tab. Select only the recovery in red square. Push "erase chosen partition". Now try to flash the recovery from the first tab again...
Remember to post the output from the "actual tab" here... i don't want the other info..

try to flash this instead:
http://rapidshare.com/files/387932920/recovery-RA-sapphire-v1.7.0G-cyan.img

It didn't work again after erasing recovery partition. Here's the output. I'm downloading that other file right now. You want me to flash that as recovery?
###Calling fastboot with: erase recovery###
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
********************************
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\MagicFenderCombo\recovery-RA-sapphire-v1.7.0G.img###
sending 'recovery' (4520 KB)... OKAY [ 1.704s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.522s

yes as recovery
also try this: http://www.androidspin.com/download...Y/&file=recovery-RA-sapphire-v1.6.2G-blue.img

tried cyan version and same result. The purple progress bar on the never starts to fill up.
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\Fender\recovery-RA-sapphire-v1.7.0G-cyan.img###
sending 'recovery' (4528 KB)... OKAY [ 1.703s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.517s
********************************

mumilover said:
yes as recovery
also try this: http://www.androidspin.com/download...Y/&file=recovery-RA-sapphire-v1.6.2G-blue.img
Click to expand...
Click to collapse
same result:
###Calling fastboot with: flash recovery C:\Documents and Settings\jtb30262\Desktop\Fender\recovery-RA-sapphire-v1.6.2G-blue.img###
sending 'recovery' (4580 KB)... OKAY [ 1.703s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 33.517s
********************************

check your pm

Flash the eng spl again, the 1.33.2010... find it under magicfiles bundled with the tool.
If it goes well, then reboot into fastboot again... then try to flash the recovery... if it goes well, then flash the hboot that was meant to the fender (the one you downloaded to begin with) and, reboot if that want well to.

brotha its beastie here is your answer
You need to revert back to a HTBOOT that will accept the update. Here is your instructions.
http://forum.xda-developers.com/showthread.php?t=622530

... and here is some help for AFTER you have downgraded
you should be able to apply the directions the original gentlemen told you after you downgrade. in order to downgrade you MUST have a goldcard. If his solution does not work do not fear but follow this http://forum.xda-developers.com/showthread.php?t=623141 and THEN apply his fix. Let me know via text or not if this works ... and get your ass back to work you too brent!

beastiezee said:
you should be able to apply the directions the original gentlemen told you after you downgrade. in order to downgrade you MUST have a goldcard. If his solution does not work do not fear but follow this http://forum.xda-developers.com/showthread.php?t=623141 and THEN apply his fix. Let me know via text or not if this works ... and get your ass back to work you too brent!
Click to expand...
Click to collapse
Brent and work in the same sentence. That's an oxymoron isn't it?

Unbrick Hard Bricked Moto G (2nd.Gen) [5.0/4.4.4]

Deleted

Reserved

It's possible to force downgrade bootloader from 5.0 to 4.4.4, or better to 4.4.2 with this method in working devices, not bricked ones?

@Falcon G my phone still not booting on bootloader
i think this guide not work on new bootloader android 5.0
Always get it http://forum.xda-developers.com/showpost.php?p=57312495&postcount=22

dadme said:
It's possible to force downgrade bootloader from 5.0 to 4.4.4, or better to 4.4.2 with this method in working devices, not bricked ones?
Click to expand...
Click to collapse
No You shouldn't even try it you may permanently brick your device.

Sandivisi said:
@Falcon G my phone still not booting on bootloader
i think this guide not work on new bootloader android 5.0
Click to expand...
Click to collapse
It will work on 5.0 if you see qhsusb_bulk when you plug in your phone

Falcon G said:
It will work on 5.0 if you see qhsusb_bulk when you plug in your phone
Click to expand...
Click to collapse
look this pic, i follow your guide. this right?

see pic again,
and this after i run blankflash.bat
Code:
# MSM8626
[config 0x801]
programmer=programmer_8626.mbn
singleimage=singleimage_8626.bin
[config 0x805]
programmer=programmer_8926.mbn
singleimage=singleimage_8926.bin
[diag error.0x010B0C0D]
count=2
message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet"
last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
[diag blank-flash]
fail=3
pass=0
yield=0.00%
dphu=100.00
[diag error.0x010B0C13]
count=1
message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame"
last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC

Sandivisi said:
see pic again,
and this after i run blankflash.bat
Code:
# MSM8626
[config 0x801]
programmer=programmer_8626.mbn
singleimage=singleimage_8626.bin
[config 0x805]
programmer=programmer_8926.mbn
singleimage=singleimage_8926.bin
[diag error.0x010B0C0D]
count=2
message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet"
last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
[diag blank-flash]
fail=3
pass=0
yield=0.00%
dphu=100.00
[diag error.0x010B0C13]
count=1
message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame"
last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
Click to expand...
Click to collapse
I have the same problem. I installed brazilian soak test, then set 4.4.2 and updated on OTA to 4.4.4, during installation my device is dead. Now in Task Manager Qualcomm HS-USB QDLoader 9008. Probably i think need this utility for 5.0 bootloader, MBM-CL or qboot, i do not know....

MadL1fe said:
I have the same problem. I installed brazilian soak test, then set 4.4.2 and updated on OTA to 4.4.4, during installation my device is dead. Now in Task Manager Qualcomm HS-USB QDLoader 9008. Probably i think need this utility for 5.0 bootloader, MBM-CL or qboot, i do not know....
Click to expand...
Click to collapse
maybe i give up now, because no dev or someone cant help us!
i will bought my moto g to service center motorola, tommorrow maybe
hope my device get back.

Sandivisi said:
see pic again,
and this after i run blankflash.bat
Code:
# MSM8626
[config 0x801]
programmer=programmer_8626.mbn
singleimage=singleimage_8626.bin
[config 0x805]
programmer=programmer_8926.mbn
singleimage=singleimage_8926.bin
[diag error.0x010B0C0D]
count=2
message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet"
last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
[diag blank-flash]
fail=3
pass=0
yield=0.00%
dphu=100.00
[diag error.0x010B0C13]
count=1
message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame"
last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
Click to expand...
Click to collapse
Hi is this the XT1033 you are running blankflash on?
Have you unzipped all the files to a folder.
Also have you tried switching the usb cable with a different one.

Sandivisi said:
maybe i give up now, because no dev or someone cant help us!
i will bought my moto g to service center motorola, tommorrow maybe
hope my device get back.
Click to expand...
Click to collapse
In my country no motorola...

Falcon G said:
Hi is this the XT1033 you are running blankflash on?
Have you unzipped all the files to a folder.
Also have you tried switching the usb cable with a different one.
Click to expand...
Click to collapse
yes, it is on XT-1033
yes, iam also unzipped all the files to a folderbut still no work
i tired all switching the usb cable but still get some problem
I think, this guide not work on new bootloader until someone get MBM-CI from Android 5 or someone create singleimage
MadL1fe said:
In my country no motorola...
Click to expand...
Click to collapse
so just wait until someone can help us

Falcon G said:
Hi is this the XT1033 you are running blankflash on?
Have you unzipped all the files to a folder.
Also have you tried switching the usb cable with a different one.
Click to expand...
Click to collapse
Are you sure this is contains the 5.0 bootloader image or 4.4.4?
These errors the ppl get if they tried to install the OTA to 4.4.4 from 4.4.2 are due to bootloader downgrade which ofc doesnt work.Now they need the 5.0 bootloader to blankflash it and get the devices working.
Can you confirm which version you're offering in the OP?

liveroy said:
Are you sure this is contains the 5.0 bootloader image or 4.4.4?
These errors the ppl get if they tried to install the OTA to 4.4.4 from 4.4.2 are due to bootloader downgrade which ofc doesnt work.Now they need the 5.0 bootloader to blankflash it and get the devices working.
Can you confirm which version you're offering in the OP?
Click to expand...
Click to collapse
Yes it works with 5.0 boot loader (41.3 or something)
Sent from my XT1031 using Tapatalk

Falcon G said:
Yes it works with 5.0 boot loader (41.3 or something)
Sent from my XT1031 using Tapatalk
Click to expand...
Click to collapse
Nope.
OKAY [ 1.815s]
identifying device
...serial = 0x23EC8AD
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.007s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.003s]
validating files
OKAY [ 0.026s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
OKAY [ 0.011s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)

My bootloader v 0x4816.
i have just updated to lollipop based on 1064 firware.
i got 1068.
Is my bootloader for lollipop

It don't work, please advice.... http://forum.xda-developers.com/moto-g/help/dead-moto-g-xt1032-lollipop-downgrade-t2966996

This works to a small degree. It fixes the brick part and gets to boot-loader, but that's as far as it'll go. It'll give either a "Permission Denied" or a "Preflash Validation Failed" or a "Remote Failure" for every and any file you try to flash or boot into afterwards, be it in fastboot or mfastboot.
Code:
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot devices
a0918259 fastboot
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash bootl
oader motoboot.img
target max-sparse-size: 256MB
sending 'bootloader' (1953 KB)...
OKAY [ 0.100s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.127s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash parti
tion gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.367s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>fastboot boot recover
y.img
downloading 'boot.img'...
OKAY [ 0.339s]
booting...
FAILED (remote failure)
finished. total time: 0.343s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot boot recove
ry.img
downloading 'boot.img'...
OKAY [ 0.342s]
booting...
FAILED (remote failure)
finished. total time: 0.346s

VictoriousShooter said:
This works to a small degree. It fixes the brick part and gets to boot-loader, but that's as far as it'll go. It'll give either a "Permission Denied" or a "Preflash Validation Failed" or a "Remote Failure" for every and any file you try to flash or boot into afterwards, be it in fastboot or mfastboot.
Code:
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot devices
a0918259 fastboot
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash bootl
oader motoboot.img
target max-sparse-size: 256MB
sending 'bootloader' (1953 KB)...
OKAY [ 0.100s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.127s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash parti
tion gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.367s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>fastboot boot recover
y.img
downloading 'boot.img'...
OKAY [ 0.339s]
booting...
FAILED (remote failure)
finished. total time: 0.343s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot boot recove
ry.img
downloading 'boot.img'...
OKAY [ 0.342s]
booting...
FAILED (remote failure)
finished. total time: 0.346s
Click to expand...
Click to collapse
man u atleast got to fastboot but we are still stuck on blank screen...btw did u flash the lollipop ota? wer u on 4.4.4 bootloader or 5.0 bootloadeR?

[FIRMWARE] [XT1069] [STOCK] [5.0.2] [FASTBOOT] RETBR_XT1069_5.0.2_LXB22.46-28.zip

Stock ZIP Firmware for XT1069
File: RETBR_XT1069_5.0.2_LXB22.46-28.zip​
Tested and working 100%!
Stock, retail firmware for XT1069. Android Lollipop 5.0.2.
DOWNLOAD LINK: Mega
PLEASE NOTE: Your device will be fully wiped!
Be warned and backup your data.
Proceed at your own risk! Do not blame me for bricked devices.
Instructions:
1. Download and unzip firmware file from above.
2. Download mfastboot from here and unzip in the same folder as firmware files.
3. Boot your device into bootloader and connect to computer via USB.
2. Flash firmware with fastboot. Flashing commands provided below.
ATTENTION! For Lollipop firmware, there's a 4th system.img_sparsechunk. (KitKat FW had only 3 files.)
Please see changes in flashing commands below.
Code:
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 system system.img_sparsechunk.4
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 reboot
After reboot, enjoy your fresh Lollipop.
Notes: This is the stock Motorola firmware file, for XT1069 device (only!), Android version 5.0.2 (Lollipop).
This firmware is NOT rooted.
To remove the "Unlocked Bootloader Warning", please refer to my other topic, here.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any comments, please write below.
If you like, hit THANKS button. :good:

rafaelbrunner said:
Stock ZIP Firmware for XT1069
File: RETBR_XT1069_5.0.2_LXB22.46-28.zip​
Tested and working 100%!
Stock, retail firmware for XT1069. Android Lollipop 5.0.2.
DOWNLOAD LINK: Mega
PLEASE NOTE: Your device will be fully wiped!
Be warned and backup your data.
Proceed at your own risk! Do not blame me for bricked devices.
Instructions:
1. Download and unzip firmware file from above.
2. Download mfastboot from here and unzip in the same folder as firmware files.
3. Boot your device into bootloader and connect to computer via USB.
2. Flash firmware with fastboot. Flashing commands provided below.
ATTENTION! For Lollipop firmware, there's a 4th system.img_sparsechunk. (KitKat FW had only 3 files.)
Please see changes in flashing commands below.
Code:
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 system system.img_sparsechunk.4
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 reboot
After reboot, enjoy your fresh Lollipop.
Notes: This is the stock Motorola firmware file, for XT1069 device (only!), Android version 5.0.2 (Lollipop).
This firmware is NOT rooted.
To remove the "Unlocked Bootloader Warning", please refer to my other topic, here.
Screenshot:
Any comments, please write below.
If you like, hit THANKS button. :good:
Click to expand...
Click to collapse
Friend would offer me only the file MOTOBOOT.img ???

iamDeeh said:
Friend would offer me only the file MOTOBOOT.img ???
Click to expand...
Click to collapse
If you want to update your bootlaoder .. There's a thread for that ! With all necessary links ! Refer that please

Unable to flash my xt1069
Hello , my xt1069 is stock in initial logo becouse that i follow all steps in this tutorial but when reboot nothing happens is still stock in initial logo. I hope that you help me. Sorry for my bad english

reisyreinier said:
Hello , my xt1069 is stock in initial logo becouse that i follow all steps in this tutorial but when reboot nothing happens is still stock in initial logo. I hope that you help me. Sorry for my bad english
Click to expand...
Click to collapse
This is a stock firmware so your phone should be stock after flashing.
What do you mean with "initial logo"?

reisyreinier said:
Hello , my xt1069 is stock in initial logo becouse that i follow all steps in this tutorial but when reboot nothing happens is still stock in initial logo. I hope that you help me. Sorry for my bad english
Click to expand...
Click to collapse
Do you mean Stuck at boot logo?

reefuge said:
Do you mean Stuck at boot logo?
Click to expand...
Click to collapse
Yes, that's what I meant is stuck at boot logo. I unlock the bootloader and do the process again but the result is the same. When i execute comands the phone show yellows letters, in other post i read that this is a good signal and all commands return OK but when restart still stuck at boot logo. The phone is Motorola XT1069 dual sim

Is it worth to update it from Kitkat to Lollipop? Why?

reisyreinier said:
Yes, that's what I meant is stuck at boot logo. I unlock the bootloader and do the process again but the result is the same. When i execute comands the phone show yellows letters, in other post i read that this is a good signal and all commands return OK but when restart still stuck at boot logo. The phone is Motorola XT1069 dual sim
Click to expand...
Click to collapse
have you deleted usercache and datacache once you have flashed all files BEFORE you reboot ?
put phone into ap fastboot mode and run my test -reset .bat file from the attached zip file (please unzip to pc )
choose option 5 - reset
choose option 4 - reboot
choose option 6 - exit

reefuge said:
have you deleted usercache and datacache once you have flashed all files BEFORE you reboot ?
put phone into ap fastboot mode and run my test -reset .bat file from the attached zip file (please unzip to pc )
choose option 5 - reset
choose option 4 - reboot
choose option 6 - exit
Click to expand...
Click to collapse
Yes, i delete usercache and datacache before reboot but anyway i run your script and this is the result for option 5
FACTORY RESET
ECHO is off.
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.016s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.031s]
finished. total time: 0.094s
Done!.........
Then reboot and nothing happens the phone is still stuck in boot logo.
Is there any pre-condition to run the process(i mean battery fully charged, etc)?
I ask you that becouse all commands return ok but dont do anything.
This is the log for complete process
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
OKAY [ 0.309s]
finished. total time: 0.328s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2184 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.991s]
finished. total time: 1.087s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (697 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.059s]
finished. total time: 0.131s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.362s]
writing 'boot'...
OKAY [ 0.192s]
finished. total time: 0.554s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.373s]
writing 'recovery'...
OKAY [ 0.193s]
finished. total time: 0.566s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257607 KB)...
OKAY [ 8.103s]
writing 'system'...
OKAY [ 4.578s]
finished. total time: 12.681s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (256614 KB)...
OKAY [ 8.071s]
writing 'system'...
OKAY [ 4.911s]
finished. total time: 12.982s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (259672 KB)...
OKAY [ 8.166s]
writing 'system'...
OKAY [ 4.764s]
finished. total time: 12.930s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (240897 KB)...
OKAY [ 7.581s]
writing 'system'...
OKAY [ 3.939s]
finished. total time: 11.520s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (38920 KB)...
OKAY [ 1.269s]
writing 'system'...
OKAY [ 0.658s]
finished. total time: 1.927s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.595s]
writing 'modem'...
OKAY [ 0.812s]
finished. total time: 2.406s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.059s]
finished. total time: 0.059s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1013 KB)...
OKAY [ 0.117s]
writing 'fsg'...
OKAY [ 0.046s]
finished. total time: 0.163s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.063s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.067s]
finished. total time: 0.067s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot -w
erasing 'userdata'...
OKAY [ 0.018s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.068s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.048s]
finished. total time: 0.178s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot reboot
rebooting...
finished. total time: 0.001s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$
thanks in advance for your time

reisyreinier said:
Yes, i delete usercache and datacache before reboot but anyway i run your script and this is the result for option 5
FACTORY RESET
ECHO is off.
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.016s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.031s]
finished. total time: 0.094s
Done!.........
Then reboot and nothing happens the phone is still stuck in boot logo.
Is there any pre-condition to run the process(i mean battery fully charged, etc)?
I ask you that becouse all commands return ok but dont do anything.
This is the log for complete process
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
OKAY [ 0.309s]
finished. total time: 0.328s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2184 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.991s]
finished. total time: 1.087s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (697 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.059s]
finished. total time: 0.131s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.362s]
writing 'boot'...
OKAY [ 0.192s]
finished. total time: 0.554s
[email protected]sarrollo22:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.373s]
writing 'recovery'...
OKAY [ 0.193s]
finished. total time: 0.566s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257607 KB)...
OKAY [ 8.103s]
writing 'system'...
OKAY [ 4.578s]
finished. total time: 12.681s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (256614 KB)...
OKAY [ 8.071s]
writing 'system'...
OKAY [ 4.911s]
finished. total time: 12.982s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (259672 KB)...
OKAY [ 8.166s]
writing 'system'...
OKAY [ 4.764s]
finished. total time: 12.930s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (240897 KB)...
OKAY [ 7.581s]
writing 'system'...
OKAY [ 3.939s]
finished. total time: 11.520s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (38920 KB)...
OKAY [ 1.269s]
writing 'system'...
OKAY [ 0.658s]
finished. total time: 1.927s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.595s]
writing 'modem'...
OKAY [ 0.812s]
finished. total time: 2.406s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.059s]
finished. total time: 0.059s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1013 KB)...
OKAY [ 0.117s]
writing 'fsg'...
OKAY [ 0.046s]
finished. total time: 0.163s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.063s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.067s]
finished. total time: 0.067s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot -w
erasing 'userdata'...
OKAY [ 0.018s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.068s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.048s]
finished. total time: 0.178s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$ fastboot reboot
rebooting...
finished. total time: 0.001s
[email protected]:~/Documents/desarrollo_propio/Moviles/Motorola XT 1069/RETBR_XT1069_5.0.2_LXB22.46-28_cid12_CFC.xml$
thanks in advance for your time
Click to expand...
Click to collapse
I will say the 1st boot after flashing can take 10 minutes + so it may seem stuck but isn't... have you left a good 15 to 20 minutes to pass before confirming its stuck // also you do have a xt1069 for certain?
battery must be over about 25% if I remember correctly -- think it refuses and says about battery too low in >10% in red -
I know with my xt1068 not only is there 8gb and 16gb but also early and late version (the late having a toshiba front cam) and uses LXB22-99-16 (feb 25th build) as opposed to (6th jan build) -my xt1068 can run either build as the early model
are xt1069 dual sim like xt1068 with added dtv ?

reefuge said:
I will say the 1st boot after flashing can take 10 minutes + so it may seem stuck but isn't... have you left a good 15 to 20 minutes to pass before confirming its stuck // also you do have a xt1069 for certain?
battery must be over about 25% if I remember correctly -- think it refuses and says about battery too low in >10% in red -
I know with my xt1068 not only is there 8gb and 16gb but also early and late version (the late having a toshiba front cam) and uses LXB22-99-16 (feb 25th build) as opposed to (6th jan build) -my xt1068 can run either build as the early model
are xt1069 dual sim like xt1068 with added dtv ?
Click to expand...
Click to collapse
Sorry for the delay, but I had connectivity issues
I had never waited the 10 min, so I followed your advice, but after 30 min the outcome was the same, the phone was stuck at the boot logo. Yes my phone is dual sim and supports dtv. Im very shure that i have an xt1069, my intention is upload a picture from back side of my phone(label) but i dont know how to upload a picture to here.
thanks in advance

Hey, my frontal camera dont work after installing this rom, Im sure that is the correct rom (motorola moto g DTV ), and the camera was working before.
what should i do? factory reset again??
----
edit:
i think i found the solution, so i'm just trying to use another rom instead

thalesw said:
Hey, my frontal camera dont work after installing this rom, Im sure that is the correct rom (motorola moto g DTV ), and the camera was working before.
what should i do? factory reset again??
----
edit:
i think i found the solution, so i'm just trying to use another rom instead
Click to expand...
Click to collapse
Use this later version for toshiba front cam you need this LXB22.91-16 version for xt1069 BR stock rom

Droid Turbo Downgrade 5.1 Lollipop OTA to 4.4.4 Kitkat

Hi, i know some of you are not very happy with the update, and ONLY if you took the OTA (and not flashed the full image) there is still hope for you.
im not sure if this will work, i need someone with a Droid Turbo (DT) to try.
the risk is 0, if this metod doesnt work, it will simply not flash, so no risk on it.
First you have to download the original Kitkat Firmware of Droid Turbo:
https://mega.co.nz/#!hZVThbjC!SqvNd7KYqYEvnbHRulVKJ2N9dsjMuNXpkcl1h-ENL3g
Requisites:
Android Studio or Minimal ADB and Fasboot (i personally recommend Minimal Adb and Fastboot because thats all we gonna need and its lighter than Android Studio 2 Mb vs 800Mb)
Kitkat Firmware
mFastboot (motorola Fastboot) i uploaded it for you: https://mega.co.nz/#!MVtz1DLb!CZTh_-wCl-qyta4Q0yZuPk_TB6Wq7Z4zElk6eArXrXk
Installation:
1.- Install MAaF
Install Minimal ADB and Fastboot
2.- Install mFastboot
Copy the contents of mfastboot.zip and put them on Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot)
Now you have working Fastboot AND mFastboot
3.- Copy Firmware
Copy the contents of your desired firmware to Minimal ADB and Fastboot Folder like this:
VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml
unzip and put all content of the file on the Minimal ADB and Fastboot Folder
Now you are ready to flash!
First turn off your device and Put it on fastboot mode (Power and volume down for 2 seconds with your phone off)
4.- Get Detected
type
Code:
fastboot devices
on minimal adb to see if your pc detects your phone on fastboot mode
if you get some numbers and letters like the picture you are ready to go.
if not, you are missing drivers, looks for Motorola Device Manager
5.- Install
Copy and Paste these commands on Minimal ADB and Fastboot:
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
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 erase cache
mfastboot reboot
Click to expand...
Click to collapse
and thats all, as easy as copy from here and paste on cmd.
i highly recommend that you erase everything for a smoother experience, but some people want to keep all their files, so this line its optional
mfastboot erase userdata
Click to expand...
Click to collapse
and thats all, as easy as copy from here and paste on cmd.
when your phone finishes flashing just press enter to execute mfastboot reboot and you will boot kitkat again
Once again i have not tried this, the bigger risk is that you will have to flash lollipop again in case it doesnt work.
Anyone willing to try? be the first to downgrade to Kitkat!

Gonna test it out now!!
Thanks man!!!
Also below is a link for the 21.128-15_15_CFC_SVC.xml (got errors when trying to unzip your download @Jaocagomez)
http://www.rootjunkysdl.com/files/Droid%20Turbo/Firmware/VRZ_XT1254_KDF21.128-15_15_CFC_SVC.xml.zip

You are going to get a Preflash Validation failed error message from fastboot. This was attempted when people had soft bricks from sideloading the ota and there was no img available.
http://gyazo.com/c5d1be6c5a88265bf13af3cbce30ce12

I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(

weaver11b said:
I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(
Click to expand...
Click to collapse
what happens if you skip bootloader.img?

This happens:
C:\adb>mfastboot flash radio radio.img
target max-sparse-size: 256MB
sending 'radio' (85544 KB)...
OKAY [ 2.682s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
OKAY [ 1.734s]
finished. total time: 4.420s
C:\adb>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.786s
C:\adb>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 0.472s]
finished. total time: 0.994s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\adb>

weaver11b said:
This happens:
C:\adb>mfastboot flash radio radio.img
target max-sparse-size: 256MB
sending 'radio' (85544 KB)...
OKAY [ 2.682s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
OKAY [ 1.734s]
finished. total time: 4.420s
C:\adb>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.786s
C:\adb>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 0.472s]
finished. total time: 0.994s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\adb>
Click to expand...
Click to collapse
Looks like its not gonna work, damn

weaver11b said:
I didn't side load mine, i took the OTA and as per his directions this MAY work with the OTA so it is worth a shot.
---------- Post added at 12:01 PM ---------- Previous post was at 11:24 AM ----------
There is now no hope whatsoever for those who took the OTA. I think it is time I accidentally drop my phone and call for a replacement. Although the only thing i truly wanted root for was to kill the wakelocks using amplify, greenify, and powernap. This phone still get 2days worth of battery with 5.1, just feel emasculated without root :'(
Click to expand...
Click to collapse
Side loading the OTA zip and taking the OTA update are the samething.
There is the same amount of hope as there has always been. This method was already tried at least two weeks ago, there is nothing special about it. It is the same way you flash any motorola image from fastboot.

what about flashing kitkat with mofo?
not free but it could work

How is this any different than RootJunky's youtube method of reverting back to stock KK firmware? If you click on the VRZ_XT1254_KDF21.128-15_15_CFC.bat in the folder you download from his site file in fastboot it runs these commands which are similar to yours.
SET fastboot=fastboot.exe
%fastboot% oem fb_mode_set
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot bootloader.img
%fastboot% flash radio radio.img
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
%fastboot% flash system system.img_sparsechunk4
%fastboot% flash system system.img_sparsechunk5
%fastboot% flash system system.img_sparsechunk6
%fastboot% erase ddr
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% oem fb_mode_clear
pause
This is the standard way of reverting back to the original KK firmware and I've been able to do it from a Mofo'd CF Lollipop image fine. If you took the Lollipop OTA this method is gonna be incompatible with the updated Lollipop bootloader. You need the original KK bootloader for this to work.

sorry, dont work after flash original image brazil 5.0.2 rsdlite?

Jaocagomez said:
Looks like its not gonna work, damn
Click to expand...
Click to collapse
based on this I am closing this thread

Hard Brick (QDL state) --> Back to life (essential support) & sensors not working

Hard Brick (QDL state) --> Back to life (essential support) & sensors not working
Hi everyone,
Hope you are doing well, here my little story :
My PH was dead (QDL state) after a bad flashing, thanks to essential support I could have back my phone working, but unfortunately sensors (auto rotation & compass) are not working.
Essential support recommend me to re flash the last build that would probably be the best shot at getting the phone back up and running.
I would like to have your process recommendation to minimize the risk of a second hard brick. What USB C cable & windows drivers I should have, and what flashing process will be the best to re-flash the latest stock build ?
Current build phone: QP1A.190711.148
baseband version : 2.0.c4-M2.0.10
Kernel: 4.4.19-perf+
Bootloader unlock " DEVICE STATE - unlocked" (but i do not know if the critical partition is unlock too)
If you recommend me to run some other test before flashing, let me know.
Thank you in advance for your help.

Most of what you're asking is on the Essential Developer site. As far as a cable goes, just make sure it's not the originally supplied C-C cable supplied by Essential. I use an A-C cable.

Ok thank you, just to be sure, in the process I do not need to "Run the command: fastboot flashing unlock" as my device seems unlock.
I have the following :
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Device modem EFS unlocked: false ???
(bootloader) Charger screen enabled: true

I just make a test by running the flashall.bat and after more than 20 min I have the following state:
C:\...\platform-tools>fastboot flash nvdef_a nvdef.img
Sending 'nvdef_a' (310 KB) OKAY [ 0.095s]
Writing 'nvdef_a' OKAY [ 0.005s]
Finished. Total time: 0.207s
C:\...\platform-tools>fastboot flash nvdef_b nvdef.img
Sending 'nvdef_b' (310 KB) OKAY [ 0.094s]
Writing 'nvdef_b' OKAY [ 0.005s]
Finished. Total time: 0.111s
C:\...\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (23857 KB) OKAY [ 0.613s]
Writing 'boot_a' FAILED (remote: 'Error flashi
ng partition.')
fastboot: error: Command failed
C:\...\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (23857 KB) OKAY [ 0.632s]
Writing 'boot_b' FAILED (remote: 'Error flashi
ng partition.')
fastboot: error: Command failed
C:\...\platform-tools>fastboot flash system_a system.img
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 25.063s]
Writing 'system_a' FAILED (remote: 'Flash Write
Failure')
fastboot: error: Command failed
C:\...\platform-tools>fastboot flash system_b system.img
_ "still waiting the result"
Can I disconnect o reboot the the phone manually ?
--> Everything works fine finally, i used an other cable A-C

Hi !
How did you solve your hardbrick problem please ?
Thank you !

The key point is OPs device was bootloader unlocked prior to issues happening.
The common hard Rock issue most face is when the bootloader device is locked and an upgrade is borked. This is when the user is left with no recourse except get support from essential which is situational (send device back and get a replacement), if essential decides they want to help based on your circumstance.