Database Users

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

Re-locking bootloader but is unlocked at each reboot

Hi everyone,
I went back to stock recovery and stock ROM (5.9.020S) in order to use Android Pay.
But I am facing one last issue for locking the device. Each time I go into fast boot mode, I lock the device, I check with device-info, it confirms it is locked. However after reboot I check again it has reverted back as unlocked.
How can I lock the persistently?
It is as if there is a script somewhere at boot that automatically unlock the device bootloader.

- flash the aboot from stock ROM
- flash the xbl from stock ROM
- do not reboot to keep the bootloader still unlocked
- boot in TWRP (do not flash)
- wipe, factory reset, format, reboot system

In order to do what you suggest, I flashed TWRP recovery first. Then I followed all the steps. Then I tried to flash the stock recovery back and tried to lock. Unfortunately, it did not help, still the same issue.
In fastboot, I do "fastboot flashing lock" or "fastboot oem lock". Then I check the status with "fastboot oem device-info". Right after, I always get "Device unlocked: false" which is good and confirm the lock has worked at first.
But if I reboot the bootloader and try again, then the status is back to "Device unlocked: true" and the device is unlocked again. It keeps unlocking after reboot if I attempt to lock.
I need to have the device NOT unlocked in order to use Android Pay. So now, I am not sure what to do to be able to lock the device...

You don't need to flash TWRP in fact sometimes you don't need it (if there is no encryption but do it to be sure) right after flashing
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn

These were indeed the files I flashed previously for aboot and xbl.
I tried again to flash the files in fastboot mode, then lock the device with "fastboot oem lock". After reboot, it is unlocked again.

Did you extract those files from 20s or any official OTA zip? Flashing those files are guaranteed to lock the bootloader again. I've tried it many times already so not sure what else could be missing.
What is being displayed when you do right after the flashing and TWRP steps?
Like this?
fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.097s]
finished. total time: 0.098s
---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------
See this thread if it will help...
https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513

I got the files from 20S. It really does not work for me.
I do:
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
After this when I check, it is like this (before and after reboot):
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.110s]
finished. total time: 0.111s
Click to expand...
Click to collapse
Anyway, thanks for trying to help me!

Pixel fastboot secret commands and bootloader RIPping

