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

Windows Phone Internals updated to version 2.4

Search This thread

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
My experience with L640: trying on PC with win10 rs1 32bit - pipe errors etc. On another PC with Win 10 64bit 1709 (16299.192) working ok, for the first time finding profile and then unlock bl, root and mass. Next unlock and relock was faster - probably profile was saved as djtonka writes above...

Profiling data is indeed saved. For Lumia 640 you may want to redownload the emergency file using WPI 2.4. Because emergency files are mixed up by Microsoft and WPI 2.4 tries to download the correct files (different names).
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
if you can flash the uefi partition on your phone, then all you need is this to build the kernel https://developer.qualcomm.com/download/db410c/little-kernel-boot-loader-overview.pdf

but the problem most of us are facing is that we don't have access to flash the uefi partition.

and we can't wipe those phones either since we don't have the board support packages for the soc's..

The UEFI partition can be replaced on Lumia's with bootlaoder Spec A. Not on Lumia's with bootloader Spec B! This is because SecureBoot Hack v2 works entirely different. You can add custom efi's though. Quite a few people already experimenting with this. For example: https://forum.xda-developers.com/windows-10-mobile/bds-menu-prototype-devices-t3745288
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
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.

Try again with WPI version 2.4 and let me know the results.
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
if windows phone internals would allow us to flash other partitions in the FFU for example plat.bin or uefi.bin like it does EFIESP/MainOS/Data partitions we could bypass this RDC problem in the later model phones.

that's assuming windows phone internals flashes them in uefi mode and somehow bypasses the RDC authentication issue.

or windows phone internals rebuilds an FFU and flashes it. in this case same applies, incorporate the option to build other partitions into the FFU.

WPI is capable of flashing any partition. But to be able to do that it needs at least an FFU with a header which is accepted by the phone. So, there you have the chicken and the egg.
 

the_R4K_

Senior Member
Jun 10, 2017
54
30
Horki
my phone unlocked but I can't start unsigned .efi
But I can boot in to Mass Storage and flash\backup partitions...
WPInternals give this info:
Effective bootloader security - Enabled
UEFI - Not blown
Secure Boot platform - Enabled
Effective Secure Boot status - Disabled
PS1 I runed efishell (using bootarm.efi from grub2 for lumas) and try run another .efi but it's give error: "Error reported: Security Violation"
chainloading using grub2 give error too...
PS2 i seen in log. After first unlocking "effective bl security" been disabled but now it's active((
 

Midral

Member
Jan 17, 2009
18
1
unlock and root performed on my lumia 950 RM-1104
Effective bootloader security - Enabled
UEFI - Not blown
Secure Boot platform - Enabled
Effective Secure Boot status - Disabled
 

holistic33

New member
Feb 6, 2018
2
0
Lumia 435 rm-1070 cant unlock bootloader wpi 2.4

hi @Heathcliff74
i have a lumia 435 rm-1070, this device has not reset protection feature. i tried to unlock bootloader with wpi 2.3 first, now with 2.4 and the result is the same: not valid ffu provided. i downloaded ffu and ede files with wpi (downloaded again with wpi 2.4)

