It looks like the seller just turned it on to make sure it worked.

It was been on the original 10586.0 firmware.

There is not a mark on it.

Bargain for £40

it's downstream kernel 4.14.134, thx to _z3r0_0n3__ for creating this! He used Arch linux ARM, but i used PMOS modifyed kernel, more on github: https://github.com/nickdemon22/ztOS-a51

Meu Lumia 720 acabou de chegar, ele está na versão 8.1 do Windows phone eu gostaria de instalar a Live Store, mas não sei fazer o desbloqueio para permitir instalação de aplicativos fora da loja.

Alguém pode me ensinar o passo a passo do desbloqueio do Jailbreak?

With a similar post I made, wanted to see/restore old 520 phone. Yet that won't be possible to do with windows if the drivers are undetected to an extent (screen damage and potential fault from battery)

Then windows tools won't be an option for flashing firmware: to then apply/flash custom roms. Now i ask for what experienced tools or how to ensure i can flash fresh firmware.

https://github.com/bkerler/edl.git

https://github.com/bkerler/edl/issues/214

With these refferences, there are possible readback info to extracract and check the 'corrupt rom' issue i stated in my previous post.

https://www.reddit.com/r/LumiaLovers/comments/1x5uic5/a_very_longwinded_but_genuine_query_about/

Anyone have these files or comprehensive ways to use this tool to reflash stock rom b4 any custom rom procedures?

Previous post also asked if the linux commandline tool 'fwupdmgr' will be able to flash firmware of external devices via generic usb connections? Anyone familiar with or has found how to use either tools.

Unison 2.0:

Well, I did it. What was going to be 1.9 is Unison 2.0. It is on the GitHub repository, so the community can keep building on the same guidelines. This is not just a refactor. There is a lot of new stuff in the chat, and yes, some UI touch from me. Anyways, here it comes.

What's fixed

✅ Sending to groups works again. It used to freeze and unlink the device: the sender-key cache overflowed local settings and the next start looked like the phone had never been paired. That cache is its own file now.

✅ Status works. Opening one no longer sticks on a black screen at 0. The media keys survive sync, a failed download falls back to the thumbnail, and a video with no duration still moves on.

✅ Quoted replies in a private chat no longer stall the send. The app was naming the other person on the quote, the server dropped the frame, and the message sat there until it timed out.

✅ Muting a chat no longer deletes its pin. Pins and mutes survive a sync.

✅ A deleted message stays deleted, in your language, in the bubble and on the chat list.

✅ The personal chat keeps your profile name, instead of some random push name.

✅ A message left spinning by a crash is marked failed.

✅ The chat list on a small phone waits for the first sync, then shows the names it already knows.

✅ Connect finishes on Creators Update, and you can search the chat list.

Architecture Split into:

Unison.Uwp (UI / Dependency Injection)

Unison.Core (ViewModels and Contracts)

Unison.Socket (session)

Unison.Baileys (Protocol / Crypto)

Unison.Background (out-of-process socket task)

MVVM, with Dependency Injection. The screens talk to façades, not to the raw client.

Localized in English, Portuguese, Spanish, Dutch, Indonesian, Italian, Polish, German, Russian, and Ukrainian.

Current highlights

🎨 New icon. Isometric mark on the Start tile, the splash, and the boot screen. The live tile is that mark on a transparent background.
🎨 New Shell based on Windows Phone 8 Whatsapp called Whatsapp Legacy ( Go to settings to activate it)

🟦 Custom live tiles. A new message puts the contact and the preview on the tile, medium, wide, and large, plus the unread count. Pin a chat to Start from the info pane. Turn live tiles off in Settings if you want the tile quiet.

💬 Reply to a message. Text, photo, video, sticker, voice note, and document each get their own quote strip. Tap the conversation and the quote goes away.

👥 Groups send again, and @ picks a member or Everyone.

🟢 Status: list and viewer. Photos and videos open instead of a black frame stuck at zero.

📋 On the old WhatsApp look, long-press a bubble: Copy, Reply, and pin for 24 hours, 7 days, or 30 days. Tap outside and the bar closes.

📷 Camera inside the chat, a caption on a photo, and documents from the clip.

📱 Two looks: the Unison theme, and a Windows Phone 8 WhatsApp theme.

