Windows 10: KB4052623 bricked my device and recovery key not working

After installing the latest updates late March, my Surface crashed, after several tries, however, it was able to repair itself and boot up. Reading about what might have caused it, I removed KB4052623.


This month it wanted to install the May updates and after it rebooted it crashed again. This time it was not able to repair itself, so I decided to use the Troubleshooter to uninstall the latest security update. Something I didn't know, it now asks you for the recovery key. Having no clue what it was, I followed the link provided on the blue screen, logged into my Microsoft account and retrieved the recovery key. After I typed in the number, it told me it failed to unlock the device with this recovery key.


Following the instructions as listed in the Forbes article https://www.forbes.com/sites/gordonkelly/2020/03/26/microsoft-windows-10-warning-crashes-boot-problems-no-internet-wifi-upgrade-windows-10-free/#43ee11c54846, and turning off secure boot, it again asked me for the key, and upon entering it, I again got the message: "Failed to unlock with this recovery key".


Am I out of luck and do I have to start with a fresh install?

:)

 

Windows Device Recovery Tool Support for bricked Lumia 950

My new Lumia 950 bricked during recovery with Windows Device Recovery Tool 3.1.5. Trying Emergency flashing revealed Lumia 950 (RM-1104) is not in the Device List. How do I unbrick my phone? Is there a way, or do I wait for the emergency package for RM-1104
to be put on the device list?

Any answers, pls?

 

Lumia 520 bricked by Windows Phone Recovery Tool

As farby said, did you get the updated version AND verify the versions number as explained in post linked to?

So while the cause of the failure is know and the application is fixed there is no guarantee that a an already bricked phone will recover with the new version. Also I suggest you post your questions and results in the linked post as it is most likely the
team working on this will post updates and see your responses.

 

android recovery and kernel.img

IF you cannot enter ADB then your drivers are not working. Download the proper drivers for the device and do adb.exe devices to see if it shows anything