Database Info

[Q] Back to 4.4.4 from 5.0.2 - Moto G 2013

hello everybody
my english is not so good, i try to describe and hope you understand what i mean.
ok let´s go
i updated my moto g 2013 (with open bootloader but without root) from original stock 4.4.4. manually to 5.0.2 - Not OTA. i did it with fastboot.
i don´t like 5.0.2 because the phone has to many bugs and it won´t be better. bad 3g and sometimes i don´t have any signal, play store services are shut down very often, can´t open playstore because my account is not available and yesterday all my apps from homescreen were gone......and so on.....
now i want to have 4.4.4 back again and i hope you can help me.
what i have is the original stock 4.4.4 (XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml)!
in this post, there are only BR, FR, MX, GB Firmware http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
1. what about my firmware, does it works too with this method?
so, here are so many posts about downgrade/restore..... just give me a link or post a description here or something else with an easy guide please.
more questions i have
2. which is the right description, tools, downgrade for my phone? the link above?
2. i read that after downgrade to 4.4.4 the phone has a kind of line or light on the display, is that right and why the phone get this?
3. what about this here? has it something to do with this display bug or for what is this file http://forum.xda-developers.com/showpost.php?p=54103676&postcount=2
what i have to do with this file? important for downgrade?
4. is it possible to downgrade bootloader too and how?
i know here are many posts about this and don´t be angry to me that i start a new one. a friend recommend this forum and said, here are a lot of good and helpful people.
so thank you so much

I hate lollipop!!
xodbx said:
hello everybody
my english is not so good, i try to describe and hope you understand what i mean.
ok let´s go
i updated my moto g 2013 (with open bootloader but without root) from original stock 4.4.4. manually to 5.0.2 - Not OTA. i did it with fastboot.
i don´t like 5.0.2 because the phone has to many bugs and it won´t be better. bad 3g and sometimes i don´t have any signal, play store services are shut down very often, can´t open playstore because my account is not available and yesterday all my apps from homescreen were gone......and so on.....
now i want to have 4.4.4 back again and i hope you can help me.
what i have is the original stock 4.4.4 (XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml)!
in this post, there are only BR, FR, MX, GB Firmware http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
1. what about my firmware, does it works too with this method?
so, here are so many posts about downgrade/restore..... just give me a link or post a description here or something else with an easy guide please.
more questions i have
2. which is the right description, tools, downgrade for my phone? the link above?
2. i read that after downgrade to 4.4.4 the phone has a kind of line or light on the display, is that right and why the phone get this?
3. what about this here? has it something to do with this display bug or for what is this file http://forum.xda-developers.com/showpost.php?p=54103676&postcount=2
what i have to do with this file? important for downgrade?
4. is it possible to downgrade bootloader too and how?
i know here are many posts about this and don´t be angry to me that i start a new one. a friend recommend this forum and said, here are a lot of good and helpful people.
so thank you so much
Click to expand...
Click to collapse
Did u find a way to revert back to kit Kat?

hey
no, sorry
i´m waiting for the answers

Just flash the 4.4.4 firmware via fastboot, using the following commands:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Use only this commands, absolutely DON'T flash gpt.bin and motoboot.bin, or you'll end bricking your device.
mfastboot download link: https://mega.co.nz/#!xgYkgI6I!E4MkiSwCm1AS4qor5xP8QTNeL-BAFZLrV9JDCIlBImM
I have successfully downgraded from 5.0.2 Retail DE to 4.4.4 Retail DE this way. The line glitch is due to a compatibility issue between kitkat kernel and lollipop bootloader, but it isn't so annoying, you only have to lock and unlock your device only once after every reboot. BTW I think that a hard reset will solve most of the problems you've faced on lollipop, I haven't experienced any of the issues you're talking about.

hello and thanks for your answer
why is there a different way for downgrade between yours and this http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553 ???
whats the different?
and what about the adb drivers. it must be installed first, saw on a video? i don´t need it for downgrade? i have a "minimal adb+fastboot setup.exe"!
what is behind ...... don´t flash gpt.bin and motoboot.bin...?
and i did a hard reset after update to 502, but have still some bugs
sorry for all my questions, i´m a bit careful

The partition layout may be different between KK and LP; therefore, I would recommend flashing gpt.bin.
You won't be able to flash motoboot.bin because your phone probably has the 41.18 bootloader which cannot be downgraded.
When you downgrade to KK, you will see a line running from the top to the bottom of the screen. It looks like it is rippling. Don't worry, this is happening because your are running KK on a LP bootloader. To get rid of the rippling, just lock and unlock the phone using the power button.
If you flash to stock KK and run the OTA update to 5.02, the rippling will go away because you'll be running stock LP on a LP bootloader.

Hello and thanks for answer, but you say its recommend to flash GPT and the other member said DON'T. so two different answers,. What happened if i flash and don't flash???

