Samsung Galaxy Xcover 2 (samsung-skomer)
|Name||Galaxy Xcover 2|
|Original software||Android 4.1.2|
|Chipset||ST-Ericsson NovaThor U8500|
|CPU||2x 1 GHz ARM Cortex-A9|
Users owning this device
The mainline kernel can only be booted through U-Boot, not directly with the Samsung bootloader. U-Boot is installed as intermediate bootloader on the boot partition, so it does not replace the Samsung bootloader entirely.
Boot into Download Mode using the NovaThor U8500 U-Boot installation instructions to install U-Boot. For this device, Skomer, you should flash the .img U-Boot file, not the .raw file.+ + and follow the
Finally, just follow the Installation guide.
Since battery charging is not yet working with the mainline kernel, it is helpful to have an external Samsung battery charger at hand for charging the battery. If you plan to work intensively on the device, it is also nice to have two batteries so that you can charge one while working with the other. If you don't have an external battery charger you need to reflash the original firmware just to charge the battery which is not going to be possible if you run the battery out, so catch-22. Also worth noting is that even if you were to magically get the original firmware/recovery back on the device, you may end up in a situation where you cannot charge regardless because the phone turns off before it's able to start charging, and loops like this. In some cases it can reach enough charge during this to be able to charge properly eventually, but this may not always be the case. An external battery charger is definitely recommended.
- Display (no brightness control)
- GPU (Mali-400 MP using Lima)
- Broadcom WiFi
- Bluetooth (partial)
- HALL sensor
Bluetooth does not have any Bluetooth device address (bdaddr or "MAC address") set after boot at the moment. To make Bluetooth work, you need to manually configure one:
# apk add bluez-btmgmt # btmgmt public-addr <bdaddr>
<bdaddr> is a MAC address like
The Bluetooth controller should then show up in
# apk add bluez # rc-service bluetooth start $ bluetoothctl
DSI Scaling Error in Phosh
If your are running phosh, and the scaling is wrong so that you cannot type in the password to unlock the initial login screen, this can be fixed by changing this file
/usr/share/phosh/phoc.ini like this:
[output:DSI-1] scale = 1