echo(
echo Searching for a compatible device...

:: Ensure that we are flashing right device
:: :: H9436
:: H9436

@call :devices

if not "%serialnumbers%" == "" GOTO no_error_serialnumbers

:: If fastboot devices does not list any devices, then we cannot flash.
echo(
echo We did not find any devices with fastboot.
echo(
echo The device is not properly connected to your computer or
echo you might be missing the required windows fastboot drivers for your device.
echo(
echo Go to the Windows Device Manager and verify that the fastboot driver for the
echo device is properly installed.
echo(
pause
exit /b 1

:no_error_serialnumbers

for %%d in ( %serialnumbers% ) do (
set fastbootcmd=%fastbootcmd_no_device% -s %%d
@call :getvar product
findstr /R ":: H9436
:: H9436" %tmpflashfile% >NUL 2>NUL
if not errorlevel 1 (
call :new_product_found %%d
)
)

if not [%products%] == [] goto :no_error_product

echo(
echo The DEVICE this flashing script is meant for WAS NOT FOUND!
echo(
echo This script found following device:
type %tmpflashfile%
pause
exit /b 1

:no_error_product

if "%products%" == "%products: =%" GOTO :no_multiple_products

echo(
echo It seems that there are multiple compatible devices connected in fastboot mode.
echo Make sure only the device that you intend to flash is connected.
pause
exit /b 1


:no_multiple_products

:: Now we know which device we need to flash
set fastbootcmd=%fastbootcmd_no_device% -s %products%

:: Check that device has been unlocked
@call :getvar secure
findstr /R /C:"secure: no" %tmpflashfile% >NUL 2>NUL
if not errorlevel 1 GOTO no_error_unlock
echo(
echo This device has not been unlocked for the flashing. Please follow the
echo instructions how to unlock your device at the following webpage:
echo %unlockwebsite%
echo(
echo Press enter to open browser with the webpage.
echo(
pause
start "" %unlockwebsite%
exit /b 1

:no_error_unlock

echo(
echo The device is unlocked for the flashing process. Continuing..

Originally Posted by rinigus

I cannot comment much on Windows flash script - never used it. Even don't know whether anyone else has used Windows to flash using that script. The script is taken from SFOS repos and I can only hope it works.

You can probably run through executed commands and see where it fails specifically. In the end, it should be calling fastboot. For searching, it should try to find device using fastboot output, if I remember Linux script correctly. Probably something similar is done in Windows.

But I let users with better Windows experience to guide you through.

Originally Posted by JoOppen

I once successfully flashed another XZ3 with your SFOS 3 port using Jolla's batch script, Sony's fastboot and the sa0119adb driver. So in general all should be fine ...

Apparently some detail escapes me this time. I'll keep trying - thank you for the support - and of course the port!

Originally Posted by JoOppen

I once successfully flashed another XZ3 with your SFOS 3 port using Jolla's batch script, Sony's fastboot and the sa0119adb driver. So in general all should be fine ...

Apparently some detail escapes me this time. I'll keep trying - thank you for the support - and of course the port!

Originally Posted by Korkkiruuvi

Have you found solution? I'm unable to flash newest sailfish with flash-on windows bat. commandline disappears after few seconds. I also tried previous sailfish release with same result.

I also used newflasher to revert everything normal and try again. I also wonder is it recuired to flash both separate downloads from xperifirm as it suggest two separate downloads "52.1.A.3.137" "190510.001-10073" both few gigabytes large.

As I see someone has confirmed it should work (github).

Could it related to that I tried aosp11 port & twrp-recovey from xda-developers and messing those files somehow.

Can't use linux to test flash for now.

Is it correct to keep standalone android platform-tools actual files same place where lies sailfish flashing files? I could not get fastboot work any other ways.

Originally Posted by Korkkiruuvi

Afterall decided try linux and worked flawlessly. However next issues are graphic artifacts; everytime swipe to home both sides causes artifacts, also random actions does very commonly. Does it same that already reported in github? Might be however it could be reduced by underclocking gpu or something similar.

Any instructions for that?

Originally Posted by levone1

Yes, you would need to do that. Alao, with the state of the port currently being aarch64-base, your only option would be Xperia 10 II, (and then buy a license). I'm considering buying one just for that reason. I already have an XA2 that I bought for that, but no good anymore since port base changed...

Originally Posted by KeTbl4

Hello sailors . I like xz2c and SFOS . I bought a 10 mark II ($200) and a Jolla license (sfos x - another $50) . I transferred files from 10 mkII (ofono-alien-binder-plugin , libalienaudioservice ,apkd8-android-settings ,apk d8, alienkeyboardservice, aliendalvik-system, aliendalvik-configs, aliendalvik, alienaudioservice-plugin-sailfish, alienaudioservice, apkd8-l10n-all- translations) necessary for android to work on XZ2c and support appeared on xz2c. I would also like to migrate Predictive text input (required) and MS Exchange support (as appropriate) but I don 't know how to do it . Tell me tell me is it possible to transfer these functions ? If possible , which files should be transferred ?