Database Users

Can not download factory images for Moto G4 Plus XT1643

From every where , i'm getting this link to download the factory image of MotoG4Plus XT1643 (indian version) :
-- can not paste Entire link here as i don't have 10 posts. Still , here's the link with / replaced by ' ' :
filefactoryfile 6jgqz4jlyiyj G4_XT1641-XT1643_ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip
However , for some reason my ISP has blocked the site.
Can anyone who has this file upload it to drive or some other folder ? Or give me some other link ?
Or , if anyone has a nandroid backup of their phone via twrp , can you send me that ?
I badly need to get my phone working by today , ASAP.
Thanks a lot !
-> Story : I wanted to move to CyanogenMod13 , so i did a backup of my phone via twrp and wiped it clean. However , i forgot to move backup to laptop , and now i don't have any backup. Plus, in CM13 i can not receive any phone calls.

varun196 said:
From every where , i'm getting this link to download the factory image of MotoG4Plus XT1643 (indian version) :
-- can not paste Entire link here as i don't have 10 posts. Still , here's the link with / replaced by ' ' :
filefactoryfile 6jgqz4jlyiyj G4_XT1641-XT1643_ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip
However , for some reason my ISP has blocked the site.
Can anyone who has this file upload it to drive or some other folder ? Or give me some other link ?
Or , if anyone has a nandroid backup of their phone via twrp , can you send me that ?
I badly need to get my phone working by today , ASAP.
Thanks a lot !
-> Story : I wanted to move to CyanogenMod13 , so i did a backup of my phone via twrp and wiped it clean. However , i forgot to move backup to laptop , and now i don't have any backup. Plus, in CM13 i can not receive any phone calls.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?a=show&w=files&flid=72578. Go to this page and download firmware named amz. This is the correct firmware for indian varient..

Hi ! thanks a lot for that !
In the meantime , i found a link to XT1643. and i installed it , everything works fine , except that my baseband is unknown. Is there any way to restore just the baseband info ? cause everything else works fine.
I'm on a slow net plan , and if i can just fix that part , i will be saved from downloading 1Gb software all over again.

varun196 said:
Hi ! thanks a lot for that !
In the meantime , i found a link to XT1643. and i installed it , everything works fine , except that my baseband is unknown. Is there any way to restore just the baseband info ? cause everything else works fine.
I'm on a slow net plan , and if i can just fix that part , i will be saved from downloading 1Gb software all over again.
Click to expand...
Click to collapse
Flash the above rom mentioned in the link.They rom you flashed previously would have been of other region.the above link is correct for xt1643 indian variant.

anhoxhrs said:
Flash the above rom mentioned in the link.They rom you flashed previously would have been of other region.the above link is correct for xt1643 indian variant.
Click to expand...
Click to collapse
Hello !
i can not find how to flash the amz .tgz file : twrp does not recognize the file ,
and in the file there are no sparsechunks which i can install unlike in the american version.
I followed the commands below to install
G4_XT1641-XT1643_ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip
And since then i'm having my baseband unknown. I'm trying to re run the same commands , but now from the amz folder's data , but no avail. Can someone identify the problem ? :
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 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 erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

varun196 said:
Hello !
i can not find how to flash the amz .tgz file : twrp does not recognize the file ,
and in the file there are no sparsechunks which i can install unlike in the american version.
I followed the commands below to install
G4_XT1641-XT1643_ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip
And since then i'm having my baseband unknown. I'm trying to re run the same commands , but now from the amz folder's data , but no avail. Can someone identify the problem ? :
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 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 erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Flash this rom throughe adb https://drive.google.com/file/d/0B1N6dGU7FEXsSjR3QUtsRU1RTVk/view

Thank you everyone ! I was able to get my phone working by using the amz link , and slightly modifying some of the commands i listed above.

varun196 said:
Thank you everyone ! I was able to get my phone working by using the amz link , and slightly modifying some of the commands i listed above.
Click to expand...
Click to collapse
What did you modify?i dint see any mistake.

anhoxhrs said:
What did you modify?i dint see any mistake.
Click to expand...
Click to collapse
The steps were not for indian version. In the amz - indian version , you can not simply follow all the steps : a few (~2) files are not there , and there are no chunks. I was making some mistake before , but next time got it correct.

I did the same but my wifi is not working now. Dont have my laptop also with me. Is there a flashable zip available?
Sent from my Moto G (4) using Tapatalk

