Related
Plz give the cmd code for checking details of bootloader locked or unlocked
Here you go
fastboot -i 0x1ebf oem device-info
jogson said:
Plz give the cmd code for checking details of bootloader locked or unlocked
Click to expand...
Click to collapse
**************************WARNING****************************************
Please not that unlocking and re-locking boot loader in CM12 (Lollipop) Would ERASE USER DATA!
So first make sure that your device (yureka) is detected fastboot -i 0x1ebf devices
fastboot -i 0x1ebf oem lock
Please hit Thanks! if it worked!
Follow at your own risk. Unlocked bootloader required.
This is how I was able to fix my softbrick after updating to -64 on my US XT1625 Amazon G4. Credit goes to Android Doctor (his YouTube tutorial), I changed his fastboot commands a little though to better match how a real Moto upgade would act (based off of the flashfile.xml file in the firmware zip).
From here download "XT1625_ATHENE_AMAZON_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" (Here's a direct link if it works for you).
Extract that zip to a folder and copy ADB/fastboot files to that folder. Navigate or open a command prompt window to that directory. Boot your phone into fastboot (power it off and power it back on holding the volume down key or just run "adb reboot bootloader" if you're in recovery). Run the following commands from the command prompt window when your phone is in the bootloader and your command prompt window is navigated to the folder you extracted XT1625_ATHENE_AMAZON...zip to (you can also copy and paste them all into command prompt):
Running the below commands unmodified will wipe your data. You can try to run them without the "fastboot erase userdata" command at the bottom to possibly save your data (I can't guarantee anything).
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
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 erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Again, I give no guarantees on this and probably won't be checking back on this thread for replying or updating. Also note, Amazon ads will return to your lock screen.
beano311 said:
Follow at your own risk.
This is how I was able to fix my softbrick after updating to -64 on my US XT1625 Amazon G4. Credit goes to Android Doctor (his YouTube tutorial), I changed his fastboot commands a little though to better match how a real Moto upgade would act (based off of the flashfile.xml file in the firmware zip.
From here download "XT1625_ATHENE_AMAZON_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" (Here's a direct link if it works for you).
Extract that zip to a folder and copy ADB/fastboot files to that folder. Navigate or open a command prompt window to that directory. Boot your phone into fastboot (power it off and power it back on holding the volume down key or just run "adb reboot bootloader" if you're in recovery). Run the following commands from the command prompt window when your phone is in the bootloader and your command prompt window is navigated to the folder you extracted XT1625_ATHENE_AMAZON...zip to (you can also copy and paste them all into command prompt):
Running the below commands unmodified will wipe your data. You can try to run them without the "fastboot erase userdata" command at the bottom to possibly save your data (I can't guarantee anything).
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
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 erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Again, I give no guarantees on this and probably won't be checking back on this thread for replying or updating. Also note, Amazon ads will return to your lock screen.
Click to expand...
Click to collapse
Will this work on a locked bootloader?
Mathracer1 said:
Will this work on a locked bootloader?
Click to expand...
Click to collapse
I think not. Check out the youtube link I posted. The first thing you see in the video description is "UNLOCKED BOOTLOADER REQUIRED BEFORE DOING THIS THIS,UNLOCKED BOOTLOADER RQUIRED BEFORE DOING THIS, UNLCOKED BOOTLOADER REQUIRED BEFORE DOING THIS". I'll update the main post to reflect this.
I tried this with a unlocked bootloader and it worked.
I then locked the bootloader at the last step. However, the software status still shows "modified". How do I make it official?
SemiConductor said:
I tried this with a unlocked bootloader and it worked.
I then locked the bootloader at the last step. However, the software status still shows "modified". How do I make it official?
Click to expand...
Click to collapse
I don't think there is a way of relock. Well, whatever you do and whatever you see on the screen or your PC says it has been locked again, the hardware counter tells the bootloader has been unlocked once. I read this from somewhere else on the internet. Correct me if it is wrong.
beano311 said:
I think not. Check out the youtube link I posted. The first thing you see in the video description is "UNLOCKED BOOTLOADER REQUIRED BEFORE DOING THIS THIS,UNLOCKED BOOTLOADER RQUIRED BEFORE DOING THIS, UNLCOKED BOOTLOADER REQUIRED BEFORE DOING THIS". I'll update the main post to reflect this.
Click to expand...
Click to collapse
Yes! its able to flash whith Locked Bootloader, but only flash oem, system, recovery, non-hlos, cache, userdata, flash boot, bootloader,gpt, always because a locked bootloader
Lussardi said:
Yes! its able to flash whith Locked Bootloader, but only flash oem, system, recovery, non-hlos, cache, userdata, flash boot, bootloader,gpt, always because a locked bootloader
Click to expand...
Click to collapse
Please could you specify better that I should install, I am desperate :llorando:
stephydth said:
Please could you specify better that I should install, I am desperate :llorando:
Click to expand...
Click to collapse
Code:
only flash oem, system, recovery, non-hlos, cache, userdata, boot, bootloader
download firmware zip extract and flash above mentioned
Hey all, I think many of you have already seen my post in the other thread, but in an effort to make it more visible to anyone that didn't see it and to new users, here it is again.
If a mod wants to make it a sticky, feel free.
Make sure you have fastboot working properly in your environment.
Code:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.
Here is a link to my original post in the other thread, replies following that have confirmation. Some folks have mentioned using only the enable command alone worked for them, but I haven't tried that myself. Also some oneplus 3 users have confirmed it works there as well.
** And the usual disclaimer.. I'm not responsible for any damage, issues, or your phone attacking you in your sleep due to the information I have provided **
th3g1z said:
Hey all, I think many/most of you have already seen my post in the other thread, but in an effort to make it more visible to anyone that didn't see it and to new users, here it is again.
If a mod wants to make it a sticky, feel free.
Make sure you have fastboot working properly in your environment.
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.
Here is a link to my original post in the other thread, replies following that have confirmation. Some folks have mentioned using only the enable command alone worked for them, but I haven't tried that myself. Also some oneplus 3 users have confirmed it works there as well.
http://forum.xda-developers.com/showpost.php?p=70698410&postcount=112
And the usual disclaimer.. I'm not responsible for any damage, issues, or your phone attacking you in your sleep due to the information I have provided.
Click to expand...
Click to collapse
Worked a treat. Brilliant now we just need a way to remove the bootloader message and bobs your uncle.
That was easy! Thank you so much
Some commands which I found from aboot.img.
Code:
oem boot_mode rf/wlan/ftm/normal
oem console
oem unconsole
oem dump
oem kmemleak detect
oem kmemleak undetect
oem reboot-shutdown
oem reboot-bootloader
oem boot_mode
oem disable_dm_verity
oem enable_dm_verity
oem force_training
oem unforce_training
oem datafs
oem unlock
oem lock
flashing unlock
flashing lock
flashing lock_critical
flashing unlock_critical
flashing get_unlock_ability
oem device-info preflash
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel
oem run-tests
Dump --->
Code:
aboot.img: OEM panel override:%s
aboot.img: OEM ID: 0x%x
aboot.img: Verified boot.img with oem keystore
aboot.img: Verification with oem keystore failed. Use embedded certificate for verification
aboot.img: If you don't want to see this screen, please lock your device by "fastboot oem lock" and erase userdata.
aboot.img: androidboot.ftm_mode=ftm_at ftm_console_silent androidboot.ftm_mode=ftm_wlan androidboot.ftm_mode=ftm_mos androidboot.ftm_mode=ftm_rf androidboot.ftm_mode=ftm_recovery mos fastboot add_pcba_number_cmdline add_console_cmdline add_rf_version_cmdline add_project_name_cmdline add_oem_dm_verity_cmdline_len add_battery_absent_cmdline add_reboot_mode_cmdline ˆ‘ ˆ‘(ˆ‘0ˆ‘4ˆ‘8ˆ‘Lˆ‘Tˆ‘`ˆ‘`ˆ‘`ˆ‘lˆ‘tˆ‘xˆ‘€ˆ‘ˆˆ‘add_pwron_reason_cmdline add_ddr_info_cmdline add_oem_angela_cmdline_len add_battery_absent_cmdline_len add_kmemleak_cmdline add_oem_secboot_cmdline_len add_rpmb_enable_status_cmdline_len ˆ‘œˆ‘Ü{ˆ‘¤ˆ‘¬ˆ‘´ˆ‘¼ˆ‘Ȉ‘add_pwron_reason_cmdline_len add_rpmb_enable_status_cmdline add_hw_version_cmdline_len add_hw_version_cmdline add_oem_angela_cmdline add_oem_secboot_cmdline add_selinux_cmdline_len add_reboot_mode_cmdline_len add_selinux_cmdline add_oem_dm_verity_cmdline add_rf_version_cmdline_len userdata fs type: %s enable force training
aboot.img: Kmemleak detect close default Kmemleak detect open Use 'fastboot oem boot_mode rf/wlan/ftm/normal' unlock device to dump keystore Dump partition: %s Partition table doesn't exist
aboot.img: platform/oneplus/op_cmdline.c dumpaddr failed to dump partition %02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X partition table doesn't exist unknown partition name oem console oem unconsole oem dump oem kmemleak detect oem kmemleak undetect oem reboot-shutdown oem reboot-bootloader oem boot_mode oem disable_dm_verity oem enable_dm_verity oem force_training oem unforce_training oem datafs COLD WARM androidboot.startupmode=pwrkey androidboot.startupmode=usb_charger androidboot.startupmode=dc_charger androidboot.startupmode=rtc androidboot.startupmode=unknow androidboot.startupmode=pon1 androidboot.startupmode=hard_reset androidboot.startupmode=SMPL true false %s: enter. cmdline_len=%d
aboot.img: unlocked! locked! Device already : %s oem unlock is not allowed yes recoveryfs androidboot.bootdevice= app/aboot/aboot.c boot_dev_buf androidboot.serialno= androidboot.verifiedbootstate= Devinfo paritition possibly corrupted!!!. Please erase devinfo partition to continue booting
aboot.img: oem_project_name product serialno Invalid partition index
aboot.img: flash: erase: continue oem unlock oem lock flashing unlock flashing lock flashing lock_critical flashing unlock_critical flashing get_unlock_ability oem device-info preflash oem enable-charger-screen oem disable-charger-screen oem off-mode-charge oem select-display-panel oem run-tests sbl sdi xbl hyp pmic green orange yellow red logging enforcing boot_linux_from_flash :ÿ&í p=c ÁÊ õò p=c H1 1 8 H1
aboot.img: ffbm- cmd_oem_runtests Running LK tests ...
Have fun.
I'm not responsible for any bricked devices
~LampunVarjostin
th3g1z said:
Hey all, I think many of you have already seen my post in the other thread, but in an effort to make it more visible to anyone that didn't see it and to new users, here it is again.
If a mod wants to make it a sticky, feel free.
Make sure you have fastboot working properly in your environment.
TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.
Here is a link to my original post in the other thread, replies following that have confirmation. Some folks have mentioned using only the enable command alone worked for them, but I haven't tried that myself. Also some oneplus 3 users have confirmed it works there as well.
** And the usual disclaimer.. I'm not responsible for any damage, issues, or your phone attacking you in your sleep due to the information I have provided **
Click to expand...
Click to collapse
Is it work for rooted ob 2?
'fastboot oem disable_dm_verity' did not worked on my phone.
ozzyville said:
'fastboot oem disable_dm_verity' did not worked on my phone.
Click to expand...
Click to collapse
You need to enter both commands. Disable and enable.
Thanks. It worked on Oneplus 3T but did not work on Oneplus 3.
Thanks
th3g1z said:
Hey all, I think many of you have already seen my post in the other thread, but in an effort to make it more visible to anyone that didn't see it and to new users, here it is again.
If a mod wants to make it a sticky, feel free.
Make sure you have fastboot working properly in your environment.
Code:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.
Here is a link to my original post in the other thread, replies following that have confirmation. Some folks have mentioned using only the enable command alone worked for them, but I haven't tried that myself. Also some oneplus 3 users have confirmed it works there as well.
** And the usual disclaimer.. I'm not responsible for any damage, issues, or your phone attacking you in your sleep due to the information I have provided **
Click to expand...
Click to collapse
It Worked On My 3T. Thanks Mate
Thanks, worked!
Same for oneplus 3?
lace79 said:
Same for oneplus 3?
Click to expand...
Click to collapse
It worked for my OP3
LampunVarjostin said:
Some commands which I found from aboot.img.
Code:
oem boot_mode rf/wlan/ftm/normal
oem console
oem unconsole
oem dump
oem kmemleak detect
oem kmemleak undetect
oem reboot-shutdown
oem reboot-bootloader
oem boot_mode
oem disable_dm_verity
oem enable_dm_verity
oem force_training
oem unforce_training
oem datafs
oem unlock
oem lock
flashing unlock
flashing lock
flashing lock_critical
flashing unlock_critical
flashing get_unlock_ability
oem device-info preflash
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel
oem run-tests
Dump --->
Code:
aboot.img: OEM panel override:%s
aboot.img: OEM ID: 0x%x
aboot.img: Verified boot.img with oem keystore
aboot.img: Verification with oem keystore failed. Use embedded certificate for verification
aboot.img: If you don't want to see this screen, please lock your device by "fastboot oem lock" and erase userdata.
aboot.img: androidboot.ftm_mode=ftm_at ftm_console_silent androidboot.ftm_mode=ftm_wlan androidboot.ftm_mode=ftm_mos androidboot.ftm_mode=ftm_rf androidboot.ftm_mode=ftm_recovery mos fastboot add_pcba_number_cmdline add_console_cmdline add_rf_version_cmdline add_project_name_cmdline add_oem_dm_verity_cmdline_len add_battery_absent_cmdline add_reboot_mode_cmdline ˆ‘ ˆ‘(ˆ‘0ˆ‘4ˆ‘8ˆ‘Lˆ‘Tˆ‘`ˆ‘`ˆ‘`ˆ‘lˆ‘tˆ‘xˆ‘€ˆ‘ˆˆ‘add_pwron_reason_cmdline add_ddr_info_cmdline add_oem_angela_cmdline_len add_battery_absent_cmdline_len add_kmemleak_cmdline add_oem_secboot_cmdline_len add_rpmb_enable_status_cmdline_len ˆ‘œˆ‘Ü{ˆ‘¤ˆ‘¬ˆ‘´ˆ‘¼ˆ‘Ȉ‘add_pwron_reason_cmdline_len add_rpmb_enable_status_cmdline add_hw_version_cmdline_len add_hw_version_cmdline add_oem_angela_cmdline add_oem_secboot_cmdline add_selinux_cmdline_len add_reboot_mode_cmdline_len add_selinux_cmdline add_oem_dm_verity_cmdline add_rf_version_cmdline_len userdata fs type: %s enable force training
aboot.img: Kmemleak detect close default Kmemleak detect open Use 'fastboot oem boot_mode rf/wlan/ftm/normal' unlock device to dump keystore Dump partition: %s Partition table doesn't exist
aboot.img: platform/oneplus/op_cmdline.c dumpaddr failed to dump partition %02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X partition table doesn't exist unknown partition name oem console oem unconsole oem dump oem kmemleak detect oem kmemleak undetect oem reboot-shutdown oem reboot-bootloader oem boot_mode oem disable_dm_verity oem enable_dm_verity oem force_training oem unforce_training oem datafs COLD WARM androidboot.startupmode=pwrkey androidboot.startupmode=usb_charger androidboot.startupmode=dc_charger androidboot.startupmode=rtc androidboot.startupmode=unknow androidboot.startupmode=pon1 androidboot.startupmode=hard_reset androidboot.startupmode=SMPL true false %s: enter. cmdline_len=%d
aboot.img: unlocked! locked! Device already : %s oem unlock is not allowed yes recoveryfs androidboot.bootdevice= app/aboot/aboot.c boot_dev_buf androidboot.serialno= androidboot.verifiedbootstate= Devinfo paritition possibly corrupted!!!. Please erase devinfo partition to continue booting
aboot.img: oem_project_name product serialno Invalid partition index
aboot.img: flash: erase: continue oem unlock oem lock flashing unlock flashing lock flashing lock_critical flashing unlock_critical flashing get_unlock_ability oem device-info preflash oem enable-charger-screen oem disable-charger-screen oem off-mode-charge oem select-display-panel oem run-tests sbl sdi xbl hyp pmic green orange yellow red logging enforcing boot_linux_from_flash :ÿ&í p=c ÁÊ õò p=c H1 1 8 H1
aboot.img: ffbm- cmd_oem_runtests Running LK tests ...
Have fun.
I'm not responsible for any bricked devices
~LampunVarjostin
Click to expand...
Click to collapse
how to get that's all list command?
Jeez, that was ridiculously easy. Thanks for finding this!!
not work on oneplus 3
It works on my Oneplus 3 A3000. Thanks. It was a little annoying.
zainifame said:
Some commands which I found from aboot.img.
Dump --->
how to get that's all list command?
Click to expand...
Click to collapse
https://www.google.fi/amp/s/www.xda...dden-fastboot-commands/amp/?client=ms-unknown
Thanks, worked on my oneplus 3.
well successfully disabled that dm verify message now one last thing can the disable bootloader unlock msg be disabled ..
Well, that was easy.
thanks
OEM unlock & usb debugging both are enabled in developer option... but giving same error, FAILED(remote:unknown command)
Follow the procedure as shown in the thread
Just try to flash with older stock firmware using SP Flash Tool.
I had a similar problem and the older firmware gave it up unlock bootloader without any problem.
When unlocking with fastboot keep the order:
fastboot oem unlock
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot format userdata
Please change name of twrp-3xx....img to twrp.img
how to see unlock key when our devices unlocked motorola e4plus
Code:
plcrazyprogrammer said:
Just try to flash with older stock firmware using SP Flash Tool.
I had a similar problem and the older firmware gave it up unlock bootloader without any problem.
When unlocking with fastboot keep the order:
fastboot oem unlock
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot format userdata
Please change name of twrp-3xx....img to twrp.img
Click to expand...
Click to collapse
I do not know whether my EFS and Persist are intact but I have backed them up. I had installed Pixel Experience 9.0 and then restored my TWRP backup to go to Stock Oreo, Build Number: OPSS28.85-13-5. This is my current Build, unlocked, rooted and has TWRP.
Can I follow this (https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738) guide to go back to Stock Nougat and then upgrade to the latest official update from moto?
I am asking to confirm as the Stock ROM given in the guide is Nougat ROM and I am on Oreo as mentioned above. I won't have any problems right? I do not want to lose VoLTE and my IMEI.
Any help will be appreciated.
Installed Oreo ROM via fastboot on my Moto G5 Plus [RETIN/Indian/ XT1686]
I am sharing my experience here so that it might help someone looking to flash stock ROM via fastboot. This is not meant to be a tutorial, but I will list out the steps I followed. I am not responsible if you mess up or hard/soft brick your device when following the steps I mentioned below. Always make a backup of your data/photos/videos/music and whatever else. Also make a backup with TWRP to be safe.
So instead of following the guide linked in the above post, I followed this one and successfully unrooted and returned to stock: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
But I did not use the ROM linked by the OP in that thread. Instead I downloaded this one : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This RETIN ROM works for me because I have the Indian XT1686. I don't know if it matters but I had the same version (13-5) before, but I am not sure whether it was RETAIL or RETIN.
Anyways guys make sure you download the right ROM for your device if you are going to install via fastboot. You can download the right ROM for your device from here: https://mirrors.lolinet.com/firmware/moto/potter/official/
There are different folders for ROMs of different regions in the above link. So carefully download the one your device is compatible with.
Also, I installed fastboot drivers from here: https://forum.xda-developers.com/showthread.php?t=2588979
Follow the instructions and also follow the video tutorials in the post to install fastboot drivers if your phone isn't detected in fastboot.
Then once I had downloaded the ROM and installed ADB, I extracted the ROM zip into a folder. Copy pasted ADB Files into the same folder (download ADB Files that worked for me _ attached to this post below).
FInally I put my phone in fastboot (turn off phone, then press volume down and power simultaneously till fastboot shows up). Connected the phone to my PC. Then opened CMD in the folder where I had extracted the ROM and copy pasted the ADB Files. To open cmd in a folder, just type cmd in the address bar of the folder and press enter.
And then I copy pasted the following code into the cmd window:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash 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 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
The above commands will run when pasted in cmd and your phone will be flashed with the ROM. It took a couple minutes to install and then I had to press enter while still in cmd to reboot the phone. Then the phone rebooted. Took a couple minutes more to boot, so stay patient. Then once the phone booted, I disconnected it from my PC and set the phone up as usual. DO NOT disconnect the phone when the fastboot commands are running and the ROM is being flashed. Note that the above fastboot commands will only flash the ROM. It will not lock the bootloader.
If you want to lock the bootloader then follow the instructions here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
Note that I haven't locked my bootloader. So you will have to try and see for yourself whether it locks your bootloader.
Also once I booted up I got update notification and was able to update to the Feb 2019 OTA security update. So I can for sure say that updates work. VoLTE, calling, camera, almost everything I checked works.
Cheers. :victory: