Database Users

Fail flash XT1575, firmware stock.

Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!

Lisandro4m41 said:
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Click to expand...
Click to collapse
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.

acejavelin said:
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
Click to expand...
Click to collapse
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot 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

Lisandro4m41 said:
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot 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
Click to expand...
Click to collapse
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.

acejavelin said:
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
Click to expand...
Click to collapse
Thanks! Right now I'm downloading the firmware of the Motorola official page. I hope it works. Thanks again!

I downloaded the firmware from the official website, but I can not install it, how I go about flashing?

Lisandro4m41 said:
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Click to expand...
Click to collapse
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?

Lisandro4m41 said:
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Click to expand...
Click to collapse
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.

acejavelin said:
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
Click to expand...
Click to collapse
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?

Lisandro4m41 said:
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Click to expand...
Click to collapse
Usually it means either the bootloader is still locked (which we know your's is unlocked) or the file is incorrect for your device. Sometimes it's a random error, try erasing the modemst1 and modemst2 first, then flash NON-HLOS.bin a time or two until it gives and OK and continue from there like normal.

I have not retested flash, but I solved my problem. The problem was that the phone was locked in Claro AR. No relation to the Bootloader error, but got what I wanted haha. Thanks for your time.
Greetings from Argentina.

Bricked phone trying to root, now unable to flash stock rom

So I successfully installed TWRP recovery.
I then tried to flash SuperSU, but that gave me a boot loop, so I wanted to try and flash the stock rom again.
I wiped my phone with TWRP.
I wasn't totally sure what the correct version of the ROM was to download. I can't check because the phone is already wiped. It's a UK Moto X Play "lux XT1562 16GB P2C" single sim slot. I had installed an OTA update yesterday. I downloaded XT1562_LUX_RETEU_6.0.1_MPD24.107-52.xml.zip, would that be the correct version? Is there any way to know for sure?
So when I tried to flash the stock rom I ran into problems.
I ran "fastboot flash partition gpt.bin" and I got "(bootloader) Preflash validation failed".
I saw someone say that this could be because you need to flash the correct version of the bootloader first, so I did "fastboot flash bootloader bootloader.img" which was successful, but even after restarting "fastboot flash partition gpt.bin" still failed.
I'm really confused as to what I'm doing wrong. Am I having problems because I'm trying to flash the wrong version of the bootloader, or a version older then that which I had on my phone before wiping? Is this the kind of error you'd get if you were trying to downgrade, or should that work fine?
Help greatly appreciated!
Edit: Should I possibly try flashing 5.1.1 X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip or is flashing an older version a bad idea?

Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen

tavares_one said:
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
Click to expand...
Click to collapse
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
It fails when I try and flash gpt.bin
Code:
❯ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.143s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.740s
and on the bootloader logs is says
Code:
cmd: getvar:partition-type:partition
cmd: getvar:max-download-size
cmd: download 00008000
cmd: flash:partition
version downgraded for primary_gpt

johtso said:
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
Click to expand...
Click to collapse
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Dio-Genes said:
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
Click to expand...
Click to collapse
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.

johtso said:
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
Click to expand...
Click to collapse
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot

fablebreton said:
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
...
Click to expand...
Click to collapse
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s

johtso said:
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
Click to expand...
Click to collapse
Your bootloader is unlocked ?

fablebreton said:
Your bootloader is unlocked ?
Click to expand...
Click to collapse
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"

johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.

johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
if impossible with stock and if Twrp ok why not flash a custom rom

minimale_ldz said:
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
Click to expand...
Click to collapse
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU

johtso said:
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
Click to expand...
Click to collapse
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says

minimale_ldz said:
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
Click to expand...
Click to collapse
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Edit: It worked! You're an absolute life saver! So confusing that those two ROM are named so similarly..

johtso said:
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Click to expand...
Click to collapse
No idea what it means, but both your getvar info and linked firmware are MPDS. Anyway - good luck.

Relock Bootloader in Nougat

Hi, Here is my issue: I have the xt1625 and i downloaded an OTA nougat software from india NPJ25.9 (7.0). It worked great, then i unlock my bootloader to install cm14. The problem began when i wanted to revert back to the official Nougat, i was able to come back but the .bat file that came with the Stock Rom didnt have the option to relock the bootloader so i tried downgrade to mm to lock it with the fastboot oem lock begin and fastboot oem lock, However it didnt work.
The mfastboot said bootloader pre verification failed and never locked, so i went back to nougat which i am running atm. the problem is i still am with unlocked bootloader and i see a change in the warning screen instead of n/a it says bad key.
another problem i see is during flashing some of them return (bootloader) image signed with key bad key
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.560s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.276s]
finished. total time: 0.842s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.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' (16484 KB)...
OKAY [ 0.556s]
writing 'recovery'...
(bootloader) Image signed with key bad key
And the lock never happens. it says at the end: flash a valid android image and rerun the comand.
Does anyone have a solution for this? can the bootloader be locked with nougar rom, if so, should i edit the .bat file? and how? i tried edditing the .bat file but dont know how. does the ''bad key'' message means something wrong?

Samerhk said:
Hi, Here is my issue: I have the xt1625 and i downloaded an OTA nougat software from india NPJ25.9 (7.0). It worked great, then i unlock my bootloader to install cm14. The problem began when i wanted to revert back to the official Nougat, i was able to come back but the .bat file that came with the Stock Rom didnt have the option to relock the bootloader so i tried downgrade to mm to lock it with the fastboot oem lock begin and fastboot oem lock, However it didnt work.
The mfastboot said bootloader pre verification failed and never locked, so i went back to nougat which i am running atm. the problem is i still am with unlocked bootloader and i see a change in the warning screen instead of n/a it says bad key.
Does anyone have a solution for this? can the bootloader be locked with nougar rom, if so, should i edit the .bat file? and how? i tried edditing the .bat file but dont know how. does the ''bad key'' message means something wrong?
Click to expand...
Click to collapse
I have successfully flashed latest nougat and locked my bootloader through oem lock command.

Iqbal Ansari said:
I have successfully flashed latest nougat and locked my bootloader through oem lock command.
Click to expand...
Click to collapse
my problem is the guy who posted the nougat rom did it with a .bat file but didnt include the lock comands, and i dont know how to add them. do you have the .bat file or bloc comands you can share?

Samerhk said:
my problem is the guy who posted the nougat rom did it with a .bat file but didnt include the lock comands, and i dont know how to add them. do you have the .bat file or bloc comands you can share?
Click to expand...
Click to collapse
The command to flash a factory image is everywhere. Just search.
These are the commands i used,
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
fastboot reboot

Iqbal Ansari said:
The command to flash a factory image is everywhere. Just search.
Click to expand...
Click to collapse
i have searched and tried every command. I noted after command fastboot oem unlock begin it gives and error saying still need signed boot.img and there is the problema with the bad key thing. i really am out of ideas here.

Samerhk said:
i have searched and tried every command. I noted after command fastboot oem unlock begin it gives and error saying still need signed boot.img and there is the problema with the bad key thing. i really am out of ideas here.
Click to expand...
Click to collapse
I used the firmware which is available on russian lenovo forum.
The error has something to do with your firmware.

Iqbal Ansari said:
I used the firmware which is available on russian lenovo forum.
The error has something to do with your firmware.
Click to expand...
Click to collapse
thanks. i will try a different nougat rom

Samerhk said:
thanks. i will try a different nougat rom
Click to expand...
Click to collapse
Can you tell if you managed to solve? i have the same problems when i tried to lock bootloader and haven't find any solution..

mksail said:
Can you tell if you managed to solve? i have the same problems when i tried to lock bootloader and haven't find any solution..
Click to expand...
Click to collapse
I did not. The nougat firmware I installed had a bad signature key and I could not relock because of it and downgrading did not help because boot loader cannot be downgraded. I have to wait for a newer nougat firmware with not bad key Signed to lock. I have npj25.99-11 so I have to wait for newer version.
Enviado desde mi Moto G (4) mediante Tapatalk

Samerhk said:
I did not. The nougat firmware I installed had a bad signature key and I could not relock because of it and downgrading did not help because boot loader cannot be downgraded. I have to wait for a newer nougat firmware with not bad key Signed to lock. I have npj25.99-11 so I have to wait for newer version.
Enviado desde mi Moto G (4) mediante Tapatalk
Click to expand...
Click to collapse
Hopefully not too long a wait - is 99-11 the latest build from Moto? Haven't seen any firmware updates captured yet.

Same here...
I flashed a Nugat rom last night and ran into the same issues. I'll be eager to flash again once a new rom is available.
Samerhk said:
...i still am with unlocked bootloader and i see a change in the warning screen instead of n/a it says bad key.
another problem i see is during flashing some of them return (bootloader) image signed with key bad key
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.560s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.276s]
finished. total time: 0.842s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.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' (16484 KB)...
OKAY [ 0.556s]
writing 'recovery'...
(bootloader) Image signed with key bad key
Click to expand...
Click to collapse

Same, but when I run the commands to lock the bootloader, the phone stays at "bad key" forever ( no warning message only a black screen with "bad key" on it) and i have to flash the rom without the lock commands for the phone to boot. And I'm also getting those errors.
Mine is XT1641

Old thread, but same problem here. I can't get the phone to boot no matter what now. I tried out this link: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Everything is normal up to running the `fastboot flash boot boot.img` and then it complains `(bootloader) Image signed with key bad key`. The phone refuses to boot no matter what now. Any advice on how to fix it?

Please help - official OTA Nougat update has left phone in boot loop

Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you

adavies said:
Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you
Click to expand...
Click to collapse
First of all, "adb devices" doesn't work on the bootloader. The adb app only works in recovery or while booted into the system. Secondly, is your bootloader unlocked? How you proceed depends on that. If you still want to install Nougat there are a couple of options. Let me know your current bootloader status. Above all, don't panic and do something rash.
Here is a link to your phone's stock firmware" https://www.filefactory.com/file/5c...24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip

Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.

Also thank you for the link to the firmware, I just checked and this is the same file that I already downloaded so I do at least have peace of mind that I selected the right one.

Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.

_wyrm said:
Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.
Click to expand...
Click to collapse
Hi, thanks for your reply, sadly I have tried all the options from the bootloader with no success, they do the following:
START - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
RESTART BOOTLOADER - Just takes me back to the same bootloader screen immediately
RECOVERY MODE - Takes me back to android man fallen over with 'No command' underneath
POWER OFF - turns it off (obviously lol)
FACTORY MODE - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BARCODES - displays white screen with four barcodes relating to IMEI, SKU, DATE and SERIAL NUMBER
BP TOOLS - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
QCOM - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BOOTLOADER LOGS - Doesn't do anything when I click the power button on this option but shows some yellow text on the screen that says 'Fastboot reason: Volume down key pressed'
That is all the options I have then, none seem to resolve the problem.
Thank you

Also, I'm not sure if this is relevant but when I ran the flashstock.bat file to try and install the files from XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml, I noticed as the text scrolled up the CMD window that there was several mentions of:
slot count not found
slot suffixes not found
has-slot system not found
invalid signed image
These lines appear several times, I'm not sure if this is part of the problem or not. If the CMD window didn't automatically close I would have copied and pasted exactly what it says.
Thanks again

Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.

adavies said:
Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.
Click to expand...
Click to collapse
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
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 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 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 oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612

_wyrm said:
Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.
Click to expand...
Click to collapse
Hi, thank you for your reply, I just downloaded and tried the RSD Lite software. It detected my phone on Port number 1 as 'Fastboot athene_13mp S' and I selected the 'flashfile.xml' and pressed start. Unfortunately it stopped with the status 'Failed flashing process. 3/27 flash partition "gpt.bin" -> Phone returned FAIL.' Does anyone know how to get round this?
Thank you

pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
]
Click to expand...
Click to collapse
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.

