Finally... unbrick your Lumia device QHSUSB_DLOAD without JTAG

Search This thread

HCA_YT

New member
Jun 5, 2019
2
0
I tried using WDRT but it doesen't work.
Screenshot_2.png
Screenshot_3.png
Screenshot_4.png
Screenshot_5.png
Screenshot_6.png
Screenshot_7.png

After, I tried using thor2 but...:
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode emergency -hexfile C:\dump\HEX.hex -mbnfile C:\dump\GPT0.bin -orig_gpt

THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile C:\dump\HEX.hex -mbnfile C:\dump\GPT0.bin -orig_gpt
Process started Wed Jul 14 16:18:38 2021
Logging to file C:\Users\GABORE~1\AppData\Local\Temp\thor2_win_20210714161838_ThreadId-11556.log
Debugging enabled for emergency

Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Connection to DLOAD mode succeeded
Get Dload parameters
Sending HEX flasher to the device
Sending GO command if HEX flasher successfully uploaded.
Emergency Programmer V1 version 2014.10.31.001
Mbn download selected
Waiting for connection to flash programmer
Connecting to flash programmer
Received valid HELLO_RSP
Safe version=true, transfer size=15360
Received valid SECURITY_RSP
Successfully connected to flash programmer
Connection to flash programmer succeeded
Uploading bootloader(s), UEFI, etc from MBN image to the eMMC. This will take up to 20 seconds
Reading GPT from binary
-- GPT STARTs--
name: DPP
startLBA: 4096
endLBA: 20479
size: 0x0000000000800000 bytes
attributes: 0x0


name: MODEM_FSG
startLBA: 20480
endLBA: 26623
size: 0x0000000000300000 bytes
attributes: 0x0


name: SSD
startLBA: 28672
endLBA: 28703
size: 0x0000000000004000 bytes
attributes: 0x0


name: SBL1
startLBA: 32768
endLBA: 35767
size: 0x0000000000177000 bytes
attributes: 0x0


name: SBL2
startLBA: 36864
endLBA: 39863
size: 0x0000000000177000 bytes
attributes: 0x0


name: SBL3
startLBA: 40960
endLBA: 45055
size: 0x0000000000200000 bytes
attributes: 0x0


name: UEFI
startLBA: 45056
endLBA: 50055
size: 0x0000000000271000 bytes
attributes: 0x0


name: RPM
startLBA: 53248
endLBA: 54247
size: 0x000000000007d000 bytes
attributes: 0x0


name: TZ
startLBA: 57344
endLBA: 58343
size: 0x000000000007d000 bytes
attributes: 0x0


name: WINSECAPP
startLBA: 61440
endLBA: 62463
size: 0x0000000000080000 bytes
attributes: 0x0


name: BACKUP_SBL1
startLBA: 65536
endLBA: 68535
size: 0x0000000000177000 bytes
attributes: 0x0


name: BACKUP_SBL2
startLBA: 69632
endLBA: 72631
size: 0x0000000000177000 bytes
attributes: 0x0


name: BACKUP_SBL3
startLBA: 73728
endLBA: 77823
size: 0x0000000000200000 bytes
attributes: 0x0


name: BACKUP_UEFI
startLBA: 77824
endLBA: 82823
size: 0x0000000000271000 bytes
attributes: 0x0


name: BACKUP_RPM
startLBA: 86016
endLBA: 87015
size: 0x000000000007d000 bytes
attributes: 0x0


name: BACKUP_TZ
startLBA: 90112
endLBA: 91111
size: 0x000000000007d000 bytes
attributes: 0x0


name: BACKUP_WINSECAPP
startLBA: 94208
endLBA: 95231
size: 0x0000000000080000 bytes
attributes: 0x0


name: UEFI_BS_NV
startLBA: 98304
endLBA: 98815
size: 0x0000000000040000 bytes
attributes: 0x0


name: UEFI_NV
startLBA: 102400
endLBA: 102911
size: 0x0000000000040000 bytes
attributes: 0x0


name: PLAT
startLBA: 106496
endLBA: 122879
size: 0x0000000000800000 bytes
attributes: 0x0


