Database Users

[XT1032] OTA to 4.4.4 (falcon_umts.EURetail.en.EU)

Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.

Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Click to expand...
Click to collapse
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.

feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
It should be. I flashed it using Philz recovery.

feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
I had the same problem, TWRP did not take the OTA file properly. Every time it wanted to boot after the install started, it started TWRP and if I restarded the device it went into a bootloop.
So I installed Philz and everything went fine!

It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app

drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?

Is it OK to flash this if I'm already on 4.4.4?

Quark^2 said:
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?
Click to expand...
Click to collapse
You´ve restored wrong kernel. It may be working for you, but it is different from stock. The error says that there is something that is not supposed to be there in the kernel partition.
Nicolae-Daniel said:
Is it OK to flash this if I'm already on 4.4.4?
Click to expand...
Click to collapse
You´re kidding, right?

No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?

Nicolae-Daniel said:
No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?
Click to expand...
Click to collapse
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.

knizmi said:
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.
Click to expand...
Click to collapse
By connectivity I meant signal strength.

My US-Global XT1032 still waiting...

tonyleeloveyou said:
My US-Global XT1032 still waiting...
Click to expand...
Click to collapse
US Global already has 4.4.3. The new kernel and dialer are already there, so don´t expect any improvements besides security patches when we get 4.4.4.

I received the OTA today. Updated without problems. Stock XT1032 8GB Moto G.

drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're still on Stock Recovery and don't want to use Philz, you can try to update the OTA by following the steps in the OP of this Post. I tried a lot of flashing, but in the end only this worked:
http://forum.xda-developers.com/moto-g/general/ota-file-indian-dual-sim-4-4-4-t2810166
Just follow the steps below the text:
REVERT TO STOCK WITHOUT LOSING DATA OR ANYTHING ELSE
Phone is unlocked, rooted and had xposed modules on it

Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.
Click to expand...
Click to collapse
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip

dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
So why don´t you revert your build.prop to stock?

dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
Knizmi is right. You modified your build.prop file, and an OTA update requires unmodified system files. You can add files to /system without problems however, so the su binary for example isn't an issue.
Sent from my Moto G using Tapatalk

OK, and where do i find a stock build.prop?
i don't know what modifications i have, but can i replace the stock one with my current after flashing? (and do i need to?)

HI! Firstly thanks for share the zip.
I´m using cwm recovery, superSU and xposed. Can I flash the zip directly from the recovery without any change? Will I lose the recovery (coming back to stock recovery) if I succed?
I tried to install the OTA after uninstall xposed and checking the ota survival mode on superSU, but it didn´t work (bootloop).
Thanks in advance.

OTA path

Does anyone know where is located the downloaded OTA?

yes but you need root
its in \cache
i have the update also but cant flash as i loaded the twrp recovery image and only stock recovery can run the ota

MAX_G said:
yes but you need root
its in \cache
i have the update also but cant flash as i loaded the twrp recovery image and only stock recovery can run the ota
Click to expand...
Click to collapse
Thanks. I couldn't find it, so I updated and now I lost root...
Strange isse, before OTA update (I have stock recovery) I wanted to NAND backup through TWRP boot, but phone wasn't found by fastboot neither adb... So I updated without backupping. Now too phone isn't found by fastboot, so I cannot neither root!
USB debug is on like always, I already tried to disable and enable again, but no way

A2017 flashed A2017U B29 failed to update to Nougat

I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks

Thalias said:
I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks
Click to expand...
Click to collapse
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.

bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
Thanks. I am downloading again. Hope it works this time.

bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.

Thalias said:
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.
Click to expand...
Click to collapse
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat

Teet1 said:
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat
Click to expand...
Click to collapse
I got b29 from zte website. Can I install it with stock recovery?

Thalias said:
Is there a link to download it?
Click to expand...
Click to collapse
https://www.zteusa.com/axon-7
Go under Support<Software Updates.

bkores said:
https://www.zteusa.com/axon-7
Go under Support<Software Updates.
Click to expand...
Click to collapse
Can I install it with stock recovery?