🔔 Toasts with the contact and the message. Acks and protocol noise stay out of the notification.

🖼️ Photos download when you open them: fullscreen, zoom, share, save.

🧭 Start, QR login, then Chats, Status, Settings, and Debug. Calls and Favorites open too. They are empty for now.

🔄 Re-pair from the Debug page. No reinstall.

✨ No more placeholder labels. The bubble says what the message actually is.

Known issues

⚠️ The private-chat reply fix still needs a real phone pass.

⚠️ Voice notes still need work on record and playback.

⚠️ Sending a video in a chat is not done yet. Opening a video you already received, and Status video, is.

⚠️ Calls and Favorites are just the empty page.

⚠️ If the app is killed, it does not quietly resume the socket in the background by itself.

Credits

u/MaskNinjaSquared

u/Mayconus

u/Negociation

Installation note: install the new APPX as an update. Uninstalling the app removes your linked WhatsApp session.

Download

WinArchive: a Microsoft Store replacement with software update, and a web store.

Metrostore: another Microsoft Store replacement. Apps are installed by hand.

GDrive (Unison / WinArchive / Metrostore):

drive.google.com/drive/folders/1nI6Xez…zj7dTbyL1XqV4X4iOMUoHcC?…

Introducing MetroSurf 2: Modern Browsing with WebKit.

A breakthrough in web compatibility. This is MetroSurf 2. After a long period of secret development, the next generation of MetroSurf is here: a remarkably powerful and capable web browser for Windows Phone. From a special GPU pipeline to JavaScript through JIT and custom optimisations for the Windows Phone platform which include new certificates and networking, MetroSurf 2.0 pushes past what was thought possible and opens a whole new world for Windows Phone. This is made possible by porting the WebKit engine (that powers many modern browsers) to Windows Phone.

The Best of MetroSurf Engineering

MetroSurf initially started as an application that patched Internet Explorer 11's WebView. Finding workarounds for Windows Phone's limitations provided valuable knowledge. And all of that experience became the foundation of MetroSurf 2.0. Additionally, Windows Phone devices were built with tight limits on memory, a handful of CPU cores, and a range of mobile GPU architectures. Studying these constraints helped build optimisations that enabled the modern web to work on Windows Phone 8.1.

Use Google Services Logged In

