yashsingh1/xdaforums huggingface dataset:
[Windows 10 Mobile] nate0:
I did initially unlock it after flashing the original FFU for Denim. Then I relocked it. Updated to 14393.2007 (Unsupported by WPI 2.3), had issues with side loading appx files and editing the registry as neither of these features were working. So I relocked it again. Updated to 15063.297, did a hard reset, unlocked secure boot enabling mass storage, then enabled root access. The boot loader security is still enabled/blown, but the secure boot technology (UEFI Secure boot) is disabled/not blown.

When performing a hard reset I get a blue screen that states something like "A request was made to clear TPM....press Vol Up to clear it, press Vol Dn to continue without clearing. This will clear any keys stored...." I allow the request to clear TPM by pressing the appropriate Volume key and the boot up continues.
[Windows 10 Mobile] djtonka:
so you done unlocking again on 15063.297 without proper FFU?
[Windows 10 Mobile] lcdkhoa:
hi man, in this case, my Lumia had the problem before WPI 2.3 had been released.

I had done some tricks to modified led on Lumia 730 and then the error "Unable to find a boot option" occurred.

To now, my Lumia can't boot into windows. Okay
[Windows 10 Mobile] devilrex:
Hi.

I think u need L730 stock FFU and flash whit WPI.
[Windows 10 Mobile] lcdkhoa:
haiz, I already but ...
[Windows 10 Mobile] devilrex:
Nothing ? O.o
[Windows 10 Mobile] monoWench:
Running Win 10 15254.158 and it auto downloaded RM1085_1078.0053.10586.13169.12547.035242_retail_prod_signed.ffu

Recently reflashed back to Win 8.1 using the device recovery tool which used the same original ffu as WPInternals downloaded: RM1045_02540.00019.15234.50009_RETAIL_prod_signed_1036_026A88_000-AU.ffu
[Windows 10 Mobile] lcdkhoa:
hmm, nothing changed.
[Windows 10 Mobile] djtonka:
It include 10.0.10586.xxx so way different then 15254.158....
[Windows 10 Mobile] devilrex:
Same for L735.

But something strange happened:

running W10M, WPI downloaded alternative FFU RM1085.xxx.xxx but Windows drivers had corrupted.

Then used WDRM, restored WM8.1, WPI not recognized any alternative FFU O.O

Fortunately he had downloaded it before.
[Windows 10 Mobile] ahsan547:
Error 0x1003 Hash mismatch

-even with original ffu lumia 540 RM-1141, 059X291

used supported ffu of Rm1128 l550 10.0.10586.107
[Windows 10 Mobile] kukmikuk:
I get same blue screen when I did hard reset on 15063.297, but I press Vol Dn to continue without clearing. What is the diffrence when I press your Vol Up to clear TPM??
[Windows 10 Mobile] djtonka:
In this reset the device makes a deeper hardware reset, where e.g. Real Time Clock (RTC) and Battery Charging State are cleared.
[Windows 10 Mobile] kovalDN:
Heathcliff74, great jobs:good:

There is a problem.

After partition recovery Lumia 650 is determined by the (Platform Name) "Microsoft.MSM8909..2.0" instead of "Microsoft.MSM8909.P6237.2.0":

Original FFU is not Flash:

Flash failed!

Error 0x1304: Invalid platform ID

On the phone only flashing mode (two arrows).

Other tools are also not Flash.
[Windows 10 Mobile] megagprime:
we need to remove reset protection... :cowboy:
[Windows 10 Mobile] nate0:
https://docs.microsoft.com/en-us/wi...initialize-and-configure-ownership-of-the-tpm

"Clearing the TPM resets it to an unowned state. After you clear the TPM, the Windows 10 operating system will automatically re-initialize it and take ownership again."
[Windows 10 Mobile] nate0:
Can you still mount the phone in mass storage mode?

If so, boot to mass storage mode, when complete use a partitioning software to assign a drive letter to the partition label PLAT. Once done go in and look for a file named pconf.bin. Open it in notepad or a text editor. Then add the entry back at line 1 -- NAME=P6237. Click save, then go back to the partitioning software and clear the drive letter from the plat partition and reboot. I attached an example of a pconf.bin file so you see the format.
[Windows 10 Mobile] kovalDN:
Already wrote above that
[Windows 10 Mobile] nate0:
So you are stuck in flashing mode? Can you boot to the OS?
[Windows 10 Mobile] kovalDN:
Yes.

No.
[Windows 10 Mobile] nate0:
Try using thor2 with emergency mode. Boot with thor to edmode first, then using the emergency loaders flash the needed FFU file. If the OS is recovered and it boots you can push the needed plat cab file for your phone to update the PLAT ID by using iutool.
[Windows 10 Mobile] kovalDN:
Also wrote above that
[Windows 10 Mobile] nate0:
[MENTION=405418]kovalDN[/MENTION]

I am thinking if you can boot to flash mode, then thor2 should return some sort of out put from the phone. Hopefully you find some other way to recover the PLAT ID.
[Windows 10 Mobile] nate0:
[MENTION=405418]kovalDN[/MENTION]

In emergency mode. I flashed an AT&T FFU for a factory unlocked variant with a PLAT ID not matching the FFU, without having to use skip_ID_check skip_rkh_check or skip_integrity_check skip_signature_check. Did you try it without those options?

Edit: Your Platform ID is missing or corrupted. There is no FFU with the plat ID of Microsoft.MSM8909..

If you boot to the OS you can update the PLAT ID with your appropriate FW mmo.base.phone.plat_xxxxxxx.cab matching your country variant here
[Windows 10 Mobile] jethro tarw:
there may be a clue in this thread https://xdaforums.com/windows-10-mobile/guide-convert-950-ds-rm-111813058-t3534168/page3
[Windows 10 Mobile] kovalDN:
There was such idea, but where can I get AT&T FFU for Lumia 650.

And in any case it does not solve the problem with firmware as

This is the same, it does not solve a problem with this "INVALID_PLATFORM_ID".

Don't know such command. How to use it?
[Windows 10 Mobile] nate0:
[MENTION=405418]kovalDN[/MENTION]

There is no such ffu (AT&T branded) for the 650.

The skip_integrity_check was a mistyped option on my part sorry about that, I meant to type skip_signature_check. I noticed in both times you flashed using this method "C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode emergency -hexfile "MPRG8909_fh.ede" -edfile "RM1152_fh.edp" -ffufile "RM1152_1078.0042.10586.13333.15864.03535B_retail_ prod_signed.ffu" -skip_hash -skip_id_check -skip_signature_check -skip_rkh_check"

The device cannot skip those options easily unless I believe an RnD certificate exists which can be the case on prototype models.

If you run this from edmode does it still fail? `C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode emergency -hexfile "MPRG8909_fh.ede" -edfile "RM1152_fh.edp" -ffufile "RM1152_1078.0042.10586.13333.15864.03535B_retail_ prod_signed.ffu`

Edit: if it still fails when flashing this way then I believe the reason I've been able to flash a different variant ffu from edmode, would be due to the uefi boot security I had disabled with WPI 2.3, which I did not consider in your case.
[Windows 10 Mobile] devilrex:
Any news 4 this ?
[Windows 10 Mobile] jethro tarw:
it appears you can flash any ffu with the same RKH it doesn't matter which RM-XXXX it's for if you flash the corresponding edfile (edp) in emergency.

but this problem with the product ID being invalid seems to need to be fixed first.

I think you are right they should remove those flags as they will trigger the need for a RDC uploaded to the phone first.

---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------

just

thor2 -mode rnd -skip_gpt_check -boot_edmode

thor2 -mode emergency -hexfile MPRG8909_fh.ede -edfile RM1152_fh.edp -ffufile RM1152_1078.0042.10586.13333.15864.03535B_retail_p rod_signed.ffu

---------- Post added at 12:38 AM ---------- Previous post was at 12:31 AM ----------

we need to make RCD's and be able to change the RKH's

on a serious note. i'd really like to see WPI 2.3 to be able to dump the payload for us to play with ourselves as where it is breaking down for me and some others is flashing the modified payload to the phone in emergency mode. it gets a pipe error.

which leaves only the UEFI secure disabled.

if we could patch the mounted images, we could get around that. but it's not working at the moment.
[Windows 10 Mobile] RomLord14495:
does this tool even work I have been trying to unlock my Lumia icon and no success it. keeps on saying no supported FFU. I'm doing all the instructions my supposed to put in a special mode something.
[Windows 10 Mobile] RomLord14495:
I got it to work but the bootloader isn't fully unlocked the secureboot chain is unlocked. Not the bootloader
[Windows 10 Mobile] mayur.3.92:
Lumia 950XL doesn't unlock
[Windows 10 Mobile] jethro tarw:
It does appear to be truly bricked.

- Unless, we can modify the FFU file to match your invalid product code, but for that we would need certificates uploaded to the phone as your still secure.

---------- Post added at 12:27 PM ---------- Previous post was at 12:06 PM ----------

Maybe we should all start reading this documentation.

https://docs.microsoft.com/en-us/wi.../use-the-flashing-tools-provided-by-microsoft

