Database Info

Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) UPDATED 10/10

This is only for devices currently on 4.4 or rooted 5.1 w/ moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Note 12/2/2015:
Development on this has been discontinued with the release of the SunShine bootloader unlock.
To use SunShine without having to deal with KingRoot, you can flash the Rooted v3 system img and then use SunShine to unlock. This is the most stable method if you can use mofo.
After unlocking using SunShine, please flash the latest bootloader/radio images from here. This will bring your phone completely up to date and provide a more stable experience with custom ROMs.
These images are still flashable after unlocking your bootloader if you'd like a stable, closest-to-stock ROM possible.
Instead of using mofo to flash the system image, you can just use
Code:
fastboot flash system filename-goes-here.img
You can then flash your own tweaks like Xposed.
I'd recommend making a back up of the stock ROM in TWRP so you have a stable base to go back to if anything goes wrong.
Note 10/10/2015:
Updated all images to the latest OTA update (SU4TL-44) and included the latest official Xposed version (v75) in extras v5.
Follow the instructions with 5.1_images_v4.zip to flash the updated firmware images.
Note 9/5/2015:
Updated extras (v4) to include the latest official Xposed version (v73). Read the previous note for more information.
Note 8/31/2015:
Updated extras to the latest official Xposed version (v72). Reflashing all of the images is not required, only the extras system.img using mofo.
You can download the full extras image (1.5gb), or if you already have the rooted v2 image, use the extras v3 patch (8mb) with the instructions below.
Using the rooted v2 image + patch will allow you to update in the future without redownloading the entire image (as long as you keep the original after patching).
Note 7/23/2015:
Updated to the latest OTA (23.11.39). Make sure to follow instructions and reflash all images from the latest zip.
Unfortunately, I couldn't provide a patch to go from rooted image v1->v2, so a redownload is needed.
When applying the latest extras, make sure you're applying it to the rooted image v2.
Files (updated 10/10/2015 w/ latest OTA & extras v5)
5.1 firmware images (v4)
SHA1: 8be8a19664e6ba5aa556838bb3f744cdbf41f2ef
Stock 5.1 system image (v3)
SHA1: 1e67fc22331f035e9f3bd6c28d81fb173dd86a3e
Rooted 5.1 system image (v3)
SHA1: b8ff04d7f6ad9de31292cf62da94a3d80d3e373c
Extras 5.1 system image (rooted v3 + extras v5) (see below for details)
SHA1: 126744919f86132c05d15e79373ea759f74e37cf
Instructions
A data wipe is not required, but please back up any important data beforehand in case something goes wrong.
After extracting 5.1_images_v4.zip, reboot into bootloader and run the following commands to prepare your phone for the latest 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem modem.img
fastboot flash mdm1m9kefs3 fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash recovery recovery.img
fastboot erase ddr
fastboot reboot-bootloader
Then use mofo to flash the system image of your choice and reboot.
After flashing a system image, the first boot will stay on the Motorola logo for an extra 30 seconds to 1 minute. This is rebuilding the cache partition (erased by moforoot after every flash).
If your phone doesn't boot after 5 minutes (and isn't showing the "Upgrading apps" dialog), try formatting the cache in recovery by doing the following:
While phone is off, hold the volume down button and turn it on to boot into bootloader. Use the volume keys to find the recovery option and press power to confirm.
Once you see the dead Android (it may also say "No Command", this is normal), pull up the recovery menu by holding power and pressing volume up (5.1 recovery is different than 4.4) and use the wipe cache option.
If the screen is blank in recovery with a periodically flashing Android icon, try booting the phone normally and trying again. This happened to me a few times, and I theorize it's because of the cache partition not being formatted after erased.
Extras (updated 10/10/2015 w/ latest OTA & Xposed official v75)
Download patch (v5)
SHA1: 451be2eef3df509facf16b807c6fc665c8fac090
If you don't want to deal with patching the image using xdelta3, you can download the full extras image in the Files section above.
This will prevent you from updating without redownloading the whole image in the future, but is easier for less experienced users.
Current extras:
Xposed official v75 (download APK from here)
(optional) ad blocking
busybox/sqlite3
tethering enabled
To apply the patch, use the rooted v3 image (not an already patched image) as a base, and follow the patching instructions (using xdelta3) in this post.
After patching the system.img with the extras, you'll use mofo to flash the patched image.
To use ad blocking, download AdAway (available in F-Droid) and enable it. Make sure the "Target hosts file" is set to "/data/hosts" in settings.

