#### amoxx

##### Member
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)
IMPORTANT thing is the driver. Did you restart to advanced startup option in Windows 10 to enable install unsignature driver? (Mode 7).

#### Javaron

##### Member
IMPORTANT thing is the driver. Did you restart to advanced startup option in Windows 10 to enable install unsignature driver? (Mode 7).
Yes, I've restarted to Advance Startup Option & Installed the Unsigned Diver Successfully, but the same result shows

#### amoxx

##### Member
Yes, I've restarted to Advance Startup Option & Installed the Unsigned Diver Successfully, but the same result shows
Can you show me the screenshot in the device manager when you plug the phone to the computer?

#### Attachments

• Screenshot 2022-11-21 203703.png
204.9 KB · Views: 21

#### amoxx

##### Member
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.

#### Javaron

##### Member
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

amoxx

#### Javaron

##### Member
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
Can you give me the .hex file for Nokia Lumia 730 ?

#### TechDiff

##### New member
omg thanks to this thread I was able to revive my old 920 after I brick it XD ..
specially :

- Trogper - Jakub Blazej :

-bruggesboy:

an important note that kept me from easily flashing my phone out of the "QHSUSB_DLOAD" was the USB cable, make sure to use a good "usb cable ,not a generic one" the flashing always stopped around 1% using a generic usb cable , but after switching to a good cable "my original PS4 controller cable" the whole thing worked

#### Cello Ski

##### New member
Please, i am a new bee to windows phone.
I was trying to update to windows 10 den my phone got brick.
it has a dead screen and when i connect it to the computer system it show usb unrecognised .
please i would be happy if someone could hlp me out

#### [email protected]

##### Member
hello i have a Lumia 820 but boot is damaged because i changed a id of partition by mistake and is detected as HID.

Last edited:

### Top Liked Posts

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

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

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

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

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

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

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.