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
Related
Hi experts
I'm unable to install the MiniCMSandwich kernel on my st15i. tried this method (the 2nd one via flashtool) twice or thrice but still my i'm not able to install it
http://forum.xda-developers.com/showthread.php?t=1500226
the log is this
05/000/2012 16:00:25 - INFO - <- This level is successfully initialized
05/000/2012 16:00:25 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
05/000/2012 16:00:25 - INFO - You can drag and drop ftf files here to start flashing them
05/000/2012 16:00:30 - INFO - Device disconnected
05/001/2012 16:01:25 - INFO - Device connected with USB debugging off
05/001/2012 16:01:25 - INFO - For 2011 devices line, be sure you are not in MTP mode
05/001/2012 16:01:29 - INFO - Device connected with USB debugging on
05/001/2012 16:01:29 - INFO - Connected device : ST15
05/001/2012 16:01:29 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
05/001/2012 16:01:29 - INFO - Android version : 2.3.3 / kernel version : 2.6.32.9-perf
05/001/2012 16:01:29 - INFO - Root Access Allowed
05/002/2012 16:02:15 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
05/002/2012 16:02:15 - INFO - Device Status: ADB mode
05/002/2012 16:02:16 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
05/002/2012 16:02:21 - INFO - Device will soon enter fastboot mode
05/002/2012 16:02:21 - INFO - Device disconnected
05/002/2012 16:02:23 - INFO - Device connected in fastboot mode
05/002/2012 16:02:57 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot_smultron_rc3_final.img
05/002/2012 16:02:57 - INFO - Flashing selected kernel
05/002/2012 16:02:57 - INFO - FASTBOOT Output:
sending 'boot' (6006 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
05/002/2012 16:02:57 - INFO - Please check the log before rebooting into system
05/002/2012 16:02:59 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
05/003/2012 16:03:00 - INFO - Device will soon reboot back into fastboot mode
05/003/2012 16:03:00 - INFO - Device disconnected
05/003/2012 16:03:02 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
05/003/2012 16:03:02 - INFO - Device connected in fastboot mode
05/003/2012 16:03:02 - INFO - Device will soon reboot back into fastboot mode
05/003/2012 16:03:02 - INFO - Device disconnected
05/003/2012 16:03:04 - INFO - Device connected in fastboot mode
05/003/2012 16:03:10 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot_smultron_rc3_final.img
05/003/2012 16:03:10 - INFO - Flashing selected kernel
05/003/2012 16:03:10 - INFO - FASTBOOT Output:
sending 'boot' (6006 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
05/003/2012 16:03:10 - INFO - Please check the log before rebooting into system
Another question how can i check the kernel is installed properly so that i can proceed to install miui ?????
Thanks
same problem in cmd also
Whne i'm trying to use the cmd method it's saying the same error. my bootloader is unlocked & the device is rooted. I can use the R/O & R/W both on root explorer. then why it's saying that "The device must be rooted first"
Please help
thanks again
Comon
Someone plz reply
Thanks
Is the phone in fastboot? Do you have drivers installed?
Sent from my WT19i using xda premium
i have Bricked my Xperia ion(soft brick).
And now if i plug to charger or to pc it starts rebooting ( only sony logo lights up and then become yellowish and restarts the phone,it appears i think 10-20 times and then turn off).
I can't charge because if i put to wall charger after 10 minutes it starts bootlooping and then turn off and again the led becomes red and then again it starts bootloops........:crying::crying::crying::crying::crying::crying::crying::crying:
Gaurav Vashist said:
i have Bricked my Xperia ion(soft brick).
And now if i plug to charger or to pc it starts rebooting ( only sony logo lights up and then become yellowish and restarts the phone,it appears i think 10-20 times and then turn off).
I can't charge because if i put to wall charger after 10 minutes it starts bootlooping and then turn off and again the led becomes red and then again it starts bootloops........:crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Ok, can you enter to CWM?
Plus, this is not the subforum to post this things.
Try this.
This is the forum where you can post your problem.
manudo said:
Ok, can you enter to CWM?
Plus, this is not the subforum to post this things.
Try this.
This is the forum where you can post your problem.
Click to expand...
Click to collapse
no i can't enter the cwc:crying::crying:
and for ur rom i think u should try a different name ( my opinion_)
Gaurav Vashist said:
no i can't enter the cwc:crying::crying:
and for ur rom i think u should try a different name ( my opinion_)
Click to expand...
Click to collapse
I don't have that device but there's something called "fastboot" mode that is for flashing custom kernels. I suggest that try to enter that mode, if you can... Flash a kernel for your phone and enter to CWM, if you can do that, you have done a HUGE step.
Have to update my signature, I'll build in JB not ICS, nevermind.
manudo said:
I don't have that device but there's something called "fastboot" mode that is for flashing custom kernels. I suggest that try to enter that mode, if you can... Flash a kernel for your phone and enter to CWM, if you can do that, you have done a HUGE step.
Have to update my signature, I'll build in JB not ICS, nevermind.
Click to expand...
Click to collapse
i can access fastmode but flashtool gives an error"device must be rooted first"
05/023/2014 10:23:13 - INFO - <- This level is successfully initialized
05/023/2014 10:23:14 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
05/023/2014 10:23:21 - INFO - Device disconnected
05/023/2014 10:23:43 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/023/2014 10:23:43 - INFO - Preparing files for flashing
05/023/2014 10:23:43 - ERROR - .\firmwares\prepared\userdata.sin (Access is denied)
05/023/2014 10:23:43 - INFO - Cannot open bundle. Flash operation canceled
05/024/2014 10:24:02 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/024/2014 10:24:02 - INFO - Preparing files for flashing
05/024/2014 10:24:42 - INFO - List of connected devices (Device Id) :
05/024/2014 10:24:42 - INFO - List of ADB devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:42 - INFO - List of fastboot devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:48 - INFO - Please connect your device into flashmode.
05/031/2014 10:31:42 - INFO - Device connected in fastboot mode
05/032/2014 10:32:03 - INFO - Flash canceled
05/032/2014 10:32:12 - ERROR - This action needs a connected device in ADB mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ ]
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/032/2014 10:32:25 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/033/2014 10:33:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\kernel.sin
05/033/2014 10:33:04 - INFO - Flashing selected kernel
05/033/2014 10:33:04 - INFO - sending 'boot' (3209 KB)...
05/033/2014 10:33:04 - INFO - FAILED (remote: The Device must be rooted first)
05/033/2014 10:33:04 - INFO - finished. total time: 0.008s
05/033/2014 10:33:04 - INFO - FASTBOOT Output:
sending 'boot' (3209 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.008s
and also i can't access recovery mode)
No i think there should be no issuse
Gaurav Vashist said:
i can access fastmode but flashtool gives an error"device must be rooted first"
05/023/2014 10:23:13 - INFO - <- This level is successfully initialized
05/023/2014 10:23:14 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
05/023/2014 10:23:21 - INFO - Device disconnected
05/023/2014 10:23:43 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/023/2014 10:23:43 - INFO - Preparing files for flashing
05/023/2014 10:23:43 - ERROR - .\firmwares\prepared\userdata.sin (Access is denied)
05/023/2014 10:23:43 - INFO - Cannot open bundle. Flash operation canceled
05/024/2014 10:24:02 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/024/2014 10:24:02 - INFO - Preparing files for flashing
05/024/2014 10:24:42 - INFO - List of connected devices (Device Id) :
05/024/2014 10:24:42 - INFO - List of ADB devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:42 - INFO - List of fastboot devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:48 - INFO - Please connect your device into flashmode.
05/031/2014 10:31:42 - INFO - Device connected in fastboot mode
05/032/2014 10:32:03 - INFO - Flash canceled
05/032/2014 10:32:12 - ERROR - This action needs a connected device in ADB mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ ]
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/032/2014 10:32:25 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/033/2014 10:33:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\kernel.sin
05/033/2014 10:33:04 - INFO - Flashing selected kernel
05/033/2014 10:33:04 - INFO - sending 'boot' (3209 KB)...
05/033/2014 10:33:04 - INFO - FAILED (remote: The Device must be rooted first)
05/033/2014 10:33:04 - INFO - finished. total time: 0.008s
05/033/2014 10:33:04 - INFO - FASTBOOT Output:
sending 'boot' (3209 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.008s
and also i can't access recovery mode)
No i think there should be no issuse
Click to expand...
Click to collapse
Try to post the same thing in the Xperia ION forum, since I don't own the device, there's a LOT of people that can help you.
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
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.
so guys, i'm new here, and i have some biggest troubles with a xperia e4 e2124 dtv. he´s stucked on sony logo, after this some white flashing lines appear at the bottom of the screen, and the phone's shut down. i've tried to save him on PCC, but in the end get an error or appear a message that says the phone was blocked lol.
It can't keep it in flash mode as it always restarting / unplugging from the pc / flashtool. bootloader status is locked but it seems that in flashtools is unlocked "BLU '' because I get the bootloader unlock code, but does not accept any command in fastboot mode. usb debugging is disabled, I can not create a scatter file because the phone It is not detected by the MTK DROID. It is not detected by SP flashtools.I have tried everything but the phone has no sign of life. I tried to flash some ROM's and recovery, but nothing, the phone still no response. Please help me
this what's happened >>>>>
C:\Users\Soares\Desktop\nicholas\minimal_adb_fastboot_v1.4.2>fastboot devices
LW100265K1 fastboot
C:\Users\Soares\Desktop\nicholas\minimal_adb_fastboot_v1.4.2>fastboot flash recovery recovery.img
sending 'recovery' (5477 KB)...
OKAY [ 0.181s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.184s
C:\Users\Soares\Desktop\nicholas\minimal_adb_fastboot_v1.4.2>fastboot flash b
boot.img
sending 'boot' (25264 KB)...
OKAY [ 0.814s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.817s
C:\Users\Soares\Desktop\nicholas\minimal_adb_fastboot_v1.4.2>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Users\Soares\Desktop\nicholas\minimal_adb_fastboot_v1.4.2>
////////////////////////
08/001/2019 01:01:19 - INFO - Device connected in flash mode
08/001/2019 01:01:31 - INFO - Device disconnected
08/002/2019 01:02:23 - INFO - Device connected in flash mode
08/002/2019 01:02:42 - INFO - Device disconnected
08/002/2019 01:02:45 - INFO - Device connected in flash mode
08/003/2019 01:03:03 - INFO - Device disconnected
08/003/2019 01:03:06 - INFO - Device connected in flash mode
08/003/2019 01:03:08 - INFO - Device disconnected
08/003/2019 01:03:17 - INFO - Device connected in flash mode
08/003/2019 01:03:36 - INFO - Device disconnected
08/003/2019 01:03:38 - INFO - Device connected in flash mode
08/003/2019 01:03:57 - INFO - Device disconnected
08/003/2019 01:03:59 - INFO - Device connected in flash mode
08/004/2019 01:04:18 - INFO - Device disconnected
08/004/2019 01:04:21 - INFO - Device connected in flash mode
08/004/2019 01:04:24 - INFO - Device disconnected
08/005/2019 01:05:13 - INFO - Selected Bundle for Sony Xperia E4(E2124). FW release : 24.0.B.5.14. Customization : Sony Xperia E4 (E2124)
08/005/2019 01:05:13 - INFO - Preparing files for flashing
08/009/2019 01:09:47 - INFO - Please connect your device into flashmode.
08/010/2019 01:10:57 - INFO - Device connected in flash mode
08/011/2019 01:11:02 - INFO - Opening device for R/W
08/011/2019 01:11:04 - INFO - Reading device information
08/011/2019 01:11:04 - INFO - Phone ready for flashmode operations.
08/011/2019 01:11:04 - INFO - Opening TA partition 2
08/011/2019 01:11:04 - INFO - Start Flashing
08/011/2019 01:11:04 - INFO - Processing loader.sin
08/011/2019 01:11:04 - INFO - Checking header
08/011/2019 01:11:04 - INFO - Flashing data
08/011/2019 01:11:04 - INFO - Loader : S1_Root_2f8b - Version : MT6582_15 / Boot version : / Bootloader status : ROOTABLE
08/011/2019 01:11:04 - INFO - Max packet size set to 512K
08/011/2019 01:11:04 - INFO - USB buffer size set to 512K
08/011/2019 01:11:21 - INFO - Found a template session. Using it : C:\Users\Soares\.flashTool\firmwares\prepared\default.fsc
08/011/2019 01:11:21 - INFO - Opening TA partition 2
08/011/2019 01:11:21 - INFO - Writing TA unit 00002774. Value : 01
08/011/2019 01:11:21 - INFO - Closing TA partition
08/011/2019 01:11:21 - INFO - Flashing finished.
08/011/2019 01:11:21 - INFO - Please unplug and start your phone
08/011/2019 01:11:21 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
08/002/2019 02:02:08 - INFO - Please connect your device into flashmode.
08/002/2019 02:02:09 - INFO - Opening device for R/W
08/002/2019 02:02:10 - INFO - Reading device information
08/002/2019 02:02:10 - INFO - Unable to read from phone after having opened it.
08/002/2019 02:02:10 - INFO - trying to continue anyway
08/002/2019 02:02:10 - INFO - Phone ready for flashmode operations.
08/002/2019 02:02:10 - INFO - Opening TA partition 2
08/002/2019 02:02:10 - INFO - No loader in the bundle. Searching for one
08/002/2019 02:02:24 - INFO - Processing loader.sin
08/002/2019 02:02:24 - INFO - Checking header
08/002/2019 02:02:24 - ERROR - Processing of loader.sin finished with errors.
08/002/2019 02:02:24 - ERROR - Error in processHeader : 1 : Função incorreta.
08/002/2019 02:02:24 - INFO - Your phone bootloader cannot be officially unlocked
08/002/2019 02:02:24 - INFO - You can now unplug and restart your phone