I am following the official guide [*1], which is suggested from this root instruction[*2].
But I keep getting this error:
Code:
C:\fastboot>fastboot.exe -i 0x0fce oem unlock 0xMYKEYGOTFROMSONY
...
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
What could be wrong? Is there anyway to get more debug information to see why it's failing?
Here is my settings:
Phone model: D6503 / Xperia Z2
OS: Win 7 64-bit
USB Driver: Android Bootloader Interface version 4.0.0.0 [12/6/2010]
(This one is using android_winusb.inf dowloaded from Sony official site, and the rest files from latest Android SDK (64-bit)[*3].)
In the service info > Rooting status: Bootloader unlock allowed: Yes
Running this cmd:
Code:
>fastboot.exe -i 0x0fce getvar version
shows "5.0".
I didn't insert the SIM card while unlocking.
The phone USB debugging mode is enable already.
*1 = unlockbootloader.sonymobile.com/instructions
*2 = androidcentral.us/2014/04/root-sony-xperia-z2-on-android-4-4-2/
*3 = dl.google.com/android/adt/22.6.2/adt-bundle-windows-x86_64-20140321.zip
If you run "adb devices" from wherever your adb.exe is, does your phone show up? That's a good way to test if your USB drivers are working.
Download latest flashtool and install all drivers again and then use flashtool folders to use USB might work out better for you
Sent from my D6503 using XDA Premium 4 mobile app
i think you shouldn't show your unlock key to us
He didn't.
@JMonkeYJ: I ran adb.exe with my Z2 phone in fastboot mode, but it didn't find any device.
@festa20: I downloaded flashtool-0.9.16.0-windows, installed it.
- then run flashtool\drivers\Flashtool-drivers.exe, install below drivers:
Flashmode drivers, fastboot drivers, Xperia Z2 Device Drivers.
(But when connect Z2 to the USB in fastboot mode, in Windows 7 Device Manager, it still shows:
SAMSUNG Android Phone (my old phone was a Samsung):
Sony ADB Interface (Driver Provider: Google Inc., Driver data: 12/6/2010, Driver Version: 4.0.0.0)
Looks like the ADB driver is still the old one I installed, not from the flashtool(?)
- I then run flashtool\x10flasher_lib\fastboot.exe in command line, still got same error...
Looks like it's a driver issue, how do I install the correct driver?
khumash said:
@JMonkeYJ: I ran adb.exe with my Z2 phone in fastboot mode, but it didn't find any device.
@festa20: I downloaded flashtool-0.9.16.0-windows, installed it.
- then run flashtool\drivers\Flashtool-drivers.exe, install below drivers:
Flashmode drivers, fastboot drivers, Xperia Z2 Device Drivers.
(But when connect Z2 to the USB in fastboot mode, in Windows 7 Device Manager, it still shows:
SAMSUNG Android Phone (my old phone was a Samsung):
Sony ADB Interface (Driver Provider: Google Inc., Driver data: 12/6/2010, Driver Version: 4.0.0.0)
Looks like the ADB driver is still the old one I installed, not from the flashtool(?)
- I then run flashtool\x10flasher_lib\fastboot.exe in command line, still got same error...
Looks like it's a driver issue, how do I install the correct driver?
Click to expand...
Click to collapse
If your device is plugged in to PC in fastboot mode you need to do "fastboot devices"
nickwarn said:
If your device is plugged in to PC in fastboot mode you need to do "fastboot devices"
Click to expand...
Click to collapse
Running "fastboot devices" can see my device now. But still fail to unlock.
Code:
Flashtool\x10flasher_lib>fastboot.exe devices
MYZ2SN fastboot
khumash said:
Running "fastboot devices" can see my device now. But still fail to unlock.
Code:
Flashtool\x10flasher_lib>fastboot.exe devices
MYZ2SN fastboot
Click to expand...
Click to collapse
Let me know when you have time I will help u through team viewer and see what we can do
Sent from my D6503 using XDA Premium 4 mobile app
We did it
Sent from my D6503 using XDA Premium 4 mobile app
festa20 said:
We did it
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Many thanks to festa20 walk me through the whole process!!!
help
hi
i have the same problem in my z2 d6503 please help i can enter the recovery mode when i used the commend
fastboot flash boot ***.img
it said not command not allowed even i cant flash my device in flashtools it said error with loader.sin
help
Sony xperia z2 tablet - failed command not allowed
nickwarn said:
If your device is plugged in to PC in fastboot mode you need to do "fastboot devices"
Click to expand...
Click to collapse
I get a similar msg.
Running SDK from Linux (Tiny Core)
fastboot fired up fine
But got similar message after following Sony step-by-step.
./fastboot devices
then tried
./fastboot -i etc.
RESULT:
FAILED: (REMOTE: Command not allowed)
Any ideas?
Is there a different tool I should try another utility?
This Z2 is a Verizon release...and I noticed Sony site mentions some Z2 devices cannot be unlocked.
Is this an evil empire block?
Help!
I have problem just like OP. How did you fixed it?
Bootloader Unlocked Allowed : Yes
and fastboot working, detect my phone.
I already tried with 14,15 digit IMEI but result are same as the output bootloader key is same
I have issue using this method as well as trying to use flashtool. Both doesn't work. For fastboot I get into the command prompt and it's just stuck on waiting for device. In flashtool it can't find my device and tells me to reboot the phone. Any ideas? BTW my phone is rooted does that have something to do with it?
you cant adb bootloader unlock unless you have added/modded some adb files
(only aplies to z2 btw)
(yes fastboot and flasmode too you need the files(try developer.sonymobile.com)
try flashtool from flashtool.net
install drivers first before trying
Envious_Data said:
you cant adb bootloader unlock unless you have added/modded some adb files
(only aplies to z2 btw)
(yes fastboot and flasmode too you need the files(try developer.sonymobile.com)
try flashtool from flashtool.net
install drivers first before trying
Click to expand...
Click to collapse
Still don't work after downloading again. Anyone else got it working willing to help out? I've tried going through Sony developer again and it doesn't work. BTW my handset says bootloader is unlockable.
nyichiban said:
Still don't work after downloading again. Anyone else got it working willing to help out? I've tried going through Sony developer again and it doesn't work. BTW my handset says bootloader is unlockable.
Click to expand...
Click to collapse
have you got the drivers, adb files, adb installed with fastboot n flashmode and do you have the files for those
you can get all these files from sonymobile or adb download
of course you can try the easy way to unlock which is USING FLASHTOOL
festa20 said:
We did it
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you do? I'm having the same problem as khumash, I get:
Code:
>fastboot.exe -i 0x0fce oem unlock 0xMYKEY
...
FAILED (remote: Command did not succeed)
finished. total time: 0.020s
However, my device shows up when I do "fastboot devices", though nothing shows up when I do "adb devices"
festa20 said:
Let me know when you have time I will help u through team viewer and see what we can do
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ive got the same problem is there any chance you could help me please? its been driving me crazy trying to do this lol.
Related
i have a xperia u with locked bootlocker and also it is allowed to unlock it.
but when i connect it in fastboot mode and open cmd in fastboot folder and paste first command for boot unlocker
and that is fastboot.exe -i 0x0fce getvar version but it shows only WAITING FOR DEVICE....
it does nothing more than this...
pls help me... what to do:crying:
Bcuz you are not yet install fastboot driver
Sent from my ST25i using xda premium
nscharan007 said:
i have a xperia u with locked bootlocker and also it is allowed to unlock it.
but when i connect it in fastboot mode and open cmd in fastboot folder and paste first command for boot unlocker
and that is fastboot.exe -i 0x0fce getvar version but it shows only WAITING FOR DEVICE....
it does nothing more than this...
pls help me... what to do:crying:
Click to expand...
Click to collapse
Your phone must have decided to abandon fastboot and went into charging mode. When you connect to fastboot, check to see if the charging icon comes up, if it does. It means your phone is not staying in fastboot.
You'll need to install fastboot drivers.
Refer to this thread http://forum.xda-developers.com/showthread.php?t=1554632
I faced your problem before, and following that thread unlocked my bootloader. Good luck!
nscharan007 said:
i have a xperia u with locked bootlocker and also it is allowed to unlock it.
but when i connect it in fastboot mode and open cmd in fastboot folder and paste first command for boot unlocker
and that is fastboot.exe -i 0x0fce getvar version but it shows only WAITING FOR DEVICE....
it does nothing more than this...
pls help me... what to do:crying:
Click to expand...
Click to collapse
try multi xperia u tool @AlexDroid00
HERE
Flashtool is the easiest and fastest way, just click on Bootloader Unlock, and follow the steps
I recently purchased an Xperia Z2 D6503 from Amazon (International version); and when trying to unlock the bootloader I ran into this issue.
I followed all steps until the part where it requires that I go to device manager> right click on s1 fastboot> update drivers> and select newest google usb drivers with the modified sony file in there. However, when I try that instead of showing a progress bar and telling me it is now an ADB boot loader interface it simply says it was unable to install drivers.
I tried different folders, different drivers, and nothing works. I tried to skip to the step of opening command prompt and typing fastboot.exe -i 0x0fce getvar version, however the message [waiting on device] appears and nothing ever happens... I waited 10 minutes and nothing happened.
I didn't try the last step of typing fastboot.exe -i 0x0fce oem unlock 0xKEY, so does anyone know what to do here?
PS: I did have a Nexus 5 before this, and unlocking the bootloader there was similar but went smooth and got it first try... not here.
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
Me too !
Drivers are here: https://developer.android.com/studio/run/win-usb
These are the ones I use for ADB/Fastboot.
May I ask if anybody solved this already?
Having the same issue, tried various drivers, but fastboot won't find my phone
Help is highly apperciated!
Clock
If you using windows 10 have you disable the drivers signature verification.. And search on here (XDA) for Min ADB & Fastboot tools, easier than using SDK tools unless you modding apks ect..
Okay, I got this working.
When in fastboot mode, you have to go to the device manager, update driver, and manually choose the google fastboot driver. Then the ! is gone and it works.
Fastboot drivers for Xperia XZ1
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode.
Click to expand...
Click to collapse
I add a hint to the solution that is working for me (Windows 7, 64 bit): https://forum.xda-developers.com/showpost.php?p=79221714&postcount=44
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
when u connect phone to pc choose no data transfer then open cmd and write: adb reboot fastboot
Click to expand...
Click to collapse
Hey everyone!
I'm having trouble unlocking the bootloader of my Vivo Y33S. I've tried everything, installed the necessary drivers, and used the Vivo fastboot software, but this annoying 'waiting for device' error keeps popping up. It's like my phone refuses to unlock its boot loader!
If any of you have managed to successfully unlock the bootloader of a Vivo Y33S and dealt with this 'waiting for device' error, I could really use your help. Any tips, alternative drivers, or suggestions to get past this error and unlock the bootloader using the Vivo fastboot software would be awesome!
By the way, my Vivo Y33S is running stock firmware version PD2147GF_EX_A_38.13.0 of that helps.
Thanks a bunch in advance for your support! Your insights and expertise are much appreciated!
Please use mtk client to unlock bootloader to unlock your device.
iVIERMA said:
Hey everyone!
I'm having trouble unlocking the bootloader of my Vivo Y33S. I've tried everything, installed the necessary drivers, and used the Vivo fastboot software, but this annoying 'waiting for device' error keeps popping up. It's like my phone refuses to unlock its boot loader!
If any of you have managed to successfully unlock the bootloader of a Vivo Y33S and dealt with this 'waiting for device' error, I could really use your help. Any tips, alternative drivers, or suggestions to get past this error and unlock the bootloader using the Vivo fastboot software would be awesome!
By the way, my Vivo Y33S is running stock firmware version PD2147GF_EX_A_38.13.0 of that helps.
Thanks a bunch in advance for your support! Your insights and expertise are much appreciated!
Click to expand...
Click to collapse
Thank you for your help
i'm sorry, But it does not let me download it, may you Send a link to download it?
Enabling USB Debugging on phone is required so that your PC is able to identify your device in Fastboot Mode.
The typical Windows shell commands sequence is
Code:
adb devices
adb reboot fastboot
fastboot devices
[/coode]
xXx yYy said:
Enabling USB Debugging on phone is required so that your PC is able to identify your device in Fastboot Mode.
The typical Windows shell commands sequence is
Code:
adb devices
adb reboot fastboot
fastboot devices
[/coode]
Click to expand...
Click to collapse
I do have USB debugging and OEM unlocking enabled, but the Vivo version of fastboot doesn't detect it, while the normal version does. Unfortunately, I can't use the normal version since it doesn't work with Vivo devices.
Try this
Release v1 · AndroPlus-org/fastboot-vivo
Built with Android 11 source
github.com
xXx yYy said:
Try this
Release v1 · AndroPlus-org/fastboot-vivo
Built with Android 11 source
github.com
Click to expand...
Click to collapse
I have tried it, but it still doesn't recognize my device. I have the drivers installed, so I'm not sure what the problem could be.
Is there any other way to unlock the bootloader of the Vivo y33s?
Okay, I have now tried something else and discovered that Vivo Fastboot actually recognizes the device. However, when I execute the command 'fastboot bbk unlock_vivo' or 'fastboot vivo_bsp unlock_vivo', it displays the following error messages:
'FAILED (remote: Unrecognized command bbk unlock_vivo). finished. total time: 0.001s'
'FAILED (remote: Unrecognized command vivo_bsp unlock_vivo). finished. total time: 0.002s