Database Users

Seeking G4 Plus (XT1642) Marshmallow stock ROM for the UK

I have a G4 Plus which i've flashed with a stock ROM. The phone is running Marshmallow 6.0.1 and the build number is: MPJ24.139-48 - the patch level is 1 May 2016. When I hit 'update' it doesn't update to July 2016 which is the latest available patch in the UK.
Does anyone have a UK marshmallow rom for the G4 Plus which I can load onto the phone and then update to the July 2016 patch??
Any help would be fantastic. Thanks in advance.

https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Select I agree and then moto g from the dropdown menu. The instructions are fairly straightforward. XT1625 works for your device. Bootloader probably does not need to be unlocked if not downgrading**
Then execute the following
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
Edit: Use 7-Zip to extract the tarball from tgz file, and then again extract the files from the tarball.
**I'm not sure though, select allow oem unlocking in developer options just in case

mrinmaydhar - thank you very much. I will try that out now.

Which stock ROM did you flash, btw?
You may like to look at this stock ROM here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Though it's for XT1643, I've previously successfully flashed it onto a UK XT1642, dual SIM G4 Plus and had no issues. It also brings the July security patch and build 139-63/64, and from what I remember, kept the EMEA baseband and IMEI numbers for both SIM ports.

echo92 said:
Which stock ROM did you flash, btw?
You may like to look at this stock ROM here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Though it's for XT1643, I've previously successfully flashed it onto a UK XT1642, dual SIM G4 Plus and had no issues. It also brings the July security patch and build 139-63/64, and from what I remember, kept the EMEA baseband and IMEI numbers for both SIM ports.
Click to expand...
Click to collapse
Thanks i'll try that because it sounds like you've had a good success with it!
I flashed this one: ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
It worked but it was stuck on the 1st May 2016 security patch and kept saying it was up to date and wouldn't upgrade further.

Quick update: I tried echo's rom link because the other one had issues - WiFi wouldn't work.
Echo's xt1643 rom works well. It also includes the July 2016 patch level as mentioned in the posts above.
My next question is: when Nougat arrives, I assume we'll be able to upgrade to it. Will the nougat upgrade install the recovery file? For whatever reason, I don't think my recovery file installed properly when I flashed the rom. Just wondering ifnNougat will overwrite it when it is released?

motogfalcon said:
Quick update: I tried echo's rom link because the other one had issues - WiFi wouldn't work.
Echo's xt1643 rom works well. It also includes the July 2016 patch level as mentioned in the posts above.
My next question is: when Nougat arrives, I assume we'll be able to upgrade to it. Will the nougat upgrade install the recovery file? For whatever reason, I don't think my recovery file installed properly when I flashed the rom. Just wondering ifnNougat will overwrite it when it is released?
Click to expand...
Click to collapse
Nice one, from the sounds of it, everything's working
As for Nougat (whenever it arrives in the UK and Europe!), you should be receiving an OTA update, since you're up to the latest MM 139-63/64 build for our region. It also should flash onto your device provided no modifications have been made to the recovery/system (bootloader lock/unlock doesn't appear to matter).
What did you see that suggested your recovery wasn't properly installed? If it was an error such as 'not signed' or 'bad key', but reported OK after flashing, don't worry about it.

I got the 'not signed' message. Excellent! All seems to be working well. Looking forward to when Motorola release Nougat. It's a shame they haven't kept on top of the security patches because its a great device I think! Thanks again!

motogfalcon said:
Excellent! All seems to be working well.
Click to expand...
Click to collapse
What is your software channel now? Still retgb ?

Yes retgb. Apparently Lenovo are releasing Nougat soon in the UK so hopefully I'll get it on the retgb channel

Help with june security update - or should I say, how to get it?!

Hi,
I have a complete stock moto g4 plus XT1642, with firmware build number NPJS25.93-14-4 (march security update), retgb.
I didn't get the June security update, and I the phone insists that my software is up to date..
I am not interested in rooting my phone. How can I force it to update?
(I also have the same problem with another retgb moto g4 non-plus..).
Thanks!

Yeah, retgb updates seem to be taking a little while to deploy... Like your experience, I was waiting for updates on the retgb channel too... Then I updated using the captured updates on XDA, which appeared to have worked okay
You've got 2 routes:
1) You can download the June 2017 OTA update from here to your device: https://drive.google.com/drive/folders/0B-GUyOfb8OgzR1VrQ1NHWDVmWE0
This is the same update that was on XDA, just mirrored to my Google Drive as the original link does not appear to work.
File name:Blur_Version.25.201.4.athene.retail.en.US.zip
Size: 56 MB
md5 checksum: 4ce250195b2eb71c960ec3b6579bc9d0
Ensure your device is fully updated to NPJS25.93-14-4 (bootloader should be version B1:05), you have a stock recovery, unmodified system and baseband (baseband version should end in .62R), as this update requires the March 2017 update. If your bootloader is still locked, this should all be applicable. Then:
Boot to stock recovery (notes on how to access stock recovery are here: https://forum.xda-developers.com/showpost.php?p=72981796&postcount=58 )
Select 'apply update from SD card'
Locate the Blur_Version.25.201.4.athene.retail.en.US.zip on your device
Install update.
You may wish to wipe cache before rebooting.
Now, you should be updated to June 2017. There's also the September 2017 OTA (requiring the June 2017 patch) which you can apply in the same fashion: https://forum.xda-developers.com/moto-g4-plus/how-to/captured-ota-september-security-patch-t3680367
I successfully flashed the June 2017 OTA onto my XT1642, retgb (so same as yours) that had previously been running on NPJS25.93-14-4 and have had no issues - my network provider, 3 UK, works well
2) If you want to, you can jump straight to the September 2017 stock build, which is running on my XT1642, and this is the method I chose to update (as I was rooted too, so needed a near clean start). I think it should be suitable for the Moto G4 too that you have, but you may wish to check the following stock ROM thread to confirm.
a) Download the September 2017 stock ROM (NPJS25.93-14-10): https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
b)Set up ADB as directed in the above post. Extract the ROM files in the same folder as your ADB terminal (so you should see files like oem.img and bootloader.img mixed with adb.exe and fastboot.exe)
c)If you wish to keep your data and do not need to re-lock your bootloader (i.e. your bootloader is already locked, or unlocked) and are simply updating, you could use the following fastboot commands to keep your data intact. Back up your data just in case your system becomes unstable and needs a factory reset, though I did not notice any corruption of my data. The initial boot was a little slow (presumably to rebuild caches and update links as necessary):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands should update your GPT, bootloader, recovery, system and modem to NPJS25.93-14-10, Sept 2017 patch. Though you could edit one of the flashing scripts - provided in the stock ROM thread - to match the above commands, I preferred to manually copy each command and execute the commands, checking each command flashed. As with anything affecting the firmware of your device, take your time in flashing. Using the September 2017 stock ROM, my XT1642 is still running happily with the September security patch (and seems smoother too )
Bear in mind that with the June and September updates, the bootloader is updated to version B1:06. Thus, it makes downgrading risky. From the sounds of it, you're not interested in rooting/downgrading, so this might not be for you anyway. Just a heads up that downgrading from the June or September 2017 stock ROMs (e.g. by flashing the older stock ROM without flashing GPT/bootloader) and then accepting OTA updates may cause a device to hard brick. We have ways of attempting to rescue a device in this state but I really wouldn't like to try them if at all possible.
Good luck whichever route you choose

What's the latest U.S build version of Moto g5 plus? (OTA HELP)

