Database Users

Upgrade from Kit Kat leak to Kit Kat stock

I found a way to not return to stock It might work an any phone that is on the leak. I'm with Movistar Chile carrier
just fownload the file from here http://sbf.droid-developers.org/ghost/list.php and then flash as follow.
Please use the motorola fastboot.
Option 1
$ 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
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Option 2:
You can use also RSDlite, to do so remove the line from de xml
<step operation="getvar" var="max-download-size" />
also you can remove this lines:
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
if you have problems and cannot go out from bootloader using RSDlite you need to put the following commnad in fastboot mode.
fastboot oem fb_mode_clear
this will clear any bad flashing.
just did and it worked using option 1, didn't test the second option..
I'm not responsable for any bricked phones. My carrier is Movistar Chile and has been with tmobile version for a while.
Edit: Adding motorola fastboot for Linux, Mac and Windows.
Hope this help to anyone

everything worked except for system...that part failed on me.
C:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fastboot flash system s
ystem.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 820542232 is not a multiple of t
he block size 4096
sending sparse 'system' (4 KB)...
error: write_sparse_skip_chunk: don't care size 820542232 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 820542232 is not a multiple of t
he block size 4096
OKAY [ 0.283s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 0.718s

kcbboy said:
everything worked except for system...that part failed on me.
Click to expand...
Click to collapse
you need to make sure you have motorola fastboot. the standard android version doesn't work.

kcbboy said:
everything worked except for system...that part failed on me.
C:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fastboot flash system s
ystem.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 820542232 is not a multiple of t
he block size 4096
sending sparse 'system' (4 KB)...
error: write_sparse_skip_chunk: don't care size 820542232 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 820542232 is not a multiple of t
he block size 4096
OKAY [ 0.283s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 0.718s
Click to expand...
Click to collapse
Will update my post but indeed you need the Motorola fastboot. Otherwise wiki not work.

OP worked great. thanks given.
System Version on leak was 140.42.3.ghost_row.Retail.en.US. New version is 140.44.3.ghost_row.Retail.en.US just in case you were wondering

Glad it worms for you

For anyone impatient on Rogers (started with the official OTA update, bootloader unlcoked, TWRP installed in recovery)
Followed the instructions above, skipping the recovery (as I wanted to keep TWRP), but clearing cache just for good measure.
Seems to be working great! Thanks for the clear and simple post!
EDIT: I think some of my settings or XPosed modules were screwing stuff up. Quickly reset userdata and everything is great

nimnox said:
For anyone impatient on Rogers (started with the official OTA update, bootloader unlcoked, TWRP installed in recovery)
Followed the instructions above, skipping the recovery (as I wanted to keep TWRP), but clearing cache just for good measure.
Seems to be working great! Thanks for the clear and simple post!
Click to expand...
Click to collapse
You are welcome just tried to put to anyone who has the tmobile leak, and doesnt want to reverto to 4.2.2 stock.
I even had all my stuff in there

beelzebu said:
I found a way to not return to stock to have tmobile OTA.
just fownload the file from here http://sbf.droid-developers.org/ghost/list.php and then flash as follow.
Please use the motorola fastboot.
$ 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
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
just did and it worked.
I'm not responsable for any bricked phones. My carrier is Movistar Chile and has been with tmobile version for a while.
Hope this help to anyone
Click to expand...
Click to collapse
So you just grabbed TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip, and manually fastbooted based on the commands in the XML, minus erase cache and erase userdata, right?

KidJoe said:
So you just grabbed TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip, and manually fastbooted based on the commands in the XML, minus erase cache and erase userdata, right?
Click to expand...
Click to collapse
I did erase cache, but that is what I did over the leaked version from tmobile.

You can also use rsdlite and just edit the xml file to remove the get var line near the top and the $ fastboot erase userdata. That is likely as simple as it gets to go from the updated leak to the final release.

Steve-x said:
You can also use rsdlite and just edit the xml file to remove the get var line near the top and the $ fastboot erase userdata. That is likely as simple as it gets to go from the updated leak to the final release.
Click to expand...
Click to collapse
That's true, will added it to the thread. thx

beelzebu said:
That's true, will added it to the thread. thx
Click to expand...
Click to collapse
See option 3 (and/or 4) on -> http://forum.xda-developers.com/showthread.php?t=2536735

KidJoe said:
See option 3 (and/or 4) on -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
Thx @KidJoe just added to the thread. basically just wanted to inform what to do if you where on the tmobile leak and dont want to restore stock 4.2.2

I can say that it workos for any version of the phone that was on leak and maube if it wan´t on the leak to have the kitkar stock from VZ, AT&T or tmobile.

mandrsn1 said:
you need to make sure you have motorola fastboot. the standard android version doesn't work.
Click to expand...
Click to collapse
Do you know where I can find motorola fastboot for Mac?
tks!

fvc2000 said:
Do you know where I can find motorola fastboot for Mac?
tks!
Click to expand...
Click to collapse
Here are the mfastboot for linux/windows and Mac

beelzebu said:
Here are the mfastboot for linux/windows and Mac
Click to expand...
Click to collapse
Tks!
Another question...
The modem part of the flash is this, right?
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
so IF the att modem doesn't work anymore with Band7, could I use this commands to flash the LEAK modem?

fvc2000 said:
Tks!
Another question...
The modem part of the flash is this, right?
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
so IF the att modem doesn't work anymore with Band7, could I use this commands to flash the LEAK modem?
Click to expand...
Click to collapse
That could work, I havent tested as dont have 4g yet. You can try it. You can even flash original files if I'm not mistaken. Even you can flash the AT&T ones as they have almost all bands.
I think you should try out.

I'm also a Movistar CL user, to flash any version of firmware bootloader unlocked is required, right?
Enviado desde mi Moto X

[TUTORIAL] Going back to KK from Soak Lollipop

Hello, I'm trying to help people who installed the soak test of Lollipop but is not enjoying the ROM with lots of bugs and want to go back to KK.
THIS IS ONLY FOR XT1225, BRAZILIAN FIRMWARE RETAIL UPDATED VIA OTA
YOU NEED TO HAVE YOUR BOOTLOADER UNLOCKED
It will work even if you have root on lollipop
Do it at your own risk!
So, this is the procedure:
DOWNLOADS
1 - Download the Stock ROM from here:
RETBR_XT1225_4.4.4_KXG21.50-9
2 - Download Motorola Drivers from HERE
3 - Download Moto Fastboot from HERE
* IT NEED TO BE MOTO FASTBOOT, known as "mfastboot" . Android Fastboot wont handle the system flash.
INSTRUCTIONS
1 - Backup your phone, otherwise you will lose everything on it
2 - Extract ROM files to a folder (I did on " C:\MAXX\ " )
3 - Extract Moto Fastboot files on same folder you extracted the ROM
4 - Shutdown your phone and put it on fastboot mode (when off, press Power Button + Volume down)
5 - Plug your phone on your PC
6 - Install Motorola Drivers NOW. (For me it only install the driver at this time. If you have the proper driver installed already, skip this step)
7 - Open a command prompt and go to the folder that you extracted the ROM and Moto fastboot
8 - Now, you need to type every line, pressing enter when is a new line and waiting the process to be sucessfully
Code:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
For me it worked, now your phone will reboot and boot right again on KK
I had tried to do with RSD Lite but it always fail on flash the partition.
So, this procedure above is tested by me and it works.

Well all i just did was to restore my twrp backup and then flash my radio.img and that's it didn't lose anything and my cell works like charm just like before flashing lollipop

These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!

Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
remember that this tutorial is ONLY FOR WHO UPDATES WITH OTA.
if u updated the phone with official OTA ,u can t downgrade to 4.4.4
or if the firmware img of 5.0.2 will go out and u will flash it U CAN T GO BACK TO 4.4.4 either.
always make a nandroid backup in twrp of 4.4.4 .it will be useful.

I've received a OTA without TWRP.... so, I did not could make a nandroid

Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
This was the case with the 2013 Moto X, there is no such problem with the 2014 model. It is unlikely to be a problem with the XT1225. Motorola learned from that mistake.

do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?

arcaneck said:
do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?
Click to expand...
Click to collapse
Did you install the lollipop via OTA after flashing brazilian firmware ?

yes i did

It's the same procedure but with the mx firmware

works fine thanks

Works for me too

do you have the mx ota?

Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!

I've installed the zip file of the soak test (I didn't receive it through OTA), will this procedure work for me? Really tired of the instability of 5.0.2

I have the same problem
megadu said:
Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!
Click to expand...
Click to collapse
I have the same problem.
After the command "mfastboot flash boot boot.img ". Do not process more.
Can anyone help me? Please!

Have you unlocked the bootloader?

boot.img can never been be downgraded. If you downgrade from version 5.x to 4.4.4 you have to skip that file.

I update my motorola using this guide http://forum.xda-developers.com/droid-turbo/general/guideinstall-lollipop-ota-root-ur-moto-t3029690 , can i do the downgrade ?
Thanks!

im have the same question, im using now cm12 with twrp, bootloader unlocked. can i go back to stock 4.4.4 using this tutorial? its safe?

Stock ROM Nougat 7.0 For Moto G4 Plus XT1643

Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
edit :
head to this link for flashing procedure and lock/ re-lock the bootloader on moto g4 plus :
https://forum.xda-developers.com/showpost.php?p=70383231&postcount=15

http://forum.xda-developers.com/mot...d-ota-nougat-ota-moto-g4-plus-t3517059/page37
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk

zazzy24 said:
http://forum.xda-developers.com/mot...d-ota-nougat-ota-moto-g4-plus-t3517059/page37
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
this is captured ota I'm asking for updated stock rom for flashing.. thanks for your head up (Y)

snd team said:
this is captured ota I'm asking for updated stock rom for flashing.. thanks for your head up (Y)
Click to expand...
Click to collapse
It isn't released. That's already discussed.

snd team said:
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
Click to expand...
Click to collapse
Find it here. It's flashable ROM zip:
removed link.. mod edit: not flashable..

removed link.. mod edit: not flashable..
Anyone tried this ? is it compatible with Indian (XT1643) version?

Arivendu said:
Find it here. It's flashable ROM zip:
removed link.. mod edit: not flashable..]
Click to expand...
Click to collapse
Don't misguide users. You shouldn't post if you are not sure about something.
First, its not a zip file. Its a rar file.
Second, its not flashable. You need to flash it using fastboot.

Arivendu said:
Find it here. It's flashable ROM zip:
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Click to expand...
Click to collapse
Thanks buddy you're the best
praveenbda said:
Anyone tried this ? is it compatible with Indian (XT1643) version?
Click to expand...
Click to collapse
yes sure see the topic title and also tested on XT1643

also I'm able to re-lock the bootloader

TO relock the bootloader and Flashing
First of all download the stock firmware rar file ( thanks to Arivendu for heads up) - multi platform support (windows linux etc)
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Mirrors :
https://files.fm/u/hfapbktm
https://drive.google.com/open?id=0B-ReAPgYg5ISNFpaeV92V2hRaWc
https://mega.nz/#!0oV33RhI!5U51UqC4v16qTSN5ur6FAV7EOpLTXL0Pfm12n71GGwc
***** this firmware also worked for other moto g4 variants *****
extract it
open folder name : athene_oem_user_7.0_NPJ25.93-11_12_release
under the folder their is a folder name "Windows"
copy files from "windows" folder to root folder
and use below command to re-lock bootloader and flash your phone with latest version of stock 7.0 (tested on xt1643)
SHIFT + Mouse right click >>> open command window here
and enter this commands one by one
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
Or download the oem unlock and flash mobile.zip (833.6 KB) from atatchment and place the files in root dir where you extracted the firmware
and run the OEM lock.bat file for automation
if the device not reboot after firmware flash run this command at the end :
Code:
fastboot reboot

