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?

[Q] Moto G stuck at Bootloader unlocked screen

Hi all,
My moto g has a problem. It is stuck at the "warning bootloader unlocked screen"
I can boot into fastboot and flash stuff but when i try to boot it keeps displaying the "warning bootloader unlocked screen"
i have tryed several guides to flash orignal firmware but somehow it doesnt work.
Stange thing is is that i have CMW installed but when i flash TWRP or something it says its ok but then when i go to recovery CMW always comes back.

Had the same problem, white boot logo. Download from here http://forum.xda-developers.com/showthread.php?t=2646415 During the process it will say something about boot loader, but never mind. U should have a OTA update when it finished and will lose root, but its not a big problem
regards

bobrda said:
Had the same problem, white boot logo. Download from here http://forum.xda-developers.com/showthread.php?t=2646415 During the process it will say something about boot loader, but never mind. U should have a OTA update when it finished and will lose root, but its not a big problem
regards
Click to expand...
Click to collapse
Yeah i tryed that one but it doesnt work even the logo doesnt work.

Beukhof1 said:
Yeah i tryed that one but it doesnt work even the logo doesnt work.
Click to expand...
Click to collapse
Maybe to try this one? Its the GPE rom but it may fix the phone .. http://forum.xda-developers.com/showthread.php?t=2646404

bobrda said:
Maybe to try this one? Its the GPE rom but it may fix the phone .. http://forum.xda-developers.com/showthread.php?t=2646404
Click to expand...
Click to collapse
Same thing its says its all ok but when i boot i just keeps showing the logo.
Code:
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>SET fastboot=fastboot
.exe
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe getvar m
ax-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_set
... FAILED (remote failure)
finished. total time: 0.036s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash pa
rtition gpt.bin
sending 'partition' (32 KB)... OKAY [ 0.081s]
writing 'partition'... INFOThis may take a few seconds, if a
INFOdifferent partition table is being
INFOflashed since we need to backup
INFOand restore a few partitions
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.469s]
finished. total time: 0.550s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
toboot motoboot.img
sending 'motoboot' (1940 KB)... OKAY [ 0.205s]
writing 'motoboot'... INFOflashing tz ...
INFOflashing rpm ...
INFOflashing sdi ...
INFOflashing aboot ...
INFOflashing sbl1 ...
OKAY [ 1.380s]
finished. total time: 1.586s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
dem NON-HLOS.bin
sending 'modem' (47484 KB)... OKAY [ 4.088s]
writing 'modem'... OKAY [ 0.732s]
finished. total time: 4.820s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash fs
g fsg.mbn
sending 'fsg' (719 KB)... OKAY [ 0.109s]
writing 'fsg'... OKAY [ 0.032s]
finished. total time: 0.142s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst1
erasing 'modemst1'... OKAY [ 0.035s]
finished. total time: 0.035s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst2
erasing 'modemst2'... OKAY [ 0.046s]
finished. total time: 0.046s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash lo
go logo.bin
sending 'logo' (2563 KB)... OKAY [ 0.271s]
writing 'logo'... OKAY [ 0.085s]
finished. total time: 0.356s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash bo
ot boot.img
sending 'boot' (10240 KB)... OKAY [ 0.896s]
writing 'boot'... OKAY [ 0.731s]
finished. total time: 1.627s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash re
covery recovery.img
sending 'recovery' (10240 KB)... OKAY [ 0.897s]
writing 'recovery'... OKAY [ 0.729s]
finished. total time: 1.626s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk1
sending 'system' (248834 KB)... OKAY [ 21.396s]
writing 'system'... INFOInvalid signed image
OKAY [ 4.452s]
finished. total time: 25.848s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk2
sending 'system' (253442 KB)... OKAY [ 23.077s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 4.052s]
finished. total time: 27.131s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk3
sending 'system' (210534 KB)... OKAY [ 19.748s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 3.446s]
finished. total time: 23.195s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase ca
che
erasing 'cache'... OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase us
erdata
erasing 'userdata'... OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_clear
... OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>pause
Press any key to continue . . .

