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.
Related
Hey guys! I'm a noob, I aknowledge it and I apologize for it.
I've been trying to open the bootloader on my brand new Ray by following the official Sony Ericsson guide found on their website. The problem is that I'm stuck with this step:
# Open a command window and go to the tools folder within the Android SDK folder.
# Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your phone is connected properly.
The only answer that I get from command promt is: 'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.
This leads me to thinking that there's not fastboot in the SDK-folder. Why is this? I've followed the guide to the letter, and I've checked several times that I actually did follow it to the letter. Any help guys? Please?
Found the solution after hours and hours of fighting, still not through with all the problems though.
Try flashtool, inside x10 flasher folder you will find the required fastboot and adb.exe and dll for them. Try from there.
http://forum.xda-developers.com/showthread.php?t=1034087
Try this to unlock boot loader I uses it found Easier than se site
It.sounds like a driver problem I had the same issue the link above has the.drivers needed.to sort it out
sent from my gorgeus Xperia Ray
I've been trying to work this our for quiet some time now.
Phone - Live with Walkman
PC - Windows 8 - 64 bit
What I did till now:
- Installed the Android SDK on my machine (for fastboot.exe)
- Acquired the unlock key from sony website (and verified that my bootloader can be unlocked *#*#7978423*#*#)
- Also, went to the Windows 8 PC settings and disabled the driver signature enforcement to false
- Downloaded the driver file from sony website and copied it in usb_drivers
Now,
When I switch off my phone and put it into fastboot mode (Power up and USB cable), nothing happens in PC ... didn't asked for any drivers.
Running 'fastboot.exe -i 0x0fce getvar version' gives nothing.
In device manager, I can see a S1Fastboot Loader device but with no drivers. When I tried to manually install drivers, it didn't do anything.
Finally - I installed ADB driver instead.
Now, the command 'fastboot.exe -i 0x0fce getvar version' gicves '0.3' :laugh::laugh::laugh::laugh:
BUT -
fastboot.exe -i 0x0fce oem unlock 0x[my_key] is failing.
What should I do now???????
Seems like some issues with windows 8?????
arpitghiya said:
I've been trying to work this our for quiet some time now.
Phone - Live with Walkman
PC - Windows 8 - 64 bit
What I did till now:
- Installed the Android SDK on my machine (for fastboot.exe)
- Acquired the unlock key from sony website (and verified that my bootloader can be unlocked *#*#7978423*#*#)
- Also, went to the Windows 8 PC settings and disabled the driver signature enforcement to false
- Downloaded the driver file from sony website and copied it in usb_drivers
Now,
When I switch off my phone and put it into fastboot mode (Power up and USB cable), nothing happens in PC ... didn't asked for any drivers.
Running 'fastboot.exe -i 0x0fce getvar version' gives nothing.
In device manager, I can see a S1Fastboot Loader device but with no drivers. When I tried to manually install drivers, it didn't do anything.
Finally - I installed ADB driver instead.
Now, the command 'fastboot.exe -i 0x0fce getvar version' gicves '0.3' :laugh::laugh::laugh::laugh:
BUT -
fastboot.exe -i 0x0fce oem unlock 0x[my_key] is failing.
What should I do now???????
Seems like some issues with windows 8?????
Click to expand...
Click to collapse
You Just Need Unlock it 1 time.so u can use a windows 7 pc for one time.no need to discuss.
.
.
anyway u can use flashtool.
I have a problem to install ADB drivers too, on windows 8, BUT I sloved it with this tutorial: http://forum.xda-developers.com/showthread.php?t=2044804
And now I have unlocked my Xperia mini pro bootloader
So it's posible to unlock bootloader on win 8 after installing ADB drivers.
How about IMEI did you enter first 14 corectly without last one?
I think that you have wrong unlock code.
arpitghiya said:
Now,
When I switch off my phone and put it into fastboot mode (Power up and USB cable), nothing happens in PC ... didn't asked for any drivers.
Click to expand...
Click to collapse
Volume up button, not power.
I'm having troubles with unlocking the bootloader from my xperia U. I am following the steps from this site unlockbootloader.sonymobile.com/instructions , and everything goes very well until step 13. I am not asked to install the driver they mention in that step and I haven't found a solution to install it.
I tried to avoid that step and to go straight into command window and entering the commands ( like fastboot.exe -i 0x0fce getvar version). I don't get a response but an error that states the .exe file couldn't be recognized.
I have flastool installed, and I have installed all the drivers from it. I also tried to use the 'blu' option, but then I get the message "your phone can not be officially unlocked" . I have been searching for 5 days now, and I don't know what to do..
Any kind of help is welcome!
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:
I'm at a total loss here...
phone has unlocking and USB debugging toggled on.
phone is not a US phone and unlocking is allowed.
phone goes into fastboot mode (by turning on while holding volume)
"fastboot devices" command returns my phone is in fastboot and connected
"fastboot oem unlock 0xPASSWORD" returns FAILED (remote: 'Command not supported in default implementation')
and fastboot: error: Command failed
I have no idea what to do or try from here.
If I try to flash an image i get:
FAILED (remote: 'Download is not allowed on locked devices')
so, defiantly still locked out of the bootloader
Try below steps
1. Ensure you have platform tools 33.x , 34 has issues.
2. Try to reboot to bootloader from pc.
adb reboot bootloader
3. Try running
fastboot flashing unlock unlockcode
Try it :
fastboot oem unlock
or
fastboot flashing unlock
SOLVED I am so happy. I'm on day 3 of trying to get the phone to bootload.
there is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.
fastboot through the phone shows the drop down menu and no blue light illuminated on phone.
fastboot through adb phone is black screen with a blue light on right corner on the phone.
the windows drivers behave differently between the two. I am running windows 10. phone model XQ-CT72
steps that solved the issue. For anyone in the future.
I downloaded and used platform tools version 33.0.3 NOT version 34.
"adb reboot bootloader" used from windows PC
opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. It would not detect it on its own, or even use the SONY driver without me telling it to specifically. device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver
everything worked following these instructions here https://www.droidwin.com/unlock-bootloader-and-root-sony-xperia-1-iv/
alexriethmeier said:
There is definitely a difference between going into ...
Click to expand...
Click to collapse
fastboot, part of the android bootloader, abl
fastbootd, part of recovery
I had same issue and same solution fixed it what you showed and did. I was terrified, after investing so much money on this phone and not getting it unlocked.
You won't need to go through such hassle if you just use Linux VM (a Ubuntu distro will do). The driver works out of the box.