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.

Unroot and Flash OTA update

i have my Mi a1 rooted with Twrp 3.1.1 with Magisk on november 6 2017 security patch , How do i flash ota update after i unroot my phone please help.

It won't be possible, since you flashed TWRP... System should be completely unmodified. Only method I know to get ota from your point is to clean flash newest stock image. And after that I would recommend to flash magisk only, without any Custom recovery.

lmfao009 said:
It won't be possible, since you flashed TWRP... System should be completely unmodified. Only method I know to get ota from your point is to clean flash newest stock image. And after that I would recommend to flash magisk only, without any Custom recovery.
Click to expand...
Click to collapse
how do i do it without losing my data can you pls explain im kinda noobi

Here's the link http://en.miui.com/download-333.html
The latest oficial ROM is oreo January security patch. You need flash manually and wait for february security patch.

Code:
ltf_195 said:
Here's the link
The latest oficial ROM is oreo January security patch. You need flash manually and wait for february security patch.
Click to expand...
Click to collapse
but This will be a Direct update from November 6 17 patch to January Update , wont it brick my phone ?

Kamran47 said:
Code:
but This will be a Direct update from November 6 17 patch to January Update , wont it brick my phone ?
Click to expand...
Click to collapse
Hi, did you flashed the stock rom?
Did you have any issue about the phone was rooted before flashing?
Thank you.

If you are in India , you can go to xiaomi service centre & ask for re-flashing the full software which will automatically unroot your phone & you can install ota updates . They will charge Rs 180 for it

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

Moto g5 plus stock ROM

I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).

kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.

Thanks for the response
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.

psychopac said:
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Click to expand...
Click to collapse
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.

kash664 said:
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
Click to expand...
Click to collapse
Make sure to follow the flashing instructions mentioned by the thread OP properly

psychopac said:
Make sure to follow the flashing instructions mentioned by the thread OP properly
Click to expand...
Click to collapse
Yes. Hope everything turns out fine

kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
I hope i can help !!

vishalrickz said:
I hope i can help !!
Click to expand...
Click to collapse
Sure sir

Galaxy S8+ G955F stuck on Oreo July's patch

Hi, thanks for reading. My S8+ G955F stopped finding updates after 2018 July's security patch, when I try to search for updates manually it says that the device is up to date already (its 2019 April's 20th today).
I never flashed a custom ROM, it's 100% stock and Knox is intact.
I wonder if there is a way to just update with Samsung official tooling or just flash with TWRP the OneUI Pie official ROM without having to go through every update to date manually (there must be dozens of them).
I attached my current build and firmware below.
Thanks for reading and have a great day.

xRaevyn said:
Hi, thanks for reading. My S8+ G955F stopped finding updates after 2018 July's security patch, when I try to search for updates manually it says that the device is up to date already (its 2019 April's 20th today).
I never flashed a custom ROM, it's 100% stock and Knox is intact.
I wonder if there is a way to just update with Samsung official tooling or just flash with TWRP the OneUI Pie official ROM without having to go through every update to date manually (there must be dozens of them).
I attached my current build and firmware below.
Thanks for reading and have a great day.
Click to expand...
Click to collapse
You could try first Samsung's Smart Switch to see if that will update your phone.
If not the other way would be to download your firmware and flash with Odin.

spawnlives said:
You could try first Samsung's Smart Switch to see if that will update your phone.
If not the other way would be to download your firmware and flash with Odin.
Click to expand...
Click to collapse
having the same issue . do you need to go update by update if you decide to install by odin? or can you just pick the last version and install it?

zoiden said:
having the same issue . do you need to go update by update if you decide to install by odin? or can you just pick the last version and install it?
Click to expand...
Click to collapse
No you don't need to do incremental updates
Just update to the version you want