Database Users

Moto Z official firmware downloads

Rogers Canada
http://www.filefactory.com/file/386..._subsidy-RGRCA_regulatory-DEFAULT_CFC.xml.zip
Telus Canada
http://www.filefactory.com/file/3pe..._subsidy-TELUS_regulatory-DEFAULT_CFC.xml.zip
Retail Mexico
http://www.filefactory.com/file/50m...d50_subsidy-DEFAULT_regulatory-03_CFC.xml.zip
Retail Europe
http://www.filefactory.com/file/6ht...ubsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip
Retail Canada
http://www.filefactory.com/file/3vz...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
? (Colombia)
http://www.filefactory.com/file/102...ubsidy-MOVSTLA_regulatory-DEFAULT_CFC.xml.zip
At&t Mexico
http://www.filefactory.com/file/3qf...sidy-IUSMXLA_regulatory-03_CFC_ATT_MX.xml.zip
Bell Canada
http://www.filefactory.com/file/57c...subsidy-BELLCA_regulatory-DEFAULT_CFC.xml.zip
Verizon
http://www.filefactory.com/file/662...MCL24.203-22_cid2_subsidy-DEFAULT_CFC.xml.zip
http://www.filefactory.com/file/1iq...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Retail China
http://www.filefactory.com/file/1ar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

great! You have the folder link in FileFactory?

Hello.
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25

Thank you.

Hello,
How to install the rom?
Thank you.

tonime said:
Hello,
How to install the rom?
Thank you.
Click to expand...
Click to collapse
Flash it manually using mfastboot command.

I have a doubt, i purchased a moto z with at&t México and flashed the retail firmware of this thread for my country and works fine, but when i enter in bootloader mode the info of the Phone shows that my Phone is a sheridan version, so i'm confused, what version i have? ��

nesgcmx said:
I have a doubt, i purchased a moto z with at&t México and flashed the retail firmware of this thread for my country and works fine, but when i enter in bootloader mode the info of the Phone shows that my iPhone is a sheridan version, so i'm confused, what version i have? ��
Click to expand...
Click to collapse
Probably Griffin. As others already reported, on bootloader mode all reports to be Sheridans... :fingers-crossed:

enetec said:
Probably Griffin. As others already reported, on bootloader mode all reports to be Sheridans... :fingers-crossed:
Click to expand...
Click to collapse
Moto Z has two product name.

alphaeva said:
Moto Z has two product name.
Click to expand...
Click to collapse
Yeah, just to make things more... confused!
We have Z, Force, Play, single sim, dual sim, Verizon's, unlocked, etc... we *really* need confused codename and product codes to help us on this...
Anyway @motorola they are surely fans of The Griffin's series..... Sheridan is the surname of the series' director...

Located the US firmware and uploaded it to Mega if anyone needs it https://mega.nz/#!vtVmgAoI!J1cZtlRi0FjRHbxIJGA5U8CLx6RwUWQjwrCbjzf_Naw

How do you "Flash it manually using mfastboot command."?

<redacted>
<How do you delete a post?>

SolusCado said:
How do you "Flash it manually using mfastboot command."?
Click to expand...
Click to collapse
fastboot flash partition gpt.bin
fastboot flash motoboot boot.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 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 system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Keep in mind depending on the region you're flashing you may have a different number of sparse chunks (I think VZW has like 16, where as stock has like 13) You just enter the amount of sparse chunks you need to flash.

Prfndhatrdofman said:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.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 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 system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Keep in mind depending on the region you're flashing you may have a different number of sparse chunks (I think VZW has like 16, where as stock has like 13) You just enter the amount of sparse chunks you need to flash.
Click to expand...
Click to collapse
Thanks; that worked - though now I find that the pre-Rooted EU ROM I was using doesn't seem to work with my Hasselblad Camera Mod.

SolusCado said:
Thanks; that worked - though now I find that the pre-Rooted EU ROM I was using doesn't seem to work with my Hasselblad Camera Mod.
Click to expand...
Click to collapse
I would just root yourself then. I couldn't get systemless root to work with the current TWRP available so I just flashed a forced System ROOT instead.
http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Download from there and flash it in TWRP. But say goodbye to Android pay obviously

:/ Ok; try as I might I cannot seem to get my Moto Z to boot if I have SuperSU installed. My bootloader is unlocked, and I've been able to flash different ROMS with no problem. But if I try to install SuperSU (v2.78-SR1) to a working ROM, or install JanJan's pre-rooted US ROM, then Android simply never boots. I just downloaded the three more recent versions of SuperSU to give them a try, but does anyone have any suggestions of what I might be doing wrong here?