Thalias said:
Can I install it with stock recovery?
Click to expand...
Click to collapse
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".

bkores said:
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".
Click to expand...
Click to collapse
I got following message at bottom left of screen
Supported API: 3
Sorry, you can't sd upgrade

I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.

MiMtnBiker said:
I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.
Click to expand...
Click to collapse
Thanks. I forgot to unzip the file and put it in the root of sd card and I have done what you said too. It is running installation now.

I'm failing now? I went from ZAD v.3 back to stock B29 (I have an unlocked bootloader). I do have the MiFavor recovery (not TWRP)
I got the notification there was an upgrade, it took 6 hours to download... but the update "failed". I tried applying the update via SD card, but I get about 32% in and says "Update failed"......It also lists "Status 8" and "system partition has unexpected contents".

Sounds like y'all are having a hell of a time between the slow OTA speeds and then getting it to actually flash.
So I think I'll hold off for now. Hopefully we can get some TWRP-flashable zips soon enough... I think DrakenFX is already busy with all that

You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.

After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?

gpz1100 said:
You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.
Click to expand...
Click to collapse
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.

tele_jas said:
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.
Click to expand...
Click to collapse
No problem upgrading using the OTA on an sdcard here. Flashed the draken stock_system zip, then fastboot flashed the B29 stock recovery. Reboot to recovery (which is now stock) and update from sd card. If you've messed with other partitions, you may need to flash more B29 .img's.

Thalias said:
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?
Click to expand...
Click to collapse
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too

yosef019 said:
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too
Click to expand...
Click to collapse
I don't know Chinese so I prefer Eng community with support and US region always get latest update first.

April Security Update

Just switched on my Moto G 2015 (US Retail, XT1540 2GB) for the first time in a week or two and got an update notification...
April 1 2017 security update, Build Number MPIS24.65-25.1-19 and System Version 24.221.19.osprey_retus_2gb.retus.en.US.retus
Is this news to people, or am I just way behind?

I have the same model, just did check system for updates and the update notification popped up. No notification before checking.

you are just way behind........got this update months back

RijuSarkar said:
you are just way behind........got this update months back
Click to expand...
Click to collapse
But you have something different than a 1540. I believe 1540 was the last to get the January update, while there are other models with 6.01 which the 1540 most likely will never get.

I've never got an update.

Just got mine today, 6/26/17. Also have an XT1540.

So I followed the same instructions here as I did for the last security update to a rooted device. It worked perfectly with the exception of the unlocked boot loader warning. The dark logo I used survived the January security system update, but was lost with this update.

@MrTooPhone
What do you mean by restored data partition I your instructions,I am not getting that.i am on stock not rooted but unlocked bootloader

25vikasp said:
@MrTooPhone
What do you mean by restored data partition I your instructions,I am not getting that.i am on stock not rooted but unlocked bootloader
Click to expand...
Click to collapse
If you are on stock ROM, unrooted, and stock recovery, you should be able to take the OTA upgrade with no issue regardless if your bootloader is locked or not.. I had to restore my unrooted stock ROM prior to accepting the OTA update. Than using TWRP, I restored the data partition from my last saved rooted ROM.

MrTooPhone said:
If you are on stock ROM, unrooted, and stock recovery, you should be able to take the OTA upgrade with no issue regardless if your bootloader is locked or not.. I had to restore my unrooted stock ROM prior to accepting the OTA update. Than using TWRP, I restored the data partition from my last saved rooted ROM.
Click to expand...
Click to collapse
Thanks for reply,i forgot to mention I have twrp installed.in order to update I just restored my non rooted nandroid backup.so currently it is asking me to update so should I proceed and how to take backup for data partition

25vikasp said:
Thanks for reply,i forgot to mention I have twrp installed.in order to update I just restored my non rooted nandroid backup.so currently it is asking me to update so should I proceed and how to take backup for data partition
Click to expand...
Click to collapse
I would not proceed if TWRP is installed. You need the stock recovery installed for the OTA upgrade successfully install. Once stock recovery is installed, you can boot into TWRP and complete all actions as if TWRP was installed. I never installed TWRP.

