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

Windows Phone Internals updated to version 2.4

Search This thread

eKoKnight

Senior Member
Feb 2, 2014
59
1
you knew the risk of using the tool

---------- Post added at 02:40 PM ---------- Previous post was at 02:32 PM ----------






working on trying to find a way

Ya though it be nice if there was a warning on the program about devices with reset protection which there was not on the notes. Now if only a dev can make a program to cross exam the imei number from micrososft reset protection to shut it off on the device since the website indicates reset protection is off when really it is not. I wonder though on that note if I am ever able to unlock the bootloader if there be a way with root access to turn off reset protection within root access... Any thought in regards of that? Or is Reset Protection hardware that can not be overwritten on the Lumia 950? Or is it just the OS of Windows Mobile 10 or firmware?

---------- Post added at 02:26 AM ---------- Previous post was at 02:24 AM ----------

Ya though it be nice if there was a warning on the program about devices with reset protection which there was not on the notes. Now if only a dev can make a program to cross exam the imei number from micrososft reset protection to shut it off on the device since the website indicates reset protection is off when really it is not. I wonder though on that note if I am ever able to unlock the bootloader if there be a way with root access to turn off reset protection within root access... Any thought in regards of that? Or is Reset Protection hardware that can not be overwritten on the Lumia 950? Or is it just the OS of Windows Mobile 10 or firmware?

P.S. Im not overly upset at least I found a way to bypass Reset Protection on my phone. Though its annoying if it ever comes to having to hard reset my phone to then have to go through the process to bypass once again.

---------- Post added at 02:33 AM ---------- Previous post was at 02:26 AM ----------

Ya though it be nice if there was a warning on the program about devices with reset protection which there was not on the notes. Now if only a dev can make a program to cross exam the imei number from micrososft reset protection to shut it off on the device since the website indicates reset protection is off when really it is not. I wonder though on that note if I am ever able to unlock the bootloader if there be a way with root access to turn off reset protection within root access... Any thought in regards of that? Or is Reset Protection hardware that can not be overwritten on the Lumia 950? Or is it just the OS of Windows Mobile 10 or firmware?
 

c:/Lumia

Member
Jan 25, 2018
16
1
Ya though it be nice if there was a warning on the program about devices with reset protection which there was not on the notes. Now if only a dev can make a program to cross exam the imei number from micrososft reset protection to shut it off on the device since the website indicates reset protection is off when really it is not. I wonder though on that note if I am ever able to unlock the bootloader if there be a way with root access to turn off reset protection within root access... Any thought in regards of that? Or is Reset Protection hardware that can not be overwritten on the Lumia 950? Or is it just the OS of Windows Mobile 10 or firmware?

---------- Post added at 02:26 AM ---------- Previous post was at 02:24 AM ----------

Ya though it be nice if there was a warning on the program about devices with reset protection which there was not on the notes. Now if only a dev can make a program to cross exam the imei number from micrososft reset protection to shut it off on the device since the website indicates reset protection is off when really it is not. I wonder though on that note if I am ever able to unlock the bootloader if there be a way with root access to turn off reset protection within root access... Any thought in regards of that? Or is Reset Protection hardware that can not be overwritten on the Lumia 950? Or is it just the OS of Windows Mobile 10 or firmware?

P.S. Im not overly upset at least I found a way to bypass Reset Protection on my phone. Though its annoying if it ever comes to having to hard reset my phone to then have to go through the process to bypass once again.

---------- Post added at 02:33 AM ---------- Previous post was at 02:26 AM ----------

Ya though it be nice if there was a warning on the program about devices with reset protection which there was not on the notes. Now if only a dev can make a program to cross exam the imei number from micrososft reset protection to shut it off on the device since the website indicates reset protection is off when really it is not. I wonder though on that note if I am ever able to unlock the bootloader if there be a way with root access to turn off reset protection within root access... Any thought in regards of that? Or is Reset Protection hardware that can not be overwritten on the Lumia 950? Or is it just the OS of Windows Mobile 10 or firmware?

reset protection i think is hardware
 

Attez

Member
Jan 30, 2018
11
0
WPI crashes

I got exception "." during bootloader unlock on Windows Phone 8.1. Device is Lumia 640 LTE. My phone didn't booted anymore (was stuck in flash mode), but I fixed it with WDRT. Then I upgraded to Windows 10 Mobile and tried to unlock bootloader again but now I didn't got exception "." anymore but WPI crashed immediately when tried to unlock bootloader. Phone didn't booted up again (was stuck in flash mode), but I fixed it with WDRT. On Windows 10 Mobile WPI log file just says:
Error: Bad FFU file:

