[Windows Phone 8 Development and Hacking] rgxHost:
Reference For Manually Unbrick​

Thor2 Boot Modes

Boot to System

thor2 -mode rnd -bootnormalmode

Boot Into Boot Manager

thor2 -mode rnd -bootlumiabootmgr

Emergency Mode

thor2 -mode rnd -boot_edmode

USB MSC Mode

thor2 -mode rnd -bootmsc

Needless to say that you can check thor2 help file with:

thor2 /?

Problems with the *.hex File:

People who have a problem with the hex file, is because the hex file is invalid. The converter tool does not do a good job with converting bin files which are bigger than 64 KB.

To demonstrate: look at the file size of the original bin-files. Some are 60 KB and some are 74 KB. The conversion of the files with size 74 KB fails.

Look at the output hex-file in Notepad++.

Scroll to line 4098. From there on you see that all lines have an extra character. There is an odd number of digits, which is not possible with hex-values.

How to correct it?

Insert this line at linenumber 4098:

:020000042A01CF

All the next lines, except the last 3 lines start with:

:101

Replace that with:

:10

The last 3 lines should not be changed.

Save the hex-file and it will be ready to use.

Note: That line must be put at line 4098. And everything below will go down one line. Look at the lengths of the lines. In the original hex-file all lines from 4098 and below have an extra character. That is wrong. To go beyond the 64 KB limit, this extra line is needed and then the bad characters from the lines below must be removed as described.

Addittionaly:

1. The bin files in your opening post are fine, but they are probably incomplete. There are Lumia models, which have the same RKH, but they need different MPRG's. Not much we can do about now.

2. The bin files are converted to hex files. Those hex files are in your opening post. But not all of them are correct. I corrected a few of them and those are in post #76. You probably want to update the files in your opening post with these files.

Info

Tutorial it is not a complete step-by-step.

You need to sign everything as does .vpl programming (All recovery/flashing tool uses .vpl flashing).

1. Direct write .FFU will work as MSFT.

2. Writing with .Vpl file will work as OEM.

It is all same thing, but try to understand between two diff things.

Some security will get tight or can be vulnerable. (Actual I mean, OS will run with more differential)

How to get *.hex file

1) Get "bin2hex" Console Application

2) In Command Prompt go to your Bin2Hex.exe location and Copy your *.bin file there.

3) Type: bin2hex myBinFile.bin MyNewHexGile.hex

i.e: 00E9427DF118D9E27D098D13BECB6C6C89CE59F4.bin HEX.hex

The application will create the *.hex file for you.

Note: There's a chance that the new *.hex file could not be perfectly converted.

Check: Addittional Reference > Problems with *.hex files on this post (above).

Tip #1:

Use this extra FLAG in order to prevent the device to fail receiving the files through "Thor2":

-maxtransfersizekb 256

*Note: Some people reported that this value can be too high and cause flashing issues

XDA Links

Title: "Finally... unbrick your Lumia device QHSUSB_DLOAD without JTAG"

Title: "Qualcomm/Intel HEX files"

Title: "How to recover a Lumia with a malfunctioning USB port"