Beukhof1 said:
Same thing its says its all ok but when i boot i just keeps showing the logo.
Code:
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>SET fastboot=fastboot
.exe
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe getvar m
ax-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_set
... FAILED (remote failure)
finished. total time: 0.036s
Sorry I cant help you than. This two rooms work on my phone.. talking about xt 1032
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash pa
rtition gpt.bin
sending 'partition' (32 KB)... OKAY [ 0.081s]
writing 'partition'... INFOThis may take a few seconds, if a
INFOdifferent partition table is being
INFOflashed since we need to backup
INFOand restore a few partitions
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.469s]
finished. total time: 0.550s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
toboot motoboot.img
sending 'motoboot' (1940 KB)... OKAY [ 0.205s]
writing 'motoboot'... INFOflashing tz ...
INFOflashing rpm ...
INFOflashing sdi ...
INFOflashing aboot ...
INFOflashing sbl1 ...
OKAY [ 1.380s]
finished. total time: 1.586s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
dem NON-HLOS.bin
sending 'modem' (47484 KB)... OKAY [ 4.088s]
writing 'modem'... OKAY [ 0.732s]
finished. total time: 4.820s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash fs
g fsg.mbn
sending 'fsg' (719 KB)... OKAY [ 0.109s]
writing 'fsg'... OKAY [ 0.032s]
finished. total time: 0.142s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst1
erasing 'modemst1'... OKAY [ 0.035s]
finished. total time: 0.035s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst2
erasing 'modemst2'... OKAY [ 0.046s]
finished. total time: 0.046s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash lo
go logo.bin
sending 'logo' (2563 KB)... OKAY [ 0.271s]
writing 'logo'... OKAY [ 0.085s]
finished. total time: 0.356s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash bo
ot boot.img
sending 'boot' (10240 KB)... OKAY [ 0.896s]
writing 'boot'... OKAY [ 0.731s]
finished. total time: 1.627s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash re
covery recovery.img
sending 'recovery' (10240 KB)... OKAY [ 0.897s]
writing 'recovery'... OKAY [ 0.729s]
finished. total time: 1.626s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk1
sending 'system' (248834 KB)... OKAY [ 21.396s]
writing 'system'... INFOInvalid signed image
OKAY [ 4.452s]
finished. total time: 25.848s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk2
sending 'system' (253442 KB)... OKAY [ 23.077s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 4.052s]
finished. total time: 27.131s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk3
sending 'system' (210534 KB)... OKAY [ 19.748s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 3.446s]
finished. total time: 23.195s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase ca
che
erasing 'cache'... OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase us
erdata
erasing 'userdata'... OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_clear
... OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Sorry I cant help you. It works on my phone. model xt 1032

bobrda said:
Sorry I cant help you. It works on my phone. model xt 1032
Click to expand...
Click to collapse
I have the same model

Beukhof1 said:
I have the same model
Click to expand...
Click to collapse
Don't know whats couching you the problem. try to push rom via adb
or maybe this one http://forum.xda-developers.com/showthread.php?t=2542219
i had no success with this rom, but...
it's beyond my knowledge

bobrda said:
Don't know whats couching you the problem. try to push rom via adb
or maybe this one http://forum.xda-developers.com/showthread.php?t=2542219
i had no success with this rom, but...
it's beyond my knowledge
Click to expand...
Click to collapse
Every thing i flash even recovery doesnt seem to stick because when i fastboot twrp i still have my cmw.

Beukhof1 said:
Every thing i flash even recovery doesnt seem to stick because when i fastboot twrp i still have my cmw.
Click to expand...
Click to collapse
Few dayes ago i download Gb 4.4.2 rom and flash it with no mistakes thru the flash! It have no errors while flashing. After that had a update to 176.44.1
So my phone is for European market and with sparsechunk.0 sparsechunk.1 sparsechunk.2 have no errors. With 1.2.and 3sparsechunk i have errors, but i can but in the rom normally...
Then i use a mototool 3 and root my phone with twrp recovery...

