Microsoft releases a factory image for the Surface Duo
Microsoft as an Android OEM is a thought that would’ve seemed ridiculous just a few years back, but yet, here we are. Microsoft has launched the Surface Duo: a device with a very unique dual-screen form factor, and it’s running Android. And Microsoft actually seems to be part of the developer-friendly OEM crowd: the device is fully bootloader unlockable, meaning that, if you want to, you can get custom ROMs up and running on your device, not to mention rooting and other mods. But what if you mess up your device while trying to mod it (it happens to the best of us) and it doesn’t boot anymore, who are you gonna call? Well, Microsoft. They’ve put up a factory image for the Surface Duo, actually, and it’s just as easy to download as it is for other Surface devices.
Surface Duo Unboxing – Hands-on with Microsoft’s Dual Screen Android Device
Microsoft also provides a handy support page laying down the steps for installing a factory image onto your Surface Duo. As for the factory image itself, it is provided together with Windows 10 recovery images for other Surface devices. Since the Surface Duo is actually an Android phone, however, Microsoft makes it clear that the procedure for flashing it will be different than that of its Windows-powered family members. For one, you don’t need a USB drive, and the download page links to the tutorial page I mentioned earlier. You will, however, need to sign in to your account and provide your serial number in order to download it.
Once you’re done with that, however, it’s pretty standard stuff: download the image, reboot your Surface Duo into recovery mode, and then use ADB to sideload it. Once that’s done and over, reboot your device.
If you want to grab a Surface Duo, you can rest assured that you will be able to mod your device without a hassle, so far at least.
Are you planning on getting a Surface Duo?
The post Microsoft releases a factory image for the Surface Duo appeared first on xda-developers.
from xda-developers https://ift.tt/3k2pDNX
via IFTTT
No comments: