Vorobejsawka,

I have hereRM892_3051.50009.1424.0006_RETAIL_eu_belarus_russia_223_06_451740_prd_signed.ffu
RM892_msimage_v1.0.mbn Engineering-SBL3-Lumia-925.bin FAST8960_CATWALK.hex
I downloaded them a long time ago and worked with these files many times .... what else? or is it not those
emergency files also give an error


Post has been editedzakarya67 - 23.02.19, 02:04

zakarya67,
To remove the dump, I generally saw a different team, a little different from yours

thor2 -mode ffureader -ffufile "C: \ ProgramData \ Microsoft \ Packages \ Products \ rm-892 \ RM892_3051.50009.1424.0006_RETAIL_eu_belarus_russia_223_06_451740_prd_signed.ffu" -dump_gpt -filedir C: \ dump

And here it’s painted a littlehttps: //answers.micros... 6c-a4be0c4dd525? page = 9, there are also links to HEX files just for x2x modelshttp://1drv.ms/1NTTW2m

I got a little confused with emergence files, a little they are not like that ...

Here's anotherhttps: //forum.xda-deve…-unbrick-jtag-t3082592

Post has been editedVorobejsawka - 23.02.19, 09:32

what's next

Post has been editedzakarya67 - 23.02.19, 11:33

zakarya67 , now you need to select the appropriate hex file for the set of numbers and letters that is at the very bottom, the long and the folder that gave on OneDrive

Posted on 02/23/2019, 11:47:

zakarya67 , and then execute the command already with these hex file and bin

Here is hexCD84376222AAF204C85119532BF34EA55C8844E4.zip(59.07 KB)


Drop it into the folder where the firmware and the file GPT0.bin from the Dump folder then execute the command thor2 –mode emergency –hexfile C: \ RM892 \ CD84376222AAF204C85119532BF34EA55C8844E4.hex –mbnfile C: \ RM892 \ GPT0.bin –orig_gpt

As the process ends and a red screen appears, connect the charger for an hour or two, let it charge, then run the command for thor2 firmware -mode uefiflash -ffufile "C: \ RM892 \ RM892_3051.50009.1424.0006_RETAIL_eu_belarus_russia_223_06_451740_prd_signedff

As the green screen appears, execute the command thor2 -mode rnd –bootnormalmode

The phone will reboot into normal mode. That should be all. Good luck.

Post has been editedVorobejsawka - 23.02.19, 12:23

zakarya67 , you need to look for an error in the command, is the path correct? Now I’ll recheck the team

zakarya67 , you need to try this, copy the hex and bin file to the thor2 folder. Just copy, there already rename it to HEX.hex and try the command thor2 -mode emergency -hexfile HEX.hex -mbnfile GPT0.bin -orig_gpt

On XDA, they really write that you need to rename GPT0.bin to msimage.mbn together with the extension and then do this command thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt

Try it again ... but first, copy both files to the folder with thor2 and rename them as in the command

And for toga firmware like this they write preferably thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C: \ RM892 \ XXX.vpl
XXX change to the name of the file with the VPL extension which is in the folder C: \ RM892

Post has been editedVorobejsawka - 23.02.19, 14:18

zakarya67 , you need to look for the solution error code ... Something is again somewhere wrong ... Or we are missing something ...

Posted on 02/23/2019, 2:43 p.m.:

zakarya67 , try also renaming the bin file itself with another command.

zakarya67 , no, this is something with the driver. Try a different USB port. That it can only be made assumptions ... And there are a lot of them ... My name is Sanya. вњЊпёЏ

(Sawka was once upon a time when there wasn’t much mobile Internet, there were chats through operators, and there the letter W was used instead of the Russian letter Ш, from there I got the nickname VorobeySashka.)

Post has been editedVorobejsawka - 23.02.19, 15:44

zakarya67 , I excited the group in the Cart, on this problem, and attached the photo, they answered that the body is in 9008 mode, and there are almost zero chances to return to life. By the way, have you tried in WDRT to click My phone on determined, choose Lumia and try? Nothing?

Post has been editedVorobejsawka - 23.02.19, 21:23

Yes ... Mode 9008. And in WDRT there is already No support for devices not included in the WM10 list .... In particular, the РҐ2РҐ series
I had to directly reflash the loader - as long as there are no results ... I will dig. You may have to overcome kualkomm

Post has been editedzakarya67 - 24.02.19, 02:44

in short - from 9008 mode, consider the body as a corpse

Tell me how to enter the body in 9008 by force? I killed 620, it does not boot and swear Unable to find bootable options. I read that in 9008 you can restore the bootloader, but I can not do it myself, I need to shorten the contacts or get soldered. Idiot, a couple of years ago I also banged 810.

hqqddy so try


one end of the cable is connected to the computer’s USB port, then at Nokia Lumia we press the volume up button and while pressing it gently connect the other end of the cord to the device. We don’t release the button, after connecting the Windows Device Recovery Tool it should start automatically and reinstall the drivers so that the PC “sees” the smartphone;
hold down the volume up button until the Lumia vibrates significantly. At this point, the utility should have time to detect your smartphone, activate the special UEFI mode and find the software necessary to restore the device’s operating system (you will need an Internet connection);
wait a while until a new firmware loads and installs;
After completing the recovery procedure, the smartphone must be rebooted in the usual way. The error "Unable to find a bootable option. Press any key to shut down В»you fixed

Vorobejsawka, this is some kind of fake, I tried, the body does not go into any mode from these manipulations and wdrt itself does not start, why would it behave like that. It is necessary to try to raise with emergency, somewhere on the screw there is a bunch of everything, it is necessary to understand.

Post has been editedhqqddy - 16.03.19, 09:54

when connected, it’s like an unknown device. in the task manager the body in9008 does not recover