Lumia 520/521Devices Unusable After Using Windows Phone Recovery Tool: Please Read

For users with Lumia 520/521 devices that have become unusable after an attempted recovery using the Windows Phone Recovery Tool (WPRT):
 
We have been gathering your feedback and actively researching the situation.  We have important updates to share:
 
Failures:
Devices that have failed to recover appear to fall into one of two different states:

  • Displaying a red Nokia logo
  • Displaying a black screen and the device is non-responsive after attempting to boot.
 
Issue Identification:
Although our investigation is not complete, we’d like to share some initial insight into what we’ve uncovered:
 
Data writing size & speed:  It was discovered that some devices are having trouble accepting the recovery image data being flashed.  The blocks of data were too large for some devices to handle, and the memory on the device was having trouble with the speed at which the data was being written.  In short, devices were getting too much data, too quickly.  This would cause the failure as the new software is corrupted.
 
Small portion of 520/521 devices affected:  As we reviewed logs and worked through issue reproduction, we identified the subset of affected 520/521 devices that may encounter this issue.  There is no direct way for an end-user to check their device unfortunately, however it is positive news that not all units would experience this issue..
 
Changes:
As a result of these findings, we are making two key changes to the way the recovery tool (WPRT) works.  We will be lowering the size of the data blocks being fed to the device during recovery (lowering from 2MB down to 128kB), and we will also be slowing down the data writing speed (from 8MB/sec to 5 MB/sec).  Testing has showed promising results from these changes.
 
To implement these changes, we have released an updated version of the WPRT tool.  You may notice when launching the WPRT that it checks for updates automatically.  Before attempting any further recovery or flashing on 520/521 devices, ensure that you’ve closed and re-launched the WPRT.  It will find this new mandatory version and automatically update.
 
Before we re-enable the update path from WP8 to Windows 10 Technical Preview for these devices, we will be reaching out to users to do a bit of additional real-world testing.  Once we’re confident in the results, we’ll turn the update path back on for these devices.
 
User Expectations & Recovery efforts:
For users who have already unusable devices, we’re continuing to research this situation.  There is no guarantee that using this updated version of the tool will recover an already-bricked device.  If your device is showing the red Nokia logo, please do the following:

  • Ensure your device has a good power source (connected via USB cable that can transfer data and charge the device simultaneously)
  • Close the WPRT, re-open, and take the update to the new version of the WPRT.  The new version is 1.2.4
  • Once he new version is installed, re-attempt the flashing process.
  • If your device is not recognized, click the "My phone was not detected" button and continue the attempted recovery process
If your device is on a blank/black screen and is unresponsive, you may attempt the same steps as listed above.  Devices that do not have the red Nokia logo on the screen are in a different state and will not have the same recovery rate should they be recoverable.  Please do try to recover and share your results.
 
Please check back for additional details and updates.  More information will be shared as it becomes available.
 

Was this discussion helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this discussion?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this discussion?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

C:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recove
ode emergency -hexfile F771E62AF89994064F77CD3BC16829503BDF9A3D.
mage.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 -mode emergency -hexfile F771E62AF89994064F77CD3BC16829503
file msimage.mbn -orig_gpt
Process started Thu Apr 30 18:21:34 2015
Logging to file C:\Users\SURIAL~1\AppData\Local\Temp\thor2_win_2
readId-6412.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
Message send failed with error code -1
Waiting connection to DLOAD: 2 of 2
Check if device in Dload
Message send failed with error code -1
Failed to connect to DLOAD mode
Make sure that the COM port is free. Close QPST.
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 10.00 seconds.

THOR2_EMERGENCYFLASHV1_ERROR_PROGRAMMER_SEND_FAILED

THOR2 1.8.2.15 exited with error code 85030 (0x14C26)

anyone has any sugestion?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Nice progression, since i have tried everything. I think I have to close some of it, anyone can tell me what the message mean: Close QPST , i did fully uninstall the QPST driver but keep getting this message, and when my phone is connected it is in QHSUSB_DLOAD mode.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

same problem as here..

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

its done, my phone is working again

THank you very much

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

You must detach your phone from USB, reboot it by detach/attach battery and attach to PC again

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

thanks man for ur help.

i have entered first command to extract gtp0.bin from ffu image.

but i got this error

 

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 ffureader -ffufile RM914_3058.50000.1425.0001_RETAIL_im_india_269_01
_444377_prd_signed.ffu -dump_gpt -filedir e:\dump
Process started Thu Apr 30 20:57:21 2015
Logging to file D:\Users\praneeth\AppData\Local\Temp\thor2_win_20150430205721_Th
readId-6568.log
Debugging enabled for  ffureader

Initiating do FFUReader operations
Version of FfuReader is 2015021601
Parsing FFU... Please wait...
Failed to parse FFU file. Header size: 0x00000000, Payload size: 0x0000000000000
000, Chunk size: 0x00000000, Header offset: 0x00000000, Payload offset: 0x000000
0000000000

File open failed

Unknown error code.

THOR2 1.8.2.15 exited with error code -1 (0xFFFFFFFF)

D:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool>

please help me. please

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

its done, my phone is working again

THank you very much

Hello Jayesh

Can you please help me extract the hex and bin file from FFU??

if yours is also indian version (RM914_3058.50000.1425.0001_RETAIL_im_india_269_01_444377_prd_signed.ffu) please attach the files.

Thank you.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

now i'm getting this : C:\Program Files (x86)\Microsoft Care Sui
ode emergency -hexfile F771E62AF89994064F
mage.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.
thor2 -mode emergency -hexfile F771E62AF8
file msimage.mbn -orig_gpt
Process started Thu Apr 30 18:35:07 2015
Logging to file C:\Users\SURIAL~1\AppData
readId-7560.log
Debugging enabled for  emergency

Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.3
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 success
Emergency Programmer V1 version 2014.10.3
Mbn download selected
Waiting for connection to flash programme
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 7 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 8 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 9 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 10 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 11 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 12 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 13 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 14 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ
Waiting to reconnect: 15 of 80
Connecting to flash programmer
Message send failed with error code -1
Failed to get response to HELLO_REQ

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I had this issue, looks like every time you run thor2 it will only work the first time. You get the QPST error, try unplugging the USB , and put back in , then run the command again.....
sjj

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I stucked on this step too :(

Phone in DLOAD mode detected, but error is appear...

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Discussion Info


Last updated June 9, 2023 Views 95,274 Applies to: