Database Info

[Q] XT1032 bricked please someone help me!!

Hello everybody i have a moto g XT1032 16 gb, bought on amazon. after unlocking bootloader and rooting my device, i used a guide on youtube (Convert Moto G (XT1032) to a Google Play Edition) to try the gp edition .... i updated to kitkat 4.4.4 and after that i received the update to lollipop 5.0.1, i updated it but now my device is stuck on bootloop
please someone help me!!

Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum.xda-developers.com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.

BobDiaz said:
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
forum. xda-developers. com/ moto-g/general/ guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum. xda-developers. com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
Click to expand...
Click to collapse
Thanks for your reply, basically is stuck on the boot with the google logo and a lock unlocked that i think it's for the unlocked bootloader..And when I power off the device by pressing for a long time the power button, after 2/3 seconds it reboot automatically....
now i'll try with the guides you gave me! I hope it will works
------------------------------------------------------------------------------
Edit: I did execute the .bat file and it did work! Thank you so much! now,i can't understand the second link you gave me... do i have to do that process' or it's fine like this? and now if I download the lollipop update, am i supposed to have the same problem?

stechiocca said:
Edit: I did execute the .bat file and it did work! Thank you so much! now,i can't understand the second link you gave me... do i have to do that process' or it's fine like this? and now if I download the lollipop update, am i supposed to have the same problem?
Click to expand...
Click to collapse
When you say "it work", did you mean that you can boot normally or that you can flash any rom that you wish? Or you didn't try that? The second link helped me because I couldn't flash any rom except GPE's (the partition table of these are different). If you wish to revert to your stock rom, you'll need to do as the second tutorial said.
I am now with an 5.0.1 Lollipop running well.
Please, give-me a feedback of your situation.
:good:

BobDiaz said:
When you say "it work", did you mean that you can boot normally or that you can flash any rom that you wish? Or you didn't try that? The second link helped me because I couldn't flash any rom except GPE's (the partition table of these are different). If you wish to revert to your stock rom, you'll need to do as the second tutorial said.
I am now with an 5.0.1 Lollipop running well.
Please, give-me a feedback of your situation.
:good:
Click to expand...
Click to collapse
So, first of all, now I can only boot normally and use it as gpe 4.4.4... This morning I received the lollipo 5.0.1 update, I did it but when it was at half of the installation, it stopped and there was the little android with an "ERROR" message.. if you want I can attach a photo with the error, so you may know how to solve (I did it when I had the stock recovery)... Now I tried to flash a ROM, so I put the CWM and rebooted into recovery, but when I tried ti install zip from SD card it said me "error: can't mount /sdcard" (I had this problem already when I used the guide to convert into gpe) So now what I have to do? I would like to try Lollipop, and I would like also to be able to flash any rom whenever I want!
--------------------------------
Edit: I just attached a photo of the problem so may be you can understand what happens!

stechiocca said:
So, first of all, now I can only boot normally and use it as gpe 4.4.4... This morning I received the lollipo 5.0.1 update, I did it but when it was at half of the installation, it stopped and there was the little android with an "ERROR" message.. if you want I can attach a photo with the error, so you may know how to solve (I did it when I had the stock recovery)... Now I tried to flash a ROM, so I put the CWM and rebooted into recovery, but when I tried ti install zip from SD card it said me "error: can't mount /sdcard" (I had this problem already when I used the guide to convert into gpe) So now what I have to do? I would like to try Lollipop, and I would like also to be able to flash any rom whenever I want!
--------------------------------
Edit: I just attached a photo of the problem so may be you can understand what happens!
Click to expand...
Click to collapse
So, like I said above... Just follow the second link.
The first one give you a temporary solution. It main objective is restore the capacity of mounting the partitions and booting into /system.
The second one open your horizons again, letting you decide which rom you will install. Just follow this and you'll can feel the sweetness of the Lollipop!
DO NOT try to install ANY actualizations over the TEMPORARY GPE edition. If you want do go back to GPE, do the second tutorial before.
Gimme your feedback and click ThankYou if it was usefull!
Nice wood bench, by the way.
:good:

BobDiaz said:
So, like I said above... Just follow the second link.
The first one give you a temporary solution. It main objective is restore the capacity of mounting the partitions and booting into /system.
The second one open your horizons again, letting you decide which rom you will install. Just follow this and you'll can feel the sweetness of the Lollipop!
DO NOT try to install ANY actualizations over the TEMPORARY GPE edition. If you want do go back to GPE, do the second tutorial before.
Gimme your feedback and click ThankYou if it was usefull!
Nice wood bench, by the way.
:good:
Click to expand...
Click to collapse
Ok i'm downloading the necessary files ... just two last questions before I do this, cause i'll wait for your answer before starting doing everything... 1) Will I lose all userdata? obviously I'm going to backup my data but ... am I going to lose my file and data?
2) will it work even if my original software was Retail DE?
and finally, thank you for the help, I'm going to click thank you even if it doesn't work (hope not obviously ), cause you were very helpful

I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.
I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?

stechiocca said:
Ok i'm downloading the necessary files ... just two last questions before I do this, cause i'll wait for your answer before starting doing everything... 1) Will I lose all userdata? obviously I'm going to backup my data but ... am I going to lose my file and data?
2) will it work even if my original software was Retail DE?
and finally, thank you for the help, I'm going to click thank you even if it doesn't work (hope not obviously ), cause you were very helpful
Click to expand...
Click to collapse
Wel... The answers:
1) Yes. You'll loose all your user data. One of the steps during the installation of any room is erase all the cache partitions and the userdata. That way, you can prevent any compatibility issues.
2) You phone will "forget everything about it's past", and will "think" that it is Brazilian now. If you don't like it, try downloading an ADB compatible DE rom. But, in my opinion, the Lollipop is way better than the Kit Kat. Unless you need the Xposed Modules.
Cheers!
Merry Christmas! :laugh:
---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------
redbull93 said:
I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.
I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?
Click to expand...
Click to collapse
Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.
Give us a feedback!
Cheers!

@BobDiaz do you think i should also erase dalvik cache? because i do everything step by step but it does remain in bootloop with the google logo ....

Let me just understand:
Did you try the first tutorial again or you are in the second for the first time?
You ALWAYS need to erase your cache partitions. Doing a clean installation always prevent bugs and incompatibility issues.
I'll ask for photos again. Show me, if possible, the step-by-step; Or upload a video on youtube.
Cheers!

BobDiaz said:
Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.
Give us a feedback!
Cheers!
Click to expand...
Click to collapse
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.
Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?

redbull93 said:
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.
Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?
Click to expand...
Click to collapse
Actually, you can't.
You can only apply UPDATES to the rom it was meant to be. You cannot apply an Lollipop Update made to an 4.4.4 Retail-BR to an GPE, even if it was an 4.4.4. It will bug the partition table, leading your device to bootloop.
If you've already tried to do as the second tutorial said more than one time, following all the steps, and it still is in bootloop, i recommend you to try searching for a alternative.
Give us the feedback anyway!
Cheers!

Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.
Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.
Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"
Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"
Image 3: State after entering the last "flash system .. " command

redbull93 said:
Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.
Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.
Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"
Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"
Image 3: State after entering the last "flash system .. " command
Click to expand...
Click to collapse
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.
Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.
This is probably a partition table error.
Give us the feedback!
=]
________________________________________
I've seen this in other topic:
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884

BobDiaz said:
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.
Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.
This is probably a partition table error.
Give us the feedback!
=]
________________________________________
I've seen this in other topic:
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
Click to expand...
Click to collapse
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it??

stechiocca said:
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it??
Click to expand...
Click to collapse
I could not upload here in XDA the gpt.bin that I've used.
Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").
Try the stock from your country.

BobDiaz said:
I could not upload here in XDA the gpt.bin that I've used.
Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").
Try the stock from your country.
Click to expand...
Click to collapse
hey, how are you? i'm really happy because it finally worked! I just had to "mfastboot flash partition gpt.bin" to make it works and i didn't get the "image is too large" problem... now i'll do the second part of the second guide hope it will work!! thank you a lot @BobDiaz

Excellent.
Try the other tutorial and tell me how did it go.

@BobDiaz Now i'm currently running correctly lollipop 5.0 brazil en BR, am i able to install a custom recovery and flash any rom whenever i want?

Moto G XT1033 (India) problems updating to Lollipop

Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium

The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.

I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?

Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?

pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.

skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?

pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.

skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!

pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!

Moto G Bootloop/Freeze

I have a Moto G (XT1032) and it seems to be stuck somewhat in a bootloop. The reason I say this is because I can get into fastboot, go into recovery, and sometimes it will get to the "M" but nowhere past that. On a normal boot up, it will get to the "BOOTLOADER UNLOCKED" screen (yes I have unlocked bootloader and rooted), and that's it. I believe this happened because I was trying to flash Android 5.0.1 to the device because it wasn't available yet. Thanks in advance for any help, and if you need more information just ask. The last thing I want to do is have to send it in.

HopperPlaysMC said:
I have a Moto G (XT1032) and it seems to be stuck somewhat in a bootloop. The reason I say this is because I can get into fastboot, go into recovery, and sometimes it will get to the "M" but nowhere past that. On a normal boot up, it will get to the "BOOTLOADER UNLOCKED" screen (yes I have unlocked bootloader and rooted), and that's it. I believe this happened because I was trying to flash Android 5.0.1 to the device because it wasn't available yet. Thanks in advance for any help, and if you need more information just ask. The last thing I want to do is have to send it in.
Click to expand...
Click to collapse
What did it say when you tried installing 5.0? Have you tried clearing cache/dalvik?

dustcollector69 said:
What did it say when you tried installing 5.0? Have you tried clearing cache/dalvik?
Click to expand...
Click to collapse
I have tried installing cache/dalvik, and when installing 5.0, it would have an issue installing because of updater-script. On my phone (in recovery mode sideloading from adb) it would say "Installation aborted"

HopperPlaysMC said:
I have tried installing cache/dalvik, and when installing 5.0, it would have an issue installing because of updater-script. On my phone (in recovery mode sideloading from adb) it would say "Installation aborted"
Click to expand...
Click to collapse
Hmm, im not sure why it would say that.. Did you format system before flashing?If you don't mind losing data you could always reflash stock firmware through fastboot in the bootloader

dustcollector69 said:
Hmm, im not sure why it would say that.. Did you format system before flashing?If you don't mind losing data you could always reflash stock firmware through fastboot in the bootloader
Click to expand...
Click to collapse
I formatted before installing. I know it's problem with my phone because the Android 5 is for GPE and I have a falcon version Moto G. I know there is a way to bypass it though. I don't mind losing data either as I had to anyway to unlock the bootloader.

I'm also going to try sideloading 5.0 again after clearing dalvik/cache again.

HopperPlaysMC said:
I formatted before installing. I know it's problem with my phone because the Android 5 is for GPE and I have a falcon version Moto G. I know there is a way to bypass it though. I don't mind losing data either as I had to anyway to unlock the bootloader.
Click to expand...
Click to collapse
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219

dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Will give it a try, but if not I will tell you what I see after trying to sideload to 5.

dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Got GPE 4.4.4 running, I shall now try 5.0.1

dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Ok, so at least my phone is working, but I can't sideload 5 onto my device. Here is what I see on the phone after the CMD reaches 100%:
Code:
Restarting adbd...
status 0
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
If you can help me with this, I would be grateful.

HopperPlaysMC said:
Ok, so at least my phone is working, but I can't sideload 5 onto my device. Here is what I see on the phone after the CMD reaches 100%:
Code:
Restarting adbd...
status 0
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
If you can help me with this, I would be grateful.
Click to expand...
Click to collapse
thats good you at least got your phone working, can you send me the link to the zip your trying to install? are you sure its not corrupted?

probably its corrupted, try download the ota from settings menu and tell us

esd316 said:
probably its corrupted, try download the ota from settings menu and tell us
Click to expand...
Click to collapse
OTA isn't showing up, but it may be corrupted

dustcollector69 said:
thats good you at least got your phone working, can you send me the link to the zip your trying to install? are you sure its not corrupted?
Click to expand...
Click to collapse
Here's the link: goo.gl/zDJG9q (That'll directly download it)

HopperPlaysMC said:
Here's the link: goo.gl/zDJG9q (That'll directly download it)
Click to expand...
Click to collapse
im downloading now, will check it out in a bit
why dont you flash one of these zips instead and through a custom recovery though?
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

dustcollector69 said:
im downloading now, will check it out in a bit
why dont you flash one of these zips instead and through a custom recovery though?
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I have clockwork recovery, I will attempt to flash one of those later.

All of the ROMs for my phone on http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 are Brazilian.

Yep flash a stock rom for xt1032 (try a optimized) and that should work

esd316 said:
Yep flash a stock rom for xt1032 (try a optimized) and that should work
Click to expand...
Click to collapse
Can you link me one? Or do i just do a Brazilian one?

Tried installing the Brazilian one and... my phone is messed up again and I have no idea how I fixed it. Help again?

Moto G (1st gen) OTA to Lollipop fails

Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks

Same problem here

Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.

A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...

Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.

A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.

Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.

A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?

Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.

A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.

Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.

Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least

Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...

To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.

fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?

fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.

YOG4PAS2QL bricks my OPO

Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.

erdeebee said:
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
Click to expand...
Click to collapse
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471

The only error I got, was that it's impossible to boot. I'll try your guide asap

Heisenberg said:
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.

Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.

erdeebee said:
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Click to expand...
Click to collapse
erdeebee said:
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
Click to expand...
Click to collapse
Is there a reason you're using that particular build instead of the latest? How are you installing it?

Heisenberg said:
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Click to expand...
Click to collapse
I'm sorry, I thought my message was clear. The latest build gives the same problem. With this build, I'm able to boot. I installed this in terminal as a fastboot-images.

This guy has the exact same problem.

erdeebee said:
This guy has the exact same problem.
Click to expand...
Click to collapse
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip

Mr hOaX said:
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Click to expand...
Click to collapse
I've tried the first, didn't work. I've tried flashing 11S and started upgrading. I didn't have issues until 12.0. When I got to 12.1 I couldn't reboot (but I could shut down and boot). With the latest update I couldn't even boot normally.

Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk

erdeebee said:
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
Click to expand...
Click to collapse
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough

playya said:
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
Click to expand...
Click to collapse
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.

erdeebee said:
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
Click to expand...
Click to collapse
My bad on that did not even realize there was another page.. dont know how that happened... Wow I say just start from scratch and go to cm page and download the latest stock software. I am sorry I see others have tried to help you and to be honest your breakdown is a lil confusing. NO worries though hopefully someone will come along to help