Database Info

[Q] Fastboot blues on the Moto X: is this the end?

Phone: Moto X / KitKat 4.4
Carrier: AT&T (XT1058)
Problem: Mysteriously stopped booting.
Good News: Fastboot is recognized.
Bad News: (bootloader) Flash write failure
Taking this guide as my playbook - http://forum.xda-developers.com/moto-x/moto-x-qa/kitkat-update-crashed-moto-x-t2535150 I tried to flash on a stock OS. Here's the main spot from the thread I'm working from-
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
The mission objective is simple: retrieve files off of sdcard and factory reset.
So with my mfastboot (not the android one), I'm trying to flash my stock OS back on so I can get a drive in windows and retrieve sdcard files. Actually, ANY OS back on at this stage of the game will be nice.
Things I have NOT done:
1. rooted the phone, or
2. unlocked the boot loader
If doing these will help, let me know.
So I get my download from sbf.droid-developers.org for 4.4.2 & ATT carrier and unpack the files.
flashing for 'partition' in gpt.bin actually works (yay), but I get the above error ("Flash write failure") for system.img and recovery.img
uh-oh
It seems others with this problem changed cables and USB ports, so I tried that. No dice.
Someone said something about permissions, so I started my command window with administrator privileges, also no luck.
Unless, of course, they meant permissions on the phone side of things? Would that actually help?
So at this juncture if my SDCard died I can go for warranty because I never did any unlocking.
However, if the SDCard can be saved, I am willing to void the warranty and unlock. The data on it is valueable to me and yes a lesson I learned here is I should start using dropbox or equivalent service. Noted.
Should I unlock the phone and try mfastboot flash system system.img, or am I already dead?

Factory reset doesn't even work, I get "no valid piv block in sp for system"
I just ran mfastboot erase cache and at the command prompt I get:
(bootloader) Failed to erase partition
FAILED: Remote failure
The phone screen says, 'Failed to erase partition cache'
This doesn't sound good.... Is there anyway can get this thing booted?

Ah, nevermind, it just keeps getting errors flashing everything. Something with the phone itself is seriously wrong.
I've decided to return it. I think my data is lost.

[Help] Moto G 4G peregrine issues

Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.

Ferguson35000 said:
Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Click to expand...
Click to collapse
I'm stil stuck.
Is there anybody able to help me ?
Thank you.

Ferguson35000 said:
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Click to expand...
Click to collapse
I got this problem when installing CWM too. I believed the problem is in this line:
fastboot flash recovery CWM-6.0.5.0-peregrine.img
Click to expand...
Click to collapse
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710

UncolourTV said:
I got this problem when installing CWM too. I believed the problem is in this line:
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
Click to expand...
Click to collapse
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.

Ferguson35000 said:
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Click to expand...
Click to collapse
I have the same issue with this program under linux or windows, it doesn't recognize my device. I have activated USB debug, tried under bootloader or with the phone normally started but nothing better.
only fastboot boot recovery.img works.

You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues

hacktrix2006 said:
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
Click to expand...
Click to collapse
Thank you for answering.
I will try this then come back.

Ferguson35000 said:
Thank you for answering.
I will try this then come back.
Click to expand...
Click to collapse
Same error :
I still have the mismatch thing with mfastboot ...

Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.

hacktrix2006 said:
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
Click to expand...
Click to collapse
Hello, I have bought the phone less than one month ago.
It was directly on 4.4.4 after unpacking.
Have you tried renaming the CWM file? Maybe the "-" are a problem although I highly doubt it. Did you try re downloading the file? Running the command window as an administrator? Last resort, you could use TWRP, I'm running on this currently and haven't had any problems installing/flashing ROMs with it and imo prefer it over CWM.
Click to expand...
Click to collapse
I have tried both and they both have the same problem :/ CWM as well as TWRP...
Still no idea what happens.

same problem
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on

kosamuky said:
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
Click to expand...
Click to collapse
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you

