Hi I found a fix for the moto g after the 4.4.4 gpe update.
THIS IS THE FIX
I AM NOT RESPONSIBLE FOR ANY BRICKS!!!!!
but it has been tested several times and it worked allways.
This is my experience how I resolved my brick.
1)I downloaded my 4.4.2 firmware from EU. I live in europe
2)Then I downloaded the Indian 4.4.4 update from this threat and extracted it. or you can download the gpt.zip file, extract it and place it in your firmware folder.
3)replace gpt.bin file in your firmware xml folder by the one of the 4.4.4 indian firmware.
then open your cmd from the extracted folder of your stock firmware and type following commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Probably the motoboot flash will fail but that is nothing to worry about.
gpt.bin file
this is the gpt.bin file you need to flash to restore stock moto g rom
Could i use this for xt1033? Cause u take the gpt of xt1033 in indian
Sent from my GT-N7105 using Tapatalk
What firmware did you download?
Sent from my Moto G using XDA Premium 4 mobile app
answer
windylawyer.1712 said:
Could i use this for xt1033? Cause u take the gpt of xt1033 in indian
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
I think so
answer
Clarkiieh said:
What firmware did you download?
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the european and US 4.4.2,both worked
Why this useful topic is not popular ==
Sent from my GT-N7105 using Tapatalk
windylawyer.1712 said:
Why this useful topic is not popular ==
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
No idea, I solved the problem for me, those who want to profit from it can use it, pitty for those who dont
Great!
Nice simple solution - can't believe that there are so much threads outside don't knowing what to do :laugh:
I've tried flashing that GPT image, but I'm getting this:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 5.036s]
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.395s
ok
Konpon96 said:
I've tried flashing that GPT image, but I'm getting this:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 5.036s]
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.395s
Click to expand...
Click to collapse
Download the 4.4.4 indian firmware, extract it and use that gpt.bin file
gpt
Saphire007 said:
Download the 4.4.4 indian firmware, extract it and use that gpt.bin file
Click to expand...
Click to collapse
unzip this file and try again. BUT ONLY WITH STOCK FIRMWARE, NO GPE EDITION
Saphire007 said:
Download the 4.4.4 indian firmware, extract it and use that gpt.bin file
Click to expand...
Click to collapse
I used gpt.bin that you attached to second post. Isn't it the one from 4.4.4 firmware? If it isn't, where I can get firmware package with Indian stock? The site I usually use to download Moto firmware (http://sbf.droid-developers.org/phone.php?device=14) doesn't have any package for India.
EDIT: I've tried many stocks (no GPE) - EU Retail 4.4.2, GB Retail 4.4.2, US Retail 4.4.3, but it doesn't accept GPT with "Failed to write primary GPT.". Trying to flash motoboot ends with:
Code:
(bootloader) Failed to erase partition
(bootloader) Need a valid, signed GPT
FAILED (remote failure)
finished. total time: 5.024s
Going further with flashing shows this for every partition (modem, boot, recovery etc):
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition <partition>
FAILED (remote failure)
link
Konpon96 said:
I used gpt.bin that you attached to second post. Isn't it the one from 4.4.4 firmware? If it isn't, where I can get firmware package with Indian stock? The site I usually use to download Moto firmware (http://sbf.droid-developers.org/phone.php?device=14) doesn't have any package for India.
Click to expand...
Click to collapse
I can't post link yet, I need 10 posts. But I will give you the name
> Moto G > Moto G General > 4.4.4 update [OTA file] Indian Dual Sim XT1033 || Installation procedure
Saphire007 said:
I can't post link yet, I need 10 posts. But I will give you the name
> Moto G > Moto G General > 4.4.4 update [OTA file] Indian Dual Sim XT1033 || Installation procedure
Click to expand...
Click to collapse
Ok, thanks, I'll try it.
EDIT: Still nothing, "Failed to write primary GPT" is displayed everytime I try to flash gpt.bin.
No good solution for this problem is available yet
I have tried to solve this problem from last 5 days, but didn't got solution. The only solution available now is RIFF box, JTAG fix, but it is highly technical and requires RIFF box (cost around Rs; 5000) , so the best option to solve this problem is to give your moto g/x/e to service center... They will either change the motherboard or eMMC storage card, or JTAX fix...
Keep goggling for solution... because until unless we are not getting 4.4.4 singleimage and programmer file for particular handset we cant blankflash the device to restore bootloader and partition..
Hit Thanks, if I have saved your time
.
vikaskrdhiraj said:
I have tried to solve this problem from last 5 days, but didn't got solution. The only solution available now is RIFF box, JTAG fix, but it is highly technical and requires RIFF box (cost around Rs; 5000) , so the best option to solve this problem is to give your moto g/x/e to service center... They will either change the motherboard or eMMC storage card, or JTAX fix...
Keep goggling for solution... because until unless we are not getting 4.4.4 singleimage and programmer file for particular handset we cant blankflash the device to restore bootloader and partition..
Hit Thanks, if I have saved your time
Click to expand...
Click to collapse
If you want to hand in your device, go ahead. But not everyone is giving up zo fast that they wil hand in their phone so easily as you should do. This method can work for a lot of devices who are bricked from the GPE 4.4.4 update.
Hit your thans button? hmm, i wonder why it is still on 0.
Saphire007 said:
If you want to hand in your device, go ahead. But not everyone is giving up zo fast that they wil hand in their phone so easily as you should do. This method can work for a lot of devices who are bricked from the GPE 4.4.4 update.
Hit your thans button? hmm, i wonder why it is still on 0.
Click to expand...
Click to collapse
Hope it can fix, but I have given my handset to service center, from last 2 days they are unable to identify the problem, because handset is in full dead condition, but logic board is right, I can't say them that i have corrupted the bootloader due to warranty problem. Till now they didn't find that warranty is void.
Its better that you also try to take your handset to service center they will do eMMC repair or change the entire motherboard.
vikaskrdhiraj said:
Hope it can fix, but I have given my handset to service center, from last 2 days they are unable to identify the problem, because handset is in full dead condition, but logic board is right, I can't say them that i have corrupted the bootloader due to warranty problem. Till now they didn't find that warranty is void.
Its better that you also try to take your handset to service center they will do eMMC repair or change the entire motherboard.
Click to expand...
Click to collapse
Why should I, it is fully fixed, no problems at all with my fix
Thank you so much...I tryed 30+ methods and then solve it with this simple solution....
Just one question... Will this affect performance of the phone in any way??...beacuse we are now running stock 4.4.2 on partition table of gpe 4.4.4 ...
Just curious ....
I have a cricket xt1045, and after attempting to flash the US retail version of the 5.1 firmware onto the phone, I'm unable to get out of fastboot mode, and can't successfully reflash any firmware, even the cricket branded one. I get a "preflash validation failed" error:
C:\...>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.388s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.825s
my cid is one I can't seem to find any firmwares for, 0x0010 . Do CIDs need to match in order to flash at all? if so, is anyone aware of any cid 10 firmwares out there I could flash? The cricket one i was able to find is cid16.
The error I get when attempting to boot is "failed to validate system image".
Any help anyone might have would be greatly appreciated, or if I could provide any more information that would help anyone help me, please let me know. Thanks.
Did you ever figure out a solution? I'm in the same boat as you. Sorry for the gravedig.
No, I sold the phone as is on eBay and got a Moto X. Look through my old posts, I was talking in a different thread with another guy that had the same problem, might be something helpful there. Good luck.
Lol Same exact problem. There's a graveyard of these damn Cricket XT1045's and cheapskates that want more than they offer. Lol
Hello!
I tried to make a downgrade of my XT1039 from Lolipop to Kit Kat.
My XT1039 bootloader is unlock (I have status3 in the fastboot menu) but when I try to flash the kit kat stock rom I see this:
writing 'partition' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.352s
I am not an expert but I think that from this point the rest of commands are not applied. After finishing the flash I reboot the device and it get's stuck in the bootanimation.
I don't know what to do. I red that is not possible to recover if the device was already updated to Lolipop but I am not sure. Should I try a Cyanogen firmware?
Any advice please?
Thanks you so much
This is a dangerous way to downgrade to KitKat. People have dead phones by flashing an older Bootloader.
You can safely flash one of these Stock KitKat ROMs: http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-kitkat-rom-t3160127
If you choose an Untouched ROM - Do not accept OTA Updates. Such updates are disabled in the Optimized ROMs.
OK, thak you very much.
I have a bricked moto g turbo which is locked so i cant flash firmware files i tried getting bootloader unlock code but a error shows up to tick allow bootloader unlock in developer options but i can't turn on my phone so I cant enable that option. please help
You don't need to be unlocked to flash factory firmware. Just go to http://forum.xda-developers.com/showthread.php?t=3169639 and get the correct firmware and follow the instructions in http://forum.xda-developers.com/showthread.php?t=3187750 and flash your device.
Bootloader unlock is only needed for downgrading, root, and flashing custom ROMs and recovery. It is not needed to flash a full factory image that is the same or newer.
And for the record, if OEM Unlocking is not enabled, the bootloader cannot be unlocked.
fastboot flash partition gpt.bin
sending 'partition' (32 KB)... OKAY
writing 'partition'... (bootloader) Preflash validation failed
FAIL
FAILED (remote failure)
Execution time is 1(s)
getting error
Hi i have the same error. But my problem is with the módem. I cant take signal. I try flash the original rom and don't work
Do you have the log file?
Hi. I got a Moto Maxx with Android Marshmallow (Telcel carrier).
After trying several roms, I decided to go back to stock, since I couldn't find a Marshmallow rom, I decided to update from 4.4. I installed "Mexico Retail Stock Kitkat /// RETLA_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-DEFAULT_CFC.xml.zip" from this thread. Everything went fine, although I lost the custom recovery during the process.
Then, from the software updater option on the phone, I updated to Lollipop. Unfortunately, it didn't updated. Instead, I got a bricked phone. It didn't turned on.
In order to recover it. I followed this guide. The phone turned on again, and now I am stuck on an "empty" bootloader. The upper half of the screen only shows "Start", similar to the picture from the guide.
But I can't flash any stock rom. It seems by doing the steps of that guide, I re-locked my phone. I can't unlock it because, while I know my unlock bootloader code, mfastboot tells me I must enable "Enable OEM Unlock" in the developer settings (which I can't reach).
Trying to flash any stock rom gives me the following errors:
Code:
[B]>mfastboot flash partition gpt.bin[/B]
[I]target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.104s[/I]
>[B]mfastboot flash bootloader bootloader.img[/B]
[I]target max-sparse-size: 256MB
sending 'bootloader' (2159 KB)...
OKAY [ 0.112s]
writing 'bootloader'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.202s[/I]
>[B]mfastboot flash radio radio.img[/B]
[I]target max-sparse-size: 256MB
sending 'radio' (85457 KB)...
OKAY [ 2.753s]
writing 'radio'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.802s[/I]
>[B]mfastboot.exe flash system system.img_sparsechunk.0[/B]
[I]target max-sparse-size: 256MB
sending 'system' (253363 KB)...
OKAY [ 8.205s]
writing 'system'...
[B](bootloader) Permission denied[/B]
FAILED (remote failure)
finished. total time: 8.226s[/I]
I can't access to recovery. Please, help me :crying::crying::crying:
Why do people relock their bootloader?
With an unlocked bootloader you can flash other region images, if necessary, like Brazil. With locked bootloader your need Mexico. Your may even need your carrier firmware.
ChazzMatt said:
Why do people relock their bootloader?
Click to expand...
Click to collapse
It wasn't my intention. The phone bricked, and in order to return to bootloader I followed that guide. It worked but it seems that during the process it locked the phone.
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
---------- Post added at 03:23 PM ---------- Previous post was at 03:14 PM ----------
See this thread, but you'll need your region firmware.
https://forum.xda-developers.com/showthread.php?t=3662683
ChazzMatt said:
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
Click to expand...
Click to collapse
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
jairjy said:
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
Click to expand...
Click to collapse
Because while you had downgraded to Kitkat, but you still had Marshmallow bootloader. You can't take OTA, because it will install bootloader and you cannot downgrade bootloader.
Have we discussed this before, because someone else did EXACTLY the same thing. Downgraded to Kitkat, then tried to take Lollipop OTA --which tries to install Lollipop bootloader!