the log:
2018-02-05 21:12:22.129: Windows Phone Internals version 2.4.6609.40600
2018-02-05 21:12:22.144: Copyright Heathcliff74 / wpinternals.net
2018-02-05 21:12:22.285: Found device on interface: 08324f9c-b621-435c-859b-ae4652481b7c
2018-02-05 21:12:22.285: Device path: \\?\usb#vid_0421&pid_06fc&mi_03#6&2c7110ae&0&0003#{08324f9c-b621-435c-859b-ae4652481b7c}
2018-02-05 21:12:22.285: Connected device: Lumia
2018-02-05 21:12:22.285: Mode: Normal
2018-02-05 21:12:22.925: Operator: MOV-MX
2018-02-05 21:12:22.941: Manufacturer Model Name: RM-1070_1009
2018-02-05 21:12:22.941: Product Code: 059W9F9
2018-02-05 21:12:22.957: Firmware: 02074.00000.15234.28005
2018-02-05 21:12:22.957: IMEI: ***************
2018-02-05 21:12:22.988: Public ID: 90 17 41 D8 3A 17 04 9D E7 4E BF 25 E6 0E FE 63 86 2A 96 C1
2018-02-05 21:12:23.004: Bluetooth MAC: 80 C5 E6 B3 5E F4
2018-02-05 21:12:23.019: WLAN MAC: 80 C5 E6 B5 CE B0
2018-02-05 21:12:23.019: Bootloader Security: Enabled
2018-02-05 21:12:23.035: Simlock: Active
2018-02-05 21:18:55.903: Start unlock. Phone needs to switch to Flash-mode
2018-02-05 21:18:55.903: In order to start unlocking the bootloader, the phone needs to be switched to Flash-mode.
2018-02-05 21:18:57.593: Switching to Flash-mode
2018-02-05 21:18:57.624: Rebooting phone to Flash mode
2018-02-05 21:18:57.640: Rebooting phone to Flash mode...
2018-02-05 21:19:08.803: Lumia disconnected
2018-02-05 21:19:13.657: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-02-05 21:19:13.657: Device path: \\?\USB#VID_0421&PID_0714#5&1f74503e&0&2#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-02-05 21:19:13.657: Connected device: Lumia
2018-02-05 21:19:13.657: Mode: Flash
2018-02-05 21:19:15.573: Phone type: RM-1070
2018-02-05 21:19:15.573: Product code: 059W9F9
2018-02-05 21:19:15.573: Root key hash: 80F2F707F2EF1F5650E81C07A552E2B911896BB046EB7D33D699F736B29FF74B
2018-02-05 21:19:15.573: Firmware version: 02074.00000.15234.28000
2018-02-05 21:19:15.573: IMEI: ***************
2018-02-05 21:19:15.573: Flash app: 2.59
2018-02-05 21:19:15.573: Flash protocol: 2.34
2018-02-05 21:19:15.573: SecureBoot: Enabled
2018-02-05 21:19:15.573: Flash app security: Enabled (FFU security: Enabled, RDC: Not found, Authenticated: False)
2018-02-05 21:19:15.573: JTAG: Disabled
2018-02-05 21:19:44.398: Adding FFU to repository: C:\ProgramData\WPInternals\Repository\RM-1070\RM1070_02074.00000.15234.28005_RETAIL_prod_signed_1009_02ACC4_000-MX_MV.ffu
2018-02-05 21:19:44.398: Platform ID: Nokia.MSM8210.P6200
2018-02-05 21:19:44.398: Firmware version: 02074.00000.15234.28000
2018-02-05 21:19:44.398: OS version: 6.3.9651.2
2018-02-05 21:19:44.429: Adding emergency files to repository: C:\ProgramData\WPInternals\Repository\RM-1070\MPRG8x12_fh.ede
2018-02-05 21:19:44.429: Type: RM-1070
2018-02-05 21:19:44.429: Unlock Bootloader
2018-02-05 21:19:44.429: Processing resources:
2018-02-05 21:19:44.429: Profile FFU: C:\ProgramData\WPInternals\Repository\RM-1070\RM1070_02074.00000.15234.28005_RETAIL_prod_signed_1009_02ACC4_000-MX_MV.ffu
2018-02-05 21:19:44.429: EDE file: C:\ProgramData\WPInternals\Repository\RM-1070\MPRG8x12_fh.ede
2018-02-05 21:19:44.898: Error: El valor no puede ser nulo.
Nombre del parmetro: No FFU with supported OS version was provided
2018-02-05 21:19:44.898: El valor no puede ser nulo.
Nombre del parámetro: No FFU with supported OS version was provided
2018-02-05 21:19:47.548: Security flags: 0x00004BFF
2018-02-05 21:19:47.579: Platform Name: Nokia.MSM8210.P6200.1.1
2018-02-05 21:19:47.595: Public ID: 90 17 41 D8 3A 17 04 9D E7 4E BF 25 E6 0E FE 63 86 2A 96 C1
2018-02-05 21:19:47.626: Root Key Hash: 80 F2 F7 07 F2 EF 1F 56 50 E8 1C 07 A5 52 E2 B9 11 89 6B B0 46 EB 7D 33 D6 99 F7 36 B2 9F F7 4B
2018-02-05 21:19:47.626: Platform Secure Boot Status: True
2018-02-05 21:19:47.626: Uefi Secure Boot Status: True
2018-02-05 21:19:47.626: Effective Secure Boot Status: True
2018-02-05 21:19:47.626: Bootloader Security Qfuse Status: True
2018-02-05 21:19:47.626: Bootloader Security Authentication Status: False
2018-02-05 21:19:47.626: Bootloader Security Rdc Status: False
2018-02-05 21:19:47.626: Effective Bootloader Security Status: True
2018-02-05 21:19:47.626: Native Debug Status: False
2018-02-05 21:19:47.689: Bootloader: Lumia Bootloader Spec B
2018-02-05 21:19:47.689: ProductCode: 059W9F9
2018-02-05 21:19:47.689: ProductType: RM-1070
2018-02-05 21:20:09.353: FFU not added, because it was already present in the repository.
2018-02-05 21:20:09.353: Emergency files not added, because they were already present in the repository.
2018-02-05 21:20:09.400: FFU not added, because it was already present in the repository.
2018-02-05 21:20:09.400: Unlock Bootloader
2018-02-05 21:20:09.400: Processing resources:
2018-02-05 21:20:09.400: Profile FFU: C:\ProgramData\WPInternals\Repository\RM-1070\RM1070_02074.00000.15234.28005_RETAIL_prod_signed_1009_02ACC4_000-MX_MV.ffu
2018-02-05 21:20:09.400: EDE file: C:\ProgramData\WPInternals\Repository\RM-1070\MPRG8x12_fh.ede
2018-02-05 21:20:09.400: FFU with supported OS version: C:\ProgramData\WPInternals\Repository\RM-1070\RM1070_02074.00000.15234.28005_RETAIL_prod_signed_1009_02ACC4_000-MX_MV.ffu
2018-02-05 21:20:10.181: Error: El valor no puede ser nulo.Nombre del parmetro: No FFU with supported OS version was provided
2018-02-05 21:20:10.181: El valor no puede ser nulo.
Nombre del parámetro: No FFU with supported OS version was provided
2018-02-05 21:20:31.836: FFU not added, because it was already present in the repository.
2018-02-05 21:20:31.836: Emergency files not added, because they were already present in the repository.
2018-02-05 21:20:31.883: FFU not added, because it was already present in the repository.
2018-02-05 21:20:31.883: Unlock Bootloader
2018-02-05 21:20:31.883: Processing resources:
2018-02-05 21:20:31.883: Profile FFU: C:\ProgramData\WPInternals\Repository\RM-1070\RM1070_02074.00000.15234.28005_RETAIL_prod_signed_1009_02ACC4_000-MX_MV.ffu
2018-02-05 21:20:31.883: EDE file: C:\ProgramData\WPInternals\Repository\RM-1070\MPRG8x12_fh.ede
2018-02-05 21:20:31.883: FFU with supported OS version: C:\ProgramData\WPInternals\Repository\RM-1070\RM1070_02074.00000.15234.28005_RETAIL_prod_signed_1009_02ACC4_000-MX_MV.ffu
2018-02-05 21:20:32.554: Error: El valor no puede ser nulo.Nombre del parmetro: No FFU with supported OS version was provided
2018-02-05 21:20:32.554: El valor no puede ser nulo.
Nombre del parámetro: No FFU with supported OS version was provided
2018-02-05 21:22:46.789: Rebooting phone to Normal mode
2018-02-05 21:22:46.789: Rebooting phone to Normal mode...
2018-02-05 21:22:46.860: Lumia disconnected
2018-02-05 21:22:51.612: Found device on interface: 9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc
2018-02-05 21:22:51.612: Device path: \\?\USB#VID_0421&PID_0714#5&1f74503e&0&2#{9e3bd5f7-9690-4fcc-8810-3e2650cd6ecc}
2018-02-05 21:22:51.612: Connected device: Lumia
2018-02-05 21:22:51.612: Mode: Bootloader
2018-02-05 21:23:02.420: Lumia disconnected
2018-02-05 21:23:23.030: Found device on interface: 08324f9c-b621-435c-859b-ae4652481b7c
2018-02-05 21:23:23.030: Device path: \\?\USB#VID_0421&PID_06FC&MI_03#6&2c7110ae&0&0003#{08324f9c-b621-435c-859b-ae4652481b7c}
2018-02-05 21:23:23.030: Connected device: Lumia
2018-02-05 21:23:23.030: Mode: Normal
2018-02-05 21:23:23.223: Operator: MOV-MX
2018-02-05 21:23:23.241: Manufacturer Model Name: RM-1070_1009
2018-02-05 21:23:23.299: Product Code: 059W9F9
2018-02-05 21:23:23.308: Firmware: 02074.00000.15234.28005
2018-02-05 21:23:23.319: IMEI: ***************
2018-02-05 21:23:23.325: Public ID: 90 17 41 D8 3A 17 04 9D E7 4E BF 25 E6 0E FE 63 86 2A 96 C1
2018-02-05 21:23:23.328: Bluetooth MAC: 80 C5 E6 B3 5E F4
2018-02-05 21:23:23.338: WLAN MAC: 80 C5 E6 B5 CE B0
2018-02-05 21:23:23.360: Bootloader Security: Enabled
2018-02-05 21:23:23.384: Simlock: Active
2018-02-05 21:37:43.283: Windows Phone Internals version 2.4.6609.40600
2018-02-05 21:37:43.283: Copyright Heathcliff74 / wpinternals.net
2018-02-05 21:37:43.392: Found device on interface: 08324f9c-b621-435c-859b-ae4652481b7c
2018-02-05 21:37:43.392: Device path: \\?\usb#vid_0421&pid_06fc&mi_03#6&2c7110ae&0&0003#{08324f9c-b621-435c-859b-ae4652481b7c}
2018-02-05 21:37:43.392: Connected device: Lumia
2018-02-05 21:37:43.392: Mode: Normal
2018-02-05 21:37:44.001: Operator: MOV-MX
2018-02-05 21:37:44.017: Manufacturer Model Name: RM-1070_1009
2018-02-05 21:37:44.017: Product Code: 059W9F9
2018-02-05 21:37:44.017: Firmware: 02074.00000.15234.28005
2018-02-05 21:37:44.048: IMEI: ***************
2018-02-05 21:37:44.064: Public ID: 90 17 41 D8 3A 17 04 9D E7 4E BF 25 E6 0E FE 63 86 2A 96 C1
2018-02-05 21:37:44.080: Bluetooth MAC: 80 C5 E6 B3 5E F4
2018-02-05 21:37:44.111: WLAN MAC: 80 C5 E6 B5 CE B0
2018-02-05 21:37:44.142: Bootloader Security: Enabled
2018-02-05 21:37:44.142: Simlock: Active
2018-02-05 22:17:08.278: Windows Phone Internals version 2.4.6609.40600
2018-02-05 22:17:08.278: Copyright Heathcliff74 / wpinternals.net
2018-02-05 22:17:08.450: Found device on interface: 08324f9c-b621-435c-859b-ae4652481b7c
2018-02-05 22:17:08.450: Device path: \\?\usb#vid_0421&pid_06fc&mi_03#6&2c7110ae&0&0003#{08324f9c-b621-435c-859b-ae4652481b7c}
2018-02-05 22:17:08.450: Connected device: Lumia
2018-02-05 22:17:08.450: Mode: Normal
2018-02-05 22:17:09.169: Operator: MOV-MX
2018-02-05 22:17:09.169: Manufacturer Model Name: RM-1070_1009
2018-02-05 22:17:09.184: Product Code: 059W9F9
2018-02-05 22:17:09.184: Firmware: 02074.00000.15234.28005
2018-02-05 22:17:09.200: IMEI: ***************
2018-02-05 22:17:09.216: Public ID: 90 17 41 D8 3A 17 04 9D E7 4E BF 25 E6 0E FE 63 86 2A 96 C1
2018-02-05 22:17:09.231: Bluetooth MAC: 80 C5 E6 B3 5E F4
2018-02-05 22:17:09.263: WLAN MAC: 80 C5 E6 B5 CE B0
2018-02-05 22:17:09.294: Bootloader Security: Enabled
2018-02-05 22:17:09.294: Simlock: Active
 