Hello! https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I used that forum to re-lock bootloader and flash stock rom! WHOOHOO, but fastboot is still saying my software status is modified, and I can't tell if I'm receiving OTA updates? How do I check that? I went into settings > About phone > software updates > YOUR SOFTware is up to date.
So I'm wondering if since my fastboot says my firmware is modified, that i'm not receiving OTA. Can someone please confirm they're running un-touched moto g5 plus software, and confirm what latest buildnumber is? U.S. phones only please.
I really need help, I need to receive OTA updates, and I'd assume since it says my "software is up to date" that it is, but I want someone to confirm..
BUILD NUMBER NPNS25.137-33-11

if anyone knows anything about this PLEASE post I'm desparate.

OK flashed rom from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ from december
that should be the latest one,
NPN25.137-92
security patch nov 1 2017
HOWEVER, even though i may be on the latest rom it's still disturbing that i don't receive ota updates. any way to get around this?

beatlesfan5858 said:
OK flashed rom from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ from december
that should be the latest one,
NPN25.137-92
security patch nov 1 2017
HOWEVER, even though i may be on the latest rom it's still disturbing that i don't receive ota updates. any way to get around this?
Click to expand...
Click to collapse
I think once you leave stock, you won't receive OTA's again, even if you re-flash and lock bootloader. You will have to download the updated ROM and manually install it.

lol... You are a lot newer than mine (which I thought was current) and I have NPN25-137-83 (August 1, 2017) and I am completely stock with locked bootloader, never touched it. Are you sure you flashed the right software channel image for your device, retus?
There has only been a couple OTA updates for this device ever, your not missing anything. And BTW, your "modified" status is normal until you get your first OTA, it should then become official. Note that Bootloader Status will ALWAYS be a 2 and will never go back to 0, it isn't possible for anyone but Moto to do that.

beatlesfan5858 said:
Hello! https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I used that forum to re-lock bootloader and flash stock rom! WHOOHOO, but fastboot is still saying my software status is modified, and I can't tell if I'm receiving OTA updates? How do I check that? I went into settings > About phone > software updates > YOUR SOFTware is up to date.
So I'm wondering if since my fastboot says my firmware is modified, that i'm not receiving OTA. Can someone please confirm they're running un-touched moto g5 plus software, and confirm what latest buildnumber is? U.S. phones only please.
I really need help, I need to receive OTA updates, and I'd assume since it says my "software is up to date" that it is, but I want someone to confirm..
BUILD NUMBER NPNS25.137-33-11
Click to expand...
Click to collapse
I flashed the stock ROM for RETUS (US variant of the G5 Plus), compared it with a with a friend who is on RETUS and on the latest version, and found out that the latest version is build number NPN25.137-83 with the August 1st security patch. When I flashed the stock ROM, my bootloader said I was on official software. If you want me to help you out, I can.

reCoded said:
I flashed the stock ROM for RETUS (US variant of the G5 Plus), compared it with a with a friend who is on RETUS and on the latest version, and found out that the latest version is build number NPN25.137-83 with the August 1st security patch. When I flashed the stock ROM, my bootloader said I was on official software. If you want me to help you out, I can.
Click to expand...
Click to collapse
OK where can I find the stock ROM NPN25.137-83? So the steps would be....
1. Download stock rom
2. oem lock device
3. Flash stock rom/ erase everything?
EDIT: to clarify where I'm at right now, I re-unlocked bd and rooted with Magisk, but have root access gives me nothing but trouble. I have a broken camera now since I've rooted, the app doesn't want to open. No doubt about it, I want to go back to the way everything was normally, receiving OTA updates and have official software. I never should've messed with anything.

OK I downloaded 137-83 from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL
Then tried oem locking and reflashing everything with this link https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
But it didn't want to oem lock, because it says it requires a "signed boot img"
So what should I do from here?