name: EFIESP
startLBA: 131072
endLBA: 262143
size: 0x0000000004000000 bytes
attributes: 0x0


name: MODEM_FS1
startLBA: 262144
endLBA: 268287
size: 0x0000000000300000 bytes
attributes: 0x0


name: MODEM_FS2
startLBA: 270336
endLBA: 276479
size: 0x0000000000300000 bytes
attributes: 0x0


name: UEFI_RT_NV
startLBA: 278528
endLBA: 279039
size: 0x0000000000040000 bytes
attributes: 0x0


name: UEFI_RT_NV_RPMB
startLBA: 282624
endLBA: 282879
size: 0x0000000000020000 bytes
attributes: 0x0


-- GPT ENDs --

Sending OPEN_MULTI_REQ
Received valid response to OPEN_MULTI_REQ
Programming image C
Image opened successfully for reading
Uploading MBN image 70
SAFE hex file was used and unallowed memory address was being written.
Reset the device and use the correct HEX file.
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 18.00 seconds.

Unknown error code.

THOR2 1.8.2.18 exited with error code 85034 (0x14C2A)
This is what I get. Can someone help me? What can I do?
 
Last edited:

felipeunderx

Member
Jan 27, 2021
15
2
The battery of my phone is not removable, and I do not know how to connect it, it should charge rebooted or connected to the pc but it does not charge, so I ask if it is already hardware problem of my phone lumia 1320.

Regarding your problem, have you tried the emergency files that are left at the beginning of this topic?

I will leave the command that helped me to recover my device from the emergency state, maybe it will help you:

Code:

thor2 -mode emergency -hexfile %HomePath%\Desktop\YOUR_HEX_FILE.hex -mbnfile %HomePath%\Desktop\YOUR_MBN_FILE.mbn -ffufile %HomePath%\Desktop\YOUR_ROM_FILE.ffu -skipffuflash
The problem continues... help please.


Now when I connect it by usb, the phone disconnects and connects every two minutes and does it again and so on, the phone is in flash mode (NOKIA FLASH). I am afraid to flash it in this state, will there be any solution, the usb ports are in good condition and the usb cable too.

I have bought the universal charger that was posted earlier, and I'm charging the battery.
 
Jun 18, 2021
6
0
Still haven't got any idea on my 730, i've charged it using charger from previous post, it still stuck on DLOAD. When i flash it, it's okay, but fails with FAILED_TO_BOOT_FLASHAPP after reboot. It's not emmc, since i've killed boot handy when attempted to unlock bootloader(and loosened cable). However, i've noticed some strange things:
Battery is charged MAX to 75%. Probably battery is just loosing it's charge(2015 year), so can i try to connect some other nokia battery and flash from there? Also tried to flash without battery, no luck. May be try press some buttons? Found few topics about my phone on xda, and people successfuly restored their devices but without any files or mentions.
 

mak6021

Senior Member
Nov 26, 2016
78
22
40
Polotsk
_20211104_033708.JPG

Hi, does that mean memory failed? Can't you get up to it already?
Nokia 620
R846
Id******L6
 
Last edited:

kenkitt

Senior Member
Jul 16, 2013
115
37
I think you need to use windows recovery tool, sometimes this commands don't work.
 

[email protected]

New member
Jan 3, 2022
3
0
1
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile C:\rm-994\HEX.hex -mbnfile C:\rm-994\GPT0.bin -mbnfile C:\rm-994\GPT1.bin -orig_gpt
Process started Tue Feb 01 23:21:54 2022
Logging to file C:\Users\data\AppData\Local\Temp\thor2_win_20220201232154_ThreadId-1036.log
Debugging enabled for emergency

Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Connection to DLOAD mode succeeded
Get Dload parameters
Sending HEX flasher to the device
Sending GO command if HEX flasher successfully uploaded.
Emergency Programmer V1 version 2014.10.31.001
Mbn download selected
Waiting for connection to flash programmer
Connecting to flash programmer
Received valid HELLO_RSP
Safe version=true, transfer size=15360
Received valid SECURITY_RSP
Successfully connected to flash programmer
Connection to flash programmer succeeded
Uploading bootloader(s), UEFI, etc from MBN image to the eMMC. This will take up to 20 seconds
Reading GPT from binary
-- GPT STARTs--
name: DPP
startLBA: 4096
endLBA: 20479
size: 0x0000000000800000 bytes
attributes: 0x0


