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

[xavk]

I just had a similar issue and solved it by careful use of CAPS.

The code provided by Sony is case sensitive (as already stated) and mine was all in capitals. The error I made was using 0XKEYINCAPS. Once I switched to 0xKEYINCAPS it worked first time....

 

[flakac]

Hi Guys,

So i bought a second hand XZ(C6603) as an upgrade from my XS. The previous owner told me he had unlocked the bootloader and then again relocked it(he used the BLU function in flashtool). Yesterday i wanted to unlock it again but somehow i cant get it unlocked anymore. In the service menu it says: "Bootloader unlock allowed" YES meaning i can unlock it.

I've used flashtool and adb both with the same result:

14/055/2013 22:55:31 - INFO - Device connected in fastboot mode
14/055/2013 22:55:36 - INFO - Unlocking phone using key XXXXXXXXXXXXXXXXXX
14/055/2013 22:55:36 - INFO - ...
14/055/2013 22:55:36 - INFO - FAILED (remote: Command did not succeed)
14/055/2013 22:55:36 - INFO - finished. total time: 0.035s

XXXXXXXXXXXXXXXXXX= the unlock code i got from Sony

I've all ready tried whiping & reflashing it with the flashtool(.423 frimware) and also repaired it with PC companion but after that i still get the same results

Anyone got some advise for me? Could it be a driver related isue(btw i'm on win 7 64)?

I had same problem with Xperia Z1,but from any reason I tried official way to unlock bootloader again and SONY sent me new email with new code.

 

[kamy0074]

guys i have still error FAILED (remote: Command did not succeed) and with make folder with name bx903**** then make a txt folder with name ulcode and type the cod of sony mail .. and then unlock agine bye flashtolls dont work why?

 

[kamy0074]

guys i have still error FAILED (remote: Command did not succeed) and with make folder with name bx903**** then make a txt folder with name ulcode and type the cod of sony mail .. and then unlock agine bye flashtolls dont work why?

no one here help me??

no one know???


if u dont know!!! how to root this peace of ****?

 

[kingvortex]

Try unlocking with fastboot.
How to unlock the bootloader.

Also, it's generally considered bad manners to call people names when asking for help, so I went ahead and reported your post (Edit - I see a mod agreed and deleted it). Please don't do it in future.

Sent from my C6603 using Tapatalk

 

[asdera58]

I had same problem with Xperia Z1,but from any reason I tried official way to unlock bootloader again and SONY sent me new email with new code.

Z1 Compact same error damn how to unlocked.
Onemore time rooting and locked
tray UL error damn sony

 

[timchew]

Yeah i know that is/was not the problem



Pff, finaly got i unlocked! Found a German forum where someone had the same problem:
http://www.android-hilfe.de/root-custom-roms-modding-fuer-sony-xperia-z/380742-xperia-z-root-bootloader-unlock-anleitung-23.html

Had to create a folder in flashtool/custom with my XZ serial code as name. In the folder i created a text file named ulcode.txt in text file i've put the unlock code i got from Sony after that it unlocked!

Thanks guys for the advice! For now i'm going to flash the sh*t out of my XZ

Thanks, Bro! This finally works!

 

[woutervanvliet]

Had the same problem, very simple solution

I landed here after having been unable to re-unlock the bootloader on my Xperia Z using fastboot in linux. Turned out, the solution was to change the code supplied on Sony's unlock bootloader site a little bit.

It told me to use:

fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXX

One of the commenters here adviced to enter the unlock code in uppercase, which it already was. But then, with a near desperate state of mind, I changed that other hexcode to uppercase.

fastboot -i 0x0FCE oem unlock 0xXXXXXXXXXXXXX

And then finally I got the OKAY.

EDIT: Hmm, yes, - I did get an OKAY. And flashed boot.img which kinda bricked my phone. Still not sure why and all, but I guess this is to say: when unlocking doesn't gives any kind of problems, don't get impatient and proceed extra carefully!

 

[Stronger1101]

Yeah i know that is/was not the problem



Pff, finaly got i unlocked! Found a German forum where someone had the same problem:
http://www.android-hilfe.de/root-custom-roms-modding-fuer-sony-xperia-z/380742-xperia-z-root-bootloader-unlock-anleitung-23.html

Had to create a folder in flashtool/custom with my XZ serial code as name. In the folder i created a text file named ulcode.txt in text file i've put the unlock code i got from Sony after that it unlocked!

Thanks guys for the advice! For now i'm going to flash the sh*t out of my XZ

Yes, this is the way to solve the problem.

Thanks brother

 

[xerwudjohn]

Yes, this is the way to solve the problem.

Thanks brother

XZ serial code is the IMEI number?

 

[tTiIbBoOyY]

can you please help me how to create a text file

can you please help me how to create a text file,i have the same problem with my xperia m...............

 

[kingvortex]

can you please help me how to create a text file,i have the same problem with my xperia m...............

Use Notepad or any other text editor.

Sent from my C6603

 

[tTiIbBoOyY]

Use Notepad or any other text editor.

Sent from my C6603

please tell me how,im a beginner,can you make me a procedure please . . .

 

[lucaszell]

please tell me how,im a beginner,can you make me a procedure please . . .

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)

 

[lelong37]

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)

Thanks you guys, this worked...!!!!

 

[Freethefire]

Just a heads up!

In the newer Flashtool, you need to put the folder in "C:\Users\<username>\.flashTool\registeredDevices" in step 3.
That is, if you've picked the default for your flashtool home folder.

Thanks for the solution btw! Saved me a few days headache

 

[BluBoy87]

Weird bootloader issue, help

Do you have any branding on the phone from your carrier, are you sure rooting hasn't changed status to yes by accident.

Are your drivers correctly installed (load up flashtool and connect your phone in fastboot and it will say device connecter in fastboot)

Sent from my C6603 using xda premium

Hi

I had tried several times to unlock boot-loader of my Xperia Z C6603. Changed fastboot driver, IMEI remove one digit for unlocking key from Sony developer website. But when i unlock device in command prompt. it says :

C:\Users\Lenovo\Desktop\fastboot>fastboot.exe -i 0x0fce oem unlock 0xEA0E3A0975A9FE8F
...
OKAY [ 0.194s]
finished. total time: 0.194s

C:\Users\Lenovo\Desktop\fastboot>fastboot reboot
rebooting...

finished. total time: 0.001s

It reboots , then format it self, turned in, and when recheck boot-loader status, it shows

"Bootloader unlock allowed: Yes"


instead of bootloader unlocked.!!!

What to do? I would like to mention that i am currently on Firmware: 10.6.A.0.454

Please help

---------- Post added at 11:05 AM ---------- Previous post was at 11:02 AM ----------

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)

Doesn't work for me even in flashtool ver. 0.9.18.6

 

[cscomic]

I had the same problem too, but after I upgrade the "FASTBOOT Driver" and reboot windows, it resolved~

so I think upgrading the FASTBOOT Driver maybe the key~

Hi Guys,

So i bought a second hand XZ(C6603) as an upgrade from my XS. The previous owner told me he had unlocked the bootloader and then again relocked it(he used the BLU function in flashtool). Yesterday i wanted to unlock it again but somehow i cant get it unlocked anymore. In the service menu it says: "Bootloader unlock allowed" YES meaning i can unlock it.

I've used flashtool and adb both with the same result:

14/055/2013 22:55:31 - INFO - Device connected in fastboot mode
14/055/2013 22:55:36 - INFO - Unlocking phone using key XXXXXXXXXXXXXXXXXX
14/055/2013 22:55:36 - INFO - ...
14/055/2013 22:55:36 - INFO - FAILED (remote: Command did not succeed)
14/055/2013 22:55:36 - INFO - finished. total time: 0.035s

XXXXXXXXXXXXXXXXXX= the unlock code i got from Sony

I've all ready tried whiping & reflashing it with the flashtool(.423 frimware) and also repaired it with PC companion but after that i still get the same results

Anyone got some advise for me? Could it be a driver related isue(btw i'm on win 7 64)?

 

[tania247260]

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)

thanks a lot my friend. it worked

 

[andsol]

I had the same problem too, but after I upgrade the "FASTBOOT Driver" and reboot windows, it resolved~

so I think upgrading the FASTBOOT Driver maybe the key~

Which drivers you have used?