Database Info

[FIX] Downgrading from 4.4.4 bricked your phone? Possible fix here

So I don't have a procedure to fix it but the guys at #android on Freenode gave me a bunch of tips which eventually made my phone work. It loaded a custom rom (liquid smooth) and I can make calls.
Sorry if I can't give you a more precise solution... if someone can figure out the exact reason why I was able to install a custom rom properly, it would help us find a solution to fix the GPT.BIN error.
In a nutshell, I was getting errors when trying to install a custom rom via TWRP (bypassing the stock rom errors) but now I'm able to install a custom rom and run it fine. Please read the logs despite all the crap around it.
Here is the chat log... follow though and do what I did - the solution might be in some fastboot commands I tried:
[08:31] <Jonnyw2k> what does "fastboot oem unlock" say
[08:31] <asdfsdfsadf> (bootloader) Device already unlocked! FAILED (remote failure) finished. total time: 0.003s
[08:39] <asdfsdfsadf> writing 'partition'... Preflash validation failed FAILED (remote failure)
[08:39] <asdfsdfsadf> mfastboot
[08:40] <asdfsdfsadf> not sure what the error is.....
[08:40] <Khaytsus> Well that just looks vulgar at a glance
[08:42] <Jonnyw2k> asdfsdfsadf there is a "fastboot oem fb_mode_clear" command that apparently sometimes helps, but that seems to be more todo with a fastboot issue
[08:42] <asdfsdfsadf> ... OKAY [ 0.002s] finished. total time: 0.003s
[08:43] <asdfsdfsadf> same error when I flash gpt.bin
[08:43] <DrChandra> Perhaps the partition is damaged.
[08:43] <Jonnyw2k> try flashing the gpt now
[08:43] <Aevum> what phone is it ?
[08:43] <asdfsdfsadf> moto g xt1032
[08:44] <DrChandra> Consider the erase and format commands within fastboot
[08:45] <Aevum> motorola havehttp://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <asdfsdfsadf> just did -w
[08:45] <Aevum> motorola havehttp://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <Aevum> fdoijghfiodjhadt
[08:45] <Aevum> try this http://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <asdfsdfsadf> formatting 'userdata' partition... Creating filesystem with parameters: Size: 6173884416 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 23551 Label: Blocks: 1507296 Block groups: 46 Reserved block group size: 367 Created filesystem with 11/376832 inodes and 50150/1507296 blocks sending 'userdata' (98165 KB)... writing 'userdata'... OKAY [ 9.953s] erasing 'cache'... OKAY [ 0.24
[08:46] <asdfsdfsadf> Aevum: tried that twice... to give you some insight, I upgraded to 4.4.4 GPE on a non-gpe device, many people got bricked when they tried to downgrade
[08:47] <asdfsdfsadf> After fastboot -w command, same error when trying to partition
[08:47] <Aevum> i dont know what flashing tools motorola uses, becuase theres usuayl the fastboot and ADB
[08:47] <Aevum> and also a proprietary tool from the manufacturer for bathc flashing
[08:48] <asdfsdfsadf> RSD Lite doesn't detect hte phone in fastboot
[08:49] <Aevum> theres usualy a fastboot and a flashing mode
[08:49] <DrChandra> RSD might be asking for a fastboot version and mismatching against whatever is being returned by the bootloader. It could e part of what Motorola uses to prevent anything but their own tool from being used.
[08:52] <Aevum> can you get ADB access ?
[08:52] <The0x539> y'know what
[08:52] <asdfsdfsadf> Aevum: yes ADB works
[08:52] <The0x539> I'll wait until I actually get it
[08:52] <DrChandra> I don't think he can boot, so he won't have adb
[08:53] <asdfsdfsadf> ADB works from stock and custom recovery
[08:53] <asdfsdfsadf> They both can get pushed files
[08:53] <asdfsdfsadf> But when it's time to install
[08:53] <asdfsdfsadf> they fail
[08:53] <DrChandra> asdf: So the main OS is what isn't booting?
[08:53] <asdfsdfsadf> Yes
[08:53] <asdfsdfsadf> But main os can't even get installed
[08:53] <DrChandra> Can you mount anything from recovery?
[08:53] <asdfsdfsadf> Anything I throw at it gives a partition error
[08:54] <asdfsdfsadf> Let me go to recovery and I'll give you the exact errors
[08:54] <Aevum> you are pre flashing the correct boot.img for every rom before, no ?
[08:54] <DrChandra> I wish fastboot could boot directly into recovery. I have to operate it from the screen to get there, or double boot.
[08:54] <asdfsdfsadf> Aevum: yes
[08:55] <Aevum> and the hboot versions coinside ?
[08:55] <DrChandra> Damaged flash memory
[08:55] <Jonnyw2k> you can "fastboot boot recovery.img"
[08:55] <asdfsdfsadf> Jonnyw2k: lfashes but nothing works after it finishes
[08:55] <Aevum> i would format the whole internal memory and start over with a stock image
[08:56] <DrChandra> Jonnyw2k: Yes, but you're not booting what's on the device, and transferring it takes forever.
[08:56] <Jonnyw2k> he's trying that its the partition table that is messed up but he cant flash a new one
[08:56] <asdfsdfsadf> >adb push Rom.zip /sdcard/
[08:56] <asdfsdfsadf> Let me transfer this
[08:56] <asdfsdfsadf> IT's a rom
[08:56] <asdfsdfsadf> And I'll give you the message in TWRP{
[08:56] <DrChandra> I use TWRP
[08:57] <asdfsdfsadf> TWRP works here... it just can't install ****
[08:57] <asdfsdfsadf> Let me get the message
[08:57] <asdfsdfsadf> 1 minute
[08:57] <Sloth514> how come i feel like this conversation should b in #android-root
[08:58] <DrChandra> Well, if the main OS partition (system) is messed up, you can't mount it, and/or you can't write it, so trying to get TWRP to install Rom.zip isn't going to work.
[08:58] <asdfsdfsadf> wow
[08:58] <asdfsdfsadf> mother****ers
[08:58] <asdfsdfsadf> rom booting :/
[08:58] <asdfsdfsadf> PC detecting phone during boot
[08:59] <DrChandra> ADB to main OS?
[08:59] <asdfsdfsadf> I adb'd liquidsmooth rom.zip
[08:59] <asdfsdfsadf> and ran it from TWRP
[08:59] <asdfsdfsadf> IT installed with no issue
[08:59] <asdfsdfsadf> Rebooted
[08:59] <DrChandra> Oh, ran it. YOu didn't install it.
[08:59] <asdfsdfsadf> Liquid smooth is now loading...
[09:00] <asdfsdfsadf> Still loading. I guess the first time is slow
[09:00] <Jonnyw2k> DrChandra he flashed the rom.zip from TWRP, and now is booting the rom
[09:00] <DrChandra> He didn't say he flashed it
[09:02] <DrChandra> asdfsdfsadf: Did you do an Install from TWRP, and select Rom.zip from the sdcard?
[09:02] <asdfsdfsadf> Yes DrChandra
[09:02] <asdfsdfsadf> After pushing it with ADB
[09:02] <DrChandra> OK, he flashed it
[09:02] <asdfsdfsadf> But I tried that before and got errors
[09:02] <asdfsdfsadf> Some command I typed in fastboot must have fixed it...
[09:03] <DrChandra> How is it that TWRP knows how to write the system partition and all the flash tools don't?
[09:03] <asdfsdfsadf> But right now the issue is that I'm stuck at the animated boot scren (never got this far)
[09:03] <asdfsdfsadf> normally it takes time, but not several minutes, right?
[09:03] <Jonnyw2k> you can try and reboot
[09:03] <Jonnyw2k> press and hold power till it turn off
[09:04] <Jonnyw2k> then turn it on again
[09:10] <DrChandra> Well, if the device is badly broken enough, even fastboot won't work.
[09:10] <Khaytsus> fastboot will _always_ work unless you somehow broke the bootloader
[09:10] <DrChandra> logcat is miles above that
[09:10] <asdfsdfsadf> fastboot works, it just won't flash gpt.bin... wait let me try that again now that liquidsmooth actually got flashed though TWRP
[09:10] <Khaytsus> logcat requires the system be at least in some normal condition, even if it's boot looping or something
[09:10] <Leeds> Khaytsus: it seems that - at least at one point - fastboot was working in the sense of responding, but not working because the partition table was so screwed that it couldn't read/write partitions
[09:11] <Khaytsus> Leeds: Heh. Interesting. I suppose if you break _partitions_, yeah....
[09:13] <Khaytsus> fastboot flash partition gpt.bin <-- looks like this is what you do
[09:13] <asdfsdfsadf> So: fastboot flash partition gpt.bin Gives me: writing 'partition'... (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.423s
[09:14] <asdfsdfsadf> Which is the original error
[09:14] <DrChandra> I've never seen fastboot write to "partition" before. It's always "system", "boot", "userdata", or "cache"
[09:15] <asdfsdfsadf> The only difference between now and then is that the rom actually boots but just stays stuck on the animation screen
[09:15] <Khaytsus> That error means unsigned or unrecognized img file
[09:15] <Khaytsus> You sure this file is valid?
[09:15] <asdfsdfsadf> Yes, tried 2 copies
[09:15] <asdfsdfsadf> Ok something just happened
[09:15] <asdfsdfsadf> Rom just loaded
[09:15] <asdfsdfsadf> I'm on the home screen
(Rebooted twice after it was stuck on loading screen)

Sorry for the long thread... Cleaning up the chat logs to make it more clear.

newklear85 said:
Sorry for the long thread... Cleaning up the chat logs to make it more clear.
Click to expand...
Click to collapse
don't get it xD

man, i have same problem on my xt1033 BR
i flash CM4.4.4
try flash restock 4.4.3
and it brinked..
long stuck on infinite bootload
or get multi FC on first boot
i read and try all method but no one work
i cant enter in any recovery..
twrp and cwm philz dnt work..
See:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovert i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
"i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report."

hansdepaula said:
man, i have same problem on my xt1033 BR
i flash CM4.4.4
try flash restock 4.4.3
and it brinked..
long stuck on infinite bootload
or get multi FC on first boot
i read and try all method but no one work
i cant enter in any recovery..
twrp and cwm philz dnt work..
See:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovert i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
"i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report."
Click to expand...
Click to collapse
I shortened the chat log. What are you getting when you do fastboot flash partition GPT.BIN from your stock rom?

gpt.bin for 4.4.3 stock dual sim + recovery twrp 2.6.3.3
Code:
C:\Users\Hans\Desktop\443>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.019s]
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.352s]
finished. total time: 0.373s
C:\Users\Hans\Desktop\443>mfastboot.exe flash recovery TWRP-2.6.3.3-falcon.img
target max-sparse-size: 256MB
sending 'recovery' (8678 KB)...
OKAY [ 0.302s]
writing 'recovery'...
OKAY [ 0.181s]
finished. total time: 0.485s
C:\Users\Hans\Desktop\443>
recovery give me a black screen and all touch return a vibration
i need press power for 10s to go away and try again
---------------------------------------------------------------------------
gpt.bin for 4.4.2 stock dual sim + recovery twrp 2.6.3.3
Code:
C:\Users\Hans\Desktop\442>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Users\Hans\Desktop\442>mfastboot.exe flash recovery TWRP-2.6.3.3-falcon.img
target max-sparse-size: 256MB
sending 'recovery' (8678 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.165s]
finished. total time: 0.479s
C:\Users\Hans\Desktop\442>
same
recovery give me a black screen and all touch return a vibration
i need press power for 10s to go away and try again
-------------------------------------------------------------------------
my fastboot dnt write nothing,
i think, sone thing have format partitions to RAW system
and i cant white or format then..
see more logs about my case: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
maybe you can help..
thx..

newklear85 said:
I shortened the chat log. What are you getting when you do fastboot flash partition GPT.BIN from your stock rom?
Click to expand...
Click to collapse
it works for me THANk YOU
the only thing is i don't have mobile network any fix???
p.s. i use paranoid ANdroid neweset version

Fresroqir said:
it works for me THANk YOU
the only thing is i don't have mobile network any fix???
p.s. i use paranoid ANdroid neweset version
Click to expand...
Click to collapse
Only thread in here that can potentially make it work... almost no attention lol
For the mobile network, flash the radio that came with stock.

man, you can upload to me a new gpt.bin and motoboot.img ..
4.4.4 maybe
i only have 4.4.3 and lower versions, and it dont work..
:/

[Q] Which Moto G stock firmware to use?

I'm looking to restore my Moto G to stock, but I don't know which version to choose.
Can anyone help me for which one I need because the one that I did flash, is the last one you see in the picture, and now my network (T-Mobile) isn't working anymore.
Also what is the difference between the AWSRetail.en.US and the Retail.en.US?

Model no. XT1032 is non-AWS. XT1034 is AWS. Only the later is compatible with T-Mobile’s 1700 (AWS) bands.

lost101 said:
Model no. XT1032 is non-AWS. XT1034 is AWS. Only the later is compatible with T-Mobile’s 1700 (AWS) bands.
Click to expand...
Click to collapse
Okay I really appreciate that info. Do you think you could by any chance help me fix the problem with my phone? It cant seem to connect to my carrier and the radio and gps is off. I really don't know how to fix this.. please help
And when I go into Settings>More...>Mobile Networks>Network Operators it tell says, "Error while searching for networks." And then when I try to press Choose Automatically, I get a message saying, " Your SIM card does not allow a connection to this network".
But that's not true because it has been working all this time.

