Database Develop

FAILED (remote: Command not allowed)

Hello friends
if i want to flash recovery or relock the device it tells me "FAILED (remote: Command not allowed)".
Till the nougat update it wasn't a problem, it worked like described in every guide.
I think my drivers are ok, no errors in device manager and on Marshmallow everything worked fine.
The big problem is my home banking app detects the unlocked bootloader and stops working
so i need to either lock my device or root it.
Here are some data may they will help
At fastboot
Phone Unlocked
FRP Lock
About phone
Device Name: Honor 5C
Model number: NEM-L51
Build number: NEM-L51C432B350
EMUI version: 5.0
Android version: 7.0
Developer options
OEM unlocking is in off position and greyed out
USB debugging is on
I use "ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05" on Windows 10
hope you can help
greetings
Max

1 - Go to settings
2 - developer options (Need to enable)
3 - "OEM unlock" is enable
Done .

MHN.1515 said:
1 - Go to settings
2 - developer options (Need to enable)
3 - "OEM unlock" is enable
Done .
Click to expand...
Click to collapse
Hi MHN.1515
Thx for your reply but unfortunately OEM unlocking is greyed out and in off position.
greetings
Max

Maximilian Hauser said:
Hi MHN.1515
Thx for your reply but unfortunately OEM unlocking is greyed out and in off position.
greetings
Max
Click to expand...
Click to collapse
To return to the previous Android (6)

To return to the previous Android (6)
Click to expand...
Click to collapse
Hi MHN.1515,
and thanks for your participation.
this is exactly what i did.
I went back to the stock image "Honor 5C stock ROM images (latest: B102) NEM-L51" from PaulOBrien on MoDaCo. (Thank you for providing the image at this place)
Then i flashed NEM-L51C432B130 from here. (Thanks to Druger too) In this process the bootloader got locked again.
From there i updated to Nougat again, the good things are my phone is locked so i can use my homebanking app
and in developer options i can turn the Unlocking bootloader switch to on or off as is want to root it again one day.
So i hope i described the process well so it can help people with the same problem.
Greetings
Max
Btw. next time i need a better backup strategy, or at least a backup strategy

Maximilian Hauser said:
Hi MHN.1515,
and thanks for your participation.
this is exactly what i did.
I went back to the stock image "Honor 5C stock ROM images (latest: B102) NEM-L51" from PaulOBrien on MoDaCo. (Thank you for providing the image at this place)
Then i flashed NEM-L51C432B130 from here. (Thanks to Druger too) In this process the bootloader got locked again.
From there i updated to Nougat again, the good things are my phone is locked so i can use my homebanking app
and in developer options i can turn the Unlocking bootloader switch to on or off as is want to root it again one day.
So i hope i described the process well so it can help people with the same problem.
Greetings
Max
Btw. next time i need a better backup strategy, or at least a backup strategy
Click to expand...
Click to collapse
As far as I know this is the only way
You try to build in other (For example : NEM-L51C432B120) :
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1165/g104/v61511/f1/full/update.zip
I build my phone is different
So I can not be sure this file , But you try
(Please Thanks for button press )

[Solved] Any way to unlock FRP after OTA update? (P10 Lite)

Hello!
I recently rooted my new P10 Lite before version B124 was released, but then I decided to update my phone from B102 to B124 by flashing the recovery image from the Update file and then updating via OTA with the full update files.. The phone updated successfully but yesterday I used adb to boot into the bootloader in order to flash TWRP but noticed that FRP is now locked and i cannot flash TWRP without getting command not allowed error.
I also tried unlocking the bootloader (just in case it was locked for some reason) using the password i got from huawei but even that gives me an error. The enable OEM option in developer settings is greyed out since after the update and is till greyed out even after clearing cache and factory resetting the device. Now is there a way for me to unlock FRP again in order to flash TWRP? Or maybe another way to flash TWRP. Hopefully someone knows a way.

Use DC Unlocker.
I used it to unlock my bootloader on P9. Works perfectly.
They do FRP unlock and supports P10 Lite.
Costs 15 credits so 15 Euro.

dadvs1 said:
Use DC Unlocker.
I used it to unlock my bootloader on P9. Works perfectly.
They do FRP unlock and supports P10 Lite.
Costs 15 credits so 15 Euro.
Click to expand...
Click to collapse
Will do, thanks for the help!

Check that video bro...
https://youtu.be/h_uQqAHKJBg

Jonny93 said:
Will do, thanks for the help!
Click to expand...
Click to collapse
Wasted 15 credits on that and it didnt help me flash twrp like i thought it would
osa993ma said:
Check that video bro...
https://youtu.be/h_uQqAHKJBg
Click to expand...
Click to collapse
Thanks bro. Wish i saw it before spending 15 credits in DC unlocker. Even after removing frp i am still not able to tick enable OEM unlock in developer settimgs or flash twrp in fastboot. Only thing on my mind right now is to lock bootloader and see if enable oem unlock option will be available after that.

Please heelp frp lock

I accedentally switched OEM UNLOCK and now after reboot there is an error
Custom Binary Blocked By Frp Lock
Can you please help STEP BY STEP HWO TO FIX IT ?? i dont wanna to brick not8

klisza1993 said:
I accedentally switched OEM UNLOCK and now after reboot there is an error
Custom Binary Blocked By Frp Lock
Can you please help STEP BY STEP HWO TO FIX IT ?? i dont wanna to brick not8
Click to expand...
Click to collapse
Flash stock firmware with latest Odin in download mode. That should get you back up and running. OEM toggle switch should re-appear within 7 days (unless the date change trick works for you). The OEM unlock thread has more background, and there is a sticky thread here for the date workaround.

I have flashed all again and its working. Weird for me is about thso OEM issue - ive never had one xd even after flash srock firmware i could switch oem unlock. Curious what's depends from

klisza1993 said:
I have flashed all again and its working. Weird for me is about thso OEM issue - ive never had one xd even after flash srock firmware i could switch oem unlock. Curious what's depends from
Click to expand...
Click to collapse
Usually that error happens when you are not on stock (rooted with twrp, etc.) and hit the OEM toggle...it sees you have modified your phone in an unauthorized way and puts you in 'jail'.

I toggled it by myself i didnt know that it should be always on...
OEM issue - what is the problem. I have heard that the problem os thatbon some phones therenis no such options .... curious why

klisza1993 said:
I toggled it by myself [emoji14] i didnt know that it should be always on...
OEM issue - what is the problem. I have heard that the problem os thatbon some phones therenis no such options .... curious why
Click to expand...
Click to collapse
Snapdragon bootloaders are locked so OEM unlock toggle isn't really relevant there. For Exynos there is a long thread here with lots of info. Essentially it can take 7 days to appear if you don't see it at first boot or if you end up in jail.

Skip Update?

I just got a new Mi A2 and, thanks to Amazon, it came on a very old version of Android.
I have done Original version -> November OTA -> March OTA (Pie) and now trying to do April. However, the phone boot loops every time it tries to install it. If I leave it for 20 minutes or so unpowered it will finally restart and report 'Couldn't Update'
I have enabled OEM unlock, but not done the actual unlock in fastboot - could this be the cause? Is there a way to manually skip April too and go straight to June?
Thanks for any help.

Did have the same problem after unlocking bootloader it finished the update , was strange as hell so I stay unlocked for any case.

anryl said:
Did have the same problem after unlocking bootloader it finished the update , was strange as hell so I stay unlocked for any case.
Click to expand...
Click to collapse
So do a full unlock before trying again? At the moment I don't have the boot loader unlocked, I've just enabled the OEM unlock so I could unlock in case needed.

I never wait so long always do the 3button restart and see what's going on but here I did the full unlock and then it worked. On my wife's pink a2 all went fine no unlock needed so it's strange.

Sigh. I thought all this nonsense wouldn't be needed on an Android One phone.
Will give it a week or so and then go down the full unlock and re-set up route.

FFS found the solution on one of the other myriad boot loop threads - take the sim cards out before restarting.

Good for u mine was without sim.

It's still flaky. Have to power it on manually two or three times after restart - it doesn't boot loop, it just doesn't boot.

Question System has been destroyed & bootloader locked because of DSU Loader installing

Hi Guys
Need your assistance, its a complete mess here.
I found android 14 pre releases in developer options -> DSU Loader -> Installed GSM+ARM64. Thought it will install android 14 pre release (Saw in one of youtube video -
).
Post restart phone it went to system has been destoryed.
1. OEM unlock option was not checked (Bootloader locked)
2. Only booting in fastboot mode.
3. Flashing through EDL/ Flash Auth not working.
I can only think of unlocking bootloader may fix this issue but problem is bootloader is locked. Can't unlock it because oem unlock is not enabled under developer options.
Please help me bypass OEM unlock check so that I can unlock bootloader & probably flashing TWRP or Orange recovery will fix the problem
Thank you

This tutorial is for those who have the bootloader unlocked (see the video at 3 minutes 38, the padlock is open).
What did you want to do?
The phone is bricked, nothing to do with the locked bootloader, see a Xiaomi repair center.

Hi
I missed that it is for unlocked bootloader.
So if bootloader is locked, it should not update the partitions & if so it should roll back to original miui if it fails.
But instead it bricked my phone.
So if someone can help me unlock bootloader I can try flashing recovery & then rom.
Or suggest better option. service center people asked to replace motherboard.

hi!
If there is any way to fix it, unfortunately it is paid.

MJLH2V said:
hi!
If there is any way to fix it, unfortunately it is paid.
Click to expand...
Click to collapse
I am ok with paid service but not with the motherboard replacement

hi, is there way to flash this bricked phone please?

ketananxi said:
I am ok with paid service but not with the motherboard replacement
Click to expand...
Click to collapse
I can flash your phone.

ketananxi said:
Hi Guys
Need your assistance, its a complete mess here.
I found android 14 pre releases in developer options -> DSU Loader -> Installed GSM+ARM64. Thought it will install android 14 pre release (Saw in one of youtube video -
).
Post restart phone it went to system has been destoryed.
1. OEM unlock option was not checked (Bootloader locked)
2. Only booting in fastboot mode.
3. Flashing through EDL/ Flash Auth not working.
I can only think of unlocking bootloader may fix this issue but problem is bootloader is locked. Can't unlock it because oem unlock is not enabled under developer options.
Please help me bypass OEM unlock check so that I can unlock bootloader & probably flashing TWRP or Orange recovery will fix the problem
Thank you
Click to expand...
Click to collapse
It is imperative to unlock the bootloader with a xiaomi account where unlocking is authorized and associated with your smartphone. Without it, not worth it...
So unlock the bootloader and apply one of those countless FAQs that you'll find on XDA or youtube.
For me, settled in an hour.
Good luck,
Translated by Google...

BlitZ! said:
It is imperative to unlock the bootloader with a xiaomi account where unlocking is authorized and associated with your smartphone. Without it, not worth it...
So unlock the bootloader and apply one of those countless FAQs that you'll find on XDA or youtube.
For me, settled in an hour.
.
Click to expand...
Click to collapse
What is the use of this post since the user has the bootloader locked?