SolusCado said:
:/ Ok; try as I might I cannot seem to get my Moto Z to boot if I have SuperSU installed. My bootloader is unlocked, and I've been able to flash different ROMS with no problem. But if I try to install SuperSU (v2.78-SR1) to a working ROM, or install JanJan's pre-rooted US ROM, then Android simply never boots. I just downloaded the three more recent versions of SuperSU to give them a try, but does anyone have any suggestions of what I might be doing wrong here?
Click to expand...
Click to collapse
Sounds to me like you need a different Boot image then. I flashed the boot.img that was disabled force encryption, then flashed the System mode SuperSU. No issues at all. US Moto Z 64 GB model.

link to indian firmware...not able to download it as filefactory.com is restricted... tried via apn also still a no go...can anyone download it and upload it to other server??
http://www.filefactory.com/file/20s..._subsidy-DEFAULT_regulatory-XT1650-03.xml.zip

Prfndhatrdofman said:
Located the US firmware and uploaded it to Mega if anyone needs it https://mega.nz/#!vtVmgAoI!J1cZtlRi0FjRHbxIJGA5U8CLx6RwUWQjwrCbjzf_Naw
Click to expand...
Click to collapse
Do this have the modem (baseband) included?.. I need to completely put everything back to factory.
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
dallas90733 said:
Do this have the modem (baseband) included?.. I need to completely put everything back to factory.
Click to expand...
Click to collapse
Nevermind- I didn't read

Android Pay and unlocked Moto G5+

I bought my G5+ with unlocked bootloader, gone stock through fastboot. Still Anadroid Pay won't work cuz of the unlock. I have unlocked bootloader on my other Moto X Play with stock MM rom and it works smoothly. Any clue?

wiceqq said:
I bought my G5+ with unlocked bootloader, gone stock through fastboot. Still Anadroid Pay won't work cuz of the unlock. I have unlocked bootloader on my other Moto X Play with stock MM rom and it works smoothly. Any clue?
Click to expand...
Click to collapse
G5+ doesn't have a nfc in it. Android pay is not supposed to work in it, unlocked or not.
Sent from my LG G5 using XDA Labs

suhridkhan said:
G5+ doesn't have a nfc in it. Android pay is not supposed to work in it, unlocked or not.
Sent from my LG G5 using XDA Labs
Click to expand...
Click to collapse
Of course it does have nfc, mine is 3/32 but im asking about unlock and android pay

Android pay opens if you bypass safety net, but the NFC won't work, unless you have the NFC model (I believe it is the Indian model)

wiceqq said:
Of course it does have nfc, mine is 3/32 but im asking about unlock and android pay
Click to expand...
Click to collapse
Sorry, my bad. I was thinking about the US model which I have. If you cannot relock the bootloader, I believe your option is to use Magisk to bypass safetynet check.

wiceqq said:
I bought my G5+ with unlocked bootloader, gone stock through fastboot. Still Anadroid Pay won't work cuz of the unlock. I have unlocked bootloader on my other Moto X Play with stock MM rom and it works smoothly. Any clue?
Click to expand...
Click to collapse
You should relock bootloader
Code:
fastboot oem lock begin
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot oem lock
fastboot reboot

Stock rom NPP25.137-93 to relock bootloader of x1672

https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
BR firmware with november update for xt1672, only this one worked for me to relock bootloader :fingers-crossed:

Ellcid01 said:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
BR firmware with november update for xt1672, only this one worked for me to relock bootloader :fingers-crossed:
Click to expand...
Click to collapse
I can't download from there. Can you upload a mirror? To androidfilehost, google drive. Thank you.

Ellcid01 said:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
BR firmware with november update for xt1672, only this one worked for me to relock bootloader :fingers-crossed:
Click to expand...
Click to collapse
No download link. ?

Fedray said:
I can't download from there. Can you upload a mirror? To androidfilehost, google drive. Thank you.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=745849072291696119

Ellcid01 said:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
BR firmware with november update for xt1672, only this one worked for me to relock bootloader :fingers-crossed:
Click to expand...
Click to collapse
I confirm that it works perfectly even on variant XT1675 Tim Italy single sim 16 GB storage 2 GB ram thanks.:good:

Ellcid01 said:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
BR firmware with november update for xt1672, only this one worked for me to relock bootloader :fingers-crossed:
Click to expand...
Click to collapse
Can confirm that the above ROM works with my Moto G5 XT1675 (UK), I flashed this and was (finally!) able to re-lock the phone's bootloader.

Has anyone tried this on the 3gb/16gb dual SIM variant

ROM works for X1676 2/16, but bootloader isn't able to lock

Nice! Though I have used firmware from the firmware centre and have managed to relock the bootloader....

people what about motoG5 xt1677

hello, it works on xt1671, I used it to update my phone (without erase any data) and it works, it's curious that the software channel is still the same that I ever had, tigco, that means Tigo Colombia (i'm from Colombia).

Nicomix said:
hello, it works on xt1671, I used it to update my phone (without erase any data) and it works, it's curious that the software channel is still the same that I ever had, tigco, that means Tigo Colombia (i'm from Colombia).
Click to expand...
Click to collapse
How'd you manage to do just update it?

NM99 said:
How'd you manage to do just update it?
Click to expand...
Click to collapse
I just use fastboot in this way:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
without write "fastboot erase userdata".

Ellcid01 said:
https://androidfilehost.com/?fid=745849072291696119
Click to expand...
Click to collapse
Hey friend this work for my moto g5 NPP25.137-72 XT1670??????

rosel11078 said:
Hey friend this work for my moto g5 NPP25.137-72 XT1670??????
Click to expand...
Click to collapse
Dont know i have only xt1672

Ellcid01 said:
Dont know i have only xt1672
Click to expand...
Click to collapse
I visit here https://firmware.center/firmware/Motorola/Moto G5/Stock/
the site only show solution for XT1670 and 1677 so Maybe work, I don't know we need to ask somebody here

masterdex said:
I confirm that it works perfectly even on variant XT1675 Tim Italy single sim 16 GB storage 2 GB ram thanks.:good:
Click to expand...
Click to collapse
I confirm the same. Thanks!

How do I lock the bootloader with this update? I tried yesterday but couldn't do it, got the bad key message.
EDIT: Nevermind, today at work I was able to lock it. Hopefully I'll be able to get OTA updates.

Hi, how can i install it? Do i have to flash from twrp?

Nicomix said:
I just use fastboot in this way:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
without write "fastboot erase userdata".
Click to expand...
Click to collapse
DO NOT USE THIS PROCEDURE!
I just hard-bricked my MOTO G5 XT1676 with this.

Unlock tethering how?

I have unlocked bootloader. Now I need to unlock the tethering. Apparently it is done by editing the build prop. Instructions will be appreciated.
BTW I had rooted the phone with the Tool kit, the camera had stopped working, so I reinstalled the OEM ROM November update, now the root and TWRP are gone and the camera is working again..
TIA

goodjuju said:
I have unlocked bootloader. Now I need to unlock the tethering. Apparently it is done by editing the build prop. Instructions will be appreciated.
BTW I had rooted the phone with the Tool kit, the camera had stopped working, so I reinstalled the OEM ROM November update, now the root and TWRP are gone and the camera is working again..
TIA
Click to expand...
Click to collapse
Tethering is down to your carrier, some allow it others block it, the phone itself allows tethering natively, or have I misunderstood your question.

It depends entirely on how the carrier is restricting tethering... if they doing by MAC/traffic analysis there is nothing you can do. If they are doing it by just the provisioning flag, you can edit your build.prop and change "net.tethering.noprovisioning" to true. Then may need to change make a change from a su terminal shell, "settings put global tether_dun_required 0". But again, this all depends on how your carrier is blocking tethering.

Thanks Acejavelin. That's exactly the info I was looking for.
I don't see a "net.tethering.noprovisioning" line in the build prop. Should I insert the line? Any specific location in the build prop? Should the line read "net.tethering.noprovisioning=true"
TIA

goodjuju said:
Thanks Acejavelin. That's exactly the info I was looking for.
I don't see a "net.tethering.noprovisioning" line in the build prop. Should I insert the line? Any specific location in the build prop? Should the line read "net.tethering.noprovisioning=true"
TIA
Click to expand...
Click to collapse
Yes, just add it at the bottom, the order isnt important.

Got the tethering to work. But it reverted back when I tried to relock the bootloader and installed the stock ROM. Checked the build.prop sure enough the added line vanished. Is there a way to make it stick?

