Hello Moderators,
My Device Model : XT 1644 64 GB variant
Current Rom: Lineage OS
Bootloader Status: Unlocked
Since the US variant didn't get the nougat update, I decided to unlock my bootloader and switch to a CM based ROM.Though I love it I've been facing a lot of issues in fingerprint sensor and advanced settings
Now I'd like to go back to my stock ROM and I've few doubts
1. If I don't lock my bootloader again after switching to stock ROM will I be still eligible to receive the official updates?
2. This link to stock ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 says that it's for the Indian version will it work on the US versions?
3. After flashing the stock ROM will it be okay if I follow this thread and update to nougat https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943?
4.Does the soak test have any bugs?
5.If I'm on the soak test and Once the official nougat is available for my device what should I do?
I have a twrp backup of my stock ROM too
Click to expand...
Click to collapse
@rahulsnair @1chrome
Thanks for taking your time to help me out !!! I'd surely love to return the favour someday
Vijay Selvaraju said:
Hello Moderators,
My Device Model : XT 1644 64 GB variant
Current Rom: Lineage OS
Bootloader Status: Unlocked
Since the US variant didn't get the nougat update, I decided to unlock my bootloader and switch to a CM based ROM.Though I love it I've been facing a lot of issues in fingerprint sensor and advanced settings
Now I'd like to go back to my stock ROM and I've few doubts
1. If I don't lock my bootloader again after switching to stock ROM will I be still eligible to receive the official updates?
2. This link to stock ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 says that it's for the Indian version will it work on the US versions?
3. After flashing the stock ROM will it be okay if I follow this thread and update to nougat https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943?
4.Does the soak test have any bugs?
5.If I'm on the soak test and Once the official nougat is available for my device what should I do?
@rahulsnair @1chrome
Thanks for taking your time to help me out !!! I'd surely love to return the favour someday
Click to expand...
Click to collapse
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way
echo92 said:
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way
Click to expand...
Click to collapse
Thanks a lot bro @echo92
I actully followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 these steps now I'm running on stock nougat
Just omitted the bootloader unlock part since you told me that I'll be receiving updates even if the bootloader is unlocked
echo92 said:
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way
Click to expand...
Click to collapse
Thanks a lot bro @echo92
I actully followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 these steps now I'm running on stock nougat
Just omitted the bootloader unlock part since you told me that I'll be receiving updates even if the bootloader is unlocked
Related
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.
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
inFiniTyz_Z said:
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
Click to expand...
Click to collapse
If you wish to simply re-lock your bootloader, the easiest thing is to flash this fastboot stock ROM (which is Nougat) and use the locking script as directed in the first post. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this may wipe your data - so back up, and the relocking may or may not work, in which case you may have to wait for a more up to date fastboot stock ROM to become available.
If you were to downgrade to Marshmallow, you cannot downgrade your bootloader and GPT partitions, at best, your existing bootloader would try to prevent you from downgrading those partitions. At worst, you'll brick your device again if you were to flash those - though we've got possible ways of fixing that, it's not a route I'd want to go down. Flashing the rest of Marshmallow is no problem, however, ensure you have the correct MM firmware for your device and territory.
Will this version work for my country(Germany) without OTA trouble?
inFiniTyz_Z said:
Will this version work for my country(Germany) without OTA trouble?
Click to expand...
Click to collapse
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
echo92 said:
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
Click to expand...
Click to collapse
THANK YOU IT WORKED AND THE WARNING DISAPPEARED. I am on Nougat, locked and its working like a charm
I WOULD KISS YOUR BUTT IF ITS HAVE TO BE
I am having xt1686 indian variant .. i unlocked the bootloader and installed the custom roms.. now while going back to stock i mistakenly installed NPNS (US VARIANT, I suppose) ..
I am unable to install the NPN version now .. i guess the bootloader is not matching ..
Right now i am having a bootloader - C0.8(*) in NPNS ...
PLEAAE SUGGEST HOW TO MOVE TO INDIAN VERSION OF NPN... THNKS..
S does not mean US or any other variant specific build... there are literally different builds for different variants. My US Retail version is NPN25.173-83
In previous Moto models, the S meant it had been upgraded from an OTA, but in looking in my current device it has received several OTAs and does not have the S, so either that has been depreciated or our original assumptions in earlier models was incorrect.
Either way, the fact the S is there does not mean US (or any other country), just a slightly different build... I don't have an answer of why you can't go back though.
https://forum.xda-developers.com/g5-plus/help/npns-nps-firmware-t3677576
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
abhi.a3s said:
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
Click to expand...
Click to collapse
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. If you've flashed a NPNS firmware, you'd likely be at least on the may security patch. The Indian firmware you'd need is the January patch (NPN25.137-15, as I don't think the NPN25.137-67 or 67-5 firmwares have been leaked). Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
echo92 said:
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
Click to expand...
Click to collapse
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
abhi.a3s said:
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
echo92 said:
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Click to expand...
Click to collapse
Well ofcourse there is a big potential of hard bricking the device by the method. That's why I said last resort.
So what do you suggest?
TWRP image? And if it doesn't work, he should probably wait up for next NPN build? @toyesh.patra you should consider keeping a custom rom if possible.
Btw
The ota update which I received was August patch. After which I unlocked my bootloader. It was either NPN25.137-67 or NPN25.137-67-5. I'M not sure about version. But it was definitely August patch.
Or maybe I was lucky one time.
Won't do it another time.
anuraag.neo said:
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
Click to expand...
Click to collapse
For 1686? Full fastboot firmware leaked?
yea, right now i m using the 67-5 build using twrp..
although i wanted to use the 67-5 with locked bootloader.. nevermind ..
psychopac said:
For 1686? Full fastboot firmware leaked?
Click to expand...
Click to collapse
Yes
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
psychopac said:
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
Click to expand...
Click to collapse
Yes
I can't download it. How Can I download? please upload googel Thanks bro
birkhoffChang said:
I can't download it. How Can I download? please upload googel Thanks bro
Click to expand...
Click to collapse
use search function before asking
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
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
Few mins ago Moto pushed February security patch for RETBR.
Download it here:
https://motoota.lolinet.com/index.p....26.241.15.addison.retail.en.US&carrier=retbr
You need to be on build NPNS26.118-22-2-12 to flash this update!
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
Just the security patch. Although islt coincided with the Oreo update in China. Let's hope that's in preparation for retbr Oreo.
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
I presume they will push Oreo in few hours.
rafikowy said:
I presume they will push Oreo in few hours.
Click to expand...
Click to collapse
That will be great. Even though I'll wait for a .xml.zip, on the one hand I accidentally did a downgrade (and I have no idea of the bootloader of September and December patch are different enough to cause bricking with OTAs) and I think my phone is due for a factory reset. It reboots very randomly and even though battery life is great I'm told it should be even better. Let's see if that does the fix
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
8cpaiw said:
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
Click to expand...
Click to collapse
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Artim_96 said:
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Click to expand...
Click to collapse
Hahahah true, but I'm still hoping for the best outcome
Already available for RETIN and RETUS. I'm guessing this is the last nougat patch, hopefully Oreo is next
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
You are 100% right :good:
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
If I'm reading the info in fastboot correctly, the Feb update does include an updated bootloader:
C1.14 (sha-a62b7ae, 2018-02-21 16:09:43)
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
SherlockDk said:
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
Click to expand...
Click to collapse
If the blankflashes in the other thread don't work, then you may either:
1)Have to wait for a newer blankflash to get leaked. These are Motorola internal development tools and as such aren't generally available - as they're also signed by Motorola, we may not be able to make them ourselves. The ones we have either came with the factory stock ROM or a leak from a generous Motorola engineer. You may be lucky and a blankflash may be included if an Oreo factory stock ROM comes out (not the usual fastboot ROM, a full factory image).
2)Have to pay to have your motherboard replaced, which seems to be 60-70% of the cost of a new device as far as I understand, so you may wish to put that money towards a new device instead.
I'm sorry I don't have better news, hard bricks are very difficult to resolve without the proper tools. You may wish to research making a loader image (a partition level copy of a working device, loaded onto an SD card), but it's not a definite rescue method.
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
fernseher said:
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
Click to expand...
Click to collapse
You will stay on RETEU. The link I provided is RETAIL version.
Hey can i use these files for my guide? This save me some time
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Bad url
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
If you still have that file, please upload it to androidfilehost or somewhere.