Last edited:

Hikey

Senior Member
Feb 15, 2008
413
3
reset protection tempered

Tried to bootloader relock my reset protection tempered Lumia 640 (RM-1073) with wpinternal2.4, the reset protection still on...
The FRP was switched on by wpinternal2.3 by mistake, my IMEI is not listed on MS database... Help please... :crying::crying::crying:
 

XDASumiaki

Member
Jan 11, 2018
22
5
XD

Thor2 has an option to do this:

Removes secure boot configuration policy: thor2.exe -mode rnd -remove_sbcp -skip_gpt_check -skip_com_scan

Ever someone managed to get this work? Because i couldnt... I now try it with unlocked bootloader...
This is the function to remove the bootloader's integrity checks / security key, in theory...:confused:
 

djtonka

Senior Member
Aug 1, 2010
1,104
510
City
You all unlocking it, what next?

---------- Post added at 08:22 AM ---------- Previous post was at 08:19 AM ----------

Just done 640 but is pointless doing any attempt for custom while when device is open for official way to any upgrade
 

eKoKnight

Senior Member
Feb 2, 2014
59
1
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.
 

spavlin

Senior Member
Dec 26, 2006
321
641
2018-02-05 13:33:52.986: Windows Phone Internals version 2.4.6609.40600
2018-02-05 13:33:53.002: Copyright Heathcliff74 / wpinternals.net
2018-02-05 13:33:53.205: Found device on interface: 86e0d1e0-8089-11d0-9ce4-08003e301f73
2018-02-05 13:33:53.205: Device path: \\?\usb#vid_05c6&pid_9006&mi_00#6&2d0cb51d&2&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2018-02-05 13:33:53.205: Connected device: Lumia
2018-02-05 13:33:53.205: Mode: Qualcomm Emergency 9006
2018-02-05 13:33:58.096: Found device on interface: 53f56307-b6bf-11d0-94f2-00a0c91efb8b
2018-02-05 13:33:58.096: Device path: \\?\usbstor#disk&ven_qualcomm&prod_mmc_storage&rev_1.00#7&14ad7efe&0&1234567890abcdef&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
2018-02-05 13:33:58.096: Connected device: Lumia
2018-02-05 13:33:58.096: Mode: Mass storage mode
2018-02-05 13:34:09.502: Последовательность не содержит элементов
2018-02-05 13:34:09.502: The sequence does not contain any elements
& Can not enable Enable Root Access

