Unlock Bootloader: FAILED (remote: Command not allowed)

Ferramont103

Member
Nov 9, 2014
5
0
0
Pretoria
Hi :D

I followed the guide here: http://goo.gl/b7NTn9

My problem is, I keep getting the error FAILED (remote: Command not allowed) as soon as I press "unlock" after I pasted the unlock code.

Can anyone perhaps help , please? I'm at my wits end on this one.

Log Dump:
Code:
24/052/2016 13:52:13 - INFO  - Please connect your device into flashmode.
24/052/2016 13:52:21 - INFO  - Device connected in flash mode
24/052/2016 13:52:21 - INFO  - Opening device for R/W
24/052/2016 13:52:21 - INFO  - Reading device information
24/052/2016 13:52:21 - INFO  - Phone ready for flashmode operations.
24/052/2016 13:52:21 - INFO  - Opening TA partition 2
24/052/2016 13:52:21 - INFO  - Current device : E2303 - [COLOR="red"]DEVICE_CODE_HERE[/COLOR] - 1294-6067_R9A - 1291-5963_26.1.A.2.167 - GENERIC_26.1.A.2.167
24/052/2016 13:52:21 - INFO  - Closing TA partition
24/052/2016 13:52:21 - INFO  - Processing loader.sin
24/052/2016 13:52:21 - INFO  -     Checking header
24/052/2016 13:52:21 - INFO  -     Flashing data
24/052/2016 13:52:22 - INFO  - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_36 / Bootloader status : ROOTABLE
24/052/2016 13:52:22 - INFO  - Max packet size set to 512K
24/052/2016 13:52:22 - INFO  - Opening TA partition 2
24/052/2016 13:52:22 - INFO  - Start Reading unit 000008B2
24/052/2016 13:52:22 - INFO  - Reading TA finished.
24/052/2016 13:52:22 - INFO  - Closing TA partition
24/052/2016 13:52:22 - INFO  - Ending flash session
24/052/2016 13:52:22 - INFO  - Now unplug your device and restart it into fastbootmode
24/052/2016 13:52:22 - INFO  - Device connected in flash mode
24/052/2016 13:52:23 - INFO  - Device disconnected
24/054/2016 13:54:13 - INFO  - Device connected in fastboot mode
24/054/2016 13:54:32 - INFO  - Unlocking phone using key [COLOR="red"]UNLOCK_KEY_HERE[/COLOR]
24/054/2016 13:54:32 - INFO  - ...
24/054/2016 13:54:32 - INFO  - FAILED (remote: Command not allowed)
24/054/2016 13:54:32 - INFO  - finished. total time: 0.005s
Thank you for reading!
 
Last edited:

ardentis

Senior Member
Jan 4, 2015
564
167
0
Have you checked to see if unlock is allowed? And if it says it can be unlocked, did you put the right imei for unlock. I found that the unlock code for the Xperia M worked fine
 
  • Like
Reactions: Ferramont103

swizzyneck

New member
Feb 24, 2016
2
1
0
hy :)

exactly the same problem is occuring to me !
i tried to unlock the bootloader with different options for example the new and the old version of flashtool but it´s not working. :(
the rooting status is: Bootloader unlock allowed: Yes
i also noticed that when you put in your imei code on the sony developer page you have to put in 15 digits to get the ul-code but the flashtool just shows 14 digits of the imei code when you have to enter it.

i have the e2303 8Gb
build number 26.1.A.2.167
Android 5.0

Thank you !
 
Last edited:
  • Like
Reactions: Ferramont103

ardentis

Senior Member
Jan 4, 2015
564
167
0
Make sure you use the imei from the phone and not the unlock tool. It's purposely wrong to protect your imei if you share a picture of the unlock tool. Just keep trying
 

TomTOm_83

Senior Member
Dec 11, 2010
77
2
0
Vienna
Make sure you use the imei from the phone and not the unlock tool. It's purposely wrong to protect your imei if you share a picture of the unlock tool. Just keep trying
I have also the Problem, in the settings is Allowed, but the Software can't unlock the
the Bootloader well (remote: Command not allowed),

I have with Blu install't .1.128 but no way.

Do have tips for me?
i have read the Driver can under windows 8.1 a problem, but he find my Smartphone,
also must it work or?!

Greetz
 
Sep 11, 2013
6
9
0
Unlocking the bootloader in M4 Aqua

Was stuck with the same problem. M4, says its bootloader can be unlocked.

13/034/2016 22:34:37 - INFO - Unlocking phone using key XXXXXXXXXXXXXXX
13/034/2016 22:34:37 - INFO - ...
13/034/2016 22:34:37 - INFO - FAILED (remote: Command not allowed)
13/034/2016 22:34:37 - INFO - finished. total time: 0.005s

The solution is to enable OEM unlocking in the developer options. Also, in some cases, it helps to perform a factory reset before unlocking.
Good luck!
 
Last edited:
  • Like
Reactions: minhtri16796

ethoms

Member
Apr 9, 2011
20
5
0
Singapore
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
 
  • Like
Reactions: htcity and psyqho

htcity

New member
Jul 21, 2016
2
1
0
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
Thanks bro. It worked
 

mamun88

New member
Dec 4, 2014
1
0
0
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.

i have same problem, but my device bootlop so i can't allow OEM unlocking. someone help me please? tanks
 
Jun 24, 2015
13
3
0
This thread is dead, but I'll post anyways. I am using xperia xz1c. Bootloader unlock is allowed. OEM unlocking is allowed. Device is being detected on fastboot devices command. On fastboot, the output I am getting is "FAILED (remote: command did not succeed)". I have tried latest platform tools 28.0.1, older platform tools 25.0.5 and 26.0.0 with no success. Thanks for reading.