Anyone Captured the Verizon G 4.4.4 update? - Moto G Q&A, Help & Troubleshooting

Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.

judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
No luck here...there is post over on Android Forums that Verizon users are getting the 4.4.4 OTA update but nobody has posted the captured zip file yet.

Captured Verizon CDMA Moto G 4.4.4 Update Zip
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.

netkeys said:
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.

judask24 said:
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
Click to expand...
Click to collapse
This is the file downloaded on 7-21-2014. Attached is a screen shot of the updater.

netkeys said:
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.

randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?

chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
It was pulled from the /cache folder. If you put in /storage/sdcard0 you may also need to rename to update.zip

randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
Yes please do. My wife's phone is wanting to update since Sunday night.

Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.

chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
I think you can select "apply update from sdcard" in the recovery mode. No?
EDIT: You flashed to PagePlus. I missed that part. Sorry about that.

I was on a AOSP based rom.
So I flashed back to stock via CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.
Booted up once to make sure the the flash went well.
Flashed CWM via bootloader. Tried TWRP first, did not work with the update.zip.
Renamed the zip above to update.zip and flashed via cwm. Worked fine. (yes the zip is 4.4.4)
Before rebooting, went ahead and flashed supersu.zip.
Then rebooted back to bootloader and flashed my preferred recovery, TWRP.
All seems well. This is on PagePlus.

Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.

XDA Dark said:
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
Click to expand...
Click to collapse
It sounds like the 4.4.4 update is working fine...the only issue is that there doesn't seem to be a full stock 4.4.4 flash available (like we have for 4.4.2), and from what I can tell from posts (haven't tried this myself), you cannot reflash the full stock 4.4.2 after the 4.4.4 update since the bootloader and/or partitions have changed. There may be some workarounds, but those seem to be for other models or geographies as best I can tell. Once we have the full 4.4.4 flash, then at least you can always revert to that, but it doesn't appear to be released yet.

I've been keeping an eye out for the update OTA. I guess I'd rather just go down that path officially since my phones not rooted and had stock locked bootloader. Just wish it would hurry up and be pushed to my device.

Install zip via stock recovery
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
Ota file works it is 4.4.4 update for Verizon Mota G. Download zip to phone power off. Hold down power and volume down for a few seconds release. Once at menu go to recovery. Once in recovery android with exclamation with no options will appear. Press and hold Volume up for 10 seconds continue to hold while now also pressing power button for 3 seconds release. Your in recovery mode select update from zip and proceed. Happy camping with new dialer update camera shots in low lightness and other fixes and features!

randomchaos26 said:
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
Click to expand...
Click to collapse
Followed these directions and worked without any problem.
The fixed the external USB mounting problem that was in 4.4.2

I updated today on Boost Mobile Moto G flashed to Page Plus with no issues... Success
Sent from my XT1028 using XDA Free mobile app

randomchaos26 said:
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
Click to expand...
Click to collapse
Thanks for the instruction. Questions:
(1) My flashed page plus moto-g is on rooted stock rom (with unlocked bootloader of course). Do I still need to restore the system partition back to stock?
(2) What is "CFC-fastboot"? Do you mean
fastboot falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip
(i.e. no underscore between fastboot and falcon) ?
Thanks!

it's available on OTA now yay

Related

XT1033 (Australian Dual Sim 8GB) upgrade to KitKat?

Hey Guys, bought my phone in Australia at retail. It's running 4.3 JB. I've already unlocked the bootloader and installed a recovery. Now I want to run KitKat. I checked and there's no OTA, it says I'm already up to date. I don't care about the dual sim at all as I only have one sim (it's actually quite annoying having two icons in the statusbar).
Can I just go and install any Moto G KitKat ROM onto the phone and it will work? Is it better to have the official OTA so that it updates the radios before installing a custom KitKat ROM? Do the radios matter? Will I brick my XT1033 if I install a ROM for XT1031, XT1032 etc. ?
Just asking before I kill the phone.
Thanks guys
Single SIM ROMs are not compatible with dual chip XT1033.
From what I have read there is only 2 options:
1. unlock the phone and load en.GB 4.3 ROM and wait for the 4.4 kitkat update on it
2. CM11 by dhacker29 - Read first post about the details about how to flash to XT1033 where you need to flash a modem as well. http://forum.xda-developers.com/showthread.php?t=2608377
Whatever you do, make sure you do a backup of the stock ROM as I don't see Australian ROM in the stock images thread yet. So if you need to go back you can safely restore. To Restore from CM11 you need to flash the old modem as well that is in the same thread.
There are no cases of bricking so far that I am aware of. Also you could try fastboot flashing* the en.GB 4.4.2 firmware.
http://forum.xda-developers.com/showpost.php?p=49861244&postcount=101​
*mfastboot may be required.
EDIT: You should be aware that flashing the GB firmware also includes the GB Modem/Radio firmware. If you notice data/wifi/coverage issues after flashing, this may be the reason. There is currently on AU firmware image you can restore with.
Excluding the following commands should allow you to retain the AU Modem/Radio firmware:
flash modem NON-HLOS.bin
erase modemst1
erase modemst2
flash fsg fsg.mbn​
syl0n said:
Single SIM ROMs are not compatible with dual chip XT1033.
From what I have read there is only 2 options:
1. unlock the phone and load en.GB 4.3 ROM and wait for the 4.4 kitkat update on it
2. CM11 by dhacker29 - Read first post about the details about how to flash to XT1033 where you need to flash a modem as well. http://forum.xda-developers.com/showthread.php?t=2608377
Whatever you do, make sure you do a backup of the stock ROM as I don't see Australian ROM in the stock images thread yet. So if you need to go back you can safely restore. To Restore from CM11 you need to flash the old modem as well that is in the same thread.
Click to expand...
Click to collapse
thats true, I flased cm11 and both sim signal not work,
then I flash modem xt1033 same not work again,
finally I restored my stock room and sit like a boss for waiting 4.4 officiall update,
my moto g from malaysia retailer. :angel:
invictussevenfold said:
thats true, I flased cm11 and both sim signal not work,
then I flash modem xt1033 same not work again,
finally I restored my stock room and sit like a boss for waiting 4.4 officiall update,
my moto g from malaysia retailer. :angel:
Click to expand...
Click to collapse
hi, do you manage to flash kitkat and get single sim to work?
devalian said:
hi, do you manage to flash kitkat and get single sim to work?
Click to expand...
Click to collapse
i did, with the following update OTA GB 4.4.2, but something wrong when flash using sideload or put zip file to sdcar, so it cant be done.
n today I want to change my moto to single sim, because I dont need dual sim acctually. keep calm developer
invictussevenfold said:
i did, with the following update OTA GB 4.4.2, but something wrong when flash using sideload or put zip file to sdcar, so it cant be done.
n today I want to change my moto to single sim, because I dont need dual sim acctually. keep calm developer
Click to expand...
Click to collapse
cool. i did tried a several methods, but i couldnt get the radio signal at all. so was wondering what did i did wrongly.
mind to elaborate more on your steps?
juzza87 said:
Hey Guys, bought my phone in Australia at retail. It's running 4.3 JB. I've already unlocked the bootloader and installed a recovery. Now I want to run KitKat. I checked and there's no OTA, it says I'm already up to date. I don't care about the dual sim at all as I only have one sim (it's actually quite annoying having two icons in the statusbar).
Can I just go and install any Moto G KitKat ROM onto the phone and it will work? Is it better to have the official OTA so that it updates the radios before installing a custom KitKat ROM? Do the radios matter? Will I brick my XT1033 if I install a ROM for XT1031, XT1032 etc. ?
Just asking before I kill the phone.
Thanks guys
Click to expand...
Click to collapse
I downloaded and uncompressed android 4.3 firmware - Blur_Version.14.71.8.falcon_umts.Retail.en.GB from http://sbf.droid-developers.org/phone.php?device=14
then ran the "flash-all.bat" script. Rebooted and then did the OTA update. A single (primary) sim works no issues, and my model number now says XT1032 instead of XT1033.
I'm sure you'd get the same result by just flashing straight Android 4.4.2 for Great Britain - Blur_Version.174.44.9.falcon_umts.Retail.en.GB
I only need one sim anyway, so it works well for me. then I make lots of modifications with Xposed.
gregneal said:
I downloaded and uncompressed android 4.3 firmware - Blur_Version.14.71.8.falcon_umts.Retail.en.GB from http://sbf.droid-developers.org/phone.php?device=14
then ran the "flash-all.bat" script. Rebooted and then did the OTA update. A single (primary) sim works no issues, and my model number now says XT1032 instead of XT1033.
I'm sure you'd get the same result by just flashing straight Android 4.4.2 for Great Britain - Blur_Version.174.44.9.falcon_umts.Retail.en.GB
I only need one sim anyway, so it works well for me. then I make lots of modifications with Xposed.
Click to expand...
Click to collapse
I am really curious so I'll try this. Downloading "Blur_Version.174.44.9.falcon_umts.Retail.en.GB" and will report back, worst case I just run the stock flash all again (Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03) now that I know there's no risk
juzza87 said:
I am really curious so I'll try this. Downloading "Blur_Version.174.44.9.falcon_umts.Retail.en.GB" and will report back, worst case I just run the stock flash all again (Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03) now that I know there's no risk
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2542219
Changed the filenames for these commands to reflect the files in the folder:
mfastboot flash system system.img_sparsechunk1
to
mfastboot flash system system.img_sparsechunk.0
It is rebooting now.
Boot animations works [OK]
"Preparing Device - Please Wait..." [OK]
Choose Language (KK style!) [OK]
So far I only have one SIM card working with only one set of icons at the top and it has successfully connected to Vodafone AU (YES!)
Wifi network detected [OK]
OK everything is running! WiFi is working, phone is now running 4.4.2 KitKat! Just called myself and it worked!
THANKS GUYS
I will follow up later on. First thing I'll try is recovery, root, xposed framework and see if I can change the battery icon to show percentage (this wasn't possible on the JB ROM but I suspected because of the dual sim and likely a different SystemUI.apk
I had trouble rooting but then just used this flashable zip http://forum.xda-developers.com/showthread.php?t=2585755 and it got there.
I installed Xposed and everything worked as expected, using gravity box I changed the battery to one with a percentage and reduced the navigation bars to 70% (gives more screen real estate). Using the Google Experience Launcher, Google Keyboard and enabling ART has made this device a bit closer to my Nexus 4 which the screen broke on, so I'm very happy with this device.
Now I just need to work out how to get rid of the carrier name in the status bar (VODAFONE AU takes up a lot of room :silly
EDIT: Thanks Moto X community http://repo.xposed.info/module/com.penree.android.xposed.hidecarriermotox now it's gone
devalian said:
cool. i did tried a several methods, but i couldnt get the radio signal at all. so was wondering what did i did wrongly.
mind to elaborate more on your steps?
Click to expand...
Click to collapse
I think you should be waiting for general thread for moto G dual sim, and also they will create another rom for it.
I use Q10 now, bored with android :victory:
I flashed Google Play edition 4.4.2 ROM on my XT1033 + added Xposed GravityMod. Gives me 90% of what Cyanogenmod does so I am pretty happy.
syl0n said:
I flashed Google Play edition 4.4.2 ROM on my XT1033 + added Xposed GravityMod. Gives me 90% of what Cyanogenmod does so I am pretty happy.
Click to expand...
Click to collapse
Can you share some step by step instructions and links please?
Sent from my XT1033 using Tapatalk
occtec said:
Can you share some step by step instructions and links please?
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
try this.
http://forum.xda-developers.com/showthread.php?t=2635706
it works for me, changing XT1033 to single sim and kitkat.
1) download the file in the link
2) run the program and flash image with outside usa
3) flash cwm recovery
4) push superSU
5) install xposed framework with framework installer.
devalian said:
try this.
http://forum.xda-developers.com/showthread.php?t=2635706
it works for me, changing XT1033 to single sim and kitkat.
1) download the file in the link
2) run the program and flash image with outside usa
3) flash cwm recovery
4) push superSU
5) install xposed framework with framework installer.
Click to expand...
Click to collapse
Will give it a shot later, cheers mate. Just flat out with work atm. :banghead:
Sent from my XT1033 using Tapatalk
occtec said:
Can you share some step by step instructions and links please?
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2633272
Follow step by step instructions for International. Flash it all using fastboot. After the last step, before reboot, flash this GPE recovery: http://forum.xda-developers.com/showthread.php?t=2634008 (unzip it and run this command: fastboot flash recovery CWM6046-falcon_gpe.img)
Then I rebooted into the CWM recovery and used adb sideload to load to root it - follow this post exactly: http://forum.xda-developers.com/showpost.php?p=49996027&postcount=19
Once rooted installed Xposed and customise
syl0n said:
I used this: http://forum.xda-developers.com/showthread.php?t=2633272
Follow step by step instructions for International. Flash it all using fastboot. After the last step, before reboot, flash this GPE recovery: http://forum.xda-developers.com/showthread.php?t=2634008 (unzip it and run this command: fastboot flash recovery CWM6046-falcon_gpe.img)
Then I rebooted into the CWM recovery and used adb sideload to load to root it - follow this post exactly: http://forum.xda-developers.com/showpost.php?p=49996027&postcount=19
Once rooted installed Xposed and customise
Click to expand...
Click to collapse
How do you find the Play Edition compared to the Motorola version of KitKat? Pretty much the same thing just without the Motorola apps, settings, sounds and wallpaper?
I'm really happy with the Motorola software but wouldn't mind putting the Play edition on if it's much better
juzza87 said:
How do you find the Play Edition compared to the Motorola version of KitKat? Pretty much the same thing just without the Motorola apps, settings, sounds and wallpaper?
I'm really happy with the Motorola software but wouldn't mind putting the Play edition on if it's much better
Click to expand...
Click to collapse
Its not that much different.
The main issues i have with moto edition is that there is no internet calling in dialer (This is for VOIP accounts - Moto removed it from the Moto G for some reason and most 3rd party apps suck compared to native VOIP calling)
Minor issues (Nothing that can't be fixed with root)
- hidious career label in status bar (in en.GB 4.2.2)
- ugly dual SIM 2 signal bars wasting space on the status bar + 3G/H+ icon
- No useless Motorola apps that I don't need
Whats better in Moto ROM
- Camera App (GPE has no HDR)
- FM Radio (not in GPE)
- Faster file system (but this is barely noticable, GPE feels the same speed for me)
Is it ok to update to kitkat from 4.3? Ive only just tried it and says update available

Stagefright update (LMY48B->LMY48I)

I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
exhibit679 said:
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
Click to expand...
Click to collapse
You must return to stock before you attempt to install that zip. That means you cannot be rooted or have custom recovery in place
I've got a stock N5 I bought from Google on LMY48B and there's still no update for me.
Does anyone know what the roll-out timeline is for the LMY48I?
When should I conclude that I'm not going to get it OTA and resign myself to factory wipe and flashing the image?
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Nemesis02 said:
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Click to expand...
Click to collapse
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
moeREM said:
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
Click to expand...
Click to collapse
I have the same problem her as well with my nexus 5 it keeps saying error with little droid I've tried side loading manually but it didn't work also tried hard reset and wiping cache but nothing solved the problem so i just figured out the problem is the package it self
Same problem here
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
lpganesh said:
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This possibility makes me spend a lot of time, becouse i have lcd_density changed and all apps when i restore a backup are not in the main screen.
walt disney said:
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Click to expand...
Click to collapse
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Working - confirmed
cloney said:
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Click to expand...
Click to collapse
Thanks, confirmed that this method worked. Managed to update my rooted nexus 5 to LMY48I
Tried to install ota update after reverting to stock recovery using Simple Recovery Switcher app. However, also the error message, with little Android picture also appears. Please help
I assume this removed your root, though.
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Pastorelli's said:
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Click to expand...
Click to collapse
I'm with you, not going to try to flash these things, there are a few zip files out there dated a couple days ago, apparently the zips aren't tested prior to release since everyone is getting failure when flashing the zip file.
Is there really no method to apply OTA updates on rooted/modified devices (e.g. modify the update.zip itself to bypass whatever checks it performs)?
Same problem here- only had a custom recovery and root. brought back the stock recovery and did full unroot from SuperSu.
OTA update installtion stops with "Error".
Just flash the system image from the update.
Sent from my Nexus 5 using Tapatalk
Thanks, I ended up doing this http://forum.xda-developers.com/showpost.php?p=62288667&postcount=196
(flashing stock system, boot and recovery from my current version, letting OTA update install and re-rooting according to http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905)
I guess i could have flashed the new version just the same.

Shutting down Repeatedly When trying to Update Marshmallow

Hi All,
I have Moto X play running on android 5.1.1 lollipop. It was rooted recently and used with cyanogen Mod 12.1 for a month. during that time i did back up of entire phone. later i restored that and at present i have been using stock Rom. Recently i got official update for Android marshmallow and i downloaded the 500+Mb file and tried to install. In that process it was going to Twrp recovery mode and not installing properly. So i did reboot system. After 5 mins i turned on mobile, it got shutdown and i again restored my backup . It was working fine. cant we update to Marshmallow with the rooted device? If so how to stop the notifications of android system updates? I tried this way but still i am getting update notification
Apps--> All---> Motorola Update services--> turned off the notification
.How to disable it so that i should not receive update notification? or any other process to upgrade to marshmallow even after rooting? Please let me know
Mkrishna89 said:
Hi All,
I have Moto X play running on android 5.1.1 lollipop. It was rooted recently and used with cyanogen Mod 12.1 for a month. during that time i did back up of entire phone. later i restored that and at present i have been using stock Rom. Recently i got official update for Android marshmallow and i downloaded the 500+Mb file and tried to install. In that process it was going to Twrp recovery mode and not installing properly. So i did reboot system. After 5 mins i turned on mobile, it got shutdown and i again restored my backup . It was working fine. cant we update to Marshmallow with the rooted device? If so how to stop the notifications of android system updates? I tried this way but still i am getting update notification
Apps--> All---> Motorola Update services--> turned off the notification
.How to disable it so that i should not receive update notification? or any other process to upgrade to marshmallow even after rooting? Please let me know
Click to expand...
Click to collapse
you need stock recovery to update to OTA mm, you cannot update from TWRP. download the lollipop stock-firmware extract the recovery file and flash it, then update.
i wanted to ask that after restoring from backup you got OTA update notification ? or you downloaded the MM update from other sources?? because i thought after rooting i wont get official OTA.
Mkrishna89 said:
Hi All,
I have Moto X play running on android 5.1.1 lollipop. It was rooted recently and used with cyanogen Mod 12.1 for a month. during that time i did back up of entire phone. later i restored that and at present i have been using stock Rom. Recently i got official update for Android marshmallow and i downloaded the 500+Mb file and tried to install. In that process it was going to Twrp recovery mode and not installing properly. So i did reboot system. After 5 mins i turned on mobile, it got shutdown and i again restored my backup . It was working fine. cant we update to Marshmallow with the rooted device? If so how to stop the notifications of android system updates? I tried this way but still i am getting update notification
Apps--> All---> Motorola Update services--> turned off the notification
.How to disable it so that i should not receive update notification? or any other process to upgrade to marshmallow even after rooting? Please let me know
Click to expand...
Click to collapse
if you have your backup just do a full flash on stock rom and start fresh. there's an Asian 6.0 rom (I believe it is Indian) on the x play github. then proceed with root again.
bablu048 said:
you need stock recovery to update to OTA mm, you cannot update from TWRP. download the lollipop stock-firmware extract the recovery file and flash it, then update.
i wanted to ask that after restoring from backup you got OTA update notification ? or you downloaded the MM update from other sources?? because i thought after rooting i wont get official OTA.
Click to expand...
Click to collapse
Actually i am not android developer or android related person. After i heard many things about rooting the devices. I just give it a try by watching the video in you tube. So i am not aware of the core technical terms you specified.
First rooted the mobile. before installing the cyanogen Mod 12.1, i took back up in TWRP recovery mode. i used that same backup to restore after my device got shutdown. Yes even after rooting i got the Update notification
pijes said:
if you have your backup just do a full flash on stock rom and start fresh. there's an Asian 6.0 rom (I believe it is Indian) on the x play github. then proceed with root again.
Click to expand...
Click to collapse
I did not understand core android technical terms as i am not android guy. You mean to say unroot the device and perform root again?
bablu048 said:
you need stock recovery to update to OTA mm, you cannot update from TWRP. download the lollipop stock-firmware extract the recovery file and flash it, then update.
i wanted to ask that after restoring from backup you got OTA update notification ? or you downloaded the MM update from other sources?? because i thought after rooting i wont get official OTA.
Click to expand...
Click to collapse
Sir, if you have time please browse through Youtube and search for the name "dhananjay bhosale". In his playlists, there will be a moto x play playlist.in the you can find how to root moto........, by this way i rooted my mobile. i dont have any knowledge in android. I just Followed that Video. i could not able to post the link here as i am a new member
Mkrishna89 said:
Actually i am not android developer or android related person. After i heard many things about rooting the devices. I just give it a try by watching the video in you tube. So i am not aware of the core technical terms you specified.
First rooted the mobile. before installing the cyanogen Mod 12.1, i took back up in TWRP recovery mode. i used that same backup to restore after my device got shutdown. Yes even after rooting i got the Update notification
Click to expand...
Click to collapse
i think if you can block/disable notifications for Google Play Services, it'll remove the update notification.
settings>>apps>>google play services>>disable all notifications
bablu048 said:
i think if you can block/disable notifications for Google Play Services, it'll remove the update notification.
settings>>apps>>google play services>>disable all notifications
Click to expand...
Click to collapse
Sir, Is it possible to unroot the rooted devices in any way? if so could you please let me know
if you want to unroot you can do it from superuser, its mentioned in the youtube video. just unroot from superuser settings.
then if you want to upgrade to marshmallow download Indian stock lollipop rom from https://github.com/motoxplay/stock. unzip it on your computer to the the folder where you kept TWRP while flashing it . you'll see a file named recovery.img.
from adb run the command
Code:
fastboot flash recovery recovery.img
i.e flash this recovery just the way you flashed TWRP.
then you can update to marshmallow.
and did disabling google play services removed your update notification???
Mkrishna89 said:
Sir, Is it possible to unroot the rooted devices in any way? if so could you please let me know
Click to expand...
Click to collapse
You just have to download the twrp flashable 6.0 zip file and restore it through twrp. No extra things.
Sent from my XT1562 using Tapatalk
bablu048 said:
if you want to unroot you can do it from superuser, its mentioned in the youtube video. just unroot from superuser settings.
then if you want to upgrade to marshmallow download Indian stock lollipop rom from https://github.com/motoxplay/stock. unzip it on your computer to the the folder where you kept TWRP while flashing it . you'll see a file named recovery.img.
from adb run the command
Code:
fastboot flash recovery recovery.img
i.e flash this recovery just the way you flashed TWRP.
then you can update to marshmallow.
and did disabling google play services removed your update notification???
Click to expand...
Click to collapse
I diabaled. But at present i dont have internet connection to my mobile and i will let you know once i got any notification again about the update.
So as you said can i proceed that above steps with my rooted mobile? i mean flashing the unzip file like i did before? wont be any problem? or i have to unroot and root again after flashing the recovery.img??
Mkrishna89 said:
I diabaled. But at present i dont have internet connection to my mobile and i will let you know once i got any notification again about the update.
So as you said can i proceed that above steps with my rooted mobile? i mean flashing the unzip file like i did before? wont be any problem? or i have to unroot and root again after flashing the recovery.img??
Click to expand...
Click to collapse
Does your phone have twrp flashed or not?
Sent from my XT1562 using Tapatalk
K.khiladi said:
Does your phone have twrp flashed or not?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Yes Twrp flashed and successfully rooted
Mkrishna89 said:
Yes Twrp flashed and successfully rooted
Click to expand...
Click to collapse
Then please download the twrp flashable 6.0 zip and restore it through twrp.
Wait I will provide you the link of the thread.
Read the first post of that thread carefully.
Edit - here is the link, go to the thread, download the Indian one and follow the procedure
http://forum.xda-developers.com/showthread.php?t=3272979
[ROM] 6.0 TWRP Flashable Stock - Brazil / India / Canada versions
Sent from my XT1562 using Tapatalk
Mkrishna89 said:
I diabaled. But at present i dont have internet connection to my mobile and i will let you know once i got any notification again about the update.
So as you said can i proceed that above steps with my rooted mobile? i mean flashing the unzip file like i did before? wont be any problem? or i have to unroot and root again after flashing the recovery.img??
Click to expand...
Click to collapse
Edit: do as the post above this mentions.[i didn't know about that thread but it'll also work]
or
nope no problem just flash the recovery. but before doing anything take a backup on your external sdcard twrp>>backup[look at bottom to change where to store the backup select sd card] for security if in case anything goes wrong, you can flash twrp again and restore.
and remember to select 'ALLOW OEM UNLOCK' and usb debugging options from settings>>developer options
K.khiladi said:
Then please download the twrp flashable 6.0 zip and restore it through twrp.
Wait I will provide you the link of the thread.
Read the first post of that thread carefully.
Edit - here is the link, go to the thread, download the Indian one and follow the procedure
http://forum.xda-developers.com/showthread.php?t=3272979
[ROM] 6.0 TWRP Flashable Stock - Brazil / India / Canada versions
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Ya i got the thread. Before i proceed i want you let you know how i rooted my mobile. please check this link and let me know whether if i do in the way specified in the thread will works for me?
https://www.youtube.com/watch?v=PzQyg9t9j6U&index=3&list=PL3yX1-A8wnSmKqZGL55-7EYPFRol3zuIA
Mkrishna89 said:
Ya i got the thread. Before i proceed i want you let you know how i rooted my mobile. please check this link and let me know whether if i do in the way specified in the thread will works for me?
https://www.youtube.com/watch?v=PzQyg9t9j6U&index=3&list=PL3yX1-A8wnSmKqZGL55-7EYPFRol3zuIA
Click to expand...
Click to collapse
Just follow the procedure as given in that thread and everything will be fine.
It has nothing to do with the way you rooted your phone.
If a phone has twrp installed, he has nothing to fear about upgrading to latest versions as the updates are made available on Xda in Twrp flashable zip.
So no need to format the stock firmware again and then update and then all the headache.
Sent from my XT1562 using Tapatalk
bablu048 said:
Edit: do as the post above this mentions.[i didn't know about that thread but it'll also work]
or
nope no problem just flash the recovery. but before doing anything take a backup on your external sdcard twrp>>backup[look at bottom to change where to store the backup select sd card] for security if in case anything goes wrong, you can flash twrp again and restore.
and remember to select 'ALLOW OEM UNLOCK' and usb debugging options from settings>>developer options
Click to expand...
Click to collapse
Sir, In your previous post you meant to say this?
1. First unroot the mobile using the super Su (settings)
2. Then flash the Stock lollipop rom mentioned in the github
3. Then update the mobile to Marshmallow
4. Then again root the device
You meant to say this?
Mkrishna89 said:
Sir, In your previous post you meant to say this?
1. First unroot the mobile using the super Su (settings)
2. Then flash the Stock lollipop rom mentioned in the github
3. Then update the mobile to Marshmallow
4. Then again root the device
You meant to say this?
Click to expand...
Click to collapse
1. correct
1.1. check oem unlock and usb debugging
1.2. Copy the original old backup which you took, to your external sdcard. [just to return to stock if anything goes wrong]
2. Just flash the recovery which is present in the lollipop rom, no need to flash the whole rom.
3. correct
4. Do NOT flash the old superuser to root. To root again follow these steps http://forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
that other post was much easier
bablu048 said:
Edit: do as the post above this mentions.[i didn't know about that thread but it'll also work]
or
nope no problem just flash the recovery. but before doing anything take a backup on your external sdcard twrp>>backup[look at bottom to change where to store the backup select sd card] for security if in case anything goes wrong, you can flash twrp again and restore.
and remember to select 'ALLOW OEM UNLOCK' and usb debugging options from settings>>developer options
Click to expand...
Click to collapse
Hi Sir, I followed the other method. downloaded the twrp 6.0 zip from the thread. extracted to sdcard/twrp/backups.
wiped the data, restored that. after that i flashed the Super Su and reboot system. but it was stuck at motorola logo. in that description this will happen if we choose install super su. But i didnt do that.but still stuck at motorola logo.
so again i tried and now with out flashed Super su and downloaded super Su from google play,. getting error binaries cannot be updated. please help me

Moto G 2015 XT1541, TWRP 3.0.0: Updater process ended with ERROR: 7

Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
robert1010 said:
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
Click to expand...
Click to collapse
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Both update methods, as described above, fail. Method 1: using the phone's system updater, method 2: using the official(?) OTA upgrade files provided on this site.
But it looks like the OTA file is of a version I already have. See attachment.
Sorry, I misread your reply. I am looking for the stock recovery now keep you posted.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
robert1010 said:
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
Click to expand...
Click to collapse
Anyone who can help me with this please?

Moto G4 Plus US XT1644 Stock Unmodified 6.0.1 TWRP Backup & Recovery/Logo Images

Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .

Categories

Resources