Garry1313 said:
I did the same but my wifi is not working now. Dont have my laptop also with me. Is there a flashable zip available?
Click to expand...
Click to collapse
Stock moto roms are not in flashable zip format.You may have flashed the wrong rom on yout device.Like you have a g4 of us and flash firmware of the uk model.

varun196 said:
The steps were not for indian version. In the amz - indian version , you can not simply follow all the steps : a few (~2) files are not there , and there are no chunks. I was making some mistake before , but next time got it correct.
Click to expand...
Click to collapse
what did you modify i also have moto g4 plus and i have flashed it now my fingerprint doesnt work hmm

I got my phone working https://drive.google.com/file/d/0B1N6dGU7FEXsSjR3QUtsRU1RTVk/view
by using this rom, thanks guys.

Cant flash android 7.x.x based custom roms in TWRP

Hello guys, i have a problem with flashing custom roms.
Device unlocked, twrp tryed : 3.0.2 and newest
dev info : clark xt1572
Flashed androids 6..x.x based roms and works great.
Problems : bootloops or kernel usunes (cant boot) whats is problem ? kernel ? handybad kernel cant flash.
What is problem ?
Sry for bad english.

GeloXD said:
Hello guys, i have a problem with flashing custom roms.
Device unlocked, twrp tryed : 3.0.2 and newest
dev info : clark xt1572
Flashed androids 6..x.x based roms and works great.
Problems : bootloops or kernel usunes (cant boot) whats is problem ? kernel ? handybad kernel cant flash.
What is problem ?
Sry for bad english.
Click to expand...
Click to collapse
What was your last stock rom? 5.1, 6.x, 7.0?

I am suspecting a radio version issue here... try flashing the latest factory image via fastboot for your variant and boot fully. Do not use images from Moto, get the latest ones from https://firmware.center/firmware/Motorola/
After that, only use TWRP 3.1.1-0, then wipe system, data, caches, then flash ROM only and boot, if successful, flash Gapps and/or SuperSU (if recommended by dev of ROM) and test boot again.
If the very first boot fails, I would want to see the output of a "fastboot getvar all" and the recovery logs of the ROM flashes after you have tried the factory image flash.

acejavelin said:
I am suspecting a radio version issue here... try flashing the latest factory image via fastboot for your variant and boot fully. Do not use images from Moto, get the latest ones from https://firmware.center/firmware/Motorola/
After that, only use TWRP 3.1.1-0, then wipe system, data, caches, then flash ROM only and boot, if successful, flash Gapps and/or SuperSU (if recommended by dev of ROM) and test boot again.
If the very first boot fails, I would want to see the output of a "fastboot getvar all" and the recovery logs of the ROM flashes after you have tried the factory image flash.
Click to expand...
Click to collapse
Ok i will try it thanks. How i can flash image via fastboot ? adb sideload ?
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
OK this post will be helpfull
dzidexx said:
What was your last stock rom? 5.1, 6.x, 7.0?
Click to expand...
Click to collapse
Android 7.0 updated from stock recovery (for Germany region)

There isn't flashable working custom rom at stock nougat.
(Another partition table or drivers)
You have to downgrade or wait month-two.
Downgrade isn't safe. @GeloXD
Link in your post isn't good too.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
This one is better:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110

dzidexx said:
There isn't flashable working custom rom at stock nougat.
(Another partition table or drivers)
You have to downgrade or wait month-two.
Downgrade isn't safe. @GeloXD
Link in your post isn't good too.
Click to expand...
Click to collapse
This.... We don't have ROMs compatible with the new Nougat radio and partition table. Suggest staying stock for now.

dzidexx said:
There isn't flashable working custom rom at stock nougat.
(Another partition table or drivers)
You have to downgrade or wait month-two.
Downgrade isn't safe. @GeloXD
Link in your post isn't good too.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
This one is better:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
acejavelin said:
This.... We don't have ROMs compatible with the new Nougat radio and partition table. Suggest staying stock for now.
Click to expand...
Click to collapse
Now with downgrade solution have 7.1.2 custom android. System partition cant flash but other bot radio work good now i have what i need but still android pay and root / bootloader unlocked doesnt work ;/

GeloXD said:
Now with downgrade solution have 7.1.2 custom android. System partition cant flash but other bot radio work good now i have what i need but still android pay and root / bootloader unlocked doesnt work ;/
Click to expand...
Click to collapse
What custom do you have? Root with supersu?
Unroot it and use magisk v13(magisk hide &/or core only u need).

