Database Users

Can't find update (XT1625)

So I cannot find an update for the Moto g4. The software update says it is fully up to date even though it is running Android 6.1.1 when 7.0 is out.
If any info is needed, ask me.

I'm guessing you mean v6.0.1 MM (NPJ24-139.64/65 I think is the latest MM for XT1625 and XT1644 devices)?
If you wanted to, you could flash the fastboot stock ROM for NPJS25.93-14.4 which is the latest update available (v7.0, March 2017 security update):https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 As always, be aware that the update may affect your data (as with any flash to system), back up accordingly.

echo92 said:
I'm guessing you mean v6.0.1 MM (NPJ24-139.64/65 I think is the latest MM for XT1625 and XT1644 devices)?
If you wanted to, you could flash the fastboot stock ROM for NPJS25.93-14.4 which is the latest update available (v7.0, March 2017 security update):https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 As always, be aware that the update may affect your data (as with any flash to system), back up accordingly.
Click to expand...
Click to collapse
Are you sure this is for XT1625? It looks like it is for XT1641 and 1645.

FIUSHerson said:
Are you sure this is for XT1625? It looks like it is for XT1641 and 1645.
Click to expand...
Click to collapse
It should work, as the NPJS25.93-14.4 build is based on the NPJ25.93-14 (Dec 2016 security patch) build, just updated with the March 2017 security update.
If you wish to be more certain, you can flash the aforementioned NPJ25.93-14 update via the fastboot ROM (from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369) which has XT1625 users reporting it flashes, and then wait for the OTA for the March 2017 security patch (which recent indications suggest it's been deployed in the US), or you could sideload the OTA (after flashing the Nougat 93-14 update) by downloading from here: https://forum.xda-developers.com/moto-g4-plus/how-to/official-moto-g4-plus-ota-update-build-t3584982
Hopefully, by flashing the Nougat update, OTA updates will arrive again via the retail USA software channel.

Is there a full firmware available for the US version's latest NPNS25.137-35-5

I am trying to re-lock the bootloader, which requires flashing a stock firmware. But it won't allow flashing any older version due to older security patch. Any ideas?
Is the full firmware for the US version with May security update available somewhere?

If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)

echo92 said:
If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
Thanks a lot.
That worked perfect. Flashed NPNS25.137-35-5 on my US unlocked version and it got the May security patch.

suhridkhan said:
Thanks a lot.
That worked perfect. Flashed NPNS25.137-35-5 on my US unlocked version and it got the May security patch.
Click to expand...
Click to collapse
Hi!!! Hey could you please help me with something? Can you tell me which version of bootloader you have right now?
To know that, you have to restart the phone into bootloader mode, and you have to tell me the number after BL: line
You'll see something like:
AP Fastboot Flash Mode (Secure)
BL: C1.07 (sha-9d7f987, 2017-04-01 13:44:7) <---- THIS IS WHAT I NEED TO KNOW!!! Please!
Or could you take a picture of this screen?

MarckozZ said:
Hi!!! Hey could you please help me with something? Can you tell me which version of bootloader you have right now?
To know that, you have to restart the phone into bootloader mode, and you have to tell me the number after BL: line
You'll see something like:
AP Fastboot Flash Mode (Secure)
BL: C1.07 (sha-9d7f987, 2017-04-01 13:44:7) <---- THIS IS WHAT I NEED TO KNOW!!! Please!
Or could you take a picture of this screen?
Click to expand...
Click to collapse
I got this.
BL: C0.8A(*) (sha-c90d6a9-dirty, 2017-04-24 13:31:32)
Just curious, what is the use of this information?

suhridkhan said:
I got this.
BL: C0.8A(*) (sha-c90d6a9-dirty, 2017-04-24 13:31:32)
Just curious, what is the use of this information?
Click to expand...
Click to collapse
I totally hardbricked my potter. To revive it, I had to blankflash some files from other Moto phone. Now I have the bootloader from Moto Z Play (which has the version number I gave you as an example).
I asked you the bootloader version to make sure I can flash the new 135.5-5 bootloader and partition table to return my phone back to normal! But since I have software parts from Moto Z Play, I'm afraid it wont accept potter bootloader back again. So, I'll test this later!

