Windows Phone Internals - Copyright 2018 by Rene Lergner - wpinternals.

net -
@heathcliff74xda

Changes for version 2.8:

- NEW FEATURE:
Support for Windows Mobile 10.0.15254.547

Changes for version 2.7:

- NEW FEATURE:
Support for Windows Mobile 10.0.15254.538, 10.0.15254.541 and 10.0.15254.544

- FIX:
After unlocking the bootloader, the iris scanner would not work anymore on Lumia
950 and Lumia 950 XL. This is now fixed.
Thanks to @gus33000.

- FIX:
A phone with a non-supported OS-version may boot to a Blue Screen after unlocking
the bootloader. This is now fixed.
Thanks to @gus33000.

- FIX:
Some Silverlight apps would not work after unlocking the phone. This is now
fixed. Thanks to @gus33000.

Changes for version 2.6:

- NEW FEATURE:
Support for Windows Mobile 10.0.15254.530

Changes for version 2.5:

- NEW FEATURE:
New commandline functions for backing up and restoring the partition-table of the
phone: BackupGPT and RestoreGPT. The
backup-file is an XML-file containing all the information about the partitions.
If you want you can edit this file and
then restore it back to the phone. Obviously this is very risky and you should do
this with caution and at your own
risk!

- NEW FEATURE:
The archive of a Custom ROM can contain a file named "Partitions.xml". When this
file is present, it is parsed and
merged with the existing partition-table on the phone. You can get an example of
such XML-file by using the commandline
to create a backup of the partition-table of the phone. The Partitions.xml file
inside the archive does not need to be
complete. Only new partitions and modified partitions need to be present inside
the XML-file. For modified partitions,
you only need the name and the modified properties. Other elements can be
omitted. The information in the XML-file will
be merged into the existing partition-table. This behavior can be tested using
the commandline-function MergeGPT.

- NEW FEATURE:
Support for Windows Mobile 10.0.15254.490 and 10.0.15254.527, for both SecureBoot
unlock and Root Access.

- NEW FEATURE:
You can add an existing FFU-file to the repository on the download-page of
Windows Phone Internals.

- FIX:
On a small number of Lumia phones Windows Phone Internals was not able to find a
Flashing Profile. The parameters which
were checked have been extended in this version. This problem should be fixed now
for most phones.

- FIX:
Windows Phone Internals 2.4 could crash when launched on Windows 7. This is
fixed. In Windows Phone Internals 2.4 there
was a fix for detecting misbehaving Mass Storage drivers. This detection doesn't
work properly on Windows 7. When Windows
Phone Internals is launched on Windows 7 the detection for misbehaving Mass
Storage drivers is disabled. So Windows Phone
Internals doesn't crash anymore on Windows 7, but for most stable unlocking
behavior you should launch Windows Phone
Internals on Windows 8.1 or on Windows 10.

- FIX:
When a corrupt FFU-file was used for unlocking, Windows Phone Internals could
crash. FFU-files can get corrupted when the
download is aborted. Windows Phone Internals will now verify the headers and the
length of the FFU-file before the
unlock-process starts.

- FIX:
Under some circumstances a phone could get stuck in Flash-mode after a stock FFU
was flashed. This behavior is detected
and in this case the phone is first relocked before the stock FFU is flashed to
fix this problem.

- FIX:
Relocking a phone that was not unlocked, could leave the phone in flash-mode.

- FIX:
When a phone in Mass Storage mode has had a drive-letter assigned to partitions
other than MainOS, the next time these
drive-letters are also assigned. When a phone is unlocked, the extra drive-
letters could confuse the unlock-process.
Unlocking now checks the partition-names for correct behavior.

- FIX:
When unlocking a phone with Bootloader Spec A, which was already updated with new
firmware, Windows Phone Internals
could crash due to unexpected changes in the partition-layout. This is now
detected and handled properly.

- FIX:
Some driver versions for Qualcomm Emergency Download mode failed to report a
correct Bus Name. Because of this Windows
 Phone Internals was not able to detect the phone properly when it was switching
to Emergency Download Mode. This could
make Windows Phone Internals hang while trying to switch to Emergency Download
mode when the phone was being unlocked.
When the Bus Name in the driver is missing, Windows Phone Internals will make
some assumptions to unlock the phone
successfully.

- FIX:
On some engineering Lumia's the function to switch to Mass Storage Mode did not
work properly.

- FIX:
When there is no Profile FFU available, the button to restore the bootloader was
disabled without a warning. Under
these circumstances this new version will display a proper warning.

Changes for version 2.4:

- FIX:
Disabling Root Access could result in a BSOD on some phones.

- FIX:
Unlocking the bootloader on some Lumia 950's and 950 XL's could result in a BSOD
on the phone.
Windows Phone internals detected this and reverted the changes.
This version will prevent this situation and should unlock all Lumia 950's and
950 XL's correctly now.

- FIX:
Sometimes the driver for mass storage mode fails to start properly on PC.
This could stall the unlock process of Windows Phone Internals.
This version properly detects the failing driver, reverts the changes and informs
the user.
The user can retry to unlock the phone after the phone booted properly again.

- FIX:
The commannd-line interface of WPinternals.exe is working properly now.

- FIX:
The "Restore bootloader" function can now properly restore the original
bootloader,
when the unlock process was interrupted for some reason.

- FIX:
While scanning for a flashing profile, Windows Phone Internals could end up
interrupting the process due to an exception.
The exception is handled properly and the process should finish correctly now.

- FIX (experimental):
Reset Protection Protection
The Reset Protection Response Data is backed up when the bootloader is unlocked.
And it is restored when you restore the bootloader.

- FIX:
Regression bug: Restore Bootloader was not working properly anymore on Lumia x2x
devices.
- Many other improvements.

Known limitations:

- LIMITATION:
Due to the complexity of SecureBoot Hack v2, unlocking mounted ROM images is only
possible for Lumia's with Bootloader
Spec A. For Lumia's with bootloader Spec B you can create Custom ROM's with Root
Access using the "Build and capture"
technique, as described on the Getting started page.

- LIMITATION:
Occasionally the Mass Storage drivers on the PC can misbehave. In this case, the
phone will be in mass storage mode,
but the PC does not recognize it. This could affect the unlock process. Windows
Phone Internals now has a detection-method
for this behavior, but that only works on Windows 8.1 and Windows 10. So for the
most stable unlock-experience, you should
avoid Windows 7 or older.

- LIMITATION:
Lumia's with Bootloader Spec B can only flash partitions on a 0x100 sector-
boundary (or 0x20000 bytes-boundary). Your
partition-layout should comply to this rule. When Windows Phone Internals
calculates a new partition layout for a Custom
ROM, the layout will automatically comply to this rule.

- LIMITATION:
Some phones, namely the Lumia 535 models, may experience problems during the
unlock process. The first part of the unlock
succeeds, but when the phone is being switched to Mass Storage Mode, it is not
able to find a working Flashing Profile
anymore. This issue is under investigation.

- LIMITATION:
When you try to unlock or relock a phone with a non-supported OS version, then
you will need to provide a donor-FFU with
a supported OS-version. When unlocking or relocking the phone, modifications will
be made to the phone, which may also
cause the existing flashing-profile to become invalid. In this case Windown Phone
Internals may need to search for a new
flashing profile during any unlock- or relock-attempt.

- LIMITATION:
Windows Phone Internals supports only one single connected phone at a time. When
multiple phones are connected, Windows
Phone Internals can start showing unexpected and unstable behaviour.