Flash the AWSRetail.en.US stock firmware and everything should be fine again.

lost101 said:
Flash the AWSRetail.en.US stock firmware and everything should be fine again.
Click to expand...
Click to collapse
Are you sure? Because I actually have model no. XT1032
Also Im really sorry if I keep annoying you

Veyzo said:
Are you sure? Because I actually have model no. XT1032
Click to expand...
Click to collapse
How do you know this? All models state '1032' under About phone > Baseband version.
You have flashed the the retail XT1032 US stock firmware and radio is not working. That suggests a) have an XT1034 or b) you didn't flash correctly.

lost101 said:
How do you know this? All models state '1032' under About phone > Baseband version.
You have flashed the the retail XT1032 US stock firmware and radio is not working. That suggests a) have an XT1034 or b) you didn't flash correctly.
Click to expand...
Click to collapse
Yes I checked the Baseband version and it does say 1032. You might be right that it was flashed wrong, but Iv'e tried it about 3 times now it still isn't working.
Could you show me how to correctly flash it on a Mac? The guide I followed was the one here on xda-developers for the Moto G and I'm not sure what I could have done wrong, I really just need my network to work again.

Veyzo said:
Yes I checked the Baseband version and it does say 1032. You might be right that it was flashed wrong, but Iv'e tried it about 3 times now it still isn't working.
Could you show me how to correctly flash it on a Mac? The guide I followed was the one here on xda-developers for the Moto G and I'm not sure what I could have done wrong, I really just need my network to work again.
Click to expand...
Click to collapse
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Oh okay I understand. Well the way I know that it is XT1032 is because that is what it shows registered on my Google account. (check attached screenshot)

The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.

lost101 said:
The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.
Click to expand...
Click to collapse
Alright I will try doing that. Thanks for helping me

lost101 said:
The answer is simple. Follow the guide, flash XT1032 firmware. If that doesn't work, flash XT1034 firmware.
Click to expand...
Click to collapse
Okay so I flashed it, but the phone will not boot. It just stays stuck on the warning screen that tells you your bootloader is unlocked. And I was positive that I did flash it correctly because in the guide, it says that each command I enter in terminal should return with "OKAY" and they all did.
Here is my log in terminal with the commands I entered to flash the ROM (I bolded the commands and the OKAY'S) :
Last login: Thu Jul 17 17:17:15 on ttys000
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.027s]
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.359s]
finished. total time: 0.386s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.101s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.297s]
finished. total time: 1.398s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.091s]
writing 'logo'...
OKAY [ 0.137s]
finished. total time: 0.229s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.376s]
writing 'recovery'...
OKAY [ 1.004s]
finished. total time: 1.381s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (260693 KB)...
OKAY [ 8.202s]
writing 'system'...
OKAY [ 17.607s]
finished. total time: 25.809s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (261168 KB)...
OKAY [ 8.218s]
writing 'system'...
OKAY [ 15.416s]
finished. total time: 23.634s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (219321 KB)...
OKAY [ 6.915s]
writing 'system'...
OKAY [ 22.025s]
finished. total time: 28.940s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.527s]
writing 'modem'...
OKAY [ 2.279s]
finished. total time: 3.806s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.072s]
finished. total time: 0.072s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.071s]
finished. total time: 0.071s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (717 KB)...
OKAY [ 0.120s]
writing 'fsg'...
OKAY [ 5.355s]
finished. total time: 5.475s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase cache
erasing 'cache'...
OKAY [ 0.144s]
finished. total time: 0.144s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot erase userdata
erasing 'userdata'...
OKAY [ 2.202s]
finished. total time: 2.202s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$ ./fastboot reboot
rebooting...
finished. total time: 0.001s
Jais-MacBook-Pro:US_retail_XT1034_KXB21.14-L1.32_CFC_SVC.xml Jai$
So what am I doing wrong here? Is there anything else I can do?

You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img

All the fastboot commands in the correct order.
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
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​

alresave said:
You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img
Click to expand...
Click to collapse
Oh wow can't believe I missed that.. I'll try it again and see what happens

lost101 said:
As I said, Baseband version is not an indicator of which model you have.
Fastboot flash: Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Dude you are the best! That one worked like you said and my network is working again! I really do appreciate the help! ::good::good::good::

alresave said:
You did not flash boot.img
After recovery you should have
fastboot flash boot boot.img
Click to expand...
Click to collapse
OMG Thanks so much man, you noticing that just saved my phone!

Failed to erase partition...getting desperate here

Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.

Try using mfastboot:
https://www.androidfilehost.com/?fid=23578570567719065​
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata​
Is the phone definitely an XT1033 Dual-SIM?

lost101 said:
Try using mfastboot:
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata​
Is the phone definitely an XT1033 Dual-SIM?
Click to expand...
Click to collapse
Yes sir it was bought in Saudi (asia) and is dual sim. The box also states that it is xt1033.
I have tried what you have suggested but the error still remains.
C:\Users\...\Desktop\mfastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 14.955s
C:\Users\...\Desktop\mfastboot>mfastboot erase userdata[/U]
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.953s
If it is of any help, the screen says that it has 41.18 bootloader, I don't exactly know what this information is for.

Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​

lost101 said:
Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
Click to expand...
Click to collapse
I already tried sir along with the Brazilian firmware and both returned the same error. The same partition error,
I get stuck right at the first command "mfastboot flash partition gpt.bin", it says the the phone couldn't erase the partition. I'm starting to hate motorola right now
The money I saved just to buy this phone and I only got to use it for 1 month.
I understand that my partition is likely messed up or is corrupted even though I did nothing with my phone except upgrading it to lollilop (biggest mistake ever), what I don't understand is there aren't anyone else here in the forum who seem to have the same problem as mine, its like I am the only who has this kind of error so there are no threads at all discussing on how to solve this.

You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img​
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