Hey there folks, i was trying to find the white bootlogo of pixel in the bootloader img and exploring stuff meanwhile i came through some interesting fastboot secrets....
on a linux machine...
Code:
strings bootloader-marlin-8996-012001-1702151126.img | grep "flashing"
gives output:
Code:
cmd_flashing_get_unlock_bootloader_nonce
cmd_flashing_unlock_bootloader
cmd_flashing_lock_bootloader
%s: flashing kernel
%s: flashing ramdisk
%s: invalid flashing type
invalid flashing type
flashing unlock
flashing lock
flashing lock_critical
flashing unlock_critical
flashing get_unlock_ability
flashing get_unlock_bootloader_nonce
flashing unlock_bootloader
flashing lock_bootloader
Code:
strings bootloader-marlin-8996-012001-1702151126.img | grep "oem"
gives output:
Code:
cmd_oem_flag_batt_disable_safty_timer
cmd_oem_flag_htc_radio_debug_func
cmd_oem_flag_batt_for_pa_test
cmd_oem_flag_batt_disable_tbatt_protect
cmd_oem_flag_batt_keep_charge_on
cmd_oem_flag_uart
cmd_oem_flag_batt_test_pwr_supply
cmd_oem_dsir add=0x%x, value=0x%x
fastboot oem dsir 53
fastboot oem dsiw 51 FF
Usage: oem get_ks_token [frp|ftm|download] [reboot count]
Reset the stored oem panel in device info
cmd_oem_ramdump failed
oem unlock is not allowed
write_allow_oem_unlock failed
oem reboot-download
oem reboot-ftm
oem rebootRUU
oem listpartition
oem listram
oem dmesg
oem last_dmesg
oem update_emmc_partition
oem read_mmc
oem write_mmc
oem test_emmc
oem ufs_get_lun
oem ufs_set_lun
oem erase_phone_storage
oem unlock
oem lock
oem device-info
oem show-barcodes
oem ramdump
oem getcolorid
oem setcolorid
oem getcid
oem setcid
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel
oem readconfig
oem writeconfig
oem easydump
oem readunlock
oem dumpDataCode
oem dsiw
oem dsir
oem ddrtest
oem dump_ram_full
oem get_ks_token
oem get_anti_theft_status
oem sha1sum
oem readmeid
oem refurbish
oem batt_enable_bms_charger_log
oem batt_disable_tbatt_protect
oem batt_enable_fast_charge
oem batt_test_pwr_supply
oem batt_for_pa_test
oem batt_disable_safty_timer
oem batt_keep_charge_on
oem uart
oem htc_radio_debug_func
oem htcramdump
oem autordump2storage
cmd_oem_easydump
cmd_oem_flag_autordump2storage
cmd_oem_flag_batt_enable_bms_charger_log
cmd_oem_flag_batt_enable_fast_charge
cmd_oem_ramdump
cmd_oem_flag_htcramdump
oemerr_%x
androidboot.oem_unlock_support=
oemerr_99
Usage: oem ddrtest 0x<addr> 0x<size> <round> [<break>]
Default test: oem ddrtest 0 0 0
ABT_Propdata_oem
NOCError_Propdata_oem
BIMCError_Propdata_oem
use_oem_external_hdcp
oem_pshold_config
/tz/oem
oem=M
/secboot/oem_secapp
/secboot/oem_general
/tz/oem
macchiato_read_oem_pk_hash() failed {0x%x}
oem_pshold_config
ABT_Propdata_oem
NOCError_Propdata_oem
BIMCError_Propdata_oem
i dont want to fire up my device by giving random commands so if you are curious enough and have a spare device, i'd love to know further outputs...
for example the command:
fastboot flashing unlock_critical (will it forcefully unlock?? even verizon???)
please share output of this command if you are on unlocked bootloader (this can help me to find out splash image and other hidden partitions)
fastboot oem listpartition
so far i found two image like files (.rgb) inside bootloader...
dead_battery.rgb
dead_battery_charging.rgb
Thanks in advance if you are going to help me...

the get/setcolorid seems would be useful if someone wants to replace their backplate with an ebay one that has a different colour, my HTC One M9 also has this command.
unfortunately it require the bootloader to be unlocked even if I just wanna use the getcolorid command (which from what it says make no changes to the device)
PS D:\Desktop\platform-tools> .\fastboot.exe oem getcolorid
...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.097s

This is some good info. If you have anything else please do share with us Verizon Pixelerz because we do have a few members trying to figure out an exploit.. looks like this could help with reverse engineering the lock/unlock method for us. It's a start, right? Thank you very much OP. ?

I tried some of these commands too but many needed the boot loader to be unlocked.
This was on Pixel 2 XL

AndroidUser00110001 said:
I tried some of these commands too but many needed the boot loader to be unlocked.
This was on Pixel 2 XL
Click to expand...
Click to collapse
Too bad we can't get a script to execute these commands in some sequence to trigger a bug that let's us in... I just don't know..
Sent from my Pixel XL using Tapatalk

this is actually a pretty cool post...
my pixel is unlocked and so I haven't had much interest in poking around with the bootloader... unfortunately, I don't have an extra pixel, otherwise I would fir sure be investigating this. very curious. (but unwilling to sacrifice my phone. lol).

C:\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.190s]
finished. total time: 0.191s
C:\platform-tools>fastboot oem get_ks_token
...
(bootloader) INFO< Please cut following message >
(bootloader) INFO<<<< Identifier Token Start >>>>
(bootloader) INFO83BC9A76DAD508F92D65EA158E53B949
(bootloader) INFO3213EC77833C57857662EC575FCE27DE
(bootloader) INFOB6C64EEAEFE22ABEF859991CF5E5AFDC
(bootloader) INFO31B8E07AD21F9DDBDD3D91EC7E0988BF
(bootloader) INFO50F15CB886907DC162D0C5C2AB5E59B4
(bootloader) INFO8375E5CBB99EA10B59A1A1B83C3E7E5E
(bootloader) INFOD488BA89360F8974A8A35EDBC85A86FE
(bootloader) INFO75AD4F0F53D59445BB84BDB4BAAB2121
(bootloader) INFOCB045E978F029B644B5AD3D136207261
(bootloader) INFO0B93906FECFA423F8A4E6EBA9CB1CA80
(bootloader) INFO3F0FCDF5515506C0DA0343CC52367921
(bootloader) INFO2696BDA5F7D1812757A849C261AB05D4
(bootloader) INFO3CE67FFEC33948BB60BC2EEF5C8599E2
(bootloader) INFOC94C568D143811064ABFFA9734C4FEBB
(bootloader) INFO7F7D3233DC8235B225A5C0A918F0A56D
(bootloader) INFO072D7C6B52AC38761AA25F672150BAAB
(bootloader) INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.540s]
finished. total time: 0.541s