You can try to install the ROM without flash gpt.bin.
When going from GPE to non-GPE and vice versa, gpt.bin had to be flashed.

Hey audit13
Thanks for answer but i don't understand what you mean. What is gpe ?non gpe? Vice versa? No plan, sorry

Gpe means google play edition and non gpe means non Google play edition
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
As there are many threads about downgrading
So Im very much confused
Can anyone help me with the best way
If yes then it will be needfull to me

xodbx said:
Hey audit13
Thanks for answer but i don't understand what you mean. What is gpe ?non gpe? Vice versa? No plan, sorry
Click to expand...
Click to collapse
GPE = Google Play Edition
Non-GPE = Stock ROM
GPE uses the ext4 file system for data.
Non-GPE uses f2fs for data.
Flashing GPT.bin is recommended, in my experience, when going from GPE to non-GPE and vicer versa.

audit13 said:
GPE = Google Play Edition
Non-GPE = Stock ROM
GPE uses the ext4 file system for data.
Non-GPE uses f2fs for data.
Flashing GPT.bin is recommended, in my experience, when going from GPE to non-GPE and vicer versa.
Click to expand...
Click to collapse
hello and thanks for your answers. sorry, i was sick for a few days and could not write back.
so my moto g has the google play app. is it a gpe? i have the original ....XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml...
have to flash or not gpt.bin?
thanks again

xodbx said:
hello and thanks for your answers. sorry, i was sick for a few days and could not write back.
so my moto g has the google play app. is it a gpe? i have the original ....XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml...
have to flash or not gpt.bin?
thanks again
Click to expand...
Click to collapse
OK guys, i did it without flashing bootloader and GPT and it works. Thanks for Helping me :good:

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.

Official stock firmwares added for xt1562,xt1563

http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Edit :Follow this thread for flashing http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750

Nice! Now we just need kernel source I believe then developers can get their hands dirty (well, after making a proper TWRP).

Hope so very soon

Thanks for the files.
@Devhux TWRP is already posted in original dev section.
Envoyé de mon XT1562 en utilisant Tapatalk

Fastboot Commands Full Path
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Fast link for xt1563 CA Default : https://mega.nz/#!qQZRDYAb!-W3iKudrm7xdxh2W6rdRSkDuc7142uP8zFRq8t2hPig

1st of all: thx for uploading!
secondly: the name of the original FW for the 1562 is called "XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC.xml.zip"
What about the "RETASIA" part, this kinda makes me wonder whether this might be intended for some kind of Asian version of the X. But I'm in Germany and also got the 1562. Will this work, regardless?
Best wishes derelektrischemoench

Which one of these is for the Wind variant XT1563?

noel_105 said:
Which one of these is for the Wind variant XT1563?
Click to expand...
Click to collapse
Flash the one i uploaded via mega works in all carriers,your in Canadian network right?

derelektrischemoench said:
1st of all: thx for uploading!
secondly: the name of the original FW for the 1562 is called "XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC.xml.zip"
What about the "RETASIA" part, this kinda makes me wonder whether this might be intended for some kind of Asian version of the X. But I'm in Germany and also got the 1562. Will this work, regardless?
Best wishes derelektrischemoench
Click to expand...
Click to collapse
im not 100 % sure if it will work

Hi @derelektrischemoench, I am based in France and got an X Play from retail and the original firmware does say RETASIA so I assume you should have no issue.
Full name is : 23.21.10.lux_retasia_ds.retasiaall.en.03 retfr
Build : LPD23.118-10

XMoDuLeSx said:
Flash the one i uploaded via mega works in all carriers,your in Canadian network right?
Click to expand...
Click to collapse
Thanks, yes Wind Mobile.

paugustin said:
Hi @derelektrischemoench, I am based in France and got an X Play from retail and the original firmware does say RETASIA so I assume you should have no issue.
Full name is : 23.21.10.lux_retasia_ds.retasiaall.en.03 retfr
Build : LPD23.118-10
Click to expand...
Click to collapse
Interesting, I've got my x play from retail as well here in Germany but mine says lux_reteu.reteu.en.EU reteu.
.... Whatever that means.

if you can help with stock firmware XT1563 DUAL SIM BRASIL, to with a rom stock not appear card slot !

amadeusmattos said:
if you can help with stock firmware XT1563 DUAL SIM BRASIL, to with a rom stock not appear card slot !
Click to expand...
Click to collapse
http://www.filefactory.com/file/5r5...D23.118-6.1_cid12_subsidy-DEFAULT_CFC.xml.zip
reflash this one and if it does't work flash this :
http://www.filefactory.com/file/4bi...D23.118-6.1_cid12_subsidy-MOVSTLA_CFC.xml.zip

XMoDuLeSx said:
http://www.filefactory.com/file/5r5...D23.118-6.1_cid12_subsidy-DEFAULT_CFC.xml.zip
reflash this one and if it does't work flash this :
http://www.filefactory.com/file/4bi...D23.118-6.1_cid12_subsidy-MOVSTLA_CFC.xml.zip
Click to expand...
Click to collapse
I tried and did not work! Does not work the slot! when I bought worked with the ORIGINAL STOCK ROM that came with unit , bought it in BRAZIL

can someone upload this to another place? i download at 24kbs from file factory.

Does anybody know why firmware for EU is missing? I guess I could use Asia one, but just in case I wanted to go back to stock.

I'm positive it was there before when thread was first posted. Maybe they were accidentally removed (just guessing)

Does anyone have a mirror for a XT1563 firmware ? Bandwith on FileFactory is horribly slow :/

vache said:
Does anyone have a mirror for a XT1563 firmware ? Bandwith on FileFactory is horribly slow :/
Click to expand...
Click to collapse
XMoDuLeSx said:
Fast link for xt1563 CA Default : https://mega.nz/#!qQZRDYAb!-W3iKudrm7xdxh2W6rdRSkDuc7142uP8zFRq8t2hPig
Click to expand...
Click to collapse
Was much faster for me. Filefactory was the worst download speed I've had since NetZero AOL dialup days.

XT 1643 Downgrade Nougat To Marshmallow (100% Future OTA not Brick Your Device)

First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.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 erase userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem

prakash27091987 said:
First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.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 erase userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem
Click to expand...
Click to collapse
Downgrading only boot and system caused messed up fingerprint. Used all commands except bootloader provided in other thread for downgrade and now everything's good.

I see that the bootloader is not being downgraded. Doesn't that mean OTAs might still brick your device?

Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk

this is not working means fingerprint problem comes

Silesh.Nair said:
Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
So are you saying that the bootloader was updated and if we do the OTA we might brick our phone?

I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
The point about bricks is regarding downgrade. In previous phones, downgrading from L to K, but keeping the L bootloader and then getting official L OTA would brick phone. Motorola has never supported downgrade on any phone. So if you downgrade, and later take OTA you could brick. Especially if running M with N bootloader.
The whole title of this thread is wrong - no way can anyone 100% guarantee no future brick.

Silesh.Nair said:
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Taking OTA to official N from soak test N is not an issue, the issue arises when someone took the N soak test, downgrade to M, OTA to official N.
tl;dr if i'm not wrong:
M -> Official N = No brick
M -> Soak test N -> Official N = No brick
Soak test N -> Downgrade to M -> OTA to official N = Brick

When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
You can say what you want but go read the G And X2 communities. EVERY user that updated to M then rolled back to L and later took an OTA back to M bricked. The OTA doesn't take into a count that the bootloader was a newer version - I don't remember the mechanics, but the OTA expected a different version of the bootloader.
Search XDA or the Internet for "Blank flash files" . The problem is downgrade related. If you take any upgrade, be prepared to stay on it. Do NOT downgrade.

Well, it may be true. I don't just blindly flash files on my device. I go thru the zip file to see what files are patched to make sure that I don't get into trouble. That need not be the case with all users.
Let's wait for the official OTA to be released and then we'll see how it goes.
Sent from my Moto G4 Plus using Tapatalk

ok guys ive just done some testing and ive found that whilst on official android 6.0 my bootloader version was (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13
then after upgrading to 7.0 soak test the bootloader version changed to (moto-msm8952-b1.00) with the date 2016-06-24
so after i then did the downgrade back to 6.0 marshamallow and the bootloader version downgraded back to its original (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13 so moral of the story is the bootloader does infact downgrade too and doesnt stay with the new android 7.0 bootloader like many seem to claim on this thread if u guys want to try this for yourself run this command to get your bootloader versions before update and after u updateto 7.0 & then 1 last time when u downgrade to 6.0 u will need to run the below command via adb fastboot
fastboot getvar version-bootloader

The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147

chromedome00 said:
The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
Click to expand...
Click to collapse
soo we cant take ota but we can install it manually that doesnt effect i think

does downgrading work if my device is brick??
does downgrading work if my device is brick??

sucssecfully downgraded from marshmallow after brick in nougat .........tons of thank
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....

drdhaval1987 said:
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....
Click to expand...
Click to collapse
dOWNGRADE process please

kemesh said:
dOWNGRADE process please
Click to expand...
Click to collapse
its already mentioned in this thread....simply follow the steps........

When I am trying to install the Nougat OTA zip file from within the stock recovery, it is giving me the following errors:
Code:
Verifying current system. . .
Mount count = 9
Last mount path = /system
Last mount time = 1479061757 -> Sun Nov 13 18:29:17 2016
Device was remounted R/W 9 times
Last remount happened on Sun Nov 13 18:29:17 2016
E1004: system partition fails to recover
E: unknown command [log]
E: unknown command [log]
E: Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I go about fixing this? I have followed your guide on how to downgrade and downgraded my XT1643 to -63 baseband.
Help please!

[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.