then perhaps we can understand what we are doing here.

if we treat ourselves as a device manufacturer. perhaps we can wipe our devices and start fresh on them.

---------- Post added at 12:32 PM ---------- Previous post was at 12:27 PM ----------

I guess, the solution is to use qfil to flash a uefi onto the phone by using the qualcom comport driver in emergency mode. then perhaps we can control everything on the phone. and build an ffu to work and flash all partitions in memory.

However, I'm not sure which thread this should be discussed in as your phone bricked while using wpi, it was actually thor2 that bricked your device.

after a bit of reading to change the product code you need to edit SMBIOS config file in the PLAT (FAT12) partition inside the FFU.

also something that may be of interest is this area/partition of the ffu file called DPP (0X0000200000: 0X0000800000) - which is where certificates are used.

---------- Post added at 01:00 PM ---------- Previous post was at 12:32 PM ----------

something else I noticed.

"◦To force the device into the FFU download mode manually, press and release the power button to boot the device, and then immediately press and hold the volume up button. This option is available only after an initial FFU has been flashed to the device."

anyway if you've got the disk space try downloading Assessment and Deployment Kit (ADK) from Microsoft and try using ffutool included in it to flash the ffu file. it might skip some checks?!

https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit

https://msdn.microsoft.com/en-us/library/windows/hardware/dn789235(v=vs.85).aspx

"In a non-retail image, OEMs can disable the device platform validation for flashing by adding the DISABLE_FFU_PLAT_ID_CHECK feature to the OEMInput file that is used to generate the image. "

https://msdn.microsoft.com/en-us/library/windows/hardware/dn756803(v=vs.85).aspx - SMBIOS

---------- Post added at 01:28 PM ---------- Previous post was at 01:00 PM ----------

I'm assuming windows phone internals has the ability to build a FFU image since it can take it's component partitions separately and flash them to the phone successfully. maybe the DISABLE_FFU_PLAT_ID_CHECK can be used?
[Windows 10 Mobile] fwtrtdfdgh:
It fails on 950 and 950XL

Tool failed to unlock bootloader on both 950 and 950 XL. ROMs and emergency files downloaded through tool's Platform->Download option

Also failed to enable root access on mounted ROM images - results in application crash and close.

Log file reads:

2018-01-16 04:53:21.205: Dumping ROM...

2018-01-16 04:54:30.257: Successfully dumped ROM partitions!

2018-01-16 04:59:06.770: Error: Object reference not set to an instance of an object.

2018-01-16 05:08:44.732: Windows Phone Internals version 2.3.6584.1869

2018-01-16 05:08:44.732: Copyright Heathcliff74 / wpinternals.net

2018-01-16 05:09:31.641: Error: Object reference not set to an instance of an object.

2018-01-16 05:18:35.418: Windows Phone Internals version 2.3.6584.1869

2018-01-16 05:18:35.422: Copyright Heathcliff74 / wpinternals.net

---------- Post added at 12:52 PM ---------- Previous post was at 12:35 PM ----------

Same issue on a PC with win 7 ultimate and win 10 pro, both x64

So it's not OS related.
[Windows 10 Mobile] LeddaZ:
Same thing happened with ROM image from Lumia 635, 535 and 950 XL.

Log content:

2018-01-16 12:55:20.303: Windows Phone Internals version 2.3.6584.1869

2018-01-16 12:55:20.304: Copyright Heathcliff74 / wpinternals.net

2018-01-16 12:58:04.402: Error: Object reference not set to an instance of an object.
[Windows 10 Mobile] nate0:
[MENTION=405418]kovalDN[/MENTION]

Did you try this or can you?

Boot into edmode, then run thor2 -mode emergency -hexfile MPRG8909_fh.ede -edfile RM1152_fh.edp -orig_gpt, then flash the ffu using uefiflash mode, or you can try vpl mode.

Edit: I tested this on a 1520, and am able to flash an ffu of the same RKH signature but different platform ID with out changing the phone's platform ID, I am not sure why it works this way. Because if I flash the ffu in edmode in the same line without the -orig_gpt it fails with the platform ID error. If you get your Lumia 650 to flash, check the platform ID in the log to see if it updated. On this too I am not sure why it took two runs, but I ran the above command twice before it actually changed my platform ID from Nokia.MSM8974.P6081.2.2 to Nokia.MSM8974.P6081_ATT.2.2, I have done this more than several times going back and forth trying to get my uefi updated on this 1520 so it can charge properly and hopefully boot it as I messed up several days ago.
[Windows 10 Mobile] fwtrtdfdgh:
Right! Dumped ROM images have been created just fine though. Maybe there is a way to manually make changes to unlock mounted ROMs, not through tool.
[Windows 10 Mobile] jethro tarw:
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.
[Windows 10 Mobile] nate0:
Where's the challenge in that? ?
[Windows 10 Mobile] jethro tarw:
well as an alternative I'm looking into building an ffu.
[Windows 10 Mobile] zombie197:
I managed to finally get into my phone. I think the key things to note are, WM10 > 14393 and Interop tools > 1.9