I can confirm that rar contains factory images and it's working fine on my Moto G4 Plus XT1644 64GB/4Gb RAM (RETUS). Finally, running Nougat on my device.

snd team said:
no i don't have any link and i confirm it is original moto firmware
Click to expand...
Click to collapse
Thanks, I had a browse and it looks like it's from http://lenovo-forums.ru/topic/22076-moto-g⁴-plus-npj2593-11/
Although the website says they are not an official Lenovo forum, if it's working for people, that's great. It'd be nice if we get a Nougat ROM we can flash in stock recovery without adb fastboot

Massive cleaning on the thread.. Please be warry of whatever type of file you are flashing on your devices.. A little mistake will brick your devices. I hope no one will post again a non-flashable zip.. and pls. put into considerations the knowledge of others. Not everyone knows what a RAR file or a ZIP file is... Please be cautious.. AND LASTLY .. NO FLAMING ..... NEVER ALLOWED HERE

reyscott said:
Massive cleaning on the thread.. Please be warry of whatever type of file you are flashing on your devices.. A little mistake will brick your devices. I hope no one will post again a non-flashable zip.. and pls. put into considerations the knowledge of others. Not everyone knows what a RAR file or a ZIP file is... Please be cautious.. AND LASTLY .. NO FLAMING ..... NEVER ALLOWED HERE
Click to expand...
Click to collapse
thanks for cleaning cheers

Fastboot flashing steps
snd team said:
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
edit :
head to this link for flashing procedure and lock/ re-lock the bootloader on moto g4 plus :
https://forum.xda-developers.com/showpost.php?p=70383231&postcount=15
Click to expand...
Click to collapse
Hi guys
I have an XT1643 and I have downloaded the firmware mentioned below. It was a 7z compressed file with password as "lenovo-forums.ru"
"athene_oem_user_7.0_NPJ25.93-14_16_release.7z"
I couldn't find the commands for flashing this through bootloader. If someone may know a solution, could you please post the command or guide me?
thanks

shailuo said:
Hi guys
I have an XT1643 and I have downloaded the firmware mentioned below. It was a 7z compressed file with password as "lenovo-forums.ru"
"athene_oem_user_7.0_NPJ25.93-14_16_release.7z"
I couldn't find the commands for flashing this through bootloader. If someone may know a solution, could you please post the command or guide me?
thanks
Click to expand...
Click to collapse
The fastboot commands are the same as in the post you linked in your quote. Alternatively, you may refer to the instructions listed here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
One way to flash your stock ROM is (just expanding on the instructions mentioned previously):
1) Download the Motorola drivers and minimal adb tool from the links here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Install the drivers and tool as directed by the installers.
2)Extract the 7z ROM with your preferred decompression tool (that can handle .7z file types). The resulting folder should be about 2 GB. Copy the files (from the extracted stock ROM) to your adb folder (may be on your C:\ drive, you may have to give permission to copy).
3)Connect your device to your computer. Enable USB debugging.
3a)Once recognised by your computer, open the adb terminal and type/execute 'adb devices' without the quotes. Your device should return back its serial number if properly detected.
4)Back up all necessary data and files to your computer. Flashing a fastboot ROM may wipe your data from your device.
5)Reboot your device to bootloader mode.
5a) Re-confirm you can still detect your device in fastboot mode by executing 'fastboot devices'. Should get your serial number again.
6)Run the commands as directed in the fastboot ROM thread in the adb terminal.
6a)These commands are for relocking your bootloader:
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
6b) If you don't wish to type all this, you may wish to download and run the scripts from this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Ensure you copy the scripts to the adb folder, where your ROM files and the adb terminal should be. There should be 2 scripts there, one for if you want to relock your bootloader, one if you don't wish to.