MrTooPhone said:
I would not proceed if TWRP is installed. You need the stock recovery installed for the OTA upgrade successfully install. Once stock recovery is installed, you can boot into TWRP and complete all actions as if TWRP was installed. I never installed TWRP.
Click to expand...
Click to collapse
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong

25vikasp said:
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong
Click to expand...
Click to collapse
That is correct. I still have stock recovery installed, but I use fastboot commands to boot into TWRP recovery.
After connecting the phone to the usb, using Linux, I do the following commands from the same directory where my TWRP img file is located.
Code:
./adb reboot bootloader
sudo ./fastboot boot twrp-osprey-3.1.0-r1.img
This loads TWRP in your phone but does not install it.
From windows I think the commands basically the same without the "./"

25vikasp said:
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong
Click to expand...
Click to collapse
You can boot TWRP without flashing it to get root.

B353 Update with unlocked bootloader

Has anybody with an unlocked bootloader completed the recent B353 system update? My M3 has downloaded the update (even though I have automatic updates turned off). It says it's going to do the update on the next reboot. I assume that the update will fail, because I have an unlocked bootloader. I would prefer to stop the update if possible.
Has anybody done this update manually? Did you run into any problems with getting root back after the update?

woody1 said:
Has anybody with an unlocked bootloader completed the recent B353 system update? My M3 has downloaded the update (even though I have automatic updates turned off). It says it's going to do the update on the next reboot. I assume that the update will fail, because I have an unlocked bootloader. I would prefer to stop the update if possible.
Has anybody done this update manually? Did you run into any problems with getting root back after the update?
Click to expand...
Click to collapse
My M3 is unlocked. The first attempt at the OTA update failed for reasons I don't know. But I initiated the download again and the second time it installed. I had to re-root afterward, but the update *did not* re-lock the bootloader, thankfully.
[Edit] My partition setup is probably different from yours. Recovery has the original Huawei recovery on it; I put TWRP onto recovery2. That's probably the only reason the OTA was able to perform the update.

CCarson said:
My M3 is unlocked. The first attempt at the OTA update failed for reasons I don't know. But I initiated the download again and the second time it installed. I had to re-root afterward, but the update *did not* re-lock the bootloader, thankfully.
[Edit] My partition setup is probably different from yours. Recovery has the original Huawei recovery on it; I put TWRP onto recovery2. That's probably the only reason the OTA was able to perform the update.
Click to expand...
Click to collapse
That's really good to know. I had the Hauwei recovery on recovery2 originally, but I think I forgot to put it there the last time I updated. That would be great if I didn't have to unlock the bootloader to do an upgrade!

woody1 said:
That's really good to know. I had the Hauwei recovery on recovery2 originally, but I think I forgot to put it there the last time I updated. That would be great if I didn't have to unlock the bootloader to do an upgrade!
Click to expand...
Click to collapse
Not sure, but I think the recovery and recovery2 recoveries are different. I think the Huawei recovery2 is an emergency restore utility, which I opted to overwrite with TWRP. (It's the one you can run using vol-up at the bootloader unlocked warning page.)
The normal Huawei recovery is the usual sort of vendor recovery that's booted into to do the auto-updates.

CCarson said:
Not sure, but I think the recovery and recovery2 recoveries are different. I think the Huawei recovery2 is an emergency restore utility, which I opted to overwrite with TWRP. (It's the one you can run using vol-up at the bootloader unlocked warning page.)
The normal Huawei recovery is the usual sort of vendor recovery that's booted into to do the auto-updates.
Click to expand...
Click to collapse
I think that's right. The 2nd recovery is called erecovery and it's not very useful. I think that's a good practice to put TWRP there.

I can't get the OTA update to work. That's probably because I have TWRP in the first recovery partition and the OTA is expecting to find the stock recovery there. When the OTA runs, it boots into TWRP and seems to install, but nothing happens. I wonder if there's a way I can put the stock recovery back into the first recovery partition and then run the OTA update?

Has anybody gotten this update through Firmware Finder? It doesn't show up for me.