Database Users

upgrading to nougat

Hi all,
I am using xt1643. I installed nougat sock test rom and it is not providing options to update to final nougat rom. Current build npj25.75-2
I read in a thread that downgrading can cause problems. So, what should i do: downgrade to marshmallow and then upgrade via ota or directly flash final nougat rom??
Thanks in advance.

ankit.hinsu said:
Hi all,
I am using xt1643. I installed nougat sock test rom and it is not providing options to update to final nougat rom. Current build npj25.75-2
I read in a thread that downgrading can cause problems. So, what should i do: downgrade to marshmallow and then upgrade via ota or directly flash final nougat rom??
Thanks in advance.
Click to expand...
Click to collapse
The 75-2 soak test update is a dead end unless you were on the official soak test program. I've not seen any further updates captured to allow you to formally upgrade via OTA to the official Nougat (currently build 93-14).
You could explore either option though:
1) Downgrade to MM, do not flash gpt partitions or bootloader (omit those commands) - you may find a signed stock ROM here: http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 (and the associated guide for downgrading: https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-downgrade-nougat-to-marshmallow-t3487201). Then update via OTA to Nougat. You may prefer this to ensure that your update comes directly from Motorola. EDIT: note this method will void your warranty.
2) Flash via fastboot/RSDLite either the 93-11 Nougat update (v7.0, Nov 2016 security update) https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 and update to the latest version via OTA, or flash 93-14 (v7.0, Dec 2016) https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 This option is the more direct/less potential for things going wrong, it's up to you how much you'd trust the updates you flash. EDIT: This method does not appear to void your warranty.
With either option, back up your key data and be aware your settings and personal data may be erased in the process. Personally, I'd suggest a full wipe to limit the number of issues that may arise. Good luck though

You can now flash full stock roms with (the right) TWRP:
https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147
bootloader and partition table is not flashed with these zips

Hey @echo92 and @Droidphilev...
Can I use this method??
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296

ankit.hinsu said:
Hey @echo92 and @Droidphilev...
Can I use this method??
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Click to expand...
Click to collapse
No idea. Never done that. I use the flashable zips.

ankit.hinsu said:
Hey @echo92 and @Droidphilev...
Can I use this method??
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Click to expand...
Click to collapse
It appears to be the same method as one of the 93-11 methods I posted above: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Just bear in mind with using the 93-11 update to install it in India or somewhere we know that particular firmware has been released (and thus has an upgrade path to the latest 93-14 firmware) or download this 93-14 OTA update once you've updated to 93-11. https://forum.xda-developers.com/moto-g4-plus/how-to/ota-zip-update-npj25-93-14-t3539407

Thanks for the help....Followed the other link and successfully upgraded to Nougat full build 93-11 and then updated using OTA to 93-14.

Want to downgrade to an earlier 7.0

Since 7.0 came to the s7, I have been keeping up with the monthly updates the carriers push out but for the past couple of months I've been getting some terrible kernel wake locks and I've tried everything possible to prevent them but I can't find a solution. So my thought was downgrading to an earlier 7.0 where I didn't have that problem.
Now my question is: Has the bootloader been updated prior to the first 7.0 monthly update (march)? Because I've heard once the bootloader has been updated you can't go downgrade to an earlier bootloader and I've experienced a soft brick on my s7 edge while tried to downgrade to an earlier version of marshmallow and someone told me it was because of an update to the bootloader. The firmware i'm on now is G935W8VLU2BQH1 and I want to go down to G935W8VLU2BQB6 which is the first nougat update (march)

orlans21 said:
Since 7.0 came to the s7, I have been keeping up with the monthly updates the carriers push out but for the past couple of months I've been getting some terrible kernel wake locks and I've tried everything possible to prevent them but I can't find a solution. So my thought was downgrading to an earlier 7.0 where I didn't have that problem.
Now my question is: Has the bootloader been updated prior to the first 7.0 monthly update (march)? Because I've heard once the bootloader has been updated you can't go downgrade to an earlier bootloader and I've experienced a soft brick on my s7 edge while tried to downgrade to an earlier version of marshmallow and someone told me it was because of an update to the bootloader. The firmware i'm on now is G935W8VLU2BQH1 and I want to go down to G935W8VLU2BQB6 which is the first nougat update (march)
Click to expand...
Click to collapse
Just download rom from sammobile, you will have all the files for downgrading.

MS420 said:
Just download rom from sammobile, you will have all the files for downgrading.
Click to expand...
Click to collapse
I did that back in December while on 6.0.1 and odin failed then when rebooting I got a software error message

orlans21 said:
I did that back in December while on 6.0.1 and odin failed then when rebooting I got a software error message
Click to expand...
Click to collapse
Well, I downgraded from 7.0 to 6.0 but with twrp, so maybe it's not possible via odin, but I flashed many times nougat via odin, from april to february security patch, it always worked..

MS420 said:
Well, I downgraded from 7.0 to 6.0 but with twrp, so maybe it's not possible via odin, but I flashed many times nougat via odin, from april to february security patch, it always worked..
Click to expand...
Click to collapse
So then it's possible. As long as Samsung didn't update the bootloader between March and August then I should be good. Did you include BL in Odin when you downgraded to an earlier security patch?

orlans21 said:
So then it's possible. As long as Samsung didn't update the bootloader between March and August then I should be good. Did you include BL in Odin when you downgraded to an earlier security patch?
Click to expand...
Click to collapse
Yes.

MS420 said:
Yes.
Click to expand...
Click to collapse
Then they haven't updated it so far. When I wanted to go from 6.0.1 November security patch back to February security patch it failed and the phone went into a softbrick

orlans21 said:
Then they haven't updated it so far. When I wanted to go from 6.0.1 November security patch back to February security patch it failed and the phone went into a softbrick
Click to expand...
Click to collapse
Well, if you have custom recovery, you can downgrade to 6.0.1 very easy..

MS420 said:
Well, if you have custom recovery, you can downgrade to 6.0.1 very easy..
Click to expand...
Click to collapse
I've chosen not to root this phone so I just have stock recovery

What firmware for XT1681

Hey there !
I have a Moto G5 Plus International edition (XT1681) with firmware NPNS25.137-92-4 (latest January Patch).
I want to know what firmware to download from here (https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/) for factory flash not to get bricked like an idiot.
I don't know which one is good
Thanks

The last 2 ROMs are for your device, if you have a custom recovery I recommend to install the flashable version from this link .
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Here are the same version of your device NPNS25.137-92-4 (20180101 security patch)

Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/

CobraBoyFR said:
Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/
Click to expand...
Click to collapse
i didnt try to flash over a fastboot rom, maybe you cant do that.

Thanks
But basically, what I need is flashing full stock firmware (with recovery and kernel), no matter if it's january update or not. Just the factory images I had when I bought the phone. And I don't know what version is OK for my phone (XT1681 with NPNS25.137-92-4 now) 'cause I don't want to hard brick it when OTA updating (to Oreo for example)

From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.

RokCruz said:
From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.
Click to expand...
Click to collapse
Right now I'm on stock NPNS25.137-92-4, with TWRP recovery + Magisk root + ElementalX kernel
I'm not planning to flash any custom ROM for the moment. When the official Oreo update comes out, I want to update. But I know it won't go well if I OTA update it with my current configuration. That's why I want to be able to flash stock with fastboot (rough clean install), no matter what version I get : All i want is to be able to update to Oreo when it's out. Problem is, I don't know which image I need to download from here : https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I know it's there, but don't know exactly the good version.

This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.

RokCruz said:
This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.
Click to expand...
Click to collapse
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.

echo92 said:
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.
Click to expand...
Click to collapse
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?

RokCruz said:
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?
Click to expand...
Click to collapse
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).

echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
That was roughly what I figured out but damn, those explanations, thanks buddy :highfive:

The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.

driverdis said:
The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.
Click to expand...
Click to collapse
On xt1681 right?
Thanks for your feedback

echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
yeah i cant apply normal OTA over flashable rom. I was on NPN25.137-92(flashable) i download NPNS25.137-92-4(flashable too) i dirty flashed it and it works perfect without lose my stuff

I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.

jkl555 said:
I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.
Click to expand...
Click to collapse
Just to reply to myself for (2). I found the following link
https://www.stockrom.net/2017/05/st...g5-plus-xt1683-xt1681-android-7-0-nougat.html

