Speedy Blupi for Windows Phone

Speedy Blupi for Windows Phone is remake of Speedy Blupi I and Speedy Blupi II developed for the Windows Phone platform and released in 2013. Game studio: Dada Games

It seems, that the development of Speedy Blupi for Windows Phone is discontinued.

Source code of Speedy Blupi for Windows Phone is not available.

Decompiling the XAP file of Speedy Blupi may be possible. Investigation is needed.

It seems, that Speedy Blupi for Windows Phone has almost no new features, if compared to Speedy Blupi I and Speedy Blupi 2.

The graphics is almost the same, maybe rerendered in the more detailed resolution. Riding the jeep or jetpack provides some new animations in the ase, Blupi/Eggbert is moving down or up

Download

https://files.openeggbert.com/download_games/speedy_blupi_for_windows_phone/speedblu.xap ^[1]

Screenshots

https://files.openeggbert.com/speedy_blupi/windows_phone/screenshots/blupi_windows_phone.png

How to run

Windows Phone is the discontinued mobile operating system developed by Microsoft for smartphones.

You can run Speedy Blupi on Windows Phone 8.1. of Windows Phone 10.0 (other versions were not yet tested)

Windows Phone - physical device

It is possible to run Speedy Blupi (2013) on a Windows Phone physical device even in 2024.

If you do not own a Windows Phone device just now and are going to buy one: make sure, that you are buying a device, where it is possible to unlock the bootloader and root it.

You need to have a Windows Phone - the physical device. Speedy Blupi was was successfully tested and running on the on Nokia Lumia 920, other devices were not yet tested)

The Windows Phone store is closed, installing XAP files directly on the device is not possible.

As the Windows Phone was shutdown, you need to unlock the bootloader and root it. Please, note, that you need some non-free tools to do it. Some of these tools has no source code available.
You probably need this tool: https://github.com/ReneLergner/WPinternals
- And some other tools - this documentation is not complete and must be improved.

It was successfully tested, that Speedy Blupi is running on Windows Phone Lumia 920. It probably runs also on many other devices, but it was not tested.

Warning: unlocking the bootloader and rooting the physical device have some risks. Make backup of files on the Windows Phone device, if needed.

To install a XAP file on the Windows Phone physical device, the following steps are needed:

Install Windows Phone Device Recovery
Install Windows Phone Internals (I have finally used a version released in 2015, the latest version did not work) https://github.com/ReneLergner/WPinternals
Install Windows Phone SDK 8.0 Lite and Windows Phone SDK 8.1 Lite https://archive.org/details/wp-8.1-sdk-tools-lite-setup-av-1.20_202201
Download files for your phone models (if exist). For Nokia Lumia: https://lumiafirmware.com/
Run Windows Phone Internals, unlock the bootloader, root the device using the downloaded files.
Then press the Windows logo key, type "Deploy" and start the Windows Phone 8.1 Deploy application and deploy the XAP file.

Windows Phone - emulator

It is definitely possible (successfully tested) to run Speedy Blupi for Windows Phone on Windows 10 Pro or Windows 11 Pro.

Unfortunately, the control is not good. Probably the best way is to enable and use the multi-touch feature of the emulator.

Requirements:

Windows 10 Pro or 11 Pro
4 GB RAM or more

Install:

Microsoft Emulator for Windows 10 Mobile Anniversary Update
Microsoft Emulator via Microsoft Store
Windows Phone SDK 8.0 Lite and Windows Phone SDK 8.1 Lite https://archive.org/details/wp-8.1-sdk-tools-lite-setup-av-1.20_202201

Actions:

Start Microsoft Emulator and run any of the 6 emulated devices
Run Windows Application Deployment 8.1 and deploy the file speedblu.xap
Now you can play Speedy Blupi for Windows Phone, but on Windows 10 or Windows 11.

Note: There is a Windows Phone emulator for Android, but its development is no more active and it only supports several XAP applications, installation Speedy Blupi on this emulator was not successful.