But in Windows Phone 8.1 there is more content. Here is a part of WPI log file on Windows phone 8.1:

2018-01-28 17.17.35.260: Unlock Bootloader
2018-01-28 17.17.35.260: Processing resources:
2018-01-28 17.17.35.260: Profile FFU: C:\ProgramData\WPinternals\Repository\RM-1072\RM1072_02177.00000.15184.36002_RETAIL_prod_signed_1002_027096_000-33_MV.ffu
2018-01-28 17.17.35.260: EDE file: C:\ProgramData\WPInternals\Repository\RM-1072\MPRG8x26_fh.ede
2018-01-28 17.17.35.260: FFU with supported OS version: C:\ProgramData\WPinternals\Repository\RM-1085\RM1085_1078.0053.10586.13169.12547.035242_retail_prod_signed.ffu
2018-01-28 17.17.35.551: Assembling data for unlock
2018-01-28 17.17.35.551: Assembling data for unlock
2018-01-28 17.17.35.568: Supported FFU: C:\ProgramData\WPinternals\Repository\RM-1085\RM1085_1078.0053.10586.13169.12547.035242_retail_prod_signed.ffu
2018-01-28 17.17.35.587: Taking mobilestartup.efi from supported FFU
2018-01-28 17.17.35.603: Attempt patch: SecureBootHack-V2-EFIESP
2018-01-28 17.17.35.613: Pattern: 0, 0
2018-01-28 17.17.35.613: Pattern: 1, 0
2018-01-28 17.17.35.613: Pattern: 2, 0
2018-01-28 17.17.35.613: Pattern: 3, 0
2018-01-28 17.17.35.613: Pattern: 4, 0
2018-01-28 17.17.35.613: Apply: 10.0.10586.318
2018-01-28 17.17.35.617: Edit BCD
2018-01-28 17.17.36.063: Initializing flash...
2018-01-28 17.17.36.064: Rebooting phone
2018-01-28 17.17.36.139: Lumia disconnected
2018-01-28 17.17.40.679: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.17.40.679: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.17.40.679: Connected device: Lumia
2018-01-28 17.17.40.679: Mode: Bootloader
2018-01-28 17.17.40.767: No flashing profile found
2018-01-28 17.17.40.767: Custom flash attempt: 1 of 64
2018-01-28 17.17.40.767: Scanning for flashing-profile - attempt 1 of 64
2018-01-28 17.17.41.378: Custom flash attempt failed
2018-01-28 17.17.41.386: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-28 17.17.41.386: Error 0x1003: Hash mismatch
2018-01-28 17.17.41.387: Rebooting phone
2018-01-28 17.17.41.449: Lumia disconnected
2018-01-28 17.17.47.378: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.17.47.378: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.17.47.378: Connected device: Lumia
2018-01-28 17.17.47.378: Mode: Flash
2018-01-28 17.17.47.485: Custom flash attempt: 2 of 64
2018-01-28 17.17.48.094: Custom flash attempt failed
2018-01-28 17.17.48.094: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-28 17.17.48.094: Error 0x1003: Hash mismatch
2018-01-28 17.17.48.094: Rebooting phone
2018-01-28 17.17.48.162: Lumia disconnected
2018-01-28 17.17.54.089: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.17.54.089: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.17.54.089: Connected device: Lumia
2018-01-28 17.17.54.089: Mode: Flash
2018-01-28 17.17.54.209: Custom flash attempt: 3 of 64
2018-01-28 17.17.54.934: Custom flash attempt failed
2018-01-28 17.17.54.934: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-28 17.17.54.934: Error 0x1003: Hash mismatch
2018-01-28 17.17.54.934: Rebooting phone
2018-01-28 17.17.54.985: Lumia disconnected
2018-01-28 17.18.01.094: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.18.01.094: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.18.01.094: Connected device: Lumia
2018-01-28 17.18.01.094: Mode: Flash
2018-01-28 17.18.01.198: Custom flash attempt: 4 of 64
2018-01-28 17.18.01.811: Custom flash attempt failed
2018-01-28 17.18.01.811: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-28 17.18.01.811: Error 0x1003: Hash mismatch
2018-01-28 17.18.01.811: Rebooting phone
2018-01-28 17.18.01.864: Lumia disconnected
2018-01-28 17.18.07.844: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.18.07.844: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.18.07.844: Connected device: Lumia
2018-01-28 17.18.07.844: Mode: Flash
2018-01-28 17.18.07.950: Custom flash attempt: 5 of 64
2018-01-28 17.18.08.751: Custom flash attempt failed
2018-01-28 17.18.08.751: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-28 17.18.08.751: Error 0x1003: Hash mismatch
2018-01-28 17.18.08.751: Rebooting phone
2018-01-28 17.18.08.818: Lumia disconnected
2018-01-28 17.18.14.371: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.18.14.371: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.18.14.371: Connected device: Lumia
2018-01-28 17.18.14.371: Mode: Flash
2018-01-28 17.18.14.483: Custom flash attempt: 6 of 64
2018-01-28 17.18.15.078: Error on USB port!
2018-01-28 17.18.15.101: Lumia disconnected
2018-01-28 17.18.15.118: Device: Lumia BootMgr - Microsoft
2018-01-28 17.18.15.118: Last written: 4E4F4B58465300040000000100000021
2018-01-28 17.18.15.118: Error: Failed to read from pipe.
2018-01-28 17.18.15.118: Error: Failed to read pipe on WinUSB device.
2018-01-28 17.18.15.118: Error: Jrjestelmn liitetty laite ei toimi
2018-01-28 17.18.15.118: Connection to phone is lost - 2 2 262144 0 0 0
2018-01-28 17.18.15.118: Expect phone to reboot
2018-01-28 17.18.15.118: Waiting for phone to connect...
2018-01-28 17.18.15.604: Found device on interface: 71de994d-8b7c-43db-a27e-2ae7cd579a0c
2018-01-28 17.18.15.604: Device path: \\?\USB#VID_05C6&PID_9008#5&521a615&0&1#{71de994d-8b7c-43db-a27e-2ae7cd579a0c}
2018-01-28 17.18.15.604: Connected device: Lumia
2018-01-28 17.18.15.604: Mode: Qualcomm Emergency Download 9008
2018-01-28 17.18.15.613: Sending programmer: C:\ProgramData\WPInternals\Repository\RM-1072\MPRG8x26_fh.ede
2018-01-28 17.18.15.614: Protocol: 0x00000002
2018-01-28 17.18.15.614: Supported: 0x00000001
2018-01-28 17.18.15.614: MaxLength: 0x00000400
2018-01-28 17.18.15.614: Mode: 0x00000000
2018-01-28 17.18.15.632: Programmer loaded into phone memory
2018-01-28 17.18.15.632: Starting programmer
2018-01-28 17.18.15.633: Programmer being launched on phone
2018-01-28 17.18.15.635: Wait to transfer control to programmer
2018-01-28 17.18.16.136: Send first hello to programmer
2018-01-28 17.18.16.638: Error on USB port!
2018-01-28 17.18.16.638: Device: \\?\USB#VID_05C6&PID_9008#5&521a615&0&1#{71de994d-8b7c-43db-a27e-2ae7cd579a0c}
2018-01-28 17.18.16.638: Last written: 30375057000000000000000000000000
2018-01-28 17.18.16.638: Error: Failed to write to pipe: 30375057000000000000000000000000
2018-01-28 17.18.16.638: Error: Failed to write pipe on WinUSB device.
2018-01-28 17.18.16.641: Error: Semaforin aikakatkaisun mraika on lopussa
2018-01-28 17.18.18.141: Error on USB port!
2018-01-28 17.18.18.141: Device: \\?\USB#VID_05C6&PID_9008#5&521a615&0&1#{71de994d-8b7c-43db-a27e-2ae7cd579a0c}
2018-01-28 17.18.18.141: Last written: 30375057000000000000000000000000
2018-01-28 17.18.18.141: Error: Failed to read from pipe.
2018-01-28 17.18.18.141: Error: Failed to read pipe on WinUSB device.
2018-01-28 17.18.18.141: Error: Semaforin aikakatkaisun mraika on lopussa
2018-01-28 17.18.18.145: Did not receive hello from programmer
2018-01-28 17.18.47.155: Lumia disconnected
2018-01-28 17.18.52.397: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.18.52.397: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.18.52.397: Connected device: Lumia
2018-01-28 17.18.52.397: Mode: Flash
2018-01-28 17.18.52.498: Custom flash attempt: 7 of 64
2018-01-28 17.18.53.120: Custom flash attempt failed
2018-01-28 17.18.53.120: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-28 17.18.53.120: Error 0x1003: Hash mismatch
2018-01-28 17.18.53.120: Rebooting phone
2018-01-28 17.18.53.187: Lumia disconnected
2018-01-28 17.18.58.739: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.18.58.739: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.18.58.739: Connected device: Lumia
2018-01-28 17.18.58.739: Mode: Flash
2018-01-28 17.18.58.848: Custom flash attempt: 8 of 64
2018-01-28 17.18.59.492: Custom flash attempt failed
2018-01-28 17.18.59.493: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-28 17.18.59.493: Error 0x1003: Hash mismatch
2018-01-28 17.18.59.493: Rebooting phone
2018-01-28 17.18.59.557: Lumia disconnected
2018-01-28 17.19.05.106: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-01-28 17.19.05.106: Device path: \\?\USB#VID_0421&PID_0714#5&521a615&0&1#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-01-28 17.19.05.106: Connected device: Lumia
2018-01-28 17.19.05.106: Mode: Flash
2018-01-28 17.19.05.205: Custom flash attempt: 9 of 64
2018-01-28 17.19.05.765: Custom flash attempt failed
2018-01-28 17.19.05.765: Error: Flash failed! - 8 -1 0 0 0 0
2018-01-28 17.19.05.765: Error 0x1005: Data not aligned correctly
2018-01-28 17.19.05.765: Rebooting phone
2018-01-28 17.19.05.800: Lumia disconnected
2018-01-28 17.19.06.179: Found device on interface: 86e0d1e0-8089-11d0-9ce4-08003e301f73
2018-01-28 17.19.06.180: Device path: \\?\USB#VID_05C6&PID_9008#5&521a615&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2018-01-28 17.19.06.180: Connected device: Lumia
2018-01-28 17.19.06.180: Mode: Qualcomm Emergency Download 9008
2018-01-28 17.19.06.180: Sending programmer: C:\ProgramData\WPInternals\Repository\RM-1072\MPRG8x26_fh.ede
2018-01-28 17.19.06.180: Protocol: 0x00000002
2018-01-28 17.19.06.180: Supported: 0x00000001
2018-01-28 17.19.06.180: MaxLength: 0x00000400
2018-01-28 17.19.06.180: Mode: 0x00000000
2018-01-28 17.19.06.199: Programmer loaded into phone memory
2018-01-28 17.19.06.199: Starting programmer
2018-01-28 17.19.06.199: Programmer being launched on phone
2018-01-28 17.19.06.199: Wait to transfer control to programmer
2018-01-28 17.19.06.704: Send first hello to programmer
2018-01-28 17.19.07.208: First hello from PC accepted by programmer
2018-01-28 17.19.07.714: Error: Tyypin . poikkeus.
2018-01-28 17.19.07.715: Tyypin . poikkeus.
 