You can now use your Google Account on MetroSurf 2.0 to access various services (both Google's and third-party). This is possible because MetroSurf now passes Google reCAPTCHA and Cloudflare Turnstile. MetroSurf finally has control over POST requests, fixing a well known limitation of 1.0-1.4. Some services like Google Drive are more prone to crashing because of unimplemented JavaScript APIs from WebKit to Windows Phone.

Remarkable Rendering and Compositing

Simply put: it's magical to open a website on MetroSurf 2.0 and let it render modern content directly on Windows Phone 8.1 or Windows 10 Mobile. Even blur effects work, as a special GPU pipeline was built to facilitate texturing and compositing. Scrolling is done separately from JavaScript to ensure a smoother experience even if the website is still loading content.

A Breakthrough in Web Compatibility

MetroSurf 2.0 uses a different networking system with new certificates, which enables WebSockets and many websites to work. Videos go through Windows Phone's native Media Object extension, enabling YouTube to play 720p/60fps videos even on low-end devices. A lot of work went into letting videos play on Windows Phone 8.1 via the WebKit engine!

A Note from MetroSurf Development

It is incredible how many websites now run on Windows Phone 8.1. While testing this, I had plenty of fun simply browsing the web. Just hopping from one website to another is a magical experience. The possibilities that MetroSurf 2.0 enables are extraordinary. Instagram, Reddit, YouTube, and Spotify actually render and you can use them. It may not be fast every time because of the slow hardware, but the optimisations done definitely improve the overall usability. You can also download files with MetroSurf 2.0. Devices with 512 MB RAM may have some more issues as the engine was not properly optimised for them.

Open Source and Download Links

Part of MetroSurf 2's code is open source. See the official MetroSurf GitHub.
Download MetroSurf 2 on the official MetroSurf Discord.

So, what websites are you going to browse now?

the reason why I'm asking this is because I'm thinking of trying to daily drive it for a while and since my lumia 635 is locked to EE and my sim card is giffgaff how do I unlock it?

Title: Lumia 950 stuck in boot loop after failed Windows Phone Internals bootloader unlock (pipe error)

Hi everyone,

I have a Lumia 950 purchased from AliExpress, and I'm having trouble recovering it after a failed attempt to unlock the bootloader using Windows Phone Internals (WPinternals).

Here is what happened:

1. I connected my Lumia 950 to my PC and tried to unlock the bootloader using Windows Phone Internals.
2. The process failed with a pipe error. The error displayed something like 4lx4lx4l (I'm not sure if I copied that correctly).
3. After the failed attempt, I tried flashing the phone back to its original firmware using an FFU.
4. The flash attempt failed, and the phone stopped booting normally.
5. Now it gets stuck on the gears screen and repeatedly restarts, showing "Preparing automatic repair" before rebooting again.
6. At one point, I also saw the lightning bolt and gear icon.

Device details:

• Device: Microsoft Lumia 950
• RM model: RM-1118
• Purchased from: AliExpress
• Tool used: Windows Phone Internals
• Current issue: Stuck in a boot loop after a failed bootloader unlock and firmware recovery attempt.

I also tried a forced reset, but the gears do not appear to move. I'm worried that the firmware or boot configuration may be corrupted.

My questions:

• Is the phone recoverable using the correct FFU and Thor2, or another recovery method?
• Could this be a bootloader or partition issue caused by the failed WPinternals operation?
• How can I determine whether the phone is still in flash mode and recognized by Windows?
• Is there a safe way to recover it without making the situation worse?

I would appreciate any advice from people who have recovered a Lumia 950 from a similar situation. Thanks!

Buongiorno a tutti, ho un grosso problema con il mio Nokia Lumia 610 con Windows Phone 7.8 perché non é sbloccato e il tool per sbloccarlo ha chiuso i server tempo fa(perché poi vorrei installare delle app .xap)C’é qualcuno che può aiutarmi? Perché io colleziono vecchi telefoni e sarei molto grato a chi mi aiuta. Grazie a tutti.

I saw one on Ebay, excellent condition, and exactly the right one for my phone, BUT IT COSTS $100 FOR SHIPPING FROM AUSTRALIA LOL.

The battery itself? Around $18, but I feel weird paying an arm and a leg just for shipping.

Do you guys know any other alternatives? And please not Cellspare.

Thanks a lot!

Hello everyone!
I recently noticed something concerning about the Vianium project, which was developing modern applications and networking libraries for Windows Phone 8.1 and Windows 10 Mobile.
The official GitHub organization previously advertised 23 public repositories, including Vianigram, Vianium Browser, Vianium TLS, Vianium HTTP, and many other projects.
However, when I checked GitHub, only 3 public repositories remained visible. Many of the original repository links now return 404 errors.
Official GitHub: https://github.com/vianium
Project website: https://vianium.com/
This is particularly concerning because Vianium was working on technologies that could help keep Windows Phone usable on the modern internet, including TLS 1.3, HTTP/2, and a native Telegram client.
I haven’t found an official explanation for what happened.
Does anyone know:
Why did most of the Vianium repositories disappear? Were they deleted, made private, or moved somewhere else?
Has the developer made any announcement about the future of the project?
Does anyone have backups, forks, or Git clones of the missing repositories?
Are there any archived source code snapshots on GitHub, Internet Archive, or other services?
Is Vianium still being actively developed, and could the repositories become public again?
I really hope the source code hasn’t been permanently lost.
With Windows Phone already facing so many challenges, preserving projects like Vianium is incredibly important.
Of course, any preservation effort should respect the developer’s wishes and the original software licenses.
If anyone knows what happened or where the source code can still be found, please share the information.
Thank you! Let’s keep Windows Phone development alive!

sorry for my english, i dont speak english very well

Hi I love the windows phone and I want to put a metro launcher on a galaxy S7 active reminds me of the ATIV so I would like to put it on. Any launcher that works?

Hello everyone!
On October 7, 2026, LumiaFirmware.com officially shut down after more than a decade of providing firmware files for Nokia and Microsoft Lumia devices.
This is a major loss for the Windows Phone preservation community.
The website hosted approximately 5 TB of firmware files, including original FFU images, rare regional and carrier-specific firmware versions, and emergency recovery files.
I’m particularly concerned that some firmware files may have existed only on LumiaFirmware and might not be available anywhere else.
If no other copies exist, these files could eventually be lost forever, potentially making it much harder or even impossible to restore certain Lumia devices.
Other archives, such as LumiaDB, are still available, but it’s unclear whether they contain everything that LumiaFirmware hosted.
I believe we should act as soon as possible to find out what has already been preserved.
I have several questions:
Does anyone have a complete or partial backup of LumiaFirmware.com?
Were any large portions of its firmware collection archived before the shutdown?
Are there existing Internet Archive collections containing these files?
Could we compare LumiaFirmware’s former catalog with LumiaDB and other archives to identify missing firmware?
Is there an existing community preservation project that could help collect and safely archive missing files?
Could the original website eventually be restored, if its owner wishes to reopen it?
Even a complete list of filenames, product codes, firmware versions, and checksums would be incredibly valuable.
An important request regarding the website’s owner:
Please respect the owner’s decision and privacy. They maintained this valuable resource for more than a decade, and we should be grateful for their contribution.
Please do not repeatedly contact the owner, send mass messages, harass them, or pressure them into reopening the website or releasing the archive. Such actions would be unfair and could make the situation worse.
If the original LumiaFirmware ever returns, I sincerely hope it will happen voluntarily and with the support of the community.
To be clear, there is currently no confirmation that the original files have been deleted. However, I believe it’s important to investigate existing backups now rather than risk losing potentially irreplaceable firmware in the future.
If you have backups or know about existing preservation efforts, please share any useful information.
Let’s keep this discussion focused on preserving files, locating backups, and finding constructive solutions.
Thank you to everyone helping preserve Windows Phone history!

it says that "package could not be verified" am i doing smth wrong or?

i recently bought a lumia 1520 (rm940) and i have been trying to unlock its bootloader. however, the 3rd option doesn't appear for the ffu image withh supported os. Can someone please help me or give the required files? Because i cant find the ffu image with supported os on the internet, and wut doesn't give me the downloads.

Hi r/windowsphone! cmplog (Tеlеgram chаnnel) been porting Firefox's engine to Windows 10 Mobile, and it's now usable enough to share. It's called Gecko: a UWP browser built on Gecko from Firefox 155.0.1, running on our phones. Current version: 155.0.1.186.

Edge on W10M is stuck on EdgeHTML 15, and more and more sites simply don't work in it anymore. This is a modern engine, so most of them do again.

What works

• Modern Gecko engine with a JavaScript JIT, plus WebAssembly
• GPU rendering (WebRender over Direct3D 11) that redraws only what changed, so heavy sites like the YouTube home page load and scroll fast
• Hardware H.264 decoding up to 1080p60, including streaming (Media Source Extensions: YouTube, VK Video). The browser picks H.264 on its own when a site also offers VP9 or AV1
• Video goes straight to the display's hardware overlay when nothing is drawn on top of it, so fullscreen 1080p60 YouTube plays smoothly in portrait and landscape
• Frame rate synced to the display, fullscreen video with rotation
• Phone clipboard both ways, downloads (Downloads\Gecko or a folder of your choice, "Save as", file uploads)
• Hardware back button that does the expected thing: closes the keyboard, menus, dialogs, fullscreen, goes back in the tab, and only then leaves the app
• Microphone for WebRTC sites, with the system permission prompt
• Sign-in popups (Google, VK, etc.) open as a new tab and return to the site afterwards
• Tabs, pinch zoom, readable text on desktop-only pages (font inflation like Firefox for Android)
• Discord works after login (it's shown a desktop browser)
• Memory management built around the 2 GB address space of a 32-bit process
• Firefox telemetry is off

Low-end phones: a hacky GPU path for Direct3D feature level 9_3

Firefox's GPU renderer needs Direct3D 11 at feature level 10 or higher. Low-end phones like the Lumia 650 (Adreno 304) only go up to feature level 9_3, where it simply doesn't start. Normally that means falling back to rendering everything on the CPU, which on a Snapdragon 212 is painfully slow.

So there's a custom in-between path for these phones. Pages are drawn by Firefox's software renderer (SWGL), but the heavy part, shading the pixels, is moved to the GPU: the work goes through pixel shaders the 9_3 hardware can still run, rendered into tiles, and composited by Direct3D 11. Shaders the driver might refuse are probed during idle time, so a refusal doesn't surface in the middle of a frame. Hardware H.264 decoding works at 9_3 too.

This solution helps a lot compared to pure CPU rendering, but a Lumia 650 is still much slower than an Elite x3. The fast paths (direct GPU rendering, the video overlay) need feature level 10+.

1 GB phones: a page file can help

On phones with 1 GB of RAM the system unloads apps that use too much memory, and a browser on YouTube easily takes 400–600 MB. If the browser keeps getting closed on you, enabling a page file gives the system somewhere to put memory and makes that happen less often.

Windows 10 Mobile has no setting for it, but on an interop-unlocked phone it can be turned on in the registry (e.g. with Interop Tools):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

PagingFiles = "u:\pagefile 1024 1024"

(minimum and maximum size in MB), then reboot. This is a system tweak at your own risk; it costs internal storage space and adds wear to the flash.

What doesn't (yet)

• No DRM video (Netflix and the like): there are no DRM plugins for this platform
• VP9/AV1 are software-only, so sites without H.264 won't play well above 360p
• Camera in WebRTC hasn't been tested yet (only the microphone has), so no video calls for now
• No printing, no Web Speech
• No auto-update: new versions are installed as a new package over the old one (your data is kept)
• Everything runs in a single process with no sandbox: UWP on the phone doesn't allow child processes
• Extensions run on the same thread as pages, so uBlock Origin noticeably slows things down even when switched off from its own menu. Disable it in about:addons if you notice
• Very heavy sites like Discord can bump into the address-space limit and stutter

Devices

• HP Elite x3: tested, works well
• Lumia 650: tested, runs on the feature level 9_3 path above, but noticeably slow
• Lumia 950 / 950 XL, Alcatel Idol 4S, Acer Jade Primo and other Snapdragon 808/810/820 phones with 3 GB RAM: should work reasonably well

Requirements

• Windows 10 Mobile 1703 (15063) or newer, ARM
• Interop unlock (the package declares restricted capabilities: code generation for the JIT and broad file-system access for the profile)
• The Gecko.cer certificate from the release installed on the phone
• At least 1 GB RAM. On YouTube the browser uses 400–600 MB, so on 1 GB phones it will be slow (see the page file note above)

Download & source

• Download: https://github.com/Computershik73/gecko-w10m/releases/latest
• Source: https://github.com/Computershik73/gecko-w10m

This is still a beta, so expect rough edges. Bug reports are very welcome. If something crashes, the browser keeps logs (quiet by default, verbose mode can be switched on in its settings), and they help a lot.

Hi r/windowsphone! cmplog (Telegram channel) has been porting Firefox's engine to Windows 10 Mobile, and it's now usable enough to share. It's called Gecko: a UWP browser built on Gecko from Firefox 155.0.1, running on our phones. Current version: 155.0.1.186.

Edge on W10M is stuck on EdgeHTML 15, and more and more sites simply don't work in it anymore. This is a modern engine, so most of them do again.

What works

• Modern Gecko engine with a JavaScript JIT, plus WebAssembly
• GPU rendering (WebRender over Direct3D 11) that redraws only what changed, so heavy sites like the YouTube home page load and scroll fast
• Hardware H.264 decoding up to 1080p60, including streaming (Media Source Extensions: YouTube, VK Video). The browser picks H.264 on its own when a site also offers VP9 or AV1
• Video goes straight to the display's hardware overlay when nothing is drawn on top of it, so fullscreen 1080p60 YouTube plays smoothly in portrait and landscape
• Frame rate synced to the display, fullscreen video with rotation
• Phone clipboard both ways, downloads (Downloads\Gecko or a folder of your choice, "Save as", file uploads)
• Hardware back button that does the expected thing: closes the keyboard, menus, dialogs, fullscreen, goes back in the tab, and only then leaves the app
• Microphone for WebRTC sites, with the system permission prompt
• Sign-in popups (Google, VK, etc.) open as a new tab and return to the site afterwards
• Tabs, pinch zoom, readable text on desktop-only pages (font inflation like Firefox for Android)
• Discord works after login (it's shown a desktop browser)
• Memory management built around the 2 GB address space of a 32-bit process
• Firefox telemetry is off

Low-end phones: a hacky GPU path for Direct3D feature level 9_3

Firefox's GPU renderer needs Direct3D 11 at feature level 10 or higher. Low-end phones like the Lumia 650 (Adreno 304) only go up to feature level 9_3, where it simply doesn't start. Normally that means falling back to rendering everything on the CPU, which on a Snapdragon 212 is painfully slow.

So there's a custom in-between path for these phones. Pages are drawn by Firefox's software renderer (SWGL), but the heavy part, shading the pixels, is moved to the GPU: the work goes through pixel shaders the 9_3 hardware can still run, rendered into tiles, and composited by Direct3D 11. Shaders the driver might refuse are probed during idle time, so a refusal doesn't surface in the middle of a frame. Hardware H.264 decoding works at 9_3 too.

This solution helps a lot compared to pure CPU rendering, but a Lumia 650 is still much slower than an Elite x3. The fast paths (direct GPU rendering, the video overlay) need feature level 10+.

1 GB phones: a page file can help

On phones with 1 GB of RAM the system unloads apps that use too much memory, and a browser on YouTube easily takes 400–600 MB. If the browser keeps getting closed on you, enabling a page file gives the system somewhere to put memory and makes that happen less often.

Windows 10 Mobile has no setting for it, but on an interop-unlocked phone it can be turned on in the registry (e.g. with Interop Tools):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

PagingFiles = "u:\pagefile 1024 1024"

(minimum and maximum size in MB), then reboot. This is a system tweak at your own risk; it costs internal storage space and adds wear to the flash.

What doesn't (yet)

• No DRM video (Netflix and the like): there are no DRM plugins for this platform
• VP9/AV1 are software-only, so sites without H.264 won't play well above 360p
• Camera in WebRTC hasn't been tested yet (only the microphone has), so no video calls for now
• No printing, no Web Speech
• No auto-update: new versions are installed as a new package over the old one (your data is kept)
• Everything runs in a single process with no sandbox: UWP on the phone doesn't allow child processes
• Extensions run on the same thread as pages, so uBlock Origin noticeably slows things down even when switched off from its own menu. Disable it in about:addons if you notice
• Very heavy sites like Discord can bump into the address-space limit and stutter

Devices

• HP Elite x3: tested, works well
• Lumia 650: tested, runs on the feature level 9_3 path above, but noticeably slow
• Lumia 950 / 950 XL, Alcatel Idol 4S, Acer Jade Primo and other Snapdragon 808/810/820 phones with 3 GB RAM: should work reasonably well

Requirements

• Windows 10 Mobile 1703 (15063) or newer, ARM
• Interop unlock (the package declares restricted capabilities: code generation for the JIT and broad file-system access for the profile)
• The Gecko.cer certificate from the release installed on the phone
• At least 1 GB RAM. On YouTube the browser uses 400–600 MB, so on 1 GB phones it will be slow (see the page file note above)

Download & source

• Download: https://github.com/Computershik73/gecko-w10m/releases/latest
• Source: https://github.com/Computershik73/gecko-w10m

This is still a beta, so expect rough edges. Bug reports are very welcome. If something crashes, the browser keeps logs (quiet by default, verbose mode can be switched on in its settings), and they help a lot.

Hey all, I've been working on ztOS, a phone OS with a custom shell called ztMETRO. It recreates the look and motion of Windows Phone 8.1on Arch Linux ARM with mainline Linux 7.1.

The shell itself is written in C and opengl for acceleration, and there is a separate SDK to build application for this using python.

What works on the S9 (starlte):

• Boots from internal storage, 60 fps shell with the Panfrost GPU
• Touch, Wi-Fi, 4G data, SIM, speaker, light sensor, haptics
• Start, tiles, app switcher, action centre and lock screen
• Updater and an SDK for apps in Python/Qt

What doesn't yet:
Calls connect but you can't hear anything
No camera, Bluetooth, GPS or mic

It's very much alpha. The installer has been tested on bare-metal hardware, but there are some bugs so read the known quirks before flashing. Feedback, issues and testers welcome!

Repository

discord