Beukhof1 said:
Hi all,
My moto g has a problem. It is stuck at the "warning bootloader unlocked screen"
I can boot into fastboot and flash stuff but when i try to boot it keeps displaying the "warning bootloader unlocked screen"
i have tryed several guides to flash orignal firmware but somehow it doesnt work.
Stange thing is is that i have CMW installed but when i flash TWRP or something it says its ok but then when i go to recovery CMW always comes back.
Click to expand...
Click to collapse
Did you manage to get a fix for this? I have the exact same issue, did all the steps you mentioned and have not found a fix, did you hace any luck?

Iggyavendano said:
Did you manage to get a fix for this? I have the exact same issue, did all the steps you mentioned and have not found a fix, did you hace any luck?
Click to expand...
Click to collapse
Nope sorry man. Mine is stille dead. I think the flash memory is defectieve.

Beukhof1 said:
Nope sorry man. Mine is stille dead. I think the flash memory is defectieve.
Click to expand...
Click to collapse
I went back to my carrier rom and It worked... after a few flashes on lollipop I couldn't get it to work even on stock lollipop...
hope it helps.

Try with mfastboot-v2. You can find the link with a quick search. mfastboot may help with flashing larger system images than normal fastboot. Just give it a try.
And if you are on lollipop & trying to downgrade to kitkat, skip flashing motoboot.img & gpt.bin

legolas06 said:
Try with mfastboot-v2. You can find the link with a quick search. mfastboot may help with flashing larger system images than normal fastboot. Just give it a try.
And if you are on lollipop & trying to downgrade to kitkat, skip flashing motoboot.img & gpt.bin
Click to expand...
Click to collapse
I had the same problem, and tried everithing said here, the only thing that worked, was mfastboot - v2, thank a lot for the sugestion.

Device not seen
I'm having the same problem – stuck on "Warning Booloader Unlocked" screen. Can't get to the bootloader screen. 'adb devices' and 'mfastboot devices' both show empty device lists, which means that I can't execute any adb or mfastboot commands...
Moto G XT1032 (Gen 1, 2013), attempted to install 5.1 firmware using steps at www . droidviews . com/restore-moto-g-to-stock-and-downgrade-firmware (sorry, not allowed to add live link). Bootloader unlocked, USB drivers installed, USB debugging enabled. All mfastboot steps executed without error, but I missed sparsechunk.0 – duh. Finished with a 'mfastboot reboot', and ever since, can't get past the bootloader warning, and no device seen by adb or mfastboot... Can't imagine it's a connectivity or PC driver issue, as was working fine minutes ago before the reboot.
All the solutions I've found depend on adb or mfastboot being able to see my device. Any tips to get the device seen again?
Thanks!

aussiejim said:
I'm having the same problem – stuck on "Warning Booloader Unlocked" screen. Can't get to the bootloader screen. 'adb devices' and 'mfastboot devices' both show empty device lists, which means that I can't execute any adb or mfastboot commands...
Moto G XT1032 (Gen 1, 2013), attempted to install 5.1 firmware using steps at www . droidviews . com/restore-moto-g-to-stock-and-downgrade-firmware (sorry, not allowed to add live link). Bootloader unlocked, USB drivers installed, USB debugging enabled. All mfastboot steps executed without error, but I missed sparsechunk.0 – duh. Finished with a 'mfastboot reboot', and ever since, can't get past the bootloader warning, and no device seen by adb or mfastboot... Can't imagine it's a connectivity or PC driver issue, as was working fine minutes ago before the reboot.
All the solutions I've found depend on adb or mfastboot being able to see my device. Any tips to get the device seen again?
Thanks!
Click to expand...
Click to collapse
Problem solved – eventually got into bootloader screen on phone, after at least 20 tries... If you have same problem, keep on trying.

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.

nexus 5 (LG-D820) stuck in CWM recovery

hello,
i've got this lg-D820 stuck in CWM Recovery v6.0.4.5 screen
i want to flash it back to recovery and downloaded 5.1.1 factory image from google developers site
but i always get error while flashing bootloader,something like this-
Code:
sending 'bootloader' (3119 KB)...
OKAY [ 0.334s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.583s
rebooting into bootloader...
OKAY [ 0.076s]
finished. total time: 0.080s
< waiting for device >
i need help to fix this set

now my device(mi a2 lite) is stuck in a boot loop and the device is locked after android 10 update

using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!

FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.