echo92 said:
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
Great question. Mine is the US version with -33, so it must not be an EU firmware. I asked the same question a few weeks back and no one can confirm either way. I do wish we had some confirmation so someone doesn't flash the wrong version. Maybe if everyone responded with version info (screenshot?) and location?

long2ski said:
Great question. Mine is the US version with -33, so it must not be an EU firmware. I asked the same question a few weeks back and no one can confirm either way. I do wish we had some confirmation so someone doesn't flash the wrong version. Maybe if everyone responded with version info (screenshot?) and location?
Click to expand...
Click to collapse
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
Code:
ui_print("Source: motorola/potter/potter:7.0/NPN25.137-33/35:user/release-keys");
ui_print("Target: motorola/potter/potter:7.0/NPN25.137-35/37:user/release-keys");
3)Seems that devices running on other networks are on the 137-33 firmware (e.g. AT&T, retus: https://forums.lenovo.com/t5/Moto-G...ce-G5-plus-stuck-on-NPN25-137-33/td-p/3738547)
4) Seems that there's 2 update paths to the May security patch:
From 137-33 > 137-35 > NPNS25.137-35-5 (this May update seems to be also the wider reported version too for US devices, probably this is the path if you are on the Verizon network)
From 137-33 > NPNS25.137-33-5
I don't know if there's any major differences between the 2 builds besides the VoLTE 911 fix, or if you were on the 137-33-5 build whether you could switch to the Verizon network and be able to make emergency calls on VoLTE (I honestly would hope that fix was rolled into both May patches though...) I'm also not sure what factors decide which update you get, besides possibly being on the Verizon network at some point?
I honestly hope at a later date, Motorola unifies the firmware (like they've done with the G4 Plus), so you can just flash one version rather than multiple different types.
Again, if someone has more information (as I don't have a G5 Plus), feel free to add/correct what I've written!

I have a US version that was shipped with NPN25.137-35 and I'm on the AT&T network.

echo92 said:
If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
That last one for indian version?and it's latest .67?

dayask said:
That last one for indian version?and it's latest .67?
Click to expand...
Click to collapse
If you mean the NPN25.137-35 firmware, I don't think it was released in India (unless your device came with it?). As far as I can tell, looks like 137-67 appears to be the latest build currently for India.

echo92 said:
If you mean the NPN25.137-35 firmware, I don't think it was released in India (unless your device came with it?). As far as I can tell, looks like 137-67 appears to be the latest build currently for India.
Click to expand...
Click to collapse
So which one you recommend?

Hello XDA - Am new here, but thought i'd share my info - I have build number NPNS25.137-33-5 (7.0 Nougat) with 1. May (just upgraded from jan/feb if memory serve) as latest security patch. I am from Europe, more specific based in the Benelux area (NL/BE/GE) - If i can provide any more info on the matter, please let me know!

dayask said:
So which one you recommend?
Click to expand...
Click to collapse
I'd suggest staying on NPN25.137-67 if you're on an Indian device, else you may not receive OTA updates. Furthermore, if you swap to 137-35 you may run the risk of bricking your device in future.

So I went ahead and took a chance and flashed the *35 build on top of *33 in rsd lite. It works. Almost immediately I got the OTA of the *35-5 update. I think @echo92 is right and it is more geared towards Verizon. It took me a little to get AT&T to work on LTE here in the US but it all seems fine now.

I had -35 flashed on EU device and no updates for me.

wiceqq said:
I had -35 flashed on EU device and no updates for me.
Click to expand...
Click to collapse
Ah, then you may be on the wrong build for the EU region (I've only seen reports of 137-33 for the EU), and thus the reteu software channel might not have an update for you. I see from your previous post you flashed the 137-35 update onto your device?
I honestly don't know if you can safely revert to NPN25.137-33, but here's a stock NPN25.137-33 ROM to flash via fastboot (as always, back up your data and keep it off your device, as this fastboot ROM will likely wipe your device in the flash): https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
I also do not know what will happen if you try to flash the NPNS25.137-35-5 update onto a reteu device (it might work, but could result in you being off the update path still).
Good luck either way.

echo92 said:
Ah, then you may be on the wrong build for the EU region (I've only seen reports of 137-33 for the EU), and thus the reteu software channel might not have an update for you. I see from your previous post you flashed the 137-35 update onto your device?
I honestly don't know if you can safely revert to NPN25.137-33, but here's a stock NPN25.137-33 ROM to flash via fastboot (as always, back up your data and keep it off your device, as this fastboot ROM will likely wipe your device in the flash): https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
I also do not know what will happen if you try to flash the NPNS25.137-35-5 update onto a reteu device (it might work, but could result in you being off the update path still).
Good luck either way.
Click to expand...
Click to collapse
Well right now I'm on a custom rom. When I'll decide to revert to stock I'll probably fastboot flash -33 build and see how it goes. Cheers.

echo92 said:
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
Code:
ui_print("Source: motorola/potter/potter:7.0/NPN25.137-33/35:user/release-keys");
ui_print("Target: motorola/potter/potter:7.0/NPN25.137-35/37:user/release-keys");
3)Seems that devices running on other networks are on the 137-33 firmware (e.g. AT&T, retus: https://forums.lenovo.com/t5/Moto-G...ce-G5-plus-stuck-on-NPN25-137-33/td-p/3738547)
4) Seems that there's 2 update paths to the May security patch:
From 137-33 > 137-35 > NPNS25.137-35-5 (this May update seems to be also the wider reported version too for US devices, probably this is the path if you are on the Verizon network)
From 137-33 > NPNS25.137-33-5
I don't know if there's any major differences between the 2 builds besides the VoLTE 911 fix, or if you were on the 137-33-5 build whether you could switch to the Verizon network and be able to make emergency calls on VoLTE (I honestly would hope that fix was rolled into both May patches though...) I'm also not sure what factors decide which update you get, besides possibly being on the Verizon network at some point?
I honestly hope at a later date, Motorola unifies the firmware (like they've done with the G4 Plus), so you can just flash one version rather than multiple different types.
Again, if someone has more information (as I don't have a G5 Plus), feel free to add/correct what I've written!
Click to expand...
Click to collapse
i also am in the U.S. on straight talk with ATT but i have NPN25.137-33 on mine and i got it in july bought it off amazon without ads 64gb version for $299 and its asking me to update to the NPNS25.137-35-5 i believe i soft bricked mine when i updated it now it goes straight to twrp recovery when booting up i used a back up copy i had the phone works fine but still goes to recovery when i shut it down how do i fix this any help will be greatly appreciated.

shaker3000 said:
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
i also am in the U.S. on straight talk with ATT but i have NPN25.137-33 on mine and i got it in july bought it off amazon without ads 64gb version for $299 and its asking me to update to the NPNS25.137-35-5 i believe i soft bricked mine when i updated it now it goes straight to twrp recovery when booting up i used a back up copy i had the phone works fine but still goes to recovery when i shut it down how do i fix this any help will be greatly appreciated.
Click to expand...
Click to collapse
Update TWRP to the latest.

questions about the 7.1.1 update

Hi guys, I recently read about 7.1.1 being officially released, the thing is I already updated to Nougat via the soak test uploaded last year, should I revert to stock rom and get Nougat officially? How it is on performance quality?, Also, I'm on September security patch, do i have risk of bricking?

If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

igna.98 said:
If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
How is your GPS on that firmware? Also, do you know if that firmware will work on the XT1607?

zahna said:
How is your GPS on that firmware? Also, do you know if that firmware will work on the XT1607?
Click to expand...
Click to collapse
I'm not able to tell you how GPS works because I don't own the phone, I installed it in a friend's phone. And AFAIK it can be installed on all models except Verizon's XT1609. Tell me if it works for you

igna.98 said:
If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
will it work on xt1607 ?
UPDATE: I will try it, when i get back home.

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

February security patch available (RETBR)

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.