You're right settings does take some time to provision. Just leave your phone on the reset screen for 10 minutes and when you come back to it, you should be able to get into settings.
[Windows 10 Mobile] the_R4K_:
WARNING do not enter in mass storage mode, if you have ffu mounted(vhd created from ffu).

after that my phone can't boot in normal\mass storage mode.

restoring EFIESP does not resolve this problem.

had to flash original ffu for resolve that.

if need I can give log.
[Windows 10 Mobile] RomLord14495:
Why would want to flash an att rom to 650 when there's a cricket ffu u can flash that has lte once u unlock the phone

---------- Post added at 08:06 PM ---------- Previous post was at 08:06 PM ----------

I mean sim unlock
[Windows 10 Mobile] entezar3323:
Does it support the Lumia 830؟؟؟؟

Does it support the Lumia 830؟؟؟؟
[Windows 10 Mobile] the_R4K_:
all lumias supported.
[Windows 10 Mobile] fwtrtdfdgh:
Nop. Absolutely no luck with 950 RM-1104 and 950 XL RM-1085 so not all of them.
[Windows 10 Mobile] NIKOSXRI:
We need to wait.Rene twitted yesterday that he is working on it
[Windows 10 Mobile] djtonka:
The one above did the homework too. Lazy cows
[Windows 10 Mobile] entezar3323:
not working

Does not work for the Lumia 830 rm-985
[Windows 10 Mobile] djtonka:
Just made Custom ROM for 830, based on AU or CFU, included Docking and LED out of the box. Testing time.
[Windows 10 Mobile] entezar3323:
The FFU-image you selected for profiling does not have a supported OS-version. Windows Phone Internals needs to extract files from a supported OS-version. You need to select such FFU. If necessary, you can select an FFU-image for a different model.

The program crashes

---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------

The program downloads the Windows 8.1 flash file
[Windows 10 Mobile] titi66200:
Same with Nokia Lumia 830 RM-984
[Windows 10 Mobile] djtonka:
same what?
[Windows 10 Mobile] ahsan547:
Again! Not working with lumia 540 RM-1141.

Tried with Stock & l550.ffu

can't unlock BL , ROOT ACCESS, MASS STORAGE.

evertime the device stucks into red screen(flash mode) after some attempts telling failed to write pipe: bla bla bla, custom flash failed.

Log says: hash mismatch
[Windows 10 Mobile] titi66200:
This

The FFU-image you selected for profiling does not have a supported OS-version. Windows Phone Internals needs to extract files from a supported OS-version. You need to select such FFU. If necessary, you can select an FFU-image for a different model.

The program crashes
[Windows 10 Mobile] djtonka:
Update to TH2, unlock using FFU from L550/650 with proper OS version. Then your profile is saved for future reference. It is weird, but as soon as you downgrade to Denim again, the tool will keep this backup FFU in profile and let you play with bootloader w/o problem any more even doing it on Denim.
[Windows 10 Mobile] kukmikuk:
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...
[Windows 10 Mobile] entezar3323:
sorry

You can get a guide

What kind of work do I do?
[Windows 10 Mobile] prokakavip:
Who has been successful on lumia 950 please show me how :confused:
[Windows 10 Mobile] jethro tarw:
I have found even thought it has saved the profile in the wpinternals.config is sometimes scans the flashing profile again, sometimes it finds it then at 14%, 40% or fails to find it. even if I revert back to original bootloader. it seems things are far from consistent.

as it stands now I have a 550 wiith unlocked UEFI.

the only thing that's in my way now is being able to flash the UEFI partition to the phone without the RDC certificates or being able to rebuild a FFU with a modified UEFI.

any pointers as I cant get hold of the board support packages for a snapdragon 210 as they are no longer open source and such I cant build a fresh FFU from scratch using the windows AEK or any other driver kit or hardware kit.
[Windows 10 Mobile] ahsan547:
Bro please!

Not working with lumia 540 RM-1141.

Upgraded to Th2 - 10.0.10586.107

Used the 540 ffu which is for RM-1141,Same product code written in the back part of my l540

and lumia 550.ffu ver th2 10.0.10586.107, pc has win 10 fcu 16299.15 x64

