Database Users

XT-1644 Official Nougat Update?

My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png

You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.

echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?

waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612

echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.

waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.

Trouble flashing STOCK recovery

I am able to flash stock firmware with fastboot, however recovery.img and boot.img always fail with "(bootloader) image signed with key bad key"... doesnt matter if its 139.48-49-64 or the nougat soak test. I have xt1625 US retail, i made sure im using the correct non-amazon US firmware...
It boots up and runs properly, and i can install twrp... however, im unable to install the OTA updates without stock recovery, so im stuck on NPJ25.93-11 instead of 14
anybody have any similar issue?

That error with the boot.img and recovery.img, if I recall, usually shows up - provided after the warning the log says they were flashed okay, then you shouldn't have any problems, as you've experienced.
Yup, you cannot install any OTA updates from Motorola once you've modified your system - you need to be on stock recovery and system. Unlocking your bootloader is okay, but modifying your recovery, kernel, or any other part of your system may stop the OTA from installing. Your possible options are to re-flash the 93-11 update and download the 93-14 OTA if it's available in your region, or fastboot one of the 93-14 ROMs in the Guides section (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)

ourangashane said:
I am able to flash stock firmware with fastboot, however recovery.img and boot.img always fail with "(bootloader) image signed with key bad key"... doesnt matter if its 139.48-49-64 or the nougat soak test. I have xt1625 US retail, i made sure im using the correct non-amazon US firmware...
It boots up and runs properly, and i can install twrp... however, im unable to install the OTA updates without stock recovery, so im stuck on NPJ25.93-11 instead of 14
anybody have any similar issue?
Click to expand...
Click to collapse
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.

pastorbob62 said:
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
Click to expand...
Click to collapse
Likely fastboot'ed one of the Nougat images in the Guides section; I've not seen any mentions of OTA updates in the US either - Canada and Brazil appear to have received it thus far, hopefully the US isn't far behind!

echo92 said:
Likely fastboot'ed one of the Nougat images in the Guides section; I've not seen any mentions of OTA updates in the US either - Canada and Brazil appear to have received it thus far, hopefully the US isn't far behind!
Click to expand...
Click to collapse
That would be my guess as well. I don't get why some are so impatient to get Nougat that they risk flashing firmware not intended for their devices. Then they wonder why they are having issues. Oh well!

pastorbob62 said:
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
Click to expand...
Click to collapse
No, no update yet.... i just flashed the indian version from the forum..
echo92 said:
That error with the boot.img and recovery.img, if I recall, usually shows up - provided after the warning the log says they were flashed okay, then you shouldn't have any problems, as you've experienced.
Yup, you cannot install any OTA updates from Motorola once you've modified your system - you need to be on stock recovery and system. Unlocking your bootloader is okay, but modifying your recovery, kernel, or any other part of your system may stop the OTA from installing. Your possible options are to re-flash the 93-11 update and download the 93-14 OTA if it's available in your region, or fastboot one of the 93-14 ROMs in the Guides section (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Click to expand...
Click to collapse
Had i just used my eyes lol... Id been looking for a fastboot 93-14, i must have been way too tired lol.. thank you

Help - T Mobile OTA 7.1.2 Update fails with "Error" on Stock Android 7.1.1

Hi,
My 6P is on 7.1.1 Stock Android and I recently unlocked my bootloader, downgraded radio to 3.72 from 3.78 since 3.78 radio was giving LTE issues on T-Mobile. And yesterday, I saw the OTA 7.1.2 update message, so I tried to install, but after re-start, around 30% through the installation process, it suddenly aborts to "Error!". The update availability message again appeared this morning, only to error out again the same way.
I didn't see anyone having similar issue, so wanted to post here to see what could I do.
Thanks

solluidforever said:
Hi,
My 6P is on 7.1.1 Stock Android and I recently unlocked my bootloader, downgraded radio to 3.72 from 3.78 since 3.78 radio was giving LTE issues on T-Mobile. And yesterday, I saw the OTA 7.1.2 update message, so I tried to install, but after re-start, around 30% through the installation process, it suddenly aborts to "Error!". The update availability message again appeared this morning, only to error out again the same way.
I didn't see anyone having similar issue, so wanted to post here to see what could I do.
Thanks
Click to expand...
Click to collapse
OTAs will not install if you have changed any partition. Think of OTAs like a puzzle piece. You can change one side of the puzzle piece by cutting it off to suit your needs, however you have effectively ruined the possibility of the next piece fitting into where you cut off.
Download the Full OTA Image and ADB sideload the OTA. This is the only present form of "OTA" that will install over any user modifications done to the phone. This process will not wipe your phone.
https://developers.google.com/android/ota
Sent from my Nexus 5X using Tapatalk

Thank you. Someone on reddit suggested another option of flashing the radio image for 3.78(which was the one for 7.1.1) and then to try the OTA - Luckily, he uploaded the 3.78 radio image file on gdrive, so I pulled it and succesfully was able to update to 7.1.2.
The issue is that as observed in other threads, only 3.72 radio is the only temporary radio image file which lets me have stable LTE connection on T-Mobile. So, if I want to flash back 3.72 radio image now, for future update I realize that I need to have a 3.81(tied to 7.1.2 build) raido image file as backup. Can you let me know if it's easy for a newbie to understand how to obtain the radio image file? I downloaded 7.1.2 (N2G47J) file from the URL you provided, and it contains radio.modem.img file. Is that it?

I was in the nexus 6p beta program. I am currently suffering the GOOGLE boot loop. Current build on the phone is N2G47i. Out of no where , the phone froze , reboot and just got stuck and never boot pass the GOOGLE boot screen.
I tried to ADB Sideload , but it would not take any file , be it OTA or FUll image that is older than March 8 , as the N2G47i build. is new than the official build. There is no new build newer than March 8 as far as i can tell. My phone is stock non root and bootloader locked. If anyone can assist , I would appreciated.

solluidforever said:
Thank you. Someone on reddit suggested another option of flashing the radio image for 3.78(which was the one for 7.1.1) and then to try the OTA - Luckily, he uploaded the 3.78 radio image file on gdrive, so I pulled it and succesfully was able to update to 7.1.2.
The issue is that as observed in other threads, only 3.72 radio is the only temporary radio image file which lets me have stable LTE connection on T-Mobile. So, if I want to flash back 3.72 radio image now, for future update I realize that I need to have a 3.81(tied to 7.1.2 build) raido image file as backup. Can you let me know if it's easy for a newbie to understand how to obtain the radio image file? I downloaded 7.1.2 (N2G47J) file from the URL you provided, and it contains radio.modem.img file. Is that it?
Click to expand...
Click to collapse
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Good luck...
510jungleboy said:
I was in the nexus 6p beta program. I am currently suffering the GOOGLE boot loop. Current build on the phone is N2G47i. Out of no where , the phone froze , reboot and just got stuck and never boot pass the GOOGLE boot screen.
I tried to ADB Sideload , but it would not take any file , be it OTA or FUll image that is older than March 8 , as the N2G47i build. is new than the official build. There is no new build newer than March 8 as far as i can tell. My phone is stock non root and bootloader locked. If anyone can assist , I would appreciated.
Click to expand...
Click to collapse
Hello... Isn't N2G47H newer than N2G47I ?
Try sideloading 7.1.2 public release: https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
Supposed to be the latest...
If the above doesn't work, try factory reset from recovery. If your bootloader is unlocked, you can try to flash a full stock image from Google site: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
If nothing work, you should likely think about RMA your device.
Good luck...

5.1 said:
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Good luck...
Hello... Isn't N2G47H newer than N2G47I ?
Try sideloading 7.1.2 public release: https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
Supposed to be the latest...
If the above doesn't work, try factory reset from recovery. If your bootloader is unlocked, you can try to flash a full stock image from Google site: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
If nothing work, you should likely think about RMA your device.
Good luck...
Click to expand...
Click to collapse
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.

510jungleboy said:
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
Click to expand...
Click to collapse
Ok. Got it. Well... I guess you have to wait next month if you don't want to RMA. Sorry...
Good luck...

510jungleboy said:
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
Click to expand...
Click to collapse
If you still have a warranty you should RMA your device. Doing a stock OTA update when you are fully on stock with no modifications shouldn't boot loop your phone unless there is something wrong with it. These phones have serious build issues that cause them to permanently bootloop, seemingly out of nowhere. From what I've read people don't generally recover from the type of boot loop you are describing but good luck. If the phone isn't under warranty it's likely time for a new one. The 6P doesn't seem to last very long past the expiration of the warranty.

Thanks for the link
5.1 said:
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Click to expand...
Click to collapse
Hi, thanks for the url, that is really helpful. Also, I realized that, the file is also available in the unzipped version of Nexus 6P Image file. So, it was helpful for me to learn alternatives along with process. :good:

Which stock firmware should I use for an XT1687?

I see over a dozen different versions here but I'm not sure which one to download:
https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I've already tried two different ones but I receive no cell signal when it boots.
Any ideas?
Thanks!

I actually found the answer on my own: none of them. Wrestling with the G5 this morning made me lose my mind. I ended up with the Pixel ROM.

Does anyone have a copy of the XT1687 stock rom (carrier unlocked ... I bought mine at Costco)? I could really use it.
My phone is totally messed up. My /system is empty except for 'bin'....
Thank you for any help!

I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml

dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
did going back to stock and accepting the OTA work for you??!

roydhritiman said:
did going back to stock and accepting the OTA work for you??!
Click to expand...
Click to collapse
I ended up with some kind of error with the OEM partition, but in the end all of the details on my settings screen show that I'm on the latest security patch, kernel, etc.

dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
dunderball said:
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?

dlong said:
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
Patches, a full ROM is rarely sent as an OTA. You'll know it's a full ROM if the size of the OTA is greater than 1GB. Anything less than say 300-400MB is patches to the system

dlong said:
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
I went from version 83 to successful OTA 92 (November patch), then to 93 January patch (but ended up with a failure message after booting up for whatever reason). I'm on retus, baseband M8953_37.46.07.47R POTTER_NA_CUST, build number NPNS25.137-93-4.
As far as I see, I don't see any full stock firmware out for NPNS25.137-93-4 which is unfortunate. I have a feeling my update to Oreo will fail if it ever comes out. I'm not even sure why my OTA fails, as I do my best to avoid modifying any partitions and mostly use systemless modules through Magisk. Whatever though.

No joy. So apparently, since I'm on NPN25.137-92 (POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), I wasn't able to downgrade to (POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
I did re-flash everything and the results seems to be the same (unable to 'see' new updates). I am on November 2017 patch but when I check for upgrades, it states the system is up to date.
I hope that because my phone is 'unlocked from store (Costco - USA)' that RETAIL is the correct firmware. Anyone know for sure?
Also... I guess I wiped recovery when I installed TWRP. Is there an OEM recovery.img available for Moto 5G Plus?
Edit: So the whole reason, I originally rooted my phone was so that I can enable Hot Spot by adding net.tethering.noprovisioning=true to /system/build.prop (now I wonder if root is even required to do that?)

Another question about Soak Test?

Hello everyone, so after flashing the current soak test with recovery stock(OPJ.28.108) i unlocked bootloader and flashed magisk 17.1 (which updated to 18.0 recently).
With TWRP in order to avoid any issues, i deleted the ota app from /priv-app and flashed 8.1 aroma gapps, stayed in stock kernel, due to sources not available yet.
How will i update to newer soak tests or final release when they come? Can i flash them with MinimalADB Fastboot? @Jleeblanch's TWRP Flashable one, uses 7.0 Firmware, from what i know.

Now that you've unlocked your bootloader, you can fastboot flash the stock firmware from this thread to return to the stock firmware. However, you may get errors when fastboot flashing the bootloader.img or gpt.bin (partition table), probably saying you can't downgrade or something along those lines.
If a newer version of the soak test or an official version becomes available, you should be able to easily update, but we won't know for sure until that time comes.
In my thread there is a TWRP flashable version of Stock 7.0 and the Oreo soak test 8.1.0, just so you know.

Jleeblanch said:
In my thread there is a TWRP flashable version of Stock 7.0 and the Oreo soak test 8.1.0, just so you know.
Click to expand...
Click to collapse
Oh really? Thanks for the help dude!

If previous soak tests have been anything to go by, we'll likely have to wait for the next soak test update to be leaked. Motorola only releases soak test updates to those users that have applied to its soak test program. If you've flashed the soak test from XDA, Motorola won't send you an update, so we'd have to wait for someone on the test program to provide a copy of said update/updates. However, the aforementioned TWRP versions of the soak test should be updated if we can find the next soak test update.

Guys, quick question, after a soak test begins, how long can we expect before a final version?

Edduardoa said:
Guys, quick question, after a soak test begins, how long can we expect before a final version?
Click to expand...
Click to collapse
About 2-3 months if the soak test doesn't encounter significant or serious bugs - from how long previous soak tests have taken. Expect the release to take longer if there are serious bugs or ones that are hard to fix.
Unless you're part of the soak test itself, there's no guarantee we'll see soak test updates between now and the final release. It depends on whether someone can capture them and leak them to XDA.

Jleeblanch said:
However, you may get errors when fastboot flashing the bootloader.img or gpt.bin (partition table), probably saying you can't downgrade or something along those lines.
Click to expand...
Click to collapse
Which one is the safer downgrade? Yours TWRP Flashable or Fastboot ignoring the "oem_lock" commands? I'm currently with the Oreo ROM, Partition and Bootloader.

xSamukaBRx said:
Which one is the safer downgrade? Yours TWRP Flashable or Fastboot ignoring the "oem_lock" commands? I'm currently with the Oreo ROM, Partition and Bootloader.
Click to expand...
Click to collapse
Though I've not tried this, I think the TWRP flashable would be the safer bet, given TWRP doesn't affect the bootloader or GPT. Furthermore, OTA updates with this set up may likely fail to install before they did any damage to your device.
However, I'm not sure if downgrading in this manner may cause you to lose IMEI or SIM usage, so you may wish to read up on a few of the IMEI threads on this forum before proceeding.

So installing a twrp flashable soak test won't effect/upgrade the bootloader?
If that's the case what if I actually wanted to do that using twrp?

Henry Markle said:
So installing a twrp flashable soak test won't effect/upgrade the bootloader?
If that's the case what if I actually wanted to do that using twrp?
Click to expand...
Click to collapse
Shouldn't do, since TWRP doesn't appear to have the security authorisation to write to the bootloader or GPT.
By the same thought, you'd have to fastboot flash the GPT or bootloader. However, fastboot may not let you flash an older bootloader/GPT (e.g. from Oreo to Nougat) and block you reporting a security downgrade error. This, I don't think you can downgrade your bootloader or GPT

echo92 said:
Though I've not tried this, I think the TWRP flashable would be the safer bet, given TWRP doesn't affect the bootloader or GPT. Furthermore, OTA updates with this set up may likely fail to install before they did any damage to your device.
However, I'm not sure if downgrading in this manner may cause you to lose IMEI or SIM usage, so you may wish to read up on a few of the IMEI threads on this forum before proceeding.
Click to expand...
Click to collapse
@xSamukaBRx, as @Jleeblanch mentioned, that the TWRP flashable Stock ROMs don't have "fastboot erase modemst1" and "fastboot erase modemst2", so you won't lost IMEI.
If you have never touched your persist partitions, then even if you lose IMEI, it can be fixed so no worries about that. However, I would strongly recommend to take EFS backup right now as your device shows IMEI in settings i.e you have a working efs now.
Edit: As @echo92 mentions in the next post, that OTA updates will erase modemst1 and mdoemst2.
I would recommend it is better to fix persist now since everything if working fine to avoid imei problem in future altogether.
Nobody knows what Official Oreo would do to the persist. In the worst case there might be some restriction which would prevent us from fixing/changing persist.

Heeth21 said:
@xSamukaBRx, as @Jleeblanch mentioned, that the TWRP flashable Stock ROMs don't have "fastboot erase modemst1" and "fastboot erase modemst2", so you won't lost IMEI.
If you have never touched your persist partitions, then even if you lose IMEI, it can be fixed so no worries about that. However, I would strongly recommend to take EFS backup right now as your device shows IMEI in settings i.e you have a working efs now.
Click to expand...
Click to collapse
In addition to the good points made above, try to avoid flashing the Nougat stock ROM (not referring to the TWRP flashable) and use OTA updates if you were previously on stock Oreo. Besides the possible risk of hard bricking, many if not all the OTA updates we have erase modemst1/modemst2 (your EFS, I think) as part of their update script, then rebuild modemst1/st2 on the next boot. Thus, you may then lose IMEI as your baseband and other partitions become mismatched and then you may have to try the persist repair.