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

Finally... unbrick your Lumia device QHSUSB_DLOAD without JTAG

Search This thread

felipeunderx

Member
Jan 27, 2021
13
1
Hi, I have a lumia 1320 RM-994 phone. It was totally dead, it wouldn't turn on and with the guide and the hex and mbn files I managed to get a black screen with white letters that says NOKIA.

My pc recognizes it as "Nokia USB Connectivity", I would like to know how I could fix this and make this black screen change to red and flash the phone. Windows phone recovery tool does not detect it at all.

Here I leave a picture in the state in which it is:

 

iskender4444

Member
Mar 6, 2016
22
1
Hi, I have a lumia 1320 RM-994 phone. It was totally dead, it wouldn't turn on and with the guide and the hex and mbn files I managed to get a black screen with white letters that says NOKIA.

My pc recognizes it as "Nokia USB Connectivity", I would like to know how I could fix this and make this black screen change to red and flash the phone. Windows phone recovery tool does not detect it at all.

Here I leave a picture in the state in which it is:

Connect Lumia your pc then Open WDRT and select not detect my Phone or like that a option click it and select Lumia. hold power +vol down like 8-10 sec. pc will be see your recovery mode.
 

felipeunderx

Member
Jan 27, 2021
13
1
Connect Lumia your pc then Open WDRT and select not detect my Phone or like that a option click it and select Lumia. hold power +vol down like 8-10 sec. pc will be see your recovery mode.
The phone does not restart even if I press the buttons you tell me (volume down + power) but the pc now recognises the phone as "NOKIA FLASH" but it still has a black screen and white letters.


Still the WPRT tool does not recognise the device.

 
Last edited:
Jun 18, 2021
6
0
Power cycle the phone (short battery or remove and reinsert it)
Hi, sad but not working. Tried to charge battery, falsh with or without battery. eMMC isn't dead since i've flashed phone using wdrt.

May be someone got different hex/edp files for lumia 730? Since ones from lumiafirmware aren't booting, and phone is in emergency mode.

It seems like that secureboot can't check signature of flashed bootloader, so nothing happen.

Log:
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 -configfile emergency_flash_config.xml -ffufile ffu.ffu
Process started Fri Jun 18 11:22:36 2021
Logging to file C:\Users\9234~1\AppData\Local\Temp\thor2_win_20210618112236_ThreadId-9664.log
Debugging enabled for emergency

Initiating emergency download
Using Sahara emergency protocol
QUATTRO EMERGENCY FLASH START
Quattro Emergency Programmer version 2014.11.25.001
ED download selected
EXECUTE EMERGENCY DOWNLOAD START, FIREHOSE
Emergency Programmer V3 version 2015.03.09.001
ED download selected
Sahara image entries START
0x0D, MPRG8x26_fh.ede, true
Sahara image entries END
Starting Sahara emergency download
Entering state WAIT_HELLO
HELLO packet already received as handshake message
Erased stored HELLO packet
Sending HELLO_RESP
HELLO_RESP sent
Entering state WAIT_COMMAND
READ_DATA received
Opening image MPRG8x26_fh.ede
Image opened successfully
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
READ_DATA received
Sending RAW_DATA
RAW_DATA sent
END_IMAGE_TX received
END_IMAGE_TX with success status
Closing image MPRG8x26_fh.ede
Image closed successfully
Sending DONE
DONE sent
Entering state WAIT_DONE_RESP
DONE_RESP received
Stopped Sahara emergency download (status code = 0)
EXECUTE EMERGENCY DOWNLOAD END, FIREHOSE
Quattro Emergency Programmer version 2014.11.25.001
EDPAYLOAD download selected
EXECUTE EMERGENCY DOWNLOAD START, FIREHOSE
Emergency Programmer V3 version 2015.03.09.001
EDPAYLOAD download selected
Sending firehose single image
Waiting for Ed ready message, timeout 500 ms
Waiting for Ed ready message...DONE, status 0
Handling ed image RM1040_fh.edp to partition EMERGENCY
Image opened successfully for reading
Payload tool:
Apr 4 2014 08:12:09 Version 000.000.003
Payload generation info:
Fri Jun 20 06:56:16 2014
SW_ID:00000000ffff0000H, KCI:1289, MSM_ID:008000E100000000H, RKH:B68498287D74BB4247C4F8D0C3B19C1FCBCE9AB4H
Send signature
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Validation is enabled." /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="EMMC: size_in_sectors:15269888, mfr_id:21, oem_id:0, prod_rev:1, mfr_date:9/2014" /></data>
Send signature. DONE.
Send hashtable
Send hashtable.DONE.( 0 )
Configure FIREHOSE
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="32768" MaxPayloadSizeToTargetInBytesSupported="32768" MaxXMLSizeInBytes="4096" Version="May 7 2014_14:06:49" Revision="1" ChipSerialNumber="88707571" TargetName="8x26" /></data>
Successfully configured FIREHOSE
<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 53248, num 509" /></data>
Rawmode: ON

<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 53757" /></data>
Rawmode: OFF