name: MODEM_FSG
startLBA: 20480
endLBA: 26623
size: 0x0000000000300000 bytes
attributes: 0x0


name: SSD
startLBA: 28672
endLBA: 28703
size: 0x0000000000004000 bytes
attributes: 0x0


name: SBL1
startLBA: 32768
endLBA: 35767
size: 0x0000000000177000 bytes
attributes: 0x0


name: SBL2
startLBA: 36864
endLBA: 39863
size: 0x0000000000177000 bytes
attributes: 0x0


name: SBL3
startLBA: 40960
endLBA: 45055
size: 0x0000000000200000 bytes
attributes: 0x0


name: UEFI
startLBA: 45056
endLBA: 50055
size: 0x0000000000271000 bytes
attributes: 0x0


name: RPM
startLBA: 53248
endLBA: 54247
size: 0x000000000007d000 bytes
attributes: 0x0


name: TZ
startLBA: 57344
endLBA: 58343
size: 0x000000000007d000 bytes
attributes: 0x0


name: WINSECAPP
startLBA: 61440
endLBA: 62463
size: 0x0000000000080000 bytes
attributes: 0x0


name: BACKUP_SBL1
startLBA: 65536
endLBA: 68535
size: 0x0000000000177000 bytes
attributes: 0x0


name: BACKUP_SBL2
startLBA: 69632
endLBA: 72631
size: 0x0000000000177000 bytes
attributes: 0x0


name: BACKUP_SBL3
startLBA: 73728
endLBA: 77823
size: 0x0000000000200000 bytes
attributes: 0x0


name: BACKUP_UEFI
startLBA: 77824
endLBA: 82823
size: 0x0000000000271000 bytes
attributes: 0x0


name: BACKUP_RPM
startLBA: 86016
endLBA: 87015
size: 0x000000000007d000 bytes
attributes: 0x0


name: BACKUP_TZ
startLBA: 90112
endLBA: 91111
size: 0x000000000007d000 bytes
attributes: 0x0


name: BACKUP_WINSECAPP
startLBA: 94208
endLBA: 95231
size: 0x0000000000080000 bytes
attributes: 0x0


name: UEFI_BS_NV
startLBA: 98304
endLBA: 98815
size: 0x0000000000040000 bytes
attributes: 0x0


name: UEFI_NV
startLBA: 102400
endLBA: 102911
size: 0x0000000000040000 bytes
attributes: 0x0


name: PLAT
startLBA: 106496
endLBA: 122879
size: 0x0000000000800000 bytes
attributes: 0x0


name: EFIESP
startLBA: 131072
endLBA: 262143
size: 0x0000000004000000 bytes
attributes: 0x0


name: MODEM_FS1
startLBA: 262144
endLBA: 268287
size: 0x0000000000300000 bytes
attributes: 0x0


name: MODEM_FS2
startLBA: 270336
endLBA: 276479
size: 0x0000000000300000 bytes
attributes: 0x0


name: UEFI_RT_NV
startLBA: 278528
endLBA: 279039
size: 0x0000000000040000 bytes
attributes: 0x0


name: UEFI_RT_NV_RPMB
startLBA: 282624
endLBA: 282879
size: 0x0000000000020000 bytes
attributes: 0x0


name: MMOS
startLBA: 286720
endLBA: 474652
size: 0x0000000005bc3a00 bytes
attributes: 0x0


name: MainOS
startLBA: 475136
endLBA: 4434444
size: 0x0000000078d41a00 bytes
attributes: 0x0


name: Data
startLBA: 4440064
endLBA: 15151103
size: 0x0000000146e00000 bytes
attributes: 0x0


-- GPT ENDs --




























Sending OPEN_MULTI_REQ
Received valid response to OPEN_MULTI_REQ
Checking eMMC read / write test results...
eMMC Read test passed. eMMC Write test passed!
Programming image C
Image opened successfully for reading
Uploading MBN image 70
SAFE hex file was used and unallowed memory address was being written.
Reset the device and use the correct HEX file.
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 11.00 seconds.

Unknown error code.

THOR2 1.8.2.18 exited with error code 85034 (0x14C2A)
 

xversion1

Member
Nov 24, 2016
23
1
this command will create gpt0.bin and rename it as msimage.mbn

mine was F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD so my hex file in binary format was F771E62AF89994064F77CD3BC16829503BDF9A3D.bin
I don't understand these step. I see gpt0.bin in C:\dump folder but there's no msimage.mbn. Am I supposed to manually rename it?
And where can I find this string F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD? I don't see anything like it in C:\dump.
Still get my Lumia 930 brick for 8 years or more, don't even remember, I bought it since it's released.
 

iskender4444

Member
Mar 6, 2016
32
2
I don't understand these step. I see gpt0.bin in C:\dump folder but there's no msimage.mbn. Am I supposed to manually rename it?
And where can I find this string F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD? I don't see anything like it in C:\dump.
Still get my Lumia 930 brick for 8 years or more, don't even remember, I bought it since it's released.
this unbrick method only works Spec-A models Lumias.
 

nexuspolaris

Member
Jan 18, 2016
7
3
Hello !
I have Lumia 1320 stucked on redscreen with nokia logo, PC sees it as NOKIA BOOTMGR, and tried a lot of solutions but still not unbricked it.
Here's my last log, cand anyone point me to the next step to try as I get error to comunicate with device:
Thank you very much! already the 3rd day trying to fix ...


C:\Users\Gorguts>cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool

C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -maxtransfersizekb 256 -ffufile "C:\ProgramData\Microsoft\Packages\Products\RM-994\RM994.ffu"
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -maxtransfersizekb 256 -ffufile C:\ProgramData\Microsoft\Packages\Products\RM-994\RM994.ffu
Process started Sun Sep 25 13:17:31 2022
Logging to file C:\Users\Gorguts\AppData\Local\Temp\thor2_win_20220925131731_ThreadId-11016.log
Debugging enabled for uefiflash

Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Detecting UEFI responder
Lumia UEFI Application did not respond to version info query
Device is not in Lumia UEFI mode
Device mode get failed, mode is 6
Connection lost, trying to re-connect
Rebooting to the normal mode...
Rebooting from the WP/MMOS failed.
Operation took about 6 minutes, 54 seconds.

THOR2_ERROR_TO_COMMUNICATE_WITH_DEVICE

THOR2 1.8.2.18 exited with error code 84102 (0x14886)

C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>
 
  • Like
Reactions: iskender4444

amoxx

Member
Nov 14, 2022
9
2
I tried to unbrick my Nokia Lumia 720 and it's fixed LOL, I have some error with thor 2 but after I removed battery and install right driver and it's worked LOL!
My phone has been felt to QHSUSB_DLOAD after I used Windows Phone Internals to unlock bootloader, and I think I have put wrong bootloader hex file... or something.
command: thor2 -mode emergency -hexfile FAST8930_RMxxx.hex -mbnfile RMxxx_msimage_v1.0.mbn -ffufile RMxxx.ffu
the ffu you can download on lumia firmware:
First install Windows Device Recovery Tools from Microsoft, or you can download in thread 1.
And secondly, install the QHUSB driver because the Lumia use Qualcomm SOC, so you can you any Qualcomm USB driver.
And driver is QHUSB: https://androidfilehost.com/?fid=674106145207490601
NOTE: IF YOU USE WINDOWS 8 OR 10 YOU NEED TO RESTART TO ADVANCED BOOT OPTION TO INSTALL UNSIGNED DRIVER BECAUSE THIS DRIVER IS OLD ENOUGH.
and all Lumia hex file I collect from someone on Youtube:
you need to put the all file needed to C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
and run the command:
thor2 -mode emergency -hexfile FAST8930_RMxxx.hex -mbnfile RMxxx_msimage_v1.0.mbn -ffufile RMxxx.ffu
It's error or not, don't worry disconnect the battery and turn power on.
flash the ffu file with WP internals: https://windows-phone-internals.en.lo4d.com/windows
You can search how to flash default FFU on the internet.
with xxx is the model of your phone.
if the link died, tell me. I will update soon.
YouTube Tutorial:
Peace!
310753002_482253610392320_5455420814667957969_n.jpg
 