Fastboot flashing locked, Need help

Hi Guys, my moto g5+ is always rebbot to fastbbot and it says Fastboot flashing is locked and i'm unable to flash any files via fastboot, i tried many of the stock ROM flashing guides but as flashing is locked i'm getting access denied error. Screenshot is attached, PFA below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Anybody has any solutions.. please reply

This error i'm getting..
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader "C:\Pr
ogram Files (x86)\Minimal ADB and Fastboot\Boot Images\bootloader.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.117s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.761s]
finished. total time: 0.878s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem "C:\Program F
iles (x86)\Minimal ADB and Fastboot\Boot Images\oem.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (75638 KB)...
OKAY [ 1.649s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s

Is OEM unlock toggled in your settings screen? That is an option that must always be on if you intend on messing around with any device. If it is, try unlocking your bootloader again the official way. If OEM unlock was toggled on before it should work, then flash stock again.
If it doesn't work, have you been able to enter recovery mode?

bazinga137 said:
Is OEM unlock toggled in your settings screen? That is an option that must always be on if you intend on messing around with any device. If it is, try unlocking your bootloader again the official way. If OEM unlock was toggled on before it should work, then flash stock again.
If it doesn't work, have you been able to enter recovery mode?
Click to expand...
Click to collapse
Yes, oem unlock is toggled. and i tried the official way but i was unsuccessful. i unlocked oem before and it is unlocked. but the problem is "flashing_locked" in fastboot mode and i'm unable to flash anything via fastboot.. i already installed twrp before and using it..i can flash any ROMs via TWRP but not via FastBoot.. i wanted to give my mobile to my bro but before that i want it to be like how it was when i bought... if any solution plz help..

Vishweshwaraiah Kj said:
Yes, oem unlock is toggled. and i tried the official way but i was unsuccessful. i unlocked oem before and it is unlocked. but the problem is "flashing_locked" in fastboot mode and i'm unable to flash anything via fastboot.. i already installed twrp before and using it..i can flash any ROMs via TWRP but not via FastBoot.. i wanted to give my mobile to my bro but before that i want it to be like how it was when i bought... if any solution plz help..
Click to expand...
Click to collapse
Hi, I have the exact same problem "flashing_locked" in my Moto X4, did you solve this problem?
In my case I do not have TWRP anymore and I do not have to boot the system ...
I can not enable the USB debugging option...

You need to type "flashing unlock" in fastboot cmd

Thomas Hunter said:
You need to type "flashing unlock" in fastboot cmd
Click to expand...
Click to collapse
If i do it :
"Enable USB USB debbuguing <in development option>"
But there is no boot

IVANWB said:
If i do it :
"Enable USB USB debbuguing <in development option>"
But there is no boot
Click to expand...
Click to collapse
You have to enable USB debugging and OEM unlock before you flash anything.
As @bazinga137 wrote: It's a "must".
Sent from my Moto G5 Plus using XDA Labs

IVANWB said:
If i do it :
"Enable USB USB debbuguing <in development option>"
But there is no boot
Click to expand...
Click to collapse
I will make a short video tomorrow that will show you the steps you have to make

IVANWB said:
If i do it :
"Enable USB USB debbuguing <in development option>"
But there is no boot
Click to expand...
Click to collapse
Sorry for the late.
just to be clear but could you still get in the bootloader?

Thomas Hunter said:
Sorry for the late.
just to be clear but could you still get in the bootloader?
Click to expand...
Click to collapse
Sorry for the delay in replying.
I sent my device yesterday for the warranty.
They said it was necessary to change the plate and the guarantee will cover.
I could get into the bootloader, but I could not do any flash files, as I requested to enable USB debugging, but since there was no system and no boot, it was not possible to enable this option.
The Flashing unlock options did not work.
Thanks for the help.

IVANWB said:
Sorry for the delay in replying.
I sent my device yesterday for the warranty.
They said it was necessary to change the plate and the guarantee will cover.
I could get into the bootloader, but I could not do any flash files, as I requested to enable USB debugging, but since there was no system and no boot, it was not possible to enable this option.
The Flashing unlock options did not work.
Thanks for the help.
Click to expand...
Click to collapse
You can just type "flashing unlock" without enabling USB debugging.
And What did it say in the command prompt?

help solution
Thomas Hunter said:
You can just type "flashing unlock" without enabling USB debugging.
And What did it say in the command prompt?
Click to expand...
Click to collapse
that oem unlock from developer is enabled in the system, but this is impossible since the device does not start because it is damaged, any solution?

my fastboot too dumping anyother usb jacks but we have a way thrue firmware reflash
my fastboot too dumping anyother usb jacks but we have a way thrue firmware reflash:п

Thomas Hunter said:
You need to type "flashing unlock" in fastboot cmd
Click to expand...
Click to collapse
Thank you so much man ! Thank you for these 2 magical words. Now I can fix my phone & die in peace.

Vishweshwaraiah Kj said:
Hi Guys, my moto g5+ is always rebbot to fastbbot and it says Fastboot flashing is locked and i'm unable to flash any files via fastboot, i tried many of the stock ROM flashing guides but as flashing is locked i'm getting access denied error. Screenshot is attached, PFA below:
Click to expand...
Click to collapse
I'm having the same problem here in my Moto G8 Power.
.\fastboot.exe flashing unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.007s
.\fastboot.exe oem unlock JDSKDFVNADVXJVXCM
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.011s
Lenovo Rescue also fails:
When i try to star any stock rom:

Guys...I have the same problem on my motorola. Was anybody able to fix this ?

Constantinologia said:
.\fastboot.exe flashing unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.007s
.\fastboot.exe oem unlock JDSKDFVNADVXJVXCM
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.011s
Lenovo Rescue also fails:
View attachment 5250841
When i try to star any stock rom:
View attachment 5250847
Click to expand...
Click to collapse
Same problem here. Phone is asking to make change through OS but it can't boot into the OS. Anyway of bypassing this?

Pessoal que está tentando com o "BOOTLOADER BLOQUEADO" esquece só fazendo reparo via EMMC, tem que abrir o aparelho e regravar a ROM direto na memória CHIP, muitos técnicos falam que é problema de memória ou terá que fazer a substituição da placa mãe, agora se vc já tem o "BOOTLOADER DESBLOQUEADO" é só mandar o comando no adb Fastboot desbloquear o flash que já será necessário, o pessoal fica repetindo as respostas como se nós chegassemos até aqui e não tentamos nada, já tentamos de tudo mas infelizmente é isso! achei um rapaz que faz esse procedimento só que ele cobra 250,00 no Paraná

unlocking bootloader

i have a motorola moto c how do i unlock the bootloader the fastboot oeam get_unlock_data command says its unknown command

Presumably that's a typo in your quote?
You should quote exactly what happened so people can help.
There are two different errors, local or remote.
Code:
C:\>fastboot stupidcmd
fastboot: usage: unknown command stupidcmd
C:\>fastboot oem stupidcmd
(bootloader) 'stupidcmd' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
fastboot: error: Command failed
Have you tried fastboot oem help?
To answer your question, I believe that Motorola in general has stopped supporting fastboot unlocking on the less expensive models.

delete

Renate said:
Presumably that's a typo in your quote?
You should quote exactly what happened so people can help.
There are two different errors, local or remote.
Code:
C:\>fastboot stupidcmd
fastboot: usage: unknown command stupidcmd
C:\>fastboot oem stupidcmd
(bootloader) 'stupidcmd' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
fastboot: error: Command failed
Have you tried fastboot oem help?
To answer your question, I believe that Motorola in general has stopped supporting fastboot unlocking on the less expensive models.
Click to expand...
Click to collapse
i did try fastboot oem help but it didnt help and its not the typo and the error is remote