Thanks, I thought the entire thing had to match.0CBD2EED6F62230571CBAB55B7DBC15F8A7DC7BB.hex
read the first 40bytes from RKH
Thanks, I thought the entire thing had to match.0CBD2EED6F62230571CBAB55B7DBC15F8A7DC7BB.hex
read the first 40bytes from RKH
You can give me the link? thanksplease link my hex files in the OP since there is a difference in content of generated hex files from different sources
it is on this thread...You can give me the link? thanks
Same problem for me....I managed to get the hex and the GPT files.
I have a matching file in the archive
But can't connect to my phone:
c:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool>thor2 -mode emergency -hexfile "D:\recover_phone\CD84376222AAF204C85119532BF34EA55C8844E4.hex" -mbnfile "D:\dump\gpt.bin" -orig_gpt
THOR2 1.8.2.15
Built for Windows @ 13:33:08 Mar 11 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile D:\recover_phone\CD84376222AAF204C85119532BF34EA55C8844E4.hex -mbnfile D:\dump\gpt.bin -orig_gpt
Process started Thu Apr 30 19:35:22 2015
Logging to file C:\Users\Amit\AppData\Local\Temp\thor2_win_20150430193522_ThreadId-6640.log
Debugging enabled for emergency
Initiating emergency download
Operation took about 21.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.15 exited with error code 84000 (0x14820)
It is looking like this in the device manager:
![]()
Yes ... I inserted the end of my post, his steps to blink flash rom lumia 520 with -maxtransfersizekb 1it is on this thread...
exe and source for bin->hex
http://forum.xda-developers.com/showpost.php?p=60442666&postcount=37
hex files and instructions
http://forum.xda-developers.com/showpost.php?p=60444532&postcount=39
C:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool>thor2.ex
e -mode emergency -hexfile CD84376222AAF204C85119532BF34EA55C8844E4.hex -mbnfile
GPT.bin -orig_gpt
THOR2 1.8.2.15
Built for Windows @ 13:33:08 Mar 11 2015
Thor2 is running on Windows of version 6.2
thor2.exe -mode emergency -hexfile CD84376222AAF204C85119532BF34EA55C8844E4.hex
-mbnfile GPT.bin -orig_gpt
Process started Thu Apr 30 21:51:37 2015
Logging to file C:\Users\LQS\AppData\Local\Temp\thor2_win_20150430215137_ThreadI
d-7040.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.
Message send failed with error code -1
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 8.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_MSG_SEND_RECEIVE_FAILED
THOR2 1.8.2.15 exited with error code 85021 (0x14C1D)
Remove all the drivers and Nokia programs and start from scratch. It must be detected as Nokia Emergency ConectivityHere is what i got on my 925 (RM-910)
My phone is detected as QHSUSB_DLOAD, when i try to update the driver to "EmergencyDownload" the phone is not recognized anymore, and i have to unplug it.Code:C:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool>thor2.ex e -mode emergency -hexfile CD84376222AAF204C85119532BF34EA55C8844E4.hex -mbnfile GPT.bin -orig_gpt THOR2 1.8.2.15 Built for Windows @ 13:33:08 Mar 11 2015 Thor2 is running on Windows of version 6.2 thor2.exe -mode emergency -hexfile CD84376222AAF204C85119532BF34EA55C8844E4.hex -mbnfile GPT.bin -orig_gpt Process started Thu Apr 30 21:51:37 2015 Logging to file C:\Users\LQS\AppData\Local\Temp\thor2_win_20150430215137_ThreadI d-7040.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. Message send failed with error code -1 ALPHA EMERGENCY FLASH END Emergency messaging closed successfully Operation took about 8.00 seconds. THOR2_EMERGENCYFLASHV1_ERROR_MSG_SEND_RECEIVE_FAILED THOR2 1.8.2.15 exited with error code 85021 (0x14C1D)
Remove all the drivers and Nokia programs and start from scratch. It must be detected as Nokia Emergency Conectivity
It was a problem on the hex file, i generated a new one(attached),Tryed to update the driver to Nokia Emergency connectivity , it succeeds but still show as QHSUSB_DLOAD (On two differents computers)
![]()
Edit : Actually i don't think it's a driver problem !
PS : My phone is a 925 (RM-910)
C:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool>thor2.ex
e -mode emergency -hexfile MyHex.hex -mbnfile msimage.mbn -orig_gpt
THOR2 1.8.2.15
Built for Windows @ 13:33:08 Mar 11 2015
Thor2 is running on Windows of version 6.2
thor2.exe -mode emergency -hexfile MyHex.hex -mbnfile msimage.mbn -orig_gpt
Process started Fri May 01 00:23:06 2015
Logging to file C:\Users\LQS\AppData\Local\Temp\thor2_win_20150501002306_ThreadI
d-1820.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
Checking eMMC read / write test results...
eMMC Read test passed. eMMC Write test passed!
Programming image m
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 10.00 seconds.
Unknown error code.
THOR2 1.8.2.15 exited with error code 85034 (0x14C2A)
I still don't get it...where does the BIN come from? The instructions only let's you generate the GPT0.bin (rename to msimage.mbn) and the GPT1.bin...there are no other files. It's probably really simple but i just don't get itThanks!!!!now I am charging my red screen.
took me forever to figure out where to get the BIN from as I had already downloaded a HEX file. However that HEX file did not work and when I generated my own it did.
Can you explain how generate yours?Thanks!!!!now I am charging my red screen.
took me forever to figure out where to get the BIN from as I had already downloaded a HEX file. However that HEX file did not work and when I generated my own it did.
That driver can't be installed on windows 8Same problem for me....
When I try to install the drivers from device manager I get an error that the "system cannot find the file specified"
You need to reinstall the driver, see aboveI managed to get the hex and the GPT files.
I have a matching file in the archive
But can't connect to my phone:
THOR2_ERROR_CONNECTION_NOT_FOUND
some bin2hex tools arent working for bins larger than 64k.Ok, i now understand the .bin files in the MPRG folder come from the ATF tool. I used the correct .bin file to generate a .hex file. It just doesn't work. The posted .hex file here on XDA als doesn't work for the lumia 925/rm-892 (CD84376222AAF204C85119532BF34EA55C8844E4). I posted my exact steps in this thread (username Michel Loyen):
http://answers.microsoft.com/en-us/.../c5d072d5-c26e-4a02-907d-fde2ca5e34c7?page=79
If someone has any solution please tell me![]()