Related
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!
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? .
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.
#WeirdMoto
Motorola started rolling out September security patch which, you know, fixes Blueborn vulnerability. But instead of starting in India or other Moto's favorite country, they stated rolling it out in Latin America!
Changes:
-September security patch
-Bug fixes
Here you go! https://mega.nz/#!OU10kJAD!V2eW4QoXuGjzlLlct4NG-eQ5NvLru9em0aG8_CrSA9o (sorry because of Mega lol)
Thanks,can someone upload a twrp backup?
Can I flash if my device is rooted and I have TWRP?
ElGranLagarto said:
Can I flash if my device is rooted and I have TWRP?
Click to expand...
Click to collapse
No
ElGranLagarto said:
Can I flash if my device is rooted and I have TWRP?
Click to expand...
Click to collapse
Unlikely - the OTA would possibly fail and also leave you in a TWRP soft bootloop unless you booted to bootloader and then selected 'Start' to boot to system.
As this OTA will only flash on NPJS25.93-14-8 systems (looking at the updater script), the easiest way would be to use the NPJS25.93-14-8 stock ROM to revert to a fully stock device. Of course, this will remove root and TWRP on your device, but OTAs require a clean, unmodified device to work from.
Assuming you are currently on NPJS25.93-14-8 and were fully updated before flashing TWRP and rooting, you may be able to use the following flashing commands with the fastboot stock ROM to revert to stock without affecting your data. These commands are edited assuming your GPT and bootloader are the same patch level as NPJS25.93-14-8. As always, back up your data in case you need to factory reset, and also this depends on your device being formally and fully updated to NPJS25.93-14-8 previously, if not formally updated (including bootloader to B1:06), you may run into issues including a hard brick. If you are not sure, ignore the following flashing commands and fully flash the NPJS25.93-14-8 stock ROM as per in the linked post. Or wait for the TWRP flashable of the NPJS25.93-14-10 system ROM (which only flashes the system side of the build).
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 cache
fastboot reboot
The stock ROM for the NPJS25.93-14-8 build is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
A formally updated system to NPJS25.93-14-8 should include:
Bootloader version at B1:06.
Modem version ending in 62.01R.
Security patch at 1 June 2017.
After this, you should be able to update to NPJS25.93-14-10 via OTA. Needless to say, after you update via OTA, it therefore becomes risky to flash the June 2017 stock ROM or any older ROMs. As we've seen previously, downgrading and then attempting to update via OTA runs a high risk of hard bricking, and it may be the case that the June 2017 blankflash we have no longer works once updated to September 2017. Be careful. If you need to revert back to stock after flashing the September 2017 OTA, wait for the NPJS25.93-14-10 stock ROM.
EDIT - I saw from your previous posts asking about the NPJ25.93-14-8.1 update. If you've updated from NPJ25.93-14 to NPJS25.93-14-8.1, you likely won't be able to flash this update anyway as the expected build is different to what the NPJS25.93-14-10 update is expecting.
For NPJ25.93-14-8.1:
Code:
Package expects build thumbprint of 7.0/NPJ25.93-14-8.1/2:user/release-keys or 7.0/NPJ25.93-14/16:user/release-keys
For NPJS25.93-14-10:
Code:
Package expects build thumbprint of 7.0/NPJS25.93-14-10/10:user/release-keys or 7.0/NPJS25.93-14-8/8:user/release-keys
Successfully installed in my XT1641 with NPJS25.93-14-8. Thanks for capture and upload it.
Hallo, my phone (XT1643) isn't rooted and is NPJS25.93-14-8 running. Is it possible to put the updatefile into the internal storrage and flash it with orig. Motorola Recovery?
How can apply this OTA
How can apply this OTa patch to my Moto g4 plus ...and now my build number is NPJS25.93-14-8 hope it works fine after update this OTA. And let me know how I can apply this OTA
Marv42 said:
Hallo, my phone (XT1643) isn't rooted and is NPJS25.93-14-8 running. Is it possible to put the updatefile into the internal storrage and flash it with orig. Motorola Recovery?
Click to expand...
Click to collapse
Niket03 said:
How can apply this OTa patch to my Moto g4 plus ...and now my build number is NPJS25.93-14-8 hope it works fine after update this OTA. And let me know how I can apply this OTA
Click to expand...
Click to collapse
Similar steps should apply to you both - verify that you have NPJS25.93-14-8 fully updated on your device (e.g. bootloader is version B1:06) and everything is stock and not modified - so no TWRP, root, or custom logo.bin for example. Your recovery should also be the same version that came with the NPJS25.93-14-8 stock ROM/OTA update. Having an unlocked bootloader is not a problem, though if it is unlocked, you should be seeing the unlocked bootloader warning when you boot (from a stock logo.bin).
1)Download the OTA update to your device, likely it'll be in the Downloads folder.
2)Follow these instructions to get to the stock recovery:https://forum.xda-developers.com/showpost.php?p=72981796&postcount=58
3)Once in the stock recovery, select the 'Apply update from SD card' command with the volume keys, press power to use the command.
4)Navigate to your Download folder and find the update.
5)Press power whilst the update is selected to install.
5a)If there's an issue with mounting internal memory, you may try the 'Mount /system' command and attempt to re-select your update.
6)Once the update is finished, you may wish to 'Wipe cache' from the recovery menu. You do not have to factory reset.
7)Once done, you can choose to reboot.
If you choose, you can wait for the OTA update to arrive, which should automate the process for you.
As always, once you've updated, it becomes very risky to downgrade. I'd suggest not to downgrade from the September 2017 stock update if you can (with an older stock ROM), or if you really want to, do not update via OTA. Use an updated stock ROM (Sept 2017 fastboot ROM, which currently we don't have yet) to update if you've downgraded.
Thanks! Applied successfully on my Moto G4 XT1624. Working great as always.
Firmware
Firmware Patch -10
rsdsecure-cloud.motorola.com/download/ATHENE_NPJS25.93-14-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Any changes !!!!! ... It says bug fixes so ......
Updated via OTA in India.
well I am rooted with magisk and custom kernel installed. and I got OTA for updating it, so should I update it via OTA or flash it through fastboot?
Fastboot
siddhesh9146 said:
well I am rooted with magisk and custom kernel installed. and I got OTA for updating it, so should I update it via OTA or flash it through fastboot?
Click to expand...
Click to collapse
You need full stock setup for flashing via an OTA, else it'll fail — that includes recovery, kernel and the ROM. In addition, you can update only a full stock ROM through fastboot, not an OTA.
zeomal said:
You need full stock setup for flashing via an OTA, else it'll fail — that includes recovery, kernel and the ROM. In addition, you can update only a full stock ROM through fastboot, not an OTA.
Click to expand...
Click to collapse
I already flashed it from fastboot; thanks for your help!
siddhesh9146 said:
I already flashed it from fastboot; thanks for your help!
Click to expand...
Click to collapse
Siddesh how to update please tell me
---------- Post added at 11:19 AM ---------- Previous post was at 11:19 AM ----------
siddhesh9146 said:
I already flashed it from fastboot; thanks for your help!
Click to expand...
Click to collapse
Send me d link of stock rom of September patch
usha55 said:
Siddesh how to update please tell me
---------- Post added at 11:19 AM ---------- Previous post was at 11:19 AM ----------
Send me d link of stock rom of September patch
Click to expand...
Click to collapse
Link for the September 2017 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
If you wish to update and try to save your data (provided you were on an earlier stock Motorola build), have a look at the flashing commands in this post: https://forum.xda-developers.com/showpost.php?p=73970028&postcount=251 Else, you'll have to use the flashing commands in the main thread, which will wipe your data, so back up as required. You do not have to relock your bootloader if you do not wish to.
anyone tell me please if i lock oem now can i get normal updates from only im fed up of doing this fastboot,,and 1 more qstion if i lock my bootloader/oem can i unlock it again
---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------
why because im a hard brick survivor ,now if i unlock oem/bootloader i can update my phone normally from system updates
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
anuone reply me guys
I take no credit for this, thank the Motorola-Firmware-Team on Android File Host, and you can follow any leaked firmware on their Twitter feed.
I no longer have a Moto X Pure Edition, so I can't personally vouch for this firmware, but it seems like it is a totally legit full factory firmware image of Nougat NPH25.200-22 for flashing in fastboot.
This is the "official" full factory image of Nougat NPH25.200-22 and NOT the OTA file. It can be used for a clean flash and to relock the bootloader which is recommended to pass SafetyNet API checks if you are planning on staying stock and not rooting.
Flashfile.xml shows: version="clark_retus-user 7.0 NPH25.200-22 21 release-keysM8992_1255331.29.01.88.09R", MD5 matches, and all dates are correct.
This is ONLY for the Moto X Pure Edition, Retail US (RETUS) variant. I have no information on any other firmware or device.
Tested and verified as official Nougat factory ROM image by @Andromendous
This image is NOT flashable in TWRP, like all factory images it is flashed with fastboot in the bootloader... How to flash:
Code:
fastboot oem lock begin (if wanting to re-lock bootloader, othewise use `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 system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
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 lock (only if you used `fastboot oem lock begin`, otherwise end with `fastboot oem fb_mode_clear`)
fastboot reboot
See https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 for detailed instructions
Downloads
Original source: https://androidfilehost.com/?fid=889964283620765304
Google Drive mirror: [removed]
@acejavelin: Since you have been one of the guru's on this phone, can this file be flashed in fastboot directly if I am on stock MM android December update rooted with Magisk and TWRP installed? I just want to make sure that when I am ready to take the plunge, I can take the minimal work procedure since I factory wipe after all major updates anyway.
Does this mean people who haven't received 7.0 OTA can flash this ROM and get Nougat without any complications such as corrupted bootloader and stuff? Also read multiple times that downgrading to 6.0 and again upgrading to 7.0 via OTA corrupts the bootloader leading to hard brick (which is now solver using external SD), will flashing this would solve this too?
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
acejavelin said:
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
Click to expand...
Click to collapse
Great! I plan on holding on to this phone for about another 6 months or so and might as well get the update. Will probably go over to stock nougat in December. Custom ROMs just always seem to have at best some minor issue(s) that prevents me from sticking with them.
Dude Ace you are the f-ing man. Thanks for the find.
I flashed it manually while on Hashbangs LOS rom. I was stuck on 6.0 modem and tried to just flash the modem, which made me lose sim service. I then flashed the entire imagine manually and booted just fine.
Now I'm back to LOS with 7.0 modem and so far so good. Hashbang is doing a great job, he's already cleaned multiple bugs just today.
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
schneid said:
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
Click to expand...
Click to collapse
It's a factory image... Have to flash each piece manually with fastboot, this is not a flashable TWRP or other recovery image
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
We don't know that for sure... NPH25.200-22 is what has been rolling out to Sprint, T-Mobile, and AT&T devices, but it seems that Verizon users are getting NPH25.200-23 according to one verified (via screen shot) report on Lenovo's official forum.
The issue is we know the Moto OTA server keeps track of what device get's what version, if you flash this it won't know you have it so if a future OTA update comes out, you might be offered it via push and will have to wait until it's available by pull.
andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
Yes. There's a huge difference. With this you wont brick your phone.
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
CLETjB said:
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
Click to expand...
Click to collapse
Yes, you can relock... unless you have already applied NPH25.200-23, otherwise you should be able to relock from ANY version out there currently.
We don't know what's up with NPH25.200-23 for sure though... recently Moto has been doing "different" versions for Verizon users that don't seem to get to anyone else, we also see it in the Moto G5+, and we don't know the differences either. Most likely it's just a minor VZW specific change and can be ignored. If the update does get pushed later, you should have no issues taking the OTA update when on this firmware, it is the official factory image.
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
ghitus said:
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
Click to expand...
Click to collapse
As I stated in the first post... no, I have idea or information about any other images for other variants and I suggest following MotoFirmware123 on Twitter as that is the best place to find leaked firmware. Motonovo has gotten very tight on letting firmware get out, but if it becomes available this is likely where it will come from, IF it ever gets leaked.
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Oaklands said:
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Click to expand...
Click to collapse
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
acejavelin said:
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
Click to expand...
Click to collapse
Thank you. His phone is now ready.
Finally !Thanks, man!
Now I just flash via fastboot and avoid all the OTA updates process.
you are the man!