Attachments

  • 20221115_193952.jpg
    20221115_193952.jpg
    1.3 MB · Views: 5
  • 20221115_193715.jpg
    20221115_193715.jpg
    2.5 MB · Views: 5
  • 20221115_193721.jpg
    20221115_193721.jpg
    1.4 MB · Views: 5
Last edited:

iskender4444

Member
Mar 6, 2016
32
2
I tried to unbrick my 720 and it's fixed LOL, I have some error with thor 2 but after I removed battery and install right driver and it's worked LOL!
command: thor2 -mode emergency -hexfile FAST8930_RMxxx.hex -mbnfile RMxxx_msimage_v1.0.mbn -ffufile RMxxx.ffu
the ffu you can download on lumia firmware:
And driver is QHUSB: https://androidfilehost.com/?fid=674106145207490601
NOTE: IF YOU USE WINDOWS 8 OR 10 YOU NEED TO RESTART TO ADVANCED BOOT OPTION TO INSTALL UNSIGNED DRIVER BECAUSE THIS DRIVER IS OLD ENOUGH.
and hex file I collect from someone on Youtube:
you need to put the all file needed to C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
and run the command:
thor2 -mode emergency -hexfile FAST8930_RMxxx.hex -mbnfile RMxxx_msimage_v1.0.mbn -ffufile RMxxx.ffu
It's error or not, don't worry disconect the battery and turn power.
flash the ffu file with WP internals: https://windows-phone-internals.en.lo4d.com/windows
You can search how to flash default FFU on the internet.
with xxx is the model of your phone.
if the link died, tell me. I will update soon.
Peace!
310753002_482253610392320_5455420814667957969_n.jpg
Have a good one brother :)
 
  • Wow
Reactions: amoxx

Javaron

Member
Nov 16, 2022
11
1
Try to install Qualcomm driver I used in my thread and use thor2.exe to detect phone. I have the video for tutorial on YouTube, link in the below the thread. Let try it!
Initiating FFU flash operation
WinUSB in use.
Operation took about 1 minute, 0 seconds.

THOR2_ERROR_NO_DEVICE_WITHIN_TIMEOUT