but can't unlock BL , ROOT ACCESS, MASS STORAGE... anything :( .

evertime the device stucks into red screen(flash mode) after some attempts wpi reports "failed to write pipe: bla bla bla, custom flash failed".

And the Log says: hash mismatch
[Windows 10 Mobile] XDASumiaki:
OK

Wait! I dont understand why you copied to the another device. By the way you can swap the batteries but thats a littlebit difficult.

The ESP partition have somewhere a *.efi file for the charging app...I think that is not for that model, or bad configuration. If u copy back the original if you have backup, it may work.

For partitions you need to remake the Data partition, on Linux you can mount the disk image and figure out with a partition manager, you will need to copy the files from the volume for temporarily, and try delete the partition and set it up with the correct identifiers , filesystem, and mount point. After that you just just copy back the files on it. I think it should work. But i still dont understand why you copied the raw emmc image...
[Windows 10 Mobile] djtonka:
Didn't you or someone previously didn't flashed using different software variant? Flash it first with that FFU image
[Windows 10 Mobile] nate0:
It was my own fault. Was experimenting but with the wrong partioning tool and was hasty about it. I was trying to copy over certain partitons (MODEM_FSG etc...) from a AT&T variant in order to correctly use LTE on it in the US. Messed up those partitions and in a last effort just copied over all partitons before the battery died to atleast keep it alive.
[Windows 10 Mobile] dastolly:
Lumia 950xl Unlocked

So I was able to unlock the 950xl and enter mass storage mode. I removed my phone from my Microsoft account following previous issues with the Bitlocker that others have noted. I had those issues, use WDRT, removed the phone from my account, then reattempted the unlock sequence. This worked, and I was able to enter mass storage mode as well. Unfortunately, it fails the flash when I try to relock the bootloader. I am unable to reflash with any FFU and I am unable to re enter mass storage mode. Any help with this would be greatly appreciated, or I'll be unlocked and depending on custom roms from here on out. I'm also happy to share what I can with an unlocked 950xl.

The error I'm getting when I try to restore the bootloader is: Flash Failed! Error 0X1106: Security header validation failed. Any ideas would be greatly appreciated.
[Windows 10 Mobile] titi66200:
[MENTION=8869982]dastolly[/MENTION]

What FFU did you use to unlock the bootloader of your 950XL?
[Windows 10 Mobile] dastolly:
I searched and downloaded the debranded FFU. I just typed in my product code - 059X5F0 - and downloaded all.

"RM1085_1078.0053.10586.13169.11302.034DF6_retail_prod_signed.ffu"
[Windows 10 Mobile] zombie197:
Did you try flashing with Phone Image designer tool?
[Windows 10 Mobile] XDASumiaki:
Not problem. EFI partition contains charging app, restore the original and you can charge, afterall try flash back the original FFU!!! If you have not flashmode(WDRT / thor2) only MTP, deploy the FFU manually for a different place in your storage (partition in Virtual Hard Disk file the best way) and try to dump the partitions. Be AWARE. Hi! :) I have actually more problems then you, I'm developing my own EFI bootloader for Linux/Android Kernel. Looks good. :rolleyes:
[Windows 10 Mobile] dastolly:
Just downloaded and tried, but my device is not appearing in the drop down for Phone Image Designer Tool.... Thoughts?
[Windows 10 Mobile] jethro tarw:
that's simple. you don't have the right drivers installed.

don't forget in this stage of the build, the phone is a qualcom soc, not a Lumia. so the drivers are the key here.
[Windows 10 Mobile] RomLord14495:
Actually you have the correct drivers u have to pit ur phone in uefi mode to flash via wpid which you do by turning off ur phone than you plug in ur phone into ur pc and press and hold volume up u till u get a cog with a lightning.bolt
[Windows 10 Mobile] dastolly:
Thanks for the help! Downloaded and installed the drivers, but it is still not showing up in the tool! In fact, it will only show up in WPInternals.... Strange.
[Windows 10 Mobile] zombie197:
You need to put the phone in FFU download mode. Completely shutdown your phone, press and hold the power button till you feel it vibrate. Then, immediately press volume up and release the power button till you see a lightning and gears sign. It should look like this ideally https://www.windowsblogitalia.com/wp-content/uploads/2015/05/FFU-Lumia.jpg

This will absolutely not work unless you disable driver signature enforcement and then install the drivers. I was going in circles a few time before I did that.
[Windows 10 Mobile] entezar3323:
Please provide a solution

There is no way to unlock the Lumia 830?
[Windows 10 Mobile] djtonka:
Follow my post on previously pages. I own 830 and is unlockable