getting error whilw flashing
snd team said:
First of all download the stock firmware rar file ( thanks to Arivendu for heads up) - multi platform support (windows linux etc)
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Mirrors :
https://files.fm/u/hfapbktm
https://drive.google.com/open?id=0B-ReAPgYg5ISNFpaeV92V2hRaWc
https://mega.nz/#!0oV33RhI!5U51UqC4v16qTSN5ur6FAV7EOpLTXL0Pfm12n71GGwc
***** this firmware also worked for other moto g4 variants *****
extract it
open folder name : athene_oem_user_7.0_NPJ25.93-11_12_release
under the folder their is a folder name "Windows"
copy files from "windows" folder to root folder
and use below command to re-lock bootloader and flash your phone with latest version of stock 7.0 (tested on xt1643)
SHIFT + Mouse right click >>> open command window here
and enter this commands one by one
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
Or download the oem unlock and flash mobile.zip (833.6 KB) from atatchment and place the files in root dir where you extracted the firmware
and run the OEM lock.bat file for automation
if the device not reboot after firmware flash run this command at the end :
Code:
fastboot reboot
Click to expand...
Click to collapse
log:
Fastboot device is ready
There are 1 device(s) connected: ZY2237XWMH
Trying to flash device ZY2237XWMH
Starting flashing device ZY2237XWMH...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s ZY2237XWMH flash partition gpt.bin"
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.048s
All devices are flashed
Press any key to continue .
Iam getting same error even while flshing without bootloader and GPT. (Iam trying downgrade from 7.1.2 to stock 7.0)
please help me with this

Udaya.kr said:
log:
Fastboot device is ready
There are 1 device(s) connected: ZY2237XWMH
Trying to flash device ZY2237XWMH
Starting flashing device ZY2237XWMH...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s ZY2237XWMH flash partition gpt.bin"
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.048s
All devices are flashed
Press any key to continue .
please help me with this
Click to expand...
Click to collapse
What firmware did you have previously on your device, and are you trying to relock your bootloader? The firmware linked here is quite old (November 2016 security patch), and the warning you're getting suggests you have newer firmware on your device.
If you're on the June update, do not flash this firmware.

echo92 said:
What firmware did you have previously on your device, and are you trying to relock your bootloader? The firmware linked here is quite old (November 2016 security patch), and the warning you're getting suggests you have newer firmware on your device.
If you're on the June update, do not flash this firmware.
Click to expand...
Click to collapse
Successfully flashed june firmware and re locked bootloader. thank you for your help.

Udaya.kr said:
Successfully flashed june firmware and re locked bootloader. thank you for your help.
Click to expand...
Click to collapse
Can you please share the link for june fastboot rom for XT1643?

Moto G boots only into TWRP

My XT1625 has an unlocked bootloader and TWRP installed. Today I got a notification that the Sept security patch was available so I downloaded it and tried to install. I was paying attention until I noticed it booted back into TWRP and does it everytime so I guess accepting and installing that patch was a no-no. I got it to boot into Android from instructions in another post.
Can I locate the patch in TWRP and flash it from there? Btw, I did notice that the patch was only 49MB so it clearly wasn't the entire Nougat ROM.

lmacmil said:
My XT1625 has an unlocked bootloader and TWRP installed. Today I got a notification that the Sept security patch was available so I downloaded it and tried to install. I was paying attention until I noticed it booted back into TWRP and does it everytime so I guess accepting and installing that patch was a no-no. I got it to boot into Android from instructions in another post.
Can I locate the patch in TWRP and flash it from there? Btw, I did notice that the patch was only 49MB so it clearly wasn't the entire Nougat ROM.
Click to expand...
Click to collapse
You cannot flash an official OTA update. You need to be on official recovery for this. Have a look at here, same question https://forum.xda-developers.com/moto-g4-plus/help/luck-moto-g4-plus-flashable-logo-bin-t3701652
For update its advisable to use the full stock rom to be flashed with fastboot like this one https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Please use always search function as this happens every week a few times and same question is answered already enough.
Also worth having a look here https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and also ask here.

strongst said:
You cannot flash an official OTA update. You need to be on official recovery for this. Have a look at here, same question https://forum.xda-developers.com/moto-g4-plus/help/luck-moto-g4-plus-flashable-logo-bin-t3701652
I saw that other post and edited mine to acknowledge that I saw the fix (see last sentence of 1st paragraph.)
For update its advisable to use the full stock rom to be flashed with fastboot like this one https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Thanks. I probably won't go to that much trouble.
Please use always search function as this happens every week a few times and same question is answered already enough. I generally do.
Also worth having a look here https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and also ask here.
Click to expand...
Click to collapse
I rebooted and it went back to TWRP again. I will ask how to fix this in the help thread.

