Database Users

P8 lite ALE-l21 FASTBOOT&RESCUE MODE

Hi,
My phone only enter fastboot&rescue mode.
Try to flash b052 firmware via fastboot but:
Se va a flashear la ROM B052 completa,
Si no desea hacerlo cierra esta ventana.
target max-download-size: 450MB
sending 'boot' (21706 KB)...
OKAY [ 0.652s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.659s
target max-download-size: 450MB
sending 'recovery' (34280 KB)...
OKAY [ 1.028s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.034s
target max-download-size: 450MB
sending 'cust' (218981 KB)...
OKAY [ 6.632s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.636s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 17.205s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 17.218s
ROM B052 flasheada, si todo ha ido bien
debe reiniciarse el telÚfono.
Si sale el recovery hacer un hard reset y
reiniciar el telefono.
Actualizar a travÚs del men˙ del telÚfono.
rebooting...
finished. total time: 0.032s
What now?

boneksl said:
Hi,
My phone only enter fastboot&rescue mode.
Try to flash b052 firmware via fastboot but:
Se va a flashear la ROM B052 completa,
Si no desea hacerlo cierra esta ventana.
target max-download-size: 450MB
sending 'boot' (21706 KB)...
OKAY [ 0.652s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.659s
target max-download-size: 450MB
sending 'recovery' (34280 KB)...
OKAY [ 1.028s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.034s
target max-download-size: 450MB
sending 'cust' (218981 KB)...
OKAY [ 6.632s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.636s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 17.205s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 17.218s
ROM B052 flasheada, si todo ha ido bien
debe reiniciarse el telÚfono.
Si sale el recovery hacer un hard reset y
reiniciar el telefono.
Actualizar a travÚs del men˙ del telÚfono.
rebooting...
finished. total time: 0.032s
What now?
Click to expand...
Click to collapse
is your bootloader unlock?

Nope, i send imei,sn and id to huawei and they answer me:
Dear User,
Huawei Customer Service is pleased to be at your service, sorry for bringing you the trouble, if you want to unlock your phone, you should meet the condition as follows:
1.Please register your Huawei ID in our official website http://huawei.com/en/ on your PC.
2.Log in your Huawei ID on your phone for 14 consecutive days.
3.Each Huawei ID should not apply for the unlock code more than twice within half years.
If you meet the conditions, please go to http://emui.huawei.com/en/ and click the 'download' button, then click 'unlock bootloader' button to login your Huawei ID other than any other third party ID to apply for the unlock code. Please contact us by mail or local service hotline as follows if error message appears.
TEL: http://consumer.huawei.com/en/contact-us/index.htm?tag=hotline
Mail: http://consumer.huawei.com/en/contact-us/index.htm?tag=email
Please submit your mobile model, S/N, IMEI/MEID and error message in your e-mail. We also need to know that your phone is rooted, it can be out of the best working state and part of functions may not be able to work normally. In addition, the system is vulnerable to be invaded by viruses once your phone is permitted to unlock. What's more, for the lacking of fully tested, the third party software will not be compatible with your phone. Unlocking will bring unexpected negative impacts and the device will be not normal, and can not be restored, Huawei after-sales service office will not provide warranty service for your rooted phone, and you may bear the cost. So we strongly advise you to think it twice.
If you have any other problem, please send your feedback to us. We will be at your service to help you solve your problems.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team (3207)

boneksl said:
Nope, i send imei,sn and id to huawei and they answer me:
Dear User,
Huawei Customer Service is pleased to be at your service, sorry for bringing you the trouble, if you want to unlock your phone, you should meet the condition as follows:
1.Please register your Huawei ID in our official website http://huawei.com/en/ on your PC.
2.Log in your Huawei ID on your phone for 14 consecutive days.
3.Each Huawei ID should not apply for the unlock code more than twice within half years.
If you meet the conditions, please go to http://emui.huawei.com/en/ and click the 'download' button, then click 'unlock bootloader' button to login your Huawei ID other than any other third party ID to apply for the unlock code. Please contact us by mail or local service hotline as follows if error message appears.
TEL: http://consumer.huawei.com/en/contact-us/index.htm?tag=hotline
Mail: http://consumer.huawei.com/en/contact-us/index.htm?tag=email
Please submit your mobile model, S/N, IMEI/MEID and error message in your e-mail. We also need to know that your phone is rooted, it can be out of the best working state and part of functions may not be able to work normally. In addition, the system is vulnerable to be invaded by viruses once your phone is permitted to unlock. What's more, for the lacking of fully tested, the third party software will not be compatible with your phone. Unlocking will bring unexpected negative impacts and the device will be not normal, and can not be restored, Huawei after-sales service office will not provide warranty service for your rooted phone, and you may bear the cost. So we strongly advise you to think it twice.
If you have any other problem, please send your feedback to us. We will be at your service to help you solve your problems.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team (3207)
Click to expand...
Click to collapse
in order to flash files via fastboot commands you need to have bootloader unlock,here is a tutorial on how to unlock https://www.youtube.com/watch?v=63L7FBuWFrc

Recovering 2G/3G after Set Radio band to USA

I recovered 2G/3G/4G network for SIM1 in Moto G5, here are recovery instructions step-by-step for dummies
Original posts by bablu048: post#13 & post#15
Recovering 2G/3G/4G network after Set Radio Band Mode to United states in the hidden Testing menu (*#*#INFO#*#*)
Problem description: Lost 2G/3G/4G network connectivity on SIM1 = unable to make/receive calls via SIM1, just SMS working
How it happened: see attachment
Phone model: Lenovo Moto G5 3GB/16GB
Model type: XT1676 (EU, Asia, Australia - dual sim)
Software Build number: NPP25.137-72
My phone info (important):
oem_locked
Software status: official
Phase 1 - prepare to recovery 2G/3G/4G
1- install this "Minimal ADB and Fastboot" on your pc
2- unlock "Developer options"
2a- Settings->About->tap on "Build number" 7 times to enable it
2b- go back to Settings - you'll see Developer options
3- enable "USB debugging" in "Developer options"
4- connect to PC and run "Minimal ADB and Fastboot" that you installed
4a- accept the prompt on your device "Allow USB debugging? The computer's RSA key fingerpint is: ..."
5- now run those commands and you see SerialNO of your phone
Code:
adb devices
Code:
[FONT="Courier New"]C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
ZYxxxxxxxx device
C:\Program Files (x86)\Minimal ADB and Fastboot>[/FONT]
6- switch off phone, take out SIM/SIMs
Phase 2 - recovering 2G/3G/4G
7- press and hold buttons "Vol[down]+Power" to boot into bootloader
8- connect to PC and run "Minimal ADB and Fastboot" that you installed
9- now run those commands
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Code:
[FONT="Courier New"]C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.028s]
finished. total time: 0.028s
C:\Program Files (x86)\Minimal ADB and Fastboot>exit[/FONT]
10- on phone select "Power off" and switch off phone, insert SIM/SIMs
11- switch on phone
12- done, 2G/3G/4G is working again
13- Big Thanks to bablu048 !!!

Can confirm, worked on my G5. I didn't even realize my sim connection problems was because of setting the radio band accidentally. Thanks!
Although, that did stop those annoying pop-up messages everytime I switched my data off. Anyway I can disable them?

1rdc said:
Can confirm, worked on my G5. I didn't even realize my sim connection problems was because of setting the radio band accidentally. Thanks!
Although, that did stop those annoying pop-up messages everytime I switched my data off. Anyway I can disable them?
Click to expand...
Click to collapse
Is your bootloader unlocked? Or is it locked?....because some people on other forums said that by doing this method on an unlocked bootloader you may lose your IMEI and both the networks.... please do reply. Thanks in advance.

Harish Topgi said:
Is your bootloader unlocked? Or is it locked?....because some people on other forums said that by doing this method on an unlocked bootloader you may lose your IMEI and both the networks.... please do reply. Thanks in advance.
Click to expand...
Click to collapse
My phone is running on stock rom without any modifications (no branded version):
oem_locked
Software status: official

Thanks a lot
hello,
really sorry about my English, I'm French.
I have a G4 plus and of course I made the mistake of clicking the wrong button.
Your handling worked perfectly
thank you very much

I just tried this on G5 (XT1675) because I've had lots of problems with ProjectFi in Europe. But now it won't connect at all and the phone shows a blank IMEI.
Any ideas or suggestions on what to do?

I have tried this fix, but just get "waiting for devices " after attempting the reset modemst1 command? What am I doing wrong.
Moto g5s plus.

my imei is 0 already tried everything but I did not have any results help me please it's an xt1672

Worked for my Moto XT1575 using Linux (Fedora 27).
Thanks a lot.
If fastboot does not progress ( keeps showing < waiting for any device >) , try using sudo to avoid permission issue.
Example:
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot erase cache
Kofola said:
I recovered 2G/3G/4G network for SIM1 in Moto G5, here are recovery instructions step-by-step for dummies
Original posts by bablu048: post#13 & post#15
Recovering 2G/3G/4G network after Set Radio Band Mode to United states in the hidden Testing menu (*#*#INFO#*#*)
Problem description: Lost 2G/3G/4G network connectivity on SIM1 = unable to make/receive calls via SIM1, just SMS working
How it happened: see attachment
Phone model: Lenovo Moto G5 3GB/16GB
Model type: XT1676 (EU, Asia, Australia - dual sim)
Software Build number: NPP25.137-72
My phone info (important):
oem_locked
Software status: official
Phase 1 - prepare to recovery 2G/3G/4G
1- install this "Minimal ADB and Fastboot" on your pc
2- unlock "Developer options"
2a- Settings->About->tap on "Build number" 7 times to enable it
2b- go back to Settings - you'll see Developer options
3- enable "USB debugging" in "Developer options"
4- connect to PC and run "Minimal ADB and Fastboot" that you installed
4a- accept the prompt on your device "Allow USB debugging? The computer's RSA key fingerpint is: ..."
5- now run those commands and you see SerialNO of your phone
Code:
adb devices
Code:
[FONT="Courier New"]C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
ZYxxxxxxxx device
C:\Program Files (x86)\Minimal ADB and Fastboot>[/FONT]
6- switch off phone, take out SIM/SIMs
Phase 2 - recovering 2G/3G/4G
7- press and hold buttons "Vol[down]+Power" to boot into bootloader
8- connect to PC and run "Minimal ADB and Fastboot" that you installed
9- now run those commands
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Code:
[FONT="Courier New"]
$ fastboot erase modemst1
< waiting for any device >
^C
$ sudo fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.007s]
finished. total time: 0.007s
$ sudo fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.006s]
finished. total time: 0.006s
$ sudo fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.039s]
finished. total time: 0.039s
[/FONT]
10- on phone select "Power off" and switch off phone, insert SIM/SIMs
11- switch on phone
12- done, 2G/3G/4G is working again
13- Big Thanks to bablu048 !!!
Click to expand...
Click to collapse

I have just made this same mistake on my Moto G5 Plus but my phone is unlocked and I noticed Harish Topgi say that I could delete the IMEI if I try this. Can someone confirm if this is the case. I have a XT1685 dual SIM model and the second SIM position still works ok. Is it possible to just delete modemst1 to see if this fixes the problem

Great article and worked for me on Moto G5
Great article and worked for me on Moto G5 (again stupidly set to USA Radio). Couple of bits of extra info. I had to download Motorola device drivers to get past the ''waiting for devices" issue (search for fastboot cedric s driver), sudo is a unix/linux command not available on windows systems. And lastly on the final reboot it took 2 or 3 mins to connect back to the 4G system so don't give up too quickly

Hi, I'm on Lineage 15.1 (Oreo 8.1) obviously 64bit + twrp 64bit and I think I've encountered the same issue, although never set USA before. Realised that travelling across Europe as I didn't have 2g/3g. Anyone with a 64bit installation already tried this method to recover 2g/3g, before I attempt the same? Any way to backup anything in case I lose the IMEI? Thanks guys!

can u plz upload fastboot cedric s driver

Tengo un moto g5 cedric 2g de ram 32g de interna dual sims.
Mi moto g5 cedric 2 de RAM y 32 de interna dual sims solo me lee la simcard en la ranura 2 pero en la 1 no me la lee sin embargo tengo mis 2 imei. Como puedo solucionar esto Estoy con un ROM Resurrección Remix Android 7.1.2

It works for the g5s plus!
thank you sooo much!

Hi, everyone i try to set radio band on ufeel prime 7.1.1 stock rom with (QuickShortcutMaker.apk) try activities (Band Mode) in (Engineer Mode) and set it all then reboot device for me work one sim only sorry for bad English

thanks a lot, worked perfect on Moto G5S +,
I removed magisk root, did not activate oem-lock, forgot to remove SIM-card, everything went okay.
Of course then reinstalled magisk again.
I don't know if it is important, I did not flash the twrp just started the Twrp-recovery from "fastfoot boot twrp.img".

Hello, i have the same problem, my phone can't get the 2g/3g anymore... i am not able to solve the problem as you said...
I text: "adb devices" and then i see: "list of devices" but there are no device... i can't undestand why.... (i followed all the steps)
---------- Post added at 07:06 PM ---------- Previous post was at 06:43 PM ----------
Ok i have solved the problem... thank you very much!

Thank you....
IT WORKS ,,,,

Thank you so so so much !
Almost 4 years later, I broke my G4 Plus with the help of "4636" menu
Following your instructions made all back in line again, you're my savior !

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á

bootloader yellow alert

had the bootloader unlocked and ended up giving hardbrick after an update via OTA.
I managed to recover but had the alert that the bootloader was unlocked, so I wanted to block again, then by fasstboot, I made the command: fastboot flashing lock, and apois this alert began to appear.
I'm afraid to give a factory reset and give hardbrick.
image attached
https://drive.google.com/file/d/1V_UK0iGIhDO31dETqs9t83uZ_TOHHYIJ/view?usp=sharing

What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.

echo92 said:
What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.
Click to expand...
Click to collapse
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
I really wanted to reset the factory; but I'm afraid to brick it again

luis dambrowski said:
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
Click to expand...
Click to collapse
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.

echo92 said:
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.
Click to expand...
Click to collapse
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem

luis dambrowski said:
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem
Click to expand...
Click to collapse
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go... never mind, I had a look at my ADB folder and the same is for me
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)

echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Click to expand...
Click to collapse
a piece of the log
"
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.174s]
finished. total time: 0.175s
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.176s]
finished. total time: 0.178s
D:\Downloads\Nova pasta (2)\teste>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.007s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.146s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader 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' (3651 KB)...
OKAY [ 0.128s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.329s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.095s
D:\Downloads\Nova pasta (2)\teste>fastboot flash boot boot.img
(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 [ 1.176s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.194s
D:\Downloads\Nova pasta (2)\teste>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 [ 1.241s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.254s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.540s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.553s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem 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' (96490 KB)...
OKAY [ 3.140s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.149s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 16.071s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.079s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250846 KB)...
......
"

echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)
Click to expand...
Click to collapse
I will do now,
D:\Downloads\Nova pasta (2)\teste>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.067s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.209s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader 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' (3651 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.368s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.105s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.120s
D:\Downloads\Nova pasta (2)\teste>fastboot flash boot boot.img
(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.738s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.755s
D:\Downloads\Nova pasta (2)\teste>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.707s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.723s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.696s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.710s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem 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' (96490 KB)...
OKAY [ 4.547s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.555s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...

luis dambrowski said:
I will do now,
.
Click to expand...
Click to collapse
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?

echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.

echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
and if I do a blankflash again now and do the rom flash, would it work?

luis dambrowski said:
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.
Click to expand...
Click to collapse
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)

echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
When I did the GPT / bootloader flash (gpt and boot) process, there was apparently no change.
do you suggest doing the flash with that (bootloader.img and gpt.bin) now? to remove this alert?
in fact this alert does not bother me, but I intend to remove it for future upgrade via OTA.
finally I will try to redo the process with ADB v1.4.3.

echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA

luis dambrowski said:
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA
Click to expand...
Click to collapse
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.

echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
ainda esta no firmware de março de 2017!
Tive uma ideia de desbloquear o bootloader e instalar o TWRP e colocar uma custom rom. No entanto, o código de desbloqueio não pode ser encontrado no site da motorola, mas sim o desbloqueio do bootloader.
Pois bem, o probloma aqui é o bootloader !!
Estou sem ideias de como prosseguir.
Sera que quando sair de novo update, (talvez algum) de certo o processo?

echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
good news!!! solved problem.
What did I do:
I used the command: fastboot flashing unlock
then he asked to repeat the command and then unlocked the bootloader, with the alert that was yellow turned red.
There I did the rom flash of April 2018 and it went without errors.
rom update and no bootloader alert.
echo92 thank you very much for your attention. big hug!!!

How to root ZTE Blade A7P (Z6252CA)?

I have tried to unlock my bootloader using fastboot flashing unlock and fastboot flashing unlock_critical, however I get the error message:
Code:
(bootloader) Start unlock flow
FAILED (remote: '
Unlock operation is not allowed
')
fastboot: error: Command failed
I have turned on OEM unlocking in developer settings, and the output of fastboot flashing get_unlock_ability is:
Code:
(bootloader) unlock_ability = 16777216
OKAY [ 0.002s]
Finished. Total time: 0.002s
From that output, the bootloader unlock should work, however, it does not. Please help me.