asked 2019-10-24 20:02:41 +0200
It seems that update of 3.2.0.xx is in the very long run away. Thus progres with SFOS X happens very too slowly ... I have been considering flashing my XA2 back to Android again.
Does anyone know if relocking of bootloader of XA2 with Android happens as shown in
https://www.theandroidsoul.com/relock-bootloader-fastboot-android/
The relocking is required to get my Galaxy Watch working again with Android.
So it goes ....
answered 2019-10-25 16:44:10 +0200
Do not relock it. Unlocking deletes TA partition with DRM and this cannot be restored. You can brick your phone..
Flash stock with emma or with flash tool for xperia devices (or flash lineageos) then, flash magisk and try to setup hide root for samsung galaxy watch app. With luck, it may works, as it may hide unlocked state too.
@skkayman I found Magisk & Magisk manager in Aptoide. Just came in my mind if magisk etc could be used even with Sailfish OS to make my Galaxy Watch working. However Galaxy wearables app wont get bt contact at all, but what about Galaxy wearables app should be rooted? Should Sailfish bt be then available also for Galaxy Wearables app? If my Galaxy Watch worked, then it should be not important whether android or saifish os were in duty ...
N9Sailfish ( 2019-10-26 08:35:03 +0200 )editYes bluez5 is not compatible with Galaxy whatch bt. But if there were some "magic" somewhere .... Edit: Or maybe ... Xperia XA2 works and connects music via bluez5 to my radio bt (ADP2). Galaxy watch has bt 4.1 ADP2. Watch recognises XA2 SFOS , Thus, I do not know exactly what's the situation ...
N9Sailfish ( 2019-10-26 08:43:42 +0200 )editMagisk etc does not work in XA2 SFOS. Tried install. Saw also discussion of topic in March 2019 here in this site. No hope to get working in SFOS. Only way is to flash back ... Again.
N9Sailfish ( 2019-10-27 19:23:30 +0200 )editanswered 2019-10-25 09:36:25 +0200
As I know there is no way to relock XA2 bootloader.
Asked: 2019-10-24 20:02:41 +0200
Seen: 958 times
Last updated: Oct 25 '19