lmacmil said:
I rebooted and it went back to TWRP again. Will I have to boot to fastboot mode and select factory mode every time now or is there a fix that will boot into Android instead of TWRP?
Click to expand...
Click to collapse
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear

____Mdd said:
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I will give it a try.

lmacmil said:
I will give it a try.
Click to expand...
Click to collapse
use the following script :
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 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

____Mdd said:
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Got error messages:
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.008s

siddhesh9146 said:
use the following script :
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Is this going to wipe my system like a factory reset? If so, can I just restore the backup I made after I installed TWRP initially? Or just do a factory reset?

@lmacmil ignore it, use both commands then try to boot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
lmacmil said:
Is this going to wipe my system like a factory reset? If so, can I just restore the backup I made after I installed TWRP initially? Or just do a factory reset?
Click to expand...
Click to collapse
Don't use it if you are thinking to just run script and not to flash... since it has "erase modemst1 & 2" it will erase modem, but will not flash fsg/modem, also "erase data" will wipe everything on phone.. this can put you in trouble..
Instead of doing this, as strongst said in his post, flash complete firmware, see the link for september's update he gave in his post.
Then move everything from your phone to PC (images / video/ etc)
Then flash firmware...

____Mdd said:
@lmacmil ignore it, use both commands then try to boot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
Don't use it if you are thinking to just run script and not to flash... since it has "erase modemst1 & 2" it will erase modem, but will not flash fsg/modem, also "erase data" will wipe everything on phone.. this can put you in trouble..
Instead of doing this, as strongst said in his post, flash complete firmware, see the link for september's update he gave in his post.
Then move everything from your phone to PC (images / video/ etc)
Then flash firmware...
Click to expand...
Click to collapse
Still boots to TWRP. Maybe this is the time to move to LineageOS 14.1. I was going to wait until 15 was stable but if I'm going to lose everything, I might as well get more up to date.
This seems to have killed my cell signal too. Just noticed that last time I booted to Android.

lmacmil said:
Still boots to TWRP. Maybe this is the time to move to LineageOS 14.1. I was going to wait until 15 was stable but if I'm going to lose everything, I might as well get more up to date.
This seems to have killed my cell signal too. Just noticed that last time I booted to Android.
Click to expand...
Click to collapse
Did you flash complete stock ROM ?
Move your files to External Storage then try it.

____Mdd said:
Did you flash complete stock ROM ?
Move your files to External Storage then try it.
Click to expand...
Click to collapse
I decided since I would have to reinstall all my apps anyway that I would flash LineageOS 14.1, which I did. I did the appropriate wipes (data, system, cache, Dalvik/ART), then flashed the latest nightly and Gapps. It was successful but it's still booting into TWRP and I still have no cell service. I thought that a complete wipe and installation of new ROM would correct those issues but it did not. And since it didn't, I'm not confident that flashing the stock ROM would either but unless there's something else to try, I will do it. One concern I have is I have a plain G4 and the ROM is for the G4 Plus. My build was NPJ25.93-14.5 and I think the Plus build is NPJS... Not sure if that makes a difference.
Maybe I should restore my original Nandroid backup first and see if that fixes things.

lmacmil said:
. My build was NPJ25.93-14.5 and I think the Plus build is NPJS... Not sure if that makes a difference.
Click to expand...
Click to collapse
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
If this too doesn't work, then you have to find correct firmware for your phone and flash it..
EDIT: for easiness to find correct firmware, restore backup, then see "about phone" for build number, it will help to find firmware..
EDIT-2:
I found 2 firmware of version you said,
But one says Amazon and another doesn't. You have Nandroid, restore and check your phone build..
Then go for following one correctly..
AMAZON : Click here
Non-AMAZON : Click here

____Mdd said:
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
If this too doesn't work, then you have to find correct firmware for your phone and flash it..
EDIT: for easiness to find correct firmware, restore backup, then see "about phone" for build number, it will help to find firmware..
EDIT-2:
I found 2 firmware of version you said,
But one says Amazon and another doesn't. You have Nandroid, restore and check your phone build..
Then go for following one correctly..
AMAZON : Click here
Non-AMAZON : Click here
Click to expand...
Click to collapse
Mine was the non-Amazon version. See attachment. The software channel was "retus" and the baseband version also said "ATHENE_RETUSA_CUST" The Amazon version software channel is amz.
I was able to get the bootloader unlock code from Motorola and they don't allow the Amazon versions to be unlocked.
I'll try your suggestions. Thanks for your continued help.

____Mdd said:
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
Click to expand...
Click to collapse
This is what I got:
D:\Computer\Minimal ADB and Fastboot>fastboot devices
ZY223N5GLF fastboot
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Computer\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12530 KB)...
OKAY [ 0.402s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.190s]
finished. total time: 0.595s
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.001s]
finished. total time: 0.001s
=================================
Not sure why I'm getting the bootloader error messages but I backed up just the bootloader recently so am going to restore that and see what happens.

@lmacmil that "not found" is ignorable, just check you get "OKAY" after one command ends... Since GPT and Bootloader commands got "OKAY" they are flashed successfully..... Go for complete firmware...

____Mdd said:
@lmacmil that "not found" is ignorable, just check you get "OKAY" after one command ends... Since GPT and Bootloader commands got "OKAY" they are flashed successfully..... Go for complete firmware...
Click to expand...
Click to collapse
I guess I need to bite the bullet and do this. It will install stock recovery and erase TWRP, right? If that's the case, and I don't relock the bootloader, will I be able to accept the OTA update? Or does an unlocked bootloader prevent OTA updates?
Last question: I just extract the firmware .zip file to the same folder where fastboot and adb reside? Then type the commands one by one (or copy/paste from the script shown in the thread about flashing stock firmware.)
Thanks again.

lmacmil said:
I guess I need to bite the bullet and do this. It will install stock recovery and erase TWRP, right?
Click to expand...
Click to collapse
Yes, it will install stock recovery, you will have to install TWRP again.
If that's the case, and I don't relock the bootloader, will I be able to accept the OTA update? Or does an unlocked bootloader prevent OTA updates?
Click to expand...
Click to collapse
It will be fine, You will have successful installation with unlocked bootloader too, no need to lock back..
Last question: I just extract the firmware .zip file to the same folder where fastboot and adb reside? Then type the commands one by one (or copy/paste from the script shown in the thread about flashing stock firmware.)
Thanks again.
Click to expand...
Click to collapse
You did right, that's why there is "OKAY" when command end, see your own post where you asked for "not found" error... Keep Going..

____Mdd said:
Yes, it will install stock recovery, you will have to install TWRP again.
You did right, that's why there is "OKAY" when command end, see your own post where you asked for "not found" error... Keep Going..
Click to expand...
Click to collapse
Success! Just flashed the stock Nougat ROM and as soon as it booted up, I let it download and install the Sept security patch. I am now on NPJ25.93-14.7.
Thanks again for all your help.
Lee

Moto G5 plus - Cant' relock bootload : (bootloader) Still require signed boot.img

I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked. That's weird, I thought a phone with open bootloader would not receive OTA, but mine does.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damn thing.
Everything works fine, except for Netflix that can't be installed no longer and my bank software who keeps complaining.
C:\MinimalADBFastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.099s]
finished. total time: 0.161s
C:\MinimalADBFastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.285s]
finished. total time: 0.689s
C:\MinimalADBFastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.491s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.364s]
finished. total time: 0.861s
I just dunno what to do to relock, any advice ?

CanadianGixxerman said:
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked. That's weird, I thought a phone with open bootloader would not receive OTA, but mine does.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damn thing.
Everything works fine, except for Netflix that can't be installed no longer and my bank software who keeps complaining.
C:\MinimalADBFastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.099s]
finished. total time: 0.161s
C:\MinimalADBFastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.285s]
finished. total time: 0.689s
C:\MinimalADBFastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.491s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.364s]
finished. total time: 0.861s
I just dunno what to do to relock, any advice ?
Click to expand...
Click to collapse
An unlocked bootloader has nothing to do with getting OTA updates. At least you get the unlock code from the manufacturer himself.
Only changes in /system or /vendor like rooting or other tweaks make OTA fail.
About locking the BL, a bit of research would have taken you here: https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
For Oreo the whole sets of commands are for
Locking:
-----------------
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
-------------------
Flashing:
-------------------
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
--------------------
Edited because of wrong number of sparechunk files for Oreo firmwares.

@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.

CanadianGixxerman said:
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
Click to expand...
Click to collapse
You can get signed images from Lenovo Moto smart assistant app, just go for rescue and let the firmware gets download, then go to the c/LMSA/ROM there you can find the firmware which has signed, use that image for locking bootloader, then you can lock your bootloader.and don't get anger on wolfcity he just try to help you as, some person don't know how to lock bootloader so they just post on XDA without reading the other thread only.

CanadianGixxerman said:
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
Click to expand...
Click to collapse
I don't wanted to sound rude or something like that.
You didn't mention that you used all the fastboot locking commands in you first post, you just posted three lines of flashing boot, recovery and logo.
So no offense.
What sounds strange to me is that Netflix and your banking app aren't working with an unlocked bootloader. Normally these applications are looking for traces of rooting methods like magisk or SuperSU. I'm unlocked and rooted with magisk and Netflix is working for me if I put in on magisk's hide list. Maybe you have some files on your device that trigger these anti rooting mechanisms? Sometimes just a file or folder named magisk could be enough.

