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!
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
hey im using xperia mini pro. it is rooted. running stock .58 gingerbread rom and stock kernel.
i want to unlock my bootloader so i can use a custom kernels.
the reason i want to use a custom kernels is so that my wifi problems (keep disconnecting by itself) will be no more. hopefully. and of course to overclock and underclock my device :laugh:
im following someguyfromhell guide to unlock bootloader http://forum.xda-developers.com/showthread.php?t=1568792 at #10. but for some reason when i go to this site http://unlockbootloader.sonymobile.com my browser crashed. any idea???
and last question, what custom kernel is the best for my mini pro.
rage kernel? http://forum.xda-developers.com/showthread.php?t=1398910
krsh kernel? http://forum.xda-developers.com/showthread.php?t=1349630
or
x kernel? http://forum.xda-developers.com/showthread.php?t=1451150
which kernel gives the best battery life is most important and also for performance. which do you think the best personally?
ok thats all. i hope i can managed to unlock my bootloader and flash a custom kernels this night
Download XDA ROM HUB tool from http://forum.xda-developers.com/showthread.php?t=1715277
It allows for easy BL unlock, root/unroot
Also rage is in my opinion very good with battery life.
You've got Rage for GB, ICS and CM7.2
iONEx said:
Download XDA ROM HUB tool from http://forum.xda-developers.com/showthread.php?t=1715277
It allows for easy BL unlock, root/unroot
Also rage is in my opinion very good with battery life.
You've got Rage for GB, ICS and CM7.2
Click to expand...
Click to collapse
nice. so i just simply download the application and unlock my bootloader by there?
no need to go to http://unlockbootloader.sonymobile.com and enter my email and imei and that ****?
edit: i have tried that program. i clicked on unlock bootloader it asked me to put my imei by typing *#06# then i typed it after i click UNLOCK MY BOOTLOADER. then it ask are you sure? i clicked yes. then my phone shut off and blue led notification comes out but i checked on my computer it says cant complete install or something.
what did i miss?
Might be your adb driver wasnt installed.might be a wild guess but make sure u install all the driver
Sent from my SK17i using XDA
xhanafix said:
Might be your adb driver wasnt installed.might be a wild guess but make sure u install all the driver
Sent from my SK17i using XDA
Click to expand...
Click to collapse
how to install the driver?
EDiT:
if you can't do it with ROM HUB:
connect phone in fastboot mode, open a cmd window and type fastboot.exe -i 0x0fce getvar version
you should get some response. like 0.3. That's just confirming that your phone is connected properly.
after that, type fastboot.exe -i 0x0fce oem unlock 0xKEY
KEY is your unlock key.
iONEx said:
EDiT:
if you can't do it with ROM HUB:
connect phone in fastboot mode, open a cmd window and type fastboot.exe -i 0x0fce getvar version
you should get some response. like 0.3. That's just confirming that your phone is connected properly.
after that, type fastboot.exe -i 0x0fce oem unlock 0xKEY
KEY is your unlock key.
Click to expand...
Click to collapse
this is complicated
im now downloading and installing all the android sdk files.
everytime i go to fastboot mode. nothing happens
omg guys. could someone just simply give me the link of that drivers or whatever to install?
i have installed android sdk manager and follow this ****ing tutorial http://forum.xda-developers.com/showpost.php?p=27376017&postcount=2
i already got my special key to unlock my bootloader.
but whenever i connet my phone to fastboot mode by switching off and switch on my phone to my pc using usb while holding volume up button. blue led appear. then nothing happens!
its supposed to do this next "You will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
Open command prompt, first enter this
Code:
cd C:\...\android-sdk\platform-tools
Replace C with the correct drive letter and ... with the path to the android-sdk folder. Next, enter this command
Code:
fastboot.exe -i 0x0fce oem unlock 0xKEY" bla bla bla but i have no options to do this whatever because nothing happens when my phone on fastboot mode.
seriously i can go ape**** doing this
check if you have adb installed.
go to device manager. when you connect your phone to PC, you should see "sony ericsson" appear, and under that adb.
open cmd window. go start> run type cmd> hit enter.
just type adb. if you get a listing, you have adb.
if not,
follow this: ADB for dummies
if your adb driver installed correctly then hold SHIFT + right click the fastboot folder and choose open command from here. Follow the tutorial and ull be unlocking your bootloader in no time.
im unable to post a link but you can also check youtube and search for unlocking bootlader xperia videos.
Ok
I just updated to ICS and so far loving the new custom roms available
Im a total nooby when it comes to this so i used WotanServer (google it) to upgrade my phone to ICS then changed used a custom kernal which was recommended for the custom firmware.
Some roms don't allow you to use other kernals so it really depends on the rom itself in my opinion.
So the thing i would recommend to do it:
upgrade to .62
use and download SE Bootloader Unlocking v1.6 by quangnhut123 (it's under Arrow
Xperia Mini & Mini Pro & Active Android Developloment)
Unlock bootloader, root your device
then i used a method to upgrade my device without loosing my root and then installed krsh kernal with a custom rom which support krsh kernal ..
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:
So I just purchased this phone and am trying to follow the instructions on the Sony site. The rooting status in my service menu says my devices should be able to be unlocked.
Device is on android 13 on latest update, OEM unlock and USB debugging are both enabled.
I downloaded the usb drivers and the platform tools from the Sony site.
I opened a command prompt in the platform tools folder and when I run fastboot devices I get a response
When I run the command with my unlock code, I get the error
FAILED (remote: Command not supported in default implementation)
I tried to go to device manager to update the drivers, however when I do that it says the best driver is already installed.
I read in another thread to try to boot into the bootloader rather than fastboot. When I select reboot to bootloader the device seemingly shuts off.
EDIT: OK, I'm dumb and was in fastbootd mode rather than fastboot. I've now entered fastboot correctly (holding volume up while I plug it in, getting a black screen and a blue LED), updated the drivers correctly, and am now getting the error that the device is already unlocked. Now I guess I just need to verify that it is indeed unlocked, anyone have some advice on that?
EDIT 2: OK it seems to be going through the unlock process despite that error rather than the expected confirmation. After a few reboots it is now giving me the setup process again so I hope it worked. Leaving thread up for others who have the same issue to stumble accross.