Softpedia >News >Microsoft >Windows Phone
Softpedia Homepage   

First Windows 10 Mobile Redstone Build Breaks Down Charging on Lumia 550

Watch out, as you might need to downgrade to 10586

Feb 21, 2016 08:45 GMT  ·  By
Lumia 550 is Microsoft's most affordable Windows 10 Mobile device
   Lumia 550 is Microsoft's most affordable Windows 10 Mobile device

Microsoft rolled out the first Windows 10 Mobile Redstone build a couple of days ago for new Lumia phones, including 950, 950 XL, and 550, but it appears that this last model is actually hit by a critical bug after the update.

Lumia 550 running Windows 10 Mobile build 14267 might not be able to charge anymore and in a statement released today, Microsoft confirmed that it’s indeed aware of a bug that’s particularly affecting this model.

Company engineers said that Lumia 550 owners whose devices are impacted by the bug should return to Windows 10 Mobile 10586.107 because for the moment, there’s no workaround available.

“Several Windows Insiders with a Lumia 550 have reported an issue where their phone no longer charges or connects via USB after upgrading to Build 14267. If you have a Lumia 550, we recommend holding off going to this build. If you have hit this issue we recommend rolling back to Build 10586 using the Windows Device Recovery Tool,” the Windows development team said.

Charge it in flashing mode before downgrading

In case you’ve already used your device a lot and it’s near the 0 percent battery limit, Redmond says that you need to recharge it before downgrading to .107.

“If your Lumia 550 is really low on battery, switch your phone into flashing mode by turning your phone off first and press power button and then volume up until you see a lightning bolt on your phone’s screen. This will allow your Lumia 550 to charge. You should let it charge a bit before using the Windows Device Recovery Tool to roll back to Build 10586.”

This new Windows 10 Mobile Redstone build is only available for devices that shipped with Windows 10 in the first place, and after hearing of this bug, it’s pretty clear that Microsoft made the right call here. Plenty of people criticized the company for not making it available for all Windows Phone devices participating in the Insider program, but it’s now more than obvious that bugs like this could wreak havoc on a wide array of phones unless Microsoft makes the right decision.