beatlesfan5858 said:
OK I downloaded 137-83 from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL
Then tried oem locking and reflashing everything with this link https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
But it didn't want to oem lock, because it says it requires a "signed boot img"
So what should I do from here?
Click to expand...
Click to collapse
You'd likely have to wait for the next US retail firmware to be leaked to be able to lock your device.
Given that you've flashed the NPN25.137-92 firmware, you've likely still got the bootloader from that firmware, and so using an older NPN25.137-83 firmware won't permit you to re-lock your bootloader. You cannot downgrade bootloaders (and probably reports a security downgrade error if you try).
Also, now that you likely have a different system to your bootloader, I would caution against taking OTA updates until you've flashed the newer US firmware. I don't know if bootloaders for US firmware are different or the same as other region's firmware, and hopefully someone knows (or can compare firmwares), but mixing builds with different patch levels or regions could lead to a hard brick if taking OTA updates. Be careful.

Thanks I don't want to brick my device. So what should I flash right now? I want to delete everything (root) and go back to stock rom so my camera works! See above for what rom I'm on, it's December security patch. Should I just reflash that one? I won't try to downgrade now. How do I wipe twrp and restore stock recovery and stock everything? Show me the way Jedi master!

Please someone tell me! I really need my phone to be functional.

beatlesfan5858 said:
Thanks I don't want to brick my device. So what should I flash right now? I want to delete everything (root) and go back to stock rom so my camera works! See above for what rom I'm on, it's December security patch. Should I just reflash that one? I won't try to downgrade now. How do I wipe twrp and restore stock recovery and stock everything? Show me the way Jedi master!
Click to expand...
Click to collapse
You're on the December patch? What's your software channel? If it's not RETUS, you've screwed stuff up. The December patch isn't available to US G5 Pluses.

reCoded said:
You're on the December patch? What's your software channel? If it's not RETUS, you've screwed stuff up. The December patch isn't available to US G5 Pluses.
Click to expand...
Click to collapse
my bad! software channel retus android version 7.0 android security patch level nov 1 2017 baseband version m8953_37.46.07.47R Potter NA_Cust kernel version [email protected] #1 mon nov 20 09:32:29 CST 2017 build number NPN25.137-92 hope this helps

beatlesfan5858 said:
my bad! software channel retus android version 7.0 android security patch level nov 1 2017 baseband version m8953_37.46.07.47R Potter NA_Cust kernel version [email protected] #1 mon nov 20 09:32:29 CST 2017 build number NPN25.137-92 hope this helps
Click to expand...
Click to collapse
When your device starts up, does it say "ID: bad key" by chance?

reCoded said:
When your device starts up, does it say "ID: bad key" by chance?
Click to expand...
Click to collapse
edit it says ID:n/a just checked booting it up, that's on the unlocked bootloader screen by the way

beatlesfan5858 said:
edit it says ID:n/a just checked booting it up, that's on the unlocked bootloader screen by the way
Click to expand...
Click to collapse
Alright, you seem to have a similar situation to what I had. I cannot confirm that this will work but if you're willing, you can try it. Doing this fixed my device. My device software status is official and I pass SafetyNet. Again, I'm not sure if this will brick your device or not and I'm not responsible for anything that goes wrong.
First download the NPN25.137-83 firmware here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Now reboot your device to bootloader and type these commands ONE AT A TIME.
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Now reboot and set up your device. After doing that, restart to bootloader and type these commands again, ONE AT A TIME.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Hopefully, you should be back to stock and able to receive software updates.

reCoded said:
Alright, you seem to have a similar situation to what I had. I cannot confirm that this will work but if you're willing, you can try it. Doing this fixed my device. My device software status is official and I pass SafetyNet. Again, I'm not sure if this will brick your device or not and I'm not responsible for anything that goes wrong.
First download the NPN25.137-83 firmware here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Now reboot your device to bootloader and type these commands ONE AT A TIME.
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Now reboot and set up your device. After doing that, restart to bootloader and type these commands again, ONE AT A TIME.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Hopefully, you should be back to stock and able to receive software updates.
Click to expand...
Click to collapse
Alright i'm going to do everything exactly like you said. I'll be about 15 minutes, will report back. stick around please, and thanks so much for all your help.

