• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Windows Phone Internals updated to version 2.4

Search This thread


Jan 17, 2009
The last build is 15254.158, came up a few days ago. You don't need this tool to do that.

---------- Post added at 04:12 PM ---------- Previous post was at 04:04 PM ----------

The problem is that, to port a rom it has to be the same resolution. You won't be able to port a nexus 5x rom to a 950 since they have different resolutions, unless the rom is aosp, afaik. LG G4 has the same resolution, so does BB PRIV and Moto X Pure Edition. So, those 3 are viable options.

I do not have the right knowledge to talk about porting so mine was only an idea ...

but I think that once you have found a base rom from these phones the "little :angel:"problem should only be drivers? right?
Last edited:


Inactive Recognized Developer
Dec 1, 2010
Not possible because bootloader not unlocked.

Then how did you get that message on your phone?

If you boot the phone to normal mode and connect it with USB to PC, and you browse the phone with Windows Explorer on the PC, you will see a file called "Non-Production Errors.txt". That file will tell you why it shows that message.


May 18, 2010
Initially, I got bitlocker errors because the phone was access protected. I used the recovery tool from Microsoft to fix that.

Now I get stuck on the cogs when the bootloader is flashed, and the phone reboots endlessly. Or it just shows the sad smiley and reboots after a while.

Logs: https://pastebin.ca/3957752

My second attempt is shown from timestamp 21:30 and up.
  • Like
Reactions: prokakavip


May 21, 2010
@Heathcliff74 With Lumia 950XL I can't unlock the bootloader, I get always this message "Failed to unlock the bootloader. It is not possible to unlock the bootloader traight after flashing. Fully reboot the phone and after that you can try again." I tried many times but nothing.

EDIT: ok maybe I found the problem, I've 15xxx version installed of OS and WPInternal downloaded the 10586 version. Now I'm flashing the phone with this version and I'll try again.
Last edited:


Oct 1, 2016
Use FFU for another model for unlock

I can't get W10M FFU file for Lumia 640 but I can download FFU for Lumia 650. Will WPI work this this FFU?

Curious Boy

Senior Member
May 21, 2015
my lumia 630 has only 8.1 ffu firmware which is not supported by UNLOCKV2. WPI tell me that I can use other model ffu file but not sure which model for safe. Can you please clarify this?


Senior Member
Aug 26, 2008
after bootloader unlocking attempt, a blue screen with a smiley face came up, then the phone went into its normal patching sequence that Heathcliff stated, when the phone was done flashing, it said it wasnt able to unlock the bootloader.


Jan 11, 2018
Cant unlock bootloader

Hello, I have a BIG problem, someone mentioned this too on XDA...I did everything good and I got an exception "." at the 6th flashing profil test...and the phone go to black screen and after 10 sec reboots to the flash mode with red backround, and after this I couldnt use the phone, reboot loop with that red flash mode if the usb not connected...if its connected then its shows with Lumia Bootmgr on the Device Manager. I fixed it by this tool on the Flash page....I just flashed the original FFU and its again fine. But the problem is, I cant unlock the bootloader, it stays the same...I have Lumia RM-1067 - 640 XL Dual - 059X1H4. I installed the correct drivers with WDRT after I disabled all others because I work with another phones too for Android...but I think I didnt messed up something with drivers because it happened to an other guy too. I used the latest original FFU, and EDE file + I loaded a different Win 10 FFU for thats exractions, I tried with 4 different version
RM1104_1078.0053.10586.13169.15218.034DB1_retail_prod_signed, RM1116_1078.0038.10586.13080.12732.03336D_retail_prod_signed,
RM1116_1078.0053.10586.13169.12732.034E13_retail_prod_signed, RM1154_1078.0042.10586.13333.15817.0352ED_retail_prod_signed, and still the same error. I think there is another problem whats not working properly with the program.

The program logs...from Programdata/WPinternals:

As you see the attemp 5 still worked, at the 6 the usb device lost, later connected in Emergency Mode and flashed something (the modified bootloader maybe?) but it failed, and the bootloader is unchanged. Some info in my language thats is translated.
2018-01-11 02:36:35.518: Custom flash attempt: 5 of 64
2018-01-11 02:36:36.531: Custom flash attempt failed
2018-01-11 02:36:36.531: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-11 02:36:36.531: Error 0x1003: Hash mismatch
2018-01-11 02:36:36.531: Rebooting phone
2018-01-11 02:36:36.592: Lumia disconnected
2018-01-11 02:36:41.829: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-11 02:36:41.829: Device path: \\?\USB#VID_0421&PID_0714#5&3b19be35&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-11 02:36:41.829: Connected device: Lumia
2018-01-11 02:36:41.829: Mode: Flash
2018-01-11 02:36:41.938: Custom flash attempt: 6 of 64
2018-01-11 02:36:42.876: Lumia disconnected
2018-01-11 02:36:42.899: Error on USB port!
2018-01-11 02:36:42.920: Device: Lumia BootMgr - Microsoft
2018-01-11 02:36:42.920: Last written: 4E4F4B58465300040000000100000021
2018-01-11 02:36:42.920: Error: Failed to read from pipe.
2018-01-11 02:36:42.920: Error: Failed to read pipe on WinUSB device.
2018-01-11 02:36:42.928: Error: Egy rendszerhez csatlakoztatott eszkz nem mkdik / The device does not working...
2018-01-11 02:36:42.953: Connection to phone is lost - 2 2 262144 0 0 0
2018-01-11 02:36:42.953: Expect phone to reboot
2018-01-11 02:36:42.953: Waiting for phone to connect...
2018-01-11 02:36:45.334: Found device on interface: 86e0d1e0-8089-11d0-9ce4-08003e301f73
2018-01-11 02:36:45.334: Device path: \\?\USB#VID_05C6&PID_9008#5&3b19be35&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2018-01-11 02:36:45.334: Connected device: Lumia
2018-01-11 02:36:45.334: Mode: Qualcomm Emergency Download 9008
2018-01-11 02:36:45.468: Sending programmer: C:\ProgramData\WPinternals\Repository\RM-1067\MPRG8x26_fh.ede
2018-01-11 02:36:45.515: Protocol: 0x00000002
2018-01-11 02:36:45.515: Supported: 0x00000001
2018-01-11 02:36:45.515: MaxLength: 0x00000400
2018-01-11 02:36:45.515: Mode: 0x00000000
2018-01-11 02:36:45.537: Programmer loaded into phone memory
2018-01-11 02:36:45.538: Starting programmer
2018-01-11 02:36:45.540: Programmer being launched on phone
2018-01-11 02:36:45.547: Wait to transfer control to programmer
2018-01-11 02:36:46.048: Send first hello to programmer
2018-01-11 02:36:46.647: First hello from PC accepted by programmer
2018-01-11 02:36:47.368: Error: A program . tpus kivtelt vltott ki. / The program generated . exception.
2018-01-11 02:36:47.369: A program „.” típusú kivételt váltott ki. /The program generated "." exception.
2018-01-11 02:37:15.263: Error: Az rs tllpte az idkorltot. /The rs exceded the time limit. Wat??
2018-01-11 02:37:57.492: Windows Phone Internals version 2.3.6584.1869
2018-01-11 02:37:57.494: Copyright Heathcliff74 / wpinternals.net
2018-01-11 02:37:57.791: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-11 02:37:57.791: Device path: \\?\usb#vid_0421&pid_0714#5&3b19be35&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-11 02:37:57.791: Connected device: Lumia
2018-01-11 02:37:57.791: Mode: Flash
2018-01-11 02:37:57.934: Security flags: 0x00007BFF
2018-01-11 02:37:57.959: Platform Name: Nokia.MSM8226.P6199.2.0
2018-01-11 02:37:57.988: Public ID: 9B A0 DC CA E4 90 53 13 C4 1F D6 A4 00 45 93 12 03 68 0B 9B
2018-01-11 02:37:58.008: Root Key Hash: 68 24 55 78 4C 6A 17 30 95 2B F7 8A 8E B4 1A 4F AA 98 B4 B4 82 8B A1 F7 4C 71 E2 1E 92 1C 39 60
2018-01-11 02:37:58.008: Platform Secure Boot Status: True
2018-01-11 02:37:58.009: Uefi Secure Boot Status: True
2018-01-11 02:37:58.010: Effective Secure Boot Status: True
2018-01-11 02:37:58.011: Bootloader Security Qfuse Status: True
2018-01-11 02:37:58.012: Bootloader Security Authentication Status: False
2018-01-11 02:37:58.012: Bootloader Security Rdc Status: False
2018-01-11 02:37:58.013: Effective Bootloader Security Status: True
2018-01-11 02:37:58.014: Native Debug Status: False
2018-01-11 02:37:58.335: Phone type: RM-1067
2018-01-11 02:37:58.335: Product code: 059X1H4

Thanks for your patient! Sorry for english mistakes if had.

Top Liked Posts

  • There are no posts matching your filters.
  • 75
    Hi all! Windows Phone Internals 2.4 is ready to download. It beats the modern SecureBoot implementation. And furthermore, it brings custom ROM's, Mass Storage Mode, Root access and many more hacks to all Windows Phone 8 and Windows 10 Mobile-based Lumia-models. There is also a new Download-section in the tool, where you can download everything you need for your phone.

    Short demo here:

    Version 2.3 is released:

    Version 2.4 is released (changelog in the link):

    René (Heathcliff74)
    What We do now? Microsoft kidnapped Heathcliff74

    Hahaha! No, I'm still alive and kicking. I released that intro video 2 weeks ago, because at that time i was sure i was able to release the tool within a few days. I still haven't released the tool yet, so I owe a little explanation.

    Two weeks ago I was just wrapping up some final pieces of code. But there was a problem with the implementation of the bootloader unlock. It had to do with updatability. When the bootloader was unlocked, the phone could not be updated anymore, which makes sense. But after relocking the phone, the phone still couldn't be updated anymore. That means, that when the phone was unlocked once, it could never be updated anymore, unless you would flash a stock ROM and start over. I realized the impact of this problem later on. Because many Lumia models only have WP 8.1 based stock ROM's and the update-process from WP 8.1 to the current W10M build is painfully long. Doing experiments this way would be agonizing. And this implementation would never be useful for people who want to use this on a phone which they still want to update regularly.

    So I was looking for a solution for this problem. It took me a while to get it right. I needed a new hack and many attempts to get it implemented correctly. But I have fixed it now. I still need to finalize some stuff, but it is almost ready. If I wouldn't have been able to fix this shortly, I would have released the tool without this, but that would really have been a big disappointment for me. Because you only make a first impression once.

    If I knew all this in advance, I would have waited to release that intro-video. I mean, I worked on this for two years already. And I've worked on this in silence all that time. Because I knew that when I would publish about my progress, I would also get questions about ETA's all the time. And I simply can't answer them. I need to focus on my work. I didn't release that video to tease a lot of people and then sneak out again on purpose. I'm just as anxious as others to release this tool. And now that I have this problem fixed, I guess I can release the tool soon. But you got to realize that it is important for me to test everything properly. It is important to get it right, or else phones get bricked. So, it is ready when it is ready. Sorry to test your patience. Hang in there just a bit longer.


    PS. I will try to answer all other questions when I release the tool. No time now.
    Hey Heathcliff74, Please is there a fix to turn off reset protection after what you software has caused to many Lumia phones? It be nice if you could build a program that does a cross scan between each device IMEI and upon Microsoft Reset protection status site that states on there site that is off which will force it off on a phone that should have been off? Or at least give us something were we can disable Reset Protection. The bypass solution is a pain even though that works. Though not idea to do for any owner of a Lumia especially for us Lumia 950/XL owners.

    Wow, wow, wow! Hold it right there! The tool is full of warnings. And when you started the tool for the first time, you agreed to the Disclaimer. This text is a part of the Disclaimer-text of the Windows Phone Internals tool:

    This software is a "proof of concept" tool which uses dangerous and largely untested techniques on Windows Phones ("Target Devices"). By using this tool the target device may start showing unstable behavior and crashes. There is significant and real potential that irreversible permanent damage will occur on some devices. As such this tool must only be used against target devices which it is acceptable for such damage to occur (for example retired devices used only for test purposes). This tool should not be used against target devices, which are intended as your primary means of telecommunications, because in some circumstances you may not be able to place calls (including calls for emergency services), or you may experience increased data charges. Use of this tool may void the warranty of any chosen target device.

    It is not my software who caused problems. You took the risk and used the software on your phone. So YOU caused the problem and YOU are responsible for the problem!

    That said, I investigated the issue. Reset Protection is only present on US phones. So I was not aware of how it could be triggered, because I am not from the US. To prevent the issue, I made changes to WPinternals 2.4. It will try to backup the Reset Protection Response Data and restore it when the bootloader is restored. So there should be no new cases of this problem when using version 2.4.

    There are a couple of ways to get around Reset Protection. Some people already succeeded by using a certain ROM version in combination with Interop Tools but that is indeed very cumbersome. I contact users all the time to help with various problems. Not because I feel obliged. Just because I want to help.

    Windows Phone Internals 2.3 is released!

    Version 2.3 is released:

    Will this work on any w10m build or we will have to downgrade to an specific version(i'm at 15254.12 in both 635 and 550)??

    WPI only works on supported OS versions. Version 15254.1 and 15254.12 are both supported.

    So HTC one m8 for windows is suporrted?

    HTC One M8, HP Elite X3 and Alcatel Idol 4S are not supported. It would take me a lot of time to research. I have to see which hacks are compatible. And where I would need to find new hacks. I don't think I will have time to do this, unfortunately.

    Will the new WP Internals work with my Lumia 730 now?
    It will support lumia 635??
    If this is the case, then for sure the 1520...I hope...
    Any chance this could work on the Lumia 435?

    WPI 2.2 still supports all old Lumia's. It is now also successfully tested on Lumia 1520, 435, 550, 630, 640, 650, 830, 930, 950 and 950 XL. So I think it is fair to say that it works on all Lumia's.

    First of all, thanks for the hard work you've put into this. Quick question: If you unlock the bootloader and gain root access, can you remove root access and re-lock the bootloader? (I'm assuming you can, but I'd like to verify). I like the fact W10M is a secure OS. I would only want to unlock the bootloader and gain root access on a temporary basis.

    Yes, this is possible. However, there are still some issues with updates after having relocked the phone. I'm working hard on a fix for that.

    With this tool, will it be theoretically possible to install Windows 10 on ARM on i.e 950xl, when it's released?

    In theory.. yes. But you would need to merge the drivers into the OS. Not an easy thing to do.