Database Info

[Q] XT925 with XT926 Firmware Brick

I need some help right here. I have flashed XT925 by mistake with stock veryzon 4.1.2 (XT926 firmware). I'm stuck in fastboot mode, my Bootloader is LOCKED, thats really weird because I was unlocked before I've tried to update via OTA (my phone was bricked after that OTA update fail). I tried to flash Retail Brasil JB and some other firmwares via fastboot and RSD Lite 6.1.5 with no results... this is what my fastboot screen shows up:
---------------------o---------------------------------
Device is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
----------------------o---------------------------------
Hope you can help me :S

Are you sure you were unlocked? Seems to me you may be screwed.
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
Are you sure you were unlocked? Seems to me you may be screwed.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Yes I'm sure, my status code was 3 not 0. What do you think I can do now? Is there any solution?

I remember seeing something about the gpt while searching for a solution for a different fastboot error. But like you I'm to lazy to search for it. Since it is your problem you probably should.
Sent from my DROID RAZR HD using Tapatalk 4

mentose457 said:
I remember seeing something about the gpt while searching for a solution for a different fastboot error. But like you I'm to lazy to search for it. Since it is your problem you probably should.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
I don't know what to do, i tried a lot of possible solutions out there but I can't flash a single file to my phone. I've tried via fastboot and RSD 6.1.5 with no results, and I can't start recovery, just fastboot mode showing this screen:
Code:
Device is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT

chuYxP said:
I don't know what to do, i tried a lot of possible solutions out there but I can't flash a single file to my phone. I've tried via fastboot and RSD 6.1.5 with no results, and I can't start recovery, just fastboot mode showing this screen:
Code:
Device is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
Click to expand...
Click to collapse
Make sure your phone is mostly charged and you are trying to flash the correct firmware. http://forum.xda-developers.com/showthread.php?t=2032284

mentose457 said:
Make sure your phone is mostly charged and you are trying to flash the correct firmware. http://forum.xda-developers.com/showthread.php?t=2032284
Click to expand...
Click to collapse
I tried the newest Retail Br, Telcel Mexico and one from Veryzon for XT926 with no results.
I can't flash anything in fastboot or in RSD Lite, so maybe I will take it to Telcel, they will send it to Motorola and let's see what they say. Hope they don't notice that I unlocked the bootloader, although it says that is LOCKED and status = 0... let's see what happens

Any other ideas? Please, there must be something to do to fix this.

chuYxP said:
Any other ideas? Please, there must be something to do to fix this.
Click to expand...
Click to collapse
Make sure your phone is recognized in fastboot mode. While in fastboot mode type the following in the command prompt:
Code:
fastboot devices
You should see the devices serial number in the output.
If that works type the following in the command prompt while in fastboot mode:
Code:
fastboot oem fb_mode_clear
Then type the following:
Code:
fastboot reboot-bootloader
When it reboots back into the bootloader attempt to flash the stock firmware again.
---------- Post added at 04:27 PM ---------- Previous post was at 04:20 PM ----------
chuYxP said:
Code:
Device is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
Click to expand...
Click to collapse
If this is truly what you get when you try to flash then I can guarentee your phone is not connected correctly. It should say USB Connected where it currently says Connect USB.
---------- Post added at 04:31 PM ---------- Previous post was at 04:27 PM ----------
Make sure the correct drivers are installed. You can get them from HERE. Note that windows will remove your drivers at will. So even if you had them installed before, install them again.

mentose457 said:
Make sure your phone is recognized in fastboot mode. While in fastboot mode type the following in the command prompt:
Code:
fastboot devices
You should see the devices serial number in the output.
If that works type the following in the command prompt while in fastboot mode:
Code:
fastboot oem fb_mode_clear
Then type the following:
Code:
fastboot reboot-bootloader
When it reboots back into the bootloader attempt to flash the stock firmware again.
---------- Post added at 04:27 PM ---------- Previous post was at 04:20 PM ----------
If this is truly what you get when you try to flash then I can guarentee your phone is not connected correctly. It should say USB Connected where it currently says Connect USB.
---------- Post added at 04:31 PM ---------- Previous post was at 04:27 PM ----------
Make sure the correct drivers are installed. You can get them from HERE. Note that windows will remove your drivers at will. So even if you had them installed before, install them again.
Click to expand...
Click to collapse
It doesn't work. I've just tried that and I just can't flash a single Rom. The "fastboot oem fb_mode_clear" command doesn't work, I can't clear my fastboot screen on my device.
Sorry but my phone its connected properly, it says usb connected at the end of the screen. I reinstalled drivers too, but nothing changes, so maybe I'm screwed.

chuYxP said:
It doesn't work. I've just tried that and I just can't flash a single Rom. The "fastboot oem fb_mode_clear" command doesn't work, I can't clear my fastboot screen on my device.
Sorry but my phone its connected properly, it says usb connected at the end of the screen. I reinstalled drivers too, but nothing changes, so maybe I'm screwed.
Click to expand...
Click to collapse
Did
Code:
fastboot devices
show your serial number?

Yes, here is it:
Code:
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot de
vices
208f36d2 fastboot
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot oe
m fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot re
boot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>
But nothing happened, the fastboot screen on device still shows the same.

chuYxP said:
Yes, here is it:
Code:
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot de
vices
208f36d2 fastboot
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot oe
m fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot re
boot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>
Click to expand...
Click to collapse
Thats good. Now use this utility to flash the stock rom. http://forum.xda-developers.com/forumdisplay.php?f=1866
Download the 'lite' version.

mentose457 said:
Thats good. Now use this utility to flash the stock rom. http://forum.xda-developers.com/forumdisplay.php?f=1866
Download the 'lite' version.
Click to expand...
Click to collapse
Do you mean Mr.Parkinsons DroidHD Utility 2.0? Ok I will try it right now, hope it works, thanks.

chuYxP said:
Do you mean Mr.Parkinsons DroidHD Utility 2.0? Ok I will try it right now, hope it works, thanks.
Click to expand...
Click to collapse
You are correct. Sorry about the bad link.
Sent from my DROID RAZR HD using Tapatalk 4

mentose457 said:
You are correct. Sorry about the bad link.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
It's ok don't worry, I'm downloading the Lite version now (about 637 MB)

It doesn't worked, and my battery is dying, it says "Battery: Low" now

chuYxP said:
It doesn't worked, and my battery is dying, it says "Battery: Low" now
Click to expand...
Click to collapse
Power it off and charge it with a wall charger. I believe you cannot fastboot if the charge is below 50%.
Where does it fail? What does the utility say?

mentose457 said:
Power it off and charge it with a wall charger. I believe you cannot fastboot if the charge is below 50%.
Where does it fail? What does the utility say?
Click to expand...
Click to collapse
I can't charge with wall charger, my phone thinks that is a USB data cable and fastboot shows up... here is what the utility say:
Code:
*****************
* 4.1.2 Restore *
* by *
* Mr. Parkinson *
*****************
This program will restore your phone to Verizon stock Android 4.1.2.
It will also replace your custom recovery with stock, if you have one.
WARNING: THIS PROGRAM IS ONLY GUARANTEED FOR XT925/926 DEVICES (Droid Razr/Razr
Maxx HD)!
USE AT YOUR OWN RISK, EVEN BETTER, IF YOUR PHONE IS NOT AN XT925/926, DO NOT USE
THIS PROGRAM AT ALL.
Presione una tecla para continuar . . .
This program will now install stock 4.1.2 firmware to your device.
Before launching the utility, put your phone into Fastboot mode!
Turn of the phone, then, hold the vol-up and vol-down buttons,
while holding the power button, until the boot menu comes up.
Scroll down to AP FASTBOOT, and select it.
Presione una tecla para continuar . . .
sending 'sbl1' (101 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.075s
sending 'sbl2' (126 KB)...
OKAY [ 0.017s]
writing 'sbl2'...
Invalid partition name sbl2
FAILED (remote failure)
finished. total time: 0.076s
sending 'sbl3' (512 KB)...
OKAY [ 0.047s]
writing 'sbl3'...
Invalid partition name sbl3
FAILED (remote failure)
finished. total time: 0.106s
sending 'rpm' (140 KB)...
OKAY [ 0.019s]
writing 'rpm'...
Invalid partition name rpm
FAILED (remote failure)
finished. total time: 0.078s
sending 'tz' (192 KB)...
OKAY [ 0.022s]
writing 'tz'...
Invalid partition name tz
FAILED (remote failure)
finished. total time: 0.080s
error: cannot load 'VZW_XT926_4.1.2/emmc_appboot.mbn'
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
When the screen bcomes back on, press any key to continue!
Presione una tecla para continuar . . .
sending 'partition' (32 KB)...
OKAY [ 0.010s]
writing 'partition'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.148s
sending 'sbl1' (101 KB)...
OKAY [ 0.019s]
writing 'sbl1'...
Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl2' (126 KB)...
OKAY [ 0.018s]
writing 'sbl2'...
Invalid partition name sbl2
FAILED (remote failure)
finished. total time: 0.076s
sending 'sbl3' (512 KB)...
OKAY [ 0.047s]
writing 'sbl3'...
Invalid partition name sbl3
FAILED (remote failure)
finished. total time: 0.105s
sending 'rpm' (140 KB)...
OKAY [ 0.019s]
writing 'rpm'...
Invalid partition name rpm
FAILED (remote failure)
finished. total time: 0.077s
sending 'tz' (192 KB)...
OKAY [ 0.023s]
writing 'tz'...
Invalid partition name tz
FAILED (remote failure)
finished. total time: 0.081s
error: cannot load 'VZW_XT926_4.1.2/emmc_appboot.mbn'
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.847s
sending 'system' (30720 KB)...
OKAY [ 2.351s]
writing 'system'...
Battery Low!!
FAILED (remote failure)
finished. total time: 2.495s
sending 'recovery' (10240 KB)...
OKAY [ 0.788s]
writing 'recovery'...
Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.847s
sending 'modem' (30720 KB)...
OKAY [ 2.352s]
writing 'modem'...
Unkown partition name modem
FAILED (remote failure)
finished. total time: 2.412s
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
Invalid partition name devtree
FAILED (remote failure)
finished. total time: 0.106s
sending 'logo' (1709 KB)...
OKAY [ 0.139s]
writing 'logo'...
Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.198s
sending 'cdrom' (30720 KB)...
OKAY [ 2.352s]
writing 'cdrom'...
Unkown partition name cdrom
FAILED (remote failure)
finished. total time: 2.411s
erasing 'modemst1'...
Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.054s
erasing 'modemst2'...
Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.054s
sending 'fsg' (2704 KB)...
OKAY [ 0.216s]
writing 'fsg'...
Invalid partition name fsg
FAILED (remote failure)
finished. total time: 0.274s
erasing 'cache'...
Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.054s
erasing 'tombstones'...
Invalid partition name tombstones
FAILED (remote failure)
finished. total time: 0.054s
After this point, the utility will erase userdata.
It is recommended you do this, but not required.
Would you like to erase userdata? (Y/N CASE SENSITIVE)Y
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.054s
error: cannot load 'VZW_XT926_4.1.2/NON-HLOS'
erasing 'modemst1'...
Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.054s
erasing 'modemst2'...
Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.054s
rebooting...
finished. total time: 0.006s
You are now on stock 4.1.2 for XT925/926 devices!
Pressing any key will return to the main menu.
Presione una tecla para continuar . . .

chuYxP said:
I can't charge with wall charger, my phone thinks that is a USB data cable and fastboot shows up... here is what the utility say:
snip...[/CODE]
Click to expand...
Click to collapse
What are the errors you get when flashing the stock firmware for your carrier?

[frustration free] restore to stock firmware moto g all versions

Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck

Reserved

reserved...:cyclops:

Mkdon said:
Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck
Click to expand...
Click to collapse
worked!!!!!!!!
you sir... are a legend!!!!!!!!!
thank you so much!!!!

flowerpoweruk said:
worked!!!!!!!!
you sir... are a legend!!!!!!!!!
thank you so much!!!!
Click to expand...
Click to collapse
I am glad it helped you. Enjoy the amazing device.

my phone german retail. can i use this tutorial?

sinkadorable said:
my phone german retail. can i use this tutorial?
Click to expand...
Click to collapse
I think so. Just give a shot. if it doesnt work then just replace the stock firmware from GB to DE. Alles Beste!

it gives me the same as the original method " < waiting for device > "
i have made a full swipe to the phone, cleaned the previous custom rom already, and a have cwm recovery.. dont know if this info is important
DONE!! i havent put the adb files in the firmware folder, but has flashed flawlessly now!! thank you for this solution!! :good:

Xin_TiGeR said:
it gives me the same as the original method " < waiting for device > "
i have made a full swipe to the phone, cleaned the previous custom rom already, and a have cwm recovery.. dont know if this info is important
Click to expand...
Click to collapse
What would you like to achieve? / is your Moto G stuck in loop after factory reset? Give a full background about the issue

Thank you.It works.Excellent.

Mkdon said:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
Click to expand...
Click to collapse
What is meant by this ? what exactly am I removing ? Do I need to rename it to the firmware I am about to flash?
Cheers.
EDIT: I figured it out, I just had a noob moment in my despair and couldn't take the information in, What a difference some nicotine and a cuppa makes!
Thanks OP great work.

Mkdon said:
Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck
Click to expand...
Click to collapse
help me guys
2 days back I was using my fone and it juz went off blank screen. tried many times with power button bt nothing. den went it to fastboot mode and tried recovery/normal powerup/factory but everytime got msg "failed to validate system image". followed d procedure given here http://forum.xda-developers.com/showthread.php?t=2700502 and got this result
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd..
C:\Windows>cd..
C:\>g:
G:\>cd moto g
G:\moto g>mfastboot.exe oem lock begin
...
(bootloader) Device is already locked!
OKAY [ 0.014s]
finished. total time: 0.016s
G:\moto g>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.001s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.396s
G:\moto g>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 5.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 11.343s
G:\moto g>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 5.059s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.084s
G:\moto g>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.554s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 11.077s
G:\moto g>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.532s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 11.061s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [ 19.204s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 33.653s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (237949 KB)...
OKAY [ 17.387s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 25.518s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (243326 KB)...
OKAY [ 18.015s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 34.875s
G:\moto g>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47476 KB)...
OKAY [ 7.540s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 12.576s
G:\moto g>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
G:\moto g>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
G:\moto g>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 5.056s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.090s
G:\moto g>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
G:\moto g>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.995s
G:\moto g>mfastboot.exe oem lock
...
(bootloader) Device is already locked!
OKAY [ 0.012s]
finished. total time: 0.015s
G:\moto g>pause
Press any key to continue . .
any solution guys

Don't you need to be unlocked to flash it?
Sent from my XT1032 using XDA Free mobile app

feartheanonymity said:
Don't you need to be unlocked to flash it?
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
does unlocking void the warranty?

yasir1234 said:
does unlocking void the warranty?
Click to expand...
Click to collapse
Yes, However you can flash to stock and just relock the bootloader and warranty is back intact.

26286998 5107
feartheanonymity said:
Yes, However you can flash to stock and just relock the bootloader and warranty is back intact.
Click to expand...
Click to collapse
how do I do dat?can u pls give me steps to do so..

well there are many threads explaining how to unlock bootloader, It basically consists of getting a code through adb, putting that code onto motorola website, getting the code and sending it to the phone. check the guides in the general section.
as for relocking it, is as simple as going into fastboot and typing (in adb / fastboot) fastboot oem lock.

Moto G Stuck in Boot Loop! Help
When I flash the stock firmware I keep getting these error messages
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
(bootloader) Failed to validate sparse image
and these all end with
FAILED (remote failure)
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.035s]
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...
OKAY [ 0.448s]
finished. total time: 0.486s
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.490s]
finished. total time: 1.603s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.361s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.915s
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.372s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.948s
target reported max download size of 536870912 bytes
sending 'system' (260606 KB)...
OKAY [ 8.415s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.950s
target reported max download size of 536870912 bytes
sending 'system' (239692 KB)...
OKAY [ 7.770s]
writing 'system'...
OKAY [ 9.293s]
finished. total time: 17.065s
target reported max download size of 536870912 bytes
sending 'system' (222205 KB)...
OKAY [ 7.165s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.684s
target reported max download size of 536870912 bytes
sending 'modem' (47484 KB)...
OKAY [ 1.583s]
writing 'modem'...
OKAY [ 1.304s]
finished. total time: 2.890s
erasing 'modemst1'...
OKAY [ 0.066s]
finished. total time: 0.067s
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.068s
target reported max download size of 536870912 bytes
sending 'fsg' (721 KB)...
OKAY [ 0.125s]
writing 'fsg'...
OKAY [ 0.104s]
finished. total time: 0.231s
erasing 'cache'...
OKAY [ 0.362s]
finished. total time: 0.364s
erasing 'userdata'...
OKAY [ 2.560s]
finished. total time: 2.562s
I have tried to flash many different firmwares on it to get it out of the boot loop like "US Retail" (4.3 and 4.4.2), "Boost US" (4.3 and 4.4.2), and "Verizon US" (4.3 and 4.4.2). This always results in one of the 3 error messages or more. I have found the one that works with the least error messages is the Boost US firmware for 4.4.2 and it gives only the error message (bootloader) Failed to validate sparse image on the 3rd system file. Whenever I try to install the firmware it doesn't seem to work, and it results in the phone turning on with the Motorola logo then the phone vibrates once then turns off and repeats, or the phone shows the android logo on its back with the exclamation point after the single vibration and sits like that until it turns off a few minutes later repeating the process. I have tried everything including trying to boot normally, resetting to factory, going into recovery and wiping cache and deleting all data, and even attempting to install from ADB. I have actually successfully done this process before a few hours before trying it on this one where it ended up like this. I looked this up and apparently you can still fix the phone if it can reach the boot loader screen, but when I was working with the phone I forgot to put it in developer mode and turn on USB debugging so that might be an issue. If there is a way I could fix it that would be very helpful, but if it doesn't I can still return the phone in the next 4 days.
Thanks for the help!
Extra Info:
The phone's bootloader is locked and because it is new I do not have any backups.
Also I already have these following programs
Minimal ADB and Fastboot
RSD Lite
DFS
Mfastboot v2
r1-motog-modifiedrecoveryroot.zip
adt-bundle-windows-x86_64-20140321.zip
platform-tools.zip
Fastboot+ADB(20926).zip
adbfix.zip
These are all from other threads that have explained this issue but the fix they provided did not work.
Thanks Again!

Guys, I have a Moto-G that was sold to me as a XT-1032 US global GSM model. The guy who sold it to me said that after the OTA update for 4.4.2 was applied to his phone it never would see a signal again, and kept saying to turn off airplane even though it saw that a sim was installed. looking at the status it kept saying the radio was turned off. When I got it from him it was showing the unlocked bootloader message, but when I checked the status on the fastboot screen it was showing locked status 2, which indicates it had never been unlocked. I unlocked the bootloader and started trying different versions of the firmware to see if I could fix the issue, but nothing ever worked until I tried this method.
I only flashed the radio from the GB 4.4.2 version that the OP had provided the XML file for using the modified xml file he provided, and now my cell radio is working again. Since I had already voided any warranty on it, I went ahead with flashing the CWM recovery and the latest nightly for CM11 and it's working beautifully, very smooth. I had bought this for my wife if I could fix it, so now she's getting a nice upgrade from her old GSM galaxy nexus that had started developing issues where it had to be rebooted to get the radio to work again (on the stock 4.3 firmware mind you, just a hardware problem I think due to it's age)
So in short Thanks OP!!

Mkdon said:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
Click to expand...
Click to collapse
Thanks for posting this since my phone is having these exact issues! I was a little unsure of what you meant in step 1 above, so what I did is take the sample XML which you attached to the post and replaced the software version info in the header with the version information for my carrier's firmware. Not sure if that was what I was supposed to do. Anyway, everything works great except that it is failing to flash motoboot.img. The command windows says it's a remote error- preflash validation failed, and the phone displays an error that says the version has been downgraded for tz. Any ideas would be greatly appreciated!

Help - device not booting

I was already on stock 4.4.2. Used RSD to flash it when the phone was on JB. My phone's suddenly not botting anymore though. Just stock on the boot animation screen. I tried flashing back the same firmware, but I get "Phone Returned Failed" error on RSD lite every time
What can I do? My phone was completely stock. Bootloader wasn't unlocked.
*edit*: Boot animation runs fine. Then it's just stuck at the orb thingy which just keeps going.

pyromaniac1 said:
I was already on stock 4.4.2. Used RSD to flash it when the phone was on JB. My phone's suddenly not botting anymore though. Just stock on the boot animation screen. I tried flashing back the same firmware, but I get "Phone Returned Failed" error on RSD lite every time
What can I do? My phone was completely stock. Bootloader wasn't unlocked.
*edit*: Boot animation runs fine. Then it's just stuck at the orb thingy which just keeps going.
Click to expand...
Click to collapse
Need more details on "fail." Just saying it failed won't narrow down anything.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
Need more details on "fail." Just saying it failed won't narrow down anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Tried flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml, get this error.

pyromaniac1 said:
Tried flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml, get this error.
Click to expand...
Click to collapse
you have to edit the xml file and completely remove the line containing "gpt" in that error. the partition table cant be changed/downgraded once upgraded.

bweN diorD said:
you have to edit the xml file and completely remove the line containing "gpt" in that error. the partition table cant be changed/downgraded once upgraded.
Click to expand...
Click to collapse
I did
still luck. Whatever item it tries to flash it returns the same error. I even deleted everything in between that to system.img. Gives the same error trying to flash system.img

pyromaniac1 said:
I did
still luck. Whatever item it tries to flash it returns the same error. I even deleted everything in between that to system.img. Gives the same error trying to flash system.img
Click to expand...
Click to collapse
try this, its not the same as the utility in the dev forum, its a modified version.

bweN diorD said:
try this, its not the same as the utility in the dev forum, its a modified version.
Click to expand...
Click to collapse
Flashed the XML with RSD lite. still the same error. Removed the GPT line and tried again. Same thing.

pyromaniac1 said:
Flashed the XML with RSD lite. still the same error. Removed the GPT line and tried again. Same thing.
Click to expand...
Click to collapse
Mmk, do not use rsd, use the bat file at the bottom of the directory. You defeated the purpose of it by using rsd.
Sent from my G2 running SlimKat

bweN diorD said:
Mmk, do not use rsd, use the bat file at the bottom of the directory. You defeated the purpose of it by using rsd.
Sent from my G2 running SlimKat
Click to expand...
Click to collapse
Ran the script twice. Managed to copy this the second time :/. Phone reboots after flashing is done and like before still stuck at the end of the boot animation.
[*] Press any key to continue.
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.328s
sending 'sbl1' (101 KB)...
OKAY [ 0.028s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.156s
sending 'sbl2' (126 KB)...
OKAY [ 0.029s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.155s
sending 'sbl3' (512 KB)...
OKAY [ 0.058s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.323s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.279s
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.286s
sending 'aboot' (256 KB)...
OKAY [ 0.038s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.292s
sending 'modem' (30720 KB)...
OKAY [ 2.262s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.385s
sending 'fsg' (165 KB)...
OKAY [ 0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.144s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.045s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.043s
sending 'logo' (854 KB)...
OKAY [ 0.081s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.200s
sending 'boot' (10240 KB)...
OKAY [ 0.751s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.468s
sending 'recovery' (10240 KB)...
OKAY [ 0.779s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.503s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
sending 'system' (30720 KB)...
OKAY [ 3.806s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 5.397s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.045s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.006s

pyromaniac1 said:
Ran the script twice. Managed to copy this the second time :/. Phone reboots after flashing is done and like before still stuck at the end of the boot animation.
Click to expand...
Click to collapse
hmm, not good!
it looks like the hole phone is r/o when in fastboot. i have seen this before several times and have yet to see any one fix it.
i thought a few of those may fail, although you weren't actually downgrading any of them, they shouldn't have, but every writing and erasing command has failed. i was hoping that didn't happen.
we didn't try a factory reset but that's pointless, as the script tried it and it failed.
i dont think there is a way to fix this. maybe @SamuriHL has an idea.
just so you know Sam, the "modified" script i gave him a few post down uses moto fastboot to flash everything.
figured that was the best shot, if there was one, given what he already tried.
thanks

Without having read everything cause I'm pressed for time, my gut instinct says this:
USB cable (make sure it's the oem cable that came with the phone...yes, it matters), USB port (usb 2.0 NOT 3.0), or USB driver issue.

SamuriHL said:
Without having read everything cause I'm pressed for time, my gut instinct says this:
USB cable (make sure it's the oem cable that came with the phone...yes, it matters), USB port (usb 2.0 NOT 3.0), or USB driver issue.
Click to expand...
Click to collapse
thanks!
i hope its something that simple. since the other instances were unlocked devices running custom recovery (with other mitigating factors), this seems rarely fixable as none of the other causes for a true r/o situation apply here.
im afraid to tell him to try a fdr in recovery, as i have seen quite a few cases go worse lately for no reason.
maybe a simple fix is what is needed.
thanks for your input either way.

I always try simple before moving on to the hard stuff. To me it feels like a communication issue with the phone but I don't know for sure. It's a guess. I'd start there at the very least.

SamuriHL said:
I always try simple before moving on to the hard stuff. To me it feels like a communication issue with the phone but I don't know for sure. It's a guess. I'd start there at the very least.
Click to expand...
Click to collapse
Well a factory reset was the first thing I tried anyway. So no luck there. I've tried it with the OEM cable on my laptop as well as a different cable on my PC. Not sure about the USB 3.0 or 2.0 though. I have a lenovo x230 laptop with 2 USB 3.0 ports so ill try again and see if using those ports with the OEM cable makes a difference.

You can not use a USB 3 port. It will fail.
Sent from my SM-P600 using Tapatalk

Nope. Tried it on my PC and laptop both on the usb 2.0 port with the oem cable. Still the same

pyromaniac1 said:
Nope. Tried it on my PC and laptop both on the usb 2.0 port with the oem cable. Still the same
Click to expand...
Click to collapse
I would go an uninstall all drivers, reboot, and then reinstall the drivers and then hook your phone up again to see if that helps. Could be either drivers are corrupted or something else is hosed up.
Since you've tried it on two different computers and it failed, I'm assuming you used the same drivers on both machines? What version of the drivers are you using?
You might want to go to the moto site and get the Motorola helper to bring down the drivers.

i assume you've tried both RSD Lite and motofastboot?

SamuriHL said:
i assume you've tried both RSD Lite and motofastboot?
Click to expand...
Click to collapse
he did, several times.
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
SamuriHL said:
i assume you've tried both RSD Lite and motofastboot?
Click to expand...
Click to collapse
results from mfastboot are in post 9.
failed writing and or erasing at every step. i made the script for him, he posted the results.
even if a couple would have failed as writing equal code, they all wouldn't have as it flashes each separately.

Yea, not a situation I've seen before. Almost like the partition table is screwed up somehow so it doesn't know the mount points to flash to. Just for fun, let's try something.
Boot her up in AP Fastboot mode, connect it to USB 2.0, then try this:
o) From a cmd prompt, type: fastboot oem fb_mode_clear
o) Then flash the FXZ again either with motofastboot or RSD.
I'm just curious.

[Q] Droid Razr HD XT926 won't boot, different flash errors.

I was given a droid razr hd (xt926). Guy said he took an update and when the phone rebooted, it wouldn't go past the M boot screen. I don't know what build he was on and I don't know the previous status of the phone (root, rom, unlock, etc)
I can access AP Fastboot but I can't access anything else (Recovery, BP Tools, Factory).
I am using a Team Black Hat Cable, the most recent Motorola_End_User_Driver_Installation_6.4.0_32bit Driver, and a Windows 7 computer (my best computer is at ASUS getting fixed).
AP Fastboot Reads:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 03:15:48)
eMMC Info: Size 16GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
usb connected
______________________________________________________________________________
I first tried RSD Lite (using both 6.1.4 and 6.2.4 to flash VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I got:
Code:
Failed flashing process. 1/17 flash partition "gpt.bin" -> phone return FAIL
Trying VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml I had to delete the "getvar" line for it to begin BUT I also get the "gpt.bin" failed message here. If I delete steps in XML (get.bin, sbl1, sbl2, sbl3, etc) the process just gets hung up and fails on the next step
______________________________________________________________________________
Trying the most recent Matt's Utility, Mr.Parkinson's Utility, and SamuriHL's House of Moto (trying each build listed above) I get significant failed messages which I will post below.
Code:
Ready to flash...
Press any key to continue . . .
Flashing: UNIVERSAL.bat
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl2' (127 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.250s
sending 'rpm' (140 KB)...
OKAY [ 0.031s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.218s
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.218s
sending 'modem' (30720 KB)...
OKAY [ 2.371s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.434s
sending 'fsg' (165 KB)...
OKAY [ 0.031s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.094s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
sending 'logo' (854 KB)...
OKAY [ 0.078s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.140s
sending 'boot' (10240 KB)...
OKAY [ 0.796s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.451s
______________________________________________________________________________
Trying to manually mfastboot in cmd, I get similar errors. I tried boot.img first and got this error
Code:
mfastboot.exe flash boot boot.img
sending 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED <remote failure>
finished. total time: 1.451s
Flashing gpt.bin partition
Code:
mfastboot flash partition gpt.bin
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.250s
Is the phone FUBAR or does anyone have a suggestion how I could fix this?

Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.

eckdawg5 said:
Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, just by looking at your screen shots, I can tell you it's hard bricked.
Sent from my VS985 4G

Only fastboot with unknown usb device (device descriptor request failed)

I got a Nexus 5 that won't boot. When you turn it on normally it hangs on the Google logo indefinitely. Recovery mode results in the red triangle logo. The only thing that 'works' is fastboot. But when I plug it into any of my PC's they all say: unknown usb device (device descriptor request failed) in the device manager.
I've tried installing various drivers, but it won't detect my phone in any way. As long as the descriptor isn't known by Windows it cannot install any driver. It will just resort back to the error message. Is there any way for Windows to recognize my device again?
I've tried various PC's and USB cables / ports. It's the device at fault not my other hardware for sure.

I plugged in my Galaxy S6, and it works just fine. Now the funny thing is when I plug back to Nexus 5 it is all the sudden recognized. I flashed the stock firmware back and it hang on the google logo again. Now going to fastboot the device is not recognized again. Recovery mode now also results in a Google logo that is stuck instead of the triangle.
After some retries I can connect in fastboot and the device is recognized as: "android bootloader interface"
Now how can I unbrick it? I am able to flash something to the device, i've tried the Restore_Nexus_5_KTU84P toolkit. It flashes but when it's done the phone reboots into the same brick mode.
When I manually try to flash an .img it says:
FAILED (command write failed (Unknown error))

The bootloader remains unlocked when the phone is rebooted? What OS is on the computer? Tried different USB ports and USB cables?

Tried with Ubuntu and I can flash stable now. But no matter what stock OS I flash (tried 6,5,4.4) after that flashing is done and the phone reboots it stuck on the google logo again. Any options beside throwing it in the bin?
And yeah, the bootloader stays unlocked.

Tried the unbrick method as shown here:
http://forum.xda-developers.com/goo...ck-nexus-5-stucked-qualcomm-hs-t3043301/page1
Flashes fine, also the memory tests pass. But it doesn't change the situation at all.

If when you try to lock or unlock the bootloader and after a reboot the locking or unlocking didn't take that usually means the emmc is bad.
Sent from my Nexus 9 using XDA-Developers mobile app

Are you flashing the userdata.img file too? The file should be flashed last. After flashong, immediately boot into recovery and perform a factory wipe, then reboot.

jd1639 said:
If when you try to lock or unlock the bootloader and after a reboot the locking or unlocking didn't take that usually means the emmc is bad.
Sent from my Nexus 9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Lock / unlock sticks just fine.
audit13 said:
Are you flashing the userdata.img file too? The file should be flashed last. After flashong, immediately boot into recovery and perform a factory wipe, then reboot.
Click to expand...
Click to collapse
I did indeed also manually flash all img files including the userdata.
Code:
sending 'bootloader' (2506 KB)...
OKAY [ 0.317s]
writing 'bootloader'...
OKAY [ 0.462s]
finished. total time: 0.779s
rebooting into bootloader...
OKAY [ 0.061s]
finished. total time: 0.162s
sending 'radio' (42033 KB)...
OKAY [ 2.006s]
writing 'radio'...
OKAY [ 2.892s]
finished. total time: 4.898s
rebooting into bootloader...
OKAY [ 0.077s]
finished. total time: 0.278s
erasing 'system'...
OKAY [ 1.125s]
sending 'system' (692940 KB)...
OKAY [ 31.024s]
writing 'system'...
OKAY [ 47.110s]
finished. total time: 79.259s
sending 'boot' (8620 KB)...
OKAY [ 0.615s]
writing 'boot'...
OKAY [ 0.743s]
finished. total time: 1.358s
sending 'recovery' (9202 KB)...
OKAY [ 0.644s]
writing 'recovery'...
OKAY [ 0.775s]
finished. total time: 1.418s
erasing 'cache'...
OKAY [ 0.531s]
sending 'cache' (13348 KB)...
OKAY [ 0.840s]
writing 'cache'...
OKAY [ 1.075s]
finished. total time: 2.446s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.911s]
finished. total time: 6.911s
erasing 'userdata'...
OKAY [ 6.697s]
sending 'userdata' (137318 KB)...
OKAY [ 6.441s]
writing 'userdata'...
OKAY [ 9.135s]
finished. total time: 22.273s
rebooting...
finished. total time: 0.274s
After flashing I cannot enter recovery, cause every mode except for fastboot results in a stuck Google logo.

aapje1299 said:
Lock / unlock sticks just fine.
I did indeed also manually flash all img files including the userdata.
After flashing I cannot enter recovery, cause every mode except for fastboot results in a stuck Google logo.
Click to expand...
Click to collapse
Let's try something. I'm going to have you try to boot into twrp recovery and if you can do a factory reset from that. At the bootloader you'll use the commands fastboot boot twrp.img. Where twrp.img file be the full file name of the twrp recovery image. If you don't know where to get twrp Google teamwin nexus 5. Download that to your pc. If it boots to twrp go to wipe and wipe the device. Then try rebooting to system.

So you can't enter recovery, even from fastboot mode?

I couldn't
Don't ask me how, but today I flashed it again to show my collegue that it wouldn't work. And after flashing it it came alive all the sudden. I'm a happy man! Everything seems to work except for the camera, but that is probably something else!
--
Hmm, disconnected and reconnected the charger, phone froze. Reboot and now it's stuck on the google logo again. I think this phone is toast
--
Another update
I removed the cover, and all the sudden it booted fine again. The battery was loose inside and there was some duct inside to keep it in place. This phone has been repaired before because the screen was broken. I think something is short circuiting in there. I got it booted now and first I'm going to give it a full charge.

I declared it dead, was able to actually get TeamWin recovery flashed and it worked. Then after some time it was dead again and unable to boot. Also the camera was broken. Thanks for thinking along guys!