I have a few questions about how to install sailfish os 2.
I have Fairphone OS 1.7.1 currently installed on my Phone. Can i actually install sailfish os 2 with fastboot on this version, or do i have to downgrade? Or do I have to install Open OS anyway?
When I install Open OS 16.10.0, which verison of sailfish os 2 should i donwload? Do I have to take a lower version of Open OS?
I tried to access my Phone (in fastboot mode) on my computer with the command âfastboot devicesâ, but I didnât get any results. Is this due to the fact, that I have Fairphone OS 1.7.1 and I need Open OS?
Yes, in deed. Swipe top to botom and have a look if you see the usb - connection options.
The thing is, you have to UN-check all options.
edit:
if that also doesnât work try this on your ubuntu terminal:
$ wget -S -O - http://source.android.com/source/51-android.rules | sed âs//$USER/â | sudo tee >/dev/null /etc/udev/rules.d/51-android.rules; sudo udevadm control --reload-rules
and replace with your computers user you can find in the right uper cornerâŚ
im sorry. i was mixing the two states of the phone fastboot and adbâŚ
in the meantime i was editing my post:
or try to add these two lines to the udev rules under /etc/udev/rules.d/51-android.rules
# Fairphone 1
SUBSYSTEMS==âusbâ, ATTRS{idVendor}==â0bb4â, ATTRS{idProduct}==â0c03â, GROUP=âusersâ, MODE=â0666â
# Fairphone 2
SUBSYSTEMS==âusbâ, ATTRS{idVendor}==â2ae5â, ATTRS{idProduct}==â9015â, GROUP=âusersâ, MODE=â0666â
So i can take Knoppix and try to do the statements from novski.
If i do so, i have to do everything via Knoppix. That means that i will have to write the âfastboot commandsâ in the Knoppix terminal too. Am i right, or did i understand something wrong?
I donât see a reason why fastboot should not work if adb doesâŚ
Are you certain your phone is in bootloader mode ? ie, try to run âadb reboot bootloaderâ to be sure, instead of using the shortcuts.
Also, yes a live USB (or CD) linux can help you. You can jump as well on the occasion and install it aside your windows, this canât hurt
Then i write âadb reboot bootloaderâ and afterwards âfastboot devicesâ should find my phone, but it doesnât.
When i write âfastboot deviceâ, it says: â< waiting for device >â. When i google this problem, i can often read, that if that occurs there might be wrong drivers installed.
Some people say the problem is because when the phone is ânormallyâ connected, it needs other drivers then when it is connected with fastboot mode.
But I think, me driver ins fastboot mode should be okay. (on screen)
I found the problem. Its really the Kedacom driver. I uninstalled it. Afterwards, i could set another driver for my device. and then it worked for a short time. Because while i was doing that, the device automatically installed the kedacom driver again, and i then it didnât work anymore.
I donât know where this driver comes from. Does anyone know how to avoid that this driver installs itself automatically?