Back to stock
Ferguson35000 said:
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Click to expand...
Click to collapse
Yes its normal if you have unlocked your bootloader
To get back to stock, download a stock Fw for your device model and region, you can find a link for one if you enter the moto g section of this site and head to moto 4g lte android development section (only section specifically for peregrine model) unpack the fw files into your fastboot directory (windows) reboot your phone to fastboot mode (where u saw the status code) then press control + shift + right click to launch a command prompt window here (from within fastboot directory in windows) then copy and paste these fastboot commands 1 by 1 pressing enter each time until compete.
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_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot

So you mean, it is compulsory to have stock ROM in order to install the recovery ?
Because my problem is not to return to stock, it is to install a proper recovery (CWM or TWRP) in order to boot on it without my computer.
Thanks for your help

No but I think your problem is you have corrupt the recovery partition size maybe through bad flash or something so ur unable now to flash a recovery as the partition size is for different device or damaged and flashing cwm will no longer work as the cwm image is too big or too small for the allocation assigned to it as the devices core partition table has changed (can happen when u flash something for the falcon when you have a peregrine), I would flash back to stock via that method to restore to stock partition sizes and then reroot and flash cwm again after, just a guess from my own understanding.
Sent from my XT1039 using XDA Free mobile app

Guys I had the same trouble installing the recovery with the mismatched partition size message. This message is normal and the recovery is already installed on your device. The problem i had when selecting the recovery with the following black screen was that I used the Power Button instead of the up Button.
5) using volume down scroll to recovery and then use volume up to select

OnePlus one stuck at boot screen, please help!

FIxed with this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
My 64gb OnePlus One does not boot anymore.
I wiped system, data, cache, and dalvik and then flashed the 9/20 cm nightly, gapps, and supersu. The device rebooted and I saw the CM loading circle. However, next time I looked at the device, it was back at the Oneplus boot screen. After this, I have never been able to get it past this screen.
I have tried flashing the stock image using this guide (steps 1-3), as well as downloading the fastboot image from cnygn.com and flashing each img from fastboot using these commands:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Additionally I have tried flashing CM11 from TWRP, which still results in the same problem. I am able to access and use fastboot and twrp just fine.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
EDIT: I managed to install ColorOS with this guide, and it boots fine. However, I need CM with Google Play so after trying to get cm11s 33r with this guide, I'm back at square one with the phone not getting past the boot screen. Any ideas?

Hi so i guess you don't have a backup in the device,sometimes the easiest way to fix things is the right way just download this tool the one for your device 16/32gb the second version(v.2) put your phone in fastboot mode and hit cm update in the tool.
---------- Post added at 06:29 AM ---------- Previous post was at 06:26 AM ----------
http://www.youtube.com/watch?app=desktop&persist_app=1&v=5O2e_R_TbVg

android.345 said:
My 64gb OnePlus One does not boot anymore.
Click to expand...
Click to collapse
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
You should just need to do everything that's in the guide you linked, except the 4th step (you don't need to lock the bootloader). Flash the factory images and just reboot (don't flash/wipe/whatever anything else), it should be fine. Make sure you're flashing the right ones though, for example, since you have the 64GB version, you have to flash the userdata image for the 64GB OPO.
I don't think you should look for "1-click" toolkits, they can be more harmful than good since you don't know what you're actually doing.

bradipovsky said:
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
Click to expand...
Click to collapse
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'

android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...

bradipovsky said:
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
Click to expand...
Click to collapse
Do take a look at the update I have posted regarding ColorOS. Flashing a new rom from TWRP does not help. All fastboot commands work.
Also, I have been flashing userdata_64g.img

android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Same problem for me too. Device worked for a week with SOD-s that 2 days ago just rebooted and stay in the loop of logo 1+.. ??

bricked my moto g while downgrading lollipop to kitkat / corrupted data partition?

i was using moto g xt1033 asian retail, i changed it to 4.4.4 brazilian retail and then updated to lollipop 5.0 brazilian following a thread on xda. all worked well. i came across a thread which had an ota update for 5.0 to 5.0.1 it was a 10mb file. i put it in pendrive and flashed it via twrp. since then the phone never went past the warning bootloader unlocked page.
when i power it off, it automatically reopens but gets stuck on the warning bootloader unlocked page.
usb debugging is enabled, i can access bootloader, can use fastboot commands, it recognizes adb commands and can flash recoveries on it.
the only thing that doesnt work is that it doesnt get past the warning page.
so i went to twrp, cleared all- dalvick cache, data, internal storage, cache and system.
it gives wipe complete, FAILED
see image 1.
so i flashed the original 4.4.4 rom and it again gives the same errors and now i get waves on twrp, but still doesnt go past the warning bootloader unlocked screen.
updating partition details-
E : unable to mount '/data'
E : unable to mount '/cache'
E : unable to mount internal storage
see image 2.
basically, every time i try to wipe it or install a new rom it gives problems about partition.
so i wiped it again and installed cm11 snapshot on it.
again the same unmounting problems, but now it goes past the warning bootloader screen but always stays on the arrow rotating about the cm logo.
i searched a lot online , and i think the problem is corrupted partition.
so i followed this thread http://forum.xda-developers.com/showthread.php?t=2683787 .
first he shows a way by using terminal command from trwp . when i goto command terminal, it shows browse to starting folder i chose any folder like sdcard and enter this code
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
. it gives this
see image 3 and image 4.
i try the next alternative that is using adb and this code
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
and it gives this
see image 5.
please help me to clear this partiton problem. thank you in advance :')

I suggest you be very careful about what you do next.
It sounds like you should fastboot flash the Lollipop gpt.bin (partition table) - I believe the KitKat gpt.bin will cause you serious problems.

lost101 said:
I suggest you be very careful about what you do next.
It sounds like you should fastboot flash the Lollipop gpt.bin (partition table) - I believe the KitKat gpt.bin will cause you serious problems.
Click to expand...
Click to collapse
hey thank you for the quick reply
but could you guide me where to get the appropriate lollipop rom
and sorry for this noob question, but will installing lollipop gpt fix up the partition?

SemiNoob314 said:
hey thank you for the quick reply
but could you guide me where to get the appropriate lollipop rom
and sorry for this noob question, but will installing lollipop gpt fix up the partition?
Click to expand...
Click to collapse
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.

lost101 said:
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.
Click to expand...
Click to collapse
Thank you!
Will download and proceed as you said, though the download may take some time.
Will reply with the result.

lost101 said:
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.
Click to expand...
Click to collapse
Man you are a freaking lifesaver!!
Cannot thank you enough!! everything is working now!!
Thank you again!!

how to restore to lollipop or kitkat
i have bricked my moto g xt1033 asia firmware in a process to downgrade it from lollipop 5.0.2 to kitkat 4.4.4 i was badly struck and as the bootloader is unlocked it only shows the "WARNING bootloader unlocked " can anyone help me with what to do now to make my phone work in lollipop or kitkat any version

i want to say
---------- Post added at 08:36 AM ---------- Previous post was at 08:29 AM ----------
lost101 said:
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.
Click to expand...
Click to collapse
https://labs-dl.xda-cdn.com/apks/01e697
---------- Post added at 08:43 AM ---------- Previous post was at 08:36 AM ----------
lost101 said:
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.
Click to expand...
Click to collapse
last week i flashed motorola stock rom kitkat 4.4 on falcon using TWRP it flashed sucessfully...but after flashing i m not able to install any other custom rom like mokee,lineage,resurrection...it always stucks at boot... before flashing stock rom i flashed many rom but since the day flashing stock rom not able to flash any other looks like ROM changed the internal storage type as it says sometimes in twrp "unable to mount storage"

How to fix XT1032 Boot loop after factory reset

Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess

I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14

I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.

legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.

ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.

fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
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_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.

audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?

Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.

@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.

audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?

fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.

fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.

worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
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_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban