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

Help needed- moto g4 plus hardbricked, installed blank flash, oem locked

My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.

tried to pass the last stock if I am not mistaken version that is or updated passes without being with bootloader unlocked.

Pranav_dp said:
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.

echo92 said:
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
Click to expand...
Click to collapse
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.

Pranav_dp said:
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Click to expand...
Click to collapse
If you flashed the April 2018 security patch stock firmware, there are currently no OTA updates, the April 2018 security patch is the latest available.
If you fully flashed the latest firmware as I mentioned, you should be okay to use OTA updates. Just in future please remember to not use OTA updates if you downgraded your device by flashing old stock firmware.

i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?

Daroas said:
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Click to expand...
Click to collapse
Without a blankflash new enough to flash to the device, I don't think so. You'd have to consider a JTAG repair, a motherboard replacement or buy a new device.

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.

Bootloader - Amazon Moto G7 with Alexa Hands-Free – Unlocked – 64 GB – Clear White

Took a gamble and purchased a G7 through Amazon, fast shipping and easy returns.
It showed XT1962-1 and came with all of the Amazon apps pre-loaded. I went to the motorola bootloader unlock page and attempted to unlock it. ***IT WORKED!!!!!***.
After bootloader was unlocked, I took a bigger chance and attempted to patch the boot.img from the XT1962-1 retus stock rom. Patched appeared to be successful so I copied it back over to desktop and then flashed it back to the g7. Uh oh, now it is stuck on unlocked device screen followed by a very brief motorola splash screen then back to device is unlocked.
Tried flashing stock boot.img back with the same results. Decided to go ahead and flash full stock room back using the commands from flashflile.xml.
Rebooted and back working. Shut it down and attempted to put the patched boot.img back on and this time IT BOOTS.
installed magisk app and confirmed root. SUCCESS!

Can you please explain to a beginner what you did, and what do you mean by "flash full stock room back using the commands from flashflile.xml"?
Thanks for your time

steps
I can only tell you what worked for me and can't offer any advice or assistance if you try this and run into trouble. If you aren't comfortable with flashing or don't have a spare backup phone in-case you run into trouble then I wouldn't recommend this.
I grabbed the stock XT1962-1 retus stock image from here:
https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/
unzipped it to a folder and then dropped adb/fastboot into the same folder. I did NOT erase the modem or userdata/ddr since it was a new phone that wasn't setup to begin with.
From command prompt in the folder with the unpacked stock rom in it, run these commands. I would recommend one at a time to watch for errors.
Let it reboot once to make sure it worked. The first boot may take a while.
fastboot getvar max-sparse-size
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
rem fastboot erase modemst1
rem fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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 system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot

does hands free alexa still work though after flashing? Supposedly the hands free alexa option only works with the amazon rom.

I followed this procedure on a moto g7 power and it worked as well. I didn't have any issues booting up the first time after patching the patched boot image that magisk created like you did. I'll comment over on the g7 power board, but wanted to thank you for your instructions.

Can I safely assume that after flashing the stock rom, the phone is not converted to a stock g7 instead of Amazon branded one
Thanks.
Sent from my MI 8 Lite using Tapatalk

rootuser11 said:
Can I safely assume that after flashing the stock rom, the phone is not converted to a stock g7 instead of Amazon branded one
Click to expand...
Click to collapse
I can only say what I have experienced on my phone. It is stock, hands free alexa does appear to work. I have a buddy at work with stock g7 and the installed apps appear the same. I can't visually tell a difference between the 2 phones other than under about phone my software channel shows amazon. Others with more experience may have more information to offer you however it worked for me and I haven't had any issues and great battery life so far.

timecutter said:
I can only say what I have experienced on my phone. It is stock, hands free alexa does appear to work. I have a buddy at work with stock g7 and the installed apps appear the same. I can't visually tell a difference between the 2 phones other than under about phone my software channel shows amazon. Others with more experience may have more information to offer you however it worked for me and I haven't had any issues and great battery life so far.
Click to expand...
Click to collapse
Hmm ok. It seems like Amazon stuff still resides somewhere to indicate that the phone is related to Amazon. Ugh..
Sent from my MI 8 Lite using Tapatalk

I cannot find Netflix in Google play store
timecutter said:
I can only say what I have experienced on my phone. It is stock, hands free alexa does appear to work. I have a buddy at work with stock g7 and the installed apps appear the same. I can't visually tell a difference between the 2 phones other than under about phone my software channel shows amazon. Others with more experience may have more information to offer you however it worked for me and I haven't had any issues and great battery life so far.
Click to expand...
Click to collapse
Hi timecutter,
I have a Moto G7 (US version) with Amazon Alexa Hands-Free – Unlocked, with its firmware totally replaced with the Stock US retail firmware. Everything is fine except I cannot run Netflix. I cannot find Netflix from Google play store. I tried to download several netflix apk files from apkmirror.com and install them but all of them failed to run with the message that the version of Netflix is not compatible with my phone.
Does this happen to you? Which version of netflix did you use? Where did you get it?
Thanks.

What is best way to update Security Patches on rooted / Unlocked G7?

What is the safest way to apply the newest updates? I am still on April, been afraid to do anything without asking first.
Is there a simple way, and will I still be able to unlock/root again?

Same question. Accent being on 'safe'.

SmilingPerson said:
What is the safest way to apply the newest updates? I am still on April, been afraid to do anything without asking first.
Is there a simple way, and will I still be able to unlock/root again?
Click to expand...
Click to collapse
maybeme2 said:
Same question. Accent being on 'safe'.
Click to expand...
Click to collapse
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive

TheFixItMan said:
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
Click to expand...
Click to collapse
See this thread ...
https://forum.xda-developers.com/moto-g7/help/ota-rooted-phone-t3956012
I copied out the important parts..
1. Download the latest firmware.
2. Install adb & fastboot
3. Flash with these commands:
Code:
fastboot getvar max-sparse-size
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 dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.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 system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
DO NOT RUN THIS ONE ---- fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
you will then need to patch boot with magisk again.

TheFixItMan said:
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
Click to expand...
Click to collapse
The latest for the xt1962-1 retail is the August security patch. That's pretty good considering Lenovomoto.

I hit the notice for the June 1, 2019. Failed to install. Tried using the Lenovo Moto Smart Assistant and it bricked my phone. Now have to wait on Motorola to send a replacement. Very frustrated right now. WTF an OTA failed and the LMSA bricked the phone. SMH...

Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.

zenful said:
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
Click to expand...
Click to collapse
Locking the bootloader is not a cinch either.
Makes you wonder if the safest course might not be to just ignore the updates and stay with the android version you have.
Which is more dangerous, staying with the 'not-updated' working phone or trying to update and risking a bricked phone?

maybeme2 said:
Locking the bootloader is not a cinch either.
Click to expand...
Click to collapse
From my understanding, you need a signed/original boot.img that of which if you didn't make a backup of yours before rooting, than the LSMA can help. I'm thinking removing Magisk and full factory resetting will be necessary as well.
As for obtaining a copy of a signed/official boot.img
sd86 said:
Head on over to https://support.lenovo.com/us/en/downloads/ds101291 and download the tool, after installed put your phone in bootloader/fastboot mode and go through the rescue steps up until the firmware is downloaded, do not click rescue after the firmware is fully downloaded just head on over to C:\ProgramData\LMSA\Download\RomFiles and open the downloaded firmware and take the boot image from there and copy it to your fastboot tools folder and flash that boot.img check that the firmware matches the version installed on your phone before flashing the boot.img.
Click to expand...
Click to collapse
About the
fastboot oem lock
Click to expand...
Click to collapse
skuppej said:
The trick is to run `fastboot oem lock` 3x (not 2x) before flashing boot.img, and then run `fastboot oem lock` one last time after this is done.
Click to expand...
Click to collapse
(Above info found in this thread about relocking the bootloader)
maybeme2 said:
Which is more dangerous, staying with the 'not-updated' working phone or trying to update and risking a bricked phone?
Click to expand...
Click to collapse
I can't give you a definite answer, but the way I perceive this is;
Should I keep a version of my OS that does not have the most recent security updates but has been rooted?
Click to expand...
Click to collapse
I hope this info helps and brings some clarity for you.

zenful said:
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
Click to expand...
Click to collapse
Phone was locked and not rooted. It's now FUBAR and Moto is sending me a replacement.