shouldnt we also be updating the radio?

diabl0w said:
shouldnt we also be updating the radio?
Click to expand...
Click to collapse
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.

firstEncounter said:
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
Click to expand...
Click to collapse
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
edit: when i did the downgrade (4.4.4 to 4.4.2 radio) it disabled the ability to turn on wifi and log messages gave the error wifistatemachine: failed to load wifi driver

diabl0w said:
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
Click to expand...
Click to collapse
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.

firstEncounter said:
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
Click to expand...
Click to collapse
check my edit

diabl0w said:
check my edit
Click to expand...
Click to collapse
Radios won't be compatible across ROM versions. You would flash the 4.4.4 radio if downgrading to a 4.4.4 image, not while running 5.1.

Ummmmm. Is this a dream? Someone pinch me...... There's no one around....... Can this really be true!? I'm afraid to try it and bork everything.

firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot erase ddr
(Commands based on this post. Thanks @mikeoswego and @JulesJam!)
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Why aren't you flashing 5.1 recovery?

JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
Missed that command in the OP. Thanks!

Is the rooted image debloated
Sent from my XT1254 using Tapatalk

JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
So we should do that command as well?

janitorjohnson said:
So we should do that command as well?
Click to expand...
Click to collapse
I had trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.

JulesJam said:
I has trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
Click to expand...
Click to collapse
Is that the final command?

trikotret said:
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
No, it's completely stock with SuperSU installed.

janitorjohnson said:
Is that the final command?
Click to expand...
Click to collapse
I do
logo
boot
recovery
radios
But I do that b/c that is the way they are usually written in the scripts that come with the images. I think the only 2 where the order really matters is the bootloader and partition table and you aren't flashing those.
---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------
firstEncounter said:
No, it's completely stock with SuperSU installed.
Click to expand...
Click to collapse
I went ahead and made one too just in case there were any issues with FirstEncounter's since I already have a device set up to do this anyhow.
https://www.dropbox.com/s/rmuev8agm5wl2lh/XT1254_5.1_root_system_ext4.zip?dl=0
PLMK if there are any issues with my image. I will take it down once people have started to modify the images, test them and are sure there are no issues.
It should be easy for someone to modify the buildprop so you can have free tether.

works like a charm
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Followed instructions to a T and used OP's files... Everything works like a charm and is buttery smooth: http://imgur.com/ZwIRB8X
Bootloader acted a little weird, got a couple screen flickers... not sure if related or not. It worked itself out after one or two reboots. Thanks for the awesome instructions!

Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.

firstEncounter said:
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
Click to expand...
Click to collapse
Thank you! You are working mighty quickly I must say. We all really appreciate it!

I can not seem to boot it to recovery after doing the steps in OP. Little man blinks and says "no command" under him. Wanted to do a factory reset after the steps in OP. Any ideas? I am letting it boot into LP for the first time and then will try to get into recovery to do the reset.
After I let LP boot up, I could enter into recovery and factory reset without a problem.

Moto G 2015 xt1550 Two new Security Updates

Hi all I just got two new security updates on my xt1550 one after the other. the update versions are as follows
24.71.2.en.03 - July, 2016 Security patch
24.201.5.en.03 - October 1st, 2016 Security Patch
Can anyone else confirm they got the security patches?? my android version is on 6.0.1 and not rooted.

Yes many people have received the security updates...

yes, me too

Yes security updates are rolling out now in India, other varients got july update in late November and October patch with us.

yes i got this too and now when it reboots, it reboots to TWRP and loops back. So i cleared cache date and was able to boot properly. But i was not able to update to that version. mobile is rooted and unlocked. Is there anyway anyone can get me that link so that i can fastboot the update?

manohar1121 said:
yes i got this too and now when it reboots, it reboots to TWRP and loops back. So i cleared cache date and was able to boot properly. But i was not able to update to that version. mobile is rooted and unlocked. Is there anyway anyone can get me that link so that i can fastboot the update?
Click to expand...
Click to collapse
I faced the same issue.
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Go to this page. Download your respective factory image. Unzip. Flash the stock recovery. Now update.
After this, flash twrp if you want.

bin.sayantan said:
I faced the same issue.
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Go to this page. Download your respective factory image. Unzip. Flash the stock recovery. Now update.
After this, flash twrp if you want.
Click to expand...
Click to collapse
I dont wanna flash mobile all over again. just need to update that if possible. I got that 20MB update last month only..