<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 65536, num 306" /></data>
Rawmode: ON

<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 65842" /></data>
Rawmode: OFF

<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 69632, num 690" /></data>
Rawmode: ON

<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 70322" /></data>
Rawmode: OFF

<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 61440, num 2229" /></data>
Rawmode: ON

<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 63669" /></data>
Rawmode: OFF

<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 73728, num 538" /></data>
Rawmode: ON

<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 74266" /></data>
Rawmode: OFF

<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 77824, num 1327" /></data>
Rawmode: ON

<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 79151" /></data>
Rawmode: OFF

<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 57344, num 36" /></data>
Rawmode: ON

<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 57380" /></data>
Rawmode: OFF

Erase start. (FireHose)
<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 36864, num 32" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished address 36896" /></data>
Erase end. (FireHose)
Erase start. (FireHose)
<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 167936, num 16384" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished address 184320" /></data>
Erase end. (FireHose)
Erase start. (FireHose)
<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 184320, num 65536" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished address 249856" /></data>
Erase end. (FireHose)
<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 0, num 34" /></data>
Rawmode: ON

<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 34" /></data>
Rawmode: OFF

Send power cmd.
Send power cmd. Done.
Handling ed image ended with status 0
Payload data transfer speed(FH_SINGLE_IMAGE) (903.1 KB/s) Elapsed time 3.2 sec, data sent 2920413 bytes
EXECUTE EMERGENCY DOWNLOAD END, FIREHOSE
Resetting device
Due to configuration, reset is skipped!
QUATTRO EMERGENCY FLASH END
Emergency messaging closed successfully
WinUSB in use.
Detecting UEFI responder
Device is not in Lumia UEFI mode
Device mode get failed, mode is 7
Failed to boot to FlashApp
Operation took about 11.00 seconds.

THOR2_ERROR_BOOT_TO_FLASH_APP_FAILED
 

felipeunderx

Member
Jan 27, 2021
13
1
did u trying to with flash thor2 command ?
I need help!

It turns out that I changed the motherboard of the phone, it's a nokia lumia 1320, I live in Chile, Latin America. The reason is because it was bricked, but I'm a total noob when it comes to changing motherboards. The phone where I got the replacement plate, did not bring the sticker product code, then I do not know if I flash with the same firmware from the previous phone or what firmware should I put this phone.

Currently I tried to flash it with thor2 and when I flashed it, it disconnected and reconnected and now again it recognizes it as "Qualcomm hs usb qd-load 9008", should I try with other firmwares of my region and country?

Translated with www.DeepL.com/Translator (free version)
 

iskender4444

Member
Mar 6, 2016
22
1
I need help!

It turns out that I changed the motherboard of the phone, it's a nokia lumia 1320, I live in Chile, Latin America. The reason is because it was bricked, but I'm a total noob when it comes to changing motherboards. The phone where I got the replacement plate, did not bring the sticker product code, then I do not know if I flash with the same firmware from the previous phone or what firmware should I put this phone.

Currently I tried to flash it with thor2 and when I flashed it, it disconnected and reconnected and now again it recognizes it as "Qualcomm hs usb qd-load 9008", should I try with other firmwares of my region and country?

Translated with www.DeepL.com/Translator (free version)
NOT try different product number BUT you can different country and regions codes ffu to flash 😄
 
Jun 18, 2021
6
0
Hi, sad but not working. Tried to charge battery, falsh with or without battery. eMMC isn't dead since i've flashed phone using wdrt.

May be someone got different hex/edp files for lumia 730? Since ones from lumiafirmware aren't booting, and phone is in emergency mode.

It seems like that secureboot can't check signature of flashed bootloader, so nothing happen.

Log:
Maybe someone got idea? Bricked from trying to unlock bootloader.
Still not working :(
 

felipeunderx

Member
Jan 27, 2021
13
1
NOT try different product number BUT you can different country and regions codes ffu to flash 😄
I have tried to flash it with thor2, and when I flash the phone reaches about 21% and ends the fhasheo and can not continue, or reaches 6% or 19%, the same is with the windows phone recovery tool and windows phone internals, it may be a problem of battery charge?

If so, how do I charge the battery in flash mode? I know it's a stupid question, but I've plugged the phone with the charger for an hour or two and it doesn't charge anything.

Translated with www.DeepL.com/Translator (free version)
 
Jun 18, 2021
6
0
I have tried to flash it with thor2, and when I flash the phone reaches about 21% and ends the fhasheo and can not continue, or reaches 6% or 19%, the same is with the windows phone recovery tool and windows phone internals, it may be a problem of battery charge?

If so, how do I charge the battery in flash mode? I know it's a stupid question, but I've plugged the phone with the charger for an hour or two and it doesn't charge anything.

Translated with www.DeepL.com/Translator (free version)
Use this
1626198861556.png


In Ru they are everywhere on mobile phone stores.
 

felipeunderx

Member
Jan 27, 2021
13
1
Use this
View attachment 5361243

In Ru they are everywhere on mobile phone stores.
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
 

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
13
1
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    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.