Hey, isn't this what previous user warned about? I was on a higher up version of the software so he said I couldn't downgrade?
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517383 KB)...
OKAY [ 17.424s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.531s
that's when i typed in flash oem and flash sparseimg 0, it's giving me those validation errors.

beatlesfan5858 said:
Hey, isn't this what previous user warned about? I was on a higher up version of the software so he said I couldn't downgrade?
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517383 KB)...
OKAY [ 17.424s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.531s
that's when i typed in flash oem and flash sparseimg 0, it's giving me those validation errors.
Click to expand...
Click to collapse
It seems so. I was afraid this might of happened. That means that you'll have to wait for RETUS to get the November update or higher for you to relock. Did the commands relock your bootloader or is it still unlocked?

reCoded said:
It seems so. I was afraid this might of happened. That means that you'll have to wait for RETUS to get the November update or higher for you to relock. Did the commands relock your bootloader or is it still unlocked?
Click to expand...
Click to collapse
It wouldn't re-lock because it said the boot img wasn't signed. I know if I try with the current potter version I have, that it will relock, but I was afraid I wouldn't receive OTA updates if I did that.
edit: to clarify, I had downloaded 137-92 from the above link, and managed to relock it before on that version. However I was paranoid about ota updates so i re-unlocked, and re-rooted, which turned out to be a mistake. I'll try re-locking and flashing 137-92, which is the nov 1 2017 security update btw.

Moto G4 Plus OEM stock version upgrades and OTA after bricking device

Hello to this amazing community,
I have recently tried for the first time to root my device.
Being unaware of the XDA community, I used this guy's guide - https://theunlockr.com/2016/11/29/root-motorola-moto-g4-moto-g4-plus/ .
As I went through the steps of unlocking, booting TWRP and installing superSU, I found out that the device won't start anymore, though the bootloader was still working at that point.
Unfortunately, that guide didn't emphasized the importance of first backing-up the system with TWRP.
Panicking, I even ended up wiping the entire device.
So I started my sisyphic journey of reviving the phone.
Being clueless of OEM stock versions etc. at this point, I thought that I should look for a fresh TWRP backup someone did after purchasing my exact Moto G4 Plus model - XT1644 so I ended up recovering the version that this dear guy has uploaded:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1644-stock-unmodified-6-t3536448
Happy as I was that the machine would finally start, I found out I was running an old Marshmallow version - exactly as the title says.
Still, I assumed that new OTA versions will be available and my device will be upgraded to the most up-to-date version.
Surprisingly for a rookie as me, checking for software updates showed " Your device's software is up to date".
So I search for a more up-do-date OEM stock version, and I have found the following version - NPJS25.93-14-13 here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I ran the bash file to flash the OEM while keeping the device unlocked.
The device has loaded finally with the familiar up-to-date version, and an available OTA update appeared.
I immediately ran the update.
That's when I first became familiar with the term "Brick". The device became completely dead.
Now, thanks to siddhesh9146 inceredible thread I managed to revive the device:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
I went through his steps, installed BlankFlash, flashed the latest gpt and bootloader and flashed version NPJS25.93-14-10.
The device will finally work! I would realize then, that the latest version is actually ATHENE_NPJS25.93-14-13 ,
And again, the device won't show any updates available.
So, finally, here are my questions:
1. What could I have done wrong in first place? Was it a wrong superSU version that caused the problem? (In case my rooting aspirations will return)
2. What caused the device to turn brick? I realize it has to do with downgrading version, but after I wiped the device, I only upgraded versions.
3. In general, when OTA are available? Only the newest stock version would receive OTA? Will I have to manually upgrade versions from now on?
4. Could I upgrade now to NPJS25.93-14-13 using the version that siddhesh9146 presented without wiping my entire phone? What exactly should I flash to do so?
5. What are the precautions I have to take while doing so? Is there a risk my phone will tun brick again?
Thanks!

Good to hear your device is working again, seems like it's been through a journey.
1)When you originally rooted, were you on stock Nougat (7.0)? If so, those rooting guides will not work and are likely for Marshmallow 6.0 systems only. What they fail to mention is that attempting to root whilst still on the stock Motorola Nougat kernel likely causes your device to not boot. The Nougat 7.0 stock kernel for our devices seems to be much stricter than the Marshmallow kernel when it comes to anti-rooting protections. Thus, we generally need to flash a custom kernel onto our devices before rooting - either with SuperSU or magisk. An example of a working guide for rooting on stock Nougat Moto G4/Plus is here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
2)Do you remember what the OTA you received was? I don't think there's an OTA for a build later than NPJS25.93-14-13 out yet. That suggests that the NPJS25.93-14-13 flash didn't work - did you check if the bash script reported [OKAY] after each command? By brick, do you mean the device had a blinking LED light, and there was no screen, and you were unable to boot to the bootloader and/or recovery? If the flash didn't work, then you may have taken a Marshmallow to Nougat OTA (NPJ25.93-14) which may have corrupted your device bootloader in the process.
3)OTAs are generally available for a particular build and for a particular software channel when they are released. For NPJS25.93-14-13, that's currently the latest build for EU/UK, Brazil and India devices, and there's word that there's a February 2018 OTA coming soon (no sign of it yet).
However, for your device (XT1644), if you are on the retUS - retail US - software channel, your device is on a different update path - NPJ25.93-14.7 would be the corresponding September 2017 patch for retUS software channel devices. NPJS25.93-14-10 is not one of the builds deployed to the retUS, and as such the Motorola servers may not issue you an OTA patch, regardless of whether the firmware would work. There have been reports of NPJS25.93-14-10 and NPJS25.93-14-13 working on US devices without issue, but you may not receive OTA updates.
You could manually update to NPJS25.93-14-13 using the OTA here, provided that you fully flashed the NPJS25.93-14-10 stock ROM (including GPT and bootloader, system, modem, boot, recovery, OEM, DSP, FSG). If you did not fully flash, you may be risking another hardbrick. https://forum.xda-developers.com/showpost.php?p=74973505&postcount=7
4)If you want to flash the NPJS25.93-14-13 stock ROM to be safe, or attempt to cross flash to the Sept 2017 NPJ25.93-14.7 firmware without wiping your data, you can use the following flashing commands. Be warned that you may have to factory reset if your device becomes unstable, so backup anyway. I would recommend manually flashing these commands:
a)copy and paste the first command to the ADB terminal
b)press enter, wait for [OKAY] to appear.
c) copy the next command, individually and in order, to the terminal, repeat b) and c) until you get to the end of the list.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands omit the fastboot erase userdata, preserving your data, and omit the OEM locking commands, which would lock your bootloader and erase your data in the process as well. Bear in mind that cross flashing can be risky, however, you may have to flash the NPJ25.93-14.7 update if you wish to receive OTA updates for the retUS software channel, if you are on that software channel. Link for the NPJ25.93-14.7 stock firmware if you wish to try: https://androidfilehost.com/?fid=817906626617945295
5)Generally, the main source of hard bricks I've noted has been users have been on stock Nougat (particularly the March 2017-latest) builds. They downgrade their device to stock Marshmallow firmware, which goes okay. However, in most - if not all - cases, their bootloaders are not downgraded, so you have a system and bootloader mismatch, with a newer Nougat bootloader but an older system than their bootloader patch level. For example, a B1:06 June 2017 patch level bootloader but a July 2016 Marshmallow system patch level.
The OTA checks that are performed are mainly on the system side i.e is your device on the July 2016 system patch? Are your system, OEM, recovery, boot etc. partitions unmodified and match the expected checksums for this OTA patch? If so, then install. However, in the updater script, there is no such check for the bootloader - the OTA updates appear to assume your bootloader is of the same patch level as your system. Normally, for a locked bootloader or for a user that has only updated their device, that assumption holds.
The issue we have here is that the system was downgraded to Marshmallow, so that assumption no longer holds. As the OTA updates are signed by Motorola, they have authorisation to write to your bootloader. That means this OTA can overwrite your bootloader, and if it's applying older code, can corrupt your newer Nougat bootloader and thus hard brick your device, which necessitates a blankflash to repair.
In other words, if you downgrade your device firmware, do not use or install OTA updates. If you do downgrade, only update with stock firmware that is as new or newer than your bootloader patch level. If your device is on the same patch level , then you should be able to use OTA updates. However as mentioned above, you need to be on the correct build for your device software channel as well to receive OTA updates from Motorola.

Need help going back to full stock

Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers

guillermohs9 said:
Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers
Click to expand...
Click to collapse
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, with a TWRP flashable build you won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
You will lose your data so backup your stuff.

Wolfcity said:
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, a TWRP flashable build won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
Click to expand...
Click to collapse
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?

guillermohs9 said:
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?
Click to expand...
Click to collapse
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Yes, you have to unzip the firmware in your adb/fastboot folder on your PC and enter all fastboot commands, you can also use a flashall.bat with all commands in it. You have to copy that bat into your adb/fastboot folder too and just click it.
Here's one:https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
There are some tutorials around how to do it all but some are a bit outdated. I'm about to write an actual one.
You need Motorola drivers on your PC:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
and something like Minimal Adb & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=sharing
If you're not familiar with this procedure you can also give Lenovo Motorola Smart Assistant a shot:
https://support.lenovo.com/de/de/downloads/ds101291

Wolfcity said:
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Click to expand...
Click to collapse
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.

guillermohs9 said:
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.
Click to expand...
Click to collapse
I'll take a look what firmware has been pushed to your region. If you're on the wrong update channel you won't receive OTA updates because Motorola/Lenovo only pushes one update for every location, either the US version (17-x) or the other one (13-x).
I'm writing on that guide but it will be a bit extensive because it should cover unlocking/flashing/rooting/decrypting/locking, the whole thing.

Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:

BartKey said:
Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:
Click to expand...
Click to collapse
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot

I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Edit: flashed Twrp now it says "bad key" on the unlocked device screen but it boots into stock Oreo.
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.

guillermohs9 said:
I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Click to expand...
Click to collapse
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.

Wolfcity said:
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.
Click to expand...
Click to collapse
It used to say N/A instead. I don't mind. The problem now is that it always tries to boot into recovery.

guillermohs9 said:
....
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.
Click to expand...
Click to collapse
As I said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?

wolfcity said:
as i said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?
Click to expand...
Click to collapse
opss28.85-17-4

guillermohs9 said:
opss28.85-17-4
Click to expand...
Click to collapse
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.

Wolfcity said:
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.
Click to expand...
Click to collapse
Thanks! I figured the same about the future updates, now Motorola is focused on newer devices so december security patch is enough.
I am on stock, unrooted, relocked bootloader now. I used the commands you provided (included erase userdata) then had to flash TWRP, flash magisk, use adb shell and dd to clear that misc partition (so it boots into system), and finally did
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
to relock bootloader. It works as expected now and it's ready to be used by anyone.
Thanks a lot

Wolfcity said:
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thanks a lot @Wolfcity
I came from OPS28.85-17, without updates available.
Now I flashed OPS28.85-13 with your instructions not to erase userdata.
Checking for updates: 13.3 available -> installed
13.5 available -> installed and "up to date" security patch dec 2018
:good:

@guillermohs9 @BartKey: Great to hear everything is working! I will add your experiences to the upcoming tutorial.