manohar1121 said:
I dont wanna flash mobile all over again. just need to update that if possible. I got that 20MB update last month only..
Click to expand...
Click to collapse
Don't flash the entire stock ROM. Just the recovery image.
But please, don't flash that official update on any custom ROM.

bin.sayantan said:
Don't flash the entire stock ROM. Just the recovery image.
But please, don't flash that official update on any custom ROM.
Click to expand...
Click to collapse
I have flashed newer build in that not long ago.
u mean to say uninstall twrp? is that wat u meant flash recovery image ?

manohar1121 said:
I have flashed newer build in that not long ago.
u mean to say uninstall twrp? is that wat u meant flash recovery image ?
Click to expand...
Click to collapse
No need to wipe recovery. Flash stock recovery on top of TWRP. It will automatically be replaced.

If he is rooted he won't be able to update. OTA updates require pure stock - stock recovery, stock kernel, and an unmodified system. This means no root, xposed, or any other changes to the system including build.prop edits.
Sent from my MotoG3 using Tapatalk

bin.sayantan said:
No need to wipe recovery. Flash stock recovery on top of TWRP. It will automatically be replaced.
Click to expand...
Click to collapse
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
riggerman0421 said:
If he is rooted he won't be able to update. OTA updates require pure stock - stock recovery, stock kernel, and an unmodified system. This means no root, xposed, or any other changes to the system including build.prop edits.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
so i should lock my bootloader and flash stock recovery ?

manohar1121 said:
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
so i should lock my bootloader and flash stock recovery ?
Click to expand...
Click to collapse
You need not relock the bootloader. I have flashed system updates with stock recovery and unlocked bootloader.
Looks like you have correctly flashed the recovery. Once you get the red exclamation mark, keeping the volume up pressed, press the power button (I don't remember exactly, if it doesn't work, try the reverse).

manohar1121 said:
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
so i should lock my bootloader and flash stock recovery ?
Click to expand...
Click to collapse
No need to lock the bootloader, but if you were rooted as stated in your first post, you will the stock system and kernel. You can not update if ANY system files, kernel, or recovery are not FULL stock. Your best bet right now is to flash the stock ROM via fastboot, if you need the update.

riggerman0421 said:
No need to lock the bootloader, but if you were rooted as stated in your first post, you will the stock system and kernel. You can not update if ANY system files, kernel, or recovery are not FULL stock. Your best bet right now is to flash the stock ROM via fastboot, if you need the update.
Click to expand...
Click to collapse
I have stock ROM. 3.10.49-ge6a5415
system version - 24.71.2.osprey_retasia_ds_2gb.retasia.en.03 retin
i got OTA update. so its not possible to update if mobile is rooted is it ?

manohar1121 said:
I have stock ROM. 3.10.49-ge6a5415
system version - 24.71.2.osprey_retasia_ds_2gb.retasia.en.03 retin
i got OTA update. so its not possible to update if mobile is rooted is it ?
Click to expand...
Click to collapse
The updater script checks the system, recovery and kernel. If they do not match what is expected (full stock), then the update will fail. I can't say it any more clearly, you need FULL STOCK, ie no modifications to system files (xposed, added or deleted system apps, build.prop edits, root, custom recovery). If you have done any of this, even one, the update will fail. Flash the stock ROM via fastboot.

Got a new update Jan 2017
Moto g3 xt1550 Osprey

So, to revert back to stock 6.0.1 from custom 7.1.1, do i need to wipe system, data, cache, etc before restoring my back up of the stock?

M-in-M said:
So, to revert back to stock 6.0.1 from custom 7.1.1, do i need to wipe system, data, cache, etc before restoring my back up of the stock?
Click to expand...
Click to collapse
You should. But I think it can be done right after flashing stock ROM also.

After getting these brutal update messages every few minutes on Android 6.0 and not being to update because of root and TWRP, rather than going back to stock, I finally cracked and bit the bullet yesterday and installed Lineage. I am now on Android 7.1.2 with the April security update, and going forward new OS and security updates will be simple updates; in fact the May update as noted by the OP is due this week, and I can either install it OTA from Lineage with a press of a button, or via TWRP if I so desire . I understand others don't want to install a custom ROM for various reasons, but for me it was a no-brainer.

[GUIDE] [XT1572] Flashing Stock Firmware