goodjuju said:
Got the tethering to work. But it reverted back when I tried to relock the bootloader and installed the stock ROM. Checked the build.prop sure enough the added line vanished. Is there a way to make it stick?
Click to expand...
Click to collapse
You mean to relock with a modified system file? No. Even if you found a way to lock the bootloader with a modified file, it would then fail to boot due to other security measures in Linux.

Thanks Ace. Not savvy enough to understand what you mean. But this is what I did -
1. Use the following relock commands -
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
2. Then reflashed the stock ROM using -
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Both processes are from other posts here in XDA.

goodjuju said:
Thanks Ace. Not savvy enough to understand what you mean. But this is what I did -
1. Use the following relock commands -
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
2. Then reflashed the stock ROM using -
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Both processes are from other posts here in XDA.
Click to expand...
Click to collapse
The process of writing system sparce chunks over-write your changes... You can't have a modified build.prop and a locked bootloader. I don't know how to be more clear.

Thanks again Ace! Now I got it. Only reason to relock was to get the OTA updates. I can live without it. I have a question - Since the sparce chuncks overwrite the changes wouldn't installing updates via TWRP or fastboot also overwrite the build.prop changes? Sorry to be a pain but I am learning.

goodjuju said:
Thanks again Ace! Now I got it. Only reason to relock was to get the OTA updates. I can live without it. I have a question - Since the sparce chuncks overwrite the changes wouldn't installing updates via TWRP or fastboot also overwrite the build.prop changes? Sorry to be a pain but I am learning.
Click to expand...
Click to collapse
Having an unlocked bootloader only does not stop OTA updates, but the OTA scrupt makes several checks and I know one of them if build.prop file, the OTA will fail even if that is the only change you have made.
OTA's can only be installed in a PURELY stock device, stock recovery and stock /system partition, other than that the bootloader locked/unlocked status is not relevant. Your only real choice here is to return to stock, accept the OTA, then make the change again.

acejavelin said:
Having an unlocked bootloader only does not stop OTA updates, but the OTA scrupt makes several checks and I know one of them if build.prop file, the OTA will fail even if that is the only change you have made.
OTA's can only be installed in a PURELY stock device, stock recovery and stock /system partition, other than that the bootloader locked/unlocked status is not relevant. Your only real choice here is to return to stock, accept the OTA, then make the change again.
Click to expand...
Click to collapse
Thanks again Ace! I think instead of returning to stock every time for OTA update it will be simpler to do ZIP updates when they are made available here at XDA. Having the modified build.prop is more useful to me.

Hi, Adding this line will work for at&t blocker in G5S plus ?
Thx in advance.

alejomj said:
Hi, Adding this line will work for at&t blocker in G5S plus ?
Thx in advance.
Click to expand...
Click to collapse
What do you mean "AT&T blocker"? Don't most AT&T plans include tethering?
And will it work? Maybe, depends how they are enforcing it.

I have buyed a straight talk sim, it has 3 options att/virgin/tmobile and i choose att but when i went to use tehering it said "account not setup for mobile hotspot". But problem solved rooting the g5s plus and editing the file system/build.prop it works perfect. Thx a lot

Bootloader help

Hello guys!
I have a problem with relock my bootloader. I tried to flash stock ROM with relock commands and i have errors in console. OEM has been unlocked in developer settings...

Gooby1337 said:
Hello guys!
I have a problem with relock my bootloader. I tried to flash stock ROM with relock commands and i have errors in console. OEM has been unlocked in developer settings...
Click to expand...
Click to collapse
What error you got,if you got required signed images then you can get it from here.
https://mirrors.lolinet.com/firmware/moto/potter/official/

If you are following guides from XDA then most probably its for relocking bl on nougat.
Now the nougat firmware had 5 sparsechuck files form 0-4 whereas on Oreo firmware there are 9 sparsechunks from 0-8. Make sure you are flash 0-8 after fastbook oem lock command or you will get an error that says that the system image/oem image not signed.
Hope this helps

I usues that's commands:
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
And i got error.. image (...)

Iam relocked on my G 5 plus thanks to this .I unlocked back when I got 8.1 upgrade
Gooby1337 said:
Hello guys!
I have a problem with relock my bootloader. I tried to flash stock ROM with relock commands and i have errors in console. OEM has been unlocked in developer settings...
Click to expand...
Click to collapse
Iam relocked on my G 5 plus thanks to this .I unlocked back when I got 8.1 upgrade