lost101 said:
You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img​
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8480 KB)...
OKAY [ 5.306s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.424s

titan015 said:
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
Click to expand...
Click to collapse
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​

lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​
Click to expand...
Click to collapse
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"

Try another recovery.img just in case that one was a bad download.

titan015 said:
Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.
Click to expand...
Click to collapse
I have the same problem, do you managed to fix it?

kesy85 said:
I have the same problem, do you managed to fix it?
Click to expand...
Click to collapse
no. i've tried just about everything, didn't managed to fix it

hi
i have the same problem too bro, im from the philippines too..
have u fixed it yet?

no fix?
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.

Same for me, BUMP
hand_solo said:
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.
Click to expand...
Click to collapse
Anyone managed to fix this?

The best I've found...
hand_solo said:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
Click to expand...
Click to collapse
...is this:
Cant flash GPT / Motoboot:
Use another firmware, try for another android versions.
Fastboot Error: preflash validation failed
Try your original (or last flashed) firmware.
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076/
P.s.: I have the same problem.

titan015 said:
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"
Click to expand...
Click to collapse
lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​
Click to expand...
Click to collapse
For me the error is:
Code:
fastboot flash recovery twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
target reported max download size of 536870912 bytes
[COLOR="SeaGreen"]sending 'recovery' (9372 KB)...
OKAY [ 0.377s]
[/COLOR]writing 'recovery'...
[COLOR="Red"][B](bootloader) Permission denied
FAILED (remote failure)[/B][/COLOR]
finished. total time: 0.408s
Same thing when I try to boot instead of Flashing
Code:
fastboot boot twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
[COLOR="SeaGreen"]downloading 'boot.img'...
OKAY [ 0.347s][/COLOR]
booting...
[B][COLOR="Red"]FAILED (remote failure)
[/COLOR][/B]finished. total time: 0.354s

An unlocked Bootloader is required to flash (or boot) a custom recovery.

lost101 said:
An unlocked Bootloader is required to flash (or boot) a custom recovery.
Click to expand...
Click to collapse
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.

Der_K said:
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.
Click to expand...
Click to collapse
Please try to explain more clearly. Don't use the term ROM, if you are talking about a factory firmware image - in other words - sparsechunk files.
Can you flash the stock recovery img included in the factory firmware image?

flashing B532 fails

Hey all,
I flashed B316 to my H60-L02 and removed root,
Then i extracted B532's images (Boot, Cust, Recovery, System)
All sucessfully flashed except Boot.img
the error i get after flashing boot.img under fastboot
target reported max download size of 471859200 bytes
sending 'boot' (10272 KB)...
OKAY [ 1.078s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.106s
Click to expand...
Click to collapse
I have flashed boot.img from multiple versions many times on my H60-L02 without ever seeing this problem. so i can only assume theres something wrong with B532's boot.img, i have tried extracting it again and same problem

I do not know because I updated 5.1.1 by flash back to the developing version 5.8.5(Kitkat) and then use offical update to 5.9.16(Lollipop). Finally I flash B532(An Modified version based on EMUI B532).
You can try to download some tools which can help you to flash the offical recovery to your Honor6!

motoboot unknown partition

I am trying to upgrade my bootloader (XT1039) in order to install CM13, but when do, I get the following:
> fastboot flash motoboot motoboot_411A.zip
target reported max download size of 536870912 bytes
sending 'motoboot' (962 KB)...
OKAY [ 0.193s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.218s
My current bootloader is 4113

Be very careful as you have almost destroyed your phone. It's best to use this utility:
http://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793​

lost101 is absolutely correct. Are you trying to flash the stock 5.1 firmware for your specific device? I am guessing no seeing as how your motoboit IMG is in a .zilp format.

lost101 said:
Be very careful as you have almost destroyed your phone. It's best to use this utility:
http://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793​
Click to expand...
Click to collapse
Sadly I dont have access to a windows pc

n0ts0smart said:
lost101 is absolutely correct. Are you trying to flash the stock 5.1 firmware for your specific device? I am guessing no seeing as how your motoboit IMG is in a .zilp format.
Click to expand...
Click to collapse
Wow, you are completelly correct, I didnt even realise... unzipped and there was a .img file inside though it seems it is for the x1032?
What is the best place to download the correct bootloader?

Download the latest XT1039 5.1 Factory Firmware Image. You will find the bootloader file inside: motoboot.img
Fastboot command:
fastboot flash motoboot motoboot.img​
Factory Firmware Image index: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795