Wolfcity said:
I don't wanted to sound rude or something like that.
You didn't mention that you used all the fastboot locking commands in you first post, you just posted three lines of flashing boot, recovery and logo.
So no offense.
What sounds strange to me is that Netflix and your banking app aren't working with an unlocked bootloader. Normally these applications are looking for traces of rooting methods like magisk or SuperSU. I'm unlocked and rooted with magisk and Netflix is working for me if I put in on magisk's hide list. Maybe you have some files on your device that trigger these anti rooting mechanisms? Sometimes just a file or folder named magisk could be enough.
Click to expand...
Click to collapse
No hard feelings.
It turns out that with your instructions (1st part : Locking) I was sucessful at my aim, finally. It did whine again about the signed image requirement after line 2, I continued [9 sparsechunks though, not 5 ... ], then, upon hitting «enter» after the last line [fastboot oem lock], Shazam, it locked.
You may be right about some left over garbage files [or traces of] that could still be present in the file system. I have loaded many customs roms last year on this phone, magisk and SuperSu as well.
Last but not least : Thank you.

CanadianGixxerman said:
No hard feelings.
It turns out that with your instructions (1st part : Locking) I was sucessful at my aim, finally. It did whine again about the signed image requirement after line 2, I continued [9 sparsechunks though, not 5 ... ], then, upon hitting «enter» after the last line [fastboot oem lock], Shazam, it locked.
You may be right about some left over garbage files [or traces of] that could still be present in the file system. I have loaded many customs roms last year on this phone, magisk and SuperSu as well.
Last but not least : Thank you.
Click to expand...
Click to collapse
Good to hear it worked out for you at last.
Seems that these "unsigned" messages are nothing to worry about to much. Sorry for the "sparechunk thing", copied the wrong flashall.bat file, this is the one for Oreo :https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
with 8 sparechunk files.
Last but not least: You're welcome.

Yeah this same thing happened to me today morning.. most guides have till sparsechunk4.. where as oreo has uptill 8.. so u need to flash the rest i.e 5,6,7,8. And then it will lock..

Wolfcity said:
Good to hear it worked out for you at last.
Seems that these "unsigned" messages are nothing to worry about to much. Sorry for the "sparechunk thing", copied the wrong flashall.bat file, this is the one for Oreo :https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
with 8 sparechunk files.
Last but not least: You're welcome.
Click to expand...
Click to collapse
I also had same error. Followed what you said. Finally locked bootloader. I am very happy now.
Thank you.

Might be good for someone who has gone through it, to make a new write-up, with current info. The longer these phones have been out, and bootloader unlocked, the more fragmented the info gets. It gets harder to know what currently works, and what could possibly "fubar" the phone.

[email protected] said:
Might be good for someone who has gone through it, to make a new write-up, with current info. The longer these phones have been out, and bootloader unlocked, the more fragmented the info gets. It gets harder to know what currently works, and what could possibly "fubar" the phone.
Click to expand...
Click to collapse
What do you mean? An "locking BL guide" or something more complete like "flashing/locking/encrypting/rooting"? I'm willing to that but I have to know what you guys need.

Wolfcity said:
What do you mean? An "locking BL guide" or something more complete like "flashing/locking/encrypting/rooting"? I'm willing to that but I have to know what you guys need.
Click to expand...
Click to collapse
Sure,,,, all of it! I unlocked my first G5 plus a year and a half ago. I have hard bricked it 3 times, and now use it for a test phone, as it has an addison bootloader. My everyday G5 plus is unlocked and rooted, but I've kept it on stock roms and kernels, due to a little fear of how easily these can be corrupted. I am certainly not ignorant of most of the workings with these, even going so far as to use Qualcomm's factory utilities to dig deep inside. However, that being said, what worked when I first unlocked my original, isn't totally pertinent today. Nougat and Oreo factory roms, nougat, oreo, pie developer roms, 64 bit and 32 bit, all add to a confusing set list of what can be safely done without irreversible consequences. I've kept up on these forums for almost 2 years, but the fragmentation of guides makes it confusing enough for myself, much less a novice. Example of things that can go wrong to unsuspecting, is the loss of touchscreen with stock oreo. I haven't experienced it, but it is out there. I'm just saying it would be hugely beneficial for all, if we could get some current guides, stickied in place of our outdated ones. I have the test phone that I have put through the wringer, and am more than willing to use it as a guinea pig for any other processes that may add to the guides.

[email protected] said:
Sure,,,, all of it! I unlocked my first G5 plus a year and a half ago. I have hard bricked it 3 times, and now use it for a test phone, as it has an addison bootloader. My everyday G5 plus is unlocked and rooted, but I've kept it on stock roms and kernels, due to a little fear of how easily these can be corrupted. I am certainly not ignorant of most of the workings with these, even going so far as to use Qualcomm's factory utilities to dig deep inside. However, that being said, what worked when I first unlocked my original, isn't totally pertinent today. Nougat and Oreo factory roms, nougat, oreo, pie developer roms, 64 bit and 32 bit, all add to a confusing set list of what can be safely done without irreversible consequences. I've kept up on these forums for almost 2 years, but the fragmentation of guides makes it confusing enough for myself, much less a novice. Example of things that can go wrong to unsuspecting, is the loss of touchscreen with stock oreo. I haven't experienced it, but it is out there. I'm just saying it would be hugely beneficial for all, if we could get some current guides, stickied in place of our outdated ones. I have the test phone that I have put through the wringer, and am more than willing to use it as a guinea pig for any other processes that may add to the guides.
Click to expand...
Click to collapse
You're lucky you have the ability to financially purchase a second G5 Plus to use as a failsafe. When I purchased mine it was roughly around $300-400 (was brand new) so to have purchased another at the time wasn't an option, and may as well purchase a 700+ flagship with that money. To this day I've owned over 30 devices and tested well over that. Thus far only the Galaxy S2 and the Motorola G5 Plus were the only two that have surpassed a year with good stable service. I don't even purchase the phone cases cause devices are supposed to be visually appealing like cars, because tech will always be sexxy. Anyways, my point was since the Photon Q back in early 2014 to this G5 Plus, I've really liked Motorola. If you take the time the align this phone purrs. But I need to upgrade soon as.. Thinking of getting a Pixel 3 when it reaches my shores.. Anyways, it's 1:28am, goodnight.

I was able to purchase the second phone for less than $100 US, slightly used. So it was a no brainer to have a guinea pig phone.

Wolfcity said:
An unlocked bootloader has nothing to do with getting OTA updates. At least you get the unlock code from the manufacturer himself.
Only changes in /system or /vendor like rooting or other tweaks make OTA fail.
About locking the BL, a bit of research would have taken you here: https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
For Oreo the whole sets of commands are for
Locking:
-----------------
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
-------------------
Flashing:
-------------------
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
--------------------
Edited because of wrong number of sparechunk files for Oreo firmwares.
Click to expand...
Click to collapse
Hi!!
I need to relock my Moto G5 Plus, because my country use a Covid App to transit trough states.
And I need it to use because I´m a essential worker. This App check the locked / unlocked devices.
I Know that Netlix do the same, but it never mattered to me to that app.
Now I really need to Re Locked my phone
I have tried several methods.. and doesn´t work any of them

Mr.BUBU said:
Hi!!
I need to relock my Moto G5 Plus, because my country use a Covid App to transit trough states.
And I need it to use because I´m a essential worker. This App check the locked / unlocked devices.
I Know that Netlix do the same, but it never mattered to me to that app.
Now I really need to Re Locked my phone
I have tried several methods.. and doesn´t work any of them
Click to expand...
Click to collapse
You can orientate yourself by this guide but as the one is for Nougat you need to correct the number of the sparechunk files:
How to re-lock Bootloader of all Potter version
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader. DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm...
forum.xda-developers.com
So the first set of commands should be:
First set:
Lock.
Code:
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
Second set:
Flashing firmware.
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
Device is now full stock with locked bootloader.
For the second set of commands you can use a flashall.bat file like this:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
It may look like the first set would be enough but that's not true, you have to flash the whole firmware afterwards.
Be aware that all of your internal data (apps, settings and everything you have in internal storage) will be erased so make backups of everything. Also backup all partitions with TWRP especially persist and efs!
This tutorial may help you to find the correct firmware for your device (links available) and also guide you through the flashing process of the whole firmware;
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Maybe use also the tools and drivers from there.

Wolfcity said:
You can orientate yourself by this guide but as the one is for Nougat you need to correct the number of the sparechunk files:
How to re-lock Bootloader of all Potter version
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader. DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm...
forum.xda-developers.com
So the first set of commands should be:
First set:
Lock.
Code:
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
Second set:
Flashing firmware.
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
Device is now full stock with locked bootloader.
For the second set of commands you can use a flashall.bat file like this:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
It may look like the first set would be enough but that's not true, you have to flash the whole firmware afterwards.
Be aware that all of your internal data (apps, settings and everything you have in internal storage) will be erased so make backups of everything. Also backup all partitions with TWRP especially persist and efs!
This tutorial may help you to find the correct firmware for your device (links available) and also guide you through the flashing process of the whole firmware;
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Maybe use also the tools and drivers from there.
Click to expand...
Click to collapse
Wait so I have to run the bootloader lock first and then flash the firmware for my Motorola one p30 play as well?

smartasiankid said:
Wait so I have to run the bootloader lock first and then flash the firmware for my Motorola one p30 play as well?
Click to expand...
Click to collapse
No, the user who was asking wanted to lock his BL so I gave him the lock commands too.
I don't know anything about your device but normally the BL has to be unlocked to flash firmware on a Moto.

Wolfcity said:
No, the user who was asking wanted to lock his BL so I gave him the lock commands too.
I don't know anything about your device but normally the BL has to be unlocked to flash firmware on a Moto.
Click to expand...
Click to collapse
Oh okay. I tried relocking the bootloader on Moto one p30 play but when repeatedly entering 'fastboot oem lock' it says "still require signed boot.img" and even after I flash the boot.img when it asks to whenever I enter the fastboot oem lock command it says "still require signed boot.img"

Can you help me out please?