Hi
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!
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
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 !
ardentis said:
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
Click to expand...
Click to collapse
Thanks for replying! Yeah, I did all that, I tried the M and M2 unlock code, unlock is allowed, it just isn't doing anything though
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
ardentis said:
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
Click to expand...
Click to collapse
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
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!
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.
ethoms said:
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.
Click to expand...
Click to collapse
Thanks bro. It worked
Hi
Same problem, and thanks for oem unlocking in developers menu option.
The unlock option works fine now
ethoms said:
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.
Click to expand...
Click to collapse
i have same problem, but my device bootlop so i can't allow OEM unlocking. someone help me please? tanks
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.
Related
hey guys
recently i have got this jellybean rom
http://forum.xda-developers.com/showthread.php?t=2258058
i wanna to back again to ICS
what the kernel and rom should i flash it on flash tools
bec
no recovery and can't get it on jellybean
i wanna to back to ICS,unlock bootloader,root my phone then flash CM 10
and
yesterday i tried to unlock bootloader on jellybean
it was allowed in configuration
then i tried this method
http://www.androidauthority.com/xperia-s-unlock-bootloader-82532/
then it successfully unlocked
and the configuration
become
bootloader unlock : Yes
when i tried to root it with this method
http://forum.xda-developers.com/showthread.php?t=1886460
failed to root
and
become
bootloader unlock allow : no
nw what should i do ?
.
.
.
.
srry for my english
and flash tool INFO in bootloader unlock plugin
26/050/2013 07:50:04 - INFO - Current device : LT22i - CB511Z631Y - 1261-8592_R4H - 1254-4233_6.2.A.0.400 - WORLD_6.2.A.0.400
26/050/2013 07:50:04 - INFO - Processing loader
26/050/2013 07:50:04 - INFO - Checking header
26/050/2013 07:50:04 - INFO - Flashing data
26/050/2013 07:50:05 - INFO - Loader : S1_Root_3065 - Version : R5E003 / Bootloader status : ROOTED
26/050/2013 07:50:05 - INFO - Start Reading property
26/050/2013 07:50:05 - INFO - Reading TA finished.
26/050/2013 07:50:05 - INFO - Ending flash session
26/050/2013 07:50:05 - INFO - Now unplug your device and restart it into fastbootmode
26/050/2013 07:50:05 - INFO - Device connected in flash mode
26/050/2013 07:50:06 - INFO - Device disconnected
26/050/2013 07:50:16 - INFO - Your phone is already unlocked. Canceling task
26/050/2013 07:50:17 - INFO - Device connected in fastboot mode
umm solved all thing
thx any way
Hello,
i made Bull**** :crying: and didnt Backed up my TA. Then i unlocked the Bootloader, locked it again and now i cant unlock it any more.
when i type: "fastboot -i 0x0fce oem unlock 0xMYKEY"
It says "Command did not suceed"
Then when i try it again it says "Device already rooted"
Then i tried to make it over Flashtool, i go to "Flashtool/Custom/MyDevices" and made a Folder with my Device Serial, there i put "ulcode.txt" with my Unlock Key.
Then i used BLU over Flashtool.
But Flashtool says the same "Command did not Suceed".
I made a great Bull**** with dont backing up my TA. Sorry for that. Is it possible to unlock my bootloader again without TA or is it inpossible now ?
Thanks.
What does it say when you go into the service menu, does it still say the bootloader can be unlocked?
I think the code if I remember is *#*#7378423#*#*
Ned_Flanders said:
What does it say when you go into the service menu, does it still say the bootloader can be unlocked?
I think the code if I remember is *#*#7378423#*#*
Click to expand...
Click to collapse
Hi,
it says "Bootloader unlock is allowed".
Thanks
nibeal said:
Hi,
it says "Bootloader unlock is allowed".
Thanks
Click to expand...
Click to collapse
Does it say "Bootloader Unlocked: Yes" or Bootloader Unlock Allowed: Yes"? There is a difference between the two.
gamer649 said:
Does it say "Bootloader Unlocked: Yes" or Bootloader Unlock Allowed: Yes"? There is a difference between the two.
Click to expand...
Click to collapse
It says "Bootloader Unlock Allowed: Yes"
nibeal said:
It says "Bootloader Unlock Allowed: Yes"
Click to expand...
Click to collapse
Have you tried requesting a fresh key from Sony?
gamer649 said:
Have you tried requesting a fresh key from Sony?
Click to expand...
Click to collapse
Is there a way to get a different key ? I requested a Key and i became the same Key that i used for the first Unlock.
nibeal said:
Is there a way to get a different key ? I requested a Key and i became the same Key that i used for the first Unlock.
Click to expand...
Click to collapse
It should definitely be the same key then. Delete the document you made and go through the flashtool process as it asks you to. Then copy and paste your key in.
gamer649 said:
It should definitely be the same key then. Delete the document you made and go through the flashtool process as it asks you to. Then copy and paste your key in.
Click to expand...
Click to collapse
I tried it this way too. Without the ulcode.txt, only using BLU in Flashtool and then paste my key in the flashtool process when it asks.
There it is the same, it says "Command did not suceed".
Try to unlock the bootloader via the Sony site. You will get a key, i don´t know if it will be a new one or the same. But try it and reply with the results. Link: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
lgv2800 said:
Try to unlock the bootloader via the Sony site. You will get a key, i don´t know if it will be a new one or the same. But try it and reply with the results. Link: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Click to expand...
Click to collapse
I already tried it, its the same Key, but the Key dont works any more. Thats what i said in my first Post. here is what Flashtool says:
20/051/2015 18:51:15 - INFO - Flashtool Version 0.9.18.4 built on 12-05-2014 22:00:00
20/051/2015 18:51:15 - INFO - Executing search strategies to find proxy selector
20/051/2015 18:51:15 - INFO - No proxy found for IE. Trying next one
20/051/2015 18:51:15 - INFO - Strategy firefox failed trying next one : No Firefox installation found
20/051/2015 18:51:15 - INFO - No proxy found for java. Trying next one
20/051/2015 18:51:16 - INFO - Syncing devices from github
20/051/2015 18:51:16 - INFO - Scanning devices folder for changes.
20/051/2015 18:51:24 - INFO - Pulling changes from github.
20/051/2015 18:51:24 - INFO - Devices sync finished.
20/051/2015 18:51:29 - INFO - Device connected in fastboot mode
20/051/2015 18:51:33 - INFO - Please connect your device into flashmode.
20/051/2015 18:51:38 - INFO - Device disconnected
20/051/2015 18:51:44 - INFO - Device connected in flash mode
20/051/2015 18:51:44 - INFO - Opening device for R/W
20/051/2015 18:51:45 - INFO - Reading device information
20/051/2015 18:51:45 - INFO - Phone ready for flashmode operations.
20/051/2015 18:51:45 - INFO - Current device : D6503 - BH91Axxxxx - 1281-4640_R2B - 1278-4770_23.0.1.A.0.167 - GLOBAL-LTE_23.0.1.A.0.167
20/051/2015 18:51:45 - INFO - Processing loader.sin
20/051/2015 18:51:45 - INFO - Checking header
20/051/2015 18:51:45 - INFO - Flashing data
20/051/2015 18:51:45 - INFO - Processing of loader.sin finished.
20/051/2015 18:51:45 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_7 / Boot version : S1_Boot_MSM8974AB_LA3.0_55 / Bootloader status : ROOTABLE
20/051/2015 18:51:45 - INFO - Start Reading unit 000008B2
20/051/2015 18:51:45 - INFO - Reading TA finished.
20/051/2015 18:51:45 - INFO - Ending flash session
20/051/2015 18:51:45 - INFO - Now unplug your device and restart it into fastbootmode
20/051/2015 18:51:46 - INFO - Device connected in flash mode
20/051/2015 18:51:46 - INFO - Device disconnected
20/051/2015 18:51:49 - INFO - Device connected in flash mode
20/051/2015 18:51:52 - INFO - Device disconnected
20/051/2015 18:51:57 - INFO - Device connected in fastboot mode
20/052/2015 18:52:01 - INFO - Unlocking phone using key 7849xxxxxxxxxxxx
20/052/2015 18:52:01 - INFO - ...
20/052/2015 18:52:01 - INFO - FAILED (remote: Command did not succeed)
20/052/2015 18:52:01 - INFO - finished. total time: 0.021s
20/052/2015 18:52:22 - INFO - Device disconnected
Try a full clean install. I don´t know why unlocking the bootloader won´t work
Can someone Help please ? Is there no way to unlock the bootloader ?
If i was you, i would search for the error: remote:command not succeed
I actually got this error a few days ago. I will look into it and reply back
---------- Post added at 09:34 AM ---------- Previous post was at 09:13 AM ----------
Look at this link: http://forum.xda-developers.com/xperia-z/help/solved-bootloader-unlocking-problems-t2364334/page2
After that look at this and use Google translate for this: http://www.android-hilfe.de/anleitu...b-ul-root-bootloader-unlock-anleitung-23.html
I'm trying to unlock my bootloader, i've already installed ADB and fastboot drivers from sonys website and the Android SDK platform-tools with adb and fastboot
Both ADB and fastboot recognize my device, i've approved the device's RSA fingerprint from my phone, and I can run the command ADB reboot bootloader to get into fastboot.
Fastboot devices shows my correct device and I can run fastboot getvar version which returns 5.0
I can run fastboot reboot, and fastboot devices without any problem
When I try to unlock my device I get this error
Code:
fastboot.exe -i 0x0fce oem unlock 0xexamplekey
...
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
My devices shows bootloader unlock is allowed in the service menu.
Not sure what else to try besides another PC.
More stuff
Code:
08/053/2015 11:53:09 - INFO - Please connect your device into flashmode.
08/053/2015 11:53:10 - INFO - Opening device for R/W
08/053/2015 11:53:10 - INFO - Reading device information
08/053/2015 11:53:10 - INFO - Phone ready for flashmode operations.
08/053/2015 11:53:10 - INFO - Current device : E5823 - CB5A29DXXX - 1298-7272_R8B - 1295-6639_32.0.A.6.152 - GENERIC_32.0.A.6.152
08/053/2015 11:53:10 - INFO - Processing loader.sin
08/053/2015 11:53:10 - INFO - Checking header
08/053/2015 11:53:10 - INFO - Flashing data
08/053/2015 11:53:10 - INFO - Processing of loader.sin finished.
08/053/2015 11:53:10 - INFO - Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2_119 / Bootloader status : ROOTABLE
08/053/2015 11:53:10 - INFO - Start Reading unit 000008B2
08/053/2015 11:53:10 - INFO - Reading TA finished.
08/053/2015 11:53:11 - INFO - Ending flash session
08/053/2015 11:53:11 - INFO - Now unplug your device and restart it into fastbootmode
08/053/2015 11:53:11 - INFO - Device connected in flash mode
08/053/2015 11:53:11 - INFO - Device disconnected
08/053/2015 11:53:19 - INFO - Device connected in flash mode
08/053/2015 11:53:38 - INFO - Device disconnected
08/053/2015 11:53:46 - INFO - Device connected in fastboot mode
08/054/2015 11:54:20 - INFO - Unlocking phone using key 0xB6E1A89C6FEXXXXX
08/054/2015 11:54:20 - INFO - ...
08/054/2015 11:54:20 - INFO - FAILED (remote: Command not allowed)
08/054/2015 11:54:20 - INFO - finished. total time: 0.011s
08/054/2015 11:54:27 - INFO - Unlocking phone using key B6E1A89C6FEXXXXX
08/054/2015 11:54:27 - INFO - ...
08/054/2015 11:54:27 - INFO - FAILED (remote: Command not allowed)
08/054/2015 11:54:27 - INFO - finished. total time: 0.008s
08/055/2015 11:55:25 - INFO - List of connected devices (Device Id) :
08/055/2015 11:55:25 - INFO - - USB\VID_0FCE&PID_0DDE\CB5A29DXXX Driver installed : true
08/055/2015 11:55:25 - INFO - List of ADB devices :
08/055/2015 11:55:25 - INFO - - none
08/055/2015 11:55:25 - INFO - List of fastboot devices :
08/055/2015 11:55:25 - INFO - - CB5A29DXXX
http://forum.xda-developers.com/showthread.php?t=3236237
Xerwulf said:
http://forum.xda-developers.com/showthread.php?t=3236237
Click to expand...
Click to collapse
I've used you guide, it didn't work.
I've tried unlocking with fastboot and flash tool with no success.
Maybe you are in flashmode not fastboot? Volume down is flashmode and volume up fastboot, when I remember right
Xerwulf said:
Maybe you are in flashmode not fastboot? Volume down is flashmode and volume up fastboot, when I remember right
Click to expand...
Click to collapse
Nope, I've tried both. I can get into both modes, but flashing or unlocking gives me that error
Did you start Cmd as ADMIN?
Xerwulf said:
Did you start Cmd as ADMIN?
Click to expand...
Click to collapse
Yes.
Found my mistake, i didn't check the allow OEM bootloader unlock box. It's working now. My mistake.
tylerwatt12 said:
Found my mistake, i didn't check the allow OEM bootloader unlock box. It's working now. My mistake.
Click to expand...
Click to collapse
I'm having the exact same issue right now, where did you find this OEM bootloader unlock box?? I only have a blank screen when I get to fastboot mode on the Z5C... Cheers
ds980x said:
I'm having the exact same issue right now, where did you find this OEM bootloader unlock box?? I only have a blank screen when I get to fastboot mode on the Z5C... Cheers
Click to expand...
Click to collapse
In the same place where you enabled USB debugging (to enable ADB), developer options of settings.
You won't ever see a screen in fastboot mode, just a color LED, same with flashmode. The only time you'll see a screen is if you hit the volume buttons after the amber light during boot, which takes you into software update mode, (recovery)
Never mind found it in dev settings cant believe I missed such a small thing to create huge problems lol all done
Has anyone got a easy newbie walk through on how to replace drm keys? I unlocked bootloader and lost them in the process. The only thing that won't work is my Camera at the moment help would really be appreciated here's my model information and the faults.
frankiebateman said:
Has anyone got a easy newbie walk through on how to replace drm keys? I unlocked bootloader and lost them in the process. The only thing that won't work is my Camera at the moment help would really be appreciated here's my model information and the faults.
Click to expand...
Click to collapse
You can't recover them. Your best call is using one of the custom kernels with drm fix.
frankiebateman said:
Has anyone got a easy newbie walk through on how to replace drm keys? I unlocked bootloader and lost them in the process. The only thing that won't work is my Camera at the moment help would really be appreciated here's my model information and the faults.
Click to expand...
Click to collapse
DRM KEYS can never be revered!
before unlocking, you should have used Dirtycow script to EXTRACT TA.IMG (android6.01)
anyhow
now the only solution is to use kernel with drmfix
https://forum.xda-developers.com/xperia-x/development/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Is there one that will work with my phone and also a walk through that I can understand lol
frankiebateman said:
Is there one that will work with my phone and also a walk through that I can understand lol
Click to expand...
Click to collapse
this kernel will work: https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
tried flashing but keeps saying failed ?
13/045/2017 21:45:47 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
13/045/2017 21:45:47 - INFO - Executing search strategies to find proxy selector
13/045/2017 21:45:48 - INFO - No proxy found for IE. Trying next one
13/045/2017 21:45:48 - INFO - No proxy found for firefox. Trying next one
13/045/2017 21:45:48 - INFO - No proxy found for java. Trying next one
13/045/2017 21:45:48 - INFO - Syncing devices from github
13/045/2017 21:45:49 - INFO - Opening devices repository.
13/045/2017 21:45:50 - INFO - Scanning devices folder for changes.
13/046/2017 21:46:14 - INFO - Pulling changes from github.
13/046/2017 21:46:15 - INFO - Quietly closing devices repository.
13/046/2017 21:46:16 - INFO - Devices sync finished.
13/046/2017 21:46:16 - INFO - Loading devices database
13/046/2017 21:46:16 - INFO - Loaded 98 devices
13/046/2017 21:46:16 - INFO - Starting phone detection
13/046/2017 21:46:22 - INFO - Device connected in fastboot mode
13/046/2017 21:46:45 - INFO - Device disconnected
13/049/2017 21:49:43 - INFO - Now plug your device in Fastboot Mode
13/049/2017 21:49:53 - INFO - Device connected in fastboot mode
13/050/2017 21:50:16 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Batemans\Desktop\New folder\Suzu_F5121_34.3.A.0.206-12July17\Suzu_F5121_34.3.A.0.206-12July17\boot_F5121_34.3.A.0.206_7.1.1_clean.img
13/050/2017 21:50:16 - INFO - Flashing selected kernel
13/050/2017 21:50:18 - INFO - target reported max download size of 536870912 bytes
13/050/2017 21:50:18 - INFO - sending 'boot' (17204 KB)...
13/050/2017 21:50:18 - INFO - OKAY [ 0.558s]
13/050/2017 21:50:18 - INFO - writing 'boot'...
13/050/2017 21:50:18 - INFO - FAILED (remote: Command not allowed)
13/050/2017 21:50:18 - INFO - finished. total time: 0.561s
13/050/2017 21:50:18 - INFO - FASTBOOT Output:
target reported max download size of 536870912 bytes
sending 'boot' (17204 KB)...
OKAY [ 0.558s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.561s
13/050/2017 21:50:18 - INFO - Please check the log before rebooting into system
and bootloader is unlocked ive checked service menu
sorry for all the posts ive now managed to flash but am getting the following message. your phone is unlocked and cannot be trusted and then on loadup to start android enter your password
kistigun said:
this kernel will work: https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
Click to expand...
Click to collapse
Thanks for that! All working now just a message on startup your phone is unlocked and cannot be trusted. Is there any way to hide this?
No, that is the message you always get after unlocking your bootloader. Only solution is to relock and flash a stock rom.
I remember when sony did this to us with the z1 i think it was, we all complained to sony and they delivered an update that allowed the camera to work again with an unlocked loader.
Hello everyone; I need your help and assistance.
I am having trouble unlocking the bootloader of a Sony Xperia M4 Aqua E2303 device; the Service Menu (*#*#7378423#*#*) reveals Rooting Status: Bootloader unlock allowed - Yes.
Device Details
Android version: 5.0
Build number: 26.1.A.3.111
I have downloaded and installed the corresponding driver from https://developer.sony.com/develop/drivers/, downloaded and installed the Google USB Driver (https://developer.android.com/studio/run/win-usb), and availed an unlock code from https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
From hereon, I downloaded and extracted the SDK Platform-Tools for Windows (https://developer.android.com/studio/releases/platform-tools), but utilising the code
Code:
fastboot -i 0x0fce oem unlock 0x<myunlockcode>
(referred from https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/) only yielded within Command Prompt the message: fastboot: unknown option -i.
Since the above procedure did not yield the desired result, I attempted the alternative: Flashtool method, using the [Guides][Root][FlashTool][Drivers][Memory Problems][Unlock Bootloader] [TA Backup] (https://forum.xda-developers.com/m4-aqua/general/guide-t3130092) as a reference guide. I downloaded and installed Flashtool 0.9.18.6, and the Flashtool Drivers; albeit the installation directory on my computer is set C:\Flashtool, inside C:\Users\<myusername>\.flashTool\registeredDevices, I created a folder titled mydevices, within it another folder having the device code as its title, and within the latter folder I created a text file titled ulcode, having the unlock code as data entry.
However, post flash mode and fastboot mode processes, Flashtool concludes ....INFO - FAILED (remote: Command not allowed). I have furnished the narrative of the Flashtool process' log below.
08/024/2018 02:24:04 - INFO - Flashtool Version 0.9.18.6 built on 30-05-2015 22:30:00
08/024/2018 02:24:04 - INFO - Executing search strategies to find proxy selector
08/024/2018 02:24:04 - INFO - No proxy found for IE. Trying next one
08/024/2018 02:24:04 - INFO - Strategy firefox failed trying next one : No Firefox installation found
08/024/2018 02:24:04 - INFO - No proxy found for java. Trying next one
08/024/2018 02:24:04 - INFO - Syncing devices from github
08/024/2018 02:24:04 - INFO - Scanning devices folder for changes.
08/024/2018 02:24:11 - INFO - Pulling changes from github.
08/024/2018 02:24:11 - INFO - Devices sync finished.
08/024/2018 02:24:12 - INFO - Device disconnected
08/024/2018 02:24:22 - INFO - Device connected with USB debugging off
08/024/2018 02:24:22 - INFO - For 2011 devices line, be sure you are not in MTP mode
08/024/2018 02:24:22 - INFO - Device connected with USB debugging on
08/024/2018 02:24:22 - ERROR - root : this bundle is not valid
08/024/2018 02:24:23 - INFO - Connected device : Sony Xperia M4 Aqua
08/024/2018 02:24:23 - INFO - Installed version of busybox : N/A
08/024/2018 02:24:23 - INFO - Android version : 5.0 / kernel version : 3.10.49-perf-gc6d4e64 / Build number : 26.1.A.3.111
08/024/2018 02:24:31 - INFO - Please connect your device into flashmode.
08/024/2018 02:24:36 - INFO - Device disconnected
08/025/2018 02:25:22 - INFO - Device connected in flash mode
08/025/2018 02:25:22 - INFO - Opening device for R/W
08/025/2018 02:25:22 - INFO - Reading device information
08/025/2018 02:25:22 - INFO - Phone ready for flashmode operations.
08/025/2018 02:25:22 - INFO - Current device : E2303 - YT9114QVLK - 1293-9369_R16A - 1291-5963_26.1.A.3.111 - GENERIC_26.1.A.3.111
08/025/2018 02:25:22 - ERROR - root : this bundle is not valid
08/025/2018 02:25:22 - INFO - Processing loader.sin
08/025/2018 02:25:22 - INFO - Checking header
08/025/2018 02:25:22 - INFO - Flashing data
08/025/2018 02:25:22 - INFO - Processing of loader.sin finished.
08/025/2018 02:25:23 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_37 / Bootloader status : ROOTABLE
08/025/2018 02:25:23 - INFO - Start Reading unit 000008B2
08/025/2018 02:25:23 - INFO - Reading TA finished.
08/025/2018 02:25:23 - INFO - Ending flash session
08/025/2018 02:25:23 - INFO - Now unplug your device and restart it into fastbootmode
08/025/2018 02:25:23 - INFO - Device connected in flash mode
08/025/2018 02:25:24 - INFO - Device disconnected
08/025/2018 02:25:27 - INFO - Device connected in flash mode
08/025/2018 02:25:33 - INFO - Device disconnected
08/025/2018 02:25:51 - INFO - Device connected in fastboot mode
08/029/2018 02:29:20 - INFO - Unlocking phone using key XXXXXXXXXXXXXXXX
08/029/2018 02:29:20 - INFO - ...
08/029/2018 02:29:20 - INFO - FAILED (remote: Command not allowed)
08/029/2018 02:29:20 - INFO - finished. total time: 0.005s
I await your valuable replies, correcting whatever mistake(s) I may have very likely committed.
Having done almost all of the important leg work, I overlooked the most fundamental dynamic: Enable OEM unlock within Developer options; I was unaware of the said feature due to lack of sustained experience with Sony Xperia devices!
:silly:
The bootloader has been successfully unlocked, subsequently, custom recovery (TWRP) was successfully flashed, and the device was successfully rooted.
:good: