Sailfish X install: flash-on-windows - device not found [answered]

Question

5

Sailfish X install: flash-on-windows - device not found [answered]

asked 2017-10-11 21:11:58 +0200

MystIsland

1061 ●14 ●20 ●22

updated 2017-10-11 21:45:57 +0200

olf
10393 ●104 ●201 ●158

Running in Win7 Ultimate 64bit in VMWare Fusion on OS X High Sierra...

Have unlocked the bootloader, used Emma put in clean Android. Phone is booted to fastboot mode, blue led is showing but I can't get the flash-on-windows to work. It says:

Searching a device with vendor id '0x0fce'.. find: product:: No such file or directory

The DEVICE this flashing script is meant for WAS NOT FOUND! You might be missing the required windows fastboot drivers for your device. Go to the Windows Device Manager and update the fastboot driver for the device.

fastboot devices sees the phone as CB512EFLUP fastboot

Sony sa0114 ADB Interface Driver is shown in Windows' Device manager.

What now?

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2018-11-16 14:05:57.917080

Comments

3

use linux, run flash.sh.

Moo-Crumpus ( 2017-10-11 22:43:22 +0200 )edit

use linux, run flash.sh.
Moo-Crumpus ( 2017-10-11 22:43:22 +0200 )edit

Accepted Answer

2

answered 2017-10-11 22:22:22 +0200

rob_kouw

1358 ●21 ●34 ●42

updated 2017-10-11 22:23:04 +0200

I had this message too, running Windows 10. Thought I installed all the necessary drivers, tried to update them but they were already there. Pulled the X from the USB, reconnected while holding Volume-Up, LED turns blue. Then ran the .bat again and it worked. Result:

 This is a Windows flashing script for Sony Xperia X device.

Power on the device in fastboot mode, by doing the following:
1. Turn off your Xperia.
2. Connect one end of a USB cable to your PC.
3. While holding the volume up button pressed, connect the other end of
   the USB cable to your Xperia.
4. After this you should see the blue LED lit on Xperia, and it will be
   ready for flashing

Press any key to continue . . .
Searching a device with vendor id '0x0fce'..
The system cannot find the drive specified.
MD5SUM '77ddc7a0b9dd95db593829b97bc9868a' match for hybris-boot.img.

C:\Users\Rob\Downloads\SailfishOS-2.1.3.5-1-f5121-0.0.1.16\SailfishOS-2.1.3.5-1-f5121-0.0.1.16>fastboot.exe -i 0x0fce flash boot hybris-boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10842 KB)...
OKAY [  0.344s]
writing 'boot'...
OKAY [  0.141s]
finished. total time: 0.500s
MD5SUM '611d0db74e6ffd22addf63318508b71d' match for fimage.img001.

C:\Users\Rob\Downloads\SailfishOS-2.1.3.5-1-f5121-0.0.1.16\SailfishOS-2.1.3.5-1-f5121-0.0.1.16>fastboot.exe -i 0x0fce flash system fimage.img001
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [  0.938s]
sending sparse 'system' 1/2 (524284 KB)...
OKAY [ 17.267s]
writing 'system' 1/2...
OKAY [  6.750s]
sending sparse 'system' 2/2 (92428 KB)...
OKAY [  3.109s]
writing 'system' 2/2...
OKAY [  1.203s]
finished. total time: 29.298s
MD5SUM '88d74c452de2521e3eebd4f4dcdb3851' match for sailfish.img001.

C:\Users\Rob\Downloads\SailfishOS-2.1.3.5-1-f5121-0.0.1.16\SailfishOS-2.1.3.5-1-f5121-0.0.1.16>fastboot.exe -i 0x0fce flash userdata sailfish.img001
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [  0.500s]
sending sparse 'userdata' 1/3 (524284 KB)...
OKAY [ 17.297s]
writing 'userdata' 1/3...
OKAY [  6.828s]
sending sparse 'userdata' 2/3 (524284 KB)...
OKAY [ 17.266s]
writing 'userdata' 2/3...
OKAY [  6.781s]
sending sparse 'userdata' 3/3 (252840 KB)...
OKAY [  8.314s]
writing 'userdata' 3/3...
OKAY [  3.266s]
finished. total time: 60.268s

C:\Users\Rob\Downloads\SailfishOS-2.1.3.5-1-f5121-0.0.1.16\SailfishOS-2.1.3.5-1-f5121-0.0.1.16>fastboot.exe -i 0x0fce flash oem SW_binaries_for_Xperia_AOSP_M_MR1_3.10_v13_loire.img
target reported max download size of 536870912 bytes
sending 'oem' (163040 KB)...
OKAY [  5.563s]
writing 'oem'...
OKAY [ 21.483s]
finished. total time: 27.045s

Flashing completed.

edit flag offensive delete publish link

Comments

Same here - Win10Pro. Trying flasher.sh on linux now.

Spoofy ( 2017-10-12 01:19:35 +0200 )edit

Yeap, Linux flasher works:

Detected Linux
Searching device to flash..
Found device with vendor id '0fce': Bus 001 Device 006: ID 0fce:0dde Sony Ericsson Mobile Communications AB Xperia Mini Pro Bootloader
Fastboot command: fastboot -i 0x0fce 
Flashing boot partition..
target reported max download size of 536870912 bytes
sending 'boot' (10842 KB)...
OKAY [  0.424s]
writing 'boot'...
OKAY [  0.143s]
finished. total time: 0.567s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [  0.937s]
sending sparse 'system' 1/2 (524284 KB)...
OKAY [ 20.378s]
writing 'system' 1/2...

<< etc.

Spoofy ( 2017-10-12 01:35:31 +0200 )edit

Hi there,

it worked out for me, too. What I was doing different in step 6 of the Jolla-instruction was:

FIRST starting the bat-file: 6.6 On Windows 7, 8 & 10, double-click ‘flash-on-windows.bat’.

Then following steps 1.-4. in the cmd-line as in the answer of rob_kouw, what is basically Jollas 6.1-6.4

Then the flashing startet - even when theres was in the first moment an error message as well, which I cannot remember - and ended succesful without doing anything further.

It looked like above cmd-lines posted from rob_kouw as well.

This answer motivated me to try again and with that I changed the order of the steps like stated above.

I am very happy that the ship sails on so beautiful into the future :-)))). Hope it will for many years.

The time with Android was hard... perpetual trying to get more and more data from me :-((

zemideluxe ( 2017-10-12 23:37:42 +0200 )edit

Answer 2

0

answered 2017-10-12 02:23:53 +0200

buga
1 ●1 ●1

updated 2017-10-12 02:24:47 +0200

Hi folks! I got another problem with the "flash-on-windows.bat" file. Followed the instructions and everything worked fine until this point. Does anybody have an idea what this "ping" and "find" could be? I'm atm not able to use Linux and im not that tech savy to solve this problem alone :P

This is a Windows flashing script for Sony Xperia X device.

Power on the device in fastboot mode, by doing the following: 1. Turn off your Xperia. 2. Connect one end of a USB cable to your PC. 3. While holding the volume up button pressed, connect the other end of
the USB cable to your Xperia. 4. After this you should see the blue LED lit on Xperia, and it will be
ready for flashing

Drücken Sie eine beliebige Taste . . . Der Befehl "ping" ist entweder falsch geschrieben oder konnte nicht gefunden werden. Searching a device with vendor id '0x0fce'.. Der Befehl "ping" ist entweder falsch geschrieben oder konnte nicht gefunden werden.

The DEVICE this flashing script is meant for WAS NOT FOUND! You might be missing the required windows fastboot drivers for your device. Go to the Windows Device Manager and update the fastboot driver for the Der Befehl "find" ist entweder falsch geschrieben oder konnte nicht gefunden werden. device.

Drücken Sie eine beliebige Taste . . .

edit flag offensive delete publish link

Comments

2

ping and find are two standard windows commands. if the script can't find them either you have a faulty windows-installation or the path variable is not set correctly or yet something else. Try the following: - click the windows Logo search for cmd and type enter -> a new window with a command prompt should open. - type "set path" - look for C:\Windows\System32 -> If it is missing - what I suspect to be the problem - type the following: SETX /M PATH "%PATH%;C:\Windows\System32" Then close the window and try to install SFX again.

joschobart ( 2017-10-12 17:59:45 +0200 )edit

You my friend, are my savior..!

Worked very well! I thought it could be that, because I changed this path for unlocking the bootloader. I had issues to get the Android SDK Manager to run and several "Tutorials" told about to change that path. I just didn't know what to change in that path.

Thank you very much! You helped me to be a very happy sailor :)

buga ( 2017-10-12 19:32:18 +0200 )edit

Answer 3

0

answered 2017-10-12 17:20:50 +0200

MystIsland

1061 ●14 ●20 ●22

Couldn't solve this on Windows, but managed to do it on command line of OS X. Now rocking a Sailfish on my Xperia :)

edit flag offensive delete publish link

Answer 4

0

answered 2017-11-19 02:21:39 +0200

wolfgang

1

I also had problems on my Win 10 Computer. After changing the USB Port it worked!

edit flag offensive delete publish link

Answer 5

0

answered 2017-11-20 14:01:45 +0200

ehakkarainen

2548 ●58 ●88 ●87

Please make sure the IMEI of the phone is correct by accessing the settings menu in android - I wasted 3 hours with a wrong IMEI because the one printed on the box was slightly different from the actual one on the phone :(

I did get the same "Device not found" error when trying the unlocking with wrong IMEI based Sony unlock code.

edit flag offensive delete publish link

Answer 6

0

answered 2018-01-02 01:44:45 +0200

caa
188 ●5 ●8 ●12

On Windows: Ensure you run command prompt as Administrator (Right-Click, Run as Administrator) otherwise the flash-on-windows.bat script cannot create the tmpfile.txt file to verify the result of querying whether the device is correct.

Once you are running command prompt as Administrator, then cd to the correct directory containing fastboot.exe and all the other files, then run flash-on-windows .

edit flag offensive delete publish link

Sailfish X install: flash-on-windows - device not found [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2018-11-16 14:05:57.917080

Comments

6 Answers

Comments

Comments

Question tools

Stats

Related questions

Sailfish X install: flash-on-windows - device not found [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan close date 2018-11-16 14:05:57.917080

Comments

6 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2018-11-16 14:05:57.917080