I'm trying to unlock my bootloader using the official Sony method (i.e. they emailed me the unlocking key, I installed the Android SDK tools and platform-tools, and now I'm trying to enter the code.) I'm not sure why, but I'm getting stuck on the very last step, which is to run the command fastboot -i 0x0fce oem unlock 0x........ (where the dots represent my actual unlocking key). I just get the response < waiting for any device > and then nothing happens.
Just to clarify, I'm doing this on a Linux computer. My phone is being recognized by the computer, because for example if I run the command lsusb, I get my Xperia phone listed as one of the connected devices. I can also transfer files between the device and my computer without any problem.
Does anyone know what is causing the unlock process to hang?
PHONE:
Model: Xperia M4 Aqua
Model Number: E2306
Android Version: 6.0.1
Linux Kernel: 3.10.49
Build Number: 26.3.A.1.33
COMPUTER:
OS: Ubuntu Gnome 16.04 (64-bit)
Linux Kernel: 4.6.4
ANDROID SDK SOFTWARE:
Tools: 25.2.3
Platform-Tools: 25.0.1
Related
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.
Firstly hi everyone.
I have a notebook installed Linux Mint 13 LTE 32 bit.
I have added ubuntu phablet tools ppa to its sources and installed "phablet-tools, android-tools-adb, android-tools-fastboot" packages from ppa.
I can use adb and fastboot with my galaxy nexus.
But my Huawei Ascend P1 (U9200) only use with adb. Adb runs perfect.
But in fastboot mode, fastboot command returns with "waiting for device" output.
Why?
So my device is recognized when it's turned on but then I go to command prompt and click ADB reboot bootloader (enter). It just says waiting for device. If it's on and I click ADB devices in the command prompt it tells me the serial number and then says device. On the computer management it is recognized as a device it says the name Xperia XA Ultra. I tried to update the Google driver into ADB but that was a failed attempt. I couldn't quite understand what I was supposed to do there or really even follow the instructions because it kept telling me that I was unable to update drivers after I followed the instructions they gave me. I just kept getting an error message. So I'm wondering how do I solve this problem? I really would like to unlock my bootloader and I'm not even sure if it's going into fastboot. I got the notification after turning off the phone hold Volume Plus and plug it in it said of my computer that it was installing the fastboot drivers. I'm assuming it was in fastboot at that time even though I didn't get a blue light it just turned blue for a minute and then it was Green. It said it was installing fastboot drivers so I'm assuming it was in fastboot mode. This is a really tricky process I guess.
What windows do you have?
Also I would recommend you to Google how install fastboot on your Windows type.
Sent from my F3213 using xda premium
I have windows 10
Windows 10. Why would I need to install fastboot on Windows? Fastboot is on my Android device. I use ADB. Android debugging bridge is the bridge that goes between your operating system and fastboot the bootloader and Android and all of that in order to be able to communicate with the phone. Why would I need to install Fastboot on my windows? You sound like a customer service representative. I can't even talk to them anymore because they tried to get me to act like Chris Farley.
If you don't install fastboot on your computer you can't unlock bootloader you can't install custom recovery or root the phone!
Sent from my F3213 using xda premium
Hello,
Here is the link to the ADB Installer that contains all the files you need (ADB, Fastboot and Drivers). Download and following the screen information to install the program.
https://forum.xda-developers.com/showthread.php?t=2588979/
Thanks,
Danjuma
Hi there
please note that Windows 10 x64 blocks the installation of unsigned drivers. To be able to install them anyway you have to enter the Windows Test Mode. To do this you just have to run "bcdedit /set testsigning on" in an administrative command line and restart your computer afterwards. You'll see "Test Mode" at the bottom right corner of your desktop. To leave the testmode use "bcdedit /set testsigning off" and restart again.
Done all of this and it doesn't work...
You have to use drivers from Sony for Flashmode and use drivers included in Flashtool (C:\flashtool\drivers) for fastboot and ADB. No problem for me with Windows 10 64bits and don't need to use Test mode.
Hi all,
Today I decided to give WOS2.0 a try on my Pace (original Chinese watch A1612, now running on stock ROM 1.3.8a). So, I followed the steps to retrieve the required information for bootloader unlock:
1) "./adb devices" --> returns a device number
2) "./adb shell reboot bootloader" --> Watch shows that it's in fastboot
3) "./fastboot getvar all" --> No response....(waiting forever).
"./fastboot devices" doesn't return anything...
I also tried the same from Windows 10 (running in a virtualbox); exact same results...after entering fastboot mode, the watch seems to be invisible to the mac.
Tried another cable, same results.
What could be the issue? Could it be an issue with 1.3.8a firmware?
Regards,
Eeg.
Fastboot is broken on macOS High Sierra as of now (at least for some devices), but I am using version 1.0.36 from this site and it (somewhat) works:
https://android.izzysoft.de/downloads
And it works on VirtualBox too, make sure you add the device to USB devices in the guest settings as well that you have the proper drivers installed.
Hi,
Thanks for your help!
Version 1.0.36 seems to be working...so now I can request the bootloader unlock code. Let's hope that it's stable enough to perform the full procedure to upgrade to WOS2.0
Cheers,
Eeg.
Os simply install AmazeROM.
https://forum.xda-developers.com/smartwatch/amazfit/rom-amazerom-pace-v1-0-20180618-t3805928
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.