Related
Hello all lumia owners ,with the release of windows phone internals there is a great rush to unlock bootloader and install custom rim.
In previous post I have posted about unlocking bootloader and enabling root access but what if you have bricked your lumia?
In That case Please read this thread and fix your lumia.
Lumia can be bricked by bad updating phone or disconnection in update or something else it might also be bricked by flashing custom Rom.
REQUIREMENTS
1.Windows Device Recovery Tool (WDRT)- Get it here
2.FFU image for your phone.(Larger than 1gb)(If you have custom rom then skip ffu image and jump to method 2) - check here
3.Drivers (Installed with WDRT)
Instruction
Method 1
1.Install WDRT and run it.
2.Dont Connect your phone, just click on I can''t find my device button.
3.Let it to Search for a Device.
4.Connect your device via USB cable.
4.Start Up your lumia by pressing power button.
5.If it is not starting,Struck on logo,or just a boot loop it can be read by WDRT.
6.WDRT will show device with unknown manufacturer, o's version etc.
7.Dont Flash software with it Just close it.
8.Go to http://www.lumiafirmware.com/info and read all instruction and follow it to manual flash flu file.
9.Wait Until all is done and reply if this fixed your lumia.
Method 2 (Easy)
If you didn bricked your device in flashing or unlocking bootloader then Its better to jump out method 1 as it is more easy for you.
Or if you have custom rom for your phone and not want to download full original ffu then stay here.
1. Install Windows device recovery tool.
2. Go to :
For 32bit window.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
For 64bit window.
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
Or whatever install folder you selected.
3. Hold shift and right click on your mouse and click open command windows here.
4. Paste thor2 -mode uefiflash -ffufile " " in cmd and click enter.(This will start searching your phone)
4. Press And Hold Poweroff + Lower Volume Button (Dont release it if your phone turn on automatically)(Especially in Bootloop).
5. Connect your phone to PC ( of course using USB cable).
6. if it detect Your device it will take you to Flash Screen (Ignore errors as it appear becuase in ffu location we take " " and its completely normal.)
7. Run Windowsphone internals and now it will detect your phone in flash mode.
8. Now you can Flash Custom rom (if bootloader unlocked) or just flash stock ffu image (dont need unlocked bootloader.)
Done
I will try to find more and more method to fix brick lumia until then this method is best or just send device to service center if this didn't fixed.
Greetings;
the *.ffu file won't be found at: http://www.lumiafirmware.com/info (for most devices).
That's some misleading website info; copied to several tutorials.
Reference: "Tutorial: Unbrick Lumia Devices"
Considering your System drive is " C: "
Open: C:\Program Data\Microsoft\Packages\Products\RM-<Number>
* Where <Number> will be your device release model number.
Note: You can check Code & Release Model Number on the back of your phone by removing your battery.
Inside that folder you can see that you have some required files to recover your device from Bricked states.
i.e: the *.ffu file.
Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_20170617053045_ThreadId-10580.log
Debugging enabled for uefiflash
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)
Is there any way I can create a temporary bus between the phone and that thor utility to send a bootloader handshake?
Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_201706 17053045_ThreadId-10580.log
Debugging enabled for uefiflash
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)
what i do now? is that any way to recreat my lumia phone?
swapnilnaikwadi said:
Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_201706 17053045_ThreadId-10580.log
Debugging enabled for uefiflash
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)
what i do now? is that any way to recreat my lumia phone?
Click to expand...
Click to collapse
Same problem? did you find a solution?
YOU ARE THE MAN.
my 930 was bricked by wpinternals misuse and this simple guide fixed it!!
my nokia was completely dead, and you sir, saved my 930 with this recommended guide!!
rgxHost said:
Greetings;
the *.ffu file won't be found at: http://www.lumiafirmware.com/info (for most devices).
That's some misleading website info; copied to several tutorials.
Reference: "Tutorial: Unbrick Lumia Devices"
Considering your System drive is " C: "
Open: C:\Program Data\Microsoft\Packages\Products\RM-<Number>
* Where <Number> will be your device release model number.
Note: You can check Code & Release Model Number on the back of your phone by removing your battery.
Inside that folder you can see that you have some required files to recover your device from Bricked states.
i.e: the *.ffu file.
Click to expand...
Click to collapse
if it is possible to recover data from a damaged lumia, I do not want to lose data
Greetings; using Nokia firmware tool will reset your device to factory settings (on mine, reverts back to windows 8).
Best regards;
Hi all, i have a bricked lumia 1320 with samsung emmc. When i power it on, it says: unable to find boot options
This problem started when i downgraded from windows 10 mobile to lumia denim using WDRT. The flashing procedure went well and, at reboot, the error message appeared on screen.
i've tried with thor2, windows phone internals, WDRT to unbrick the device but i failed. Do you have other suggestions? I read that exists a way to restore the device using jtag or atf box but i don't want to buy a 100$ peripheral for a one-time procedure
I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
(REMOVE THE SPACES)
gmirz2005 said:
I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
Click to expand...
Click to collapse
Hi!
My lumia 635 has no .mbn and .hex extension files at lumiafirmwaredotcom, but .edp and .ede files.
I tried both but not working, runs 20seconds and "err connection not found"
My lumia when connected at usb is recognized as unkown device, dont know what do anymore
nhtmd2 said:
Hi!
My lumia 635 has no .mbn and .hex extension files at lumiafirmwaredotcom, but .edp and .ede files.
I tried both but not working, runs 20seconds and "err connection not found"
My lumia when connected at usb is recognized as unkown device, dont know what do anymore
Click to expand...
Click to collapse
OK, so what you need to do now is, to remove the battery of your phone and connect it to the computer.
As I am seeing the log of the program, it says that the device is not detected.
So try removing your battery, connect it to your computer, wait until the computer successfully installs the QH-USB Dloader driver.
Firstly, try repairing your phone by doing the following steps:
1. start CMD as administrator
2.type cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
or if your pc is 32 bit OS, then type C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
3.now type the following thor2 -mode emergency -protocol sahara -hexfile edefile.ede -edfile edpfile.edp
4. do it for 5 times
5. disconnect the device
6. insert the battery
7. connect it to wall charger
8. wait 10 minutes, for it to charge
9. connect the device to PC
10. if the device shows the red flash screen, then you are good to go
11. if not, then remove the device from computer, disconnect the battery, reconnect the device to computer, launch WDRT
12. click My Device Is Not Detected
13. click LUMIA
14. if your device has been detected, it will be shown in WDRT (if not then retry the steps from 1 to 7 for several times)
15. click your device
16. wait until the device recovers from Emergency State
17. wait until your device reflashes
18. enjoy!
NOTE: All data is already lost and cannot be recovered as Windows Phones use secure erase, and no data recovery tool will be able to get the files back
SO FINGERS CROSSED TO ONEDRIVE BACKUP YOUR PHOTOS/VIDEOS and ELSE!
gmirz2005 said:
OK, so what you need to do now is, to remove the battery of your phone and connect it to the computer.
As I am seeing the log of the program, it says that the device is not detected.
So try removing your battery, connect it to your computer, wait until the computer successfully installs the QH-USB Dloader driver.
Firstly, try repairing your phone by doing the following steps:
1. start CMD as administrator
2.type cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
or if your pc is 32 bit OS, then type C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
3.now type the following thor2 -mode emergency -protocol sahara -hexfile edefile.ede -edfile edpfile.edp
4. do it for 5 times
5. disconnect the device
6. insert the battery
7. connect it to wall charger
8. wait 10 minutes, for it to charge
9. connect the device to PC
10. if the device shows the red flash screen, then you are good to go
11. if not, then remove the device from computer, disconnect the battery, reconnect the device to computer, launch WDRT
12. click My Device Is Not Detected
13. click LUMIA
14. if your device has been detected, it will be shown in WDRT (if not then retry the steps from 1 to 7 for several times)
15. click your device
16. wait until the device recovers from Emergency State
17. wait until your device reflashes
18. enjoy!
NOTE: All data is already lost and cannot be recovered as Windows Phones use secure erase, and no data recovery tool will be able to get the files back
SO FINGERS CROSSED TO ONEDRIVE BACKUP YOUR PHOTOS/VIDEOS and ELSE!
Click to expand...
Click to collapse
Oh man ty very much for your answer, im gonna try it out tomorrow night and come back here to give u feedback!
Sorry for the double quote here and in the other post.
Fingers crossed, thanks!
nhtmd2 said:
Oh man ty very much for your answer, im gonna try it out tomorrow night and come back here to give u feedback!
Sorry for the double quote here and in the other post.
Fingers crossed, thanks!
Click to expand...
Click to collapse
got it!
Waiting!...
Hope it works
I have a Nokia Lumia 1020 completely unresponsive buttons and screen, except for the Windows LED logo that lights up briefly when I plug it in. It is running wp8.1 and it doesn't have a removable battery
Any help would be greatly appreciated. I honestly don't mind if it needs to be completely wiped. I mostly just use it for the camera.
ChrisWilke said:
Any help would be greatly appreciated. I honestly don't mind if it needs to be completely wiped. I mostly just use it for the camera.
Click to expand...
Click to collapse
Try leaving your phone charging for 1 day.
After that connect it to WDRT (Windows Device Recovery Tool)
And start reflashing the software.
NOTE: If the WDRT doesn't detect it, try holdin POWER and VOLUME DOWN buttons for 15 secs, it will trigger a power-cycle.
https://forum.xda-developers.com/windows-phone-8/development/unbrick-dead-boot-lumia-jtag-t3872885
Does anybody know how to use this thor2 command?
Device authentication:
thor2 -mode rnd -do_authentication -sdauthenticationtype production -skip_com_scan -skip_gpt_check [-server saisec001.europe.nokia.com] [-securesessionfile mysession.sessionid]"
Click to expand...
Click to collapse
gmirz2005 said:
I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
(REMOVE THE SPACES)
Click to expand...
Click to collapse
Thanks for your gr8 efforts - However How to find Hex and MBN files - how to identify and from where to download - can make life easy - please help i have - i have Lumia 532 - Product 059w980 - RM-1031
I'm writing this in android development section because this is only section for both models, i hope this is not a problem.
Also i want to say thanks to sataccount from gsmhosting, he found working map at the end.
This guide is for hard bricked phones, where bootloader is destroyed and there is no any tools which recognize phone.
When you connect phones without bootloader Windows detects them as exynos7420 in other devices in device manager.
All this is achieved using trial/error method and I still don't know real sboot map and where is what in sboot.bin.
What i found till now is that sboot consist from this parts:
1. fwbl1 bl1
2. bl2 bl2
3. el3_mon el3
4. bootloader bootloader
5. tzsw tzsw
I repaired my g925a and have files only for this model, but i will try to explain how to prepair files for any other model.
We have to use same version of bootloader which was previosly in phone, or if you are unsure use latest sboot.bin.
Download tools: http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip
In folder USB_DownLoad_Tool there is a folder Disk1
Connect phone and hold power button.
Windows will detect exynos7420 device, install Driver:
click manually,
com and lpt ports,
have disk,
point to data1 folder.
Don't run setup from Data1 folder!!!
Now we have to copy
WinDNWApi.dll
WinDNWApi.lib
in:
c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
Probably there is no this folder, just create it and copy 2 files.
Don't copy WinDNWApi.dat as it is written in original manual, this file is for older exynos chip and procedure will not work, everything works without this file (it only has maps for 5250 and some other cpu)
Now we have to create boot files.
Download sboot.bin for your device, as i wrote best to find same bootloader which was in device before brick.
In some hex editor create 4 files (i'm using frhed, just click copy, enter offset, new file, paste, save and over again for all four files) with this map (again thanks to sataccount):
Novi1.bin 0..0x1FFF (size 0x2000 or 8192 )
Novi_2.bin 0x2000..0x31FFF (size 0x30000 or 196608)
Novi_3.bin 0x32000..0x3dfff (size 0xC000 or 49152)
Novi4.bin 0x3E000..10EFFF (size 0xD1000 or 856064)
This is all without tzsw. If phone still does not enter to odin mod, make last file from 0x3E000 to the end of the file (18F10F) and try again.
Start multiuploader.exe
Connect phone and hold power button.
Browse and find SH-usb-booting.cfg (in attached file proba folder, that is where you will probably prepare all boot files)
click start and phone will enter odin mode.
Start odin and flash sboot and everything else.
First of all thanx this is a real sharing is caring thing.I'm seeing a way to downgrade bootloader here as tzsw gets separated well this can be done by daring dev who can take risks.
I'm not sure about downgrading.
When i tried to repair my phone, first i tried with 5.1 sboot (eng and normal). It hangs on second file. It checks somethings before start to load real bootloader. Maybe to fill whole device with zeros with dd command (deleting pit can be enough, but also maybe it ignores PIT and read some specific bytes on sda) and then restoring phone as it is just builded in factory. Of course first to make backup of EFS etc...
Even with downgraded sboot, i'm not sure can we use 6.0 and 7.0 roms?
Best way is someone with IDA knowledge to find bytes for unlocking and we can write them to sboot with dd if="something" of =/dev/sdb bs=xx count=xy
At least it is now repairable if it is bricked after that
Good find, thanks.
How did you break the bootloader (sboot) anyway?
Dd if=sboot_from_925f of=/dev/block/sdb
I had engineering boot (kernel) with adb root access. And after that phone is dead.
On 925a sboot is on sdb (just sdb without numbers), cm.bin on sdc. Probably same on all variants.
Hi
I'm not sure I understood the hex files creation step.
Start byte : 0
End byte : 0x1FFF
Size : 8192 for Novi1.bin for example
Right ?
Yes, that's it
Just compare with my files if unsure.
OK Thanks
Congrats for this amazing guide
G928c dont know version inside.
I tried 7.0 but tool hang after novi1 transfer.
with android 6 sboot all 4 files transfer succeed but no download mode
if I do 0x3E000 to the end of the file, tool hang after 1st file.
according to customer 7.0 was inside before brick.
ok I tried different 7.0 which take me to on display usb recovery mode.
but phone not detected by pc after reset by keys now phone completely dead.
no exynos mode, no download mode nothing.
PC not sensing phone anymore.
Did you restore exynos mode?
Try to add tzsw ( novi4 should be from 0x3E000 to the end of sboot.bin).
yes I open phone and re-insert battery. Now exynos mode.
(novi4 should be from 0x3E000 to the end of sboot.bin) give me USB Recovery Mode. but as previous post no detection.
do sboot contain tzsw ?
if so what is address for tzsw ?
tzsw is from 10F000 to the end of file. But you added it and phone loaded when you made novi4 from 0x3E000 to the end of sboot.bin.
I think it is still problem with different sboot version, it must be same as version previously in phone. Try few more sboot bin.
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.
I reconfirmed version form client and he said he is sure about 7.0 version.
this variant have only 3 files of 7.0 and I tried all sboot from 3 available versions.
zogu said:
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.
Click to expand...
Click to collapse
yes this is the way but in my condition not reset after 30sec and I feel phone heat too. thats why I decide to open phone.
Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...
zogu said:
Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...
Click to expand...
Click to collapse
I also think this can be memory issue.
tried all possible ways but no success.
device returned to customer.
anyways thanks for this guide and your quick response.
:good:
I dd over sdb, BOTA0 BOTA1 RECOVERY CACHE and SYSTEM, am i sol on this one? Phone doesnt get detected by pc. Even tried unplugging the battery. For those curious why...I found out theres a partiton flag set on all of those partitions. Its SYSMAGIC X , X being a number. Lowering that number on the system by dd' ing sda18 and rebooting, results in a fw error, binary 3 device 4. Aka phone thinks system installed is lower then what it really is. I know u cant downgrade the bootloader using your method, but if u dump sdb, and edit the sysmagic line in a hex editor, dd it back. It will now be corrupt, I wonder if you can now downgrade to the version we faked. Anyone care to give it a trytry?
how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working
jhony352 said:
how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working
Click to expand...
Click to collapse
It worked for me on win 7 32 bit...
Try to reinstall Visual C++ redistributable 2012
https://www.microsoft.com/en-us/download/details.aspx?id=30679
cfg file for s6 sm-g920p
thx its working
Please can you help me from where i can download cfg file for S6 sm-g920p i have sboot.bin file it is in bin format and this file is not open and work in mfc multidownloader
So, Guys. Myself thought of writing this thread so that you can prevent yourselves from entering into danger as well as get rid of it even if you enter by mistake.
As you all know that, we are currently facing an issue of SIM offline, myself got into the trouble (as per me, when i insert a sim in sim 1, device recognizes the network provider but there is no signal. sim 2 is fine) and inorder to rectify that issue, i tried all possible ways like deleting IMEI and rewriting it, changing modem etc.
But nothing worked and so thought of using NOKIA CARE SUIT (NCS) >> Product Support Tool For Store 5
& change the firmware to Nokia X2DS RM-1013 059V782 v2.1.0.13 which was the biggest mistake which i ever committed and it resulted in hard brick.
I suggest everyone not to flash 2.1.0.13 version please
In my case, i was not even able to use the volume buttons and power button inorder to get to bootloader or custom recovery. Trust me, i'm not a noob but i do know the situation in which i'm and searched everywhere and took help of lots of guys and finally found the solution to it.
Just follow these steps:
A. Requirements:
1. Nokia Firmware - Thanks to Firmware27
2. QPST_2.7.422
3. QDLoader HS-USB Driver
B. Procedure:
1. Extract Requirement - 1, 2, 3 separately.
2. Now Install requirement - 2 & in Requirement - 3, just install Setup
3. Now connect USB to NOKIA X2 & Laptop/PC
4. Click on the start menu and type QFIL in search box and open it.
5. Under "SELECT PROGRAMMER", click on the browse button and
select "rm1013_2.1.0.13_user_prog_emmc_firehose_8x10. mbn" from the Requirement - 1
6. Under "DOWLOAD", you will find "LOAD XML" and now click on that and a window will appear infront you :silly:
7. Now in the window, type *.xml in the file name so that the xml files will show up.
8. Now select "rm1013_2.1.0.12_059V787_001_rawprogram_unsparse_ui"
9. Soon another window will show up automatically and now type *.xml in the file name so that the xml files will show up.
10. Now select "P12026702dpi600_label_layout"
11. Now Click on the "DOWNLOAD" just button below the Load XML button.
- Make sure your device is connected to the PC/lappy through cable :silly:
Everything is done. Now sit back and Relax.
Your NOKIA X2 will bootup and it looks exactly like device when you purchased except the scratches and all
Note:
I'm not responsible if your device is bricked. Ofcourse if you are doing this, it means that your device might have already been bricked and i guess there is no other way except this to make it right
This works with all the snapdragon chipset devices.
my phone just showing QHSUSB_BULK but it get warning mode, after i install that files it get qloader 9008
but when i download with qspt it get on sahara cannot working
frnsl3 said:
my phone just showing QHSUSB_BULK but it get warning mode, after i install that files it get qloader 9008
but when i download with qspt it get on sahara cannot working
Click to expand...
Click to collapse
The only prob is OS which you are using and Drivers..
Thx, its helped me
Dear,
I am also having the same issue and tried ur method . But I am not able to install the last set up u provided under 2. QPST_2.7.422. it says as "The following package files could not be found:
C:\Users\AMR\Downloads\BallardAppCraftery.CraftyFileViewer_epyrqhfctk40t!App\2. QPST_2.7.422\vcredist_x86\vcredist_x86."exe subsequently the QFIL is not downloading the .xml content. A help would be greatly appreciated.
Kuttappan555 said:
Dear,
I am also having the same issue and tried ur method . But I am not able to install the last set up u provided under 2. QPST_2.7.422. it says as "The following package files could not be found:
C:\Users\AMR\Downloads\BallardAppCraftery.CraftyFileViewer_epyrqhfctk40t!App\2. QPST_2.7.422\vcredist_x86\vcredist_x86."exe subsequently the QFIL is not downloading the .xml content. A help would be greatly appreciated.
Click to expand...
Click to collapse
if you are saying that you cannot download from the link i provided.....i just checked it. Itz working fine. i saved it in my g-drive and shared the link
Hi, I tried this and everything worked fine but phone didn't boot up. I mean the flashing worked but phone did not reboot. Screenshot attached. Do you know what is missing?
Is this method still working?
Hard Bricked
Still Working??
Can someone re-upload these files or point to the right direction?
Hi,
It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device.
To get it back, I tried to follow the tutorial on lumiafirmware website.
Code:
thor2 -mode uefiflash -ffufile "C:\Users\sylva\Downloads\RM1116_1078.0053.10586.13169.12732.034E13_retail_prod_signed.ffu" -do_full_nvi_update -do_factory_reset
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile C:\Users\sylva\Downloads\RM1116_1078.0053.10586.13169.12732.034E13_retail_prod_signed.ffu -do_full_nvi_update -do_factory_reset
Process started Thu Oct 24 16:58:36 2019
Logging to file C:\Users\sylva\AppData\Local\Temp\thor2_win_20191024165836_ThreadId-16276.log
Debugging enabled for uefiflash
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)
I tried this too: xdabloger.blogspot.com/2016/04/finally-unbrick-your-lumia-device_28.html
The app told me it was downloading the urgency files, then «Operation failure» message, I guess it doesn't manage to connect to the phone.
I had a look here too forum.xda-developers.com/windows-10-mobile/tutorial-how-to-rescue-lumia-emergency-t3434825 , but I didn't find the hex file I need…
Any magic solution ?
First you should have a look at your device manager: is there an USB Device as Nokia Emergency or Qualcomm USB or Comm Port? Assign to this device the Nokia Emergency driver which came with WDRT.
Download the Emergency files from LumiaFirmware, if not already done.
Modify this command line according to your needs:
thor2 -mode emergency -hexfile "MPRG8992_fh.ede" -edfile "RM1104_fh.edp" -ffufile "RM1104_1078.0053.10586.13169.13756.034EE9_retail_prod_signed.ffu"
For me, it worked as charm on my Lumia 950 XL.
Thanks for your answer, sadly in the device panel I only have an unknow one regarding the phone … :crying:
I suggest to change USB cable and USB port. I think as there is an unknown USB device it can't be recognized properly. Also you might append a screenshot of your device manager, especially the Details tab of the properties window. Normally. a Lumia 950 XL is "unkaputtbar", but I've also a device, which is not even recognized as an unknown device. You may also PM me, if you have a different preferred language... For me. FR, IT, HU also work... ES not really, I can read it.
I noticed that the post is on 2019 I thought it's new, sorry about that... any way the steps might be helpful for others.
I faced this problem exactly, I accidentally disconnect the cable while it was flashing and the mobile got dead as your situation.
The possible solution which saved me is this:
Create folder name it "Products"
Create folder name it "RM-1116"
Copy all your flash files into "RM-1116" if you don't have everything go to lumiafirmware.com and download all the files related to your device
Move the folder "Products" Into somewhere you can access it later
Now open Windows Devices Recovery Tool
In the dots at right-bottom click and choose "Settings"
Go to "Packages"
Active "Use Custom Package path"
Click "Browser" then choose the root folder that you copied "Products" folder into... (select the root folder not the "Products" folder)
i.e. Choose "D:\Custom Packages" -> "Custom Packages contains "Products"
Now Connect you mobile to the computer
wait a little after turn on
Choose "My Device was not detected"
Choose "Lumia"
Once you mobile connected probably you will see it listed
Click on it and recover the system
This should work hopefully.
I've bricked 950XL and in the device manger i can see the qualcomm serial device
Now i wanted to download the Windows Device Recovery Tool
-------
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:b63fac0c-501e-0003-2f80-4c2de5000000 Time:2021-05-19T07:30:29.8362829Z</Message>
</Error>
-------
I have no idea how i can recover my phone
mathewm said:
I've bricked 950XL and in the device manger i can see the qualcomm serial device
Now i wanted to download the Windows Device Recovery Tool
-------
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:b63fac0c-501e-0003-2f80-4c2de5000000 Time:2021-05-19T07:30:29.8362829Z</Message>
</Error>
-------
I have no idea how i can recover my phone
Click to expand...
Click to collapse
bad news microsoft has finally retired the Windows Device Recovery Tool and the last only method to recover a lumia device
according to this thread in Microsoft forum (In Spanish) and is for the end of support of W10M in 2020
From what I understand there is not an installer that does not use the internet as well as the drivers to be able to recover the device
I quote verbatim what he meant
"I can tell you that the Windows Device Recovery Tool is no longer available for download, nor is it functional on computers that are still installed, due to the end of the life cycle of Windows Phone 8.1 in June 2019 and the end Windows 10 mobile support cycle in June 2020"
Sorry for those bad news but I had an lumia 640xl and in order to test windows rt or windows ARM I need the WDRT for drivers and to downgrade my device to WP8.1
MauriJ2001 said:
bad news microsoft has finally retired the Windows Device Recovery Tool and the last only method to recover a lumia device
according to this thread in Microsoft forum (In Spanish) and is for the end of support of W10M in 2020
From what I understand there is not an installer that does not use the internet as well as the drivers to be able to recover the device
I quote verbatim what he meant
"I can tell you that the Windows Device Recovery Tool is no longer available for download, nor is it functional on computers that are still installed, due to the end of the life cycle of Windows Phone 8.1 in June 2019 and the end Windows 10 mobile support cycle in June 2020"
Sorry for those bad news but I had an lumia 640xl and in order to test windows rt or windows ARM I need the WDRT for drivers and to downgrade my device to WP8.1
Click to expand...
Click to collapse
good news.
I could download the file from Microsoft and install it.
The download only worked with my Android Smart Phone (don't know why)
The installation worked too!
Test with the phone i can do in 2 hours
I tried to recover the phone
Possible with instructions
Bricked 950XL
Hi, It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device. To get it back, I tried to follow the tutorial on lumiafirmware website. thor2 -mode...
forum.xda-developers.com
but after the WDRT said... Waiting for reconnection the phone ist no shown anymore in the device manager.
I think now it is completely dead
mathewm said:
I tried to recover the phone
Possible with instructions
Bricked 950XL
Hi, It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device. To get it back, I tried to follow the tutorial on lumiafirmware website. thor2 -mode...
forum.xda-developers.com
but after the WDRT said... Waiting for reconnection the phone ist no shown anymore in the device manager.
I think now it is completely dead
Click to expand...
Click to collapse
I think (I'm newbie in Windows mobile development) the phone has a sudden death at this point you can only recover the phone using programming tools or JTAG
Check again if you can enter to download or serial mode and reflash using the Thor2 method or with windows phone internals if not the phone needs to be recovered with JTAG method
This my opinion and can or can't be asserted (based I'm my experience with android phones I didn't see a hard brick on lumia devices)
Did you succeed or do you need further help?
Best regards, Joachim