kukmikuk

Senior Member
Mar 17, 2015
129
23
I got exception "." during bootloader unlock on Windows Phone 8.1. Device is Lumia 640 LTE. My phone didn't booted anymore (was stuck in flash mode), but I fixed it with WDRT. Then I upgraded to Windows 10 Mobile and tried to unlock bootloader again but now I didn't got exception "." anymore but WPI crashed immediately when tried to unlock bootloader. Phone didn't booted up again (was stuck in flash mode), but I fixed it with WDRT. On Windows 10 Mobile WPI log file just says:
Error: Bad FFU file:


Which OS on PC, 32bit or 64bit? I had same problems on 32bit, when try on 64 bit with Win10 FCU, I had success with unlock bootloader Lumia 640
 

jethro tarw

Member
Jan 13, 2018
31
2
I have seen a hash mismatch message in the log too, that means you have the wrong emergency programmer downloaded. This is a common problem, as the original ones are messed up too, and even lumiafirmware.com has the wrong ones for most 640 variants

the hash mismatch in Attez's logs are normal, it's part of the bruteforce unlock of the bootloader.
 

culot

Senior Member
Oct 11, 2014
432
175
Bay
"Ya though it be nice if there was a warning on the program about devices with reset protection which there was not on the notes"


Hmmm, my device is not listed on MS's reset protect device list after flashing via this tool. So pretty much boned? Darn. Only a 640, not a big loss, but disappointing.
 
Last edited:
  • Like
Reactions: eKoKnight

Attez

Member
Jan 30, 2018
11
0
I have seen a hash mismatch message in the log too, that means you have the wrong emergency programmer downloaded. This is a common problem, as the original ones are messed up too, and even lumiafirmware.com has the wrong ones for most 640 variants

If I have wrong emergency programmer downloaded how I can find the working one?
 

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:
    https://wpinternals.net/index.php/128-introwpi22

    Version 2.3 is released:
    https://www.wpinternals.net/index.php/129-wpi23released

    Version 2.4 is released (changelog in the link):
    https://wpinternals.net/index.php/130-here-s-windows-phone-internals-2-4

    René (Heathcliff74)
    19
    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.

    Heathcliff

    PS. I will try to answer all other questions when I release the tool. No time now.
    14
    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.

    René
    12
    Windows Phone Internals 2.3 is released!

    Version 2.3 is released:
    https://www.wpinternals.net/index.php/129-wpi23released

    Heathcliff74
    11
    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.

    Heathcliff74,
    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.

    Heathcliff74.