OSFMount:
Code:
2018-02-05 13:22:14.761: Windows Phone Internals version 2.4.6609.40600
2018-02-05 13:22:14.776: Copyright Heathcliff74 / wpinternals.net
2018-02-05 13:23:13.948: Enable Root Access on EFIESP...
2018-02-05 13:23:14.234: Attempt patch: SecureBootHack-V1-EFIESP
2018-02-05 13:23:14.781: Pattern: 0, 0
2018-02-05 13:23:14.781: Pattern: 1, 0
2018-02-05 13:23:14.781: Pattern: 2, 0
2018-02-05 13:23:14.781: Pattern: 3, 0
2018-02-05 13:23:14.781: Pattern: 4, 0
2018-02-05 13:23:14.781: Pattern: 5, 0
2018-02-05 13:23:14.781: Pattern: 6, 0
2018-02-05 13:23:14.781: Pattern: 7, 0
2018-02-05 13:23:14.781: Pattern: 8, 0
2018-02-05 13:23:14.781: Pattern: 9, 0
2018-02-05 13:23:14.781: Pattern: 10, 0
2018-02-05 13:23:14.781: Pattern: 11, 0
2018-02-05 13:23:14.781: Pattern: 12, 0
2018-02-05 13:23:14.781: Pattern: 13, 0
2018-02-05 13:23:14.781: Pattern: 14, 0
2018-02-05 13:23:14.781: Pattern: 15, 0
2018-02-05 13:23:14.781: Pattern: 16, 0
2018-02-05 13:23:14.937: Pattern: 17, 1
2018-02-05 13:23:14.937: Pattern: 18, 1
2018-02-05 13:23:14.937: Pattern: 19, 1
2018-02-05 13:23:14.937: Pattern: 20, 1
2018-02-05 13:23:14.937: Pattern: 21, 1
2018-02-05 13:23:14.937: Pattern: 22, 1
2018-02-05 13:23:14.937: Apply: 10.0.15254.158
2018-02-05 13:23:15.241: Enable Root Access on MainOS...
2018-02-05 13:23:15.241: Attempt patch: RootAccess-MainOS
2018-02-05 13:23:15.677: Pattern: 0, 0
2018-02-05 13:23:15.721: Pattern: 1, 0
2018-02-05 13:23:15.721: Pattern: 2, 0
2018-02-05 13:23:15.742: Pattern: 3, 0
2018-02-05 13:23:15.742: Pattern: 4, 0
2018-02-05 13:23:15.742: Pattern: 5, 0
2018-02-05 13:23:15.742: Pattern: 6, 0
2018-02-05 13:23:15.742: Pattern: 7, 0
2018-02-05 13:23:15.742: Pattern: 8, 0
2018-02-05 13:23:15.742: Pattern: 9, 0
2018-02-05 13:23:15.768: Pattern: 10, 0
2018-02-05 13:23:15.864: Pattern: 11, 0
2018-02-05 13:23:15.864: Pattern: 12, 0
2018-02-05 13:23:15.864: Pattern: 13, 0
2018-02-05 13:23:15.864: Pattern: 14, 1
2018-02-05 13:23:15.864: Pattern: 15, 0
2018-02-05 13:23:15.864: Pattern: 16, 0
2018-02-05 13:23:15.864: Pattern: 17, 0
2018-02-05 13:23:15.864: Pattern: 18, 0
2018-02-05 13:23:15.864: Pattern: 19, 0
2018-02-05 13:23:15.864: Pattern: 20, 0
2018-02-05 13:23:15.865: Pattern: 21, 0
2018-02-05 13:23:15.865: Pattern: 22, 0
2018-02-05 13:23:15.974: Apply: 10.0.15254.158
2018-02-05 13:23:16.858: Attempt patch: SecureBootHack-MainOS
2018-02-05 13:23:16.940: Pattern: 0, 0
2018-02-05 13:23:16.973: Pattern: 1, 0
2018-02-05 13:23:16.974: Pattern: 2, 0
2018-02-05 13:23:16.974: Pattern: 3, 0
2018-02-05 13:23:16.974: Pattern: 4, 0
2018-02-05 13:23:16.974: Pattern: 5, 0
2018-02-05 13:23:16.974: Pattern: 6, 0
2018-02-05 13:23:16.974: Pattern: 7, 0
2018-02-05 13:23:16.974: Pattern: 8, 0
2018-02-05 13:23:16.974: Pattern: 9, 0
2018-02-05 13:23:16.974: Pattern: 10, 0
2018-02-05 13:23:16.974: Pattern: 11, 0
2018-02-05 13:23:16.974: Pattern: 12, 0
2018-02-05 13:23:16.974: Pattern: 13, 0
2018-02-05 13:23:16.974: Pattern: 14, 0
2018-02-05 13:23:16.974: Pattern: 15, 0
2018-02-05 13:23:16.974: Pattern: 16, 0
2018-02-05 13:23:16.974: Pattern: 17, 0
2018-02-05 13:23:16.974: Pattern: 18, 0
2018-02-05 13:23:16.974: Pattern: 19, 0
2018-02-05 13:23:16.974: Pattern: 20, 0
2018-02-05 13:23:16.974: Pattern: 21, 0
2018-02-05 13:23:16.974: Pattern: 22, 0
2018-02-05 13:23:16.974: Pattern: 23, 0
2018-02-05 13:23:16.974: Apply: 10.0.15254.158
2018-02-05 13:23:17.026: Root Access successfully enabled!
But can not enable FULL Root Access & BootLoop after flash
 
Last edited:

djtonka

Senior Member
Aug 1, 2010
1,104
510
City
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.

check it first before it as FAQ ask

---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------

hi @Heathcliff74
not valid ffu provided..

read it again and again until you understend

---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------

I used Mass Storage Mode to swap out the hosts file. Now I have a working adblocker on my 950 :cool:

wow, I am speechless. Do not forget contribute to developer.
 

eKoKnight

Senior Member
Feb 2, 2014
59
1
check it first before it as FAQ ask

---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------



read it again and again until you understend

---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------



wow, I am speechless. Do not forget contribute to developer.

Its not in Faq. That is why im asking...
 

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.