From stock Oreo to custom ROM and back to stock Oreo???

I was on Oreo 85.13 pre-release...then I unlocked bootloader...and installed pixel experience...but meanwhile I formatted all data which ihave backed up..then I installed twrp flashable with June security patch zip..and I was on Android 7..then I flashed pixel experience..now..if I want to back on Oreo stock and to lock bootloader..what should I have To do...???I heard somewhere you need stock Oreo ROM zip where I can find one...???is that same one which we have used in manually updating to Oreo... please reply...

As far as I know the only stock Oreo zip we have is the OTA, which can't be used to flash firmware. We need the full firmware file before we're able to flash stock ROMs via fastboot.
Anyway, I'm also curious if there are any differences for the unlocking/flashing/backup process starting at the official Oreo we have now, and if going back to it later is the same as it is with Nougat.

The stock US OTA update can be found here: https://technoplanners.blogspot.com...tock-update-for-moto-g5-plus-OPS28.85-13.html
This can be side-loaded to upgrade after you've flashed Nougat with one caveat. Nougat has to be at Build number NPNS25.137-92. If your Nougat ROM has the June security patches (Build number NPNS25.137-93) you'll be SOL since the manifest specifies the pre-req for the update. So the fools at Motorola released the June update for Nougat, then released Oreo at the same security patch level and won't let you apply the update. Real geniuses.

nvrpayretail said:
The stock OTA update can be found here: https://technoplanners.blogspot.com...tock-update-for-moto-g5-plus-OPS28.85-13.html
This can be side-loaded to upgrade after you've flashed Nougat with one caveat. Nougat has to be at Build number NPNS25.137-92. If your Nougat ROM has the June security patches (Build number NPNS25.137-93) you'll be SOL since the manifest specifies the pre-req for the update. So the fools at Motorola released the June update for Nougat, then released Oreo at the same security patch level and won't let you apply the update. Real geniuses.
Click to expand...
Click to collapse
That's not quite correct; the build required for this Oreo OTA that's currently around is NPNS25.137-92-14 (June 2018 security patch for Brazil and Indian devices). The NPNS25.137-93-14 patch you mentioned is the June 2018 patch for EU, US and Asian devices, which means the Oreo patch for those devices isn't around yet.
To the opening poster, as previously mentioned, you will have to wait for the OPS28.85-13 stock fastboot ROM to be leaked. You must lock with a stock firmware as new or newer than your current bootloader. You cannot downgrade bootloaders via fastboot anyway and it's really not recommended to downgrade.

The US patch is available (Blur_Version.28.51.16.potter.retail.en.US.zip). It can be downloaded from the link I provided.
Correction: My bad. Didn't realize "92" indicated India and "93" indicated US. Evidently the referenced download is labeled wrong

Update to latest Android 9 Pie from Oreo 8.0.0

Hello i am on March 1, 2018 8.0.0 with Root and TWRP , what is the best way to update to the latest stock rom and not break my phone. Thanks a lot

Better update to Nov 2018 8.1

.:Addicted:. said:
Better update to Nov 2018 8.1
Click to expand...
Click to collapse
Can u tell me how to do that without losing my data? i have twrp and magisk installed, i know i have to reflash magisk but i just install the image from twrp and i am good to go ?

I would return to clean stock ROM of the same version as you're running (restore stock boot image or reflash the whole ROM) and let the OTA engine handle the selection of necessary updates. You might receive the latest full Pie ROM or it will update incrementally, hard to say

.:Addicted:. said:
Better update to Nov 2018 8.1
Click to expand...
Click to collapse
_mysiak_ said:
I would return to clean stock ROM of the same version as you're running (restore stock boot image or reflash the whole ROM) and let the OTA engine handle the selection of necessary updates. You might receive the latest full Pie ROM or it will update incrementally, hard to say
Click to expand...
Click to collapse
Best way is to flash with Mi Flash Tool?

bibos85 said:
Best way is to flash with Mi Flash Tool?
Click to expand...
Click to collapse
The best way is to use flashing script manually, as you should remove bootloader unlock/lock commands from it.