adavies said:
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.
Click to expand...
Click to collapse
Did you manually flash the fastboot images in the sequence provided?
If that doesn't work, I would send it back to Motorola. If it isn't in warranty, well, rip.

pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
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 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 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 oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
I do still get the serial number when running 'fastboot devices', do you think unlocking the bootloader might be the answer? I went through te steps yesterday to get the code, was a little put off by voiding the warranty though. With regards to running the commands one at a time, I think I am now getting a bit confused on the correct procedure of where to run the commands from. I have tried running it from the folder for 'Minimal ADB and fastboot' (this folder contains all the files from the stock firmware folder as well which I copied and pasted in there) and also directly from the stock firmware folder itself. I will paste the results of each below (sorry to confuse the issue, my head is fried now, lol).
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\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.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.049s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I stopped after the second line as the text above suggests to me that part has failed so no point continuing. When running directly from the firmware folder I get the following :
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot devices
ZY223H6QF4 fastboot
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.062s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>
Again this seems to fail also but with some slightly different messages. Interesting that it failed on the gpt.bin part as this was also mentioned when it failed on RSD Lite.

If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.

_wyrm said:
If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.
Click to expand...
Click to collapse
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you

adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.

adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
AFAIK, this one isnt safe to skip.. Im out of ideas, sorry. Try another usb cable just in case.. but if it keeps failing at the same point you will probably need to send it to motorola service.

pastorbob62 said:
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.
Click to expand...
Click to collapse
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>

adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.

negusp said:
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.
Click to expand...
Click to collapse
You may be right. He has not successfully unlocked the phone so therefore his warranty should still be good.
---------- Post added at 04:18 PM ---------- Previous post was at 03:51 PM ----------
adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
I don't understand why you can't flash the stock ROM. Your baseband version is still on stock. That said if you want to continue trying give this a shot: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943 This will bring you up to Nougat the latest release. It does not require an unlocked bootloader and has been used on your model.
Or here: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
Otherwise I would go ahead and do a warranty return. Your warranty should still be okay since you did not go through with unlocking the bootloader.
Click to expand...
Click to collapse

need help relocking bootloader

sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks

millede74 said:
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
Click to expand...
Click to collapse
You can script them if you know how to make one. Otherwise enter them one at a time. You only need to flash this once so if you do them once each it doesn't take a long time.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
then
Code:
fastboot oem lock
you may have to repeat this last lock command until it works. I had to do it 4-5 times.

I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?

millede74 said:
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
Click to expand...
Click to collapse
fastboot needs to be in the folder with the 29.114-16-7-2 files.

Thanks

Note that you need to run the fastboot oem lock command a few times in the beginning (before you flash) and after you flash a few more times for this to completely work!

Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong

millede74 said:
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
Click to expand...
Click to collapse
Do them one at a time and post the results of each command here so we can see.

Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?

millede74 said:
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
Click to expand...
Click to collapse
It does the same thing as the commands above. The process is just automated.

This is what i get when running
ptn107 said:
It does the same thing as the commands above. The process is just automated.
Click to expand...
Click to collapse
C:\ProgramData\LMSA\Download\RomFiles>fastboot dev
ZY225FR3QL fastboot
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
mmand erases all user data.
(bootloader) Please re-run this command to continu
OKAY [ 0.014s]
Finished. Total time: 0.020s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
oid images now
(bootloader) Then re-run this command to lock
OKAY [ 0.018s]
Finished. Total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.008s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.010s]
Finished. Total time: 0.016s
C:\ProgramData\LMSA\Download\RomFiles>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.006s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.011s
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash partition gpt.bin
fastboot: error: cannot load 'gpt.bin': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash bootloader bootloader.img
fastboot: error: cannot load 'bootloader.img': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash modem NON-HLOS.bin
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash fsg fsg.mbn
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>

Correct me if I'm wrong but doesn't lmsa download the firmware as a zip file in C:\ProgramData\LMSA\Download\RomFiles ? If that's the case you need to make sure the files are extracted before running commands.