THOR2 1.8.2.18 exited with error code 84003 (0x14823)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I tried to unbrick my Nokia Lumia 720 and it's fixed LOL, I have some error with thor 2 but after I removed battery and install right driver and it's worked LOL!
    My phone has been felt to QHSUSB_DLOAD after I used Windows Phone Internals to unlock bootloader, and I think I have put wrong bootloader hex file... or something.
    command: thor2 -mode emergency -hexfile FAST8930_RMxxx.hex -mbnfile RMxxx_msimage_v1.0.mbn -ffufile RMxxx.ffu
    the ffu you can download on lumia firmware:
    First install Windows Device Recovery Tools from Microsoft, or you can download in thread 1.
    And secondly, install the QHUSB driver because the Lumia use Qualcomm SOC, so you can you any Qualcomm USB driver.
    And driver is QHUSB: https://androidfilehost.com/?fid=674106145207490601
    NOTE: IF YOU USE WINDOWS 8 OR 10 YOU NEED TO RESTART TO ADVANCED BOOT OPTION TO INSTALL UNSIGNED DRIVER BECAUSE THIS DRIVER IS OLD ENOUGH.
    and all Lumia hex file I collect from someone on Youtube:
    you need to put the all file needed to C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\
    and run the command:
    thor2 -mode emergency -hexfile FAST8930_RMxxx.hex -mbnfile RMxxx_msimage_v1.0.mbn -ffufile RMxxx.ffu
    It's error or not, don't worry disconnect the battery and turn power on.
    flash the ffu file with WP internals: https://windows-phone-internals.en.lo4d.com/windows
    You can search how to flash default FFU on the internet.
    with xxx is the model of your phone.
    if the link died, tell me. I will update soon.
    YouTube Tutorial:
    Peace!
    310753002_482253610392320_5455420814667957969_n.jpg
    1
    oh, I see you use Windows 11. Do you have any different Windows version like Windows 10? And I see the QHSUSB_BULK but in my opinion, have you try uninstall your driver and you install my driver, link in my post. You can try it and if it recognize Qualcomm HS-USB QLoader 9008 in my video that. You can try to use thor2 in cmd.View attachment 5766891
    Okay, Bro. I'll try your method with Windows 7 or 10, & let you know what will happen :)
  • 60
    04/30/2015
    And THE WAIT IS OVER ... after almost two months without telephone, as this has happened to me in February, with the help of you... have achieved UNBRICK LUMIA DEVICES WITHOUT JTAG ONLY WITH USB. Thank you, thank infinitely.

    Warning: use this tutorial at your own risk, I do not responsible of anything. To me it worked.

    05/25/2015
    Simple method:

    Yesterday update to WPRT 2.10 was released, which is able to fix DLOAD scenarios for lumias.
    Here is the link.

    --------------------------------------
    If this does not work, try the advanced method:

    Let's to the steps:
    Attachment files in the same thread.

    1) Install Thor2 (incluiding on WPRT): http://go.microsoft.com/fwlink/?LinkID=525569
    2) Download your firmware lumia with NaviFirm
    3) Install Drivers
    4) Go to the folder where it is thor 2 from cmd (run administrator)
    cd C:...

    Use this command line to extract gtp0.bin from ffu image

    Code:
    thor2 -mode ffureader -ffufile "C:\rm-914\XXX.ffu" -dump_gpt -filedir C:\dump

    this command will create gpt0.bin and rename it as msimage.mbn

    mine was F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD so my hex file in binary format was F771E62AF89994064F77CD3BC16829503BDF9A3D.bin

    convert this binary file to hex using bin2hex.exe

    Code:
    bin2hex F771E62AF89994064F77CD3BC16829503BDF9A3D.bin HEX.hex

    open .hex file in notepad
    insert :020000042A00D0 in first line
    and :040000052A000000CD before the last line

    or
    Hex files already created starting in the bin, use RESPONSIBLY depending on your Lumia device


    Now you have HEX.hex and msimage.mbn

    the use this command line

    Code:
    thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt

    Ready, disconnect the battery and reconnect. Now connect your phone to the PC
    Yeah, his phone started life with red screen!
    Charge the battery

    5) Flash rom: Now, in the case of Lumia 520/521

    Code:
    thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\ProgramData\Nokia\Packages\Products\rm-915\XXX.vpl

    .VPL remember it is not ffu. After the process 100%, your device turn with green screen, and:

    Code:
    thor2 -mode rnd -bootnormalmode
    :highfive:


    Some versions of Lumia, especially Lumia 820, 920, 920T, 925, 1020 (several models) have different .HEX, attached in the correct thread files ''CorrectedHexFiles.zip''
    thanks @Heathcliff74


    thanks @zapirkon and others users participated
    thanks @ TheBITLINK aka BIT of Windows Insider.

    Special thanks to Rathina Balan and AnnanZubair of Windows Insider Program
    Thanks all... :fingers-crossed: they are the best :):):)
    11
    draft for steps

    STEP 1 - find RootKeyHash and GPT.bin

    locate your FFU file. If your phone bricked during Downgrade, you should have it in
    c:\ProgramData\Microsoft\Packages\Products\rm-XXX...
    or
    c:\ProgramData\NOKIA\Packages\Products\rm-XXX...

    It should be best if you have the Windows Phone Recovery Tool updated to 1.2.4

    then go to the Microsoft / Windows Phone recovery folder (thor2.exe is there)
    c:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool\

    open up command line there, and make the dump in folder of your choice

    Code:
    thor2 -mode ffureader -dump_partitions -ffufile "RM9xx*.ffu" -filedir "c:\dump"

    the log will display also the hash needed for you to find correct HEX file

    Code:
    Number of partitions found 28
    RKH of SBL1: F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD
    RKH of UEFI: F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD

    also, the files are large, becaue the above step will make complete dump
    you only need GPT.bin which is around 250 KB so get this file only

    STEP 2. find the HEX file in the archive attached here

    it is named with name starting as the RKH from previous step.
    it is the first 40 bytes, so in the example
    F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD
    is infact
    F771E62AF89994064F77CD3BC16829503BDF9A3D.hex

    STEP 3. try to get RED screen

    Code:
    thor2 -mode emergency -hexfile bin.hex -mbnfile gpt.bin -orig_gpt

    the process above will not finish with success, as the provided GPT file is not only file needed to flash it. so I tried to flash it several times, reseting the phone ... etc., after 3-4 times, the phone vibrated, with red screen

    STEP 4. flash your phone FFU image
    Code:
    thor2 -mode vpl -maxtransfersizekb 1 -vplfile "C:\ProgramData\Microsoft\Packages\Products\RM .... \* .vpl"

    don't forget the -maxtransfersizekb flag because this flag perhaps was omitted in the Microsoft tool, making the flash procedure stop in the middle
    5
    Woohoo!!!! Success with my RM-893! Skiddd thanks for the bin package! Not sure where you got the RM-892 bin but I've tried several before yours and they didn't work but yours did!

    I converted to hex then had to do the edits since that one is larger than 60kb and now my phone is back to life! I've posted the edited file here for anyone with an RM-892/3 that wants to try it!
    3
    Now in every new Lumia from Microsoft there is way to force device to switch into emergency flash mode:
    3
    Can anybody tell me if this tutorial can somehow be used to unbrick my Samsung Ativ S? It's been dead for almost a month now.
    :crying:

    Not at all. By far. Sorry.:(

    ---------- Post added at 12:56 PM ---------- Previous post was at 12:53 PM ----------

    STEP 1 - find RootKeyHash and GPT.bin

    locate your FFU file. If your phone bricked during Downgrade, you should have it in
    c:\ProgramData\Microsoft\Packages\Products\rm-XXX...
    or
    c:\ProgramData\NOKIA\Packages\Products\rm-XXX...

    It should be best if you have the Windows Phone Recovery Tool updated to 1.2.4

    then go to the Microsoft / Windows Phone recovery folder (thor2.exe is there)
    c:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool\

    open up command line there, and make the dump in folder of your choice

    Code:
    thor2 -mode ffureader -dump_partitions -ffufile "RM9xx*.ffu" -filedir "c:\dump"

    the log will display also the hash needed for you to find correct HEX file

    Code:
    Number of partitions found 28
    RKH of SBL1: F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD
    RKH of UEFI: F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD

    also, the files are large, becaue the above step will make complete dump
    you only need GPT.bin which is around 250 KB so get this file only

    STEP 2. find the HEX file in the archive attached here

    it is named with name starting as the RKH from previous step.
    it is the first 40 bytes, so in the example
    F771E62AF89994064F77CD3BC16829503BDF9A3D506D3FACECAEF3F808C868FD
    is infact
    F771E62AF89994064F77CD3BC16829503BDF9A3D.hex

    STEP 3. try to get RED screen

    Code:
    thor2 -mode emergency -hexfile bin.hex -mbnfile gpt.bin -orig_gpt

    the process above will not finish with success, as the provided GPT file is not only file needed to flash it. so I tried to flash it several times, reseting the phone ... etc., after 3-4 times, the phone vibrated, with red screen

    STEP 4. flash your phone FFU image
    Code:
    thor2 -mode vpl -maxtransfersizekb 1 -vplfile "C:\ProgramData\Microsoft\Packages\Products\RM .... \* .vpl"

    don't forget the -maxtransfersizekb flag because this flag perhaps was omitted in the Microsoft tool, making the flash procedure stop in the middle



    {I quoted the whole thing above on purpose}

    Followed the steos "to the T" as they say. Worked just fine. You just forgot to mention that at the point of the Green Nokia Screen you can reset/remove batt/issue reset command to restart.

    Thank you Zapirkon for summarizing and thanks the OP as well for the finding.