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
Please Help me
My nokia lumia 520 is dead in QHSUSB_DLOAD?
Pc/ device manager/other devices show me ?QHSUSB_DLOAD
Help meeee
fix the QHSUSB_DLOAD brick
I had this the other day but I got it fixed that is if you can still access flash mode (red screen with giant nokia logo)
1. press VOL - and POWER for 10 seconds
2. go to the cellomania website just type in on google "cellomania ffu downloader", click on the first link witch has a pixelated C as its icon next to the website name put in your product code it should be 059XXXX
3. download all required files such as XXXX.pcx or XXXX.XXXX.XXXXX.ffu
4. download nokia care suite its easy to find just type it in on google and it should appear
5. once nokia care suite has installed go to C:\ProgramData\Nokia\Packages\Products\RM-915 and put all files in there
6. then open product support tool for store then click work offline because as it saved locally you don't need a wifi connection
7. then click open product
8. type in RM-915 my code is RM-935 so mine is a nokia Lumia 625
9. go into programming --> recovery
10. then click your firmware files that you saved into that folder
11. it will say that it lost connection press VOL - while you plug the usb in
12. it will say it is just flashing the VPL file but in actual fact its flashing all the files
12. and finally it will say recovery completed
13. and your phone should come up with the language selection after 5 or 10 minutes
my cell phone is dead
It does not turn on, is dead
I want to umbrick with the method without tjag but i have error
-- GPT ENDs --
Can help me fix the error?
Sending OPEN_MULTI_REQ
Received valid response to OPEN_MULTI_REQ
Checking eMMC read / write test results...
Failed to read number of eMMC sectors. eMMC is not working!!
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 12.00 seconds.
Unknown error code.
THOR2 1.8.2.18 exited with error code 85035 (0x14C2B)
@ feherneoh thanks...
This problem is strange
Because my phone never dropped and used the method in two lumias 520 but show me the same Error
Was running the OS the build windows 10 mobile 10586 insider
The battery was discharged and never turned on
feherneoh:
When I connect the phone to the computer
I quickly see a green color icons connected
QHSUSB DLOAD toolkit conectivity emergency
I use windows 10 But i don't know if the are the corrects drivers to windows 10
I'm at work now
I do not remember very well but my phone is recognized immediately when connecting to the pc
feherneoh said:
In this case the reason for immediately going into emergency mode is probably that the bootrom of the SoC cannot read the eMMC. You cannot do anything without some professional tools and luck.
Click to expand...
Click to collapse
Thank you so much..
Fight for a week with this phone
And with your answer I will not fight any more
The strange thing is that I try with
2 lumias 520 and none returned to life
Please close this topic...
Ive bricked my nokia lumia 520 while trying to unlock the bootloader:
the way i did it was
Going into C:/Program Files/Microsoft Care Suite/Windows Phone Recovery Tool
and generating GPT0.bin (this file is very important)
You can generate your GPT0.bin file by inserting
Thor2 -mode ffureader C:/example directory/myfile.ffu -dump_gpt C:/example directory
and getting the right .hex file corresponding to the RKH (root key hash) you can get your RKH by booting into flash mode, opening windows phone internals,going to the info tab and finding the really long string of letters and numbers because thats your RKH
Then going into the MPRG_HEX.zip (you can find it with a quick google search)
Rename the correct hex file with your RKH to hex.hex
Then going back into command prompt and inserting
thor2 -mode emergency -hexfile C:/example/hex.hex -mbnfile C:/example/GPT0.bin -orig_gpt
Then it should take a few seconds
DO NOT REMOVE PHONE UNTIL TOLD TO!!!!!!
Then remove phone, take out the battery, insert battery and turn on the phone, you should hear a vibration and it should boot into nokia flash mode and you can go ahead and flash the ffu by:
Thor2 -mode uefiflash -ffu C:/example/flashy.ffu
Replace the example directory with your real directory
Wait 20 minutes and your phone should be fully operational
You just revived your lumia from death!
To be safe, make a backup via TRWP of your EFS partition BEFORE you flash anything! If you're not rooted, do a nandroid backup via fastboot
Steps:
1) Set your stock dialer app as default
2) Download and install “Logkit+v1.0.apk”
3) Open dialer app and enter *#800#
Scroll down to Function Switch and then tick-mark the “VoLTE”, “VoWifi” and “VTSwitch”. Exit from app and reboot phone. Go to Settings->Wi-Fi & Network->Sim & Network->Sim 1 and enable “VoLTE” & “Wi-Fi Calling” options. Repeat step for SIM 2 if necessary. Reboot phone.
4)Download and install to PC “QPST_2.7.496” + “qud.win.1.1_installer_10061.1.zip”
5) Enable Developer options and “USB debugging”
6) Download and install “engineeringmode_V1.01.0.171117173719.25c8842-26.apk”
Open dialer app and enter *#801#
Set “Full-port switch” to ON
7) Connect your phone to PC via USB and allow USB debugging on phone
Run ADB as administrator (if you haven’t download and install to your PC)
In CMD:
ADB reboot ftm
You should see some Chinese characters on display
8) Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6"
9) In CMD:
ADB shell
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
10) Run “as administrator” PDC from QPST package. Select “Qualcomm HS-USB WWAN Adapter 9091” from list. In some cases PDC can’t connect to your phone. There is a strange solution:
Run EFS explorer from QPST package “as administrator”, select device with filled "EFS" and "Banner" fields and connect to your phone. In the moment of connection PDC works as excepted. Listing of EFS explorer takes a lot time, but after successful connection PDC stops working again. Close EFS and repeat step to finish all following steps in PDC.
In PDC right click on "Oversea-Commercial_DS" and deactivate “Sub0” and “Sub1”
Click on “Oversea-Commercial_DS” again and click remove.
Select “India-VoLTE-Vodafone”, right click and SetSelectedConfig for both “Sub0” and “Sub1”. Then click Activate button. Close PDC.
11) Download and extract “Audio+codec+EVS+HD+.zip”
Run EFC explorer “as administrator” and connect to your phone if not done earlier.
Backup to PC “overideconfig” and “overideconfig_Subscription01” from “/efsprofiles/” folder.
Replace “overideconfig” and “overideconfig_Subscription01” from “Audio+codec+EVS+HD+.zip” package with “Discard” “Clean-Up Option”. (Right click on file, “copy Data File from PC..”)
12) In ADB:
ADB reboot
13) Install “com.oem.oemlogkit_1.0.200929184727.270d7d2-1.apk” to return stock logkit.
14) Open dialer app and enter *#801#
Set “Full-port switch” to OFF
15) Disable USB Debugging if necessary.
16) Set back your custom dialer if necessary.
That’s all. You have VoLTE/VoWiFi/ViLTE/EVS HD+ codec. Icons in dialer and curtain.
After update to latest version VoLTE was not working again. I think we should repeats this step after every update, until OnePlus (if) fixed this issue.
Hello.
Does the step 9 has to be done , becouse i cant get a connection with efs explorer. Its just blank. I ask becouse i have volte and vowifi activated but my phone wont turn automatic to vowifi when i get a wifi connection. i have to first turn off volte and reboot that the phone connects to vowifi
zorantoma
Hi. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
vip77 said:
To be safe, make a backup via TRWP of your EFS partition BEFORE you flash anything! If you're not rooted, do a nandroid backup via fastboot
Steps:
1) Set your stock dialer app as default
2) Download and install “Logkit+v1.0.apk”
3) Open dialer app and enter *#800#
Scroll down to Function Switch and then tick-mark the “VoLTE”, “VoWifi” and “VTSwitch”. Exit from app and reboot phone. Go to Settings->Wi-Fi & Network->Sim & Network->Sim 1 and enable “VoLTE” & “Wi-Fi Calling” options. Repeat step for SIM 2 if necessary. Reboot phone.
4)Download and install to PC “QPST_2.7.496” + “QUD.WIN.1.1+Installer-10037.3+Setup.zip”
5) Enable Developer options and “USB debugging”
6) Download and install “engineeringmode_V1.01.0.171117173719.25c8842-26.apk”
Open dialer app and enter *#801#
Set “Full-port switch” to ON
7) Connect your phone to PC via USB and allow USB debugging on phone
Run ADB as administrator (if you haven’t download and install to your PC)
In CMD:
ADB reboot ftm
ADB shell
setprop sys.usb.config diag,serial_cdev,rmnet,adb
You should see some Chinese characters on display
8) Run “as administrator” PDC from QPST package. Select “Qualcomm HS-USB WWAN Adapter 9091” from list. In some cases PDC can’t connect to your phone. There is a strange solution:
Run EFS explorer from QPST package “as administrator” and connect to your phone. In the moment of connection PDC works as excepted. Listing of EFS explorer takes a lot time, but after successful connection PDC stops working again. Close EFS and repeat step to finish all following steps.
In PDC right click on "Oversea-Commercial_DS" and deactivate “Sub0” and “Sub1”
Click on “Oversea-Commercial_DS” again and click remove.
Select “India-VoLTE-Vodafone”, right click and SetSelectedConfig for both “Sub0” and “Sub1”. Then click Activate button. Close PDC.
9) Download and extract “Audio+codec+EVS+HD+.zip”
Run EFC explorer “as administrator” and connect to your phone if not done earlier.
Backup to PC “overideconfig” and “overideconfig_Subscription01” from “/efsprofiles/” folder.
Replace “overideconfig” and “overideconfig_Subscription01” from “Audio+codec+EVS+HD+.zip” package with “Discard” “Clean-Up Option”. (Right click on file, “copy Data File from PC..”)
10) In ADB:
ADB reboot
11) Install “com.oem.oemlogkit_1.0.200929184727.270d7d2-1.apk” to return stock logkit.
12) Open dialer app and enter *#801#
Set “Full-port switch” to OFF
13) Disable USB Debugging if necessary.
14) Set back your custom dialer if necessary.
That’s all. You have VoLTE/VoWiFi/ViLTE/EVS HD+ codec. Icons in dialer and curtain.
View attachment 5202729View attachment 5202731View attachment 5202727View attachment 5202725
Click to expand...
Click to collapse
hi i have a problem, i can't connect my op8 to efs file explore, it tells me it is not supported
Hi,
patonovich
Same question. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
Also, what Build number and Model you have? Attach screenshot
vip77 said:
Hi,
patonovich
Same question. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
Also, what Build number and Model you have? Attach screenshot
Click to expand...
Click to collapse
Yes Qualcomm appears, I could change the data with pdc, but i can't copying the files, it tells me that the cell phone is not compatible, sorry my English google translator
this is what i get when i run efs explorer
patonovich said:
Yes Qualcomm appears, I could change the data with pdc, but i can't copying the files, it tells me that the cell phone is not compatible, sorry my English google translator
Click to expand...
Click to collapse
zorantoma said:
this is what i get when i run efs explorer
Click to expand...
Click to collapse
Ok, folks. I checked again on clean device and latest version OS 11.0.4.4.IN21AA. there are some changes.
It's seems like QPST need COM device to communicate.
Disconnect your phone.
Update Qualcom driver to newer version (download in attachments 1st post section).
Connect your phone.
After "ADB reboot ftm" command BEFORE entering shell and "setprop sys.usb.config diag,serial_cdev,rmnet,adb" (look at updated command) :
Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6". After that, enter to ADB shell and use command "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" (edited). You should see your phone in EFS Eplorer and able to connect (select device with filled "EFS" and "Banner" fields. look at screenshot).
After update to latest version VoLTE was not working again. I think we should repeat this steps after every update, until OnePlus (if) fixed this issue.
vip77 said:
Ok, folks. I checked again on clean device and latest version OS 11.0.4.4.IN21AA. there are some changes.
It's seems like QPST need COM device to communicate.
Disconnect your phone.
Update Qualcom driver to newer version (download in attachments 1st post section).
Connect your phone.
After "ADB reboot ftm" command BEFORE entering shell and "setprop sys.usb.config diag,serial_cdev,rmnet,adb" (look at updated command) :
Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6". After that, enter to ADB shell and use command "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" (edited). You should see your phone in EFS Eplorer and able to connect (select device with filled "EFS" and "Banner" fields. look at screenshot).
After update to latest version VoLTE was not working again. I think we should repeat this steps after every update, until OnePlus (if) fixed this issue.
Click to expand...
Click to collapse
WOW thanks
patonovich said:
WOW thanks
Click to expand...
Click to collapse
Please report if everything went well. Good luck.
del
Thank you, it worked.
BR
Working great on OP8T,
Before this guide the Volte profile was change to the default oversea profile.
Thanl you.
UPDATE -
for some reason the OVERSEA profile is active , and volte is lost.
after that i change overideconfig files to Read only after
i copy the file to efsprofiles ,
its work for now for two days in row ,
before that the phone change to ovesea profile in half day.
not working :/
i tried exactly this and not working op8t
Grigiac said:
not working :/
i tried exactly this and not working op8t
Click to expand...
Click to collapse
What exactly "not working" which step?
vip77 said:
What exactly "not working" which step?
Click to expand...
Click to collapse
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Grigiac said:
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Click to expand...
Click to collapse
Do you have VOLTE supported and activated by carrier? Be sure using Sim slot 1 also.
vip77 said:
Do you have VOLTE supported and activated by carrier? Be sure using Sim slot 1 also.
Click to expand...
Click to collapse
yes, i did it with pdc on my last device op6 with other guide and work great
but now i have new device and tried with this guide..
and im using slot 1
i have no idea why its not working :/
Grigiac said:
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Click to expand...
Click to collapse
On which country are you?
Dreamelba said:
On which country are you?
Click to expand...
Click to collapse
Israel
tried India & telfonica uk
Nothing work
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
Hi,
my rm-914 won`t flash LK Bootloader. Bootloader was unlocked succesfully with WP Internals but i got errors when i try to install lk using uefi2lk.cmd.
Any help???
This flasher is for x86_64 (64bit) Windows, Installer for Lumia 520 (fame)
If you don't have a full backup of your phone yet, stop right here and use Win32 Disk Imager
Press any key to continue . . .
Are you REALLY sure you backed it up?
Press any key to continue . . .
Okay, don't blame me if something goes wrong, it will be your fault...
Press any key to continue . . .
Make sure there are no other phones connected to the PC
Disconnect every Android and Windows based device
Turn your phone off
Remove and re-insert the battery
Connect it to the PC after pressing ENTER
Press any key to continue . . .
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe -mode rnd -asciimsgreq NOKD -asciimsgresp NOKD -skip_com_scan
Process started Sun Apr 10 00:15:06 2022
Logging to file C:\Users\sasza\AppData\Local\Temp\thor2_win_20220410001506_ThreadId-7640.log
Initiating do RnD operations
WinUSB in use.
Debugging enabled for rnd
Starting to handle ASCII message
Sending ASCII message request : NOKD
THOR2_ERROR_TO_COMMUNICATE_WITH_UEFI_IN_DEVICE
THOR2 1.8.2.18 exited with error code 84103 (0x14887)
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe -mode thor2 -mode uefiflash -partitionname UEFI -partitionimagefile DATA\EMMCBOOT.mbn
Process started Sun Apr 10 00:15:18 2022
Logging to file C:\Users\sasza\AppData\Local\Temp\thor2_win_20220410001518_ThreadId-12580.log
Debugging enabled for partitionimageflash
Initiating flash of partition image operations
WinUSB in use.
Using programming of partition image method
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Detecting UEFI responder
Lumia UEFI Application did not respond to version info query
Device is not in Lumia UEFI mode
Device mode get failed, mode is 6
Unknown UEFI responder
Cannot flash partition image. Write the RDC into the device or use open/RnD HW & SW
Operation took about 3.00 seconds.
THOR2_ERROR_UEFI_RDC_OR_AUTHENTICATION_REQUIRED
THOR2 1.8.2.18 exited with error code 84214 (0x148F6)
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe -mode rnd -reboot
Process started Sun Apr 10 00:15:21 2022
Logging to file C:\Users\sasza\AppData\Local\Temp\thor2_win_20220410001521_ThreadId-12832.log
Initiating do RnD operations
WinUSB in use.
Debugging enabled for rnd
Detecting UEFI responder
Send HELLO
Send HELLO
Send HELLO
Send HELLO
Send HELLO
Lumia UEFI Application did not respond to version info query
Device is not in Lumia UEFI mode
Reading device mode failed
Exited with success
< waiting for device >
Done. Lumia must be in fastboot mode to do this (tap power and volume down for 10 sec and release to run fastboot mode till phone vibrate).
But after LK flashing only Android Kernel Works, TWRP wont install with adb commands, no android partitions on internal memory, can`t create partitions from adb commands.
I can boot twrp but can`t wipe partition too. TWRP says that internal memory have 0 MB. What to do? Any suggestions? Recovery to WIndows Phone from WIn32Imager don`t work. Only MinOS and Data partitions are accesible.
Done.
I did restore WP8 from WIn32Image backup once again with success using those instruction:
Restore Windows Phone 8 if you have Android installed (Windows instructions)
Thanks to @feherneoh who posted the content of this thread originally here:Post #1 Post #2 NOTE: DO NOT ask for a backup. If you do not have one, you have to accept to be permanently on Android like me. Create a folder somewhere that we can...
forum.xda-developers.com
Something went wrong as in this manual - linux partitions are not set up!!! ->
Second try... ALL OK. Instructio is ok.
wlodar2wwa said:
Done. Lumia must be in fastboot mode to do this (tap power and volume down for 10 sec and release to run fastboot mode till phone vibrate).
But after LK flashing only Android Kernel Works, TWRP wont install with adb commands, no android partitions on internal memory, can`t create partitions from adb commands.
I can boot twrp but can`t wipe partition too. TWRP says that internal memory have 0 MB. What to do? Any suggestions? Recovery to WIndows Phone from WIn32Imager don`t work. Only MinOS and Data partitions are accesible.
Click to expand...
Click to collapse
Second time, no fastboot mode is needed.
Did you manage to fix the 0 mb issue?
TabbyBeni said:
Did you manage to fix the 0 mb issue?
Click to expand...
Click to collapse
the second time everything loaded correctly.