Work : fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Doesnt work :
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 system system.img_sparsechunk.9
So i flash mixed 6 modem radios and stay in system from android 7
I still have backup android 7 in twrp, but now 7.1.2 with magisk and root work better.

dzidexx said:
What custom do you have? Root with supersu?
Unroot it and use magisk v13(magisk hide &/or core only u need).
Click to expand...
Click to collapse
I dnt know about magisk v13 i meaned 12 is the newest version.
I flashed tesla nougat 7.1.2 rom
now version : tesla clars 7.1.2 rc v4.1 official 20170509-1634 with open gapps nano variant.

GeloXD said:
Work : fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Doesnt work :
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 system system.img_sparsechunk.9
Click to expand...
Click to collapse
For 6.0.1 xt1572 should be more:
...
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
...
fastboot flash bluetooth BTFM.bin
...

I'm having the same problem. I had updated to stock 7.0 and now I just can't update to any other 7.x roms, but 6.x roms do work

Moto G4 only boots in fastboot

Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?

squanch123 said:
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
Click to expand...
Click to collapse
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.

squanch123 said:
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
Click to expand...
Click to collapse
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?

echo92 said:
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
Click to expand...
Click to collapse
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?

squanch123 said:
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
Click to expand...
Click to collapse
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?

echo92 said:
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
Click to expand...
Click to collapse
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.

squanch123 said:
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
Click to expand...
Click to collapse
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
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 erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).

echo92 said:
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
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 erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
Click to expand...
Click to collapse
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?

squanch123 said:
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
Click to expand...
Click to collapse
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).

echo92 said:
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
Click to expand...
Click to collapse
Yes that worked
Thank you very much for your help :victory:

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.

[Getting Error while installing OTA]

I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!

ksamm97 said:
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
Click to expand...
Click to collapse
Flash the complete stock rom using fastboot and lock the bootloader and then update the device through OTA.

ksamm97 said:
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
Click to expand...
Click to collapse
Facing the exact same issue here.I think the latest stock oreo needs locked bootloader to flash

No need to relock the bootloader, but you must revert back to unmodified stock firmware on your device before updating. Without seeing what error it is, it's difficult to say. A locked bootloader strictly enforces having the unmodified stock furnace, which is why an OTA update is more likely to work.
Try this:
1) download the NPJS25.93-14-18 firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Only use this if you have not updated to Oreo and you are still on NPJS25.93-14-18.
2)unzip the fastboot ROM, delete any old stock ROMs from your ADB folder and copy the stock ROM over.
3) assuming you had NPJS25.93-14-18 already on your device, flash the firmware with the following instructions - no need for the GPT/bootloader. Ensure you have your data backed up, as you may have to factory reset if you encounter instability.
Code:
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
That should get your device into an OTA friendly state without erasing your data. If that doesn't work, I suggest waiting for the Oreo fastboot ROM.

I've custom Oreo installed on my phone. Which firmware package should I install?
echo92 said:
No need to relock the bootloader, but you must revert back to unmodified stock firmware on your device before updating. Without seeing what error it is, it's difficult to say. A locked bootloader strictly enforces having the unmodified stock furnace, which is why an OTA update is more likely to work.
Try this:
1) download the NPJS25.93-14-18 firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Only use this if you have not updated to Oreo and you are still on NPJS25.93-14-18.
2)unzip the fastboot ROM, delete any old stock ROMs from your ADB folder and copy the stock ROM over.
3) assuming you had NPJS25.93-14-18 already on your device, flash the firmware with the following instructions - no need for the GPT/bootloader. Ensure you have your data backed up, as you may have to factory reset if you encounter instability.
Code:
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
That should get your device into an OTA friendly state without erasing your data. If that doesn't work, I suggest waiting for the Oreo fastboot ROM.
Click to expand...
Click to collapse

tobey_onk said:
I've custom Oreo installed on my phone. Which firmware package should I install?
Click to expand...
Click to collapse
At the moment, we only have the stock Nougat firmware to revert to - Oreo firmware doesn't seem to be out yet. However, flashing stock Nougat over custom Oreo may appear to come with some risk of losing IMEI, so be careful. You could try the TWRP flashables, be aware the stock ROM is only 32 bit.