Category:Windows Mobile
Category:Windows Phone is the predecessor of this operating system. |
This page collects some useful resources for working with Windows Phones.
Tools
WindowsPhoneInternals[1]
WPInternals is an open-source tool by an XDA-User that allows you to perform tasks like unlocking bootloaders, enabling root access and flash or backup firmware. Some fixes have been made in the GitHub repository, but no new release has been made yet. The list of supported models on the official site is outdated. See the image on the right for a more up to date list. It runs natively on Windows.
Windows Device Recovery Tool[2]
The Windows Device Recovery Tool is a proprietary tool by Microsoft which lets you recover firmware of Windows devices. It runs natively on Windows.
Projects
Android4Lumia[3]
Android4Lumia is a project which aims to built android based custom roms for Lumia phones.
Mainline4Lumia[4]
Mainline4Lumia is a project which aims to bring Linux mainline to Lumia phones.
Mainline4Lumia Website including contact data
File Collections
LumiaFirmware.com[5]
On LumiaFirmware.com you can find firmware for Lumia Phones.
EDK-II
EDK-II has been ported to various Windows Phones. A porting guide is available here.
Guides
Unlocking bootloader
Download WPInternals and Windows Device Recovery Tool.
WPInternals is a tool designed to unlock the bootloader and/or secure boot of select Lumia devices made by Nokia and Microsoft.
Windows Device Recovery Tool is installed because it automatically installs all the drivers WPInternals will need.
Once you have installed both tools, Click on "Unlock Bootloader" and follow the instructions to unlock your phone's bootloader
Enabling Boot Menu
- Make sure your phone is in mass storage mode and that EFIESP is mounted.
- Find where EFIESP was mounted, Windows will either mount it in MainOS/EFIESP or with a letter (J:, L:, etc)
- Anything inside <> needs to be filled in by you, for example: <EFIESP> becomes K:\EFIESP if K: was MainOS and EFIESP was mounted at MainOS/EFIESP
- Open cmd as Administrator and run the following commands:
- Turn on displaybootmenu:
bcdedit /store <EFIESP>/efi/Microsoft/Boot/BCD /set {bootmgr} displaybootmenu on
- Set boot menu timeout to 10s:
bcdedit /store <EFIESP>/efi/Microsoft/Boot/BCD /set {bootmgr} timeout 10
- Set displayorder:
bcdedit /store <EFIESP>/efi/Microsoft/Boot/BCD /displayorder {default}
Extra steps for phones with a camera button:
- Devices with a camera button, you can make it so you can choose the boot option using volume keys and camera to select.
- Unfortunately there is no known way to make power button be select, so phones without a camera button can't use this.
bcdedit /store <EFIESP>/efi/Microsoft/Boot/BCD /deletevalue {bootmgr} customactions
bcdedit /store <EFIESP>/efi/Microsoft/Boot/BCD /deletevalue {bootmgr} custom:54000001
bcdedit /store <EFIESP>/efi/Microsoft/Boot/BCD /deletevalue {bootmgr} custom:54000002
Adding a new BCD entry
- Make sure your phone is in mass storage mode and that EFIESP is mounted.
- Find where EFIESP was mounted, Windows will either mount it in MainOS/EFIESP or with a letter (J:, L:, etc)
- Anything inside <> needs to be filled in by you, for example: <EFIESP> becomes K:\EFIESP if K: was MainOS and EFIESP was mounted at MainOS/EFIESP
- Open cmd as Administrator and run the following commands:
- Creating a new entry:
bcdedit /store .\BCD /create /d "<NAME>" /application BOOTAPP
- Copy the GUID (the squiggly brackets and the stuff inside)
- Set the efi path:
bcdedit /store .\BCD /set <GUID> path <EFIFILE>
- Set the partition the efi file is in:
bcdedit /store .\BCD /set <GUID> device partition=<EFIPART>
- Turn on test signing:
bcdedit /store .\BCD /set <GUID> testsigning on
- Turn off integrity checks:
bcdedit /store .\BCD /set <GUID> nointegritychecks on
Extra steps for phones with a camera button
- Add BCD entry to display order:
bcdedit /store .\BCD /displayorder <GUID> /addlast
Extra steps for phones without a camera button
- We need to set a volume key to boot our new BCD entry
- custom:54000001 is for volume up, custom:54000002 is for volume down
- Set the volkey to boot our bcd entry:
bcdedit /store BCD /set {bootmgr} <VOLKEY> <GUID>
Unbricking devices on EDL mode(QHSUSB_BULK)
This guide is for Spec B devices only. While this process, make sure WPInternals is not running in the background.
- Install the WDRT if you don't have it.
- Connect the device to the PC and check how it's detected from device manager. If device is detected as "QHSUSB_BULK" on "Universal Serial Bus Devices", then it's fine. If it's detected as "Qualcomm HS-USB QDloader 9008" on "Serial Devices", select update driver and install "Care Suite Emergency Connectivity" driver. Disconnect device and remove battery after updating driver.
- Open a CMD and
cd
into WDRT directory (C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
for 64bit,C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
for 32bit) - Go to lumiafirmware.com and download FFU file and emergency files (.ede and .edp) for your device.
- Type
thor2 -mode emergency -hexfile [path to .ede file] -edfile [path to .edp file]
to CMD and hit enter, wait for it flashes. When you getFFU_PARSING_ERROR
, that means it flashed emergency payload and you can continue. - When you get red flashing screen, type
thor2 -mode uefiflash -mode uefiflash -ffufile [path to .ffu file] -do_full_nvi_update -do_factory_reset
and wait for it to flash FFU.
Devices
On the different device pages is described how porting was done for the specific device. This can be used to get further information on how to port your device
See also
Pages in category "Windows Mobile"
The following 7 pages are in this category, out of 7 total.