asked 2019-03-02 05:33:58 +0200
Hi guys need your help So i bought a sony x with sailfish os , after a time i installed android, but i need to return for sailfish and forever lol but now when i try to follow the steps i'm receiving that message :
fastboot device fastboot oem unlock < code here>
waiting device
and when i use EMMA Sony Flash tool for Xperia says : device locked but the device can be unlocked i already checked.
answered 2019-03-02 20:13:46 +0200
If Sailfish was on the device when you bought it, it means it has been unlocked already, no? Can't you just flash it without going through the unlock routine?
Hi guys , so i was doing that on windows, seems that problem was a driver or just the OS , so i tried with ubuntu <3 and worked fine using SUDO command. too fast , now i'm back using Sailfish OS. So thank you once more , thank you so much
tamarindojuice ( 2019-03-03 15:07:12 +0200 )editAsked: 2019-03-02 05:33:58 +0200
Seen: 1,332 times
Last updated: Mar 02 '19
On Linux? I made the same mistake with same result following Sony's instructions on XA2: you need to add sudo to the command. Doind the same command with sudo did the trick for me.
Terrible oversight on their part.
teemu ( 2019-03-02 08:16:33 +0200 )editWell
fastboot device fastboot oem unlock < code here>
Is not the correct command
fastboot oem unlock < code here>
Is the correct, run as administrator/sudo
Nieldk ( 2019-03-02 08:32:44 +0200 )edit@Nieldk, the commands in the post seems to be a bit messed up ('fastboot device' is a separate previous command) but judging from the results @tamarindojuice seems to be doing the correct thing except for the lack of sudo.
The correct command needs to have 0x< code here >
teemu ( 2019-03-02 09:15:47 +0200 )editSeems like the issue is 'waiting for any device' - the output of a fastboot command when there's no fastboot drivers enabling the device recognition, (or I guess on Linux, it's not drivers, but device is not being recognized). If you get that message, you typed a proper command, (maybe just a typo in the post...).Try connecting in fastboot mode and typing 'fastboot devices'.
Levone1 ( 2019-03-02 14:20:38 +0200 )edit