Database Users

[GUIDE] Lollipop for XT1064 (CANADA ONLY)

This is a guide that is strictly for those who are as impatient as I am to get Lollipop on their Moto G (2014). I know there are several guides for folks in the US, and other countries as well, but currently there is no OTA for Canada yet. We are literally left out in the cold. So, I thought I would put a collaborative guide together so the Canadians can enjoy some 5.0, too!
First and foremost, if you F up your phone, that's on you. This will void your warranty, and I am in no way responsible for any stupidity you conjure up during the process.
I have only tested this on the XT1064, which is the single SIM US/Canada model.
The issue when trying to simply follow the upgrade guide for the XT1064 is that the OTA file looks for a 4.4.4 variant of Android that needs to be the same region as where the OTA came from. If you try to install it on the Canadian versions, you will get an error. So, here goes:
1. Unlock your bootloader. Follow this wonderful guide: http://forum.xda-developers.com/mot...wip-unlock-bootloader-moto-g-2nd-gen-t2875728
2. Download the US version of 4.4.4, it can be found here: http://www.filefactory.com/file/2ygnt0x45vcr/RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
3. Extract the above file to the same location you installed Minimal ADB in the first step (C:\Program Files(x86)\Minimal ADB and Fastboot)
4. Turn your phone off and disconnect it from the computer. Press and hold the volume down (-) button and power button to get into Fastboot mode. Connect your phone to the computer.
5. Run Minimal ADB and run these commands:
PHP:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
I removed the modem commands on purpose, and I will explain why later.
6. Once the phone has rebooted, plug it in to the computer and follow this guide: http://forum.xda-developers.com/moto-g-2014/development/lollipop-moto-g-2014-xt1064-t2937361
You should now have Lollipop on your Canadian XT1064!
If you have issues with the WiFi or cellular, you may have to flash the modem commands again from the old file. I had to download the original Canadian ROM (http://www.filefactory.com/file/78znv8hx0tvt/RETCA_XT1064_4.4.4_KXB21.85-16_cid14_CFC.xml.zip) and using Fastboot flash the following:
PHP:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
After that I had no issues and everything seems to be working as it should. You can relock your bootloader afterwards if you like as well.
Thanks to the other contributors above, I was simply trying to put a quick guide together for us Canadian folks who wish to get Lollipop, too!
Cheers!

This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?

This worked for me! Thanks for the awesome tutorial!

brianshayne said:
This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?
Click to expand...
Click to collapse
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?

NexusChrist said:
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?
Click to expand...
Click to collapse
Yeah - I'm not sure what the problem was - originally it wouldn't take the US ROM due to a downgrade error. Tried it again, after a factory reset and for some reason it went through. Flashing Lollipop and the modem after was no issue at all - so good to go now. It's beautiful.
Thanks for the follow-up.
AKA: I should have just ignored downgrade error + HAB fail on phone, the first time around

I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help

ramzilla136 said:
I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help
Click to expand...
Click to collapse
Disregard the error and move on to the next command. You are going to get a few errors. Don't worry.

installing update
verifying current system
/system/app/3c_main.apl has unexpected contents
installation aborted
this is after i run the commands and upload from sd card...
followed your commands and tried few fresh zips
can you please help, it won't let me install the lollipop file

Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 erase cache
fastboot erase userdata
fastboot reboot

TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Is this procedure better? Any enhancement? Thanks.

Botsok said:
Is this procedure better? Any enhancement? Thanks.
Click to expand...
Click to collapse
This one just avoid you to flash USA KitKat and then Lollipop. This one goes directly to Lollipop.
Doesn't flash Modem/Radio from USA Lollipop because doesn't work on Canadian models, at least didn't work with WIND Mobile model.

WIND canada moto G XT1064 lollipop
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
https://mega.co.nz/#!dk430ZBZ!diHa6V-rcidHFc3niGjshk-2A9ELbqZtCnb63pFK010
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse

Just a super-dooper-uber Thanks To NexusChrist!
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post

UnderAppreciatedDev said:
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post
Click to expand...
Click to collapse
That happened because you flash the modem from Lollipop... Just flash the modem in OP and you will be ok.

spiritflare said:
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
Click to expand...
Click to collapse
Just a tad bit curious I also have a Wind Mobile Moto G2 and i'm just wondering how you unlocked the bootloader in the first place. If you could please share the process on how you did it that would be great.

Anyone know how we can get the LP bootloader on the Canadian version?
I'd like to be able to update my CM12.
Thanks!

Awesome
I'm on Bell &
everything is working 100% radio/wifi/bluetooth all good
Thanks

This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.

Kewjoe said:
This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.
Click to expand...
Click to collapse
Your carrier is most likely the reason since they have the final say on updates.

Tel864 said:
Your carrier is most likely the reason since they have the final say on updates.
Click to expand...
Click to collapse
But what about the people that bought their phones from Staples. It's unlocked and not associated to any carrier. They are directly under Motorola and still no update at all. Phone are getting 5.1 update already, but we're still at 4.4.4
What's so different in the Canadian market from the US one that the update can't come fast? Specially if the phone is not associated to a carrier and the update should come directly from Motorola

1.5 years removed from scene, need help, refreshers...

I have a Moto G4 (XT1625) Unlocked with 32GB of storage. Bootloader Unlocked and TWRP Bootloader or Recovery, IDK how to word it, but I attempt to update from Android 6.0.1 to Android 7 and the update fails. When the device reboots it reboots into the TWRP Recovery Menu. How do I proceed. Please help.
Haven't used adb, drivers, or anything and cannot seem to remember the process. Any pointers in the right direction are appreciated. Thank you.
Update 1: I am able to boot into TWRP 3.0.2-0 and see files on my MicroSD. However I downloaded a .ZIP file that was suppose to be the Nougat factory image and when I went to flash it, it says "Installing zip file.... could not find 'META-INF/COM/GOOGLE/ANDROID/UPDATE-BINARY' in the zip file. Error installing zip file."
Update 2: Can someone confirm that I would need to first somehow remove TWRP in order to update? How do I remove TWRP and get phone back to FULL STOCK.

Okay, accepting OTA updates requires a stock recovery (as you've discovered), stock kernel and unmodified system. Furthermore, the stock Nougat zip that you've downloaded needs to be extracted on your computer and flashed via fastboot, it's not flashable in TWRP.
If you're wanting to update and update to the latest Nougat build (which for US devices - XT1625 and XT1644 - appears to be NPJ25.93-14.5, June 2017), the easiest way is to download the stock Nougat ROM from here: https://www.androidfilehost.com/?fid=673368273298984458 . Download to your computer and extract the files. This build is for retail US (non-Amazon devices), with a retus software channel as listed in Settings>About Phone.
Then follow the instructions here, but using the above NPJ25.93-14.5 stock ROM instead. https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Beware that this process may erase your data in the process, so back up as necessary. If you do not wish to erase your data, then you can use the following fastboot commands instead of the commands in the guide. Back up anyway and you may have to factory reset (thus losing your data) if your device is not stable. Also, either process will remove TWRP, root and any other modifications. Xposed is still not officially released for Nougat. It is up to you if you choose to re-lock your bootloader or not (of course, re-locking the bootloader will prevent you from flashing TWRP/root/any other modifications).
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
pause
One word of warning, once you have formally updated to June 2017 (B1:06 bootloader), do not attempt to downgrade and accept OTA updates. You may wish to downgrade, but I don't recommend it - if you forget to not accept OTA updates, you may hard brick your device. If you think you'll forget, do not downgrade.

Boot up failed, Failed to validate boot image

Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest

Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?

chetana22 said:
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Click to expand...
Click to collapse
Are u using dummy bootloader I guess not orginal
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom

@ Echo
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
<<<< I was transferring data from phone memory to memory card via an option which says move media to SD card >>>>
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
<<<< I have no idea about stock ROM build. If you can help, how would I know since my device is not starting? >>>>
@ usha55
Are u using dummy bootloader I guess not orginal
<<<< I do not know >>>>
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
<<<< How do I upgrade? Please guide >>>>

@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.

____Mdd said:
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
Click to expand...
Click to collapse
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img

chetana22 said:
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
Click to expand...
Click to collapse
If you have locked bootloader, flashing of older boot.img may not work. You need to flash whole firmware.
See here,
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/page8
Download it and flash it, instructions are given there.
If you have important data on your phone, say photos/videos/or any file, then skip "erase userdata" command.. when you get device working, copy your data and then wipe your device.

Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)

chetana22 said:
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
Click to expand...
Click to collapse
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
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

It does not work
echo92 said:
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
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
Click to expand...
Click to collapse
It does not work

al3al3al3jandr0 said:
It does not work
Click to expand...
Click to collapse
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.

Now the error sends it to me in the boot.img
echo92 said:
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Click to expand...
Click to collapse
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img

al3al3al3jandr0 said:
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
Click to expand...
Click to collapse
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.

thank you
echo92 said:
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
Click to expand...
Click to collapse
ok thank you very much, you're right I'll have to wait

Sir, how to fix no found bootimage in m0t0 g4plus XT1643

Adityashankar said:
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Click to expand...
Click to collapse
Did this happen suddenly, and is this with the stock firmware or using a custom ROM?
You could try flashing the Oreo stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

Hello team, I have the same problem like chetana22 but with motorola one xt-1941-4. When i was transfering (probably) virus file from internal storage to usb flash memory, the phone stopped booting.
I have inportant and private files on internal storage, phone have quarantee... What can i do? Pls help

flash latest stock rom and skip the following instruction while flashing
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img

MOTOROLA G5S PLUS - Start up failed
My phone is G5s PLUS ... Sorry

Hi All,
Moto G4 Plus XT1643 is my phone model.
Was not being used for past 6 months, and it got stuck the boot screen .
Tried the factory reset, it got stuck in the fast boot.
Then tried the tool given by Lenovo, no luck. The "fast boot" option in the software fails.
Anyway, came to our good old XDA.
tried the options in the forum https://forum.xda-developers.com/t/...c-01-security-patch-fastboot-7-0-8-1.3608138/
Now, i am stuck with the below screens, i have attached them
Allso, do i need to start a separate thread?
Kindly help me out.

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.