As the Nougat is rolling out for XT1572 devices, here's the guide for Flashing Stock Firmware using Fastboot for receiving Nougat OTA.
(Inspired by @acejavelin guide)
Prerequisites:
1) USB Drivers (Not needed for Windows 10)
2) Fastboot installed and working.
3) Stock Factory Images for Moto X Style (XT1572): https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
Procedure:
1) Open a terminal or command prompt (Shift + Right click) window into the directory that contains the firmware files you extracted above.
2) Reboot the phone in Fastboot Mode (Reboot to Bootloader) and connect the USB Cable.
3) To verify if everything is perfect type in:
Code:
fastboot devices
If it shows your device serial number then you can be sure that it's properly connected.
4) Read the 'Notes' below.
6) Before proceeding, flash this commands to clean up the previous system's mess. This will get rid of the '(bootloader) Preflash validation failed' error when flashing gpt.bin (partition table).
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
5) Here's the actual commands to Flash the Stock Image. Please Enter them One-by-one, Don't create any .bat files or copy and paste the entire section.
Code:
[STRIKE]fastboot getvar max-sparse-size[/STRIKE]
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Make sure you read whatever is happening on the prompt, do not miss any errors. (Scroll up the prompt and re-check everything before booting)
Notes:
1) This won't Lock your bootloader but you will be able to get OTA's.
2) For receiving Nougat on RETASIA Dual Sim, download: XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
There will be a 44mb update already queued when you boot the device. It will update the device to December 2016 Security Patch.
Reboot and you will be able to get Nougat OTA (911mb), if eligible.
3) If you didn't get the OTA Update, Flash this Nougat OTA after updating to December 2016 security patch: https://forum.xda-developers.com/moto-x-style/general/ota-nph25-200-15-retasiads-t3636765 (Credits: @Sagar_1401)
4) Different firmwares may contain a different number of system.img_sparsechunk.X files, you must flash the number you have in your firmware image in order. From what I have seen, most 5.1.1 firmwares have nine, 6.0 has eight, and 6.0.1 has eleven sparsechunks.
5) You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).

There is no need to do fastboot getvar max-sparse-size, that is just for RSD Lite to check your maximum system chunk size, when doing it manually it does nothing.
Not really sure why this guide is needed, there are already a few out there that are basically identical.

Nice guide @antariksh thanks for this.
i will be flashing from my current version 6.0.1_MPH24.107-58 (seemingly higher version) tomorrow.
will update once i attempt this.

Quick tip if you can't get SafetyNet passed with Magisk V13.1 or V13.2
For Stock Nougat as we don't have boot.img
1) Backup boot with TWRP
2) Restore boot with TWRP
3) Flash Magisk zip
4) Reboot and Install Magisk Manager v5+
This won't get your SafetyNet passed.
5) Open Magisk Manager and once again press 'Download and Install'
This will automatically download and install the latest Magisk and after a reboot your SafetyNet will be passed.

antariksh said:
5) You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).
Click to expand...
Click to collapse
I got 6.0.1 ROM, how do i downgrade to 6.0? I try to flash to 6.0, it's shown message like above

hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank

trannamcloud said:
I got 6.0.1 ROM, how do i downgrade to 6.0? I try to flash to 6.0, it's shown message like above
Click to expand...
Click to collapse
titanworm said:
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
Click to expand...
Click to collapse
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.

acejavelin said:
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
Click to expand...
Click to collapse
Thanks a lot!
I go back to 6.0.1 Retapac, with security pack 1-Mar-2016, an now waiting for official Nougat OTA update

So I was on 6.0.1 as well and used the 18-8 firmware to downgrade to 6.0. had the same preflash validation error, i flashed gpt the second time after the error occurred and completed the flash like normal. Everything just worked perfectly fine after that. Got the security update to December and nought!
Edit : I did all of this keeping my bootloader unlocked.
Sent from my HTC 10 using Tapatalk
---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------
You need to go to 6.0 and not 6.0.1.. The firmware to download is XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
trannamcloud said:
Thanks a lot!
I go back to 6.0.1 Retapac, with security pack 1-Mar-2016, an now waiting for official Nougat OTA update
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk

pradeepvizz said:
So I was on 6.0.1 as well and used the 18-8 firmware to downgrade to 6.0. had the same preflash validation error, i flashed gpt the second time after the error occurred and completed the flash like normal. Everything just worked perfectly fine after that. Got the security update to December and nought!
Edit : I did all of this keeping my bootloader unlocked.
Sent from my HTC 10 using Tapatalk
---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------
You need to go to 6.0 and not 6.0.1.. The firmware to download is XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
So have you upgrade to Nougat yet?
I unlocked bootloader already, so could i bypass preflash validatation error as your guide? My phone said "downgrade failured " in bootloader screen logs

titanworm said:
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
Click to expand...
Click to collapse
Last week I flashed the MPH24.107-58-5 (6.0.1) thinking that this was the latest version. But then I TWRP restored back to my Custom ROM as there was no Nougat OTA.
On this Saturday I was able to flash the MPHS 24.49-18-8 without any issues.
Try flashing the gpt.bin twice and don't try to lock your bootloader.

trannamcloud said:
So have you upgrade to Nougat yet?
I unlocked bootloader already, so could i bypass preflash validatation error as your guide? My phone said "downgrade failured " in bootloader screen logs
Click to expand...
Click to collapse
i didn't see what the bootloader screen logs said, but when you get the error, you have to reflash the same thing again.
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
Click to expand...
Click to collapse
I have upgraded to Nougat successfully with no problems.

pradeepvizz said:
i didn't see what the bootloader screen logs said, but when you get the error, you have to reflash the same thing again.
I have upgraded to Nougat successfully with no problems.
Click to expand...
Click to collapse
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
acejavelin said:
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
Click to expand...
Click to collapse

yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin

titanworm said:
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
Click to expand...
Click to collapse
trannamcloud said:
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
Click to expand...
Click to collapse
Same me, the only way is back to 6.0.1 now

titanworm said:
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
Click to expand...
Click to collapse
trannamcloud said:
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
Click to expand...
Click to collapse
i am not expert in Moto flashing, don't honestly have the patience to wait for the OTA from 6.0.1 to 7.
Was the build MPHS24.107-58 official for ASIA DS in the first place? i see posts on the lenovo forums asking 6.0.1 for Asian version which makes me think there was no official release. i wouldn't expect a OTA update if there was no official release of the 107-58 build in Asia. mine is a Asain version, what version is yours?

hi, guys
What is your Bootloader version, mine is BL: A0.4C for 6.0 Retasia DS. I see 6.0.1 Retasia DS has BL: A0.4A. Which versions is higher? With BL: A0.4C for 6.0 Retasia DS, I cannot flash to 6.0.1 with GPT.bin and Boot.img.

I'm currently on xt 1572 retasia ds MPHS24.49-18-16 but with bootloader unlocked and twrp installed. Can someone guide me to the December 2016 file so that I can restore to stock or the nougat file so that I can directly update my phone through fastboot method. Thanks in advance.

duttandy said:
I'm currently on xt 1572 retasia ds MPHS24.49-18-16 but with bootloader unlocked and twrp installed. Can someone guide me to the December 2016 file so that I can restore to stock or the nougat file so that I can directly update my phone through fastboot method. Thanks in advance.
Click to expand...
Click to collapse
We don't have either... The best you can do is hope someone can do a TWRP backup of recovery you can restore, it needs to be the same variant and version.

pradeepvizz said:
i am not expert in Moto flashing, don't honestly have the patience to wait for the OTA from 6.0.1 to 7.
Was the build MPHS24.107-58 official for ASIA DS in the first place? i see posts on the lenovo forums asking 6.0.1 for Asian version which makes me think there was no official release. i wouldn't expect a OTA update if there was no official release of the 107-58 build in Asia. mine is a Asain version, what version is yours?
Click to expand...
Click to collapse
Confuse now. As you said, 6.0.1 build 107-58 is not official release, so maybe not receive OTA Nougat?
My version is Asian - retapac, 6.0.1 - build 107-58 with security patch 1-Mar-2016. It's unable to downgrade to any stock 6.0, as preflash error.

S251 Update Offline Update

Download the S251 update package from this link.
Rename the file to update.zip and move it to the root of your SD card (not internal storage). Boot into stock recovery and update.
If you have TWRP, it will not work. If you have root or magisk, it will not work. You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img

Do I have to uninstall magisk first ?

Sutcliffe9 said:
Do I have to uninstall magisk first ?
Click to expand...
Click to collapse
You can try that. If the update fails, you'll have to reflash the stock boot image as the update process might detect a modified boot image. Do you have the boot.img file for S244 ?

