[Solved]Bootloader unlocking problems: FAILED (remote: Command did not succeed)

flaxx187

Senior Member
Jun 23, 2013
134
4
0
hey my flashtool doesn't work he is freezing
and my imei number doesn't show in the flashtool



adb && oem is activ.

when i use the volume down taste i found nothing (under fastboot devices)
when i use the volume up taste i found my device (under fastboot devices) but it can't work because i get the error:
idk is my bootloader open ? in the config isn't the line "booatloader allowed" there stay only "root status: unknown"
target reported max download size
sending 'recovery' (15472 KB)...
OKAY [ 0.416s]
writing 'recovery'...
FAILED (remote: Command not allow
finished. total time: 0.439s

 
Last edited:

class459

Member
Oct 15, 2012
14
0
0
After many time trial and error finally succeed to unlock bootloader of my XZ..
The problem before is the rooting status showing unknown, my solution unlocking the bootloader with flashtool and I remove the "0x" inside the ulcode.txt
 

User z1c

New member
Apr 13, 2018
1
0
0
Rooting status unknown

1.: Go to the folder where Flashtool was installed
2.: Open the folder named "custom"
3.: Open the folder named "mydevices" (if it exists, in my case Flashtool version 0.9.18.4)
4.: Right button, New, Folder. Name the folder with your device code.
5.: Open the folder created previously
6.: Right button, New, Text Document. Name the text document as ulcode
7.: Open the text document created previously
8.: Paste your unlock code and save
9.: Open Flashtools and try the BLU option again.

obs 1: the step #3 I think it depends on your Flashtool version, because it wasn't mentioned at the solution

obs 2: at the step #4 is mentioned your device code. your device code is showed in the log when you click the button BLU, at the "Current device", after your device model.
Search a line like:
09/045/2015 23:45:08 - INFO - Current device : C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17
in this case, the device code is AB100C2DE3 and this should be the new folder name (step 4)

I follow your instructions successfully, but why even so "rooting status unknown" not "bootloader unlocked: yes" ..
please help me
 

moooztar

Member
Jul 21, 2016
22
3
0
Ugh! My bad - I have been sitting here for an hour (tired go figure), and FORGOT to enable not only USB debugging but also "Enable OEM unlock". ROOOOKIE mistake, but I guess someone in my state might appriciate to check that before they do this the hard way! I got the error messages mentioned here in Windows cmd of course... So check it! (I know this is not for all but tired nerds do make mistakes ;)

Worked as a charm in CMD (as Admin) on Windows 10 AFTER I fixed the driver for Android (See posts above).

Command was: fastboot -i 0x0fce oem unlock 0x<CAP-UNLOCK-CODE-FROM-SONY-AFTER-HANDING-THEM-YOUR-IMEI>

Time to sleep! haha.