Thanks, I have the s244 boot image. I will give it a go tomorrow.

Thanks for uploading this.
Hm, update built on the 7th of November but only contains the 1st of November security updates. Google released further updates on the 5th and 6th of November, with the 6th November update fixing the very serious WPA2 'Krack' issues.
At least this update fixes the blueborne stuff.

Sorted ?

Sutcliffe9 said:
Sorted
Click to expand...
Click to collapse
PLease can you sent the right .img file.
I get install failed .
I have no twrp ! i use orijinal recovery from lenovo.

Murtie said:
PLease can you sent the right .img file.
I get install failed .
I have no twrp ! i use orijinal recovery from lenovo.
Click to expand...
Click to collapse
You only have one option. You need to re-install the full S244 ROM from this thread: https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914
Follow the steps but DO NOT FLASH USERDATA or you will lose all your existing apps and settings. This will restore your system to stock configuration then you should be able to update.

It worked for me doing this
If you have TWRP, You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img

Is there any chance of getting android oreo update bro

somenderjangra said:
Is there any chance of getting android oreo update bro
Click to expand...
Click to collapse
nope.

Sutcliffe9 said:
It worked for me doing this
If you have TWRP, You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
I have doing this but the same error. installation failed
Maybe i have not the right image
Do you have the boot.img file?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Im using this stock rom>
[LENOVO P2] [S244] [7.0] [STOCK] Lenovo P2a42 Stock Nougat Update TWRP Flashable by abhayruparel
---------- Post added at 12:03 PM ---------- Previous post was at 12:03 PM ----------
[LENOVO P2] [S244] [7.0] [STOCK] Lenovo P2a42 Stock Nougat Update TWRP Flashable by abhayruparel

Where does this file come from? How can we be sure it is safe? Verified official?

If I unlock bootloader and root with magisk will it break OTA?

Question is in the title.
If I unlock bootloader and root with magisk will I lose the ability to update via OTA?

prisoner1969 said:
Question is in the title.
If I unlock bootloader and root with magisk will I lose the ability to update via OTA?
Click to expand...
Click to collapse
https://topjohnwu.github.io/Magisk/tutorials.html
assuming you didn't install twrp

So I just got my G7 today and did a quick setup during which it installed an OTA and then I went ahead and installed TWRP and Magisk. Shortly afterwards I get a notification that another OTA is available but now it won't install (as expected). Because I installed Magisk after TWRP I don't have a 'clean' boot image to rollback to in order to get the OTA - is the only option to reflash back to stock and start again but install Magisk before TWRP this time or is there another option?

vinoxflame said:
https://topjohnwu.github.io/Magisk/tutorials.html
assuming you didn't install twrp
Click to expand...
Click to collapse
Haven't done anything to it yet

So you cannot have twrp as recovery at all for this?
I also cannot get it's info to magisk tap uninstall restore images but twrp is my recovery the ota downloads then fails during install anyone have a flashable version of the latest Moto g7 power retus zip that can flash in twrp? I assume it could be done.
---------- Post added at 10:45 AM ---------- Previous post was at 10:39 AM ----------
Or if someone has stock recovery.zip for Moto g7 power retus cause the directions given sound like it shouldn't matter if you have twrp or not but if that's it how can I flash stock recovery.zip for now take the ota then I wait til I get home to reroot sounds like only way of you've installed twrp as recovery
---------- Post added at 10:46 AM ---------- Previous post was at 10:45 AM ----------
Or if someone has stock recovery.zip for Moto g7 power retus cause the directions given sound like it shouldn't matter if you have twrp or not but if that's it how can I flash stock recovery.zip for now take the ota then I wait til I get home to reroot sounds like only way of you've installed twrp as recovery

Anyone got a stock recovery.img thats what i need so I can flash the ota, I do not see it with the firmware, none of the commands say flash recovery its all sparse chunks etc nothing with recovery I need a stock recovery img for moto g7 power retus anyone please!?

toxinburn said:
Anyone got a stock recovery.img thats what i need so I can flash the ota, I do not see it with the firmware, none of the commands say flash recovery its all sparse chunks etc nothing with recovery I need a stock recovery img for moto g7 power retus anyone please!?
Click to expand...
Click to collapse
Recovery is part of the boot.img now
Sent from my mata using XDA Labs

Weird cause I restore the image and twrp stays I'll try something later do latest update I'll get it figured out. But gonna have to reinstall user data I bet